SCADA (Supervisory Control and Data Acquisition) is software that supervises and controls industrial equipment in real time — it reads data from PLCs and sensors, displays it on operator screens, raises alarms, and sends commands back to machines. MES (Manufacturing Execution System) is software that manages what your plant produces — it tracks work orders through routing steps, records which material went into which part, enforces quality checks, and reports production performance. The core difference: SCADA is a control-and-monitoring layer that works in seconds and milliseconds (ISA-95 Level 2), while MES is a production-management layer that works in work orders, shifts, and lots (ISA-95 Level 3).
The two get confused constantly, partly because vendors on both sides claim overlapping features and partly because both produce dashboards that look similar in a demo. This guide breaks down what each one actually does, where they overlap, what they typically cost, and — the part most vendor content skips — when a smaller shop needs neither.
What Does SCADA Actually Do?
SCADA grew out of the 1980s, when networked PLCs made it possible to aggregate data from multiple controllers into a single operator workstation. Forty years later, the core job hasn't changed: give a human a real-time picture of a process and the ability to act on it.
A typical SCADA system has four parts:
- Drivers and connectivity that poll PLCs, RTUs, and instruments over industrial protocols — EtherNet/IP, Modbus, S7, OPC UA. (If you want the full tour of that protocol landscape, we covered it in our guide to PLCs and the Unified Namespace.)
- An HMI layer — the graphical screens where an operator watches tank levels, motor states, and temperatures, and clicks buttons to start pumps or change setpoints.
- An alarm engine that fires when a value crosses a limit and tracks acknowledgment.
- A historian that logs time-series data for trending and troubleshooting.
The defining trait is the write path. SCADA doesn't just observe — an operator can command equipment through it: open a valve, change a line speed, put a zone in manual. The PLC still executes the actual control loop (SCADA is supervisory, not direct control), but SCADA is the human's hand on the process.
That's also why SCADA shows up where it does. Water treatment plants, breweries, chemical batching, food processing, anodizing and plating lines, oil and gas — anywhere a continuous or batch process needs a human watching and steering it in real time. Common platforms include Inductive Automation's Ignition, AVEVA (formerly Wonderware), GE iFIX, Rockwell FactoryTalk View, and Siemens WinCC.
What SCADA doesn't do: it has no concept of a work order. It doesn't know that the parts running on Line 2 belong to customer PO 4471, that they're due Thursday, or that the lot needs a material cert. It can tell you the oven is at 350°F right now. It can't tell you which jobs went through that oven last month or whether they passed inspection.
What Does an MES Do?
An MES sits one level up. Where SCADA answers "what is the equipment doing right now," an MES answers "what is being produced, from what, by whom, and did it meet spec."
The MESA International model describes eleven MES functions, but in practice most deployments center on a handful:
- Detailed scheduling and dispatching — sequencing work orders onto specific machines and telling operators what to run next.
- Production tracking — logging start/stop times, counts, and scrap against each work order as it moves through routing steps.
- Traceability and genealogy — recording which material lot, which machine, which operator, and which parameters produced each part. This is the function that regulated shops (aerospace AS9100, medical ISO 13485, automotive PPAP) buy MES for.
- Quality management — enforcing in-process inspections, capturing measurement results, holding nonconforming lots.
- Performance analysis — OEE, downtime reasons, cycle time variance. (If OEE is new territory, our OEE guide covers the formula and what a realistic score looks like.)
The timescale is transactional, not real-time. An MES cares that operation 30 on work order 8812 finished at 2:47 PM with 212 good parts and 3 scrap — not what the spindle load was at millisecond resolution while it ran. Data enters the MES from machine signals, barcode scans, and operator entry, and flows upward to the ERP (ISA-95 Level 4), which handles ordering, inventory, and invoicing.
Common MES platforms include Siemens Opcenter, Rockwell's Plex, Epicor Advanced MES, AVEVA MES, and newer app-based entrants like Tulip. The market ranges from heavyweight systems requiring year-long implementations to cloud subscriptions a mid-size shop can stand up in a quarter.
What an MES doesn't do: it doesn't control equipment. No operator opens a valve from an MES screen. And most MES products are only as good as the data feeding them — if machine data isn't wired in, you're back to operators keying in counts at a terminal, which is where a lot of MES value quietly leaks away.
How Do They Compare Side by Side?
| SCADA | MES | |
|---|---|---|
| Purpose | Real-time supervision and control of equipment and processes | Managing production: work orders, scheduling, traceability, quality |
| ISA-95 level | Level 2 (supervisory control) | Level 3 (manufacturing operations management) |
| Typical users | Operators, control engineers, maintenance techs | Schedulers, supervisors, quality engineers, plant managers |
| Real-time vs transactional | Real-time: milliseconds to seconds | Transactional: minutes, shifts, work orders, lots |
| Typical cost range | Licenses commonly $20K–$150K; $150K–$400K all-in for a mid-size plant | Cloud products commonly $10K–$50K/year for small sites; traditional implementations commonly $100K–$500K per plant |
| Typical deployment time | Weeks for a single line; commonly 6–18 months plant-wide | Commonly 6–18 months; multi-site rollouts run years |
Where Do They Overlap?
The confusion between the two is earned, because the overlap is real.
Both collect machine data. Both show dashboards. Both claim OEE — SCADA vendors sell OEE modules built on historian data, and MES vendors treat OEE as a core report. Both alarm on problems. In a demo, a well-built Ignition screen and an MES production view can look nearly interchangeable.
Where they meet in a real plant is the data handoff. SCADA (or the PLCs directly) produces machine events — cycle complete, fault code, part count — and the MES consumes them and attaches business context: that cycle belonged to this work order, this lot, this customer. In the traditional stack that handoff was a point-to-point integration project, and a brittle one. The Unified Namespace architecture exists largely to fix this: publish machine data once to a central broker, and let SCADA, MES, and anything else subscribe to what they need.
The boundary is also blurring from both directions. Ignition sells MES modules on top of its SCADA core. MES vendors are adding direct machine connectivity so they don't depend on a SCADA layer underneath. Plenty of plants run "SCADA doing light MES work" — production counts and downtime reasons tracked in custom screens — and it works, up to a point. The point is usually traceability: the day a customer audit asks you to prove which material lot went into which serial number, custom SCADA screens stop being enough.
One thing that doesn't blur: the write path. SCADA commands equipment. MES manages information about production. A system that controls your process carries safety and uptime risk that an information system doesn't, and that difference drives who installs it, how it's validated, and what it costs.
When Do You Need Which?
You need SCADA when a human has to supervise and control a process from a screen in real time. Concretely:
- Continuous or batch processes — mixing, heat treat, plating, food, chemicals — where an operator adjusts setpoints during the run
- Alarm conditions that need response in seconds, not next shift
- Multiple PLCs whose coordination a person needs to see in one place
- Regulatory logging requirements on process parameters (common in water/wastewater and food safety)
A 15-person CNC job shop rarely hits any of these. The machines already have controllers; the operator stands at the machine. There's nothing to supervise from a control room.
You need an MES when the complexity of what you make outgrows paper and spreadsheets. Concretely:
- Traceability or genealogy requirements from customers or regulators — aerospace, medical, defense, automotive
- More active work orders than a scheduler can hold in their head or a whiteboard
- Quality steps that get skipped because nothing enforces them
- Real interest in knowing actual cost per job versus quoted cost
A 30-person shop with AS9100 customers may genuinely need an MES before it needs anything resembling SCADA. A brewery needs SCADA long before it needs an MES. A 400-person automotive supplier probably needs both, integrated.
The honest heuristic: SCADA follows from your process, MES follows from your product requirements, and neither follows from shop size alone.
What Do They Cost?
Both markets quote wide ranges, and in both, services routinely cost more than software. With that caveat:
SCADA. Licenses commonly run $20K–$150K depending on platform and tag/seat count. Integration — connecting PLCs, building screens, commissioning alarms — commonly adds $50K–$200K in systems integrator fees, and plant-wide implementations typically take 6 to 18 months. All-in, a mid-size plant commonly spends $150K–$400K, plus 15–20% of license cost per year in maintenance. To be fair to the low end: a single-line HMI/SCADA setup on something like Ignition Edge can be done for a few thousand dollars if you have someone who can configure it. The six-figure numbers come from plant-wide scope and integrator hours, not the software alone. (We've written a more opinionated, bottom-funnel take on those economics in HLink vs SCADA — read this article first, that one second.)
MES. Pricing varies even more. Cloud MES products aimed at smaller shops commonly start around $10K–$50K per year in subscription fees. Traditional single-plant implementations are commonly quoted at $100K–$500K once configuration, integration, and training are included. Enterprise multi-site rollouts run into the millions and multiple years. The number that surprises buyers most isn't the license — it's the internal time: an MES only works if routings, part masters, and work instructions are accurate and someone owns keeping them that way. Shops that skip that discipline end up with an expensive system nobody trusts.
Neither figure is an argument against either system. Both pay for themselves in the right plant. The point is that these are commitments on the order of a new machining center, and they deserve the same scrutiny.
When Do You Need Neither (Yet)?
Here's the part most comparison articles won't say: if you're a manufacturer with fewer than about 50 people, the odds are good you don't need SCADA or MES yet. You need to know what your machines are actually doing, and right now you probably don't.
Most small shops can't answer basic questions with data: What was second-shift utilization last month? Which machine loses the most hours to unplanned stops? Did cycle times drift after the last tooling change? SCADA won't answer those unless you build it to (and it's overkill for the job), and an MES fed by guesses produces reports made of guesses.
Machine monitoring is the layer that answers them. It's read-only — it observes utilization, cycles, faults, and conditions without writing anything back to the machine — which means no control-logic changes, no certified integrator, and none of the safety review that comes with a system that can command equipment. Modern cellular monitoring devices cost hundreds of dollars, not tens of thousands, and deploy in hours.
Monitoring first is also the cheapest way to figure out whether you need the bigger systems at all. Three months of real utilization and downtime data tells you whether your problem is machine availability (maybe you need better maintenance, not software), scheduling chaos (an MES conversation), or process variability (closer to SCADA territory). And if you do buy an MES later, the monitoring layer becomes the machine-data feed that keeps it honest. This bottom-up path — visibility first, systems second — is part of a broader idea we cover in What Is Manufacturing Observability?
Buying a $250K system to find out what a $1K device could have told you is a common story. It doesn't have to be yours.
Where Helio Fits
Helio builds that first layer: AI-powered machine monitoring for small and mid-size U.S. manufacturers. Our $620 HLink device connects to your existing machines over cellular and streams data to software you can ask plain-English questions — no SCADA project, no MES implementation, no integrator. If you're still deciding between the systems above, start by finding out what your floor is actually doing: helioiot.com.