Building Management System and IoT: Monitor HVAC and Energy

A building management system controls HVAC well, but it rarely explains why the energy bill went up. IoTITermIoT (Internet of Things)The IoT (Internet of Things) is the network of physical objects with sensors, software and connectivity that collect and exchange data and act autonomously.View profile adds the missing data without replacing it.

Marta runs maintenance for a 12-story office building in Madrid. On the BMS screen everything is green: the air handlers start, the setpoints hold, and there are no alarms. Even so, the July electricity bill came in 18% higher than the year before. It took her three weeks to find the cause. Two air handling units were still on the winter schedule and ran on Saturday mornings, with the building empty. The BMS did exactly what it had been programmed to do. Nobody was checking whether the program still made sense.

That is the gap IoT fills in a building. The building management system keeps control of the equipment. What gets added is a layer that keeps the data for years, compares it with energy use and occupancy, and raises a flag when something works fine but shouldn't be running at all.

This guide is for system integrators, facility maintenance companies, and property managers. It covers what a BMS does and what it misses, which data pays off first, how to read BACnetBProtocolBACnetOpen protocol for building automation (HVAC)View profile and ModbusMProtocolModbusThe most widespread industrial fieldbusView profile without touching the control logic, and which faults show up in the first month of data.

What a Building Management System Does, and What It Misses

A building management system (BMS), also called a building automation system, coordinates the equipment that uses energy: air handling units, chillers, boilers, fan coils, ventilation, and sometimes lighting and elevators. Its job is control. It reads sensors, compares them with setpoints, and drives valves, dampers, and variable frequency drives to hold the temperature and air quality it has been asked for.

It is very good at that job. Controllers run loops measured in seconds, keep working when the network goes down, and are built to last 15 or 20 years. A BMS that never hangs matters more than any report.

What it misses has to do with time and context:

• Short history. Many BMS installations keep trend logs for a few weeks or months, and only for the points someone configured. Comparing this July with last July is often impossible.
• No link to energy use. The BMS knows the air handler is running. It rarely knows how many kWh that cost, because the meters live on a separate system.
• No real occupancy. Schedules are programmed for an assumed occupancy. If the fourth floor has been half empty for two months because of hybrid work, the BMS conditions it anyway.
• Screens built for the plant room. The operator workstation sits in the basement or on one specific PC. A maintenance manager with 30 buildings has no shared view.
• Fault alarms, not waste alarms. The BMS warns you when a pump fails to start. It doesn't warn you when the pump starts at 5 a.m. for no reason.

None of this is a flaw in the BMS. It is a control system, designed to control. Analyzing months of data and managing many buildings at once call for a different tool.

Smart Building IoT: A Layer on Top, Not a Replacement

When a smart building IoT project starts, the temptation is to pitch it as a BMS replacement. It almost never pays off. Replacing the controls of a working installation means construction work, downtime, a new commissioning, and the risk of leaving 600 people without air conditioning on an August Monday.

The setup that works has two layers with different roles:

The IoT layer reads from the BMS and from its own sensors, but it doesn't write to the controls unless someone decides that explicitly, for very specific cases. That separation is what lets a project start without asking the BMS vendor for permission or changing its programming, and it is what reassures the person responsible for the installation.

There is also a regulatory reason to do it now. The EU Energy Performance of Buildings Directive requires building automation and control systems in non-residential buildings whose heating or air conditioning systems exceed 290 kW, and the 2024 revision extends the requirement to systems above 70 kW by the end of 2029. Those systems must be able to monitor, analyze, and benchmark the building's energy efficiency continuously. In Spain, the RITE regulation on thermal installations in buildings carries those requirements. Many BMS installations control well and fall short on the analysis part. An IoT layer covers it.

If the building already has meters or submeters, our guide to energy monitoring systems explains how to organize them. This article focuses on what happens when that data meets HVAC data.

What to Measure: The Data That Pays Off First

You don't need to read all 4,000 points of a large BMS on day one. Five groups of data explain most of what goes wrong.

1. Equipment Status and Schedules

Start and stop events for air handlers, chillers, boilers, and pumps, with timestamps. It is the cheapest data to collect and the one that uncovers the most savings. Equipment running outside its schedule shows up in the first week. So does short cycling, a unit starting and stopping every few minutes, which usually points to a control problem or an oversized unit.

2. Supply, Return, and Setpoint Temperatures

Supply and return temperatures for each circuit, plus the active setpoint, reveal two expensive faults. The first is the forgotten setpoint, the one someone dropped to 19 °C (66 °F) for a meeting and never reset. The second is simultaneous heating and cooling, when one coil heats and another cools the same zone.

3. Electricity Use by Unit or Panel

Without energy data you can't put a price on a fault. You don't need a meter on every machine. One meter on the HVAC panel and one on the main supply deliver most of the value. With 15-minute data you can already see the base load, what the building draws when it is empty at 3 a.m.

4. Air Quality: CO2, Temperature, and Humidity by Zone

CO2 is the best occupancy indicator a building has, and in many places it is also a requirement. Spain's RITE, for example, sets indoor air quality by category: in offices and classrooms (IDA 2), CO2 should stay within 500 ppm of the outdoor level. One sensor per zone lets you ventilate for actual occupancy instead of at a fixed rate, and proves compliance.

5. Occupancy

Presence or people-counting sensors on floors and in meeting rooms. They let you tune schedules and catch floors conditioned for nobody. At Cloud Studio IoT's own office, we measure occupancy with sensors connected to the platform.

Javier, an integrator in Valencia, started this way with a chain of 40 supermarkets. He didn't read a single BMS point in the first month. He installed one meter on the HVAC panel and one CO2 and temperature sensor on the sales floor of each store. That was enough to find 11 stores where HVAC started more than two hours before opening and three where it never stopped because a manual switch was stuck in the on position. That first report paid for the second phase, the BMS integration.

How to Connect: BACnet, Modbus, and Wireless Sensors

Building data arrives by three routes, and most projects use more than one.

Reading the BMS over BACnet

BACnet is the standard protocol for building automation. The most common variant today is BACnet/IP, which runs over UDP on port 47808. Each controller exposes objects (analog and binary inputs and outputs, values, schedules, trend logs) with their properties. A gateway on the building network discovers the devices, reads the objects you care about at the interval you set, and sends them to the platform.

The key is to ask for read-only access. The gateway registers as one more client, polls the values, and writes nothing. For the BMS vendor and the service contractor that makes a big difference: the logic stays untouched, nothing competes with the operator workstation, and you can disconnect it with no effect on the building.

Reading Meters and Equipment over Modbus

Modbus is the protocol of power analyzers, energy meters, many drives, and quite a few chillers. It runs over RS-485 (Modbus RTU) or over Ethernet on port 502 (Modbus TCP). It has no auto-discovery: you need the register map for each device, and that is where most of the integration work goes. A register read with the wrong data format reports power in the millions of kilowatts.

Adding Wireless Sensors

For what the BMS doesn't measure, such as CO2 per room, occupancy, or the temperature of a zone with no sensor, battery-powered wireless sensors are the fastest route. LoRaWANProtocolLoRaWANOpen long-range, low-power LPWANView profile suits buildings well: it gets through concrete floors, one gateway covers several stories, and sensors run for years on the same battery. You don't need new cabling or any work inside the electrical panel.

From the Building to the Cloud

In all three cases the secure pattern is the same. A gateway inside the building reads locally and publishes outbound over MQTTProtocolMQTTThe standard pub/sub protocol of IoTView profile with TLS. The connection starts inside the building, so the firewall on the technical network needs no inbound rules. It is the same principle we describe for industrial plants in OPC UA vs MQTT, and our MQTT broker guide covers the transport.

What the First Month of Data Shows

Smart building projects are usually justified with an estimated savings percentage. What convinces people is the list of specific faults that appears once the data comes together. These are the ones that keep coming up.

Outdated schedules. Seasonal hours, local holidays, or a floor that emptied out and never came off the schedule. You catch them by comparing equipment status with occupancy or, without occupancy sensors, with CO2.

Abandoned setpoints. A setpoint changed by hand for one meeting that stayed that way for months. You catch them by comparing setpoints across similar zones.

Heating and cooling at the same time. It happens mostly in perimeter zones with four-pipe fan coils or in air handlers with both cooling and heating coils. Two valves open at once means paying twice. Elena, technical manager at a hotel in Malaga, found it on the sea-view floor. In the morning the sun heated the facade and the system cooled, while the reheat coil stayed open because of a badly placed sensor. Moving the sensor took one morning.

High base load. What the building draws when it is empty at 3 a.m. Circulation pumps that never stop, exhaust fans, office equipment. One chart of one week shows it.

Clogged filters and degrading equipment. An air handler that takes longer each month to reach setpoint, or a chiller whose consumption rises at the same load. These are trends over weeks, and a BMS with short history doesn't show them.

Fixed-rate ventilation. Rooms ventilated the same at 8 a.m. with two people as at noon with forty. CO2 sensors let ventilation follow occupancy, and it is one of the savings you notice first in winter.

None of these findings needs artificial intelligence. They need several months of data in one place and simple rules that someone reviews. That is why it pays to start with a few useful rules rather than a dashboard of 80 indicators.

Where an IoT Platform Fits Next to the Building Management System

Cloud Studio IoT is a white-label IoT platform for integrators, maintenance companies, and manufacturers. In a building project it takes the data layer. It doesn't replace the building management system or its controllers.

Modbus meters and equipment connect through a software module we install at the edge as a gateway. It reads locally and sends the data to the platform over MQTT with TLS. LoRaWAN sensors arrive through whichever network server the project already uses, such as The Things Stack, LORIOT, or ThingPark. BACnet is not a built-in integration today; when a building needs it, we integrate it for that project.

With the data in place, the rest is configuration: dashboards per building and per portfolio, alarm rules with notifications by email, SMS, WhatsApp, voice call, or push, scheduled reports, and SCADA-style views over each floor plan. The facility hierarchy groups buildings by client, city, or type.

For an integrator, the business model weighs most. With a multi-tenant architecture, each owner sees only their own buildings under the integrator's brand, while the maintenance team sees the whole portfolio. The smart building and facility management pages cover the use cases, and the IoT platform page explains the rest.

Conclusion

A building management system is the right tool to control a building, and rarely the right one to understand how it behaves over months or to manage many buildings at once. The essentials:

• Don't replace the BMS. Add a data layer that reads in read-only mode and can be disconnected with no effect on control.
• Start with five data groups: equipment status and schedules, temperatures and setpoints, electricity use, air quality, and occupancy.
• Read the BMS over BACnet, meters over Modbus, and fill the gaps with wireless sensors, all outbound over MQTT with TLS.
• Go after the cheap faults first: outdated schedules, forgotten setpoints, simultaneous heating and cooling, and high base load.
• A few rules that someone reviews beat a dashboard full of indicators.

If you manage buildings for several clients and want one shared view without touching their installations, talk to our team about your portfolio.

Frequently Asked Questions

What Is a Building Management System?

It is the system that runs a building's technical equipment. It coordinates HVAC, ventilation, and sometimes lighting and other equipment: it reads sensors, compares them with setpoints, and drives valves, dampers, and drives to hold the conditions it has been given.

Does IoT Replace the BMS?

It shouldn't. The BMS controls equipment in real time and should keep doing so. The IoT layer reads its data, stores it for years, combines it with energy use and occupancy, and flags waste the BMS doesn't detect.

Do You Need to Replace Controllers to Connect a BMS to an IoT Platform?

Usually not. A gateway on the building network reads the controllers over BACnet or Modbus in read-only mode and sends the data outbound. The BMS programming stays as it is.

How Much Can You Save?

It depends on the building and how well it is tuned. The most reliable approach is to measure first. The first month of data usually shows outdated schedules, forgotten setpoints, and a high base load, and each one has a cost you can calculate from the building's own consumption.