Before you begin
- Create Products and Variants
How the workflow connects
This journey connects the following stages. Complete the required checks at each stage before moving forward.
- 01Required
Select Product
Review the initial draft BOM created during Product setup.
Provides the controlled input for the next stage. - 02Required
Add Components
Confirm every required Component and quantity per finished unit.
Provides the controlled input for the next stage. - 03Required
Set quantities
Use shared entries for common materials and Variant entries only where requirements differ.
Provides the controlled input for the next stage. - 04Required
Review Variant overrides
Review units of measure and effective quantities before activation.
Provides the controlled input for the next stage. - 05Required
Approve and activate
Resolve non-positive quantities and duplicate Components within the same scope.
Step-by-step in Forge MES
- Review the initial draft BOM created during Product setup.
- Confirm every required Component and quantity per finished unit.
- Use shared entries for common materials and Variant entries only where requirements differ.
- Review units of measure and effective quantities before activation.
- Resolve non-positive quantities and duplicate Components within the same scope.
Rules to remember
- BOM items can be edited only while the Version is Draft.
- Routing creation requires an active BOM belonging to the selected Product.
- The pre-start readiness check uses the active BOM to calculate material requirements.
- Changing an active BOM can change future production readiness and should be controlled.
Configure for the client
- Match product taxonomy, item codes, BOM governance, units of measure, revision control, and serial or lot tracking policies to the client's master-data standards.
- Validate the configured behaviour with approved test data in the target environment before production use.
Ready when
- The BOM contains every required production Component.
- Quantities match one finished unit.
- Variant overrides do not duplicate shared requirements incorrectly.