Key takeaways
Short answer: SCADA is a real-time control and telemetry layer that polls PLCs, displays live values, and lets operators acknowledge alarms or change setpoints. MES is the operations layer above it: it releases work orders, enforces routing and recipe, captures what was built and from which materials, and reports throughput and quality. They overlap at the data layer but answer different questions, which is why a plant usually needs both rather than one or the other. For the wider context, see our guide to OEE for manufacturing.
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 control and visibility in the moment, measured in milliseconds to seconds. SCADA does not know what a work order is; it knows tag 4101 just dropped below its limit. That tight, real-time scope is what makes it reliable for running equipment, and exactly why it cannot, on its own, tell you whether the shift hit its target.
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.
The ISA-95 model is the clearest way to keep the two straight. Level 1 is sensors and actuators. Level 2 is SCADA and the control system — supervisory monitoring and control. 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, or expects ERP to manage the floor directly. For how the data itself moves and is stored, see unified namespace vs point-to-point integration and data historian vs data lake.
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. Neither view is complete alone. 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.
The honest framing is that SCADA and MES are rarely an either/or. If you only need to run and monitor equipment safely, SCADA may be enough. The moment you need order tracking, traceability, enforced routing, or reliable performance reporting across lines, that is MES territory, and bolting it onto SCADA with scripts tends to age badly. A practical sequence for many plants: keep SCADA for control, add a lightweight performance and OEE layer to get visibility fast, 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.
SCADA and MES both feed OEE, but they contribute different pieces. SCADA supplies the high-resolution event stream — run/stop states, speeds, and fault codes — that underpins availability and performance. MES supplies the order, count, and quality context that makes those losses meaningful and lets you attribute them to the six big losses. Without the SCADA layer you lack precision; without the MES context you lack meaning. Get both and your OEE stops being a number on a poster and becomes a list of specific, addressable losses.
Fabrico is not trying to replace your SCADA or your MES. It sits alongside them as a focused OEE and maintenance layer: it ingests machine signals, adds shift, order, and reason-code context, and turns the result into availability, performance, and quality you can act on — plus the maintenance workflows to close the loop on recurring losses. For plants that want measurement and improvement quickly without a multi-year MES programme, it is a fast first step. Book a demo to see how it slots into an existing control stack.
No. SCADA is a real-time supervisory control and data-acquisition layer that runs and monitors equipment. MES is an operations layer that manages production orders, routing, traceability, and performance. They work together rather than replacing each other.
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.
Most plants running discrete or batch production benefit from both: SCADA for control and live monitoring, MES for orders, traceability, and reporting. Smaller operations sometimes start with SCADA plus a focused OEE layer and add full MES later.
SCADA is Level 2 (supervisory control) and MES is Level 3 (manufacturing operations management), with sensors at Level 1 and ERP at Level 4.
SCADA provides the real-time machine events behind availability and performance; MES provides the order, count, and quality context. Combined, they let an OEE system attribute losses precisely and meaningfully.
Login
Blog
