MES vs ERP: Differences, Integration & Decision Guide

TL;DR: MES and ERP are not competitors — they operate on different ISA-95 layers and answer different questions. ERP manages orders, materials, and costs (Level 4). MES manages machines, operators, and real-time execution (Level 3). Neither replaces the other. The question is not "MES or ERP" but "how tightly are they integrated?" Bidirectional integration — ERP sends orders down, MES sends actuals back — eliminates manual re-entry, closes the planning-to-execution gap, and creates the data foundation for OEE, traceability, and continuous improvement.

Table of contents

1. What is the core difference between MES and ERP?
2. Functional comparison: MES vs ERP
3. What can ERP not do on the shop floor?
4. How does MES-ERP integration work in practice?
5. When do you need MES, when ERP, when both?
6. Real integration examples
7. FAQ

What is the core difference between MES and ERP?

ERP and MES address different layers of the manufacturing value chain, defined by the ISA-95 standard:

• ERP (Level 4) manages business-level processes: order handling, purchasing, materials planning, finance, logistics. Time horizon: days to weeks. Users: management, controlling, planning.
• MES (Level 3) manages shop-floor execution: production scheduling, machine data collection, production data collection, quality, traceability, real-time KPIs. Time horizon: seconds to minutes. Users: shift leaders, operators, OpEx managers.

The simplest distinction: ERP defines what to produce and when. MES ensures how it's produced and with what result. ERP manages the plan. MES manages the reality. Together, they form a closed-loop manufacturing control system.

Functional comparison: MES vs ERP

What can ERP not do on the shop floor?

This is the section most "MES vs ERP" articles skip. The honest answer: ERP was never designed for shop-floor execution. It does not fail at these tasks — it was never built for them.

The practical consequence: Manufacturers who rely solely on ERP for production visibility have a blind spot of hours to days. They see what was planned. They see what was booked at the end of the shift. They do not see what is happening right now. That gap is where MES operates.

How does MES-ERP integration work in practice?

Bidirectional integration between MES and ERP creates a closed-loop system: ERP sends orders down, MES sends actuals back.

Interface standards: REST API, OPC-UA, MQTT, SAP IDoc (ABAP), XML/CSV file exchange, Navision file interfaces.

Integration modes:

• Real-time (event-driven): MES pushes data to ERP on events (order start, order complete, scrap event). Lowest latency.
• Batch synchronization: MES aggregates data and sends at intervals (every 15 min, every hour, every shift). Lower complexity.
• Hybrid: Critical events (machine stops, quality alerts) real-time, routine bookings in batch. Most common in practice.

What integration eliminates: At Schmiedetechnik Plettenberg, the bidirectional InforCOM ↔ SYMESTIC integration eliminated all manual production bookings. When a production order is released in the ERP, all operations, machine assignments, and time targets appear automatically in SYMESTIC. During production, quantities, times, downtimes, and status updates flow back into InforCOM — without a single manual entry. The result: fewer errors, faster order tracking, and a complete production history for every order.

When do you need MES, when ERP, when both?

The common misconception: "We need to finish the ERP project first, then add MES." In practice, this delays shop-floor visibility by 12–24 months. A cloud-native MES can be deployed in parallel — capturing machine data from week one while the ERP project runs. Integration follows when the ERP is ready.

Real integration examples

The pattern: Integration complexity depends on the ERP, not on the MES. SAP requires ABAP/IDoc development. Navision uses file interfaces. InforCOM uses structured data exchange. SYMESTIC provides REST API and pre-built connectors for all major ERP systems — SAP S/4HANA, Microsoft Dynamics 365, proALPHA, Infor, abas.

FAQ

Does MES replace ERP?
No. MES and ERP operate on different ISA-95 layers and serve different functions. ERP manages business planning (orders, materials, finance). MES manages shop-floor execution (machines, quality, real-time KPIs). They are complementary, not competitive.

Can ERP calculate OEE?
Not reliably. OEE requires cycle-level machine data captured in real time (seconds). ERP operates on booking data captured in batch (hours to days). An ERP-calculated OEE is always delayed and systematically inaccurate — it misses micro-stops, short downtimes, and actual cycle time deviations.

Should I implement MES or ERP first?
If you have an ERP but no shop-floor transparency: add MES. If you have neither: start with MES — it delivers value (OEE, downtime visibility) within weeks. ERP projects take 6–18 months. A cloud-native MES can run standalone and integrate with the ERP later.

What does MES-ERP integration cost?
Integration cost depends primarily on the ERP side: SAP requires ABAP development (€ 5,000–20,000 depending on scope). Navision/Dynamics use simpler file or API interfaces (€ 2,000–8,000). The MES side (SYMESTIC) provides standard REST API and pre-built connectors included in the subscription.

Can MES work without ERP?
Yes. MES captures machine data, calculates OEE, tracks downtimes, and provides real-time dashboards independently. ERP integration adds order context (which product, which order, which customer) and eliminates double bookings. Many SYMESTIC customers start without ERP integration and add it later.

The key takeaway: ERP manages the plan. MES manages the reality. Neither is complete without the other. The integration between them — not the individual systems — is what creates a data-driven manufacturing operation. Start where you have the biggest gap: if you lack shop-floor visibility, start with MES. If you lack order management, start with ERP. If you have both but they don't talk to each other, the integration is your highest-ROI project.

→ What is MES? · → MES Software Compared · → Cloud MES vs. On-Premise · → MES Implementation · → MES vs. SCADA · → MES Costs