Agenda Technical Committee on Protected Premises Fire ... › assets › files › AboutTheCodes › 72 › ...Services provided presentation: “Fire-Resistive, Fire-Resistant and

Agenda Technical Committee on

Protected Premises Fire Alarm and Signaling Systems (SIG-PRO) First Draft Meeting Salt Lake City, UT July 25 - 27, 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-0700 • www.nfpa.org

MEETING MINUTES

NFPA TECHNICAL COMMITTEE ON PROTECTED PREMISES FIRE ALARM SYSTEMS (SIG-PRO)

Second Draft Meeting, June 25-26, 2014

La Jolla Marriott, La Jolla, CA

Item No. Subject 14-6-1 Call to Order and Welcome (8:04 AM) Chair Merton Bunker called the meeting to order at 8:04 AM. 14-6-2 Approve Agenda Motion to approve the Agenda, seconded, and approved. 14-6-3 Approve Meeting Minutes from St. Louis, MO, Sept. 2013 Motion to approve the Minutes from 09-2013, seconded, and approved. 14-6-4 Introduction of Members Those present introduced themselves (see attached Attendance Sheet for all attendees, Principles, Alternates, and Guests). Guests that attended and / or participated during the committee meeting include:

Mr. Al Ramirez, Underwriters Laboratories, Inc. Mr. Bruce Fraser, Fraser Fire Protection, SIG ECS Mr. Mike Slack, Inovonics Dan Finnegan, Siemens Allan Sanedrin, Underwriters Laboratories, Inc. Richard Roux, NFPA Staff Liaison Michael Pallett, Telecor, Inc. Bob Schifiliti, TCC Chair Joe Collins, DFW Airport Glenn Sparks, Clark County Fire Department, Las Vegas Brian Woodward, Fire Safety Engineers

14-6-5 Staff Remarks & Presentations Mr. Lee Richardson (NFPA Staff) provided presentations on the following:

Participant Conduct Overview of the New Process

Mr. Al Ramirez, Underwriters Laboratories, Inc., Regional Manager Codes and Advisory Services provided presentation: “Fire-Resistive, Fire-Resistant and Circuit Integrity Cables – and Update from UL”. 14-6-6 Task Group Work – Review of Public Comments In order to maximize the time the committee had to review the various Public Comments, Mr. Merton Bunker, SIG PRO Committee Chair assigned task groups to review the Public Comments, provide a recommendation on acting on the Public Comments (i.e., Accept and Create Second Revision, Reject but See Related Second Revision, Reject, Reject but Hold), and present the recommendation to the Committee for discussion. Task Groups below are identified in the order that each group of Public Comments were addressed.

TG on Wiring, Circuits and Pathways: Chair: Capowski; Members: Girouard, Horon, Hayes, Woosley, Lawyer, VanKuren, LeBlanc, Transue, and Novak

TG on Zoning and Isolation: Chair: Belliveau; Members: Moore, Willms, Ballou, Crowley, Struck, Shudak, Ivers, Kessler, Olenick, Mann, and Poole (SIG-NAS)

TG on Control Functions: Chair: Leszcak; Members: Doliber, Doyle, Larrimer, Elvove, Lickfett, Carter, Capowski, Birchler, Hopple, and Hemke, Burkhart

TG on System Requirements and Editorial Issues: Chair: Hammerberg, Bisker, Weiss-Ishai, Barrett, Martorano, Ruland, DeVito, Humm, Kuhta, and Ranaudo, Harris

TG on ITM Correlation: Chair: Bisker; Members: Ruchala, Hopple, and Leszcak TG on FUN Correlation: Chair: Novak; Members: Kuhta and Humm TG on Documentation: Chair: Olenick; Members: Ballou and Martorano

In addition to processing of all Public Comments, the committee entertained discussions from the following Committee Members and guests on the following:

Mr. Michael Pallett, SIG-ECS. ECS committee proposed changes to 3.3.317.2 Notification Zone; 3.3.233 Relocation; and 23.6.2 (see PC 63). There may be unintentional consequences to changing the definition of Notification Zone. Committee voted against changes proposed.

o Task Group created – Capowski (Chair), Van Keuren, Shudak, Pallett (SIG-ECS)

Task Group assigned to review references to the NEC articles (see PC 235). Novak (Chair), Parrish (SIG-ECS).

Second Revision made to remove “Class N” from Section 12.3.8 to correct an error. Class N was added to this section during the First Revision inadvertently. The separation requirements do not apply to Class N circuits.

14-6-7 Processing Schedule Mr. Lee Richardson (NFPA Staff) provided dates for the NFPA 72 document cycle.

NFPA 72 (A2015) Meeting Dates

CC FD Meeting (Tampa*) 01-07-2014 though 01-09-2014 Posting of First Draft Report 03-07-2014 Comment Closing Date 05-16-2014 TC SD Meeting (LaJolla, CA) 06-23-2014 through 06-27-2014 CC SD Meeting (Indianapolis) 10-28-2014 through 10-29-2014 Posting of Second Draft Report 01-16-2015 NITMAM Closing Date 03-06-2015 Posting of CAMs 05-01-2015 Annual Meeting (Chicago) 06-22-2015 through 06-25-2015

14-6-8 Other Business Mr. Larry Shudak hosted a discussion on section 23.2.2.1.1. 23.2.2.1.1* Software and firmware within the fire alarm control system that interfaces to other required software or firmware shall be functionally compatible. 14-6-9 Adjournment Mr. Merton Bunker thanked the committee members for their hard work in reviewing and processing all the Public Comments that were presented to the group. A motion to adjourn was moved, seconded, voted on and approved. The meeting was adjourned. The meeting spanned 2 days, 06-25-2014 and 06-26-2014. Respectfully submitted, Leonard Belliveau, Jr. NFPA 72, SIG-PRO Secretary

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

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

Statement of Problem and Substantiation for Public Input

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 Information Verification

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

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

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


As applicable in the body of the code as well as any related annexes, all references to NFPA 70, TheNational Electrical Code, should be made to the entire document instead of a specific article unlesstechnically required.


Referencing a specific article in the NEC can lead to confusion and potential enforcement issues. For example many times only Article 760 is referenced leading some to believe that is the only part of the NEC that applies and not following or acknowledging the charging requirements established in Article 90-.


Submitter Full Name: Thomas Parrish

Organization: Telgian Corporation

Street Address:

City:

State:

Zip:

Submittal Date: Wed Jun 29 15:38:04 EDT 2016


38 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


The NFPA 72 Correlating Committee Task Group on Metric Values would like to submitthe following Global Input , Any place in the body of Chapter 23 or its annex that thevalue 3 feet Is used the metric equivalent shall be 0.9 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


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: Tue Jun 28 15:51:20 EDT 2016


21 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. 179-NFPA 72-2016 [ New Section after 3.3.34 ]

3.3.x Carbon Monoxide Detection System.

3.3.x.1 Carbon Monoxide Detection System. A system or portion of a combination system thatconsists of a control unit, components, and circuits arranged to monitor and annunciate the statusof carbon monoxide alarm initiating devices and to initiate the appropriate response to thosesignals.

3.3.x.2 Combination Carbon Monoxide Detection System. A carbon monoxide detectionsystem in which components are used, in whole or in part, in common with a non–carbonmonoxide signaling system, and in which components are not used as part of a fire alarm system.

3.3.x.3 Household Carbon Monoxide Detection System. A system of devices that uses acontrol unit to produce an alarm signal in the household for the purpose of notifying the occupantsof the presence of concentrations of carbon monoxide that could pose a life safety risk.


This is a product of the 72/720 consolidation task group


Submitter Full Name: Art Black

Organization: Carmel Fire Protection

Street Address:

City:

State:

Zip:

Submittal Date: Thu Apr 28 11:04:12 EDT 2016


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


3.3.34

Building System Information Unit (BSIU) A computer-based electronic device that is intended to displaybuilding information and execute system control functions including fire system information display andcontrol.


This PI will define the BSIU which will be detailed Chapter 23, with new PI’s Buildings 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:



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

Public Input No. 414-NFPA 72-2016 [ New Section after 3.3.66.4 ]

3.3.66.5 Cross-zoned Detection

A design concept used to reduce nuisance system activations. The concept requires that two means ofdetection be located within the spacing limitations of the respective detectors (see 23.8.5.4.3).


Reintroducing an old and commonly used term to explain the design concept. See proposed changes and Annex material for 23.8.5.4.3. This term is also referenced in NFPA 13 Handbook commentary under 7.3.2 in describing detection systems for pre-action.



Public Input No. 409-NFPA 72-2016 [Section No. 23.8.5.4.3] Definition and code section


Submitter Full Name: Scott Lacey

Organization: Lacey Fire Protection Engineer

Street Address:

City:

State:

Zip:



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


3.3.93 Ethernet (Class N). Ethernet is a method of transmi ng digital informa on between two or more

electronic devices based on a common digital communica ons protocol defined in IEEE 802.3 as the Ethernet

Frame.

3.3.93.1 Cabled Ethernet. Cabled Ethernet is an Ethernet deployment of physical cables, including copper wire

cables and fibre op c cables that support the transmission of data to mul ple diverse electronic devices.

3.3.93.2 Wireless Ethernet. Wireless Ethernet is a digital communica on method that does not u lize physical

media between transmission and receiving devices, where the transmission methods are based on both IEEE

802.3 and 802.11 standards.


Necessary definitions in support of Public Input for a New Chapter 15 that presents additional requirement for the design and deployment of a Ethernet specific Class N network.



Public Input No. 420-NFPA 72-2016[Chapter 15]

Definitions are related to Public Input for a new proposedChapter 15.


Submitter Full Name: Michael Pallett

Organization: Telecor Inc.

Street Address:

City:

State:

Zip:



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

Public Input No. 714-NFPA 72-2016 [ Section No. 3.3.103.4.1 ]

3.3.103.4.1 Building Fire Alarm System.

A protected premises fire alarm system that includes any of the features identified in 23.3.3.1 and thatserves the general fire alarm needs of a building or buildings and that provides fire department oroccupant notification or both . (SIG-PRO)


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

Revise definition as building fire alarm system does not always provide fire department or occupant notification or both. Paragraph 23.3.3.1 relates these functions are optional.


Submitter Full Name: Lawrence Shudak


Street Address:

City:

State:

Zip:



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


3.3.140 Life Safety Network.

A type of combination system that transmits fire emergency communication system safety control data todevices or systems throughout a building, multiple buildings, or through gateways to other building systemcontrol units or devices . (SIG-PRO)


The term "Network" in Life Safety Networks has taken on a broader context from the perspective of both MNS and Class N. Realigning the Life Safety Network with "emergency communication systems" broadens the definition to include systems that are not necessarily only concerned with fire safety. Also adding "devices" now aligns with Class N devices that may also be part of a Life Safety Network.



Public Input No. 420-NFPA 72-2016 [Chapter15]

A new proposed Chapter 15 also references Life SafetyNetwork




Street Address:

City:

State:

Zip:



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


3.3.232 Relocation.

The movement of occupants from a fire zone an area of hazard to a safe safer area within the samebuilding. (SIG-PRO)


The existing definition refers to fire specifically. With the expansion of NFPA 72 to cover mass notification the definition should be made less specific to fire.

This proposal was the work of the task group on zone definitions. Members were Michael Pallet, Larry Shudak, Wayne Moore, Jeff VanKeuren, Dan Finnegan, and A.J. Capowski


Submitter Full Name: Anthony Capowski

Organization: Tyco/SimplexGrinnell

Street Address:

City:

State:

Zip:

Submittal Date: Sat Apr 16 13:21:24 EDT 2016


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


3.3.x Response Plan.

The action to be taken in response to a carbon monoxide alarm signal.


This is a product of the 72/720 consolidation task group.


Submitter Full Name: Art Black

Organization: Carmel Fire Protection

Street Address:

City:

State:

Zip:

Submittal Date: Thu Apr 28 10:58:19 EDT 2016


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

Public Input No. 127-NFPA 72-2016 [ Section No. 3.3.317.1 ]

3.3.317.1 Notification Zone.

A discrete area of a building, bounded by building outer walls, fire or smoke compartment boundaries, floorseparations, or other fire safety subdivisions, in which occupants or defined area outside a building, inwhich people are intended to receive common notification. (SIG-PRO)


The current definition of notification zone includes requirements for the zone that are also given in section 23.8.6.3.2. This proposal eliminates the redundancy and it expands the definition to include areas outside the building. Areas outside the building are relevant due to the expansion of NFPA 72 to include mass notification.





Street Address:

City:

State:

Zip:



111 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




Street Address:

City:

State:

Zip:



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


12.3.8* Class A, N and Class X X Pathway Separation.

Class A, N and Class X X circuits using physical conductors (e.g., metallic, optical fiber) shall be installedso that the primary and redundant, or outgoing and return conductors, exiting from and returning to thecontrol unit, respectively, are routed separately.

12.3.8.1

The outgoing and return (redundant) circuit conductors shall be permitted in the same cable assembly (i.e.,multiconductor cable), enclosure, or raceway only under the following conditions:

(1) For a distance not to exceed 10 ft (3.0 m) where the outgoing and return conductors enter or exit theinitiating device, notification appliance, or control unit enclosures

(2) Single drops installed in the raceway to individual devices or appliances

(3)


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

Major portions of Class N Circuits include two or more pathways where primary and redundant paths are to be utilized to maintain operational capability similar in concept to Class A and X circuits. Pathway separation of physical conductors needs to be implemented to reduce the likely hood of a single event affecting both paths. Revise 12.3.8 to extend pathway separation requirements to the redundant portions of Class N circuits.




Street Address:

City:

State:

Zip:


* In a single room not exceeding 1000 ft2 (93 m2) in area, a drop installed in the raceway to multipledevices or appliances that does not include any emergency control function devices


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

Public Input No. 394-NFPA 72-2016 [ Section No. 12.4 ]

12.4* Pathway Survivability.

All pathways shall comply with NFPA 70.

12.4.1 Pathway Survivability Level 0.

Level 0 pathways shall not be required to have any provisions for pathway survivability.


Pathway survivability Level 1 shall consist of pathways in buildings that are fully protected by an automaticsprinkler system in accordance with NFPA 13 with any interconnecting conductors, cables, or other physicalpathways installed in metal raceways.

12.4.3* Pathway Survivability Level 2.

Pathway survivability Level 2 shall consist of one or more of the following:

(1) 2-hour fire-rated circuit integrity (CI) or fire-resistive cable

(2) 2-hour fire-rated cable system [electrical circuit protective system(s)]

(3) 2-hour fire-rated enclosure or protected area

(4)


Pathway survivability Level 3 shall consist of pathways in buildings that are fully protected by an automaticsprinkler system in accordance with NFPA 13 and one or more of the following:

(1) 2-hour fire-rated circuit integrity (CI) or fire-resistive cable

(2) 2-hour fire-rated cable system [electrical circuit protective system(s)]

(3) 2-hour fire-rated enclosure or protected area

(4)


There are cases and have always been cases where the requirement of 2-hour circuit protection is not possible to achieve without changing the otherwise rated construction required by the building codes. Examples, which have been brought to the attention of the committees in the past, include area of refuge communications and fireman phones that are located within an elevator lobby or area of refuge space. The listing of CI cable and the like are limited to the cable, not the 4-square junction box with an RCA jack and wall plate, or the plastic intercom or phone set. As such, the 2-hour circuit protection is lost at every such point. Thus, it is not feasible to maintain a 2-hour circuit unless you build a 2-hour rating around the jack or device. i.e. The building code would require a 1-hour level of protection. In order to comply with NFPA 72 every elevator lobby, area of refuge, or such would be required to be upgraded to a 2-hour enclosure. Such extensive rating and cost impact should not be dictated by a fire alarm code. Instead, the fire alarm code should take into account traditional fire rated construction practices used for decades and recognize protective features within its own code such as Class X. Option (4) allows performance-based alternatives. However, when we know that a system does not work in many cases as outlined in A.12.4.3(4), why should each designer and installer have to prepare performance alternatives. The proposed change allows the code to work as it should without the added time and expense of preparing alternatives already

* Performance alternatives approved by the authority having jurisdiction

* Performance alternatives approved by the authority having jurisdiction

12.4.5 Pathway Continuity. Where a 2-hour level of circuit protection is otherwise required and it is notpossible to maintain a compete 2-hour level of protection due to the limitations of listed components, suchas a junction box or communication device located within a 1-hour rated elevator lobby, the provisions of12.4.5.1 shall be permitted.

12.4.5.1 Level 1 shall be permitted where there are at least two pathways that are separated by at leastone-third the maximum diagonal of the area or floor the circuit is passing through and the pathway is ClassX or Class N.


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

suggested by the Annex.




Street Address:

City:

State:

Zip:



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



Pathway survivability Level 1 shall consist of pathways in buildings that are fully protected by an automaticsprinkler system in accordance with NFPA 13 with any interconnecting conductors, cables, or other physicalpathways installed in metal raceways or metal covered cables .


Metal Clad Cable Type MC provides mechanical protection to the insulated conductors, removes the insulated conductors from direct impingement of the flame from a fire, is required to comply with the flame spread requirements of the UL 1685 70,000 BTU Vertical Tray Flame Test and, optionally complies with the Canadian FT 4 Vertical Flame Test and the UL 1666 Test for Flame Propagation Height of Electrical and Optical Fiber cables Installed Vertically in Shafts. The cable is permitted by NFPA 90A (HVAC Code) and by NFPA 70 (NEC) for wiring in plenum spaces .Permitting MC cables in Pathway Survivability Level 1 in buildings protected by automatic sprinklers provides an acceptable alternative wiring method for providing mechanical and fire protection for the pathway.


Submitter Full Name: George Straniero

Organization: AFC Cable Systems, Inc.

Street Address:

City:

State:

Zip:

Submittal Date: Mon Jun 27 15:37:06 EDT 2016


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

Public Input No. 420-NFPA 72-2016 [ Chapter 15 ]


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

15. Class N Ethernet Deployments

15.1. Applica on

15.1.1. The applica on, design, installa on, and performance of a Class N Ethernet deployment shall conform

with the requirements of this chapter.

15.1.2. The requirements of Chapter

15 Reserved7, 10, 12, 17, 18, 21, 23, and 24 shall apply unless otherwise noted in this chapter.

15.1.3. The requirements of this chapter shall not apply to chapter 26, 27, and 29 unless specifically indicated.

15.1.4. All Class N Ethernet life safety network deployments shall conform with the requirements of sec on

12.3.6, and 23.6.2 through 23.6.3.

15.1.5. The requirements of this chapter apply to Class N life safety cabled Ethernet network deployments.

15.1.6. The requirements of sec ons 15.4 and 15.5 do not apply to Class N wireless Ethernet deployments.

15.1.6.1. Class N life safety wireless Ethernet deployment shall meet the requirements of 23.16 and 24.6.

15.2. Risk Analysis

15.2.1. Each applica on of a Class N Ethernet deployment shall be specific to the nature and an cipated risks of

each facility for which it is designed.

15.2.2. The designer shall consider both fire and non‐fire emergencies when determining risk tolerances for the

survivability of the network, and the systems and devices it serves.

15.2.3. The detail and complexity of the risk analysis shall be commensurate with the complexity of the facility

for which the network is to be installed.

15.2.4. The risk analysis shall be permi ed to be limited in scope to address the requirements of an exis ng

emergency response plan.

15.2.5. The risk analysis shall consider characteris cs of the buildings, areas, spaces, campuses or regions,

equipment, and opera ons that are not inherent in the design specifica ons.

15.2.6. Those elements that are not inherent in the design specifica ons, but that affect occupant behavior or

the rate of hazard development, shall be explicitly iden fied and included in the risk analysis.

15.2.7. The risk analysis shall consider the following types of poten al events, which are not all‐inclusive but

reflect the general categories that shall be considered in the risk analysis:

(1) Natural hazards — Geological events

(2) Natural hazards — Meteorological events

(3) Human caused —Accidental events

(4) Human caused — Inten onal events

(5) Technological — Caused events

15.3. Equipment Rooms

15.3.1. The requirements of 15.3.2 thru 15.3.5 shall apply to all equipment rooms, equipment closets,

telecommunica on rooms, and telecommunica on enclosures, or the like, for which Class N Ethernet life safety

network infrastructure equipment resides.

15.3.2. Equipment rooms or enclosures shall be permi ed to contain both Class N life safety networking cable,

equipment, and associated infrastructure provided the deployment sa sfies 15.3.2.1.

15.3.2.1. Class N life safety Ethernet network cabling, equipment, and infrastructure shall be clearly segregated

and iden fied as "Fire Network", “Emergency Communica ons Network”, “Life Safety Network”, and/or "MNS

Network" as applicable.¬

15.3.2.2. Life safety Class N Ethernet networks cabling, equipment and infrastructure, includes but is not limited

to Ethernet switches, media converters, uninterruptable power supplies, separate life safety network dedicated

branch circuit power, cabling cross connects, and both copper and fiber cabling.

15.3.3. Equipment rooms shall be ven lated or condi oned to maintain an opera ng environment that meets or

exceeds all life safety network related equipment requirements.

15.3.4. Equipment rooms or enclosures shall be accessible to only authorized personnel via a locked access or

via an enclosure requiring the use of tools to open, as acceptable to the AHJ.

15.3.5. All equipment shall be installed as required by sec on 10.4

15.4. Class N Ethernet Cable Installa on

15.4.1. Class N Ethernet cable Installa on shall follow the requirements of recognized standards such as

TIA/EIA‐568 or ISO/IEC 11801, or other standards acceptable to the authority having jurisdic on.

15.4.2. No termina on of a Class N network shall be available to building occupants without first requiring

accessing via a locked enclosure or an enclosure requiring tools to open, as acceptable to the AHJ.

15.4.2.1 Excep on: Ethernet connec ons to computers, that not intended for, and not readily accessible in an

unsupervised environment to the general public, where disconnec on does not inhibit life safety network func ons

beyond that of the computer itself, and where the computer is a required aspect of the life safety network design,

based on the risk analysis, with the approval of the AHJ.


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

15.4.3. Cable installa ons shall be tested with appropriate field test measurement equipment in accordance

with applicable standards such as TIA 526, ISO/IEC14763, or other standards acceptable to the authority having

jurisdic on.

15.4.3.1. Tes ng requirements for balanced twisted‐pair cabling shall include:

(1) Wire map (e.g., con nuity, pairing)

(2) Length

(3) Inser on loss

(4) NEXT loss

(5) ACR‐F (formerly called ELFEXT)

(6) Propaga on delay and delay skew

(7) Return loss

(8) Power sum near‐end crosstalk (PSNEXT) loss

(9) PSACR‐F (formerly called PSELFEXT)

15.4.3.2. Tes ng requirements for op cal fiber cabling shall include:

(1) A enua on

(2) Op cal Bandwidth

(3) Length

(4) Polarity

15.4.4. Documentary evidence of tes ng results and clear pass/fail status for each segment of cabling u lized in

the Class N network shall be provide in accordance with Chapter 7.

15.5. Power over Ethernet (PoE)

15.5.1. Equipment providing or u lizing PoE shall meet the requirements of IEEE 802.3af or IEEE802.3at, in

addi on to other sec ons as required by this code.

15.5.2. All equipment providing PoE capabili es shall meet the requirement of sec on 10.6

15.5.3. PoE cabling deployments shall conform to all local codes, and be approved by the AHJ for both the

deployment and the applica on.

15.6. Class N Network Documenta on

15.6.1. Class N Network design and deployment shall be documented in accordance with Chapter 7 and

applicable standards such as TIA 606, ISO/ICE 14763, or other standards acceptable to the authority having

jurisdic on.

15.7. Class N Life Safety Ethernet Network Deployment Shared Pathways. Class N Ethernet pathways shall be

required to use shared pathway Level 3 as specified in 12.5.4 except as permi ed by 15.8.

15.8. Shared pathways Levels 1 and 2 shall be permi ed subject to a thorough wri en analysis of the risks,

deployment, change control, and maintenance plans, roles and responsibili es, and other risks as required in 15.10

through 15.15 and when approved by an AHJ.

15.8.1. Class N Ethernet life safety networks u lizing Shared Pathway Class 3 shall not be required to meet the

requirements of sec ons 15.10 through 15.16.

15.9. Accessibility. Class N life safety network pathways shall not be accessible to the general public for any

purpose or building occupants for any purpose other than specified in the analysis, maintenance, and deployment

plans.

15.10. Deployment Plan.

15.10.1. All equipment connected to shared pathways shall be documented in the deployment plan.

15.10.1.1. The documenta on shall include manufacturer, model, lis ngs, and intended purpose and reason for

inclusion on the shared network.

15.10.1.2. The deployment plan shall iden fy how and where each piece of equipment is connected.

15.10.2. All connec on ports, used or spare, where any unauthorized or unintended equipment may be added

to the shared network, shall be iden fied as for use only by equipment consistent with the deployment plan.

15.11. Change Control Plan. Configura on upgrades and updates shall be governed by a change control plan,

which determines the policy and procedure of the change and ensures that all documenta on is correspondingly

updated.

15.12. Management Organiza on.

15.12.1. An organiza on shall be established and maintained to manage the life safety network and shall

perform the following tasks:

(1) Contain members appropriately cer fied by each manufacturer of the equipment and devices deployed on

shared pathways to maintain such a network

(2) Service and maintain all shared Class N pathways

(3) Maintain the deployment and shared pathways plan for the life me of the shared pathways

15.12.2. Other service personnel, even when cer fied to service a specific system (i.e., fire alarm or MNS) shall

be authorized and managed by this organiza on to ensure any outages of any system are planned, managed, and


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

documented and appropriate steps are taken during outages to provide alternate protec on of life and property.

15.13. Analysis.

15.13.1. An analysis shall be performed to determine and document communica ons capability as follows:

(1) Calcula on of minimum required bandwidth such that all life safety systems can be guaranteed to operate

simultaneously and within required me limits

(2) Total bandwidth provided by the network

(3) Future bandwidth requirements

(4) Method of providing and maintaining the priori za on of life safety traffic over non–life safety traffic

15.13.2. The analysis shall determine and document the power distribu on capability as follows:

(1) The methods provided to maintain power to all shared pathway equipment

(2) A calcula on of power requirements of all connected equipment

(3) Secondary power capaci es provided to maintain all life safety equipment with minimum opera onal capacity in

accordance with 10.6.7.2.1.2

(4) Methods to disengage any non–life safety equipment in the event of emergency opera on if required to support

the minimum opera onal capacity requirements

15.14. Maintenance Plan.

15.14.1. The maintenance plan shall iden fy policy and procedures to monitor, maintain, test, and control

change of the shared pathways.

15.14.2. Wri en procedures shall be presented in maintenance plans to govern the following:

(1) Physical access to all parts of the Class N network equipment (i.e., switches, ports, server, controllers, devices, or

components)

(2) Electronic access to all parts of the Class N network (i.e., passwords, addresses)

(3)*Service outage impairment process with no ces of impairment and con ngency plans for affected systems

(4) Upgrade procedures

(5) Change control procedures, with considera on given to require an updated risk analysis if necessary

(6) Priori za on and/or segrega on configura on informa on for life safety traffic

(7) Maintenance and tes ng plans to ensure the minimum opera onal capacity with respect to secondary power is

maintained

(8) Other service, maintenance, or reconfigura on plans for any connected equipment

15.15. Other Risks. Any other iden fiable risk as required by the AHJ shall be discussed and addressed in the

analysis and maintenance plans.


Ethernet is an ubiquitous technology installed in almost every commercial building being designed today. Class N was introduced in 2016 edition, with an intention to create opportunities for developing Ethernet based technologies for Emergency Communication Systems; including the potential for Ethernet deployment of initiating devices and notification appliances. Yet, Class N is not necessarily Ethernet. Class N is a collection of performance criteria that could be achieved without necessarily utilizing Ethernet. However, it is impossible not to be aware of how thoroughly Ethernet and the technologies that utilize it have impacted almost all areas of modern life. Similar to telephone and television, Ethernet as a collection of technologies is global, and continues to proliferate; due primarily to the standard based approach to its design and deployment. Chapter 15 seeks to recognize the ongoing importance of Ethernet in delivering information, including all types of communication (visual, textual, & audible), and collecting real time information from sensors and people, and based on this information, providing system control from virtually anywhere. We may predict with confidence that Emergency Communication Systems technology will progress in all these areas. It is therefore reasonable to predict, with the introduction of Class N, Ethernet networks will play more prominent roles as a Life Safety Network. As such, Chapter 15 is intended to represent a place in this code where conditions of satisfaction for Life Safety Networks that are specific to Ethernet may be presented. There are other standards groups that have already collected a great deal of best practice information relating to the design and implementation of Ethernet networks, but they are not currently accounted for by this document, and are not recognized as requirements. And there may be instances where other standards do not go far enough to ensure the reliability of the Life Safety Network for Emergency Communication uses. Chapter 15 seeks to establish a framework to address this important area of technological progress for Emergency Communications Systems.



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


Public Input No. 410-NFPA 72-2016 [Section No. 3.3.140]

Public Input No. 418-NFPA 72-2016 [New Section after 3.3.92]

Public Input No. 425-NFPA 72-2016 [Sections 23.6.3.1, 23.6.3.2, 23.6.3.3, 23.6.3.4,23.6.3.5, ...]




Street Address:

City:

State:

Zip:



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


21.1.1

The requirements of Chapters 7 , 10 , 17 , 18 , 23 , 24 , and 26 shall apply, unless otherwise notedin this chapter.





Public Input No. 722-NFPA 72-2016 [New Section after 1.3.4] would relocate these requirements to ch 1




Street Address:

City:

State:

Zip:



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


21.2.4*

Emergency Unless failsafe operation is selected, emergency control function interface devices shall belocated within 3 ft (1 m) of the component controlling the emergency control function.


This change is proposed to reduce misinterpretations that all control function interface devices must be within 3 ft of the component controlling the emergency control function. That is not required for fail safe operation.


Submitter Full Name: Thomas Hammerberg

Organization: Automatic Fire Alarm Association

Affilliation: Automatic Fire Alarm Association

Street Address:

City:

State:

Zip:



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


21.2.4*

Emergency control function interface devices shall be located within 3 ft (1 m 0.9 m ) of the componentcontrolling the emergency control function.


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. This will match the text in the corresponding annex section.


Submitter FullName:

Thomas Parrish



Street Address:

City:

State:

Zip:



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



New Section following 21.2.6

X.X.X* Where a signaling line circuit or a control circuit is utilized to activate emergency controlfunctions, the system designer shall consider the impact of a single open or short that could disable multipleor all emergency control functions within the protected premises.

A.X.X.X The system designer should understand and consider the impact of permittinga single open or short control circuit fault to disable the activation of multiple emergency control functions.Where a failure of the fire alarm SLC or other circuit between the fire alarm system and the emergencycontrol function interface device could pose an increased risk to the occupants of a protected premise, thedesigner should consider potential methods of redundancy, survivability, and protection of the SLC or othercircuits controlling the emergency control function interface devices.


The potential that a single pathway open or short circuit fault could disable critical life safety emergency control functions or numerous emergency control functions should be considered by the system designer. There are numerous ways to enhance the reliability and capability of theses circuits to function under a single short or open fault condition. The IBC, for example, requires that smoke control systems and the associated detection and control circuits be installed in continuous raceways to provide an additional level of reliability for the system. In addition to the physical protection other methods that should be considered include but are not limited to class A configurations and SLC circuits designed in accordance with section 23.6. The proposed new section, although not requiring that the circuits be designed to survive a single open or short to maintain operational capability, at a minimum requires consideration by the system designer.


Submitter Full Name: Carl Willms

Organization: Fire Safety Consultants, Inc.

Street Address:

City:

State:

Zip:



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


21.2.11

If a fire alarm system is a component of a life safety network and it communicates data to other systemsproviding life safety functions, or it receives data from such systems, the following shall apply:

(1) The path used for communicating data shall be monitored for integrity. This shall include monitoringthe physical communication communications media and the ability to maintain intelligiblecommunications.

(2) Data received from the network shall not affect the operation of the fire alarm system in any way otherthan to display the status of life safety network components.

(3) Where non-fire alarm systems are interconnected to the fire alarm system using a network or otherdigital communication communications technique, a signal (e.g., heartbeat, poll, ping, query) shall begenerated between the fire alarm system and the non-fire alarm system. Failure of the fire alarmsystem to receive confirmation of the transmission shall cause a trouble signal to indicate within200 seconds.


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.


Submitter Full Name: Rodger Reiswig

Organization: Tyco SimplexGrinnell

Street Address:

City:

State:

Zip:

Submittal Date: Fri Jun 24 11:15:08 EDT 2016


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


21.3.2*

In facilities without a required building fire alarm system, fire alarm initiating devices used to initiate elevatorPhase 1 I Emergency Recall Operation shall be connected to either a nonrequired building fire alarmsystem or a dedicated function fire alarm control unit that shall be designated as “elevator recall control andsupervisory control unit,” permanently identified on the dedicated function fire alarm control unit and on therecord drawings.


the number "1" included in the term "Phase 1" should be changed to "I" to be consistent with this term throughout Section 21.3


Submitter Full Name: Sagiv Weiss-Ishai

Organization: San Francisco Fire Department

Affilliation: SFFD

Street Address:

City:

State:

Zip:

Submittal Date: Sat Jun 04 22:46:23 EDT 2016


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


21.3.2*

In facilities without a required building fire alarm system, fire alarm initiating devices used to initiate elevatorPhase 1 I Emergency Recall Operation shall be connected to either a nonrequired building fire alarmsystem or a dedicated function fire alarm control unit that shall be designated as “elevator recall control andsupervisory control unit,” permanently identified on the dedicated function fire alarm control unit and on therecord drawings.


A Correlating Committee task group on language/terms reviewed the language of the Code for consistency and grammar. The term “Phase I” is used 13 times in the Code, including in the heading of this section, while “Phase 1” is used twice. Recommend revising “phase 1” to “phase I” for consistency within the Code.




Street Address:

City:

State:

Zip:



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


21.3.3

Unless otherwise required by the authority having jurisdiction, only the elevator lobby, elevator hoistway,elevator machine room, elevator machinery space, elevator control room, and elevator control spacesmoke detectors or other automatic fire detection as permitted by 21.3.9 shall be used to initiate elevatorPhase I Emergency Recall Operation.

Exception: A waterflow switch shall be permitted to initiate elevator Phase I Emergency Recall Operationupon activation of a sprinkler installed at the bottom of the elevator hoistway (the elevator pit), providedthe waterflow switch and pit sprinkler are installed on a separately valved sprinkler line dedicated solelyfor protecting the elevator pit, and the waterflow switch is provided without time-delay capability.


Add the location "Machinery Space" to this list to be consistent with Section 21.3.11 and with ASME A17.1 Delete the exception since the elevator pit is a part of the elevator hoistway which is already listed in this section. Therefore, the pit should not be separately indicated in the body of the code (it should be moved to the annex as a specific location in the hoistway)Also, waterflow switches without time delay are known to cause unwanted alarms and recall the elevators upon water pressure changes in the sprinkler piping.




Affilliation: SFFD

Street Address:

City:

State:

Zip:



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


21.3.4

Each fire alarm initiating device used to initiate Phase I Emergency Recall Operation shall be capable ofinitiating elevator recall when all other devices on the same initiating device circuit have been manually orautomatically placed in the alarm condition.


the term initiating device is changed to read "fire alarm initiating device" to be consistent with other sections in 21.3




Affilliation: SFFD

Street Address:

City:

State:

Zip:



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


21.3.5*

A lobby smoke detector or other automatic fire detectors as permitted by 21.3.9 shall be located on theceiling within 21 ft (6.4 m) of the centerline of each elevator door within the elevator bank under control ofthe detector.

Exception: For lobby ceiling configurations exceeding 15 ft (4.6 m) in height or that are other than flat andsmooth, detector locations shall be determined in accordance with Chapter 17.


Not only smoke detectors are permitted to generate Phase I emergency recall operations. If other automatic smoke detectors are used, as permitted in section 21.3.9, they should follow this rule as well.







Affilliation: SFFD

Street Address:

City:

State:

Zip:



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


21.3.7 Fire Alarm Initiating Device(s) Inside Elevator’s Hoistway.

Fire alarm initiating device(s) required to be installed inside an elevator’s hoistway by other sections of this code or byother codes and standards shall

be required to be accessible for service, testing, and maintenance from outside the elevator’s hoistway.

Additional Proposed Changes

File Name Description Approved

FR_138.pdfFR 138 from last code cycle - SIG-PRO TC supports this proposal

Service_Outside_hoistway._CA.pdfThis is the CA state Elevator Code requirement for FAIDs access from outside the hoistway

A17_Hoistway_Committee_Record_13-1901.docxA copy of ASME A17.1 Record 13-1901 allowing FAIDs access from outside the hoistway


This proposal was submitted during the last code cycle and passed the first draft meeting FR-138.Due to concerns of potential conflicts with other building and/or elevator codes this proposal failed during the SR meeting.Since then, work was done by Bruce Fraser on the A17.1 hoistway committee to allow FAIDs to be accessed from outside the hoistway - either by access doors or by using air aspirating smoke detection located outside the hoistway. This proposal was approved by the A17.1 Hoistway committee on their June 2016 meeting - Record 13-1901 (see attached)Therefore, the potential conflicts are removed and this requirement for FAIDs access can be included in NFPA 72 with a reference to the A17.1 specific provisions.

This will also comply with NFPA 72 definition 3.3.4 for accessible spaces as applied to detection coverage:

3.3.4 Accessible Spaces (as applied to detection coverage in Chapter 17). Spaces or concealed areas of construction that can be entered via openable panels, doors hatches, or otherreadily movable elements (e.g., ceiling tiles). (SIG-IDS)



Public Input No. 292-NFPA 72-2016 [Section No. 21.3.7] FAIDs in sprinklered hoistways

Public Input No. 291-NFPA 72-2016 [Section No. 21.3.7] FAIDs in sprinklerd hoistways




Affilliation: SFFD

Street Address:

City:

State:


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

Zip:

Submittal Date: Thu Jun 16 10:07:29 EDT 2016


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

First Revision No. 138-NFPA 72-2013 [ New Section after 21.3.4 ]

21.3.5 Fire Alarm Initiating Device(s) Inside Elevator's Hoistway.

Fire alarm initiating device(s) required to be installed inside an elevator's hoistway by other sections of this Code or by other codes and standards shall be required to be accessible for repair, service, testing, and maintenance from outside the elevator's hoistway.


Submitter Full Name: [ Not Specified ]

Organization: [ Not Specified ]

Street Address:

City:

State:

Zip:

Submittal Date: Tue Sep 10 15:15:21 EDT 2013

Committee Statement

Committee Statement:

In California, the Elevator Safety Order has a requirement that all hoistway FAIDs must be accessible from outside the hoistway. However, this requirement only applies in the State of California but it is not a national code requirement. This will significantly reduce the life-safety risk for FA installers and service personnel, and cost to owners due to the great deal of required coordination

Response Message:


Ballot Results

This item has passed ballot

29 Eligible Voters

3 Not Returned

22 Affirmative All

2 Affirmative with Comments

2 Negative with Comments

0 Abstention

Not Returned

Ballou, Brian

Burkhart, David J.

Ruland, Scott F.

Affirmative All

Barrett, Scott

Bisker, James G.

Bunker, Jr., Merton W.

Capowski, Anthony J.

Crowley, Paul F.

Dix, Keith W.

Doliber, Diane P.

Doyle, Laura E.

Harris, Scott D.

Hayes, Mark D.

Hopple, William K.

Horon, Daniel J.

Humm, Vic

Kuhta, Thomas E.

LeBlanc, David J.

Martorano, Scott T.

Olenick, John R.

Ruchala, Kurt A.

Shudak, Lawrence J.

Struck, Donald

Weiss-Ishai, Sagiv

Willms, Carl F.

Affirmative with Comment

Hammerberg, Thomas P.

I don't necessarily agree with the "repair" part of this requirement. What if you install an air sampling system and the piping is in the hoist way and gets damaged and needs repair? You can't have that accessible from outside the hoist way.

Novak, Jebediah J.

A 2006 report produced by the Center to Protect Worker's Rights analyzed the activities and causes of death and injuries to employees engaged in work on elevators. The report found that the fatality rate for employees engaged in installation, repair, and maintenance activities is higher than average for construction. This safety-driven change will prevent employees from being exposed to the hazards present in the shaft while performing maintenance activities.

Negative with Comment

Belliveau, Jr., Leonard

This is a building code issue. Content of section is Questionable with regard to value added and cost to complete.

Leszczak, Peter

Providing access to reach an initiating device is potentially very expensive and difficult to enforce. If anything, this is an ASME A17.1 elevator code requirement and not something for NFPA 72 to delve into.

Page 1 of 1National Fire Protection Association Report

2/5/2015http://submittals.nfpa.org/TerraViewWeb/FormLaunch?id=/TerraView/Content/72-2013.dit...

A17 Hoistway Committee

Record 13‐1901

2.8.2.4 In jurisdictions enforcing the NBCC and in jurisdictions enforcing NFPA 72, the means for testing

and maintenance of fire alarm initiating devices without having to enter the hoistway shall be

permitted. When this means is provided it shall comply with either (a) or (b): (a) The means provided by piping used for air sampling shall comply with 2.8.3.1.4.

(b) The means provided by enclosing a fire alarm initiating device within a protective space shall

comply with (1) through (7):

(1) Hoistway penetrations for access panels utilized for the installation, testing and servicing

of fire alarm initiating devices shall comply with 2.1.1.1.3.

(2) Access panels shall be rated and listed for the application for which they are installed and

shall have a maximum width of 400mm (16in.) and maximum height of 400mm (16in.).

Access panels shall swing outward only.

(3) Access panel doors shall be self‐closing and self‐locking. The key shall be Group 2

Security (See 8.1).

(4) The space that houses the detection device(s) shall be furnished with protective guards

(cages) that will prevent accidental contact by a person or object with moving equipment

within the hoistway. No part of the protective guards (cages) shall be removable from

outside the hoistway or from within the space between the access panel and the

protective guards (cage). The protective guard described in (5) shall separate the rest of

the hoistway from the space containing the FAID.

(5) Protective guards (cages) shall be of noncombustible openwork material that shall reject

a ball 6 mm (0.25 in.) in diameter and be made from material equal to or stronger than

1.110 mm (0.0437 in.) diameter wire. The guard (cage) shall be so supported that when

subjected to a force of 450 N (100 lbf) applied over an area of 100 mm x 100 mm (4 in. x

4 in.) at any location, the deflection shall not reduce the clearance between the guard

(cage) and any elevator equipment in the hoistway below 25 mm (1 in.).

(6) Protective guards (cages) shall be installed such that all required hoistway running

clearances and beveling requirements are maintained. In no case shall the protective

guards (cages) extend more than 400 mm (16 in.) inside the hoistway.

(7) Prior to installation of fire alarm initiating devices or other fire detection systems in

hoistways, layout drawings indicating acceptable installation locations for access panels

and protective guards (cages) shall be coordinated with the elevator installer.

Rationale: Elevator hoistways can be extremely dangerous locations, and there are safety concerns

when fire alarm technicians, who are not trained as elevator personnel, perform work installing,

testing and maintaining fire alarm initiating devices located inside of the elevator hoistway.

The small size of the access panels in combination with the protective guards (cages) will prevent

injury to fire alarm technicians while performing work on fire alarm initiating devices located inside

the elevator hoistway and will prevent injury to elevator personnel should they be in the hoistway

while fire alarm technicians are accessing the FAIDs.

Proposed new requirement:

2.28.1(k) locations of access panels and protective guards when provided in compliance with

2.8.2.4(b).

Rationale: The location of the access panels and protective guards affects the elevator installer,

elevator personnel, the fire alarm system designer and fire alarm technicians. Indicating the location

of these on the layout drawings ensures that the information required by all parties can be found in

one place. This information is also useful to the AHJs who inspected both the elevator and the fire

alarm system.

Proposed new requirement:

2.8.3.1.4 Pipes used for air sampling smoke detection systems shall be permitted to be installed in

hoistways, machinery spaces, machine rooms, control spaces, and control rooms for the purpose of

detecting smoke in accordance with 2.27.3.2 Phase I Emergency Recall Operation by Fire Alarm

Initiating Devices and shall not encroach upon required clearances. Pipes or their sensing elements

penetrating the hoistway enclosure shall have a fire resistance rating conforming to the requirements

of the building code.

Rationale: To add requirements for air sampling type FAIDs that will be permitted to be used on

elevator installations.

CHAPTER 4. DIVISION OF INDUSTRIAL SAFETY Subchapter 6. Elevator Safety Orders GROUP 4. CONVEYANCE INSTALLATIONS FOR WHICH THE INSTALLATION CONTRACT WAS SIGNED ON OR AFTER MAY 1, 2008 ARTICLE 41. CONVEYANCES COVERED BY ASME A17.1-2004 Return to index New query

§ 3141.7. General Requirements.

(a) Conveyances shall comply with the following general requirements:

(1) Hoistway door unlocking devices described in ASME A17.1-2004, section 2.12.6, are prohibited on all conveyances;

(2) Emergency doors in blind hoistways as described in ASME A17.1-2004, section 2.11.1.2, and access panels as described in ASME A17.1-2004, section 2.11.1.4, are prohibited;

(3) All electrical equipment and wiring shall comply with CCR, Title 24, Part 3, California Electrical Code in effect at the time of installation;

(A) The light switch shall be located inside the machine room on the strike side of the machine room door;

(B) The light switch shall be located adjacent to the elevator pit access door within 18 inches to 36 inches above the access landing when access to the elevator pit is through the lowest landing door;

(C) Fire detecting systems for hoistways and the necessary wiring may be installed in hoistways, provided that the system is arranged to be serviced and repaired from outside the hoistway;

http://www.dir.ca.gov/title8/index/T8index.asp�

http://www.dir.ca.gov/samples/search/query.htm�


21.3.6

Smoke detectors or other automatic fire detection as permited by 21.3.9, shall not be installed inunsprinklered elevator hoistways unless they are installed to activate the elevator hoistway smoke reliefequipment or to initiate Phase I Emergency Recall Operation as required in 21.3.13.1 (2) and 21.3.13.2(2).


Fire detection devices other than smoke detectors, may be used to generate Phase I emergency recall operation as permitted by Section 21.3.9.



Public Input No. 289-NFPA 72-2016 [Section No.21.3.5]

same reason - to be consistent with section21.3.9




Affilliation: SFFD

Street Address:

City:

State:

Zip:

Submittal Date: Sun Jun 05 00:05:11 EDT 2016


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


21.3.7*

When sprinklers are required in elevator hoistways by other codes or standards, fire alarm initiating devicesshall be installed to initiate elevator recall in Phase I Emergency Recall Operation in accordance with 2.27.3.2.1(c) of ANSI/ASME A.17.1/CSA B44, Safety Code for Elevators and Escalators, and the following shallapply:

(1) Where sprinklers are located above at the lowest level top of recall the hoistway , the fire detectionalarm initiating device(s) shall be located at the top of the hoistway.

(2) Where sprinklers are located in the bottom of the hoistway (the pit), fire detection alarm initiatingdevice(s) shall shall be installed in the pit in accordance with Chapter 17.

(3) Outputs to from the elevator controller(s) shall fire alarm system to the elevator system shall complywith 21.3.13.

(4) The fire alarm initiating device(s) shall be accessible for testing, repair and maintenance from outsidethe hoistway

(5) Air aspirating smoke detection shall be permitted to be used for this purpose

(6) The fire alarm initiating device(s) shall be installed in accordance with 17.4.4 and 17.4.7


1. Use consistent terms for Fire alarm initiating device(s)2. Delete the specific section (2.27.2.3..1(c) ) reference for the A17.1 code and just state the general Section 2.27 since this specific section number might be changed in the next edition(s) of the A17.1 code.3. Clarify that sprinklers are installed in elevator hoistways either at the top of the hoistway or at the bottom of the hoistway (pit) - there is no code requirement in NFPA 13 to install sprinklers in other locations inside elevator hoistways.4. Clarify and be consistent with other sections in 21.3, 21.5 and 21.6 and the A17.1 code, that outputs are provided from the fire alarm system to the elevator system (delete the terms elevator management system and controller (s)) 5. The proposal for accessing fire alarm initiating devices from outside the hoistway failed during the last code cycle since there were no provisions in the A17.1 elevator code for access doors and hoistway openings. Since then, a proposal was made to include provisions in the A17.1 code for allowing FAIDs to be accessed from outside the hoistway or to use air aspirating smoke detection located outside the hoistway. This proposal was submitted by Bruce Fraser and passed the ballot at the hoistway committee during their June 2016 meeting. Therefore, when this requirement will be included in NFPA 72 it will be consistent with A17.1 new provision to allow hoistway access for FAIDs from outside the hoistway.







Affilliation: SFFD

Street Address:

City:

State:


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

Zip:



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


21.3.7*

When sprinklers are required to be installed in elevator hoistways by other codes or standards, NFPA 13,Standard for the installation of Sprinkler Systems , fire alarm initiating devices device(s) shall be installedin the hoistway to initiate elevator recall Phase I Emergency Recall Opeartion in accordance with 2.27.3.2.1(c) of ANSI/ASME A.17.1/CSA B44, Safety Code for Elevators and Escalators, and the following shallapply:

Where sprinklers are located above the lowest level of recall, the fire detection device shall be located atthe top of the hoistway.

Where sprinklers are located in the bottom of the hoistway (the pit), fire detection device(s) shall beinstalled in the pit in accordance with Chapter 17 .

Outputs to the elevator controller(s)

(1) The fire alarm intiating device(s) shall be accessible for testing, repair and maintenance from outsidethe hoistway.

(2) Air aspirating smoke detection shall be permitted to be used for this purpose.

(3) Outputs from the fire alarm system to the elevator system shall comply with 21.3.13

(4) The fire alarm initiating device(s) shall be installed in accordance with 17 . 4.4 and 17.4.7.



Picture1_Hoistway_ASD.pngExample for top of hoistway smoke detection with Air Aspirating Smoke Detector installed outside the hoistway

Picture_2_-_Hoistway_FAID.png

Example for top of hoistway ASD installation - Installed outside the hoistway

Picture_3_-_Hoistway_FAID.png

Explanation of the ASD detection for elevator hoistways - only three 3/4" pipe penetrations are required: Sampling Port, Exhaust Port and testing port

Access_Hatch_-_Hoistay_SD.GIF

Example for Access Hatch door + cage for a spot type smoke detector installed at top of elevator hoistway and accessible from outside the hoistway


The intent of this proposal is:1. To ensure that all fire alarm initiating devices required to be installed inside elevator hoistways to generate phase I Emergency Recall Operations, will be accessible for testing, repair and maintenance by fire alarm personnel from outside the elevator hoistway without the need to risk their life by riding on top of elevator cars inside elevator hoistways which are extremely dangerous environments. 2. Delete the requirement for a specific fire alarm initiating device in elevator pit since it is already included in A17.1 Section 2.27 and since this FAID is unnecessary (There is no data or known cases for hydraulic fluid fires in elevators pit which is the source for the pit sprinkler requirement per NFPA 13)






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



Affilliation: SFFD

Street Address:

City:

State:

Zip:



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


21.3.8*

Smoke detectors detector(s) shall not be installed in elevator hoistways hoistway(s) to initiate elevatorrecall unless the smoke detector is listed Phase I Emergency Recall Operation unless it is suitble for theenvironment.


1. Revise the verbiage to indicate smoke detector (s) and hoistway (s)2. Correct the term elevator Phase I Emergency Recall Operation to be consistent with Section 21.33. Change the term "listed" for the environment to "suitable" for the environment - The reason is that smoke detectors do not have specific listing for elevator hoistways. They may be listed for harsh or dirty environment which will be suitable for elevator hoistways but not necessarily listed. Also I will proposes that the annex material for this section will reference NFPA 72 annex B to allow performance based selection of specific detector (s) to be installed in elevator hoistway (s)



Public Input No. 322-NFPA 72-2016 [Section No. A.21.3.8]





Affilliation: SFFD

Street Address:

City:

State:

Zip:



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


21.3.10

When actuated, any fire alarm initiating device that is used to initiate elevator Phase 1 I Emergency RecallOperation shall be annunciated at the building fire alarm control unit or at the fire alarm control unitdescribed in 21.3.2.


A Correlating Committee task group on language/terms reviewed the language of the Code for consistency and grammar. The term “Phase I” is used 13 times in the Code, including in the heading of this section, while “Phase 1” is used twice. Recommend revising “phase 1” to “phase I” for consistency within the Code.




Street Address:

City:

State:

Zip:



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


21.3.13.1 Designated Level Recall. * Elevator Phase I Emergency Recall Opeartion to DesignatedLevel

For each elevator or group of elevators operating in a group automatic operation , an output shall beprovided from the fire alarm system to signal elevator recall to the designated level the elevator system inresponse to the following:

(1) Activation of smoke detectors detector(s) or other automatic fire detection as permitted by 21.3.9located at any associated elevator lobby served by the elevator (s) lobby other than the lobby at thedesignated level

(2) Activation of smoke detectors detector(s) or other automatic fire detection as permitted by 21.3.9located at any elevator machine any associated elevator(s) machine room, elevator machinery spacecontaining a motor controller or driving machine , elevator control space, or elevator control roomserving the elevator(s) , except where such rooms or spaces are located at the designated level

(3) Activation of smoke detectors detector(s) or other automatic fire detection as permitted by 21.3.9located in the elevator hoistway serving the elevator where sprinklers or elevator control spaces orelevator machinery spaces at any associated elevator(s) hoistway when sprinklers are located in thehoistway those hoistways , unless otherwise specified in 21.3.13.2 (3)



Proposed_definitions_and_code_sections_from_ASME_A17.docx

Proposed definitions and code sections from ASME A17.1 to help understand the elevator associated terms described in Section 21.3 of NFPA 72.


1. Revise this section to be consistent with ASME A17.1 verbiage and requirments2. Include the term group automatic operation as specified in A17.1 (propose to add the defination for a group automatic operation in the annex to this section)3. Include the specific locations described in the A17.1 code for machinery space containing a motor controller or driving machine which applies to all Machine Room Less (MRL) elevators

This is from ASME A17.1 -2013 (as a reference)

Phase I Emergency Recall Operation to the designated level shall conform to the following:(a) The activation of a fire alarm initiating device specified in 2.27.3.2.1(a) or 2.27.3.2.2(a) at any floor, other than at the designated level, shall cause all elevators that serve that floor, and any associated elevator of a group automatic operation, to be returned nonstop tothe designated level.



Public Input No. 325-NFPA 72-2016 [Section No. 21.3.13.2]




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



Affilliation: SFFD

Street Address:

City:

State:

Zip:



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

Proposed definitions and code sections from ASME A17.1‐2013 to be included in NFPA 72 Annex

material related as a reference to Section NFPA 72 21.3

Designated level: the main floor or other floor level that best serves the needs of emergency personnel for firefighting or rescue purposes identified by the building code or fire authority.

alternate level: a floor level identified by the building code or fire authority, other than the designated level.

recall level: the designated or alternate level that cars are returned to when Phase I Emergency Recall Operation is activated.

operation, group automatic: automatic operation of two or more nonattendant elevators equipped with power-operated car and hoistway doors. The operation of the cars is coordinated by a supervisory control system including automatic dispatching means whereby selected cars at designated dispatching points automatically close their doors and proceed on their trips in a regulated manner. It may include but is not limited to: operating device(s) in the car and/or at each landing that provide a means to select destinations identified with landings; keypads or touch screens at each landing and/or in the car; buttons in each car for each floor served and “UP” and “DOWN” buttons at each landing (single buttons at terminal landings). The stops set up by the momentary actuation of these devices are made automatically in succession as a car reaches the corresponding landing, irrespective of its direction of travel or the sequence in which the devices are actuated. The stops set up by the momentary actuation of the device(s) at the landing may be accomplished by any elevator in the group, and are made automatically.

2.27.3.2 Phase I Emergency Recall Operation by Fire Alarm Initiating Devices 2.27.3.2.1 In jurisdictions not enforcing the NBCC, smoke detectors or other automatic fire detectors in environments not suitable for smoke detectors (fire alarm initiating devices) used to initiate Phase I Emergency Recall Operation shall be installed in conformance with the requirements of NFPA 72, and shall be located (a) at each elevator lobby served by the elevator

(b) in the associated elevator machine room, machinery space containing a motor controller or driving machine, control space, or control room (c) in the elevator hoistway, when sprinklers are located in those hoistways

2.27.3.2.3 Phase I Emergency Recall Operation to the designated level shall conform to the following: (a) The activation of a fire alarm initiating device specified in 2.27.3.2.1(a) or 2.27.3.2.2(a) at any floor, other than at the designated level, shall cause all elevators that serve that floor, and any associated elevator of a group automatic operation, to be returned nonstop to the designated level. (b) The activation of a fire alarm initiating device specified in 2.27.3.2.1(b) or 2.27.3.2.2(b) shall cause all elevators having any equipment located in that room or space, and any associated elevators of a group automatic operation, to be returned nonstop to the designated level. If the machine room is located at the designated level, the elevator(s) shall be returned nonstop to the alternate level. (c) In jurisdictions not enforcing NBCC, the activation of a fire alarm initiating device specified in 2.27.3.2.1(c) shall cause all elevators having any equipment in that hoistway, and any associated elevators of a group automatic operation, to be returned nonstop to the designated level, except that initiating device(s) installed at or below the lowest landing of recall shall cause the car to be sent to the upper recall level. (d) In jurisdictions enforcing the NBCC, the initiation of a fire detector in the hoistway shall cause all elevators having any equipment in that hoistway, and any associated elevators of a group automatic operation, to be returned nonstop to the designated level, except that initiating device(s) installed at or below the lowest landing of recall shall cause the car to be sent to the upper recall level. (e) The Phase I Emergency Recall Operation to the designated level shall conform to 2.27.3.1.6(a) through (n). 2.27.3.2.4 Phase I Emergency Recall Operation to an alternate level (see 1.3) shall conform to the following: (a) the activation of a fire alarm initiating device specified in 2.27.3.2.1(a) or 2.27.3.2.2(a) that is located at the designated level, shall cause all elevators serving that level to be recalled to an alternate level, unless Phase I Emergency Recall Operation is in effect (b) the requirements of 2.27.3.1.6(f), (j), (m), and (n) (c) the requirements of 2.27.3.1.6(a), (b), (c), (d), (e), (g), (h), (i), (k), and (l), except that all references to the “designated level” shall be replaced with “alternate level”


21.3.13.2 Alternate Level Recall. Elevator Phase I Emergency Recall Operation to Alternate Level

For each elevator or group of elevators opearting in a group automatic operation , an output shall beprovided to signal elevator recall to the alternate level in from the fire alarm system to the elvator system in response to the following:

(1) Activation of smoke detectors detector(s) , or other automatic fire detection as permitted by 21.3.9,located at the designated level lobby served by the elevator(s)

(2) Activation of smoke detectors detector(s) , or other automatic fire detection as permitted by 21.3.9,located in the elevator machine machine room, elevator machinery space containing a motor controlleror driving machine , elevator control space, or elevator control room room serving the elevator(s) ifsuch rooms or spaces are located at the designated level

(3)


Revise the verbiage of this section to be consistent with the ASME A17.1 code verbiage and requirmentsSee rational to Section 21.3.13.1



Public Input No. 324-NFPA 72-2016 [Section No.21.3.13.1]

same rational to be consistent with the ASMEA17.1 code

Public Input No. 326-NFPA 72-2016 [Section No.21.3.13.3]




Affilliation: SFFD

Street Address:

City:

State:

Zip:


* Activation of the initiating devices fire alarm initiating device(s) identified in 21.3.13.1 (3) if they areinstalled at or below the lowest level of recall in the elevator hoistway and the alternate level is locatedabove the designated level


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


21.3.13.3* Elevator Warning Visual Signal.

For each elevator or group of elevators operating in group automatic operation , an output shall be providedfrom the fire alarm system to the elevator controller system in response to any of the following:

(1) Activation of the elevator machine room, elevator machinery space, elevator control space, orelevator control room initiating devices any of the fire alarm initiating device(s) identified in 21.3.13.1(2) or 21.3.13.2 (2)

(2) Activation of the elevator hoistway initiating devices any of the fire alarm initiating device(s) identifiedin 21.3.13.1 (3) or 21.3.13.2 (3)


1. The term elevator "warning" signal is not defined in the ASME A17.1 code - the term visual signal (also known as the firefighter hat symbol) is specified in A!&.1 2. Clean the language of the sub sections of this section to be consistent with the referenced sections in 21.3.1.13 1 and 2 which already specify the specific locations of the fire alarm initiating devices 3. use the term fire alarm initiating device(s) for consistency with other sections in 21.3 and the A17.1 code



Public Input No. 324-NFPA 72-2016 [Section No. 21.3.13.1] referenced section

Public Input No. 325-NFPA 72-2016 [Section No. 21.3.13.2] referenced section





Affilliation: SFFD

Street Address:

City:

State:

Zip:



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


21.3.13.3 * Elevator Warning Signal.

For each elevator or group of elevators, an output shall be provided to the elevator controller in response toany of the following:

(1) Activation of the elevator machine room, elevator machinery space, elevator control space, orelevator control room initiating devices identified in 21.3.13.1 (2) or 21.3.13.2 (2)

(2) Activation of the elevator hoistway initiating devices identified in 21.3.13.1 (3) or 21.3.13.2 (3)


This section is unnecessary, redundant and confusing.The reason is that "Elevator Warning Signal" is not a defined term in the ASME A17.1 code and there is no need to provide additional output signals from the fire alarm system to the elevator system in addition to the signals specified in sections 21.3.13.1 and 21.3.13.2Therefore, this section (21.3.13.3) is redundant and unnecessary.

The visual signal (firefighter's hat symbol) described in the ASME A17.1 code is activated solely by the elevator system (solid or flashing) upon a specific defined priority described in the A17.1 code.

This is the section from the A17.1-2013 code describing the operation of the Visual Signal in SOLID mode which can be activated upon the Manual Phase I FIRE Recall keyed switch (not related to the activation of the fire alarm system - and therefore this section in NFPA 72 is confusing)

2.27.3.1.6 (h) An illuminated visual and audible signal systemshall be activated. The visual signal shall be one of thesymbols shown in Fig. 2.27.3.1.6(h) and located on thecar-operating panel. The entire circular or square areaor the outline of the hat, or the outline of the area shownin Fig. 2.27.3.1.6(h) shall be illuminated. The visual signal shall remain activated until the car is restored toautomatic operation. When the door is open, the audiblesignal shall remain active until the door is closed. Whenthe door is closed, the audible signal shall remain activefor a minimum of 5 s. The audible signal shall not beactive when the car is at the recall level.

The fire alarm system is only responsible for providing the output signals required in 21.3.13.1 and 21.3.13.2 to the elevator system, and the elevator system does the rest (turning this visual signal Solid or Flashing)

This is the section from ASME A17.1-2013 describing the "Flashing" operation of the visual symbol

2.27.3.2.6 When Phase I Emergency RecallOperation is initiated by a fire alarm initiating devicefor any location listed in 2.27.3.2.6(a) through (e), asrequired by 2.27.3.2.3 or 2.27.3.2.4, the visual signal [see2.27.3.1.6(h) and Fig. 2.27.3.1.6(h)] shall illuminate intermittently only in a car(s) with equipment in that location,as follows:(a) machine room


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

(b) machinery space containing a motor controller ordriving machine(c) control room(d) control space(e) hoistway



Public Input No. 326-NFPA 72-2016 [Section No. 21.3.13.3] Same section but different proposal




Affilliation: SFFD

Street Address:

City:

State:

Zip:



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


21.4 Elevator Power Shutdown.

21.4.1*

Where heat detectors are used to shut down elevator power prior to sprinkler operation, the detector Whenheat detector(s) are used to activate the disconnecting means described in 2.8 of ANSI/ASME A.17.1/CSAB44, Safety Code for Elevators and Escalators, to disconnect the main line power supply to the affectedelevator and any other

power supplies used to move the elevator upon or prior to the activation of sprinkler(s). the detector(s) shallhave both a lower temperature rating and a higher sensitivity lower Response Time Index (RTI) ascompared to the sprinkler (s) .

21.4.2*

If heat detectors are used to shut down elevator power prior to sprinkler operation, they The heatdetector(s) in 21.4.1 shall be placed within 24 in. (610 mm) of each sprinkler and be installed inaccordance with the requirements of Chapter 17.

21.4.2.1

Engineering methods, such as those specified in Annex B, shall be permitted to be used to select andplace heat detectors to ensure response prior to any sprinkler operation under a variety of fire growth ratescenarios.

21.4.3*

If pressure or waterflow switches switche(s) are used to shut down elevator power immediately upon, orprior to, the discharge of water from sprinklers activate the disconnecting means described in 2.8 ofANSI/ASME A.17.1/CSA B44, Safety Code for Elevators and Escalators, to disconnect the main line powersupply to the affected elevator and any other

power supplies used to move the elevator upon or prior to the activation of sprinkler(s) , the use of devices withtime-delay switches or time-delay capability shall not be permitted.

21.4.4*

Control circuits to shut down elevator power of the disconnecting means described in 21.4.1 shall bemonitored for the presence of operating voltage. Loss of voltage to the control circuit for the disconnectingmeans shall cause a supervisory signal to be indicated at the building fire alarm control unit or at the controlunit described in 21.3.2.

21.4.5

The fire alarm initiating devices described in 21.4.2 and 21.4.3 shall be monitored for integrity by the firealarm control unit required in 21.3.1 and 21.3.2.


To be consistent with the ASME A17.1 code and requirements.Heat detectors activate the elevator Shunt Trip breaker via fire alarm system control relay - The shunt trip beaker is refereed as the "disconnecting means" described both in the A17.1 code and in this section The RTI term is used as it referenced in NFPA 72 Chapter 17 and annex B.




Affilliation: SFFD

Street Address:


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

City:

State:

Zip:



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


21.5 Fire Service Access Elevators.

Where one or more elevators are specifically designated and marked as fire service access elevators,21.5.1and 21.5.2 shall apply.

21.5.1 *

Status of elevator(s), including location within the hoistway, direction of travel, and whether the elevator(s)are occupied, shall be permitted to be displayed on a building fire alarm system annunciator located at thefire command center.

21.5.2

Temperature and presence of smoke in associated elevator lobbies, machine rooms, control rooms,machinery spaces, or control spaces shall be continuously monitored and displayed on a building fire alarmsystem annunciator(s) located at the fire command center.

21.5.3 2

The conditions in 21.5.1 and 21.5.2 shall be permitted to be displayed on a standard emergencyservices interface complying with Section 18.11 . listed non-fire alarm system annunciator(s) or other asapproved by the authority having jurisdiction.


Mr. Jack Poole (SIG-PRO Chair) and Mr. Richard Roux (NFPA 72 Staff Liaison) requested formation of a task group to clarify and further define the fire alarm system interface requirements with occupant evacuation elevators. The task group (Bruce Fraser, Sagiv Weiss-Ishai, Kurt Ruchala, Carl Willms, Dan Finnegan, and Brandon Wilkerson (Chair)) developed a revised section 21.6, proposed revisions to section 21.5, proposed a revision to the section 21.6.2.3.5 included in the new section 21.6, and developed a flow chart intended to capture the requirements in graphic form. These proposed changes are important due to the complexities included in occupant evacuation elevator operation and the associated fire alarm system interface. Because this is a relatively new code concept which is applied in a relatively small number of buildings and can have a major impact on occupant safety during fire and non-fire emergencies, it is critical that NFPA 72 clearly outline the fire alarm system expectations. The changes proposed by this task group are a result of detailed coordination with the ASME A17.1/CSA B44 Task Group, real-world experience, and multiple task group meetings.

The required monitored conditions other than temperature and presence of smoke described in NFPA 72-2016 Section 21.5 are proposed to be deleted since they are not provided by the fire alarm system. Other revisions are proposed for clarity and in coordination with the revisions proposed for section 21.6.



Public Input No. 666-NFPA 72-2016 [Section No. 21.6]

Public Input No. 740-NFPA 72-2016 [Sections A.21.6.2.1.1(2), A.21.6.2.1.2, A.21.6.2.1.4,A.21....]


Submitter Full Name: Brandon Wilkerson

Organization: Poole Fire Protection

Affilliation: NFPA 72 Occupant Evacuation Operation Task Group

Street Address:

City:


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

State:

Zip:



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


21.5.2

Temperature and presence of smoke in associated lobbies, machine rooms, control rooms, machineryspaces, or control spaces shall be continuously monitored and displayed on a building fire alarm systemannunciator located at the fire command center.


All of the spaces noted in this paragraph that are required to be continuously monitored for temperature and smoke are currently required to be provided with smoke detection that reports to the FACP in the fire command center. The current code language noting "continuously monitored and displayed" would imply some type of system is required other than a fire alarm system. Fire alarm systems don't display obscuration levels continuously or temperature at multiple points continuously. The smoke detection currently required in these spaces provides the early warning of a potential hazardous environment to provide the necessary safety for fire fighters.





Submitter Full Name: Raymond Grill

Organization: Arup

Street Address:

City:

State:

Zip:



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


21.5.3

The conditions in 21.5.1 and 21.5.2 shall be permitted to be displayed on a standard emergencyservices interface complying with Section 18.11.


If PI 441 is accepted, reference to this section should be deleted.





Submitter Full Name: Raymond Grill

Organization: Arup

Street Address:

City:

State:

Zip:



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


21.5.3

The conditions in 21.5.1 and 21.5.2 shall be permitted to be displayed on a standard emergencyservices interface complying with Section 18.11 .


This section was revised by the OEO TG and there is no need to have this "standard emergency service interface"See rational for PI 772 and 773 related to section 18.11



Public Input No. 774-NFPA 72-2016 [Section No. A.21.5.1] same rational

Public Input No. 773-NFPA 72-2016 [Section No. A.18.11] same rational

Public Input No. 772-NFPA 72-2016 [Section No. 18.11] same rational




Affilliation: SFFD

Street Address:

City:

State:

Zip:



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


21.6.2.3.6* When the first active alarm is initiated from a discharge floor, the fire alarm systemshall send a signal to the elevator control system.


Mr. Jack Poole (SIG-PRO Chair) and Mr. Richard Roux (NFPA 72 Staff Liaison) requested formation of a task group to clarify and further define the fire alarm system interface requirements with occupant evacuation elevators. The task group (Bruce Fraser, Sagiv Weiss-Ishai, Kurt Ruchala, Carl Willms, Dan Finnegan, and Brandon Wilkerson (Chair)) developed a revised section 21.6, proposed revisions to section 21.5, proposed a revision to the section 21.6.2.3.5 included in the new section 21.6, and developed a flow chart intended to capture the requirements in graphic form. These proposed changes are important due to the complexities included in occupant evacuation elevator operation and the associated fire alarm system interface. Because this is a relatively new code concept which is applied in a relatively small number of buildings and can have a major impact on occupant safety during fire and non-fire emergencies, it is critical that NFPA 72 clearly outline the fire alarm system expectations. The changes proposed by this task group are a result of detailed coordination with the ASME A17.1/CSA B44 Task Group, real-world experience, and multiple task group meetings.

These changes are proposed separately from the general 21.6 changes because the ASME A17.1/CSA B44 Task Group has not yet clearly addressed the required occupant notification where the active alarm on the elevator discharge level has activated either as the first or a subsequent alarm.








Street Address:

City:

State:

Zip:



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



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

21.6 * Occupant Evacuation Elevators.

21.6.1

Elevator Status.

Where one or more Where elevators are

specifically designated and marked for use by occupants forto be used for occupant self- evacuation during fires and non-fire emergencies , they shall comply with

all of the provisions ofSections 21.5 and 21.6 .

21.6.2

ElevatorOccupant Evacuation Operation (OEO).

Outputs from the fire alarm system to the elevator

controller(s)system shall be provided to implement elevator occupant evacuation operation in accordance with

Section 2Section 2 .27 of ASME A17.1/CSA B44 (

20132016 ), Safety Code for Elevators and Escalators , as required in 21.6.2.1 through 21.6.2.5.

21.6.2.1 Applicability. OEO shall only be initiated upon an automatic or manual signal from the firealarm system to the elevator system.

21.6.2.1.1* OEO shall apply separately to each individual elevator and to elevators having “groupautomatic operation” or designated as an “elevator group” or “group of elevators”.

21.6.2. 1. 2 * OEO shall function per 21 . 6.2.1.1 only prior to Phase 1 Emergency Recall Operation.

21.6.2.

1 2 Partial Building Evacuation.

Where an elevator or group of elevators is designated for use by occupants for self- evacuation, theprovisions of 21.6.2.

1.13 through 21.6.2.

1.46 shall apply for partial building evacuation.

21.6.2.

1.1 3 Initiation.

Output signal(s) shall be provided to initiate elevator occupant evacuation operation upon automatic ormanual detection of a fire on a specific floor or floors as a result of either or both of the following:Activation of anyOEO shall be initiated by either manual means from the Fire Command Center (FCC) in accordance with21.6.2.4 or by actuation of an automatic fire alarm initiating device in

the building, other than an initiating device used for elevator Phase I Emergency Recall Operation inaccordance with 21. 6.2. 3.

13 1.

21.6.2.3.1* An active automatic fire alarm initiating device that does not initiate Phase I EmergencyRecall Operation shall cause the fire alarm system to provide a signal to the elevator system indicating thefloor of an active alarm.

21.6.2.

* Activation of manual means at the fire command center by authorized or emergency personnel


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

13 .2

* Floor Identification.

(A)

The output signal(s) shall identify each floorThe floors to be evacuated

.

(B)

The identified floorsshall be a contiguous block of floors

including the following:

The floor with the first activated automatic initiating device.

Floors with any subsequently activated automatic initiating device(s).

Floors identified by manual means from the fire command center.

Two floors above the highest floor identified bydesignated as “the elevator evacuation zone” consisting of at least the floor with an active alarm, two floorsabove the floor with the active alarm and two floors below the floor with the active alarm.

21.6.2.

1.2(B) (1) through3.3* When the floor designated as the elevator discharge level falls within the elevator evacuation zone,it is not to be evacuated by the elevator(s), and the fire alarm system shall initiate a voice message toinstruct the occupants on that level to exit the building.

21.6.2.

1.2(B) (3).Two floors below the lowest floor identified by3.4 If activation of an automatic fire alarm initiating device which does not initiate Phase I EmergencyRecall Operation occurs on an additional floor(s) including the elevator discharge level at any time whileOEO is in effect, the elevator evacuation zone shall be expanded to include all floors with an active alarm,all floors between the highest and lowest floor with an active alarm plus two floors above the highest floorwith an active alarm and two floors below the lowest floor with an active alarm.

21.6.2.

1.2(B) (1) through3.5 If the first active alarm is on the elevator discharge level, automatic initiation of OEO shall not bepermitted for all elevators having that same elevator discharge level.

21.6.2.

1.2(B) (3).

(C)

The identified floors shall be displayed on a standard emergency services interface along with the otherelevator status information required by 21.6.1 .


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

4* Manual Floor Selection.

(A) A means shall be furnished at the FCC to provide for the manual selection of each floor in the building.

(B) The manual floor selection shall be activated only by authorized or emergency personnel.

(C) When OEO is not yet in effect, and a manual floor selection is made to initiate OEO, a signal shall besent to the elevator system simulating an active alarm.

(D) When OEO is in effect and a manual floor selection is made, the elevator evacuation zone shall beexpanded as described in 21.6.2.3.4.

(E) The manual selection shall provide a non-latching output(s).

21.6.2.

1.3 Manual Floor Selection.5* Fire Alarm Output Signals to Elevator System.

(A)

A means shall be provided atOutput from the fire

command centeralarm system to

allow the manual selection of floorsthe elevator system shall identify each floor with an active alarm .

(B)

The floors shall be selected on the basis of information from authorized or emergency personnelOutput from the fire alarm system to the elevator system shall include the following:

(1) The floor with the first activated automatic fire alarm initiating device.

(2) Floor(s) with any subsequently activated automatic fire alarm initiating device(s).

(3) Floor(s) selected by manual means from the FCC.

(C) The identified floor(s) shall be displayed on the building fire alarm system annunciator at the FCC or ona listed non-fire alarm system annunciator or other annunciator as approved by the authority havingjurisdiction .

21.6.2.

1.46 *

Occupant Notification.

The in-building fire emergency voice/alarm communications system shall transmit messages coordinated

messages throughout the buildingwith the elevator system’s text displays in all elevator lobbies .

(A)

Automatic voice evacuation messages shall be transmitted to the

floors identified in 21.6.2.1.2elevator evacuation zone to indicate the need to evacuate and that elevator service is available.

(B)

Automatic voice messages shall be transmitted to the floors not being evacuated within the specific groupof elevator(s) performing OEO, to inform occupants

of evacuation status and shall include an indicationthat elevator service is not available.

(C) *

Automatic voice messages shall be transmitted to the


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

floors identified in 21.6.2.1.2elevator evacuation zone to indicate that elevator service is not available when all elevators

have been recalled on Phase I Emergency Recall Operationserving that elevator evacuation zone are out of service .

(D)

All automatic voice messages shall be coordinated so as not to be in conflict with the text displaysprovided separately by the elevator

managementsystem.

(E) * When required by the building code, the emergency voice/alarm communications system’sspeaker(s) located in each OEE lobby, shall be connected to a separate notification zone for manualpaging only. Individual paging zones per each OEE lobby on each floor, grouped paging zone for all OEElobbies on a floor, or vertical paging zone for each elevator group shall be permitted as approved by theauthority having jurisdiction.

(F) Visible notification appliances (strobes) shall comply with 24.5.17.3(1), (2), and (3).

21.6.2.

2 7 Total Evacuation.

Where an elevator or group of elevators is designated for use by occupants for evacuation, the provisionsofA means to initiate total building evacuation, labeled “ELEVATOR TOTAL BUILDING EVACUATION” shallbe provided at the FCC.

21.6.2.

2.1 through7.1 When this means is actuated, the fire alarm system shall provide a signal to the elevator systemindicating that all floors in the building are to be evacuated.

21.6.2.

2.3 shall apply for total evacuation7.2 The in-building fire emergency voice/alarm communications system shall transmit an evacuationmessage throughout the building to indicate the need to evacuate .

21.6.2. 8* Suspension of OEO for an Individual Elevator or Group of Elevators.

21.6. 2.

1 Output(s) to signal elevator occupant evacuation operation for total evacuation shall be manuallyactivated from the fire command center by a means labeled “ELEVATOR TOTAL BUILDINGEVACUATION.”8.1 OEO shall be suspended for an individual elevator or group of elevators when an individual elevatoror a group of elevators have been manually recalled via an elevator system designated key operatedswitch(s) labeled “Car Fire Recall” or “Group Fire Recall”.

21.6.2. 8. 2 When OEO has been suspended as in 21 .

2 The output(s) shall identify that all floors are to be evacuated.6.2.8.1, the in-building fire emergency voice/alarm communications system shall transmit messagescoordinated with the elevator system’s text displays in compliance with 21.6.2.6.

21.6.2.9* Partial Termination of OEO.

21.6.2.9.1 OEO shall be terminated for a specific group of elevator(s) when the signal(s) provided in21.3.13.1 and 21.3.13.2 associated with this group of elevator(s), has initiated Phase I Emergency RecallOperation for this group of elevator(s).

21.6.2.

2.3 The9.2 When OEO has been partially terminated, the in-building fire emergency voice/alarm communicationssystem shall transmit


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

an evacuation message throughout the building to indicate the need to evacuate.messages coordinated with the elevator system’s text displays in compliance with 21.6.2.6.

21.6.2.10 Total Termination of OEO.

21.6.2.10.1 OEO shall be terminated for all elevators in the building upon reset of the fire alarm system.

21.6.2.10.2* OEO shall be terminated when there are no elevators available for self-evacuation.



Proposed_Changes_for_Section_21_6_-_TG_-_Rev13.docx

This is the total public input for the code body and annex material for 21.6 as developed by the OEO TG.


Mr. Jack Poole (SIG-PRO Chair) and Mr. Richard Roux (NFPA 72 Staff Liaison) requested formation of a task group to clarify and further define the fire alarm system interface requirements with occupant evacuation elevators. The task group (Bruce Fraser, Sagiv Weiss-Ishai, Kurt Ruchala, Carl Willms, Dan Finnegan, and Brandon Wilkerson (Chair)) developed a revised section 21.6, proposed revisions to section 21.5, proposed a revision to the section 21.6.2.3.5 included in the new section 21.6, and developed a flow chart intended to capture the requirements in graphic form. These proposed changes are important due to the complexities included in occupant evacuation elevator operation and the associated fire alarm system interface. Because this is a relatively new code concept which is applied in a relatively small number of buildings and can have a major impact on occupant safety during fire and non-fire emergencies, it is critical that NFPA 72 clearly outline the fire alarm system expectations. The changes proposed by this task group are a result of detailed coordination with ASME A17.1/CSA B44 OEO Task Group, real-world experience, and multiple task group meetings.

Because the proposed changes to 21.6 affect nearly every existing paragraph, the task group recommends replacing the section in its entirety, including the associated annex material.




Public Input No. 745-NFPA 72-2016 [New Section after 21.6]





Street Address:

City:

State:

Zip:



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

Page 1 of 6

Proposed Changes for Section 21.6 … TG – Rev13 Rationale/Substantiation Mr. Jack Poole (SIG‐PRO Chair) and Mr. Richard Roux (NFPA 72 Staff Liaison) requested formation of a task group to clarify and further define the fire alarm system interface requirements with occupant evacuation elevators. The task group (Bruce Fraser, Sagiv Weiss‐Ishai, Kurt Ruchala, Carl Willms, Dan Finnegan, and Brandon Wilkerson (Chair)) developed a revised section 21.6, proposed revisions to section 21.5, proposed a revision to the section 21.6.2.3.5 included in the new section 21.6, and developed a flow chart intended to capture the requirements in graphic form. These proposed changes are important due to the complexities included in occupant evacuation elevator operation and the associated fire alarm system interface. Because this is a relatively new code concept which is applied in a relatively small number of buildings and can have a major impact on occupant safety during fire and non‐fire emergencies, it is critical that NFPA 72 clearly outline the fire alarm system expectations. The changes proposed by this task group are a result of detailed coordination with ASME A17.1/CSA B44 OEO Task Group, real‐world experience, and multiple task group meetings. Because the proposed changes to 21.6 affect nearly every existing paragraph, the task group recommends replacing the section in its entirety, including the associated annex material. 21.6* Occupant Evacuation Elevators. A.21.6 Occupant evacuation elevators (OEE) are not required by code and they will be provided for a relatively limited number of buildings, mainly office use high‐rise buildings over 420 feet in lieu of a required third stairway as a building code exception. They could also be provided on a voluntary basis in other buildings due to ADA or mobility of occupants concerns. It is highly recommended that those involved with design and installation of these systems become familiar with available information such as ASME A17.1/CSA B44 (2016), Safety Code for Elevators and Escalators, Section 2.27 regarding Occupant Evacuation Operation (OEO) and its non‐mandatory Appendix V “Building Features for Occupant Evacuation Operation”. It will be imperative that a great amount of coordination and performance based design be done between elevator and fire alarm system designers, installation contractors and the authority having jurisdiction. 21.6.1 Elevator Status. Where elevators are to be used for occupant self‐evacuation during fires and non‐fire emergencies, they shall comply with Sections 21.5 and 21.6. 21.6.2 Occupant Evacuation Operation (OEO). Outputs from the fire alarm system to the elevator system shall be provided to implement elevator occupant evacuation operation in accordance with Section 2.27 of ASME A17.1/CSA B44 (2016), Safety Code for Elevators and Escalators, as required in 21.6.2.1 through 21.6.2.5. 21.6.2.1 Applicability. OEO shall only be initiated upon an automatic or manual signal from the fire alarm system to the elevator system. 21.6.2.1.1* OEO shall apply separately to each individual elevator and to elevators having “group automatic operation” or designated as an “elevator group” or “group of elevators”. A.21.6.2.1.1 The term “Group automatic operation” is defined in ANSI/ASME A17.1/CSA B44, Safety Code for Elevators and Escalators. Other terms such as “elevator group” or “group of elevators” are used in 21.6 to refer to those elevators sharing a common car call operation. For instance, if an elevator landing call is registered on a particular floor, any elevator that could respond to that call would be considered in that

Page 2 of 6

elevator group. Elevators in an “elevator group” typically share a lobby, hoistway, and/or machine/control room or control space. 21.6.2.1.2* OEO shall function per 21.6.2.1.1 only prior to Phase 1 Emergency Recall Operation. A.21.6.2.1.2 When OEO is activated either manually or automatically, it is applicable to all elevators serving the floors of the elevator evacuation zone. However, when a single elevator or a particular group of elevators is placed on manual Phase 1 Emergency Recall Operation, OEO continues to operate for the other elevators serving the elevator evacuation zone. Similarly, when a fire alarm initiating device(s) described in 21.3.13.1 and 21.3.13.2 is actuated, Phase 1 Emergency Recall Operation will cause recall only to the associated elevator or group of elevators and not to all elevators in the elevator evacuation zone not associated with that elevator or group of recalled elevators. See also 21.6.2.8. 21.6.2.2 Partial Building Evacuation. Where an elevator or group of elevators is designated for use by occupants for self‐evacuation, the provisions of 21.6.2.3 through 21.6.2.6 shall apply for partial building evacuation. 21.6.2.3 Initiation. OEO shall be initiated by either manual means from the Fire Command Center (FCC) in accordance with 21.6.2.4 or by actuation of an automatic fire alarm initiating device in accordance with 21.6.2.3.1. 21.6.2.3.1* An active automatic fire alarm initiating device that does not initiate Phase I Emergency Recall Operation shall cause the fire alarm system to provide a signal to the elevator system indicating the floor of an active alarm. A.21.6.2.3.1 This signal to the elevator system is caused by the activation of a fire alarm initiating device other than that which is described in 21.3.13.1 and 21.3.13.2. 21.6.2.3.2 The floors to be evacuated shall be a contiguous block of floors designated as “the elevator evacuation zone” consisting of at least the floor with an active alarm, two floors above the floor with the active alarm and two floors below the floor with the active alarm. 21.6.2.3.3* When the floor designated as the elevator discharge level falls within the elevator evacuation zone, it is not to be evacuated by the elevator(s), and the fire alarm system shall initiate a voice message to instruct the occupants on that level to exit the building. A.21.6.2.3.3 The elevator discharge level is considered the same level as the designated level of elevator recall for an individual elevator or a group of elevators. More than a single elevator discharge level may exist in a building. 21.6.2.3.4 If activation of an automatic fire alarm initiating device which does not initiate Phase I Emergency Recall Operation occurs on an additional floor(s) including the elevator discharge level at any time while OEO is in effect, the elevator evacuation zone shall be expanded to include all floors with an active alarm, all floors between the highest and lowest floor with an active alarm plus two floors above the highest floor with an active alarm and two floors below the lowest floor with an active alarm. 21.6.2.3.5 If the first active alarm is on the elevator discharge level, automatic initiation of OEO shall not be permitted for all elevators having that same elevator discharge level. 21.6.2.4* Manual Floor Selection. (A) A means shall be furnished at the FCC to provide for the manual selection of each floor in the building.

Page 3 of 6

(B) The manual floor selection shall be activated only by authorized or emergency personnel. (C) When OEO is not yet in effect, and a manual floor selection is made to initiate OEO, a signal shall be sent to the elevator system simulating an active alarm. (D) When OEO is in effect and a manual floor selection is made, the elevator evacuation zone shall be expanded as described in 21.6.2.3.4. (E) The manual selection shall provide a non‐latching output(s). A.21.6.2.4 The manual selection means such as a switch or a push button for each floor, is intended in lieu of automatic initiating devices that may be impaired or out of service and would otherwise have actuated to provide automatic initiation in accordance with 21.6.2.3. Manual fire alarm boxes are not included because they are typically activated at locations remote from the fire and could lead to misinformation about the location of the fire. The manual selection means could also serve to evacuate the building or portions of the building for non‐fire related emergencies. The manual selection means is required to provide a non‐latching output(s) from the fire alarm system to the elevator system to prevent the need for fire alarm system reset upon a wrong or unwanted manual selection of a floor(s). 21.6.2.5* Fire Alarm Output Signals to Elevator System. (A) Output from the fire alarm system to the elevator system shall identify each floor with an active alarm. (B) Output from the fire alarm system to the elevator system shall include the following: (1) The floor with the first activated automatic fire alarm initiating device. (2) Floor(s) with any subsequently activated automatic fire alarm initiating device(s). (3) Floor(s) selected by manual means from the FCC. (C) The identified floor(s) shall be displayed on the building fire alarm system annunciator at the FCC or on a listed non‐fire alarm system annunciator or other annunciator as approved by the authority having jurisdiction. A.21.6.2.5 The fire alarm system uses the floor identification to automatically establish an elevator evacuation zone for voice messaging purposes. The elevator system also uses the floor identification to determine the contiguous block of floors to be evacuated (elevator evacuation zone). So, that zone would typically be the floor of an active alarm plus two floors above and two floors below the floor with the active alarm for a total of five floors or as otherwise determined by the authority having jurisdiction. The elevator evacuation zone is updated to reflect changing conditions as indicated by the output signal(s). This information is sent to the elevator system and also used for occupant notification. The output signals from the fire alarm system can be in the form of contact closures or serial communications or other acceptable means approved by the authority having jurisdiction. Coordination needs to be provided between the fire alarm system installer, the elevator system installer, and the authority having jurisdiction. 21.6.2.6* Occupant Notification. The in‐building fire emergency voice/alarm communications system shall transmit messages coordinated with the elevator system’s text displays in all elevator lobbies. (A) Automatic voice evacuation messages shall be transmitted to the elevator evacuation zone to indicate the need to evacuate and that elevator service is available. (B) Automatic voice messages shall be transmitted to the floors not being evacuated within the specific group of elevator(s) performing OEO, to inform occupants that elevator service is not available. (C)* Automatic voice messages shall be transmitted to the elevator evacuation zone to indicate that elevator service is not available when all elevators serving that elevator evacuation zone are out of service. (D) All automatic voice messages shall be coordinated so as not to be in conflict with the text displays provided separately by the elevator system. (E)* When required by the building code, the emergency voice/alarm communications system’s speaker(s)

located in each OEE lobby, shall be connected to a separate notification zone for manual paging only.

Page 4 of 6

Individual paging zones per each OEE lobby on each floor, grouped paging zone for all OEE lobbies on a floor,

or vertical paging zone for each elevator group shall be permitted as approved by the authority having

jurisdiction.

(F) Visible notification appliances (strobes) shall comply with 24.5.17.3(1), (2), and (3). A.21.6.2.6 Prerecorded automatic voice messages provided by the in‐building fire emergency voice/alarm communications system need to be coordinated with the text displays provided separately by the elevator system to all affected elevator lobbies and floors served by the elevator(s) operating in OEO so that occupants will understand what to expect and how to react. Additional visual information will be provided in each affected elevator lobby by the elevator system to further inform occupants of the status of the elevators. Refer also to 24.3.6 and associated Annex material (Messages for One‐Way Emergency Communications Systems) for additional information. It is important to note that all elevator lobbies served by elevator(s) operating in OEO, both within the elevator evacuation zone and on other floors outside that zone, will be considered as affected lobbies and they will be provided with variable messages generated by the elevator system. The fire alarm system will not provide automatic voice messages in the affected elevator lobbies, but rather it will provide automatic messages to all floors having those affected lobbies via audible appliances located outside those lobbies. The messages provided by the fire alarm system and the elevator system on the affected floors and lobbies must be coordinated so as not to conflict each other. It is especially important to address additional automatic or manual alarm actuation(s) and the impact on expanding the elevator evacuation zone and the corresponding voice messaging that has to adjust to the change. Sample voice message content to be added to normal message (to be coordinated with the variable message display provided by the elevator contractor): Condition: Specific block of floors being evacuated “Elevators and stairs are available for evacuation” Condition: Floors not in the elevator evacuation zone within an elevator group performing OEO “Elevators not available, they are temporarily dedicated to other floors” Condition: On the discharge level “Elevators dedicated to evacuation. Do not enter elevator” Condition: If some elevators have been recalled but other elevator(s) are still available: “Elevators and stairs are available for evacuation” Condition: If all elevators serving a floor or elevator evacuation zone are recalled: “Elevators are out of service, Use stairs to evacuate” Voice messaging is permitted to all other floor(s) in the building not in the elevator evacuation zone and not served by elevator(s) performing OEO in accordance with the facility emergency response plan approved by the authority having jurisdiction.

Page 5 of 6

For further information on voice messaging strategies refer to “Incorporating Emergency Messaging Guidance into Practice” A.21.6.2.6(C) This new message will require a signal(s) from the elevator system to the fire alarm system. This signal(s) will indicate to the fire alarm system that all elevators serving an elevator evacuation zone are out of service due to Phase I Emergency Recall operation or due to other elevator out‐of‐service associated condition(s) such as inspection operation, malfunction, etc. A.21.6.2.6(E) The emergency voice/alarm communications system’s speaker(s) located in each OEE lobby are not permitted to transmit automatic voice messages since they may interrupt occupants using the required OEE elevator lobby two way communication system. Therefore, manual paging zones are required for those speakers by applicable building code(s). The specific zone selection will be performed from a fire alarm system paging panel located in the FCC. Since a very large number of individual paging zones may be required, it is permitted to group all OEE lobbies’ speakers per floor or vertically per elevator group as a single paging zone. The OEE lobby paging zone will be dedicated to speakers which only serve OEE lobbies and will be separate from all other speakers outside of an OEE lobby. 21.6.2.7 Total Evacuation. A means to initiate total building evacuation, labeled “ELEVATOR TOTAL BUILDING EVACUATION” shall be provided at the FCC. 21.6.2.7.1 When this means is actuated, the fire alarm system shall provide a signal to the elevator system indicating that all floors in the building are to be evacuated. 21.6.2.7.2 The in‐building fire emergency voice/alarm communications system shall transmit an evacuation message throughout the building to indicate the need to evacuate. 21.6.2.8* Suspension of OEO for an Individual Elevator or Group of Elevators. 21.6.2.8.1 OEO shall be suspended for an individual elevator or group of elevators when an individual elevator or a group of elevators have been manually recalled via an elevator system designated key operated switch(s) labeled “Car Fire Recall” or “Group Fire Recall”. 21.6.2.8.2 When OEO has been suspended as in 21.6.2.8.1, the in‐building fire emergency voice/alarm communications system shall transmit messages coordinated with the elevator system’s text displays in compliance with 21.6.2.6. A.21.6.2.8 Suspension of OEO can occur when an individual elevator or group of elevators is temporarily recalled by manual means using key operated switch(s) designated as “Car Fire Recall” or “Group Fire Recall”. It is important to recognize that OEO continues operation using the available elevator(s). The affected elevator(s) will return to OEO operation when the individual “Car Fire Recall” or the “Group Fire Recall” key switch has been turned off. 21.6.2.9* Partial Termination of OEO. 21.6.2.9.1 OEO shall be terminated for a specific group of elevator(s) when the signal(s) provided in 21.3.13.1 and 21.3.13.2 associated with this group of elevator(s), has initiated Phase I Emergency Recall Operation for this group of elevator(s).

Page 6 of 6

21.6.2.9.2 When OEO has been partially terminated, the in‐building fire emergency voice/alarm communications system shall transmit messages coordinated with the elevator system’s text displays in compliance with 21.6.2.6. A.21.6.2.9 Partial termination can occur when a particular group of elevators has been taken out of service because they have been recalled under automatic Phase 1 Emergency Recall, but other elevator(s) in the elevator evacuation zone are still available for evacuation. 21.6.2.10 Total Termination of OEO. 21.6.2.10.1 OEO shall be terminated for all elevators in the building upon reset of the fire alarm system. 21.6.2.10.2* OEO shall be terminated when there are no elevators available for self‐evacuation. A.21.6.2.10.2 There are several instances where signals must be received from the elevator system. One of these is when the Phase I Emergency Recall key switch is used to manually initiate recall for all elevators. In this case, the fire alarm system needs to know that it must cancel or change OEO voice messaging. Another situation requiring a signal from the elevator system is when, for whatever reason, the elevator system cannot provide the intended operation. In this case the fire alarm system needs to know so it does not provide incorrect messaging to a floor(s). See also Annex A.21.6.2.6(c).


Add new Section 21.8 and renumber subsequent paragraphs:

21.8 When any device or function is disconnected for purposes of testing or maintenance, a trouble signalshall be generated.


NFPA 72 only requires that a disconnect switch for releasing systems must provide a trouble signal when disconnected (23.8.5.11.1). This should be required for any disconnect switch to ensure it will be reconnected.

Note to staff: After submitting this PI, Terra View showed "Add new section after 21.8" . This should be the new 21.8.


Submitter Full Name: Thomas Hammerberg

Organization: Automatic Fire Alarm Association

Affilliation: Automatic Fire Alarm Association

Street Address:

City:

State:

Zip:



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


Low Speed High Velocity (LSHV) Fans

LSHV Fans shall shut down upon activation of the buildings fire alarm system.


The velocity that is created by these fans can have a significant impact on fire growth. It also can interfere with the spray from sprinklers.These new fans have been addressed in NFPA 13 but have yet to be identified in NFPA 72.


Submitter Full Name: Brad Geistler

Organization: Wixom Fire Department

Street Address:

City:

State:

Zip:

Submittal Date: Thu Jun 09 09:44:31 EDT 2016


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



Type your content here ...NFPA 72 21.11 Vehicle Motor Fueling Stations, Emergency Stops.

21.11.1Where motor fueling facilities have fire alarm systems installed and motor fueling capabilities withemergency stop override protection systems for fuel dispensing. The fire alarm system and the emergencystop system shall be interconnected to each other.


There is no current mandate for such interconnection between the emergency stops for fueling pumps and the fire alarm system of fueling stations. When this connection is incorporated, the fueling pumps shut off when the alarm is activated, without the interconnection, vehicles could continue to actively be fueled (fuel dispensing could continue). If interconnected, either the fire alarm or the emergency stop would stop the fuel pumps.

By combining these actions a potential for creating a greater incident could be lessened.


Submitter Full Name: Robert Tribbie

Organization: West Virginia State Fire Mar

Street Address:

City:

State:

Zip:

Submittal Date: Wed Dec 23 14:14:19 EST 2015


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


23.1.1*

The application, installation, and performance of fire alarm systems within protected premises , includingfire alarm and supervisory signals, shall comply with the requirements of this chapter.


This Public Input (PI) is relocating existing material that is within the 2015 edition of NFPA 720 into the applicable section of NFPA 72. The PI is not changing the technical requirements of NFPA 720 but is relocating material from NFPA 720 into NFPA 72. This change is being made in response to a 2015 the NFPA Standards Council decision to merge NFPA 720 into NFPA 72 because the two standards have similar requirements and extracted material. The problem with maintaining two separate standards is with every new edition of NFPA 720 updating requirements and extracts from NFPA 72 has become a very time consuming effort that is prone to error for both NFPA Staff and the NFPA 720 Technical Committee. The scope and title of NFPA 72 was intentionally changed in 2010 to be broad enough to include CO as well as other signaling needs.

This PI is being submitted on behalf of the NFPA 720/72 Consolidation Task Group.


Submitter Full Name: Richard Roberts

Organization: Honeywell Fire Safety

Street Address:

City:

State:

Zip:

Submittal Date: Fri May 27 16:34:53 EDT 2016


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


23.1.2

The requirements of Chapters 7 , 10 , 12 , 17 , 18 , 21 , 24 , and 26 shall apply unless otherwisenoted in this chapter.





Public Input No. 722-NFPA 72-2016 [New Section after 1.3.4] would relocate these requirements to Ch 1




Street Address:

City:

State:

Zip:



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


23.2 General.

23.2.1* Purpose.

The systems covered in Chapter 23 shall be for the protection of life or property, or both, by indicating theexistence of heat, fire, smoke, carbon monoxide or other emergencies impacting the protected premises.

23.2.2 Software and Firmware Control.

23.2.2.1

A record of installed software and firmware version numbers shall be prepared and maintained inaccordance with Sections 7.5 and 7.7.

23.2.2.1.1*

Software and firmware within the fire alarm control system that interfaces to other required software orfirmware shall be functionally compatible.

23.2.2.1.2*

The compatible software or firmware versions shall be documented at the initial acceptance test and at anyreacceptance tests.

23.2.2.2*

All software and firmware shall be protected from unauthorized changes.

23.2.2.3

All changes shall be tested in accordance with 14.4.2.







Street Address:

City:

State:

Zip:



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


23.3 System Features.

The features required for a protected premises fire alarm system shall be documented as a part of thesystem design and shall be determined in accordance with 23.3.1 through 23.3.3.

23.3.1 Required Systems.

Features for required systems shall be based on the requirements of other applicable codes or statutesthat have been adopted by the enforcing jurisdiction.

23.3.2* Nonrequired (Voluntary) Systems and Components.

The features for a nonrequired system shall be established by the system designer on the basis of thegoals and objectives intended by the system owner.

23.3.2.1

Nonrequired protected premises systems and components shall meet the requirements of this Code.

23.3.2.2

Nonrequired systems and components shall be identified on the record drawings required in 7.2.1(14).

23.3.3 Required Features.

23.3.3.1* Building Fire Alarm Systems.

Protected premises fire alarm systems that serve the general fire alarm needs of a building or buildingsshall include one or more of the following systems or functions:

(1) Manual fire alarm signal initiation

(2) Automatic fire alarm and supervisory signal initiation

(3) Monitoring of abnormal conditions in fire suppression systems

(4) Activation of fire suppression systems

(5) Activation of emergency control functions

(6) Activation of fire alarm notification appliances

(7) In-building fire emergency voice/alarm communications

(8) Guard’s tour supervisory service

(9) Process monitoring supervisory systems

(10) Activation of off-premises signals

(11) Combination systems

23.3.3.2* Dedicated Function Fire Alarm Systems.

23.3.3.2.1

In facilities without a building fire alarm system, a dedicated function fire alarm system shall be permittedand shall not be required to include other functions or features of a building fire alarm system.

23.3.3.2.2

Where a dedicated function fire alarm system exists and a building fire alarm system is subsequentlyinstalled, the systems shall be interconnected and comply with 23.8.2.


This Public Input (PI) is relocating existing material that is within the 2015 edition of NFPA 720 into the applicable section of NFPA 72. The PI is not changing the technical requirements of NFPA 720 but is relocating material from


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

NFPA 720 into NFPA 72. This change is being made in response to a 2015 the NFPA Standards Council decision to merge NFPA 720 into NFPA 72 because the two standards have similar requirements and extracted material. The problem with maintaining two separate standards is with every new edition of NFPA 720 updating requirements and extracts from NFPA 72 has become a very time consuming effort that is prone to error for both NFPA Staff and the NFPA 720 Technical Committee. The scope and title of NFPA 72 was intentionally changed in 2010 to be broad enough to include CO as well as other signaling needs.





Street Address:

City:

State:

Zip:



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


23.3.3.1* Building Fire Alarm Systems.

Protected premises fire alarm systems that serve the general fire alarm signaling needs of a building orbuildings shall include one or more of the following systems or functions:

(1) Manual fire alarm signal initiation

(2) Automatic fire alarm and supervisory signal initiation

(3) Monitoring of abnormal conditions in fire suppression systems

(4) Activation of fire suppression systems

(5) Activation of emergency control functions

(6) Activation of fire alarm notification appliances if required

(7) In-building fire emergency voice/alarm communications

(8) Guard’s tour supervisory service

(9) Process monitoring supervisory systems

(10) Activation of off-premises signals

(11) Combination systems







Street Address:

City:

State:

Zip:



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


23.3.3.2* Dedicated Function Fire Alarm Systems.

23.3.3.2.1

In facilities without a building fire alarm system, a dedicated function fire alarm system shall be permittedand shall not be required to include other functions or features of a building fire alarm system.

23.3.3.2.2

Where a dedicated function fire alarm system exists and a building fire alarm system is subsequentlyinstalled, the systems shall be interconnected and comply with 23.8.2.







Street Address:

City:

State:

Zip:



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


23.4.1 Purpose.

Section 23.4 provides information that shall be used in the design and installation of protected premisesfire alarm systems for the protection of life and property.







Street Address:

City:

State:

Zip:



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


23.4.1 * Purpose.

Section 23.4 provides information that shall be used in the design and installation of protected premisesfire alarm systems for the protection of life and property.



Lacey_Annex_A_material_for_23-4.docx


To clarify importance of this information being established prior to contractors bidding a project and the importance that it be based around the user’s needs and benefit. Currently there is nothing that helps to identify who is responsible for establishing this criteria. It is not a contractors responsibility to establish during a bid, and not an AHJ’s to make up job to job.




Street Address:

City:

State:

Zip:

Submittal Date: Mon Mar 14 16:16:32 EDT 2016


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

Proposed Annex A material for: 23.4.1 Purpose

A.23.4.1 Establishing system performance requires an analysis of the facility, user, occupants,

hazards, construction, and intended operational functions. When an owner/user hires a designer(s) to

prepare bid documents, it is essential that the designer(s) establish the performance criteria for the

system based around the needs of the owner/user. For projects being bid, it should not be the

contractor’s responsibility to establish this criteria during or after a project is bid. Establishing

performance criteria during/after a project is bid seldom works out in the best interest of the

user/occupant/hazard. AHJ’s who are going to require specific performance criteria based on occupancy

and/or occupant loads should do so in written policy/regulation/ordinance.

Reason:

To clarify importance of this information being established prior to contractors bidding a project and the

importance that it be based around the user’s needs and benefit. Currently there is little which identifies

who is responsible for establishing this criteria and it is frequently left up to the contractor during

bidding.

Submitted by Scott Lacey


23.6.1.1

For the purpose of this section, each floor of the building shall be considered a separate zone.


Remove paragraph. The current paragraph requires the designer to provide one SLC per floor. This should not be mandated for a small multi-story building that may only have a few SLC devices. Also, if I have a two-story "L" shaped building I should be allowed to run down one wing of first floor and then up to second floor and back along the same wing using one SLC for south wing and then say one SLC to protect both floors of west wing - each wing being a Class A loop. Has the committee provided justification that current floor requirement is safer than my proposed circuit that would not be allowed? Current requirement mandates one zone per floor which could be Class B, but prohibits me from splitting floors using a Class A loop while limiting wire/conduit length. I run a lot of Class A conduit circuits and the current language is not favorable for wire and conduit routing in hotel/apartment/wing shaped buildings. The designer should be allowed to define the "zones" based on project. Proposed circuiting should not require a formal performance-based design to be submitted.




Street Address:

City:

State:

Zip:



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


23.6.1.3(3)* An existing SLC that is having additional initiating devices connected to it which wasnot required to meet the requirements of 23.6.1 when it was originally approved.


Many existing systems may not be capable of, or easily modified to fulfill the requirement of 23.6.1. If an SLC in an existing building is being added to, or having a minor modification to accommodate a tenant and the SLC is currently covering multiple Zones as defined in 23.6.1.1 or 23.6.1.2 then significant effort may be required to reinstall or reroute cable for the SLC. Additionally, isolation modules have different specifications from different manufacturers. Some manufacturers require an isolation module every 25 address and there are modules that take 3 address in the system. If a previously approved system is large enough the extra addresses required by the installation of isolation modules may exceed the system limitations of the number of address available, where prior to this requirement the system was within the limitations of the addresses available.

Please see the two scenarios below which I believe may help illustrate my point.

Scenario 1 – A six story R-1 (Hotel) covering a total of approximately 190,000 square feet was electively replacing the single station smoke alarms inside of all guest rooms with a system smoke detector monitored by the FACU. The system was installed two years prior to this requirement. This accounted for approximately 500 new addressable detectors on the system which I believe should have been held to the performance requirements of 23.6.1 and was shown as such. However, the 800 plus existing devices throughout the other portions of the building were not being altered and outside of the scope of work. If the existing areas, which were not inside the project’s scope, were required to adhere to 23.6.1 the expense, time, and effort required to modify the existing cabling throughout the building, as well as cards added to the FACU would have been so great the building owner would likely not be willing to do any work on the system whatsoever.

Scenario 2 – A 1,200 square foot tenant space inside of a 200,000 square foot Covered Mall was being remodeled including adding new dressing rooms. This required a new remote power supply which required a relay module to activate the new remote power supply, monitoring module, and a smoke detector. In total 3 new addressable devices were being added to a system already supporting approximately 150 addressable devices which have been previously approved as Class B circuits. Is it practical for the owner of the Mall to be required, possibly by an AHJ, to change the existing cable design of the Mall so it may be in compliance with 26.3.1 for the addition of 3 devices?



Public Input No. 590-NFPA 72-2016 [New Section after A.23.6.1.3]


Submitter Full Name: Harrison Bradstreet

Organization: Fire Safety Consultants

Affilliation: Illinois Fire Inspectors Association

Street Address:

City:

State:

Zip:



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

Public Input No. 412-NFPA 72-2016 [ Section No. 23.6.2 [Excluding any Sub-Sections] ]

* No area or zone shall be serviced solely by a single device where Class N pathways are deployed, suchthat a single device failure would render an area or zone incapable of initiating input signals or receivingoutput signals.

Exception: When a risk analysis is performed to determine areas where a single device is sufficient andacceptable to the authority having jurisdiction.



23_6_2_Annex.docx


The annex addition seeks to establish a context for the requirement of 23.6.2. For some, this requirement suggests that at least twice as many devices must be applied to a Class N installation as compared a Class A, B, or X installation. From certain perspectives, for some occupancies, readers have reached this conclusion. Instead, as a design requirement, this can be established as a necessary Class N design decision based on risk, and an understanding of these risks in comparison with already accepted risk and requirements. This is already established for current FA design in consideration of the purchase and deployment of a Class A or X based Fire Alarm, in comparison to a Class B system. This annex material seeks clarify this point for readers in relation to Class N, and to establish a rationale and an example of that rationale for potentially requiring additional Class N devices, in consideration of the differences in risk presented by the different allowed pathway classes.



Public Input No. 416-NFPA 72-2016 [Section No. 23.6.2 [Excluding any Sub-Sections]]




Street Address:

City:

State:

Zip:



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

A.23.6.2 The intention of this paragraph is to ensure that care is taken when designing Class N systems

to mitigate any additional risk that could be present when zone is serviced by a single Class N device. A

"zone" is a defined term (see 3.3.317) that presents a "zone" as a “defined area”. Since Class N allows

for the loss of a single device based on second ground fault in the Class N pathway without first

establishing a trouble condition at the occurrence of the first ground fault, the risk of a loss of

functionality of isolated devices due to multiple ground faults occurring sequentially must be considered

in designs of a Class N network of devices. However, this clause is not intended to necessarily require

the installation of twice as many (or more) Class N devices as compared to a design based on Class A, B,

or X pathways. The failure of a single Class N device must still be alerted with a trouble signal. It is not

the intention to establish a disproportionate burden of reliability or cost for Class N as compared to the

other allowable pathway classes. Other pathway classes are permitted to lose all devices in a zone (see

23.6.1), while Class N is only permitted to lose one device. Yet there might be instances where it is

appropriate to require additional Class N devices. For example, a large space where it is otherwise

impractical to expect users to find a second pull station should one pull station be in failure. Ultimately,

the term “zone” as used in this context is a "defined area" that at most is bounded by floors, fire or

smoke barriers, and exterior walls. Depending on the facility and the AHJ and the risks for that

occupancy, this defined area may be smaller then that, but not be larger. The specifics of the "defined

area" must be established by the system designer and approved by the authority having jurisdiction,

based on an understanding of the different risks presented by a Class N design, as compared to a Class

A, B, or X design.


No area or zone shall be serviced solely by a single device where Class N pathways are deployed, suchthat a single device failure would render an area or a zone incapable of initiating input signals or receivingoutput signals.

Exception: When a risk analysis is performed to determine areas where a single device is sufficient andacceptable to the authority having jurisdiction.


The term "area" is not defined in chapter 3. A dictionary definition of area is "a section of space within a building, room, etc." (From <http://www.merriam-webster.com/dictionary/area> ) is too broad to be practically applied to this requirement. Further the word "zone" is a defined term in chapter 3, as a "defined area …". Chapter 3 goes on to establish parameters for the term "defined area". But the requirement should not be conflicted between the use of the word "area" with the term "defined area". This differentiation could lead to confusion (as to the meaning of the difference between "area" and "defined area"). This public input seeks to improve clarity by deleting the redundant word and relying on the defined term rather then the undefined one.



Public Input No. 412-NFPA 72-2016 [Section No. 23.6.2 [Excluding any Sub-Sections]] Same Paragraph




Street Address:

City:

State:

Zip:



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


Class N pathways shall be required to use shared pathway Level 3 as specified in 12.5.4 except aspermitted by 23.6.3.1 through 23 . 6.3.8.


The criteria for the exception is presented in 23.6.3.1. In 23.6.3.1 the requirements are presented textually. The paragraph references and the textual references match. So for clarity, the paragraph references and the textual references are presented together rather then in two separate paragraphs.



Public Input No. 422-NFPA 72-2016[Section No. 23.6.3.1]

These two paragraphs work together to create the exception andthen the criteria for the exception




Street Address:

City:

State:

Zip:



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


23.6.3.1 Level 1 and Level 2.

Shared pathways Levels 1 and 2 shall be permitted subject to a thorough written analysis of the risks, thedeployment, change control, and maintenance plans, roles and responsibilities, and a deployment plan asidentified other risks as required in 23.6.3.3 through 23.6.3.8 and when approved by an AHJ inconsideration of the analysis, maintenance, and deployment plans the AHJ .


Corrected the references to cover the intended range of requirements. Also improved the clarity by listing the relevant requirements in order and completely for the specific things covered by 23.6.3.3.through 23.6.3.8. Also 23.6.3.2, accessibility was omitted from this list so that it could stand alone as a requirement, even if the Class N deployment was based on Shared Pathways level 3.



Public Input No. 421-NFPA 72-2016 [Section No. 23.6.3 [Excluding any Sub-Sections]]

Public Input No. 425-NFPA 72-2016 [Sections 23.6.3.1, 23.6.3.2, 23.6.3.3, 23.6.3.4,23.6.3.5, ...]




Street Address:

City:

State:

Zip:



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

Public Input No. 425-NFPA 72-2016 [ Sections 23.6.3.1, 23.6.3.2, 23.6.3.3, 23.6.3.4,

23.6.3.5, ... ]

Sections 23.6.3.1, 23.6.3.2, 23.6.3.3, 23.6.3.4, 23.6.3.5, 23.6.3.6, 23.6.3.7, 23.6.3.8

23.6.3.1 Level 1 and Level 2.

Shared pathways Levels 1 and 2 shall be permitted subject to a thorough written analysis of the risks, themaintenance plans, roles and responsibilities, and a deployment plan as identified in 23.6.3.3 and whenapproved by an AHJ in consideration of the analysis, maintenance, and deployment plans.

23.6.3.2 Accessibility.

Class N pathways shall not be accessible to the general public for any purpose or building occupants forany purpose other than specified in the analysis, maintenance, and deployment plans.

23.6.3.3 Deployment Plan.

23.6.3.3.1

All equipment connected to shared pathways shall be documented in the deployment plan.

23.6.3.3.1.1

The documentation shall include manufacturer, model, listings, and intended purpose and reason forinclusion on the shared network.

23.6.3.3.1.2

The deployment plan shall identify how and where each piece of equipment is connected.

23.6.3.3.2

All connection ports, used or spare, where any unauthorized or unintended equipment may be added to theshared network, shall be identified as for use only by equipment consistent with the deployment plan.

23.6.3.4 Change Control Plan.

Configuration upgrades and updates shall be governed by a change control plan, which determines thepolicy and procedure of the change and ensures that all documentation is correspondingly updated.

23.6.3.5 Management Organization.

23.6.3.5.1

An organization shall be established and maintained to manage the life safety network and shall performthe following tasks:

(1) Contain members appropriately certified by each manufacturer of the equipment and devicesdeployed on shared pathways to maintain such a network

(2) Service and maintain all shared Class N pathways

(3) Maintain the deployment and shared pathways plan for the lifetime of the shared pathways

23.6.3.5.2

Other service personnel, even when certified to service a specific system (i.e., fire alarm or MNS) shall beauthorized and managed by this organization to ensure any outages of any system are planned, managed,and documented and appropriate steps are taken during outages to provide alternate protection of life andproperty.

23.6.3.6 Analysis.


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

23.6.3.6.1

The analysis shall be performed to determine and document communications capability as follows:

(1) Calculation of minimum required bandwidth such that all life safety systems can be guaranteed tooperate simultaneously and within required time limits

(2) Total bandwidth provided by the network

(3) Future bandwidth requirements

(4) Method of providing and maintaining the prioritization of life safety traffic over non–life safety traffic

23.6.3.6.2

The analysis shall determine and document the power distribution capability as follows:

(1) The methods provided to maintain power to all shared pathway equipment

(2) A calculation of power requirements of all connected equipment

(3) Secondary power capacities provided to maintain all life safety equipment with minimum operationalcapacity in accordance with 10.6.7.2.1.2

(4) Methods to disengage any non–life safety equipment in the event of emergency operation if requiredto support the minimum operational capacity requirements

23.6.3.7 Maintenance Plan.

23.6.3.7.1

The maintenance plan shall identify policy and procedures to monitor, maintain, test, and control change ofthe shared pathways.

23.6.3.7.2

Written procedures shall be presented in maintenance plans to govern the following:

(1) Physical access to all parts of the Class N network equipment (i.e., switches, ports, server,controllers, devices, or components)

(2) Electronic access to all parts of the Class N network (i.e., passwords, addresses)

(3)

(4) Upgrade procedures

(5) Change control procedures, with consideration given to require an updated risk analysis ifnecessary

(6) Prioritization and/or segregation configuration information for life safety traffic

(7) Maintenance and testing plans to ensure the minimum operational capacity with respect tosecondary power is maintained

(8) Other service, maintenance, or reconfiguration plans for any connected equipment

23.6.3.8 Other Risks.

Any other identifiable risk as required by the AHJ shall be discussed and addressed in the analysis andmaintenance plans.


These sections are proposed to be moved to a new Chapter 15 that specifically targets Class N Ethernet. When these sections were written by the Class N Task Group, it was specifically in the context of Class N Ethernet. But Class N is not necessary Ethernet. Class N is a list of performance requirements that can be implemented in multiple ways; but also in ways more fundamentally consistent with Ethernet standards. However, if Class N were to be deployed by some other technology other then Ethernet, there would not tend to be these requirements in

* Service outage impairment process with notices of impairment and contingency plans foraffected systems


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

the code at all; any more then there are these requirements for Class A, B, or X. By moving these paragraphs to a Class N Ethernet specific location in the code, we restore specific technology independence to Chapter 23. Because the context for these paragraphs was Ethernet Class N, but this was not stated in the code, these paragraphs occur as out of place.

Note, 23.6.3.1 was changed in a related PI. This change is intended to propagate to Chapter 15. But none of the other paragraphs were intended to be changed, nor their purpose altered. They are just intended to be moved.



Public Input No. 420-NFPA 72-2016[Chapter 15]

Intended to move these paragraphs to the proposed Chapter15.

Public Input No. 422-NFPA 72-2016[Section No. 23.6.3.1]

The changes proposed for 23.6.3.1 are intended to be movedto Chapter 15 as well.




Street Address:

City:

State:

Zip:



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


23.8.2* Fire Alarm Control Units.

23.8.2.1

Fire alarm systems Systems shall be permitted to combine all detection, notification, and auxiliaryfunctions in a single system or be a combination of component subsystems.

23.8.2.2

Except as permitted in 23.8.2.3, the fire alarm systems components shall be permitted to share controlequipment or shall be able to operate as stand-alone subsystems, but shall be arranged to function as asingle system in accordance with 23.8.2.4 through 23.8.2.10.

23.8.2.3

Where the building is not served by a building fire alarm system, independent dedicated function fire alarmsystems and/or releasing fire alarm systems shall not be required to be interconnected to function as asingle system.

23.8.2.4

All component subsystems shall be capable of simultaneous, full-load operation without degradation of therequired overall system performance.

23.8.2.5

The method of interconnection of fire alarm control units shall meet the monitoring requirements ofSection 12.6, NFPA 70 Article 725 and NFPA 70 Article 760, and shall be achieved by the followingrecognized means:

(1) Electrical contacts listed for the connected load

(2) Data communications over a signaling line circuit(s) dedicated to the fire alarm or shared with otherpremises operating systems

(3) Other listed methods

23.8.2.6

Where the signaling line circuit is shared by other premises operating systems, operation shall be inaccordance with 23.8.4.

23.8.2.6.1

All signal control and transport equipment (such as routers and servers) located in a critical fire alarm oremergency control function interface device signaling path shall be listed for fire alarm service, unless thefollowing conditions are met:

(1) The equipment meets the performance requirements of 10.3.5.

(2) The equipment is provided with primary and secondary power and monitored for integrity as requiredin Section 10.6, 10.6.9, Section 10.18, and Section 12.6.

(3) All programming and configuration ensure a fire alarm system actuation time as required in 10.11.1.

(4) System bandwidth is monitored to confirm that all communications between equipment that is criticalto the operation of the fire alarm system or emergency control function interface devices take placewithin 10 seconds; failure shall be indicated within 200 seconds.

(5) Failure of any equipment that is critical to the operation of the fire alarm system or emergency controlfunction interface devices is indicated at the master fire alarm control unit within 200 seconds.

23.8.2.6.2

A listed barrier gateway, integral with or attached to each control unit or group of control units, asappropriate, shall be provided to prevent the other systems from interfering with or controlling the fire alarmsystem.


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

23.8.2.6.3

Where Class N is utilized for shared equipment, the requirements in 23.6.3 shall also apply.

23.8.2.7

Each interconnected fire alarm control unit shall be separately monitored for alarm, supervisory, andtrouble conditions with supervised pathways that are in accordance with the manufacturers’ publishedinstructions.

23.8.2.7.1

Alarm conditions on interconnected fire alarm control units shall annunciate as alarm signals and initiate theevacuation signals.

23.8.2.7.2

Supervisory conditions on interconnected fire alarm control units shall annunciate as supervisory signals.

23.8.2.7.3

Trouble conditions on interconnected fire alarm control units shall annunciate as trouble signals.

23.8.2.7.4*

Where supervised pathways between interconnected fire alarm control units is not achievable, a supervisedannunciator shall be installed adjacent to control unit(s) to annunciate the status of the each control unit.

23.8.2.8

Interconnected fire alarm control unit alarm signals units shall be permitted to be monitored by zone or bycombined common signals.

23.8.2.9

Protected premises fire alarm control units shall be capable of being reset or silenced only from the firealarm control unit at the protected premises, unless otherwise permitted by 23.8.2.10.

23.8.2.9.1

Where multiple control units of the same manufacturer are interconnected in a network arrangement andserve the same protected premises, the control units shall be arranged to be reset or silenced from onelocation.

23.8.2.9.2

Where multiple control units of the different manufacturers are interconnected in accordance with 23.8.2.5through 23.8.2.8 and serve the same protected premises, the control units shall be permitted to be reset orsilenced individually at each control unit.

23.8.2.9.3

Resetting procedures shall be documented and permanently posted beside each control unit andannunciator.

23.8.2.10

Remote resetting and silencing of a fire alarm control unit from other than the protected premises shall bepermitted with the approval of the authority having jurisdiction.

23.8.2.11 An initiating devices with integral sounders shall be permitted to be silenced locally, providedthe control panel continues to indicate an alarm function. <5.8.2.9>

23.8.2.11.1 If the carbon monoxide dissipates, the initiating device shall return normal mode. <5.8.2.9.1


This Public Input (PI) is relocating existing material that is within the 2015 edition of NFPA 720 into the applicable section of NFPA 72. The PI is not changing the technical requirements of NFPA 720 but is relocating material from NFPA 720 into NFPA 72. This change is being made in response to a 2015 the NFPA Standards Council decision to merge NFPA 720 into NFPA 72 because the two standards have similar requirements and extracted material. The problem with maintaining two separate standards is with every new edition of NFPA 720 updating requirements and extracts from NFPA 72 has become a very time consuming effort that is prone to error for both NFPA Staff and the NFPA


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

720 Technical Committee. The scope and title of NFPA 72 was intentionally changed in 2010 to be broad enough to include CO as well as other signaling needs.





Street Address:

City:

State:

Zip:



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


23.8.3 Protected Premises Fire Alarm Systems Interconnected with Dwelling Unit Fire WarningEquipment.

23.8.3.1

A protected premises fire alarm system shall be permitted to be interconnected to a household fire alarmsystem(s) for the purpose of activating the notification appliances connected to the household fire alarmsystem(s).

23.8.3.2

The activation of dwelling unit smoke alarms shall only be permitted to be displayed at the protectedpremises control unit and annunciators as supervisory signals.

23.8.3.3

If interconnected, an alarm condition at the protected premises fire alarm system shall cause the fire alarmnotification appliance(s) within the family living unit of the dwelling unit fire warning system to becomeenergized. The notification appliances shall remain energized until the protected premises fire alarmsystem is silenced or reset.

23.8.3.4

The interconnection circuit or path from the protected premises fire alarm system to the dwelling unit firewarning system shall be monitored for integrity by the protected premises fire alarm system in accordancewith Section 12.6.

23.8.3.5

An alarm condition occurring at the dwelling unit fire warning system or the operation of any test switchesprovided as part of the dwelling unit fire warning equipment shall not cause an alarm condition at theprotected premises fire alarm system.







Street Address:

City:

State:

Zip:

Submittal Date: Sat May 28 09:20:55 EDT 2016


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


23.8.4 Combination Systems

23.8.4.1* Fire alarm systems shall be permitted to share components, equipment, circuitry, and installationwiring with non-fire alarm systems.

23.8.4.2 Building System Information Unit (BSIU)

23.8.4.2.1* A Building System Information Unit which only displays information and events from the firealarm system and other building non-fire systems need only be listed to ANSI/UL 60950, InformationTechnology Equipment - Part 1: General Requirements, ANSI/UL 62368-1 Audio/Video, Information andCommunication Technology Equipment-Part 1: Safety Requirements, or equivalent.

23.8.4.2.2 All the requirements of 23.8.4.2.2.1 - 23.6.4.2.2.5 are to be met when a BSIU is capable ofcontrolling an interconnected fire alarm system through acknowledge, silence, and reset controls.

23.8.4.2.2.1 The equipment forming the Building Sytems Information Unit shall be listed to ANSI/UL 60950,Information Technology Equipment-Part 1: General Requirements, or ANSI/UL 62368-1 Audio/Video,Information and Communication Technology Equipment-Part 1: Safety or equivalent requirements.

23.8.4.2.2.2 A FACP Fire Alarm Control Unit (FACU) controlling the entire fire alarm system is locatedwithin the same room as the BSIU.

23.8.4.2.2.3 A listed barrier connection shall be provided in the communication path from the Fire AlarmControl Unit and the BSIU.

23.8.4.2.2.4 For non-fire equipment not listed to the performance requirements specified in 10.3.5, therequirements of 23.8.4.4.1 through 23.8.4.4.4 shall apply.

23.8.4.2.2.5 The application software for the BSIU shall be listed to ANSI/UL 864, Control Units andAccessories for Fire Alarm Systems.



BSIU_Diagram_FINAL_6_26_16_.pdf BSIU Diagram -


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



Organization: Nema

Street Address:

City:

State:

Zip:



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


23.8.4 Combination Systems.

23.8.4.1*

Fire alarm systems shall be permitted to share components, equipment, circuitry, and installation wiring withnon–fire alarm systems.

23.8.4.2

Operation of a non–fire system function(s) originating within a connected non-fire system shall not interferewith the required operation of the fire alarm system, unless otherwise permitted by this Code.

23.8.4.3*

For non–fire alarm equipment listed to the performance requirements specified in 10.3.5, the requirementsof 23.8.4.3.1 through 23.8.4.3.3 shall apply.

23.8.4.3.1

The equipment shall be permitted to be attached to a fire alarm circuit, either among the fire alarm devicesor as a branch or extension of the fire alarm pathways, when the following requirements are met:

(1) All the equipment and pathways shall meet the monitoring for integrity requirements of 10.6.9,Section 10.18, and Section 12.6.

(2) All the equipment and pathways shall be maintained by a single service organization.

(3) All the equipment and pathways shall be installed in accordance with the requirements of this Code.

(4) All the equipment shall be listed as compatible with the fire alarm equipment or the equipment shallhave an interface listed as compatible with the fire alarm equipment.

23.8.4.3.2

If the equipment is attached to the fire alarm system via separate pathways, then short circuits or opencircuits in this equipment, or between this equipment and the fire alarm system pathways, shall not impedeor impair the monitoring for integrity of the fire alarm system or prevent alarm, supervisory, or fire safetycontrol signal transmissions.

23.8.4.3.3

Grounds in this equipment, or between this equipment and the fire alarm system pathways, shall bereported, annunciated, and corrected in the same manner as grounds in the rest of the fire alarm system.

23.8.4.4

For non-fire alarm equipment not listed to the performance requirements specified in 10.3.5, therequirements of 23.8.4.4.1 through 23.8.4.4.3 shall apply

23.8.4.4.1

Short circuits or open circuits in the equipment, or between the equipment and the fire alarm systempathways, shall not impede or impair the monitoring for integrity of the fire alarm system or prevent alarm,supervisory, or fire life safety control signal transmissions.

23.8.4.4.2

Grounds in this equipment, or between this equipment and the fire alarm system pathways, shall bereported, annunciated, and corrected in the same manner as grounds in the rest of the fire alarm system.

23.8.4.4.3

Removal, replacement, failure, maintenance procedures, or ground on this hardware, software, or circuitsshall not impair the required operation of the fire alarm system.


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

23.8.4.5

Speakers used as alarm notification appliances on fire alarm systems shall also be permitted to be used foremergency communications systems when installed in accordance with Chapter 24.

23.8.4.6*

In combination systems, fire alarm signals shall be distinctive, clearly recognizable, and shall be indicatedas follows in descending order of priority, except where otherwise required by other governing laws, codesor standards, or by other parts of this Code:

(1) Signals associated with life safety

(2) Signals associated with property protection

(3) Trouble signals associated with life and/or property protection

(4) All other signals

23.8.4.7

If the authority having jurisdiction determines that the information being displayed or annunciated on acombination system is excessive and is causing confusion and delayed response to a fire emergency, theauthority having jurisdiction shall be permitted to require that the display or annunciation of information forthe fire alarm system be separate from, and have priority in accordance with, 23.8.4.6, over information forthe non–fire alarm systems.

23.8.4.8*

Signals from carbon monoxide detectors and carbon monoxide detection systems transmitted to a firealarm system shall be indicated as a carbon monoxide alarm signal.

Exception: When in accordance with the building’s response plan, evacuation plan, fire safety plan, orsimilar documentation, signals from carbon monoxide detectors and carbon monoxide detection systemstransmitted to a fire alarm system shall be permitted to be supervisory signals.

23.8.4.8.1

Signals from carbon monoxide detectors and carbon monoxide detection systems transmitted to a firealarm system shall be indicated as “Carbon Monoxide Alarm” on the fire alarm system control unit orannunciator.

23.8.4.8.2*

Fire alarm system processing for and occupant response to carbon monoxide alarm signals shall be inaccordance with the building’s response plan, evacuation plan, fire safety plan, or similar documentation.

23.8.4.9*

Signals from a fire extinguisher electronic monitoring device or fire extinguisher monitoring systemtransmitted to a fire alarm system shall be permitted to be supervisory signals.







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


Street Address:

City:

State:

Zip:

Submittal Date: Sat May 28 09:25:44 EDT 2016


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


23.8.4.5

Speakers Textual audible notification appliances used as alarm notification appliances on fire alarmsystems shall also be permitted to be used for emergency communications systems when installed inaccordance with Chapter 24.


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:

Submittal Date: Wed May 18 08:31:16 EDT 2016


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

Public Input No. 750-NFPA 72-2016 [ Section No. 23.8.4.8 [Excluding any Sub-Sections]

]

Signals from carbon monoxide detectors and carbon monoxide detection systems transmitted to a fire alarmsystem shall be indicated as a carbon monoxide alarm signal.

Exception:

When

When in accordance with the building’s response plan, evacuation plan, fire safety plan, or similardocumentation, signals from carbon monoxide detectors and carbon monoxide detection systemstransmitted to a fire alarm system shall be permitted to be supervisory signals.


Carbon monoxide detectors do not initiate a supervisory condition, they initiate Alarm and Trouble conditions. An End Of Life ( EOL) should be Trouble. An End Of Life ( EOL) should be Trouble. Per definition NFPA 720-2015 and NFPA 72 – 2016;

3.3.253.2 Carbon Monoxide Alarm Signal. A signal indicating a concentration of carbon monoxide at or above the alarm threshold that could pose a risk to the life safety of the occupants and that requires immediate action.[720, 2015] (SIG-FUN)

3.3.253.9* Supervisory Signal. Asignal that results from the detection of a supervisory condition. (SIG-FUN) 3.3.253.10* Trouble Signal. A signal that results from the detection of a trouble condition. (SIG-FUN)

A.3.3.253.9 Supervisory Signal. Examples include activated supervisory signal-initiating device outputs, supervisory data transmissions to supervising stations, the light and sound from actuated supervisory notification appliances, a delinquency signal indicating a guard’s tour supervisory condition, and so forth. The term guard’s tour supervisory signal, associated with systems supporting guard’s tour supervisory service, is a message indicating that a guard has activated a guard’s tour reporting station (not in itself an indication of a supervisory condition). Guard’s tour supervisory signals are not a subset of the general category of supervisory signals as used in this Code.

A.3.3.253.10 Trouble Signal. Examples include off-normal outputs from integrity monitoring circuits, the light and sound from actuated trouble notification appliances, trouble data transmission to a supervising station, and so forth.



Public Input No. 752-NFPA 72-2016 [Section No. A.23.8.4.8]


Submitter Full Name: Anthony Mucci

Organization: Tyco Integrated Security

Street Address:

City:

State:

Zip:



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


23.8.5.3 Fire Alarm Signal Initiation — Initiating Devices with Separate Power and Signaling Wiring.

23.8.5.3.1

Automatic fire alarm signal initiating devices that have integral trouble signal contacts shall be connected tothe initiating device circuit so that a trouble condition within a device does not impair alarm transmissionfrom any other initiating device.

Exception: Where the trouble condition is caused by electrical disconnection of the device or by removingthe initiating device from its plug-in base.

23.8.5.3.2*

Automatic fire alarm signal initiating devices that use a nonintegral device to monitor the integrity of thepower supply wiring to the individual initiating devices shall have the nonintegral device connected to theinitiating device circuit so that a fault on the power supply wiring does not impair alarm transmission fromany operational initiating device.







Street Address:

City:

State:

Zip:



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


23.8.5.4.1*

Systems equipped with alarm verification features shall be permitted under the following conditions:

(1) The alarm verification feature is not initially enabled, unless conditions or occupant activities that areexpected to cause nuisance alarms are anticipated in the area that is protected by the smokedetectors. Enabling of the alarm verification feature shall be protected by password or limited access.

(2) A smoke detector that is continuously subjected to a smoke concentration above alarm threshold doesnot delay the system functions of Sections 10.7 through 10.16, or 21.2.1 by more than 1 minute.

(3) Actuation of an alarm-initiating device other than a smoke detector causes the system functions ofSections 10.7 through 10.16, or 21.2.1 without additional delay.

(4) The current status of the alarm verification feature is shown on the record of completion [see Figure7.8.2(a), item 4.3].

(5) When in accordance with the building’s response plan, evacuation plan, fire safety plan, orsimilar documentation, signals from carbon monoxide detectors and carbon monoxide detection systemstransmitted to a fire alarm system, carbon monoxide alarm verification shall not be permitted .


Verification is extremely difficult and possibly unsafe because carbon monoxide is odorless, tasteless, and colorless. Its presence is undetectable by smell, taste, or sigh, but can be determined only with special equipment for the purpose of measuring levels of Carbon Monoxide. Carbon monoxide can be mixed and migrate throughout a building through the HVAC system, so initiating device quantity and placement is to be in the area of coverage in accordance to NFPA720-2015; 5.8.5.3 Requirements for Carbon Monoxide Detectors. 5.8.5.3.1 Carbon monoxide detectors shall be installed as specified in the manufacturer’s published instructions in accordance with 5.8.5.3.1(1) and 5.8.5.3.1(2), or 5.8.5.3.1(3): (1)*On the ceiling in the same room as permanently installed fuel-burning appliances (2)*Centrally located on every habitable level and in every HVAC zone of the building (3) A performance-based design in accordance with 5.8.5.3.2




Street Address:

City:

State:

Zip:



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


23.8.5.4.3 * Cross-zoned Detection

Systems that require the operation of two automatic detectors to initiate the alarm response shall bepermitted, provided that the following conditions are satisfied:

(1) The systems are not prohibited by the authority having jurisdiction.

(2)

(3) At least two automatic detectors are in each protected space Two means of detection shall beprovided within the listed coverage area of the detectors used .

(4) The alarm verification feature is not used.



Lacey_Annex_A_material_for_new_23-8-5-4-3.docx Annex material


The current language of (2) does not follow with the spacing limitations of a detector and the original intent of cross-zone spacing. Current language only requires that there be at least two detectors in a SPACE/ROOM. What if it’s a 1,800 ft² room which requires two spot smoke detectors anyway? This would require the fire to potentially get twice as large before detected. The proposed language also brings back the applicable term of cross-zone to define this condition. This term is used in panel programming to indicate that two devices are required as input to achieve an applicable output. A term is also needed/helpful in explaining, specifying, and training the concept. I am not sure why we need paragraph (1). Why is it up to the AHJ if properly spaced and designed per listings? I ask that the committee consider the need/benefit for (1). If necessary leave (1) in. A related proposal to definitions of Cross-zone will be submitted. This term is also referenced in NFPA 13 Handbook commentary under 7.3.2 in describing detection systems for pre-action.



Public Input No. 414-NFPA 72-2016 [New Section after 3.3.66.4]




Street Address:

City:

State:

Zip:



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

Proposed Annex A material for: 23.8.5.4.3

A.23.8.5.4.3 The concept of cross‐zoned detection is used to require two detectors to sense the fire

before output operations are activated. It reduces a nuisance activation by a single detector. However,

when using this approach it is required that there be no delay in activation that would normally occur

with a single detector. Therefore, at least two detectors are required within the same listed spacing that

a single detector would normally cover. An example would be a computer room with a clean agent

system calling for cross‐zoned detection utilizing smoke detectors. Assuming the room is square shaped

taking up 3,400 ft². We will assume air flow is not an issue and normal spacing will be used. A single

spot smoke detector covers 900 ft² (30’ x 30’). Normal detection would call for four detectors evenly

spaced to protect the 3,400 ft² area. However, cross‐zone requires that there be two detectors within

each 900 ft² listed spacing to ensure that the fire is detected within the same amount of time as any

single detector. As such, a minimum of eight detectors would be required. The concept is that we do

not want the fire to grow twice as large before two detectors activate an output function. This generally

results in twice the number of detectors/coverage for a given space. Another option could be to provide

4 spot detectors and one aspirating detector sized and piped to cover the 3,400 ft² room. If high air flow

is a factor, than additional detectors would likely be required in accordance with 17.7.6.3.3. The term

cross‐zoned came from conventional panel technology where you would have a row of detectors on

Zone 1, and a row of detectors on Zone 2 needing both zones to go into alarm.

Reason:

The current language of (2) does not follow with the spacing limitations of a detector and the original

intent of cross‐zone spacing. Current language only requires that there be at least two detectors in a

SPACE/ROOM. What if it’s a 1,800 ft² room which requires two spot smoke detectors anyway? This

would require the fire to potentially get twice as large before detected. The proposed language also

brings back the applicable term of cross‐zone to define this condition. This term is used in panel

programming to indicate that two devices are required as input to achieve an applicable output. A term

is also needed/helpful in explaining, specifying, and training the concept. I am not sure why we even

need paragraph (1). Why is it up to the AHJ if properly spaced and designed per listings? I ask that the

committee consider the need/benefit for (1). A related proposal to definitions of Cross‐zone will be

submitted.

Submitted by Scott Lacey


23.8.5.6.3*

If a valve is installed in the connection between a sprinkler system and an initiating device, the valve shallbe supervised in accordance with 17.16.1 unless the valve is arranged to cause operation of thesupervisory signal initiating device when it is in its non off -normal position.



The term “off-normal” is typically used to describe “non-normal” conditions. Revise to be consistent with the remainder of the Code. See 17.16.1.1 and 3.3.58.1.




Street Address:

City:

State:

Zip:



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


Power Loss Calculations

23.8.6.5 Emergency Voice/Alarm Communication Notification Appliance Circuits. Emergency voice/alarmcommunication notification appliance circuits shall be capable of full-load operation with a wiring powerloss not to exceed 12.5% (0.5dB) as determined in accordance with Sections 23.8.6.5.1, 23.8.6.5.2 or23.8.6.5.3.

23.8.6.5.1 Power Loss Calculations. A calculation for each circuit shall be provided to the authority havingjurisdiction demonstrating simultaneous full-load operation with a wiring power loss not to exceed 12.5%(0.5dB). Power loss calculations similar to the following shall be used:

PLoss = 10 * Log [1 - ((2 * RL) / (2 * RL (VLine squared / PRated))]

RL = (RRef / 1000) * D

With variables defined as follows:

D = length of wire used (in feet)

PLoss = power loss (in dB)

PRated = power driven on line from the amplifier (in watts)

RL = wire gauge resistance (in ohms)

RRef = wire resistance based on gauge of wire used (in ohms/ft.)

VLine = voltage on line (typically 25 volts or 70 volts)

Alternatively the distance may be calculated using a calculation similar to:

D = (61 / RRef) * (VLine squared / PRated)

23.8.6.5.2 Published power loss tables based on a power loss of not greater than 12.5% (0.5dB).

23.8.6.5.3 Manufacturers Power Loss Calculator. When allowed by the authority having jurisdictionmanufacturers calculations showing circuits are capable of simultaneous full-load operation with a wiringpower loss not to exceed 12.5% (0.5dB) are acceptable.


This PI was created to provide prescriptive requirements for calculating power loss due to wiring in emergency voice alarm communication systems. The three methods are provided for achieving a result. This PI will provide more uniform sound output from all speakers, regardless of their location on the circuit.


Submitter Full Name: Lynn Nielson

Organization: City Of Henderson

Affilliation: Self

Street Address:

City:

State:

Zip:



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

Public Input No. 718-NFPA 72-2016 [ Section No. 23.8.6.2 [Excluding any Sub-Sections]

]

Notification appliances shall not be required in exit stair enclosures, exit passageways, and elevator cars inaccordance with 23.8.6.2.1 through 23.8.6.2.4. In buildings required to be provided with emergencyvoice/alarm communications systems notification appliances shall be required in exit stair enclosures, exitpassageways, and elevator cars in accordance with 23.8.6.2.1 through 23.8.6.2.4.


The base code seems to indicate that there is allowance for not having devices in exit enclosures, exit passageway, and elevator cars. However, there are instances where devices are required in these areas, and the subsections to this code have several of those instances. In order to eliminate confusion about whether alarm devices are required in these areas, this change is necessary.




Affilliation: Self

Street Address:

City:

State:

Zip:



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


23.8.6.2.3

The evacuation signal shall not be required to automatically operate in exit stair enclosures and exitpassageways. Manually activated speakers shall be provided in exit stair enclosures and exit passagewaysin buildings required to have Emergency Voice/Alarm Communication systems in accordance with Section24.4.


The base code allows for elimination of alarms in stairs and passageways. It is unclear from the base NFPA 72 code whether any audible devices are required in these areas. However, the IBC and IFC require alarms in these areas. The intent of this PI is to clearly indicate that manually activated speakers shall be required where the building is served by a voice alarm system. Voice alarm systems are required in large facilities in case specific instructions need to be relayed to building occupants. There are an unlimited number of scenarios that can be imagined that would necessitate live voice instructions to occupants in these areas. It is important to have this capability for live messaging to all areas of a building, including exit stairs and exit passageways.




Affilliation: Self

Street Address:

City:

State:

Zip:



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


23.8.6.2.4

The evacuation signal shall not be required to automatically operate in elevator cars. Manually activatedspeakers shall be provided in elevator cars in buildings required to have Emergency Voice/AlarmCommunication systems in accordance with Section 24.4.


The base code allows for elimination of alarms in elevator cars. It is unclear from the base NFPA 72 code whether any audible devices are required in these areas. However, the IBC and IFC require alarms in these areas. The intent of this amendment is to clearly indicate that manually activated speakers shall be required where the building is served by a voice alarm system. Voice alarm systems are required in large facilities in case specific instructions need to be relayed to building occupants. There are an unlimited number of scenarios that can be imagined that would necessitate live voice instructions to occupants in these areas. It is important to have this capability for live messaging to all areas of a building, including elevator cars.




Affilliation: Self

Street Address:

City:

State:

Zip:



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


23.8.6.3.2

The boundaries of notification zones contained within a building shall be coincident with building outerwalls, building fire or smoke compartment boundaries, floor separations, or other fire safety subdivisions.


With the advent of mass notification a notification zone could include areas outside the building. A related proposal from this task group revised the definition of notification zone to reflect that. This paragraph needs to be modified to clarify that these requirements for notification zones are for indoor zones, not outdoor zones.





Street Address:

City:

State:

Zip:



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


23.10.2*

Fire alarm systems used for partial evacuation and relocation shall be designed and installed such thatattack by fire within an evacuation a signaling zone shall not impair control and operation of the notificationappliances outside the evacuation signaling zone. Performance features provided to ensure survivabilityshall be described and technical justification provided in the documentation submitted to the authorityhaving jurisdiction with the evaluation required in 23.4.3.1.


A Correlating Committee task group on language/terms reviewed the language of the Code for consistency and grammar. Editorial revision to align with the glossary terms for zone.




Street Address:

City:

State:

Zip:



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


23.10.3

Speakers Textual audible notification appliance that transmit tone signals shall be permitted to be used asfire alarm notification appliances.






Street Address:

City:

State:

Zip:



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


23.11.4

The installation wiring shall be monitored for integrity in accordance with the requirements of Section 12.6.

23.11.4.1

Removal of the electric coil from the solenoid valve it controls shall cause a supervisory signal at thereleasing service fire alarm control unit


The placement of the coil onto the solenoid valve is not currently supervised. When testing the solenoids on a water based suppression system It is common for the technician to remove the coil from the solenoid before activating the release panel and then checking to see if the solenoid is producing a magnetic field by inserting a screwdriver. The coil can be left removed from the solenoid without any indication. NFPA 2001 put this requirement into effect in 2016 because of similar concerns. This change would standardize this requirement across codes and eliminate any possible confusion as well as increase the dependability of the systems.


Submitter Full Name: Michael Henke

Organization: Potter Electric Signal Company

Street Address:

City:

State:

Zip:

Submittal Date: Wed Jan 06 11:43:04 EST 2016


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


23.16* Special Requirements for Low-Power Radio (Wireless) Systems.

23.16.1* Listing Requirements.

Compliance with Section 23.16 shall require the use of low-power radio equipment specifically listed for thepurpose.

23.16.2* Power Supplies.

A primary battery(s) (dry cell) shall be permitted to be used as the sole power source for devicesincorporating a low-power radio transmitter/transceiver where all of the following conditions are met:

(1) Each transmitter/transceiver shall serve only one device and shall be individually identified at thesystem control unit.

(2) The battery(s) shall be capable of operating the low-power radio transmitter/transceiver and itsassociated device for not less than 1 year before the battery depletion threshold is reached.

(3) A low battery signal shall be transmitted before the device is no longer capable of providing 7 days oftrouble signal operation followed by the signaling of a single non-trouble response. The low batterysignal shall be distinctive from alarm, supervisory, tamper, and trouble signals, shall visibly identify theaffected low-power radio transmitter/transceiver, and, when silenced, shall automatically re-sound atleast once every 4 hours.

(4) Catastrophic (open or short) battery failure shall cause a trouble signal identifying the affectedlow-power radio transmitter/transceiver at the system control unit. When silenced, the trouble signalshall automatically re-sound at least once every 4 hours.

(5) Any mode of failure of a primary battery in a low-power radio transmitter/transceiver shall not affectany other low-power radio transmitter/transceiver.

23.16.3 Alarm Signals.

23.16.3.1*

When a wireless initiating device is actuated, its low-power radio transmitter/transceiver shall automaticallytransmit an alarm signal.

23.16.3.2

Each low-power radio transmitter/transceiver shall automatically repeat alarm transmissions at intervals notexceeding 60 seconds until the initiating device is returned to its non-alarm condition.

23.16.3.3

Signals shall have priority in accordance with 23.8.4.6.

23.16.3.4

Response time shall be in accordance with 10.11.1.

23.16.3.5*

A fire An alarm signal from a low-power radio transmitter/transceiver shall latch at its system control unituntil manually reset and shall identify the particular initiating device in alarm.

23.16.4 Monitoring for Integrity.

23.16.4.1

The low-power radio transmitter/transceiver shall be specifically listed as using a communication methodthat is highly resistant to misinterpretation of simultaneous transmissions and to interference (e.g., impulsenoise and adjacent channel interference).


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

23.16.4.2

The occurrence of any single fault that disables communication between any low-power radiotransmitter/transceiver and the receiver/transceiver system control unit shall cause a latching trouble signalwithin 200 seconds at the system control unit that individually identifies the affected device.

23.16.4.3

A single fault on the signaling channel shall not cause an alarm signal.

23.16.4.4

The periodic communication required to comply with 23.16.4.2 shall ensure successful alarm transmissioncapability.

23.16.4.5

Removal of a low-power radio transmitter/transceiver from its installed location shall cause immediatetransmission of a distinctive trouble signal that indicates its removal and individually identifies the affecteddevice.

23.16.4.6

Reception of any unwanted (interfering) transmission by a retransmission device or by the receiver systemcontrol unit for a continuous period of 20 seconds or more shall cause an audible and visible troubleindication at the system control unit.

23.16.4.7

The indication required by 23.16.4.6 shall identify the specific trouble condition as an interfering signal.

23.16.5 Output Signals from Receiver/Transceiver/System Control Unit.

When the receiver/transceiver or system control unit is used to actuate remote devices, such as notificationappliances and relays, by wireless means, the remote devices shall meet the following requirements:

(1) Power supplies shall comply with Chapter 10 or the requirements of 23.16.2.

(2) All monitoring for integrity requirements of Chapters10, 12, 23, and 23.16.4 shall apply.

(3) Response time shall be in accordance with 10.11.1.

(4) Each transceiver/system control unit shall automatically repeat activated response signals associatedwith life safety events at intervals not exceeding 60 seconds or until confirmation that the output devicehas received the alarm signal.

(5) The remote devices shall continue to operate (latch-in) until manually reset at the system control unit.







Street Address:

City:


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

State:

Zip:



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


23.16.2* Power Supplies.

A primary battery(s) (dry cell) that meet the requirements of 23.16.2.1 or 23.16.2.2 shall be permitted tobe used as the sole power source for devices incorporating a low-power radio transmitter/transceiver .

23.16.2.1 One or more primary batteries without fault tolerance where all

ofthe following conditions are met:

(1) Each transmitter/transceiver shall serve only one device and shall be individually identified at thesystem control unit.

(2) The battery(s) shall be capable of operating the low-power radio transmitter/transceiver and itsassociated device for not less than 1 year before the battery depletion threshold is reached.

(3) A low battery signal shall be transmitted before the device is no longer capable of providing 7 days oftrouble signal operation followed by the signaling of a single non-trouble response.

(4) The low battery signal shall be distinctive from alarm, supervisory, tamper, and trouble signals, shallvisibly identify the affected low-power radio transmitter/transceiver, and, when silenced, shallautomatically re-sound at least once every 4 hours.

(5) Catastrophic (open or short) battery failure shall cause a trouble signal identifying the affectedlow-power radio transmitter/transceiver at the system control unit. When silenced, the trouble signalshall automatically re-sound at least once every 4 hours.

(6) Any mode of failure of a primary battery in a low-power radio transmitter/transceiver shall not affectany other low-power radio transmitter/transceiver.

23.16.2.2 Multiple primary batteries with fault tolerance where all the following conditions are met.

(1) Two or more batteries are provided

(2) The failure of a single battery does not affect the operation of the unit.

(3) The combined batteries shall be capable of operating the low-power radio transmitter/transceiverand its associated device for not less than 1 year before the battery depletion threshold is reached.

(4) A low battery signal shall be transmitted before the device is no longer capable of providing 7 daysof trouble signal operation followed by the signaling of a single non-trouble response.

(5) Each individual battery is to be separately monitored for the battery depletion threshold and a lowbattery signal shall be transmitted when an individual battery reached the battery depletion threshold.

(6) The low battery signal shall be distinctive from alarm, supervisory, tamper, and trouble signals,shall visibly identify the affected low-power radio transmitter/transceiver, and, when silenced, shallautomatically re-sound at least once every 4 hours.

(7) Catastrophic (open or short) failure of any individual battery shall cause a trouble signal identifyingthe affected low-power radio transmitter/transceiver at the system control unit. When silenced, thetrouble signal shall automatically re-sound at least once every 4 hours.

(8) Each transmitter/transceiver shall be permitted to serve more than one device and shall beindividually identified at the system control unit.


The current requirements limit the number of devices and the effect on any other low-power transmitter that can be served by a low-power radio transmitter/transceiver because it may be operating from a single primary battery as the sole power source and due to maintenance and battery failure. If at least two independent primary battery sources are provided and are both monitored for integrity and each is capable of serving the load, then the number of devices served should not be restricted. It is proposed that 23.16.2 (3) be divided into two numbered requirements in accordance with the manual of style.


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




Street Address:

City:

State:

Zip:



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


23.16.3 Alarm Signals.

23.16.3.1*

When a wireless initiating device is actuated, its low-power radio transmitter/transceiver shall automaticallytransmit an alarm signal.

23.16.3.2

comply with one of the following:

A) Each low-power radio transmitter/transceiver shall automatically repeat alarm transmissions atintervals not exceeding 60 seconds until the initiating device is returned to its non-alarm condition , or

B) Each low-power radio transmitter/transceiver shall automatically repeat alarm transmissions atintervals not exceeding 60 seconds until the transmitter/transceiver receives a single confirming receipt ofthe alarm signal by the control unit, and, following a reset, the current status of the transmitter/transceiveris indicated at the control unit .

23.16.3.3 2

Signals shall have priority in accordance with 23.8.4.6.

23.16.3.4 3

Response time shall be in accordance with 10.11.1.

23.16.3.5 4 *

A fire alarm signal from a low-power radio transmitter/transceiver shall latch at its system control unit untilmanually reset and shall identify the particular initiating device in alarm.


There is no need to continue to transmit an alarm signal once it has been received by the control unit since alarm signals must be latched at the control unit. This will help to reduce the power consumption from battery operated devices during system testing and increase battery life.


Submitter Full Name: Andrew Berezowski

Organization: Honeywell Inc.

Street Address:

City:

State:

Zip:



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



Type your content here ..

.23.16.3.5.1

Alarm signals received at wireless receivers shall not be required to latch if the receiver is monitored by afire alarm panel that latches the alarm signal.


Requiring a wireless receiver to latch in alarm until manually reset adds unnecessary complexity and possible confusion to the reset process. The current process requires that the person resetting the fire alarm system has to know that a wireless receiver exists, where it is, and to reset it first before resetting the fire alarm panel. Resetting the panel first without resetting the receiver would just re-initiate the alarm.This section seems to have been written around a wireless system where a wireless device transmits to a wireless receiver/panel so the receiver/panel had to latch in alarm.Now it is possible to have a wireless transmitter on a device send an alarm signal to a wireless receiver that can be mounted remotely from a hard wired fire panel and the receiver can be monitored by that fire panel. An example would be to have a tamper switch with a wireless transmitter in it mounted to a post indicator valve across the parking lot from the protected building. A wireless receiver would be mounted inside the building in a line of sight from the post indicator valve. The wireless receiver provides a dry contact output that is connected to a zone or monitor module of the fire alarm panel. The fire panel will latch in alarm when the receiver goes into alarm. There is no need to make the receiver latch and require someone to go find it and manually reset it..The fire panel will identify the device in alarm just as if it were hard wired directly to the device. The wireless system will simply be a wireless bridge between the device and fire panel.


Submitter Full Name: Michael Henke

Organization: Potter Electric Signal Company

Street Address:

City:

State:

Zip:

Submittal Date: Tue May 24 12:16:45 EDT 2016


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

Public Input No. 196-NFPA 72-2016 [ Section No. A.3.3.67 ]

A.3.3.67 Device (Class N).

Class N devices include components connected to a Class N network that monitor the environment (e.g.,smoke, heat, contact closure, manual “in case of fire” pull) and/or provide some output(s) (e.g., dry contact,audible/visual alert/notification, addressable speaker textual audible notification appliance ) that arerequired to provide the real-time functionality necessary for the protection of life and property. In this way, acomponent connected to the network used for noncritical functions (i.e., maintenance) can be differentiatedand excluded from the monitoring for integrity requirements of Class N.

Also in this way, transport equipment (e.g., switches, routers, hubs, media converters) and other equipment(e.g., printers, storage devices) can be differentiated from the requirements applied to Class N devices ifthey do not provide life safety–specific environmental monitoring, inputs, or outputs for the life safetysystem. This is not to say that this equipment is not important to the overall operation of the system, justthat this equipment is not considered a “device” in the context of Class N. Equipment that does not meetthe definition of a device cannot be specifically supervised but rather generally supervised as they are partof the supervised pathways that service the Class N devices themselves.






Street Address:

City:

State:

Zip:



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


A.3.3.92 Endpoint (Class N).

An endpoint device originates and/or terminates a communication stream and does not forward it to otherdevices.

An FACU, ACU, ECCU endpoint originates and/or terminates a communication stream with autonomy. Ifdata is sent to or received from other locations, that communications stream forms a new path. The newpath could even employ a different communications protocol and, where permitted, have a differentpathway class designation as defined in Section 12.3.

The exception in 12.3.6(1) shows Class N communication paths do not require redundant paths whenconnected to a single endpoint device. However, a connection to an FACU, ACU, or ECCU must beredundant even when those elements are an endpoint on a Class N communication path, with the exceptedallowance of 20 ft (6 m 6.1 m ) inside a raceway or enclosure defined in 12.6.9.


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



Street Address:

City:

State:

Zip:



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

Public Input No. 541-NFPA 72-2016 [ Section No. A.3.3.103.1 ]

A.3.3.103.1 Combination System.

Examples of non-fire systems are security, card access control, closed circuit television, soundreinforcement, background music, paging, sound masking, building automation, mass notification, time,and attendance.


This new annex will support clarification of combination systemsBuildings 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



Organization: Nema

Street Address:

City:

State:

Zip:



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


A.3.3.103.4 Protected Premises (Local) Fire Alarm System.

A protected premises fire alarm system is any fire alarm system located at the protected premises. It caninclude any of the functions identified in Section 23.3. Where signals are transmitted to a communicationcommunications center or supervising station, the protected premises fire alarm system also falls under thedefinition of one of the following systems: central station service alarm system, remote supervising stationalarm system, proprietary supervising station alarm system, or auxiliary alarm system. The requirementsthat pertain to these systems apply in addition to the requirements for the protected premises fire alarmsystems.






Street Address:

City:

State:

Zip:



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

Public Input No. 618-NFPA 72-2016 [ Section No. A.3.3.136.1.1 ]

A.3.3.136.1.1 Emergency Control Function Interface.

See Figure A.3.3.136.1.1.

Figure A.3.3.136.1.1 Emergency Control Function Interface.

Revise FACP to FACU in figure A.3.3.136.1.1



FACU is used consistently –with the exception of four clauses – throughout the Code, including 3.3.100 in the Glossary, to describe a fire alarm control unit. Revise ”FACP” to “FACU” for consistency within the Code.




Street Address:

City:

State:

Zip:



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


A.12.2.1

In the 2007 edition of NFPA 72, initiating device circuit, signaling line circuit, and notification appliancecircuit performance class/style tables were rooted in “copper” wiring methods. Fire alarm control units usenew communication communications technologies, such as Ethernet, fiber optics, and wireless, which donot fit in the “copper” wiring methods.






Street Address:

City:

State:

Zip:



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

Public Input No. 96-NFPA 72-2016 [ Section No. A.12.3 ]

A.12.3

Unless mandated otherwise in writing, it is the responsibility of the system designer / engineer preparingbid documents to establish the circuit designations appropriate for the user, hazard, and/or occupants.When a system is to be competitively bid, circuit designations should be identified in the bid documents.

The intent of the circuit designations is not to create a hierarchal ranking; rather it is to provide guidance onthe levels of performance.

Users of the Chapter 12 designations should review whether there are other abnormal conditions notspecified in Chapter 12 that the pathways need to annunciate and operate through for their application.


Currently there is no clarification in NFPA 72 of who identifies the Class Designation. Some AHJ's make it up by project. Many bid engineers leave it up to the contractor to design and price during bid which results in significant price differences that are not in the interest of the owner/user. The initial designer / bid preparer needs to be responsible for evaluating what is best for the owner/user based on cost/benefit. Although not mandated language, Annex provides clarification of intent. If an AHJ wants to mandate than they can provide a written mandate per ordinance/regulation, and not just make it up each job and each reviewer/inspector.




Street Address:

City:

State:

Zip:



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

Public Input No. 201-NFPA 72-2016 [ Section No. A.12.3.6(1) ]


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

A.12.3.6(1)


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

The Class N pathway designation is added to specifically address the use of modern network infrastructurewhen used in fire alarm and emergency communication systems.

Class N networks can be specified for ancillary functions but are not required for supplemental reportingdescribed in 23.12.4. [See Figure A.23.12.4].

Ethernet network devices are addressable but with an important distinction from device addresses on atraditional SLC multi-drop loop. A device with an Ethernet address is, in most cases, a physical endpointconnected to a dedicated cable. Traditional SLC devices are all wired on the same communication line (inparallel), similar to an old party-line telephone system. By comparison, Ethernet’s network switches directeach data packet to its intended recipient device like our modern phone systems.

Class N uses redundant paths as a means to compensate for Ethernet wiring that does not report a singleconnection to ground, a basic requirement of Class B. Thus, the physical separation of Class A andClass X, and equipment redundancy described in 12.3.7, is not inherently required of Class N. In otherwords, failure of a single switch is permitted take down a class N segment and is only required to report theloss of communication. Where redundant path segments are intended to have survivability similar toClass A or Class X, the physical separation requirements and overall equipment redundancy must bespecified in addition to the Class N designation.

As a visual model, Class N could be likened to a redundant pathway backbone, allowed to have Class Cbranch paths to single endpoint devices. Therefore, every effort is made in this section to clearly distinguishthe single endpoint device from the transport equipment required to have redundant paths.

Class N requires redundant, monitored pathway segments to and from control equipment (fire alarm controlunits, ACUs, or ECCUs) where any interruption in communications could potentially affect multiple endpointdevices. Typically, interconnected communications equipment such as Ethernet switches, wirelessrepeaters, or media converters are used in combination to create pathways. Chapter 12 describes therequired behavior of Class N pathways. All equipment must meet the requirements of other chapters inNFPA 72 (such as, but not limited to, requirements pertaining to secondary power supplies, equipmentlistings, and environment conditions).

Redundant pathways, isolated from ground, are actually common practice in robust Ethernet designs.Managed network switches commonly have specific uplink ports that are intended for load sharing andallow two parallel connections. For compliance with Class N, a trouble must be reported if either of theseconnections fails. [See Figure A.12.3.6(1)(a) and Figure A.12.3.6(1)(b).]

Class N pathways can use metallic conductor communications cable, such as a 100 ohm balanced twistedpair (e.g., Category 5E), including single-pair or multi-pair single?pair or multi?pair cable, or othercommunications media, such as optical fiber cable or wireless transmission, or a combination of two ormore such transport mediums.

Where a conductor-based conductor?based media is used for Class N, the intention is not to monitorfaults on individual conductors but rather to monitor the operational capability and performance of thepathway as a whole. Similar to Class C, end-to-end end?to?end verification is used in Class N.

Primary and required redundant pathways are independently and continuously verified for their ability tosupport end-to-end end?to?end communications to and from each endpoint device and its associatedcontrol equipment. Pathway segments that service more than one device must have at least one verifiedredundant pathway segment. Should any primary pathway segment fail, communication is supported by theredundant pathway segment(s.) Failure of either a primary or redundant pathway will indicate a trouble.

Redundant pathway segments are generally independent and do not normally share media with the primarypathways. However, there are exceptions, such as different frequencies for wireless components, or ringtopologies. [See Figure A.12.3.6(5).]

A Class N network can be made more reliable with physically distinct pathway segments (i.e., an alternateconduit, or cable tray route, or wireless transmission frequency range, or a combination of distinct media).In addition to the required primary segments and redundant segments, a Class N pathway is permitted tohave nonrequired segments. [See Figure A.12.3.6(1)(c) .] Additional nonrequired pathway segments areallowed to be connected and not independently monitored for integrity as long as two paths are monitoredto meet the redundancy requirement of Class N.

Figure A.12.3.6(1)(a) Class N Pathway Block Diagram – Example 1.


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

Figure A.12.3.6(1)(b) Class N Pathway Block Diagram – Example 2.

Traditionally, NFPA has used the word device for input components and the term appliance for componentsused in notification. With respect to Class N, the term device includes appliances and other intelligent,addressable components that perform a programmable input or output function. Examples of Class Ndevices include the following:

(1) Input components such as alarm initiating modules switches and sensors

(2) Output components such as output modules, Ethernet speakers textual audible notificationappliances (i.e., IEEE 802.3af PoE speakers textual audible notification appliances ), intelligentstrobes visible notification appliances , textual signage, and intelligent audio amplifiers

Transmission equipment components (e.g., media converters, Ethernet switches, patch panels, cross-connects cross-connects ) are connected to the Class N pathway merely to transport instructions betweenother equipment. As such, they are not considered devices with respect to Class N pathways.

The audio amplifier listed above is an example of an addressable device that can receive a digital audioinput from the Class N pathway and then provide a notification appliance circuit (NAC) output with Class A,B, or X pathways. Other endpoint devices can similarly provide alternate class pathways for strobes visiblenotification appliances (NACs) or initiating devices (IDCs). From the perspective of the Class N pathway,communications terminates at this endpoint device. However, since these types of endpoints can supportmultiple notification appliance devices or initiating devices, path segments are subject to the redundantpathway requirement unless protected in an enclosure or raceway less than 20 ft (6 m) in length. [SeeFigure A.12.3.6(1)(c) .]

Figure A.12.3.6(1)(c) Class N Pathway to Endpoint with Multiple Devices.

Class N connections between control equipment are required to have redundant monitored pathwaysegments if a failure of a primary pathway segment in between control equipment could impair theoperation of the control equipment. [See Figure A.12.3.6(1)(d).]

Figure A.12.3.6(1)(d) Class N Pathway Block Diagram with Multiple Control Units.


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

Class N is also permitted to include dual port devices that provide both transmission and input/outputfunctions. Endpoint devices can have multiple connection ports and support dual pathway segmentconnections; thus the term endpoint device is not intended to prohibit more than one connection to adevice. Even with dual connections, where other devices depend on the path, primary and redundant pathsare required. But, where an endpoint device has two connection ports, and when a secondary nonrequiredconnection is added, there is no requirement to separately supervise the nonrequired redundant pathwaysegment. [See Figure A.12.3.6(1)(e).]

Figure A.12.3.6(1)(e) Class N Pathway Block Diagram with Device with Dual Pathway Connection.



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.

The only changes being proposed are to (2) for the term "speaker." and "strobe." I noticed Terraview didn't like the hyphens that were already in the section and modified them on its own. Terra seems to be alive. Please disregard everything that Terra has done except for the "speaker" changes in (2).

Also need to change the figure in Figure A.12.3.6(1)(c) Class N Pathway to Endpoint with Multiple Devices to remove "speaker' to textual notification appliance as well as "strobe" to visible notification appliance.

Remember, this process was done to make things easier on us. (the meetings have been long and everyone needs a laugh, you are welcome.)

Further;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.




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


Street Address:

City:

State:

Zip:



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


A.12.3.6(4)

Operational conditions of the pathway include factors such as latency, throughput, response time, arrivalrate, utilization, bandwidth, and loss. Life safety equipment connected to a Class N network activelymonitors some or all of the pathway’s operational conditions so that an improperly installed or configuredpathway or a subsequently degraded pathway or segment is detected by the life safety equipment andreported as a trouble. The trouble condition is reported when operational conditions of the pathway(s) havedeteriorated to the point where the equipment is no longer capable of meeting its minimum performancerequirements, even if some level of communication communications to devices is still maintained.Performance requirements include the activation of an alarm within 10 seconds, the reporting of a troublesignal within 200 seconds, and delivery of audio messages with required intelligibility. End-to-endcommunications might be operational under system idle conditions, but in the event of an alarm, theincreased load on a degraded pathway could cause a partial or complete failure to deliver required lifesafety signals. Such predictable failure must be actively detected and reported.






Street Address:

City:

State:

Zip:



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


A.12.4

The intent of the pathway survivability designation is to provide options for the protection of the pathwaycircuits and not to create a hierarchical ranking. Other chapters within NFPA 72 or other code-makingjurisdictions can select the survivability option that best meets their needs.

Unless mandated otherwise in writing, it is the reponsibility of the system designer / engineer preparing biddocuments to establish the pathway survivability designations appropriate for the user, hazard, and/oroccupants. When a system is to be competitively bid, pathway survivability should be identified in the biddocuments. Such criteria should be reviewed by the building department and accepted beforeArchitectural / Engineering bid documents are released for contractor use and bidding.


Currently there is no clarification in NFPA 72 of who identifies the Pathway Survivability. Some AHJ's make it up by project. Many bid engineers leave it up to the contractor to design and price during bid which results in significant price differences that are not in the interest of the owner/user. The initial designer / bid preparer needs to be responsible for evaluating what is best for the owner/user based on cost/benefit. Although not mandated language, Annex provides clarification of intent. If an AHJ wants to mandate than they can provide a written mandate per ordinance/regulation, and not just make it up each job and each reviewer/inspector.




Street Address:

City:

State:

Zip:



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

Public Input No. 668-NFPA 72-2016 [ Sections A.12.4.3, A.12.4.3(4), A.12.4.4(4) ]

Sections A.12.4.3, A.12.4.3(4), A.12.4.4(4)

A.12.4.3

Methods of survivability protection might alternate within a protected premise. For example, 2-hourresistive fire-resistance rated cable might extend from a 2-hour fire-rated enclosure.

A.12.4.3(4)

A performance-based alternative is needed because it is possible to construct a nonsprinklered, TypeV(000) building that employs relocation or partial evacuation (e.g., a single-story ambulatory health careoccupancy) that would not warrant either a 2-hour fire resistance–rated -resistance rated enclosure or a2-hour fire-resistance cable. Examples of performance alternatives that might be considered in a design forsurvivability are a strategic application of Class A, Class X, or Class N segments and also wirelesscommunication pathways.

A.12.4.4(4)

A performance-based alternative is needed because it is possible to construct a sprinklered single-storyType V(111) or multistory Type II(111) building that employs relocation or partial evacuation (e.g., a healthcare occupancy) that would not warrant either a 2-hour fire resistance–rated -resistance rated enclosureor a 2-hour fire-resistance cable (a 1-hour fire-rated enclosure would suffice). Examples of performancealternatives that might be considered in a design for survivability are a strategic application of Class A,Class X, or Class N segments and also wireless communication pathways.



Editorial revision to align the different references to rated cables and enclosures.




Street Address:

City:

State:

Zip:



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


A.12.4.3(4)

A performance-based alternative is needed because it is possible to construct a nonsprinklered, TypeV(000) building that employs relocation or partial evacuation (e.g., a single-story ambulatory health careoccupancy) that would not warrant either a 2-hour fire resistance–rated enclosure or a 2-hour cable.Examples of performance alternatives that might be considered in a design for survivability are a strategicapplication of Class A, Class X, or Class N segments and also wireless communication communicationspathways.






Street Address:

City:

State:

Zip:



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


A.12.4.4(4)

A performance-based alternative is needed because it is possible to construct a sprinklered single-storyType V(111) or multistory Type II(111) building that employs relocation or partial evacuation (e.g., a healthcare occupancy) that would not warrant either a 2-hour fire resistance–rated enclosure or a 2-hour cable (a1-hour enclosure would suffice). Examples of performance alternatives that might be considered in a designfor survivability are a strategic application of Class A, Class X, or Class N segments and also wirelesscommunication communications pathways.






Street Address:

City:

State:

Zip:



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


A.12.5

Shared pathway designations propose a list of shared pathways, some of which are only allowable fornonrequired functions. Other sections of this Code determine which of the shared pathways are allowed tobe used as paths for required fire alarm signaling. Refer to 23.8.2.6 for shared communicationcommunications requirements.






Street Address:

City:

State:

Zip:



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


A.21.3.8

It should be noted that smoke detectors installed in hoistways can be a source of nuisance activation dueto the harsh or dirty environment in some elevator hoistways . Therefore, hoistways need the smokedetectors specifically intended for those types of spaces (environments) required to be installed in elevatorhoistways should be specifically seleceted to withstand the potentilal harsh or dirty environment in thosehoistways. The selection of the specific detectors could be based on performace methods described inAnnex B as accesptable to authority having jurisdication .


Revise the annex wording to be consistent with the proposed change for Section 21.3.8 and allow the use of Annex B for performance based selection of smoke detection in elevator hoistways.



Public Input No. 321-NFPA 72-2016 [Section No. 21.3.8] This is the section for this annex





Affilliation: SFFD

Street Address:

City:

State:

Zip:



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


A.21.3.9

The objective of Phase I Emergency Recall Operation is to have the elevator automatically return to therecall level before fire can affect the safe operation of the elevator. This includes both the safe mechanicaloperation of the elevator, as well as the delivery of passengers to a safe lobby location. Where ANSI/ASMEA17.1/CSA B44, Safety Code for Elevators and Escalators, specifies the use of smoke detectors fire alarminitiating devices used to initiate Phase I Emergency Recall Operation , these devices are expected toprovide the earliest response to situations that would require Phase I Emergency Recall Operations. Theuse of other automatic fire detection is only intended where smoke detection would not be appropriate dueto the environment. Where ambient conditions prohibit the installation of smoke detectors, the selection andlocation of other automatic fire detection should be evaluated to ensure the best response is achieved.When heat detectors are used, consideration should be given to both detector temperature and time lagcharacteristics (Response Time Index) . The consideration of a low temperature rating alone might notprovide the earliest response. It should be noted that smoke detectors installed in hoistways can be asource of nuisance activation. Therefore, hoistways need smoke detectors specifically intended for thosetypes of spaces (environments). Performace based selection of specific automatic fire detection suitable forelevator hoistways may be based on Annex B as acceptable to the authority having jurisdication.


1. Corrected the reference to smoke detectors in ASME A17.1 - The A.17.1 code specifies Fire Alarm Initiating Devices (FAIDs) as fire alarm devices initiating elevator Phase I Emergency Recall Operations - FAIDs includes other automatic fire detection devices such as heat detectors.2. Indicate the term Response Time Index (RTI) for heat detectors as the time lag characteristic - since this term is defined in NFPA 723.Reference Annex B as a source for performance based design which may be used for selecting smoke or heat detectors for elevator hoistways



Public Input No. 321-NFPA 72-2016 [SectionNo. 21.3.8]

This section specifies smoke detectors for elevatorhoistways

Public Input No. 322-NFPA 72-2016 [SectionNo. A.21.3.8]

This annex is related to fire detectors devices required inelevator hoistways




Affilliation: SFFD

Street Address:

City:

State:

Zip:



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


A.21.5.1

Signals to the standard emergency service interface providing the status of the elevator(s), includinglocation within the hoistway, direction of travel, and whether they are occupied should be provided by theelevator management system.


There is no such standard emergency service interface and it is not needed. This section was revised by the OEO Task group to eliminate the need of elevator related supervision



Public Input No. 772-NFPA 72-2016 [Section No. 18.11] same rational

Public Input No. 773-NFPA 72-2016 [Section No. A.18.11] same rational





Affilliation: SFFD

Street Address:

City:

State:

Zip:



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

Public Input No. 667-NFPA 72-2016 [ Sections A.21.6.2.1.1(2), A.21.6.2.1.2, A.21.6.2.1.4,

A.21.... ]

Sections A.21.6.2.1.1(2), A.21.6.2.1.2, A.21.6.2.1.4, A.21.6.2.1.4(C)

A.21.6 Occupant evacuation elevators (OEE) are not required by code and they will be provided for arelatively limited number of buildings, mainly office use high-rise buildings over 420 feet in lieu of a requiredthird stairway as a building code exception . They could also be provided on a voluntary basis in otherbuildings due to ADA or mobility of occupants concerns. It is highly recommended that those involved withdesign and installation of these systems become familiar with available information such as ASMEA17.1/CSA B44 (2016), Safety Code for Elevators and Escalators, Section 2. 27 regarding OccupantEvacuation Operation (OEO) and its non-mandatory Appendix V “Building Features for Occupant EvacuationOperation”. It will be imperative that a great amount of coordination and performance based design be donebetween elevator and fire alarm system designers, installation contractors and the authority havingjurisdiction.

A.21.6.2. 1.1 The term “ Group automatic operation ” is defined in ANSI/ASME A17.1/CSA B44, SafetyCode for Elevators and Escalators . Other terms such as “ elevator group ” or “ group of elevators ” are usedin 21.6 to refer to those elevators sharing a common car call operation. For instance, if an elevator landingcall is registered on a particular floor, any elevator that could respond to that call would be considered in thatelevator group. Elevators in an “elevator group” typically share a lobby, hoistway, and/or machine/controlroom or control space.

A.21.6.2.1.2 When OEO is activated either manually or automatically, it is applicable to all elevatorsserving the floors of the elevator evacuation zone. However, when a single elevator or a particular group ofelevators is placed on manual Phase 1 Emergency Recall Operation, OEO continues to operate for the otherelevators serving the elevator evacuation zone. Similarly, when a fire alarm initiating device (

2) The manual meanss) described in 21.3.13.1 and 21.3.13.2 is actuated, Phase 1 Emergency Recall Operation will cause recallonly to the associated elevator or group of elevators and not to all elevators in the elevator evacuation zonenot associated with that elevator or group of recalled elevators. See also 21.6.2.8.

A.21.6.2.3.1 This signal to the elevator system is caused by the activation of a fire alarm initiating deviceother than that which is described in 21.3.13.1 and 21.3.13.2.

A.21.6.2.3.3 The elevator discharge level is considered the same level as the designated level of elevatorrecall for an individual elevator or a group of elevators. More than a single elevator discharge level may existin a building.

A.21.6.2.4 The manual selection means such as a switch or a push button for each floor, is intended in lieuof automatic initiating devices that

aremay be impaired or out of service and would otherwise have actuated to provide automatic initiation inaccordance with 21.6.2.

13 .

1 (2).Manual fire alarm boxes

location throughout the buildingare not included because they are typically activated at locations remote from the fire and could lead tomisinformation about the location of the fire. The manual selection means could also serve to evacuate thebuilding or portions of the building for non-fire related emergencies. The manual selection means is requiredto provide a non-latching output(s) from the fire alarm system to the elevator system to prevent the need forfire alarm system reset upon a wrong or unwanted manual selection of a floor(s).

A.21.6.2.

1.2 5 The fire alarm system uses the floor identification to automatically establish


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

aan elevator evacuation zone for voice messaging purposes. The elevator system also uses the flooridentification to determine the contiguous block of floors to be evacuated

consistent with 21.6.2.1.2(B) . The established block of floors(elevator evacuation zone). So, that zone would typically be the floor of an active alarm plus two floors aboveand two floors below the floor with the active alarm for a total of five floors or as otherwise determined by theauthority having jurisdiction. The elevator evacuation zone is updated to reflect changing conditions asindicated by the output signal(s). This information is sent to the elevator system and also used for occupantnotification. The output signals from the fire alarm system can be in the form of contact closures or serialcommunications or other acceptable means approved by the authority having jurisdiction . Coordinationneeds to be provided between the fire alarm system installer

and, the elevator system installer , and the authority having jurisdiction .

A.21.6.2.

1.4 Messages6 Prerecorded automatic voice messages provided by the in-building fire emergency voice/alarmcommunications system need to be coordinated with the

operation of the elevatorstext displays provided separately by the elevator system to all affected elevator lobbies and floors served bythe elevator(s) operating in OEO so that occupants will understand what to expect and how to react.

Additional visual information will be provided in each affected elevator lobby by the elevator

managementsystem to further inform occupants of the status of the elevators. Refer also to 24.3.6 and associated Annexmaterial (Messages for One-Way Emergency Communications Systems) for additional information.

It is important to note that all elevator lobbies served by elevator(s) operating in OEO, both within theelevator evacuation zone and on other floors outside that zone, will be considered as affected lobbies andthey will be provided with variable messages generated by the elevator system.

The fire alarm system will not provide automatic voice messages in the affected elevator lobbies, butrather it will provide automatic messages to all floors having those affected lobbies via audible applianceslocated outside those lobbies. The messages provided by the fire alarm system and the elevator system onthe affected floors and lobbies must be coordinated so as not to conflict each other.

It is especially important to address additional automatic or manual alarm actuation(s) and the impact onexpanding the elevator evacuation zone and the corresponding voice messaging that has to adjust to thechange.

Sample voice message content to be added to normal message (to be coordinated with the variablemessage display provided by the elevator contractor) :

Condition: Specific block of floors being evacuated

“Elevators and stairs are available for evacuation”

Condition: Floors not in the elevator evacuation zone within an elevator group performing OEO

“Elevators not available, they are temporarily dedicated to other floors”

Condition: On the discharge level

“Elevators dedicated to evacuation. Do not enter elevator”

Condition: If some elevators have been recalled but other elevator(s) are still available:

“Elevators and stairs are available for evacuation”

Condition: If all elevators serving a floor or elevator evacuation zone are recalled:

“Elevators are out of service, Use stairs to evacuate”

Voice messaging is permitted to all other floor(s) in the building not in the elevator evacuation zone and notserved by elevator(s) performing OEO in accordance with the facility emergency response plan approved bythe authority having jurisdiction.

For further information on voice messaging strategies refer to “Incorporating Emergency MessagingGuidance into Practice”

A.21.6.2.


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

1.46 (C)

This new message will require a signal (s) from the elevator

managementsystem to the fire alarm system.

This signal(s) will indicate to the fire alarm system that all elevators serving an elevator evacuation zone areout of service due to Phase I Emergency Recall operation or due to other elevator out-of-service associatedcondition(s) such as inspection operation, malfunction, etc.

A.21.6.2.6(E) The emergency voice/alarm communications system’s speaker(s) located in each OEE lobbyare not permitted to transmit automatic voice messages since they may interrupt occupants using therequired OEE elevator lobby two way communication system. Therefore, manual paging zones are requiredfor those speakers by applicable building code(s). The specific zone selection will be performed from a firealarm system paging panel located in the FCC. Since a very large number of individual paging zones may berequired, it is permitted to group all OEE lobbies’ speakers per floor or vertically per elevator group as asingle paging zone. The OEE lobby paging zone will be dedicated to speakers which only serve OEE lobbiesand will be separate from all other speakers outside of an OEE lobby.

A.21.6.2.8 Suspension of OEO can occur when an individual elevator or group of elevators is temporarilyrecalled by manual means using key operated switch(s) designated as “Car Fire Recall” or “Group FireRecall”. It is important to recognize that OEO continues operation using the available elevator(s).

The affected elevator(s) will return to OEO operation when the individual “Car Fire Recall” or the “Group FireRecall” key switch has been turned off.

A.21.6.2.9 Partial termination can occur when a particular group of elevators has been taken out of servicebecause they have been recalled under automatic Phase 1 Emergency Recall, but other elevator(s) in theelevator evacuation zone are still available for evacuation.

A.21.6.2.10.2 There are several instances where signals must be received from the elevator system. Oneof these is when the Phase I Emergency Recall key switch is used to manually initiate recall for all elevators.In this case, the fire alarm system needs to know that it must cancel or change OEO voice messaging. Another situation requiring a signal from the elevator system is when, for whatever reason, the elevatorsystem cannot provide the intended operation. In this case the fire alarm system needs to know so it doesnot provide incorrect messaging to a floor(s). See also Annex A.21.6.2.6(c).



Proposed_Changes_for_Section_21_6_-_TG_-_Rev13.docx

This is the consolidated code body and annex revisions proposed for 21.6 by the NFPA 72 OEO TG.



Because the proposed changes to 21.6 affect nearly every existing paragraph, the task group recommends replacing the section in its entirety, including the associated annex material.



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







Street Address:

City:

State:

Zip:



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

Page 1 of 6

Proposed Changes for Section 21.6 … TG – Rev13 Rationale/Substantiation Mr. Jack Poole (SIG‐PRO Chair) and Mr. Richard Roux (NFPA 72 Staff Liaison) requested formation of a task group to clarify and further define the fire alarm system interface requirements with occupant evacuation elevators. The task group (Bruce Fraser, Sagiv Weiss‐Ishai, Kurt Ruchala, Carl Willms, Dan Finnegan, and Brandon Wilkerson (Chair)) developed a revised section 21.6, proposed revisions to section 21.5, proposed a revision to the section 21.6.2.3.5 included in the new section 21.6, and developed a flow chart intended to capture the requirements in graphic form. These proposed changes are important due to the complexities included in occupant evacuation elevator operation and the associated fire alarm system interface. Because this is a relatively new code concept which is applied in a relatively small number of buildings and can have a major impact on occupant safety during fire and non‐fire emergencies, it is critical that NFPA 72 clearly outline the fire alarm system expectations. The changes proposed by this task group are a result of detailed coordination with ASME A17.1/CSA B44 OEO Task Group, real‐world experience, and multiple task group meetings. Because the proposed changes to 21.6 affect nearly every existing paragraph, the task group recommends replacing the section in its entirety, including the associated annex material. 21.6* Occupant Evacuation Elevators. A.21.6 Occupant evacuation elevators (OEE) are not required by code and they will be provided for a relatively limited number of buildings, mainly office use high‐rise buildings over 420 feet in lieu of a required third stairway as a building code exception. They could also be provided on a voluntary basis in other buildings due to ADA or mobility of occupants concerns. It is highly recommended that those involved with design and installation of these systems become familiar with available information such as ASME A17.1/CSA B44 (2016), Safety Code for Elevators and Escalators, Section 2.27 regarding Occupant Evacuation Operation (OEO) and its non‐mandatory Appendix V “Building Features for Occupant Evacuation Operation”. It will be imperative that a great amount of coordination and performance based design be done between elevator and fire alarm system designers, installation contractors and the authority having jurisdiction. 21.6.1 Elevator Status. Where elevators are to be used for occupant self‐evacuation during fires and non‐fire emergencies, they shall comply with Sections 21.5 and 21.6. 21.6.2 Occupant Evacuation Operation (OEO). Outputs from the fire alarm system to the elevator system shall be provided to implement elevator occupant evacuation operation in accordance with Section 2.27 of ASME A17.1/CSA B44 (2016), Safety Code for Elevators and Escalators, as required in 21.6.2.1 through 21.6.2.5. 21.6.2.1 Applicability. OEO shall only be initiated upon an automatic or manual signal from the fire alarm system to the elevator system. 21.6.2.1.1* OEO shall apply separately to each individual elevator and to elevators having “group automatic operation” or designated as an “elevator group” or “group of elevators”. A.21.6.2.1.1 The term “Group automatic operation” is defined in ANSI/ASME A17.1/CSA B44, Safety Code for Elevators and Escalators. Other terms such as “elevator group” or “group of elevators” are used in 21.6 to refer to those elevators sharing a common car call operation. For instance, if an elevator landing call is registered on a particular floor, any elevator that could respond to that call would be considered in that

Page 2 of 6

elevator group. Elevators in an “elevator group” typically share a lobby, hoistway, and/or machine/control room or control space. 21.6.2.1.2* OEO shall function per 21.6.2.1.1 only prior to Phase 1 Emergency Recall Operation. A.21.6.2.1.2 When OEO is activated either manually or automatically, it is applicable to all elevators serving the floors of the elevator evacuation zone. However, when a single elevator or a particular group of elevators is placed on manual Phase 1 Emergency Recall Operation, OEO continues to operate for the other elevators serving the elevator evacuation zone. Similarly, when a fire alarm initiating device(s) described in 21.3.13.1 and 21.3.13.2 is actuated, Phase 1 Emergency Recall Operation will cause recall only to the associated elevator or group of elevators and not to all elevators in the elevator evacuation zone not associated with that elevator or group of recalled elevators. See also 21.6.2.8. 21.6.2.2 Partial Building Evacuation. Where an elevator or group of elevators is designated for use by occupants for self‐evacuation, the provisions of 21.6.2.3 through 21.6.2.6 shall apply for partial building evacuation. 21.6.2.3 Initiation. OEO shall be initiated by either manual means from the Fire Command Center (FCC) in accordance with 21.6.2.4 or by actuation of an automatic fire alarm initiating device in accordance with 21.6.2.3.1. 21.6.2.3.1* An active automatic fire alarm initiating device that does not initiate Phase I Emergency Recall Operation shall cause the fire alarm system to provide a signal to the elevator system indicating the floor of an active alarm. A.21.6.2.3.1 This signal to the elevator system is caused by the activation of a fire alarm initiating device other than that which is described in 21.3.13.1 and 21.3.13.2. 21.6.2.3.2 The floors to be evacuated shall be a contiguous block of floors designated as “the elevator evacuation zone” consisting of at least the floor with an active alarm, two floors above the floor with the active alarm and two floors below the floor with the active alarm. 21.6.2.3.3* When the floor designated as the elevator discharge level falls within the elevator evacuation zone, it is not to be evacuated by the elevator(s), and the fire alarm system shall initiate a voice message to instruct the occupants on that level to exit the building. A.21.6.2.3.3 The elevator discharge level is considered the same level as the designated level of elevator recall for an individual elevator or a group of elevators. More than a single elevator discharge level may exist in a building. 21.6.2.3.4 If activation of an automatic fire alarm initiating device which does not initiate Phase I Emergency Recall Operation occurs on an additional floor(s) including the elevator discharge level at any time while OEO is in effect, the elevator evacuation zone shall be expanded to include all floors with an active alarm, all floors between the highest and lowest floor with an active alarm plus two floors above the highest floor with an active alarm and two floors below the lowest floor with an active alarm. 21.6.2.3.5 If the first active alarm is on the elevator discharge level, automatic initiation of OEO shall not be permitted for all elevators having that same elevator discharge level. 21.6.2.4* Manual Floor Selection. (A) A means shall be furnished at the FCC to provide for the manual selection of each floor in the building.

Page 3 of 6

(B) The manual floor selection shall be activated only by authorized or emergency personnel. (C) When OEO is not yet in effect, and a manual floor selection is made to initiate OEO, a signal shall be sent to the elevator system simulating an active alarm. (D) When OEO is in effect and a manual floor selection is made, the elevator evacuation zone shall be expanded as described in 21.6.2.3.4. (E) The manual selection shall provide a non‐latching output(s). A.21.6.2.4 The manual selection means such as a switch or a push button for each floor, is intended in lieu of automatic initiating devices that may be impaired or out of service and would otherwise have actuated to provide automatic initiation in accordance with 21.6.2.3. Manual fire alarm boxes are not included because they are typically activated at locations remote from the fire and could lead to misinformation about the location of the fire. The manual selection means could also serve to evacuate the building or portions of the building for non‐fire related emergencies. The manual selection means is required to provide a non‐latching output(s) from the fire alarm system to the elevator system to prevent the need for fire alarm system reset upon a wrong or unwanted manual selection of a floor(s). 21.6.2.5* Fire Alarm Output Signals to Elevator System. (A) Output from the fire alarm system to the elevator system shall identify each floor with an active alarm. (B) Output from the fire alarm system to the elevator system shall include the following: (1) The floor with the first activated automatic fire alarm initiating device. (2) Floor(s) with any subsequently activated automatic fire alarm initiating device(s). (3) Floor(s) selected by manual means from the FCC. (C) The identified floor(s) shall be displayed on the building fire alarm system annunciator at the FCC or on a listed non‐fire alarm system annunciator or other annunciator as approved by the authority having jurisdiction. A.21.6.2.5 The fire alarm system uses the floor identification to automatically establish an elevator evacuation zone for voice messaging purposes. The elevator system also uses the floor identification to determine the contiguous block of floors to be evacuated (elevator evacuation zone). So, that zone would typically be the floor of an active alarm plus two floors above and two floors below the floor with the active alarm for a total of five floors or as otherwise determined by the authority having jurisdiction. The elevator evacuation zone is updated to reflect changing conditions as indicated by the output signal(s). This information is sent to the elevator system and also used for occupant notification. The output signals from the fire alarm system can be in the form of contact closures or serial communications or other acceptable means approved by the authority having jurisdiction. Coordination needs to be provided between the fire alarm system installer, the elevator system installer, and the authority having jurisdiction. 21.6.2.6* Occupant Notification. The in‐building fire emergency voice/alarm communications system shall transmit messages coordinated with the elevator system’s text displays in all elevator lobbies. (A) Automatic voice evacuation messages shall be transmitted to the elevator evacuation zone to indicate the need to evacuate and that elevator service is available. (B) Automatic voice messages shall be transmitted to the floors not being evacuated within the specific group of elevator(s) performing OEO, to inform occupants that elevator service is not available. (C)* Automatic voice messages shall be transmitted to the elevator evacuation zone to indicate that elevator service is not available when all elevators serving that elevator evacuation zone are out of service. (D) All automatic voice messages shall be coordinated so as not to be in conflict with the text displays provided separately by the elevator system. (E)* When required by the building code, the emergency voice/alarm communications system’s speaker(s)

located in each OEE lobby, shall be connected to a separate notification zone for manual paging only.

Page 4 of 6

Individual paging zones per each OEE lobby on each floor, grouped paging zone for all OEE lobbies on a floor,

or vertical paging zone for each elevator group shall be permitted as approved by the authority having

jurisdiction.

(F) Visible notification appliances (strobes) shall comply with 24.5.17.3(1), (2), and (3). A.21.6.2.6 Prerecorded automatic voice messages provided by the in‐building fire emergency voice/alarm communications system need to be coordinated with the text displays provided separately by the elevator system to all affected elevator lobbies and floors served by the elevator(s) operating in OEO so that occupants will understand what to expect and how to react. Additional visual information will be provided in each affected elevator lobby by the elevator system to further inform occupants of the status of the elevators. Refer also to 24.3.6 and associated Annex material (Messages for One‐Way Emergency Communications Systems) for additional information. It is important to note that all elevator lobbies served by elevator(s) operating in OEO, both within the elevator evacuation zone and on other floors outside that zone, will be considered as affected lobbies and they will be provided with variable messages generated by the elevator system. The fire alarm system will not provide automatic voice messages in the affected elevator lobbies, but rather it will provide automatic messages to all floors having those affected lobbies via audible appliances located outside those lobbies. The messages provided by the fire alarm system and the elevator system on the affected floors and lobbies must be coordinated so as not to conflict each other. It is especially important to address additional automatic or manual alarm actuation(s) and the impact on expanding the elevator evacuation zone and the corresponding voice messaging that has to adjust to the change. Sample voice message content to be added to normal message (to be coordinated with the variable message display provided by the elevator contractor): Condition: Specific block of floors being evacuated “Elevators and stairs are available for evacuation” Condition: Floors not in the elevator evacuation zone within an elevator group performing OEO “Elevators not available, they are temporarily dedicated to other floors” Condition: On the discharge level “Elevators dedicated to evacuation. Do not enter elevator” Condition: If some elevators have been recalled but other elevator(s) are still available: “Elevators and stairs are available for evacuation” Condition: If all elevators serving a floor or elevator evacuation zone are recalled: “Elevators are out of service, Use stairs to evacuate” Voice messaging is permitted to all other floor(s) in the building not in the elevator evacuation zone and not served by elevator(s) performing OEO in accordance with the facility emergency response plan approved by the authority having jurisdiction.

Page 5 of 6

For further information on voice messaging strategies refer to “Incorporating Emergency Messaging Guidance into Practice” A.21.6.2.6(C) This new message will require a signal(s) from the elevator system to the fire alarm system. This signal(s) will indicate to the fire alarm system that all elevators serving an elevator evacuation zone are out of service due to Phase I Emergency Recall operation or due to other elevator out‐of‐service associated condition(s) such as inspection operation, malfunction, etc. A.21.6.2.6(E) The emergency voice/alarm communications system’s speaker(s) located in each OEE lobby are not permitted to transmit automatic voice messages since they may interrupt occupants using the required OEE elevator lobby two way communication system. Therefore, manual paging zones are required for those speakers by applicable building code(s). The specific zone selection will be performed from a fire alarm system paging panel located in the FCC. Since a very large number of individual paging zones may be required, it is permitted to group all OEE lobbies’ speakers per floor or vertically per elevator group as a single paging zone. The OEE lobby paging zone will be dedicated to speakers which only serve OEE lobbies and will be separate from all other speakers outside of an OEE lobby. 21.6.2.7 Total Evacuation. A means to initiate total building evacuation, labeled “ELEVATOR TOTAL BUILDING EVACUATION” shall be provided at the FCC. 21.6.2.7.1 When this means is actuated, the fire alarm system shall provide a signal to the elevator system indicating that all floors in the building are to be evacuated. 21.6.2.7.2 The in‐building fire emergency voice/alarm communications system shall transmit an evacuation message throughout the building to indicate the need to evacuate. 21.6.2.8* Suspension of OEO for an Individual Elevator or Group of Elevators. 21.6.2.8.1 OEO shall be suspended for an individual elevator or group of elevators when an individual elevator or a group of elevators have been manually recalled via an elevator system designated key operated switch(s) labeled “Car Fire Recall” or “Group Fire Recall”. 21.6.2.8.2 When OEO has been suspended as in 21.6.2.8.1, the in‐building fire emergency voice/alarm communications system shall transmit messages coordinated with the elevator system’s text displays in compliance with 21.6.2.6. A.21.6.2.8 Suspension of OEO can occur when an individual elevator or group of elevators is temporarily recalled by manual means using key operated switch(s) designated as “Car Fire Recall” or “Group Fire Recall”. It is important to recognize that OEO continues operation using the available elevator(s). The affected elevator(s) will return to OEO operation when the individual “Car Fire Recall” or the “Group Fire Recall” key switch has been turned off. 21.6.2.9* Partial Termination of OEO. 21.6.2.9.1 OEO shall be terminated for a specific group of elevator(s) when the signal(s) provided in 21.3.13.1 and 21.3.13.2 associated with this group of elevator(s), has initiated Phase I Emergency Recall Operation for this group of elevator(s).

Page 6 of 6

21.6.2.9.2 When OEO has been partially terminated, the in‐building fire emergency voice/alarm communications system shall transmit messages coordinated with the elevator system’s text displays in compliance with 21.6.2.6. A.21.6.2.9 Partial termination can occur when a particular group of elevators has been taken out of service because they have been recalled under automatic Phase 1 Emergency Recall, but other elevator(s) in the elevator evacuation zone are still available for evacuation. 21.6.2.10 Total Termination of OEO. 21.6.2.10.1 OEO shall be terminated for all elevators in the building upon reset of the fire alarm system. 21.6.2.10.2* OEO shall be terminated when there are no elevators available for self‐evacuation. A.21.6.2.10.2 There are several instances where signals must be received from the elevator system. One of these is when the Phase I Emergency Recall key switch is used to manually initiate recall for all elevators. In this case, the fire alarm system needs to know that it must cancel or change OEO voice messaging. Another situation requiring a signal from the elevator system is when, for whatever reason, the elevator system cannot provide the intended operation. In this case the fire alarm system needs to know so it does not provide incorrect messaging to a floor(s). See also Annex A.21.6.2.6(c).

Public Input No. 740-NFPA 72-2016 [ Sections A.21.6.2.1.1(2), A.21.6.2.1.2, A.21.6.2.1.4,

A.21.... ]

Sections A.21.6.2.1.1(2), A.21.6.2.1.2, A.21.6.2.1.4, A.21.6.2.1.4(C)

A.21.6.2.1.1(2)

The manual means is intended in lieu of automatic initiating devices that are impaired or out of service andwould otherwise have actuated to provide automatic initiation in accordance with 21.6.2.1.1(2). Manual firealarm boxes location throughout the building are not included because they are typically activated atlocations remote from the fire and could lead to misinformation about the location of the fire.

A.21.6.2.1.2

The fire alarm system uses the floor identification to automatically establish a contiguous block of floors tobe evacuated consistent with 21.6.2.1.2(B). The established block of floors is updated to reflect changingconditions as indicated by the output signal(s). This information is sent to the elevator system and alsoused for occupant notification. The output signals from the fire alarm system can be in the form of contactclosures or serial communications. Coordination needs to be provided between the fire alarm systeminstaller and the elevator system installer.

A.21.6.2.1.4

Messages need to be coordinated with the operation of the elevators so that occupants understand whatto expect and how to react. Additional visual information will be provided in each elevator lobby by theelevator management system to further inform occupants of the status of the elevators.

A.21.6.2.1.4(C)

This new message will require a signal from the elevator management system to the fire alarm system.



NFPA_OEO_Rev_10.pdfFlowchart to describe OEO and fire alarm interface. This is part of the NFPA 72 task group for Occupant Evacuation Operation revision (see justification).



This flowchart is intended to provide an overall view of the operational requirements between the elevator and fire alarm systems and is intended to be appended to the new Section 21.6 proposed by the task group.





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






Street Address:

City:

State:

Zip:



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

AutoCAD SHX Text

Fire Alarm Initiating Device (FAID) Activation

AutoCAD SHX Text

Initial Alarm Discharge Level non Phase I FAID?

AutoCAD SHX Text

First FAID Activated

AutoCAD SHX Text

Signal OEO To Elevator System the Active Alarm Floor

AutoCAD SHX Text

OEO Available Message to the Elevator Evacuation Zone

AutoCAD SHX Text

Alert Message Elevator Not Available All Other Floors Outside the Elevator Evacuation Zone(s)

AutoCAD SHX Text

OEO Available Message Range of Floors Within Elevator Evacuation Zone(s)

AutoCAD SHX Text

OEO Not Available Message All Floors Within The Elevator Group

AutoCAD SHX Text

FCC Manual OEO Floor Switch Acttivated

AutoCAD SHX Text

FCC Manual Total Building Evacuation Switch Acttivated

AutoCAD SHX Text

Signal OEO Manually Selected Floor(s) To The Elevator System

AutoCAD SHX Text

Signal OEO Total Building Evacuation To The Elevator System

AutoCAD SHX Text

Total Building Evacuation Message All Floors

AutoCAD SHX Text

Yes

AutoCAD SHX Text

Yes

AutoCAD SHX Text

No

AutoCAD SHX Text

Signal Phase I Discharge Level or Alternate Level To Elevator System

AutoCAD SHX Text

No New Message

AutoCAD SHX Text

Message Update OEO Available Message Also to Manually Selected Elevator Evacuation Zone(s)

AutoCAD SHX Text

Message Update OEO Available Message Also to Manually Selected Floor Elevator Evacuation Zone(s) Alert Message All Other Floors

AutoCAD SHX Text

Manual Floor(s) Switch Activation from Fire Command Center

AutoCAD SHX Text

No New Message

AutoCAD SHX Text

Message Update Total Building Evacuation Message All Floors

AutoCAD SHX Text

Automatic Activation of Fire Alarm

AutoCAD SHX Text

Manual Total Building Evacuation Switch Activation from Fire Command Center

AutoCAD SHX Text

Fire Alarm System Inputs

AutoCAD SHX Text

Fire Alarm System Output Signals to Elevator System

AutoCAD SHX Text

Fire Alarm / Voice Emergency Communication System Messages

AutoCAD SHX Text

Manual Fire Alarm System Activation of OEO from Fire Command Center (FCC)

AutoCAD SHX Text

Manual Selection of a Floor and Manual Selection of Elevator Total Building Evacuation Responses Disabled During an Initial FAID Discharge Level or Any Phase 1 Initiation Device Alarm Condition

AutoCAD SHX Text

Elevator System to Terminate OEO For The Affected Elevator Group

AutoCAD SHX Text

OEO Not Activated

AutoCAD SHX Text

Discharge Level non Phase I FAID ?

AutoCAD SHX Text

No

AutoCAD SHX Text

Yes

AutoCAD SHX Text

OEO Terminated

AutoCAD SHX Text

Initial Alarm Phase I Initiating Device ?

AutoCAD SHX Text

Phase I FAID ?

AutoCAD SHX Text

Yes

AutoCAD SHX Text

No

AutoCAD SHX Text

Yes

AutoCAD SHX Text

No

AutoCAD SHX Text

No

AutoCAD SHX Text


AutoCAD SHX Text


AutoCAD SHX Text


AutoCAD SHX Text

Manual Elevator System Phase I Activation

AutoCAD SHX Text

Elevator System to Signal Fire Alarm System Elevator Group is in Phase I Recall

AutoCAD SHX Text

OEO Not Available Message All Floors Within The Group

AutoCAD SHX Text

Elevator System Phase I Recall Initiated From Elevator System

AutoCAD SHX Text

Fire Alarm System in OEO Mode ?

AutoCAD SHX Text

Yes

AutoCAD SHX Text

Elevator System Output Signal(s) to Fire Alarm System

AutoCAD SHX Text

OEO Suspended

AutoCAD SHX Text

Signal Discharge Level Alarm to Elevator System

AutoCAD SHX Text

Discharge Leave Message Exit the Building

AutoCAD SHX Text

General Notes 1Occupant Evacuation Operation (OEO) applies to each elevator group separately. Occupant Evacuation Operation (OEO) applies to each elevator group separately. 2Elevator Group refers to elevator(s) operating on an automatic group operation as defined Elevator Group refers to elevator(s) operating on an automatic group operation as defined in A17.1 3Fire Alarm Initiating Device shown as; (FAID)Fire Alarm Initiating Device shown as; (FAID)

AutoCAD SHX Text

Definitions 1Elevator Evacuation Zone - Contiguous block of floors consisting of the floor of the first Elevator Evacuation Zone - Contiguous block of floors consisting of the floor of the first active alarm plus two floors above and two floors below. 2Elevator Discharge Level - The designated recall level for each individual elevator or group Elevator Discharge Level - The designated recall level for each individual elevator or group of elevators where occupants exit the elevator(s) and exit the building

AutoCAD SHX Text

OEO Available Message to the Elevator Evacuation Zone

AutoCAD SHX Text

Message Update OEO Available Message Also to Manually Selected Elevator Evacuation Zone(s)



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

A.23.6.1


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

The intent of 23.6.1 applies to both short-circuit faults and open-circuit faults.

Fire alarm and signaling system communications technologies have evolved to the point that SLCs are nowthe prevalent means of monitoring initiation devices, controlling output devices, and communicatingbetween panels, annunciators, and controllers.

The extent of coverage of traditional IDCs is inherently limited based on the quantity of powered initiationdevices or code limitations. Similarly, the extent and coverage of NACs also are limited by the powerrequired to operate the devices. SLCs, unlike IDCs and NACs, have few limitations, and it is now commonthat a single SLC can monitor and control more than 250 devices. In addition, a single SLC can be the onlypathway by which alarms are initiated, emergency control functions are controlled, and audible and visualnotification appliances are activated.

A total catastrophic failure of a fire alarm and life safety system due to a single open or short on an SLCcan negate most, if not all, of this Code’s requirements for specifying an acceptable minimum level ofperformance and reliability for the protection of life and property from fire.

Designers should carefully consider the potential that a single SLC short or open caused by a fire orinadvertent damage to the SLC could disable an entire SLC prior to the activation of an alarm conditionalong with the subsequent alarm signaling and emergency control functions.

With traditional IDCs and NACs, a single open, ground, or short fault on one circuit could not affect theperformance of other IDCs, NACs, and emergency control circuits. As such, the occurrence of a singleshort or open could limit the extent of the failure to a particular zone or area.

One method for providing an acceptable level of performance and reliability of SLCs is to limit the potentialcatastrophic failure to one zone, in a way similar to how traditional IDCs and NACs have been and are nowrequired to do.

A single zone could be designated in the following ways:

(1) By floor where an SLC would not span multiple floors

(2) By floor area, where a large floor would be split into multiple zones based on a maximum floor area

size (e.g., 22,500 ft2)

(3) By fire barrier or smoke barrier compartment boundaries, which an SLC would not cross

(4) By maximum length or circuit, where an SLC would not be longer than a predetermined length (e.g.,300 ft)

See the definition of zone (3.3.314) and Figure A.23.6.1(a) through Figure A.23.6.1(d) for additionalclarification.

Figure A.23.6.1(a) depicts a Class B SLC with four zones. Wiring of more zones would require one isolatorfor each additional zone. The isolator can be integrated into the device or a separate component. If a singleshort or open occurs beyond the isolators, only one zone will be affected.

Figure A.23.6.1(a) Class B Isolation Method.


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

Figure A.23.6.1(b) depicts a Class A SLC with four zones. Wiring of more zones would require one isolatorfor each additional zone. The isolator can be integrated into the device or a separate component. If a singleshort or open occurs, only one zone will be affected. If a single open occurs, no devices will be affected.

Figure A.23.6.1(b) Class A Isolation Method.

FIGURE A.23.6.1(b)

Note: The two isolation modules shown at the FACP FACU are not required if the panel SLC controlleris internally isolated from shorts between outgoing and return termination points.

Figure A.23.6.1(c) depicts a hybrid Class A SLC loop with Class B SLC branches serving four zones that isdesignated as a Class B SLC. Wiring of more zones would require one isolator for each additional zone.The isolator can be integrated into the device or a separate component. If a single short occurs, only onezone will be affected. If a single open occurs, it might affect only one zone.

Figure A.23.6.1(c) Hybrid Isolation Method.


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

FIGURE A.23.6.1(c)

Note: The two isolation modules shown at the FACP FACU are not required if the panel SLC controlleris internally isolated from shorts between outgoing and return termination points.

Figure A.23.6.1(d) depicts an incorrect Class B SLC configuration with four zones. If a single short or openoccurs, one or more zones could be affected depending on the location of the single short.

Figure A.23.6.1(d) Incorrect Use of Isolators on an SLC.



FACU is used consistently – with the exception of four clauses – throughout the Code, including 3.3.100 in the Glossary, to describe a fire alarm control unit. Revise ”FACP” to “FACU” for consistency within the Code.


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

Replace "FACP" with FACU" in Figures A.23.6.1(b) and A.23.6.1(c).




Street Address:

City:

State:

Zip:



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

Public Input No. 590-NFPA 72-2016 [ New Section after A.23.6.1.3 ]

A.23.6.1.3(3) In many cases existing systems are partially modified with initiating devices beingadded as a part of the scope of work. In this case the SLC may not have been installed in a mannerwhich may be easily modified to accommodate isolation modules and/or keep a single SLC loopconfined to a single zone. This condition makes it clear that the requirements of SLC Zones doesnot apply to existing systems which were not required to meet the zoning requirements of 23.6.1when originally approved.


Many existing systems may not be capable of, or easily modified to fulfill the requirement of 23.6.1. If an SLC in an existing building is being added to, or having a minor modification to accommodate a tenant and the SLC is currently covering multiple Zones as defined in 23.6.1.1 or 23.6.1.2 then significant effort may be required to reinstall or reroute cable for the SLC. Additionally, isolation modules have different specifications from different manufacturers. Some manufacturers require an isolation module every 25 address and there are modules that take 3 address in the system. If a previously approved system is large enough the extra addresses required by the installation of isolation modules may exceed the system limitations of the number of address available, where prior to this requirement the system was within the limitations of the addresses available.

Please see the two scenarios below which I believe may help illustrate my point.

Scenario 1 – A six story R-1 (Hotel) covering a total of approximately 190,000 square feet was electively replacing the single station smoke alarms inside of all guest rooms with a system smoke detector monitored by the FACU. The system was installed two years prior to this requirement. This accounted for approximately 500 new addressable detectors on the system which I believe should have been held to the performance requirements of 23.6.1 and was shown as such. However, the 800 plus existing devices throughout the other portions of the building were not being altered and outside of the scope of work. If the existing areas, which were not inside the project’s scope, were required to adhere to 23.6.1 the expense, time, and effort required to modify the existing cabling throughout the building, as well as cards added to the FACU would have been so great the building owner would likely not be willing to do any work on the system whatsoever.

Scenario 2 – A 1,200 square foot tenant space inside of a 200,000 square foot Covered Mall was being remodeled including adding new dressing rooms. This required a new remote power supply which required a relay module to activate the new remote power supply, monitoring module, and a smoke detector. In total 3 new addressable devices were being added to a system already supporting approximately 150 addressable devices which have been previously approved as Class B circuits. Is it practical for the owner of the Mall to be required, possibly by an AHJ, to change the existing cable design of the Mall so it may be in compliance with 26.3.1 for the addition of 3 devices?



Public Input No. 589-NFPA 72-2016 [New Sectionafter 23.6.1.3]

Annex material provided should PI 589 be insertedinto the code.


Submitter Full Name: Harrison Bradstreet

Organization: Fire Safety Consultants

Affilliation: Illinois Fire Inspectors Association

Street Address:

City:


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

State:

Zip:



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

Public Input No. 542-NFPA 72-2016 [ New Section after A.23.8.4.1 ]

A23.8.4.2.1

For examples of non-fire systems, see A3.3.103.1


This new annex will support clarification of combination systems; a New A 3.3.103.1 PI has been submittedBuildings 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.



Organization: Nema

Street Address:

City:

State:

Zip:



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


A.23.8.4.3

For systems such as carbon monoxide detection, fire extinguisher electronic monitoring device, emergencycommunication communications (mass notification), or intrusion, much of the benefit of a combinationsystem comes from being able to use common wiring. If the equipment in the combination system is ofequivalent quality to fire alarm equipment, and the system monitors the wiring and equipment in the sameway as fire alarm equipment, then sharing of wiring is permitted. If the equipment is not of equivalentquality, isolation between the systems would be required.






Street Address:

City:

State:

Zip:



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


A.23.8.4.8

See NFPA 720A.23.8.4.8 See NFPA 720 for more information.


No longer needed



Public Input No. 750-NFPA 72-2016 [Section No. 23.8.4.8 [Excluding any Sub-Sections]] Body




Street Address:

City:

State:

Zip:



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


A.23.10.2

One or more of the following means might be considered acceptable to provide a level of survivabilityconsistent with the intent of this requirement:

(1) Installing a fire alarm system in a fully sprinklered building in accordance with NFPA 13

(2) Routing notification appliance circuits separately

(3) Using short-circuit fault-tolerant signaling line circuits for controlling evacuation signals

The requirement for notification appliances to operate in those evacuation signaling zones that are notattacked by fire will also require that circuits and equipment that are common to more than one evacuationsignaling zone be designed and installed such that the fire will not disable them. For instance, a signalingline circuit used to control notification appliances in multiple evacuation signaling zones should be properlydesigned and installed so that one fire would not impair the signaling line circuit, rendering the notificationappliances serving more than one evacuation signaling zone inoperative. Power supply requirements ofChapter 10 apply to these systems. The secondary power supply requirements of that chapter meet theintent of these survivability requirements.


A Correlating Committee task group on language/terms reviewed the language of the Code for consistency and grammar. Editorial revision to align with the glossary terms for zone.




Street Address:

City:

State:

Zip:



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

Public Input No. 262-NFPA 72-2016 [ Section No. C.2.2.1.7 ]

C.2.2.1.7 Fire Scene Operations.

Compartmentation, water supply, fire fighter access, and communication links are important for manualfire-fighting operations. Fire alarm system monitoring, reporting, display, and control functions that enhancethe maintenance and operation of these elements that enhance fire scene operations should be consideredin the design, installation, and maintenance of protected premises fire alarm systems. An example would bea flashing light visible notification appliance over the fire department connection.


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:



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

Public Input No. 626-NFPA 72-2016 [ Section No. C.3 ]

C.3 Premises Mission/Use/Property Protection.

The loss of use or mission of a facility to the effects of accidental fire can have a very significant impact onthe community or organization served by the facility. In such a case, it is appropriate to enhance functionalcharacteristics of the protected premises system. Considerations include the following:

(1) Criticality/Mission Continuity

(2) Community — Loss of operations of the facility might affect the community beyond the facility.Consider the sensitivity of fire detection and the effectiveness of alarm processing, emergencyresponse, and fire suppression to minimize effects on the community served due to facilityimpairment by fire.

(3) Operations

(4) On-premises — Fire might result in business interruption or reduced effectiveness.

(5) Elsewhere — Services provided by the facility to remote locations might cease or bereduced.

(6) Life Safety

(7) Evacuation/Relocation — Size, distribution, and mobility of the occupant population should beconsidered with knowledge of facility emergency planning and availability of emergency responseresources to determine the extent to which people movement might be managed during a fireincident.

(8) Defend - In - Place — A protected premises system might be used to activate facility fire safetyelements necessary to defend occupants in place or to enhance rescue assistance.

(9) Property

(10) Value — Cost, availability, and time required to reestablish facility contents should be consideredwhen determining the sensitivity of fire detection and the effectiveness of alarm processing,emergency response, and fire suppression.

(11) Replacement — Availability and time required to replace damaged facility contents should beconsidered when determining the sensitivity of fire detection and the effectiveness of alarmprocessing emergency response and fire suppression.

(12) Redundancy — Duplication of facility contents in separate locations might reduce the need forsensitivity of fire detection or other property protection system capabilities.



The term “defend-in-place” is used twice in the standard. “Defend in place” should be revised to “defend-in-place” in Annex C3 o be consistent with the usage in the source clause A.24.4.8 and because hyphens are generally used in compound nouns to communicate a single idea.



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



Street Address:

City:

State:

Zip:



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

Documents

Agenda Technical Committee on Protected Premises Fire ... › assets › files › AboutTheCodes › 72 › ...Services provided presentation: “Fire-Resistive, Fire-Resistant and