Manufacturing build control
Plan, schedule and record an exact build using released sources, then capture authoritative as-built evidence and independent acceptance. It does not perform material custody itself.
Screen orientation
Manufacturing planning/execution, Quality acceptance and Configuration decisions are role-separated. Product, MBOM, instruction and baseline selectors are limited to released authorised sources.
The four sections expose plan authority, execution, as-built and acceptance. Each build shows its pinned source versions and only the next actions allowed by its state and caller role.
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 |
|---|---|---|---|---|
| Plan title / Priority | Text and select | Required to create a build plan. | Use a traceable plan name and the approved priority; priority does not create a production dispatch by itself. | Creates the governed planning record. |
| Baseline source / Released manufacturing BOM | Select | Required. | Select exact released sources. A plan remains pinned to these sources even if a later revision is released. | Defines the controlled design and manufacturing basis. |
| Released instruction evidence | Controlled document select | Required when the plan needs instructions. | Select the released instruction version rather than a local or unreviewed file. | Pins execution guidance to the plan. |
| Target start / Target completion | Date/time | Required for a planned build schedule. | State intended timing; use governed rescheduling rather than rewriting historical evidence. | Provides schedule context without allocating capacity automatically. |
| Product unit / Exact registered product unit | Select | Required when the output is a serialized product. | Select the exact registered product context. Do not use it to infer installed materials or service history. | Associates the build with its authorised product identity. |
| Actual labour minutes | Number | Required only where the operation result captures actual labour. | Record observed attributable labour time, not an estimated standard time. | Adds operational evidence for the build/cost rollup boundary. |
| Signed artifact SHA-256 | Text | Required when a signed execution artifact is captured. | Enter the exact cryptographic hash supplied by the approved signing path. Do not hand-enter an approximate file name. | Pins the referenced signed artefact identity. |
Actions and effects
When to use: After all exact released sources and routing are selected.
What it does: Creates/release a governed build plan; it does not issue material or command equipment.
When to use: When the assigned authorised operator records the observed operation event.
What it does: Captures attributable execution evidence against the pinned plan.
When to use: After exact evidence is available, with independent acceptance where required.
What it does: Retains the as-built/acceptance record without silently changing Inventory custody.
Lists and states
- Build list: status, product unit, source versions, schedule and acceptance show the current controlled state.
- Operation history: planned/released operation, execution actor, result and evidence distinguish instructions from observed work.
Authority boundary
Build control governs manufacturing evidence. Assembly/Inventory remain authoritative for material custody and stock; Moduvio does not control PLCs, CNCs or safety systems.