Before you begin
- Create and Validate a Routing
- Assign Lines to Product
- Create Shifts
How the workflow connects
This journey connects the following stages. Complete the required checks at each stage before moving forward.
- 01Required
Optional Production Order
Use a Production Order to group and monitor related Work Orders. Name and a unique Order Number are required; Client is optional and restricts the Work Orders that can be grouped.
Provides the controlled input for the next stage. - 02Required
One or more Work Orders
Use a Work Order as the executable manufacturing record for a Product with Routing, input quantity, priority, due date, and Shifts.
Provides the controlled input for the next stage. - 03Required
Production Tasks
Use Test Order only for production-line setup or workflow testing because Test Orders are excluded from analytics.
Step-by-step in Forge MES
- Use a Production Order to group and monitor related Work Orders. Name and a unique Order Number are required; Client is optional and restricts the Work Orders that can be grouped.
- Use a Work Order as the executable manufacturing record for a Product with Routing, input quantity, priority, due date, and Shifts.
- Use Test Order only for production-line setup or workflow testing because Test Orders are excluded from analytics.
Rules to remember
- A Production Order groups Work Orders and does not define executable quantity by itself.
- A Work Order can exist without being grouped under a Production Order.
- At least one Shift is required before a Work Order can be started.
- Test Orders are not calculated in production analytics.
Configure for the client
- Match planning fields, scheduling rules, serial-generation policy, capacity controls, approval gates, and release permissions to the client's production-planning model.
- Validate the configured behaviour with approved test data in the target environment before production use.
Ready when
- Grouping demand uses a Production Order with the intended client restriction.
- Every executable quantity is represented by a routed Work Order.
- Test Order is enabled only for non-analytics setup or workflow testing.