Before you begin
- Production Tasks
How it works
Follow the arrows from left to right. Each stage prepares the information the next stage needs.
- 01Required
Identify Station
Open the Station work area and identify or scan the unit.
provides the information needed for - 02Required
Scan unit
Review the current operation, instructions, required inputs, and quality gates.
provides the information needed for - 03Required
Review instructions
Scan serialised Components or enter the exact quantity for quantity-based Components.
provides the information needed for - 04Required
Load material and tools
Complete required checks and record the operation result.
provides the information needed for - 05Required
Perform work
Finish the step so Forge can move the unit to the next valid operation.
provides the information needed for - 06Required
Record result
This stage contributes to the outcome: Follow the normal sequence an operator uses to process a unit at a Station.
provides the information needed for - 07Required
Complete step
This stage contributes to the outcome: Follow the normal sequence an operator uses to process a unit at a Station.
Why this connection matters: Operators should work from the Station that matches the current Routing step.
Step-by-step in Forge
Navigation: Manufacturing → Station work area
- Open the Station work area: Select the operator's Station and scan or enter the finished-unit serial.
- Review the operation: Read the instructions, required Components, tools, and quality gates.
- Capture inputs: Scan each serialised Component and enter the exact quantity for bulk Components.
- Record the result: Complete required checks and select the pass, fail, hold, or repair outcome.
- Finish the operation: Select Complete so Forge records the Route Log and moves the unit to its next valid step.
Watch the task
Watch: Operator Execution Flow
GIF walkthrough placeholder for Operator Execution Flow.
Rules to remember
- Operators should work from the Station that matches the current Routing step.
- Required Component and verification inputs block completion when missing.
- Failed results must follow the configured exception path.
Ready when
- The correct unit and operation are visible.
- Required inputs validate successfully.
- The completed step appears in the unit history.