Manufacturing Execution System vs ERP on the Shop Floor: Who Owns What

Key takeaways

• ERP plans, schedules, and handles transactions; MES executes and records real-time floor reality.
• Forcing ERP to run the floor produces stale data — it was never built for second-by-second events.
• MES sits between ERP and the machines, translating plans into execution and reality back into ERP.
• The integration boundary is where most shop-floor data projects succeed or fail.

Short answer: ERP owns planning, scheduling, and financial transactions. MES owns real-time execution: what ran, when, how fast, and what failed. ERP asks "what should happen"; MES records "what actually happened." Forcing ERP to track the floor directly produces stale, manually-entered data because ERP was never designed for second-by-second machine events. See also mes vs erp.

What ERP owns

• Demand and production planning.
• Material requirements (MRP).
• Purchasing and inventory transactions.
• Financials and costing.
• Order management.

What MES owns

• Work order execution and dispatch.
• Real-time machine and labor data.
• Downtime, scrap, and quality capture.
• Genealogy and traceability.
• OEE and performance.

Why ERP fails as a floor system

ERP transactions are batch-oriented and human-entered. The floor generates thousands of events per shift. By the time an operator keys a number into ERP, it is already stale and often wrong. MES captures events automatically as they happen.

The integration boundary

MES receives the schedule and work orders from ERP, executes them, and feeds back actuals (quantities, times, scrap). Get this handshake wrong and you get double entry, conflicting numbers, and the classic "why does ERP say something different from the floor?" problem.

Common mistakes

1. Skipping MES and bolting data entry onto ERP. Stale, manual, wrong.

2. No clear handoff. ERP and MES fight over the same data.

3. Treating OEE as an ERP feature. ERP cannot see micro-stops or speed loss.

How OEE relates

OEE is an MES-layer metric — it needs real-time Availability, Performance, and Quality data ERP never sees. A modern OEE platform can act as the MES execution layer, capturing floor reality and feeding actuals back to ERP.

See how Fabrico captures this automatically on your lines — explore OEE for manufacturing or book a demo.

Related reading

• mes vs erp
• mes vs cmms
• oee for manufacturing

Frequently asked questions

Can ERP do OEE?

Not accurately. OEE needs real-time machine data ERP does not capture.

Do I need both?

Most plants do — ERP for planning, MES for execution.

Where does a CMMS fit?

Maintenance execution; it complements MES. See the MES vs CMMS distinction.

Is MES always separate software?

Increasingly an OEE/MES platform covers execution without a heavyweight legacy MES.