David Dierickx on , updated
Before we let the big ones fly, Factry Historian’s v6.4 release marks a product update focused on perfecting the functionalities you’ve grown to depend on.
At the heart of this new v6.4 release is the Collector Auto-Update feature, bringing notable efficiency improvements and time savings for Factry Historian Administrators, especially for those overseeing extensive networks of collectors.
Instead of manually updating each collector individually, which can be time-consuming, the Auto-Update feature automates the process, ensuring all collectors are always up-to-date with the latest features and patches.
The 6.4 release introduces a number of enhancements to the Factry Historian portal, aimed at improving user experience. One is the ability to batch update alerts, equipping users with a more efficient way to manage notifications across their systems.
Previously, adjusting alert settings for multiple collectors required navigating to each one individually. From this update onwards, users can apply changes to alert settings across all relevant collectors simultaneously.
This means that tasks which used to entail hundreds of clicks, can now be completed with just a few. You’re welcome!
Furthermore, the addition of Disk IO monitoring enhances system performance insights by improving visibility into disk health and usage. It now allows for setting custom thresholds, enabling proactive management.
As we continue to refine Factry Historian, we’re already planning future updates that will include more advanced features, such as Asset Templating.
Moreover, the upcoming Grafana Data Source improvement (to be launched soon) promises to bring a significant enhancement to your data analyses.
For instance, you’ll be able to merge live and event data for a unified view of metrics, enabling straightforward comparisons of batch performances against real-time data. This enhancement simplifies identifying trends and anomalies, eliminating the need for complex SQL queries or manual data handling.
We’re calling on all clients to test-drive and share your thoughts. Join us as we refine this advancement to serve a wide range of operational needs.
As a Data Engineer at Factry, I often face the challenge of guiding industrial companies along their Overall Equipment Effectiveness (OEE) journey. These projects have provided me with some interesting experiences and valuable insights, and I’m eager to share what I’ve learned so far.
Being part of Factry’s Data Engineering team means we’re spending a lot of time providing customer support and fixing specific issues in our clients’ setup. We’ve noticed that we’re frequently being asked similar questions and spend quite a bit of time helping users fix similar errors. In this blogpost, we’ll be going over some common OPC-UA and time synchronization errors and how to fix them.
When information is trapped in isolated systems across the production floor, getting valuable insights is increasingly difficult, and integration becomes fragile. The result? Wasted time, missed opportunities, and inefficiencies that eat away at the bottom line. In this article, we’ll explore the real costs of data fragmentation and how Factry Historian can bring clarity and efficiency to your operations.
