MES vs SCADA: Differences and When You Need Each One

A SCADA supervises and controls the process in real time: it watches signals, raises alarms and acts on machines. An MES manages production as a business: work orders, traceability, quality and performance. They are not alternatives but complementary layers: the SCADA looks at seconds and machines; the MES looks at shifts, batches and orders. Many plants need both, but rarely at the same time.

Two distinct layers of the same pyramid

MES and SCADA get confused so often because both "show screens with plant data". But in the classic automation pyramid model (ISA-95) they occupy different levels. The SCADA lives at level 2, right next to the process: its unit of work is the signal and its time horizon is seconds. The MES lives at level 3, between the process and the ERP: its unit of work is the work order and its horizon is shifts, batches and orders. The right question is not which of the two to choose, but what problem you have: a process problem (controlling and supervising what is happening right now) or a production management problem (knowing what was made, with what materials, when and at what performance).

What a SCADA does (and does not do)

A SCADA (Supervisory Control And Data Acquisition) connects to PLCs and field equipment for three functions: visualising the process on real-time mimic screens, alarming when a variable goes out of range and acting on the process (starting, stopping, changing setpoints) from the control room or the operator's station. It usually includes a process signal historian and trending tools.

What a SCADA does not do well is production management: it does not know which work order is running, it does not trace batches or raw materials, it does not manage quality or calculate an OEE with downtime causes properly assigned. It can be forced into that role (and many plants have forced it, with scripts and custom screens), but the result is fragile and expensive to maintain. The SCADA is a piece of the control layer, close to PLC connectivity and plant instrumentation.

What an MES does (and does not do)

An MES (Manufacturing Execution System) manages the execution of production: it receives work orders (normally from the ERP), sequences them and releases them to the shop floor, records consumption and output per batch, traces materials from origin to finished product, manages quality checks and self-inspections, and logs stoppages and loss causes to calculate indicators such as OEE (covered in detail in the OEE guide). It is the natural bridge between the ERP, which thinks in orders and costs, and the shop floor, which thinks in machines and shifts: that is why MES projects almost always go hand in hand with ERP integration.

What an MES does not do is real-time control: it does not replace the SCADA or the PLCs, it does not manage process alarms at second-level latencies, and it does not act on valves or drives. It needs plant data (which is why an MES without good connectivity ends up fed by hand, its most common failure mode), but it consumes that data at the pace of production events, not of a control loop.

Comparison table: MES versus SCADA

Criterion	SCADA	MES
ISA-95 level	Level 2 (supervision and control)	Level 3 (operations management)
Unit of work	Signal, alarm, setpoint	Work order, batch, production report
Time horizon	Seconds and minutes (real time)	Shifts, days, complete batches
Typical users	Operators and maintenance, in the control room or at the machine	Supervisors, planning, quality, operations management
Questions it answers	What is happening right now? What triggered the alarm?	What was made, with which materials, at what performance and why was time lost?
Acts on the process	Yes: setpoints, start/stop, manual control	Not directly: it instructs and records, it does not control
Batch traceability	No (outside its scope)	Yes: a core function
Systems it integrates with	PLCs, instrumentation, field equipment	ERP, SCADA/shop-floor data capture, quality, warehouse
Cost of an outage	Loss of immediate supervision and control	Loss of records and traceability; the process keeps running

Signs that you need each one

You need a SCADA (or a better one) if:

Operators supervise the process machine by machine, with no overall view and no centralised alarm management.
There are critical process variables (temperatures, pressures, levels) that nobody monitors systematically.
Acting on the process means physically walking to each control cabinet.

You need an MES if:

Production reports are filled in by hand and typed into the ERP afterwards, hours late and with errors.
Reconstructing the traceability of a batch after a complaint takes days of digging through paperwork.
OEE is calculated in spreadsheets, without reliable downtime causes.
Planning releases orders with no visibility of what is really happening on the shop floor.

Use cases by company size

Workshop or small plant

With few machines and simple discrete processes, a full SCADA is usually overkill: supervision is handled by the machines' own HMIs plus a light data-capture layer. The need that appears first is the management one: stopping production against paper. There the answer is not always a full MES; digital production reports well integrated with the ERP are often enough, growing from there.

Mid-size plant

This is where the MES versus SCADA question comes up most strongly, and where the answer is usually "both, in phases". If the process is continuous or critical (chemicals, food with cooking stages, surface treatment), the SCADA comes first: without reliable supervision there is no foundation. If the process is discrete and the pain sits in traceability, production reporting and performance, the MES delivers value sooner. In both cases, the investment that multiplies the value of the two is the connectivity layer: having machines, SCADA and MES share the same plant data instead of each capturing it on its own.

Multi-plant industrial group

At this scale the SCADA is a local matter for each plant (each process has its own), while the MES tends to become corporate: a common model of orders, traceability and indicators that allows plants to be compared and consolidated. The challenge stops being functional and becomes one of architecture and integration: how to connect each plant's heterogeneous control systems to a homogeneous production data model, which is the domain of OT/IT integration.

In what order to implement them

When both are needed, the sensible order is almost always bottom-up: first secure control and data capture (PLCs, SCADA or lightweight capture, connectivity), then build the management layer on top (MES, ERP integration). An MES fed by hand because the connectivity never existed becomes a system of digital bureaucracy: operators type what they used to write. The reverse sequence, starting by making sure plant data flows automatically and reliably, means every subsequent layer rests on solid foundations. It is the same principle we apply when digitalising a factory step by step.

Frequently asked questions about MES and SCADA

Can an MES replace a SCADA?

No. The SCADA supervises and acts on the process in real time, with second-level latencies and a direct connection to the PLCs; the MES manages orders, batches, quality and performance at the pace of production events. They are different levels of the automation pyramid (2 and 3 in ISA-95) and they complement each other: the MES consumes data that the control layer captures.

Which comes first, the MES or the SCADA?

As a general rule, bottom-up: first the control and data-capture layer (PLCs, SCADA where the process demands it, plant connectivity) and then the MES on that foundation. An MES without automatic capture ends up fed by hand and loses much of its value. If the process is discrete and simple, lightweight capture may be enough instead of a full SCADA before the MES.

Can the SCADA and the MES share the same plant data?

Yes, and it is the recommended architecture: instead of each system connecting to the machines on its own, a common connectivity layer captures the signals once and serves them to SCADA, MES, historian and analytics. It reduces load on the PLCs, avoids discrepancies between systems and means adding a new consumer does not touch the plant.

And where does the ERP fit into all this?

The ERP occupies level 4: orders, purchasing, costs and planning at business level. The MES is its counterpart on the shop floor: it receives work orders from the ERP and returns real output, consumption and statuses. Without an MES (or a lightweight equivalent), that conversation happens by hand with paper reports; with it, the ERP works with real, current plant data.

If you are weighing up a move towards either layer, at Captia Connect we build the foundation both of them need: PLC connectivity, OT/IT integration and ERP integration. And when MES and SCADA have to share the same plant data, that common foundation is an industrial data platform.