SCADA vs MES: What Each Does and Which Your Plant Needs

Key takeaways

• SCADA lets operators see and steer the process right now. It answers: what is this machine doing, and can I step in?
• MES runs the production order and keeps its record. It answers: are we making the right product, the right way, and from what?
• In the ISA-95 model, SCADA sits at Level 2 (supervisory control) and MES at Level 3 (operations management).
• Choose by the problem, not the label.
• If your problem is lost hours, neither has to come first. A focused OEE platform can turn machine signals into availability, performance and quality by line and shift.

Short answer: SCADA is the supervisory layer: it reads PLCs, shows live values, raises alarms and lets operators change setpoints. MES is the operations layer above it: it releases orders, enforces the routing and recipe, and records what was made and from which materials.

Which one does your plant need? Operators can't see or steer the process: SCADA. Orders, lots or steps go wrong: MES. Lines lose hours and nobody can say why: neither first, start with OEE.

They overlap at the data layer but answer different questions. A plant can end up with both, each for its own reason. For the wider context, see our guide to OEE explained.

What SCADA actually does

SCADA is the supervisory layer that sits directly on top of your PLCs and field devices.

It polls tags, temperatures, speeds, pressures, motor states, on a fast cycle, renders them on operator screens, raises and logs alarms, and lets operators change setpoints or acknowledge faults.

Its job is supervision in the moment, measured in seconds. The fast control loops run in the PLC below it. SCADA does not know what a work order is; it knows tag 4101 just dropped below its limit.

That tight scope is what makes it good at supervision, and why it cannot, on its own, tell you whether the shift hit its target.

What MES actually does

MES operates one level up, in the language of production rather than signals. It receives orders from ERP, releases them to the floor, enforces the correct routing and recipe, and blocks a step if the prerequisites are not met.

As parts move, it records genealogy, which batch, which materials, which operator, which machine, so a defect can be traced months later. It also rolls raw events into operational reporting: counts, scrap, and downtime by reason.

Where SCADA sees a stopped motor, MES sees order 8842 paused for a changeover on Line 3. That order context is what turns telemetry into decisions.

SCADA vs MES side by side

This is the typical split. Some products span both, so ask what a product records, not what it is called.

Where they sit: the ISA-95 stack

The ISA-95 model is the clearest way to keep the two straight. Level 1 is sensors and actuators. Level 2 is SCADA: supervisory monitoring and control, above the PLCs.

Level 3 is MES, manufacturing operations management: dispatching, tracking, quality, and performance. Level 4 is ERP, business planning and logistics. SCADA and MES are neighbours, not competitors: SCADA hands real-time data up, MES hands orders and constraints down.

Problems usually start when a plant tries to make SCADA do Level 3 work with custom scripts. For how the data itself moves and is stored, see unified namespace vs point-to-point integration and data historian vs data lake.

A worked example: one stop, two systems

Example data: a filler stops for 12 minutes. SCADA captures it instantly: motor 3 faulted at 09:14:07, alarm raised, operator acknowledged at 09:14:40. That is the control truth, to the second.

MES adds the production truth: the stop happened during order 8842, it was logged as an unplanned mechanical failure, it cost 1,140 units against the run rate, and it pushed the order past the shift. Each view answers a different question.

SCADA tells you what failed; MES tells you what it cost and where it lands in the plan. An OEE layer then folds that single event into the day's availability loss so it is comparable across lines and weeks.

Which layer does this plant need?

Take your last bad week. Find the problem that cost the most, then read across.

Three plants, three answers

• Tanks, valves and pumps across a site, run from a control room. Start with SCADA, or a DCS if your process uses one. Add an MES when batch records become the problem.
• A food plant with customer audits and lot records on paper. Its panels already work, so an MES is the next spend. Check first if your ERP's lot tracking can do it.
• Packaging or metal lines with stand-alone machines. The ERP runs orders well enough, and each machine has its own panel. Neither comes first: measure the bottleneck line, then decide.

For that third plant, read OEE software vs SCADA. If your question includes the controllers too, see PLC vs SCADA vs MES.

If you only need to watch and steer the process, SCADA may be enough.

The moment you need order tracking, traceability or enforced routing, that is MES territory, and bolting it onto SCADA with scripts tends to age badly.

If you already run SCADA, a practical sequence is: keep it for control, add an OEE layer (a light MES) to see where the hours go, and adopt full MES capabilities as traceability and compliance demands grow.

You do not have to buy the entire stack on day one to start measuring losses.

Common mistakes

• Forcing SCADA to be an MES. Custom scripts that fake order tracking become unmaintainable and trap your data.
• Buying an MES to find lost hours. If orders and lots are not your problem, you pay for a project around them. Check first that the MES gets stops from a machine signal.
• Expecting ERP to see the floor. ERP bookings show what was confirmed, not the stops between bookings.
• Confusing dashboards with control. A nice SCADA HMI is not the same as performance analysis; live values are not trends.
• Ignoring data context. Counting stops without order, shift, and reason context produces numbers nobody trusts.

How it shows up in OEE

SCADA and MES can each feed OEE, but they contribute different pieces. SCADA can supply the event stream, run and stop states, speeds and fault codes, that underpins availability and performance.

MES can supply the order, count, and quality context that lets you attribute those losses to the six big losses. Neither is required: an OEE system can read the PLC or a sensor directly, and order data can come from the ERP.

So ask where each stop comes from, a machine signal or someone typing it, and whether short stops show up. That decides if the number can be trusted.

How Fabrico fits

Fabrico is a cloud-based OEE and light MES platform. It does not replace SCADA for supervising and steering machines, and it is not a full MES.

Machine data comes from the PLC, or from a Fabrico IoT device with external sensors on older machines. Stops come from that signal. The operator adds the reason on a tablet or phone, and OEE and downtime show per line and shift.

Routings, BOMs, dispatching and genealogy stay in your ERP. So if you need enforced routing or lot records at the station, buy a full MES instead. Maintenance is built in, as a complement.

Installing the devices and connecting the machines takes about one month. Full rollout across the lines you choose takes 3 to 4 months.

If lost hours are the problem you found above, it can be a first step. Book a demo or Contact us to go through how it fits next to your control stack.

Related reading

• Unified namespace vs point-to-point integration
• Data historian vs data lake
• Digital work instructions vs paper SOPs
• OAE vs OEE

Frequently asked questions

Is MES the same as SCADA?

No. SCADA is a real-time supervisory control and data-acquisition layer that monitors equipment and lets operators steer it. MES is an operations layer that manages production orders, routing, traceability, and performance. They do different jobs.

Can SCADA replace an MES?

Not well. SCADA can be scripted to imitate some MES functions, but order tracking, genealogy, and enforced routing are outside its design, and those custom scripts tend to become fragile and hard to maintain.

Do I need both SCADA and MES?

Not always. You need SCADA if operators must supervise and steer the process, and MES if you must control and prove how orders are made. Some plants need both. If your main loss is stopped time, you can start with a focused OEE layer and decide later.

We already have SCADA. What does an MES add?

Orders, steps and lot records. SCADA can tell you a motor stopped; an MES ties that time to the order and keeps the record of what was made.

Can SCADA give us OEE?

It can hold the raw events, and some teams script reports on top. Check who maintains them, and how operators add stop reasons.

Is Fabrico SCADA or MES?

Closer to MES. Fabrico is a cloud-based OEE and light MES platform: machine data, production monitoring, and OEE and downtime analytics. It does not replace SCADA or a full MES.

Where do SCADA and MES sit in ISA-95?

SCADA is Level 2 (supervisory control) and MES is Level 3 (manufacturing operations management), with sensors at Level 1 and ERP at Level 4.

How do SCADA and MES relate to OEE?

SCADA can provide the machine events behind availability and performance; MES can provide the order, count, and quality context. An OEE system can also read the PLC or a sensor directly, with neither in place.

Next step

Bring your last bad week and the list of machines on one line to the demo.