Operational guide · For Plant Managers

MES vs SCADA: what each one really is, and how to decide without being sold smoke.

Confusing MES and SCADA is the first trap in a plant digitization project. One vendor shows dashboards and calls it SCADA. Another shows nearly identical screens and calls it MES. They are different things, and on the shop floor they need to talk to each other. This guide explains the difference in operational terms — no glossary, no smoke — and gives you the concrete criteria to choose when to start from SCADA, when to start from MES, and why in 2026 the right answer is almost always "both, on a single platform".

Published
9 min read
1 · The definitions

SCADA, MES, PLC, WMS: what they actually do every day.

All these names live inside ISA-95, a model that splits the plant into levels — field, control, production, business. In real life nobody talks in levels. They talk in problems: who watches alarms in real time, who tracks lots, who schedules production, who runs the warehouse. Those problems map to different tools, and understanding who does what is the first step.

The definitions that actually matter on the shop floor — not the white-paper kind:

  • PLC (Programmable Logic Controller)

    The layer that talks to sensors and actuators — opens valves, stops conveyors, reads encoders. Cycle times in single-digit milliseconds. The PLC is the truth on the field: if the PLC says the valve is closed, it's closed. Typical brands: Siemens S7-1500, Rockwell Logix, Beckhoff, Omron.

  • SCADA (Supervisory Control And Data Acquisition)

    The layer that supervises one or more PLCs in real time. Shows dashboards, alarms, andon, process historians. Lets humans send commands to the field through a UI — start, stop, recipe load, alarm reset. SCADA is the eyes of the shift lead.

  • MES (Manufacturing Execution System)

    The layer that executes the production order: schedules it on the line, tracks it lot-by-lot, counts good units and scrap, computes OEE, talks to the ERP. The MES is the memory of what was produced, by whom, on which machine, with which recipe.

  • WMS (Warehouse Management System)

    The layer that runs the warehouse: intake, locations, picking, FEFO/FIFO, shipping. In F&B and pharmaceutical, critical for shelf-life and downstream traceability.

The vendor selling you "SCADA that does everything" is probably selling you SCADA with a few bolt-on MES tables. Not automatically wrong — wrong when you pay for it as MES.
2 · In practice

The four differences you actually feel on the floor.

On the brochure SCADA and MES look like the same product: both show dashboards, both handle alarms, both talk to the PLC. In production the difference is felt on four axes:

  • Time horizon

    SCADA lives in the present: "what is the machine doing right now". MES lives in history and the planned future: "what did we produce yesterday, what do we have to produce tomorrow, what was the scrap cause on shift 2".

  • Data granularity

    SCADA logs individual tags (pressure, temperature, speed) at high frequency. MES logs production events (unit X completed, lot Y started, recipe Z loaded) at event frequency.

  • Audience

    SCADA serves operator and shift lead. MES serves production planning, quality, plant director. Different jobs with different questions — they need different interfaces, not the same dashboard repainted.

  • Enterprise integration

    SCADA typically doesn't talk to ERP. MES does: receives orders, returns actuals, syncs recipe master data, reconciles inventory. Without MES, ERP lives in a parallel world to what happens on the line — the number-one source of misalignment.

3 · To avoid

Three mistakes we see on the floor — always the same ones.

Over the past few years we have walked into dozens of plants where choices were made under vendor pressure or audit deadline. Three patterns keep repeating:

  • "SCADA is enough, we'll track lots on Excel"

    Works until the ISO 22000 or IFS auditor asks for forward/backward traceability in under 4 hours. At that point Excel is a legal problem, not just an inefficiency. MES isn't a nice-to-have upgrade: it's the minimum viable layer for any modern supply-chain audit.

  • "Let's buy enterprise MES first, then look at SCADA"

    MES without a reactive SCADA means the operator doesn't see alarms in real time and has no field control. The result: MES receives slow, dirty, paper-mediated data. The dashboard numbers look clean but they are disconnected from line reality.

  • "We'll build SCADA in-house with library X and buy the MES"

    Two disconnected stacks that will grow apart over years with two different roadmaps. The first divergence usually hits at the first product format change: SCADA updates recipes in one place, MES expects them from another. Three months to glue it back together.

4 · Decision

How to choose without letting the vendor of the day drive.

The question is not "SCADA or MES". It is "which next problem costs me the most, and which tool fixes it". Three concrete scenarios:

  • Modern automation, zero production visibility

    PLCs are there, machines run, but the production manager can't quote the main line's OEE. Start with SCADA + MES together, lightweight, on a single platform — a year of operation gives you data for the next investment decisions.

  • Legacy SCADA, audit/traceability deadline approaching

    WinCC, Movicon, Zenon, FactoryTalk in production for years, no structured traceability. Either add MES as a layer on top of existing SCADA, or — recommended — replace both with a unified platform if SCADA is 5+ years old.

  • Building a brand-new line

    Never start with two separate vendors for SCADA and MES. Ever. New line = unified platform, single source of truth, one team integrating PLCs, one recipe logic. The savings in the first 12 months are three times the software cost.

5 · ARIA

How ARIA puts SCADA and MES on a single platform.

ARIA is the MES/SCADA platform IOMA builds and installs in plants. SCADA and MES are not two modules with two databases: they are two views on the same real-time dataset, with one user model, one PLC integration, one recipe. The shift lead sees the SCADA dashboard; the production manager opens the same app and sees actuals, OEE, lot traceability.

The key message: ARIA eliminates the entire category of "who is authoritative, SCADA or MES?" questions. It's always the same system. And when you add Warehouse or Mobile, the stack stays as one.

FAQ

Frequently asked questions about MES and SCADA

Questions Plant Managers ask before starting an MES/SCADA project.

Can I have an MES without already having SCADA?

Yes, but it almost always means SCADA already exists — even if it's not called that. A PLC with an HMI is effectively a tiny SCADA. Having an MES with no real-time field visibility means the MES receives slow, paper-mediated data: useful for reports, useless for floor decisions.

Are MES and ERP the same thing?

No. ERP runs customer orders, suppliers, invoicing, master data, accounting — the commercial life of the company. MES runs the physical execution of an order on the line — who makes it, with which recipe, with what raw-material lot. ERP and MES exchange production orders (ERP → MES) and actuals (MES → ERP).

What does "traceability" actually mean from an MES point of view?

Traceability is the ability to answer in minutes questions like: "starting from raw-material lot X, where did the finished products end up?" (forward), "customer lot Y came from which raw material?" (backward), "who was the operator on machine Z on March 15 at 14:30?". A serious MES answers all three with parameterised queries, not with a shift lead digging through paper.

Roughly, what does SCADA + MES cost?

Typical range for a mid-size plant in Italy: from €30k for a single line with ARIA Lite + basic Warehouse, up to €250-400k for a multi-line plant with enterprise MES, ERP integration, OT cybersecurity, recipe and format change. Software is usually 30-40% of the total; the rest is PLC integration, server hardware, training, validation.

How long until we're live in production?

For a single line with existing automation: 8-14 weeks from kick-off to go-live. For a multi-line plant with an audit as the deadline: 4-9 months in phases (one line at a time). Beware of anyone promising "MES in 2 weeks": that means style sheets on top of an Excel.

Do I have to change my PLCs to install a modern MES?

No. A serious MES integrates with the PLCs you have — Siemens S7-300/400/1500, Rockwell Logix, Beckhoff, Schneider Modicon, Omron — via OPC UA, Modbus, or native protocols. The ARIA stack interfaces even with year-2000 PLCs still in production.

Go deeper

Related pages the Plant Manager usually opens after this guide.

ARIA · MES/SCADA platform

How ARIA brings SCADA, MES, Warehouse, and Mobile onto a single platform — already in production on multi-station lines.

Services · PLC programming

The layer underneath every MES and SCADA. Siemens S7-1500, motion control, safety, documented diagnostics.

Services · OT cybersecurity

MES + SCADA mean line data on the network: it needs segmentation, hardening, IEC 62443. For NIS2-covered operators, already mandatory.

Let's talk

Got a project in mind?

Tell us about your idea or your operational challenge. Our team is ready to listen and propose the right technology fit.

Let's talk about your project