How to specify a building management system (BMS)

1. What a BMS does — and what it does not

A building management system monitors and controls the building’s services from one place: air handling and chilled-water plant, ventilation, energy metering and often lighting, with alarms, trends and reports on top. It connects to other systems — a chiller’s own controller, a VRF system, power meters — and shows them alongside the rest. A BMS may monitor the fire alarm system, but it does not replace it: life-safety systems stay independent and are governed by their own standards.

2. Fix the scope before the point count

List every system the BMS will control, and every system it will only read. For each, name who supplies it and who owns the controls. The most common cause of dispute on site is a piece of plant — a chiller, a packaged unit, a VRF outdoor unit — that arrives with its own controller while the specification assumed the BMS would control it directly. Decide on day one whether each item is controlled by the BMS or integrated through a communication link.

3. Count the points the right way

A BMS is sized in input/output points. There are four kinds: analogue inputs (temperatures, pressures, humidity, CO₂), analogue outputs (valve and damper positions, fan speed), digital inputs (status, alarms, filter switches) and digital outputs (start/stop commands). Count them equipment by equipment: for each air handling unit, pump or fan, write down every sensor it needs and every command it must receive. Add spare capacity for future points — a common practice is to specify spare I/O and spare controller capacity rather than discovering at commissioning that the panel is full.

4. Network architecture and open protocols

Most systems follow the same layers: field controllers close to the plant, network controllers that join them, and a supervisory server or workstation for operators. What matters for the owner is that the layers talk through open protocols, so a different contractor can service or extend the system later. The standard for building automation is BACnet (ANSI/ASHRAE 135, also published as ISO 16484-5), used over twisted-pair serial (MS/TP) or over Ethernet (BACnet/IP). Modbus is the common protocol for meters and for much packaged equipment, and is normally brought in through a gateway or a native driver. Specify the protocols by name, and require the supplier to provide the protocol documentation for every device that is integrated.

5. Graphics, alarms, trends and reports

State what the operators will see and do, not only what the system contains:

• Graphics — a floor-plan and plant schematic for each system, with live values and the ability to override.
• Alarms — priorities, who is notified, how an alarm is acknowledged and how long records are kept.
• Trends — which points are logged, at what interval, and for how long; trend data is what makes fault-finding and energy analysis possible.
• Users — roles and permissions, so that a technician and a manager see and can change different things.
• Reports — energy, runtime and alarm summaries on a schedule.

6. Write the sequence of operations

The sequence of operations is the behaviour of the building, written in words: how an air handling unit starts, how the supply temperature is controlled, what happens on a high-pressure alarm, how the chiller plant stages up and down. It is the document the programmer writes from and the commissioning engineer tests against. A specification without it leaves the behaviour to the programmer’s judgement.

7. Commissioning and handover

• Functional testing of every sequence against the written specification, with a signed record.
• An as-built point list and network diagram.
• A backup of every controller’s program and of the supervisory database, handed to the owner.
• Operator training, and operation and maintenance documentation.
• A clear statement of warranty and of who services the system afterwards.

8. Local conditions worth designing for

Plant rooms are warm, humid and dusty, and mains quality varies, so check the ingress protection of enclosures and put controllers and network equipment on a clean, backed-up supply. Where the system will be reached remotely, treat the network as a security boundary: separate it from the office network, control remote access and plan updates.

Questions to ask any BMS supplier

• Which open protocols are supported natively, and which need a gateway?
• Who can program, service and extend the system after handover — and what is licensed?
• What is included in the price: graphics, trend setup, sequences, training, documentation?
• What spare capacity is included in each controller?
• How is the system backed up, and who holds the backup?