Skip to content

Tiedonkeruu

Antti Haaraniemi

Process historian or reporting system?

Summary

A process historian and a reporting system overlap: both collect and store process data. A historian is strong at storage and retrieval, a reporting system at what is done with the data. This article sets out the differences and helps you decide whether you need one, the other or both.

When a plant looks for a system to collect process data, two names come up: process historian and reporting system. Both collect data from the automation system and store it. The difference is in the focus, and it decides which one pays off for the plant sooner.

What is a process historian?

A process historian (also data historian or industrial historian) is a database built for storing process data over the long term. Its core jobs are:

  • Collection from automation systems, often through several protocols
  • Efficient storage with compression, so that years of data fit on disk
  • Fast retrieval over long time ranges
  • Interfaces for other systems that fetch data from the historian

A historian is infrastructure. It is good at keeping data safe and available, but reports, analyses and views are often built with separate tools on top of it.

What is a reporting system?

An industrial reporting system starts from the user's need: which reports are needed, for whom and how often. It comprises report templates, scheduling, delivery, calculated values, trends, dashboards and alarm analyses. It needs its data from somewhere: either from storage of its own or from a historian.

Side by side

Process historian and reporting system
Process historianReporting system
FocusStorage and retrievalReports, analysis, views
UserOften other systems and specialistsProduction, energy, maintenance, management
Finished reportUsually a separate tool or add-onCore function
ScopeOften company-wide, many plantsOften one plant or process area

Which one fits you?

  • A historian already exists: a reporting system can read from it. You may not need new storage, only an end to what is now done by hand.
  • No historian, and the need is reports: a reporting system with long-term storage of its own does both.
  • Dozens of plants and a central data architecture: a company-wide historian is a procurement of its own, and reporting is built on top of it.

Where does DataPortia™ fit?

DataPortia is a reporting and analysis system with history storage of its own. It does the core job of a process historian:

  • collection through OPC UA subscriptions; in a load test 10 000 values per second (10 connections × 1 000 measurement points once a second) were all stored
  • storage in PostgreSQL 18 with TimescaleDB, automatic compression after two days (saving more than 90 % of disk space)
  • an adjustable retention period, 24 months by default.

Its focus, however, is on what is done with the data: scheduled reports with your own template, calculation points, trends, dashboards, alarm analyses and local AI analysis.

If the plant already has a historian, DataPortia does not replace it; it can read that history with OPC UA history reads, if the historian offers them through an OPC UA server. The read is gap-based: only the missing periods are fetched.

DataPortia is not a company-wide historian. It reads OPC UA only, it does not serve data onwards as an OPC UA server, and other systems read its data through a read-only REST API.

The same question is answered briefly in the FAQ, and the storage details are on the OPC UA data acquisition page.

Try DataPortia for 30 days with your own data: the trial includes every feature except the HA add-on and commits you to nothing.

Request a 30-day trial Get in touch