agenda technical committee on emergency communication systems (sig-ecs) first draft ... ·...

Agenda Technical Committee on

Emergency Communication Systems (SIG-ECS) First Draft Meeting Salt Lake City, UT July 28 - 29, 2016

Item 16-7-1. Call to Order

Item 16-7-2. Roll Call and Introductions

Item 16-7-3. Approval of Meeting Agenda

Item 16-7-4. Approval of Meeting Minutes

Item 16-7-5. Staff/Chair Remarks

Item 16-7-6. Task Group Reports

Item 16-7-7. Public Inputs, Committee Inputs and First Revisions

Item 16-7-8. Old Business

Item 16-7-9. New Business

Item 16-7-10. Review Dates and Times for Future Meetings/Conference Calls

Item 16-7-11. Adjournment and Closing Remarks

National Fire Protection Association 1 Batterymarch Park, Quincy, MA 02169-7471 Phone: 617-770-3000 • Fax: 617-770-7070 • www.nfpa.org

Technical Committee on Emergency Communication Systems 2016 Second Draft Meeting Minutes

San Diego, CA June 24 & 25, 2014

Wayne Moore-Chair

A. 6.24.14 TC meeting called to order by Chair Wayne Moore at 8:06 AM B. Introductions of all present, plus 6 guests C. Sign in sheets gathered by NFPA staff, see attached roster of attendees D. Agenda was reviewed and Approved, E. Meeting Minutes for First Draft were Approved F. Discussion/presentation on Process for Second Draft Actions G. Reviewed Task Group activities, noted below. H. Worked on various PC’s (Total of 35 PC’s to work) I. Lunch break at 11:50 AM to 1:00 PM J. Resumed meeting at 1:00 PM to review proposed Annex K. 1:30 PM worked on various PC’s L. 6:20 PM Closed the session for the day M. 6.25.14 Session called to order at 8:00 AM N. Al Ramirez of UL presented an update on CI Cables listings O. Next steps Ballots and CC reviews actions P. New Business: None Q. A total of 39 PC and CI were processed in this session R. Closed session 11:40 AM.

a. The meeting closed on a sobering note, this will be Wayne Moore’s last session as Chair, and Wayne took Chapter 24 from an idea to a very valuable part of NFPA 72. His leadership is respected and the committee looks forward to his continued participation within the committee.

The following task groups are for record only. Most of the tasks are closed and noted. They will be removed with when the next cycle starts.

Task Group Scope

Chair Members

Documentation Review Ch 24 documentation

requirements and recommend reduction in duplicative material and relocate

some material to appropriate locations for improved flow.

Report: Completed, 11 PI’s submitted, with renumbering of sections

CLOSED

Bruce Fraser Andrew Woodward, Rodger Reiswig, Sean Remke

Numbering of Sections Review Ch 24 numbering and

recommend ways to reduce length of section paragraph numbering and to promote major headings for improved

usability. Report: See above for comments,

CLOSED

Bruce Fraser Andrew Woodward, Rodger Reiswig, Sean Remke

Risk Analysis Where do we make this mandatory?

Is required for MNS System. Impacts on Combination Systems

where MNS is involved.

Report: John reported on actions taken, submitted various PI’s. Tried to simplify

the process, lots of discussion—will review the PI’s in detail

CLOSED

John Fuoto Sean Remke, Oded Aron, Joe Collins, Joe Ripp, Aviv

Siegel, Bruce Fraser

LOC Mounting Heights and define use by Occupant vs. Authorized user

Develop language and PI

Report: Submitted PI’s CLOSED

Scott Lacey Ray Hansen, Waymon Jackson

Req for Monitoring FA and MNS Stand Alone Systems

Develop Language and PI Report: Submitted PI’s

CLOSED

Scott Lacey Derek Matthews, Ray Hansen

Test Schedule for Elevator Define and prepare PI

Report: Submitted PI’s

CLOSED

Bruce Fraser Wayne Moore

Test Schedule Area of Refuge Communication Systems

Clean up 14.4.3.2; LSC 101 7.2.12 Develop PI

Report: TG has draft of changes, need to submit CI to ECS and Chp 14 TMS

CLOSED

Rodger Reiswig Derek Mathews, Dan Finnegan, Waymon Jackson

FPRF Research on Messaging What should we put into our code for

guidance and direction Develop PI

Report: Submitted PI’s

Worked SR’s and submitted in this session

Dan Finnegan John Fuoto, Wayne Moore

Technology for Providing

Intelligibility May need to allow non-Fire listed

products for certain applications……

Report: TG submitted PI’s

John Fuoto

Mike Pallett , Denise Pappas, Andrew Woodward, Wayne

Moore, Derek Mathews, Dan Finnegan, Joe Collins

Audio Circuit db Loss Evaluate data from chapter 23, place in

Annex Develop PI

Report: Need some outside SME on

this topic, need placeholder into document CLOSED

Charlie Hall Waymon Jackson, Joe Dafin, Jim Chambers

24.4.2.8 Review Evacuation Signals

Correlate with Chp 18, change title to just evac. Revise and create PI

Report: Formed a TG to review and develop revisions to submitted PI

CLOSED

Dan Finnegan Mike Pallett, Jim Mongeau

Prescriptive vs Performance Base for Risk Analysis

Develop PI

Report: PI’s submitted CLOSED

Sean Remke Ray Hansen, Waymon Jackson, Bruce Fraser

Area of Refuge Compare actual requirements with other

two way requirements


Mike Pallett Derek Mathews Needs to work with Rodgers

task group

LCD screens that would be primary visual notification appliances

Review and develop PI


Mike Pallett

Derek Mathews

Review of First Draft Document NEW (9.09.13)

Review FD accuracy as printed, including Correlation

CLOSED

Bruce Fraser

Bruce Fraser-Chair John Fannin Joe Collins

Review Communication Systems for Elevator and Stairs NEW (9.11.13)

Overlap of Systems-Recommendations

Bruce Fraser

Joe Ripp, Andrew Woodward Jim Mongeau, Mike Pallett,

ECS-PRO ColorationCollaboration

Define Zone/Notification To be worked next cycle

Mike Pallett-rep ECS

tbd

Submitted Daniel P Finnegan

Secretary ECS TC

Public Input No. 485-NFPA 72-2016 [ Global Input ]

Change "emergency response plan" to "emergency action plan".

Statement of Problem and Substantiation for Public Input

This proposed public input is to correlate with NFPA 101 terminology to reduce misinterpretations and confusion.

Submitter Information Verification

Submitter Full Name: Thomas Hammerberg

Organization: Automatic Fire Alarm Association

Affilliation: Automatic Fire Alarm Association

Street Address:

City:

State:

Zip:

Submittal Date: Mon Jun 27 09:28:00 EDT 2016

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

5 of 1374 6/30/2016 11:10 AM


Rewrite the "Exception" text throughout NFPA 72 and replace with standard subsection text.


NFPA 72 contains numerous sections that are written with "Exception" text. This is inconsistent the direction provided in the Manual of Style and should be corrected. Differing types of style that are inconsistent with the MOS create confusion as the proper application of the code by the end user.

As an example, 10.4.4 is currently written with an "exception" as follows:

"10.4.4* In areas that are not continuously occupied, automatic smoke detection shall be provided at the location of each fire alarm control unit(s), notification appliance circuit power extenders, and supervising station transmitting equipment to provide notification of fire at that location.Exception: Where ambient conditions prohibit installation of automatic smoke detection, automatic heat detection shall be permitted."

This section could easily be rewritten to be consistent with the MOS in the following manner with the exception becoming core text in a subsection modifying 10.4.4:

10.4.4* In areas that are not continuously occupied, automatic smoke detection shall be provided at the location of each fire alarm control unit(s), notification appliance circuit power extenders, and supervising station transmitting equipment to provide notification of fire at that location.10.4.4.1 Where ambient conditions prohibit installation of automatic smoke detection, automatic heat detection shall be permitted.

The above is just one example but applies throughout to all "exception" text in NFPA 72.


Submitter Full Name: Anthony Apfelbeck

Organization: Altamonte Springs Building/Fire Safety Division

Street Address:

City:

State:

Zip:

Submittal Date: Thu May 19 08:52:10 EDT 2016


1 of 1374 6/30/2016 11:10 AM


Replace the terms Fire Alarm Control Panel and FACP through the document (including alldiagrams) with the terms Fire Alarm Control Unit and FACU respectively.


The terms Fire Alarm Control Panel and FACP are not defined in the code. The terms Fire Alarm Control Unit and FACU are defined in section 3.3.100*


Submitter Full Name: Daniel Gauvin

Organization: Tyco Fire Suppression and Building Products

Street Address:

City:

State:

Zip:



2 of 1374 6/30/2016 11:10 AM


The NFPA 72 Correlating Committee Task Group on Metric Values would like to submitthe following Global Input , Any place in the body of Chapter 24 or its annex that thevalue 40 inches Is used the metric equivalent shall be 1.02 m


This Task Group was established to provide conversion values from inch-pound units to Metric units in a consistent manner throughout the document. This will establish a baseline value for the use of each unit of measurement to provide consistency.


Submitter FullName:

Thomas Parrish

Organization: Telgian Corporation

Affilliation:NFPA SIG-AAC Metric Task Group, Tom Parrish, A. M. Fred Leber,and Jeffery G. Van Keuren

Street Address:

City:

State:

Zip:

Submittal Date: Wed Jun 29 14:17:42 EDT 2016


29 of 1374 6/30/2016 11:10 AM






Submitter FullName:

Thomas Parrish



Street Address:

City:

State:

Zip:



31 of 1374 6/30/2016 11:10 AM






Submitter FullName:

Thomas Parrish



Street Address:

City:

State:

Zip:



35 of 1374 6/30/2016 11:10 AM


The NFPA 72 Correlating Committee Task Group on Metric Values would like to submit the following GlobalInput , Any place in the body of Chapter 24 or its annex that the value 10 inches Is used the metricequivalent shall be 254 mm.




Submitter FullName:

Thomas Parrish



Street Address:

City:

State:

Zip:

Submittal Date: Tue Jun 28 14:42:50 EDT 2016


8 of 1374 6/30/2016 11:10 AM


The NFPA 72 Correlating Committee Task Group on Metric Values would like to submitthe following Global Input , Any place in the body of Chapter 24 or its annex that thevalue 24 inches Is used the metric equivalent shall be 610 mm




Submitter FullName:

Thomas Parrish



Street Address:

City:

State:

Zip:



19 of 1374 6/30/2016 11:10 AM


The NFPA 72 Correlating Committee Task Group on Metric Values would like to submit thefollowing Global Input , Any place in the body of Chapter 24 or its annex that the value 28inches Is used the metric equivalent shall be 711 mm.




Submitter FullName:

Thomas Parrish



Street Address:

City:

State:

Zip:



20 of 1374 6/30/2016 11:10 AM


The NFPA 72 Correlating Committee Task Group on Metric Values would like to submitthe following Global Input , Any place in the body of Chapter 17 or its annex that thevalue 36 inches or 3 feet Is used the metric equivalent shall be 910 mm




Submitter FullName:

Thomas Parrish



Street Address:

City:

State:

Zip:



27 of 1374 6/30/2016 11:10 AM

Public Input No. 2-NFPA 72-2015 [ Chapter 2 ]

Chapter 2 Referenced Publications

2.1 General.

The documents or portions thereof listed in this chapter are referenced within this Code and shall beconsidered part of the requirements of this document.

2.2 NFPA Publications.

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

NFPA 10, Standard for Portable Fire Extinguishers, 2013 edition.

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

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

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

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

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

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

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

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

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

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

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

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

NFPA 1031, Standard for Professional Qualifications for Fire Inspector and Plan Examiner, 2014 edition.

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

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

NFPA 1620, Standard for Pre-Incident Planning, 2015 edition.

2.3 Other Publications.


47 of 1374 6/30/2016 11:10 AM

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.(Superseded by ASCE 7)

ANSI S1.4a, Specifications for Sound Level Meters, 1985, reaffirmed 2006. (Superseded by ANSI/ASAS1.4 Part 3)

ANSI /ASA S1.4 Part 3/IEC 61672-3, Electroacoustics-Sound Level Meters - Periodic Tests, 2014.

ANSI /ASA S3.41, American National Standard Audible Emergency Evacuation Signal, 1990, reaffirmed2008.ANSI/ 2015 .

2.3.2 ASCE Publications.

American Society Of Civil Engineers, 1801 Alexander Bell Drive, Reston, VA 20191.

ASCE 7-10, Minimum Design Loads for Buildings and Other Structures, 2010, Supplement 1 andrevised commentary, 2013.

2.3.3 ASME Publications.

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

ANSI/IEEE

2.3.4. EIA Publications.

Electronic Industries Alliance, 2500 Wilson Boulevard, Arlington, VA 22201-3834.

EIA Tr 41.3, Telephones .

2.3.5. IEEE Publications.

IEEE, 449 and 501 Hoes Lane, Piscataway, NJ 08854-4141.

IEEE C2, National Electrical Safety Code ,

2007.ANSI/TIA

2016.

2.3.6. IMSA Publication.

International Municipal Signal Association, 597 Haverty Court, Suite 100, Rockledge, FL 32955 .

“IMSA Official Wire and Cable Specifications,” 2012.

2.3.7 ISO Publications.

International Organization for Standardization, ISO Central Secretariat, Chemen de Blandonnet 8, CP401, 1214 Vernier, Geneva Switzerland .

ISO 7731, Danger signals for public and work places — Auditory danger signals , 2003.

2.3.8 Telcordia Publications.

Telcordia Technologies, One Telcordia Drive, Piscataway, NJ 08854.

GR-506-CORE, LATA Switching Systems Generic Requirements: Signaling for Analog Interface, 2006.

GR-909-CORE, Fiber in the Loop Systems Generic Requirements, 2004.


48 of 1374 6/30/2016 11:10 AM

2.3.9. TIA Publications.

Telecommunications Industry Association, 1320 North Courthouse Road, Suite 200, Arlington, VA 22201.

TIA -568-C.3, Optical Fiber Cabling Components Standard , June 2008 , Addendum 1, 2011 .

ANSI/

2.3.10. UL Publications.

Underwriters Laboratory, 333 Pfingsten Road, Northbrook, IL 60062-2096.

UL 217, Standard for Single and Multiple Station Smoke Alarms ,

6th

8 th edition,

2006, revised 2012

2015 .

ANSI/

UL 268, Standard for Smoke Detectors for Fire Alarm Systems , 6th edition, 2009.

ANSI/

UL 827, Standard for Central-Station Alarm Services ,

7th

8 th edition,

2008

2014 , revised

2013

2015 .

ANSI/

UL 864, Standard for Control Units and Accessories for Fire Alarm Systems ,

9th

10 th edition,

2003, revised 2012

2014 .

ANSI/

UL 985, Standard for Household Fire Warning System Units ,

5th

6 th edition,

2000, revised 2008

2015 .

ANSI/

UL 1638, Visual Signaling Appliances — Private Mode Emergency and General Utility Signaling , 4thedition, 2001, revised 2013.

ANSI/

UL 1730, Standard for Smoke Detector Monitors and Accessories for Individual Living Units of MultifamilyResidences and Hotel/Motel Rooms , 4th edition, 2006, revised 2012.

ANSI/

UL 1971, Standard for Signaling Devices for the Hearing Impaired , 3rd edition, 2002, revised 2013.


49 of 1374 6/30/2016 11:10 AM

ANSI/

UL 1981, Central Station Automation Systems ,

2nd

3rd edition,

2003

2014 , revised

2012

2015 .

ANSI/

UL 2017, Standard for General-Purpose Signaling Devices and Systems , 2nd edition, 2008, revised 2011.

ANSI/

UL 2572, Mass Notification Systems , 1st edition, 2011, revised 2012.

ANSI/

UL 60950, Information Technology Equipment — Safety — Part 1: General Requirements , 2nd edition,2007, revised

2011

2014 .

2.3. 2 EIA Publications.

Electronic Industries Alliance, 2500 Wilson Boulevard, Arlington, VA 22201-3834.

EIA Tr 41.3, Telephones .

2.3.3 IMSA Publication.

International Municipal Signal Association, 165 East Union Street, Newark, NY 14513-0539.

“IMSA Official Wire and Cable Specifications,” 2012.

2.3.4 ISO Publications.

International Organization for Standardization, 1, ch. de la Voie-Creuse, Case postale 56, CH-1211Geneva 20, Switzerland.

ISO 7731, Danger signals for public and work places — Auditory danger signals , 2003 (reconfirmed2009).

2.3.5 Telcordia Publications.

Telcordia Technologies, One Telcordia Drive, Piscataway, NJ 08854.

GR-506-CORE, LATA Switching Systems Generic Requirements: Signaling for Analog Interface, 2006.

GR-909-CORE, Fiber in the Loop Systems Generic Requirements, 2004.

2.3.6 11. Other Publications.

Merriam-Webster’s Collegiate Dictionary, 11th edition, Merriam-Webster, Inc., Springfield, MA, 2003.


50 of 1374 6/30/2016 11:10 AM

2.4 References for Extracts in Mandatory Sections.

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

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

NFPA 654, Standard for the Prevention of Fire and Dust Explosions from the Manufacturing, Processing,and Handling of Combustible Particulate Solids, 2013 edition.

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

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

NFPA 5000® , Building Construction and Safety Code®, 2015 edition.


Referenced current SDO names, addresses, standard names, numbers, and editions.

Related Public Inputs for This Document

Related Input Relationship

Public Input No. 3-NFPA 72-2015 [Chapter H]


Submitter Full Name: Aaron Adamczyk

Organization: [ Not Specified ]

Street Address:

City:

State:

Zip:

Submittal Date: Mon Dec 21 17:16:12 EST 2015


51 of 1374 6/30/2016 11:10 AM

Public Input No. 664-NFPA 72-2016 [ New Section after 2.3 ]

2.3.6 UL Publications.

Underwriters Laboratories Inc., 333 Pfingsten Road, Northbrook, IL 60062-2096. www.ul.com

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

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

ANSI/UL 827, Standard for Central-Station Alarm Services , 7th edition, 2008, revised 2013.

ANSI/UL 864, Standard for Control Units and Accessories for Fire Alarm Systems , 9th edition, 2003,revised 2012.

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

ANSI/UL 1638, Visual Signaling Appliances — Private Mode Emergency and General Utility Signaling , 4thedition, 2001, revised 2013.

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

ANSI/UL 1971, Standard for Signaling Devices for the Hearing Impaired , 3rd edition, 2002, revised 2013.

ANSI/UL 1981, Central Station Automation Systems , 2nd edition, 2003, revised 2012.

ANSI/UL 2017, Standard for General-Purpose Signaling Devices and Systems , 2nd edition, 2008, revised2011.

ANSI/UL 2572, Mass Notification Systems , 1st edition, 2011, revised 2012 .

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


This proposal merely moves UL standards from Section 2.3.1 ANSI Publications to a new Section 2.3.6 titled UL Publications. Other NFPA codes such as NFPA 101, 13, etc. treat UL referenced standards in this same manner. The move will make it easier for code users to locate UL referenced standards. Assume existing Section 2.3.6 will be renumbered 2.3.7.

In separate public inputs we proposed updates to UL referenced standards, and introduced new referenced standards. If those changes are accepted they should be relocated to this section.

Also assume staff can delete these ANSI/UL standards are deleted from Section 2.3.1.


Submitter Full Name: Howard Hopper

Organization: UL LLC

Street Address:

City:

State:

Zip:



54 of 1374 6/30/2016 11:10 AM

Public Input No. 552-NFPA 72-2016 [ Section No. 2.3.1 ]

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–13, Safety Code for Elevators and Escalators, 2013.

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

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






ANSI/UL 1638, Visual Signaling Appliances — Private Mode Emergency and General Utility Signaling , 4thedition, 2001, revised 2013.


ANSI/UL 1971, Standard for Signaling Devices for the Hearing Impaired , 3rd edition, 2002, revised 2013.

ANSI/UL 1981, Central Station Automation Systems , 2nd edition, 2003, revised 2012.

ANSI/UL 2017, Standard for General-Purpose Signaling Devices and Systems , 2nd edition, 2008, revised2011.

ANSI/UL 2572, Mass Notification Systems , 1st edition, 2011, revised 2012.

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


The deleted UL Standards should be removed from this section and placed under a separate section in Referenced Publications for UL Standards.


Submitter Full Name: Ronald Farr


Street Address:

City:

State:

Zip:



60 of 1374 6/30/2016 11:10 AM


TITLE OF NEW CONTENT

Add New Section 2.?.? UL Publications

Underwriters Laboratories Inc., 333 Pfingsten Road, Northbrook, IL 60062-2096.






ANSI/UL 1638, Visual Signaling Appliances — Private Mode Emergency and General Utility Signaling ,5th edition, 2001, revised 2016.


ANSI/UL 1971, Standard for Signaling Devices for the Hearing Impaired , 3rd edition, 2002, revised2013.

ANSI/UL 1981, Central Station Automation Systems , 3rd edition, 2003, revised 2015.

ANSI/UL 2017, Standard for General-Purpose Signaling Devices and Systems , 2nd edition, 2008,revised 2016.

ANSI/UL 2572, Mass Notification Systems , 2nd edition, 2011, revised 2016 .

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


This proposal requests to add a new section in Referenced Publications and places those UL Standards that were removed from 2.3.1 (PI 552) under a separate section identified as UL Publications and also updates the referenced standards to the current editions.


Submitter Full Name: Ronald Farr


Street Address:

City:

State:

Zip:



65 of 1374 6/30/2016 11:10 AM

Public Input No. 207-NFPA 72-2016 [ New Section after 3.3.275 ]

Speaker

A person who delivers speciifc insutrcitons or information to occupants in a building or to those that are inareas outside around building.


As part of the CC TG on terms, the term "Speaker" was reviewed throughout the entire document for proper use. In some cases it refers to a physical appliance while other sections use it to refer to a person. There needs to be a definition as to what a speaker is when referring to a person who is delivering instructions and or information to occupants.

For an example of how the term is used within NFPA 72, see annex section A.24.3.2.


Submitter Full Name: Rodger Reiswig

Organization: Tyco SimplexGrinnell

Street Address:

City:

State:

Zip:

Submittal Date: Wed May 18 11:47:25 EDT 2016


110 of 1374 6/30/2016 11:10 AM


Emergency Management Program

3.3.x A performance-based set of all emergency functions necessary to be prepared and carried out tomanage an emergency, which spans four phases, including mitigation, preparedness, response, andrecovery, for a facility.


See Public Input No. 484. Added new term, "emergency management program," to Section 3.3 in order to understand its use as part of new term, "emergency operations and response plan."



Public Input No. 510-NFPA 72-2016 [Section No. 3.3.33] Public Input Nos. 489 - 507 and 509 - 512


Submitter Full Name: Bruce Abell

Organization: US Army Corps of Engineers

Street Address:

City:

State:

Zip:



86 of 1374 6/30/2016 11:10 AM


7 . 1.6

The requirements of Chapters 10 , 12 , 14 , 17 , 18 , 21 , 23 , 24 , 26 , and 27 shall apply unlessotherwise noted in this chapter.


if PI 722 is accepted this is redundant information and would not be required, this can lead to confusion and is additional non-required test that is not enforceable as code language.



Public Input No. 722-NFPA 72-2016 [New Section after 1.3.4] would replace this code section


Submitter Full Name: Thomas Parrish


Street Address:

City:

State:

Zip:



113 of 1374 6/30/2016 11:10 AM

Public Input No. 512-NFPA 72-2016 [ New Section after A.3.3.90 ]

Emergency Management Program

A.3.3.x Mitigation activities are those designed to reduce or eliminate the impact of hazards. Preparednessactivities include those that build organizational and individual capabilities to deal with disasters. Responseactivities include all necessary action to stop ongoing negative effects of a disaster. Recovery activities arethose that restore the organization, its employees, and the community back to normal. The facility shouldcommunicate its needs and vulnerabilities to those responsible for providing emergency response to thecommunity, especially to the facility, and should identify the capabilities of its community in supporting theirmission during the process of developing the emergency management program. Typically, an organizationmay appoint an emergency management coordinator, who then establishes an emergency managementcommittee to manage the program and update it continuously as needed. Emergency managers considerand take into account all hazards, all phases, all impacts, and all stakeholders relevant to disasters.


See Public Input No. 484. Since it is recommended that "emergency management program" be added to Chapter 3 of NFPA 72 (2016), the contents with this public input are intended to supplement the understanding and application of the new term to Section 3.3.







Street Address:

City:

State:

Zip:



1113 of 1374 6/30/2016 11:10 AM


24.1.3

The requirements of Chapters 7 , 10 , 12 , 17 , 18 , 21 , 23 , 26 , and 27 shall also apply unlessotherwise noted in this chapter.


if PI 722 is accepted this is redundant information and would not be required, this can lead to confusion and is additional non-required test that is not enforceable as code language.



Public Input No. 722-NFPA 72-2016 [New Section after 1.3.4] relocates these requirements to CH 1




Street Address:

City:

State:

Zip:



882 of 1374 6/30/2016 11:10 AM

Public Input No. 779-NFPA 72-2016 [ Section No. 24.3.1.2 ]

24.3.1.2*

Where no listed loudspeaker do not exists to achieve the intelligibility requirements of the Code for anotification zone, nonlisted loudspeakers shall be permitted to be installed to achieve the intelligibility forthat notification zone.


Rewording the verbiage of this section


Submitter Full Name: Sagiv Weiss-Ishai

Organization: San Francisco Fire Department

Affilliation: SFFD

Street Address:

City:

State:

Zip:



883 of 1374 6/30/2016 11:10 AM


24.3.2* Microphone Use.

All authorized users of systems that have microphones for live voice announcements shall be provided withposted instructions for using the microphone in accordance with the emergency response plan asapproved by the authority having jurisdication .


Only authorized person(s) should be able to announce live emergency messages.If posted messages are required by this section, they must be included on the emergency response plans and be specifically reviewed and approved by the AHJ prior to their posting




Affilliation: SFFD

Street Address:

City:

State:

Zip:



884 of 1374 6/30/2016 11:10 AM

Public Input No. 493-NFPA 72-2016 [ Sections 24.3.6.1, 24.3.6.2 ]

Sections 24.3.6.1, 24.3.6.2

24.3.6.1*

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

24.3.6.2*

Based on the emergency operations and response plan, emergency messages shall have content thatprovides information and instructions to people in the building, area, site, or installation.


See Public Input No. 484. Note: It should be understood that the submitter for this particular public input did NOT identify each and every occurrence of where to make this change within NFPA 72 because this is a conceptual issue to address and resolve GLOBALLY. So, there are other sections within NFPA 72 that are affected and will be subject to modifications. Then, correlate this task with the technical committees from other NFPA codes, standards, and recommended practices affected by this particular proposed global change with respect to the use and application of specific terms that are unique and distinct within the National Fire Codes, where there is an accompanying set or sets of minimum requirements linked to such terms.







Street Address:

City:

State:

Zip:



885 of 1374 6/30/2016 11:10 AM


24.3.6.2*

Based on the emergency response plan, pre recorded emergency voice messages shall have content thatprovides information and instructions to people in the building, area, site, or installation.


Pre recorded voice messages are different from posted or live messages to be announced via a microphone.




Affilliation: SFFD

Street Address:

City:

State:

Zip:



886 of 1374 6/30/2016 11:10 AM


24.3.6.3*

A message template of the pre-recorded emergency voice message shall be developed for each messagerequired in 24.3.6.1. and be included on the permit plans.

Message(s) in other langauge(s) than English, shall be permitted to be added to Engilsh languagemessage(s) as approved by the AHJ


The intent of this proposal is to require all voice messages to be provided in the English language but to allow the addition of other language (s) if approved by the AHJ.




Affilliation: SFFD

Street Address:

City:

State:

Zip:

Submittal Date: Thu Jun 30 00:01:31 EDT 2016


887 of 1374 6/30/2016 11:10 AM


24.3.7.1 *

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

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

(2) In-building mass notification systems (see Section 24.5)

(3) Wide-area mass notification systems (see Section 24.6)

(4) Distributed recipient mass notification systems (DRMNS) (see Section 24.7)

Additional Proposed Changes

File Name Description Approved

24.3.7.1_Annex.docx


The IBC relies on NFPA72 to set the design and installation requirements for Fire Emergency Voice Alarm Communication Systems (EVACS). EVAC (as is referenced by both IBC and NFPA72) are traditionally understood to be UL864 listed systems. Certainly where Fire EVAC systems are required by the building code, there is a minimum expectation of UL864 systems with voice capabilities. But NFPA72 broadens the Emergency Communication System definition to also include In-Building MNS and Wide Area MNS, which are also required to support voice notification, but for a broader range of emergencies. Since MNS systems require risk assessment, there is an opportunity to assess a wider performance based design perspective, then a strictly UL864 listed system, or available UL864 & UL2572 listed combination systems which may previously only been considered. When presented and approved by the authority having jurisdiction, both fire and voice performance requirements of EVAC can be meet and even exceeded when there is an advantage to designing with separate but integrated listed systems. For example a UL864 listed fire system where voice is provided by a listed and interfaced UL2572 listed system might be considered by the authority having jurisdiction for some performance based designs. This public input seeks to more clearly establish the possibility of integrated systems for consideration by system designer and the authority having jurisdiction.


Submitter Full Name: Michael Pallett

Organization: Telecor Inc.

Street Address:

City:

State:

Zip:

Submittal Date: Sat Jun 25 11:40:12 EDT 2016


888 of 1374 6/30/2016 11:10 AM

Other codes reference NFPA72 with respect to the Emergency Voice Alarm Communications Systems

(EVAC) for design and installation requirements (e.g., IBC 2015: 907.5.2.2). If EVAC systems are

required, they are expected to be UL864 listed systems. However, owners or designers could identify

risks in addition to fire that might also require additional emergency communications systems such as

In‐building MNS, Wide‐area MNS, or Distributed recipient MNS. If a Mass Notification System (MNS) is

included in the design, a risk assessment must be conducted. In consideration of the risk assessment,

related design could include combinations of the Emergency Communications Systems options

presented in 24.3.7.1. For example, depending on the specifics of the facility under consideration, the

design could include combination systems or other combinations of separate UL864, UL2017, and

UL2572 listed equipment as long as these systems are interfaced in compliance with chapter 24 and are

approved by the AHJ.


24.3.7.2

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

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

(2) Two-way radio communications enhancement systems (see Section 24.9)

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

Elevator emergency

(4) Stairway communications systems (see Section 24.

11

(5) 12 )

(6) Stairway communications Elevator Landing Communications systems ( see Section See Section24. 12 13 )

(7) Occupant Evacuation Elevator Lobby Communications Systems (See Section 24.14)


See rational for PI # 330 for Section 24.11 to delete this system from NFPA 72See rational for PI # 331 for adding Section 24.13 after section 24.12See rational for PI # 332 for adding Section 24.14 after section 24.13



Public Input No. 330-NFPA 72-2016[Section No. 24.11]

This proposal includes the rational for deleting this systemfrom NFPA 72

Public Input No. 331-NFPA 72-2016 [NewSection after 24.12]

New proposed section for elevator landing communicationsystem


New proposed section for Occupant Evacuation ElevatorLobby communication systems

Public Input No. 334-NFPA 72-2016[Section No. 24.3.7.2]




Affilliation: SFFD

Street Address:

City:

State:

Zip:



889 of 1374 6/30/2016 11:10 AM


24.3.7.2

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

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

(2) Two-way radio communications enhancement systems (see Section 24.9)

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

(4) Elevator emergency communications systems (see Section 24.11)

(5) Stairway communications systems (see Section 24.12)

(6) Elevator Landing communications systems (see Section 24.13)

(7) Occupant Evacuation Elevator Lobby communications systems (see Section 24.14)


In case if the Elevator Emergency communications systems in Section 24.11 will not be removed from NFPA 72 per PI 330 - I would still like to add the proposed systems in Sections 24.13 and 24.14 (Elevator Landing and OEE communication systems ) to Section 24.3.7.2 as specified two-way communication systems required by the building code (IBC-2015)



Public Input No. 330-NFPA 72-2016 [SectionNo. 24.11]

If this section will not be removed than this PI would apply


Added system specified in the building code


Added system specified in the building code

Public Input No. 333-NFPA 72-2016 [SectionNo. 24.3.7.2]

Prefer this PI to completely remove the system specified in24.11 from NFPA 72




Affilliation: SFFD

Street Address:

City:

State:

Zip:



890 of 1374 6/30/2016 11:10 AM


24.3.10.1 A Building System Information Unit

24.3.10.1.1 A Building System Information Uit which only displays information and events from the MassNotification Systme shall comply with Sections 23.8.4.2.1 and 23.8.4.2.2



BSIU_Diagram_FINAL_6_26_16_.pdf BSIU Diagram


This PI supports the code change proposals in Chapter 23 for the BSIU. This will allow the inclusion of MNS in the BSIU and follow the requirements in 23.8.4.2.1 and 23.8.4.2.2Buildings are advancing with technologies in HVAC, Security, Elevators, Energy Controls, Healthcare and Lighting. There are integration and human interfaces that the building operators and designers are expecting. First responders are embracing new technologies and the fire life safety industry needs to do so all well without affecting reliability and performance. This public input is the first step in taking the fire life safety system into the technology flow. It defines the PC Workstation as the interface with the complete building technology. And for the first time we introduce the use of the current PC Workstation technology having UL Listing for “Shock and Hazard” to be a part of the total building system without the UL 864 listing which is a hindrance to the advancements in technologies. Please see the attached for additional descriptions.


Submitter Full Name: Vince Baclawski

Organization: Nema

Street Address:

City:

State:

Zip:



891 of 1374 6/30/2016 11:10 AM


24.3.10* Control Unit Listing for Mass Notification Systems.

Control units installed as part of a mass notification system shall be in compliance with this Code and atleast one of the following applicable standards: and ANSI/ UL 864, Standard for Control Units andAccessories for Fire Alarm Systems

ANSI/UL 2017, Standard for General-Purpose Signaling Devices and Systems

ANSI/ UL 2572, Mass Notification Systems .


ANSI/UL2572 includes unique requirements for Mass Notification Systems which are derived from Chapter 24. Examples of unique requirements are: priority of signaling, overriding and relinquishing control of the fire alarm signaling, not overriding special notification releasing signaling, activating notification appliances that have completed the minimum number of required cycles once every 30 seconds. A single system or control unit is permitted to provide multiple life safety services when evaluated to the respective requirements as stated in 24.5.23. By revising 24.3.10, it does not prohibit combination systems listed to ANSI/UL864 or ANSI/UL2017 from providing mass notification service, but those systems must also be evaluated to ANSI/UL2572. This revision will help reduce confusion for AHJs and customers.



Public Input No. 693-NFPA 72-2016 [Section No. A.24.3.10]


Submitter Full Name: Derek Mathews


Street Address:

City:

State:

Zip:



892 of 1374 6/30/2016 11:10 AM

Public Input No. 508-NFPA 72-2016 [ New Section after 24.3.11.1 ]

TITLE OF NEW CONTENT

Type your content here ... 24.3.11.1.1 When an owner has a campus setting of buildings that has conducteda Risk Analysis, when new buildings are built within the same campus, the existing Risk Analysis can beutilized .


This PI will support the advancement of ECS-MNS into national building codes. It clarifies questions being raised by higher education management that question if they have a campus wide Risk Analysis do need need to conduct another one when a new building is built.


Submitter Full Name: Daniel Finnegan

Organization: Siemens Industry Inc

Street Address:

City:

State:

Zip:



893 of 1374 6/30/2016 11:10 AM


24.3.11.4

The risk analysis shall be permitted to be limited in scope to address the communication requirements of anexisting emergency operations and response plan.


See Public Input No. 484.







Street Address:

City:

State:

Zip:



894 of 1374 6/30/2016 11:10 AM


24.3.11.10

The risk analysis shall be used as the basis for development of the ECS provisions of the facilityemergency operations and response plan.









Street Address:

City:

State:

Zip:



895 of 1374 6/30/2016 11:10 AM


24.3.12* Emergency Response Plan Elements.

A well-defined emergency operations and response plan shall be developed in accordance withNFPA 1600 and NFPA 1620 as part of the design and implementation of a mass notification system.









Street Address:

City:

State:

Zip:



896 of 1374 6/30/2016 11:10 AM


24.3.13.6

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


A Correlating Committee task group on language/terms reviewed the language of the Code for consistency and grammar.

Editorial revision to align with the common usage elsewhere in the Code regarding hyphenating "wide-area."


Submitter Full Name: Lawrence Shudak


Street Address:

City:

State:

Zip:



897 of 1374 6/30/2016 11:10 AM

Public Input No. 435-NFPA 72-2016 [ Section No. 24.3.13.8.1 ]

24.3.13.8.1*

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

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

24.3.13.8.1.1

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

24.3.13.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.

comply with NFPA 1221, Standard for the Installation, Maintenance, and Use of Emergency Services

Communications Systems.


All the installation requirements including survivabillity requirements for radio enhancement two way communication systems are included in NFPA 1221. There should not be redundant and/or conflicting requirements in NFPA 72. The specific servivavibility requirements for the radio systems are listed in Section 9.6.2.1.1 and Section 5.10 of NFPA 1221

9.6.2.1.1* Where a two-way radio communications enhance-ment system is used in lieu of a two-way in-building wired emer-gency communications system, it shall have a pathwaysurvivability of Level 1, Level 2, or Level 3. [72:24.3.13.8.1]Exception: Where leaky feeder cable is utilized as the antenna, it shallnot be required to be installed in metal raceway. [72:24.3.13.8.1]



Public Input No. 438-NFPA 72-2016 [Section No. 24.3.13.8.3]





Affilliation: SFFD

Street Address:

City:

State:

Zip:



898 of 1374 6/30/2016 11:10 AM


24.3.13.8.2

Where a two-way radio communications enhancement system is used in lieu of a two-way in-building wiredemergency communications system required by other codes or standards , the design of the system shallbe approved by the authority having jurisdiction.


In some jurisdictions, (such as SFFD), the radio enhancement system is a mandatory system (for high-rise buildings) and it is not installed in lieu of another wired-system.There is no reason to include the "in lieu of.." language in this section.

This current section has also a conflict with the IBC-2015 requirement (below) which uses the opposite requirement: (wired system installed in lieu of a radio system which indicates that the Radio system is the mandatory system)

[F] 907.2.13.2 Fire department communication system.Where a wired communication system is approved in lieu ofan emergency responder radio coverage system in accordancewith Section 510 of the International Fire Code, the wiredfire department communication system shall be designed andinstalled in accordance with NFPA 72 and shall operatebetween a fire command center complying with Section 911,elevators, elevator lobbies, emergency and standby powerrooms, fire pump rooms, areas of refuge and inside interiorexit stairways. The fire department communication deviceshall be provided at each floor level within the interior exitstairway.




Affilliation: SFFD

Street Address:

City:

State:

Zip:



899 of 1374 6/30/2016 11:10 AM


24.3.13.8.3*

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


This requirement is redundant and conflicts with 24.3.13.8.1 which established pathway survivability for the riser wiring. This requirement could result in riser wiring being required to have a 2 Hour fire rating in a building that only requires a 1 Hour fire rating.







Street Address:

City:

State:

Zip:



900 of 1374 6/30/2016 11:10 AM


24.3.13.8.3 *

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


Specific installation requirements for radio enhancement systems should be included only in NFPA 1221



Public Input No. 435-NFPA 72-2016 [SectionNo. 24.3.13.8.1]

reference to NFPA 1221 as the applicable code for radiosystems installations




Affilliation: SFFD

Street Address:

City:

State:

Zip:



901 of 1374 6/30/2016 11:10 AM


24.3.13.8.3*

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


A Correlating Committee task group on language/terms reviewed the language of the Code for consistency and grammar. Editorial correction. The intent is to be fire-rated (actually fire-resistance rated). Add "fire" to the text to communicate intent and align with usage elsewhere in the Code.




Street Address:

City:

State:

Zip:



902 of 1374 6/30/2016 11:10 AM


24.3.13.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 to match the enclosure ratings .


this is related to PI-430 that would remove the 2 hour requirement and follow the requirements of 24.3.13.8.1 for pathway survivability. This removes the reference to a 2 hour enclosure for buildings that may only have a one hour fire resistance rating per the Building codes. If PI-430 is accepted this would need to also be accepted to eliminate a potential correlation issue.



Public Input No. 430-NFPA 72-2016 [Section No. 24.3.13.8.3] needed if PI-430 is accepted,




Street Address:

City:

State:

Zip:



903 of 1374 6/30/2016 11:10 AM


24.3.13.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 firestopped to2-hour ratings.


Specific installation requirements for radio enhancement systems should be included only in NFPA 1221



Public Input No. 435-NFPA 72-2016 [Section No. 24.3.13.8.1] Reference to NFPA 1221




Affilliation: SFFD

Street Address:

City:

State:

Zip:



904 of 1374 6/30/2016 11:10 AM


24.3.13.8.4

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


A Correlating Committee task group on language/terms reviewed the language of the Code for consistency and grammar. Editorial correction. The intent is to be fire-rated (actually fire resistance rated) . Add "fire" to the text to communicate intent and align with usage elsewhere in the Code.




Street Address:

City:

State:

Zip:



905 of 1374 6/30/2016 11:10 AM


24.4.4.2*

Except as specified in 24.4.4.3, in occupancies where sleeping accommodations are provided and thevoice message is intended to communicate information to those who could be asleep, a low - frequencytone that complies with 18.4.5 shall be used.



The term “low frequency” is used 17 times in the Code, 15 times without the hyphen. Revise the term in this clause to align with the usage elsewhere in the Code.




Street Address:

City:

State:

Zip:



906 of 1374 6/30/2016 11:10 AM


24.4.4.3*

In areas where sleeping accommodation are provided, but the voice communication system is used tocommunicate to occupants who are awake, the low - frequency tone shall not be required.



The term “low frequency” is used 17 times in the Code, 15 times without the hyphen. Revise the term in this clause to align with the usage elsewhere in the Code.




Street Address:

City:

State:

Zip:



907 of 1374 6/30/2016 11:10 AM


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 selected notificationzone.

(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 operations and response plan.



Note: It should be understood that the submitter for this particular public input did NOT identify each and every occurrence of where to make this change within NFPA 72 because this is a conceptual issue to address and resolve GLOBALLY. So, there are other sections within NFPA 72 that are affected and will be subject to modifications. Then, correlate this task with the technical committees from other NFPA codes, standards, and recommended practices affected by this particular proposed global change with respect to the use and application of specific terms that are unique and distinct within the National Fire Codes, where there is an accompanying set or sets of minimum requirements linked to such terms.







Street Address:

City:

State:

Zip:



908 of 1374 6/30/2016 11:10 AM

Public Input No. 509-NFPA 72-2016 [ Sections 24.4.8.3.1, 24.4.8.3.2 ]

Sections 24.4.8.3.1, 24.4.8.3.2

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 other signalingzones in accordance with the building fire safety emergency operations and response plan.

24.4.8.3.2

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


While the term “building fire safety plan” is defined in the chapter of NFPA 72 for specific terminology and their related definitions (i.e., Chapter 3), it is important to note that ONLY Section 24.4.8, which is the portion of the chapter for emergency communications systems in NFPA 72 addressing relocation and partial evacuation, includes associated requirements linked to “building fire safety plan.” See Public Input No. 484.







Street Address:

City:

State:

Zip:



909 of 1374 6/30/2016 11:10 AM

Public Input No. 778-NFPA 72-2016 [ New Section after 24.4.8.3.2 ]

Partial Evacuation

24.4.8.4 Under a fire condition, where the system is used to transmit Partial Evacuation instructions, thealert tone specified in 24.4.2.1 followed by a message (or messages where multi-channel capability is used)shall be provided.


This section is added to separate the alert tones required for partial evacuation from the alert tones required for relocation.When partial evacuation of occupants is employed, the occupants on specific floors or areas in the building are expected to evacuate/exit the building and not to relocate to another floor/area in the building.Therefore the evacuation message (which is the same message for total or partial building evacuation) shoul be preceded and followed by the same alert tone described in section 24.4.2.1




Affilliation: SFFD

Street Address:

City:

State:

Zip:



910 of 1374 6/30/2016 11:10 AM

Public Input No. 776-NFPA 72-2016 [ Section No. 24.4.8.4 [Excluding any Sub-Sections]

]

Where provided, loudspeakers in each enclosed stairway, each exit passageway, each occupantevacuation elevator lobby, and each group of elevator cars within a common hoistway shall be connected toseparate notification zones for manual paging only.


This specific requirement comes from the IBC (2012 and 2015 Edition) specifically for occupant evacuation elevator lobbies.See section and rational below:

907.5.2.1 Audible alarms. Audible alarm notificationappliances shall be provided and emit a distinctive sound thatis not to be used for any purpose other than that of a firealarm.Exceptions:1. Audible alarm notification appliances are notrequired in critical care areas of Group I-2 Condition2 occupancies that are in compliance with Section907.2.6, Exception 2.2. A visible alarm notification appliance installed in anurses’ control station or other continuouslyattended staff location in a Group I-2 Condition 2suite shall be an acceptable alternative to the installation of audible alarm notification appliancesthroughout the suite in Group I-2 Condition 2 occupancies that are in compliance with Section 907.2.6,Exception 2.3. Where provided, audible notification applianceslocated in each occupant evacuation elevator lobbyin accordance with Section 3008.9.1 shall be connected to a separate notification zone for manualpaging only.

Exception 3 is intended to address the concern thatautomatic emergency voice/alarm messages do notinterfere with operation of the two-way communication associated with the occupant evacuation elevators. Live voice messages would be appropriate inthe lobbies.




Affilliation: SFFD

Street Address:

City:

State:

Zip:



911 of 1374 6/30/2016 11:10 AM


24.4.8.4.1

The evacuation signal specified in 18.4.2 shall not operate in elevator cars, exit stair enclosures, and exitpassageways.


The intent is to clarify the "evacuation signal" mentioned in this section




Affilliation: SFFD

Street Address:

City:

State:

Zip:



912 of 1374 6/30/2016 11:10 AM


24.4.8.4.2

Manually activated speakers textual audible notification appliance shall be permitted in exit stairenclosures and exit passageways in buildings that have emergency voice/alarm communications systemsin accordance with Section24.4.


As part of the CC TG on terms, the term "Speaker" was reviewed throughout the entire document for proper use. In some cases it refers to a physical appliance while other sections use it to refer to a person. In this section the term is for an appliance and the proper term "Textual Audible Notification Appliance" should be used.




Street Address:

City:

State:

Zip:



913 of 1374 6/30/2016 11:10 AM


Sections 24.5.1.7, 24.5.1.8

24.5.1.7

The priority level of recorded messages shall be determined by the emergency and operations andresponse plan.

24.5.1.8

Only recorded messages determined by the emergency operations and response plan to be of higherpriority than fire alarm activation shall be permitted to override the fire alarm notification and initiate themass notification priority indicator.










Street Address:

City:

State:

Zip:



914 of 1374 6/30/2016 11:10 AM


24.5.2.2*

Where required by the emergency operations and response plan, the mass notification system shallprovide the capability for authorized personnel to remotely activate live and prerecorded emergencymessages.









Street Address:

City:

State:

Zip:



915 of 1374 6/30/2016 11:10 AM


24.5.8 Initiation Indication.

The source of system activation shall be visibly and audibly indicated at the emergency command centerand at the building control unit, unless otherwise required by the emergency operations and response plan.









Street Address:

City:

State:

Zip:



916 of 1374 6/30/2016 11:10 AM


24.5.9.4

Non-fire emergency manual actuating stations (boxes) shall be listed to ANSI/UL 2017, Standard forGeneral Purpose Signaling Devices and Systems or UL2572, Standard for Safety, Mass NotificationSystems .


Chapter 24 references UL2572 as an qualifying standard for In building Mass Notification Systems. UL2572 contains requirements for construction of enclosures (section 5) and Performance - Other Tests including Jarring Tests (section 57), Ignition Tests Through Bottom-Panel Openings (section 61), and Mechanical Strength Test for Metal Enclosures and Guards (section 65), and Wet Location and Outdoor-Use Tests (section 74). It reasonable that a Mass Notification System with its required components, submitted and tested to the 2572 standard should not also be required to also have components such as manual actuating stations (boxes) be tested to UL2017 - in addition.




Street Address:

City:

State:

Zip:



917 of 1374 6/30/2016 11:10 AM


24.5.16.2

The visible notification required by 24.5.16.1 shall be accomplished using strobes visible notificationappliances .


As part of the CC TG on terms, the term "light" was reviewed throughout the entire document for proper use. In some cases it refers to a physical appliance while other sections use it to refer to the output of an appliance. In this section the term is for an appliance and the proper term "visible notification appliance" should be used.




Street Address:

City:

State:

Zip:



918 of 1374 6/30/2016 11:10 AM


Sections 24.5.16.2, 24.5.16.3

24.5.16.

2 2

The visible notification required by 24.5.16.1 shall be accomplished using strobes , graphic or textualsigns .

24.5.16.

3 3

In addition to the strobes required by 24.5.16.1 , textual, graphic, or video displays shall be permitted.


Due to enhanced diagnoses of children and adults on the autism spectrum, school districts and non-profit organizations that serve these individuals are expanding programs to meet the needs of this growing population. Many programs are constructing new buildings to handle the increased demand. Staff members who work with ASD individuals are finding that emergency voice alarm communication systems are far more effective at notifying persons with autism spectrum disorder (ASD) than the standard temporal 3 fire alarm pattern.

As currently written, section 24.5.16.2 gives code officials no other choice but strobes. While additional research is necessary, early studies along with interviews of people who work with these individuals are concluding that strobes can have an adverse affect on children and adults on the autism spectrum (or other sensory processing disorder). In some cases, children and adults on the autism spectrum have physically assaulted staff members to the point of causing injury because of the person's reaction to the strobe activating. On the other hand, activation of graphic and textual signs have not shown the same tendency for those on the autism spectrum to react violently.

In summary, my goal is to give code officials the authority to accept graphic or textual signs in place of strobes. The intent of the code is still met since signs will be provided for those with hearing impairments or when located in high-noise areas.


Submitter Full Name: John Swanson

Organization: MN State Fire Marshal Division

Street Address:

City:

State:

Zip:

Submittal Date: Tue Jan 12 17:42:06 EST 2016


919 of 1374 6/30/2016 11:10 AM


24.5.16.3

In addition to the strobes visible notification appliances required by 24.5.16.1, textual, graphic, or videodisplays shall be permitted.






Street Address:

City:

State:

Zip:



920 of 1374 6/30/2016 11:10 AM


24.5.17.1

Where strobes visible notification appliances are used as visible appliances , they shall meet therequirements of 24.5.17.2 through 24.5.17.10.


As part of the CC TG on terms, the term "light" and “strobe” was reviewed throughout the entire document for proper use. In some cases it refers to a physical appliance while other sections use it to refer to the output of an appliance. In this section the term is for an appliance and the proper term "visible notification appliance" should be used.




Street Address:

City:

State:

Zip:



921 of 1374 6/30/2016 11:10 AM


24.5.17.3

Strobes Visible Notification Appliances used in combination systems where the same strobe visiblenotification appliance is used for both mass notification and fire notification shall comply with the following:

(1) Be clear or nominal white, meeting the listing requirements of ANSI/UL 1971, Standard for SignalingDevices for the Hearing Impaired

(2) Have no marking or be marked with the word “ALERT” stamped or imprinted on the appliance

(3) Be visible to the public






Street Address:

City:

State:

Zip:



922 of 1374 6/30/2016 11:10 AM


24.5.17.5

Strobes Visible notification appliances with colored lenses shall be marked with the listed effective intensityusing the lens color installed.






Street Address:

City:

State:

Zip:



923 of 1374 6/30/2016 11:10 AM


24.5.17.6

The spacing of colored strobes visible notification appliances shall be in accordance with public modespacing requirements of Section 18.5 using the effective intensity as the basis for spacing.






Street Address:

City:

State:

Zip:



924 of 1374 6/30/2016 11:10 AM


24.5.17.7

Where strobes visible notification appliances are used solely for mass notification, the word “ALERT” shallbe stamped or imprinted on the appliance and be visible to the public.






Street Address:

City:

State:

Zip:



925 of 1374 6/30/2016 11:10 AM


24.5.17.8

Where colored strobes are visible notification appliances used solely for mass notification, they shall belisted to an applicable standard such as ANSI/UL 1638, Visual Signaling Appliances — Private ModeEmergency and General Utility Signaling.






Street Address:

City:

State:

Zip:



926 of 1374 6/30/2016 11:10 AM


24.5.17.9

Strobe Visible notification appliances listed to ANSI/UL 1971, Standard for Signaling Devices for theHearing Impaired, shall be considered as meeting the intent of this Code.

Exception: Color lens strobes visible notification appliances shall meet the requirements of 24.5.17.8.






Street Address:

City:

State:

Zip:



927 of 1374 6/30/2016 11:10 AM


24.5.17.10

Strobes Visible notification appliances used for mass notification shall meet the synchronizationrequirements of Section 18.5.






Street Address:

City:

State:

Zip:



928 of 1374 6/30/2016 11:10 AM


24.5.24.2

Evaluation documentation in accordance with 7.3.9 shall be provided by the emergency communicationssystem designer attesting to the fact that the public address system has been evaluated and:

(1) meets the performance requirements of Chapter 24 and the emergency response plan theemergency response plan, and

(2) a ll cases where the public address system does not meet Chapter 24 performance requirements aredocumented, and evaluated for risk in the risk assessment .


Public Address systems are defined (3.3.210) independently of Mass Communication Systems (3.3.85.1.3) and Emergency Communication Systems (3.3.85). Therefore, it is reasonable to conclude that a Public Address System is intentionally considered to be different then an Emergency Communication System. But 24.5.24.2 appears to assign the same performance criteria to a P.A. system as an ECS; in fact, all ECS systems inclusively including MNS and EVAC. This therefore would include 24.3.10, requiring the P.A. system to be listed under UL864, UL 2017, or UL2572, which would then require the P.A. system to be equivalent to a listed ECS system. This is self referential and ultimately negates the entire clause in practicality. Commercial P.A. systems are not usually designed to that same criteria as a ECS systems, so they are not likely to be equivalent. Further, it is unlikely that a system designer would attest that any system meets the performance requirements of chapter 24 due to the significant scope of chapter 24 and extensive testing that would need to be undertaken to make such a claim. This testing might be expected to be consistent with the testing required by UL for standards such as both 2572 and 864, before such a claim might be made by an independent designer. Regardless of the current requirements imposed by 24.5.24, the circumstances where a P.A. system is utilized for emergency communications is always a function of AHJ approval. For example, the US military bases where P.A. systems are used for Emergency Communications are not UL2572 listed, and have not been expected to meet all the performance requirements of Chapter 24.

This public input seeks to legitimize 24.5.24.2 by making it practical to meet. It is unlikely that existing or new P.A. systems will meet all the performance requirements of Chapter 24, or be designed to meet UL2572. With this change the onus is now to declare P.A. system deficiencies with respect to Chapter 24, so that they can be properly included and analyzed as to risk from the perspective of a risk assessment. This clause could be supported by manufactures who voluntarily disclose aspects of their systems that do not meet chapter 24, to support system designers in evaluating the risk of using their products. The annex material is intended to provide examples to illustrate a conditions where the P.A. system does not meet the performance requirements of chapter 24, yet still the risk may be evaluated as reasonable, and warrant the authority having jurisdiction's approval. As the clause currently stands, practically speaking, P.A. systems are unlikely to ever satisfy the clause and therefore the option and risks of P.A. system being used in this way is unlikely to be presented in the risk assessment for consideration by the AHJ. This appears to contradict the intent of the clause.



Public Input No. 427-NFPA 72-2016 [Section No. 24.5.24.2] Both refer to the same paragraph

Public Input No. 427-NFPA 72-2016 [Section No. 24.5.24.2]



929 of 1374 6/30/2016 11:10 AM



Street Address:

City:

State:

Zip:



930 of 1374 6/30/2016 11:10 AM


24.5.24.2 *

Evaluation documentation in accordance with 7.3.9 shall be provided by the emergency communicationssystem designer attesting to the fact that the public address system has been evaluated and meets theperformance requirements of Chapter 24 and the emergency response plan.



24_5_24_2_Annex.docx


The annex material is intended to provide examples to illustrate a conditions where the P.A. system does not meet the performance requirements of chapter 24, yet still the risk may be evaluated as reasonable, and warrant the authority having jurisdiction's approval. As the clause currently stands, practically speaking, P.A. systems are unlikely to ever satisfy the clause and therefore the option and risks of P.A. system being used in this way is unlikely to be presented in the risk assessment for consideration by the AHJ. This appears to contradict the intent of the clause.



Public Input No. 426-NFPA72-2016 [Section No. 24.5.24.2]

Annex material, and material for this paragraph are both attempting toprovide a practical implementation of the requirement.

Public Input No. 426-NFPA72-2016 [Section No. 24.5.24.2]




Street Address:

City:

State:

Zip:



931 of 1374 6/30/2016 11:10 AM

A.24.5.24.2

Based on a risk assessment, the utilization of a P.A. system, used for Emergency Communications, that does not meet all performance requirements of chapter 24 can still be evaluated for risk, and utilized with the approval of the authority having jurisdiction. For example, consider a P.A. system with outdoor horns, that do not meet the requirements for HPSA nor sound pressure requirements from Chapter 18 (referenced by Chapter 24). In the risk assessment, this can be presented as a reasonable risk based on the argument that an evacuation of such a structure will not utilize outdoor horns. However, a similar argument might fail to be considered reasonable for a large sporting facility.

Another example could be a P.A. System that is not listed for UL864, UL2017, or UL2572, but is an Attendant Monitored System (as per UL2017), and is being utilized regularly with a history of reliability. Similarly, many constant use Attendant Monitored P.A. systems do not support the monitoring for integrity requirements of sections 10.6.9, 10.18 and 12.6 (as required in 24.3.5.2). However, despite these non‐compliances, these P.A. systems might be considered for approval when the risks for their use are documented and assessed. In either case, based on a risk assessment, the authority having jurisdiction is presented with facts that can be used to approve or deny the use of the P.A. System in those circumstances, for specific occupancy types.


24.5.25.2

All of the following features shall be provided in, or added to, the public address system:

(1) Emergency messages must have priority over non-emergency messages.

(2) All individual or zone speaker textual audible notification appliance volume controls must default tothe emergency sound level when used for an emergency mass notification message.

(3) When monitoring of circuit integrity is provided by the public address system, monitoring mustcontinue, even if local loudspeaker volume controls are placed in the “off” position.

(4) The required visible notification appliance network (i.e., strobes and textual signs) must be providedwhere required.






Street Address:

City:

State:

Zip:



932 of 1374 6/30/2016 11:10 AM


24.6.1.2

Where required by the emergency operations and response plan, multiple languages shall be permitted tobe used.










Street Address:

City:

State:

Zip:



933 of 1374 6/30/2016 11:10 AM


24.6.7.2*

HPSAs shall be installed at a height and orientation to prevent hearing damage to anyone in the immediatevicinity of the speakers appliances .


As part of the CC TG the term speakers was reviewed throughout the document. The term here should be modified to the term appliances.




Street Address:

City:

State:

Zip:



934 of 1374 6/30/2016 11:10 AM


24.7.3* Network Security Compliance.

DRMNS shall comply with NIST / Common Criteria / CIS / else security requirements, and have certaincertifications.

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


This is really a plug: in 2019 - and even in 2016 - requiring install behind a firewall barely scratch the surface. This is not enough as a requirement.

There are multiple security and risk management frameworks today, and there are a few emerging. It will be by the TC to review and select the most appropriate one(s), and possibly review certification / assessment processes. There are minimal security requirements in UL 2572 40.1-40.4 re data security and 40.5-40.6 re physical security; some are relevant, but may not be enough.


Submitter Full Name: Aviv Siegel

Organization: AtHoc Inc

Street Address:

City:

State:

Zip:



935 of 1374 6/30/2016 11:10 AM


24.8.15

If telephone jacks are provided, two or more portable handsets, as determined by the authority havingjurisdiction, a minimum of five portable handsets shall be stored at each control center for use byemergency responders.


It would reduce the confusion from 24.8.6. As of now with this code in place the AHJ chooses how many portable handsets they have in the control center. However in the testing method for the system performance (14.4.3.2 item 5(f) it states to test with five handsets simultaneously. So the code at question should correlate with 14.4.3.2 and 24.8.6 that way the client can receive a proper test according to 14.4.3.2.


Submitter Full Name: Anthony Rogers

Organization: Wilson Fire Equipment

Street Address:

City:

State:

Zip:

Submittal Date: Thu May 26 13:14:34 EDT 2016


936 of 1374 6/30/2016 11:10 AM

Public Input No. 330-NFPA 72-2016 [ Section No. 24.11 ]

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 in accordancewith ANSI/ASME A17.2, Guide for Inspection of Elevators, Escalators and Moving Walks .


The two way communication system in elevator cars should not be included in NFPA 72 since it is not under the jurisdiction of NFPA 72.This is a specific Elevator Code required system and only Elevator personnel has jurisdiction over the installation of this system inside elevator cars. Since it is not a Building Code required system - it should be deleted from NFPA 72.Typically, the Elevator Code ASME A17.1 references the NFPA 72 Code in Section 2.27 - "Emergency Operation and Signaling Devices" - however it does not specify compliance with NFPA 72 for this specific elevator in-car communication system.

If this section will be deleted from NFPA 72 - the elevator in-car communication system will still be installed in elevator cars per the A17.1 code which indicates that is not necessary to have this section in NFPA 72.



Public Input No. 329-NFPA 72-2016 [Section No. 24.11.2] This is a sub section to Section 24,11

Public Input No. 332-NFPA 72-2016 [New Section after 24.12]






Affilliation: SFFD

Street Address:

City:

State:

Zip:



937 of 1374 6/30/2016 11:10 AM


24.11.2

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


This sub section to section 24.11 should be deleted since it references a different Building two way communication system not governed by the ASME A17.1 code.

Section 24.11 specifically describes the elevator in-car two way communication system which is solely governed by the ASME A17,1 Code Section 2.27.

The two way communication system required in Occupant Evacuation Elevators lobbies is a Building system described in IBC-2015 Section 1009.8 which is required in elevator landings and specifically in OEEs lobbies - This is not an Elevator system and it is not required to comply with the ASME A17.1 code.

This is from IBC-2015 Section 1009.8 (This is a Building Code required system):1009.8 Two-way communication. A two-way communication system complying with Sections 1009.8.1 and 1009.8.2 shall be provided at the landing serving each elevator or bank of elevators on each accessible floor that is one or more stories above or below the level of exit discharge.

The OEE lobby section 3008.6.6 in IBC-2015 requires the same system described in 1009.8 since it references sub sections 1009.8.1 and 1009.8.2. Therefore this is a Building Code required system and not Elevator Code required system.

3008.6.6 Two-way communication system. A two-way communication system shall be provided in each occupant evacuation elevator lobby for the purpose of initiating communication with the fire command center or an alternate location approved by the fire department. The two-way communication system shall be designed and installed in accordance with Sections 1009.8.1 and 1009.8.2.

This is the section from the elevator Code ASME A17.1 - 2013 (Elevator Car required system)

2.27.1.1 Emergency Communications2.27.1.1.1 A two-way communications meansbetween the car and a location staffed by authorized personnel shall be provided. 2.27.1.1.2(a) Two-way communications shall be directed to alocation(s) staffed by authorized personnel who can takeappropriate action.(b) If the call is not acknowledged [2.27.1.1.3(c)]within 45 s, the call shall be automatically directed toan alternate on- or off-site location.2.27.1.1.3 The two-way communication meanswithin the car shall comply with the followingrequirements:



Public Input No. 330-NFPA 72-2016 [Section No. 24.11]



938 of 1374 6/30/2016 11:10 AM




Affilliation: SFFD

Street Address:

City:

State:

Zip:



939 of 1374 6/30/2016 11:10 AM


24. 13 Elevator Landing Communications System

24.13.1 Where required by the building code in force and not included as part of another emergencycommunications system, an elevator landing communications system shall be installed in

accordance with 24.13.

24.13.2 The elevator landing communications system shall be permitted to be integrated with anothertwo-way emergency communications system providing it is installed in accordance with 24.13.

24.13.3 The elevator landing communications system shall comprise with remotely locatedcommunications points and a central control point.

24.13.4 Each remote point shall have the capability to communicate with the central control point.

24.13.5* Quantity and locations of the remote communications points shall be as required by the buildingcode in force and engineering specifications.

24.13.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 acceptable to theauthority having jurisdiction where responsible personnel can initiate the appropriate response.

24.13.7 The physical location of the central control point shall be as designated by the building code inforce or the authority having jurisdiction.

24.13.8 The remote communications points shall provide for two-way communications, provide anaudible and visible signal to indicate communication has occurred, and indicate to the receiver thelocation sending the signal.

24.13.9 Instructions for the use of the elevator landing two way communication system, instructions forsummoning assistance via the system, and written identification, including in braille, of the location shallbe posted adjacent to each remote communications point.


Elevator landing two way communication systems are required by the Building code - IBC-2015 (Section 1009.8) to be installed in elevator landings of applicable elevators.

This is a very common required two-way communication system by the IBC code since there is a building code exception for areas of refuge in fully sprinklered buildings and in R-2 occupancies. Therefore this system must be included and specified in NFPA 72 as a building code required communication system. The term elevator landing includes both enclosed and unenclosed elevator lobbies (the elevator lobby is considered the immediate area in front of the elevator where occupants wait for elevator service)

This is the IBC-2015 Code section requiring the communication system in elevator landings:

1009.8 Two-way communication. A two-way communication system complying with Sections 1009.8.1 and 1009.8.2shall be provided at the landing serving each elevator or bankof elevators on each accessible floor that is one or more stories above or below the level of exit discharge.Exceptions:1. Two-way communication systems are not requiredat the landing serving each elevator or bank of elevators where the two-way communication system isprovided within areas of refuge in accordance withSection 1009.6.5.


940 of 1374 6/30/2016 11:10 AM

2. Two-way communication systems are not requiredon floors provided with ramps conforming to theprovisions of Section 1012.3. Two-way communication systems are not required atthe landings serving only service elevators that arenot designated as part of the accessible means ofegress or serve as part of the required accessibleroute into a facility.4. Two-way communication systems are not required atthe landings serving only freight elevators.5. Two-way communication systems are not required atthe landing serving a private residence elevator.









Affilliation: SFFD

Street Address:

City:

State:

Zip:



941 of 1374 6/30/2016 11:10 AM


24.14 Occupat Evacuation Elevator Lobby Communications System

24.14.1 A two-way communications system shall be provided in each occupant evacuation elevator lobbyfor the purpose of initiating communication with the central control point approved by the authority havingjurisdication.

24.14.2 The requirments in sections 24.13.1 through 24.13.9 shall apply


This is a a specific Building communication system required by IBC-2015 Section 3008.6.6 to be provided in Occupant Evacuation Elevator lobbies. Therefore, this system must be included in and specified by NFPA 72. Since it is not an Elevator Code required system it was proposed to remove this section from the Elevator (in-car) Communication system included in the 2016 Edition of NFPA 72.

Since this system is required by IBC-2015 to meet the same requirements of an elevator landing communication system specified in 1009.8.1 and 1009.8.2 - It is proposed to point to the previously added section 21.13 as a reference rather than repeating the same requirements for elevator landing communication system.

This is the section from IBC-2015 requiring this system:

3008.6.6 Two-way communication system. A two-way communication system shall be provided in each occupant evacuation elevator lobby for the purpose of initiating communication with the fire command center or an alternate location approved by the fire department. The two-way communication system shall be designed and installed in accordance with Sections 1009.8.1 and 1009.8.2



Public Input No. 331-NFPA 72-2016[New Section after 24.12]

This is the added section 24.13 referenced in this section forelevator landing communication system

Public Input No. 329-NFPA 72-2016[Section No. 24.11.2]

This PI is referenced in the rational for this proposal

Public Input No. 330-NFPA 72-2016[Section No. 24.11]

This PI is referenced in the rational for this proposal






Affilliation: SFFD

Street Address:

City:

State:

Zip:



942 of 1374 6/30/2016 11:10 AM


24.13.1.2

The emergency command center shall contain the following:

(1) The in-building fire emergency voice/alarm communications system equipment including:

(2) Fire alarm system controls

(3) Fire alarm system annunciator

(4) In-building fire emergency voice/alarm communications system controls

(5) Area of refuge (area of rescue assistance) emergency communications systems equipment

(6) Elevator emergency communications systems equipment

(7) Distributed recipient MNS control stations where provided

(8) Tables and chairs to accommodate emergency management staff

(9) Other equipment/information deemed necessary by the facility emergency operations and responseplan such as:

(10) Displays indicating the location of the elevators and whether they are operational

(11) Status indicators and controls for air-handling systems

(12) Fire fighter’s control panel for smoke control systems

(13) Fire department communications unit

(14) Controls for unlocking stairway doors simultaneously

(15) Security systems

(16) Emergency and standby power status indicators

(17) Telephone for emergency use with controlled access to the public telephone system

(18) Schematic building plans indicating the typical floor plan and detailing the building core, meansof egress, fire protection systems, security systems, fire-fighting equipment, and fire departmentaccess

(19) Generator supervision devices, manual start, and transfer features

(20) Other monitoring, control, information display, and management systems associated withoperation of the ECC






943 of 1374 6/30/2016 11:10 AM






Street Address:

City:

State:

Zip:



944 of 1374 6/30/2016 11:10 AM


24.14.6.1 General.

All designs shall meet the goals and objectives specified in 24.14.1 and shall be considered equivalent,provided that the performance criterion in 24.14.6.2 is met, the design team concurs with the design, andthe risk analysis considers the following factors:

(1) Number of persons to be notified

(2) Occupancy characteristics

(3) Anticipated threat

(4) Staff capabilities

(5) Coordination with the emergency operations and response plan










Street Address:

City:

State:

Zip:



945 of 1374 6/30/2016 11:10 AM

Public Input No. 205-NFPA 72-2016 [ Section No. A.24.3.1.1 ]

A.24.3.1.1

In certain situations, it is important to provide a distributed sound level with minimal sound intensityvariations to achieve an intelligible voice message. This differs from past fire alarm design practice thatused fewer notification appliances but with each having greater sound pressure output levels.Nonemergency system design practice is to use more speakers textual audible notification appliances andless sound intensity from each speaker textual audible notification appliance . Besides improvingintelligibility of the message, this approach minimizes annoyance to building occupants from the systemand lessens the likelihood of tampering with the system by occupants because of speakers textual audiblenotification appliance being too loud. In other applications, such as outdoor signaling where reverberationis not a problem, intelligibility can be achieved by using fewer appliances or clusters of appliances coveringlarger areas.

Intelligibility is a complex function of the source audio, the acoustic response of the architectural featuresand materials of the immediate vicinity, and the dynamics created by the room’s occupants. Refer toAnnex D for more information on speech intelligibility and how it is predicted. Spacing speakers textualaudible notification appliances closely can be an intelligibility-enhancing technique but can occasionallylead to opposite results when improperly designed. There are several techniques using directionalityfeatures that do not use closely spaced speakers textual audible notification appliance but rather use theroom/space acoustic response in their favor.






Street Address:

City:

State:

Zip:



1235 of 1374 6/30/2016 11:10 AM


A.24.3.1.2

In certain acoustically challenging areas, listed fire alarm speakers textual audible notification appliancesmight not be capable of producing an intelligible message. Non–fire alarm listed speakers textual audiblenotification appliances are permitted to be installed in these limited areas. A failure of a non-listed speakertextual audible notification appliances should not disrupt the operation of listed fire alarm speakers textualaudible notification appliances and operation of the fire alarm or mass notification control equipment.Typically, a dedicated speaker audio notification applaince circuit and other audio components such asamplifiers could be necessary to meet this functionality.


As part of the CC TG on terms, the term "Speaker" was reviewed throughout the entire document for proper use. In some cases it refers to a physical appliance while other sections use it to refer to a person. In this section the term is for an appliance and the proper term "Textual Audible Notification Appliance" should be used. Also changed the term "Speaker Circuit" to Notification appliance circuit.to align with the changes of the general term "speaker."




Street Address:

City:

State:

Zip:



1236 of 1374 6/30/2016 11:10 AM

Public Input No. 260-NFPA 72-2016 [ Section No. A.24.3.7 ]

A.24.3.7

One-way emergency communications systems are intended to broadcast information, in an emergency, topersonnel in one or more specified indoor or outdoor areas. It is intended that emergency messages beconveyed either by audible or visible textual means or both. This section does not apply to bells, horns, orother sounders and lights visible notification appliance , except where used in conjunction with the desiredoperation of emergency messages and signaling.

Two-way emergency communications systems are divided into two categories, those systems that areanticipated to be used by building occupants and those systems that are to be used by fire fighters, police,and other emergency services personnel. Two-way emergency communications systems are used both toexchange information and to communicate information, such as, but not limited to, instructions,acknowledgement of receipt of messages, condition of local environment, and condition of persons, and togive assurance that help is on its way.

NFPA 72 contains requirements that can impact the application of emergency communications systems.For instance, coordination of the functions of an emergency communications system with other systemsthat communicate audibly and/or visibly [such as fire alarm systems, security systems, public address (PA)systems] is essential in order to provide effective communication in an emergency situation. Conflicting orcompeting signals or messages from different systems could be very confusing to occupants and have anegative impact on the intended occupant response. Where independent systems using audible and/orvisible notification are present, the emergency communications system needs to interface with thosesystems to effect related control actions such as deactivating both audible and visible notificationappliances. The use of a single integrated combination system might offer both economic and technicaladvantages. In any case, coordination between system functions is essential. The coordination ofemergency communications systems with other systems should be considered part of the risk analysis forthe emergency communications system. (See Figure A.24.3.7.)

Additional documents such as NEMA Standard SB 40, Communications Systems for Life Safety in Schools,can also be used as supplemental resources to provide help with risk assessment and applicationconsiderations.

Figure A.24.3.7 Emergency Communications Systems.







1237 of 1374 6/30/2016 11:10 AM

Street Address:

City:

State:

Zip:



1238 of 1374 6/30/2016 11:10 AM


A.24.3.7

One-way emergency communications systems are intended to broadcast information, in an emergency, topersonnel in one or more specified indoor or outdoor areas. It is intended that emergency messages beconveyed either by audible or visible textual means or both. This section does not apply to bells, horns, orother sounders and lights, except where used in conjunction with the desired operation of emergencymessages and signaling.

Two-way emergency communications systems are divided into two categories, those systems that areanticipated to be used by building occupants and those systems that are to be used by fire fighters, police,and other emergency services personnel. Two-way emergency communications systems are used both toexchange information and to communicate information, such as, but not limited to, instructions,acknowledgement of receipt of messages, condition of local environment, and condition of persons, and togive assurance that help is on its way.

NFPA 72 contains requirements that can impact the application of emergency communications systems.For instance, coordination of the functions of an emergency communications system with other systemsthat communicate audibly and/or visibly [such as fire alarm systems, security systems, public address (PA)systems] is essential in order to provide effective communication in an emergency situation. Conflicting orcompeting signals or messages from different systems could be very confusing to occupants and have anegative impact on the intended occupant response. Where independent systems using audible and/orvisible notification are present, the emergency communications system needs to interface with thosesystems to effect related control actions such as deactivating both audible and visible notificationappliances. The use of a single integrated combination system might offer both economic and technicaladvantages. In any case, coordination between system functions is essential. The coordination ofemergency communications systems with other systems should be considered part of the risk analysis forthe emergency communications system. (See Figure A.24.3.7.)

Additional documents such as NEMA Standard SB 40, Communications Systems for Life Safety inSchools, can also be used as supplemental resources to provide help with risk assessment andapplication considerations.

Figure A.24.3.7 Emergency Communications Systems.


There is a typo within the diagram A.24.3.7 Emergency Communications Systems."Info command and contol section 24.13" It should say control and not contol




Affilliation: SFFD


1239 of 1374 6/30/2016 11:10 AM

Street Address:

City:

State:

Zip:



1240 of 1374 6/30/2016 11:10 AM


A.24.3.8

The layers can be used in combination. In all cases, the system design needs to follow the risk analysis andbe integrated into the emergency response plan. Research has shown that more than one layer has beenused to be effective. Multiple layers provide an extra level of notification (a safety net). The overall MNSapplication is likely to exploit a number of public and individual systems or components that combine toproduce a reliable and robust solution to achieve emergency notification objectives.

Layer 1 could consist of elements such as the following:

(1) Emergency voice/alarm communications systems (EVACS)

(2) In-building mass notification system (MNS)

(3) One-way voice communication systems (PA)

(4) Two-way voice communication systems

(5) Visible notification appliances

(6) Textual/digital signage/displays


(1) Wide-area outdoor mass notification systems (MNS)

(2) High power speaker arrays (HPSA)


(1) Short message service (SMS)

(2) Email

(3) Computer pop-ups

(4) Smartphone applications (Apps)

(5) Reverse 911/automated dialing


(1) Radio broadcast (satellite, AM/FM)

(2) Television broadcast (satellite, digital)

(3) Location specific messages/notifications

(4) Weather radios

(5) Social networks

Also see Optimizing Fire Alarm Notification for High Risk Groups research project.


As per 24.3.7 In-building mass notification systems was added to the list specifically so as not to inadvertently imply to a casual reader that MNS and Emergency Voice Alarm Communication System are the same thing.




Street Address:


1241 of 1374 6/30/2016 11:10 AM

City:

State:

Zip:

Submittal Date: Sat Jun 25 11:49:18 EDT 2016


1242 of 1374 6/30/2016 11:10 AM


A.24.3.8

The layers can be used in combination. In all cases, the system design needs to follow the risk analysis andbe integrated into the emergency operations and response plan. Research has shown that more than onelayer has been used to be effective. Multiple layers provide an extra level of notification (a safety net). Theoverall MNS application is likely to exploit a number of public and individual systems or components thatcombine to produce a reliable and robust solution to achieve emergency notification objectives.


(1) Emergency voice/alarm communications systems (EVACS)

(2) One-way voice communication systems (PA)

(3) Two-way voice communication systems

(4) Visible notification appliances

(5) Textual/digital signage/displays


(1) Wide-area outdoor mass notification systems (MNS)

(2) High power speaker arrays (HPSA)


(1) Short message service (SMS)

(2) Email

(3) Computer pop-ups

(4) Smartphone applications (Apps)

(5) Reverse 911/automated dialing


(1) Radio broadcast (satellite, AM/FM)

(2) Television broadcast (satellite, digital)

(3) Location specific messages/notifications

(4) Weather radios

(5) Social networks

Also see Optimizing Fire Alarm Notification for High Risk Groups research project.









1243 of 1374 6/30/2016 11:10 AM


Street Address:

City:

State:

Zip:



1244 of 1374 6/30/2016 11:10 AM


A.24.3.9

The design documents might include, but are not limited to, shop drawings, input/output matrix, batterycalculations, notification appliance voltage drop and wattage calculations for strobes and speakers textualaudible notification appliances , and product data sheets.



Also modified section as voltage drop calculations is used for horns and strobes while wattage calculations are required for audio systems. Yes, voltage comes into play for audio but many do not provide calculations for wattage and use the inverse square law and this causes many audio systems to not function as intended.




Street Address:

City:

State:

Zip:



1245 of 1374 6/30/2016 11:10 AM


A.24.3.10

A fire emergency voice/ alarm communications systems (EVACS) control unit that is listed in accordancewith ANSI/UL 864 or an emergency alarm system control unit listed to ANSI/UL 2017 can be used for MNSas long as the control unit has also been evaluated to ANSI/UL 2572 . The unique requirements in Chapter24 for mass notification systems are included in ANSI/UL2572. A control unit is permitted to providemultiple life safety services when evaluated to the respective requirements. A control unit only listed inaccordance with ANSI/UL 2572 or ANSI/UL 2017 cannot be used as a fire alarm control unit.


“fire alarm” was revised to “fire emergency voice/alarm communication system (EVACS)” because not all fire alarm control units have voice capability which is required for mass notification systems. The additional revisions are intended to clarify that control units can be evaluated to multiple standards such as such as ANSI/UL864 and ANSI/UL2017 to provide a combination of life safety signaling, and in order to provide mass notification services, the control unit must also be evaluated to ANSI/UL2572. ANSI/UL2572 includes unique requirements for mass notification systems which are derived from Chapter 24. Examples of unique requirements are: priority of signaling, overriding and relinquishing control of the fire alarm signaling, not overriding special notification releasing signaling, activating notification appliances that have completed the minimum number of required cycles once every 30 seconds. These requirements only reside in ANSI/UL2572. This revision will clarify any confusion for AHJs and customers.



Public Input No. 681-NFPA 72-2016 [Section No. 24.3.10] Annex material for 24.3.10


Submitter Full Name: Derek Mathews


Street Address:

City:

State:

Zip:



1246 of 1374 6/30/2016 11:10 AM


A.24.3.11.1

Although this chapter outlines some specific criteria and/or limitations, each application should be based onrecognized performance-based design practices and the emergency operations and response plandeveloped for the specific facility.

Here are the general categories of questions that might be presented to the senior manager responsible formass notification decisions. The actual questions for each project must be tailored to the area, the building,the campus, and the culture of the user organization. Following is a brief description of potential contentwithin the mass notification event questions:

(1) What is the type of emergency event — that is, is it fire, security, safety, health, environmental,geological, meteorological, utility service disruption, or another type of event?

(2) What is the urgency of the emergency event — that is, does it represent immediate danger, has italready occurred, is it expected to occur soon, is it expected to occur in the future, or is its occurrenceunknown?

(3) What is the anticipated or expected severity of the emergency event that is, how will it impact ourfacility and its functions, is it expected to be extreme, severe, etc.?

(4) What is the certainty of the emergency event that is, is it happening now, is it very likely to occur, is itlikely to occur, is it possible that it will occur in the future, is it unlikely to occur, or is its occurrenceunknown?

(5) What is the location of the event, or from what direction is the emergency event approaching — that is,has it or will it be approaching from the north, south, east, or west?

(6) What zone or areas should receive the emergency message(s) — that is, is it a floor of a building,multiple floors of a building, the entire building, multiple buildings, a campus of buildings, an entire townor city, an entire state, an entire region of states, or an entire country?

(7) What is the validity of the emergency event — that is, has the emergency event been investigatedand/or confirmed?

(8) What instructions should we send to our personnel — that is, should they evacuate the facility, shouldthey shelter-in-place, should they shelter-in-place at a special location, should they proceed to a safehaven area, and other action oriented items?

(9) Are there any special instructions, procedures, or special tasks that we need to remind personnelabout or to accomplish — that is, close your office door, open your office door, stay away fromwindows, do not use elevators, and other information relating to personnel actions?

The questions suggested in items (1) through (9) are offered for consideration, and not all of them might beappropriate for every mass notification system installation. It is important to remember that when anemergency event occurs, the response must be immediate and deliberate. Therefore, there is no time forindecision. So the questions selected to reside in the emergency messaging decision tree illustrated initems (1) through (9) must be straightforward and as simple as possible. They must also be tailored to thespecific organization, culture, site, and unique requirements of each local environment.








1247 of 1374 6/30/2016 11:10 AM



Street Address:

City:

State:

Zip:



1248 of 1374 6/30/2016 11:10 AM


A.24.3.13.3

This section is not meant to preclude a performance-based pathway survivability approach. As with mostperformance-based approaches, documentation should be provided by the designer and maintained withsystem documentation for the life of the system. Written documentation of the approval from the authorityhaving jurisdiction should also be maintained. A performance-based approach to pathway survivabilitycould be equivalent to, less stringent than, or more stringent than the prescriptive approach in 24.3.13.Often a performance-based approach will result from a risk analysis.

This section is also not meant to preclude less stringent pathway survivability requirements supported by arisk analysis for those unique occupancies that employ emergency voice alarm / emergency alarm communication systems for relocation or partial evacuation as part of their fire safety plan where relocationor partial evacuation could be readily superseded by total evacuation and where buildings are of a typeother than Type I or Type II (222) construction where the pathway survivability performance requirementdoes not need to be for two hours. Examples include low rise education and day care occupancies, nursinghomes, ambulatory health care occupancies, hotel and dormitory occupancies, and residential board andcare occupancies.


A Correlating Committee task group on language/terms reviewed the language of the Code for consistency and grammar. Editorial revision to align with same terminology references in the Code. Revise "voice alarm/emergency communication system" term to "emergency voice/alarm communication system"




Street Address:

City:

State:

Zip:



1249 of 1374 6/30/2016 11:10 AM

Public Input No. 670-NFPA 72-2016 [ Sections A.24.3.13.8.1, A.24.3.13.8.3 ]

Sections A.24.3.13.8.1, A.24.3.13.8.3

A.24.3.13.8.1

Extensive searches and discussions with cable manufacturers have not been able to identify a source oflisted 2-hour fire -rated coaxial or fiber cables. Listed fire-rated 75 ohm coaxial cables for security camerasexist but are not adaptable to distributed antenna systems operating at much higher radio frequencies.Coaxial cable with characteristics similar to low loss 50 ohm, 1⁄2 in. (13 mm) diameter, coaxial cables areavailable in plenum and riser ratings. Past installations have used these plenum and riser rated coaxialcables prior to this Code.

The fiber component of fiber-optic cables melts at temperatures well below the 1825°F (996°C) testspecification for listed 2-hour fire-rated cable.

Using 2-hour-rated cable enclosures throughout each floor of most structures is impractical, especiallywhen added to existing structures.

A.24.3.13.8.3

Examples of 2-hour fire -rated enclosures could include stairwells and elevator hoistways for firstresponders–use elevators.



Editorial correction. The intent is to be fire-rated. Add "fire" to the text.




Street Address:

City:

State:

Zip:



1250 of 1374 6/30/2016 11:10 AM


A.24.4.6.1

SpeakersTextual audible notification appliances located in the vicinity of the in-building fire emergency voice/alarmcommunications control equipment should be arranged so they do not cause audio feedback when thesystem microphone is used.

SpeakersTextual audible notification appliances installed in the area of two-way telephone stations should bearranged so that the sound pressure level emitted does not preclude the effective use of the two-waytelephone system. Circuits for

speakerstextual audible notification appliances and telephones should be separated, shielded, or otherwisearranged to prevent audio cross-talk between circuits.






Street Address:

City:

State:

Zip:



1251 of 1374 6/30/2016 11:10 AM


A.24.4.7.1

Special suppression systems that are delivered through a total flooding or localized application include, butare not limited to, carbon dioxide, clean agents, halons, and other extinguishing agents. Specialsuppression systems require audible and visible warning alarms to provide personnel the opportunity toevacuate or to alert personnel not to enter the area of discharge that could be hazardous to life. A specialsuppression system discharge can be a life-threatening hazard for personnel who are not notified and,therefore, fail to react to the pre-discharge alarm. In such cases, pre-discharge and discharge alarmsshould be independent of the fire alarm speakers textual audible notification appliances that are used aspart of the mass notification system. A special suppression system discharge could pose a greater threat topersonnel that are located in the protected area, or that could enter the protected area, if the local signalswere to be overridden and they did not receive the appropriate warning.






Street Address:

City:

State:

Zip:



1252 of 1374 6/30/2016 11:10 AM



1253 of 1374 6/30/2016 11:10 AM

A.24.4.8


1254 of 1374 6/30/2016 11:10 AM

When a fire or other emergency occurs in a building, the usual goal is to evacuate the occupants orrelocate them so that they are not exposed to hazardous conditions. The exception occurs in occupanciesusing stay-in-place/defend-in-place (SIP/DIP)[1] strategies. It might also be necessary to alert and provideinformation to trained staff responsible for assisting evacuation or relocation. Figure A.24.4.8 showsseveral key steps in a person’s reaction and decision-making process [2].

Occupants rarely panic in fire situations [3,4]. The behavior that they adopt is based on the information theyhave, the perceived threat, and the decisions they make. The entire decision path is full of thought anddecisions on the part of the occupant, all of which take time before leading to the development of adaptivebehavior. In hindsight, the actions of many occupants in real fires are sometimes less than optimal.However, their decisions might have been the best choices given the information they had. Fire alarmsystems that only use audible tones and/or flashing strobe lights visible notification appliances impart onlyone bit of information: fire alarm. It has long been recognized that environments having complex egresssituations or high hazard potentials require occupant notification systems that provide more than one bit ofinformation [5]. To reduce the response time of the occupants and to effect the desired behavior, themessage should contain several key elements [3,6].

Figure A.24.4.8 Key Steps in Person’s Reaction.

The key elements include the following:

(1) Tell occupants what has happened and where

(2) Tell occupants what they should do

(3) Tell occupants why they should do it

There does not seem to be any research that has tested actual message content to determine the best wayto inform occupants. The problem is that each building and each fire is unique. Messaging is furthercomplicated by the need to give different information to different people, depending on their location relativeto the fire, their training, and their physical/mental capabilities.

Messages should use positive language and avoid negative instructions that could be misinterpreted due tounintelligible communications. For example, if you want people to leave an area, say so: “A fire has beenreported in the area. For your safety, use the stairs to evacuate the area immediately.” A bad example is:“The signal tone you have just heard indicated a report of an emergency. If your floor evacuation signalsounds after this message, do not use the elevator, walk to the nearest stairway and leave the floor. Whilethe report is being verified, occupants on other floors should await further instructions.” This message is toolong, ambiguous, and subject to misunderstanding if not heard clearly. The word “not” might not be heardclearly, or it might be heard to apply to the entire remaining sentence. Similarly, care should be used inselecting and clearly enunciating words such as “fifth” and “sixth,” which can sound the same if the systemand environment lead to low intelligibility.

See A.24.3.6.1 for more information on methodology for improved message content, structure, and


1255 of 1374 6/30/2016 11:10 AM

intelligibility. Refer to Annex D for more information on speech intelligibility and how it is predicted.

Content of the message should be predicated on the building fire safety plan, the nature of the building andits occupants, the design of the fire alarm system, and testing of the occupant reaction to the message.Caution is advised that the fire alarm system operation and message actuation might be initiated by amanual pull station or detector remote from the fire.

[1] Schifiliti, R. P., “To Leave or Not to Leave — That is the Question!”, National Fire Protection Association,World Fire Safety Congress & Exposition, May 16, 2000, Denver, CO.

[2] Ramachandran, G., “Informative Fire Warning Systems,” Fire Technology, vol. 47, no. 1, February 1991,National Fire Protection Association, 66–81.

[3] J., Bryan, “Psychological Variables That May Affect Fire Alarm Design,” Fire Protection Engineering,Society of Fire Protection Engineers, Issue No. 11, Fall 2001.

[4] Proulx, G., “Cool Under Fire,” Fire Protection Engineering, Society of Fire Protection Engineers, IssueNo. 16, Fall 2002.

[5] General Services Administration, Proceedings of the Reconvened International Conference on FireSafety in High Rise Buildings, Washington, D.C., October 1971.

[6] Proulx, G., “Strategies for Ensuring Appropriate Occupant Response to Fire Alarm Signals,” NationalResearch Council of Canada, Ottawa, Ontario, Construction Technology Update, No. 43, 1–6, December2000.






Street Address:

City:

State:

Zip:



1256 of 1374 6/30/2016 11:10 AM


A.24.5.2.2

Authorized personnel could effect message initiation over the mass notification system from either a anemergency command center or a secondary (backup) control station(s). In cases where clusters of facilitieswithin the same geographical region exist, one or more regional control stations could effect messageinitiation. The mass notification system could permit activation of messages originated by mobile sentriesand roving patrols using wireless activation devices. Since it is common practice to allow mass notificationsystems to be utilized for “nonemergency” messages, the emergency command center should incorporatea clearly marked and easy to operate means to distinguish between emergency and non-emergency use.Comprehensive training and a fail-safe default to the emergency mode of operation should be employed toensure that no actual emergency message gets transmitted as a non-emergency broadcast.


Part of Task Group work assigned by CC. Editorial grammatical correction.



Organization: Tyco/SimplexGrinnell

Street Address:

City:

State:

Zip:

Submittal Date: Wed Mar 30 11:01:31 EDT 2016


1257 of 1374 6/30/2016 11:10 AM


A.24.5.2.2

Authorized personnel could effect initiate message initiation signaling over the mass notification systemfrom either a an emergency command center or a secondary (backup) control station(s). In cases whereclusters of facilities within the same geographical region exist, one or more regional control stations couldeffect initiate message initiation signaling . The mass notification system could permit activation ofmessages originated by mobile sentries and roving patrols using wireless activation devices. Since it iscommon practice to allow mass notification systems to be utilized for “nonemergency” messages, theemergency command center should incorporate a clearly marked and easy to operate means to distinguishbetween emergency and non-emergency use. Comprehensive training and a fail-safe default to theemergency mode of operation should be employed to ensure that no actual emergency message getstransmitted as a non-emergency nonemergency broadcast.



While the uses of "effect" are grammatically correct, recommend the attached revisions to simplify the text.

Revise "non-emergency" to eliminate hyphen to be consistent with other usages of the term in the Code. A hyphen is not recommended for words with ”non” prefix.




Street Address:

City:

State:

Zip:



1258 of 1374 6/30/2016 11:10 AM


A.24.5.4.1

Alternate methods that achieve the desired statistical availability could be deemed acceptable in lieu ofmonitoring the integrity of circuits, signaling channels, or communication pathways where consistent withthe risk analysis and emergency response plan.

An example of an alternate method could include Attenent Monitored Systems. An Attenent MonitoredSystem is defined in UL2017 - 2008 Standard for General Purpose Signalling Devices and Systems, insection 1.2 under the context of emergency signaling products that are associated with property and/or lifesafety and are of a non-fire/non-security alarm nature. The definition is as follows: "Type AM (Attendant-Monitored) devices or systems are intended to be constantly operated and maintained by competent andexperienced personnel, either locally or at a remote station". Attendant Monitored Systems that areconstantly operated, are an example of a system that could achieve a statistically significant availability tosatisfy the authority having jurisdiction. For example, ANSI/NEMA SB 40 2010, Communications Systemsfor Life Safety in Schools, references "Operational Integrity" in relation to systems that are used regularlyfor routine purposes, and suggest that such system would be statistically more available due to a lower riskof falling into a state of disrepair. SB 40 also addresses system readiness in relation to constant use, andrecommends that to the greatest extent possible, equipment used in Emergency Communication should beused daily in routine situations. Therefore, it is important to consider the level to which a system isconstantly operated, and the level of operator training, during the preparation of a risk analysis.. Based onthe occupancy of a premises, the risk analysis, and emergency response plan, the designer and AHJ mayconsider where it is appropriate for loudspeaker circuits to utilize this exemption.


Substation: 24.5.4 creates circumstances for an exemption, and the annex elaborates on the criteria for the exemption, but no examples are provided for context for this criteria. This addition to the annex seeks to provide additional clarity by providing an example of an alternate method, with justification, in context with the exemption, from other relevant ANSI standards already referenced in NFPA72 in relation to Mass Notification Systems (i.e., UL2572 and ANSI/NEMA SB 40).




Street Address:

City:

State:

Zip:



1259 of 1374 6/30/2016 11:10 AM


A.24.5.18.2

The requirement of 24.5.18.2 does not imply that multiple primary methods of visible appliances cannotexist in a common area. Both strobes and graphical or textual appliances are designated as primary wherethe authority having jurisdiction declares both to be required. When textual audible notification is required,consideration is warranted for high-noise areas and for a hearing - impaired person’s capability of clearlyreceiving 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 spaces whereintelligibility is impossible or impractical to provide. In designating a primary visual notification appliance, itis easy to assume that a strobe is sufficient and all other visual notification is automatically supplemental.

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 primary notificationappliance where intelligibly cannot be achieved or where consideration for lone individuals or groups ofindividuals with hearing impairments might prevent them from responding appropriately to emergencyinstructions.



The term “hearing impaired” is used multiple times in the standard with most occurrences not hyphenated. The usage in each occurrence is not confusing where a hyphen is needed to clarify the intent. Revise to eliminate the hyphen and align with the remainder of the usage in the Code.




Street Address:

City:

State:

Zip:



1260 of 1374 6/30/2016 11:10 AM

Public Input No. 231-NFPA 72-2016 [ Section No. A.24.6.5.1(B) ]

A.24.6.5.1(B)

Refer to Annex D for more information on speech intelligibility and how it is predicted.

Normal weather conditions should be specified as appropriate for the geographic location.

In outdoor areas, such as in industrial areas with many multi-story buildings, the maximum distance ofpersonnel from an outdoor speaker textual audible notification appliance often has to be significantlyreduced to retain acceptable intelligibility of the voice message. Speakers Textual audible notificationappliances that provide directional capability should be used. These can be mounted on building exteriorsif the speakers textual audible notification appliances do not radiate unacceptable levels of sound into thebuilding on which they are mounted.

At some sites, it could be necessary to control the amount of sound that propagates in undesirabledirections, such as into civilian communities adjacent to the site boundaries or into wildlife areas withprotected or endangered animal species. Additionally, in some areas, it might be necessary to mountwide-area mass notification speakers textual audible notification appliances on the side of a building whilesimultaneously preventing an unacceptable increase in that building’s interior noise levels.






Street Address:

City:

State:

Zip:



1261 of 1374 6/30/2016 11:10 AM


A.24.6.7.2

High power speaker arrays should be mounted not to exceed the OSHA and FEMA Publication CPG-17 foroccupational noise exposure limits or an absolute limit of 123 C-weighted decibels (dBC) as referenced inFEMA to anyone in the immediate vicinity of the speakers high power speaker arrays .


As part of the CC TG on terms, the term "Speaker" was reviewed throughout the entire document for proper use. In some cases it refers to a physical appliance while other sections use it to refer to a person. In this section the term is for an appliance and the proper term "Textual Audible Notification Appliance" should be used.In this case the term "speaker" should be modified to reference High Power Speaker Arrrays.




Street Address:

City:

State:

Zip:



1262 of 1374 6/30/2016 11:10 AM

Public Input No. 770-NFPA 72-2016 [ Section No. A.24.7 ]


1263 of 1374 6/30/2016 11:10 AM

A.24.7


1264 of 1374 6/30/2016 11:10 AM

Distributed recipient mass notification systems are enterprise-class systems for the management of, andmass distribution of, emergency notification messages within buildings, throughout installations, acrossentire geographical regions, or throughout a worldwide military command. Using distributed recipient massnotification systems, designated system operators would be able to rapidly and reliably inform appropriatepersonnel of homeland security levels (including chemical, biological, radiological, and nuclear threats;hazardous weather conditions; and many other critical events), possibly with near real-time responsecapability.

A distributed recipient mass notification system is meant to communicate to a wide range of targetedindividuals and groups. These systems might use mass dialing systems, including reverse 911, email, SMS,or other directed communications methods to broadcast information. They might also use wired or wirelessnetworks for one- or two-way communications and/or control between a building or area and an emergencyservices organization (information, command, and control).

Distributed Though classified as One-Way ECS, distributed recipient mass notification systems could becapable of centrally tracking, in real time, all alerting activities for each individual recipient, includingsending, receiving, and responding to alerts, and be able to generate reports based on tracked information.Distributed recipient mass notification systems could be able to provide ability to collect and report userresponses to alerts, such as "I am safe", "I need asisstance", "I am not in affected area".

Distributed recipient mass notification systems could incorporate a predefined library of signals andmessaging appropriate for, but not limited to, the following:

(1) Presidential alert message

(2) Homeland security levels

(3) Terrorism threats, watches, or warnings

(4) Evacuation routes

(5) Emergency directives

(6) Personnel recall requirements

(7) Federal, DOD, police, fire, or locally /installation-specific warning and notification requirements

(8) Amber alerts

The distributed recipient mass notification system could be capable of monitoring emergency notificationsfrom multiple data sources [Commercial Mobile Alert System (CMAS such as Wireless Emergency Alert(WEA ), National Weather Service, Emergency Managers Weather Information Network (EMWIN), NavalMeteorology and Oceanography (METOC), and others as determined locally] and automatically sending outnotifications to designated facilities and personnel based on predefined rules.

A mass notification system could also be capable of reaching out to all online personnel by leveraging ahighly secure, redundant, Web-based IP network architecture to manage the entire mass notificationprocess. Agencies and organizations can create role-based uses such as operators, administrators, andrecipients, based on their access rights across multiple facilities, campuses, and installations. System rulescould be established to determine operator permissions and actions such as creating and activatingscenarios, as well as the extent and geography of alerts and delivery systems and devices that should beused. Such a Web-based mass notification system would employ an open, standards-based architecture.The system could be integrated with existing user directories to support organizational hierarchy andemergency response groups. It could be structured to allow emergency criteria–based targeting ofemergency alerts.

Additionally, this annex material provides information on ongoing development of system requirements fornet-centric alerting systems (NCAS) that will be based on IP technologies. This annex is not mandatory, butis provided to stimulate development of suitable requirements and standards. Consequently, usersuggestions and feedback on this annex are highly encouraged and requested. Methods to ensurereliability and robustness in off-normal or emergency conditions are of particular concern. The requiredamount of and method for isolating alerting functions from normal, non-alerting system functions needsdevelopment.

NCAS leverage the IP network infrastructure to instantly reach those personnel who have access to nearlyany IP-connected devices [such as pop-up alerts on personal computers (PC), text messages to personaldata assistants (PDA) and cellular telephones, electronic mail to IP-capable cellular telephones messages ,and voice messages to voiceover-IP (VoIP) telephones and PCs]. Additionally, NCAS could be used toactivate, through a single user interface, other (IP based and non-IP based) alerting systems, such as


1265 of 1374 6/30/2016 11:10 AM

wide-area alerting systems and traditional dial-up telephone alerting systems.

NCAS can be installed independently or at a central location. In a centrally managed NCAS configuration,personnel and facilities in the regional operations center’s particular area of coverage could be alertedinstantly by events, either from any individual installation, or centrally from the regional operations center.Using management tools, designated operators from each installation in the region could log in via a webbrowser and have complete access to their own portion of the NCAS. The regional operations center wouldretain the ability to centrally monitor and manage all portions of the system, including supervisory andtrouble conditions of the different system components and integrated components.

The NCAS would incorporate a Web-based management and alert activation application through which alloperators and administrators could gain access to the system’s capabilities, based on the users’permissions and the defined access policy. Such a management application would incorporatemanagement of the alert activation flow through all delivery methods, as well as end-user management,operators’ permission and access, tracking and reporting, and all administrative aspects of the system.

Distributed recipient mass notification systems could interface and interoperate with other types of massnotification capabilities, including wide-area and in-building mass notification systems. During emergencies,systems operators should not need to send notifications using multiple alerting systems. The distributedrecipient mass notification system, particularly NCAS, might be able to provide the capability to integrateuser interfaces and consolidate access to multiple mass notification and alerting systems.


1. Clarification on capability to track and report progress and responses though DRMNS is classified as one-way ECS2. Update CMAS with WEA (name changed a few years ago)3. Update with current industry terms and capabilities.




Street Address:

City:

State:

Zip:



1266 of 1374 6/30/2016 11:10 AM


A.24.7.2

Distributed recipient mass notification systems could be capable of sending alert messages in a prioritizedmethod to target recipients according to the following:

(1) Hierarchical organizational structure (as would be imported from an active directory)

(2) Organizational roles

(3) Specific distribution lists [e.g., hazardous materials (HAZMAT) response teams]

(4) Specific distribution (e.g., hearing impaired or others with impairments that warrant prioritizednotification)

(5) Dynamic groups created through on-the-fly queries of the user directory

(6) Geographical locations (e.g., entire bases, zones within bases)

(7) IP addresses (required for targeting devices in specific physical locations)

Distributed recipient mass notification systems should provide mechanisms to update user and targetingdata; for example, user data import, integration with personnel directories, and self-user registration.

Distributed recipient mass notification systems could use a Web-based user interface, support locallydesignated standard network ports and protocols, and provide open interfaces to support interoperability,such as eXtensible markup language (XML) and common alerting protocol (CAP) based emergencymessages. (See OASIS Standard CAP-V1.2, OASIS Common Alerting Protocol version 1.2.)


Move the annex material in current 24.7.3 to annex 24.7.2 as it is more relevant in context: 24.7.2 is about targeting, while 24.7.3 is about network security.7



Public Input No. 769-NFPA 72-2016 [Section No. A.24.7.3]




Street Address:

City:

State:

Zip:



1267 of 1374 6/30/2016 11:10 AM


A.24.7.3

Distributed recipient mass notification systems should provide mechanisms to update user and targetingdata; for example, user data import, integration with personnel directories, and self-user registration.

Distributed recipient mass notification systems could use a Web-based user interface, support locallydesignated standard network ports and protocols, and provide open interfaces to support interoperability,such as eXtensible markup language (XML) and common alerting protocol (CAP) based emergencymessages. (See OASIS Standard CAP-V1.2, OASIS Common Alerting Protocol version 1.2.)

Here will come annex text re security requirements, compliance and certification.


1. Delete the text that was moved to annex 24.7.2 where it is more in context.2. Added plug for the modified security requirement.



Public Input No. 762-NFPA 72-2016 [Section No. A.24.7.2] Move annex text from A24.7.3 to A24.7.2




Street Address:

City:

State:

Zip:



1268 of 1374 6/30/2016 11:10 AM


A.24.7.5

Distributed recipient mass notification systems would be capable of sending alert messages to end-users(recipients) via multiple delivery methods, including the following:

(1) Audio-visual network alerts to desktops and laptops via desktop pop-up

(2) Text alerts to mobile phones and pagers

(3) Text alerts to electronic mail (e-mail) clients

(4) Text alerts to social networks

(5) Audio alerts to phones

(6) Audio alerts to existing wide-area or building voice and or mass notification systems

(7) Network alerts to any other IP-connected devices via standard XML and CAP protocols

The system could be extendable to support additional delivery methods in the future as this technologydevelops.


Keeping up with the industry, add social networks as means to distribute notifications.




Street Address:

City:

State:

Zip:



1269 of 1374 6/30/2016 11:10 AM


A.24.13

An emergency communications system information, command, and control is intended to include wired orwireless networks for one- or two-way communications and/or control between a building or area and anemergency command center and could include an emergency services organization or public alarmreporting system. In a very basic configuration, a system and the receiving facility could be a supervisingstation system. However, there can be more complex systems that allow control of building systems andcommunication communications to building occupants from a remote location, including a municipal orother public alarm reporting command center or possibly even from a mobile command vehicle usingsecure communications.


As part of the CC TG on terms, the term "communication(s)” was reviewed throughout the entire document for proper use regarding reference to singular and plural use. The term should be plural use in this context.




Street Address:

City:

State:

Zip:

Submittal Date: Fri Jun 24 12:01:41 EDT 2016


1270 of 1374 6/30/2016 11:10 AM


A.24.14

The risk analysis forms the basis for the emergency response plan.

Ensuring accurate information dissemination to the right people, at the right place, and at the right time isessential to the mitigation of threat actions and consequences. Trained personnel are charged with makingsuch decisions in real time. Quite often, the instructions provided to personnel in affected areas pertain toacting in specific defensive ways so as not to expose them to danger. A typical example is the case of achemical or biological agent attack wherein the right response is to relocate to secure areas within thebuilding while sealing doors and windows and shutting down air intakes, rather than to leave the buildingand be exposed to the attacking agent.

In cases of bomb threats, where specific information is available, directions for evacuation are to be given;these directions require more specificity than simply the instruction “Evacuate the building.” In most cases,the evacuation route might depend on threat intelligence and is likely to be different from that specified inan emergency response plan. Most people can tell where the fire comes from but do not always knowwhere the bomb is. Automatic evacuation of a building, a common procedure in cases of a fire, is to beavoided, since it might expose personnel to even greater danger.

One of the reasons for implementing a mass notification system is the threat of terrorism. Terrorism attackstend to be well organized and are often planned with details to inflict the widest degree of damage that ispossible. The mass notification system must be designed to withstand various attack scenarios and surviveeven if some damage has already occurred.

Each design of a mass notification system should be specific to the nature and anticipated risks of eachfacility for which it is designed. Although this chapter outlines some specific criteria and/or limitations, eachdesign should be based on recognized performance-based design practices.

The mass notification system should take into account various considerations, such as those indicated inthis chapter. The particular design might or might not incorporate these provisions.

Considerations for developing a mass notification system are as follows:

(1) Specific design for the facility

(2) Account for anticipated risks

(3) Use of live and/or prerecorded messaging

(4) Interfacing with other building emergency communications systems

(5) Interfacing with wide-area notification systems

(6) Ability to control the HVAC and access control systems

(7) Access to system components

(8) Survivability of the system

(9) Communication Communications link redundancy and security

(10) Redundancy and security of the emergency command center

(11) Ability to customize and add to prerecorded message library

(12) Messages should be tailored to the situation and audience

(13) Scripted messages for live voice messages

(14) Proper training of individuals that operate the system


As part of the CC TG on terms, the term "communication(s)” was reviewed throughout the entire document for proper use regarding reference to singular and plural use. The term should be plural use in this context.


1271 of 1374 6/30/2016 11:10 AM




Street Address:

City:

State:

Zip:

Submittal Date: Fri Jun 24 12:06:25 EDT 2016


1272 of 1374 6/30/2016 11:10 AM

agenda technical committee on emergency communication systems (sig-ecs) first draft ... ·...

Documents