Replace the tag database, the historian and the alarm server.
The tag database knows the name. The historian knows the value. The alarm server knows something went wrong. None of them knows what the equipment is, so every question that spans them is reconciled by hand. That reconciliation is the job nobody was hired to do and everybody does.
What Indagate reads from your SCADA and historian installation
- Modbus registers and OPC UA nodes, mapped into the asset model
- Existing tag names, scaling and engineering units
- Historian archives, migrated onto the asset timeline
- Alarm conditions, priorities and acknowledgement history
What it takes over
- Supervisory control: setpoints, commands, overrides and their release
- Scheduling, held against the asset model and executed as supervisory writes
- Historisation, retention and query against the asset rather than the tag
- Alarming: conditions, severity, acknowledgement and history
- Work history, recorded beside the telemetry that prompted it
- The reconciliation between all four, which stops being a job
What stays exactly where it is
- PLCs and field controllers keep executing their logic
- Safety relays, interlocks, E-stops and machine guarding remain authoritative
- Existing tag addressing stays valid — the namespace maps onto it, it does not rename it
- Your historian archive comes across rather than being stranded in a system you keep running only to read
Replacing the supervisory layer is not replacing the control layer. Indagate is not a safety-rated controller, and the field controllers you already trust keep doing the job they were commissioned to do.
Common questions
What happens to our existing tag names?
They are carried into the model as attributes, so a tag your team knows by name stays findable by that name while also resolving through the asset it belongs to.
How much historian data can we bring across?
As much as your historian will export. The archive lands on the same asset timeline as live data, so a query can span the cutover without anyone thinking about where the rows came from — and you stop paying to keep a system alive purely so somebody can read 2019.
Do our existing dashboards have to be rebuilt?
Views generate from the asset model rather than being drawn per screen, so most of what a dashboard showed is available without rebuilding it. Anything genuinely bespoke is identified during scoping.
Scope a SCADA and historian cutover.
Bring your point list, your controller inventory and the trend history you need to keep. We will map what moves, what stays and what it takes.