Decision owner
Change control board
The named role remains accountable for the consequential decision.
Aerospace & Defense
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
This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.
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.
A proposed change replaces a hydraulic actuator seal material to address a supplier obsolescence.
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.
The final decision is auditable and tied to the frozen evidence, cost, schedule, open questions, and approving authority.
Step 1 of 5
| Field | Value |
|---|
| Field | Value |
|---|
The output appears here immediately. More technical evidence remains available below.
The demonstration keeps deterministic controls, AI assistance, and approval separate.
Source systems enforce identity, workflow order, policy filters, and record updates.
Retrieval and generation assemble relevant evidence into a cited recommendation or draft.
Change control board verifies material claims and approves the consequential action.
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.
Automated stage
What happens: Review the proposed seal-material change, its justification, affected programs, target board date, and proposed effectivity before analysis begins.
Why it matters: A consistently classified change request gives every downstream resolver the same scope and baseline.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/change-intake-and-classification
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Traverse requirement and bill-of-material links to enumerate invalidated verification evidence, affected parts, stock, effectivity, and fielded units.
Why it matters: The board receives a measured blast radius instead of a subjective estimate.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/requirement-and-bom-traceability-expansion
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Test engineering reviews qualification links and records whether each test needs full, delta, or no requalification, including cost and duration.
Why it matters: Certification cost and schedule consequences are visible before approval.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/requalification-determination
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Retrieve the technical-order and illustrated-parts-catalog sections whose content or effectivity the material change invalidates.
Why it matters: Publication work is scoped before release, reducing late manual discovery.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/publication-impact-scoping
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Present the consolidated impact assessment to the change-control board and require a named human approver before the disposition is recorded.
Why it matters: The final decision is auditable and tied to the frozen evidence, cost, schedule, open questions, and approving authority.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/change-control-board-disposition
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Run a stage to see its explanation, evidence, full request, and full response.
Ask a question and receive an answer grounded in retrieved EngineeringChangeRequest evidence.
Select a starter question or enter your own.
Loaded live from /api/config, /api/domain/model, and
/api/domain/sample.
engineeringChangeRequests/tenantId + /changeRequestIdA 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.
| Container | Role | Hierarchical partition key | Document types |
|---|---|---|---|
engineeringChangeRequests |
Primary | /tenantId + /changeRequestId |
ChangeRequest, RequirementLink, BomImpact, QualificationTestLink, ImpactAssessment |
technicalPublicationLibrary |
Reference | /tenantId + /ataChapter |
PublicationImpactChunk |
| 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 |
List requirements whose verification the change invalidates and that therefore need reverification.
engineeringChangeRequests
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.changeRequestId = @changeRequestId AND c.type = 'RequirementLink' AND c.invalidatedByChange = true ORDER BY c.requirementLevel ASC
Quantify how many fielded units and how much existing stock the effectivity change disturbs.
engineeringChangeRequests
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.changeRequestId = @changeRequestId AND c.type = 'BomImpact' AND c.interchangeabilityClass != 'fullyInterchangeable' ORDER BY c.fieldedUnitCount DESC
Rank qualification tests requiring repeat or delta qualification by cost and duration.
engineeringChangeRequests
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.changeRequestId = @changeRequestId AND c.type = 'QualificationTestLink' AND c.requalificationVerdict IN ('fullRequalification','deltaQualification') ORDER BY c.estimatedTestCostUsd DESC
Find publication sections whose effectivity or content the change invalidates so updates are scoped before release.
technicalPublicationLibrary
partition-key-fan-out
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.ataChapter IN (@affectedAtaChapters) AND c.type = 'PublicationImpactChunk' ORDER BY RANK RRF(VectorDistance(c.chunkVector, @changeVector), FullTextScore(c.chunkText, @queryTerms))