MES and SCADA for SMEs: deploy them in 3 phases, in days
2026-02-11
It’s not a choice between one or the other: SCADA monitors and controls production in real time, while MES manages orders, traceability, and quality across shifts and days. Under the ISA-95 model, the former operates at Level 2 and the latter at Level 3. In most factories, both end up being necessary because they answer different questions.
In summary:
Installing SCADA first helps provide real-time visibility into machines, but it does not replace the order and quality management provided by an MES.
MES focuses on managing batches, traceability, and quality results, working on a time horizon of shifts and days, not seconds.
SCADA and MES integration should follow the ISA-95 model, using open standards such as OPC UA or MQTT to reduce costs and complexity.
In small factories, implementation should follow phases: SCADA first, then critical order management, followed by gradual scaling based on results.
The right choice is to use both systems together, rather than trying to make one replace the other, to address different management and control needs.
Table of contents
-
What SCADA is and what functions it covers on the shop floor
-
What an MES is and what it contributes to traceability and quality
-
A practical roadmap for implementing MES and SCADA in an SME
What SCADA is and what functions it covers on the shop floor
SCADA is the layer that tells you what is happening right now on each machine. It collects signals from sensors and programmable logic controllers, displays them on operator screens, and triggers alarms when something goes out of range. Its time horizon is measured in milliseconds or seconds, not shifts.
The functions it covers are specific:
-
Data acquisition from sensors, PLCs, and drives.
-
Human-machine interface (HMI) so the operator can see and act on the process.
-
Management of alarms and critical safety or shutdown events.
-
Historical recording of process variables (historian).
-
Remote control of actuators and equipment start/stop.
Common protocols include OPC UA, Modbus, and EtherNet/IP, chosen for their reliability in environments with electrical noise and fast cycles. Typical users are control room operators and maintenance staff who need to see the machine’s status by the second. If the plant still lacks reliable visibility into its equipment, SCADA is usually the first reasonable investment, before considering any higher layer.
Pro tip: Don’t install SCADA expecting it to replace paper production reports. Its role is to monitor the machine, not manage the manufacturing order: you’ll need an MES for that.
What an MES is and what it contributes to traceability and quality
An MES manages production execution: which order is being manufactured, with which batch, who made it, and with what quality result. It works on a time horizon of shifts and days, not seconds, and connects the shop floor with planning and management.
Its main functions include:
-
Releasing and tracking manufacturing orders.
-
Batch genealogy and traceability of consumed materials.
-
Quality control with nonconformance records for each operation.
-
Capturing times and downtime associated with each order, not just the machine.
-
Calculating indicators such as OEE from contextualized data.
Typical users include planning, quality, and management, as well as the operators themselves, who record their work from a screen or mobile phone. Measurable benefits appear quickly: fewer reworks due to batch identification errors, complete traceability in the event of a customer complaint, and much cleaner consumption closeout against the ERP. Industrial production control software covers precisely this layer when an Excel spreadsheet is no longer enough.
Key differences between MES and SCADA
The quickest way to tell them apart is to ask what question each one answers. SCADA answers, “What is happening right now on this machine?” MES answers, “What is being manufactured, how and by whom, and with what result?”—a distinction that neatly sums up the logic behind both production system layers.
The criteria that set them apart:
-
Objective: SCADA aims for immediate control; MES aims for order execution and traceability.
-
Focus: SCADA looks at the machine; MES looks at the product, batch, and operator.
-
Users: SCADA is for the control room and maintenance; MES involves planning, quality, and management.
-
Time horizon: milliseconds and seconds versus shifts and days.
-
Decisions enabled: adjusting a process parameter versus deciding whether an order is closed, repeated, or blocked due to quality.
Imagine a line stoppage. SCADA detects it instantly, triggers the alarm, and records the exact start and end times. MES, on the other hand, links that stoppage to the specific manufacturing order, calculates its impact on the shift’s OEE, and records whether it affected a batch already committed to a customer. Without this context, the machine data provided by SCADA has no meaning to management. If your problem is not knowing what the machine is doing, start with SCADA; if your problem is not knowing what has been manufactured or with what quality, you need an MES.
How SCADA and MES are integrated according to ISA-95
The ISA-95 model organizes the factory into levels: Levels 0 and 1 are sensors and controllers, Level 2 is SCADA, Level 3 is MES, and Level 4 is ERP. The usual data flow moves up from the PLC to SCADA, from there to MES, and ends at ERP for costs and purchasing; in the opposite direction, MES sends instructions and manufacturing constraints down to the plant.
This relationship is not competition but complementarity: SCADA feeds MES with real-time data, and MES returns orders and constraints that the plant must follow. Cloud platforms have made this integration considerably simpler than the custom API development of a decade ago.
Key fact: Keeping the layers separate according to ISA-95 and using open standards such as OPC UA or MQTT reduces maintenance complexity compared with forcing systems to converge, which tends to increase maintenance costs in the medium term.
Best practices to keep things simple:
-
Use OPC UA or MQTT to connect SCADA with MES instead of proprietary point-to-point connections.
-
Let ERP manage costs and purchasing; don’t ask it to provide shop-floor traceability—that’s what MES is for.
-
Don’t let MES try to act as SCADA by reading sensors directly: it loses order and quality context.
A practical roadmap for implementing MES and SCADA in an SME
The sequence that works best in factories with fewer than one hundred operators follows three phases, without skipping steps or oversizing the project from day one.
-
Visibility first. Install SCADA or a lightweight OEE system to get reliable machine data before thinking about traceability.
-
MES for critical processes. Add order management, quality, and traceability where the risk of rework or complaints is highest, not across the whole plant at once.
-
Scale toward MOM. Integrate maintenance, warehousing, and comparisons between lines once the basic MES is working reliably.
This sequence aligns with what digitalization guides for medium-sized companies recommend: forcing premature convergence between SCADA and MES often creates fragile solutions that cost more to maintain than to implement.
Pro tip: Don’t wait until the process is perfect to digitize it. Start with the line with the most rework or complaints: that’s where the return becomes apparent in weeks, not years.
Why the right question is not “MES or SCADA”
The discussion about which of the two systems is “better” starts from a mistaken premise. Neither replaces the other because they answer different questions, and trying to stretch SCADA to make it act as MES (or vice versa) is the quickest way to end up with a system that satisfies no one: not the operator, who can’t find the information, nor management, which doesn’t trust the data.
What fails in practice is not the technical choice, but the sequence. Many SMEs try to implement a complete MES before they have reliable machine data, and the result is a system that records orders on a poor information base. A phased roadmap is not excessive caution: it’s the difference between a project that is being used after three months and one that gets abandoned.
The opposite mistake happens too: sticking with SCADA alone for years because “we already have visibility,” while traceability remains on paper and every customer complaint is investigated by hand. If your factory already knows what its machines are doing but doesn’t know what has been manufactured or with what quality, that is exactly the sign that it needs to take the next step.
An MES designed for SMEs, without a months-long project.
There are platforms that bring together production control, planning, warehousing, and maintenance in a single system that can be up and running in days, with no long-term commitment.
Some platforms cover MES functions such as digital orders, batch traceability, and quality recording, along with planning and purchasing, warehouse management, and maintenance, with artificial intelligence agents that automate repetitive tasks through natural-language instructions. The shared goal of SME managers is to gain real visibility into the factory without having to be physically on the shop floor, through an intuitive interface that can be used from a mobile phone.
If your factory already has SCADA or basic machine control and the next step is order traceability, you can review Bold Factory’s industrial production control software and request a demo to see how it adapts to your specific process.
Sources
To understand the full architecture, it is worth reviewing the ISA-95 model, the explanation of how MES and SCADA work together, and the analysis of their future convergence published by Automation World.
