SCADA vs MES vs ERP: The Difference and How They Connect
SCADA vs MES vs ERP explained — what each layer does, where they sit in the ISA-95 hierarchy, how data flows between them, and why you need all three.
SCADA monitors and controls the physical process in real time (ISA-95 Level 2). MES executes and records production operations at the shift and order level (Level 3). ERP manages business-wide planning, finance, and supply chain above the factory (Level 4). The three systems operate on different time horizons, serve different users, and solve different problems — but they share data across well-defined boundaries to close the loop from field device to boardroom.
Quick-Answer Comparison: SCADA vs MES vs ERP
| Dimension | SCADA | MES | ERP |
|---|---|---|---|
| ISA-95 level | Level 2 | Level 3 | Level 4 |
| Primary purpose | Monitor and control the physical process | Execute, record, and analyze production operations | Plan and manage the business |
| Time horizon | Milliseconds to minutes | Seconds to shifts | Days to quarters |
| Connects to PLCs | Yes — direct protocol integration | No — reads via SCADA / historian layer | No |
| Production orders | None — operates on process variables | Accepts, sequences, and closes work orders | Creates and releases work orders |
| Real-time control | Yes — writes setpoints and outputs | No — issues instructions to operators | No |
| OEE calculation | Add-on in some packages | Native core capability | Retrospective reporting only |
| Lot traceability | Limited timestamp correlation | Full genealogy — consumed lots to finished serials | Inventory-level lot tracking |
| Typical users | Control room operators, maintenance | Production supervisors, quality technicians | Finance, planning, procurement |
| Key standards | IEC 62443, ISA-18.2, ISA-101 | ISA-95 / IEC 62264, ISA-88, MESA | GAAP / IFRS, ISO 9001 |
The Automation Pyramid and ISA-95 in Brief
The fastest way to understand why SCADA, MES, and ERP each exist is to look at the ISA-95 / IEC 62264 standard and the Purdue Reference Model it formalizes. Both frameworks describe a five-level hierarchy in which each layer communicates only with its immediate neighbors — never skipping levels in a well-designed architecture.
┌─────────────────────────────────────────────────┐
│ 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 │
└─────────────────────────────────────────────────┘
Each boundary has a defined integration protocol. Level 1 to Level 2 uses real-time field protocols such as OPC UA, EtherNet/IP, and Profinet. Level 2 to Level 3 uses aggregated data via OPC UA Historical Access, SQL historian queries, or MQTT. Level 3 to Level 4 uses business-layer messages: ISA-95 XML, REST APIs, SAP Plant Connectivity (PCo), or B2MML (Business to Manufacturing Markup Language).
For a deeper treatment of the ISA-95 standard itself — including its object models, activity models, and the full B2MML message set — see the dedicated ISA-95 guide. For now, knowing that SCADA is Level 2, MES is Level 3, and ERP is Level 4 gives you the framework to understand everything else in this article.
What SCADA Does — Level 2, Real-Time Monitoring and Control
SCADA (Supervisory Control and Data Acquisition) is the software layer that sits directly above PLCs and DCS controllers. It reads tag values from controllers using field protocols (OPC UA, Modbus TCP, EtherNet/IP, Profinet), displays live process state to operators on graphical HMI screens, raises alarms when process variables exceed limits, logs historical trend data, and — critically — can write setpoints and commands back down to field devices.
What SCADA does well
- Real-time process visualization — displays tank levels, temperatures, pressures, motor states, valve positions, and every other process variable on operator graphics updated every second or faster
- Alarming and event logging — implements ISA-18.2-compliant alarm management, capturing alarm onset, acknowledgement, and return-to-normal with millisecond timestamps
- Historical trending — stores time-series process data in a historian database (OSIsoft PI / AVEVA PI, Ignition Historian, Wonderware InTouch Historian) at configurable sample rates
- Remote control — lets operators issue commands (start pump, open valve, change setpoint) without walking to the panel, typically with proper authorization levels
- Recipe management — in process industries, SCADA can store and download ISA-88 recipes to PLCs, setting batch parameters automatically
What SCADA does not do
SCADA has no concept of a production order, a work order, or a lot number. It knows that Reactor 3 is running at 78°C — it does not know that Reactor 3 is currently executing Work Order WO-4400123 for Customer ABC, consuming Lot L-9902 of raw material. That business context belongs to MES.
SCADA also does not report upward to ERP. Historian time-series data is not the same as a production confirmation, a goods issue document, or a quality inspection record. SCADA is the data source; MES and ERP are the consumers of the business context that surrounds that data.
For engineering standards that govern SCADA design, see the SCADA best practices guide covering the ISA-112 lifecycle, ISA-18.2 alarm management, ISA-101 HMI design, and IEC 62443 cybersecurity.
What MES Does — Level 3, Execution, Scheduling, Traceability, and OEE
MES (Manufacturing Execution System) is the software layer at ISA-95 Level 3 that bridges the physical process world of SCADA with the business planning world of ERP. It accepts production orders from ERP, translates them into actionable work instructions for operators and machines, tracks every material lot and serial number through production, and reports actual results back up to ERP in near real time.
The Manufacturing Enterprise Solutions Association (MESA International) and the ISA-95 standard together define eight core MES functions:
- Production scheduling and dispatching — sequencing work orders to machines and cells based on current capacity, tooling availability, and material readiness
- Work order management — issuing electronic work instructions, assembly sequences, and traveler documents to operators at the point of use
- Material tracking and genealogy — recording which raw material lots were consumed to produce which finished serial numbers, enabling full forward and backward traceability for quality holds and recalls
- Labor tracking — logging which operator performed which operation and for how long, feeding actual labor hours back to ERP for cost variance analysis
- Quality management — collecting in-process inspection measurements, running SPC (Statistical Process Control) charts against control limits, triggering non-conformance workflows when defects occur
- Equipment management — tracking machine states (producing, idle, planned downtime, unplanned downtime) against OEE targets
- Performance analysis — calculating OEE (Availability × Performance × Quality) in real time by shift, machine, and product family
- Data collection — integrating with PLCs, SCADA systems, barcode scanners, RFID readers, and vision systems to capture process data automatically without manual entry
What MES does not do
MES has no financial accounting engine and no demand signal from customers. It knows there is a work order and when it must be complete. It does not know why that order exists, what it will sell for, or how to plan the purchase order for the raw materials. That strategic planning layer belongs to ERP.
What ERP Does — Level 4, Business Planning, Orders, and Inventory
ERP (Enterprise Resource Planning) is the integrated business software suite that manages 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 dominate industrial manufacturing. ERP operates at ISA-95 Level 4 — it has no direct connection to PLCs, historians, or field devices.
Core ERP functions in a manufacturing context
- Production planning and MRP — Material Requirements Planning calculates how much of each raw material and component to order and when, driven by demand forecasts, firm sales orders, and current inventory levels
- MPS (Master Production Scheduling) — sets the production plan in terms of finished goods quantities per time period, balancing demand against demonstrated capacity
- Inventory management — tracks raw material, work-in-process, and finished goods inventory at the warehouse and plant level in units and financial value
- Procurement and purchasing — manages supplier relationships, generates and tracks purchase orders, processes goods receipts, and handles accounts payable
- Sales order management — records customer orders, performs ATP (available-to-promise) checks against inventory and production schedules, and triggers order fulfilment
- Financial accounting and costing — compares standard cost to actual cost (via data received from MES), calculates product profitability, and consolidates into the general ledger
- Quality management at the business level — manages supplier quality ratings, customer complaint resolution, and certificates of conformance — not in-process SPC
What ERP does not do
ERP cannot perform real-time shop-floor control — it was built around transactional database commits, not continuous data streams. Running OEE calculations or SPC charts inside SAP is technically possible in some add-ons but architecturally wrong: ERP databases cannot sustain the write frequency that production data demands. ERP receives aggregated production confirmations from MES; it does not poll PLCs.
Three-Way Comparison: Scope, Timeframe, Users, and Data
| Dimension | SCADA | MES | ERP |
|---|---|---|---|
| Scope | Physical process — one plant, one production line | Production operations — one or more plants | Enterprise — all plants, supply chain, financials |
| Timeframe | Milliseconds to minutes | Seconds to shifts (8–12 hours) | Days to fiscal quarters |
| Data type | Time-series process variables, alarms, events | Production order status, lot data, OEE, quality records | Financial transactions, inventory balances, planned orders |
| Data volume per day | Very high — millions of tag samples | Moderate — thousands of production events | Low — hundreds of business transactions |
| Update frequency | Sub-second to 1-second scans | Near real time to shift-end | Batch — often end-of-day or hourly at best |
| Primary users | Control room operators, maintenance technicians | Production supervisors, quality engineers, schedulers | Finance controllers, procurement buyers, supply chain planners |
| Connects to | PLCs / DCS (down), historian (up), MES (up) | SCADA / historian (down), ERP (up) | MES (down), customer and supplier systems (out) |
| Vendor examples | Ignition, Wonderware, FactoryTalk View, WinCC | Siemens Opcenter, Rockwell FactoryTalk, Aveva MES, Tulip | SAP S/4HANA, Oracle Cloud, MS Dynamics 365, Infor |
How Data Flows Between SCADA, MES, and ERP
Understanding the direction and content of data flows across the three system boundaries is the single most important thing a controls engineer can know about this topic. Most integration failures come not from bad technology choices but from mismatched data models at the boundary.
Downward flow — from ERP through MES to SCADA
- ERP releases a production order specifying part number, quantity, required completion date, allocated material lots, the bill of materials, and the routing (sequence of operations with standard times and work centres).
- MES receives the production order and creates a scheduled job, assigning it to a specific machine or cell based on current capacity and setup state. MES may also download electronic work instructions, quality inspection plans, and material pick lists.
- MES can push recipe parameters or setpoint changes down to SCADA, which in turn writes them to PLCs. This is the path for ISA-88 batch recipes and for automated format changes (switching from Product A to Product B by downloading a new parameter set).
Upward flow — from SCADA through MES to ERP
- SCADA / historian streams process data up to MES — cycle counts, machine states, process variable trends, alarm events, and batch endpoint data. The integration protocol is typically OPC UA Historical Access, SQL queries against the historian, or an MQTT/message-broker pattern.
- MES aggregates and contextualizes that data — attaching process variable values to specific work orders, lots, serial numbers, and operations — then calculates OEE, yield, and scrap.
- MES reports production confirmations up to ERP: actual quantity produced, actual quantity scrapped, actual material lots consumed, actual labor hours per operation, quality inspection results, and non-conformance records. ERP uses these to update inventory, calculate cost variances, and close production orders.
A process historian sits at the boundary between Level 2 and Level 3. It is not MES — it stores and serves raw time-series data. MES queries the historian to pull the process context it needs to populate production records without requiring SCADA to push every tag value individually.
The integration glue
The Level 3 / Level 4 interface (MES ↔ ERP) is standardized by ISA-95 Part 2 using the B2MML XML schema. Most modern implementations replace B2MML with REST APIs or vendor-specific adapters — SAP Plant Connectivity (PCo) and SAP Manufacturing Integration and Intelligence (MII) for SAP shops; Oracle Manufacturing Operations Center for Oracle environments. The technology choice matters less than agreeing on the canonical data model for production orders, BOMs, confirmations, and quality records before implementation begins.
Where the Lines Blur
In practice, the clean boundaries of the ISA-95 pyramid erode at the edges. Understanding where they blur prevents scope creep and vendor overselling.
SCADA with MES features
Modern SCADA platforms, particularly Inductive Automation Ignition with the MES Module and AVEVA System Platform, include production order tracking, OEE dashboards, and basic genealogy. For small, single-product facilities with simple work order models, this can be sufficient. For multi-product, multi-site, regulated, or high-traceability environments (food and beverage, pharmaceuticals, automotive), purpose-built MES software handles the complexity better.
The test: Does your operation require lot genealogy linking consumed raw material lots to finished serial numbers? Does it need to dispatch work across multiple machines, manage operator certifications, or run SPC with automatic hold triggers? If yes, SCADA-with-MES-features will reach its limits quickly.
MES with ERP features
Some MES vendors — especially in specific verticals — have added costing, planning, and even financial modules. Similarly, ERP vendors (SAP Digital Manufacturing, Oracle ME) have acquired or built MES capabilities that run inside the ERP platform or as tightly integrated add-ons. This convergence is real and accelerating under Industry 4.0 pressure.
The test: Can the combined system sustain sub-second production data from 200 machines simultaneously while also running month-end financial close? Integrated platforms work well until data volume and transaction volume conflict with each other. Most mid-to-large manufacturers still run best-of-breed MES and ERP on separate stacks with a defined integration layer.
The IIoT edge layer
Industry 4.0 platforms (PTC ThingWorx, Siemens MindSphere/Industrial IoT, Azure IoT Hub + Azure Digital Twins) sometimes insert a new layer between SCADA and MES, aggregating data from multiple plants into a cloud historian and providing analytics. This does not replace any of the three core systems — it adds an edge aggregation and analytics capability on top of the existing hierarchy. The manufacturing automation guide covers how IIoT fits into modern factory architecture in more detail.
Do You Need All Three?
The practical answer depends on the complexity of your manufacturing operations. Here is how most facilities end up with their system stack:
Small / simple operations
A small manufacturer running a single product line with a handful of operators may operate with SCADA and ERP only — no dedicated MES. SCADA provides process visibility; ERP handles production orders and inventory. The gap — lack of real-time OEE, no lot genealogy, no electronic work instructions — is tolerable at low complexity. Manual processes fill the void.
Mid-size / multi-product operations
Once a facility runs multiple product families, manages regulated lot traceability, or needs to calculate OEE across several machines to drive improvement programs, the gap between SCADA and ERP becomes painful. An MES layer earns its cost in reduced manual data entry, faster root-cause analysis on quality escapes, and defensible audit trails for regulators (FDA, IATF 16949, ISO 22000).
Large / multi-site / regulated operations
Pharmaceutical, medical device, automotive, and aerospace manufacturers typically require all three systems fully integrated. MES is not optional when 21 CFR Part 11 electronic records and signatures are mandatory, or when IATF 16949 requires 100% traceability of automotive components. ERP coordinates production across multiple plants; MES executes and records at each plant; SCADA monitors each production line within each plant.
The right question is not "do we need all three?" but "where does the complexity justify the investment?" Most manufacturers grow into MES — they do not implement all three layers on day one.
For a broader view of the industrial control systems that underpin all three of these software layers, including PLC architecture, network design, and field device selection, see the complete guide. The manufacturing automation guide covers the full automation architecture from field device to enterprise system in a single reference.
Frequently Asked Questions
What is the difference between SCADA, MES, and ERP?
SCADA monitors and controls the physical process in real time — it reads PLC tag data and can write commands back to field devices. MES manages production operations at the order and lot level — it accepts work orders from ERP, tracks execution, and records actual results. ERP manages the business above the factory — demand planning, procurement, finance, and supply chain. Each system occupies a distinct level in the ISA-95 / Purdue Model hierarchy: SCADA at Level 2, MES at Level 3, ERP at Level 4.
Is SCADA part of MES?
No. SCADA and MES are separate systems at adjacent levels of the ISA-95 hierarchy. SCADA is at Level 2 and communicates directly with PLCs and field devices. MES is at Level 3 and has no direct connection to field hardware — it consumes aggregated data from SCADA and the process historian. Some SCADA platforms (Ignition MES Module, AVEVA System Platform) include basic MES features, but a full MES and a SCADA system perform fundamentally different functions and cannot replace each other for complex manufacturing operations.
How do SCADA, MES, and ERP connect?
Data flows upward from SCADA to MES and from MES to ERP, and downward from ERP through MES to SCADA. SCADA sends time-series process data and events to MES via OPC UA Historical Access, SQL historian queries, or MQTT. MES contextualizes that data against production orders and reports production confirmations, goods issues, quality results, and labor hours up to ERP via ISA-95 XML messages, REST APIs, or vendor adapters such as SAP Plant Connectivity.
Do you need all three?
Not always at every stage of growth. Simple, single-product operations can run with SCADA and ERP alone, accepting manual processes in the gap. Multi-product, regulated, or high-traceability manufacturers need MES to close the loop between real-time process control and business planning. The decision point is usually lot genealogy requirements, OEE improvement programs, regulatory compliance (FDA 21 CFR Part 11, IATF 16949), or the cost of manual data entry between SCADA historian exports and ERP production confirmations.
