Maintenance ticket triage
Sensor alarm and technician voice note become one work order, spare parts and a safe stop window included.
Maintenance ticket triage
- Alarm: bearing vibration 7.8 mm/s on press line P-03 (threshold 6.3)
- Last 48 h of vibration and temperature trend pulled from the historian
- Trend: +38% in 6 days, temperature +9 °C → developing bearing fault
- Technician note transcribed: "grinding noise on the drive side since Monday"
- Manual §7.4 and 3 similar work orders (2024–2026) retrieved
- Fault class: drive-side bearing 6312-2RS · priority P2 · 5–7 days to failure
- Spare part 6312-2RS: 2 in central store, 0 at plant → transfer needed
- Safety: LOTO procedure and 2-person rule attached, Sat 06:00 window available
- Planned stop > 4 h → shift supervisor approved the Saturday window
- Work order WO-88213 created, part transfer requested, technician assigned
Simulation · derived from real agent definitions · every agent can be built by dialogue with the Autonomous Agent and validated with a test corpus
Vibration threshold alarm from SCADA
Prioritised work order opened in the CMMS, part transfer requested, technician assigned
Agents
Maintenance Supervisor
Decomposes the objective, delegates to agents, manages approval points, merges the result.
Signal Agent
Reads trend and anomaly from historian data
get_sensor_windowdetect_anomalyField Note Agent
Transcribes the technician's voice note
transcribe_audioextract_observationsDiagnosis Agent
Classifies the fault using manuals and past work orders
search_manualssearch_work_order_historyclassify_failurePlanning Agent
Plans the work order with parts, safety and shift window
check_spare_partscreate_work_orderassign_technicianSteps
| # | Kind | Agent | What happens | System | ms | tok |
|---|---|---|---|---|---|---|
| 01 | ingest | Maintenance Supervisor | Alarm: bearing vibration 7.8 mm/s on press line P-03 (threshold 6.3) | — | 180 | — |
| 02 | tool | Signal Agent | Last 48 h of vibration and temperature trend pulled from the historian | SCADA / Historian | 420 | — |
| 03 | reason | Signal Agent | Trend: +38% in 6 days, temperature +9 °C → developing bearing fault | — | 640 | 520 |
| 04 | reason | Field Note Agent | Technician note transcribed: "grinding noise on the drive side since Monday" | — | 820 | 340 |
| 05 | retrieve | Diagnosis Agent | Manual §7.4 and 3 similar work orders (2024–2026) retrieved | Manuals & Work Order Vector Store | 480 | 760 |
| 06 | reason | Diagnosis Agent | Fault class: drive-side bearing 6312-2RS · priority P2 · 5–7 days to failure | — | 780 | 980 |
| 07 | tool | Planning Agent | Spare part 6312-2RS: 2 in central store, 0 at plant → transfer needed | SAP S/4HANA MM | 430 | — |
| 08 | verify | Planning Agent | Safety: LOTO procedure and 2-person rule attached, Sat 06:00 window available | — | 360 | 280 |
| 09 | approval | Maintenance Supervisor | Planned stop > 4 h → shift supervisor approved the Saturday window | — | 2,400 | — |
| 10 | write | Planning Agent | Work order WO-88213 created, part transfer requested, technician assigned | CMMS (Maximo) | 560 | — |
Supplier invoice three-way match
Invoice, PO and goods receipt matched in SAP automatically; only out-of-tolerance lines reach a buyer.
Warranty claim processing
Dealer claims validated for coverage, parts and labour in minutes; big amounts go to the regional manager.
Time to move from experimenting with AI to transforming with it.
In a 30-minute discovery session we take your 2–3 priority business problems, show a live demo of a similar scenario, and draft a roadmap that starts with the Value layer.
- Your 2–3 priority problems
- Live demo of a similar scenario
- Roadmap starting with value analysis