Ignition Module
The Factry Historian Ignition Module connects Ignition SCADA to Factry Historian. It registers as a historian provider in Ignition, so tags you mark for historization in Ignition are collected by Factry automatically, with no second configuration required.
The module is open-source. Source and issue tracker on GitHub.
What it does: The module uses Ignition's historian provider API to intercept historization requests for tags you configure in Ignition Designer. Those tags are streamed into Factry Historian. New tags or lines added to Ignition later are picked up automatically.
It also works the other way around. Ignition reads history back out of Factry for the Power Chart, tag history bindings, Perspective components, reports and scripting. The read path is not limited to what Ignition wrote: every active measurement in the Historian instance, whichever collector produced it, and the full asset tree are browsable and queryable from Ignition.
The module registers itself in Factry as a collector of type ignition and reports health periodically, so the Ignition Gateway appears on the Collectors page like any other collector.
Version requirements
- Ignition 8.3 or higher.
- Factry Historian v8.2 or higher, because reading data back out relies on gRPC endpoints that v8.2 added, including the asset tree and the collector a measurement belongs to.
What you can use it for
- Ignition as SCADA, Factry as the historian. Replace the SQL tag history provider with a purpose-built time series backend, and keep retention, contextualisation, calculations and events in Factry.
- One history store for several gateways. Multiple Ignition Gateways, one collector each, all writing into the same Historian instance. Reports and dashboards query a single place.
- Non-Ignition data on Ignition screens. Measurements that Factry collects itself over OPC-UA, Modbus, Siemens S7 or REST are trendable in Ignition without collecting them twice.
- Asset-based operator screens. Bind Perspective components to asset properties from the Factry asset tree, so screens follow the plant model instead of tag paths.
- Lab and manual values next to automated tags. Values entered through manual entry forms sit in the same store as Ignition tag history and can be trended together.
More information
- Store and forward, on how data is buffered when Factry is unreachable