Technical Maintenance Copilot
Outcome
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.
| Portfolio attribute | Value |
|---|---|
| Primary persona | Maintenance engineer |
| Primary aggregate | AircraftMaintenanceContext |
| Cosmos DB containers | 2 |
| Grounding data | technical orders, manuals, configurations, faults |
| Development estimate | USD 60-220 monthly dev estimate |
| Runtime options | Python FastAPI and C# ASP.NET Core |
Productivity hypothesis
These measures reflect the workflow, evidence, decision boundary, and industry risk for this use case.
| Impact type | Measure | Conservative internal assumption | Customer measurement |
|---|---|---|---|
| Productivity | Task cycle time | 10-20% reduction | (baseline median task minutes - assisted median task minutes) / baseline median task minutes * 100 |
| Quality or risk | Evidence discovery time | 15-25% reduction | (baseline median evidence-search minutes - assisted median evidence-search minutes) / baseline median evidence-search minutes * 100 |
Important: Conservative internal pilot assumptions only; not public benchmarks, commitments, or expected customer results. Validate against a comparable baseline or matched control cohort with mandatory human review.
Rationale: Technical orders, manuals, configurations, and fault records can shorten maintenance preparation while preserving human maintenance authority.
Pilot guardrail: Verify configuration applicability and require maintainer approval for every consequential action.
Customer validation plan
- Baseline the current workflow with representative users and tasks.
- Run the accelerator on the same task mix with human review retained.
- Measure task cycle time and evidence discovery time with the documented formulas.
- Replace internal assumptions with customer-observed results before a business case.
Why Azure Cosmos DB
This AI solution needs an operational data plane, not only a vector index:
- Hybrid vector and full-text retrieval combines semantic recall with exact identifiers, codes, names, and domain language.
- Hierarchical partition keys and metadata predicates keep tenant and domain boundaries in the normal query path.
- Operational JSON, source chunks, workflow and agent state, feedback, and audit records remain together for low-latency reads and governed writes.
- Change feed reacts to source and operational updates without polling.
- Autoscale throughput, configurable consistency, and multi-region distribution support variable demand and enterprise availability.
Domain workflow

| Stage | Actor | Input → output | Approval |
|---|---|---|---|
| 1. Fault intake and ATA classification | Maintenance controller | FaultReport → classifiedFault | Policy controlled |
| 2. Configuration effectivity resolution | Configuration resolver | ConfigurationItem → effectiveProcedureSet | Policy controlled |
| 3. Directive and bulletin compliance check | Airworthiness compliance service | DirectiveCompliance → blockingDirectiveSet | Policy controlled |
| 4. Task card assembly with parts and tooling | Technical maintenance copilot | effectiveProcedureSet → TaskCardDraft | Policy controlled |
| 5. Certifying staff release and sign-off | Licensed certifying engineer | TaskCardDraft → releasedTaskCard | Human required |
Technical architecture

Cosmos DB data model
| Container | Hierarchical partition key | Documents | Search paths |
|---|---|---|---|
aircraftMaintenanceContexts | /tenantId, /tailNumber | Aircraft, ConfigurationItem, FaultReport, DirectiveCompliance, TaskCardDraft | /symptomVectorEmbedding, /symptomVector |
technicalOrderLibrary | /tenantId, /ataChapter | TechnicalOrderChunk | /chunkVectorEmbedding, /chunkVector |
Query contract
| Query | Container | Scope | Purpose |
|---|---|---|---|
| EffectiveProcedureRetrieval | technicalOrderLibrary | single-partition | Retrieve only technical order content whose effectivity expression matches this tail's configuration baseline and revision level. |
| OpenDirectivesBlockingReturn | aircraftMaintenanceContexts | single-partition | List airworthiness directives and bulletins that are due or overdue for this tail. |
| RecurringFaultPattern | aircraftMaintenanceContexts | single-partition | Detect whether this symptom has recurred on the tail, which changes the troubleshooting path. |
| LifeLimitedComponentsDue | aircraftMaintenanceContexts | single-partition | Surface installed components approaching life limits that could be addressed in the same hangar visit. |
Python and C# services route each document type to its declared container and hierarchical partition key. ETag-based writes protect mutable aggregates, while append-only records and bounded cross-partition queries preserve scale.
Azure deployment

Clone the source repository, authenticate with Azure, and run:
Set-Location accelerators/aerospace-defense/technical-maintenance-copilot
az login
./Deploy.ps1 -Runtime python -Location eastus2
Change python to csharp to deploy the .NET implementation.
Explore the implementation
- Launch signed-in demo
- Implementation article
- Domain data model
- Workflow and API contract
- Python application
- C# application
- Domain container Bicep
- Platform Bicep
- Cost and configuration
- Source repository