Diagnostic sessions
What a technician sends, how the agent identifies the unit, how it walks the diagnostic tree, and what every returned step must contain.
Inputs
Serial or nameplate photo (or HMI about-screen); alarm code, screenshot or log export; photos of the condition; a line of description. Any subset; the agent asks precisely for what is missing.
Unit identification
Serial → installed-base record → model, revision, firmware, options, upgrades. Hybrid units are flagged. If the serial cannot be read, candidates are narrowed by site and partial serial and a specific photo is requested.
Walking the tree
The agent retrieves the diagnostic tree for the alarm or symptom in the unit's revision, applies bulletins, reads the photos for visible conditions, and orders the checks. Cascading alarms are ordered by timestamp so the probable root is checked first.
Every step must have
- The check, in the manual's terms
- A citation: manual revision, section, page — or bulletin number
- Expected result or spec where the manual gives one
- Safety prerequisites placed before it if the manual requires them
Steps without a citation are rejected by the pipeline. If the tree has no branch for the evidence, the case escalates rather than continuing.
Turns
A session runs up to 24 hours: the technician reports a measurement, the agent returns the next steps. Photos beyond three add 0.1 case each.
Parts
Likely parts are proposed from the catalogue with supersession followed and variant checked against the unit's options; adapter kits are flagged.
Work-order summary
Drafted at session end from everything established, with references inline, in the OEM's format.