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. 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’s job. See also oee for manufacturing.

What SCADA does

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

What a historian does

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

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 control and the historian as the system of record feeding analytics and OEE.

Common mistakes

Using SCADA logs as history: resolution and retention are too limited. Querying the historian for control: latency makes it unsuitable for real-time action.

How OEE relates

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.

See how Fabrico captures this automatically on your lines — explore OEE for manufacturing or book a demo.

Related reading

• oee for manufacturing
• why shop floor data conflicts with erp

Frequently asked questions

Is a historian part of SCADA?

Often integrated, but a distinct function.

Can OEE run off SCADA alone?

Live OEE yes; trend analysis needs stored history.

What resolution does a historian keep?

Sub-second to seconds, compressed for long retention.

Do I need both?

For analytics and compliance, yes.