What is a BMS alarm escalation procedure?

• A. Classify severity, document, and monitor until resolution.
• B. Notify on-call personnel, escalate per protocol, classify severity, document, and monitor until resolution.
• C. Immediately shut down all systems on any alarm.
• D. Do nothing and log the alarm.

Answer: (B)

The main idea tested is how to handle a BMS alarm in a way that guarantees a timely, coordinated response. A proper escalation procedure isn’t just noticing an alarm; it’s a defined sequence that makes sure the right people are alerted, the issue is prioritized correctly, actions are recorded, and the situation is watched until it’s resolved.

Why this sequence works best: you start by notifying the on-call personnel so someone aware of the current shift and responsibilities can react quickly. Escalation per protocol ensures that if the initial responder doesn’t acknowledge or resolve the alarm within the expected time, the alert moves up to higher-level or alternate contacts. Classifying the severity assigns urgency and helps determine what kind of response is needed, whether it’s a quick inspection, a targeted corrective action, or a full shutdown procedure. Documenting everything creates an audit trail and helps with accountability and post-incident learning. Finally, monitoring until resolution means you confirm the issue is resolved and systems are back to normal, preventing repeated alarms from being treated as non-issues.

Why the other options don’t fit: immediately shutting down all systems on any alarm is inappropriate and risky because not every alarm requires a full shutdown; misapplying this can cause unnecessary downtime or safety issues. Doing nothing and logging the alarm misses the essential response step—someone must be alerted and engaged to address the problem. Only classifying severity, documenting, and monitoring omits the critical initial notification and escalation that ensure timely action and accountability.