Engineering

Engineering Change Orders with atomic revision control

Items, BOMs, and routes are revision-controlled. ECOs promote changes atomically — either all revisions in the change set approve together, or none do. Approved revisions are immutable. OEM MoC notification rules for Ford, GM, and Stellantis fire automatically.

Request a Demo

ECO state machine

Draft → InReview → Approved. Rejected (first rejection flips the ECO immediately). Cancelled from Draft or InReview. Once all configured required roles have signed, the ECO moves to Approved and all revision transitions execute in a single database transaction — atomically.

Immutable approved revisions

Once a revision (Item, BOM, or Route) reaches Approved status, the RevisionImmutabilityInterceptor blocks any further edits. Only four lifecycle fields remain mutable after approval: Status, EffectiveFrom, EffectiveUntil, and ApprovingEcoId. All other mutations throw an error at the database level — not the API level.

Tamper-evident signature hash

Each ECO approval record stores a SHA-256 hash of the change content: title, description, reason, effective date, and all revision transitions. Auditors or regulators can independently recompute the hash from the stored fields and confirm nothing was altered after signature. This satisfies 21 CFR Part 11 §11.10 integrity requirements for closed systems.

Revision formats

Revision identifiers are strings, never integers. Four formats are supported:

  • Alpha — bijective base-26 (A → Z → AA → AB …)
  • Numeric — zero-padded integer (01, 02 … 99, 100)
  • AlphaNumeric — combined (A01 → A99 → B01)
  • Custom — any scheme via a registered format resolver

Revision history sorts by RevisionSequence (integer counter) — not by the revision string. ASCII ordering of strings is incorrect ("Z" > "AA").

Work order revision snapshots

When a work order is released, the current BOM revision and Route revision strings are snapshotted onto the work order record. This means production history is immutably linked to the exact revision in effect at release time — even if subsequent revisions supersede the BOM or route.

Management of Change (MoC) and OEM notification

ECOs carry MoC extension fields: notification status, retroactive analysis scope, risk re-evaluation trigger, and validation plan JSON. When an ECO is approved, customer notification rules fire automatically based on change type and customer code:

  • Ford Q1 §3.4 — change notification requirement
  • GM SQ-IPPM §5.3 — supplier product and process change notification
  • Stellantis CSR Jun 2025 — MoC notification baseline

Retroactive impact analysis walks the lot genealogy tree when MoCRetroactiveAnalysisScope ≠ None, returning every production unit built against the superseded revision.

Regulatory mapping

StandardClauseQontiv feature
IATF 16949§8.5.6Control of changes
AS9100 Rev D§8.1.2 / §8.3.6Configuration management / design change
ISO 13485§7.3.7Design and development changes
21 CFR Part 11§11.10Immutability + tamper-evident hash

Every revision immutable. Every change signed.

ECO workflow with multi-role approvals — designed for IATF 16949 §8.5.6 and 21 CFR Part 11.

Request a Demo See pricing