Replace the supervisory layer, not the plant.

The automation stack hasn’t been rebuilt since the 1990s. The part that aged worst is the layer on top — the head-end, the historian, the alarm server and the licensing that came with them. That is the part Indagate replaces.

Most portfolios run more than one. Metasys, Desigo and WebCTRL end up in different buildings, bought by different people in different decades, and the only thing they have in common is that nobody can ask all three the same question.

What a cutover looks like

  • Survey: point list, controller inventory, trend history and alarm rules as they exist today
  • Model: your assets built into the namespace, mapped onto existing addressing
  • Read-only parallel run: Indagate beside the incumbent, so you can compare before you commit
  • Commissioned write paths, one system at a time, with the old head-end still available
  • Decommission, once your team has stopped opening the old one

Your knowledge, and your data

Every site Indagate runs accumulates operating knowledge: how your buildings behave, which faults recur, what your operators already know, and what actually worked the last time. That knowledge compounds where it is useful — at your site, on every shift.

And it stays yours. Your points, your history, your records — exportable on a documented schema, for as long as you run the platform and on the way out if you ever stop. You are replacing a head-end that made leaving expensive. We are not going to rebuild that.

Bring your point list.

The first conversation is a survey, not a pitch: what you run, what it costs you, and what a parallel run would take.