CT · ENGINEERING CHANGE IMPACT ANALYSIS

ChangeTrace

Propose a change. See exactly what it affects across requirements, test procedures, analysis reports, demonstrations, and inspection checklists. Re-verify only what actually moved. ChangeTrace lets engineering teams iterate internally without over-testing unchanged subsystems, while the design stays continuously validated against the requirements baseline. When you need a compliance-ready delta package for a change review board, a customer, or a regulatory submittal, it generates one against whichever standard applies (MIL-STD-973, ISO 10007, AS9100, FDA 21 CFR 820.30, or your internal CM standard). Version 1.1 adds a 50-requirement aerospace-class reference baseline (TAP-1), polymorphic verifier registries for all four MIL-STD-961E methods, a coupling graph with per-edge standard citations, cost and schedule basis of estimate with per-facility selection, and a live Gantt that shows exactly how many weeks an ECP pushes the ready-for-flight date.

LAST UPDATED · APRIL 23, 2026
IN PRIVATE BETA

What it produces

  • Precise impact trace across a 50-requirement TAP-1 reference baseline spanning 15 subsystems and all four MIL-STD-961E verification methods (Test, Analysis, Demonstration, Inspection)
  • Re-verification scope, the minimum set of verifiers actually affected, with an explicit list of verifiers that can be safely skipped
  • Coupling cascade with citations: parametric ECPs ripple through the baseline with a rationale per edge grounded in MIL-STD-461G App A, MIL-HDBK-217F, MIL-STD-1629A, or the relevant governing standard
  • Method Rationale per requirement: why each verification method was selected (feasibility, precision, cost/risk, standards mandate), which alternatives were rejected and why, and the validation basis. Defensible at the Change Control Board without reconstructing six-month-old logic
  • Cost and schedule basis of estimate: four method-specific cost kernels price every affected verifier in dollars, labor hours, and schedule weeks, with per-verifier facility selection and configurable labor rates
  • Dynamic schedule Gantt with a baseline diamond, ready-with-ECP diamond, and a red schedule-slip bracket showing exactly how many weeks the ECP pushes the ready-for-flight date
  • Critical-path identifier flags the longest-schedule verifier plus any verifier within 20 percent (parallel-critical) per MIL-HDBK-340 Sec 5.3
  • Zero Re-Inspection pill: when no physical characteristic is affected, the Inspection lane renders as a feature, not an empty field. The tool correctly identifies that firmware timing and trip-point changes require no technician hours
  • Method-change Class I gate per MIL-STD-973 catches the silent Class II submittal that would fail CCB review
  • Impact taxonomy per requirement (Both / Req Update / TP Update / Cascaded / No Change)
  • Exportable delta package: MIL-STD-973, ISO 10007, AS9100, or your internal CM standard, TXT / HTML / Word / PDF

Who it's for

  • Engineering teams iterating on designs internally (commercial and regulated alike) who need to know precisely what a change impacts before re-testing
  • Systems engineers authoring ECPs against MIL-STD-973, ISO 10007, or AS9100 baselines
  • Configuration Management Leads managing baseline changes across modular architectures
  • Program engineers responding to customer-directed changes or regulatory submittal deadlines
  • Chief engineers and CCBs who need a defensible basis of estimate on re-verification cost and schedule impact before authorizing a change
  • Change review boards (internal CCB, customer ERB, regulatory submittal) needing defensible structured impact analysis with citable rationale on every cascaded coupling

Standards encoded

Every AI-assisted field ships with a hardcoded fallback written against the relevant standard, so your package renders correctly even when the network doesn’t.

  • MIL-STD-973, Defense-industry configuration management
  • MIL-STD-961E, Method-selection framework (Test/Analysis/Demonstration/Inspection)
  • MIL-HDBK-340, Test sequencing and cost kernel basis
  • MIL-STD-1629A, FMECA coverage analysis for cascade rationale
  • MIL-STD-461G App A, EMI switching-signature coupling
  • MIL-HDBK-217F, Part-stress reliability model for duty-cycle cascades
  • ASME V&V 10, Model verification and validation credibility
  • NASA-STD-7009A, Modeling and simulation credibility
  • PMBOK schedule-compression guidance
  • ISO/IEC 17025, Test facility accreditation for facility-swap analysis
  • ISO 10007, The commercial/industrial sibling of MIL-STD-973
  • AS9100, Aerospace QMS change-control requirements
  • FDA 21 CFR 820.30, Medical device design-change controls
  • EIA-649, Consensus Standard for Configuration Management
  • FAR 52.243, Change clauses for federal contracts
  • Customer-specific internal CM standards (BYO doctrine)

How to get access

ChangeTrace is in private beta. Current pricing:

  • Starter $599/month, 1 seat, all 4 modules, unlimited packages, all doctrine references, email support. Best for solo practitioners and boutique consultancies.
  • Team $2,499/month, up to 10 seats, shared program library, multi-user collaboration, RFP amendment auto-tracking, custom standards library.
  • Enterprise $9,999/month, unlimited seats, AWS GovCloud tier, SSO, audit logging, custom integrations, dedicated CSM.

See full pricing details · Request a demo · Browse the doctrine corpus

Related modules

ChangeTrace is one of four integrated modules. The four are designed to flow into each other across the capture-to-delivery lifecycle: