Assembly work orders
Plan an Assembly from one released BOM, reserve and consume exact components, then receive the independently completed output with genealogy.
Screen orientation
Assembly permissions, assigned site and clearance apply. Planning, component consumption and independent completion use their existing authorities.
The planning form defines the released BOM/output context. Work-order detail exposes reservation, scan-confirmed consumption, completion and immutable input/output genealogy.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Released BOM | Select | Required. | Choose the exact released Assembly BOM revision. | Pins the build definition. |
| Site · Finished stock location | Selects | Required. | Choose the authorised build site and eligible finished location. | Scopes custody and output. |
| Planned quantity · Finished batch · Serial assignment | Quantity/identity controls | Required according to tracking. | Set exact output quantity and governed identity evidence. | Defines the planned output. |
| Ownership pool · Approved internal numbering profile | Selects | Required as applicable. | Retain ownership and approved serial generation context. | Pins identity/ownership rules. |
| Work-order reference · Project / contract · Work centre | Text/selects | Required. | Use attributable manufacturing and programme references. | Creates the work-order identity/context. |
| Planning notes | Long text | Required. | Record the build basis and constraints. | Becomes retained planning evidence. |
| Consumption authority · Consumption notes | Scan/action fields | Required to consume components. | Scan/select only exact reserved eligible inputs and cite the authority. | Posts governed component consumption and genealogy. |
| Independent completion reference · Acceptance notes | Completion fields | Required. | A separate authorised actor records the accepted output evidence. | Receives the finished Assembly and closes genealogy. |
Actions and effects
When to use: From one released BOM with complete output context.
What it does: Creates planned work and component requirements; it does not create finished stock.
When to use: For exact eligible balances under authorised execution.
What it does: Posts explicit component custody/ledger movements and records allocations.
When to use: After requirements are complete, by an independent authorised actor.
What it does: Creates the output identity/balance and immutable genealogy.
Lists and states
- Assembly work-order register: use status, exact version and accountable actors to distinguish current work from retained history.
- History and evidence: hashes and source/version references identify the immutable facts used by each decision.
Authority boundary
Assembly owns its explicit component/output stock transactions. It does not release Engineering BOMs, Manufacturing plans, Quality NCR decisions or customer delivery.