SCADA vs Historian: Real-Time Control vs the System of Record

Key takeaways

• SCADA monitors and controls the process in real time.
• A historian captures and stores time-series data long-term for analysis.
• SCADA is built for now; historians are built for trend, compliance, and forensics.
• Relying on SCADA for history loses data; relying on a historian for control is too slow.

Short answer: SCADA supervises and controls the process in real time, the live screens and setpoints operators act on now. A historian is the long-term time-series database that records what happened for trend analysis, compliance and root cause. SCADA is optimised for the present moment; the historian for the permanent record. Each is poor at the other job. See also oee for manufacturing.

What SCADA does

SCADA (supervisory control and data acquisition) is the control-room layer: live monitoring and control of machines and processes, with alarms, setpoints and operator screens. It is built for the here-and-now, keep the process safe and in control this second.

• Live monitoring and operator control.
• Alarms and setpoints.
• Short-term buffering, not deep history.

What a historian does

A historian is purpose-built to store high-resolution time-series data for the long term, compressed, queryable and retained for months or years. It exists to answer questions about the past that SCADA cannot, because SCADA was never meant to remember.

• High-resolution time-series storage.
• Compression and long retention.
• Query and trend for analysis and audit.

A worked example

A batch goes out of spec on Tuesday. The operator's SCADA screen showed the temperature drift live and they acknowledged the alarm, but SCADA only buffers a few hours, so by the time quality investigates on Thursday the live data is gone.

The historian, however, has the full second-by-second temperature curve for the whole batch, so the team can pinpoint exactly when and how far it drifted. SCADA kept the process running; the historian explained what went wrong.

Why you need both

SCADA keeps the process running safely now; the historian lets you ask why last Tuesday's batch drifted. Use SCADA for real-time control and the historian as the system of record that feeds analytics, OEE and compliance reporting. Neither substitutes for the other.

Common mistakes

1. Using SCADA logs as history. Resolution and retention are too limited for real analysis.

2. Querying the historian for control. Latency makes it unsuitable for real-time action.

3. No historian at all. Every analysis becomes "we think" instead of "the data shows."

4. Historian data nobody analyses. Storage cost with no insight.

Where OEE lives

OEE analytics live on historian-grade data, you need the stored time series to decompose losses and trend OEE over weeks and months, not just watch a live screen. The machine signals originate at the control layer; their long-term meaning is unlocked at the historian.

How Fabrico fits

Fabrico consumes machine data and retains it for the trend analysis OEE needs, complementing SCADA control with a system of record for losses. Book a demo to see historian-grade OEE analysis.

Related reading

• oee for manufacturing
• why shop floor data conflicts with erp
• mes vs scada
• iiot vs iot

Frequently asked questions

Is a historian part of SCADA?

Often integrated, but a distinct function, control versus long-term record.

Can OEE run off SCADA alone?

Live OEE partly, but trend analysis needs stored history a historian provides.

What resolution does a historian keep?

Sub-second to seconds, compressed for long retention.

Do I need both SCADA and a historian?

For control plus analytics and compliance, yes.

Where does ERP fit relative to these?

Above both. ERP plans and accounts; SCADA controls; the historian remembers.