Buyer resource
SCADA vs Historian vs MES: What Each System Does
SCADA supervises and controls a process in real time; it is what operators watch and act through. A historian stores time-series process data for later analysis, at a resolution and retention SCADA is not built for. MES manages the work itself: orders, materials, quality records and traceability. Each answers a different question, and buying one expecting another produces a system nobody uses.
Published · Last reviewed by Geek Engineering senior engineering review.
The three layers at a glance
| System | Question it answers | Typical data | Main users |
|---|---|---|---|
| SCADA | What is the process doing right now, and what should I do about it? | Live values, alarms, setpoints, commands | Operators, shift supervisors |
| Historian | What did the process do, and how did it change over time? | Compressed time-series tags kept for years | Process engineers, quality, reliability |
| MES | What are we making, from what, and did it meet specification? | Work orders, genealogy, recipes, quality results, downtime reasons | Production planning, quality, plant management |
Where the boundaries blur
Most SCADA packages keep short-term trends, most historians include basic dashboards, and many MES products bundle both. The overlap is why projects go wrong: a plant buys a SCADA upgrade expecting traceability, or an MES expecting live control. Start from the question you need answered, then check which layer is designed to answer it at the scale you need.
In the ISA-95 model, SCADA and historians sit at level 2 with control, MES at level 3, and ERP at level 4. The model is a useful map for deciding which system owns each piece of data.
Choosing what to add first
- Operators cannot see problems in time: improve SCADA, alarms and screens first.
- Engineers cannot explain quality or yield problems: add a historian and connect the right tags.
- You cannot trace which lot went into which product, or why the line stopped: you need MES functions, often starting with downtime tracking and genealogy.
- Planning and the plant floor disagree on what was produced: integrate MES with ERP.
OEE and downtime tracking
Downtime and OEE tracking is the most common first MES function, because it needs little more than machine states and reason codes, and it pays back quickly. It can be built in SCADA, bought as a standalone product or delivered as an MES module. Choose based on whether the data will later need to connect to orders and quality records.
Key takeaways
- SCADA is for now, a historian is for the past, MES is for the work.
- Start from the question you need answered, not the product category.
- ISA-95 levels help decide which system owns which data.
- Downtime tracking is the usual first step toward MES.
Related questions
Do we need a historian if our SCADA system already has trends?
Often yes. SCADA trends are usually short-term and limited in resolution. A historian stores high-resolution data for years and makes it available to analysis tools, which is what root-cause work, quality investigations and AI projects need.
Is MES the same as ERP?
No. ERP plans and accounts for the business: orders, inventory, purchasing and finance. MES executes production on the floor: which machine, which materials, which operator, what result. They exchange orders and production results.
What is the cheapest way to start with MES?
Start with one function on one line, usually downtime and OEE tracking or electronic batch and traceability records, and prove the value before expanding. A plant-wide MES rollout as the first step carries the highest risk of failure.
Prefer to talk this through?
Send a short brief — objective, equipment, timeline — and a senior engineer will respond with questions and an honest fit assessment.
Get a Quote