MES vs SCADA: ISA-95 Layers, Differences & Integration

TL;DR: MES and SCADA operate on different ISA-95 layers and serve fundamentally different purposes. SCADA (Level 2) monitors and controls physical processes in real time — pressures, temperatures, valve states. MES (Level 3) manages production execution — orders, OEE, quality, traceability, shift performance. SCADA is the eyes of the factory. MES is the brain. SCADA tells you "Machine X stopped." MES tells you "Machine X stopped during Order 4711, Product Y, Shift B — and this is the 3rd time this week for the same alarm code." Neither replaces the other. The question is how tightly they're integrated.

Table of contents

1. What is the core difference between MES and SCADA?
2. Where do MES and SCADA sit in the ISA-95 model?
3. Functional comparison: MES vs SCADA
4. What can SCADA not do that MES does?
5. How does MES-SCADA integration work?
6. When do you need MES, when SCADA, when both?
7. FAQ

What is the core difference between MES and SCADA?

The confusion between MES and SCADA arises because both work with real-time data from the shop floor. The distinction lies in scope, purpose, and data context:

• SCADA (Supervisory Control and Data Acquisition) monitors and controls machine-level processes. It reads sensor signals, displays process values, triggers alarms, and allows operators to intervene in real time. SCADA operates at the physics level: temperature, pressure, flow rate, valve position.
• MES (Manufacturing Execution System) manages production execution. It contextualizes raw signals into business-relevant information: Which order is running? What's the OEE? Why did the machine stop? How does Shift A compare to Shift B? MES connects the machine world to the order world.

The simplest distinction: SCADA shows what happens at the machine. MES explains why it happens and what it means for production performance.

Where do MES and SCADA sit in the ISA-95 model?

The ISA-95 standard defines 5 levels of manufacturing systems. MES and SCADA occupy adjacent but distinct layers:

SCADA sits directly above the automation layer — it reads and controls physical processes. MES sits above SCADA — it manages production operations. The data flows upward: sensors → PLCs → SCADA → MES → ERP. The context flows downward: orders → schedules → machine assignments → setpoints.

Functional comparison: MES vs SCADA

What can SCADA not do that MES does?

SCADA was designed for process monitoring and control — not for production management. These are not limitations, they are design boundaries:

The practical consequence: Manufacturers who rely solely on SCADA for production management see the machine. They don't see the production. SCADA tells them "Line 3 ran at 92 % uptime." MES tells them "Line 3 ran Order 4711 at 68 % OEE because 14 % was lost to changeovers and 8 % to micro-stops under 30 seconds — and this is 12 % worse than last week on the same product."

How does MES-SCADA integration work?

In modern plants, MES and SCADA connect through bidirectional interfaces. The data flows in both directions:

Interface protocols: OPC-UA (most common for modern PLCs/SCADA), MQTT (for IoT edge devices), REST API (for cloud integration), digital I/O (for brownfield equipment without network connectivity).

How SYMESTIC connects to SCADA environments: SYMESTIC's Cloud MES connects directly to SCADA and PLC layers via OPC-UA, MQTT, or digital I/O. At Brita, modern OPC-UA line controllers feed alarm data directly into SYMESTIC. At Neoperl, SPS-based alarm capture provides automatic downtime categorization without operator input. At Carcoustics (500+ machines, 7 countries), IXON IoT gateways bridge the gap between legacy SCADA environments and the cloud MES via MQTT to Azure. In all cases, SCADA remains the process control layer — SYMESTIC adds the production management layer on top.

A real-world integration example: A SCADA alarm detects a pressure spike on a stamping press. SCADA displays the alarm and logs it. That's where SCADA's job ends. SYMESTIC receives the same signal, maps it to the current production order, the product variant, the shift, and the operator. It checks: has this alarm occurred before on this product? (Yes — 7 times in the last 30 days.) Is it correlated with quality defects? (Yes — scrap rate increases 3× within 15 minutes after this alarm.) MES triggers a notification, updates the downtime Pareto, and provides the data for root-cause analysis in the next improvement meeting.

When do you need MES, when SCADA, when both?

The key insight for discrete manufacturers: In discrete manufacturing (automotive, metal processing, plastics, packaging), SCADA is often invisible — it's embedded in the PLC/HMI layer of each machine. There is no separate SCADA system to "integrate with." Instead, the MES connects directly to PLCs via OPC-UA or digital I/O. The MES effectively absorbs the SCADA role for production management purposes. This is why SYMESTIC customers like Meleghy, Klocke, and Neoperl don't have a separate SCADA project — the MES connects directly to the machine layer.

FAQ

Does MES replace SCADA?
No. MES and SCADA serve different purposes on different ISA-95 layers. SCADA controls physical processes (Level 2). MES manages production execution (Level 3). In discrete manufacturing, MES often connects directly to PLCs, making a separate SCADA system unnecessary — but in process industries, SCADA remains essential for safety and process control.

Can SCADA calculate OEE?
Not meaningfully. OEE requires order context (which product at what target cycle time), quality data (good parts vs. scrap), and standardized downtime categorization. SCADA sees signals, not orders. An OEE calculated from SCADA alone would lack the context needed for actionable improvement.

Do I need SCADA if I have MES?
In process industries (chemical, pharma, food) — yes, for safety-critical process control. In discrete manufacturing — often no. The MES connects directly to PLCs and captures the production-relevant signals. SCADA functionality (alarming, visualization) is either embedded in the machine HMI or handled by the MES process data module.

How does MES connect to existing SCADA systems?
Via OPC-UA (most common), MQTT, or REST API. SCADA exposes process data as tags/variables. MES subscribes to relevant tags and maps them to production context (order, product, shift). The integration is additive — MES reads from SCADA without disrupting process control.

What about DCS (Distributed Control Systems)?
DCS is functionally similar to SCADA but optimized for continuous processes (refineries, chemical plants). For the MES vs. SCADA comparison, DCS occupies the same ISA-95 Level 2 position. MES sits above DCS just as it sits above SCADA.

The key takeaway: SCADA is the eyes of the factory — it monitors physical processes in real time. MES is the brain — it interprets what happens, connects it to orders and KPIs, and enables optimization. In discrete manufacturing, MES often connects directly to PLCs, making a separate SCADA layer unnecessary. In process industries, both are essential. The integration between them — raw signals flowing up, production context flowing down — is what creates the digital nervous system of modern manufacturing.

→ What is MES? · → MES vs. ERP · → MES Software Compared · → Cloud MES vs. On-Premise · → Machine Data Collection · → OEE