Siemens Desigo Analytics Integration: Turn Your BMS Into a Decision Queue

Photo by Miha Meglic on Unsplash.

Siemens Desigo runs a lot of buildings well. It holds setpoints, executes schedules, and raises alarms exactly as commissioned. What it was never built to do is tell you which of ten thousand trend points actually matters this week, or rank a problem in one building against a problem three sites over. That gap is why so many Desigo estates end up adding an analytics layer on top, and it is worth being precise about what that layer should and should not do, since "analytics" gets used loosely enough to mean almost anything. Our Siemens Desigo integration page covers the mechanics of the connection itself; this article is about the reasoning for adding it, and what changes once the data starts flowing.

What Desigo gives you, and where it stops

Desigo is a genuinely strong control layer. It speaks BACnet natively, carries a rich object model that means something at the point level, and runs schedules and sequences reliably across both Desigo CC and the classic estates that came before it. Most complaints about a Desigo installation are not really complaints about Desigo. They are a facilities team buried in trend logs nobody has time to read, or a supervisor screen that shows everything and prioritizes nothing.

That is the edge Desigo was never built to work at. Analytics and cross-site prioritization sit outside a control system's job everywhere, not just at Siemens. A BMS is built to run one building correctly, not to weigh a sticking valve in Malmö against a drifting chiller three sites away and tell you which to fix first. Ask a Desigo estate to do that and you get more screens, not more clarity. Desigo CC's own trend and reporting tools are useful for exactly what they were designed for: showing you what a point did. They were not designed to tell you why it matters, or what else in the building moved at the same time.

Reading Siemens Desigo BACnet data, without touching control

None of this requires touching anything Desigo controls. BACnet is the native language on almost every Desigo installation, and OPC UA increasingly sits alongside it wherever a site has bridged Desigo into a wider industrial or IT data layer. Both protocols expose points for reading without granting write access to the control loop, which is the property that makes an analytics layer possible without a controls project.

An analytics layer built correctly reads those points passively. It takes no command authority and pushes no setpoints; it never sits in the safety chain. The FrostLogic Edge Agent installs on the existing Desigo management PC, or wherever the BACnet or OPC UA network is reachable, and from that point forward it is ingest only. There is no rip-and-replace and no controls contractor to bring in. Whatever is already running the building keeps running exactly as it did before.

That distinction matters more than it sounds. Plenty of BMS upgrade projects stall because they ask a facilities team to trust a new system with control before it has proven itself with visibility. Read-only skips that argument. Desigo keeps running the building. The analytics layer just watches, and because it never asks for write access, getting it approved rarely requires the same sign-off chain as a controls change.

Getting a Desigo estate connected

In practice there are a handful of routes in, depending on how the estate was built. A Desigo system with BACnet exposed on the management network is the simplest case: the Edge Agent reads the points directly and starts syncing, often the same day it is installed. Where a site already runs a cloud-connected Desigo deployment, the connection can go through an API instead, which sometimes means data flows before the agent is even needed on site.

The harder case is the estate everyone assumes is too old to bother with: commissioned a decade ago, licence lapsed, nobody left who remembers the original controls contractor. That estate is still readable. If the BACnet network is there, a PC that can reach it is usually enough, and the lapsed licence stays exactly as lapsed as it was. None of these routes ask Desigo to change how it runs the building.

What a Siemens building analytics layer adds on top

Once the data is flowing, the interesting part starts. FrostLogic Explore runs six detection methods against Desigo's own points: statistical baselines, forecast residuals, pattern and seasonality matching, cross-signal correlation, drift detection, and physics constraints, then reconciles what each one finds rather than trusting any single method on its own. Forecasting adds confidence bounds to every prediction, so an estimate comes with a stated margin of error instead of false precision. Continuous compliance checks the same data against BREEAM, LEED, and Nordic Swan criteria on an ongoing basis, rather than in the usual scramble before an audit.

None of that stays confined to a single building. Run it across a Desigo estate, or a portfolio mixing Desigo with other vendors, and every finding lands in one ranked queue instead of ten separate dashboards. That is the part a control system was never going to give you, however good its supervisor screen looks, and it is the part that makes a mixed-vendor portfolio manageable from one seat instead of one login per building.

A worked Desigo example

Here is what that looks like on an actual point. A supply-air temperature on a Desigo-controlled AHU starts running half a degree warm. Nothing alarms. It sits well inside any threshold Desigo would flag, and on a supervisor screen it looks like noise.

Statistics barely notices, since half a degree sits inside normal variance. Drift detection catches the slope anyway: the slow, directional creep a threshold rule is built to ignore because no single reading ever crosses a line. Cross-signal correlation shows the heating valve commanding more flow to compensate, exactly the kind of relationship a single-point alarm cannot see because it only ever looks at one signal at a time. Severity scoring weighs the persistence of the drift against the rising energy draw and flags it as material rather than cosmetic, the difference between something worth a look and something worth a ticket.

What reaches the engineer is not forty raw threshold alerts scattered across a shift log, each one true but none of them useful on its own. It is one line: "AHU-3 heating valve drifting, approximately 4% energy impact, investigate this week." Desigo saw the temperature the entire time. It just had no way to say what the temperature meant, and that is the whole difference between a trend log and a decision.

Other BMS? Same approach

None of this is specific to Siemens. The same read-only pattern applies to any BMS speaking BACnet, Modbus, or OPC UA, which covers most of them; our guide to BACnet vs Modbus vs OPC UA breaks down which protocol you are actually dealing with and what that means for getting data out cleanly. Running a mixed estate, Siemens in some buildings and something else down the road? The full list of supported integrations covers Schneider, Honeywell, and the rest, all reading into the same model and the same queue, so a portfolio never needs one tool per vendor.

FAQ

Does adding analytics to Desigo require touching the control logic?
No. The connection is read-only from end to end. It does not modify sequences, setpoints, or alarm logic, and it never sits in Desigo's safety chain, so there is nothing for a controls contractor to sign off on.

What protocols does this read from a Desigo estate?
BACnet natively, since that is what almost every Desigo installation already speaks. OPC UA where a site has bridged Desigo into a broader industrial or IT data layer, which is increasingly common on newer or converged sites.

Does this replace Desigo CC or its built-in analytics?
No. Desigo CC keeps doing what it already does, running the building and showing its own trend data. Explore reads the same points read-only and adds detection, forecasting, and ranking on top, without removing anything from the existing supervisor.

Is there a CMMS overlap?
No. Explore is not a CMMS. It surfaces and ranks what is wrong; opening a work order and dispatching a technician stays with whatever maintenance system the team already runs.

Which Desigo generations does this work with?
Anything that exposes its points over BACnet or OPC UA, which in practice covers current Desigo CC installations and the classic estates commissioned years before it, licence status notwithstanding.

Does this need new hardware on site?
Usually not. The FrostLogic Edge Agent typically installs on the existing Desigo management PC or a server that can already reach the BMS network, and most installs take an afternoon rather than a project.

How long before findings start showing up?
Most estates see first findings within the first week of data flowing, though the queue gets sharper as more history accumulates and the model learns what normal looks like for that specific building.

Where is the data hosted?
EU-hosted infrastructure on Hetzner, GDPR-native by default. Nothing about Desigo's own data residency or network setup changes as a result of connecting it.