Aerospace & Defense

Engineering Change Impact Copilot

Designed for Configuration manager

Let the configuration manager see the true blast radius of a proposed engineering change: which requirements, parts, effectivity ranges, qualification tests and publications it disturbs, so the change board decides with the affected artifacts enumerated rather than estimated.

Contract AER-03 · primary aggregate EngineeringChangeRequest · mode loading

Decision brief

Change control board disposition: 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

Change control board

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 proposed change replaces a hydraulic actuator seal material to address a supplier obsolescence.

Decision to make

Let the configuration manager see the true blast radius of a proposed engineering change: which requirements, parts, effectivity ranges, qualification tests and publications it disturbs, so the change board decides with the affected artifacts enumerated rather than estimated.

Outcome to show

The final decision is auditable and tied to the frozen evidence, cost, schedule, open questions, and approving authority.

  1. 1Change intake and classification
  2. 2Requirement and BOM traceability expansion
  3. 3Requalification determination
  4. 4Publication impact scoping
  5. 5Change control board disposition

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

Change control board 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 EngineeringChangeRequest 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
Let the configuration manager see the true blast radius of a proposed engineering change: which requirements, parts, effectivity ranges, qualification tests and publications it disturbs, so the change board decides with the affected artifacts enumerated rather than estimated.
Primary aggregate
EngineeringChangeRequest
Primary container
engineeringChangeRequests
Hierarchical key
/tenantId + /changeRequestId
Schema version
1

Sample scenario

A proposed change replaces a hydraulic actuator seal material to address a supplier obsolescence. Traceability expansion enumerates 23 affected requirements, 6 of whose verifications are invalidated because they relied on the original material's temperature performance, 4 part numbers across two effectivity ranges with 118 fielded units not fully interchangeable, and a requirement to delta-qualify the thermal cycling test at 340,000 dollars and 62 days. Publication scoping identifies 11 sections across two technical orders and the illustrated parts catalog. The board approves the change with the delta qualification funded, and the frozen assessment drives the publication update and effectivity cut-in.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
engineeringChangeRequests Primary /tenantId + /changeRequestId ChangeRequest, RequirementLink, BomImpact, QualificationTestLink, ImpactAssessment
technicalPublicationLibrary Reference /tenantId + /ataChapter PublicationImpactChunk

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
ChangeRequest engineeringChangeRequests /tenantId + /changeRequestId change::{changeRequestId} changeVector
RequirementLink engineeringChangeRequests /tenantId + /changeRequestId change::{changeRequestId}::requirement::{requirementId} requirementVector
BomImpact engineeringChangeRequests /tenantId + /changeRequestId change::{changeRequestId}::bom::{partNumber}::{positionCode} None
QualificationTestLink engineeringChangeRequests /tenantId + /changeRequestId change::{changeRequestId}::test::{testPlanId} None
PublicationImpactChunk technicalPublicationLibrary /tenantId + /ataChapter ata::{ataChapter}::publication::{pubDocId}::{chunkOrdinal} chunkVector
ImpactAssessment engineeringChangeRequests /tenantId + /changeRequestId change::{changeRequestId}::assessment::{assessmentId} None

Query patterns