Short answer
An existing BMS usually already exposes most of the points a monitoring layer needs, over BACnet, Modbus or a vendor API. What is typically missing is resolution below site level, attribution to tenancy or system, water sub metering and continuous air quality. All of that can be added by reading the BMS and fitting retrofit sensors only where a measurement genuinely does not exist, which means the BMS is neither replaced nor modified.
Start by finding out what you already have
The single most common finding on an integration survey is that the building is better instrumented than anyone believed, and that the data is simply not being read. A BMS commissioned in the last fifteen years is usually exposing hundreds of points that no one has ever queried.
| Category | Usually already present | Usually missing |
|---|---|---|
| HVAC | Temperatures, setpoints, run states, valve and damper positions, alarms | Energy per unit, efficiency as a ratio, filter loading trend |
| Electrical | Main incomer, sometimes floor level | Tenancy and system attribution, power factor, interval demand |
| Water | Occasionally a pulse input on the main | Almost everything: sub metering, night flow, cooling tower make up and blowdown |
| Air quality | CO2 where demand controlled ventilation exists | PM2.5, VOC, continuous logging, room level records |
| Occupancy | Access control counts, sometimes | Anything connected to plant scheduling |
The pattern is consistent: energy and HVAC are partially covered, water is barely covered at all, and nothing is attributed below the level the system was commissioned to report.
How the integration actually works
- Read the BMS. Over BACnet/IP or BACnet MSTP, Modbus TCP or RTU, or a vendor API. Metasys, EcoStruxure, Desigo CC, Honeywell EBI and Forge and the other major platforms all expose points this way.
- Put a gateway on site. An edge gateway does the reading and buffers locally, so a connectivity interruption delays data rather than losing it, and telemetry stays on your network.
- Normalise into one model. Points from different systems and vendors are mapped into a single asset model, which is what makes a mixed portfolio comparable.
- Fill the gaps. Retrofit sensors only where a measurement genuinely does not exist. Clamp on ultrasonic flow meters and split core current transformers fit without breaking pipework or circuits.
- Leave the BMS alone. No configuration change, no new control logic, no risk to a commissioned system. The integration is read only unless you specifically want supervisory setpoint control later.
The objections worth taking seriously
01
Our BMS is old
Age is less of a problem than assumed. BACnet has been standard for a long time and Modbus for far longer. A genuinely closed proprietary system is now rare, and where one exists the fallback is metering in parallel rather than integrating.
What it costsWorth checking rather than assuming. The survey answers it in a morning.
02
IT will not allow it
A reasonable concern and the reason for the edge gateway architecture. The gateway sits on the OT network, communicates outbound only, and buffers locally. Data residency options exist where that matters.
What it costsBring IT into the survey rather than after it. The conversation is much shorter that way.
03
The BMS vendor will not support it
Reading standard protocol points does not modify the system and does not typically affect support. It is worth confirming with your maintainer, and it is a different question from asking them to change configuration.
What it costsA ten minute conversation that avoids a much longer one later.
04
We are planning to replace the BMS anyway
Then layering is even more attractive in the interim, because a vendor agnostic layer survives the replacement. The measurement history continues across the transition rather than restarting.
What it costsDeferring measurement until after a BMS project usually means deferring it by years.
What good looks like at the end
A single model of the estate in which every site is readable regardless of what is installed in it, consumption is attributable below site level, water and air sit alongside energy, and an export for a rating scheme or an assurance provider is a query rather than a project. The BMS continues doing exactly what it did before.
Do we need to replace our BMS to get energy monitoring?
No. In most buildings the required points already exist on a commissioned BMS and can be read over BACnet, Modbus or a vendor API. Retrofit sensors are added only for measurements that genuinely do not exist, most often water sub metering and zone level air quality.
Replacing a working control system to gain an energy view means paying again for control you already have.
Which BMS platforms can be integrated?
Metasys, EcoStruxure, Desigo CC, Honeywell EBI and Forge, along with SCADA systems and standalone IoT, IAQ and pressure sensors. The platform is hardware agnostic with support for more than 130 device types across any protocol.
Does data leave our network?
An on site edge gateway reads the BMS and buffers locally, so telemetry stays on your network and a connectivity gap delays rather than loses data. Data residency options exist where that is a requirement.
Will this interfere with our control system?
Not in a read only integration, which is the recommended starting point. No configuration is changed and no control logic is added, so there is no risk to a commissioned system.
Supervisory setpoint control through the same integration is possible later, as a separate decision with its own change control.
