One of the most persistent misconceptions in manufacturing: "Our ERP already does everything, right?" Many ERP vendors sell their platform as the center of your digital universe. In practice, that's not true, and it's costing you money.
In this blog, we explain where the line is, why that line exists, and which mistakes we see time and again among Flemish SMEs.
One thing up front: MES isn't the whole story. It's the execution layer, and here it sits inside a broader MOM platform, alongside planning, quality, maintenance and traceability.
What does ERP actually do?
Enterprise Resource Planning (ERP) manages the business side of your company: from sales orders to production planning, from raw material procurement to invoicing. It works on a transactional basis: you see updates when a business event takes place. Think: raw material consumed, semi-finished product created, order delivered.
Typical ERP functions:
- Capacity planning and job sequencing
- Bill of Materials
- Supply chain management
- Inventory management
- Financial reporting (costs, revenue, margins)
The decision cycle of ERP is weeks, months, years. Quarterly figures, annual budgets, monthly forecasts.
What does MES do?
A Manufacturing Execution System (MES) sits on the shop floor. It's the layer where you actually execute the planned production: where you make your money. MES works event-driven and in real time: every second, every minute, every shift.
Typical MES functions:
- Work order management and execution
- OEE tracking (per minute, per shift, per line)
- Downtime logging and root cause analysis
- Machine-level scheduling
- Traceability and genealogy of production events
The decision cycle of MES is seconds to shifts. OEE is typically recalculated every 60 seconds. Downtime is detected in real time. An operator sees immediately what's happening on their line.
The same four axes, side by side:
| ERP | MES | |
|---|---|---|
| Manages | The business side: orders, purchasing, invoicing | Execution on the shop floor |
| Works with | Transactions | Events |
| Decision cycle | Weeks, months, years | Seconds to shifts |
| Sees of a running order | Start and finish | Every metre, every stop, every speed change |
| Who works with it | Management and administration | Operator, shift lead, production manager |
The fundamental difference: transactions vs. events
This is the core of it. ERP works with transactions: you bundle a series of events and send them upward as a package. MES works with events: every meter of film produced, every sensor reading, every status change is recorded live.
A concrete example: say you have a printing press that prints a roll of foil.
- In ERP you see two moments: raw material consumed (start) and semi-finished product created (3 hours later). In between: silence.
- In MES you see everything that happens in between: every running meter, every speed change, every short stop, the OEE per minute.
If you rely on ERP alone, you have a 3-hour blind spot. And in those 3 hours you lose efficiency you'll never get back, because you didn't even know it was there.
The 4 most common mistakes
1. Treating ERP as the "center of the universe"
ERP vendors love to sell this story. But ERP isn't designed for real-time decisions on the shop floor. Its data architecture (transaction-based, with delays of minutes to hours) isn't suited to tell an operator that their line is currently running 12% below target.
2. Trying to cram MES functions into ERP
We regularly see companies trying to build OEE calculations or downtime logging into their ERP. The result: slow queries, outdated data, and operators who bypass the system because it doesn't respond fast enough. MES functionality belongs in a system designed for event-driven, real-time data.
3. Ignoring the IT/OT gap
ERP is IT territory. PLCs, SCADA, and sensors are OT territory. MES sits exactly in between, and it shows: of the manufacturers we talk to in Belgium, only a small minority runs a digital MES today. It's where IT and OT meet, and often clash. Anyone who doesn't acknowledge this ends up building a system that neither team truly owns.
4. Failing to distinguish between planning and execution
Planning (ERP) and execution (MES) are fundamentally different processes with different speeds, different data requirements, and different users. A planner works with weekly schedules and capacity models. An operator works with what's happening on their machine right now. You connect these two worlds through integration, not by forcing them into one system.
So how do ERP and MES actually work together?
The right approach: let each system do what it's good at, and connect them through structured transactions.
From ERP to MES flow work orders, bills of materials, schedules, and raw material data. From MES to ERP flow completed work orders, consumption records, quality data, and production output, bundled as transactions.
In a modern architecture, there's often a Unified Namespace (UNS) in between: an MQTT-based data bus that ensures every layer, from PLC to ERP, has access to the right data, at the right time, in the right format.
Conclusion
ERP and MES aren't competitors. They're complementary systems, each with its own speed, scope, and users. The mistake isn't having an ERP, it's assuming ERP is enough to run your shop floor.
If your factory is running today without an MES, you're missing insight into what's happening on your lines shift by shift, minute by minute. And that insight is exactly where the profit lies.
The companies making the difference today don't have the most expensive ERP system, they understand what's happening on the shop floor, in real time!