BMS Fault Finding for HVAC/R Technicians

Sometimes it is the BMS. Sometimes it is not.

On commercial sites, it is common to hear someone say:

“The air conditioning is not working. It must be the BMS.”

Sometimes that is true. A lot of the time, it is not that simple.

Most larger HVAC and refrigeration systems now have some level of BMS control or monitoring. Air handling units, chillers, pumps, packaged units, VRF systems, exhaust fans and cold rooms may all be connected back to a Building Management System.

That can be useful, but it can also cause confusion.

The BMS might show a unit running, but there may be no airflow. It might show a valve open, but there may be no chilled water flow. It might show a room temperature, but the sensor may not be reading the actual occupied space correctly.

The BMS gives you information. It does not always give you the full answer.

Start with command and status

A good starting point is one simple question:

Is the BMS asking the plant to run, and is the plant actually responding?

That question can save a lot of wasted time.

A BMS command is what the system is asking for. A status is what the system believes has happened.

For example, an AHU may show the run command as on, but the run status may still be off. That usually means the BMS is asking the unit to run, but the unit has not proven operation.

The fault could be a local VSD issue, fire trip, isolator, control fuse, safety circuit, overload, failed relay, local switch position or wiring issue.

In that case, saying “the BMS is not running the unit” is probably wrong. The BMS may already be doing its part.

A valve at 100% does not always mean cooling

This is one of the most common traps.

A chilled water valve might show 100 percent open on the graphics, but that does not prove chilled water is flowing through the coil. It may only mean the BMS is sending a 100 percent signal.

The actuator could have failed. The valve spindle could be seized. The actuator may be driving the wrong way. The coil could be air locked. The strainer may be blocked. The chilled water pump may not be maintaining flow.

The BMS command is only one part of the story.

You still need to check pipe temperatures, airflow, valve movement, water flow and supply air temperature.

If the area is hot, prove the basics first

When a tenant or client reports a hot area, do not start by blaming controls. Start with the space.

Check the actual room temperature with your own meter and compare it to the BMS reading.

If the BMS says the room is 27°C, but your meter says 23°C, the issue may be the sensor, not the air conditioning.

The sensor could be poorly located, affected by heat, out of calibration, incorrectly scaled or mapped to the wrong area.

If the sensor is wrong, the control response will be wrong.

Once the temperature reading is confirmed, check the basics:

Is the system scheduled on? Is the setpoint correct? Is the unit in the right mode? Is there a cooling demand? Is the fan running? Is the valve opening? Is the supply air temperature dropping? Is chilled water available? Is airflow correct?

A BMS can help guide the fault finding, but it does not replace normal HVAC checks.

Packaged units and VRF systems can be misleading

Packaged units and VRF systems often have their own local controls.

The BMS may only provide an enable, setpoint, mode command or fault signal. The unit’s own controller still manages compressors, inverter operation, reversing valve, fan control, defrost, safeties and protection timers.

This can lead to confusion.

The BMS may be asking for cooling, but the local controller may be locked out. The BMS may be sending a setpoint, but the wall controller may have another value. A VRF system may have a master indoor unit controlling mode for the group. A unit may not respond immediately because of compressor delay timers or internal safeties.

This is why the graphics page should be treated as a starting point, not the final answer.

Cold room alarms need context

A cold room high temperature alarm does not automatically mean the refrigeration plant has failed.

It could be caused by doors being left open, warm stock being loaded, defrost operation, iced evaporators, failed fans, damaged door seals, probe location, sensor issues or an actual plant fault.

The alarm tells you the temperature went outside the expected range. It does not always tell you why.

This is where trend logs are useful. They can show what happened before you arrived.

Did the temperature rise during defrost? Was the door open for a long period? Did the room recover by itself? Was there a plant fault at the same time? Has the issue happened before?

The trend often tells a better story than the alarm alone.

Trends are useful, but they are not perfect

BMS trends can be very helpful, especially for intermittent faults.

They can show room temperature, setpoint, valve position, fan status, chilled water temperature, alarms, door openings and plant operation over time.

But trends still need to be checked against the real site conditions.

A trend showing fan status on does not prove airflow. A trend showing valve position at 100 percent does not prove water flow. A trend showing temperature does not prove the sensor is accurate.

BMS data is useful evidence, but it still needs to make sense on site.

Be careful writing “BMS issue”

Service reports matter.

Writing “BMS issue” when the BMS has not been proven faulty can create confusion and unnecessary arguments between contractors.

A better report explains what was checked.

Example 1:

BMS run command was active, however AHU run status was not proven. Local VSD was found in fault, preventing fan operation. Fault appears downstream of BMS control.

Example 2:

BMS cooling demand was active and chilled water valve was commanded open. Supply air temperature remained higher than expected, indicating cooling was not being achieved despite BMS demand. Recommend further checks to confirm chilled water flow, valve operation, coil condition and airside performance.

That wording is much clearer. It explains what the BMS was doing, what the plant was doing, and what should happen next.

The main takeaway

A BMS-controlled site is still an HVAC/R site.

The equipment still needs airflow, refrigerant, water flow, electrical supply, safeties, working sensors, correct valve operation and proper commissioning.

The BMS is only one part of the control chain.

When fault finding, ask:

What is the BMS asking for?

What is the plant actually doing?

Does the sensor reading make sense?

Is the field device physically responding?

Does the trend history support the complaint?

The best HVAC/R technicians do not need to become full-time controls programmers.

But understanding the basics of BMS commands, statuses, sensors, trends and alarms makes fault finding faster, reporting clearer and call-backs less likely.

Sometimes the BMS is the issue.

Sometimes it is simply showing you where the real issue is.