Manufacturing

Maintenance Troubleshooting Copilot

Designed for Maintenance technician

Get a maintenance technician from a fault code to a verified repair by combining equipment history, sensor evidence, manuals, and prior successful fixes, with supervisor authorization before any safety-critical intervention.

Contract MAN-01 · primary aggregate TroubleshootingSession · mode loading

Decision brief

Authorize safety-critical intervention: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Maintenance supervisor

The named role remains accountable for the consequential decision.

Governed evidence

5 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

A filler line throws a torque-limit fault for the third time this week; the copilot correlates rising drive current for 40 minutes before each trip, ranks a worn gearbox coupling ahead of a sensor fault based on two prior repairs where the sensor swap did not hold, walks the technician through the coupling inspection, and the supervisor signs the lockout permit before disassembly..

Decision to make

Get a maintenance technician from a fault code to a verified repair by combining equipment history, sensor evidence, manuals, and prior successful fixes, with supervisor authorization before any safety-critical intervention.

Outcome to show

Authorized work with a signed permit record gives Maintenance supervisor the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Report the fault at the machine
  2. 2Correlate sensor and fault evidence
  3. 3Rank causes from history and manuals
  4. 4Guide the repair step by step
  5. 5Authorize safety-critical intervention

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Maintenance supervisor verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved TroubleshootingSession evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Get a maintenance technician from a fault code to a verified repair by combining equipment history, sensor evidence, manuals, and prior successful fixes, with supervisor authorization before any safety-critical intervention.
Primary aggregate
TroubleshootingSession
Primary container
troubleshootingSessions
Hierarchical key
/tenantId + /assetId
Schema version
1

Sample scenario

A filler line throws a torque-limit fault for the third time this week; the copilot correlates rising drive current for 40 minutes before each trip, ranks a worn gearbox coupling ahead of a sensor fault based on two prior repairs where the sensor swap did not hold, walks the technician through the coupling inspection, and the supervisor signs the lockout permit before disassembly.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
troubleshootingSessions Primary /tenantId + /assetId TroubleshootingSession, AssetProfile, FaultEvent, RepairHistoryRecord
maintenanceProcedureLibrary Reference /tenantId + /procedureId MaintenanceProcedure

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
TroubleshootingSession troubleshootingSessions /tenantId + /assetId session::{assetId}::{sessionId} symptomVector
AssetProfile troubleshootingSessions /tenantId + /assetId asset::{assetId} None
FaultEvent troubleshootingSessions /tenantId + /assetId fault::{assetId}::{eventUtc}::{faultCode} None
MaintenanceProcedure maintenanceProcedureLibrary /tenantId + /procedureId procedure::{procedureId}::{stepIndex} stepVector
RepairHistoryRecord troubleshootingSessions /tenantId + /assetId repair::{assetId}::{workOrderId} rootCauseNarrativeVector

Query patterns