Does the SCADA server store any history at all?

Usually a short rolling buffer — recent alarm and event logs, maybe a few hours or days of trend data for immediate operator review — but not the deep, compressed, multi-year archive that a historian maintains. The SCADA server's buffer exists for immediate operational context, not long-term analysis.

What is swinging-door compression and why does it matter here?

It's a common historian compression algorithm that discards data points that fall within a tolerance band of a straight line drawn between the last stored point and the current one — effectively storing only the points needed to reconstruct the trend shape within an acceptable error, rather than every raw sample. This is why a historian can affordably retain years of high-resolution data per tag, something a SCADA server's live database isn't designed to do at that scale.

Can control commands be issued from a historian?

No. A historian is a read-optimized archive with no operational control interface — it has no path back to an RTU or PLC to change an output. Control commands flow exclusively through the SCADA server (or DCS), which is precisely why losing the SCADA server is the more urgent operational emergency of the two.

If the historian and SCADA server run on the same physical server, are they still separate systems?

Usually yes, at the software level — they remain separate services or products (a real-time SCADA/HMI engine and a historian database engine) even when co-located on one machine for a smaller installation. Larger installations typically split them onto dedicated servers specifically because their performance profiles and failure/redundancy requirements differ.

What compliance requirements typically depend on the historian rather than the SCADA server?

Regulatory frameworks that require demonstrating what a process actually did over time — EPA environmental discharge reporting, FDA 21 CFR Part 11 electronic records in pharma/food manufacturing, and utility interconnection or NERC reporting in power systems — depend on the historian's long-term, tamper-evident time-series record, not the SCADA server's current-value snapshot.

← SCADA & Industrial Controls Studio

Concept Explainer · SCADA

Historian vs. SCADA Server

Losing one means your operators go blind right now. Losing the other means you can't prove what happened six months ago. They are not the same system wearing two names.

It's a common assumption that the "historian" is just where the SCADA server logs its data — a backup copy, or the same database with a longer retention setting. In most real SCADA architectures they're separate pieces of software, often on separate servers, doing genuinely different jobs on genuinely different data models. The SCADA server owns the live, current state of every point — the value right now, whether it's in alarm right now, and the ability to send a control command right now. The historian owns time — a compressed, queryable archive of what every point did over the last five years, built for trend charts and compliance reports, not for driving a control action.