Skip to content

Building Management System Integration

Utility data tells you what a building consumed. A building management system tells you why. We integrate with any BMS, over whatever secure path the site allows, so both live in the same platform instead of two systems that never talk to each other.

Requires Huckleberry Controls — a live BMS integration

Live equipment readings for a packaged HVAC unit, showing Niagara live data with internal temperature and humidity sensors, effective and configured setpoints, thermostat limits, and on-off states for bypass, occupancy, fan and heating.
Live BMS sensors, setpoints and on/off states, refreshed every few minutes.

Whatever BMS you already run

We are not asking you to replace a working building system, and we are not tied to a single vendor. The platform is data-agnostic by design: the BMS you have is the one we integrate with, and adding a site running something different is a configuration exercise rather than a new product.

Niagara is the system we deploy most, and for Niagara sites we connect to JACE controllers directly — reading live points rather than importing periodic exports. Sensor readings, thermostat setpoints, and equipment states arrive continuously and refresh every few minutes. For cooling, heating, fan, and bypass, that means the current state of the equipment is visible from the same screen as the consumption it produces.

Niagara, whichever badge is on the panel

Niagara is a framework rather than a single product, and it ships under a number of manufacturers’ names. We work with the Niagara lines from Honeywell, Lynxspring, and Schneider Electric, alongside Tridium’s own — the badge on the controller does not change what can be read from it.

That matters more than it might sound. A portfolio assembled over a decade rarely has the same brand in every mechanical room, and being told that half your sites are unsupported is how most integration conversations end. Here they are the same integration.

A secure connection that fits the site

The connection method is chosen per site rather than imposed. Where opening a path from the building network is not an option — which is most of the time — a secure cellular VPN gives us connectivity that is independent of site IT entirely. Where other secure routes are available and preferred, we use those instead.

This is usually what decides whether a BMS integration happens at all. The blocker is rarely the software; it is a network conversation that never resolves. Being flexible about the path removes that conversation, and it means a network reconfiguration at one location does not silently end data collection.

What it unlocks

Live equipment data is the prerequisite for the real-time side of the platform: current demand monitoring, consumption heat maps by day and hour, spike alerts ranked by cost, and multi-sensor equipment history.

It also changes what a consumption anomaly means. Without it, a spike is a number to investigate; with it, the equipment state at that moment is already on screen.

One model for every source

Utility providers, building systems, submeters, and manual entry all land in the same data model. A mixed portfolio — different BMS vendors at different sites, some buildings with no building system at all — reports as one estate rather than as several that have to be reconciled.

Who it’s for

Controls contractors
Surface building system data to stakeholders who are never going to open the BMS itself.
Facility engineers
Equipment state and energy consumption in one view, refreshed continuously.
IT and security
A connection path chosen to fit your constraints, including one that never touches the corporate network.

See it against your own sites

The fastest way to judge this is to point it at a handful of your buildings and see what comes back.

Request a demo