Before you begin
- Pre-Start Validation and Release
How the workflow connects
This journey connects the following stages. Complete the required checks at each stage before moving forward.
- 01Required
Create one task per serial
Open Production Tasks on the released Work Order and verify one Task exists for each confirmed serial.
Provides the controlled input for the next stage. - 02Required
Assign initial Line
Review task distribution by Line Type and Line, then open a unit Task.
Provides the controlled input for the next stage. - 03Required
Follow Routing
Confirm Task status, assigned serial, Work Order, Product, Line, and Line Type.
Provides the controlled input for the next stage. - 04Required
Record status and Route Logs
Review Stage Progress, Bound Identifiers, BOM Progress, and Routing and Process Details.
Step-by-step in Forge MES
- Open Production Tasks on the released Work Order and verify one Task exists for each confirmed serial.
- Review task distribution by Line Type and Line, then open a unit Task.
- Confirm Task status, assigned serial, Work Order, Product, Line, and Line Type.
- Review Stage Progress, Bound Identifiers, BOM Progress, and Routing and Process Details.
Rules to remember
- Release creates one Production Task per confirmed finished-unit serial.
- Capacity planning provides the initial Line assignment, and the selected Routing defines the current Stage and Station.
- Required BOM components remain Pending until consumed during execution.
- Generated Product identifiers can be bound to the Task before execution begins.
Configure for the client
- Match operator roles, scan enforcement, material-consumption rules, equipment integration, work instructions, and exception permissions to the client's shop-floor controls.
- Validate the configured behaviour with approved test data in the target environment before production use.
Ready when
- Task count matches Work Order quantity.
- Every Task has a serial and eligible Line.
- Operators can find Tasks at the correct Station.