Migrate IO-Base
to Factry
IO-Base was developed by Teréga solutions to support their multi-energy infrastructure operations and digital-twin use cases. Factry Historian is our core business: built for industrial operations that need real-time process insight, quality monitoring, and AI-ready data across continuous and batch environments.
Built for gas grids not plants, IO-Base once sufficed, but today its generic model holds your operations back.
Not designed for manufacturing
IO-Base was not created for plant-floor visibility, production analysis, or operational decision-making.
No built-in process context
IO-Base stores raw time-series data only. It offers no native detection of states, downtime, or process events. All operational context must be added manually.
Custom work needed
To use IO-Base in a factory, teams must build their own models, hierarchies, KPIs and domain-specific logic on top of the platform. Nothing production-ready is included out of the box.
No plant visibility
IO-Base focuses on infrastructure-level digital twins and multi-energy system optimisation. It does not provide operator views, quality insights, downtime analytics or line performance dashboards.
With a decade of experience
Migration without disruption
Switching from IO-Base doesn’t have to be risky. With Factry Historian we make sure we focus on continuity first. Your plant keeps running while data, events and dashboards move over step by step.
Replace Legacy Historians
Switch from costly, rigid systems to Factry Historian. Our scalable, user-friendly, and open solution integrates effortlessly with your existing infrastructure. It’s the smart choice for modernizing your data strategy.
Modern architecture, zero fuss
Factry Historian is modular, scalable, and easy to deploy across on-prem, central, or cloud environments. Let’s skip the consulting army and start small!
Seamless migration
Use our enhanced Grafana plugin to browse assets, query time ranges, or view batch-specific data. Thanks to Factry dashboards become dynamic tools, not static reports.
FAQs
We have (most of) the answers! Let us know if you still can’t find what you’re looking for.
Yes, we offer a guided onboarding for Factry Historian for a limited period and easy opt-out.
Yes, really! There are no artificial limits to tags or users in Factry software. Of course, the infrastructure on which the software is running should be able to support the load.
FactryOS integrates with various ERP systems, such as SAP, Dynamics 365 Finance and Operations, Monitor, Navision, QAD, LISA, etc. If you have another ERP system, we implement a new interface with it.
Factry Historian integrates with various systems for analytics & visualizations (Seeq, Grafana, Power BI) and data egress (MQTT forwarding, Parquet files). Have a look at our Integrations page.
Factry provides a ticketing helpdesk, phone support during CET business hours, and optional 24/7 premium support. Additionally, there’s detailed documentation, 24/7 monitoring of system and software health, and software updates.
Both are possible. Factry Historian and FactryOS can run practically anywhere with a Linux OS.
We have a built-in integration with Grafana via an official datasource plugin. You can browse asset hierarchies, trend time-series, overlay events, and build dashboards, all natively. Data is also accessible via REST API, MQTT, Parquet exports, or direct database connections, enabling integration with any BI/Analytics tool (e.g. PowerBI, Tableau, Python, Seeq).
Factry Historian connects to a wide range of industrial sources like PLCs, DCS or SCADA systems through standard protocols such as OPC‑UA, OPC-DA, Modbus TCP, and MQTT (JSON/SparkplugB), and integrates with virtually anything through its open API. Whatever systems you use, Factry makes it easy to collect and centralize your data on your terms. Have a look at our Integrations page.