Workflow

Flow 33 — Exact built product to accepted FAT/SAT/commissioning evidence

Bind a BUILT product to its accepted as-built configuration and approved Flow 32 result; independently sign a sequential FAT/SAT/commissioning campaign; then record, verify and contract-accept every phase against unchanged fingerprints.

Overview

Inventory meaning

Flow 33 records immutable acceptance evidence only. It does not deliver product, send a customer message, command equipment, change safety state, edit Engineering or Quality sources, post accounting, or reserve, consume, move or reclassify stock/custody; product and unit remain BUILT.

Responsible roles

Manufacturing Engineer author → different Product Engineer technical signer → different Quality Engineer quality signer → different Project / Contract Manager releaser → Production Operator phase recorder → different Quality Inspector verifier → Project / Contract Manager contract acceptor

Process

1
Freeze built source
Resolve exact BUILT order/unit, configuration-accepted as-built and approved Flow 32 result/definition fingerprints.
Sources read-only
2
Define phases
Freeze unique ordered FAT, SAT and commissioning locations, dates, CLEAN procedures, adapters, prerequisites and parameters.
Definition only
3
Sign campaign
Product Engineering, Quality and Programme make three different attributable decisions on unchanged source/definition fingerprints.
No execution yet
4
Record & verify
Production records one phase at a time; a different Quality Inspector accepts exact observations and fingerprints.
Evidence only
5
Contract accept
Contract authority records external witness organisation/name/reference; every accepted phase completes the campaign.
No delivery/custody action
READ ONLY

Role handoff

Detailed reference chapters

FAT, SAT and commissioning acceptance evidence Signed software/test execution and result packs Manufacturing plan, execution evidence and authoritative as-built Product configuration and released baselines Controlled documents and evidence roles

Detailed steps

1
As Manufacturing Engineer, open Manufacturing → FAT, SAT & commissioning and select one BUILT product with configuration-accepted as-built and approved Flow 32 execution result.
2
Create campaign v1 with unique ordered FAT, SAT and commissioning definitions. Bind each phase to its required location type, exact location reference, target date, CLEAN procedure, manual/automated JSON adapter, prerequisites and objective parameters.
3
Submit v1, reject it as a different Product Engineer and retain it. Create v2, obtain a Product Engineer technical signature, a different Quality Engineer signature and a different Project / Contract Manager release on unchanged source/definition fingerprints.
4
As Production Operator, record FAT first using the exact location, parameter coverage and adapter contract; an automated adapter requires its immutable external record identity. Submit the immutable result.
5
As a different Quality Inspector, reject one result, retain it, verify its replacement, then have the Project / Contract Manager record external witness organisation, name, acceptance reference and CLEAN evidence. Repeat sequentially for SAT and commissioning.
6
Confirm the campaign completes only after all declared phases are accepted and reconcile unchanged BUILT status, source fingerprints, Engineering/Quality sources, machine/safety, messaging, delivery, inventory, custody, Assembly, identity and accounting witnesses.

Field-by-field practice data

Use a disposable training tenant

Define a sequential FAT, SAT and commissioning campaign for one training build. The page shows sample set A; the workbook includes independent A, B and C values.

Download all workflow samples (.xlsx)

Field names match the current application labels. Select existing approved records where shown, leave optional values blank unless they genuinely apply, and never copy fictitious TRAIN values into live work.

Manufacturing Engineer

Create the acceptance campaign

Open /manufacturing/acceptance

Enter the three controlled references and scope before independent signatures and release.

Exact field name	Requirement	Sample value A	How to use it
Campaign title	Required	`TRAIN-A actuator acceptance campaign`	Use a unique controlled title.
Scope and authority boundary	Required	`FAT, SAT and commissioning evidence capture only; no customer delivery or custody authority.`	State the exact campaign boundary.
FAT factory reference	Required	`TRAIN-A-FAT-001`	Use the approved factory-test reference.
SAT customer-site reference	Required	`TRAIN-A-SAT-001`	Use the approved site-acceptance reference.
Commissioning field reference	Required	`TRAIN-A-COM-001`	Use the approved commissioning reference.
FAT result adapter	Required	`TRAIN-ADAPTER-FAT-V1`	Select the approved bounded adapter.
CLEAN procedure and campaign evidence	Select existing	`TRAIN-A-ACCEPT-EVID-001`	Select exact CLEAN evidence.
External witness organisation	Conditional	`Training Customer A`	Capture only after the corresponding phase is verified.
Acceptance reference	Conditional	`TRAIN-A-CUSTOMER-ACC-001`	Use the externally supplied reference; no message is sent.

Expected result: Phase execution remains sequential and each result requires independent verification.

End state

One completed acceptance campaign retains exact built-product provenance, independently signed procedure definitions, sequential immutable phase results, separate Quality verification and attributable external contract evidence without acquiring customer-delivery, custody, machine or source authority.