The discrete manufacturing data model
Discrete manufacturing produces identifiable, countable units. A car. A circuit board. A chair. Each unit is built from a structured hierarchy of sub-assemblies and components — the Bill of Materials. Each unit follows a defined sequence of operations through specific workstations — the routing. The ERP must understand both structures to plan, schedule, and cost production accurately.
The complexity scales quickly. A finished automotive component may have four or five BOM levels. The top-level assembly depends on sub-assemblies that depend on machined parts that depend on raw material. Changing a component at level three requires re-evaluating cost, lead time, and stock requirements all the way up. This is not a spreadsheet problem. It is a multi-level explosion problem that only proper MRP can solve.
Features that genuinely matter
- Multi-level BOM — unlimited depth, version control, BOM comparison across revisions
- Routing with workstation capacity — operations mapped to workstations with setup and run times
- MRP engine — demand-driven material requirements planned across all BOM levels
- Work orders with job cards — production split into trackable operations at each workstation
- Actual vs. standard costing — real material consumption and labour captured per work order
- Serial number tracking — each finished unit gets a unique identity for warranty and service
Shop floor execution: where ERPs most often fail
The gap between ERP plan and factory reality is widest on the shop floor. Work orders are created in the ERP. But shop floor supervisors work from paper job cards, update the ERP at the end of the shift (or week), and the system is perpetually behind reality. Shop floor execution — real-time job card completion, material issue confirmations, quality inspection at each operation — is the capability that most manufacturing ERPs promise and few actually deliver.
A proper MES-ERP integration, or better yet a platform where MES and ERP are the same system sharing one database, eliminates this gap. Job card completion by an operator on a tablet immediately updates the production order progress, material consumption, and work-in-progress valuation. No batch sync. No end-of-shift data entry.
The ERP tells you what was planned. The MES tells you what actually happened. The best platforms make those the same question.
What is noise in the feature list
Many discrete manufacturing ERP vendors compete on feature breadth. Advanced planning and scheduling, digital twin simulation, AI-powered demand forecasting — these features exist and can add value. But they are layer-two investments that deliver nothing if the foundational data — accurate BOMs, real-time work order progress, actual material consumption — is not clean. Start with the foundation before the superstructure.