MES vs ERP: What's the Difference and Why You Need Both
One of the most common questions from operations managers and IT leads: "We already have an ERP — do we really need a separate MES?" The answer is almost always yes. Here's why, and what each system actually does.
The Short Answer: Different Layers, Different Jobs
ERP and MES operate at different levels of the manufacturing enterprise — defined by the ISA-95 standard (also known as IEC 62264):
- ERP (Level 4): Business management — orders, procurement, financials, inventory planning, customer delivery commitments
- MES (Level 3): Manufacturing operations management — production execution, shopfloor tracking, OEE, quality, maintenance, shift management
- SCADA/PLC (Level 1–2): Automation — machine control, real-time process data
What Each System Manages
🏢 ERP Manages
- Sales orders and customer commitments
- Production planning and scheduling (MPS, MRP)
- Procurement and supplier management
- Inventory and warehouse management
- Finance and cost accounting
- HR and payroll
- Planned vs actual reporting (after the fact)
🏭 MES Manages
- Production order execution and work instructions
- Real-time machine status and OEE
- Downtime tracking and root cause analysis
- Quality control and non-conformance
- Predictive and preventive maintenance
- Shift handover and team communication
- Part traceability and genealogy
Why ERP Cannot Replace MES
ERPs are designed for business transaction processing — planned at planning horizons of days, weeks, or months. They are not designed to capture machine-level events at second-by-second resolution. Specifically, an ERP cannot:
- Calculate OEE from PLC signals in real time
- Detect a 47-second micro-stoppage on a packaging line at 3:17 AM
- Identify that Line B is running at 94% of target cycle time due to a worn feed roller
- Alert maintenance when a motor's current draw deviation suggests bearing failure in 12 days
- Capture the shift handover note from night shift about a recurring label misread at Station 7
These are the events that determine whether your OEE is 72% or 85% — and they live entirely below the ERP's visibility horizon.
How MES and ERP Integrate
| Data Flow | Direction | What It Enables |
|---|---|---|
| Production orders | ERP → MES | MES knows what to produce, in what quantity, by when |
| Production actuals (qty, scrap) | MES → ERP | ERP inventory and cost reporting uses real production quantities |
| Material consumption | MES → ERP | ERP inventory updates with actual component usage per batch |
| Labour reporting | MES → ERP | Actual shopfloor hours feed payroll and cost centre reporting |
| Equipment downtime summary | MES → ERP | Maintenance cost and asset depreciation can reference actual utilisation |
The "We'll Just Use Excel" Trap
Many plants operate with an ERP plus manual data collection — spreadsheets, whiteboards, paper shift logs. This approach suffers from three fatal flaws:
- Data latency: By the time the Excel file is updated, the shift is over and the problem has already caused the damage.
- Data accuracy: Manual entry by operators under pressure produces 10–30% data error rates.
- Analytical depth: You can't calculate cycle time efficiency or identify micro-stoppages from daily production count entries.
Frequently Asked Questions
Bridge the Gap Between ERP and Shopfloor
Shopfloor Copilot gives your ERP the production actuals it needs — and gives your shopfloor team the real-time visibility ERP cannot provide. No custom integration project required to start.
See the Platform →