Traditional process or 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 your 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.  





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 predictive analytics.  As computing power and technology have advanced, the traditional process historian has been limited by its complex hardware infrastructure, which can limit storage, capacity and speed.

Ready to discover the power of DataHUB4.0, get in touch for a free demo.

Useful Resources

You might be interested in

Advancing from Pilot to Enterprise Rollout

Check out our helpful tips that will see the implementation of Industrial Analytics advance beyond the proof of concept phase.

Read Article

Data storage comparison

Compare the differences between data historian, data lake and data warehouse. What's best for machine learning?

Read Article