Blog
Our Insights
Factry closes the gap between human insight and machine precision, ensuring both work together at their peak potential.

What is an Industrial Data Historian
What an industrial data historian actually does, how it differs from a generic database, and what separates a modern, open architecture from the legacy systems still running most plants.
Usman Khalil

Factry Historian v8.2: Built to plug in, built to hold up
This release centers on a complete rebuild of the REST API with lots of stability optimizations to improve and performance under load. There are also refinements to event and calculation workflows under the hood. All this results in noticeably faster asset trees, richer event detail and a more informative homepage.
Usman Khalil
.png)
Factry Historian + Ignition: configure once, collect forever
The Factory Historian Connector for Ignition is available now! Mark a tag in Ignition once —> Factry Historian picks it up automatically. No duplicate setup, 30ms query latency, and your data open to any tool.
Usman Khalil
.png)
Ignition v8.3: Ignition built the door with the new API. Here’s what walks through it.
"Ignition v8.3 introduces a new public API that enables module developers to implement their own historians, making Ignition a platform for building historians." Here's what that means for you.
Usman Khalil

Batch Analysis: A Practical Guide for Process Manufacturers
What batch analysis actually means, the methods teams use to compare and improve batches, and the one prerequisite most guides skip that decides whether any of it works.
Usman Khalil

Does your SCADA do two jobs at once?
SCADA historians are designed for operational access ie. high-frequency tag storage, real-time trend views, alarm history. They do that job well. They're not designed, however to handle long-term analytics, cross-system context, data access for teams outside the OT environment. That's a different job with different requirements.
Usman Khalil
.png)
Root Cause Analysis in Manufacturing: Why It Takes Hours, Not Twenty Minutes
Root cause analysis methodology takes twenty minutes. Finding the data to run it takes the other three hours. Here's why, and what actually fixes it.
Usman Khalil
%20(1).png)
Data Unification: How Three Industrial Giants Solved a Costly Problem
How three fermentation and food & beverage giants replaced fragmented OT and IT systems with one unified data layer, and what became possible once they did.
Usman Khalil
.png)
How manufacturers are cutting their energy bill without guessing
Most factories already monitor energy at the site level. Rising energy prices mean that's no longer enough. This guide walks through how food manufacturers are moving from total-consumption monitoring to batch-level energy intelligence: what to meter, how to connect it to process data, and which KPIs actually drive action.
Usman Khalil
