33. Manufacturing plan, execution evidence and authoritative as-built
Bridge released design to attributable build evidence and exact as-built acceptance while keeping material consumption, output receipt and physical genealogy in the existing Assembly/Inventory authority.
Purpose
Bridge released design to attributable build evidence and exact as-built acceptance while keeping material consumption, output receipt and physical genealogy in the existing Assembly/Inventory authority.
Manufacturing Engineer, different Production Manager, different Production Planner, Production Operator, different Quality Inspector, different Configuration Manager and read-only Product/Materials/Programme/Audit observers
MPL-… rejected v1 → released v2 → MBL-… exact WO/output → setup/assembly/test PASS → as-built v1 rejected → v2 Quality accepted → Configuration accepted → product unit BUILT.
Before you begin
- Flow 31 has independently released the current exact MBOM for one active assembly CI from a released product baseline
- The MBOM retains complete exact design-line coverage and governed routing
- The authoritative assembly work order/output already exists for the same BOM, assembly item and site
- A matching REGISTERED product unit links the completed received active assembly physical identity
- At least one same-site ACTIVE, CLEAN evidence version exists
- Plan author, plan approver, scheduler, Quality reviewer and Configuration accepter are distinct named authorities
Manufacturing, custody and configuration authority boundaries
Each version freezes the current independently released MBOM plus its released baseline, assembly CI, item revision, BOM output quantity, exact material definitions and immutable definition fingerprint. Submission, approval and scheduling reject a stale source.
The plan copies unique ordered operations and exact gross material issue evidence from Flow 31. Plan authors cannot inject an ad hoc setup, assembly, software-load, inspection or test routing.
The planner binds one approved plan version to one exact pre-existing assembly work order and output. This creates no assembly requirement, reservation, consumption, output receipt or stock movement.
The latest prior operation must pass before the next starts. A FAIL requires an exact open MANUFACTURING NCR whose source is this build. Immutable failed attempts and NCR references remain after a later retry passes.
Every latest operation attempt must pass, all failure NCRs must be CLOSED, the assembly work order must be COMPLETED, the chosen output must be RECEIVED with an ACTIVE physical identity, and the exact matching product unit must still be REGISTERED.
The immutable source contains the released plan fingerprint, completed work order/output, every operation attempt, exact output-component allocation, batch/serial and resolvable physical identity, plus the matching product unit/baseline.
Quality review is separate from all plan/schedule/execution/capture actors. Configuration acceptance is also separate from Quality and recalculates the complete authoritative fingerprint before requesting Product Configuration to mark only the exact unit BUILT.
Flow 31 provides a bounded controlled MBOM hand-off, not automatic full EBOM transformation. Maintenance orchestration, machine/PLC control, financial posting, inventory valuation and external MES dispatching remain outside scope; Flow 33 separately records bounded FAT/SAT/commissioning evidence without acquiring those authorities.
Flow 27 never inserts or updates current_stock, stock_ledger, assembly requirements/allocations/outputs, locations, ownership, physical identities or NCR lifecycle. Those owning modules remain authoritative.
Procedure
- 1
Select one exact current released Flow 31 MBOM, author and submit plan v1 from its copied material/routing definition, reject independently, then author v2 and release only an unchanged combined fingerprint.
- 2
Schedule released v2 against one exact existing assembly work-order output and reconcile zero stock/custody effects.
- 3
Record every operation in order with controlled evidence; retain any failed attempt with its exact manufacturing NCR before a passing retry.
- 4
Complete the existing assembly workflow, close every failure NCR and register/link the exact product unit in Product Configuration.
- 5
Capture immutable as-built v1, reject it independently in Quality, capture v2 and accept only an unchanged authoritative fingerprint.
- 6
Accept v2 as a separate Configuration Manager and reconcile product-unit BUILT with unchanged stock, ledger, assembly output, allocations and physical identity.
Expected result
- Plan lifecycle follows DRAFT → PLAN_REVIEW → RELEASED with immutable rejected versions
- Build lifecycle follows EXECUTION → AS_BUILT_CAPTURE → QUALITY_REVIEW → CONFIGURATION_REVIEW → BUILT
- Plan author cannot approve or schedule their own version
- Operations cannot run out of released sequence and FAIL requires its exact open build NCR
- Capture is blocked until all latest attempts pass, failure NCRs close and exact completed genealogy exists
- Rejected as-built versions remain immutable and may be replaced
- Quality and Configuration acceptance reject stale authoritative fingerprints
- Final acceptance changes only the matching product unit REGISTERED → BUILT
- Flow 27 never changes stock, ledger, assembly/custody, physical identity or NCR lifecycle records
- Auditor mutation attempts are rejected