loader

Traditional process data historians have been in use now for decades – before the time of the internet of things!  Originally designed to collect data from industrial sites they formed a representation of the ‘process’ undertaken on the site, keeping a time-series record in a database locally (sometimes referred to as a site historian). 

Eventually businesses became networked, and data was shared with head-office (aka the rise of the enterprise historian).  Today industrial businesses still need to retain a record of their ever-increasing volume of data, and thanks to modern technology this data can be viewed and analysed in real-time.

Most time-series database solutions are now accessible on the cloud, however not all solutions are equal.  It’s important to understand the design limitations and opportunities so you can make an informed decision when choosing how to store time-series data. After all, history shows us that once a customer stores their data in one solution, they are some-what tied to that solution for an extended period of time – flaws and all.  

 

HOW DOES A TRADITIONAL PROCESS HISTORIAN FUNCTION?

HOW DOES DATAHUB+ FUNCTION?

 

When looking for a time-series process historian it’s important to consider cost, speed and reliability as well as future business requirements for in-house advanced analytics and AI.  As computing power and technology have advanced, many traditional process historians are limited by complex hardware infrastructure, which limits storage, capacity and speed.

Ready to discover the power of DataHUB+, get in touch for a demo.

Useful Resources

You might be interested in

Comparison of DataHUB+ and OSIsoft PI

Compare OSIsoft PI System to VROC's DataHUB+ and see how the two stack up against one another

Read Article

DataHUB+ : A Modern Alternative to PI ProcessBook

With Pi ProcessBook retiring, DataHUB+ emerges as a strong contender as a Process Historian and Visualization Tool.

Read Article