Blog

Building management system (BMS) maintenance checklist: alarms, sensors and schedules at every site

· Facilities desk

  • bms
  • building-controls
  • multi-site
  • facilities-maintenance
  • checklist

The building management system (BMS) screen in the plant room shows forty-two active alarms. Most have been there since winter, so nobody reads them anymore. One of them is a chilled water valve that stopped responding a fortnight ago. Another is a zone temperature sensor that now reads three degrees low, so the floor above runs colder than anyone asked for while the cooling plant works overtime. The first hot week of summer arrives, and the complaints start on level 4.

A BMS rarely fails all at once. It drifts. Alarms get muted, sensors wander, schedules stop matching the hours people are actually in the building, and the system keeps running just well enough that nobody books the work. The answer is a regular check at every site, with every fault written down as a job.

This checklist is for operators running more than one site with building controls. It isn’t engineering advice. Changes to controls, setpoints and wiring belong with your building management and controls contractor.

Why BMS faults hide

  • Alarm fatigue. When the alarm list is long and old, real faults sit among nuisance alarms and get ignored with them.
  • Sensors drift. A temperature or humidity sensor that reads a little wrong, or sits in a sunny spot or behind a cupboard, makes the plant work to the wrong number without anyone noticing.
  • Schedules go stale. Opening hours change, a floor is re-let, a site moves to weekend trading, or daylight saving starts in the states that use it. The time schedules in the controller stay where they were.
  • Overrides get left on. Someone forces a fan or pump on to fix a problem, then the override stays in place for months.
  • Old panels age quietly. Controllers and network links keep working until a part fails and nobody can find a replacement.

Check these at every site

Have your controls contractor, or a trained member of your own team, work through these and write down what they find:

1. Alarm list. Review every active and recurring alarm. Clear the ones that are fixed, raise a job for each real fault, and ask the contractor to tune or remove nuisance alarms so the list means something again. 2. Sensors. Check temperature, humidity and carbon dioxide sensors against a calibrated reading. Look at where each one sits: direct sun, a supply air vent or a closed cupboard all give false readings. 3. Time schedules. Compare every schedule with the hours each area is actually used, including public holidays and the Christmas period. Check the controller clock after daylight saving changes. 4. Setpoints. Check heating and cooling setpoints for each zone match what you agreed, and that nobody has quietly widened or narrowed them. 5. Overrides. List every manual override and forced point. Remove the ones that are no longer needed, and record why any that stay are still there. 6. Trend logs. Look at a week of trends for supply air, chilled water and zone temperatures. Valves stuck open, fans running all night and zones that never reach setpoint show up here first. 7. Controllers and network. Check controllers are online, batteries and power supplies are healthy, and the controls network runs current software, with a saved copy of the programming. 8. Records. Make sure the operation and maintenance manuals, points list and schematics on site match what is actually installed.

Planning a retrofit? Add a note of spare points, legacy panels and parts that are hard to replace, so the scope is clear before anyone prices the work.

Who does what

  • Controls contractor. Alarms, sensors, schedules, setpoints, programming, controllers and the controls network.
  • [Heating and cooling](/trades/hvac) contractor. The plant itself: chillers, air handling units, fan coil units, valves and actuators that the BMS reports on.
  • [Electrical](/trades/electrical) contractor. Power to controllers and panels, and anything wet or damaged near a switchboard.

Most BMS faults sit between two of these. A zone that won’t hold temperature can be a sensor, a stuck valve or a tired fan, which is why it helps to have each one booked as a job with notes and photos rather than a phone call.

Air movement matters for more than comfort. If your sites are reviewing ventilation for the new exposure standard, our workplace exposure limits checklist covers the site checks. For rooftop plant after a storm, see our hail damage checklist, and after a blackout, our power outage checklist includes checking the controls run their normal schedule.

Running BMS work on one OpsChase board

OpsChase is one AI-powered platform for running maintenance across one site or many. OpsChase isn’t a building management system, and your alarms stay on your BMS. When a person has to attend, the work lands in one place:

  • Whoever sees the alarm or the problem raises a job from their phone, with a photo of the screen, the reading and a note on what is at stake.
  • Jobs are booked to your own team or your contractors. Set your regular contractors per site and per trade, such as the controls firm, the heating and cooling firm and the electrician for each site, so each job goes to the right regular contractor.
  • Faults are sorted by priority across every site, so a failed chilled water valve before a heatwave isn’t waiting behind a nuisance alarm.
  • Each job is tracked until the work is done, then closed with proof of completion: photos and sign-off on the work order.
  • Keep licence, public liability, induction and site-access details on file for each contractor firm through contractor compliance, so the team can check them before booking anyone into a plant room.

With Assets and planned maintenance switched on, BMS servicing, sensor checks, schedule reviews after daylight saving and heating and cooling servicing become planned maintenance, booked at every site on the dates you set. Each controller, air handling unit and chiller keeps its own service history, so you can see what was done and when. Those jobs sit beside your scheduling so you know who is on site before the contractor arrives.

What the manager sees

Across every site, the manager sees one board:

  • Every open BMS and heating and cooling fault, by site, sorted by priority.
  • Who is booked to attend each job, with photos, readings and contractor notes.
  • Which sites are due for BMS servicing and which are up to date.
  • Late jobs showing against your response targets.

For more on running several sites from one view, see multi-site maintenance and facilities maintenance.

Where to start

This week, ask each site for a photo of its current BMS alarm list and a note of any zone that runs too hot or too cold. Book a controls check at the sites with the longest lists before summer load peaks. Then see how OpsChase handles it on pricing, or book a demo with a list of your sites.

Every alarm that matters becomes a job, and every job is on one board until it’s done.

Related on OpsChase

Questions

Who raises a building management system fault?
Whoever sees it: a site manager reviewing the alarm screen, a staff member on a floor that runs too hot, or your controls contractor on a service visit. They raise it from their phone with a photo of the screen and the reading, and the job is tracked until the work is done.
How do BMS jobs book to the right contractor per site and trade?
Set your regular contractors per site and per trade, such as the controls firm, the heating and cooling firm and the electrician for each site, so a drifting sensor or a stuck valve goes to the right firm for that site and that kind of work.
What stays in our building management system?
Alarms, trend logs, schedules, setpoints and programming all stay in your BMS. OpsChase holds the maintenance side: the jobs raised when someone has to attend, planned servicing, and the photos, readings and notes that show each job was done.
What does the manager see across sites?
One board with every open BMS and heating and cooling fault by site, sorted by priority, who is booked to attend, which sites are due for servicing, and any late jobs showing against your response targets.

All articles

OpsChaseOpsChase

Start with the part you need today and add the rest when you’re ready. One site or many.

Book a demo