Diagnostic Template Descriptions
How is diagnostics automated within an IETM troubleshooting procedure?
The Diagnostician provides two services for automating diagnostics in an
IETM troubleshooting procedure: (1) identification of the part or parts that
need to be repaired, and (2) identification of the test most likely to
minimize the diagnostic effort or time (best test).
What information is required to automate an IETM troubleshooting procedure?
The Diagnostician provides its two services based on a Diagnostic Knowledge
Base (DKB) specific to the unit being troubleshooted and on the measurement
and observation results that are obtained during the troubleshooting process.
The Diagnostic Knowledge Base is developed using the Diagnostic Profiler based
on CAD data and test engineering information or troubleshooting legacy data.
Does the Diagnostician distinguish between tests and observations and
measurements?
The Diagnostician considers tests to be troubleshooting procedure units
that contain one or more observations and measurements. The Diagnostician does
not distinguish between observations and measurements or between measurements
made manually and measurements made automatically. Typically, tests will
consist of groups of observations and measurements that will always be done
together regardless of diagnostic considerations..
What IETM authoring templates are provided to automate diagnostics?
The Diagnostician services require an initial frame with a
D_LOAD_DIAGNOSTICS template to identify the diagnostic knowledge base. As
observations and measurements are made, the results must be provided to the
DiagnosticianTM using the most appropriate and convenient of the templates:
D_SET_MEAS, D_SET_MEAS_FAIL, D_SET_MEAS_PASS or D_SET_MEAS_VAL. The best test
to make next can be obtained at any time using D_GET_NEXT_TEST. The diagnostic
results can be obtained by using the D_GET_SUSPECT_COUNT and
D_GET_SUSPECT_PART templates.
What IETM authoring techniques support use of the diagnostic best test
services?
Use of the Diagnostician best test service is most easily accomplished by
centralizing the test sequencing control in one AIMSS topic and placing each
test that is to be sequenced in its own AIMSS topic or set of topics. Within
the test sequencing control topic, D_GET_NEXT_TEST is repeatedly executed
until no more tests are returned. Each time D_GET_NEXT_TEST provides a test
name, a call frame is implemented to execute the selected test.
Return to
Diagnostics Template List
Return to
Class V Products Page
