On this page
A building management system (BMS) is the supervisory layer for the services in a building: cooling and heating, ventilation, lighting, meters, and the alarms from fire and access where those systems are connected. It does not replace each machine’s own controller. It watches them, schedules them, and puts the faults in front of one operator. This sheet says what that looks like in practice.
What to list before integration starts
- The plant that already exists: chillers, air handling units, fan coil units, pumps, and the lighting panels.
- The protocol each one speaks. BACnet, Modbus, and KNX cover most of a commercial building. A unit with a closed protocol needs a gateway, and that gateway has to be in the design.
- Who is on duty. A web dashboard is only useful if someone is responsible for the alarm it raises.
- What “used less energy” will be judged against. Meters have to be in the design, not added as a screen with no inputs.
What the BMS is, and is not
| System | The BMS usually does | The BMS should not do |
|---|---|---|
| HVAC | Schedules, setpoints, and fault display for chillers, AHUs, and FCUs | Replace the chiller’s own safety controls |
| Lighting | Time schedules and occupancy commands | Be the only way to turn a light on if the network fails |
| Energy | Read electrical and thermal meters, and show where the load goes | Invent savings without meters to compare against |
| Fire and access | Display their alarms and, where agreed, release doors or stop fans | Replace the fire alarm panel. Life safety stays on its own system |
PSS integrates plant over BACnet, Modbus, and KNX onto one supervisory platform, with web dashboards and an alarm list. The point of the screen is that a failed pump, a stuck valve, or a chiller that did not start is visible when it happens, not at the end of the month on a bill.
Schedules are the quiet saving
Most of the energy a BMS saves is unglamorous: air handling that starts before occupancy and stops after it, lighting that follows the same clock, and setpoints that are not left at commissioning values forever. None of that works if the time schedules are bypassed with a local hand switch and nobody puts them back. The dashboard should show when a point is in hand, not only when it is in alarm.
Practical BMS design and handover notes
- Agree the points list. For every plant item, define command, status, setpoint, measured value, alarm, units, and update rate. A protocol connection without a points list is not an integration.
- Define the cause-and-effect. Document what a fire signal, high temperature, failed pump, or loss of communication should do. Keep life-safety decisions on the dedicated safety system.
- Protect the management network. Use separate networks or VLANs, named accounts, backups, and controlled remote access. Do not expose a controller directly to the public internet.
At handover, test points in both directions: command a fan and verify its feedback, change a setpoint and verify the plant response, unplug a communication path and confirm the right alarm appears. Store the graphics backup, controller programs, address list, and alarm matrix with the as-built drawings.
Common problems and how to fix them
The graphic is green and the room is hot
The point on the screen is a command or a stale value, not a measured temperature. Check the sensor, the controller’s communication status, and the age of the last reading. A graphic with no “last update” time hides a network that stopped an hour ago.
Hundreds of alarms, every morning
Plant that is off overnight is being alarmed as failed. Suppress alarms for equipment that is scheduled off, and keep the real faults. An alarm list nobody reads is the same as having no BMS.
A new chiller will not appear on the system
Its protocol or its register list was never agreed. Ask for the points list before the chiller is ordered. Retrofitting a gateway after installation costs more than specifying BACnet or Modbus in the tender.
Frequently asked questions
Does a BMS replace the fire alarm?
No. The fire alarm detects and evacuates on its own panel. The BMS may display that alarm and shut down fans or release doors, under a written cause-and-effect, but it is not the life-safety system.
What is BACnet?
A protocol made for building systems, so controllers from different makers can share points. Modbus is the other protocol you will meet constantly, especially on meters and drives. KNX is common on lighting and room controls.
Can operators use it from outside the building?
Yes, if the web dashboard is published on purpose, with accounts and a separated network. An open port on the BMS is not remote access. It is an exposed controller.
Talk to PSS about the building
PSS designs and integrates building management systems for HVAC, lighting, metering, and alarms. Contact the PSS team to book a first site survey.
