SCADA vs MES: Two Different Questions About the Same Machines
The SCADA vs MES comparison confuses people because both systems attach to the same machines, sometimes to the same screen. The cleanest way to separate them is to listen to the questions each one answers. Stand in front of the filling machine at nine in the morning. SCADA answers: what is this machine doing right now? Running, fill weight 498 g against a 500 g target, no active alarms. A MES answers: which order is this machine making, which material lot is going into it, who has been running it, is the order on schedule, and what has the scrap cost so far? Two different questions about one machine.
What SCADA Answers: What Is Happening Right Now
SCADA is the present tense of the factory. It watches station states (running, idle, fault, starved, blocked), live sensor values, and alarms. Done well, it also does the bookkeeping that makes those states trustworthy: a station state machine so a running state means something consistent, and downtime events generated automatically with a debounce window, so a genuine jam becomes an event while a sensor flicker does not. What SCADA data deliberately lacks is context. The tags do not know that this hour of production belongs to order PO-4471.
What a MES Answers: What It Means for the Order
A manufacturing execution system reads the same machine activity as production. Not a cycle count: 340 of 500 units done on PO-4471. Not a material flow: lot RM-8842 consumed, which matters the day someone asks where that lot went. Not just an operator badge: the shift that touched the order last. And not a bare downtime list: the order that is 45 minutes behind plan, and the scrap percentage eating its margin. If you want the full picture of that layer, start with what a MES is.
SCADA vs MES: Where the Line Sits
Here is the dividing line we use: if the answer makes no sense without knowing what an order is, it belongs to the MES. Machine state, cycle time, fill weight, alarm history: all order-agnostic, all SCADA territory. Quantity good versus quantity planned, yield by lot, schedule adherence, scrap cost by order: all order-keyed, all MES territory. A quick test is to delete the order number from the screen. Whatever is still meaningful is SCADA.
Why the Two Need Each Other
SCADA without a MES produces beautiful dashboards with no cost story. You can see that line 2 lost three hours to faults this month, but not which orders paid for those hours. A MES without SCADA is the mirror image: an order book where every number was typed by a human, hours after the machine already knew. Factories usually feel the SCADA side first, which is why we recommend the machine-data layer before the MES for most plants, a sequence we explain in OEE before MES.
The Practical Integration: Two Flows
The integration between the two is unglamorous and stable: states and counts flow up, orders and confirmations flow down.
- Up: station states, cycle counts, downtime events with reasons, and alarms stream from the machines into the MES, each event keyed to the station that produced it.
- Down: the MES dispatches the work order to the terminal at the station, and the operator's confirmations (starts, quantities, pauses, completions) come back through the same pipe.
It is the same pattern as the ERP handoff described in MES vs ERP, one layer down. Voltrus ships the machine-data layer first: a gateway, keyed SCADA ingest, station state machines, automatic downtime events with debounce, and hourly OEE rollups per station and line. The MES then reads from that layer instead of installing one. If your factory already runs a SCADA or OEE layer, you have finished the hardest part of a MES project before the project started.
Frequently Asked Questions
Can SCADA do what a MES does?
You can add order fields to SCADA screens, and many plants do. It works until someone has to recall which lot went into which order, or until two orders run the same machine on the same day. At that point the order context needs a system of record, and a tag database is not one.
We already have SCADA and OEE dashboards. Do we still need a MES?
If production truth still gets re-typed into spreadsheets to answer where an order stands, yes. The upside: your project starts from data that already flows, the head start described above.
Is OEE a SCADA feature or a MES feature?
Both, in sequence. The raw data comes from the machine layer: a station down 8 of 60 planned minutes is 86.7% availability, and 640 units against an ideal pace of 1,000 per hour is 64% performance. The rollup becomes trustworthy when it is computed per station and line with performance capped at 100%. Order-level OEE needs the MES context on top.
What about historians and data lakes?
Keep them. A historian stores tags; a MES consumes events and answers order questions. The MES subscribes to what it needs and leaves the raw history where it is.
Start With the Machine-Data Layer
Voltrus MES is live: one line to start, SCADA-grade machine data from day one. See what ships today.
See Voltrus MES