Replace Metasys. Keep your controllers.
The head-end is the part that ages, licenses and locks you in. The controllers in the mechanical room are the part that works. Indagate replaces the first and leaves the second alone.
What Indagate reads from your Metasys installation
- BACnet/IP and MS/TP objects exposed by your existing controllers
- Point names, units and engineering ranges as they are configured today
- Historical trend data, migrated into the asset record rather than left behind
- Alarm definitions, priorities and routing rules
What it takes over
- Supervisory control: setpoints, commands, overrides and their release
- Scheduling, held against the asset model and executed as supervisory writes
- Trending, retention and query across every asset
- Alarming: conditions, severity, acknowledgement and history
- Graphics, generated from the asset model instead of drawn per site
What stays exactly where it is
- Field controllers keep executing the sequences they were commissioned with
- Safety relays, interlocks and E-stops remain authoritative
- Existing BACnet addressing stays valid — the namespace maps onto it, it does not renumber it
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
Do we have to replace the JCI controllers?
No. Indagate speaks to them over BACnet as a supervisory client. Replacing controllers is a separate decision you can make later, per unit, on its own budget.
What happens to years of Metasys trend history?
It migrates into the asset record, so a trend from before the cutover sits on the same timeline as one from after it. History that cannot be exported from your installation is identified during scoping, before anything is committed.
What happens if Indagate is offline?
Your controllers keep running the sequences they were commissioned with. Supervisory functions — new setpoint writes, schedule changes, overrides, agent actions — pause until the connection returns, and the record shows the gap rather than hiding it.
Scope a Metasys 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.