MES vs ERP: What ERP Misses on the Shop Floor and How They Share Data

Enterprise Resource Planning (ERP) systems are essential for finance, planning, procurement and supply chain. But when it comes to real time shop floor visibility, an ERP cannot see what is truly happening at the machine, line and shift level. This blind spot is exactly where a Manufacturing Execution System (MES) and real time OEE monitoring create value.

This article explains what an MES captures that ERP cannot, where each system should own the truth, and how to connect them so that planning and execution use the same live data.

Request a demo

ERP vs MES: Two Different Views of the Same Factory

ERP is built for business processes. It works in orders, items, quantities, dates and costs. It helps you answer questions like: What do we have to produce next week, what material do we need and what will it cost.

MES is built for production processes. It works in machines, shifts, cycles, micro stops, operator actions, changeovers and defects. It helps you answer questions like: Why are we behind schedule right now, where are we losing time and how can we stabilise output on this line.

At a high level:

• ERP plans and records what should happen and what has happened commercially.
• MES monitors what is happening now, why it is happening, and what operators and maintenance are doing in response.

Both are needed. The challenge is that many manufacturers try to stretch ERP down to the shop floor, or stretch MES up into planning. That often creates manual workarounds, unreliable data and frustrated teams.

What ERP Cannot See On The Shop Floor

An ERP relies on transactional events entered by people. Goods receipts, production confirmations, time bookings and material issues are all discrete actions. They do not describe the true flow of production between those events, which is where most losses hide.

Typical blind spots of ERP on the shop floor include:

1. Micro stops and speed losses

ERP can show that a work order took 10 hours instead of the planned 8. It cannot show that the line stopped for a few seconds hundreds of times, that speeds dropped during certain SKUs, or that startup after breaks is consistently slower.

An MES with machine connectivity and OEE monitoring captures:

• Every stop and speed change with timestamps.
• Automatic categorisation of downtime and speed loss, supported by operators when needed.
• Performance trends by product, tool, shift, crew and machine.

This level of detail is essential for continuous improvement and reliable capacity estimation. For more context on how OEE and MES complement each other, see this article on OEE vs MES.

2. Real time OEE and loss structure

ERP can report planned versus actual quantities and durations, usually after the event. It cannot calculate OEE in real time or show where you are losing Availability, Performance and Quality during the shift.

An MES focused on OEE:

• Calculates OEE and its components continuously.
• Breaks losses down into a clear structure: setup, changeover, breakdown, minor stoppages, speed loss, scrap and rework.
• Surfaces losses by priority and trend, not only by category.

Without this, improvement efforts are based on partial information or anecdote. ERP alone cannot provide the granularity required for structured loss analysis.

3. Actual run sequence, changeovers and setups

ERP plans sequences. It does not see what sequence operators actually run, how long changeovers really take and what conditions influence setup time.

An MES records:

• Start and end of every run as it happens.
• Setup and changeover time automatically, not only what is booked at the end.
• Which crew, tooling, materials and parameters were involved.

This data is crucial for realistic planning and for improvement projects focused on SMED and faster changeovers.

4. Machine states and operator actions

ERP knows about work orders. It does not know whether a machine is running, idle, blocked, starved or faulted at this moment, or what the operator is doing about it.

An MES with integrated maintenance and production workflows like Fabrico:

• Shows live machine status and reason codes.
• Lets operators log issues, notes and checklists directly at the machine.
• Triggers maintenance tasks when specific patterns or downtimes appear.

This is where a built in CMMS inside the MES becomes important. It lets maintenance receive issues straight from production data, rather than relying on phone calls or paper notes.

5. Quality at the line, not only at inspection

ERP holds quality results linked to batches or lots, usually at key inspection points. It rarely tracks scrap and rework in real time per cycle, cavity or machine.

An MES can capture:

• Scrap and rework quantities by reason, operator and time.
• First pass yield by product and machine.
• Correlations between quality issues, setups, parameters and maintenance actions.

This continuous view of quality lets you address issues before they become systemic and compromise customer deliveries.

Where ERP Should Remain The Source Of Truth

MES does not replace ERP. Each has a clear domain where it should own the master data and transactions.

ERP should remain the source of truth for:

• Customers, vendors and pricing.
• Sales orders and purchase orders.
• Bills of materials and routings, where appropriate.
• Inventory valuation and financial postings.
• High level production planning and MRP.

MES should be the operational system for:

• Production execution and dispatching at the line.
• OEE, downtime and performance monitoring.
• Operator instructions and checklists at the machine.
• Real time quality checks and process data collection.
• Maintenance requests and work execution on assets.

When both systems are connected properly, planners work in ERP with reliable feedback from the MES, and production teams work in the MES without retyping ERP data.

How MES And ERP Share Data In Practice

For mid size and large manufacturers, MES and ERP integration usually revolves around a few core data flows. The goal is to avoid duplicate entry, achieve a consistent view of orders and inventory, and surface real time performance information where decisions are made.

1. From ERP to MES: what needs to be produced

Typically ERP sends the MES:

• Production orders with quantities and due dates.
• Item and BOM information needed on the line.
• Planned routing or work centers.

In Fabrico, production orders from ERP appear as dispatch lists on the shop floor. Supervisors and operators can see what is next, with the right production context and instructions.

2. Inside the MES: what is really happening

Once orders are dispatched, the MES takes over execution and monitoring.

Fabrico connects directly to machines to capture:

• Start and end of each job.
• Good and reject counts where available.
• Machine states and downtime reasons.

Operators complement the data with confirmations, reason codes and comments through simple interfaces instead of complex ERP screens. The built in CMMS uses the same data to create and prioritise maintenance work based on actual performance and failures, not only on calendar or manual tickets.

3. From MES to ERP: what has been produced

At completion, the MES sends back to ERP:

• Produced quantities, including scrap where relevant.
• Actual production times to update performance and capacity data.
• Optionally, consumption information for backflushing rules.

This allows ERP to keep inventory, cost and delivery information accurate, while avoiding manual confirmations at the end of each order.

4. Performance dashboards for both operations and leadership

On top of this transactional exchange, MES and ERP can also share aggregated data for reporting. Operations teams need line level, shift level and asset level detail. Leadership needs rolled up KPIs across sites, products and customers.

Fabrico provides real time OEE and loss analysis for plants and lines, and this information can be surfaced in BI tools together with ERP data on revenue, margins and service levels. This connection helps leadership understand the operational reality behind the financial results.

Why Real Time OEE And Maintenance Matter For ERP Users

From an ERP point of view, the value of MES and OEE can look narrow at first: better shop floor visibility. In practice, it also improves the quality of ERP planning and financial data.

Real time OEE and integrated maintenance workflows help ERP users to:

• Plan capacity realistically, based on stable and measured performance.
• Quote lead times more confidently, especially for constrained resources.
• Reduce premium freight and overtime caused by unexpected downtime.
• Align maintenance budgets with actual asset performance and criticality.

Linking OEE, maintenance and production in one environment is described in more detail here: MES vs CMMS. The key point is that maintenance actions become directly connected to production losses, instead of operating in isolation.

How Fabrico Connects MES, OEE And ERP

Fabrico is a cloud based MES and OEE platform designed to capture data directly from machines, connect it with operator input and turn it into actions for production and maintenance.

For manufacturers running an ERP, Fabrico typically:

• Receives production orders and item data from ERP.
• Provides dispatch lists and work instructions to the shop floor.
• Captures OEE, downtime and performance data in real time.
• Creates and manages maintenance work based on those events with its built in CMMS capabilities.
• Sends back production confirmations and performance data to ERP.

This architecture keeps ERP clean and focused on business processes, while giving plants the real time control they need on the shop floor. For more on the production monitoring side, see this guide to the best production monitoring systems.

Choosing The Right Boundary Between ERP And MES

When you consider an MES like Fabrico alongside your ERP, it helps to define a clear boundary:

• Keep ERP as the planning and financial backbone.
• Use MES as the real time execution and improvement layer on the shop floor.
• Integrate the two so data flows automatically and consistently in both directions.

If ERP is stretched too far into real time production control, shop floor teams end up with slow, complex transactions and little operational insight. If MES is stretched too far into planning, you duplicate logic and master data. A clear division, supported by integration, avoids these problems.

Next Steps

If you are evaluating how to combine MES, OEE and ERP in your plants, it helps to see live data flowing from machines into orders and actions.

• Request a demo to see how Fabrico connects to machines, operators and ERP.
• Contact us to discuss your current ERP landscape and shop floor challenges.