Students often rece/ve notification of a weather or security event n multiple formats, including on their laptops. All photos: Siemens

Size: px

Start display at page:

Download "Students often rece/ve notification of a weather or security event n multiple formats, including on their laptops. All photos: Siemens"

Pierce Houston
5 years ago
Views:

1 Students often rece/ve notification of a weather or security event n multiple formats, including on their laptops. All photos: Siemens o RISK ANALYSIS and mass notification NFPA 72 includes risk analysis, which covers natural, technological, and manmade disasters and addresses scenarios of concern, probability, and potential consequences. BY RAY GRILL, PE, FSFPE, Arup, Washingtor), D.C. In the fire alarm community, there has been a lot of discussion about mass notification. The incorporation of mass notification systems (MNS) in buildings first got attention after the Dept. of Defense (DoD) began requiring the installation of such systems as a result of the attack on Khobar Towers in Saudi Arabia in Khobar Towers provided housing for the U.S. Air Force, Saudi Air Force, and other military. The explosion detonated outside of this high-rise residential building caused 20 fatalities and injured 372 people. The marines on security duty became aware of the impending event and did everything they could to try to warn occupants, but without equipment to facilitate notification, they were unable to warn all of the occupants before the explosion. As a result of the Khobar Towers attack, MNS was required through the DoD Unified Facilities Criteria (UFC) "DoD Minimum Antiterrorism Standards for Buildings," which became effective in Concurrently, UFC "Design and O&M; MNSs" was developed. UFC Consuiting-Specifying Engineer APRiL 2010

2 01 provided the design, installation, and maintenance requirements for MNS. Soon thereafter, the Air Force petitioned NFPA to start a standard development project to address the design and installation of MNS, with a goal of revising NFPA 72 to allow fire alarm systems to also perform mass notification functions. In response to that petition, NFPA expanded the scope of the Signaling Systems for the Protection of Life and Property Project to include mass notification. This scope expansion resulted in significant revisions to the 2007 edition of NFPA 72 focused on allowing fire alarm systems to also function as MNS. An annex to the 2007 edition of NFPA 72 provided guidance for the design and installation of MNS. The work of the committees did not stop there. The 2010 edition of NFPA 72 was revised, reorganized, and expanded. It now includes requirements for the design, installation, and maintenance of MNS in a The work of the committees did not stop there. The 2010 edition of NFPA 72 was revised, reorganized, and expanded. It now includes requirements for the design, installation, and maintenance of MNS in a new Chapter 24 titled, "Emergency Communication Systems." new Chapter 24 titled, "Emergency Communication Systems." This chapter includes all the requirements for emergency voice/ alarm communication systems, firefighter communications, and mass notification. The name of the code has also been changed from the "National Fire Alarm Code" to the "National Fire Alarm and Signaling Code" to recognize this expansion of scope. As with other systems addressed by the code, NFPA 72 does not require an MNS to be installed. However, if one is Many mass notification systems send messages to users' cell phones and smart phones. APRIL 2O10

3 THIS IDEA WAS SO COOL... Temado ««min«-. TÄe CcV«Office and warehouse notification systems must be both audible and visual, tike this sign. THE INDUSTRY'S BEST SELLING CEILING-MOUNT SPOT COOLING SYSTEM 10,500 Btu/h of cooling Quick & easy installation No specioi electric required Fits into tight ceiling spaces No floor space needed To team more visit movincool.com or call MOVINCOOL THE #1 SPOT COOLING SOLUTION 2010 DENSO Sain Colilomia. Inc MovinCoal, SpoKoot and Of fits Pro aie legitltred liodímniki ol DENSO Cor poca) ion. Input #212 at csemag.œnvquickresponse Consulting-Spacifying Engineer APRIL 2010 provided, the code requires that the system be designed, installed, and maintained in accordance with the provisions of NFPA 72. Risk analysis Prior to the incorporation of mass notification requirements in the body of the code, NFPA 72 did not have any requirements for risk analysis. While the 2007 edition of NFPA 72 has guidelines for the design and installation of mass notification in Annex E, there are no requirements. The body of the 2007 edition was modified to change language that previously prevented a fire alarm system from either performing mass notification or being integrated with an MNS. When the new Technical Committee on Emergency Communications Systems was considering Annex E guidelines for the design of an MNS for incorporation into the code as requirements, the committee realized that many of the MNS design recommendations needed to consider the specifics of the project and the many variables that could apply. In order to write requirements for MNS in the body of the code, the committee determined that performance-based design approaches would need to be incorporated. Performance-based design includes risk analysis. A key requirement of the 2010 edition of y NFPA 72 is that MNS be designed to address the nature and anticipated risks of the facility. The requirement for a risk analysis recognizes that design approaches for MNS have to be specific to each project and may need to vary significantly from facility to facility in order to meet safety goals. The committee also realized that prescriptive requirements could not address all situations. What is a risk analysis? NFPA 72 defines risk analysis as a process to chararterize the likelihood, vulnerability, and magnitude of incidents associated with natural, technological, and manmade disasters and other emergencies that address scenarios of concern, their probability, and their potential consequences. While the code identifies things that should be considered in the risk analysis, it does not define the detail of analysis. The code does not intend that a risk analysis be a thesis. The depth of analysis needs to be discussed with the owner and other stakeholders as early as possible in the design process to facilitate the work. The design brief and risk analysis should be prepared and approved before the actual design of the system is procured to avoid either additional cost for design

features that weren't anticipated before the risk analysis was prepared, or overpaying for a system that anticipated more features or devices than needed to meet the safety goals.

4 features that weren't anticipated before the risk analysis was prepared, or overpaying for a system that anticipated more features or devices than needed to meet the safety goals. Where is a risk analysis required? The design of an MNS requires that a design brief be prepared using recognized performance-based design practices. The design brief becomes the basis for the MNS design and a document that all of the design team members, owner, authority having jurisdiction, and other stakeholders can agree on. In the context of compliance with NFPA edition, the approved design brief sets features and performance of the MNS for a specific facility or application. Guidelines for the preparation of a design brief won't be discussed here, but the Society of Fire Protection Engineers (SFPE) publishes a guide to performance based design that is widely recognized in the design and enforcement community. NFPA 72 specifically requires a risk analysis to be performed under the following conditions: partmentation features (i.e., automatic door closure). For events other than fire, it may be appropriate and necessary for these systems to perform one way in a fire emergency and another way in the event of a different type of emergency. Depending on the situation, operation in fire mode in a nonfire condition may create confusion or a hazard to life. That is why the code recognizes the need to allow for other signals to take priority over fire alarm signals. In the case of systems that use trained personnel to direct emergency actions, if the signals to these trained personnel are not given the necessary and appropriate priority, it may prevent personnel from receiving a notification signal that requires their immediate action to dirert occupants or emergency responders. Drivers of risk analysis The need for the MNS to be specific to the application is the main driver for the risk analysis. While there can be many different fire scenarios in a building, the actions required to address occupant safety can be defined prescriptively in the WE MADE IT BIGGER! INTRODUCING THE NEW More than twice the cooling copocity - 25,000 Btu/h More energy efficient 14SEER, R410Arefrigeront and RoHS compliont Higher sensible cooling ideol for server rooms The challenge with an MNS is that every facility or campus has unique risks that need to be addressed by the system design. Includes stote-of-the-ort wall mount controller Still compact, self-contained and sits only 20' tall When signals other than fire signals need to take precedence To inform the determination of survivability criteria for emergency communication system circuits when not specifically defined by the code If an MNS is being provided. Signal priority can impact not only the activation of notification appliances and the activation of messages, but also activation of other building features that may be expected to operate in an emergency. These features might include exhaust and HVAC systems, containment, and comcode. Performance-based design is applied when there is either a unique building design or unique hazard that requires a more in-depth analysis to achieve life safety or property goals. The challenge with an MNS is that every facility or campus has unique risks that need to be addressed by the system design. Nonfire events that should be considered include: Security breach (presence of armed assailants, etc) Public disturbance (demonstration, riot, etc.) The Ceiling Mount Series is designed to save you space, Hme and cost - and it's backed by one of the best warranty coverages in the business. To learn more visit movincool.com or call MOVINCOOL 7010 DENSO Solat Cahfamia, Inc. MovinCsol, SpolCool and Offii«Pro ait tsgklered Irademaiks a( DENSO Coiporaiion. Input #213 at osemag.œm/quidtresponse Consulting-Spscifying Engineer APRIL 2O1O O

5 NS design features I A number of features of a mass notifican system (MNS) are specifically driven by e risk analysis. These include: Whether the system is provided with apability for remote operation The definition of notification zones Content of the messages and whether ire-recorded messages wilt be used 'The level oí survivability of notification Ippljance circuits Priority of signals (at control equipment tnd those sent to recipients) Whether Ihe system will be allowed 9 automatically send messages to recipients Type, location, and security of control md interface equipment Whether the system will control the peration of other building systems Whether wide area signaling (outside of uildings) is required or provided. Health (toxic chemical release) Geological (earthquake, volcano, tsunami, etc.) Meteorological (tornado, hurricane, flood, hail, etc.) Utility outage Medical emergency Terrorism-related. The owner and operators of a facility need to be involved to assist in defining the potential risks. A number of questions should be asked to identify the risks and features that may need to be incorporated in a system design. Here are some examples: What event(s) may occur that would need emergency action (i.e., is it fire, security, safety, health, environmental, geological, meteorological, utility service disruption, or another type of event)? What is the urgency of the emergency event? How quickly will action need to be taken to avoid injury or property damage? What is the expected severity of an event? What is the probability of an event occurring? What areas of the facility are subject to the risk? What actions need to be taken by occupants and emergency responders for each event? What is the validity of the emergency event, and has the emergency event been investigated and/or confirmed? What general and special instructions should we send to which occupants? Risk analysis considerations Key factors that need to be considered in the risk analysis include: The number of people that need to be notified for the various events " Characteristic of the occupancy (i.e., building construction, equipment, operations) " Management/staff capabilities Extent of notification (there may be different first responders for different emergencies). Emergency response plan The risk analysis also provides the basis for the development of the emergency response plan. The MNS design should be coordinated with this plan. The risk analysis may also identify areas of improvement or modifications needed for the emergency response plan. The emergency response plan should include the following: Emergency response team members and structure Emergency response procedures for each expected type of event Emergency response equipment Notification/communication Message content Message recipients Authority to send messages Initiation procedure Emergency response training and drills. A framework It was not the intent of the NFPA 72 Technical Committee on Emergency Communication Systems that every risk analysis be a thesis paper. Preparing a risk analysis for an MNS can be challenging. One of the first steps isto get the stakeholders on the same page in defining the purpose and goals for the MNS as well as the threats. The owner and ultimate user of the system need to take an active role in defining these factors. If they don't actively participate in this process, the designer could miss important factors that aren't obvious to an outside party or make design decisions that are not compatible with the facilities emergency management plan or operations. Different facilities will need different depths of risk analysis. The breadth and depth of analysis should be agreed upon with the owner at the beginning of the process and should be documented in the risk analysis. A basic outline for a risk analysis for the purpose of informing MNS design should include: Project description Goals and purpose of the MNS Expected characteristics of the occupants Expected characteristic of management and staff (availability, roles in emergencies, etc.) Occupancy characteristics (threats and hazards present) Anticipated events that could present a risk (internal and external) Given the factors above, design features required for the system to be effective. Icsel Griil is a principal with Arup, where he focuses on fire protection engineering. He is a memberoiconsulting Specifying Engineer's editorial advisory board and a past president of the Society of Fire Protection Engineers. Consulting-Specifying Engineer APRIL 2010

6 2010, Consulting-Specifying Engineer, Reed Business Information, a division of Reed Elsevier, Inc. All Rights Reserved. Copyright of Consulting-Specifying Engineer is the property of Reed Business Information and its content may not be copied or ed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or articles for individual use.

MNEC NFPA 72 WHITE PAPER

MNEC NFPA 72 WHITE PAPER In 2010, the National Fire Protection Assocation (NFPA), significantly changed their code # 72 (National Fire Alarm Code) and has forever improved the importance of communicating