Engineering & Industry 4 min readORG-F12

Industrial Historian vs SCADA vs Time-Series Database: Where Plant Data Belongs

Share

SCADA, an industrial historian and a general time-series database may all display trends, but they solve different problems. The architecture should assign acquisition, operational context, durable history, analytics access and record ownership explicitly instead of treating the products as interchangeable stores.

The short answer

Keep real-time supervision and operator interaction in the control-system boundary. Use a historian when dependable industrial collection, compression, quality, event context and long retention are required. Use a general time-series platform where approved analytics or application workloads benefit from flexible development and scale. Decide with requirements for latency, loss tolerance, timestamp authority, quality semantics, backfill, retention, query load, redundancy, cybersecurity and ownership. One system can serve several roles, but every role still needs explicit acceptance tests.

  • Separate control, operational history and analytical consumption responsibilities.
  • Preserve source timestamps, quality and operating context.
  • Design for store-and-forward, gaps, clock errors and recovery.
  • Document authoritative records and consumer limitations.
Similar trend screens do not make platform responsibilities interchangeable.
Text-free comparison of SCADA supervision, historian retention and time-series analytics responsibilities

Similar trend screens do not make platform responsibilities interchangeable.

Decision guide

Platform roleBest fitMain design risk
SCADASupervision, alarms, operator displays and near-real-time control contextOverloading the control environment with broad analytical demand
HistorianDurable industrial history with collection and quality semanticsPoor tag/context governance or untested recovery
Time-series databaseApplication and analytics workloads with flexible developmentAssuming generic ingestion preserves industrial meaning
Archive/exportRegulated or contractual evidence packagesConfusing a snapshot with the operational source of truth

A practical workflow

  1. 01

    Define consumers, decisions, latency, availability, retention and recovery objectives.

  2. 02

    Map sources, clocks, quality semantics, rates, events and network boundaries.

  3. 03

    Assign each platform role and identify the authoritative copy for each use.

  4. 04

    Test normal collection, overload, outage, backfill, failover and query isolation.

  5. 05

    Publish ownership, interfaces, limits, backups, recovery and change controls.

Test the full data path under outage, backfill and recovery conditions.
Text-free plant-data flow showing sources, operational boundary, durable history, analytics consumers and recovery

Test the full data path under outage, backfill and recovery conditions.

Evidence and acceptance

Retain architecture and data-flow diagrams, tag and context ownership, protocol and interface versions, timestamp and quality mapping, rate and retention calculations, compression rules, cybersecurity zones, identity and access model, outage/backfill tests, redundancy evidence, backup and restore results, performance tests, consumer contracts and handover responsibilities.

Recovery is complete only after gaps and quality are reconciled.
Text-free recovery path covering outage detection, buffering, backfill, reconciliation and restored service

Recovery is complete only after gaps and quality are reconciled.

Common mistakes

  • Sending every high-frequency value to every platform.
  • Dropping quality and source timestamps during integration.
  • Allowing analytics queries to affect operational performance.
  • Assuming replication is a tested backup.
  • Leaving tag naming, retention and decommissioning ownerless.

Responsibility boundary

Primary sources

Technical claims and product boundaries were checked against these primary sources. Fact-checked

  1. Guide to Operational Technology (OT) Security, SP 800-82 Rev. 3National Institute of Standards and Technology
  2. ISA-95 Standard: Enterprise-Control System IntegrationInternational Society of Automation

Frequently asked questions

Can SCADA replace a historian?

Some products include historical functions, but suitability depends on retention, recovery, quality, scale and governance requirements.

Is a time-series database safe for control?

A general database must not be assumed to provide the deterministic or safety functions of the control system.

Where should timestamps originate?

Define an authoritative source and clock architecture, then test mapping and drift across the complete path.

Does AutoNexit store live process history?

No. It stores controlled project records and evidence, not historian telemetry.

Related articles

ORG-F08

What Is a SCADA System? Layers, Components, Data Flow, and Security Boundaries

A SCADA system supervises an industrial process by acquiring data, presenting state, managing alarms and trends, and supporting authorized operator actions. A useful design must show each component, trust boundary, data path, failure mode, and operating responsibility rather than reducing SCADA to a screen or server.

ORG-F15

OPC UA vs MQTT: Which Belongs Where in an Industrial Data Architecture?

OPC UA and MQTT solve different parts of an industrial information problem. OPC UA defines interoperable services, information models, security, and client-server or PubSub behavior; MQTT is a lightweight publish-subscribe transport through a broker. Many architectures use both, but only when semantics, topic governance, security, quality, and ownership are explicit.

ORG-F20

Industrial Edge Gateway Selection: Interfaces, Workloads, Security, and Handover

Selecting an industrial edge gateway begins with data sources, destinations, workload, latency, availability, offline behavior, environmental limits, ownership and support—not CPU and protocol logos alone. The accepted system needs a documented security boundary, buffered-data policy, maintainable software baseline and tested replacement procedure.