Before you begin
- Forge MES in Plain Language
- Manufacturing Basics for New Users
How the workflow connects
Forge MES uses two setup branches—where work happens and what is being made. They meet in the Routing and Line assignment before a Work Order can run.
- 01Factory setup
Site and Line
The Site identifies the physical location. The Line is the production lane that can receive and hold Production Tasks.
provides the factory structure used by - 02Factory setup
Station and Shift
Stations identify the exact work points used by a Routing. Shifts identify when production is available to run.
combines with the product definition - 03Product setup
Product and active BOM
The Product identifies the finished item. Its active BOM identifies the Components and quantities required for one unit.
provides the material definition required by - 04Process setup
Routing and Line assignment
The Routing orders the work across Stations. The active Product-to-Line assignment says which Line is allowed to start that Product.
makes it possible to create and schedule a - 05Production plan
Work Order
The Work Order requests a quantity of the routed Product for a due date and Shift. It stays pending until the release checks pass.
creates one unit-level record per output as - 06Execution
Production Tasks
Each Production Task represents one finished unit. It enters an eligible Starting Line, follows the Routing, and retains the unit's execution history.
Step-by-step in Forge MES
- Sites locate Stations and can also group Lines.
- Products use BOMs to define material requirements.
- Routings connect operations to Stations and require an active BOM.
- Product-to-Line assignments identify where a product can start production.
- Releasing a Work Order creates unit-level Production Tasks on eligible Lines.
Rules to remember
- A missing prerequisite blocks the next record even when the next screen is visible.
- Projects and Product Families are recommended organisational layers, not hard execution blockers.
- Production Orders are optional grouping records; Work Orders create executable production.
Configure for the client
- Confirm the client's enabled modules, terminology, operating model, roles, and implementation boundaries before converting this standard journey into a solution design.
- Validate the configured behaviour with approved test data in the target environment before production use.
Ready when
- I can follow the dependency chain from Site to Production Task.
- I know which organisational records are recommended.
- I understand why a Production Order alone does not start production.