For owners & operators
One building, running in parallel. Then decide.
A fault at 05:40 means the supervisory system for the alarm, the historian for the trend, the CMMS for the last repair, and a phone call for what actually fixed it. Every time, by every person. Indagate starts beside what you have, on one building, and builds the record none of those four kept.
Start beside what you already run.
Nothing gets ripped out on day one. The gateway reads the same controllers your current system reads; they keep executing the sequences they were commissioned with. Supervisory writes are granted per site, on named equipment, at a priority you choose — and life-safety priorities are refused at the gateway regardless.
You prove it against a system you already trust, on one building, before anyone says the word portfolio.
What accumulates while it runs.
Every trend, alarm, override, setpoint change and work order lands against the asset it happened to — with who did it and the reason they gave. Your best operator will never fill in a notes field, but they will correct a wrong answer, and that correction is the capture: the thing they know that was never in any document, now on the record.
By the time you decide, the record is where the answer comes from and the old system is just moving signals. Nobody has to win an argument about replacing it.
The question IT will ask first.
Which agent acted on that line in March, under what permissions, and who approved it? Every agent declares its reach before install, is admitted against a named device or refused, and lands every action on the record with the grant that allowed it. The review packet answers the seven questions before the meeting.
What the first ninety days look like.
- Day 1
- Gateway on, read-only. Every device and point on the network, as named, in the asset model.
- Week 2
- First supervisory writes granted on named equipment at a chosen priority. Each one recorded with the actor and the reason.
- Day 90
- Ninety days of decisions, with reasons, that the old system never held — and a choice, made on a record rather than a demo.
Specifics
- Runs beside
- Metasys, Desigo CC, WebCTRL, SCADA and historians — controllers untouched
- Records
- Trends, alarms, control actions, overrides, schedule changes and work orders, with actor and reason
- Exports
- Your points, your history, your records, on a documented schema — while you run it and on the way out
Common questions
What happens to the system we have?
It keeps running. The point of the parallel run is that you never have to switch it off on a promise. You stop needing it when the record is where the answers come from — and that is a thing you notice, not a date on a plan.
What if we stop?
Your points, your history and your records export on a documented schema. You were replacing a system that made leaving expensive. We are not going to rebuild that.
Bring your point list.
Send the point list, the controller inventory and the history you need to keep. We come back with what we would do first on one building, and what stays exactly where it is.