Why this matters. A manufacturing ERP rarely fails on a missing module — it almost always fails on the data chain between BOM, routing and setup matrix. Tick modules without hardening master data and you buy a fast demo and a long ramp-up. According to Bitkom Research Industry 4.0 (2026), 97 percent of German industrial firms run at least one Industry 4.0 application — but only when the ERP data base holds.
When this approach fits — and when it does not
This approach fits when:
-
You run discrete or mixed-mode manufacturing with at least fifty active BOMs;
-
Make-to-order, configure-to-order or batch production sets the takt;
-
BOM, routing and shopfloor feedback must converge into one operational picture.
This approach does not fit when:
-
You run pure continuous process manufacturing on recipes — different master-data logic applies;
-
The shopfloor stays paper-based and feedback is entered weeks later;
-
Traceability is treated as nice-to-have rather than a regulatory obligation.
The data chain decides — four levers
Across more than 1,200 selection projects, the pattern is consistent: bill-of-material quality decides the project before any module does. Four levers carry every manufacturing ERP rollout:
-
Bill-of-material quality: multi-level BOMs with clean variant logic, maintained quantities and substitute rules. Without a clean BOM, MRP delivers phantom requirements.
-
Routings and setup matrix: realistic standard times, setup sequences and machine groups. The setup matrix is the most common bottleneck — and the one least often maintained.
-
ERP–MES interface: embedded MES carries through medium variant complexity; above seconds-range takt time or double-digit line counts, best-of-breed MES becomes mandatory.
-
Traceability as obligation: CSRD, supply-chain due-diligence law and product liability turn batch genealogy and serialisation into a baseline requirement — no longer optional.
A common mistake and how to avoid it
A machine builder in Baden-Württemberg, 240 staff, manufactures special tooling in batch sizes of five to fifty. The new ERP was chosen from a module checklist; the BOM was left as it was. After go-live, MRP runs took four hours and disposition-relevant components were missing from the proposals. Three quarters of master-data rework followed — avoidable with a data-quality assessment before contract signature.
The VDMA digital strategy names uniform data flow between ERP and machine layer as the precondition for Industry 4.0. In machine building this is literal; in every discrete setting it holds equivalently.
What to do next
-
Audit the ten most-used BOMs for multi-level structure, variants and maintenance status.
-
Compare three critical routings to shopfloor reality — standard time against actual.
-
Assess the ERP–MES interface against your takt time, variant complexity and traceability obligations.
We assess your data chain before selection — that prevents the costly master-data rework after go-live.
FAQ
Bill-of-material management, MRP, routings, shopfloor data capture, variant configurator and batch or serial-number tracking. The decisive factor is not the module list but data quality in BOM and routing. Modules deliver the function; master data delivers the outcome.
Discrete manufacturing works with bills-of-material and routings; process manufacturing works with recipes, yield and batch progression. Master-data models, demand planning and feedback logic differ fundamentally. A generic manufacturing ERP rarely covers both cleanly.
Embedded MES carries through medium variant complexity and takt times in minutes. Above seconds-range takt time, double-digit line counts or high variant variety, best-of-breed MES becomes mandatory — for latency, visualisation and shopfloor-specific function.
