Visual work instructions
Release immutable visual instructions against an exact manufacturing plan/operation, pin them to dispatch and require ordered operator observations and independent Quality holds.
Screen orientation
Manufacturing instruction permissions, exact site and classification clearance apply. Author, Production releaser, named operator and Quality hold reviewer are separate where required.
The definition editor selects an exact target and ordered steps/media. Registers show version/review history and dispatch-pinned execution progress.
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 |
|---|---|---|---|---|
| Exact released manufacturing plan · Attachment scope · Immutable target | Selectors | Required. | Pin one current released plan and plan-start or exact operation target. | Creates the immutable source fingerprint. |
| Package title · Controlled purpose | Text | Required. | Name the instruction and state its bounded operational purpose. | Freezes package context. |
| Sequence · Step code · Title · Released instruction | Step controls | Required for every ordered step. | Use concise inert work guidance in execution order. | Defines the released step sequence. |
| Observation prompt | Text | Required when operator evidence is expected. | Ask for an attributable observation, not a machine command. | Defines the execution response. |
| Controlled media type · Media caption · Controlled media version | Media controls | Required when media is attached. | Select only same-site CLEAN PHOTO, VIDEO or DRAWING evidence. | Pins immutable authenticated media. |
| Acknowledgement requirement · Execution evidence requirement · Hold point | Step gates | Optional individually; authoritative when enabled. | Set explicit acknowledgement/evidence and Quality hold behavior. | Controls completion of the pinned run. |
| Package-definition evidence | Controlled evidence | Required. | Attach CLEAN definition evidence. | Pins author evidence. |
| Decision · Attributable note · Controlled transition evidence | Review controls | Required at submit/release/reject/hold review. | Record the accountable outcome and CLEAN evidence. | Creates immutable review facts. |
| Required execution evidence | Controlled evidence | Required only for a step that demands it. | The named operator selects evidence for the exact pinned step. | Completes that observation requirement. |
| Pinned fingerprint · Progress · Dispatch · Next | Read-only run state | Derived. | Use these values to follow the dispatch-pinned version and next permitted step. | Explains run state without changing it. |
Actions and effects
When to use: Against an exact released target.
What it does: Creates an immutable definition version.
When to use: By a different Production Manager while source/fingerprint remain current.
What it does: Makes the exact version eligible for future dispatch pins.
When to use: By the exact dispatch operator in sequence.
What it does: Appends acknowledgement/evidence and opens a hold when configured.
When to use: By a different Quality Inspector.
What it does: Accepts continuation or keeps the run blocked; it does not disposition stock.
Lists and states
- Instruction package and pinned run 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
Instructions are inert governed evidence. They do not operate PLC/CNC/machines, replace dispatch/execution, change source plans, move stock or create a generic workflow/template engine.