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

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

ERP plans and schedules; MES executes and records what actually happened on the floor. Why forcing ERP to run the floor produces stale, wrong data.
Manufacturing Execution System vs ERP on the Shop Floor: Who Owns What
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: Enterprise resource planning (ERP) and the manufacturing execution system (MES) sit at different altitudes of the same factory. ERP plans, schedules and accounts; the MES executes the plan on the floor and records what physically happened — machine by machine, second by second. When a plant forces ERP to act as its shop-floor system, it ends up with stale, hand-keyed data that never matches reality, because ERP was never built for the pace of the floor. See also mes vs erp.

What ERP actually owns

ERP is the system of record for the business. It answers planning and financial questions: what should we make, with what materials, against which orders, at what cost. Its data is transactional and batch-oriented — a purchase order, a goods receipt, a production confirmation — entered minutes or hours after the fact.

  • Demand, sales and production planning (MRP).
  • Purchasing, inventory and materials transactions.
  • Costing, finance and order management.
  • The master data (BOMs, routings, work centres) the floor consumes.

What the MES actually owns

The MES is the system of execution. It lives on the floor and answers a different question entirely: what is happening right now, and what just happened. It captures thousands of events per shift automatically, not through human data entry.

  • Dispatching and executing work orders.
  • Real-time machine state, counts, speeds and stoppages.
  • Downtime, scrap and quality capture with reason codes.
  • Genealogy, traceability and operator activity.
  • OEE and live performance.

The core difference: plan versus reality

ERP describes the plan; the MES describes reality. ERP says a work order should produce 1,000 units in eight hours; the MES records that the line actually ran 6 hours 40 minutes, stopped 14 times, lost 22 minutes to a changeover and scrapped 31 parts. ERP cannot see any of that — it only sees the final confirmation someone keys in at shift end. The gap between the two is where most factories lose money invisibly.

A worked example

A packaging line is told by ERP to make 10,000 units. At shift end an operator confirms "10,000 produced" in ERP and the books look perfect. The MES, capturing directly from the PLC, tells the real story: 10,420 units started, 9,980 good, 440 scrapped, with 38 micro-stops eating 41 minutes and the machine running 6% under rated speed. ERP shows a healthy order; the MES shows a 12-point OEE loss and a recurring jam worth fixing. Only the execution layer makes that visible, and only because it never relied on a person to notice.

How the two should connect

The right architecture is not ERP-or-MES but ERP-then-MES-then-ERP. ERP releases the schedule and work orders downward; the MES executes them and feeds validated actuals — real quantities, times and scrap — back up. ERP stops being a data-entry chore and becomes a consumer of trusted numbers. Get this handshake wrong and you get double entry, conflicting reports, and the endless meeting argument about whose number is right.

Common mistakes

1. Skipping the MES and bolting data entry onto ERP. Operators key numbers from memory; the data is late, rounded and wrong.

2. No clear ownership boundary. ERP and MES both try to own the same event and drift apart.

3. Treating OEE as an ERP feature. ERP cannot see micro-stops or speed loss, so its efficiency figure is fiction.

4. Manual reconciliation instead of integration. Teams spend hours each week making two systems agree instead of capturing once.

How it shows up in OEE

OEE is an execution-layer metric by definition. Availability, Performance and Quality all require real-time machine data that ERP never captures. Plants that compute OEE from ERP confirmations get one flattering number with no losses to act on; plants that compute it from the MES get a loss tree they can actually attack.

How Fabrico fits

Fabrico provides the execution layer — capturing OEE, downtime and quality straight from your machines and feeding clean actuals back toward ERP — without a heavyweight legacy MES rollout. Book a demo to see the floor-to-ERP data flow on your own lines.

Related reading

Frequently asked questions

Can ERP do OEE?

Not accurately. OEE needs real-time machine data ERP does not capture; an ERP efficiency figure hides the actual losses.

Do I need both ERP and an MES?

Most plants do — ERP for planning and finance, an execution layer for the floor. They answer different questions.

Where does a CMMS fit?

A CMMS handles maintenance execution and complements the MES; together they connect production reality with maintenance action.

Is an MES always separate software?

Increasingly an OEE/MES platform covers execution without a heavyweight legacy MES, then integrates with ERP.

What is the first integration to build?

Push the ERP schedule and work orders down, and feed real produced and scrap quantities back up — that single loop ends most number disputes.

Latest from our blog

Încă te întrebi?
Verificați singuri!
Încă te întrebi?

Programați o întâlnire individuală cu experții noștri sau înscrieți-vă direct în planul nostru gratuit.
Nu este nevoie de card de credit!

By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy și Cookies Declaration