Key takeaways
Short answer: SCADA is the control layer: live monitoring and control of machines and processes. MES is the manufacturing-operations layer above it: dispatching production orders, tracking what was made, genealogy, and performance like OEE. SCADA asks "is the process in control?"; MES asks "are we executing the plan well?" They integrate rather than compete. See also manufacturing execution system vs erp shop floor.
SCADA lives at the control layer, closest to the machine. It monitors and controls equipment in real time, raises alarms, and gives operators the screens and setpoints to keep the process safe and stable second by second. Its world is the present state of the equipment.
MES sits a layer up, between SCADA and ERP. It manages execution of the plan: which order is running, what was actually produced, the genealogy and traceability of each unit, and performance metrics like OEE. Its world is the manufacturing operation, not just the machine.
A reactor's SCADA holds the temperature at setpoint and alarms if it drifts — pure control. The MES knows that this reactor run is work order 4471 for customer X, ties the SCADA temperature trace to that batch's genealogy, records the yield and OEE, and releases the next order when this one completes. Ask SCADA "how did order 4471 perform?" and it cannot answer — it has no concept of an order. Ask MES "is the temperature in control right now?" and it defers to SCADA. Each is authoritative in its own layer.
SCADA feeds MES the live signals; MES gives those signals business context — which order, which product, how it performed. SCADA without MES is blind to the plan; MES without SCADA has no real-time data. The integration is vertical, not competitive.
OEE is an MES-layer metric built on SCADA-layer data. The machine signals come from control; the loss classification and order context come from execution management. That is why a pure SCADA system shows live values but not a decomposed OEE loss tree.
1. Running production management in SCADA. It has no concept of orders, genealogy or OEE.
2. Expecting MES to do real-time control. Latency makes it unsuitable for closed-loop control.
3. No integration between the layers. Live data and business context never meet.
4. Buying one expecting it to do both. They are complementary layers, not substitutes.
OEE needs both: SCADA-grade signals for the raw events and MES-grade context to turn them into Availability, Performance and Quality by order and asset. A modern OEE platform effectively provides the MES execution context on top of control-layer data.
Fabrico provides the execution-layer context — orders, OEE and genealogy — on top of machine signals, without a heavyweight legacy MES. Book a demo to see control data turned into operational insight.
Yes — MES is the operations layer above the SCADA control layer.
It provides live values, but full OEE needs the order and loss context the MES layer adds.
Yes — SCADA feeds data up to MES, which adds business context.
Above MES, for planning and financial transactions.
Most plants do — SCADA controls, MES executes, ERP plans — though one platform can cover execution and OEE.
Programați o întâlnire individuală cu experții noștri sau înscrieți-vă direct în planul nostru gratuit.
Nu este nevoie de card de credit!
Login
Blog
