Replace Desigo CC. Keep your controllers.

A management station priced per point teaches a building to add fewer points. That is the wrong incentive to design a building around, and it is a property of the head-end rather than of your plant.

What Indagate reads from your Desigo CC installation

  • BACnet objects, and Siemens-native points where they are exposed to BACnet
  • 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, classes 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 across every point you care to keep, without a per-point decision
  • Alarming: conditions, severity, acknowledgement and history
  • Client access for as many operators as the site has, not as many as it licensed

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

How does Indagate price, if not per point?

Per site, against what the site runs rather than how many points you dared to trend. Tell us the size of the estate and we will put a number against it before you spend engineering time.

Can we keep the Siemens controllers and field devices?

Yes. Indagate is a supervisory client to them over BACnet. Controller replacement is a separate decision, per unit, on its own schedule.

What happens to our Desigo trend and alarm history?

It migrates into the asset record so history spans the cutover on one timeline. What cannot be exported from your particular installation is identified during scoping, before anything is committed.

Scope a Desigo CC 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.