MES vs ERP: The Difference and How They Work Together (2026)

MES (Manufacturing Execution System) manages real-time production on the shop floor; ERP (Enterprise Resource Planning) manages business-wide planning, finance, and supply chain. They operate at different levels of the ISA-95 / Purdue model hierarchy and solve fundamentally different problems — but they share data to close the loop between the factory floor and the boardroom. Most mid-to-large manufacturers need both.

Introduction: Two Systems, Two Domains

If you have stood next to a PLC panel and also sat in a budget review, you already sense the gap. The control engineer's world runs in milliseconds: scan times, cycle counts, OEE percentages updated every shift. The ERP world runs in days or weeks: purchase orders, production orders, material requirements planning (MRP), financial consolidation.

MES lives in the narrow band where those two worlds meet. It translates production orders from ERP into executable work instructions for operators and machines, then reports actual production results back up to ERP in near real time. ERP uses those results to update inventory, trigger procurement, and roll costs into the financial ledger.

The confusion between the two systems — and between MES, SCADA, and ERP — is partly a language problem. ERP vendors write marketing content aimed at CFOs. MES vendors aim at operations directors. Controls engineers sit in the middle trying to make sense of both. This guide cuts through that noise using the ISA-95 standard as a common reference frame.

What Is a Manufacturing Execution System (MES)?

A Manufacturing Execution System is software that directs, monitors, and records manufacturing operations from the moment a production order is released until the finished goods are confirmed into inventory. The term was standardized by the Manufacturing Enterprise Solutions Association (MESA International) in the early 1990s and later formalized in the ANSI/ISA-95 (IEC 62264) standard series.

Core MES Functions

ISA-95 Part 3 defines eight production operations management categories. In practice, MES software covers most or all of these:

• Production scheduling and dispatching — sequencing work orders to machines and cells based on capacity, tooling, and material availability
• Work order management — issuing electronic work instructions, traveler documents, and assembly sequences to operators
• Material tracking and genealogy — tracking lots, serial numbers, and consumed materials from receipt through finished goods
• Labor tracking — recording which operators performed which operations and for how long
• Quality management — collecting in-process inspection data, managing SPC charts, triggering non-conformance workflows
• Equipment management — tracking machine states (run, idle, down), planned vs. unplanned downtime, and maintenance requests
• Performance analysis — calculating OEE (Overall Equipment Effectiveness), throughput, yield, and scrap in real time
• Data collection — integrating directly with PLCs, SCADA systems, barcode scanners, and vision systems to capture process data automatically

MES software is sold by vendors including Siemens Opcenter, Rockwell FactoryTalk ProductionCentre, Aveva MES, Tulip, and many industry-specific solutions.

What Is an ERP System?

An Enterprise Resource Planning system is an integrated suite of business applications that manages and connects financial accounting, procurement, sales, inventory, human resources, and production planning across the entire enterprise. SAP S/4HANA, Oracle Cloud ERP, Microsoft Dynamics 365, and Infor CloudSuite are the dominant platforms in industrial manufacturing.

Core ERP Functions in a Manufacturing Context

• Production planning and MRP — generating planned orders based on demand forecasts, BOMs, and stock levels
• Inventory management — tracking raw material, WIP, and finished goods inventory at the warehouse and plant level
• Procurement and purchasing — managing supplier relationships, purchase orders, and goods receipts
• Financial accounting and costing — standard cost vs. actual cost variance, product profitability, general ledger
• Sales order management — customer orders, ATP (available-to-promise) checks, delivery scheduling
• Quality management (at the business level) — supplier quality, customer complaints, certificates of conformance
• Human resources and payroll — workforce planning and labor cost allocation

ERP plans what should happen. MES records what actually happens. That single sentence captures most of what you need to know — but the details of the boundary matter enormously when you are specifying systems.

MES vs ERP: Core Functions Side by Side

Dimension	MES	ERP
Primary domain	Shop floor operations	Enterprise business management
Time horizon	Seconds to shifts	Days to quarters
Data granularity	Machine-level, lot-level, serial-level	Plant-level, SKU-level, cost center
Real-time capability	Yes — continuous process data	Limited — batch updates, day-end closes
Production planning	Detailed sequencing / dispatching	MRP / MPS / capacity requirements planning
Material tracking	Genealogy, lot traceability, WIP location	Inventory quantities, warehouse locations
Quality	In-process SPC, non-conformance, inspection	Supplier quality, customer complaints, CoC
Labor	Operator activity, machine time per op	Payroll, workforce planning, HR
OEE / downtime	Native real-time calculation	Reported retrospectively if at all
Integration with PLCs	Direct (OPC UA, Profinet, EtherNet/IP)	Rarely — relies on MES or SCADA as intermediary
Standards	ISA-95 (IEC 62264), ISA-88, MESA	GAAP/IFRS, ISO 9001, industry-specific
Typical users	Production supervisors, quality technicians, engineers	Finance, procurement, planning, supply chain

Real-Time Shop Floor vs. Strategic Enterprise Planning

The most practically important difference between MES and ERP is time resolution.

An ERP production order is, in effect, a contract with the shop floor: "Produce 500 units of Part A by end of day Friday, consuming these raw material lot numbers, at this standard cost." That contract is set hours or days before production begins.

The MES accepts that contract and manages everything that happens during execution: which machine runs the job first, what happens when Machine 3 goes down and the job must re-route to Machine 5, how an operator records a quality deviation on Unit 247, and what the actual cycle time was on every unit. By the time the shift ends, the MES has a granular production report that ERP could never generate on its own.

ERP is incapable of real-time shop-floor control for a structural reason: it was designed around transactional database commits, not continuous data streams. Running an OEE calculation or a statistical process control chart inside SAP is technically possible but architecturally wrong — ERP databases are not designed for the write frequency that production data demands.

MES is incapable of enterprise-level planning for the opposite reason: it has no model of the supply chain, no financial ledger, no demand signal from customers. It knows there is a work order; it does not know why that work order exists or what it costs the business.

Data Flow and Integration Between MES and ERP

In a well-integrated plant, data flows in both directions across the MES-ERP boundary — a concept formally defined in ISA-95 Part 2 as the Level 3 / Level 4 interface.

Downward flow (ERP to MES)

1. ERP releases a production order specifying part number, quantity, required date, and allocated material lots.
2. ERP sends the current bill of materials and routing (sequence of operations, standard times).
3. ERP may send the production schedule at a high level (daily or shift-level buckets).

Upward flow (MES to ERP)

1. MES confirms goods issues — actual material consumed — so ERP can update inventory.
2. MES confirms production completions — actual quantity produced, including yield and scrap counts.
3. MES reports actual labor hours per operation for cost variance analysis.
4. MES reports non-conformances and quality holds that affect available inventory.

This bidirectional interface is often implemented using ISA-95 XML messages, REST APIs, or ERP-native integration adapters (SAP Plant Connectivity, for example). The integration point is frequently the most complex part of an MES implementation — not because the technology is difficult, but because the data models on either side were built by different teams with different assumptions.

For deeper context on IIoT integration patterns that underpin modern MES-ERP data exchange, see our guide to IIoT and PLC integration.

Where MES Sits for the Controls Engineer: The Purdue / ISA-95 Model

This is the section that ERP vendor blogs structurally cannot write — and the reason controls engineers often find MES content unsatisfying. The Purdue Reference Model (developed by Theodore Williams in the 1990s) and its modern equivalent in ISA-95 / IEC 62264 define five levels of industrial automation hierarchy. Understanding which level each system occupies explains every integration decision.

The Five Levels

Level 0 — Field devices Sensors, actuators, transmitters, and final control elements. These generate raw physical signals: 4–20 mA analog, discrete 24 VDC, encoder pulses, thermocouple voltages.

Level 1 — Basic control (PLC / DCS) Programmable Logic Controllers (PLCs) and Distributed Control Systems (DCS) execute the real-time control logic: reading Level 0 signals, running ladder logic or function block programs, and writing outputs back to field devices. Scan cycles are typically 10–100 ms. This is where industrial control systems live.

Level 2 — Supervisory control (SCADA / HMI) SCADA systems and HMI panels aggregate data from Level 1 controllers, display process state to operators, log historical trends, and manage alarms. SCADA does not run production orders — it monitors and controls the physical process. See SCADA best practices for design guidance at this level.

Level 3 — Manufacturing operations (MES) MES sits at Level 3. It has no direct connection to field devices. It receives data from SCADA/historians (via OPC UA, database queries, or messaging middleware) and issues work instructions to human operators. Level 3 is concerned with production operations over a horizon of shifts and days — not milliseconds.

Level 4 — Business planning (ERP) ERP operates at Level 4. It has no direct knowledge of individual machines or process variables. It plans production in buckets of days and weeks, manages financial transactions, and connects the factory to the supply chain and customer base.

The ISA-95 Hierarchy (Visual Reference)

┌─────────────────────────────────────────────────┐
│  LEVEL 4 — ERP                                  │
│  Business planning, MRP, finance, supply chain  │
│  Horizon: days → quarters                       │
├─────────────────────────────────────────────────┤
│  LEVEL 3 — MES                                  │
│  Manufacturing execution, OEE, quality, WIP     │
│  Horizon: seconds → shifts                      │
├─────────────────────────────────────────────────┤
│  LEVEL 2 — SCADA / HMI                          │
│  Supervisory control, alarming, historian       │
│  Horizon: milliseconds → minutes                │
├─────────────────────────────────────────────────┤
│  LEVEL 1 — PLC / DCS                            │
│  Real-time control logic, I/O scan              │
│  Horizon: 10–100 ms scan cycle                  │
├─────────────────────────────────────────────────┤
│  LEVEL 0 — Field devices                        │
│  Sensors, actuators, transmitters               │
│  Horizon: continuous physical process           │
└─────────────────────────────────────────────────┘

This hierarchy clarifies what "integration" means at each boundary:

• L1 ↔ L2: OPC UA, Modbus TCP, EtherNet/IP, Profinet — real-time tag data
• L2 ↔ L3: OPC UA Historical Access, SQL historian queries, MQTT — aggregated process data and events
• L3 ↔ L4: ISA-95 XML, REST APIs, SAP Plant Connectivity, B2MML — production orders and confirmations

MES vs SCADA vs ERP: The Three-Way Comparison

The question "what is the difference between MES, SCADA, and ERP?" is the most frequent source of confusion for engineers who are new to manufacturing IT. All three systems exist in the same plant. They share data. In some vendor product lines, features overlap. Here is the direct comparison.

Dimension	SCADA	MES	ERP
ISA-95 level	L2	L3	L4
Primary purpose	Monitor and control the physical process	Execute and record production operations	Plan and manage the business
Real-time control	Yes — can write setpoints and outputs to PLCs	No — issues instructions to operators, not PLCs	No
Production orders	None — operates on process variables	Accepts, sequences, and closes work orders	Creates and releases work orders
Historian / trending	Yes — native or via separate historian	Consumes historian data; does not replace it	No
Quality data	Process variable trends, SPC in some systems	In-process inspection, non-conformance, SPC	Supplier/customer quality, CoC
OEE calculation	Sometimes (via downtime tracking add-ons)	Native — real-time OEE is a core MES capability	Retrospective reporting only
Lot traceability	Limited — timestamp-based correlations	Full genealogy: consumed lots → finished serial numbers	Inventory-level lot tracking
Connects to PLCs	Yes — direct protocol integration	Indirectly — via SCADA/historian layer	No
Users	Control room operators, maintenance	Production supervisors, quality technicians	Finance, planning, procurement
Key standards	IEC 62443, ISA-18.2, ISA-101	ISA-95, ISA-88, MESA	GAAP/IFRS, ISO 9001

The critical boundary: SCADA is not MES

A common misunderstanding is that a well-configured SCADA system can replace MES. It cannot — not for three reasons:

1. SCADA has no order model. SCADA does not know that you are running Work Order 4400123 for Customer X. It knows that Tank 3 is at 78°C and Pump 7 is running. MES maps process state to production orders and business context.
2. SCADA does not manage people. Work instructions, operator certifications, labor recording, and shift handover are MES functions. SCADA presents process data to already-trained operators.
3. SCADA does not report upward to ERP. SCADA historians are not ERP-ready — they produce time-series data, not production confirmations, goods issues, or quality records in the format ERP systems expect.

For manufacturing operations beyond simple, single-product lines, SCADA and MES are complementary, not alternatives. Refer to our manufacturing automation guide for a broader view of how these layers fit into a complete automation architecture.

Can MES Replace ERP — or Is MES Part of ERP?

Can MES replace ERP?

No. MES does not replace ERP. MES has no financial accounting engine, no accounts payable/receivable module, no MRP engine that plans across multiple plants, and no customer relationship management capability. A plant running only MES has no system generating production orders, managing purchase orders, or producing financial statements.

Some smaller manufacturers use MES-like features built into an advanced planning and scheduling (APS) tool, which may reduce the need for a full ERP at very small scale. But for any business with multiple plants, customers, suppliers, or financial reporting requirements, ERP is a separate mandatory layer.

Is MES part of ERP?

Not technically — though the line is blurring. Major ERP vendors have added manufacturing execution modules:

• SAP offers SAP Digital Manufacturing (formerly SAP ME / SAP MII) which integrates tightly with SAP S/4HANA but is architecturally a separate application running at Level 3.
• Oracle offers Oracle Manufacturing Execution System within the Oracle Fusion Cloud supply chain suite.
• Microsoft Dynamics 365 has manufacturing execution features in its Supply Chain Management module.

These bundled offerings are often called "integrated MES" or "ERP-embedded MES." They reduce integration complexity but frequently have shallower shop-floor functionality than best-of-breed standalone MES platforms. The right choice depends on the complexity of your production environment and how tightly your operations team needs to interact with machine-level data.

The important architectural point: even when sold as part of an ERP suite, the MES component still operates at ISA-95 Level 3. The conceptual boundary does not disappear just because two applications share a database.

Do You Need Both MES and ERP?

The short answer: most discrete and process manufacturers above a certain scale need both.

When you need MES in addition to ERP

• You produce complex discrete assemblies with multi-level BOMs and serialized traceability requirements (aerospace, medical devices, automotive)
• You need real-time OEE visibility by machine, line, or cell
• You have regulatory requirements for electronic batch records or production genealogy (FDA 21 CFR Part 11, EU MDR, ISO 13485)
• You run complex production routings with alternative machines, tool changes, or setup sequences
• Your scrap and rework rates are high and you need root-cause data at the operation level
• You are pursuing digital twin in manufacturing capabilities that require accurate as-built data

When ERP alone may be sufficient

• Simple, high-volume repetitive manufacturing with limited product variants
• Single-product lines where the only production event is a daily count confirmation
• Very small plants (fewer than 20–30 production employees) where manual data collection is practical

When SCADA alone may be sufficient at L3 (without a full MES)

• Continuous process industries (water/wastewater, power generation, bulk chemicals) where production is measured in flow rates rather than discrete work orders
• Plants where process optimization and real-time alarming are the primary requirements and order-level traceability is not

The IIoT integration guide covers how modern cloud-connected architectures are shifting some traditional MES data collection into IIoT platforms — relevant if you are evaluating whether a lightweight IIoT solution can substitute for a full MES at lower cost.

Summary Comparison Table

	MES	ERP
Full name	Manufacturing Execution System	Enterprise Resource Planning
ISA-95 level	Level 3	Level 4
Manages	Shop floor operations	Business operations
Time resolution	Real-time to shift-level	Daily to quarterly
Creates work orders?	No — receives them from ERP	Yes
Closes work orders?	Yes — with actuals	Receives confirmations from MES
OEE tracking	Yes, natively	No
Full lot genealogy	Yes	Partial (warehouse-level)
Financial accounting	No	Yes
MRP / supply chain	No	Yes
Talks directly to PLCs	Indirectly (via SCADA/historian)	No
Key standard	ISA-95, ISA-88	GAAP/IFRS, ISO 9001
Example vendors	Siemens Opcenter, Rockwell FactoryTalk, Aveva, Tulip	SAP, Oracle, Microsoft Dynamics, Infor

---

Frequently Asked Questions

What is the difference between MES and ERP?

MES (Manufacturing Execution System) manages the real-time execution of production on the shop floor — tracking work orders, operator activities, machine states, quality data, and material genealogy as production happens. ERP (Enterprise Resource Planning) manages the broader business: creating and planning production orders, managing inventory and procurement, running financial accounting, and connecting the factory to customers and suppliers. MES operates at ISA-95 Level 3 (seconds to shifts); ERP operates at Level 4 (days to quarters). They exchange data across the Level 3/4 interface — production orders flow down from ERP to MES; actual completions, material consumption, and quality results flow back up.

Is MES part of ERP?

Not architecturally. MES is a separate application operating at ISA-95 Level 3 while ERP operates at Level 4. Some major ERP vendors (SAP, Oracle, Microsoft) sell MES modules that integrate tightly with their ERP platforms, which can reduce integration complexity. However, even these bundled solutions remain architecturally distinct: the MES component handles real-time shop-floor operations that the ERP core is not designed to manage. In practice, "integrated ERP-MES" suites trade some shop-floor functionality depth for easier data integration.

Do you need both MES and ERP?

Most mid-to-large manufacturers need both. ERP is the system of record for business planning, financial accounting, and supply chain management. MES is the system of record for what actually happened on the shop floor. Without MES, the ERP production confirmation is a manual count from the shift supervisor. Without ERP, the MES has no demand signal, no BOM, and no financial context for its production data. The two systems are complementary rather than competitive. Smaller manufacturers or simple continuous-process operations may manage with ERP alone if their traceability and real-time visibility requirements are limited.

What is the difference between MES, SCADA, and ERP?

These three systems occupy three different levels of the ISA-95 / Purdue model hierarchy. SCADA (Level 2) monitors and controls the physical process — it reads signals from PLCs, displays process variables to operators, logs historical trends, and manages alarms. It knows the state of pumps, temperatures, and pressures but has no knowledge of production orders or business context. MES (Level 3) sits above SCADA and maps process activity to production orders — it knows that Line 2 is running Work Order 4400123, what material lots are being consumed, and whether the resulting product passed inspection. ERP (Level 4) sits above MES and manages the business — it created Work Order 4400123 in response to a customer order, planned the material requirements, and will record the financial cost when MES confirms the completion. Each level communicates with the levels immediately above and below it; ERP does not communicate directly with SCADA or PLCs.