How to Prevent Building Automation System Alarm Fatigue

A building automation system is supposed to help facility teams identify problems quickly. But when the BAS generates hundreds of repetitive, low-priority, or unnecessary notifications, alarms can start having the opposite effect.

This is known as building automation system alarm fatigue.

When operators see the same alarms every day, receive alerts for conditions that do not require action, or get flooded with notifications after a single equipment failure, it becomes harder to identify the alarm that actually matters.

For commercial buildings, hospitals, schools, manufacturing facilities, warehouses, and other large properties, poorly managed building automation system alarms can contribute to slower response times, overlooked equipment problems, unnecessary service calls, and avoidable HVAC downtime.

Preventing alarm fatigue requires more than deleting alarms. The goal is to make sure every alarm provides useful information and directs the facility team toward a meaningful action.

What Is Building Automation System Alarm Fatigue?

Alarm fatigue occurs when facility personnel are exposed to so many BAS alarms that the alerts begin losing their effectiveness.

Eventually, operators may:

• Ignore recurring alarms
• Automatically acknowledge alarms without investigating them
• Have difficulty identifying high-priority problems
• Miss the first alarm that caused a larger equipment failure
• Become accustomed to systems continuously operating in an alarm state
• Spend excessive time investigating conditions that do not require immediate action

The problem is not necessarily the total number of points monitored by the BAS. A large facility can have thousands of sensors and operating points without creating alarm fatigue.

The real issue is how many conditions are configured to interrupt someone and demand attention.

“When we walk into a facility with a long list of active alarms, one of the first things we look at is how many of those alarms actually require somebody to do something. If operators see the same warnings every day, eventually those warnings stop getting their attention.”

Choice Mechanical Services Service Manager

A BAS should collect a tremendous amount of information. That does not mean every abnormal value needs to become an alarm.

Not Every BAS Notification Should Be an Alarm

One of the most important questions to ask when evaluating BAS alarms is simple:

Does someone actually need to take action when this condition occurs?

If the answer is no, it probably should not be configured as an operator alarm.

Many conditions are better handled as:

• BAS events
• Trend data
• Maintenance notifications
• Fault detection and diagnostics findings
• Dashboard alerts
• Work orders
• Historical logs

For example, a temporary temperature deviation in an ordinary office may be useful information, but it may not require a technician to respond immediately.

A chilled-water pump failure during occupied cooling operation is different. If that pump failure threatens the operation of the entire chilled-water system, the facility team needs to know about it quickly.

“A BAS can collect thousands of points of information, but that doesn’t mean every point needs to create an alarm. We want alarms to tell the facility team that there is a condition they need to investigate or act on.”

Choice Mechanical Services Service Manager

Separating informational events from actionable alarms can immediately reduce unnecessary alarm traffic while preserving the valuable operational data collected by the BAS.

Common Causes of Building Automation System Alarm Fatigue

Common BAS Alarm Problems and What to Check

Alarm Problem	What You May See	What to Investigate
Alarm threshold too close to normal operation	Temperature, pressure, humidity, or flow repeatedly crosses the alarm limit	Alarm setpoint, normal operating range, sensor accuracy, and system stability
Insufficient deadband	Alarm repeatedly activates and clears around the same value	Deadband, sensor noise, control-loop stability, and equipment operation
No startup delay	Fan, pump, boiler, or chiller alarms during normal startup	Equipment startup time, proof timers, and alarm persistence settings
Incorrect operating-state logic	Flow, pressure, or temperature alarms while equipment is intentionally off	Occupancy, enable status, maintenance modes, and sequence logic
Mechanical or control instability	Repeated alarms from valves, dampers, fans, pumps, or temperature points	Control tuning, sensors, actuators, mechanical components, and sequence of operation
Communication failure	Large groups of controllers or devices alarm simultaneously	BAS network, controllers, switches, wiring, power, BACnet communications, and device addressing
Duplicate alarm sources	The same equipment fault appears several times	Factory controls, BACnet integration, supervisory logic, and BAS programming
Single failure causing cascading alarms	Dozens of alarms appear after one equipment failure	First alarm, equipment dependencies, root cause, and downstream consequence alarms

1. Alarm Limits Are Too Close to Normal Operating Conditions

Consider a space temperature alarm configured to activate at 76°F.

If the space normally operates between 74°F and 76°F, that alarm may activate regularly even though the HVAC system is still operating within an expected range.

The same problem can occur with:

• Supply air temperature
• Static pressure
• Chilled-water differential pressure
• Hot-water temperature
• Humidity
• Refrigeration temperatures
• Building pressure
• Equipment amperage

Alarm thresholds need enough separation from normal system fluctuations to identify a meaningful abnormal condition.

Before changing an alarm limit, however, the underlying HVAC operation should always be evaluated. Increasing an alarm threshold simply to hide unstable equipment can allow a real mechanical or controls problem to continue unnoticed.

2. Insufficient Alarm Deadband

Deadband, sometimes called hysteresis, prevents a sensor reading from repeatedly moving in and out of alarm.

Suppose a high-temperature alarm activates at 78°F. Without adequate deadband, a reading moving between 77.9°F and 78.1°F could repeatedly generate alarm and normal messages. A properly configured system might activate the alarm at 78°F but require the temperature to fall below a lower reset point before clearing it. Deadband is particularly important for analog readings that naturally fluctuate.

Common examples include:

• Temperature
• Pressure
• Humidity
• Airflow
• Water flow
• Differential pressure

If an alarm is constantly switching between normal and alarm states, the first step should be determining why.

The problem could be alarm configuration, but it could also be a failing sensor, unstable control loop, mechanical problem, or poor system tuning.

3. No Alarm Delay

Commercial HVAC equipment does not always respond instantly.

A large supply fan may need several seconds to reach operating speed. Pumps need time to establish flow. Chillers and boilers go through startup sequences before reaching normal operating conditions.

If the BAS expects immediate confirmation, it may generate false alarms every time equipment starts.

For example:

Supply fan commanded ON → BAS immediately checks fan proof → fan has not reached speed yet → fan failure alarm

A properly engineered delay gives the equipment time to complete its normal startup sequence before the BAS determines that something has actually failed.

“Commercial HVAC equipment needs time to respond. A fan has to come up to speed, a pump has to establish flow, and a chiller has to work through its startup sequence. If the controls don’t account for that, you can create alarms during completely normal operation.”

Choice Mechanical Services Service Manager

Similar delays can help prevent unnecessary alarms caused by:

• Normal equipment startup
• Short temperature fluctuations
• Pressure spikes
• Temporary network interruptions
• Morning warm-up
• Building cooldown
• Equipment staging

Alarm delays should still leave enough time for operators to respond before the condition can damage equipment or disrupt building operations.

The goal is not to delay important information. It is to prevent normal equipment behavior from being mistaken for a failure.

4. Alarms Ignore Equipment Operating State

One of the biggest causes of unnecessary BAS alarms is alarm logic that does not consider whether the equipment should actually be operating.

Consider a chilled-water pump. If the plant has been intentionally shut down, the BAS should not necessarily generate:

• Low chilled-water flow
• Pump failure
• Low differential pressure
• High chilled-water temperature

Those conditions may be completely normal when the plant is disabled.

The same principle applies to air handlers. A supply-air pressure alarm should generally not activate simply because an AHU is intentionally off.

Good BAS alarm logic considers operating conditions such as:

• Occupied versus unoccupied mode
• Equipment enable status
• Scheduled shutdown
• Maintenance mode
• Morning warm-up
• Cooldown
• Seasonal operation
• Startup sequences
• Emergency operating modes

State-based alarm logic can eliminate a significant amount of unnecessary alarm traffic while making the remaining alarms more meaningful.

5. One Failure Generates Dozens of Alarms

Some of the worst BAS alarm floods happen because one mechanical failure creates a chain reaction throughout the HVAC system. Consider a chilled-water plant. A pump fails.

That single problem could produce:

1. Pump failure alarm
2. Low chilled-water flow alarm
3. Low differential pressure alarm
4. Chiller alarm
5. High chilled-water supply temperature alarm
6. AHU cooling alarms
7. High discharge-air temperature alarms
8. Zone temperature alarms

Across a large building or campus, one equipment failure can quickly create dozens or hundreds of notifications.

The technician then has to determine which alarm represents the original problem and which alarms are simply consequences.

“One mechanical failure can create a chain of alarms across an entire building. Our job is to work backward and find the first thing that went wrong. Fixing the root problem is a lot more important than chasing every alarm that happened afterward.”

Choice Mechanical Services Service Manager

Whenever possible, the BAS should help operators identify the first or primary failure rather than forcing them to search through a long chronological alarm list.

Alarm grouping and equipment relationships can make a major difference during these situations.

6. Communication Problems Create Alarm Floods

Network failures are another common source of alarm floods.

If a supervisory controller, network switch, automation server, or communication trunk goes offline, dozens or hundreds of connected devices may suddenly appear unavailable.

Without proper alarm management, the BAS may generate a separate communication alarm for every individual device.

The facility team does not necessarily need 200 notifications telling them that equipment on the same network segment disappeared.

They need a useful notification identifying the communication failure and showing which systems are affected.

Proper alarm hierarchy and network troubleshooting can dramatically reduce these alarm floods.

Repeated communication alarms should also be investigated. They may point to issues involving:

• BAS controllers
• Network switches
• Wiring
• Power supplies
• BACnet communications
• IP networks
• Device addressing
• Intermittent hardware failures

Ignoring recurring communication alarms can make it harder to recognize when a true network failure occurs.

7. Packaged Equipment Produces Duplicate Alarms

Modern commercial HVAC equipment frequently includes its own factory controls.

That includes:

• Chillers
• Boilers
• Variable frequency drives
• Rooftop units
• Cooling towers
• Pumps
• Refrigeration systems
• Generators
• UPS systems

A single fault may be reported by the equipment controller, BACnet integration, supervisory controller, and separate BAS programming.

Now one equipment problem becomes three or four alarms.

When integrating packaged equipment, facility teams and controls contractors should determine which system will serve as the primary source for each alarm and eliminate unnecessary duplication.

The operator still needs access to detailed fault information. They simply should not have to acknowledge multiple versions of the same event.

8. Control Problems Are Being Treated as Alarm Problems

Sometimes the alarm configuration is not actually the problem.

The HVAC system itself may be unstable.

Examples include:

• Hunting control valves
• Rapidly cycling dampers
• Poorly tuned control loops
• Excessive fan speed changes
• Simultaneous heating and cooling
• Improper equipment staging
• Incorrect control sequences
• Inaccurate sensors

If a duct static pressure reading repeatedly crosses an alarm threshold because the fan control loop is unstable, increasing the alarm deadband may reduce the notifications.

But the control problem still exists.

“Sometimes the alarm is doing exactly what it was programmed to do. The real problem is a valve that’s hunting, a sensor that’s drifting, a fan that’s cycling, or a sequence that isn’t working correctly. You have to look at the mechanical system and the controls together.”

Choice Mechanical Services Service Manager

This is an important distinction.

A BAS can show technicians where abnormal conditions are occurring, but the system cannot automatically correct every underlying mechanical issue.

When the same alarms repeatedly appear around one piece of equipment, technicians should review the actual system operation before simply changing alarm settings.

Start by Finding Your Worst BAS Alarm Offenders

You do not have to redesign the entire building automation system to start reducing alarm fatigue. Begin by reviewing the BAS alarm history.

Look for:

• Most frequently occurring alarms
• Alarms that repeatedly activate and clear
• Alarms that remain active for days
• Equipment producing multiple alarms
• Duplicate alarms
• Communication alarms
• Alarms occurring during normal startup
• Alarms occurring when equipment is intentionally off
• Alarms that operators routinely acknowledge without taking action

In many facilities, a relatively small number of improperly configured points generate a large percentage of the overall alarm volume.

Correcting those problem alarms can quickly make the BAS significantly easier to manage.

Eliminate Chattering Alarms

A chattering alarm repeatedly activates, clears, and activates again over a short period. These alarms should not simply be acknowledged indefinitely. Investigate why they are occurring.

Possible causes include:

• Failing sensors
• Loose wiring
• Electrical interference
• Communication issues
• Insufficient deadband
• Incorrect alarm thresholds
• Poor control-loop tuning
• Mechanical equipment cycling

A properly operating HVAC system should not continuously generate the same alarm.

Chattering alarms are often one of the fastest opportunities for improving BAS performance because a handful of points may account for a significant percentage of the alarm history.

Address Standing Alarms

Standing alarms are conditions that remain active for extended periods. It is not unusual to encounter BAS systems with alarms that have remained active for weeks or even months. That creates a serious operational problem because operators eventually begin treating the abnormal condition as normal.

Every standing alarm should have an explanation.

The condition should be:

• Corrected
• Assigned for repair
• Converted into an appropriate maintenance task
• Temporarily managed during approved maintenance
• Removed as an alarm if no meaningful operator action is required

Acknowledging an alarm is not the same as correcting the problem.

If an alarm remains active every day, the facility should understand why.

Create Clear BAS Alarm Priorities

Example BAS Alarm Priority Structure

Priority	When to Use It	Typical Response
Critical	A condition could result in major equipment damage, loss of a critical environment, or severe operational disruption if action is not taken quickly.	Immediate investigation and response
High Priority	A significant HVAC or building-system problem requires prompt attention, but some response time is available.	Prompt operator or technician response
Routine	A condition requires corrective action but does not create an immediate operational risk.	Schedule investigation or repair
Maintenance / Informational	The condition provides useful diagnostic or maintenance information but does not require a time-sensitive operator response.	Dashboard, trend review, FDD system, or work order

A useful rule: alarm priority should be based on what happens if nobody responds and how much time is available before that consequence occurs. If everything is critical, nothing is critical. Building automation systems should use a limited and clearly defined priority structure.

Critical

Immediate response is necessary to prevent major equipment damage, loss of a critical environment, serious operational disruption, or another severe consequence.

High Priority

Prompt action is necessary, but the facility team has some time to investigate and respond.

Routine

The condition requires attention but does not require an immediate response.

Maintenance or Informational Event

Useful information that should be tracked without interrupting the operator.

Priority should be based on two questions:

What happens if nobody responds?

How much time do we have before that consequence occurs?

Avoid assigning alarm priority simply based on the size, cost, or visibility of the equipment.

A large piece of equipment can generate a routine alarm. A seemingly small component can create a critical condition if its failure threatens an important process.

Make BAS Alarm Messages Useful

An alarm message such as:

AHU-4 ALARM

does not provide enough information.

The operator now has to open graphics, check equipment status, review trends, and determine what actually happened.

A better alarm provides immediate context.

Whenever the BAS allows it, alarm information should include:

• Equipment name
• Specific abnormal condition
• Current sensor value
• Alarm threshold
• Alarm priority
• Time alarm began
• Equipment operating state
• Recommended operator action

For example:

AHU-4 Supply Fan Failed to Prove. Fan commanded ON. Verify VFD status and supply fan operation.

The technician immediately knows what happened and where to begin troubleshooting.

That can significantly reduce diagnostic time, especially during a larger equipment failure.

Use Alarm Suppression Carefully

Alarm suppression can be extremely effective when it is built around predictable equipment operating conditions.

For example, downstream airflow and temperature alarms may provide little useful information when an air handler has already been intentionally shut down for maintenance.

The BAS can temporarily suppress alarms that are irrelevant during that operating state.

However, suppression should always be intentional and documented.

Facility teams should know:

• Which alarms are suppressed
• Why they are suppressed
• What condition activates the suppression
• When the alarms become active again

Critical alarms should never be casually suppressed simply because they are inconvenient.

Fire alarm, life-safety, and other code-regulated systems also require separate consideration. These systems should not be modified as part of a general BAS alarm cleanup without the proper engineering, testing, and code review.

Use Alarm Shelving as a Temporary Tool

Some BAS platforms allow operators to temporarily shelve an alarm.

This can be useful during:

• Equipment repair
• Commissioning
• Planned shutdowns
• Controls troubleshooting
• Temporary operating conditions

Shelving should have a defined reason and expiration.

If technicians repeatedly shelve the same alarm, the underlying mechanical, controls, or sensor problem needs to be corrected.

Otherwise, shelving simply becomes another method of ignoring the alarm.

Keep Fault Detection Separate From Urgent Alarms

Modern BAS platforms and fault detection and diagnostics systems can identify increasingly complex HVAC problems.

Examples include:

• Sensor drift
• Leaking valves
• Simultaneous heating and cooling
• Economizer problems
• Damper performance issues
• Excessive equipment runtime
• Abnormal energy use

These findings can be extremely valuable for preventive maintenance.

But most do not require someone to respond immediately.

Instead of sending every diagnostic finding to the primary BAS alarm screen, lower-priority issues can often be routed to:

• Maintenance dashboards
• Work-order systems
• Energy-management reports
• Technician review queues
• Preventive maintenance planning

The primary alarm channel should remain focused on conditions that actually require timely human intervention.

Review BAS Alarm Performance Regularly

Alarm management should not end when a building is commissioned. Commercial HVAC systems change constantly. Equipment gets replaced. Setpoints change. Occupancy patterns change. Control sequences are modified. Sensors drift. New equipment gets integrated into the BAS. Alarm performance should therefore become part of routine commercial HVAC and building controls maintenance.

Facility teams should regularly review:

• Most frequent alarms
• Standing alarms
• Chattering alarms
• Alarm floods
• Duplicate alarms
• Communication failures
• Temporarily suppressed alarms
• Shelved alarms
• Operator response times
• Recurring equipment faults

It is also useful to compare alarm histories over time.

If a particular chiller, boiler, air handler, or pump suddenly begins producing significantly more alarms than normal, that change may provide an early indication of a developing mechanical or controls problem.

Preventive Maintenance Can Reduce BAS Alarm Fatigue

Many recurring building automation alarms eventually lead back to equipment maintenance.

Dirty coils, worn belts, failing actuators, plugged strainers, deteriorating sensors, improperly operating valves, damaged dampers, unstable pumps, and other mechanical problems can all create abnormal readings at the BAS.

Preventive maintenance gives technicians an opportunity to address these conditions before they develop into larger failures.

A strong commercial HVAC maintenance program should look beyond whether the equipment is simply running.

Technicians should also evaluate whether the system is:

• Reaching expected temperatures
• Maintaining proper pressures
• Producing adequate airflow
• Maintaining required water flow
• Responding properly to control commands
• Operating without excessive cycling
• Providing accurate sensor readings
• Following the intended sequence of operation

The BAS can provide valuable clues, but those clues still need to be evaluated alongside the physical HVAC system.

Better BAS Alarms Lead to Better HVAC Decisions

The goal of a building automation system is not to generate as many alarms as possible.

The goal is to give building operators the right information at the right time.

A well-designed alarm strategy helps facility teams quickly determine:

• What happened
• Which equipment is affected
• How serious the condition is
• What likely caused it
• What should happen next

“A good BAS should make a technician’s job easier. When an alarm comes in, we want to know what happened, which equipment is affected, and where we need to start looking. The fewer meaningless alarms you have, the easier it is to recognize the ones that matter.”

Choice Mechanical Services Service Manager

Reducing alarm fatigue does not mean reducing visibility into the building.

Facilities should continue collecting detailed sensor data, trends, equipment statuses, diagnostic information, and historical events.

The difference is that not every piece of information needs to interrupt an operator.

When building automation system alarms are properly configured and the underlying HVAC equipment is operating correctly, the BAS becomes what it was intended to be: a tool that helps facility teams identify problems quickly and make better decisions.

Commercial HVAC and Building Automation Support in Indianapolis

Choice Mechanical Services works with commercial facilities throughout Indianapolis and Central Indiana to troubleshoot HVAC performance problems, identify equipment and control issues, and keep complex mechanical systems operating reliably.

Our commercial HVAC capabilities include:

• HVAC+R services
• Boiler repair and installation
• Chiller repair and installation
• Commercial piping and plumbing
• Preventive maintenance agreements
• Emergency HVAC services

When BAS alarms point to a mechanical problem, experienced HVAC troubleshooting is critical.

A building automation system can identify abnormal temperatures, pressures, flows, equipment statuses, and operating conditions. The next step is determining why those conditions are occurring.

Choice Mechanical Services helps facility teams get beyond the alarm message and identify the mechanical or operational problem behind it.

For commercial HVAC service in Indianapolis and Central Indiana, contact Choice Mechanical Services at (317) 885-0200. Choice Mechanical Services provides 24-hour emergency commercial HVAC service, 7 days a week, 365 days a year.