MES vs SCADA: Which Should You Implement First? Decide by Shop-Floor Conditions
When a plant starts a digitalization project, MES and SCADA often land in the same tender as if they were one system. Both connect to equipment, both show screens, both handle data — but they own different objects. SCADA owns the equipment's current state, alarms and operator screens. MES owns how work orders run, how material moves, how quality is recorded and how lots are traced. Which layer you put in first depends on what the site already has, and whether equipment maintenance or production control is the more urgent pain. This article gives factory IT and maintenance a framework they can put side by side.
What MES and SCADA each own
SCADA is the real-time layer on the equipment side. It reads PLC, instrument and robot values, draws status on screens, raises alarms against thresholds, and gives operators and maintenance a window they can watch, acknowledge and reset. The refresh cycle is designed in seconds, or faster. Without this layer, the shop floor judges equipment by walk-around checks and by memory after a stop.
MES is the execution layer on the production side. It takes plans or work orders and records what each station did, which material lot was used, whether the process followed the recipe, how defects were judged, and how lots are traced forward and back. It also reads equipment data, but not so maintenance can watch a live curve — it binds process data to the work order, the person and the material. Both layers need collection. Collection alone does not mean you already have MES.
- Time scale differs: SCADA watches second-level equipment state and alarms; MES watches the execution of work orders, shifts and lots
- Who reads the screens differs: SCADA is for operators and equipment maintenance; MES is for production, quality and planning
- How data is used differs: SCADA is for monitoring, alarms and operation; MES is for execution, error-proofing, statistics and traceability
- What you cannot run without differs: SCADA mainly needs PLCs and instruments; MES also needs barcodes, recipes, people and work-order masters
- The split with ERP differs: SCADA can run on its own; MES usually receives work orders from ERP and returns completions and consumption
When you should put SCADA in first
Equipment is not on the network yet, maintenance cannot see a central screen, stop causes cannot be explained — those are gaps in the equipment layer. If you put MES in while those gaps remain, output and defect counts fall back to manual entry, and the system soon becomes another spreadsheet. In a typical discrete plant, if several PLC brands sit on the same line and alarms still live on each machine's local screen, stand up collection, monitoring, alarms and screens first. Only then does later MES have process data it can actually use.
- Key equipment is not connected, stations have no live status, and maintenance can only walk to the local screen at the machine
- Alarms are scattered across machines with no central list, so you only learn what happened after a stop
- You want to tally stop losses or running time, but run, stop and fault signals are not yet in a unified tag list
- Several PLC brands and older machines share the same shop, so collection and screens must be unified before work-order execution
When you should put MES in first
The equipment layer is already enough — machines have an HMI, or the line already has central monitoring — but work orders still move on paper and by word of mouth, material is easy to load wrong, and audits ask for lot history. What you lack is not more monitoring screens; it is execution, error-proofing and traceability. Process curves can come from the SCADA you already have. Work orders, material and lot identity will not assemble themselves just because you added another screen. Those needs sit in MES.
- The line already has usable monitoring or machine screens, but work orders, booking and defects still live on paper and spreadsheets
- The main losses now are mixed material, wrong assembly and skipped operations, so barcode checks and error-proofing come before extra monitoring screens
- Customer or system audits require lot or serial traceability, so people, material and process data must bind to one identifier
- ERP can already issue work orders; what is missing is the shop-floor execution loop and completion return, not central equipment monitoring
If you run both in parallel, draw the boundary first
It is common for both sides to be urgent: maintenance wants central monitoring and alarms, production wants traceability and error-proofing. You can start both in the same program. That does not mean building one unlayered system. SCADA keeps the tag list, screens, alarms and real-time database. MES owns work orders, material, quality and traceability. MES reads process data from SCADA and does not rebuild operator screens inside MES. SCADA does not dispatch work orders or deduct material on its screens. We implement both SCADA HMIs and shop-floor MES, covering multi-protocol collection, central monitoring and alarms, plus plan execution, material, quality and traceability. Which layer to start with is based on the data sources the site already has and the problem to clear first, not on the order of a product catalogue.
What a parallel project must write into the technical agreement early is interface direction and master-data ownership: which tags SCADA collects and hands to MES, which system issues work orders, where completions return, and how each layer buffers during a communication break. The person who draws the boundary must understand both the equipment tag list and production master data. On a cross-border project you need an English-speaking contact, otherwise maintenance and production duties will not land in the same technical agreement. Once the boundary is set, the two layers can be built in parallel and accepted layer by layer.
| Shop-floor condition | Which layer to start with | Why |
|---|---|---|
| Equipment is not connected; no central screens or alarms | SCADA first | Without a collection layer, MES output, stops and process curves fall back to manual entry, and the floor will not keep filling them in after go-live |
| HMI or central monitoring already exists; work orders and traceability are still on paper | MES first | The equipment layer can already show status; what is missing is execution, material, quality and lot history |
| Audits require traceability, and line monitoring is almost empty | Both in parallel, draw the boundary first | Traceability needs process curves (SCADA) and barcode work orders (MES). Fix interfaces and masters first, then implement in parallel |
| Several PLC brands on one line; maintenance cannot cover local machine screens | SCADA first | The pain is central monitoring and alarms, not scheduling. Stand up the tag list and screens first |
| Frequent changeovers; wrong material or wrong sequence is the main request | MES first, connect the collection points needed for error-proofing | The core is error-proofing and material checks. Monitoring screens can follow, but equipment signals used for error-proofing must be connected in the same step |
Summary
The difference between MES and SCADA is not the name. It is the object each layer owns: one watches equipment now, the other watches the production process. Which layer you put in first depends on whether the site lacks live monitoring, or execution and traceability.
If both are missing, you can run them together, but the tag list, work orders and interface direction must go into the technical agreement first. If the picture is still unclear, start with a shop-floor data-source check: which signals can already be collected, how work orders move today, then decide which layer to start with.
Discuss SCADA first or MES first
Tell us how the line is monitored today, how work orders and traceability run, and which problem you need to clear first. We will propose a layered scope from those shop-floor conditions.
Contact Us