By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.
Preferences Deny Accept All Cookies
UMH Blog
Historian ·

Historians vs UNS + TimescaleDB | Which option is better?

Traditional Historians excel at providing shop floor insights, but modern architectures like UNS offer more flexibility. With protocol converters, real-time data, and tools like Node-RED and Grafana, UNS can now effectively replace most Historian features.

Historians vs UNS + TimescaleDB | Which option is better?

In this video, we take a closer look at what Historians are good at, and why a Unified Namespace (UNS) might be a better option moving forward. Historians offer great insights into production, but open-source databases often struggle with data insertion, visualization, and data modeling. That’s where the UNS comes in. With tools like Node-Red and Benthos-UMH, a UNS can handle these tasks, and while visualization still has room for improvement, tools like Grafana are making it easier. We also discuss how UNS can effectively model data, making it a strong alternative to Historians.

💡
To dive deeper and learn more about UNS, check out this page.

Prefer to watch instead, we have a mini video series which covers all the components in depth: Watch here

Further Resources:

Share Tweet Share Share Email

Read next

Can Unified Namespace replace your MES?
·

Can Unified Namespace replace your MES?

The MES has been THE place to integrate data on the shop floor for many years, and the UNS challenges this MES-centric approach and pushes it from infrastructure into the application category. Watch this video to know about Alex view.

Share, Engage, and Contribute!

Discover how you can share your ideas, contribute to our blog, and connect with us on other platforms.

Explore the community