39. FAT, SAT and commissioning acceptance evidence
Prove sequential FAT, SAT and commissioning against one exact BUILT product and accepted upstream evidence while keeping customer delivery, custody, external messaging, machine, safety, Engineering-source, Quality-source and financial authority outside Moduvio.
Purpose
Prove sequential FAT, SAT and commissioning against one exact BUILT product and accepted upstream evidence while keeping customer delivery, custody, external messaging, machine, safety, Engineering-source, Quality-source and financial authority outside Moduvio.
Manufacturing Engineer, different Product Engineer, different Quality Engineer, different Project / Contract Manager, Production Operator, different Quality Inspector and contract authority
BLD-… / unit SN-… BUILT + accepted as-built + approved MER-… → MAC-… v1 rejected → v2 released → FAT MAR-… v1 rejected/v2 accepted → SAT accepted → commissioning accepted → COMPLETED.
Before you begin
- Flow 32 result pack is APPROVED and the same build has CONFIGURATION_ACCEPTED as-built evidence
- Build order and product unit both remain BUILT
- Every procedure and transition evidence version is same-site, within classification and CLEAN
- Campaign author, Product Engineering reviewer, Quality reviewer and release reviewer are different named users
- Result author and Quality verifier are different named users
Sequential evidence and authority boundaries
The source SHA-256 freezes the BUILT order/unit, current configuration-accepted as-built snapshot/fingerprint and approved Flow 32 execution-pack/result identities and fingerprints. Creation and every later decision recompute it.
Each immutable version declares FAT at a factory, SAT at a customer site and commissioning at a customer-site or field reference, with unique sequence, date, CLEAN procedure/hash, prerequisites, adapter and exact parameters.
A different Product Engineer technically approves the campaign, a different Quality Engineer approves procedure/parameter control and a different Project / Contract Manager releases it. No campaign actor may perform more than one decision.
A phase result cannot be created until the preceding declared phase has contract acceptance. Once result recording begins the campaign is IN_EXECUTION; it becomes COMPLETED only when every declared phase is ACCEPTED.
Execution time cannot precede campaign release. Location, adapter, parameter names and units must exactly match the phase. Result derives from all measurements; automated input requires one immutable external record reference.
A different Quality Inspector recomputes source/result fingerprints and cannot accept FAIL. Rejection retains the immutable version and only the original Production Operator may author its corrected replacement.
After Quality acceptance, the Project / Contract Manager records external witness organisation, witness name and acceptance reference with CLEAN evidence. This is an evidence assertion, not a message, signature request, delivery or custody event.
Flow 33 leaves build and unit BUILT and never edits as-built/result sources, Engineering, Quality, machine/safety, current_stock, stock_ledger, reservations, custody, Assembly, physical identities, delivery, procurement, payroll or accounting.
Procedure
- 1
Create campaign v1 from one eligible BUILT product with FAT/SAT/commissioning phase definitions and CLEAN evidence.
- 2
Submit and reject v1 as a different Product Engineer; retain it and author a corrected immutable v2 against the exact same freshly verified source.
- 3
Technically approve v2, Quality approve it as a third actor and release as a fourth Project / Contract Manager only while source/definition fingerprints remain unchanged.
- 4
Record FAT as Production Operator, prove SAT is blocked, submit and reject FAT v1 as a different Quality Inspector, then create/submit/verify FAT v2.
- 5
Record external witness and contract acceptance; repeat record → Quality verify → contract accept for SAT and commissioning in sequence.
- 6
Confirm campaign COMPLETED with product/unit still BUILT and audit every source, version, decision, evidence link and zero-authority witness.
Expected result
- Only BUILT products with accepted as-built and approved Flow 32 results are eligible
- Campaign lifecycle retains rejected immutable versions and independently signed replacement
- FAT, SAT and commissioning definitions have exact location/procedure/adapter/parameter control
- Out-of-order phase execution is rejected
- Execution before release or at a substituted location fails closed
- Automated evidence retains external record identity
- Quality verifier differs from result author and cannot accept a failed result
- Contract acceptance retains witness organisation/name/reference and controlled evidence
- Campaign completes only after every phase is accepted
- Build and unit remain BUILT and no source, message, delivery, machine, safety, inventory, custody, Assembly, identity or financial record is changed