SCADA vs MES: What Each System Does in a Plant
SCADA supervises equipment and processes; MES manages the execution and records of production work. In a SCADA vs MES comparison, the useful distinction is the responsibility each system carries: operating the process versus tracking an order through production. Their features can overlap, so define who owns each decision and record before choosing or connecting software.
What does SCADA do?
SCADA means supervisory control and data acquisition. Its role is to give operators visibility of the process and a way to issue permitted supervisory commands. Typical functions include equipment status displays, process trends, alarm presentation and operator adjustments to operating settings.
Think of the questions an operator asks during a shift: Is the pump running? Is the temperature moving away from its target? Which alarm needs attention? SCADA brings those questions into an operating view.
The distinction between supervisory control and machine control matters. A screen command may request a machine start, but the controller should determine whether the required operating conditions permit it. Define this boundary explicitly; do not treat a screen button as the complete control function.
Alarm handling deserves its own design discussion. Our guide to why operators ignore alarms explores that part of the operating interface.
Whether that supervisory layer needs a standby is covered in when a SCADA system needs redundancy.
What does MES do?
MES means manufacturing execution system. Its role is to manage and record production execution: which work is released, where it runs, which materials it uses, and what results are recorded. Depending on scope, functions can include order dispatch, material tracking, work instructions, quality records and production reporting.
The questions are different from those on the operating screen: Which order is this line making? Which material lot went into it? Has the required check been recorded? What quantity can be reported against the order?
A useful MES specification follows work through the plant. It should describe who releases an order, what operators must record, how exceptions are handled and when an order becomes complete.
How do SCADA and MES compare?
Use this table to allocate responsibilities during design. It describes a starting point for discussion; confirm the actual capabilities of the proposed products.
| Design question | SCADA responsibility to consider | MES responsibility to consider |
|---|---|---|
| What needs attention now? | Equipment condition, process values and alarms | Order progress, missing records and execution exceptions |
| What action does the operator take? | Request permitted process commands or adjust settings | Start assigned work, identify materials and record checks |
| What provides context? | Equipment, operating mode and process state | Order, product, material lot and production step |
| What records are required? | Process events, alarm events and trends | Production quantities, material use and execution history |
| What must the interface settle? | Meaning and validity of equipment signals | How signals become records against production work |
Do not make the comparison by screen appearance. Two dashboards may look similar while answering different operational questions.
Where do they sit in ISA-95?
ISA-95 (also published as IEC 62264) provides a reference model for enterprise and control system integration. It has five levels, from the plant floor up:
- Physical production processes.
- Sensing and manipulating the production process.
- Monitoring, supervisory control and automated control.
- Manufacturing operations management.
- Business planning and logistics.
ISA's own summary of the standard places both MES and SCADA at the manufacturing operations management level, with controllers such as PLCs at the level below. A product can span functions across levels, so allocate functions rather than products.
Use the model to allocate functions, rather than assigning an entire software product to a rigid box.
Where do SCADA and MES overlap?
Production counts, downtime records, recipe handling and quality data are areas to examine for overlap. Product scope varies, so ask each supplier to demonstrate the required workflow rather than relying on a feature label.
For example, an equipment signal might indicate that a machine has stopped. Your design still needs to decide whether an operator must supply a reason, who approves a correction and which order receives the lost time.
Similarly, displaying a recipe value is different from managing an approved recipe revision. Specify who approves the revision, who selects it for an order and how the controller confirms the values it accepted.
For each shared function, assign one authoritative record and define how other systems may use or correct it.
What information should pass between them?
Write interfaces around operational events and responsibilities. A practical integration checklist is:
- Order context: How does equipment data become associated with the correct order, product and production step?
- Material identity: Where is a lot recorded, and what happens if it cannot be verified?
- Equipment events: Which states, counts and measurements are needed, and what does each value mean?
- Approved settings: Who may request a change, what validates it, and how is acceptance confirmed?
- Production results: Which system records completed, rejected and consumed quantities?
- Corrections: Who may amend a record, and how are the original value and reason retained?
Agree units, timestamps and identifiers before implementation. A quantity without its unit, or a result without its order identity, leaves room for conflicting interpretations.
A communications protocol does not settle these business rules.
For the business side of that exchange, see how ERP orders should reach the shop floor.
What would this look like on a production line?
Consider an illustrative example of a filling line making one production order.
The proposed design assigns the operator's equipment view to SCADA. It shows running states, process measurements and alarms. Permitted commands pass to the controller, which checks the operating conditions.
MES holds the order context. Before work starts, the operator identifies the material lot and records the required checks. The integration associates accepted production events with that order.
Now suppose the line produces an item while its connection to MES is unavailable. The specification must answer:
- Can production continue under an agreed local procedure?
- Where is the event retained?
- How is it linked to the correct order after reconnection?
- How does the receiving system recognise an event already recorded?
- Who resolves events whose order context is uncertain?
Test these behaviours during acceptance. A successful live demonstration alone does not prove that interrupted work will reconcile correctly.
What common mistakes should you avoid?
Buying from a feature list. Start with a workflow and its exceptions. Ask suppliers to show the complete sequence, including corrections and interrupted connections.
Leaving count ownership unclear. Define what each count represents, where it originates and which system owns the reported result. Include rejects, rework and manual adjustments.
Treating a sent command as an accepted command. Specify acknowledgement, validation and rejection behaviour. Make the outcome visible to the person responsible.
Mixing production software with safety responsibilities. Define safety-related design and changes with a qualified assessor. Document the boundary between production functions and safety functions.
Leaving failure behaviour until commissioning. Put connection loss, recovery, access permissions and manual procedures into the functional design specification.
When might you need only one system?
Scope the purchase around the unresolved operational problem.
If the priority is equipment visibility and operator control, assess the SCADA requirement first. If operators already have effective process control but orders, materials and production records remain disconnected, assess the execution workflow.
A plant may also choose a limited integration rather than a full MES implementation. Define what that smaller scope covers, who handles the remaining work and what evidence will show that the arrangement is adequate.
Can MES replace SCADA?
Assess this function by function. An MES product with production dashboards still needs to demonstrate the required process visibility, command handling and alarm workflow before you assign it those responsibilities.
Can SCADA perform MES functions?
Assess the complete workflow. Recording a count is only part of tracking production against an order. Check material identity, corrections, approvals and reporting before deciding that the requirement is covered.
Related reading: linking batch identities across PLC, SCADA and MES.
Which system should own production counts?
Choose an authoritative record for each purpose. Document the originating signal, acceptance rules, order association and correction procedure. Distinguish equipment counts from quantities accepted against an order.
What should you agree before integration starts?
Agree function ownership, record ownership, message meaning, permissions and failure behaviour. Then turn each agreement into an acceptance check that can expose an incorrect result.
Planning a SCADA or MES integration? Explore our control systems services or contact us to discuss the workflow, interfaces and acceptance criteria.