First Revision No. 339-NFPA 72-2013 [ Section No. 2.2 ] Revision No. 339-NFPA 72-2013 [ Section No....

First Revision No. 339-NFPA 72-2013 [ Section No. 2.2 ]

2.2 NFPA Publications.

National Fire Protection Association, 1 Batterymarch Park, Quincy, MA 02169-7471.

NFPA 10, Standard for Portable Fire Extinguishers, 2010 2016 edition.

NFPA 13, Standard for the Installation of Sprinkler Systems, 2013 2016 edition.

NFPA 25, Standard for the Inspection, Testing, and Maintenance of Water-Based Fire Protection Systems,2011 2014 edition.

NFPA 37, Standard for the Installation and Use of Stationary Combustion Engines and Gas Turbines,2010 2016 edition.

NFPA 70®, National Electrical Code®, 2011 2014 edition.

NFPA 75, Standard for the Fire Protection of Information Technology Equipment, 2013 2016 edition.

NFPA 90A, Standard for the Installation of Air-Conditioning and Ventilating Systems, 2012 2015 edition.

NFPA 101®, Life Safety Code®, 2012 2015 edition.

NFPA 110, Standard for Emergency and Standby Power Systems, 2013 2016 edition.

NFPA 111, Standard on Stored Electrical Energy Emergency and Standby Power Systems, 2013 2016edition.

NFPA 170, Standard for Fire Safety and Emergency Symbols, 2012 2015 edition.

NFPA 601, Standard for Security Services in Fire Loss Prevention, 2010 2016 edition.

NFPA 720, Standard for the Installation of Carbon Monoxide (CO) Detection and Warning Equipment,2012 2015 edition.

NFPA 1221, Standard for the Installation, Maintenance, and Use of Emergency Services CommunicationsSystems, 2013 2016 edition.

NFPA 1600®, Standard on Disaster/Emergency Management and Business Continuity Programs,2010 2016 edition.

NFPA 1620, Standard for Pre-Incident Planning, 2010 2016 edition.

Submitter Information Verification

Submitter Full Name: Richard Roux

Organization: National Fire Protection Assoc

Street Address:

City:

State:

Zip:

Submittal Date: Thu Oct 03 11:13:33 EDT 2013

Committee Statement

Committee Statement: The TC updates 2.2 effective dates.

Response Message:

National Fire Protection Association Report http://submittals.nfpa.org/TerraViewWeb/ContentFetcher?commentPara...

28 of 326 11/21/2013 1:03 PM

First Revision No. 340-NFPA 72-2013 [ Section No. 2.3.1 ]

Global FR-158 Hide Deleted


2.3.1 ANSI Publications.



American National Standards Institute, Inc., 25 West 43rd Street, 4th Floor, New York, NY 10036.

ANSI A-58.1, Building Code Requirements for Minimum Design Loads in Buildings and Other Structures.

ANSI S1.4a, Specifications for Sound Level Meters, 1985, reaffirmed 2006.

ANSI S3.41, American National Standard Audible Emergency Evacuation Signal, 1990, reaffirmed 2008.

ANSI/ASME A17.1/CSA B44–10, Safety Code for Elevators and Escalators , 2010 2013 .

ANSI/IEEE C2, National Electrical Safety Code, 2007.

ANSI/TIA-568-C.3, Optical Fiber Cabling Components Standard, June 2008.

ANSI/UL 217, Standard for Single and Multiple Station Smoke Alarms, 2006, revised 2012.

ANSI/UL 268, Standard for Smoke Detectors for Fire Alarm Systems, 2009.

ANSI/UL 827, Standard for Central-Station Alarm Services, 2008 2013 .

ANSI/UL 864, Standard for Control Units and Accessories for Fire Alarm Systems , 2003, revised2011 2012 .

ANSI/UL 985, Standard for Household Fire Warning System Units, 2000, revised 2008.

ANSI/UL 1638, Visual Signaling Appliances — Private Mode Emergency and General Utility Signaling,2008.

ANSI/UL 1730, Standard for Smoke Detector Monitors and Accessories for Individual Living Units ofMultifamily Residences and Hotel/Motel Rooms, 2006, revised 2007.

ANSI/UL 1971, Standard for Signaling Devices for the Hearing Impaired, 2002, revised 2008.

ANSI/UL 1981, Central Station Automation Systems, 2003.

ANSI/ UL 2017, Standard for General-Purpose Signaling Devices and Systems, 2008, revised 2011.

ANSI/UL 2572, Mass Notification Systems, 2011 2012 .

ANSI/UL 60950, Information Technology Equipment — Safety — Part 1: General Requirements,2007 2011 .




Street Address:

City:

State:

Zip:


Committee Statement


29 of 326 11/21/2013 1:03 PM

Committee Statement: The TC updates 2.3.1 effective dates.

Response Message:


30 of 326 11/21/2013 1:03 PM


3.3.87 Emergency Communications Systems — Combination.

Various emergency communication systems such as fire alarm, mass notification, fire fightercommunications, area of refuge communications, elevator communications, or others and that can beserved through a single control system or through an interconnection of several control systems.(SIG-ECS)




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC deletes “and” as it is extraneous.

Response Message:


40 of 326 11/21/2013 1:03 PM


3.3.92 Emergency Response Plan.

A documented set of actions to address response to natural, technological, and man-made disasters andother emergencies prepared by the stakeholders from information obtained during the risk analysis .(SIG-ECS)




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Problem: Too many diffrent terms in NFPA 72 describing the same item, such as: Emergencyresponse plan 3.3.93, 24…. Building fire safety plan 3.3.32, 24.4.2.8.3.1 Emergency plan 18.5.3.5Emergency evacuation plan Fire safety plan Fire response plan Building response plan 23.8.4.8,23.8.4.8.2 Fire Plan 10.18.5.2 Relocation plan 23.8.1.3.1.1 Evacuation plan 23.8.6.3.1 Reasons forProposed Change: 1.There should be only one consistent term throughout NFPA 72 to describe thesame item – “Emergency Response Plan (ERP)”. All other terms, referring to the same item, andindicated in different sections throughout the NFPA 72 document are inconsistent and could beconfusing. The different terms may be indicated on the annex to Section 3.3.93 clarifying that if adifferent term such as: “Emergency Plan”, “Emergency Evacuation Plan”, “Fire Response Plan”,“Building Response Plan”, Fire Safety Plan”, “Building Fire safety Plan”, “Fire Safety and EvacuationPlans” etc., is used, it refers to the same document. My suggestion is to use the term: EmergencyResponse Plan (ERP) throughout the NFPA 72 document, since it includes the three important words:“Emergency” – which could be any type emergency (man-made or natural), “Response” – whichshould describe the building occupants’ actions to address certain emergency conditions, and “Plan” -which include specific procedures to be implemented upon those emergencies and required drills to beperformed for practice purposes. 2.I suggest to revise the definition of this term in section 3.3.93 toread: “A documented set of actions to address response to natural, technological, and man-madedisasters and other emergencies”. The reason I suggest to delete the last sentence in this definition –“prepared by the stakeholders from information obtained during the risk analysis” is that an ERP is notnecessarily required ONLY when a risk analysis is required. An ERP may be required for any typebuilding (existing or new), depending on the specific AHJ’s requirements and the applicable codesadopted by that jurisdiction, even if a risk analysis is not required. For example, in San Francisco, anERP is required for all existing and new High-Rise buildings, regardless the age of the building andregardless the fire protection system/s provided in that building, and it is not required to develop a riskanalysis for any of these buildings (We have about 600 existing high-rise buildings in SF – All havingERPs but not having Risk Analysis, the term used in SF for this required ERP is “Facility EmergencyPlan” (or FEP) but it has the same meaning as defined in section 1 above. This FEP is specific foreach building and it must be signed by the owner or the owner’s representative and be approved bySFFD which is the only AHJ for this document. (See attached PDF Example for a High-Rise FEP inSF). 3.Currently, In San Francisco the applicable building and fire codes are the 2010 edition of theCalifornia Fire Code and the California Building Code which are based on the 2009 edition of the IFCand IBC. Section 404 of the 2009 IFC is: FIRE SAFETY AND EVACUATION PLANS which hasspecific requirements regarding fire safety, evacuation and lockdown plans and associated drills.However, other jurisdictions may adopt other building and fire codes, and therefore, the definitions andterms in NFPA 72 should not be limited to certain codes or standards. 4.In my opinion, the


42 of 326 11/21/2013 1:03 PM

determination where (for which type building or facility) an ERP should be required, is dependent onthe specific AHJ requirements, based on applicable building and fire codes, and should not be relatedto or associated with a Fire Alarm system or Emergency Communication System (ECS or EVACS)requirements in NFPA 72. 5.The only place an ERP should be specifically required by NFPA 72, iswhen a Mass Notification System (MNS) is provided for a specific building/facility. Since any proposedMNS is required to have (or be based on) a Risk Analysis, an ERP should be specifically required forthat facility based on its specific Risk Analysis requirements. 6.When an ERP is required by NFPA 72for a MNS, Section 24.3.12 should mention that the ERP should be developed based on the RiskAnalysis in accordance with applicable codes and standards acceptable to the AHJ. An annex to thissection could reference examples for acceptable codes and standards to develop an ERP such asNFPA 1600, NFPA 1620, NFPA 101, IFC, etc. 7.It should be clarified in NFPA 72 that a Risk Analysisshould only be required where a MNS or ECS/MNS is provided. However, a risk Analysis should notbe required for any FA/ECS or EVACS which are not combined with MNS.

ResponseMessage:

Public Input No. 64-NFPA 72-2013 [Section No. 3.3.93]


43 of 326 11/21/2013 1:03 PM


7.3.6* Risk Analysis Documentation. (SIG-ECS)

7.3.6.1

When a risk analysis is required to be prepared, findings and considerations of the risk analysis shall bedocumented.

7.3.6.2

When determined by the stakeholders, security and protection of the risk analysis documentation shall bein accordance with 7.3.7 and Section 7.7.

7.3.6.3

The risk analysis documentation shall list the various scenarios evaluated and the anticipated outcomes.

7.3.6.4

Risk analyses for mass notification systems shall be documented in accordance with 7.3.6 and24.3.11 24.3.13 .

Supplemental Information

File Name Description

Attachment_for_FR_347.EC_edits.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The Risk Analysis Checklist A.7.8.2(g) is not considered part of the Record of Completion so thechecklist needs to be relocated to appropriate existing Section 7.3.6 Risk Analysis Documentationas Annex material.

ResponseMessage:


68 of 326 11/21/2013 1:03 PM

A.7.3.6

The Risk Analysis Checklist in Figure A.7.3.6 is not mandatory, but it can be used to initiate the

thought process for identifying hazards in a facility.

Move and rename checklist from A.7.8.2(g) to A.7.3.6. Same title.


7.5.9 Owner’s Manual.

For new emergency communications systems, an owner’s manual shall be provided and shall containthe following documentation:

(1) Detailed narrative description of the system inputs, evacuation signaling, ancillary functions,annunciation, intended sequence of operations, expansion capability, application considerations,and limitations

(2) Written sequence of operation for the system, including an operational input/output matrix

(3) Operator instructions for basic system operations, including alarm acknowledgment, system reset,interpretation of system output (LEDs, CRT display, and printout), operation of manual evacuationsignaling and ancillary function controls, and change of printer paper

(4) Detailed description of routine maintenance and testing as required and recommended and aswould be provided under a maintenance contract, including testing and maintenance instructionsfor each type of device installed, which includes the following:

(a) Listing of the individual system components that require periodic testing and maintenance

(b) Step-by-step instructions detailing the requisite testing and maintenance procedures and theintervals at which those procedures shall be performed, for each type of device installed

(c) Schedule that correlates the testing and maintenance procedures required by this section

(5) Service directory, including a list of names and telephone numbers of those who provide servicefor the system

(6) Product data sheets for all system equipment (SIG-ECS)




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC adds new 7.5.8 which is incorporated from 24.8.3. The TC adds item (6).

Response Message:

Public Input No. 597-NFPA 72-2013 [New Section after 7.5.8]


76 of 326 11/21/2013 1:03 PM

First Revision No. 348-NFPA 72-2013 [ New Section after 7.7.1.4 ]

7.7.1.5

The emergency communications system and fire alarm system as-built plans and other relateddocumentation shall be permitted to be maintained together, including the appearance of both systemson the same drawings. (SIG-ECS)




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Incorporated from Chapter 24

Response Message:


Public Input No. 600-NFPA 72-2013 [New Section after 7.7.1.4]


78 of 326 11/21/2013 1:03 PM

First Revision No. 363-NFPA 72-2013 [ New Section after 10.12.1 ]

10.12.2

Visible notification appliances, textual visible notification appliances, and speaker notification applianceslocated in the same area shall be activated and deactivated as a group unless otherwise required by anECS emergency response plan. (SIG-ECS)

10.12.3*

Visible alarm strobe notification appliances shall not be activated when speaker notification appliancesare used as permitted by 24.3.7 for non-emergency paging. (SIG-ECS)



Annex_Material_for_FR_363.EC_edits.1382627828856.docx


Submitter Full Name: Lee Richardson


Street Address:

City:

State:

Zip:

Submittal Date: Mon Oct 07 12:24:12 EDT 2013

Committee Statement

CommitteeStatement:

The material formerly in 10.13.2.1 is more clearly addressed in new 10.12.2 and 10.2.3. ThisfR also adds new A.10.12.2 - see attached

ResponseMessage:


121 of 326 11/21/2013 1:03 PM

A.12.2.3

The intent of this requirement is to ensure that hearing-impaired persons are alerted to seek additional

information regarding an emergency situation. Hearing-impaired persons might not be able to hear the

speaker notification appliances that provide evacuation tones or voice instructions. It is intended that

the speakers and visible devices located in the same area be activated together whenever tones,

recorded voice instructions, or live voice instructions are being provided.

First Revision No. 362-NFPA 72-2013 [ Section No. 10.13.2.1 ]

10.13.2.1*

When voice instructions are in progress, visible appliances in same area where speakers are activatedshall also be activated where required by the emergency response plan. (SIG-ECS)


Submitter Full Name: Lee Richardson


Street Address:

City:

State:

Zip:

Submittal Date: Mon Oct 07 11:58:22 EDT 2013

Committee Statement

CommitteeStatement:

This paragraph and its related annex material is deleted. The subject matter is moreappropriately addressed under 10.12. See FR 363. This FR also deletes A.10.13.2.1.

ResponseMessage:


124 of 326 11/21/2013 1:03 PM

First Revision No. 346-NFPA 72-2013 [ Global Input ]

Type your content here ...

Reorganize Chapter 24 in accordance with the attached outline. (Ch 24 ECS -Reorganization Global Input.docx)



Attachment_for_FR_346._no_edits.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The TC accepts the submitter’s Chapter 24 reorganization. The TC agrees to renumber therequirements and the corresponding annex text. This numbering produces a high levelrenumbering outline only and Editorial is to develop the lower level renumbering.

ResponseMessage:

Public Input No. 240-NFPA 72-2013 [Global Input]


23 of 326 11/21/2013 1:03 PM

Reorganization of Chapter 24 – Global Input

Chapter 24 Emergency Communications Systems (ECS)

24.1 Application.

24.2 Purpose.

24.3 General.

24.4 One-Way Emergency Communications Systems.

24.4.1 General.

[24.4.1.1 through 24.4.1.4 relocated by separate PI]

24.4* [24.4.2*] In-Building Fire Emergency Voice/Alarm Communications Systems (EVACS).

24.5* [24.4.3*] In-Building Mass Notification Systems.

24.6* [24.4.4*] Wide-Area Mass Notification Systems.

24.7* [24.4.5*] Distributed Recipient Mass Notification Systems (DRMNSs).

24.5 Two-Way, In-Building Emergency Communications Systems.

24.8* [24.5.1*] Two-Way, In-Building Wired Emergency Services Communications Systems.

24.9* [24.5.2*] Two-Way Radio Communications Enhancement Systems.

24.10* [24.5.3*] Area of Refuge (Area of Rescue Assistance) Emergency Communications Systems.

24.11 [24.5.4] Elevator Emergency Communications Systems.

24.12* [24.6*] Information, Command, and Control.

24.13* [24.7*] Performance-Based Design of Mass Notification Systems.

24.14 [24.8] Documentation.

First Revision No. 304-NFPA 72-2013 [ New Section after 24.3.1 ]

24.3.1* Emergency Message Content.

Emergency messages shall have a content that is:

(1) Appropriate for the intended message recipients

(2) Focused on protective actions that the intended message recipients are to take




Street Address:

City:

State:

Zip:

Submittal Date: Wed Oct 02 17:47:26 EDT 2013

Committee Statement

CommitteeStatement:

Emergency Communication Systems messages need to have content that is thought throughand is based on technical studies on the content of messaging. This proposed section is the startof this process.

ResponseMessage:



201 of 326 11/21/2013 1:03 PM


24.3.6.4

The utilization of shared pathway levels, as specified in Section 12.5 , for Class N pathways used inemergency communication systems to support ancillary functions, devices, or systems via commonpathways, shall be determined by a risk analysis and approved by the AHJ.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

MNS and ECS designs can be straightforward or complex depending on the evaluation of the risksand the requirements of emergency response plans. With the introduction of the Class N proposal, aconverged network, where MSN equipment (i.e. digitally sourced PoE speakers/intercoms and textualand graphical visual appliances) could be co-located and integrated on a shared network with otherinfrastructure systems and components (i.e. security access control, surveillance cameras,environmental controls including air handling and lighting). All of these system may be required tohave a role in an emergency response plan. In some cases integrated systems may be able toachieve higher levels of performance and functionality then separate isolated systems. A commoninfrastructure, that also supports ancillary functions, may be integrated into the business functions of afacility providing efficiencies for maintenance that are more challenging with separate divergenttechnologies. For example, in a Local Area Network, that was depended on for every day everyminute operation, an outage would not be tolerated, where as a trouble indication on a fire alarm panelmay receive a lower level of attention. Currently, it is proposed that a Class N network be limited toShared Pathway level 3, which requires dedicated equipment, separate from any other system. Thiscode does not specifically indicate conditions were Shared Pathway Class 0-2 are permissible. Thisproposal seeks to address this by taking advantage of the risk analysis approach used in chapter 24.For MNS and ECS system design, there is the opportunity for converged networks to become feasiblewithin the structure of this code. Not all facilities would have the technical competencies such that theevaluation of the risks of shared pathway level 0-2 (converged network) would result in an improvedoverall MNS/ECS design. However, in instances where technical competencies do exist (i.e. military,law enforcement, national security organizations, transportation authorities, etc.), this code should notunduly restrict innovation of design, and the ongoing support and maintenance benefits that arepossible, which established technologies can provide for a MNS or ECS.

ResponseMessage:



202 of 326 11/21/2013 1:03 PM


Relocate 24.3.6 and related annex material to become the last subsection in 24.3.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The revision allows alternatives to address situations where the cabling would have a fire ratingexceeding the building construction and an option to provide robustness through redundancy andperformance.

ResponseMessage:



16 of 326 11/21/2013 1:03 PM


24.4.1 General.

24.4.1.1 *

Messages shall be developed for each scenario developed in the emergency response plan.

24.4.1.2 *

A message template shall be developed for each message required in 24.4.1.1 .

24.4.1.3

For an evacuation message, a tone in accordance with 18.4.2 shall be used with a minimum of twocycles preceding and following the voice message.

24.4.1.4

Test messages shall clearly state the phrase “This is a test.”




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Relocate paragraphs 24.4.1.1, 24.4.1.2, 24.4.1.3, and 24.4.1.4 and associated Annex material tonew 24.3.6 Messages for One-Way Emergency Communications Systems and renumbersubsequent sections. Relocation places the requirements in a more user-friendly location. Thisproposal is the work product of a Chapter 24 Chairman-appointed Task Group on Renumbering. TGmembers: Bruce Fraser (chair), Andrew Woodward, Rodger Reiswig, and Sean Remke.

ResponseMessage:



17 of 326 11/21/2013 1:03 PM




24.3.14 Pathway Survivability.

24.3.14.1

Pathway survivability levels shall be as described in Section 12.4 .

24.3.14.2

Other component survivability shall comply with the provisions of 24.4.8.5.6 .

24.3.14.3*

The pathway survivability requirements in 24.3.14.4 through 24.3.14.12 shall apply to notificationand communications circuits and other circuits necessary to ensure the continued operation of theemergency communications system.

24.3.14.4

In-building fire emergency voice/alarm communications systems shall comply with 24.3.14.4.1 or24.3.14.4.2 .

24.3.14.4.1

For systems employing relocation or partial evacuation, a Level 2 or Level 3 pathway survivability shallbe required.

Exception No. 1: Level 1 shall be permitted where notification or evacuation zones are separated byless than 2-hour fire-rated construction.

Exception No. 2: Level 1 shall be permitted where there are at least two pathways provided that areseparated by at least one-third the maximum diagonal of the notification or evacuation zones that thepathways are passing through and the pathway is Class X or Class N.

24.3.14.4.2

For systems that do not employ relocation or partial evacuation, a Level 0, Level 1, Level 2, or Level 3pathway survivability shall be required.

24.3.14.4.3

Refer to Annex F for previous nomenclature and cross reference.

24.3.14.5

Pathway survivability levels for in-building mass notification systems shall be determined by the riskanalysis.

24.3.14.6

Pathway survivability levels for wide area mass notification systems shall be determined by the riskanalysis.

24.3.14.7

Two-way in-building wired emergency communications systems shall have a pathway survivability ofLevel 2 or Level 3.

Exception: Level 1 shall be permitted where the building is less than 2-hour fire-rated construction.

24.3.14.8

Two-way radio communications enhancement systems shall comply with 24.3.14.8.1 through24.3.14.8.4 .

24.3.14.8.1*

Where a two-way radio communications enhancement system is used in lieu of a two-way in-buildingwired emergency communications system, it shall have a pathway survivability of Level 1, Level 2, orLevel 3.

Exception: Where leaky feeder cable is utilized as the antenna, it shall not be required to be installedin metal raceway.

24.3.14.8.1.1

The feeder and riser coaxial cables shall be rated as plenum cables.


203 of 326 11/21/2013 1:03 PM

24.3.14.8.1.2

The feeder coaxial cables shall be connected to the riser coaxial cable using hybrid coupler devices of avalue determined by the overall design.

24.3.14.8.2

Where a two-way radio communications enhancement system is used in lieu of a two-way in-buildingwired emergency communications system, the design of the system shall be approved by the authorityhaving jurisdiction.

24.3.14.8.3*

Riser coaxial cables shall be rated as riser cables and routed through a 2-hour-rated enclosure.

24.3.14.8.4

The connection between the riser and feeder coaxial cables shall be made within the 2-hour-ratedenclosure, and passage of the feeder cable in and out of the 2-hour-rated enclosure shall be firestoppedto 2-hour ratings.

24.3.14.9*

Area of refuge (area of rescue assistance) emergency communications systems shall comply with24.3.14.9.1 and 24.3.14.9.2 .

24.3.14.9.1

Area of refuge emergency communications systems shall have a pathway survivability of Level 2 orLevel 3.

Exception: Level 1 shall be permitted where the building is less than 2-hour fire-rated construction.

24.3.14.9.2

Circuits intended to transmit off-premises shall have a pathway survivability of Level 0, Level 1, Level 2,or Level 3.

24.3.14.10

Elevator emergency communications systems shall have a pathway survivability of Level 0, Level 1,Level 2, or Level 3.

24.3.14.11

Central command station emergency communications systems shall have pathway survivability asdetermined by the risk analysis.

24.3.14.12

All other emergency communications system circuits shall have pathway survivability as determined bythe risk analysis.



FR_357.docx FR 357 legislative text




Street Address:

City:

State:

Zip:

Submittal Date: Fri Oct 04 13:17:10 EDT 2013

Committee Statement

CommitteeStatement:

The revision to 24.3.6.4.1 permits alternatives to address situations where the cabling would have afire rating exceeding the building construction and an option to provide robustness throughredundancy and performance. The revision to 24.3.6.7 permits the alternative to address thesituation where the cabling would have a fire rating exceeding the building construction. The revisionto 24.3.6.9.1 permits the alternative to address the situation where the cabling would have a fire


204 of 326 11/21/2013 1:03 PM

rating exceeding the building construction.

ResponseMessage:

Public Input No. 407-NFPA 72-2013 [Section No. 24.3.6.4.1]

Public Input No. 409-NFPA 72-2013 [Section No. 24.3.6.7]



205 of 326 11/21/2013 1:03 PM

24.3.14 24.3.6 Pathway Survivability.

24.3.14.1 24.3.6.1 Pathway survivability levels shall be as described in Section 12.4.

24.3.14.2 24.3.6.2 Other component survivability shall comply with the provisions of

24.4.2.8.5.6.

24.3.14.3* 24.3.6.3* The pathway survivability requirements in 24.3.14.4 through 24.3.14.12

shall apply to notification and communications circuits and other circuits necessary to ensure the

continued operation of the emergency communications system.

24.3.14.4 24.3.6.4 In-building fire emergency voice/alarm communications systems shall

comply with 24.3.14.4.1 or 24.3.14.4.2.

24.3.14.4.1 24.3.6.4.1 For systems employing relocation or partial evacuation, a Level 2 or

Level 3 pathway survivability shall be required.

Exceptions:

(1) Level 1 shall be permitted where notification or evacuation zones are separated by less than

2-hour fire rated construction.

(2) Level 1 shall be permitted where there are at least two pathways provided that are separated

by at least 1/3 the maximum diagonal of the notification or evacuation zones that the pathways

are passing thru and the pathway is Class X or Class N.

24.3.14.4.2 24.3.6.4.2 For systems that do not employ relocation or partial evacuation, a Level

0, Level 1, Level 2, or Level 3 pathway survivability shall be required.

24.3.14.4.3 24.3.6.4.3 Refer to Annex F for previous nomenclature and cross reference.

24.3.14.5 24.3.6.5 Pathway survivability levels for in-building mass notification systems shall

be determined by the risk analysis.

24.3.14.6 24.3.6.6 Pathway survivability levels for wide area mass notification systems shall be

determined by the risk analysis.

24.3.14.7 24.3.6.7 Two-way in-building wired emergency communications systems shall have

a pathway survivability of Level 2 or Level 3.

Exception:

Level 1 shall be permitted where the building is less than 2-hour fire rated construction.

24.3.14.8 24.3.6.8 Two-way radio communications enhancement systems shall comply with

24.3.14.8.1 through 24.3.14.8.4.

24.3.14.8.1* 24.3.6.8.1* Where a two-way radio communications enhancement system is used

in lieu of a two-way in-building wired emergency communications system, it shall have a

pathway survivability of Level 1, Level 2, or Level 3.

Exception: Where leaky feeder cable is utilized as the antenna, it shall not be required to be

installed in metal raceway.

24.3.14.8.1.1 24.3.6.8.1.1 The feeder and riser coaxial cables shall be rated as plenum cables.

24.3.14.8.1.2 24.3.6.8.1.2 The feeder coaxial cables shall be connected to the riser coaxial

cable using hybrid coupler devices of a value determined by the overall design.

24.3.14.8.2 24.3.6.8.2 Where a two-way radio communications enhancement system is used in

lieu of a two-way in-building wired emergency communications system, the design of the system

shall be approved by the authority having jurisdiction.

24.3.14.8.3* 24.3.6.8.3* Riser coaxial cables shall be rated as riser cables and routed through a

2-hour-rated enclosure.

24.3.14.8.4 24.3.6.8.4 The connection between the riser and feeder coaxial cables shall be

made within the 2-hour-rated enclosure, and passage of the feeder cable in and out of the 2-hour-

rated enclosure shall be firestopped to 2-hour ratings.

24.3.14.9* 24.3.6.9* Area of refuge (area of rescue assistance) emergency communications

systems shall comply with 24.3.14.9.1 and 24.3.14.9.2.

24.3.14.9.1 24.3.6.9.1 Area of refuge emergency communications systems shall have a

pathway survivability of Level 2 or Level 3.

Exception:

Level 1 shall be permitted where the building is less than 2-hour fire rated construction.

24.3.14.9.2 24.3.6.9.2 Circuits intended to transmit off-premises shall have a pathway

survivability of Level 0, Level 1, Level 2, or Level 3.

24.3.14.10 24.3.6.10 Elevator emergency communications systems shall have a pathway

survivability of Level 0, Level 1, Level 2, or Level 3.

24.3.14.11 24.3.6.11 Central command station emergency communications systems shall have

pathway survivability as determined by the risk analysis.

24.3.14.12 24.3.6.12 All other emergency communications system circuits shall have pathway

survivability as determined by the risk analysis.


24.3.8* System Classification.

Emergency communications systems (ECS) shall consist of two classifications of systems, one-way andtwo-way.

24.3.8.1

One-way emergency communications systems shall consist of the following:

(1) In-building fire emergency voice/alarm communications systems (EVACS) (see 24.4.2)

(2) In-building mass notification systems (see 24.4.3)

(3) Wide-area mass notification systems (see 24.4.4)

(4) Distributed recipient mass notification systems (DRMNS) (see 24.4.5)

24.3.8.2

Two-way emergency communications systems shall consist of the following:

(1) Two-way, in-building wired emergency services communications systems (see 24.5.1)

(2) Two-way radio communications enhancement systems (see 24.5.2)

(3) Area of refuge (area of rescue assistance) emergency communications systems (see 24.5.3)

(4) Elevator emergency communications systems (see 24.5.4)




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This material provides additional information for the benefit of the document user. This proposal isthe work product of a Chapter 24 Chairman-appointed Task Group on Renumbering. TG members:Bruce Fraser (chair), Andrew Woodward, Rodger Reiswig, and Sean Remke.

ResponseMessage:



206 of 326 11/21/2013 1:03 PM


24.3.10* Design Documentation .

Design documents in accordance with Section 7.3 shall be prepared prior to installation of any newsystem.

24.3.10.1

Systems that are altered shall have design documents prepared applicable that apply to the portions ofthe system that are altered.

24.3.10.2

Documents shall be revised as necessary following installation to represent as-built conditions and includerecord drawings.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

More clearly describes the section. This proposal is the work product of a Chapter 24 Chairman-appointed Task Group on Documentation. TG members: Bruce Fraser (chair), AndrewWoodward, and Rodger Reiswig.

ResponseMessage:



207 of 326 11/21/2013 1:03 PM


24.3.11 Listing Control Unit Listing for Mass Notification Systems .

Control units installed as part of a mass notification system shall be in compliance with this Code andapplicable standards such as ANSI/UL 864, Standard for Control Units and Accessories for Fire AlarmSystems, ; or ANSI/UL 2017, Standard for General-Purpose Signaling Devices and Systems, ; orANSI/UL 2572, Mass Notification Systems.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

More clearly describes the section. This proposal is the work product of a Chapter 24 Chairman-appointed Task Group on Renumbering. TG members: Bruce Fraser (chair), Andrew Woodward,Rodger Reiswig, and Sean Remke.

ResponseMessage:



208 of 326 11/21/2013 1:03 PM


24.3.12.3

The detail and complexity of the risk analysis shall be commensurate with the complexity of the facilityfor which the mass notification system is designed.

24.3.12.4

The risk analysis shall be permitted to be limited in scope to address the communication requirementsof an existing emergency response plan.







Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC adds text to 24.3.11 for risk analysis for mass notification systems.

Response Message:


209 of 326 11/21/2013 1:03 PM

24.3.12.3 The detail and complexity of the risk analysis shall be commensurate with the

complexity of the facility for which the mass notification system is designed.

24.3.12.4 The risk analysis shall be permitted to be limited in scope to address the

communication requirements of an existing emergency response plan.


24.3.12.5

Performance-based design and the risk analysis shall be applied in accordance with Section 24.7 .




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

As written, Section 24.3.11.3 is confusing since it refers to performance-based designs which iscovered in Section 24.7. Section 24.3.11 is titled "Risk Analsiis for Mass Notification Systems" andtherefore should not be referencing performanced-based designs. Performanced-based designsincorporate risk anaylsis and not vise-vers. This revision should make this Section more userfriendly.

ResponseMessage:



210 of 326 11/21/2013 1:03 PM


24.4.5 Operating Controls.

24.4.5.1*

Controls for the in-building fire emergency voice/alarm communications system shall be at a locationapproved by the authority having jurisdiction.

24.4.5.2

Controls shall be located or secured to allow access only by trained and authorized personnel.

24.4.5.3

Operating controls shall be clearly identified.

24.4.5.4

If there are multiple in-building fire emergency voice/alarm communications control locations, only oneshall be in control at any given time.

24.4.5.5

The location having control of the system shall be identified by a visible indication at that location.

24.4.5.6

Manual controls shall be arranged to provide visible indication of the on/off status for their associatedevacuation signaling zone.

24.4.5.7

If live voice instructions are provided, they shall perform as follows:

(1) They shall override previously initiated signals to the selected notification zone.

(2) They shall have priority over any subsequent automatically initiated signals to the selectednotification zone.

(3) If a previously initiated recorded message is interrupted by live voice instructions, upon release of themicrophone, the previously initiated recorded messages to the selected notification zones shall notresume playing automatically unless required by the emergency response plan.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

More clearly describes the section. This proposal is the work product of a Chapter 24 Chairman-appointed Task Group on Renumbering. TG members: Bruce Fraser (chair), Andrew Woodward,Rodger Reiswig, and Sean Remke.

ResponseMessage:


211 of 326 11/21/2013 1:03 PM

24.4.5 24.4.2.5 Operating Controls.

24.4.5.1* 24.4.2.5.1* Controls for the in-building fire emergency voice/alarm communications

system shall be at a location approved by the authority having jurisdiction.

24.4.5.2 24.4.2.5.2 Controls shall be located or secured to allow access only by trained and

authorized personnel.

24.4.5.3 24.4.2.5.3 Operating controls shall be clearly identified.

24.4.5.4 24.4.2.5.4 If there are multiple in-building fire emergency voice/alarm

communications control locations, only one shall be in control at any given time.

24.4.5.5 24.4.2.5.5 The location having control of the system shall be identified by a visible

indication at that location.

24.4.5.6 24.4.2.5.6 Manual controls shall be arranged to provide visible indication of the on/off

status for their associated evacuation signaling zone.

24.4.5.7 24.4.2.5.7 If live voice instructions are provided, they shall perform as follows:

(1) They shall override previously initiated signals to the selected notification zone(s).

(2) They shall have priority over any subsequent automatically initiated signals to the selected

notification zone(s).

(3) If a previously initiated recorded message is interrupted by live voice instructions, upon

release releasing of the microphone, the previously initiated recorded messages to the

selected notification zones shall not resume playing automatically unless required by the

emergency response plan.



212 of 326 11/21/2013 1:03 PM


24.4.8* Relocation and Partial Evacuation.

The requirements of 24.4.8 shall apply only to systems used for relocation or partial evacuation during afire condition.

24.4.8.1

New systems employing relocation or partial evacuation shall require documentation in accordance withSections 7.3, 7.4, and 7.5 in addition to the minimum documentation requirements of Sections 7.2 and24.15.

24.4.8.2

Systems shall be provided with manual voice transmission capabilities selectively to one or more zones oron an all-call basis.

24.4.8.3

Under a fire condition, where the system is used to transmit relocation instructions or other fire emergencynon-evacuation messages, a 1-second to 3-second alert tone followed by a message (or messages wheremulti-channel capability is used) shall be provided.

24.4.8.3.1

The sequence [the alert tone followed by the message(s)] shall be repeated at least three times to informand direct occupants in the signaling zone where the alarm initiation originated, as well as otherevacuation signaling zones in accordance with the building fire safety plan.

24.4.8.3.2

Approved alternative fire alarm notification schemes shall be permitted so long as the occupants areeffectively notified and are provided instructions in a timely and safe manner in accordance with thebuilding fire safety plan.

24.4.8.4

Where provided, loudspeakers in each enclosed stairway, each exit passageway, and each group ofelevator cars within a common hoistway shall be connected to separate notification zones for manualpaging only.

24.4.8.4.1

The evacuation signal shall not operate in elevator cars, exit stair enclosures, and exit passageways.

24.4.8.4.2

Manually activated speakers shall be permitted in exit stair enclosures and exit passageways in buildingsthat have emergency voice/alarm communications systems in accordance with 24.4.

24.4.8.5

The requirements of 24.4.8.5 shall apply to both audible (tone and voice) and visible notification appliancecircuits.

24.4.8.5.1*

Fire alarm systems used for partial evacuation and relocation shall be designed and installed such thatattack by fire within a signaling zone does not impair control and operation of the notification appliancesoutside the evacuation signaling zone.

24.4.8.5.2

Performance features provided to ensure operational reliability under adverse conditions shall bedescribed and technical justification provided in the documentation submitted to the authority havingjurisdiction with the analysis required in 23.4.3.1.

24.4.8.5.3*

All circuits necessary for the operation of the notification appliances shall be protected until they enter thesignaling zone that they serve by the protection provided by the pathway survivability level required in24.3.14.4.1 or by performance alternatives approved by the authority having jurisdiction.


213 of 326 11/21/2013 1:03 PM

24.4.8.5.4

Where the separation of in-building fire emergency voice/alarm control equipment locations results in theportions of the system controlled by one location being dependent upon the control equipment in otherlocations, the circuits between the dependent controls shall be protected against attack by fire by theprotection provided by the pathway survivability level required in 24.3.14.4.1 or by performancealternatives approved by the authority having jurisdiction.

24.4.8.5.5

Protection of circuits between redundant control equipment locations that are not mutually dependent shallnot be required.

24.4.8.5.6

Where the separation of the in-building fire emergency voice/alarm control equipment occurs as in24.4.8.5.4, and where the circuits are run through junction boxes, terminal cabinets or control equipment,such as system control units, power supplies and amplifiers, and where cable integrity is not maintained,these components shall, in addition to the pathway survivability required by 24.3.14.4.1, be protected byusing one of the following methods:

(1) A 2-hour fire-rated enclosure

(2) A 2-hour fire-rated room

(3) Other equivalent means to provide a 2-hour fire resistance–rating approved by the authority havingjurisdiction

24.4.8.5.7

Paragraphs 24.4.8 through 24.4.8.5.6 shall not automatically apply when relocation or partial evacuationis of a non-fire emergency unless identified and required by a risk analysis.



FR_358_Legislative_Text.docx




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC deletes “evacuation” in 24.4.2.8.3.1, 24.4.2.8.5.1 and 24.4.2.8.5.3.

Response Message:



214 of 326 11/21/2013 1:03 PM

24.4.8* 24.4.2.8* Relocation and Partial Evacuation. The requirements of 24.4.2.8 shall apply

only to systems used for relocation or partial evacuation during a fire condition.

24.4.8.1 24.4.2.8.1 New systems employing relocation or partial evacuation shall require

documentation in accordance with Sections 7.3, 7.4, and 7.5 in addition to the minimum

documentation requirements of Sections 7.2 and 24.8.

24.4.8.2 24.4.2.8.2 Systems shall be provided with manual voice transmission capabilities

selectively to one or more zones or on an all-call basis.

24.4.8.3 24.4.2.8.3 Under a fire condition, where the system is used to transmit relocation

instructions or other fire emergency non-evacuation messages, a 1-second to 3-second alert tone

followed by a message (or messages where multi-channel capability is used) shall be provided.

24.4.8.3.1 24.4.2.8.3.1 The sequence [the alert tone followed by the message(s)] shall be

repeated at least three times to inform and direct occupants in the evacuation signaling zone

where the alarm initiation originated, as well as other evacuation signaling zones in accordance

with the building fire safety plan.

24.4.8.3.2 24.4.2.8.3.2 Approved alternative fire alarm notification schemes shall be permitted

so long as the occupants are effectively notified and are provided instructions in a timely and

safe manner in accordance with the building fire safety plan.

24.4.8.4 24.4.2.8.4 Where provided, loudspeakers in each enclosed stairway, each exit

passageway, and each group of elevator cars within a common hoistway shall be connected to

separate notification zones for manual paging only.

24.4.8.4.1 24.4.2.8.4.1 The evacuation signal shall not operate in elevator cars, exit stair

enclosures, and exit passageways.

24.4.8.4.2 24.4.2.8.4.2 Manually activated speakers shall be permitted in exit stair enclosures

and exit passageways in buildings that have emergency voice/alarm communications systems in

accordance with 24.4.2.

24.4.8.5 24.4.2.8.5 The requirements of 24.4.2.8.5 shall apply to both audible (tone and voice)

and visible notification appliance circuits.

24.4.8.5.1* 24.4.2.8.5.1* Fire alarm systems used for partial evacuation and relocation shall be

designed and installed such that attack by fire within a an evacuation signaling zone does not

impair control and operation of the notification appliances outside the evacuation signaling zone.

24.4.8.5.2 24.4.2.8.5.2 Performance features provided to ensure operational reliability under

adverse conditions shall be described and technical justification provided in the documentation

submitted to the authority having jurisdiction with the analysis required in 23.4.3.1.

24.4.8.5.3* 24.4.2.8.5.3* All circuits necessary for the operation of the notification appliances

shall be protected until they enter the evacuation signaling zone that they serve by the protection

provided by the pathway survivability level required in 24.3.6.4.1 or by performance alternatives

approved by the authority having jurisdiction.

24.4.8.5.4 24.4.2.8.5.4 Where the separation of in-building fire emergency voice/alarm control

equipment locations results in the portions of the system controlled by one location being

dependent upon the control equipment in other locations, the circuits between the dependent

controls shall be protected against attack by fire by the protection provided by the pathway

survivability level required in 24.3.6.4.1 or by performance alternatives approved by the

authority having jurisdiction.

24.4.8.5.5 24.4.2.8.5.5 Protection of circuits between redundant control equipment locations

that are not mutually dependent shall not be required.

24.4.8.5.6 24.4.2.8.5.6 Where the separation of the in-building fire emergency voice/alarm

control equipment occurs as in 24.4.2.8.5.4, and where the circuits are run through junction

boxes, terminal cabinets or control equipment, such as system control units, power supplies and

amplifiers, and where cable integrity is not maintained, these components shall, in addition to the

pathway survivability required by 24.3.6.4.1, be protected by using one of the following

methods:

(1) A 2-hour fire rated enclosure

(2) A 2-hour fire rated room

(3) Other equivalent means to provide a 2-hour fire resistance rating approved by the authority

having jurisdiction

24.4.8.5.7 24.4.2.8.5.7 Paragraphs 24.4.2.8 through 24.4.2.8.5.6 shall not automatically apply

when relocation or partial evacuation is of a non-fire emergency unless identified and required

by a risk analysis.


24.5.3 Notification Coverage.

24.5.3.1*

The mass notification system shall provide for live voice and prerecorded localized messaging within aprotected individual building, areas surrounding the building, and other outdoor designated areas.

24.5.3.2

System design shall incorporate designation of acoustically distinguishable spaces (ADS) within anyoccupiable areas as required in Chapter 18.

24.5.3.3

Notification zones shall be established on the basis of a risk analysis.

24.5.3.4*

If the mass notification system serves more than one building, it shall be capable of providing separatemessages to one individual building or to multiple buildings at any given time.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Additional wording provides heading more clarity. This proposal is the work product of a Chapter24 Chairman-appointed Task Group on Renumbering. TG members: Bruce Fraser (chair), AndrewWoodward, Rodger Reiswig, and Sean Remke.

ResponseMessage:



215 of 326 11/21/2013 1:03 PM

25.5.3 24.4.3.3 Notification Coverage.

24.5.3.1* 24.4.3.3.1* The mass notification system shall provide for live voice and prerecorded

localized messaging within a protected individual building, areas surrounding the building, and

other outdoor designated areas.

24.5.3.2 24.4.3.3.2 System design shall incorporate designation of acoustically distinguishable

spaces (ADS) within any occupiable areas as required in Chapter 18.

24.5.3.3 24.4.3.3.3 Notification zones shall be established on the basis of a risk analysis.

24.5.3.4* 24.4.3.3.4* If the mass notification system serves more than one building, it shall be

capable of providing separate messages to one individual building or to multiple buildings at any

given time.

First Revision No. 316-NFPA 72-2013 [ Section No. 24.4.3.5.1 ]

24.4.3.5.1* Security.

Security for mass notification systems documentation shall be determined by the stakeholders inaccordance with 7.7.3 .

24.4.3.5.2 Record of Completion.

24.4.3.5.2.1*

A record of completion shall be required in accordance with Chapter 7 for documentation of the massnotification system.

24.4.3.5.2.2

All systems that are modified after the initial installation shall have the original, or latest overall system,record of completion revised or attached to show all changes from the original information and shall beidentified with a revision date.

24.4.3.5.3 Required Documentation.

Every system shall include the following documentation, which shall be delivered to the owner or theowner’s representative upon final acceptance of the system:

(1) Owner’s manual including a complete set of operations and maintenance manuals, manufacturer’spublished instructions, and product data sheets covering all system equipment

(2) Record and as-built drawings

(3) Written sequence of operation

(4) One current copy of the record of completion form, updated to reflect all system additions ormodifications

(5) For software-based systems, a record copy of the system-specific software

(6) Copy of the site-specific software stored on-site in nonvolatile, nonerasable, nonrewritablememory

(7) Emergency response plan, with operational management procedures defined for managementand activation of the system

(8) Risk analysis, when provided

24.4.3.5.4 Risk Analysis Documentation.

Document accessibility shall be in accordance with 7.7.2 and 24.4.3.5.4 .

24.4.3.5.4.1

When a risk analysis is required to be prepared, such as for a mass notification system, findings of therisk assessment shall be documented.

24.4.3.5.4.2

When identified by the stakeholders, security and protection of the risk analysis shall be in accordancewith 24.4.3.5.1 .

24.4.3.5.5 Document Accessibility.

24.4.3.5.5.1

An as-built plans cabinet shall be provided to house the documentation required in 24.4.3.5.3 .

24.4.3.5.5.2

The cabinet shall be sized so that it can neatly contain all necessary documentation, including futureinspection and service reports.

24.4.3.5.5.3

Mass notification system and fire alarm system as-built plans and other related documentation shall bepermitted to be maintained together, including the appearance of both systems on the same drawings.



216 of 326 11/21/2013 1:03 PM






Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Eliminate duplicative material – covered by 24.4.3.5, 24.8, 7.3.6, and 24.3.11 This proposal is thework product of a Chapter 24 Chairman-appointed Task Group on Documentation. TG members:Bruce Fraser (chair), Andrew Woodward, and Rodger Reiswig.

ResponseMessage:

Public Input No. 444-NFPA 72-2013 [Sections 24.4.3.5.1, 24.4.3.5.2, 24.4.3.5.3, 24.4.3.5.4, 24...]



217 of 326 11/21/2013 1:03 PM

24.4.3.5.1* Security. Security for mass notification systems documentation shall be determined

by the stakeholders in accordance with 7.7.3.

24.4.3.5.2 Record of Completion.

24.4.3.5.2.1* A record of completion shall be required in accordance with Chapter 7 for

documentation of the mass notification system.

24.4.3.5.2.2 All systems that are modified after the initial installation shall have the original, or

latest overall system, record of completion revised or attached to show all changes from the

original information and shall be identified with a revision date.

24.4.3.5.3 Required Documentation. Every system shall include the following documentation,

which shall be delivered to the owner or the owner’s representative upon final acceptance of the

system:

(1) Owner’s manual including a complete set of operations and maintenance manuals,

manufacturer’s published instructions, and product data sheets covering all system

equipment

(2) Record and as-built drawings

(3) Written sequence of operation

(4) One current copy of the record of completion form, updated to reflect all system additions

or modifications

(5) For software-based systems, a record copy of the system-specific software

(6) Copy of the site-specific software stored on-site in nonvolatile, nonerasable, nonrewritable

memory

(7) Emergency response plan, with operational management procedures defined for

management and activation of the system

(8) Risk analysis, when provided

24.4.3.5.4 Risk Analysis Documentation. Document accessibility shall be in accordance with

7.7.2 and 24.4.3.5.4.

24.4.3.5.4.1 When a risk analysis is required to be prepared, such as for a mass notification

system, findings of the risk assessment shall be documented.

24.4.3.5.4.2 When identified by the stakeholders, security and protection of the risk analysis

shall be in accordance with 24.4.3.5.1.

24.4.3.5.5 Document Accessibility.

24.4.3.5.5.1 An as-built plans cabinet shall be provided to house the documentation required in

24.4.3.5.3.

24.4.3.5.5.2 The cabinet shall be sized so that it can neatly contain all necessary

documentation, including future inspection and service reports.

24.4.3.5.5.3 Mass notification system and fire alarm system as-built plans and other related

documentation shall be permitted to be maintained together, including the appearance of both

systems on the same drawings.


24.5.15* Mounting of LOC Controls

24.5.15.1

Unless otherwise established through the emergency response plan, controls that are intended to beaccessed by authorized users shall be mounted in accordance with 24.5.15.

24.5.15.2

LOC controls, including switches, microphone, latches, and so forth, shall be located above the finishedfloor a minimum of 36 in. (91 cm) and a maximum of 48 in. (122 cm) where the horizontal reach is lessthan 10 in. (25 cm).

24.5.15.3

If a horizontal reach of 10 in. (25 cm) to 24 in. (61 cm) is required, the maximum elevation shall be limitedto 42 in. (107 cm) above the finished floor and the minimum elevation shall be limited to 28 in. (71 cm).

24.5.15.4

Text and visual indicators, including lamps, screens, displays, instructions, or labels, associated withcontrol or operation shall be visible within all points of elevation between 40 in. (102 cm) and 60 in. (152cm) above the finished floor.

24.5.15.5

Where controls and information are provided in accordance with 24.5.15.2 through 24.5.15.4, provision ofadditional or redundant controls shall be permitted within the same vicinity at an elevation or reach otherthan those indicated.

24.5.15.6

Dimensions other than those identified in 24.5.15.2 through 24.5.15.4 shall be permitted whendocumented within the emergency response plan that ADA guidelines are not applicable, or whenotherwise required by the AHJ.



Attachment_for_FR_319.docx

Attachment_Figures_for_FR_319.pdf




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Proposed language was assignment of an ECS task group to address mounting heights ofcontrols related to mass notification. These elevations could also apply to other control equipmentsuch as area of refuge communications, etc.

ResponseMessage:



218 of 326 11/21/2013 1:03 PM

Attachment for FR 319

A.24.4.3.14. Control functions need to be accessible for those intended to use them. This

requirement is not intended to require that the control enclosure be within the dimensions, but

rather the respective buttons, latches, microphone, and other items the user will need to have

within reach and view. Figure A.24.4.3.14(a) applies when the horizontal reach is less than 10

in. (25 cm). Figure A.24.4.3.14(b) applies when the horizontal reach is between 10 in. (25 cm)

and 24 in. (61 cm).

Titles for figures:

Figure A.24.4.3.14(a) Horizontal Reach of Less Than 10 in. (25 cm).

Figure A.24.4.3.14(b) Horizontal Reach of 10 in. (25 cm) to 24 in. (61 cm).

Metric dimensions for figures:

10” = 25cm

28” = 71cm

24” = 61cm

36” = 91cm

40” = 102cm

42” = 107cm

48” = 122cm

60” = 152cm


24.5.19.4

Primary textual and graphical visible appliances other than a main control unit shall be permitted to nothave a dedicated primary power circuit as required by Chapter 10 but shall meet all other requirementsfor the monitoring of primary power and all requirements for secondary power.



FR_317_LEGISLATIVE_TEXT.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

In the 2013 edition of 72 section 24.4.3.18.7 was changed so that a requirement, applied tounmonitored textual and graphical visual appliances, was clarified to be specifically applied tosupplemental textual and graphical visual appliances. The conclusion being that it is permissible notto monitor supplemental textual and graphical appliances. However 24.4.3.18.4 makes no distinctionbetween primary and supplementary textual or graphical appliances, requiring the monitoring ofpower and secondary power for both. This change makes it clearer so that now the monitoringrequirements only apply only to primary textual and graphical appliances, which harmonizes with24.4.3.18.7, such that the two sections no longer have a conflicting context.

ResponseMessage:



219 of 326 11/21/2013 1:03 PM

24.5.19.4 24.4.3.18.4 Primary textual and graphical visible appliances other than a main

control unit shall be permitted to not have a dedicated primary power circuit as required by

Chapter 10, but shall meet all other requirements for the monitoring of primary power and all

requirements for secondary power.

First Revision No. 318-NFPA 72-2013 [ New Section after 24.4.3.18.7 ]

24.5.19.8

Addressable primary textual and graphical visible appliances using signaling line circuits shall meet theperformance requirements of Section 23.6.

24.5.19.9

Non-addressable primary textual and graphical visible appliance circuits shall meet the performancerequirements of Section 23.7.



FR_318.docx FR 318 in legislative text




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Graphical and textual appliances are directly referenced in multiple sections of NFPA 72 (in bothchapter 18 and 24), which also subject to chapters 7, 10, 12, 17, 21, 23, 26, & 27. Also they arefurther subdivided into two groups primary and supplemental, both being subjected to differentrequirements for monitoring for integrity. They are also referred to as appliances, implying that theyare notification appliances, but never stating directly the monitoring for integrity requirements for thetwo groups of textual and graphical appliances. The implication that they are notification appliances,and would therefore be subject to notification appliance circuit performance requirements, is confusedby the primary and secondary designations which have different monitoring requirements. Overall thiscomplexity creates the opportunity for misinterpretation. These two new sections clearly establish thereference to the performance requirements for both addressable and non-addressable appliancecircuits. It also makes it clear that supplemental textual and graphical appliances, which by definitionare not required by this code, are also not subject to these performance requirements. This distinctionsupports section 24.4.3.18.7, which establishes criteria for not monitoring supplemental textual andgraphical visual appliances.

ResponseMessage:

Public Input No. 489-NFPA 72-2013 [New Section after 24.4.3.18.7]


220 of 326 11/21/2013 1:03 PM

24.5.19.8 An addressable primary textual and graphical visible appliance using signaling line circuits shall meet the performance requirements of Section 23.6.

24.5.19.9 Non-addressable primary textual and graphical visible appliance circuits shall meet the performance requirements of Section 23.7.


24.4.4.4 Wide-Area Mass Notification System Components.

24.4.4.4.1 Emergency Command Center. Refer to Section

24.6 for requirements of an emergency command center.

24.4.4.4.2* High Power Speaker Array (HPSA). When required

by the risk analysis, high power speaker arrays (HPSAs)

shall be provided, installed, and maintained.

24.4.4.4.2.1 The HPSAshall be arranged in such a manner to

provide intelligible voice and audible tone communications.

(A) When multiple HPSAs are used, they shall be arranged in

physical or virtual notification zones so that each notification

zone can be individually controlled by the emergency command

center.

(B)* HPSAs shall be designed to maintain the intelligibility of

voice signals within the notification zone in accordance with

the requirements of Chapter 18.

24.4.4.4.2.2 Secondary power for HPSAs used for wide-area

mass notification systems shall have sufficient capacity to operate

the unit for a minimum of 7 days in standby, followed by 60

minutes of operation at full load.

24.4.4.4.2.3 An HPSA shall have the capability to provide

voice communications and tones as determined by the emergency

response plan.

24.4.4.4.2.4* An HPSA shall operate in the environment in

which it is located, considering such factors as temperature, humidity,

wind, dust, vibration, and other environmental factors.

24.4.4.4.3 High Power Speaker Array Enclosures.

24.4.4.4.3.1 Enclosures for HPSAs shall be of the NEMA 4 or

4X type.

24.4.4.4.3.2 HPSA enclosures shall have intrusion detection

that signals the emergency command center.

(A) The signal shall be initiated whenever the door of the

enclosure is in the open position.

(B) The transmitted signal shall be a latching supervisory signal.

24.4.4.4.4 High Power Speaker Array Mounting.

24.4.4.4.4.1 HPSAs shall be mounted at a minimum mounting

height that is based on the rated output of the array.

24.4.4.4.4.2* HPSAs shall be installed at a height and orientation

to prevent hearing damage to anyone in the immediate

vicinity of the speakers.


18 of 326 11/21/2013 1:03 PM

24.4.4.4.4.3 All external conductors (conductors passing outside

of the HPSA equipment cabinet) shall be provided with

surge suppression to minimize potential equipment damage

from lightning strikes.

24.4.4.4.5 High Power Speaker Array Noise Consideration.

HPSA notification zones shall not be used to provide mass

notification inside any structures.

24.4.4.4.6* High Power Speaker Array Structural Loads,Wind,

and Seismic Design. HPSAs and their supporting structures

shall meet the structural, wind, and seismic loads as identified

in the risk analysis.

24.4.4.4.7 Textual Visible Appliances. Textual visible appliances

shall meet the requirements of Section 18.9 and

24.4.3.18.

24.4.4.4.7.1 After loss of primary power, textual visible appliances

shall have sufficient secondary power to operate for a

minimum of 2 hours of continuous display time during an

emergency event.

24.4.4.4.7.2 Scrolling message boards shall be provided with

means to control the scrolling rate.

24.4.4.4.8 In-Building Mass Notification Systems. The inbuilding

mass notification system shall meet the requirements

of 24.4.3.

24.4.4.4.9 Interfaces with Wide-Area Mass Notification Systems.

Interfaces between wide-area mass notification systems

and in-building mass notification systems, other alert and notification

systems, regional mass notification systems, and offsite

interfaces shall have a standard interface method (such as

an audio line-level output and multiple relay contacts) or supply

the necessary communications protocols to provide interoperability

and a secure communications link.

24.4.4.4.9.1 The interface shall be such that the primary

function of both systems shall not be compromised.

24.4.4.4.9.2 The interface shall be monitored for integrity in

accordance with 10.6.9 and Sections 10.19 and 12.6, so that an

abnormal condition that could prevent reliable system operation

is audibly and visibly annunciated as a trouble signal at

both systems’ control units.

24.4.4.4.10 Control Hierarchy. There shall be a predefined

control hierarchy between the wide-area mass notification system,

the in-building mass notification system, and the regional

mass notification system for information flow from the remote

control center, as well as information from specific locations.

24.4.4.4.11 Communications Links.


19 of 326 11/21/2013 1:03 PM

24.4.4.4.11.1 The wide-area mass notification system, including

communications links, shall minimize the potential for

interference from jamming, spoofing, hacking, eavesdropping,

or other malicious acts.

24.4.4.4.11.2 The wide-area mass notification system shall have

a primary and redundant communications link with minimal

functional and spatial interconnection with each other.

24.4.4.4.11.3 Wide-area and in-building mass notification systems

equipment and interface methods connecting to, or utilizing,

public emergency alarm reporting systems and associated

communications infrastructure shall be electrically and

operationally compatible so as not to interfere with the public

emergency alarm reporting systems.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC agrees to renumber the requirements and the corresponding annex text.

Response Message:



20 of 326 11/21/2013 1:03 PM

First Revision No. 323-NFPA 72-2013 [ Section No. 24.4.4.4.2.2 ]

24.6.5.2

Secondary power for HPSAs used for wide-area mass notification systems shall have sufficient capacity tooperate the unit for a minimum of 3 days in standby, followed by 60 minutes of operation at full load.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The TC revises 24.4.4.4.2.2 to be performance rated only and to correlate with the currentrequirements of UFC 4-021-01.

ResponseMessage:



221 of 326 11/21/2013 1:03 PM

24.6.5.2 24.4.4.4.2.2 Secondary power for HPSAs used for wide-area mass notification

systems shall have sufficient capacity to operate the unit for a minimum of 3 7 days in standby,

followed by 60 minutes of operation at full load.

First Revision No. 321-NFPA 72-2013 [ Section No. 24.4.4.4.7.1 ]

24.6.10.1

After loss of primary power, primary textual visible notification appliances shall have sufficient secondarypower to operate for a minimum of 2 hours of continuous display time during an emergency event.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Proposal attempts to clarify that this requirement is applicable to textual visible notificationappliances.

Response Message:

Public Input No. 115-NFPA 72-2013 [Section No. 24.4.4.4.7.1]


222 of 326 11/21/2013 1:03 PM

24.6.10.1 24.4.4.4.7.1 After loss of primary power, primary textual visible notification

appliances shall have sufficient secondary power to operate for a minimum of 2 hours of

continuous display time during an emergency event.


24.4.4.4.8 In-Building Mass Notification Systems.

The in-building mass notification system shall meet the requirements of 24.4.3 .







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This paragraph is unnecessary and is covered by 24.4.3 This proposal is the work product of aChapter 24 Chairman-appointed Task Group on Renumbering. TG members: Bruce Fraser (chair),Andrew Woodward, Rodger Reiswig, and Sean Remke.

ResponseMessage:



223 of 326 11/21/2013 1:03 PM

24.4.4.4.8 In-Building Mass Notification Systems. The in-building mass notification system

shall meet the requirements of 24.4.3.


24.7* Distributed Recipient Mass Notification Systems (DRMNS).

24.7.1* Overview.

Distributed recipient mass notification system (DRMNS) alerting shall not be used in lieu of requiredaudible and visible alerting mass notification systems but shall be integrated with mass notificationsystems whenever possible.

24.7.2* Targeted Recipients.

The DRMNS shall be capable of sending alert messages to target recipients.

24.7.3* Network Security Compliance.

DRMNSs shall be installed behind the appropriate Internet system firewalls to protect the integrity of thenetwork.

24.7.4 Network Architecture.

The network shall be provided with net-centric architecture that fully supports local designatedstandards and security requirements.

24.7.5* Delivery Methods.

The DRMNS shall be capable of sending alert messages to end users (recipients) via multiple deliverymethods.

24.7.6* Backup Distributed Recipient Mass Notification Systems.

A DRMNS used to send emergency messages shall be provided with a backup configuration to facilitatedistribution of messages.







Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Editorial Maintain the Annex material and renumber for adherence to Manual of Style

Response Message:




224 of 326 11/21/2013 1:03 PM

24.7* 24.4.5* Distributed Recipient Mass Notification Systems (DRMNSs).

24.7.1* 24.4.5.1* Overview. Distributed recipient mass notification system (DRMNS) alerting

shall not be used in lieu of required audible and visible alerting mass notification systems but

shall be integrated with mass notification systems whenever possible.

24.7.2* 24.4.5.2* Targeted Recipients. The DRMNS shall be capable of sending alert messages

to target recipients.

24.4.5.2.1* DRMNS shall provide means of populating and updating distributed recipients' data.

24.7.3* 24.4.5.3* Network Security Compliance. DRMNSs shall be installed behind the

appropriate Internet system firewalls to protect the integrity of the network.

24.7.4 24.4.5.4 Network Architecture. The network shall be provided with net-centric

architecture that fully supports local designated standards and security requirements.

24.7.5* 24.4.5.5* Delivery Methods. The DRMNS shall be capable of sending alert messages to

end-users (recipients) via multiple delivery methods.

24.7.6* 24.4.5.6* Backup Distributed Recipient Mass Notification Systems. DRMNS used to

send emergency messages shall be provided with a backup configuration to facilitate distribution

of messages.


24.9.3.1 Inbound.

A minimum inbound signal strength sufficient to provide usable voice communications as specified by theAHJ shall be provided throughout the coverage area. The minimum acceptable inbound signal level shallbe specified in dBm with an associated acceptable bit error rate (BER) for digital radio systems.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

There are a number of radios systems in use by public safety agencies in the United States. Anumber of these have different operational characteristics. A prescribed signal strengthmeasurement (-95 dBm) as specified may not produce usable voice communications for all systems-VHF, UHF, 700/800 MHz, analog, P-25, 4 slot TDMA, 2 slot TDMA etc. Requiring the AHJ to providethe operational parameters that are required for usable voice communications for the systems in useeliminates any possible confusion regarding the specified value (-95 dBm) and the value specified bythe AHJ.

ResponseMessage:



225 of 326 11/21/2013 1:03 PM

24.9.3.1 24.5.2.3.1 Inbound. A minimum inbound signal strength of −95 dBm, or other signal

strength as required by the authority having jurisdiction sufficient to provide usable voice

communications as specified by the AHJ shall be provided throughout the coverage area. The

minimum acceptable inbound signal level shall be specified in dBm with an associated

acceptable bit error rate (BER) for digital radio systems.


24.9.3.2 Outbound.

A minimum outbound signal strength sufficient to provide usable voice communications as specified by theAHJ shall be provided at the donor site. The minimum acceptable outbound signal level shall be specifiedin dBm with an associated acceptable bit error rate (BER) for digital radio systems.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

There are a number of radios systems in use by public safety agencies in the United States. Anumber of these have different operational characteristics. A prescribed signal strengthmeasurement (-95 dBm) as specified may not produce usable voice communications for all systems-VHF, UHF, 700/800 MHz, analog, P-25, 4 slot TDMA, 2 slot TDMA etc. Requiring the AHJ to providethe operational parameters that are required for usable voice communications for the systems in useeliminates any possible confusion regarding the specified value (-95 dBm) and the value specified bythe AHJ.

ResponseMessage:



226 of 326 11/21/2013 1:03 PM

24.9.3.2 24.5.2.3.2 Outbound. A minimum outbound signal strength of −95 dBm at the donor

site, or other signal strength as required by the authority having jurisdiction, shall be provided

from the coverage area. sufficient to provide usable voice communications as specified by the

AHJ shall be provided at the donor site. The minimum acceptable outbound signal level shall be

specified in dBm with an associated acceptable bit error rate (BER) for digital radio systems.


24.9.6.2* Dedicated Monitoring Panel.

A dedicated monitoring panel shall be provided within the fire command center to annunciate the status ofall signal booster locations. The monitoring panel shall provide visual and labeled indication of thefollowing for each signal booster:

(1) Normal ac power

(2) Signal booster trouble

(3) Loss of normal ac power

(4) Failure of battery charger

(5) Low-battery capacity







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Provides a better description for the user This proposal is the work product of a Chapter 24Chairman-appointed Task Group on Renumbering. TG members: Bruce Fraser (chair), AndrewWoodward, Rodger Reiswig, and Sean Remke.

ResponseMessage:



227 of 326 11/21/2013 1:03 PM

24.9.6.2* 24.5.2.6.2* Dedicated Monitoring Panel. A dedicated monitoring panel shall be

provided within the fire command center to annunciate the status of all signal booster locations.

The monitoring panel shall provide visual and labeled indication of the following for each signal

booster:

(1) Normal ac power

(2) Signal booster trouble

(3) Loss of normal ac power

(4) Failure of battery charger

(5) Low-battery capacity


24.10* Area of Refuge (Area of Rescue Assistance) Emergency Communications Systems.

24.10.1*

Where required by the building code in force, an area of rescue assistance two-way emergencycommunications system shall be installed in accordance with 24.10 .

24.10.2

The area of refuge (rescue assistance) emergency communications system shall be comprised ofremotely located area of refuge stations and a central control point.

24.10.3

The remote area of refuge stations and the central control point shall communicate with each other viapathways based on their performance capabilities under abnormal (fault) conditions in accordance withthe requirements for Class A, Class B, Class N, or Class X pathways specified in Chapter 12 .

24.10.4

All pathways between a remote area of refuge stations and the central control point shall be monitoredfor integrity.

24.10.5*

If the central control point is not constantly attended, it shall have a timed automatic communicationscapability to connect with a constantly attended monitoring location acceptable to the authority havingjurisdiction where responsible personnel can initiate the appropriate response.

24.10.6

The physical location of the central control point shall be as designated by the building code in force orthe authority having jurisdiction.

24.10.7

The area of refuge station shall provide for hands-free, two-way communication, provide an audible andvisible signal to indicate communication has occurred, and indicate to the receiver the location sendingthe signal.

24.10.8

Instructions for the use of the two-way communications system, instructions for summoning assistancevia the two-way communications system, and written identification, including in braille, of the locationshall be posted adjacent to the two-way communications system.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

From a reliability standpoint, it is important for crucial emergency communications systems toidentify pathway faults so service can be initiated as soon as possible.


228 of 326 11/21/2013 1:03 PM

ResponseMessage:




229 of 326 11/21/2013 1:03 PM

24.10* 24.5.3* Area of Refuge (Area of Rescue Assistance) Emergency Communications

Systems.

24.10.1* 24.5.3.1* Where required by the building code in force, an area of rescue assistance

two-way emergency communications system shall be installed in accordance with 24.5.3.

24.10.2 24.5.3.2 The area of refuge (rescue assistance) emergency communications system

shall be comprised of remotely located area of refuge stations and a central control point.

24.10.3 24.5.3.3 The remote area of refuge stations and the central control point shall

communicate with each other via pathways based on their performance capabilities under abnormal (fault) conditions in accordance with the requirements for Class A, Class B, Class N, or Class X pathways specified in Chapter 12.

24.10.4 All pathways between remote area of refuge stations and the central control point shall be monitored for integrity.

24.10.5* 24.5.3.4* If the central control point is not constantly attended, it shall have a timed

automatic communications capability to connect with a constantly attended monitoring location

acceptable to the authority having jurisdiction where responsible personnel can initiate the

appropriate response.

24.10.6 24.5.3.5 The physical location of the central control point shall be as designated by the

building code in force or the authority having jurisdiction.

24.10.7 24.5.3.6 The area of refuge station shall provide for hands-free, two-way

communication, provide an audible and visible signal to indicate communication has occurred

and indicate to the receiver the location sending the signal.

24.10.8 24.5.3.7 Instructions for the use of the two-way communications system, instructions

for summoning assistance via the two-way communications system, and written identification,

including included in braille, of the location shall be posted adjacent to the two-way

communications system.


24.11 Elevator Emergency Communications Systems.

24.11.1

Elevator two-way emergency communications systems shall be installed in accordance with therequirements of ANSI/ASME A17.1/CSA B44, Safety Code for Elevators and Escalators .

24.11.2

Communication shall be provided for the lobbies where the elevators are used for occupant-controlledevacuation.

24.11.3

Inspection and testing of elevator emergency communications systems shall be performed inaccordance with ANSI/ASME A17.2, Guide for Inspection of Elevators, Escalators and Moving Walks .







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

To address T&I requirements. This might also have to go to SIG-TMS This proposal is the workproduct of a Chapter 24 Task Group on elevator emergency communications systems. TGmembers: Bruce Fraser (chair), Wayne Moore

ResponseMessage:



230 of 326 11/21/2013 1:03 PM

24.11 24.5.4 Elevator Emergency Communications Systems.

24.11.1 24.5.4.1 Elevator two-way emergency communications systems shall be installed in

accordance with the requirements of ANSI/ASME A17.1/CSA B44, Safety Code for Elevators

and Escalators.

24.11.2 24.5.4.2 Communication shall be provided for the lobbies where the elevators are used

for occupant-controlled evacuation.

24.11.3 Inspection and testing of elevator emergency communications systems shall be performed in accordance with ASME/A17.2, Guide for Inspection of Elevators, Escalators and Moving Walks.


New Section after 24.5.4

24.5.5* Stairway Communications Systems

24.5.5.1 Where required by the building code in force, and not included as part of anotheremergency communications system, a stairway communications system shall be installed inaccordance with 24.5.5.

24.5.5.2 It shall be permissible for the stairway communications system to be integrated withanother two-way emergency communications system providing it is installed in accordance with24.5.5.

24.5.5.3 The stairway communications system shall be comprised of remotely locatedcommunications points and a central control point.

24.5.5.4 Each remote point shall have the capability to communicate with the central controlpoint.

24.5.5.5* Quantity and locations of the remote communications points shall be as required by thebuilding code in force and engineer specifications.

24.5.5.6* If the central control point is not constantly attended, it shall have a timed automaticcommunications capability to connect with a constantly attended monitoring location acceptableto the authority having jurisdiction where responsible personnel can initiate the appropriateresponse.

24.5.5.7 The physical location of the central control point shall be as designated by the buildingcode in force or the authority having jurisdiction.

24.5.5.8 The remote communications points shall provide for two-way communications, providean audible and visible signal to indicate communication has occurred and indicate to the receiverthe location sending the signal.

24.5.5.9 Instructions for the use of the stairway communications system, instructions forsummoning assistance via the system, and written identification, included in braille, of the locationshall be posted adjacent to each remote communications point.



Attachment_to_FR_354.EC_edits.docx




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC provides new requirements for stairway communications systems.

Response Message:


24 of 326 11/21/2013 1:03 PM

A.24.5.5

Stairway communications systems are typically provided between a constantly attended central

location, such as the fire command center, and remote points located at not less than every fifth

floor in stairways where the doors to the stairway are locked. It is important that a method to

communicate exists between that remote location and a central control point so that appropriate

action for assistance can be initiated.

A.24.5.5.5

Generally, the building code or engineer specification will provide the specifics on the required

locations of the stairway communications points, as well as the central control point.

Requirements found in 24.5.5 should be coordinated with the requirements of the building code

in force.

A.24.5.5.6

To ensure a timely response to a call for assistance, the call is to be forwarded to a constantly

attended approved location, such as a supervising station, 911 communications center, or other

monitoring location.


24.13.1.4* Staffing.

Emergency command center personnel requirements shall be defined in the documentation in theemergency response plan.

24.12.1.4.1

Emergency command center personnel requirements shall be defined in the documentation in theemergency response plan.

24.12.1.4.2*

Individuals expected to operate an emergency communications system shall be properly trained in thepurpose, functions, procedures, and anticipated actions of such systems.

24.13.1.5*

Individuals expected to operate an emergency communications system shall be properly trained in thepurpose, functions, procedures, and anticipated actions of such systems.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Delete heading, renumber (promote) sub-paragraphs, and move Annex material to new 24.6.1.4.Remove unnecessary header. This proposal is the work product of a Chapter 24 Chairman-appointed Task Group on Renumbering. TG members: Bruce Fraser (chair), Andrew Woodward,Rodger Reiswig, and Sean Remke.

ResponseMessage:



231 of 326 11/21/2013 1:03 PM

24.6.1.4* Staffing.

24.13.1.4* 24.6.1.4.1 Emergency command center personnel requirements shall be defined in

the documentation in the emergency response plan.

24.13.1.5* 24.6.1.4.2* Individuals expected to operate an emergency communications system

shall be properly trained in the purpose, functions, procedures, and anticipated actions of such

systems.

24.13.1.6 24.6.1.5 The emergency command center shall be capable of receiving voice

messages by telephone or radio and transmitting via equipment at the emergency command

center.

24.13.1.7 24.6.1.6 The emergency command center operator shall have the ability to monitor

inputs/sensors and control output devices automatically, manually, or automatically with

operator override.


24.13.2.2

The system operator shall be able to send broadcast live voice signals or activate prerecorded voicemessages, tones, and other signals.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The word broadcast better describes the activity. This proposal is the work product of a Chapter24 Chairman-appointed Task Group on Renumbering. TG members: Bruce Fraser (chair), AndrewWoodward, Rodger Reiswig, and Sean Remke.

ResponseMessage:



232 of 326 11/21/2013 1:03 PM


24.13.2.5 Multiple Emergency Communications Control Units.

In wide-area mass notification systems, the emergency command center shall have a primaryemergency communications control unit.

24.13.2.5.1

In wide-area mass notification systems, the emergency command center shall have a primaryemergency communications control unit.

24.13.2.5.2

Multiple emergency communications control units shall be permitted.

24.13.2.6

Multiple emergency communications control units shall be permitted.



FR_359.docx FR 359 in legislative text




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The TC changes the title as the paragraph applies to more than just control equipment. TheTC renumbers the requirements.

ResponseMessage:



233 of 326 11/21/2013 1:03 PM

24.6.2.5 Multiple Emergency Communications Control Units.

24.13.2.5 24.6.2.5.1 In wide-area mass notification systems, the emergency command center

shall have a primary emergency communications control unit.

24.13.2.6 24.6.2.5.2 Multiple emergency communications control units shall be permitted.

24.13.3* 24.6.3* Signals. Where identified by the risk analysis and defined in the emergency

response plan, the emergency communications control unit shall be permitted to automatically or

manually send different messages or signals to different locations.


24.13.4 Power Supply.

All control units shall meet the power supply requirements of Section 10.6 and 24.13.5 .

24.13.4.1

All control units shall meet the requirements of Section 10.6 .

24.13.4.2

The power supply for the emergency command center shall include an uninterrupted power source withcapacity sufficient to support the emergency response plan established for the specific premises.

24.13.5

The power supply for the emergency command center for emergency communications systems shallinclude an uninterrupted power source with capacity sufficient to support the emergency response planestablished for the specific premises.



FR_333.docx FR 333 legilslative text




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This modification eliminates an unnecessary section header and adds supportive wording. Thisproposal is the work product of a Chapter 24 Chairman-appointed Task Group on Renumbering.TG members: Bruce Fraser (chair), Andrew Woodward, Rodger Reiswig, and Sean Remke.

ResponseMessage:



234 of 326 11/21/2013 1:03 PM

First Revision No. 334-NFPA 72-2013 [ Section No. 24.7 [Excluding any Sub-Sections] ]

The requirements of Section 24.14 24.7 shall apply to mass notification systems designedto using recognize performance-based practices.







Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: More clearly describes the intent.

Response Message:

Public Input No. 643-NFPA 72-2013 [Section No. 24.7 [Excluding any Sub-Sections]]


235 of 326 11/21/2013 1:03 PM

24.14* 24.7* Performance-Based Design of Mass Notification Systems. The requirements of

Section 24.7 shall apply to mass notification systems designed using to recognize performance-

based practices.


24.14.1 Goals and Objectives.

The performance-based design shall meet the following goals and objectives:

(1) The risk analysis, design criteria, design brief, system performance, and testing criteria aredeveloped in accordance with this section.

(2) The system disseminates information to the target audience in an accurate and timely manner.

(3) The design and performance criteria are specific to the nature and anticipated risks of each location.

The system is capable of withstanding various scenarios and survives even if some damage hasalready occurred.

(4) Message initiation can be effected by all responding entities responsible for the safety and security ofoccupants those affected by the events of concern .




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC deletes item (4) as the goal is too vague and immeasurable.

Response Message:



236 of 326 11/21/2013 1:03 PM

First Revision No. 336-NFPA 72-2013 [ Section No. 24.8 ]

24.15 Documentation for Emergency Communications Systems .

24.15.1 New Systems.

Documentation requirements for new emergency communications systems shall comply with Sections 7.3through 7.8 in addition to the minimum requirements of Section 7.2.

24.15.2* Existing Systems

The documentation that shall be provided for all additions or alterations to existing emergencycommunications systems shall be at the direction of the authority having jurisdiction.

24.15.3 Owner’s Manual.

For new emergency communications systems, an owner’s manual shall be provided and shall containthe following documentation:

(1) Detailed narrative description of the system inputs, evacuation signaling, ancillary functions,annunciation, intended sequence of operations, expansion capability, application considerations,and limitations

(2) Written sequence of operation for the system including an operational input/output matrix

(3) Operator instructions for basic system operations, including alarm acknowledgment, system reset,interpretation of system output (LEDs, CRT display, and printout), operation of manual evacuationsignaling and ancillary function controls, and change of printer paper

(4) Detailed description of routine maintenance and testing as required and recommended and aswould be provided under a maintenance contract, including testing and maintenance instructionsfor each type of device installed, which includes the following:

(a) Listing of the individual system components that require periodic testing and maintenance

(b) Step-by-step instructions detailing the requisite testing and maintenance procedures, andthe intervals at which these procedures shall be performed, for each type of device installed

(c) Schedule that correlates the testing and maintenance procedures that are required by thissection

(5) Service directory, including a list of names and telephone numbers of those who provide servicefor the system




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Expanded header provides additional information for users of this document. This proposal is thework product of a Chapter 24 Chairman-appointed Task Group on Documentation. TG members:Bruce Fraser (chair), Andrew Woodward, and Rodger Reiswig.

ResponseMessage:


237 of 326 11/21/2013 1:03 PM

Public Input No. 445-NFPA 72-2013 [Section No. 24.8]




238 of 326 11/21/2013 1:03 PM


24.8.3 Owner’s Manual. For new emergency communications

systems, an owner’s manual shall be provided and shall contain

the following documentation:

(1) Detailed narrative description of the system inputs, evacuation

signaling, ancillary functions, annunciation, intended

sequence of operations, expansion capability, application

considerations, and limitations

(2) Written sequence of operation for the system including

an operational input/output matrix

(3) Operator instructions for basic system operations, including

alarm acknowledgment, system reset, interpretation

of system output (LEDs, CRT display, and printout), operation

of manual evacuation signaling and ancillary

function controls, and change of printer paper

(4) Detailed description of routine maintenance and testing

as required and recommended and as would be provided

under a maintenance contract, including testing and

maintenance instructions for each type of device installed,

which includes the following:

(a) Listing of the individual system components that require

periodic testing and maintenance

(b) Step-by-step instructions detailing the requisite testing

and maintenance procedures, and the intervals at

which these procedures shall be performed, for each

type of device installed

(c) Schedule that correlates the testing and maintenance

procedures that are required by this section

(5) Service directory, including a list of names and telephone

numbers of those who provide service for the system

Delete 24.8.3




Street Address:

City:

State:

Zip:



21 of 326 11/21/2013 1:03 PM

Committee Statement

CommitteeStatement:

Items (7) and (8) would not be included in an owner’s manual as they are designdocuments.

Response Message:



22 of 326 11/21/2013 1:03 PM

First Revision No. 343-NFPA 72-2013 [ New Section after A.24.3.1 ]

A.24.3.1

When a rapid-onset emergency occurs, it is not always sufficient simply to initiate alarm notificationappliances. Individuals might not know what the alarm signal means (or even hear it) and as a resultmight not respond appropriately to the warning signal. Mass notification and emergency communicationsystems have been designed and installed to be used to disseminate audible and visual messages inthe event of an emergency. Such systems are based upon guidance and requirements provided ininternational codes and standards.

There is limited guidance on how to use emergency communication systems and mass notificationsystems in the most effective manner. For example, buildings often use these systems to disseminateprerecorded, general emergency voice alarm messages that leave occupants wanting and needingfurther information before they can respond effectively. As the use of newer technologies, includingmobile devices with multiple message delivery platforms (e.g., SMS text, Internet, email, socialnetworking) increases, guidance on message content and dissemination becomes even more critical toensure effective and safe response of building occupants during an emergency.

However, for any specific application, there are characteristics that any emergency message shouldhave to be effective. Messages being appropriate means that the messages should get the attention ofthe recipients in a timely manner, the messages are credible to the recipients, and comprehensible bythe intended recipients. Being comprehensible means that the language, method of delivery, andcontent of the message are such that the intended message recipients should be able to understand themessage in enough time to be able to decide to take the appropriate response to the message.

Messages that are focused on protective actions means that the message should tell the intendedaudience what they should do to protect themselves and others.

The following referenced document describes the process in which people receive and processinformation in order to take action during rapid-onset emergencies. The document presents guidance onhow to create and disseminate emergency information in the face of rapid-onset disasters — providingguidance on dissemination of alert signals, creation of the warning message, formatting of messages forboth visual and audible means, and dissemination of the warning message. Although this document isfocused on emergency notification within buildings, many of the general principles apply to outdoor andwide-area notification as well.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This annex material will support the proposed code section 24.3.2, by explaining whymessage content is important to review and think through

ResponseMessage:

Public Input No. 384-NFPA 72-2013 [New Section after A.24.3.1]


311 of 326 11/21/2013 1:03 PM

First Revision No. 344-NFPA 72-2013 [ New Section after A.24.4.3.18 ]

A.24.5.19.2

The requirement of 24.5.19.2 does not imply that multiple primary methods of visible appliancescannot exist in a common area. Both strobes and graphical or textual appliances are designated asprimary where the authority having jurisdiction declares both to be required. When textual audiblenotification is required, consideration is warranted for high-noise areas and for a hearing-impairedperson’s capability of clearly receiving instructions.

As mass notification systems are deployed, the more complex emergency management communicationrequirements that go beyond what can be indicated by a strobe and a tone are being addressed. Theintelligibility requirements of a MNS/ECS are a direct reflection of this reality. However, for a hearing-impaired person, no degree of intelligibility might be sufficient. Additionally, there are physical spaceswhere intelligibility is impossible or impractical to provide. In designating a primary visual notificationappliance, it is easy to assume that a strobe is sufficient and all other visual notification is automaticallysupplemental.

However, where the risk analysis and an emergency response plan require the communication of MNStextual audible instructions for occupants, a strobe should not be considered a sufficient primarynotification appliance where intelligibly cannot be achieved or where consideration for lone individuals orgroups of individuals with hearing impairments might prevent them from responding appropriately toemergency instructions.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC adds the substantiation from the submitter as part of the annex material.

Response Message:

Public Input No. 492-NFPA 72-2013 [New Section after A.24.4.3.18]


312 of 326 11/21/2013 1:03 PM

First Revision No. 356-NFPA 72-2013 [ New Section after G.1.2.12.1 ]

G.1.2.12.2 References to A.24.3.1.

Kuligowski, Erica D., "NIST Technical Note 1779: “General Guidance on Emergency CommunicationStrategies for Buildings,” Feb. 2013.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC adds reference source for annex text to A.24.1.

Response Message:


326 of 326 11/21/2013 1:03 PM

First Revision No. 339-NFPA 72-2013 [ Section No. 2.2 ] Revision No. 339-NFPA 72-2013 [ Section No....

Documents

Transcript of First Revision No. 339-NFPA 72-2013 [ Section No. 2.2 ] Revision No. 339-NFPA 72-2013 [ Section No....