Connecting a Building Management System to IoT: Modbus, BACnet and What to Expect
November 11, 2026 · 5 min read · Etzal Group Team
A commercial building generates a large amount of operational data every minute: chiller loads, supply air temperatures, pump speeds, electricity use by floor. Most of it stays inside the building management system, viewed on one workstation in a plant room. Connecting that data to a wider IoT platform is often cheaper than installing new sensors, because the measurements already exist.
What a BMS does and does not do
A BMS controls and monitors mechanical and electrical plant: chillers, air handling units, fans, pumps, lighting and sometimes lifts and fire systems. It is good at keeping conditions within setpoints.
It is usually weaker at other things that building owners now want:
- Long-term history in a form that can be analysed.
- Comparison across several buildings.
- Combining plant data with occupancy, weather, tariffs and maintenance records.
- Dashboards for people who are not BMS operators.
- Flexible alerts sent to phones.
An IoT layer adds these without replacing the control system.
The two protocols you will meet
Modbus. A simple protocol from the industrial world, common on energy meters, variable speed drives, chillers and generators. Data sits in numbered registers. There is no description attached, so you need the manufacturer's register map to know that register 3027 is active power in kilowatts with a scale factor. It runs over serial cabling as Modbus RTU or over Ethernet as Modbus TCP.
BACnet. A protocol created for building automation. Each data point is an object with a name, a present value, units and a status. A gateway can discover the devices and objects on a network. It runs over Ethernet as BACnet/IP or over serial as BACnet MS/TP.
Many buildings have both: BACnet between BMS controllers, and Modbus down to individual meters and equipment.
A sound architecture
- A gateway on site connects to the BMS network and to field devices. It reads points at set intervals.
- Network separation. The gateway sits between the building control network and the outside. Controllers are never directly reachable from the internet.
- Read first. The initial integration only reads values. Control stays entirely with the BMS.
- Local buffering. Readings are stored during internet outages and forwarded afterwards.
- A platform stores history, runs analysis and serves dashboards and alerts.
Writing back to the BMS, such as adjusting a setpoint, is a later step with its own safeguards.
Before you begin: the survey
Half of the effort is finding out what exists. For each system, establish:
- Make, model and age of the BMS and its controllers.
- Which protocols are available and whether they are licensed and enabled.
- Who maintains the BMS and whether they will cooperate. Their support matters more than any technical detail.
- A points list: what is measured, with names and units.
- Network layout and where a gateway can be placed.
- Meters and equipment not connected to the BMS at all.
Expect gaps. Old buildings have undocumented changes, disconnected sensors and points named in ways only the original installer understood.
Choosing which points to read
Reading everything is tempting and unhelpful. Start from the questions you want answered:
- Energy. Main and sub-meter consumption, chiller power, pump and fan power.
- Plant performance. Chilled water supply and return temperatures, flow, chiller status and load.
- Air side. Supply and return air temperatures, fan speed, valve and damper positions, filter pressure drop.
- Comfort. Zone temperatures, humidity and carbon dioxide where measured.
- Alarms and status. Equipment trips and run hours.
A few hundred well-chosen points serve better than ten thousand unlabelled ones.
Naming is the hard part
Raw point names such as AHU_3_SAT or AI-17 mean something to the installer and little to anyone else. Build a consistent naming and tagging scheme: building, floor, system, equipment, measurement, unit. Apply it to every point as it is mapped.
This is tedious and it is what makes the data usable. Analysis across buildings depends on "supply air temperature" meaning the same thing everywhere.
Checking the data
Do not assume a point is right because it reports a number.
- Compare readings with a handheld instrument on a sample.
- Check units and scaling. A value ten times too large is usually a scale factor.
- Look for flat lines, which suggest a failed sensor.
- Check that timestamps are in one time zone.
- Confirm that meter totals reconcile with the utility bill.
What you can do with it
- Find waste. Plant running outside occupied hours, simultaneous heating and cooling, setpoints that drifted.
- Track efficiency. Chiller plant energy per unit of cooling over time.
- Maintain by condition. Filter pressure drop and run hours replace fixed schedules.
- Detect faults. A valve commanded shut while the coil still cools indicates a leak or a stuck actuator.
- Report. Energy by tenant or floor, and progress against targets.
Security
Building systems were designed for isolated networks and many have weak protection. Do not expose them. Use a gateway that makes outbound connections only, separate the networks, change default passwords, restrict who can reach the gateway and keep its software updated. Agree responsibilities with the building's IT and facilities teams.
When writing back makes sense
Once the data is trusted, limited control from the platform can add value: schedule adjustments, setpoint resets within a narrow band, demand response. Each write should be bounded by limits in the gateway, logged, and reversible by the BMS operator at any time.
Surveying existing systems, connecting them over BACnet and Modbus and building the dashboards on top are part of our IoT and Control projects. If you manage buildings whose data stays in the plant room, tell us what systems they run.
Summary
The data you need is often already in the BMS. Survey what exists, read it through a gateway over BACnet or Modbus, keep control separate, choose points by the questions you want answered, name them consistently and verify them. Add write access later, within limits.
Frequently asked questions
What is the difference between Modbus and BACnet?
Modbus is a simple, widely supported protocol that exposes numbered registers. You need the device's register map to know what each number means. BACnet was designed for buildings and describes each point as an object with a name, units and properties, which makes discovery and integration easier.
Will connecting IoT to the BMS put building control at risk?
It should not, if done properly. Start with read-only access, place the gateway on a separate network segment, and never expose BMS controllers directly to the internet. Writing setpoints from an outside system should come later, with limits and approval.
Do we need to replace an old BMS to get data from it?
Often not. Many older systems support BACnet or Modbus on at least some controllers, and meters and sensors can be added alongside. A survey of what the existing system exposes comes before any decision to replace it.
Related service
WhatsApp AI Chatbot
We build, train, and run a WhatsApp AI agent that answers customers 24/7, qualifies leads, and follows up.
