Key takeaways
Short answer: ERP and MES operate at two different altitudes. ERP is the business-planning system: it manages orders, inventory, finance, procurement, and high-level production planning across the whole enterprise. MES is the shop-floor execution system: it takes the plan, dispatches it to the line, enforces the routing, and tracks what actually happened in real time. ERP decides what and when; MES governs and records how. They are partners, not competitors. For the layer below MES, see SCADA vs MES.
Enterprise Resource Planning is the business backbone. ERP integrates the core functions of a company — sales orders, inventory, procurement, finance, HR, and high-level production planning — into one system of record. In manufacturing terms, ERP is where a customer order becomes a production order, where material requirements are planned, where costs and inventory are tracked at the business level. It works in the language of orders, money, and plans, usually on a horizon of days, weeks, and months. What ERP does not do well is the real-time, second-by-second reality of the shop floor: it knows a production order exists and is due, but not whether machine 3 is running slow right now or why last night's batch lost two hours. That granular execution truth lives a level down.
A Manufacturing Execution System lives on the floor, between the business plan and the machines. MES takes the production orders ERP releases and manages their execution in real time: it dispatches work to specific lines, enforces the correct routing and recipe, collects what was actually produced and when, captures genealogy and quality, and reports performance back up. Where ERP sees an order due Friday, MES sees that order running on Line 2 right now, at this rate, with this scrap, two hours behind because of a changeover. MES is the system that turns a plan into tracked, enforced, recorded execution — the operational truth of how production is actually unfolding, which ERP needs but cannot see on its own.
The ISA-95 model places them cleanly. Level 4 is ERP — business planning and logistics. Level 3 is MES — manufacturing operations management: dispatching, tracking, quality, and performance. Below that, Level 2 is SCADA and control, and Levels 1 and 0 are the devices and the process itself. ERP and MES are vertical neighbours that exchange information in both directions: ERP passes orders, schedules, and material plans down to MES; MES passes actual production, consumption, and status back up to ERP. Trouble usually starts when a company tries to run the floor directly from ERP with no Level 3 layer — ERP simply lacks the real-time granularity — or lets MES and ERP drift out of sync so the plan and the reality no longer match. For the data plumbing beneath, see unified namespace vs point-to-point integration.
A customer order for 10,000 units lands in ERP. ERP plans it: checks material availability, schedules it for next week, creates the production order, and commits a due date. That order flows down to MES, which dispatches it to a specific line, enforces the routing, and starts tracking. On the floor, MES records reality: the line ran at 85% of rate, lost ninety minutes to an unplanned stop, and scrapped 240 units. MES feeds that actual production and consumption back to ERP, which updates inventory, cost, and the schedule. ERP planned the what and when; MES governed and recorded the how. Neither could have done the other's job — and the loop between them is what keeps the business plan tied to floor reality.
The two answer fundamentally different questions, which is why most manufacturers of any scale run both. Try to manage the floor from ERP alone and you get plans with no real-time execution, enforcement, or traceability — the order is due, but nothing governs or records how it is actually built. Run MES with no ERP and the floor executes brilliantly but in isolation from orders, inventory, finance, and planning. The value is in the connection: ERP gives MES the right work in the right priority; MES gives ERP the truth about what really happened. Smaller operations sometimes start with ERP plus a lightweight execution or OEE layer and add full MES as traceability and complexity grow.
Neither ERP nor MES is, by itself, an OEE system, but both touch it. ERP supplies the order and schedule context; MES supplies the production counts, downtime, and quality events that OEE is built from. A focused OEE layer ties them together with the high-resolution machine signals from the control level, turning order, execution, and equipment data into availability, performance, and quality — and attributing losses to the six big losses. Without that layer, ERP knows the order was late and MES knows the line stopped, but neither cleanly answers how much output you lost and to which cause. OEE is the missing analytical lens across the stack.
Fabrico is the focused OEE and maintenance layer that complements ERP and MES rather than replacing either. It ingests the real production and downtime data, adds shift, order, and reason-code context, and turns it into live availability, performance, and quality you can act on — the granular loss truth that ERP plans against and MES tracks but neither fully analyses. For manufacturers who want that measurement quickly without a multi-year systems programme, it slots alongside whatever planning and execution stack you already run. Book a demo to see it fit your systems.
ERP (Enterprise Resource Planning) manages business-wide resources — orders, inventory, finance, and high-level planning. MES (Manufacturing Execution System) manages and tracks the real-time execution of production on the floor. ERP plans what and when; MES governs and records how.
Most manufacturers of any scale benefit from both. ERP plans the business and releases orders; MES executes, enforces, and tracks them on the floor, then feeds reality back. Running the floor from ERP alone lacks real-time execution, while MES alone is disconnected from planning.
ERP is Level 4 (business planning and logistics) and MES is Level 3 (manufacturing operations management). They exchange information vertically: ERP passes orders and plans down, MES passes actual production and status up.
Not well. ERP lacks the real-time granularity to dispatch work, enforce routing, capture genealogy, and track second-by-second execution. Those are MES functions, and trying to do them in ERP usually leads to plans disconnected from floor reality.
ERP supplies order and schedule context, MES supplies production counts and downtime events, and a focused OEE layer combines them with machine signals to produce availability, performance, and quality and attribute losses to the six big losses.
Zaloguj
Blog
