If your BAS alarm console feels like a slot machine, you don’t have monitoring—you have noise. When hundreds of alarms flood your screen every week, alarm overload doesn’t just waste time. It hides the one alarm that actually matters.
Nuisance alarms drive after-hours calls and “false urgency.” Alarm storms bury root causes. Teams stop trusting alarms—then real failures slip through unnoticed. The result? Critical equipment fails while operators are chasing ghosts.
This article lays out a 90-day alarm reset plan you can execute with your systems integrator and internal team—starting with the tools you already have.
BAS Alarms Are Not Life Safety Alarms
Before we go further, let’s be clear: BAS alarming is not the same as fire alarm or life safety signaling. You can coordinate data sharing and operational awareness between systems, but don’t blur system responsibilities or code boundaries. In many buildings, life-safety sequences can command HVAC behaviors (for example, smoke control) based on the design and AHJ requirements—coordinate deliberately and document the handoffs. Treat life safety as its own governed domain. Treat BAS alarms as operations and maintenance decision support—information that helps you act faster and smarter.
What Makes an Alarm Actually an Alarm?
Here’s the core problem: many BAS “alarms” aren’t alarms at all. They’re status messages, event logs, or informational notices that got routed to the wrong place. To fix alarm overload, you first need to know what belongs in the alarm console.
- Alarm: A condition indicating abnormal operation that requires a timely response. A critical pump has failed. A supply fan is down on your main AHU. A sustained freeze risk condition has been detected.
- Notification: Useful information that may not require immediate action. Equipment has cycled more than usual. A filter needs attention soon.
- Event log: Records a state change for traceability—often not urgent. A schedule executed. A setpoint was adjusted.
- Trend: Time-series data used for diagnosis and prevention. Temperature drift over several days. Energy consumption patterns.
If an “alarm” fires repeatedly and no one takes action, treat it as a red flag. Either the condition doesn’t belong in the alarm console, or your team doesn’t have a clear response playbook. In both cases, it should not stay as-is.
Why Alarms Get Out of Control
Commercial buildings face five common alarm failure modes:
Alarm flooding: One upstream fault triggers dozens of downstream symptoms. AHU-3’s supply fan fails, so 30 zones go out of range, generating 200 alarms. The operator misses the root cause for 45 minutes because the real problem is buried.
Nuisance thresholds: No deadband, no delay, unrealistic limits. A temperature sensor oscillates around the setpoint and triggers an alarm every 30 seconds.
Flat priority model: Everything looks equally urgent when nothing is prioritized. Critical equipment failures get lost among comfort complaints.
Inconsistent naming and fragmentation: Multiple BAS platforms, inconsistent point names, and no standardized approach across buildings make pattern recognition impossible.
No response playbooks: Operators don’t know what to do when an alarm fires, so they acknowledge it and move on—learning nothing, fixing nothing.
Your system needs root-cause grouping and symptom suppression (with an audit trail) so the right issue rises to the top.
The 90-Day Alarm Reset Plan
This is not a software purchase. It’s an operations program with quick wins.
Phase 1 (Days 1–14): Baseline and Triage
Goal: See the true shape of your alarm noise.
Export 30–90 days of alarm history from your BAS. Categorize alarms by type: critical equipment, comfort, energy, informational, or unknown. Then create three critical lists:
- Top 20 alarms by frequency: Your “repeat offenders”
- Standing alarms: Alarms that never clear
- After-hours alarms: What wakes people up unnecessarily
Identify “alarm storms”—many alarms triggered within a short window, usually indicating a single root cause.
Quick win: If you only do one thing this week, pull the alarm export and identify your top 20 offenders.
Phase 2 (Days 15–30): Write a One-Page Alarm Philosophy
Goal: Standardize what “good” looks like.
Your alarm philosophy should answer these questions on a single page:
- What qualifies as an alarm? (Action required)
- What’s your priority model? (Recommended: Critical / Major / Minor / Advisory)
- What are your naming rules? (Clear, human-readable, consistent)
- Who gets what and when? (Routing rules)
- What happens if no one responds? (Escalation rules)
- How do you handle planned work? (Suppression rules with audit trail)
- Who can change thresholds? (Change control)
Create an appendix with your “Top 10 alarm playbooks”—what to check first, when to dispatch, when to escalate. This turns alarms from anxiety into action.
Phase 3 (Days 31–60): Fix the Top 20
Goal: Deliver measurable reduction quickly.
Now tackle your repeat offenders using three mechanisms:
Tune thresholds: Add deadbands to prevent oscillation. Add time delays to avoid transient triggers. A zone that’s out of range for 15 minutes may justify an alarm; a one-second blip usually doesn’t.
Fix the instrumentation: Bad sensors, unstable signals, communication dropouts, and schedule errors are common drivers of nuisance alarms. Replace failed sensors. Fix network issues. Correct schedules.
Implement root-cause grouping: If the AHU is down, suppress the 30 downstream zone alarms in the alarm console and surface the AHU fault as primary—while still logging the downstream symptoms for diagnosis. This change can materially reduce alarm flooding during equipment failures.
Document every change. You’re building institutional knowledge, not just reducing numbers.
Phase 4 (Days 61–90): Operationalize and Prevent Regression
Goal: Lock in results and establish weekly hygiene.
Turn your cleanup into a sustainable system:
- Route only critical alarms outside the BAS for after-hours response
- Implement escalation for unacknowledged alarms
- Use maintenance modes to suppress expected alarms during planned work
- Convert recurring alarms that require maintenance into work orders—not endless repeat notifications
- Hold a 30-minute weekly review meeting with your FM, chief engineer, and systems integrator to discuss top offenders, what changed, and what’s next
Publish a simple monthly KPI dashboard: total alarm count, top 10 offenders, after-hours pages, and mean time to acknowledge.
Don’t Do This: Common Mistakes
- Don’t disable alarms permanently just to make the console look clean
- Don’t use alarms as reminders for routine maintenance—that’s what your CMMS is for
- Don’t notify everyone—route only to people who can act
- Don’t change thresholds without documentation and change control
- Don’t “alarm your way out” of missing trends—prevention needs trending and analysis, not paging
Three Actions to Do This Week
- Pull an alarm export and identify your top 20 offenders
- Draft a one-page alarm philosophy with a four-level priority model
- Pick your worst alarm storm and design suppression so the root cause rises
Alarm fatigue is fixable. It doesn’t require a capital project or a system replacement. It requires discipline, documentation, and a 90-day commitment to treat alarms as decision support—not background noise. Start with the quick wins. Build momentum. Your operators will thank you.
Sources
Smart Buildings Academy — “Creating an Effective Alarm Design & Management Strategy for Large Facilities” (Podcast 511)
https://podcast.smartbuildingsacademy.com/511
Smart Buildings Academy — “The Critical Alarm functionality most specifications don’t address”
https://blog.smartbuildingsacademy.com/evaluate-bas-alarming
AutomatedBuildings.com — “Proactive BAS Alarming for High Performance Buildings”
https://www.automatedbuildings.com/news/jul11/columns/110629094909big.html
ISA InTech — “Alarm management questions that everyone asks”
https://www.isa.org/intech-home/2020/march-april/features/alarm-management-questions-that-everyone-asks
EEMUA — Publication 191 (good-practice alignment context)
https://www.eemua.org/products/publications/digital/eemua-publication-191