Real-time values tell you what is happening now; a historian tells you what happened - and that is where most of the value in operational data lives. Trends, reports, compliance records, and root-cause analysis all depend on storing every tag over time, efficiently, for years. This guide explains what a SCADA historian is and how it differs from an ordinary database.
A SCADA Historian in plain English: A SCADA historian is a time-series database purpose-built to store the values of process tags (pressures, levels, flows, states) over time, efficiently and at scale, so operators and engineers can trend, report, and analyze historical data.
A general-purpose relational database can store time-stamped values, but it struggles at industrial scale - thousands of tags sampled every second for years is billions of rows. Historians are optimized for exactly this: fast writes of streaming values, compression (often storing only meaningful changes rather than every identical reading), and fast retrieval of a tag's history over any time range. That specialization is why process historians exist as a category.
The reference example in heavy industry is the a traditional process historian; lighter time-series historians (like Canary) and the historians built into SCADA platforms serve the same function at different scales.
Four jobs dominate: trending (plotting a tag over hours, days, or months to see behavior and drift), reporting (daily production volumes, runtime, downtime, compliance figures), analysis (comparing periods, finding the cause of an event), and compliance (an auditable record that a value stayed in range, which regulations like TSA and EPA increasingly expect). Without a historian, operational data is ephemeral - you see it once and it is gone.
On-premise SCADA historians run on servers you maintain and size. Cloud-native platforms include the historian as a managed service, so storage scales without a server room and history is queryable from anywhere. For distributed oil and gas, a built-in historian that federates across sites means production reporting and compliance records for the whole operation live in one place. Merobix, for instance, includes a time-series historian on every plan, with cross-site federation on Enterprise.
A SCADA historian is a time-series database built to store process tag values (pressures, levels, flows, states) over time, efficiently and at scale. It lets operators and engineers trend, report on, and analyze historical operational data.
A historian is a specialized time-series database optimized for fast writes of streaming values, compression of unchanged data, and fast retrieval over time ranges - handling billions of samples that would overwhelm a general-purpose relational database.
For trends, production and compliance reporting, and root-cause analysis. Real-time values disappear once shown; a historian preserves them so you can see behavior over time, prove a value stayed in range for regulators, and calculate volumes and runtime.
Modern cloud SCADA typically includes a managed historian, so storage scales without a server room and history is queryable from anywhere. Merobix includes a built-in time-series historian on every plan, with cross-site federation on Enterprise.
Merobix includes a built-in time-series historian - trends, reports, and compliance history, with no server to run.