Aerospace & Defense

Technical Maintenance Copilot

Designed for Maintenance engineer

Get the maintenance engineer from a reported fault on a specific tail number to the correct effective technical order procedure for that aircraft's exact configuration, with airworthiness directives, service bulletins and parts availability resolved before the task card is released.

Contract AER-01 · primary aggregate AircraftMaintenanceContext · mode loading

Decision brief

Certifying staff release and sign-off: 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

Licensed certifying engineer

The named role remains accountable for the consequential decision.

Governed evidence

6 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 tail reports an intermittent left-hand air data computer disagree during climb with two ACARS fault codes in ATA 34.

Decision to make

Get the maintenance engineer from a reported fault on a specific tail number to the correct effective technical order procedure for that aircraft's exact configuration, with airworthiness directives, service bulletins and parts availability resolved before the task card is released.

Outcome to show

releasedTaskCard gives Licensed certifying engineer the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Fault intake and ATA classification
  2. 2Configuration effectivity resolution
  3. 3Directive and bulletin compliance check
  4. 4Task card assembly with parts and tooling
  5. 5Certifying staff release and sign-off

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

Licensed certifying engineer 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 AircraftMaintenanceContext 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 the maintenance engineer from a reported fault on a specific tail number to the correct effective technical order procedure for that aircraft's exact configuration, with airworthiness directives, service bulletins and parts availability resolved before the task card is released.
Primary aggregate
AircraftMaintenanceContext
Primary container
aircraftMaintenanceContexts
Hierarchical key
/tenantId + /tailNumber
Schema version
1

Sample scenario

A tail reports an intermittent left-hand air data computer disagree during climb with two ACARS fault codes in ATA 34. The copilot finds the same symptom twice in the last 200 flight hours, resolves that this tail carries the post-modification ADC part number so only revision 14 of the troubleshooting procedure is effective, and retrieves the isolation steps with their required avionics qualification and static-discharge warnings. It flags an open service bulletin on the pitot-static harness that is applicable to this serial range and due in 40 flight hours, recommending it be accomplished in the same visit. The certifying engineer releases a combined task card with the ADC test set, the harness kit and both cited revisions frozen.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
aircraftMaintenanceContexts Primary /tenantId + /tailNumber Aircraft, ConfigurationItem, FaultReport, DirectiveCompliance, TaskCardDraft
technicalOrderLibrary Reference /tenantId + /ataChapter TechnicalOrderChunk

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
Aircraft aircraftMaintenanceContexts /tenantId + /tailNumber aircraft::{tailNumber} None
ConfigurationItem aircraftMaintenanceContexts /tenantId + /tailNumber aircraft::{tailNumber}::config::{ataChapter}::{positionCode} None
FaultReport aircraftMaintenanceContexts /tenantId + /tailNumber aircraft::{tailNumber}::fault::{reportedAtUtc}::{faultReportId} symptomVector
TechnicalOrderChunk technicalOrderLibrary /tenantId + /ataChapter ata::{ataChapter}::techorder::{toDocId}::{chunkOrdinal} chunkVector
DirectiveCompliance aircraftMaintenanceContexts /tenantId + /tailNumber aircraft::{tailNumber}::directive::{directiveNumber} None
TaskCardDraft aircraftMaintenanceContexts /tenantId + /tailNumber aircraft::{tailNumber}::taskcard::{taskCardId} None

Query patterns