Aircraft Troubleshooting Assistant demo

Technicians ask about a fault and get the fix path, cited to manuals and fleet history 1:32

What the demo shows

Technicians ask about a fault and get the fix path, cited to manuals and fleet history

The signature screen is an outline of the aircraft with the fault's zone glowing (zone 431, the left engine strut, for a BLEED DUCT LEAK L message) and a conversation with the agents beside it. The fault reader reads the write-up and the aircraft's fault data; the manual agent cites troubleshooting task 36-11-00-810-801 for this tail's effectivity and revision; the fleet history agent finds three earlier fleet fixes (two clamps, one sensor) and which ones held; the repeat watch agent sees the second report in nine days and refuses a reset-only close. The isolation agent ranks the causes, asks the technician what they found after each step and re-ranks with reasons: night shift's passing test drops the sensor to 11%, and the technician's finding of a loose clamp with heat marks lifts the clamp to 92%. A check agent independently confirms the part in stores, the torque, the tooling, the required-inspection list and the time to departure before the technician approves the plan; stores delivers to the gate; the technician records torque and leak check; the logbook writer drafts the corrective action, every line cited; the technician signs with their certificate and the aircraft returns to service in 2.1 hours, on time. Hand-offs carry the whole conversation to the next shift, engineers answer from the full context and approve the fleet tips the agents propose, and every step is in the audit trail.

Transcript

  1. Aircraft Troubleshooting Assistant gives technicians the fixed path for a fault, cited to manuals and fleet history.
  2. Technicians spend about 60% of their day researching and troubleshooting.
  3. At Denver, N812CV leaves at 855 with a BLEED DUCT LEAK.
  4. The left strut glows, agents cite the manual task, and three fleet fixes.
  5. It's the second report in nine days, so a reset will not close it.
  6. Night shift test passed.
  7. Now the agent asks Luis what he found.
  8. Clamp loose, heat marks.
  9. The clamp jumps to 92%.
  10. A check agent confirms part, torque, and time.
  11. Luis approves. He records his readings.
  12. The agents draft the logbook entry, every line cited.
  13. Luis reviews it and signs with a certificate.
  14. Every step cited, every decision signed, every action logged.
  15. An 812CV is back in service in 2.1 hours on time.
  16. Built on Botminds: agents, data, screens, and governance on one platform.

Transcribed from the film’s narration. Captions are on the player.