SCADA, MES, and historian: where each one ends

Ask three vendors where SCADA ends and MES begins and you will get four answers — usually drawn to favor whatever they sell. The boundaries below are the ones that survive contact with real plants.

FIG. 02From machine to data

SCADA: the present tense

SCADA supervises and controls: live visualization, alarming, operator actions, and short-term trending. Its time horizon is now — seconds to shifts. It talks to controllers (via drivers, OPC UA, or native protocols), keeps operators informed, and records what happened well enough to run the process. It is not a system of record for quality, genealogy, or compliance, even when it stores months of trend data.

Historian: the memory

The process historian stores high-resolution time-series data for years and serves it back fast: ad-hoc trends, calculations, and exports for engineers. Where SCADA trends answer "what is happening," the historian answers "what happened, exactly, and what does it correlate with." Classic names in this space include AVEVA PI System and Proficy Historian — the latter now part of Velotic, the independent industrial software company formed around the former Proficy, Kepware, and ThingWorx portfolios. Modern alternatives include open time-series databases, but the historian's compression, interpolation, and process-aware querying remain hard to replicate casually.

MES: the operations record

MES manages manufacturing operations: orders, scheduling, dispatch, genealogy, quality checks, and performance (OEE). Its horizon is shifts to months, and its data model is lots, batches, and serial numbers — not tags. MES consumes SCADA/historian data (counts, statuses, process values) and attaches it to production context: this tag value belonged to that work order at that station. ISA-95 is the standard vocabulary for this handoff.

Drawing the lines in practice

• SCADA owns control and alarming. If an operator acts on it in real time, it lives here.
• The historian owns raw process truth over time. If an engineer trends it next year, it lives here.
• MES owns production truth. If quality or the customer asks for it, it lives here.

Overlap is normal — SCADA keeps short trends, MES caches tag values — but each overlap should be a conscious cache with a defined source of truth, not an accidental second database. The most expensive failure mode is MES and SCADA disagreeing about yesterday's production count with no way to reconcile them.

References

• ISA standards: ISA-95, ISA-88, ISA/IEC 62443
• The Inductive Automation Blog — SCADA and Ignition architecture
• Automation World — MES and manufacturing operations coverage