Illustrative reference architecture. Validate requirements for your organization.
Illustrative architecture: A mine operations team sees recurring haul-truck faults while production plans and workshop capacity change across shifts. Supervisors need to understand equipment evidence, open inspections, parts, and crew qualifications before assigning work. Agents prepare coordination packets without controlling vehicles, ventilation, blasting, or safety systems.
Problem
Fault codes can repeat after an unresolved repair, telemetry links may be intermittent, and shift handoffs lose context. Optimizing maintenance solely around production targets can obscure inspection requirements or assume equipment is available when it remains restricted.
Why a multi-agent system?
Condition, inspection, resource, and handoff specialists reconcile distinct operational records. Deterministic scheduling respects supervisor-approved constraints, and every proposal carries the equipment's authoritative restriction state.
Intended outcome
The intended result is a reviewable operational decision with source evidence and explicit ownership. Measure evidence readiness and task ownership before attributing changes in equipment availability. Physical maintenance and safety decisions remain with qualified operational teams, whose actions should be distinguishable from agent preparation in the record.
Specialist agent team
Equipment evidence agent
Summarize fault history and operating context with telemetry quality flags.
Tools
Fleet historian
fault-code catalog
Authority boundary
Cannot clear faults, command vehicles, or declare equipment fit for service.
Inspection reviewer
Retrieve outstanding inspections, restriction records, and approved maintenance procedures.
Tools
Maintenance system query
inspection repository
Authority boundary
Cannot waive inspections or close safety findings.
Workshop planner
Match work scope to parts, bays, qualified crews, and approved windows.
Tools
Parts inventory
workshop scheduling simulator
Authority boundary
Cannot commit unsafe work or override equipment restrictions.
Shift handoff agent
Prepare a concise packet of open tasks, evidence, and named ownership.
Tools
Shift log draft API
task status reader
Authority boundary
Supervisors approve handoffs and work assignments.
Enterprise systems
Fleet and equipment systems
Provide timestamped condition data and authoritative restriction status through read-only adapters.
Maintenance and inspection platform
Owns work orders, approved procedures, inspection findings, and qualified signoffs.
Shift and resource planning systems
Track workshop capacity, crew qualifications, parts reservations, and handoff acknowledgements.
Architecture diagrams
Mine maintenance and shift evidence desk — logical architecture — Specialists produce bounded findings; the evidence ledger preserves source versions and human decisions before an authorized adapter changes a system of record.
Failure and decision sequence — An offline truck sends old fault events after reconnecting. The workflow records unresolved work and resumes only after the source state and reviewer authority are checked.
sequenceDiagram
participant O as "Case orchestrator"
participant S as "Fleet and equipment systems"
participant H as "Accountable reviewer"
O->>S: Receive buffered truck fault events
S-->>O: Events predate completed repair
O->>H: Show historical evidence without new dispatch
H-->>O: Confirm current inspection requirement
O->>S: Save approved next-shift task
Runtime flow
1
Register recurring fault
Deduplicate repeated messages while preserving count, asset identity, operating interval, and current restriction status.
2
Check evidence quality
Identify stale telemetry and distinguish repeated historical codes from newly observed faults.
3
Review open obligations
Retrieve unresolved inspections and previous repair evidence before proposing another maintenance action.
4
Evaluate workshop options
Apply bay, parts, crew, and approved access constraints; retain restriction state as a hard planning condition.
5
Obtain supervisor review
Present candidate work packages, missing evidence, and expected handoff ownership to the accountable supervisor.
6
Track approved execution
Create the authorized work order and shift handoff, then await qualified completion evidence before changing operational availability.
Failure recovery
An offline truck sends old fault events after reconnecting.
Detect: Event timestamps and sequence numbers place the messages before the latest verified repair.
Recover: Retain them as historical evidence and avoid reopening work solely from receipt order.
A shift handoff has no accepting supervisor.
Detect: The handoff remains unacknowledged beyond the configured shift transition window.
Recover: Escalate to the duty manager and keep the previous owner accountable until acceptance is recorded.
Security & decision boundaries
Keep vehicle, blasting, ventilation, and safety-control interfaces outside agent authority.
Treat equipment restrictions and outstanding inspections as authoritative planning constraints.
Require qualified signoff before maintenance completion changes availability status.
Preserve event time and device sequence when telemetry reconnects after an outage.
Bind work assignments to current crew qualifications and approved procedures.
Operational metrics
Measurement definitions, not promised improvements.
Handoff completeness
Open work items with evidence, owner, and acknowledged next shift divided by handed-off items.
Fault packet latency
Time from accepted new fault to supervisor-reviewable condition and maintenance context.
Stale event rejection
Historical reconnect events correctly excluded from new-fault triggers divided by audited stale events.
Work readiness
Approved packages with required parts, qualified crew, and current procedures divided by approved packages.
Architecture tradeoffs
Decision
Benefit
Cost
Offline-tolerant event handling
Preserves evidence from remote equipment.
Requires event ordering and duplicate reconciliation after reconnects.
Restriction-aware planning
Keeps operational constraints visible.
Production-oriented schedules may be less flexible.
Explicit handoff acceptance
Reduces orphaned tasks across shifts.
Requires supervisor participation and escalation coverage.
Rollout plan
Historical shift replay
Supervisors verify stale events, unresolved restrictions, and missing repair evidence across completed incidents.
Shadow workshop pilot
One fleet group evaluates work readiness and handoff ownership without changing equipment status.
Approved coordination launch
Work-order and handoff drafts launch after offline-reconnect and unaccepted-shift exercises pass.