17A. Integrated Engineering BOM and PLM release control
Create one immutable requirements-to-design-to-recursive-EBOM digital thread, govern ECR/ECO impact and independently release its exact Manufacturing handoff.
Purpose
Create one immutable requirements-to-design-to-recursive-EBOM digital thread, govern ECR/ECO impact and independently release its exact Manufacturing handoff.
Product Engineer, different Quality Engineer, different Configuration Manager, Manufacturing Engineer and Auditor
DESIGN v1 / CI-HW-001 → SYS-REQ-001 PASS → CAD-001 rev A → recursive EBOM 10/10.20 → ECR-001 → ECO-001 → PLM-… RELEASED → MBOM source.
Before you begin
- An active variant has a RELEASED effectivity-controlled baseline
- Its assembly CI resolves to the exact active approved item revision and RELEASED root BOM
- Every nested assembly uses a RELEASED BOM and every component remains active/catalogue-approved
- All allocated CIs belong to the selected baseline
- Every design and verification document version is same-site, within classification and CLEAN
- Author, Quality verifier and Configuration releaser are three different named users
Digital thread and authority boundaries
Each unique requirement retains source, statement, allocated baseline CIs, verification method, acceptance criteria, PASS/FAIL result and exact controlled evidence. Submission fails unless every result is PASS with evidence.
CAD 3D/2D, software, interface and specification records bind an explicit record/revision and exact immutable CLEAN document version to baseline CIs. Moduvio governs metadata and evidence; it is not a CAD editor.
Root lines must cover the selected released assembly BOM exactly once. Every nested line must resolve to the exact released BOM of its parent assembly; dangling parents, cycles, omissions, foreign lines and classification escalation fail closed.
Records the attributable problem, reason, priority, impact and exact affected requirement IDs. It cannot cite a requirement absent from the package.
Records effectivity, disposition and typed ADD/MODIFY/future-removal changes against exact requirement, design, EBOM or CI references. It creates change authority but does not silently rewrite source baselines or BOMs.
One SHA-256 covers the exact released baseline/BOM source; a second covers requirements, design records, recursive EBOM, ECR and ECO. Submission, both reviews and Manufacturing consumption reverify both.
The Product Engineer author submits, a different Quality Engineer performs V&V review, and a third Configuration Manager releases. No actor may inherit an earlier authority on the same version.
Only the current RELEASED package version for the exact variant, baseline, assembly CI and site appears as an MBOM source. Stale, rejected, mismatched or fingerprint-altered versions are rejected.
PLM creation and transition never update product baselines, catalogue items/BOMs, documents, current_stock, stock_ledger, reservations, custody, Assembly, procurement or accounting.
Procedure
- 1
Select the released assembly baseline and inspect its automatically derived full recursive EBOM.
- 2
Capture requirement statement, allocation, method, criteria and PASS result; bind controlled evidence and the exact controlled design record.
- 3
Record the ECR problem/impact and ECO disposition/effectivity/change line, then create the immutable draft.
- 4
Submit as the author; sign in as a different Quality Engineer and decide the unchanged verification evidence.
- 5
Sign in as a third Configuration Manager and release or reject the exact verified version.
- 6
Open Manufacturing BOM and select the released PLM package; confirm changed source fingerprints or authority reuse fail closed and all inventory/custody witnesses remain unchanged.
Expected result
- Every requirement is allocated and evidence-backed before submission
- Every design record points to an exact CLEAN immutable version
- Every recursive EBOM line resolves to an exact released parent BOM without cycles or omission
- ECR/ECO references are internally consistent and immutable
- Quality and Configuration decisions are independent and attributable
- Rejected versions remain immutable and only replacements may proceed
- Only current released PLM versions feed MBOM creation
- Audit and outbox retain each transition and its no-side-effect boundary
- No source, inventory, custody, Assembly, procurement or accounting record changes