What Is a BMS? Building Management System Explained

What a BMS monitors and controls

Exactly what is connected depends on the building, but in a typical GCC commercial or residential tower the BMS covers the following:

• HVAC: chillers or the district cooling energy transfer station, AHUs, FCUs, cooling towers, pumps and ventilation fans, with temperatures, setpoints and time schedules
• Electrical: main panels, generators, UPS and power metering
• Lighting: schedules and occupancy control for common areas, car parks and façades
• Water: tank levels, booster pumps, and leak detection in risers and plant rooms
• Status signals from other systems, such as lifts and access control, which are controlled separately but report into the BMS
• Fire alarm interface: alarm and fault signals from the fire panel. Fire alarm and suppression systems are separate life safety systems with their own approvals, and in the UAE many are also linked to Civil Defence monitoring through the Hassantuk programme, so the BMS reports on them but does not replace them

How a BMS is put together

A BMS is built in four layers, from the sensors in the plant room up to the operator's screen. The protocols matter most when you come to integrate, because a BMS built on open protocols is far easier to connect to other systems than one locked to a single manufacturer's proprietary network.

• Field devices: sensors for temperature, humidity, pressure, flow and CO2, and actuators that move valves and dampers
• Controllers: programmable controllers in plant rooms that run the control logic locally, so plant keeps operating if the network drops
• Network and protocols: open protocols such as BACnet (developed by ASHRAE and published as ISO 16484-5), Modbus, KNX and LonWorks, which let equipment from different manufacturers talk to the system
• Supervisory software: the graphics workstation or web interface where operators see alarms, trends and schedules

BMS versus CAFM

The two are often confused because both deal with building equipment, but they do different jobs. A BMS works in seconds: it reads sensors, switches plant and raises an alarm when a value goes out of range. It knows that a chilled water pump has tripped, but not who is responsible for fixing it, what the contract says about response times, or whether the same pump failed last month.

CAFM works in hours, days and years: it holds the asset register, generates PPM, dispatches technicians, measures SLAs and keeps the service history. It knows the pump's maintenance record and the contractor's performance, but it cannot see that the pump has just stopped unless something tells it. Connecting the two closes that gap.

How BMS alarms feed work orders in a CAFM

In an integrated setup, selected BMS alarms create work orders automatically, instead of relying on a control room operator to phone the helpdesk. The common mistake is connecting every alarm on day one: a BMS can generate hundreds of nuisance alarms a day, and a work order queue flooded with them is soon ignored. Start with a short list of critical alarms and add more once they are trusted. Running hours and meter readings from the BMS can also drive usage-based PPM, servicing a pump after a set number of running hours rather than on a fixed calendar.

For the alarms that are connected, the flow usually runs like this:

• The BMS raises an alarm, such as a pump trip, a high temperature in a server room or a water leak in a riser
• The integration filters it: only alarms on an agreed list pass through, and repeats of the same alarm are grouped rather than creating duplicate jobs
• The alarm is matched to the asset in the CAFM register, which is why BMS point names and CAFM asset IDs need a shared naming convention
• A work order is created with a priority set by the alarm type, which starts the SLA clock and notifies the right trade on mobile
• The technician attends, fixes the fault and closes the job, and the alarm clearing on the BMS confirms the equipment is back within range

Common questions