Tutorial: Govern a visual work instruction
Author, independently release, dispatch-pin and complete one exact controlled-media instruction without creating a second execution engine.
Learning goal
Manufacturing Engineers, Production Managers, planners, operators, Quality Inspectors and auditors.
Understand exact attachment, immutable visual media, version replacement, dispatch pinning, ordered observations and independent hold points.
Before you begin
- Use an authorised training/disposable tenant or a completed read-only example
- A manufacturing plan is current and independently released
- CLEAN same-site PHOTO, VIDEO or DRAWING versions exist in Documents
- Different named users cover author, release, operator and Quality hold decisions
Observation-first is the default. Do not create retained customer, procurement, receipt, inventory, Quality, Engineering or Manufacturing records merely to complete a tutorial.
Guided journey
- 1Inventory, Engineering, Manufacturing and QualityOpen /workspaces/manufacturing
Find the current capabilities
- Acting role
- Every learner
- What to do
- Use workspace navigation to locate Engineering PLM, Manufacturing Visual work instructions, Inventory Calibration and Lifecycle operations, and Quality Metrology impact.
- What you should observe
- Current capabilities are reachable from their owning workspaces; full Sustainment/MRO remains explicitly coming soon.
May changeNothing; workspace discovery is read-only.
Must remain unchangedVisibility does not grant a domain permission or imply a complete Sustainment/Programme module.
- 2ManufacturingOpen /manufacturing/instructions
Create immutable version 1
- Acting role
- Manufacturing Engineer
- What to do
- Select one exact released plan/operation, add unique ordered steps, controlled visual versions, acknowledgement/evidence flags and one Quality hold, then submit.
- What you should observe
- The exact plan source and visual definition receive SHA-256 fingerprints.
May changeDraft/submitted instruction version, evidence links, audit and outbox facts.
Must remain unchangedNo dispatch, operation, stock, custody, machine, callback or generic workflow is created.
- 3ManufacturingOpen /manufacturing/instructions
Reject and replace
- Acting role
- Production Manager → Manufacturing Engineer
- What to do
- Reject v1 as a different Production Manager, create replacement v2 and approve it independently.
- What you should observe
- v1 remains immutable; v2 becomes the active future pin source.
May changeReview and active-version state only.
Must remain unchangedA previously active version remains usable while a replacement is draft/rejected, and existing pins are never rewritten.
- 4ManufacturingOpen /manufacturing/readiness
Pin a fresh dispatch
- Acting role
- Production Planner → Production Supervisor
- What to do
- Plan and independently release the exact operation dispatch after v2 is active.
- What you should observe
- The dispatch requirement freezes v2 and its fingerprint; later v3 cannot change this dispatch.
May changeExisting readiness dispatch/capacity evidence plus instruction requirement.
Must remain unchangedNo material move, calibration update, Assembly action or machine command occurs.
- 5ManufacturingOpen /manufacturing/instructions
Observe in exact order
- Acting role
- Exact named Production Operator
- What to do
- Open each authenticated CLEAN media preview, acknowledge as required and record only observed facts/evidence in released order.
- What you should observe
- The run stops at the declared Quality hold and cannot skip or overwrite a step.
May changeImmutable attributable step observations.
Must remain unchangedThe operation itself is not yet executed and stock/custody remain unchanged.
- 6Quality → ManufacturingOpen /manufacturing/instructions
Clear the hold and execute
- Acting role
- Different Quality Inspector → Production Operator
- What to do
- Accept the evidence-backed hold as an independent inspector, complete remaining steps, then record the existing operation in Build control.
- What you should observe
- Only COMPLETE pinned runs unlock the established operation endpoint; rejection stays blocked.
May changeHold-review/run status, followed separately by the existing operation execution evidence.
Must remain unchangedFlow 37 never becomes a second execution, workflow, safety, stock, custody or configuration engine.