CORRELATING COMMITTEE ON SIGNALING SYSTEMS FOR THE … · 2016-03-28 · CORRELATING COMMITTEE ON SIGNALING SYSTEMS FOR THE PROTECTION OF LIFE AND PROPERTY NFPA 72 SECOND DRAFT CC

CORRELATING COMMITTEE ON SIGNALING SYSTEMS

FOR THE PROTECTION OF LIFE AND PROPERTY

NFPA 72 SECOND DRAFT CC MEETING AGENDA

October 28-29, 2014 Indianapolis, IN

Item No. Subject 14-10-1 Call to Order (8:00 A.M ET) 14-10-2 Roll Call 14-10-3 Approval of Agenda 14-10-4 Approval Meeting Minutes – January 7-8, 2014 [Enclosure] 14-10-5 Staff Remarks and Overview of New Process 14-10-6 Task Group Reports [Enclosure]

a) NFPA 720 versus NFPA 72 [Richardson/Schifiliti] b) Networks [W. Moore] c) Glossary of Terms [McNamara] d) Emergency Plan Terms [W. Moore & Bunker] e) Forms Correlation [Black] f) NFPA 72 versus NFPA 1221 [Aiken] g) Designer Terms [McNamara] h) Smoke Alarms in Commercial Occupancies [W. Moore] i) Strobe Operation [Berezowski] j) ANSI UL Reference Update [Shudak] k) TIA Supervisory Devices [J. Moore] l) Elevator Emergency Communications [Van Overmeiren] m) Wireless System Terminology [Van Keuren] n) New Process Training [NFPA Staff]

14-10-7 CC Liaison Reports

a) NFPA 25 [Norton] b) NFPA 101 [W. Moore] c) Others

14-10-8 Review of NFPA 72 Second Draft, PCs[Enclosure] and SRs

a) Chapter 2 – Group 3

b) Chapter 3 – Group 1 c) Chapter 7 – Group 2 d) Chapter 10 – Group 3 e) Chapter 12 – Group 4 f) Chapter 14 – Group 1 g) Chapter 17 – Group 1 h) Chapter 18 – Group 1 i) Chapter 21 – Group 2 j) Chapter 23 – Group 5 k) Chapter 24 – Group 4 l) Chapter 26 – Group 5 m) Chapter 27 – Group 2 n) Chapter 29 – Group 5 o) Annex F – Group 2 p) Annex G – Group 2

14-1-9 Other Business 14-1-10 Adjournment

1

First Draft Meeting Minutes

Correlating Committee on the Signaling Systems for the Protection of Life and Property

January 7-8, 2014 San Antonio, TX

(NFPA 72 CC First Draft Meeting)

Item 14-1-1 Call to Order Chair Robert P. Schifiliti (R.P. Schifiliti Associates, Inc.) called the meeting to order at 8:00 AM. Item 14-1-2 Roll Call In addition to the chair, the following CC members were present: Andrew Berezowski (P) National Electrical Manufacturer’s Association Art Black (P) Carmel Fire Protection Associates David Boswell (P) Hughes Associates, Inc J. Robert Boyer (P) UTC/Edwards Co Bruce Fraser (P) Fraser Fire Protection Services Vic Humm (P) Vic Humm & Associates Lynn Nielson (P) City of Henderson Thomas Norton (P) Norel Service Company Thomas Parrish (P) Telgian Corporation Tom Smith (P) National Electrical Contractors Association A.J. Capowski (A) Tyco Fire Suppression & Building Products Raymond Grill (A) ARUP Thomas Hammerberg (A) Automatic Fire Alarm Association Jeffrey Van Keuren (A) UTC Frank Van Overmeiren (A) FP& C Consultants, Inc L.J. Dallaire (NV TC Chair) TC on Single- and Multiple-Station Alarms &

Household Fire Alarm Systems Manuelita David (NV TC Chair) TC on Fundamentals of Signaling Systems David Lowrey (NV TC Chair) TC on Notification Appliances for Signaling Systems J. Jeffrey Moore (NV TC Chair) TC on Testing and Maintenance of Signaling Systems Warren E. Olsen (NV TC Chair) TC on Supervising Station Alarm Systems The following members attended by telephone/web due flight cancelations: John C. Fannin III SafePlace Corporation Rodger Reiswig (P) Tyco International Larry Shudak (P) Underwriters Laboratories Inc. Merton Bunker (NV TC Chair) TC on Protected Premises Fire Alarm Systems Wayne D. Moore (NV TC Chair) TC on Emergency Communications Systems The following guests were present: Shane Clary Bay Alarm Company Dan Finnegan Siemens

2

The following NFPA Staff were present: Bill Burke (Division Manager - Electrical Department) Lee F. Richardson (Secretary) Item 14-1-3 Approval of Meeting Agenda It was moved, seconded and voted unanimously affirmative that the meeting agenda be approved. Item 14-1-4 Approval of Meeting Minutes It was moved, seconded and voted unanimously affirmative that the minutes of the October 21, 2013 meeting of the Correlating Committee on Signaling Systems for the Protection of Life and Property be approved. Item 14-1-5 Staff Remarks & Overview of New Process Opening remarks, a review of the processing schedule, an overview of the new process, and a refresher on legal concerns were presented via PowerPoint. There was a brief discussion of “lessons” learned from the TC first draft meetings. When the response to a public input included a change to the code (first revision), many committee members appeared to have difficulty transitioning from the old process where a response (committee action and statement) to a public proposal was handled all in one record. With the new process there are two separate records involved: the public input and its resolution; and the first revision and its substantiation. Further, the substantiation for the first revision should be addressed without referring back to the public input or the submitter’s substantiation. The substantiation for the first revision should independently state what is changing from the current code and why. (It’s okay to use the public input substantiation as a starting point for the first revision committee statement as long as it is cleaned up to become the committee’s reason for change without referring to the PI or submitter’s proposed change or rationale). It was suggested that more extensive committee chair/committee member training be conducted to assist in the transition to the new process, especially with regard to the processing of material at meetings. (Training is further discussed under minutes item 14-1-11.) Item 14-1-6 Assignment of TC Responsibility Assignment of technical committee responsibilities was reviewed previously by the correlating committee. The responsibility for some chapters like Chapters 3 and 7 is assigned to multiple committees. This is also true to a lesser extent for other chapters. In an effort to try to minimize these occurrences (and the resulting confusion and complexity) the correlating committee made a handful of changes documented in the 2-21-13 meeting minutes. The actions of the committees during the first draft meetings went astray for two of these decisions. One of these was the decision to merge 10.11(SIG-ECS) and 23.8.1.1 (SIG-PRO) in Chapter 10 (SIG-FUN). The correlating committee decided to address this issue, if needed, during the process of reviewing the various committee actions in minutes item 14-1-9. The second of these decisions was to relocate all inspection, testing and maintenance requirements related to single- and multiple-station alarms and household fire alarm systems

3

to Chapter 29. This did not happen as a part of the committee actions for the first draft. The correlating committee reviewed the committee actions and decided not to pursue the relocation any further at this time. Item 14-1-7 Task Group Reports

a) NFPA 720 versus NFPA 72 – The correlating committee had a brief discussion and decided that a separate conference call should be held to address this issue in a more focused way. The CC chairman and NFPA Staff will develop a concept letter/email to outline the issues and various paths that might be taken. The conference call should be held late spring/early summer of 2014 and should include NFPA 720 TC members as guests. It was noted that this would not impact the 2014 edition of NFPA 720. It was also noted that approval by the Standards Council may be needed depending on the direction recommended by the correlating committee.

b) Networks – Correlating committee task group chair Wayne Moore reported that public inputs submitted by the task group had been reviewed by the SIG-PRO committee and first revisions were developed substantially based on the work of the task group. It was decided that the task group should remain active, review the work of the committee and submit public comments as needed for consideration at the second draft meetings.

c) Glossary of Terms - Correlating committee task group chair Jack McNamara was unable to attend. However, it was observed that public inputs submitted by the task group had been reviewed by the committees and in some cases first revisions were developed. It was decided that the task group should remain active, review the work of the committees and submit public comments as needed for consideration at the second draft meetings.

d) Emergency Plan Terms - Correlating committee task group co-chairs are Wayne Moore and Merton Bunker. [The issue involves the question of consistency in the use of emergency plan terms – “Response Plan,” versus “Emergency Response Plan,” versus “Emergency Plan” and others.] It was observed that task group activity was minimal. However, public inputs were submitted and first revisions were generated related to this subject. It was decided that the task group should remain active, review the work of the committees and submit public comments as needed for consideration at the second draft meetings. The scope of the task group needs to include the terms noted in minutes item 14-1-7 g).

e) Forms Correlation - Correlating committee task group chair Art Black indicated that task group activity was minimal. It was noted that only a couple of changes were made by first revisions. However, correlation is still needed to make sure the forms and there related annex examples are consistent. It was decided that the task group should remain active, review the work of the committees and submit public comments as needed for consideration at the second draft meetings.

f) NFPA 72 versus NFPA 1221 - Correlating committee task group chair Doug Aiken was unavailable. No report was provided.

g) Fire Risk Analysis Terms – After a brief discussion it was decided that this item should be incorporated with minutes item 14-1-7 d).

h) Designer Terms - Correlating committee task group chair Jack McNamara was unable to attend. The correlating committee decided to address this issue, if needed, during the process of reviewing the various committee actions in minutes item 14-1-9.

i) Smoke Alarms in Commercial Occupancies - Correlating committee task group chair Wayne Moore reported that the task group submitted changes to the IBC but

4

they were not accepted. It was reported that the situation may be made worse by a proposed revision that would require smoke alarms to be connected into building fire alarm systems. The task group will remain active and review the requirements in NFPA 72 to make sure that are no conflicts within NFPA 72 itself.

j) Strobe Operation - Correlating committee task group chair Andrew Berezowski reported that the task group submitted public input and first revisions were made in response. It was decided that the task group should remain active, review the work of the committee and submit public comments as needed for consideration at the second draft meetings.

Item 14-1-8 Correlating Committee Liaison Reports

a) NFPA 25 – Correlating committee liaison Tom Norton indicated that there was nothing to report.

b) NFPA 101– Correlating committee liaison Wayne Moore indicated that NFPA 101 is in the final stages of the revision cycle and that there were no issues to report.

c) NFPA 3 – NFPA 3/4 committee chair Wayne Moore reported that NFPA 3 is still a recommended practice and NFPA 4 is still a standard and looks good. It was noted that ICC is working on a document for commissioning.

Item 14-1-9 Review of NFPA 72 First Draft, Public Inputs, Committee Inputs, and

First Revisions The correlating committee reviewed the work of the committees chapter by chapter and produced correlating committee notes (CCNs) and first correlating revisions (FCRs) as needed for each chapter. There were a total of 20 CCNs and 18 FCRs developed by the correlating committee. The committee voted on each correlating committee action and accepted each chapter as a whole as amended by the correlating committee actions. NFPA staff noted that in five cases technical committee resolution statements were missing from the record. (These cases were PIs 597, 600, 446, 622 and 392.) This was because the PIs were reviewed by more than one committee and some of the committee statements were overwritten without preserving the original statements. Staff has a record of the missing statements and they will be added to record before that first draft is posted. In addition to the CCNs and FCRs developed by the correlating committee the following additional observations and actions are noted.

a) Chapter 2 – The concern was raised that ANSI/UL documents were not identified by the “edition” number used by UL. Larry Shudak volunteers to submit public comments as needed to provide document identification consistent with UL’s designations.

b) Chapter 3 – The SIG-NAS committee modified the ownership of the definition of “Hearing

Loss” in their action on FR 86 by assigning it to SIG-HOU. The correlating committee found this action to be acceptable.

It was observed that the reference to FR 64 in the committee statement for PI 69 should be to FR 364. It was requested that NFPA staff correct this reference if possible for the record.

c) Chapter 7 –

5

A comment expressed in voting on FR 267 raised the question of consistency in NFPA 72 on the use of terms like “enforcing authority” and “authority having jurisdiction.” The correlating committee accepted the committee’s action but has identified this question as a potential item for the Glossary of Terms task group to consider for the A2018 cycle.

The committee statement for FR 267 suggested that the correlating committee consider action to correlate the terms "system documents", "system record documents" and "record documents" throughout the Code. The correlating committee directed that the Glossary of Terms task group review the usage of these terms and, if needed, submit public comment(s) for consideration at the second draft meetings.

NFPA staff noted that FR 204 was processed by the SIG-FUN committee to add new 7.7.1.5. However since the proposed 7.7.1.5 would be officially under the scope of SIG-ECS, FR 204 was changed to CI 204. NFPA Staff provided the SIG-FUN committee notice of this action prior to the close of balloting.

NFPA staff noted that FR 303 was processed by the SIG-TMS committee to modify A.7.8.2. However since A.7.8.2 is officially under the scope of SIG-FUN, FR 303 was changed to CI 303. NFPA Staff provided the SIG-TMS committee notice of this action prior to the close of balloting.

NFPA staff noted that FR 361 was processed by the SIG-ECS committee to modify A.7.8.2. However since A.7.8.2 is officially under the scope of SIG-FUN, FR 361 was changed to CI 361. NFPA Staff provided the SIG-ECS committee notice of this action prior to the close of balloting.

d) Chapter 10 – NFPA staff noted that FR 65 was processed by the SIG-IDS committee to delete 10.4.5.1. However since 10.4.5.1 is officially under the scope of SIG-FUN, FR 65 was changed to CI 65. NFPA Staff provided the SIG-IDS committee notice of this action prior to the close of balloting.

e) Chapter 12 – After reviewing the changes for network circuit classification in 12.3.6 and A.12.3.6, it was noted that some of the terms used, such as “endpoints,” “uplink,” “switch” may be confused with usage in other parts of the code. The correlating committee directed the Glossary of Terms task group to work with the Networks task group to develop public comments for consideration at the second draft meetings to update/create definitions as needed.

f) Chapter 14 – FR 302 made changes to the required frequency of testing in Table 14.4.3.2 for Item 17(j), supervisory initiating devices. The changes were made inadvertently in the 2013 edition when the tables were merged and reformatted. (NFPA staff subsequently check to make sure the changes were not errata.) The changes made in FR 302 are as follows:

Change to Table 14.4.3.2 initiating devices Line item 17(j)(1) "Annual" changed to "Semi-Annual" in Periodic Frequency column. Change to Table 14.4.3.2 initiating devices Line item 17(j)(2) (3), (4) and (5) "Annual" changed to "Quarterly" in Periodic Frequency column.

The correlating committee concurred that the changes made for these items in the 2013 edition were inadvertent, not intended and not supported by technical substantiation. The CC directed that a TIA be developed and processed to change the testing frequencies in the 2013 edition back to the intended values (2010 edition), which will then be to be consistent with those of FR 302.

g) Chapter 17 – no additional minutes items were noted. h) Chapter 18 – no additional minutes items were noted. i) Chapter 21 – no additional minutes items were noted.

6

j) Chapter 23 – It was observed that a number of PIs and FRs made reference to FR 237. However, FR 237 does not appear to exist. NFPA staff indicated that the FR 237 record was changed to FR 366 in order to resolve a display issue that had occurred with Terra. (Notice was provide to the SIG-PRO committee prior to the close of balloting.) It was requested that NFPA staff correct these references if possible for the record.

k) Chapter 24 – It was noted that FR 329 added a requirement for the inspection and testing of elevator emergency communications systems. The correlating committee requested that a joint Chapter 14 and 24 task group be formed to reflect this change in Chapter 14. Frank Van Overmeiren agree to chair this task group.

l) Chapter 26 – no additional minutes items were noted. m) Chapter 27 – no additional minutes items were noted. n) Chapter 29 – As a part of the review for Chapter 29 it was noted that new

requirements had been added for mesh networks. Concerns were raised that the terminology used for wireless systems in Chapter 23 and 29 may need to be updated for correlation and consistency. The correlating committee directed that a joint task group between the two committees be formed to consider if any changes need to be submitted for consideration during the second draft meetings. Jeff Van Keuren agreed to chair the task group. Task group members will also include LJ Dallaire, Larry Shudak and Scott Barrett.

o) Annex G - The concern was raised that ANSI/UL documents were not identified by the “edition” number used by UL. Larry Shudak volunteers to submit public comments as needed to provide document identification consistent with UL’s designations.

Item 14-1-10 Processing Schedule – Second Draft Schedule NFPA staff requested the correlating committee to consider changing the schedule for the second draft TC and CC meetings. Having had the experience of splitting the first draft TC meetings into two separate weeks, it was observed that splitting the meetings did not realize the intended benefit of having committees consider correlation issues between meetings. In addition the time between the first set of meetings and balloting was excessively long. Further, it was noted that the current plan only allowed a two week period between the two sets of 2nd draft meetings. It was proposed to the correlating committee that all 2nd draft technical committee meetings be held during a single week – the week of June 23-27, 2014. After some discussion the correlating committee agreed to the proposed change. It was noted in the discussion that NFPA staff would need to provide agenda material by the end of May to provide committee members with sufficient time for review prior to the meetings. NFPA staff also proposed a change to the dates of the CC second draft meeting. The proposed meeting dates were October 28 & 29, 2014 instead of November 4-6, 2014. This was proposed to allow sufficient processing time for the second draft report. The correlating committee agreed to this change. The venues previously agreed to by the correlation committee for the TC meetings (Omaha or Indianapolis) were not proposed to change. However, it was suggested that Omaha be avoided for the proposed week because local events may cause hotel availability issues. As a postscript to the meeting, the NFPA Meetings Department has been unsuccessful in procuring meeting space in Indianapolis. Alternate venues are now being pursued.

7

Item 14-1-11 Discussion of Potential Training Methods & Strategy for New Process A recap of “lessons” learned (see minutes item 14-1-5) was provided and the correlating committee considered potential strategies to obtain a higher degree of success with committee member training. NFPA staff noted that there were a number of training videos available for on-line review. A list of these videos will be provided to committee members. Three significant training needs were identified during the discussion:

How to make public comments How to prepare prior to the meetings How to conduct business at the meetings

Concerning the latter need, it was suggested that perhaps a mock meeting be conducted for committee chairs with example situations prepared in advance for use during the meeting. A tentative date of April 29, 2014 was suggested for the mock meeting. NFPA staff will pursue the identification or development of training material to address these training needs. Item 14-1-12 Other Business (none) Item 14-1-13 Adjournment The meeting was adjourned at approximately 3:30 PM on January 8, 2014. Respectfully Submitted Lee F. Richardson Staff Liaison and Secretary

NFPA 72 Correlating Committee Task Groups & Action Items

(Reference 2-8-14 CC Meeting Minutes)

Task Group/ Action Item

TG Chair or Person Responsible

Issue/Activity Minutes Reference

NFPA 72 Vs NFPA 720

NFPA Staff & CC Chair

Outline the issues and possible paths to consider for a CC & SIG-CAR teleconference spring/early summer

Item 14-1-7a)

Networks TG Wayne Moore

Revisions to address the use of Ethernets for FAS [Class N circuits] / Review the work of the committee and submit public comments as needed.

Item 14-1-7b) Item 14-1-9f)

Glossary of Terms TG

Jack McNamara

Revisions to correlate with NFPA Glossary of Terms and MOS / Review the work of the committee and submit public comments as needed.

Item 14-1-7c) Item 14-1-7h) Item 14-1-9c) Item 14-1-9f)

Emergency Plan Terms TG

Merton Bunker &

Wayne Moore

Revisions to address the consistent use of emergency plan terms in the Code / Review the work of the committee and submit public comments as needed.

Item 14-1-7d) Item 14-1-7g)

Forms Correlation TG

Art Black Revisions to correlate Chapter 7 forms and the Code {terminology, format, annex examples} / Review the work of the committee and submit public comments as needed.

Item 14-1-7e)

NFPA 72 Vs NFPA 1221 TG

Doug Aiken Revisions to correlate NFPA 72 and NFPA 1221 and maintain each document within their respective scopes / Review the work of the committee and submit public comments as needed taking care not to introduce new material.

Item 14-1-7f)

Commercial Application of

Smoke Alarms TG

Wayne Moore

Revisions to model codes for the proper use of smoke alarms in commercial occupancies / Continue to follow and make there are no conflict in NFPA 72.

Item 14-1-7i)

Strobe Operation TG

Andrew Berezowski

Revisions to correlate the requirements concerning the operation of strobes for emergency communication systems / Review the work of the committee and submit public comments as needed.

Item 14-1-7j)

ANSI/UL Reference

Identification

Larry Shudak

Review Chapter 2 and Annex G references to provide reference identifications that correlated with those used by UL {e.g. edition number]

Item 14-1-9a) Item 14-1-9o)

TIA – Supervisory Device Testing

Frequency

Jeff Moore Develop a TIA for the 2013 edition of NFPA 72 to parallel the changes in FR 302 for the 2016 edition

Item 14-1-9f)

Elevator Emergency

Communications TG

Frank Van Overmeiren

Revisions to correlate Chapter 14 and 24 for changes made by FR 329 – Joint TMS/ECS task group

Item 14-1-9k)

Wireless System Terminology TG

Jeff Van Keuren

Revisions correlate terminology for wireless systems – join PRO/HOU task group. {see proposed changes in Chapter 29 for mesh network}

Item 14-1-9n)

New Process Training

NFPA Staff Develop training for SD meeting with emphasis on how to conduct business that the meetings

Item 14-1-11

Public Comment No. 235-NFPA 72-2014 [ Global Input ]

Delete references to the National Electrical code article 760 or any specific article, and just use the wordingas per the National Electrical Code.

Statement of Problem and Substantiation for Public Comment

The direct reference to only article 760 is leading to confusion as some persons do not understand how the NEC is arranged. Articles in chapters 1-4 apply to ALL wiring including Fire alarm and signaling circuits. Chapters 5-7 modify the requirements of chapters 1-4 therefore article 760 is not designed to be a stand alone chapter and should not be referred to as if it is. Chapter 8 is designed to be a stand alone chapter, except when specifically referenced back to a previous chapter.

Related Item

First Revision No. 92-NFPA 72-2013 [Section No. 12.2.4.2]

Public Input No. 514-NFPA 72-2013 [Section No. 12.2.4.2]

Submitter Information Verification

Submitter Full Name: Thomas Parrish

Organization: Telgian Corporation

Street Address:

City:

State:

Zip:

Submittal Date: Fri May 16 15:13:48 EDT 2014

Committee Statement

CommitteeAction:

Rejected but held

Resolution: SIG-PRS Action: Reject. The committee does not agree that specific references to an article or section of theNEC should be replaced with a general reference to the NEC. The specific references direct users to theintended requirements. It is important that users of the NEC be familiar with the organization of the NEC andunderstand how it is applied. // SIG-PRO Action Reject But Hold: In accordance with NFPA RegulationsGoverning the Development of NFPA Standards, this comment is held because it would propose somethingthat could not properly be handled with in the timeframe for processing the second draft. A task group hasbeen formed to review this for the next cycle. // SIG-FUN Action Reject: 12.2.3 already references thecomplete NEC. The subparagraphs specify requirements for circuits and pathways, which are covered inArticle 760. In addition, Article 760 references or amends the applicable articles in other parts of the NEC.SIG-HOU Action: Reject. The TC believes that reference to the specific article is important to understandingthe requirement.

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

1 of 365 9/22/2014 2:48 PM

Public Comment No. 236-NFPA 72-2014 [ Global Input ]

The establishment of requirements for public agencies who inspect and review plans for NFPA 72 installedsystems is outside the scope of this committee and is already addressed in other NFPA standards.


The establishment of requirements for public agencies who inspect and review plans for NFPA 72 installed systems is outside the scope of this committee and is already addressed in other NFPA standards. The requirements for fire inspection personnel and plan review personnel are addressed in NFPA 1031 and is outside the scope of this code to require additional qualifications.

Related Item

First Correlating Revision No. 15-NFPA 72-2014 [Global Input]

Public Input No. 169-NFPA 72-2013 [New Section after 10.5.4]




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: SIG-FUN Action Reject: The correlating committee has ruled that this is within the scope of thecommittee. No revised text was provided.


2 of 365 9/22/2014 2:48 PM

Public Comment No. 100-NFPA 72-2014 [ Section No. 2.3.4 ]

2.3.4 ISO Publications.

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

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


date update

Related Item

First Revision No. 1-NFPA 72-2013 [Section No. 3.3.189]


Submitter Full Name: Marcelo Hirschler

Organization: GBH International

Street Address:

City:

State:

Zip:

Submittal Date: Sun May 11 16:55:33 EDT 2014

Committee Statement

Committee Action: Rejected but see related SR

Resolution: SR-52-NFPA 72-2014

Statement: Reference updated.


3 of 365 9/22/2014 2:48 PM


3.3.11 Alarm.

An indication of the existence of a condition that requires immediate action response . (SIG-FUN)


Change "action" to "response" to be consistant with the defined condition-signal-response model adopted in the 3013 edition. We need to cascade the use of these three terms throughut the code.

Related Item



Submitter Full Name: Robert Schifiliti

Organization: R. P. Schifiliti Associates, I

Street Address:

City:

State:

Zip:

Submittal Date: Thu Apr 03 08:44:18 EDT 2014

Committee Statement

CommitteeAction:

Accepted


Statement: Change "action" to "response" to be consistent with the defined condition-signal-response model adoptedin the 2013 edition. We need to cascade the use of these three terms throughout the code.


4 of 365 9/22/2014 2:48 PM

Public Comment No. 147-NFPA 72-2014 [ New Section after 3.3.60 ]

New Definition

3.x * cross-connect. An apparatus which enables the connection of network and telecommunications cabling fromdevices, systems or equipment to the network and telecommunications cabling of other systems or equipment.


Substantiation (FCR 17)With the addition of Class N, some terminology used to express telecommunications and network concepts specifically within the context of Class N were not defined. This change is to reduce ambiguity when this term is encountered both within the text of this document and within real-world application.

Related Item



Submitter Full Name: Jeff Silveira

Organization: BICSI

Street Address:

City:

State:

Zip:

Submittal Date: Wed May 14 11:50:29 EDT 2014

Committee Statement

CommitteeAction:

Rejected

Resolution: The term is not used in the main body of the code and it's use in the proposed annex is not critical to theunderstanding of the annex material so an independent definition is not warranted.


5 of 365 9/22/2014 2:48 PM


3.3.64 Deficiency.

A condition that interferes with the service or reliability for which the part, system, or equipment was intended butdoes not rise to the level of an imparement . (SIG-TMS)


This issue was presented as a PI 545 and the comment returned was that it would create a conflict with the definition of impairment (3.3.129 now) there now exists a conflict that this would help resolve because not all deficiencies are actually an impairment. A missing Record of completion is technically a deficiency but yet will not impact the operation of the system. this becomes critical in states that include a color tag reporting system where all impairments require a red tag and requisite notifications. This also brings NFPA 72 in alignment with NFPA 25 to ensure that the water based systems connected to the fire alarm systems have corresponding requirements.

Related Public Comments for This Document

Related Comment Relationship

Public Comment No. 228-NFPA 72-2014 [Section No. 3.3.129]

Related Item

Public Input No. 545-NFPA 72-2013 [Section No. 3.3.63]




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: There are some deficiencies that rise to the level of an impairment as identified in A.3.3.129 and theproposed language would suggest otherwise.


6 of 365 9/22/2014 2:48 PM

Public Comment No. 127-NFPA 72-2014 [ New Section after 3.3.66.22 ]

Device (Class N)

A supervised component of a life safety system, that communicates with other components of lifesafety systems, and that collects environmental data, or performs specific input or output functionsnecessary to the operation of the life safety system.


With the addition of Class N pathways in the first draft, the term “device” was used specifically in the context of Class N, but not defined.The proposal is the recommendation by the Correlating Committee Task Group members thatwas comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of thecommittees.Wayne MooreA.J. CapowskiJoe L. CollinsDan HoronVic HummMichael PallettCharles PughRobert SchifilitiAviv SiegelLarry ShudakBob ElliottPaul CrowleyJeff SilveiraJeff KnightAndrew Berezowski



Public Comment No. 128-NFPA 72-2014 [New Section after A.3.3.66.19]

Related Item

First Revision No. 99-NFPA 72-2013 [New Section after 12.3.5]


Submitter Full Name: Michael Pallett

Organization: Telecor Inc.

Street Address:

City:

State:

Zip:

Submittal Date: Tue May 13 19:19:25 EDT 2014

Committee Statement

CommitteeAction:

Rejected but see related SR


Statement: With the addition of Class N pathways in the first draft, the term “device” was used with specificity in thecontext of Class N, but not defined. This revision also adds related annex to illustrate examples of what is aClass N device and how the distinction is drawn.


7 of 365 9/22/2014 2:48 PM


8 of 365 9/22/2014 2:48 PM


3.3.90 * Emergency Control Functions.

Building, fire, and emergency control elements or systems that are initiated by the fire alarm or signaling systemand either increase the level of life safety for occupants or control the spread of the harmful effects of fire or otherdangerous products . (SIG-PRO)


Removes unnecessary and limiting qualifiers.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The definition as currently worded is generic enough to cover various signaling systems such as COdetection systems. The qualifiers are inclusive and not limiting.


9 of 365 9/22/2014 2:48 PM


Endpoint (Class N)

The end of a pathway where a single addressable device or a control unit (FACU, ACU, or ECCU) is connected.


With the addition of Class N pathways in the first draft, the term “endpoint” was used specifically in the context of Class N, but not defined.The proposal is the recommendation by the Correlating Committee Task Group members thatwas comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of thecommittees.Wayne MooreA.J. CapowskiJoe L. CollinsDan HoronVic HummMichael PallettCharles PughRobert SchifilitiAviv SiegelLarry ShudakBob ElliottPaul CrowleyJeff SilveiraJeff KnightAndrew Berezowski



Public Comment No. 130-NFPA 72-2014 [New Section after A.3.3.91]

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: With the addition of Class N pathways in the first draft, the term “endpoint” was used with specificity in thecontext of Class N, but not defined. Related annex material is also added.


10 of 365 9/22/2014 2:48 PM


3.3.92 Emergency Response Plan.

A documented set of actions to address the planning for, management of and response to natural, technological,and man-made disasters and other emergencies. (SIG-ECS)


An emergency plan includes an emergency response plan plus other elements like a pre-plan and a communications plan – that leads to the ECS needs assesment.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: An emergency plan includes an emergency response plan - plus other elements like a pre-plan and acommunications plan – that leads to the ECS needs assessment.


11 of 365 9/22/2014 2:48 PM


3.3.122 Heat Alarm.

A single- or multiple-station alarm responsive to heat. (SIG-IDS HOU )

3.3.122.1 Mechanically Powered, Single-Station Heat Alarm.

A single-station heat alarm employing a mechanical power source such as a spring wound mechanism .(SIG-HOU)


Examples can never be complete and do not belong in definitions. If the TC wants to have examples, add them in the Annex.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted


Statement: The TC changes SIG-IDS to SIG-HOU. The TC revises the definition to delete the example as it is notrequired.


12 of 365 9/22/2014 2:48 PM


3.3.129 * Impairment.

An abnormal condition, of either a planned or emergency event, where a system, component, or function isinoperable A condition where a Fire Alarm or Signalling System componant or function is out of order and wherethe condtion can result in the Fire Alarm or Signalling System or unit not functioning when required . (SIG-FUN)


There Is an existing conflict that was created by the actions taken on PI 547 as well as FR244. The existing definition of impairment is too broad and the comment submitted back from the committee is not acceptable to me that the definition is too specific. These definitions shall be specific to allow proper application of the requirements. When the definitions are not specific is when there are issues and mis-interpretations. I further fell that the sub-definitions should be re-inserted as they help to clarify the conditions in states that require colored tagging and subsequent reporting of impairments.




Related Item

Public Input No. 547-NFPA 72-2013 [Section No. 3.3.130 [Excluding any Sub-Sections]]





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The proposed definition is no less broad. There is no problem identified as a consequence of theexisting definition.


13 of 365 9/22/2014 2:48 PM

Public Comment No. 34-NFPA 72-2014 [ Section No. 3.3.129 [Excluding any Sub-Sections] ]

An abnormal condition, of during either a planned or emergency event, where a system, component, or function isinoperable. (SIG-FUN)


Corrects incorrect modifier. The abmormal condition is not of the event, it is of the system, componant or function. Note also that we should really look at NFPA 25 that does a much better job of defining deficiencies and impairments. I tried years ago to take the same approach by the TMS TC felt that all impairments are critical.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

Committee Action: Accepted


Statement: Editorial correction.


14 of 365 9/22/2014 2:48 PM


3.3.150 Maintenance.

Work, including, but not limited to, repair, replacement, and inspections, testing and service, performed to ensurethat equipment operates properly. (SIG-TMS)


when the PI 550 was acted on the committee statement was made that the intent of CH. 14 is to differentiate between inspection, testing and maintenance. Chapter 14 uses all 3 items in all sections of 14.2.2 and does not define nor differentiate maintenance. This is an issue because in some jurisdictions people are only required to obtain licensing if they are conducting maintenance activities. Since the NFPA definition of maintenance does not include testing and inspection activities, they may be conducted by persons who are not properly licensed and may not be properly qualified. 14.2.2.1.2 requires that Inspection testing and maintenance programs shall verify operation of the system. This clearly defines the intent that all three of these elements, inspections, testing and maintenance are important to ensuring that systems work when required and I am simply trying to close a loophole that some possibly unqualified parties are exploiting to allow them to not meet the qualification requirements of other NFPA 72 sections as well as applicable state statutes.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: System inspection, testing and maintenance are separate components of a program to ensure continuedsystem performance in accordance with Section 14.2.2.


15 of 365 9/22/2014 2:48 PM


New Definition

3.x * media converter. A network device that connects two dissimilar types of cabling media, such as balancedtwisted-pair cabling and coaxial cabling, or balanced twisted-pair cabling and optical fiber cabling.


Substantiation (FCR 17)With the addition of Class N, some terminology used to express telecommunications and network concepts specifically within the context of Class N were not defined. This change is to reduce ambiguity when this term is encountered both within the text of this document and real-world application.

Related Item




Organization: BICSI

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The term is not used in the main body of the code and its use in the proposed annex is not critical to theunderstanding of the annex material, so an independent definition is not warranted.


16 of 365 9/22/2014 2:48 PM


3.3.168 Network (Public Emergency Alarm Repor ng Systems) .

3.3.168.1 Wireless Network (Public Emergency Alarm Repor ng Systems) .

The method of communications used in a public emergency alarm reporting system that consists of two or morepoints that are not connected by physical conductors. (SIG-PRS)

3.3.168.2 Wired Network (Public Emergency Alarm Repor ng Systems) .

The method of communications used in a public emergency alarm reporting system that consists of two or morepoints that are connected by physical conductors. (SIG-PRS)


The term “Network” is a ubiquitous term used more the 80 times in the code. This definition is particular to Public Emergency Alarm Reporting Systems, so the tile was added to give the definitions context. The term “wireless network” and “wired network” is only used in chapter 3 and chapter 27 making this definition specific to a public emergency alarm reporting systems; the context establishes clarity since both of these terms are commonly understood outside of the code.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:


Resolution: SR-1-NFPA 72-2014 Also refer to the committee response to PC 36.

Statement: The definitions for the terms “Wireless Network” and "wired network" are unique to the requirement ofChapter 27 and labels were added to recognize this distinction. Networks are used in other places in thecode and these definitions would not necessarily be applicable to the other usages.


17 of 365 9/22/2014 2:48 PM


3.3.168 Network.

3.3.168.1 Wireless Network.

The A method of communications used in a public emergency alarm reporting system that consists of two or morepoints that are not connected by physical conductors. (SIG-PRS)

3.3.168.2 Wired Network.

The A method of communications used in a public emergency alarm reporting system that consists of two or morepoints that are connected by physical conductors. (SIG-PRS)


Network is used throughout the code by many other chapters. Sanitize by deleting “used in a PEARS” in both locations. The PRS and ECS TCs should talk BEFORE the 2nd draft mtgs about these definitions.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: Retaining the definitions as they are currently shown is important to maintaining integrity of the Chapter 27requirements both now and in the future. The SIG-PRS committee wishes to retain the ownership of thesedefinitions. If other "network" definitions are desired for terms used elsewhere in the code, they can be put inplace without impacting the SIG-PRS definitions. Also refer to SR1.


18 of 365 9/22/2014 2:48 PM


TITLE OF NEW CONTENT

Type your content here ...

3.3.168.3 (NEW) Wireless Household Fire Alarm System Network - An arrangement of compatibletransmitter/transceiver devices that include smoke alarms/detectors, heat alarms/detectors, routers, and/or non-firealarm devices that communicate data between the devices and is independent or inclusive of an alarms/detectorsprimary alarm function. (SIG-HOU)


Add new definition to align with revisions to clause 29.7.8.3 - defining "Wireless Household Network".

Related Item

First Revision No. 58-NFPA 72-2013 [New Section after 29.7.8.2.5]


Submitter Full Name: Lawrence Shudak

Organization: UL LLC

Street Address:

City:

State:

Zip:


Committee Statement

Committee Action: Rejected

Resolution: Section 29.7.8.3 was deleted by SR-47 therefore the definition is not required.


19 of 365 9/22/2014 2:48 PM


3.3.198 Primary Battery (Dry Cell).

A nonrechargeable battery requiring periodic replacement. (SIG-FUN)

.

An electrochemical cell that is not capable of being discharged and then recharged such as a 9-volt alkaline cell.

Additional Proposed Changes

File Name Description Approved

SIG-TMS_Battery_Definitions.docx

SIG-TMS Battery Definitions is a list of definitions proposed as a result of SIG-TMS Battery Task Group. SIG-TMS Battery Task Group included support of IEEE Stationary Battery Committee and NFPA Committee representation from NFPA 111 & 110. New terminology is used in Battery Task Group recommendations to SIG-TMS Committee and better aligns NFPA terminology with industry standard. Primary battery requires revision, new definitions are submitted for SIG-FUN review.


Definitions would include terminology recommended as a result of SIG-TMS Battery task Group.



Public Comment No. 164-NFPA 72-2014 [Section No. 14.4.3.2]



Related Item




Submitter Full Name: Herbert Hurst

Organization: Savannah River Nuclear Solutio

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The battery terminology referenced is used inconsistently. A 9-volt battery consists of multiple cells; it is aprimary battery and not a primary cell. The term "primary battery" includes single-cell primary batteries andis the appropriate term.


20 of 365 9/22/2014 2:48 PM

NFPA 72 Battery terms used

3.3.i Cell. The basic electrochemical building block of a battery, characterized by a positive electrode, a negative electrode,

and electrolyte.

3.3.ii Primary Cell. An electrochemical cell that is not capable of being discharged and then recharged such as a 9-volt

alkaline cell.

3.3.iii Rechargeable Battery. An electrochemical cell that is capable of being discharged and then recharged.

3.3.iv Battery. Two or more cells connected together electrically. Cells may be connected in series or parallel, or both, to

provide the required operating voltage and current levels. Common usage permits this designation to be applied to a single

cell used independently.

3.3.v Battery Unit. See 3.3.x unit, multi-cell.

3.3.vii Valve-Regulated Lead-Acid Cell. A lead-acid cell that is sealed with the exception of a valve that opens to the

atmosphere when the internal pressure in the cell exceeds atmospheric pressure by a pre-selected amount. VRLA cells

provide a means for recombination of internally generated oxygen and the suppression of hydrogen gas evolution to limit

water consumption.

3.3.viii Starved Electrolyte Cell. A cell in which liquid electrolyte is immobilized, also known as AGM or Gel Cell.

3.3.viii.1 Absorbed Glass Mat (AGM) Cell. A cell in which the liquid electrolyte is immobilized in fiberglass or polymeric

fiber separators.

3.3.viii.2 Gelled Electrolyte Cell (Gel Cell) - a cell in which the electrolyte is immobilized by addition of a gelling agent

3.3.ix Trickle Charge. A continuous, low rate, constant current charge given to a cell or battery to maintain the unit in a

fully charged condition. See 3.3.x, Float Charge.

3.3.x Float Charge. A constant-voltage charge applied to a battery to maintain it in a fully charged condition, while

minimizing degradation or water consumption.

3.3.xi Fully Charged. A condition synonymous with 100% state of charge. See 3.3.k, State Of Charge.

3.3.xii State Of Charge. The stored or remaining capacity in a battery expressed as a percentage of its fully-charged

capacity.

3.3.xiii Load Test. A controlled discharge of a battery.

3.3.xiv Battery Charger. A device to restore and maintain the charge of a secondary battery.

3.3.xv Charge Controller. An electrical control device that regulates battery charging by voltage control and/or other

means, which may or may not be integrated into the battery charger.

3.3.xvi Unit, Multi-Cell. Multiple cells in a single container (e.g., 12-volt unit = 6 x 2-volt cells).


New Definition

3.x * ring topology. A physical or logical arrangement of a system or network in which nodes are connected in apoint-to-point serial fashion and forming an unbroken circular configuration. Each node receives and retransmits thesignal to the next node.



Related Item




Organization: BICSI

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected



21 of 365 9/22/2014 2:48 PM


3.3.271 Spacing.

A horizontally measured dimension related to the allowable coverage of detectors . (SIG-IDS)


Spacing relates to more than just detectors - joists, beams, horns, strobes, etc. This makes the definition more generic. Wnat examples? Put them in the annex.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: SIG-IDS: Spacing relates to more than just detectors.

(SIG-FUN Note: If this definition becomes more generic, the CC should consider reassigning it to theFundamentals TC.)


22 of 365 9/22/2014 2:48 PM


New Definition

3.x * switch (class N). A device that provides a centralized point of connection for network enabled equipment,enabling communications between all connected elements. A connection port on a switch represents a separatecommunications channel, and a switch may perform additional functions, such as port monitoring andcommunication (message) management. A switch is an integral part of a local area network (LAN),


With the addition of Class N, some terminology used to express telecommunications and network concepts specifically within the context of Class N were not defined. This change is to reduce ambiguity when this term is encountered both within the text of this document and within real-world application.

Related Item




Organization: BICSI

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected



23 of 365 9/22/2014 2:48 PM


New Definition

3.x * uplink (class N): A cabling connection between switches in a network. An uplink may also be known as a"trunk" or “backbone”.



Related Item




Organization: BICSI

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected



24 of 365 9/22/2014 2:48 PM


7.1.6

The requirements of other chapters shall also apply unless they are in conflict with this chapter.


CC NOTE: The following CC Note No. 23 Appeared in the First Draft Report.

The correlating committee makes reference to 7.1.6 and the phrase ", unless they are in conflict with this chapter." Requirements should not conflict. Where deviations from the requirements of other chapters are warranted they should be identified and addressed through appropriate allowances in the code language. The correlating committee directs the SIG-FUN committee to review the requirements in Chapter 7 with consideration to resolving any identified conflicts with other chapters. Where changes are made they should be done without introducing new material in the second draft phase. In addition the committee should consider rewording 7.1.6 to positive language. For example: The requirements of chapters x, y and z shall apply unless otherwise noted in this chapter.

Related Item

Correlating Committee Note No. 23-NFPA 72-2014 [Section No. 7.1.6]


Submitter Full Name: CC on SIG-AAC

Organization: CC on Signaling Systems for the Protection of Life and Property

Street Address:

City:

State:

Zip:

Submittal Date: Thu May 08 12:28:53 EDT 2014

Committee Statement



Statement: The section was revised to avoid the term "conflicts", since the code should not contain conflicts.


25 of 365 9/22/2014 2:48 PM


7.2.1 *

Where documentation is required by the authority having jurisdiction, the following list shall represent the minimumdocumentation required for new fire alarm systems, supervising station and shared communication equipment andemergency communications systems, including new systems and additions or alterations to existing systems:

(1)

(2) Riser diagram

(3) Floor plan layout showing locations of all devices, control equipment, and supervising station and sharedcommunications equipment with each sheet showing the following:

(4) Point of compass (north arrow)

(5) A graphic representation of the scale used

(6) Room use identification

(7) Building features that will affect the placement of initiating devices and notification appliances

(8) Sequence of operation in either an input/output matrix or narrative form

(9) Equipment technical data sheets

(10) Manufacturers’ published instructions, including operation and maintenance instructions

(11) Battery calculations (where batteries are provided)

(12) Voltage drop calculations for notification appliance circuits

Power loss db calculations for amplifier notification appliances

(1) Mounting height elevation for wall-mounted devices and appliances

(2) Where occupant notification is required, minimum sound pressure levels that must be produced by the audiblenotification appliances in applicable covered areas

(3) Pathway diagrams between the control unit, supervising station and shared communications equipment

(4) Completed record of completion in accordance with 7.5.7 and 7.8.2

(5) For software-based systems, a copy of site-specific software, including specific instructions on how to obtainthe means of system and software access (password)

(6) Record (as-built) drawings

(7) Records, record retention, and record maintenance in accordance with Section 7.7


Power loss db calculations have not been required and there hasn't been an issue in the field. This is an excessive requirement for minimum documentation. There was no technical justification provided is support of this requirement.

Related Item



Submitter Full Name: Raymond Grill

Organization: Arup

Street Address:

City:

State:

Zip:


* Written narrative providing intent and system description


26 of 365 9/22/2014 2:48 PM

Committee Statement

CommitteeAction:



Statement: A requirement for documented power loss dB calculations is redundant to the requirements for documentingthe minimum sound pressure levels that must be produced by the audible notification appliances in theapplicable covered areas and the requirement for voltage drop calculations for notification appliance circuits.The definition of "notification appliance circuit" includes the pathway connecting an amplifier to one or morespeakers.

Section 7.2.2(7) was revised to indicate that the battery calculations are intended to document that theprovided battery capacity and de-rating meet the requirements of this code.

The requirement for the completed record of inspection and testing was restored.


27 of 365 9/22/2014 2:48 PM


7.2.1*


(1)

(2) Riser diagram


(a) Point of compass (north arrow)

(b) A graphic representation of the scale used

(c) Room use identification

(d) Building features that will affect the placement of initiating devices and notification appliances






(9) Power loss db calculations for amplifier notification appliances


(11) Where occupant notification is required, minimum sound pressure levels that must be produced by theaudible notification appliances in applicable covered areas







CC NOTE: The following CC Note No. 1 appeared in the First Draft Report as First Revision No. FR267, and is also related to Public Input No. 258, 122, 21, 213, 22, 529, 558, and 560.

The correlating committee makes reference to the committee action in FR 267 and refers to the material shown deleted in item 9 of the list - "Completed record of inspection and testing ... ." The correlating committee directs the SIG-FUN committee to reconsider this deletion because a completed record of inspection and testing is required for new installations or additions or alterations to existing systems - in contrast to the reason for deletion provided in the committee statement.

Related Item











28 of 365 9/22/2014 2:48 PM





Street Address:

City:

State:

Zip:

Submittal Date: Wed Apr 30 09:08:27 EDT 2014

Committee Statement

CommitteeAction:



Statement: A requirement for documented power loss dB calculations is redundant to the requirements for documentingthe minimum sound pressure levels that must be produced by the audible notification appliances in theapplicable covered areas and the requirement for voltage drop calculations for notification appliance circuits.The definition of "notification appliance circuit" includes the pathway connecting an amplifier to one or morespeakers.




29 of 365 9/22/2014 2:48 PM


7.2.1*


(1)

(2) Riser diagram











(9) Power loss db calculations for amplifier notification appliances









Both terms “enforcing authority” (11 instances) and "Authority Having Jurisdiction" (279 instances) or "AHJ" (7 instances) are used interchangeably in the code. This should be raised to the Technical Correlating Committee to decide which is the preferred term to use in the code and to correlate all applicable references to use a single term throughout the code. SIG-FUN has indicated preference in this ballot cycle for the term "AHJ"; however, TCs should not have to spend time balloting and processing public input to change use of one term for another. It would help if the TCC or NFPA could identify a single term to be used in the code and make it consistent throughout.

Related Item



Submitter Full Name: Daniel Gauvin

Organization: Tyco/SimplexGrinnell

Street Address:

City:

State:



30 of 365 9/22/2014 2:48 PM

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The committee believes that this is a correlating issue, which should be handled by the CC. SIG-FUNprefers the term "authority having jurisdiction", if a single term is to be used. If there is a need to use theterm "enforcing authority" in some places, it should have a distinct definition.


31 of 365 9/22/2014 2:48 PM

Public Comment No. 56-NFPA 72-2014 [ Section No. 7.3.7.4 ]

7.3.7.4

Performance-based design documentation for signaling line circuit zoning shall be in accordance with 23.6.1.4 and23.6.1.5. (SIG-PRO)


CC NOTE: The following CC Note No. 3 appeared in the First Draft Report as First Revision No. 268, and is also related to Public Input No. 365 and 565.

The correlating committee makes reference to 7.3.7.4 introduced by FR 127. The correlating committee directs the SIG-PRO committee to reconsider the action on this FR to clear up the circular references that exist between 7.3.7.4 and its reference to 23.6.1.4 and the reference in 23.6.1.4 back to 7.3.7.4.

Related Item


Public Input No. 365-NFPA 72-2013 [New Section after 7.3.7.3]





Street Address:

City:

State:

Zip:


Committee Statement



Statement: The text is revised to remove a circular reference between 7.3.7.4 and 23.6.1.4.


32 of 365 9/22/2014 2:48 PM


7.5.5

Owner’s manuals for emergency communications systems shall be in accordance with Section 24.15 . (SIG-ECS)


This reference serves no purpose. It points to a section that points directly back to chapter 7:24.15 Documentation for Emergency Communications Systems.24.15.1 New Systems.Documentation requirements for new emergency communications systems shall comply with Sections 7.3 through 7.8 in addition to theminimum requirements of Section 7.2.

Related Item

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




Street Address:

City:

State:

Zip:


Committee Statement



Statement: The reference points to a section that points directly back to Chapter 7.


33 of 365 9/22/2014 2:48 PM


7.5.7 Record of Completion. (SIG-FUN)

7.5.7.1*

The record of completion shall be documented in accordance with 7.5.7 using either the record of completionforms, Figure 7.8.2(a) through Figure 7.8.2(f) , or an alternative document that contains only the elements ofFigure 7.8.2(a) through Figure 7.8.2(f) applicable to the installed system.

7.5.7.2*

The record of completion documentation shall be completed by the installing contractor and submitted to theenforcing authority and the owner at the conclusion of the job. The record of completion documentation shall bepermitted to be part of the written statement required in 7.5.2 and part of the documents that support therequirements of 7.5.9. When more than one contractor has been responsible for the installation, each contractorshall complete the portions of the documentation for which that contractor has responsibility.

7.5.7.3*

The preparation of the record of completion documentation shall be the responsibility of the qualified andexperienced person in accordance with 10.5.2.

7.5.7.4

The record of completion documentation shall be updated to reflect all system additions or modifications.

7.5.7.5

The updated copy of the record of completion documents shall be maintained in a documentation cabinet inaccordance with 7.7.2.

7.5.7.6 Revisions.

7.5.7.6.1

All modifications made after the initial installation shall be recorded on a revised version of the original completiondocuments.

7.5.7.6.2

The revised record of completion document shall include a revision date.

7.5.7.6.3*

Where the original or the latest overall system record of completion cannot be obtained, a new system record ofcompletion shall be provided that documents the system configuration as discovered during the current project’sscope of work.

7.5.7.7 Electronic Record of Completion.

7.5.7.7.1

Where approved by the authority having jurisdiction, the record of completion shall be permitted to be filedelectronically instead of on paper.

7.5.7.7.2

If filed electronically, the record of completion document shall be accessible with standard software and shall bebacked up.


CC NOTE: The following CC Note No. 6 appeared in the First Draft Report.

The correlating committee directs the SIG-TMS committee to reconsider their action on PI 596. Including the requirements from 14.6.1.2 (or an appropriate version of 14.6.1.2) within Chapter 7 rather than just a reference to 14.6.1.2 will improve the usability of the code. The correlating committee reminds the SIG-TMS committee that the relocated material will remain under their purview and an appropriate reference from Chapter 14 to the relocated material in Chapter 7 would suffice so that the detailed requirements are not repeated in both chapters.

Related Item







34 of 365 9/22/2014 2:48 PM

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:


Resolution: SR-53-NFPA 72-2014 For PC 89 SIG-FUN Rejected because the requested change belongs to SIG-TMS.SIG-TMS created SR 53.

Statement: Section 14.6.1.2 and related annex material has been relocated to become 7.5.8. Moving the requirementsfor site-specific software to Chapter 7.5.8 will improve usability of the Code by placing the site-specificsoftware documentation requirements in the “Documentation” chapter. A reference pointer to 7.5.8 has beenadded to 14.6.1.2 by SR 56.

Changes have been made to 7.5.8.1 (14.6.1.2.1) to ensure that the system owner is able to obtain theapplicable access credentials, which will allow the system owner to determine who conducts future systemprogramming for the installed system.


35 of 365 9/22/2014 2:48 PM


7.7.2.6 *

All documentation stored in electronic format shall be stored in current-day compatible media electronicdocumentation formats and interfaces shall be reviewed annually and updated by the owner or the owner'srepresentative as needed to maintain accessibility and compatibility with the associated system .


The first draft text does not indicate who is responsible for maintaining electronic documents formats so that they remain accessible. The building owner (or their representative) should be responsible for keeping the formats current because the documents are their property. The revised text is clearer and indicates that the building owner or their representative is responsible.

Related Item



Submitter Full Name: Andrew Berezowski

Organization: Honeywell Inc.

Affilliation: National Electrical Manufacturers Association

Street Address:

City:

State:

Zip:

Submittal Date: Mon Mar 17 14:08:17 EDT 2014

Committee Statement

CommitteeAction:



Statement: The first draft text does not indicate who is responsible for maintaining electronic documents formats so thatthey remain accessible. The building owner (or their representative) should be responsible for keeping theformats current because the documents are their property. The revised text is clearer and indicates that thebuilding owner or their representative is responsible.


36 of 365 9/22/2014 2:48 PM


7.7.2.6 *




NFPA_72_7-7-2-6_Publiccomment_mm.pdf PC Form


The first draft text does not indicate who is responsible for maintaining electronic documents formats so that they remain accessible. The building owner (or their representative) should be responsible for keeping the formats current because the documents are their property. The revised text is clearer and indicates that the building owner or their representative is responsible.

Related Item



Submitter Full Name: VINCE BACLAWSKI

Organization: NEMA

Street Address:

City:

State:

Zip:

Submittal Date: Mon May 19 10:14:50 EDT 2014

Committee Statement

CommitteeAction:



Statement: The first draft text does not indicate who is responsible for maintaining electronic documents formats so thatthey remain accessible. The building owner (or their representative) should be responsible for keeping theformats current because the documents are their property. The revised text is clearer and indicates that thebuilding owner or their representative is responsible.


37 of 365 9/22/2014 2:48 PM


Equipment not in service

Any equipment or system componant not in service or not being maintained in accordance with the provitsions ofthis code, shall be removed.

Equipment not in service due to replacement

Any equipment not in service due to system replacement shall be permitted to be tagged as out of service untilremoval is allowed after acceptance of the newly installed syetm so as not to permit the occupancy a period of timethat an active fire protection system would not be functioning.


Only some aspects of the fire protection system related abandoned equipment such as the cable is addressed by NFPA 70 as stated in the committees comment to PI 552. Also with the adoption of NFPA standards internationally in areas that may not adopt the series of international building and fire codes I do not feel it is in proper for the committee to reference that this requirement already exists in a code that is outside of the NFPA family. When a new fire alarm system is installed in a location that may have had an existing system there is no specified requirement to remove the existing no longer in service equipment. This proposal designates that all equipment not in service shall be removed. It is understood that at the time of transition from one system to the next that some devices may need to remain in place until testing, programming and other activities are competed, at that time these devices should be allowed a temporary signage only until the point they can and must be removed.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: Submitter has not provided sufficient evidence of a problem with abandoned equipment. This issue ishandled by the model fire codes.


38 of 365 9/22/2014 2:48 PM


10.4.4*

In areas that are not continuously occupied, an automatic smoke detector detection shall be provided at thelocation of each fire alarm control unit(s), notification appliance circuit power extenders, and supervising stationtransmitting equipment . The location of the required detector shall be in accordance with 17.7.3.2 . to providenotification of fire at that location.

Exception: Where ambient conditions prohibit installation of an automatic smoke detector detection , anautomatic heat detector detection shall be permitted.


The addition of the text "The location of the required detector shall be in accordance with 17.7.3.2." would require full coverage for the area. The intent of 10.4.4 is to provide detection of a specific hazard at the equipment location. The text of 10.4.4 in NFPA 72 2013 and associated annex material (which has been present for two code revision cycles) requires detection specifically at the equipment location and revision is not warranted. This comment proposes returning the text to the NFPA 72 2013 edition language.

Related Item

First Revision No. 247-NFPA 72-2013 [Section No. 10.4]




Affilliation: National Electrical Manufactures Association

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The text, "the location of the required detector shall be in accordance with 17.7.3.2," was deleted because itwould require full detection coverage for the area. The intent of 10.4.4 is to provide detection for a specifichazard at the equipment location so that fire is likely to be detected before the equipment is disabled. Therequirement to provide notification of a fire condition before equipment is disabled by fire should apply toemergency communication system signaling because of the analogous life safety purpose of ECS.


39 of 365 9/22/2014 2:48 PM


10.4.4 *

In areas that are not continuously occupied, an automatic smoke detector shall be provided at the location of eachfire alarm control unit(s), notification appliance circuit power extenders, and supervising station transmittingequipment . The location of the required detector shall be in accordance with 17.7.3.2 . to provide notification offire at that location.

Exception: Where ambient conditions prohibit installation of an automatic smoke detector, an automatic heatdetector shall be permitted.


The additional requirement added to 10.4.4; i.e. "The location of the required detector shall be in accordance with 17.7.3.2." creates a conflict and needs to be rejected. The intent of 10.4.4 is to provide a single detector at the location of each fire alarm control unit(s), notification appliance circuit power extenders, and supervising station transmitting equipment. Specifying that the location of the detector must comply with 17.7.3.2 triggers all 17.7.3.2 requirements including spacing requirements which trigger requirements for more than 1 detector. For example 17.7.3.2.3.1 requires detectors be placed on a ceiling at nominal 30' spacing and at one-half spacing from walls and partitions. The intent of 10.4.4 is to provide a single detector for object protection not to trigger requirements for area detection where the object to be protected is installed.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:





40 of 365 9/22/2014 2:48 PM


10.4.4*

In areas that are not continuously occupied, an automatic smoke detector shall be provided at the location of eachfire alarm control unit(s), notification appliance circuit power extenders, and supervising station transmittingequipment. The location of the required detector shall be in accordance with 17.7.3.2.



The requirement to provide notification of a fire condition prior to a control unit(s) or equipment used for transmitting notification signals being attacked by fire is equally, or in some instances more critical in an ECS or MNS system. This is a "fundamental" requirement that should apply to all signaling system notification equipment located in areas that are not continuously occupied as specified in 10.4.4. Also see Public Comment 72-72 on related annex material.

Related Item

Public Input No. 109-NFPA 72-2013 [Section No. A.10.4.4]




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:





41 of 365 9/22/2014 2:48 PM


10.5.1.1

Fire alarm system and emergency communications system plans and specifications shall be developed inaccordance with this Code by persons who are experienced in the proper design the design , application,installation, and testing of the systems.


This PC deletes the word "proper" from the section. Table 2.2.2.3 of the Manual of Style identifies “proper” as an unenforceable term.

Related Item

Public Input No. 349-NFPA 72-2013 [Section No. 10.5]


Submitter Full Name: Todd Warner

Organization: Brooks Equipment Company, Inc.

Street Address:

City:

State:

Zip:


Committee Statement



Statement: This revision deletes the word "proper" from the section, because it is unnecessary.


42 of 365 9/22/2014 2:48 PM


10.5.1.2

State or local licensure regulations shall be followed to determine qualified personnel. Depending on state or locallicensure regulations, qualified personnel shall include, but not be limited to, one or more of the following:

(1) Personnel who are registered, licensed, or certified by a state or local authority

(2) Personnel who are certified by a nationally recognized certification organization acceptable to the authorityhaving jurisdiction

(3) Personnel who are factory trained and certified for fire alarm system design and/or emergencycommunication system design of the specific type and brand of system and who are acceptable to theauthority having jurisdiction


Section 1.2.1.2 of the Manual of Style states, “All nonmandatory or informational text shall appear either in Annex A or as a separate annex in the case of specialized information.” Because this section is a partial list of possible ways that personnel may become qualified, it is by definition, informational and therefore must be relocated to the annex.







Public Comment No. 153-NFPA 72-2014 [Section No. A.10.5.3]

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The appropriate mandatory requirement is properly stated in the code. The submitter does not providejustification for removal of the mandatory clause.


43 of 365 9/22/2014 2:48 PM


10.5.1.2

State or local licensure regulations shall be followed to determine qualified personnel. Depending on state or locallicensure regulations, qualified personnel shall include, but not be limited to, All System Design Personnel shalldemonstrate knowledge of all the tasks required of them by this Code by one or more of the following:

(1) Personnel who are registered Registered , licensed, or certified by a state or local authority

(2) Personnel who are certified by a nationally recognized certification organization Certified by an organizationacceptable to the authority having jurisdiction

(3) Personnel who are factory trained and certified Certified for fire alarm system design and/or emergencycommunication system design of the specific type and brand of system and who are acceptable to theauthority having jurisdiction by the manufacturer or the manufacturer's agent


This format is used by SIG-SSS for 10.5.5. This format more clearly creates a minimum requirement by stating that personnel must demonstrate competence.

Section 2.2.2.5 of the Manual of Style states that language shall be adoptable but the current language is circular in nature. If adopted, this Code would be the law but this section refers to state and local licensure regulations which would be the requirements of this Code which refers to state and local licensure regulations, and so on forever.

This rewording and reformatting address the concern of using “nationally recognized” to describe a certification organization. Section 2.5.1.1 of the Manual of Style states, “Documents shall be written to enhance their international acceptability and adoptability” which is achieved by removing this term. Additionally, the term “nationally recognized” fails to acknowledge and recognize that there are many state and local organizations that provide continuing education. This point speaks directly to the justification for PI349 which stated that as written the Code restricts trade.

This rewording also removes “but not limited to” from the body of the code. Section 1.2.3 states, “This code establishes minimum required levels of performance…” Phrases of this nature are perfectly acceptable when applied to informational or explanatory material but do not establish a minimum standard.

The term “factory trained” is reworded to represent training by the manufacturer or the manufacturer’s agent. Factory trained is jargon and 2.5.2 of the Manual of Style states that “use of jargon… shall be avoided.” Using “manufacturer or manufacturer’s agent” is reflective of industry practice.






Related Item





Street Address:

City:

State:

Zip:



44 of 365 9/22/2014 2:48 PM

Committee Statement

CommitteeAction:



Statement: The TC maintains the requirement to follow state or local licensure regulations. The text has been revisedto address the submitters concerns regarding the use of the term “nationally recognized” as being overlyrestrictive.


45 of 365 9/22/2014 2:48 PM


10.5.1.2




(3) Personnel who are factory trained are trained and certified by the manufacturer or the manufacturer's agentfor fire alarm system design and/or emergency communication system design of the specific type and brand ofsystem and who are acceptable to the authority having jurisdiction


This PC readdresses PI349. This change makes it clear that the training and certification should be provided by the manufacturer of the equipment or an authorized agent of the manufacturer, since this is the current industry practice. This wording has proven to be acceptable in the NFPA process as it appears in the current editions of other NFPA standards.





Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The TC maintains the requirement to follow state or local licensure regulations. The text has been revisedto address the submitters concerns regarding the use of the term “nationally recognized” as being overlyrestrictive.


46 of 365 9/22/2014 2:48 PM


10.5.1.5

System Design Trainees shall be under the direct supervision of a qualified System Designer


Currently there is no provision for trainees to develop the competence and experience required by the Code. This section is similar to 10.5.5.3.



Public Comment No. 143-NFPA 72-2014 [New Section after 10.5.2.3]


Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted


Statement: The section adds provision for trainees to develop the competence and experience required by theCode. This section is similar to 10.5.5.3.


47 of 365 9/22/2014 2:48 PM


10.5.2.2




(3) Personnel who are factory trained and certified for fire alarm system installation and/or emergencycommunications system installation of the specific type and brand of system and who are acceptable to theauthority having jurisdiction





Public Comment No. 145-NFPA 72-2014 [Section No. 10.5.1.2] Similar issue

Public Comment No. 146-NFPA 72-2014 [New Section after A.10.4.4] Similar issue




Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected



48 of 365 9/22/2014 2:48 PM


10.5.2.2

State or local licensure regulations shall be followed to determine qualified personnel. Depending on state or locallicensure regulations, qualified personnel shall include, but not be limited to, one All system installation personnelshall demonstrate knowledge of all tasks required of them in this Code by one or more of the following:


(2) Personnel who are certified by a nationally recognized certification organization Certified by an organizationacceptable to the authority having jurisdiction

(3) Personnel who are factory trained and certified Certified for fire alarm system installation and/or emergencycommunications system installation of the specific type and brand of system and who are acceptable to theauthority having jurisdiction by the manufacturer or the manufacturer's agent.









Public Comment No. 155-NFPA 72-2014 [Section No. 10.5.1.2] Similar



Related Item





Street Address:

City:

State:

Zip:



49 of 365 9/22/2014 2:48 PM

Committee Statement

CommitteeAction:



Statement: The TC maintains the requirement to follow state or local licensure regulations. The text has been revisedto address the concerns regarding the use of the term “nationally recognized” as being overly restrictive.


50 of 365 9/22/2014 2:48 PM


10.5.2.2




(3) Personnel who are factory trained are trained and certified by the manufacturer or the manufacturer's agentfor fire alarm system installation and/or emergency communications system installation of the specific type andbrand of system and who are acceptable to the authority having jurisdiction





Public Comment No. 73-NFPA 72-2014 [Section No. 10.5.1.2] Similar change


Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The TC maintains the requirement to follow state or local licensure regulations. The text has been revisedto address the concerns regarding the use of the term “nationally recognized” as being overly restrictive.


51 of 365 9/22/2014 2:48 PM


10.5.2.4

System Installation Trainees shall be under the direct supervision of a qualified System Installer


Currently, there is no provision for trainees to develop the competence and experience required by the Code. This section is similar to 10.5.5.3.



Public Comment No. 142-NFPA 72-2014 [New Section after 10.5.1.4] Similar issue and text.


Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The section adds provision for trainees to develop the competence and experience required by theCode. This section is similar to 10.5.5.3.


52 of 365 9/22/2014 2:48 PM


10.5.3 * Inspection, Testing, and Service Personnel. (SIG-TMS)

10.5.3.1 * Inspection Personnel.

Inspections shall be performed by personnel who have developed competence developed knowledge throughtraining and experience that are acceptable to the authority having jurisdiction or meet the requirement of .

10.5.3.2 * Testing Personnel.

Testing personnel shall have knowledge and experience of the testing requirements contained in this Code, of theequipment being tested, and of the test methods. That knowledge and experience shall be acceptable to theauthority having jurisdiction or meet the requirement of .

10.5.3.3 Service Personnel.

Service personnel shall have knowledge and experience of the maintenance and servicing requirementscontained in this Code, of the equipment being serviced or maintained, and of the servicing or maintenancemethods. That knowledge and experience shall be acceptable to the authority having jurisdiction or meet therequirement of .

10.5.3. 4

Qualified personnel shall include, but not be limited to, one or more of the following:

(1)

(2)

(3)

(4) Personnel who are employed and qualified by an organization listed by a nationally recognized testinglaboratory for the servicing of systems within the scope of this Code

10. 5 .3.5 * Programming Personnel.

10.5.3.5.1

Personnel programming a system shall be certified by the system manufacturer.

10.5.3.5.2

System installation personnel shall be permitted to configure systems in the field per manufacturers’ publishedinstructions.

10.5.3.5.3

System end users shall be permitted to manage system operation per manufacturers’ published instructions ortraining.

10.5.3.6 Evidence of Qualification.

Evidence of qualifications shall be provided to the authority having jurisdiction upon request.





Public Comment No. 145-NFPA 72-2014 [Section No. 10.5.1.2] similar

Public Comment No. 146-NFPA 72-2014 [New Section after A.10.4.4] similar


Public Comment No. 151-NFPA 72-2014 [New Section after A.10.4.4] similar


Related Item


* Personnel who are factory trained and certified for the specific type and brand of system being serviced

* Personnel who are certified by a nationally recognized certification organization acceptable to theauthority having jurisdiction

* Personnel, either individually or through their affiliation with an organization that is registered, licensed,or certified by a state or local authority to perform service on systems addressed within the scope of thisCode


53 of 365 9/22/2014 2:48 PM




Street Address:

City:

State:

Zip:


Committee Statement


Resolution: Listed items are mandatory and required to be acceptable to the authority having jurisdiction.


54 of 365 9/22/2014 2:48 PM


10.5.3.4

Qualified personnel shall include, but not be limited to, demonstrate knowledge of all tasks required of them by thisCode by one or more of the following:

(1)

(2) Personnel who are C

(3)

(4) Personnel who are employed Employed and qualified by an organization listed by a nationally recognizedtesting laboratory for the servicing of systems within the scope of this Code












Public Comment No. 163-NFPA 72-2014 [Section No. A.10.5.3.4(2)]

Related Item





Street Address:

City:

State:

* Personnel who are factory trained and certified for the certifiedby the manufacturer or the manufacturer'sagent for the specific type and brand of system being serviced

* certified by a nationally recognized certification an organization acceptable to theauthority having jurisdiction

* Personnel, either individually or through their affiliation with an organization that is registered, Rregistered,licensed, or certified by a state or local authority to perform service on systems addressed within the scope ofthis Code


55 of 365 9/22/2014 2:48 PM

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The terms "factory trained and certified" is current verbiage used by UL. A demonstration of knowledge isbetter described by requiring one or more of the current list. It is important to note individual or affiliationnationally recognized certification programs as listed in the annex. It is important to note certification withstate or local licensing.


56 of 365 9/22/2014 2:48 PM


10.5.3.4

Qualified personnel shall include, but not be limited to, one or more of the following:

(1)

(2)

(3)

(4) Personnel who are employed and qualified by an organization listed by a nationally recognized testinglaboratory for the servicing of systems within the scope of this Code





Public Comment No. 73-NFPA 72-2014 [Section No. 10.5.1.2] Similar wording

Public Comment No. 74-NFPA 72-2014 [Section No. 10.5.2.2] Similar wording


Related Item





Street Address:

City:

State:

Zip:


Committee Statement


Resolution: The terms "factory trained and certified" is current verbiage used by UL.

* Personnel who are factory are trained and certified by the manufacturer or the manufacturer's agent forthe specific type and brand of system being serviced

* Personnel who are certified by a nationally recognized certification organization acceptable to the authorityhaving jurisdiction

* Personnel, either individually or through their affiliation with an organization that is registered, licensed, orcertified by a state or local authority to perform service on systems addressed within the scope of this Code


57 of 365 9/22/2014 2:48 PM


10.5.3.7

Inspection, Testing and Service Trainees shall be under the direct supervision of qualified Inspection, Testing andService personnel.


Currently, there is no provision for trainees to develop the competence and experience required by the Code. This section is similar to 10.5.5.3.



Public Comment No. 142-NFPA 72-2014 [New Section after 10.5.1.4] Similar issue and text.

Public Comment No. 143-NFPA 72-2014 [New Section after 10.5.2.3] Similar issue and text

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: Trainee requirements are directed under the specific requirements of their employer and as directed andregulated by state or local registration and licensing.


58 of 365 9/22/2014 2:48 PM


10.5.4.3

State or local licensure regulations shall be followed to determine qualified personnel. Depending on state or locallicensure regulations, qualified personnel shall include, but not be limited to, Qualified personnel shalldemonstrate knowledge of all tasks required of them by one or more of the following:


(2) Personnel who meet Meet the requirements of NFPA 1031, Standard for Professional Qualifications for FireInspector and Plan Examiner

(3) Personnel who are assigned Assigned to perform plan reviews and inspections by the authority havingjurisdiction







Public Comment No. 155-NFPA 72-2014 [Section No. 10.5.1.2] Similar text and format



Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The TC maintains the requirement to follow state or local licensure regulations. The committee hasclarified the options permitted to demonstrate qualification.


59 of 365 9/22/2014 2:48 PM

Public Comment No. 45-NFPA 72-2014 [ Section No. 10.6.5.1.1 ]

10.6.5.1.1

The branch circuit supplying the fire alarm equipment(s) or emergency communication system(s) shall be suppliedby one of the following:

(1) Electric utility

(2) An engine-driven generator in or equivalent in accordance with 10.6.11.2, where a person trained in itsoperation is on duty at all times

(3) An engine-driven generator arranged or equivalent arranged for cogeneration with an electric utility inaccordance with 10.6.11.2, where a person trained in its operation is on duty at all times


The phrase "or equivalent" should not have been removed. While Chapter 1 has language permitting an equivalent means, the term is necessary here to provide immediate context. Without it an engine driven generator is the only implied choice and does not allow for other choices that are not connected to or dependent upon the utility.

Related Item



Submitter Full Name: John McCamish

Organization: NECA IBEW Electrical Training

Affilliation: IBEW

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted


Statement: The phrase "or equivalent" should not have been removed. While Chapter 1 has language permitting anequivalent means, the term is necessary here to provide immediate context. Without it an engine drivengenerator is the only implied choice and does not allow for other choices that are not connected to ordependent upon the utility.


60 of 365 9/22/2014 2:48 PM

Public Comment No. 173-NFPA 72-2014 [ New Section after 10.6.7.2.1.1 ]

(2)

For battery operation less than 70 °F, battery calculations shall include a temperature correction for the minimumexpected design temperature.


Chapter 10 Fundamentals would align with Chapter 14 changes proposed by SIG-TMS Battery Task Group.







Related Item






Street Address:

City:

State:

Zip:


Committee Statement


Resolution: No substantiation was provided.


61 of 365 9/22/2014 2:48 PM

Public Comment No. 42-NFPA 72-2014 [ Section No. 10.11 ]

10.11 *

ECS Priority Signals.

Visible indication of priority signals shall be automatically indicated within 10 seconds at the fire alarm control unitor other designated location. (SIG-ECS) Actuation Time. Actuation of alarm notification appliances or emergencyvoice communications, emergency control function interface devices, and annunciation at the protected premisesshall occur within 10 seconds after the activation of an initiating device.

A.23.8.1.1 Actuation of an initiating device is usually the instant at which a complete digital signal is achieved atthe device, such as a contact closure. For smoke detectors or other automatic initiating devices, which can involvesignal processing and analysis of the signature of fire phenomena, actuation means the instant when the signalanalysis requirements are completed by the device or fire alarm control unit software. A separate fire alarm controlunit contemplates a network of fire alarm control units forming a single large system as defined in Section 23.8. Forsome analog initiating devices, actuation is the moment that the fire alarm control unit interprets that the signal froman initiating device has exceeded the alarm threshold programmed into the fire alarm control unit. For smokedetectors working on a system with alarm verification, where the verification function is performed in the fire alarmcontrol unit, the moment of actuation of smoke detectors is sometimes determined by the fire alarm control unit.

It is not the intent of this paragraph to dictate the time frame for the local fire safety devices to complete theirfunction, such as fan wind-down time, door closure time, or elevator travel time


During the First Draft the Correlating Committee requested to combine section 10.11 with 23.8.1.1 and stated that the section are basically the same. As I reviewed the actions of the TC section 23.8.1.1 was entirely deleted regarding signals. The existing section 10.11 was basically left alone. Somehow the lost material from 23.8.1.1 needs to be added to 10.11. We cannot just delete 23.8.1.1 and believe everything is covered with 10.11 as it stands.

Related Item



Submitter Full Name: Rodger Reiswig


Street Address:

City:

State:

Zip:

Submittal Date: Tue Apr 15 14:46:59 EDT 2014

Committee Statement

CommitteeAction:



Statement: SIG-ECS: The action at the first draft entirely deleted section 23.8.1.1 regarding signals. The lost annexmaterial from A.23.8.1.1 was added to A.10.11. The TC suggests that the Correlating Committee review10.12 as similar material to 10.11.

SIG-FUN: Reject PC-42: The proposed annex material was already added to A.10.12.1 in the First Draft.


62 of 365 9/22/2014 2:48 PM



63 of 365 9/22/2014 2:48 PM

10.12 Alarm Signals.

10.12.1 *

Alarm signals shall be visually and audibly annunciated at the following locations:

(1) Fire alarm control unit for protected premises alarm systems

(2) Building fire command center for in-building fire emergency voice/alarm communications systems

(3) Supervising station location for systems installed in compliance with Chapter 26

A.10.12.1 This requirement is intended for alarm signal annunciation only and does not apply to the activation ofpublic or private alarm notification appliances.

10.12.2 Visual indication shall be provided at the locations required by 10.12.1 when alarm conditions are returnedto normal.

10.12.3 *

Actuation of alarm notification appliances or emergency voice communications, emergency control functioninterface devices, and annunciation at the protected premises shall occur within 10 seconds after the activation ofan initiating

devicedevice in accordance with the required sequence of operations .

10.12.

2 4

Visible notification appliances, textual visible notification appliances, and speaker notification appliances located inthe same area shall be activated and deactivated as a group unless otherwise required by an ECS emergencyresponse plan. (SIG-ECS)

10.12.3 5 *

Visible alarm strobe notification appliances shall not be activated when speaker notification appliances are used aspermitted by 24.3.6 for non-emergency paging. (SIG-ECS)

10.12.4 6 *

A coded alarm signal shall consist of not less than three complete rounds of the number transmitted.

10.12.5 7

Each round of a coded alarm signal shall consist of not less than three impulses.

10.12.6 8 *

Resetting of alarm signals shall comply with 23.8.2.2.

10.12.7 9

The subsequent occurrence of a fault on an initiating device circuit or a signaling line circuit used for other than theinterconnection of control units shall not affect previously transmitted unacknowledged alarm signals.

10.12.8

An alarm signal that has been deactivated at the protected premises shall comply with

(see public comment that proposes relocation of 10.12.

8.1 and

10

.12.8.2.

10.12.8.1

The audible and visible alarm signal at the control unit only shall automatically reactivate every 24 hours or lessuntil alarm signal conditions are restored

to

normal.

10. 12.8.2

The audible and visible alarm signal shall operate until it is manually silenced or acknowledged.

13.6)


The code requirements with respect to where visible and audible alarm signal annunciations are required are not clear in the current code. The text proposed clarifies where, at a minimum, alarm signal annunciation is required. This was done


64 of 365 9/22/2014 2:48 PM

in a way that matches the existing signaling location requirements for annunciation of supervisory and trouble signals. The text is consistent with the format of 10.14.1 and 10.15.7. The text proposed clarifies the language used to describe the 24 hour alarm reminder and clarifies that visual indication of alarms at the control unit and on annunciators are not to be turned off when the occupant notification appliances are silenced. The added text in the renumbered 10.12.3 is necessary to indicate that notification appliances are to be activated in accordance with the sequence of operations defined by the input / output matrix or narrative required in 7.4.9. Note that PI-647 was "emulated" by NFPA staff and the content was not entered correctly. This comment seeks to present the PI content as originally intended. See the associated revision regarding PI-647 in section 10.13.5.Not that this item should be considered in combination with Public Comment 16 which relocates 10.12.8 to 10.13 with some revisions.

Related Item

Public Input No. 647-NFPA 72-2013 [Sections 10.12.1, 10.12.2]




Street Address:

City:

State:

Zip:

Submittal Date: Tue Mar 18 15:04:14 EDT 2014

Committee Statement

CommitteeAction:

Rejected

Resolution: SIG-FUN: Annunciation is already covered in 10.18. The committee's intent is to require both audible andvisible annunciators to be reactivated. SIG-ECS: The comment renumbers and changes the sections butdoes not change sections under the SIG-ECS jurisdiction, therefore, all changes should be adjudicated bySIG-FUN.


65 of 365 9/22/2014 2:48 PM


10.12 Alarm Signals.

10.12.1*

Actuation of alarm notification appliances or emergency voice communications, emergency control functioninterface devices, and annunciation at the protected premises shall occur within 10 seconds after the activation ofan initiating device.

10.12.2*

Visible notification appliances, textual visible notification appliances, and speaker notification appliances located inthe same area shall be activated and deactivated as a group unless otherwise required by an ECS emergencyresponse plan. (SIG-ECS)

10.12.3*

Visible alarm strobe notification appliances shall not be activated when speaker notification appliances are used aspermitted by 24.3.6 for non-emergency paging. (SIG-ECS)

10.12.4*

A coded alarm signal shall consist of not less than three complete rounds of the number transmitted.

10.12.5

Each round of a coded alarm signal shall consist of not less than three impulses.

10.12.6*

Resetting of alarm signals shall comply with 23.8.2.2.

10.12.7


10.12.8

An alarm signal that has been deactivated at the protected premises shall comply with 10.12.8.1 and 10.12.8.2.

10.12.8.1

The audible and visible alarm signal at the control unit only shall automatically reactivate every 24 hours or lessuntil alarm signal conditions are restored to normal.

10.12.8.2



The annex material shown associated with 10.12.3 should be associated with 10.12.2 as indicated in the committee statement for FR-363

Related Item





Affilliation: SIG-ACC Strobe Operation TG

Street Address:

City:

State:

Zip:

Submittal Date: Fri Mar 21 16:13:20 EDT 2014

Committee Statement

CommitteeAction:




66 of 365 9/22/2014 2:48 PM

Statement: The annex material associated with 10.12.2 should be associated with 10.12.3 as indicated in thecommittee statement for FR-363.


67 of 365 9/22/2014 2:48 PM


10.12.7



If an unacknowledged alarm signal has been transmitted to a control unit, the alarm signal should not be affected by a subsequent fault regardless of whether the faulted IDC or SLC is used for interconnection of control units or not. Current panel technology should be capable of storing and maintaining receipt of alarm conditions regardless of a subsequent IDC or SLC fault condition. If an IDC or SLC is used to interconnect panels, the receipt of unacknowledged alarms should be maintained on the control unit or the panel interconnection should not be allowed.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement


Resolution: Deleting the text would prevent the proper reset operation of interconnected panels.


68 of 365 9/22/2014 2:48 PM


10.13* Fire Alarm Notification Appliance Deactivation.

10.13.1

A means for turning off activated alarm notification appliance(s) shall be permitted.

10.13.2*

When an occupant notification alarm signal deactivation means is actuated, both audible and visible notificationappliances shall be simultaneously deactivated.

10.13.3

The fire alarm notification deactivation means shall be key-operated or located within a locked cabinet, or arrangedto provide equivalent protection against unauthorized use.

10.13.4

The means shall comply with the requirements of 10.18.1.

10.13.5 The means for deactivating alarm notification appliances shall not deactivate the visual indicationrequired at the locations identified in 10.12.1 (new) and 10.18

10.13.6* (relocated from 10.12.6 and modified)

An alarm signal that has been deactivated at the protected premises shall comply with 10.13.6.1 and 10.13.6.2.

10.13.6.1

Only the audible indication required by 10.12.1shall reactivate every 24 hours or less until alarm conditions arerestored to normal.

10.13.6.2


A10.13.6 This requirement does not apply to occupant notification appliances. The occupant notificationappliances should not reactivate as a result of this requirement.

10.13.7 Subsequent Actuation of Initiating Devices.

10.13.5 7 .1

Subsequent actuation of nonaddressable initiating devices on other initiating device circuits shall cause thenotification appliances to reactivate.

10.13.5 7 .2

Subsequent actuation of addressable alarm initiating devices of a different type in the same room or addressablealarm initiating devices in a different room on signaling line circuits shall cause the notification appliances toreactivate.

10.13.6 8

A fire alarm notification deactivation means that remains in the deactivated position when there is no alarmcondition shall operate an audible trouble notification appliance until the means is restored to normal.


Note that this comment should be considered in combination with Public Comment 15.The code requirements with respect to where visible and audible alarm signal annunciations are required are not clear in the current code. The text proposed by comments 15 and 16 clarifies where, at a minimum, alarm signal annunciation is required and how subsequent alarms should be indicated. This was done in a way that matches the existing signaling location requirements for annunciation of supervisory and trouble signals. The text is consistent with the format of 10.14.1 and 10.15.7. The text proposed clarifies the language used to describe the 24 hour alarm reminder and clarifies that visual indication of alarms at the control unit and on annunciators are not to be turned off when the occupant notification appliances are silenced. Note that PI-647 was "emulated" by NFPA staff and the content was not entered correctly. This comment seeks to present the PI content as originally intended. See the associated revision regarding PI-647 in section 10.12.

Related Item

Public Input No. 647-NFPA 72-2013 [Sections 10.12.1, 10.12.2]




Street Address:

City:


69 of 365 9/22/2014 2:48 PM

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The committee's intent is to reactivate the audible and visible annunciators. In addition, moving the text to10.13 may create confusion with reactivation of notification appliances.


70 of 365 9/22/2014 2:48 PM


12.3.6 Class N.

A pathway shall be designated as Class N when it performs as follows:

(1)

(2) A loss of intended communications between endpoints shall be annunciated as a trouble signal.

(3) A single open, ground, short, or combination of faults on one pathway shall not affect any other pathway.

(4)

(5)


This section and designation should either be delted or only included in Annex material. The code is specifying performance that isn't required by any codes or standards and can't be applied without the expnatory material of the Annex. The annex material should also be delted becasue it conflicts with the perofrmance criteria stated. The diagrams inthe Annex material show both redundant paths to converge in single switches which is lost would render both paths unusable.

There is nothing to preclude a designer to design for this performance. It doesn't need to be incorproated in NFPA 72.

Related Item




Organization: Arup

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: Chapter 12 sets the requirements for circuit classes that may be used by other codes or standards orother chapters of this code. Class N has been added as an option to Chapter 23 circuit requirements.

* It includes two or more pathways where operational capability of the primary pathway and a redundantpathway to each device shall be verified through end-to-end communication.

Exception: When only one device is served, only one pathway shall be required.

* Conditions that affect the operation of the primary pathway(s) and redundant pathway(s) shall beannunciated as a trouble signal when the system’s minimal operational requirements cannot be met.

* Primary and redundant pathways shall not be permitted to share traffic over the same physical segment.


71 of 365 9/22/2014 2:48 PM


12.6.17Where fire alarm control units are interconnected by an auxiliary alarm, supervisory, or trouble relay thatuses clip-on or slide-on type terminals, the circuit shall be configured to provide supervision of theterminals so that their detachment from the auxiliary relay will result in a trouble indication at the masterfire alarm control unit.

EW CONTENT

Type your content here ...



NFPA_571.pdf Clip-on terminal strip


Statement of Problem and Substantiation for Public Input

Several fire alarm panel manufacturers utilize "slip-on" or "clip-on" terminal strips for ease of maintenance. When this type terminal strip is used on output contacts for circuits supervised by another panel, the terminal strip can be removed without generating a signal. If the terminal strip is removed to facilitate service, it could be accidentally left off and prevent the transmission of signals.

Related Item





Street Address:

City:

State:

Zip:

Submittal Date: Wed Mar 19 13:30:10 EDT 2014

Committee Statement

CommitteeAction:

Rejected

Resolution: This is already covered by listing requirements in UL 864, and therefore field documentation would beprovided similar to the submitter's solution. The new section is not needed because any devices monitoredby the panel are required to be supervised. Additionally, under section 12.6.9 the submitter's cited wiringwould be permitted.


72 of 365 9/22/2014 2:48 PM

To Master Fire Alarm Control Unit from Dedicated Function Fire Alarm Control Unit.

TBX

Slip-on type terminal Strip TBX may be removed from circuit board with end-of –line resistors in place. Although circuit is lifted the wiring configuration will not result in a trouble indication at the Master FACU.

TBX


14.2.2.2.4

In the event that any equipment is observed to be part of a recall program, the building owner system owner or thesystem owner's designated representative shall be notified in writing .


I concur with a comment made during final balloting that reference to the owner or owner's designated representative should be made, along with the means of notification. The First Revision of this section has, therefore, been amended to reflect that.

Related Item



Submitter Full Name: Joe Scibetta

Organization: BuildingReports

Street Address:

City:

State:

Zip:


Committee Statement



Statement: The wording of 14.2.2.2.4 was changed to be similar to the verbiage in the existing Section 14.2.2.2.3.


73 of 365 9/22/2014 2:48 PM


14.3.1 *


74 of 365 9/22/2014 2:48 PM

Unless otherwise permitted by 14.3.2 , visual inspections shall be performed in accordance with the schedules inTable 14.3.1 or more often if required by the authority having jurisdiction.

Table 14.3.1 column 2 heading was revised by a tentative interim amendment (TIA).

Table 14.3.1 Visual Inspection

ComponentInitial

AcceptancePeriodic

FrequencyMethod Reference

1. All equipment X Annual

Ensure there are no changes that affectequipment performance. Inspect for buildingmodifications, occupancy changes, changesin environmental conditions, device location,physical obstructions, device orientation,physical damage, and degree of cleanliness.

14.3.4

2. Control equipment:

(a) Fire alarmsystems monitored foralarm, supervisory, andtrouble signals

Verify a system normal condition.

(1) Fuses X Annual

(2) Interfacedequipment

X Annual

(3) Lamps andLEDs

X Annual

(4) Primary (main)power supply

X Annual

(5) Trouble signals X Semiannual

(b) Fire alarmsystems unmonitoredfor alarm, supervisory,and trouble signals


(1) Fuses X Weekly

(2) Interfacedequipment

X Weekly

(3) Lamps andLEDs

X Weekly

(4) Primary (main)power supply

X Weekly

(5) Trouble signals X Weekly

3. Reserved

4.Supervising stationalarm systems —transmitters

Verify location, physical condition, and asystem normal condition.

(a) Digital alarmcommunicatortransmitter (DACT)

X Annual

(b) Digital alarm radiotransmitter (DART)

X Annual

(c) McCulloh X Annual

(d) Radio alarmtransmitter (RAT)

X Annual

(e) All other types ofcommunicators

X Annual

5.

In-building fireemergency voice/alarmcommunicationsequipment

X Semiannual Verify location and condition.

6. Reserved


75 of 365 9/22/2014 2:48 PM

ComponentInitial

AcceptancePeriodic

FrequencyMethod Reference

7. Reserved

8. Reserved

9. Batteries

Inspect for corrosion or leakage. Verify tightness of connections.

10.6.10

(a) VRLA

Batteries q XEnsure month and year of manufacture is marked in the month/year formaton each battery cell/unit.

Semiannually Verify marking of the month/year of manufacture

(all types). 10.6.10 (a) Lead-acid X Monthly Visually inspect electrolyte level. (b) Nickel-cadmium X Semiannual (c) Primary ( (d) Sealed lead-acid X Semiannual 10.

on each battery cell/unit. Replace any cell/unit if alarmequipment manufacturer’sreplacement date has beenexceeded

X Semiannually

Verify tightness of battery connections. Inspectterminals for corrosion, excessive container/coverdistortion, cracks in cell/unit or leakage ofelectrolyte. Replace any battery cell/unit ifcorrosion, distortion, or leakage is observed.

(b) Primary( dry cell)

X

Monthly

Semiannually

Verify marking of the month/year of manufacture Replace if alarm equipment/batterymanufacturer’s replacement date has been exceeded, not to exceed 12 months. Verify tightnessof connections. Inspect for corrosion or leakage. Replace any battery cell/unit if corrosion orleakage is observed.

10. Reserved

11. Remote annunciators X Semiannual Verify Remote annunciatorsXSemiannualVerify location and condition.

12. Notification appliance circuit power extenders X Annual Verify extendersXAnnualVerify proper fuse ratings, ifany. Verify that lamps and LEDs indicate normal operating status of the equipment. 10. 613 613 . Remote powersupplies X Annual Verify suppliesXAnnualVerify proper fuse ratings, if any. Verify that lamps and LEDs indicatenormal operating status of the equipment. 10. 614 614 . Transient suppressors X Semiannual Verify TransientsuppressorsXSemiannualVerify location and condition.

15. Reserved

16. Fiber-optic cable connections X Annual Verify connectionsXAnnualVerify location and condition.

17. Initiating devices

Verify location and condition (all devices).

(a) Air sampling


76 of 365 9/22/2014 2:48 PM

(1) General X Semiannual Verify GeneralXSemiannualVerify that in-line filters, if any, areclean. 17.7.3.6

(2) Sampling system piping and sampling ports X N/A Verify portsXN/AVerify that sampling systempiping and fittings are installed properly, appear airtight, and are permanently fixed. Confirm that samplingpipe is conspicuously identified. Verify that sample ports or points are not obstructed. 17.7.3.6

(b) Duct detectors

(1) General X Semiannual Verify GeneralXSemiannualVerify that detector is rigidly mounted.Confirm that no penetrations in a return air duct exist in the vicinity of the detector. Confirm the detectoris installed so as to sample the airstream at the proper location in the duct. 17.7.5.5

(2) Sampling tube X Annual Verify tubeXAnnualVerify proper orientation. Confirm the samplingtube protrudes into the duct in accordance with system design. 17.7.5.5

(c) Electromechanical releasing devices devicesXSemiannual

X Semiannual

(d) Fire extinguishing system(s) or suppression system(s) switches switchesXSemiannual

X Semiannual

(e) Manual fire alarm boxes boxesXSemiannual

X Semiannual

(f) Heat detectors detectorsXSemiannual

X Semiannual

(g) Radiant energy fire detectors X Quarterly Verify detectorsXQuarterlyVerify no point requiringdetection is obstructed or outside the detector’s field of view. 17.8

(h) Video image smoke and fire detectors X Quarterly Verify detectorsXQuarterlyVerify no pointrequiring detection is obstructed or outside the detector’s field of view. 17.7.7; 17.11.5

(i) Smoke detectors (excluding one- and two-family dwellings) XSemiannual

X Semiannual

(j) Projected beam smoke detectors X Semiannual Verify detectorsXSemiannualVerify beampath is unobstructed.

(k) Supervisory signal devices devicesXQuarterly

X Quarterly

(l) Waterflow devices devicesXQuarterly

X Quarterly18. Reserved


77 of 365 9/22/2014 2:48 PM

19. Combination systems

Verify location and condition (all types).

(a) Fire extinguisher electronic monitoring device/ systems systemsXSemiannual

X Semiannual

(b) Carbon monoxide detectors/ systems systemsXSemiannual

X Semiannual20. Fire alarm control interface and emergency control functioninterface X Semiannual Verify interfaceXSemiannualVerify location and condition.

21. Guard’s tour equipment X Semiannual Verify equipmentXSemiannualVerify locationand condition.

22. Notification appliances

Verify location and condition (all appliances).

(a) Audible appliances appliancesXSemiannual

X Semiannual

(b) Audible textual notification appliances appliancesXSemiannual

X Semiannual

(c) Visible appliances

(1) General GeneralXSemiannual

X Semiannual 18.5.5

(2) Candela rating X N/A Verify ratingXN/AVerify that the candela rating markingagrees with the approved drawings. 18.5. 523 523 . Exit marking audible notificationappliances X Semiannual Verify appliancesXSemiannualVerify location andcondition.

24. Reserved

25. Area of refuge two-way communication system X Annual VerifysystemXAnnualVerify location and condition.

26. Reserved

27. Supervising station alarm systems — receivers


78 of 365 9/22/2014 2:48 PM

(a) Signal receiptXDailyVerify receipt X Daily Verify receipt of signal.

(b) Receivers X Annual Verify ReceiversXAnnualVerify location and normalcondition.

28. Public emergency alarm reporting system transmission equipment

Verify location and condition.

(a) Publicly accessible alarm box boxXSemiannual

X Semiannual

(b) Auxiliary box boxXAnnual

X Annual

(c) Master box

(1) Manual operation operationXSemiannual

X Semiannual

(2) Auxiliary operation operationXAnnual

X Annual29. Reserved

30. Mass notification system

(a) Monitored for integrity


(1) Control equipment

(i) Fuses FusesXAnnual

X Annual

(ii) Interfaces InterfacesXAnnual


79 of 365 9/22/2014 2:48 PM

X Annual

(iii) Lamps/ LED LEDXAnnual

X Annual

(iv) Primary (main) power supply supplyXAnnual

X Annual

(2) Secondary power batteries batteriesXAnnual

X Annual

(3) Initiating devices devicesXAnnual

X Annual

(4) Notification appliances appliancesXAnnual

X Annual

(b) Not monitored for integrity; installed prior to adoption of the2010 edition


(1) Control equipment

(i) Fuses FusesXSemiannual

X Semiannual

(ii) Interfaces InterfacesXSemiannual

X Semiannual

(iii) Lamps/ LED LEDXSemiannual

X Semiannual

(iv) Primary (main) power supply supplyXSemiannual

X Semiannual

(2) Secondary power batteries batteriesXSemiannual

X Semiannual

(3) Initiating devices devicesXSemiannual

X Semiannual

(4) Notification appliances appliancesXSemiannual

X Semiannual

(c) Antenna X Annual Verify AntennaXAnnualVerifylocation and condition.


80 of 365 9/22/2014 2:48 PM

(d) Transceivers X Annual VerifyTransceiversXAnnualVerify location and condition.

Note: N/A = not applicable, no minimum requirement established.


The change is submitted as part of SIG-TMS Battery Task Group originating from Public Comments No. 602-NFPA 72-2013 and 625-NFPA 72-2013. Additional recommendations are proposed for Item 9 in Table 14.4.3.2 with uploaded text.






Public Comment No. 173-NFPA 72-2014 [New Section after 10.6.7.2.1.1]

Related Item






Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected but held

Resolution: The TC agrees with the technical merits of the Public Comment but it introduces new material to the extentto which the Public Comment proposes a change that is new or substantial, the complexity of the issuesraised and sufficient debate and public review has not taken place. The TC is proposing to process a TIA inparallel to correct/update the battery testing requirements within the 2016 edition of NFPA 72.


81 of 365 9/22/2014 2:48 PM



82 of 365 9/22/2014 2:48 PM

14.4.3.2 *


83 of 365 9/22/2014 2:48 PM

Systems and associated equipment shall be tested according to Table 14.4.3.2.

Table 14.4.3.2 was revised by tentative interim amendments (TIAs).

Table 14.4.3.2 Testing

ComponentInitial

Acceptance

Periodic

FrequencyMethod

1. All equipment X See Table 14.3.1.

2.Control equipment andtransponder

(a) Functions X Annually

Verify correct receipt of alarm, supervisory, and troublesignals (inputs); operation of evacuation signals andauxiliary functions (outputs); circuit supervision,including detection of open circuits and ground faults;and power supply supervision for detection of loss ofac power and disconnection of secondary batteries.

(b) Fuses X Annually Verify rating and supervision.

(c) Interfacedequipment

X Annually

Verify integrity of single or multiple circuits providinginterface between two or more control units. Testinterfaced equipment connections by operating orsimulating operation of the equipment beingsupervised. Verify signals required to be transmitted atthe control unit.

(d) Lamps and LEDs X Annually Illuminate lamps and LEDs.

(e) Primary (main)power supply

X AnnuallyTest under maximum load, including all alarmappliances requiring simultaneous operation. Testredundant power supplies separately.

3.Fire alarm control unittrouble signals

(a) Audible and visual X AnnuallyVerify operation of control unit trouble signals. Verifyring-back feature for systems using a trouble-silencingswitch that requires resetting.

(b) Disconnectswitches

X Annually

If control unit has disconnect or isolating switches,verify performance of intended function of each switch.Verify receipt of trouble signal when a supervisedfunction is disconnected.

(c) Ground-faultmonitoring circuit

X AnnuallyIf the system has a ground detection feature, verify theoccurrence of ground-fault indication whenever anyinstallation conductor is grounded.

(d) Transmission ofsignals to off-premiseslocation

X AnnuallyActuate an initiating device and verify receipt of alarmsignal at the off-premises location.

Create a trouble condition and verify receipt of atrouble signal at the off-premises location.

Actuate a supervisory device and verify receipt of asupervisory signal at the off-premises location. If atransmission carrier is capable of operation under asingle- or multiple-fault condition, activate an initiatingdevice during such fault condition and verify receipt ofan alarm signal and a trouble signal at the off-premiseslocation.

4.Supervising stationalarm systems —transmission Equipment

(a) All equipment X Annually

a Test all system functions and features in accordancewith the equipment manufacturer’s publishedinstructions for correct operation in conformance withthe applicable sections of Chapter 26.


84 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

Except for DACT, actuate initiating device and verifyreceipt of the correct initiating device signal at thesupervising station within 90 seconds. Uponcompletion of the test, restore the system to itsfunctional operating condition.

If test jacks are used, conduct the first and last testswithout the use of the test jack.

(b) Digital alarmcommunicatortransmitter (DACT)

X Annually

Except for DACTs installed prior to adoption of the2013 edition of NFPA 72 that are connected to atelephone line (number) that is also supervised foradverse conditions by a derived local channel, ensureconnection of the DACT to two separate means oftransmission.

Test DACT for line seizure capability by initiating asignal while using the telephone line (primary line forDACTs using two telephone lines) for a telephone call.Ensure that the call is interrupted and that thecommunicator connects to the digital alarm receiver.Verify receipt of the correct signal at the supervisingstation. Verify each transmission attempt is completedwithin 90 seconds from going off-hook to on-hook.

Disconnect the telephone line (primary line for DACTsusing two telephone lines) from the DACT. Verifyindication of the DACT trouble signal occurs at thepremises fire alarm control unit within 4 minutes ofdetection of the fault. Verify receipt of the telephoneline trouble signal at the supervising station. Restorethe telephone line (primary line for DACTs using twotelephone lines), reset the fire alarm control unit, andverify that the telephone line fault trouble signal returnsto normal. Verify that the supervising station receivesthe restoral signal from the DACT.

Disconnect the secondary means of transmission fromthe DACT. Verify indication of the DACT trouble signaloccurs at the premises fire alarm control unit within 4minutes of detection of the fault. Verify receipt of thesecondarey means trouble signal at the supervisingstation. Restore the secondary means of transmission,reset the fire alarm control unit, and verify that thetrouble signal returns to normal. Verify that thesupervising station receives the restoral signal from thesecondary transmitter.

Cause the DACT to transmit a signal to the DACRwhile a fault in the telephone line (number) (primaryline for DACTs using two telephone lines) is simulated.Verify utilization of the secondary communication pathby the DACT to complete the transmission to theDACR.

(c) Digital alarm radiotransmitter (DART)

X AnnuallyDisconnect the primary telephone line. Verifytransmission of a trouble signal to the supervisingstation by the DART occurs within 4 minutes.

(d) McCullohtransmitter

X AnnuallyActuate initiating device. Verify production of not lessthan three complete rounds of not less than threesignal impulses each by the McCulloh transmitter.

If end-to-end metallic continuity is present and with abalanced circuit, cause each of the following fourtransmission channel fault conditions in turn, and verifyreceipt of correct signals at the supervising station:

(1) Open


85 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

(2) Ground

(3) Wire-to-wire short

(4) Open and ground

If end-to-end metallic continuity is not present and witha properly balanced circuit, cause each of the followingthree transmission channel fault conditions in turn, andverify receipt of correct signals at the supervisingstation:

(1) Open

(2) Ground


(e) Radio alarmtransmitter (RAT)

X Annually

Cause a fault between elements of the transmittingequipment. Verify indication of the fault at the protectedpremises, or transmission of trouble signal to thesupervising station.

(f) Performance-basedtechnologies

X Annually

Perform tests to ensure the monitoring of integrity ofthe transmission technology and technology path.

Where shared communications equipment is used aspermitted by 26.6.3.1.14, provided secondary (standby)power sources shall be tested in accordance with Table14.4.3.2, item 7, 8, or 9, as applicable.

Where a single communications path is used,disconnect the communication path. Manually initiatean alarm signal transmission or allow the check-in

(handshake) signal to be transmitted automatically. b

Verify the premises unit annunciates the failure within200 seconds of the transmission failure. Restore thecommunication path.

Where multiple communication paths are used,disconnect both communication paths. Manually initiatean alarm signal transmission. Verify the premisescontrol unit annunciates the failure within 200 secondsof the transmission failure. Restore bothcommunication paths.

5.Emergencycommunicationsequipment

(a) Amplifier/tonegenerators

X AnnuallyVerify correct switching and operation of backupequipment.

(b) Call-in signalsilence

X AnnuallyOperate/function and verify receipt of correct visual andaudible signals at control unit.

(c) Off-hook indicator(ring down)

X AnnuallyInstall phone set or remove phone from hook and verifyreceipt of signal at control unit.

(d) Phone jacks X AnnuallyVisually inspect phone jack and initiatecommunications path through jack.

(e) Phone set X Annually Activate each phone set and verify correct operation.

(f) Systemperformance

X AnnuallyOperate the system with a minimum of any fivehandsets simultaneously. Verify voice quality andclarity.

6. Engine-driven generator X Monthly

If an engine-driven generator dedicated to the systemis used as a required power source, verify operation ofthe generator in accordance with NFPA 110, Standardfor Emergency and Standby Power Systems, by thebuilding owner.


86 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

7.Secondary (standby)

power supply c X Annually

Disconnect all primary (main) power supplies and verifythe occurrence of required trouble indication for loss ofprimary power. Measure or verify the system’s standbyand alarm current demand and verify the ability ofbatteries to meet standby and alarm requirementsusing manufacturer’s data. Operate general alarmsystems a minimum of 5 minutes and emergency voicecommunications systems for a minimum of 15 minutes.Reconnect primary (main) power supply at end of test.

8.Uninterruptible powersupply (UPS)

X Annually

If a UPS system dedicated to the system is used as arequired power source, verify by the building owneroperation of the UPS system in accordance with NFPA111, Standard on Stored Electrical Energy Emergencyand Standby Power Systems .

9. Battery testsPrior to conducting any battery testing, verify by theperson conducting the test, that all system softwarestored in volatile memory is protected from loss.

(a) Lead-acid type

(1) Batteryreplacement

X Annually

Replace batteries in accordance with therecommendations of the alarm equipmentmanufacturer or when the recharged battery voltage orcurrent falls below the manufacturer’srecommendations.

(2) Charger test X Annually

With the batteries fully charged and connected to thecharger, measure the voltage across the batteries witha voltmeter. Verify the voltage is 2.30 volts per cell±0.02 volts at 77°F (25°C) or as specified by theequipment manufacturer.

(3) Discharge test X Annually

With the battery charger disconnected, load test thebatteries following the manufacturer’srecommendations. Verify the voltage level does not fallbelow the levels specified. Load testing can be bymeans of an artificial load equal to the full fire alarmload connected to the battery.

(4) Load voltage test X Semiannually

With the battery charger disconnected, load test thebatteries following the manufacturer’srecommendations. Verify the voltage level does not fallbelow the levels specified. Load testing can be bymeans of an artificial load equal to the full fire alarmload connected to the battery. Verify the battery doesnot fall below 2.05 volts per cell under load.

(5) Specific gravity X Semiannually

Measure as required the specific gravity of the liquid inthe pilot cell or all of the cells. Verify the specific gravityis within the range specified by the manufacturer.Although the specified specific gravity varies frommanufacturer to manufacturer, a range of 1.205–1.220is typical for regular lead-acid batteries, while1.240–1.260 is typical for high-performance batteries.Do not use a hydrometer that shows only a pass or failcondition of the battery and does not indicate thespecific gravity, because such a reading does not givea true indication of the battery condition.

(b) Nickel-cadmiumtype


X Annually



87 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

(2) Charger test d X Annually

With the batteries fully charged and connected to thecharger, place an ampere meter in series with thebattery under charge. Verify the charging current is inaccordance with the manufacturer’s recommendationsfor the type of battery used. In the absence of specific

information, use 1 ⁄ 30 to 1 / 25 of the battery rating.




With the battery charger disconnected, load test thebatteries following the manufacturer’srecommendations. Verify the voltage level does not fallbelow the levels specified. Load testing can be bymeans of an artificial load equal to the full fire alarmload connected to the battery. Verify the float voltagefor the entire battery is 1.42 volts per cell, nominal,under load. If possible, measure cells individually.

(c) Sealed lead-acidtype


X Annually






(4) Load voltage test X SemiannuallyVerify the battery performs under load, in accordancewith the battery manufacturer’s specifications.

10.Public emergency alarmreporting system —wired system

X Daily

Manual tests of the power supply for public reportingcircuits shall be made and recorded at least onceduring each 24-hour period. Such tests shall includethe following:

(1) Current strength of each circuit. Changes in currentof any circuit exceeding 10 percent shall beinvestigated immediately.

(2) Voltage across terminals of each circuit inside ofterminals of protective devices. Changes in voltage ofany circuit exceeding 10 percent shall be investigatedimmediately.

(3) e Voltage between ground and circuits. If this testshows a reading in excess of 50 percent of that shownin the test specified in (2), the trouble shall beimmediately located and cleared. Readings in excessof 25 percent shall be given early attention. Thesereadings shall be taken with a calibrated voltmeter of


88 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

not more than 100 ohms resistance per volt. Systemsin which each circuit is supplied by an independentcurrent source (Forms 3 and 4) require tests betweenground and each side of each circuit. Common currentsource systems (Form 2) require voltage tests betweenground and each terminal of each battery and othercurrent source.

(4) Ground current reading shall be permitted in lieu of(3). If this method of testing is used, all groundsshowing a current reading in excess of 5 percent of thesupplied line current shall be given immediateattention.

(5) Voltage across terminals of common battery onswitchboard side of fuses.

(6) Voltage between common battery terminals andground. Abnormal ground readings shall beinvestigated immediately.

Tests specified in (5) and (6) shall apply only to thosesystems using a common battery. If more than onecommon battery is used, each common battery shall betested.

11. Remote annunciators X AnnuallyVerify the correct operation and identification ofannunciators. If provided, verify the correct operation ofannunciator under a fault condition.

12. Reserved

13. Reserved

14. Reserved

15. Conductors — metallic

(a) Stray voltage X N/A

Test all installation conductors with a volt/ohmmeter toverify that there are no stray (unwanted) voltagesbetween installation conductors or between installationconductors and ground. Verify the maximum allowablestray voltage does not exceed 1 volt ac/dc, unless adifferent threshold is specified in the publishedmanufacturer's instructions for the installed equipment.

(b) Ground faults X N/A

Test all installation conductors, other than thoseintentionally and permanently grounded, for isolationfrom ground per the installed equipmentmanufacturer’s published instructions.

(c) Short-circuit faults X N/A

Test all installation conductors, other than thoseintentionally connected together, for conductor-to-conductor isolation per the published manufacturer'sinstructions for the installed equipment. Also test thesesame circuits conductor-to-ground.

(d) Loop resistance X N/A

With each initiating and indicating circuit installationconductor pair short-circuited at the far end, measureand record the resistance of each circuit. Verify that theloop resistance does not exceed the limits specified inthe published manufacturer's instructions for theinstalled equipment.

(e) Circuit integrity X N/A

For initial and reacceptance testing, confirm theintroduction of a fault in any circuit monitored forintegrity results in a trouble indication at the fire alarmcontrol unit. Open one connection at not less than 10percent of the initiating devices, notification appliancesand controlled devices on every initiating device circuit,notification appliance circuit, and signaling line circuit.


89 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

Confirm all circuits perform as indicated in Sections23.5, 23.6, and 23.7.

N/A Annually

For periodic testing, test each initiating device circuit,notification appliance circuit, and signaling line circuitfor correct indication at the control unit. Confirm allcircuits perform as indicated in Sections 23.5, 23.6,and 23.7.

16.Conductors —nonmetallic

(a) Fiber optics X N/A

Test the fiber-optic transmission line by the use of anoptical power meter or by an optical time domainreflectometer used to measure the relative power lossof the line. Test result data must meet or exceedANSI/TIA 568-C.3, Optical Fiber Cabling ComponentsStandard , related to fiber-optic lines andconnection/splice losses and the control unitmanufacturer’s published specifications.

(b) Circuit integrity X N/A

For initial and reacceptance testing, confirm theintroduction of a fault in any circuit monitored forintegrity results in a trouble indication at the fire alarmcontrol unit. Open one connection at not less than 10percent of the initiating devices, notification appliances,and controlled devices on every initiating device circuit,notification appliance circuit, and signaling line circuit.Confirm all circuits perform as indicated in Sections23.5, 23.6, and 23.7.

N/A Annually


17. Initiating devices f

(a) Electromechanicalreleasing device

(1)Nonrestorable-type link

X AnnuallyVerify correct operation by removal of the fusible linkand operation of the associated device. Lubricate anymoving parts as necessary.

(2) Restorable-type

link g X AnnuallyVerify correct operation by removal of the fusible linkand operation of the associated device. Lubricate anymoving parts as necessary.

(b) Fire extinguishingsystem(s) orsuppression system(s)alarm switch

X AnnuallyOperate the switch mechanically or electrically andverify receipt of signal by the fire alarm control unit.

(c) Fire–gas and otherdetectors

X AnnuallyTest fire–gas detectors and other fire detectors asprescribed by the manufacturer and as necessary forthe application.

(d) Heat detectors

(1) Fixed-temperature, rate-of-rise,rate of compensation,restorable line, spot type(excluding pneumatictube type)

X

Annually

(see14.4.4.5)

Perform heat test with a listed and labeled heat sourceor in accordance with the manufacturer’s publishedinstructions. Assure that the test method for theinstalled equipment does not damage thenonrestorable fixed-temperature element of acombination rate-of-rise/fixed-temperature elementdetector.


90 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

(2) Fixed-temperature,nonrestorable line type

X AnnuallyDo not perform heat test. Test functionalitymechanically and electrically. Measure and record loopresistance. Investigate changes from acceptance test.

(3) Fixed-temperature,nonrestorable spot type

X See Method

After 15 years from initial installation, replace alldevices or have 2 detectors per 100 laboratory tested.Replace the 2 detectors with new devices. If a failureoccurs on any of the detectors removed, remove andtest additional detectors to determine either a generalproblem involving faulty detectors or a localizedproblem involving 1 or 2 defective detectors.

If detectors are tested instead of replaced, repeat testsat intervals of 5 years.

(4) Nonrestorable(general)

X AnnuallyDo not perform heat tests. Test functionalitymechanically and electrically.

(5) Restorable linetype, pneumatic tubeonly

X Annually

Perform heat tests (where test chambers are in circuit),with a listed and labeled heat source or in accordancewith the manufacturer's published instructions of thedetector or conduct a test with pressure pump.

(6) Single- andmultiple-station heatalarms

X AnnuallyConduct functional tests according to manufacturer’spublished instructions. Do not test nonrestorable heatdetectors with heat.

(e) Manual fire alarmboxes

X Annually

Operate manual fire alarm boxes per themanufacturer’s published instructions. Test bothkey-operated presignal and general alarm manual firealarm boxes.

(f) Radiant energy firedetectors

X Semiannually

Test flame detectors and spark/ember detectors inaccordance with the manufacturer’s publishedinstructions to determine that each detector isoperative.

Determine flame detector and spark/ember detectorsensitivity using any of the following:

(1) Calibrated test method

(2) Manufacturer’s calibrated sensitivity test instrument

(3) Listed control unit arranged for the purpose

(4) Other approved calibrated sensitivity test methodthat is directly proportional to the input signal from afire, consistent with the detector listing or approval

If designed to be field adjustable, replace detectorsfound to be outside of the approved range of sensitivityor adjust to bring them into the approved range.

Do not determine flame detector and spark/emberdetector sensitivity using a light source that administersan unmeasured quantity of radiation at an undefineddistance from the detector.

(g) Smoke detectors— functional test

(1) In other thanone- and two-familydwellings, systemdetectors

X Annually

h Test smoke detectors in place to ensure smoke entryinto the sensing chamber and an alarm response. Usesmoke or a listed and labeled product acceptable to themanufacturer or in accordance with their publishedinstructions. Other methods listed in the manufacturer'spublished instructions that ensure smoke entry fromthe protected area, through the vents, into the sensingchamber can be used.


91 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

(2) Single- andmultiple-station smokealarms connected toprotected premisessystems

X Annually

Perform a functional test on all single- and multiple-station smoke alarms connected to a protectedpremises fire alarm system by putting the smoke alarminto an alarm condition and verifying that the protectedpremises system receives a supervisory signal anddoes not cause a fire alarm signal.

(3) System smokedetectors used in one-and two-family dwellings

X AnnuallyConduct functional tests according to manufacturer’spublished instructions.

(4) Air sampling X Annually

Test with smoke or a listed and labeled productacceptable to the manufacturer or in accordance withtheir published instructions. Test from the end samplingport or point on each pipe run. Verify airflow through allother ports or points.

(5) Duct type X Annually

In addition to the testing required in Table14.4.3.2(g)(1) and Table 14.4.3.2(h), test duct smokedetectors that use sampling tubes to ensure that theywill properly sample the airstream in the duct using amethod acceptable to the manufacturer or inaccordance with their published instructions.

(6) Projected beamtype

X AnnuallyTest the detector by introducing smoke, other aerosol,or an optical filter into the beam path.

(7) Smoke detectorwith built-in thermalelement

X AnnuallyOperate both portions of the detector independently asdescribed for the respective devices.

(8) Smoke detectorswith control outputfunctions

X Annually

Verify that the control capability remains operable evenif all of the initiating devices connected to the sameinitiating device circuit or signaling line circuit are in analarm state.

(h) Smoke detectors— sensitivity testing

In other than one-and two-family dwellings,system detectors

N/A See 14.4.4.3

i Perform any of the following tests to ensure that eachsmoke detector is within its listed and markedsensitivity range:



(3) Listed control equipment arranged for the purpose

(4) Smoke detector/control unit arrangement wherebythe detector causes a signal at the control unit when itssensitivity is outside its listed sensitivity range

(5) Other calibrated sensitivity test method approved bythe authority having jurisdiction

(i) Carbon monoxidedetectors/carbonmonoxide alarms for thepurposes of firedetection

X Annually

Test the devices in place to ensure CO entry to thesensing chamber by introduction through the vents, tothe sensing chamber of listed and labeled productacceptable to the manufacturer or in accordance withtheir published instructions.

(j) Initiating devices,supervisory

(1) Control valveswitch

X

Semiannual

AnnuallyOperate valve and verify signal receipt to be within the first two revolutions of the handwheel or withinone-fifth of the travel distance, or per the manufacturer’s published instructions.

(2) High- or low-air pressure switch X

Quarterly


92 of 365 9/22/2014 2:48 PM

AnnuallyOperate switch and verify receipt of signal is obtained where the required pressure is increased ordecreased a maximum 10 psi (70 kPa) from the required pressure level.

(3) Room temperature switch X

Quarterly

AnnuallyOperate switch and verify receipt of signal to indicate the decrease in room temperature to 40°F(4.4°C) and its restoration to above 40°F (4.4°C).

(4) Water level switch X

Quarterly

AnnuallyOperate switch and verify receipt of signal indicating the water level raised or lowered a maximum 3in. (70 mm) from the required level within a pressure tank, or a maximum 12 in. (300 mm) from therequired level of a nonpressure tank. Also verify its restoral to required level.

(5) Water temperature switch X

Quarterly

Annually

Operate switch and verifyreceipt of signal to indicatethe decrease in watertemperature to 40°F (4.4°C)and its restoration to above40°F (4.4°C).

(k) Mechanical,electrosonic, or pressure-typewaterflow device

X Semiannually

Water shall be flowed through an inspector's testconnection indicating the flow of water equal to thatfrom a single sprinkler of the smallest orifice sizeinstalled in the system for wet-pipe systems, or analarm test bypass connection for dry-pipe, pre-action,or deluge systems in accordance with NFPA 25,Standard for the Inspection, Testing, and Maintenanceof Water-Based Fire Protection Systems .

(l) Multi-sensor fire detectoror multi-criteria fire detectoror combination fire detector

X Annually

Test each of the detection principles present within thedetector (e.g., smoke/heat/CO, etc.) independently forthe specific detection principle, regardless of theconfiguration status at the time of testing. Also testeach detector in accordance with the publishedmanufacturer's instructions.

Test individual sensors together if the technologyallows individual sensor responses to be verified.

Perform tests as described for the respective devicesby introduction of the physical phenomena to thesensing chamber of element. An electronic check(magnets, analog values, etc.) is not sufficient tocomply with this requirement.

Verify by using the detector manufacturer's publishedinstructions that the test gas used will not impair theoperation of either sensing chamber of a multisensor,multicriteria, or combination fire detector.

Confirm the result of each sensor test throughindication at the detector or control unit.

Where individual sensors cannot be tested

individually, test the primary sensor. j

Record all tests and results.

18. Special hazard equipment

(a) Abort switch (dead-mantype)

X AnnuallyOperate abort switch and verify correct sequence andoperation.

(b) Abort switch (recycletype)

X AnnuallyOperate abort switch and verify development ofcorrect matrix with each sensor operated.

(c) Abort switch (specialtype)

X Annually

Operate abort switch and verify correct sequence andoperation in accordance with authority havingjurisdiction. Observe sequencing as specified onas-built drawings or in system owner’s manual.


93 of 365 9/22/2014 2:48 PM

(d) Cross-zone detectioncircuit

X AnnuallyOperate one sensor or detector on each zone. Verifyoccurrence of correct sequence with operation of firstzone and then with operation of second zone.

(e) Matrix-type circuit X AnnuallyOperate all sensors in system. Verify development ofcorrect matrix with each sensor operated.

(f) Release solenoid

circuit k X Annually Verify operation of solenoid.

(g) Squibb release circuit X AnnuallyUse AGI flashbulb or other test light approved by themanufacturer. Verify operation of flashbulb or light.

(h) Verified, sequential, orcounting zone circuit

X AnnuallyOperate required sensors at a minimum of fourlocations in circuit. Verify correct sequence with boththe first and second detector in alarm.

(i) All above devices orcircuits or combinationsthereof

X AnnuallyVerify supervision of circuits by creating an opencircuit.


(a) Fire extinguisherelectronic monitoringdevice/system

X Annually

Test communication between the device connectingthe fire extinguisher electronic monitoringdevice/system and the fire alarm control unit to ensureproper signals are received at the fire alarm controlunit and remote annunciator(s) if applicable.

(b) Carbon monoxide l

device/systemX Annually

Test communication between the device connectingthe carbon monoxide device/system and the fire alarmcontrol unit to ensure proper signals are received atthe fire alarm control unit and remote annunciator(s) ifapplicable.

20. Interface equipment m X See 14.4.4.4

Test interface equipment connections by operating orsimulating the equipment being supervised. Verifysignals required to be transmitted are received at thecontrol unit. Test frequency for interface equipment isthe same as the frequency required by the applicableNFPA standard(s) for the equipment being supervised.

21. Guard’s tour equipment X AnnuallyTest the device in accordance with the manufacturer’spublished instructions.

22. Alarm notification appliances

(a) Audible n X N/A

For initial and reacceptance testing, measure soundpressure levels for signals with a sound level metermeeting ANSI S1.4a, Specifications for Sound LevelMeters, Type 2 requirements. Measure soundpressure levels throughout the protected area toconfirm that they are in compliance with Chapter 18.Set the sound level meter in accordance with ANSIS3.41, American National Standard AudibleEvacuation Signal, using the time-weightedcharacteristic F (FAST).

N/A Annuallyo For periodic testing, verify the operation of thenotification appliances.

(b) Audible textualnotification appliances(speakers and otherappliances to convey voicemessages)

X N/A


Verify audible information to be distinguishable andunderstandable and in compliance with 14.4.11.


94 of 365 9/22/2014 2:48 PM


(c) Visible X N/A

Perform initial and reacceptance testing in accordancewith the manufacturer’s published instructions. Verifyappliance locations to be per approved layout andconfirm that no floor plan changes affect the approvedlayout. Verify that the candela rating marking agreeswith the approved drawing. Confirm that eachappliance flashes.

N/A AnnuallyFor periodic testing, verify that each applianceflashes.

23.Exit marking audiblenotification appliance

X AnnuallyPerform tests in accordance with manufacturer'spublished instructions.

24.Emergency control

functions p X Annually

For initial, reacceptance, and periodic testing, verifyemergency control function interface device activation.Where an emergency control function interface deviceis disabled or disconnected during initiating devicetesting, verify that the disabled or disconnectedemergency control function interface device has beenproperly restored. [

25.Area of refuge two-waycommunication system

X Annually

Use the manufacturer’s published instructions and theas-built drawings provided by the system supplier toverify correct operation after the initial testing phasehas been performed by the supplier or by thesupplier’s designated representative.

Test the two-way communication system to verifyoperation and receipt of visual and audible signals atthe transmitting unit and the receiving unit,respectively.

Operate systems with more than five stations with aminimum of five stations operating simultaneously.

Verify voice quality and clarity.

Verify directions for the use of the two-waycommunication system, instructions for summoningassistance via the two-way communication system,and written identification of the location is postedadjacent to the two-way communication system.

Verify that all remote stations are readily accessible.

Verify the timed automatic communications capabilityto connect with a constantly attended monitoringlocation per 24.5.3.4.

26. Special procedures

(a) Alarm verification X AnnuallyVerify time delay and alarm response for smokedetector circuits identified as having alarm verification.

(b) Multiplex systems X AnnuallyVerify communications between sending and receivingunits under both primary and secondary power.

Verify communications between sending and receivingunits under open-circuit and short-circuit troubleconditions.

Verify communications between sending and receivingunits in all directions where multiple communicationspathways are provided.

If redundant central control equipment is provided,verify switchover and all required functions andoperations of secondary control equipment.

Verify all system functions and features in accordancewith manufacturer’s published instructions.


95 of 365 9/22/2014 2:48 PM

27.Supervising station alarmsystems — receivingequipment

(a) All equipment X Monthly

Perform tests on all system functions and features inaccordance with the equipment manufacturer’spublished instructions for correct operation inconformance with the applicable sections of Chapter26.

Actuate initiating device and verify receipt of thecorrect initiating device signal at the supervisingstation within 90 seconds. Upon completion of thetest, restore the system to its functional operatingcondition.

If test jacks are used, perform the first and last testswithout the use of the test jack.

(b) Digital alarmcommunicator receiver(DACR)

X MonthlyDisconnect each transmission means in turn from theDACR, and verify audible and visual annunciation of atrouble signal in the supervising station.

Cause a signal to be transmitted on each individualincoming DACR line (path) at least once every 6hours (24 hours for DACTs installed prior to adoptionof the 2013 edition of NFPA 72 ). Verify receipt ofthese signals.

(c) Digital alarm radioreceiver (DARR)

X Monthly

Cause the following conditions of all DARRs on allsubsidiary and repeater station receiving equipment.Verify receipt at the supervising station of correctsignals for each of the following conditions:

(1) AC power failure of the radio equipment

(2) Receiver malfunction

(3) Antenna and interconnecting cable failure

(4) Indication of automatic switchover of the DARR

(5) Data transmission line failure between the DARRand the supervising or subsidiary station

(d) McCulloh systems X MonthlyTest and record the current on each circuit at eachsupervising and subsidiary station under the followingconditions:

(1) During functional operation

(2) On each side of the circuit with the receivingequipment conditioned for an open circuit

Cause a single break or ground condition on eachtransmission channel. If such a fault prevents thefunctioning of the circuit, verify receipt of a troublesignal.

Cause each of the following conditions at each of thesupervising or subsidiary stations and all repeaterstation radio transmitting and receiving equipment;verify receipt of correct signals at the supervisingstation:

(1) RF transmitter in use (radiating)

(2) AC power failure supplying the radio equipment

(3) RF receiver malfunction

(4) Indication of automatic switchover

(e) Radio alarm supervisingstation receiver (RASSR) andradio alarm repeater stationreceiver (RARSR)

X Monthly




96 of 365 9/22/2014 2:48 PM


(3) Indication of automatic switchover, if applicable

(f) Private microwave radiosystems

X Monthly






(g) Performance-basedtechnologies

X Monthly

Perform tests to ensure the monitoring of integrity ofthe transmission technology and technology path.Where a single communications path is used,disconnect the communication path. Verify that failureof the path is annunciated at the supervising stationwithin 60 minutes of the failure (within 5 minutes forcommunication equipment installed prior to adoptionof the 2013 edition of NFPA 72 ). Restore thecommunication path.

Where multiple communication paths are used,disconnect both communication paths and confirmthat failure of the path is annunciated at thesupervising station within not more than 6 hours of thefailure (within 24 hours for communication equipmentinstalled prior to adoption of the 2013 edition of NFPA72 ). Restore both communication paths.

28.Public emergency alarmreporting systemtransmission equipment

(a) Publicly accessiblealarm box

X Semiannually

Actuate publicly accessible initiating device(s) andverify receipt of not less than three complete rounds ofsignal impulses. Perform this test under normal circuitconditions. If the device is equipped for open circuitoperation (ground return), test it in this condition asone of the semiannual tests.

(b) Auxiliary box X Annually

Test each initiating circuit of the auxiliary box byactuation of a protected premises initiating deviceconnected to that circuit. Verify receipt of not less thanthree complete rounds of signal impulses.

(c) Master box

(1) Manual operation X Semiannually Perform the tests prescribed for 28(a).

(2) Auxiliary operation X Annually Perform the tests prescribed for 28(b).

29.Low-power radio (wirelesssystems)

X N/AThe following procedures describe additionalacceptance and reacceptance test methods to verifywireless protection system operation:

(1) Use the manufacturer’s published instructions andthe as-built drawings provided by the system supplierto verify correct operation after the initial testing phasehas been performed by the supplier or by thesupplier’s designated representative.

(2) Starting from the functional operating condition,initialize the system in accordance with themanufacturer’s published instructions. Confirm thealternative communications path exists between thewireless control unit and peripheral devices used toestablish initiation, indication, control, andannunciation. Test the system for both alarm andtrouble conditions.


97 of 365 9/22/2014 2:48 PM

(3) Check batteries for all components in the systemmonthly unless the control unit checks all batteriesand all components daily.

30. Mass notification systems


At a minimum, test control equipment to verify correctreceipt of alarm, supervisory, and trouble signals(inputs); operation of evacuation signals and auxiliaryfunctions (outputs); circuit supervision, includingdetection of open circuits and ground faults; andpower supply supervision for detection of loss of acpower and disconnection of secondary batteries.

(b) Fuses X Annually Verify the rating and supervision.

(c) Interfaced equipment X Annually



(e) Primary (main) powersupply

X Annually

Disconnect all secondary (standby) power and testunder maximum load, including all alarm appliancesrequiring simultaneous operation. Reconnect allsecondary (standby) power at end of test. Forredundant power supplies, test each separately.

(f) Audible textual notificationappliances (speakers andother appliances to conveyvoice messages)

X Annually

Measure sound pressure level with a sound levelmeter meeting ANSI S1.4a, Specifications for SoundLevel Meters, Type 2 requirements. Measure andrecord levels throughout protected area. Set thesound level meter in accordance with ANSI S3.41,American National Standard Audible EvacuationSignal, using the time-weighted characteristic F(FAST). Record the maximum output when theaudible emergency evacuation signal is on.

Verify audible information to be distinguishable andunderstandable.

(g) Visible X Annually

Perform test in accordance with manufacturer’spublished instructions. Verify appliance locations to beper approved layout and confirm that no floor planchanges affect the approved layout. Verify that thecandela rating marking agrees with the approveddrawing. Confirm that each appliance flashes.

(h) Control unit functions andno diagnostic failures areindicated

X Annually

Review event log file and verify that the correct eventswere logged. Review system diagnostic log file;correct deficiencies noted in file. Delete unneeded logfiles. Delete unneeded error files. Verify that sufficientfree disk space is available. Verify unobstructed flowof cooling air is available. Change/clean filters, coolingfans, and intake vents.

(i) Control unit reset X AnnuallyPower down the central control unit computer andrestart it.

(j) Control unit security X AnnuallyIf remote control software is loaded onto the system,verify that it is disabled to prevent unauthorizedsystem access.

(k) Audible/visible functionaltest

X AnnuallySend out an alert to a diverse set of predesignatedreceiving devices and confirm receipt. Include at leastone of each type of receiving device.

(l) Software backup X AnnuallyMake full system software backup. Rotate backupsbased on accepted practice at site.


98 of 365 9/22/2014 2:48 PM

(m) Secondary power test X AnnuallyDisconnect ac power. Verify the ac power failure alarmstatus on central control equipment. With ac powerdisconnected, verify battery voltage under load.

(n) Wireless signals X AnnuallyCheck forward/reflected radio power is withinspecifications.

(o) Antenna X AnnuallyCheck forward/reflected radio power is withinspecifications. Verify solid electrical connections withno observable corrosion.

(p) Transceivers X AnnuallyVerify proper operation and mounting is notcompromised.

aSome transmission equipment (such as but not limited to cable modems, fiber-optic interface nodes, and VoIPinterfaces) are typically powered by the building's electrical system using a secondary (standby) power supply thatdoes not meet the requirements of this Code. This is intended to ensure that the testing authority verifies fullsecondary (standby) power as required by Chapter 10. Additionally, refer to Table 14.4.3.2, items 7 through 9, forsecondary (standby) power supply testing.

bThe automatic transmission of the check-in (handshake) signal can take up to 60 minutes to occur.

cSee Table 14.4.3.2, Item 4(a) for the testing of transmission equipment.

dExample: 4000 mAh × 1⁄25 = 160 mA charging current at 77°F (25°C).

eThe voltmeter sensitivity has been changed from 1000 ohms per volt to 100 ohms per volt so that the false groundreadings (caused by induced voltages) are minimized.

fInitiating devices such as smoke detectors used for elevator recall, closing dampers, or releasing doors held in theopen position that are permitted by the Code (see NFPA 101, Life Safety Code , 9.6.3) to initiate supervisory signalsat the fire alarm control unit (FACU) should be tested at the same frequency (annual) as those devices when theyare generating an alarm signal. They are not supervisory devices, but they initiate a supervisory signal at the FACU.

gFusible thermal link detectors are commonly used to close fire doors and fire dampers. They are actuated by thepresence of external heat, which causes a solder element in the link to fuse, or by an electric thermal device, which,when energized, generates heat within the body of the link, causing the link to fuse and separate.

hNote, it is customary for the manufacturer of the smoke detector to test a particular product from an aerosolprovider to determine acceptability for use in smoke entry testing of their smoke detector/ smoke alarm. Magnetsare not acceptable for smoke entry tests.

i There are some detectors that use magnets as a manufacturer's calibrated sensitivity test instrument.

jFor example, it might not be possible to individually test the heat sensor in a thermally enhanced smoke detector.

kManufacturer's instructions should be consulted to ensure a proper operational test. No suppression gas or agentis expected to be discharged during the test of the solenoid. See Test Plan of 14.2.10.

lTesting of CO device should be done to the requirements of NFPA 720, Standard for the Installation of CarbonMonoxide (CO) Detection and Warning Equipment.

mA monitor module installed on an interface device is not considered a supervisory device and therefore notsubject to the quarterly testing frequency requirement. Test frequencies for interface devices should be inaccordance with the applicable standard. For example, fire pump controller alarms such as phase reversal arerequired to be tested annually. If a monitor module is installed to identify phase reversal on the fire alarm controlpanel, it is not necessary to test for phase reversal four times a year.

nChapter 18 would require 15 dB over average ambient sound for public mode spaces. Sometimes the ambientsound levels are different from what the design was based upon. Private operating mode would require 10 dB overaverage ambient at the location of the device.

oWhere building, system, or occupancy changes have been observed, the owner should be notified of the changes.New devices might need to be installed and tested per the initial acceptance testing criteria.

pSee A.14.4.3.2, and Table 14.4.3.2, Item 24.



99 of 365 9/22/2014 2:48 PM

We believe that the original fixed interval testing intervals had no more technical substantiation than the intervals that there inadvertently changed. To borrow from Mr. Hurst’s comment on the negative:

Other more complex fire protection initiating devices require testing on an annual frequency, e.g., addressable detectors. Many of these devises are used in critical systems e.g., gaseous suppression. In an inquiry directed to Potter Electric Switch Co. concerning failure rates resulting from increased test frequencies the response was that there have been no reported or observed failures due to incremental increases in test frequency.

While it may be too soon to make this determination it should also be noted that these devices are typically already supervised. The exposure time during which an inactive device would create a hazard for occupants is very small compared to the risks when other parts of a fire protection system fail.

Related Item

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


Submitter Full Name: Joshua Elvove

Organization: [ Not Specified ]

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: NFPA 72 establishes the requirements for fire alarm switch testing frequency. The statistical failure rates ofelectronically supervised mechanical switches are extremely small. In a 3-year cycle, there was noevidence to suggest that more than an annual frequency was necessary.


100 of 365 9/22/2014 2:48 PM



101 of 365 9/22/2014 2:48 PM


SIG-TMS_Tables_Annex.docx Tables & associated annex

SIG-TMS_Battery_Definitions.docx Related battery definitions

SIG-TMS_Chapter_10_Fundamentals.docx Changes for Ch 10 including annex revisions


The public comment is submitted as part of recommendations of SIG-TMS Battery Task Group to resolve battery testing issues.








Related Item







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected but held



123 of 365 9/22/2014 2:48 PM



124 of 365 9/22/2014 2:48 PM

14.4.3.2*


125 of 365 9/22/2014 2:48 PM




ComponentInitial

Acceptance

Periodic

FrequencyMethod


2.Control equipment andtransponder


Verify correct receipt of alarm, supervisory, and troublesignals (inputs); operation of evacuation signals andauxiliary functions (outputs); circuit supervision,including detection of open circuits and ground faults;and power supply supervision for detection of loss ofac power and disconnection of secondary batteries.



X Annually




X AnnuallyTest under maximum load, including all alarmappliances requiring simultaneous operation. Testredundant power supplies separately.


(a) Audible and visual X AnnuallyVerify operation of control unit trouble signals. Verifyring-back feature for systems using a trouble-silencingswitch that requires resetting.


X Annually

If control unit has disconnect or isolating switches,verify performance of intended function of each switch.Verify receipt of trouble signal when a supervisedfunction is disconnected.




X AnnuallyActuate an initiating device and verify receipt of alarmsignal at the off-premises location.

Create a trouble condition and verify receipt of atrouble signal at the off-premises location.

Actuate a supervisory device and verify receipt of asupervisory signal at the off-premises location. If atransmission carrier is capable of operation under asingle- or multiple-fault condition, activate an initiatingdevice during such fault condition and verify receipt ofan alarm signal and a trouble signal at the off-premiseslocation.

4.Supervising stationalarm systems —transmission Equipment


a Test all system functions and features in accordancewith the equipment manufacturer’s publishedinstructions for correct operation in conformance withthe applicable sections of Chapter 26.


126 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

Except for DACT, actuate initiating device and verifyreceipt of the correct initiating device signal at thesupervising station within 90 seconds. Uponcompletion of the test, restore the system to itsfunctional operating condition.

If test jacks are used, conduct the first and last testswithout the use of the test jack.


X Annually

Except for DACTs installed prior to adoption of the2013 edition of NFPA 72 that are connected to atelephone line (number) that is also supervised foradverse conditions by a derived local channel, ensureconnection of the DACT to two separate means oftransmission.

Test DACT for line seizure capability by initiating asignal while using the telephone line (primary line forDACTs using two telephone lines) for a telephone call.Ensure that the call is interrupted and that thecommunicator connects to the digital alarm receiver.Verify receipt of the correct signal at the supervisingstation. Verify each transmission attempt is completedwithin 90 seconds from going off-hook to on-hook.

Disconnect the telephone line (primary line for DACTsusing two telephone lines) from the DACT. Verifyindication of the DACT trouble signal occurs at thepremises fire alarm control unit within 4 minutes ofdetection of the fault. Verify receipt of the telephoneline trouble signal at the supervising station. Restorethe telephone line (primary line for DACTs using twotelephone lines), reset the fire alarm control unit, andverify that the telephone line fault trouble signal returnsto normal. Verify that the supervising station receivesthe restoral signal from the DACT.

Disconnect the secondary means of transmission fromthe DACT. Verify indication of the DACT trouble signaloccurs at the premises fire alarm control unit within 4minutes of detection of the fault. Verify receipt of thesecondarey means trouble signal at the supervisingstation. Restore the secondary means of transmission,reset the fire alarm control unit, and verify that thetrouble signal returns to normal. Verify that thesupervising station receives the restoral signal from thesecondary transmitter.

Cause the DACT to transmit a signal to the DACRwhile a fault in the telephone line (number) (primaryline for DACTs using two telephone lines) is simulated.Verify utilization of the secondary communication pathby the DACT to complete the transmission to theDACR.

(c) Digital alarm radiotransmitter (DART)

X AnnuallyDisconnect the primary telephone line. Verifytransmission of a trouble signal to the supervisingstation by the DART occurs within 4 minutes.


X AnnuallyActuate initiating device. Verify production of not lessthan three complete rounds of not less than threesignal impulses each by the McCulloh transmitter.


(1) Open


127 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

(2) Ground


(4) Open and ground

If end-to-end metallic continuity is not present and witha properly balanced circuit, cause each of the followingthree transmission channel fault conditions in turn, andverify receipt of correct signals at the supervisingstation:

(1) Open

(2) Ground



X Annually


(f) Performance-basedtechnologies

X Annually

Perform tests to ensure the monitoring of integrity ofthe transmission technology and technology path.


Where a single communications path is used,disconnect the communication path. Manually initiatean alarm signal transmission or allow the check-in

(handshake) signal to be transmitted automatically. b

Verify the premises unit annunciates the failure within200 seconds of the transmission failure. Restore thecommunication path.

Where multiple communication paths are used,disconnect both communication paths. Manually initiatean alarm signal transmission. Verify the premisescontrol unit annunciates the failure within 200 secondsof the transmission failure. Restore bothcommunication paths.



X AnnuallyVerify correct switching and operation of backupequipment.



(c) Off-hook indicator(ring down)


(d) Phone jacks X AnnuallyVisually inspect phone jack and initiatecommunications path through jack.



X AnnuallyOperate the system with a minimum of any fivehandsets simultaneously. Verify voice quality andclarity.

6. Engine-driven generator X Monthly

If an engine-driven generator dedicated to the systemis used as a required power source, verify operation ofthe generator in accordance with NFPA 110, Standardfor Emergency and Standby Power Systems, by thebuilding owner.


128 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod



Disconnect all primary (main) power supplies and verifythe occurrence of required trouble indication for loss ofprimary power. Measure or verify the system’s standbyand alarm current demand and verify the ability ofbatteries to meet standby and alarm requirementsusing manufacturer’s data. Operate general alarmsystems a minimum of 5 minutes and emergency voicecommunications systems for a minimum of 15 minutes.Reconnect primary (main) power supply at end of test.


X Annually



(a) Lead-acid type


X Annually












X Annually



129 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod


With the batteries fully charged and connected to thecharger, place an ampere meter in series with thebattery under charge. Verify the charging current is inaccordance with the manufacturer’s recommendationsfor the type of battery used. In the absence of specific








X Annually








X Daily




(3) e Voltage between ground and circuits. If this testshows a reading in excess of 50 percent of that shownin the test specified in (2), the trouble shall beimmediately located and cleared. Readings in excessof 25 percent shall be given early attention. Thesereadings shall be taken with a calibrated voltmeter of


130 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

not more than 100 ohms resistance per volt. Systemsin which each circuit is supplied by an independentcurrent source (Forms 3 and 4) require tests betweenground and each side of each circuit. Common currentsource systems (Form 2) require voltage tests betweenground and each terminal of each battery and othercurrent source.






12. Reserved

13. Reserved

14. Reserved











For initial and reacceptance testing, confirm theintroduction of a fault in any circuit monitored forintegrity results in a trouble indication at the fire alarmcontrol unit. Open one connection at not less than 10percent of the initiating devices, notification appliancesand controlled devices on every initiating device circuit,notification appliance circuit, and signaling line circuit.


131 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

Confirm all circuits perform as indicated in Sections23.5, 23.6, and 23.7.

N/A Annually







N/A Annually






(2) Restorable-type






(d) Heat detectors


X

Annually

(see14.4.4.5)



132 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod




X See Method






X Annually





X Annually



X Semiannually











X Annually



133 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod


X Annually







In addition to the testing required in Table14.4.3.2(g)(1) and Table 14.4.3.2(h), test duct smokedetectors that use sampling tubes to ensure that theywill properly sample the airstream in the duct using amethod acceptable to the manufacturer or inaccordance with their published instructions.






X Annually




N/A See 14.4.4.3








X Annually




X

Semiannual

AnnuallyOperate valve and verify signal receipt to be within the first two revolutions of the handwheel or withinone-fifth of the travel distance, or per the manufacturer’s published instructions.

(2) High- or low-air pressure switch X

Quarterly


134 of 365 9/22/2014 2:48 PM

AnnuallyOperate switch and verify receipt of signal is obtained where the required pressure is increased ordecreased a maximum 10 psi (70 kPa) from the required pressure level.

(3) Room temperature switch X

Quarterly

AnnuallyOperate switch and verify receipt of signal to indicate the decrease in room temperature to 40°F(4.4°C) and its restoration to above 40°F (4.4°C).

(4) Water level switch X

Quarterly

AnnuallyOperate switch and verify receipt of signal indicating the water level raised or lowered a maximum 3in. (70 mm) from the required level within a pressure tank, or a maximum 12 in. (300 mm) from therequired level of a nonpressure tank. Also verify its restoral to required level.

(5) Water temperature switch X

Quarterly

Annually

Operate switch and verifyreceipt of signal to indicatethe decrease in watertemperature to 40°F (4.4°C)and its restoration to above40°F (4.4°C).

(k) Mechanical,electrosonic, or pressure-typewaterflow device

X Semiannually


(l) Multi-sensor fire detectoror multi-criteria fire detectoror combination fire detector

X Annually






Where individual sensors cannot be tested

individually, test the primary sensor. j


18. Special hazard equipment

(a) Abort switch (dead-mantype)


(b) Abort switch (recycletype)

X AnnuallyOperate abort switch and verify development ofcorrect matrix with each sensor operated.

(c) Abort switch (specialtype)

X Annually



135 of 365 9/22/2014 2:48 PM

(d) Cross-zone detectioncircuit





(g) Squibb release circuit X AnnuallyUse AGI flashbulb or other test light approved by themanufacturer. Verify operation of flashbulb or light.

(h) Verified, sequential, orcounting zone circuit






X Annually

Test communication between the device connectingthe fire extinguisher electronic monitoringdevice/system and the fire alarm control unit to ensureproper signals are received at the fire alarm controlunit and remote annunciator(s) if applicable.



Test communication between the device connectingthe carbon monoxide device/system and the fire alarmcontrol unit to ensure proper signals are received atthe fire alarm control unit and remote annunciator(s) ifapplicable.




22. Alarm notification appliances

(a) Audible n X N/A



(b) Audible textualnotification appliances(speakers and otherappliances to convey voicemessages)

X N/A




136 of 365 9/22/2014 2:48 PM


(c) Visible X N/A


N/A AnnuallyFor periodic testing, verify that each applianceflashes.







X Annually

Use the manufacturer’s published instructions and theas-built drawings provided by the system supplier toverify correct operation after the initial testing phasehas been performed by the supplier or by thesupplier’s designated representative.















137 of 365 9/22/2014 2:48 PM

27.Supervising station alarmsystems — receivingequipment



Actuate initiating device and verify receipt of thecorrect initiating device signal at the supervisingstation within 90 seconds. Upon completion of thetest, restore the system to its functional operatingcondition.




Cause a signal to be transmitted on each individualincoming DACR line (path) at least once every 6hours (24 hours for DACTs installed prior to adoptionof the 2013 edition of NFPA 72 ). Verify receipt ofthese signals.


X Monthly
















(e) Radio alarm supervisingstation receiver (RASSR) andradio alarm repeater stationreceiver (RARSR)

X Monthly




138 of 365 9/22/2014 2:48 PM



(f) Private microwave radiosystems

X Monthly






(g) Performance-basedtechnologies

X Monthly

Perform tests to ensure the monitoring of integrity ofthe transmission technology and technology path.Where a single communications path is used,disconnect the communication path. Verify that failureof the path is annunciated at the supervising stationwithin 60 minutes of the failure (within 5 minutes forcommunication equipment installed prior to adoptionof the 2013 edition of NFPA 72 ). Restore thecommunication path.

Where multiple communication paths are used,disconnect both communication paths and confirmthat failure of the path is annunciated at thesupervising station within not more than 6 hours of thefailure (within 24 hours for communication equipmentinstalled prior to adoption of the 2013 edition of NFPA72 ). Restore both communication paths.



X Semiannually

Actuate publicly accessible initiating device(s) andverify receipt of not less than three complete rounds ofsignal impulses. Perform this test under normal circuitconditions. If the device is equipped for open circuitoperation (ground return), test it in this condition asone of the semiannual tests.



(c) Master box

(1) Manual operation X Semiannually Perform the tests prescribed for 28(a).

(2) Auxiliary operation X Annually Perform the tests prescribed for 28(b).

29.Low-power radio (wirelesssystems)


(1) Use the manufacturer’s published instructions andthe as-built drawings provided by the system supplierto verify correct operation after the initial testing phasehas been performed by the supplier or by thesupplier’s designated representative.



139 of 365 9/22/2014 2:48 PM

(3) Check batteries for all components in the systemmonthly unless the control unit checks all batteriesand all components daily.

30. Mass notification systems


At a minimum, test control equipment to verify correctreceipt of alarm, supervisory, and trouble signals(inputs); operation of evacuation signals and auxiliaryfunctions (outputs); circuit supervision, includingdetection of open circuits and ground faults; andpower supply supervision for detection of loss of acpower and disconnection of secondary batteries.






X Annually

Disconnect all secondary (standby) power and testunder maximum load, including all alarm appliancesrequiring simultaneous operation. Reconnect allsecondary (standby) power at end of test. Forredundant power supplies, test each separately.

(f) Audible textual notificationappliances (speakers andother appliances to conveyvoice messages)

X Annually

Measure sound pressure level with a sound levelmeter meeting ANSI S1.4a, Specifications for SoundLevel Meters, Type 2 requirements. Measure andrecord levels throughout protected area. Set thesound level meter in accordance with ANSI S3.41,American National Standard Audible EvacuationSignal, using the time-weighted characteristic F(FAST). Record the maximum output when theaudible emergency evacuation signal is on.




(h) Control unit functions andno diagnostic failures areindicated

X Annually

Review event log file and verify that the correct eventswere logged. Review system diagnostic log file;correct deficiencies noted in file. Delete unneeded logfiles. Delete unneeded error files. Verify that sufficientfree disk space is available. Verify unobstructed flowof cooling air is available. Change/clean filters, coolingfans, and intake vents.


(j) Control unit security X AnnuallyIf remote control software is loaded onto the system,verify that it is disabled to prevent unauthorizedsystem access.

(k) Audible/visible functionaltest




140 of 365 9/22/2014 2:48 PM

(m) Secondary power test X AnnuallyDisconnect ac power. Verify the ac power failure alarmstatus on central control equipment. With ac powerdisconnected, verify battery voltage under load.









fInitiating devices such as smoke detectors used for elevator recall, closing dampers, or releasing doors held in theopen position that are permitted by the Code (see NFPA 101, Life Safety Code , 9.6.3) to initiate supervisory signalsat the fire alarm control unit (FACU) should be tested at the same frequency (annual) as those devices when theyare generating an alarm signal. They are not supervisory devices, but they initiate a supervisory signal at the FACU.













141 of 365 9/22/2014 2:48 PM

Given the supervisory function of these initiating devices, we are notified of a problem and they are serviced/repaired should any issue develop during the course of the testing interval. The more frequent testing intervals were apparently established by anecdotal assumptions and without recoverable scientific documentation. Other system components of equivalent importance to system operations are permitted to utilize an annual test frequency.

Related Item



Submitter Full Name: CRAIG GRANT

Organization: ILLINOIS UNIV OF Code Compliance and Fire Safety

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: NFPA 72 establishes the requirements for fire alarm switch testing frequency. The statistical failure rates ofelectronically supervised mechanical switches are extremely small. In a 3-year cycle, there was noevidence to suggest that more than an annual frequency was necessary.


142 of 365 9/22/2014 2:48 PM



143 of 365 9/22/2014 2:48 PM

14.4.3.2 *


144 of 365 9/22/2014 2:48 PM




ComponentInitial

Acceptance

Periodic

FrequencyMethod


2.Control equipmentand transponder


Verify correct receipt of alarm, supervisory, and troublesignals (inputs); operation of evacuation signals andauxiliary functions (outputs); circuit supervision, includingdetection of open circuits and ground faults; and powersupply supervision for detection of loss of ac power anddisconnection of secondary batteries.



X Annually

Verify integrity of single or multiple circuits providinginterface between two or more control units. Test interfacedequipment connections by operating or simulating operationof the equipment being supervised. Verify signals requiredto be transmitted at the control unit.

(d) Lamps andLEDs

X Annually Illuminate lamps and LEDs.


X AnnuallyTest under maximum load, including all alarm appliancesrequiring simultaneous operation. Test redundant powersupplies separately.


(a) Audible andvisual

X AnnuallyVerify operation of control unit trouble signals. Verifyring-back feature for systems using a trouble-silencingswitch that requires resetting.


X Annually

If control unit has disconnect or isolating switches, verifyperformance of intended function of each switch. Verifyreceipt of trouble signal when a supervised function isdisconnected.




X AnnuallyActuate an initiating device and verify receipt of alarm signalat the off-premises location.

Create a trouble condition and verify receipt of a troublesignal at the off-premises location.

Actuate a supervisory device and verify receipt of asupervisory signal at the off-premises location. If atransmission carrier is capable of operation under a single-or multiple-fault condition, activate an initiating device duringsuch fault condition and verify receipt of an alarm signal anda trouble signal at the off-premises location.

4.

Supervising stationalarm systems —transmissionEquipment


a Test all system functions and features in accordance withthe equipment manufacturer’s published instructions forcorrect operation in conformance with the applicablesections of Chapter 26.


145 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

Except for DACT, actuate initiating device and verify receiptof the correct initiating device signal at the supervisingstation within 90 seconds. Upon completion of the test,restore the system to its functional operating condition.

If test jacks are used, conduct the first and last tests withoutthe use of the test jack.


X Annually

Except for DACTs installed prior to adoption of the 2013edition of NFPA 72 that are connected to a telephone line(number) that is also supervised for adverse conditions by aderived local channel, ensure connection of the DACT totwo separate means of transmission.

Test DACT for line seizure capability by initiating a signalwhile using the telephone line (primary line for DACTs usingtwo telephone lines) for a telephone call. Ensure that thecall is interrupted and that the communicator connects tothe digital alarm receiver. Verify receipt of the correct signalat the supervising station. Verify each transmission attemptis completed within 90 seconds from going off-hook toon-hook.

Disconnect the telephone line (primary line for DACTs usingtwo telephone lines) from the DACT. Verify indication of theDACT trouble signal occurs at the premises fire alarmcontrol unit within 4 minutes of detection of the fault. Verifyreceipt of the telephone line trouble signal at the supervisingstation. Restore the telephone line (primary line for DACTsusing two telephone lines), reset the fire alarm control unit,and verify that the telephone line fault trouble signal returnsto normal. Verify that the supervising station receives therestoral signal from the DACT.

Disconnect the secondary means of transmission from theDACT. Verify indication of the DACT trouble signal occurs atthe premises fire alarm control unit within 4 minutes ofdetection of the fault. Verify receipt of the secondareymeans trouble signal at the supervising station. Restore thesecondary means of transmission, reset the fire alarmcontrol unit, and verify that the trouble signal returns tonormal. Verify that the supervising station receives therestoral signal from the secondary transmitter.

Cause the DACT to transmit a signal to the DACR while afault in the telephone line (number) (primary line for DACTsusing two telephone lines) is simulated. Verify utilization ofthe secondary communication path by the DACT tocomplete the transmission to the DACR.

(c) Digital alarmradio transmitter(DART)

X AnnuallyDisconnect the primary telephone line. Verify transmissionof a trouble signal to the supervising station by the DARToccurs within 4 minutes.


X AnnuallyActuate initiating device. Verify production of not less thanthree complete rounds of not less than three signal impulseseach by the McCulloh transmitter.


(1) Open

(2) Ground


(4) Open and ground


146 of 365 9/22/2014 2:48 PM

ComponentInitial

Acceptance

Periodic

FrequencyMethod

If end-to-end metallic continuity is not present and with aproperly balanced circuit, cause each of the following threetransmission channel fault conditions in turn, and verifyreceipt of correct signals at the supervising station:

(1) Open

(2) Ground



X Annually


(f)Performance-basedtechnologies

X Annually

Perform tests to ensure the monitoring of integrity of thetransmission technology and technology path.


Where a single communications path is used, disconnectthe communication path. Manually initiate an alarm signaltransmission or allow the check-in (handshake) signal to be

transmitted automatically. b Verify the premises unitannunciates the failure within 200 seconds of thetransmission failure. Restore the communication path.

Where multiple communication paths are used, disconnectboth communication paths. Manually initiate an alarm signaltransmission. Verify the premises control unit annunciatesthe failure within 200 seconds of the transmission failure.Restore both communication paths.



X Annually Verify correct switching and operation of backup equipment.



(c) Off-hookindicator (ring down)


(d) Phone jacks X AnnuallyVisually inspect phone jack and initiate communicationspath through jack.



X AnnuallyOperate the system with a minimum of any five handsetssimultaneously. Verify voice quality and clarity.

6.Engine-drivengenerator

X Monthly

If an engine-driven generator dedicated to the system isused as a required power source, verify operation of thegenerator in accordance with NFPA 110, Standard forEmergency and Standby Power Systems, by the buildingowner.



Disconnect all primary (main) power supplies and verify theoccurrence of required trouble indication for loss of primarypower. Measure or verify the system’s standby and alarmcurrent demand and verify the ability of batteries to meetstandby and alarm requirements using manufacturer’s data.Operate general alarm systems

a minimum of 5 minutes

and emergency voice communications systems


147 of 365 9/22/2014 2:48 PM

for a minimum of 15 minutes

. Reconnectprimary(main)powersupply atend of test.


X Annually



(a) Lead-acid type


X Annually












X Annually



With the batteries fully charged and connected to thecharger, place an ampere meter in series with thebattery under charge. Verify the charging current is inaccordance with the manufacturer’s recommendations


148 of 365 9/22/2014 2:48 PM

for the type of battery used. In the absence of specific








X Annually








X Daily




(3) e Voltage between ground and circuits. If this testshows a reading in excess of 50 percent of that shownin the test specified in (2), the trouble shall beimmediately located and cleared. Readings in excessof 25 percent shall be given early attention. Thesereadings shall be taken with a calibrated voltmeter ofnot more than 100 ohms resistance per volt. Systemsin which each circuit is supplied by an independentcurrent source (Forms 3 and 4) require tests betweenground and each side of each circuit. Common currentsource systems (Form 2) require voltage tests betweenground and each terminal of each battery and othercurrent source.


149 of 365 9/22/2014 2:48 PM






12. Reserved

13. Reserved

14. Reserved











For initial and reacceptance testing, confirm theintroduction of a fault in any circuit monitored forintegrity results in a trouble indication at the fire alarmcontrol unit. Open one connection at not less than 10percent of the initiating devices, notification appliancesand controlled devices on every initiating device circuit,notification appliance circuit, and signaling line circuit.Confirm all circuits perform as indicated in Sections23.5, 23.6, and 23.7.

N/A Annually




150 of 365 9/22/2014 2:48 PM





N/A Annually






(2) Restorable-type






(d) Heat detectors


X

Annually

(see14.4.4.5)





X See Method






151 of 365 9/22/2014 2:48 PM


X Annually





X Annually



X Semiannually











X Annually



X Annually







In addition to the testing required in Table14.4.3.2(g)(1) and Table 14.4.3.2(h), test duct smokedetectors that use sampling tubes to ensure that theywill properly sample the airstream in the duct using amethod acceptable to the manufacturer or in


152 of 365 9/22/2014 2:48 PM

accordance with their published instructions.






X Annually




N/A See 14.4.4.3








X Annually




X Semiannual

Operate valve and verify signal receipt to be within thefirst two revolutions of the handwheel or within one-fifthof the travel distance, or per the manufacturer’spublished instructions.

(2) High- or low-airpressure switch

X Quarterly

Operate switch and verify receipt of signal is obtainedwhere the required pressure is increased or decreaseda maximum 10 psi (70 kPa) from the required pressurelevel.

(3) Roomtemperature switch

X QuarterlyOperate switch and verify receipt of signal to indicatethe decrease in room temperature to 40°F (4.4°C) andits restoration to above 40°F (4.4°C).

(4) Water levelswitch

X Quarterly

Operate switch and verify receipt of signal indicatingthe water level raised or lowered a maximum 3 in. (70mm) from the required level within a pressure tank, or amaximum 12 in. (300 mm) from the required level of anonpressure tank. Also verify its restoral to requiredlevel.

(5) Watertemperature switch

X QuarterlyOperate switch and verify receipt of signal to indicatethe decrease in water temperature to 40°F (4.4°C) andits restoration to above 40°F (4.4°C).

(k) Mechanical,electrosonic, orpressure-type waterflowdevice

X Semiannually



153 of 365 9/22/2014 2:48 PM

(l) Multi-sensor firedetector or multi-criteriafire detector orcombination fire detector

X Annually






Where individual sensors cannot be tested individually,

test the primary sensor. j


18.Special hazardequipment

(a) Abort switch(dead-man type)


(b) Abort switch(recycle type)

X AnnuallyOperate abort switch and verify development of correctmatrix with each sensor operated.

(c) Abort switch(special type)

X Annually


(d) Cross-zonedetection circuit





(g) Squibb releasecircuit

X AnnuallyUse AGI flashbulb or other test light approved by themanufacturer. Verify operation of flashbulb or light.

(h) Verified,sequential, or countingzone circuit






X Annually

Test communication between the device connecting thefire extinguisher electronic monitoring device/systemand the fire alarm control unit to ensure proper signalsare received at the fire alarm control unit and remoteannunciator(s) if applicable.



Test communication between the device connecting thecarbon monoxide device/system and the fire alarmcontrol unit to ensure proper signals are received at thefire alarm control unit and remote annunciator(s) ifapplicable.


154 of 365 9/22/2014 2:48 PM




22.Alarm notificationappliances

(a) Audible n X N/A



(b) Audible textualnotification appliances(speakers and otherappliances to conveyvoice messages)

X N/A




(c) Visible X N/A


N/A Annually For periodic testing, verify that each appliance flashes.







X Annually

Use the manufacturer’s published instructions and theas-built drawings provided by the system supplier toverify correct operation after the initial testing phasehas been performed by the supplier or by the supplier’sdesignated representative.


155 of 365 9/22/2014 2:48 PM














27.Supervising stationalarm systems —receiving equipment



Actuate initiating device and verify receipt of the correctinitiating device signal at the supervising station within90 seconds. Upon completion of the test, restore thesystem to its functional operating condition.




Cause a signal to be transmitted on each individualincoming DACR line (path) at least once every 6 hours(24 hours for DACTs installed prior to adoption of the2013 edition of NFPA 72 ). Verify receipt of thesesignals.


X Monthly



156 of 365 9/22/2014 2:48 PM















(e) Radio alarmsupervising stationreceiver (RASSR) andradio alarm repeaterstation receiver(RARSR)

X Monthly





(f) Private microwaveradio systems

X Monthly






(g)Performance-basedtechnologies

X Monthly

Perform tests to ensure the monitoring of integrity ofthe transmission technology and technology path.Where a single communications path is used,disconnect the communication path. Verify that failureof the path is annunciated at the supervising stationwithin 60 minutes of the failure (within 5 minutes forcommunication equipment installed prior to adoption ofthe 2013 edition of NFPA 72 ). Restore thecommunication path.

Where multiple communication paths are used,disconnect both communication paths and confirm thatfailure of the path is annunciated at the supervisingstation within not more than 6 hours of the failure(within 24 hours for communication equipment installed


157 of 365 9/22/2014 2:48 PM

prior to adoption of the 2013 edition of NFPA 72 ).Restore both communication paths.



X Semiannually

Actuate publicly accessible initiating device(s) andverify receipt of not less than three complete rounds ofsignal impulses. Perform this test under normal circuitconditions. If the device is equipped for open circuitoperation (ground return), test it in this condition as oneof the semiannual tests.



(c) Master box

(1) Manualoperation

X Semiannually Perform the tests prescribed for 28(a).

(2) Auxiliaryoperation

X Annually Perform the tests prescribed for 28(b).

29.Low-power radio(wireless systems)


(1) Use the manufacturer’s published instructions andthe as-built drawings provided by the system supplierto verify correct operation after the initial testing phasehas been performed by the supplier or by the supplier’sdesignated representative.


(3) Check batteries for all components in the systemmonthly unless the control unit checks all batteries andall components daily.

30.Mass notificationsystems


At a minimum, test control equipment to verify correctreceipt of alarm, supervisory, and trouble signals(inputs); operation of evacuation signals and auxiliaryfunctions (outputs); circuit supervision, includingdetection of open circuits and ground faults; and powersupply supervision for detection of loss of ac powerand disconnection of secondary batteries.






X Annually

Disconnect all secondary (standby) power and testunder maximum load, including all alarm appliancesrequiring simultaneous operation. Reconnect allsecondary (standby) power at end of test. For


158 of 365 9/22/2014 2:48 PM

redundant power supplies, test each separately.

(f) Audible textualnotification appliances(speakers and otherappliances to conveyvoice messages)

X Annually

Measure sound pressure level with a sound level metermeeting ANSI S1.4a, Specifications for Sound LevelMeters, Type 2 requirements. Measure and recordlevels throughout protected area. Set the sound levelmeter in accordance with ANSI S3.41, AmericanNational Standard Audible Evacuation Signal, usingthe time-weighted characteristic F (FAST). Record themaximum output when the audible emergencyevacuation signal is on.




(h) Control unit functionsand no diagnosticfailures are indicated

X Annually

Review event log file and verify that the correct eventswere logged. Review system diagnostic log file; correctdeficiencies noted in file. Delete unneeded log files.Delete unneeded error files. Verify that sufficient freedisk space is available. Verify unobstructed flow ofcooling air is available. Change/clean filters, coolingfans, and intake vents.


(j) Control unit security X AnnuallyIf remote control software is loaded onto the system,verify that it is disabled to prevent unauthorized systemaccess.

(k) Audible/visiblefunctional test



(m) Secondary powertest

X AnnuallyDisconnect ac power. Verify the ac power failure alarmstatus on central control equipment. With ac powerdisconnected, verify battery voltage under load.









fInitiating devices such as smoke detectors used for elevator recall, closing dampers, or releasing doors held in the


159 of 365 9/22/2014 2:48 PM

open position that are permitted by the Code (see NFPA 101, Life Safety Code , 9.6.3) to initiate supervisory signalsat the fire alarm control unit (FACU) should be tested at the same frequency (annual) as those devices when theyare generating an alarm signal. They are not supervisory devices, but they initiate a supervisory signal at the FACU.












Item 7. of Table 14.4.3.2 requires a loading of the fire alarm panel batteries. SIG-TMS should review Item 7 as it potentially impacts test reults when perfoming battery tests under Item 9. In addition Battery Task Team recommendations for Items 9. (c) (3) and (4) may also be applicable.

Related Item






Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected but held


160 of 365 9/22/2014 2:48 PM



161 of 365 9/22/2014 2:48 PM


14.6.1.2.1

For software-based systems, a copy of the site-specific software shall be provided to the system owner or owner’sdesignated representative. The site-specific software documentation shall include both the user passcode andeither the system programming password or specific instructions on how to obtain the programming password fromthe system manufacturer.


The programming password is needed and the language show is good. The more problematic password for a user to obtain is their user passcode. This passcode is used for example, to set the time and date, disable a point, run a report, review historical logs, etc. It is important that an installer supply this as well as the programming passcode or how to obtain that passcode.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:






162 of 365 9/22/2014 2:48 PM


14.6.1.2.1

For software-based systems, a copy of the site-specific software, including specific instructions on how to obtainthe means of system and software access (password) shall be provided to the system owner or owner’s designatedrepresentative. The site-specific software documentation shall include either the system programming password orspecific instructions on how to obtain the password from the system manufacturer.


The text should be revised for consistency with the language used in FR-267 Section 7.2.1 of the first draft.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:






163 of 365 9/22/2014 2:48 PM


17.1.3

The requirements of Chapters 7, 10, 12, 21, 23, and 24 shall also apply unless they are in conflict with this chapter.



The correlating committee makes reference to 17.1.3 and the phrase ", unless they are in conflict with this chapter." Requirements should not conflict. Where deviations from the requirements of other chapters are warranted they should be identified and addressed through appropriate allowances in the code language. The correlating committee directs the SIG-IDS committee to review the requirements in Chapter 17 with consideration to resolving any identified conflicts with other chapters. Where changes are made they should be done without introducing new material in the second draft phase. In addition the committee should consider rewording 17.1.3 to positive language. For example: The requirements of chapters x, y and z shall apply unless otherwise noted in this chapter.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected but held

Resolution: The TC is holding this for further study due to the complexity of issues raised. The committee has createda task group to review the complete document for conflicts and to develop the appropriate revisions for thenext cycle.


164 of 365 9/22/2014 2:48 PM


Proposed change to resolved Public Input 106

All HVLS fans shall be interlocked to shut down immediately upon receiving a waterflow signal from the alarmsystem in accordance with the requirements of NFPA 72 . [NFPA 13, 11.1.7(4)]


PI 106 was resolved by the committee, stating that the objective needs to be determined on a case by case basis. However, the proposed language for this Public Comment is an excerpt of the wording used in NFPA 13 and would be useful in NFPA 72 to avoid conflicts in requirements.

Related Item



Submitter Full Name: Thomas Hammerberg

Organization: Automatic Fire Alarm Association, Inc.

Affilliation: Automatic Fire Alarm Association, Inc.

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: SIG-IDS: The SIG-IDS committee does not believe that this requirement belongs in Chapter 17 and refers itto SIG-PRO for further study. SIG-PRO: The requirement to interlock the HVLS fans (an emergency controlfunction) already exists in NFPA 13 11.1.7(4). This can be implemented in accordance with NFPA 72 21.2without adding an additional specific requirement in Chapter 21. The design of HVLS fan shutdown is anengineering decision.


165 of 365 9/22/2014 2:48 PM


18.4.1.4.1 *

The designer of the audible notification system shall identify the rooms and spaces that will have audiblenotification and those where audible notification will not be provided.


NFPA 72 does not have jurisdiction to determine where equipment is to be located. This creates conflicts with building and fire codes as well the NFPA 101. The committee stated that the IBC or IFC is not used everywhere, the the IBC is adopted in all 50 states, at least in some jurisdictions. If anything, the designer can determine the minimum acceptable dB level for occupant notification, but not whether or not audible notification is required.

IBC/IFC - 907.2 Where required—new buildings and structures.An approved fire alarm system installed in accordance with the provisions of this code and NFPA 72 shall be provided in new buildings and structures in accordance with Sections 907.2.1 through 907.2.23 and provide occupant notification in accordance with Section 907.5, unless other requirementsare provided by another section of this code.907.5 Occupant notification systems. A fire alarm system shall annunciate at the fire alarm control unit and shall initiate occupant notification upon activation, in accordance with Sections 907.5.1 through 907.5.2.3.4.907.5.2.1.1 Average sound pressure. The audible alarm notification appliances shall provide a sound pressure level of 15 decibels (dBA) above the average ambient sound level or 5 dBA above the maximum sound level having a duration of at least 60 seconds, whichever is greater, in every occupiable space within the building.

NFPA 101 - 9.6.3.5 Unless otherwise provided in 9.6.3.5.1 through 9.6.3.5.8, notification signals for occupants to evacuate shall be audible, and visible signals in accordance with NFPA72, National Fire Alarm and Signaling Code, and ICC/ANSIA117.1, American National Standard for Accessible and Usable Buildings and Facilities, or other means of notification acceptable to the authority having jurisdiction shall be provided.9.6.3.6.1 The general evacuation alarm signal shall operate throughout the entire building.9.6.3.6.2* Where total evacuation of occupants is impractical due to building configuration, only the occupants in the affected zones shall be notified initially. Provisions shall be made to selectively notify occupants in other zones to afford orderly evacuation of the entire building.

Related Item

Public Input No. 302-NFPA 72-2013 [Section No. 18.4.1.4.1]



Organization: Automatic Fire Alarm Association, Inc.

Affilliation: Automatic Fire Alarm Association, Inc.

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: This requirement does not create a conflict. It is only a requirement for design documentation. Thisstatement combined with the citations from the IBC combine to require the designer to document thosespaces that are “occupiable” and those that are not so that the plan can be reviewed and approved.


166 of 365 9/22/2014 2:48 PM


18.4.2.3

The signal shall be repeated for a period appropriate for the purposes of evacuation of the building, but for not lessthan 180 seconds. The minimum repetition time shall be permitted to be manually interrupted. The minimumrepetition time shall be permitted to be automatically interupted for the transmission of mass notification messages.


This statement seems inconsistent with the intention of MNS systems. Based on circumstances, MNS may employ automatic messages to direct occupants under various emergency situations. This section requires that evacuation signals may not be automatically interrupted for three minutes. In that time, people may have responded (or not responded) inappropriately because the nature of the emergency or the proper actions could not be made clear to occupants in time.

Related Item






Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: This statement seems inconsistent with the intention of MNS systems. Based on circumstances, MNS mayemploy automatic messages to direct occupants under various emergency situations. This section requiresthat evacuation signals may not be automatically interrupted for three minutes. In that time, people may haveresponded (or not responded) inappropriately because the nature of the emergency or the proper actionscould not be made clear to occupants in time. A reference to Chapter 24 was added for correlation. Inaddition, the section was revised to meet the Manual of Style.


167 of 365 9/22/2014 2:48 PM


18.4.5.3*

Effective January 1, 2014, audible appliances provided for the sleeping areas to awaken occupants shall produce alow frequency alarm signal that complies with the following:

(1) The

alarm signal shall be a square wave or provide equivalent awakening ability.

(2) The wave shall waveform shall have a fundamental frequency of 520 Hz ± 10 percent.



18_4_5_3_substantiation.pdf 2013 NFPA 72 ROP and ROC excerpts


My proposal lacked the necessary detail for the committee. I understand this. Allow me to recap. During the 2013 NFPA 72 ROP, it was revealed to the SIG-HOU committee that while the work of Dr. Bruck on low frequency signals indicated that a square wave was used, a look into her data by a UL 217 STP found that, in fact, she had used several other signals including a triangle wave and a sawtooth wave in addition to a square wave. This UL STP was working on the test specifications of the standardized listing product testing for low frequency. When this information was brought to the SIG-HOU commiittee's attention, the language was changed to just require a wave form. Appropriate harmonics was included in the language, but the TCC requested that this unenforceable language be removed. SIG-HOU and the TCC appropriately directed this to SIG-NAS to implement the same change for correlation, but SIG-NAS has not done so. It appears from the 2013 edition ROP and ROC, and my proposal this cycle, that SIG-NAS's refusal to implement this change is based upon a lack of scientific data. This likely results from a lack of awareness of the UL STP research which, while undocumented, discovered this information on the waveforms.

Hopefully this clears up why this change should be made. As it stands now, there is a loose correlating issue. While Chapter 29 does not point directly to 18.4.5.3, producers making product to comply with Chapter 29 can use any waveform as long as the fundamental frequency is 520 Hz and it is listed by UL 217. Meaning it has to pass UL testing, so it will have the appropriate harmonics etc. But to comply with Chapter 18, one is unnecessarily constricted to a square wave, despite the fact that other waveforms would pass UL testing and were indeed tested by Dr. Bruck. Therefore, for clarity on the issue, SIG-NAS should accept this proposal.

Related Item



Submitter Full Name: Stephen Olenick

Organization: Combustion Science & Engineering, Inc.

Affilliation: SafeAwake, LLC

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:




168 of 365 9/22/2014 2:48 PM

Statement: The effective date was eliminated, since it has passed. Reference to product listing was added to ensurethat the correct waveform, frequency, and harmonics are included in the appliance performance.


169 of 365 9/22/2014 2:48 PM


18.5.3.2

A maximum Effective January 1, 2017 a maximum pulse duration shall be 0.2 second with a maximum duty cycleof 40 percent. 20 milliseconds.


Submitter recommends this change in order to ensure that visual signaling devices continue to be effective at notifying the public, especially in indirect viewing situations. Indirect viewing is a key component, especially for situations when the public is concentrating on other tasks and not looking directly at the visual appliance or looking directly at a wall in the space. This distinction matters, as the code should be written in order to be effective as it pertains to a more typical scenario; whereby, the public is viewing, reading, or writing something such as a newspaper, book, numerical task, smart device, etc.With the advent of new light source technologies, the submitter wants to ensure that the code stays relevant by allowing for new technologies but also maintains the current safety level associated with visual notification that exists today.A key difference between the technology historically used and some of the newer technology is the pulse width in addition to the effective intensity (candela). The technology typically employed today and in the past has been a Xenon flash tube that has a very short pulse width that is less than 1millisecond (ms) in addition to meeting the effective intensity requirements. Further, the effective intensity and pulse width for the Xenon product has been used effectively in NFPA 72 for device spacing and coverage area, such as a 15 candela strobe for 20 foot by 20 foot spacing. Therefore, new technology should perform in a similar manner whereas the same intensity (candela), device spacing, and coverage area would still apply.Newer technologies can incorporate a longer pulse width than the Xenon flash tube. Up to this point, the 200 millisecond (0.2 second) pulse width in the code was acceptable since the visual notification appliances utilized a Xenon flash tube that had a very short pulse width, well below the 200 millisecond pulse duration. Newer technologies have the ability to vary the pulse width and can be set to, but not limited to, the following: 1 ms, 8, ms, 10 ms, 14 ms, 18 ms, 25 ms, 50 ms, 100 ms, or 200 ms.Two studies have been conducted and published that test alerting and detection ability in indirect viewing situations of the Xenon flash tube versus various pulse widths of newer technology. One study is "Human Factors Comparison of Detectability For LED and Xenon Tube Light Sources for Fire Alarm Notification Strobes Follow On Testing to Determine Xenon Equivalency", by Ken Savage, TYCO Fire Protection Products, May 7, 2012 (The Savage Study). The second study is "Parameters for Indirect Viewing of Visual Signals Used in Emergency Notification", Prepared by John D. Bullough, Nicholas Skinner, and Yiting Zhu, Lighting Research Center, Rensselaer Polytechnic Institute, September 2013, on behalf of The Fire Protection Research Foundation (The FPRF Study). Both studies are attached to this submission.Combined, these experimental studies tested the pulse width hypothesis on 100 test subjects: 30 for the Savage Study and 70 for the FPRF Study. The relevant testing from both was conducted in rooms that approximate 20 foot spacing and test 15 candela and 40 candela Effective Intensity. The subjects were given a task (newspaper reading in the Savage Study and numerical problems in the FPRF study) and the visual signal was behind the subject. The relevant lighting level was typical (an average of 250 lx in the case of the FPRF Study – which is considered a moderately lit room). These test environments were designed to test a likely public safety scenario.The Savage Study results were that a 15 cd (Effective Intensity) LED light source at a 14 ms pulse width was equivalent in alerting and detection capability to a 15 cd Xenon flash tube. Using additional data, The Savage Study recommends a pulse width of 20 ms.“In many cases, the 100 millisecond pulse was essentially invisible to the test subjects, yet the current standard allows up to a 200 millisecond pulse width.” Source: Human Factors Comparison of Detectability For LED and Xenon Tube Light Sources for Fire Alarm Notification Strobes Follow On Testing to Determine Xenon Equivalency, by Ken Savage, TYCO Fire Protection Products, May 7, 2012, page 15.

The FPRF Study found (in Experiment 5) that when conducting a numerical verification task (NVT) test subjects detected the 40 cd Xenon flash tube 100 percent of the time. (Note: The commercially available Xenon flash tube product was set to the nominal 15 cd setting. Based on intensity profile data provided by the manufacturer, an estimated value of 40 cd for the effective intensity was used for subsequent analysis.) Test subjects performing the NVT detected the 25 ms pulse width LED 100 percent of the time with an effective intensity of 61 cd. Test subjects performing the NVT detected the 50 ms pulse width LED 100 percent of the time with an effective intensity of 109 cd. Test subjects performing the NVT detected the 100 ms pulse width LED 90 percent of the time with an effective intensity of 182 cd. Stated differently, the 40 cd Xenon flash tube had 100 percent detection while the detection rates at the same effective intensity were as follows through extrapolation in Figure 11.a: 25 ms pulse width had 75 percent detection as did the 50 ms pulse width while the 100 ms pulse width had 25 percent detection.


170 of 365 9/22/2014 2:48 PM

Source: Parameters for Indirect Viewing of Visual Signals Used in Emergency Notification, Prepared by John D. Bullough, Nicholas Skinner, and Yiting Zhu, Lighting Research Center, Rensselaer Polytechnic Institute, September 2013, on behalf of The Fire Protection Research Foundation, page7, page 12, Figure 11.a.Therefore, because of the results of these 2 studies, submitter recommends changing the pulse width to 20 ms to ensure equal performance to Xenon flash tubes in the NFPA 72 spacing and coverage area requirements.Submitter recommends an effective date of January 1, 2017. While submitter recognizes the need for a change to the code to ensure the same level of safety as with the older technology – there is a recognition of the need for a practical approach that requires that time be allotted for manufacturers to design, test, and modify their products (if necessary) and allow for recognized testing laboratories to develop tests and certify compliance. Further, when research has been conducted that necessitates technology changes in the code, the committee for this chapter has enacted an effective date.

Note: Supporting material is available for review at NFPA Headquarters.

Related Item



Submitter Full Name: Jeffrey Klein

Organization: Honeywell/System Sensor

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: This change is needed because research has shown that the use of longer pulse widths with lights ratedusing the concept of candela effective will result in poor detection performance. Longer pulse widths must becombined with some as yet undetermined increase in peak candela intensity in order to be effective.However, the research has shown that strobes rated using candela effective and that have pulse widths up to100 ms can be effective in corridor, direct viewing application. Thus the allowance for their use in corridorswas needed. Additional work is being done to determine how the code should be modified to have aperformance metric that will work for lights with both long and short pulse durations.


171 of 365 9/22/2014 2:48 PM


18.5.3.2

A maximum pulse duration shall be 0.2 second with a maximum duty cycle of 40 percent. 20 milliseconds.


The original proposal (PI 222-NFPA72-2013) was rejected with the comment that "It is premature to adopt any new timing requirements until the independent study initiated by the Fire Protection Research Foundation and currently underway at the Lighting Research Center at Rensselaer Polytechnic Institute is concluded and the final results are presented to the TC. Proposed changes to Section 18.5.3.2 should come as a result once all of the research findings are available"

The FPRF study is complete and their testing came up with similar results to the testing done at Tyco and used to substantiate this proposal. In fact, their testing indicated a slightly larger discrepancy in perception than the Tyco testing.

This proposal was rejected in the last cycle, and since then strobes with long pulse widths have made their way onto the market. Although compliant with the current requirements our testing (as well as historical testing by other organizations, and the testing commissioned by the FPRF) shows that they are significantly less effective than short pulse length xenon based strobes. The industry has a rapidly brewing problem that needs to be addressed. We cannot wait another three years for a requirements update. In that period of time many strobes that are fundamentally ineffective will be installed in buildings.

Related Item



Submitter Full Name: Anthony Capowski


Affilliation: Tyco

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:





172 of 365 9/22/2014 2:48 PM


18.5.3.2

A maximum pulse duration shall be 0.2 second with a maximum duty cycle of 40 percent 1 seconds .


There has been a significant amount of activity centered around this single number. The reseach conducted by Mr. Savage (Tyco) and RPI (FPRF) has been extensive and extremely valuable. This research has shown that the existing strobe requirements (both UL1971 and NFPA 72) do not sufficiently define the requirements for white light visual signaling appliances for the hearing impaired. The UL1971 STP task group is working on defining the product test requirements required to address this issue at the product standard level. However the requested change from 200ms to 100ms is necessary due to additional information discovered as part of the RPI research. The RPI research clearly shows that for indirect viewing, as you increase pulse width the detection performance also increases up to 100ms. In addition, the RPI research references an earlier study by Baumgardt and Hillmann (1961) and indicates that this research implies that detection performance is linear up to a pulse widths of 100ms but above this the relationship between pulse width and performance flatens or changes. Based on this information NFPA 72 needs to change to limit the allowed pulse width to 100ms. Additional changes are required to further define the requirements for white light visual signaling appliances for the hearing impaired however these will be product standard changes which belong in the product family standards UL1971. The allowed pulse width change from 200ms to 100ms is a necessary change to NFPA 72 that will pave the way for improving the product family standard requirements (UL1971).

Related Item



Submitter Full Name: Leon Newsome

Organization: Cooper Notification

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:





173 of 365 9/22/2014 2:48 PM


21.1* Application.

The provisions of Chapter 21 shall cover the minimum requirements and methods for emergency control functioninterfaces to fire alarm systems and emergency communications systems in accordance with this chapter.

21.1.1

The requirements of Chapters 7, 10, 17, 18, 23, 24, and 26 shall apply, unless they are in conflict with this chapter.

21.1.2

The requirements of Chapter 14 shall apply.

21.1.3

The requirements of this chapter shall not apply to Chapter 29 unless otherwise stated.


CC NOTE: The following CC Note No. 8 appeared in the First Draft Report as First Revision No. 222, and is also related to Public Input No. 566.

The correlating committee makes reference to 21.1.1 and the phrase ", unless they are in conflict with this chapter." Requirements should not conflict. Where deviations from the requirements of other chapters are warranted they should be identified and addressed through appropriate allowances in the code language. The correlating committee directs the SIG-PRO committee to review the requirements in Chapter 21 with consideration to resolving any identified conflicts with other chapters. Where changes are made they should be done without introducing new material in the second draft phase. In addition the committee should consider rewording 21.1.1 to positive language. For example: The requirements of chapters x, y and z shall apply unless otherwise noted in this chapter.

Related Item






Street Address:

City:

State:

Zip:


Committee Statement



Statement: The revisions were made to use more positive language.


174 of 365 9/22/2014 2:48 PM


21.3.3

Unless otherwise required by the authority having jurisdiction, only the elevator lobby, elevator hoistway, elevatormachine room, elevator control room, and elevator control space smoke detectors or other automatic fire detectionas permitted by 21.3.10 shall be used to initiate elevator Phase I Emergency Recall Operation.

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


I would like to add the following aspects to the problem I have stated in PI 193:

1. The pit sprinkler is required by NFPA 13 for hydraulic elevators. The elevator code ASME A17.1-2013 requires to add phase I recall upon this sprinkler. It should not be the jurisdiction of NFPA 72 to act like a building code or the elevator code and to require specific protection for elevator. Requiring Phase I recall shall be the jurisdiction of the elevator code only. While I understand that intent of including duplicate Elevator Code requirements in NFPA 72 (to assist FA personnel who are not familiar with the elevator code) - This specific requirement should not be added to NFPA 72 since it causes a great deal of confusion to both FA personnel and Fire AHJs.

2. Providing a pit FAID connected to the building’s FA system or a dedicated function FA system for elevator recall, especially where this FAID is required to be accessible from outside the hoistway, is a very costly requirement (both for the initial installation and for ongoing service and maintenance). Since NFPA 72-2013 is now repeating the ASME A17.1 requirement for a FAID (or waterflow switch) installation in elevator pits having sprinklers, this new NFPA 72 requirement is causing a major enforcement problem for AHJs for the following reason:

Anytime a FA system upgrade, or a FA system replacement is performed in existing buildings having existing elevators, the current NFPA 72-2013 code requirements apply to the upgraded/replaced FA system. In many cases I see as an AHJ, reviewing FA permit plans and system designs, the existing elevator is provided with an existing pit sprinkler, but without an associated pit FAID generating Phase I recall. Now, the FA designers who are basing their system design on NFPA 72-2013 are adding pit FAIDs with associated Phase I recall, to their design plans and sequence of operations, since this is the current applicable FA code. This creates a major problem since many of the existing elevators are not even capable of Phase I recall operation. In my jurisdiction, we are not enforcing this ASME A17.1 (and now NFPA 72-2013) requirement for existing elevators even if they are capable of Phase I recall, but it takes me a great deal of time, as an AHJ, to explain to FA designers why this specific code section is not enforced.

3. In my opinion, the requirement for Phase I recall upon pit sprinkler should be also removed from the Elevator Code and I am working with both ASME Hoistway and Emergency Operations committees to remove this requirement from the elevator code since there is no evidence or empirical data for hydraulic fluids fires in elevator pits. But there is definitely no need to include this confusing requirement in NFPA 72.





Related Item




Submitter Full Name: Sagiv Weiss-Ishai

Organization: San Francisco Fire Department

Street Address:


175 of 365 9/22/2014 2:48 PM

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: ANSI/ASME A.17.1 currently has the requirement for fire alarm initiating devices to be installed in elevatorhoistways for the purpose of initiation Phase I Emergency Recall Operation in accordance with NFPA 72and the exception is part of the installation provisions.


176 of 365 9/22/2014 2:48 PM


21.3.4

Each initiating device used to initiate fire fighters' service recall shall be capable of initiating elevator recall when allother devices on the same initiating device circuit have been manually or automatically placed in the alarmcondition.


CC NOTE: The following CC Note No. 7 appeared in the First Draft Report as First Revision No. 138.

The correlating committee directs the SIG-PRO committee to reconsider their action on FR 138. The proposed change requiring access from outside the hoistway could create a conflict with other codes and standards as it would require changes to the building construction. It is suggested that the requirement be deleted or modified to prevent this potential conflict.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:


Resolution: SR-11-NFPA 72-2014 The committee notes the section reference (21.3.4) was incorrect and shouldhave been 21.3.5.

Statement: Paragraph 21.3.5 added by FR 138 is deleted to resolve potential conflicts with building andconstruction code requirement.


177 of 365 9/22/2014 2:48 PM


21.3.7

Smoke detectors shall not be installed in unsprinklered elevator hoistways unless they are installed to activate theelevator hoistway smoke relief equipment or to protect elevator control spaces or elevator machinery spacesinitiate Phase I Emergency Recall Operation as required in 21.3.15.1 (2) and 21.3.15.2 (2).


Revised wording more appropriately describes the operation. Smoke detectors really do not "protect" ... but they do "initiate".

Related Item



Submitter Full Name: Bruce Fraser

Organization: Fraser Fire Protection Service

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted


Statement: Revised wording more appropriately describes the operation. Smoke detectors really do not "protect" ...but they do "initiate".


178 of 365 9/22/2014 2:48 PM


21.3.8 *

When sprinklers are installed in elevator pits, automatic fire detection shall be installed to initiate elevator recall inaccordance with 2.27.3.2.1(c) of ANSI/ASME A.17.1/CSA B44, Safety Code for Elevators and Escalators, and thefollowing shall apply:

(1) Where sprinklers are located above the lowest level of recall, the fire detection device shall be located at thetop of the hoistway.

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

(3) Outputs to the elevator controller(s) shall comply with 21.3.15 .


This section is repeating ASME A17.1-2013 Section 2.27.3.2.1. This section creates great deal of confusion to FA designers and installers and to Fire and Elevators' HAJs. This section should NOT be under the jurisdiction of NFPA 72 since it is included in the elevator code. The requirement for Phase I recall via FAID upon pit sprinklers is not based on risk analysis, nor on empirical data and therefore it should be removed from NFPA 72.See my Public Comment # 101 for reference.



Public Comment No. 101-NFPA 72-2014 [Section No. 21.3.3] same rational


Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The text is revised to better correlate with the requirements of ASME A17.1 and to clarify the installationrequirements of NFPA 72.


179 of 365 9/22/2014 2:48 PM


21.3.9 *

Smoke detectors shall not be installed in elevator pits to initiate elevator recall unless the smoke detector is listedfor the environment.


Smoke detectors should not be installed in elevator pits for generating Phase I emergency recall. This requirement is unnecessary and confusing.If Phase I recall will not be required upon pit sprinklers per my PC 101 and 102 - since its duplicating the elevator code requirement - This section will also not be required.



Public Comment No. 101-NFPA 72-2014 [Section No. 21.3.3] same rational

Public Comment No. 102-NFPA 72-2014 [Section No. 21.3.8] elevator code requirment

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The term "pit" has been replaced with "hoistway" because the pit is part of the hoistway. The change alsobetter correlates with the related annex material.


180 of 365 9/22/2014 2:48 PM


21.3.11

When actuated, any fire alarm initiating device that has initiated has activated elevator Phase 1 Emergency RecallOperation shall also be annunciated at the building fire alarm control unit or at the fire alarm control unit describedin 21.3.2.


The problem is that some elevator associated FAIDs such as lobby smoke detectors or EMR/ECR smoke detectors could be in ALARM mode but they are not necessary the INITIATING device that initiated the phase I recall. These devices should be annunciated at the FACU also and NOT only the FAID that Initiated the Phase I Emergency Recall operation

Related Item





Street Address:

City:

State:

Zip:


Committee Statement



Statement: The revised text provides consistent terminology throughout the requirement.


181 of 365 9/22/2014 2:48 PM


21.3.12

Actuation from the elevator hoistway, elevator machine room, elevator machinery space, elevator control space, orelevator control room smoke detectors or other automatic fire detection as permitted by 21.3.10 shall causeseparate and distinct visible annunciation at the building fire alarm control unit or at the fire alarm control unitdescribed in 21.3.2 to alert fire fighters and other emergency personnel that the elevators are no longer safe touse .


If any of the FAIDs described in this section was NOT the INITIATING device for Phase I Emergency Recall Operation, but it was a subsequence device - The intent it that this device would be separately and distinctively annunciated on the FACU; However, if the Fire was not originated in the EMR/ECR or hoistway, the elevator may be still SAFE to use by responding Firefighters under Phase II emergency operation, since the Fire was not originated in the elevator associated spaces (Hoistway, EMR/ECR) and the subsequent actuation of the device was caused by a smoke migration only.

Related Item


First Revision No. 141-NFPA 72-2013 [Section No. 21.3.14 [Excluding any Sub-Sections]]




Street Address:

City:

State:

Zip:


Committee Statement



Statement: The proposed change eliminates unnecessary wording that is not part of the actual requirement.


182 of 365 9/22/2014 2:48 PM


21.3.13

Where approved by the authority having jurisdiction, the detectors used to initiate elevator recall shall be permittedto initiate a supervisory signal in lieu of an alarm signal were connected to a dedicated function fire alarm controlunit described in section 21 .3.2


If the building has a Building FA system - then the lobby detectors should initiate Alarm signal via the notification system. Allowing the generation of Supervisory signals will create great deal of inconsistencies between buildings and systems and will confuse occupants, designers, HAJs and firefighters. If the building has only a dedicated FA system for Elevator Recall and supervisory, then there is no need to generate ALARM signal (No building notification system), even if the dedicated FACU is connected (OR NOT) to a supervising station.




Related Item





Street Address:

City:

State:

Zip:


Committee Statement


Resolution: The proposed change would restrict something that is already permitted in NFPA 101.


183 of 365 9/22/2014 2:48 PM


21.3.14

Where lobby detectors are used for other than initiating elevator recall, the signal initiated by the detector shall alsoinitiate an alarm signal.


There is no need for this section per PC # 106.Also if the building has a dedicated function FA system and NOT a building FA system and there is NO notification system - There is no need to generate alarm signalExample is protected premise dedicated FACU for Elevator Recall and supervisory and for smoke detectors associated with door holders. - There is no notification system in the building and the FACU is a local only unit. There is No need to generate FA signals in this case.




Related Item





Street Address:

City:

State:

Zip:


Committee Statement



Statement: The change removes a potential conflict with 21.3.13.


184 of 365 9/22/2014 2:48 PM


21.3.15.3 * Visual Warning.

For each elevator or group of elevators, an output(s) outputs shall be provided to the elevator controller for thepurpose of causing the elevator visual warning signal to operate, in accordance with ANSI /ASME A17.1/CSAB44, Safety Code for Elevators and Escalators , in response to the following:

(1) Activation of the elevator machine room, elevator machinery space, elevator control space, or elevator controlroom initiating devices identified in 21.3.15.1 (2) or 21.3.15.2 (2)

(2) Activation of the elevator hoistway initiating devices identified in 21.3.15.1 (3) or 21.3.15.2 (3)

(3) Activation of the elevator lobby initaiting devices identified in 21.3.15.1 (1) or 21.3.15.2 (1)


The outputs from the FA control unit to the elevator controller should be provided to the elevator controller from ALL associated Elevator's FA initiating devices. Upon receiving these signals from the FA control unit, the Elevator Controller decides when to turn the Visual warning inside the elevator car in a Solid or a Flashing mode per the specific sequence described in the elevator code ASME A17.1. It is very important to provide ALL associated FA signals to the controller and Not only the Hoistway/EMR/ECR signals. The activation of the elevator visual warning signal shall be solely determined by the elevator code and not by NFPA 72.

Related Item






Street Address:

City:

State:

Zip:


Committee Statement


Resolution: There is no technical justification for the change.


185 of 365 9/22/2014 2:48 PM


21.3.15.3 * Visual Elevator Warning Signal .

For each elevator or group of elevators, an output(s) shall be provided to the elevator controller for the purpose ofcausing the elevator visual warning signal to operate in response to the following:

(1) Activation of the elevator machine room, elevator machinery space, elevator control space, or elevator controlroom initiating devices identified in 21.3.15.1 (2) or 21.3.15.2 (2)

(2) Activation of the elevator hoistway initiating devices identified in 21.3.15.1 (3) or 21.3.15.2 (3)


Revised wording more clearly describes the signal and is meant to avoid confusion.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: Revised wording more clearly describes the requirement. Editorial changes were made clarify that any ofthe outputs will cause the warning signal.


186 of 365 9/22/2014 2:48 PM


21.4.2 *

If heat detectors are used to shut down elevator power prior to sprinkler operation, they shall be placed within 24 in.(610 mm) of each sprinkler head and be installed in accordance with the requirements of Chapter 17 .Alternatively and section 21.3.4. Alternatively , engineering methods, such as those specified in Annex B, shall bepermitted to be used to select and place heat detectors to ensure response prior to any sprinkler head operationunder a variety of fire growth rate scenarios.


There is no term "Sprinkler Head" in the Sprinkler Code NFPA 13 - Therefore I propose to remove the word "Head" from NFPA 72.Also, the same rational to access smoke detectors generating Phase I recall from outside the hoistway per Section 21.3.4, shall apply to heat detectors installed for shunt trip purposes. Fire Alarm personnel shall not be required to install and service these devices on top of elevators cars inside elevator hoistways.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement



Statement: There is no term "Sprinkler Head" in the Sprinkler Code NFPA 13.


187 of 365 9/22/2014 2:48 PM


21.5 Fire Service Access Elevators.

Where one or more elevators are specifically designated and marked as fire service access elevators, theconditions specified in 21.5.1 for the elevators, associated lobbies, and machine rooms shall be continuouslymonitored and displayed during any such use.

21.5.1

The conditions monitored and displayed shall include, but are not limited to, the following:

(1) Availability of main and emergency power to operate the elevator(s), elevator controller(s), and machine room(if provided) ventilation

(2)

(3) Temperature and presence of smoke in associated lobbies and machine room (if provided)

21.5.2

The conditions shall be displayed on a standard emergency services interface complying with Section 18.11.

21.5.3

The fire alarm control panel shall have a dedicated LED to indicate smoke detector "alarm" condition inEmergency and/or Standby Electrical Power Rooms.


I have read the responses to the original Public Inputs from myself on this proposed addition and others on related Public Inputs. CI 60, CI 61 & FR13 specifically stand out.

The problem with scrolling through the LCD display of an addressable fire alarm control panel during an emergency is that there can easily be a dozen or more "troubles", "alarms" and "supervisory" reports from the various initiating devices of a fire alarm system. The fireman or other operator at the fire alarm control panel should have a constant and readily viewable reminder that building normal and emergency power may soon be compromised. If a building requires a two hour rated room for critical electrical power equipment, the status of that room is also critical. I compare it to knowing when there is smoke in the engine room of a ship - absolutely vital information.

I understand that "NFPA 72 is a minimumm code...". Elevators and generators have their specific/dedicated control panels with emergency interfaces and information. This is proposal for increased safety that can be provided by the fire alarm system. It is different than the CI 60, CI 61 and FR 13 refernces which are Chapters 3 and 26 related.

Related Item



Submitter Full Name: DAVID SROKA

Organization: MASSACHUSETTS UNIV OF

Affilliation: None

Street Address:

City:

State:

Zip:


Committee Statement


Resolution: The proposed change is a design issue that is not needed within the requirements of NFPA 72.

* Status of the elevator(s), including location within the hoistway, direction of travel, and whether they areoccupied


188 of 365 9/22/2014 2:48 PM



Where one or more elevators are specifically designated and marked as fire service access elevators, theconditions specified in 21.5.1 for the elevators, associated lobbies, and machine rooms shall be continuouslymonitored and displayed during any such use. and 21.5.2 shall apply.

21.5.1

The conditions monitored and displayed shall include, but are not limited to, the following: Availability of main andemergency power to operate the

Status of elevator(s)

, elevator controller(s), and machine room (if provided) ventilation Status of the elevator(s),

including location within the hoistway, direction of travel

,

and whether

they are occupiedTemperature

the elevator(s) are occupied shall be permitted to be displayed on a building fire alarm system annunciator locatedat the fire command center.

21.5.2 When required, temperature and presence of smoke in associated lobbies and machine room

(if provided)

shall be displayed on a building fire alarm system annunciator located at the fire command center.

21.5.

2

3 The conditions in 21.5.1 and 21.5.2 shall be permitted to be displayed on a standard emergency servicesinterface complying with Section 18.11 .


Elevator system annunciators already provide some of these elements so repeating the information is duplicative and unnecessary. The revised wording would make it permissive to provide this information on the fire alarm system.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: Elevator system annunciators already provide some of these elements so repeating the information isduplicative and unnecessary. The revised wording would make it permissive to provide this information onthe fire alarm system. Changes were also made to provide consistency of terminology with the requirementsin ASME A17.1.

*


189 of 365 9/22/2014 2:48 PM

Public Comment No. 110-NFPA 72-2014 [ Section No. 21.5 [Excluding any Sub-Sections] ]

Where one or more elevators are specifically designated and marked as fire service access elevators, the conditionsspecified in 21.5.1 for the elevators, associated lobbies, and machine rooms, control rooms, machinary spaces, orcontrol spaces, shall be continuously monitored at the fire commend center, and displayed on the elvatormanagement system or on the building fire alarm system's annunciator (s), during any such use.


The FSAE associated conditions described in this section should include ALL the elevator's associated spaces and not just machine rooms.These conditions should be monitored and displayed at the fire commend center (FCC) and be availed for responding fire fighters.Some of these conditions, such as the elevator location within the hoistway, elevator power, etc. are typically monitored and displayed on the Elevator monitoring panel located on the FCC and there is no need to include these conditions on the FA system. However, presence of smoke and continuous heat detection monitoring cannot be done by the elevator management system and should be conducted by the FA system via the main FACU or a separate FSAE dedicated FACU located in the FCC. These conditions should be clearly displayed on the FA system LED/Graphic annunciator required to be in the FCC or on a separate FSAE annunciator located in the FCC.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:





190 of 365 9/22/2014 2:48 PM


21.5.1


(1) Availability of main and emergency power to operate the elevator(s), elevator controller(s), and machine room,control room, machinery space, or control space ventilation (if provided) ventilation

(2)

(3) Temperature and presence of smoke in associated elevator (s) lobbies and machine room (if provided) ,control room, machinery space, or control space


Add FSAE associated locations such as control rooms, machinery spaces and control spaces to be consistent with other sections in chapter 21.

Related Item






Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:






191 of 365 9/22/2014 2:48 PM


21.5.2

The conditions shall be displayed on a standard emergency services interface complying with Section 18.11 .


There is currently NO "Standard Emergency Service Interface complying with Section 18.11" - This is very confusing and should be removed.The necessary FSAE conditions required to be monitored per my PC 110 and 112 could be monitored at the FCC via the elevator system (Elevator monitoring panel) and Via the building FA system and associated LED/Graphic annunciator required to be provided in the FCC

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: There is currently a requirement for a standard emergency services interface in 18.11 but therequirements are generic.


192 of 365 9/22/2014 2:48 PM



193 of 365 9/22/2014 2:48 PM

21.6

* Occupant Evacuation Elevators.

21.6.1

Elevator Status.

Where one or more elevators are specifically designated and marked for use by occupants for evacuation duringfires, they shall comply with all of the provisions of Sections 21.5 and 21.6 .

21.6.2

Elevator

Occupant Evacuation Operation (OEO).

Outputs from the fire alarm system to the elevator controller(s) shall be provided to implement elevator occupantevacuation operation in accordance with Section 2.27 of ASME A17.1/CSA B44 (2013), Safety Code forElevators and Escalators , as required in

21.6.2.1

and

through 21.6.2.

2

7 .

21.6.2.1

Partial Evacuation.

Where an elevator or group of elevators is designated for use by occupants for evacuation, the provisions of

Applicability.

21.6.2.1.1

through

Occupant Evacuation Operation shall function only prior to manual or automatic initiation of Phase I EmergencyRecall Operation.

21.6.2.1.

4 shall apply for partial evacuation

2 Occupant Evacuation Operation shall not be permitted when the automatic alarm initiating device is actuated onthe elevator discharge level.

21.6.2.2 Initiation. Where elevators are designated for use by occupants for evacuation, Occupant EvacuationOperation shall be initiated by actuation of any automatic fire alarm initiating device except those used to initiateelevator Phase I Emergency Recall Operation or by manual means from the fire command center .

21.6.2.

1

2 .1

Initiation.

Output signal(s) shall be provided from the fire alarm system to the elevator system controller(s) to initiateelevator occupant evacuation operation upon automatic or manual detection of a fire on a specific floor or floors asa result of either one or both of

the following:

21.6.2.2.2 and 21.6.2.2.3

21.6.2.2.2 Activation of any automatic fire alarm initiating device in the building, other than an initiating deviceused for elevator Phase I Emergency Recall Operation in accordance with 21.3.

15

14

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

21.6.2.

1.2


194 of 365 9/22/2014 2:48 PM

3 *

Floor Identification.

(A)

The output signal(s) shall identify each floor

to be evacuated

with an active alarm .

(B)

The identified floors shall

be a contiguous block of floors including

include the following:

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

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

(3) Floors identified by manual means from the fire command center.

(C) For the purpose of determining a block of floors as identified in ASME A17.1, the following shall be used:

(1) Two floors above the highest floor identified

by

in 21.6.2.

1.2

3 (B) (1) through 21.6.2.

1.2

3 (B) (3)

.

(2) Two floors below the lowest floor identified

by

in 21.6.2.

1.2

3 (B) (1) through 21.6.2.

1.2

3 (B) (3)

.

(

C

D )

The identified floors shall be displayed on the building fire alarm system annunciator at the fire command centeror on a standard emergency services interface

along with the other elevator status information required by 21.6.1 .

in accordance with 18.11.

21.6.2.

1.3

4 Manual Floor Selection.

(A)


195 of 365 9/22/2014 2:48 PM

A means shall be provided at the fire command center to allow the manual selection of floors.

(B)

The floors shall be selected on the basis of information received from authorized or emergency personnel.

21.6.2.

1.4

5 *

Occupant Notification.

The in-building fire emergency voice/alarm communications system shall transmit coordinated messagesthroughout the building.

(A)

Automatic voice evacuation messages shall be transmitted to the floors identified in 21.6.2.

1.2

3 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 to inform occupants ofevacuation status and shall include an indication that elevator service is not available.

(C) *

Automatic voice messages shall be transmitted to the floors identified in 21.6.2.

1.2

3 to indicate that elevator service is not available when all elevators have been recalled on Phase I EmergencyRecall Operation.

(D)

All automatic voice messages shall be coordinated with the text displays provided separately by the elevatormanagement system

During Occupant Evacuation Operation, messages at the elevator discharge level shall indicate that elevators arededicated to evacuation use only .

21.6.2.

2

6 Total Evacuation.

Where an elevator or group of elevators is designated for use by occupants for evacuation, the provisions of21.6.2.

2

6 .1 through 21.6.2.

2

6 .3 shall apply for total evacuation.

21.6.2.

2

6 .1

Output(s) to signal elevator occupant evacuation operation for total evacuation shall be manually activated fromthe fire command center by a means labeled “ELEVATOR TOTAL BUILDING EVACUATION.”


196 of 365 9/22/2014 2:48 PM

21.6.2.

2

6 .2

The output

Output (s) to the elevator system shall identify that all floors are to be evacuated.

21.6.2.

2

6 .3

The in-building fire emergency voice/alarm communications system shall transmit an evacuation messagethroughout the building to indicate the need to evacuate.

21.6.2.7* Termination of Occupant Evacuation Operation.

21.6.2.7.1 Any time that an alarm is actuated on the elevator discharge level, Occupant Evacuation Operationshall be terminated.

21.6.2.7.2 When elevator Phase I Emergency Recall Operation has been initiated either by automatic or manualmeans, Occupant Evacuation Operation shall be terminated.

21.6.2.7.3 Occupant Evacuation Operation shall be terminated upon reset of the fire alarm system



Proposed_New_Wording_for_Section_21.6.docxProposed New Wording for Section 21.6 including Annex Material


New wording correlates material released in ASME A17.1 Elevator and Escalator Safety Code 2013 edition.



Public Comment No. 200-NFPA 72-2014 [Sections A.21.6.2.1.1(2), A.21.6.2.1.2, A.21.6.2.1.4,A.21....]

Related Item

Committee Input No. 160-NFPA 72-2013 [Section No. 21.6.1]




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected but held

Resolution: The proposed changes introduce a concept that has not had public review by being included in a relatedInput or First Revision.


197 of 365 9/22/2014 2:48 PM

Proposed New Wording for Section 21.6

21.6* Occupant Evacuation Elevators.

21.6.1 Elevator Status. Where one or more elevators are specifically designated and marked for use by

occupants for evacuation during fires, they shall comply with all of the provisions of Sections 21.5 and 21.6.

21.6.2 Occupant Evacuation Operation (OEO). Outputs from the fire alarm system to the elevator

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

Section 2.27 of ASME A17.1/CSA B44 (2013), Safety Code for Elevators and Escalators, as required in

21.6.2.1 through 21.6.2.7.

21.6.2.1 Applicability.

21.6.2.1.1 Occupant Evacuation Operation shall function only prior to manual or automatic initiation of

Phase I Emergency Recall Operation.

21.6.2.1.2 Occupant Evacuation Operation shall not be permitted when the automatic alarm initiating device

is actuated on the elevator discharge level.

21.6.2.2 Initiation. Where elevators are designated for use by occupants for evacuation, Occupant

Evacuation Operation shall be initiated by actuation of any automatic fire alarm initiating device except those

used to initiate elevator Phase I Emergency Recall Operation or by manual means from the fire command

center.

21.6.2.2.1 Output signal(s) shall be provided from the fire alarm system to the elevator system controller(s)

to initiate elevator occupant evacuation operation upon automatic or manual detection of a fire on a specific

floor or floors as a result of either one or both of 21.6.2.2.2 and 21.6.2.2.3

21.6.2.2.2 Activation of any automatic fire alarm initiating device in the building, other than an initiating

device used for elevator Phase I Emergency Recall Operation in accordance with 21.3.14

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

21.6.2.3* Floor Identification.

(A) The output signal(s) shall identify each floor with an active alarm.

(B) The identified floors shall include the following:




(C) For the purpose of determining a block of floors as identified in ASME A17.1, the following shall be used:

(1) Two floors above the highest floor identified in 21.6.2.3(B)(1) through 21.6.2.3(B)(3)

(2) Two floors below the lowest floor identified in 21.6.2.3(B)(1) through 21.6.2.3(B)(3)

(D) The identified floors shall be displayed on the building fire alarm system annunciator at the fire command

center or on a standard emergency services interface in accordance with 18.11.

21.6.2.4 Manual Floor Selection.

(A) A means shall be provided at the fire command center to allow the manual selection of floors.

(B) The floors shall be selected on the basis of information received from authorized or emergency

personnel.

21.6.2.5* Occupant Notification. The in-building fire emergency voice/alarm communications system shall

transmit coordinated messages throughout the building.

(A) Automatic voice evacuation messages shall be transmitted to the floors identified in 21.6.2.3 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 to inform occupants of

evacuation status and shall include an indication that elevator service is not available.

(C)* Automatic voice messages shall be transmitted to the floors identified in 21.6.2.3 to indicate that

elevator service is not available when all elevators have been recalled on Phase I Emergency Recall

Operation.

(D) During Occupant Evacuation Operation, messages at the elevator discharge level shall indicate that

elevators are dedicated to evacuation use only.

21.6.2.6 Total Evacuation. Where an elevator or group of elevators is designated for use by occupants for

evacuation, the provisions of 21.6.2.6.1 through 21.6.2.6.3 shall apply for total evacuation.

21.6.2.6.1 Output(s) to signal elevator occupant evacuation operation for total evacuation shall be manually

activated from the fire command center by a means labeled “ELEVATOR TOTAL BUILDING EVACUATION.”

21.6.2.6.2 Output(s) to the elevator system shall identify that all floors are to be evacuated.

21.6.2.6.3 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.7* Termination of Occupant Evacuation Operation.

21.6.2.7.1 Any time that an alarm is actuated on the elevator discharge level, Occupant Evacuation Operation

shall be terminated.

21.6.2.7.2 When elevator Phase I Emergency Recall Operation has been initiated either by automatic or

manual means, Occupant Evacuation Operation shall be terminated.

21.6.2.7.3 Occupant Evacuation Operation shall be terminated upon reset of the fire alarm system

Annex Material

A.21.6 Occupant evacuation elevators will be provided for a relatively limited number of buildings, mainly

high-rise buildings. It is highly recommended that those involved with design and installation of these

systems become familiar with available information such as ASME A17.1, Section 2.27 and its non-mandatory

Appendix V “Building Features for Occupant Evacuation Operation”. It will be imperative that a great amount

of coordination be done between elevator and fire alarm system designers and installation contractors.

A.21.6.2.2.3 The manual means is intended in lieu of automatic initiating devices that could be impaired or

out of service and would otherwise have actuated to provide automatic initiation in accordance with

21.6.2.2.2. Manual fire alarm boxes location throughout the building 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.

A.21.6.2.3 The fire alarm system uses the floor identification to automatically establish a contiguous block of

floors for voice messaging purposes. The elevator system also uses the floor identification to determine the

contiguous block of floors to be evacuated. So, that block would be the floor of alarm plus two floors above

and two floors below the floor of alarm for a total of 5 floors. The established block of floors 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. Coordination needs to be provided between the fire

alarm system installer and the elevator system installer.

A.21.6.2.5 Messages need to be coordinated with the operation of the elevators so that occupants

understand what to expect and how to react. Additional visual information will be provided in each elevator

lobby by the elevator management system to further inform occupants of the status of the elevators. It is

especially important to address additional alarm actuation(s) and the impact that has on expanding the block

of floors and the corresponding messages that have to adjust to the change.

Sample voice message content to be added to normal message (to be coordinated with dynamic signage

provided by the elevator contractor):

Condition: Specific block of floors being evacuated

“Elevators and stairs are available for evacuation”

Condition: Floors not being evacuated

“Elevators not available, they are temporarily dedicated to other floors”

Condition: On the elevator discharge level

“Elevators dedicated to evacuation. Do not enter elevator”

For further information on voice messaging strategies refer to “Incorporating Emergency Messaging

Guidance into Practice”

A.21.6.2.5(C) This new message will require a signal from the elevator management system to the fire alarm

system.

A.21.6.2.7 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. In this case, the fire

alarm system needs to know that it must cancel OEO programming. 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).


21.6.2 Elevator Occupant Evacuation Operation (OEO).

Outputs from the fire alarm system to the elevator controller(s) shall be provided to implement elevator occupantevacuation operation in accordance with Section 2.27 of ASME A17.1/CSA B44 (2013), Safety Code for Elevatorsand Escalators, as required in 21.6.2.1 and 21.6.2.2.

21.6.2.1 Partial Evacuation.

Where an elevator or group of elevators is designated for use by occupants for evacuation, the provisions of21.6.2.1.1 through 21.6.2.1.4 shall apply for partial evacuation.

21.6.2.1.1 Initiation.

Output signal(s) shall be provided to initiate elevator occupant evacuation operation upon automatic or manualdetection of a fire on a specific floor or floors as a result of either or both of the following:

(1) Activation of any automatic fire alarm initiating device in the building, other than an initiating device used forelevator Phase I Emergency Recall Operation in accordance with 21.3.15

(2)

21.6.2.1.2 * Floor Identification.

(A)

The output signal(s) shall identify each floor to be evacuated.

(B)

The identified floors shall be a contiguous block of floors including the following:




(4) Two floors above the highest floor identified by 21.6.2.1.2(B) (1) through 21.6.2.1.2(B) (3).

(5) Two floors below the lowest floor identified by 21.6.2.1.2(B) (1) through 21.6.2.1.2(B) (3).

(C)

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

21.6.2.1.3 Manual Floor Selection.

(A)

A means shall be provided at the fire command center to allow the manual selection of floors.

(B)

The floors shall be selected on the basis of information from authorized or emergency personnel.

21.6.2.1.4 * Occupant Notification.

The in-building fire emergency voice/alarm communications system shall transmit coordinated messagesthroughout the building.

(A)

Automatic voice evacuation messages shall be transmitted to the floors identified in 21.6.2.1.2 to indicate the needto evacuate and that elevator service is available.

(B)

Automatic voice messages shall be transmitted to the floors not being evacuated to inform occupants of evacuationstatus and shall include an indication that elevator service is not available.

(C) *

Automatic voice messages shall be transmitted to the floors identified in 21.6.2.1.2 to indicate that elevator serviceis not available when all elevators have been recalled on Phase I Emergency Recall Operation.

(D)

All automatic voice messages shall be coordinated with the text displays provided separately by the elevatormanagement system.

21.6.2.2 Total Evacuation.

Where an elevator or group of elevators is designated for use by occupants for evacuation, the provisions of21.6.2.2.1 through 21.6.2.2.3 shall apply for total evacuation.

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


198 of 365 9/22/2014 2:48 PM

21.6.2.2.1

Output(s) to signal elevator occupant evacuation operation for total evacuation shall be manually activated from thefire command center by a means labeled “ELEVATOR TOTAL BUILDING EVACUATION.”

21.6.2.2.2

The output(s) shall identify that all floors are to be evacuated.

21.6.2.2.3

The in-building fire emergency voice/alarm communications system shall transmit an evacuation messagethroughout the building to indicate the need to evacuate.


The ASME A17.1 term is "Occupant Evacuation Operation", therefore that's how the section title should read.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement


Resolution: The proposed change is actually new material but is also addressed in PC 199 which has been held.


199 of 365 9/22/2014 2:48 PM


21.6.2.1.1 Initiation.

Output signal(s) shall be provided to initiate elevator occupant evacuation operation upon automatic or manualdetection of a fire fire conditions on a specific floor or floors as a result of either or both of the following:

(1) Activation of any automatic fire alarm initiating device in the building, other than an initiating device used forelevator Phase I Emergency Recall Operation in accordance with 21.3.15

(2)


The intent of this change is to specify that in no case occupant evacuation operation should start upon manual activation on a floor via a manual fire alarm box.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected but held


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


200 of 365 9/22/2014 2:48 PM

Public Comment No. 115-NFPA 72-2014 [ Section No. 21.6.2.1.2(C) ]

(C)

The identified floors shall be displayed on a standard emergency services interface along with the displayed at thefire command center with the other elevator status information required by 21.6.1.


There is no standard emergency service interface yet. The required information could be displayed on the elevator monitoring panel and/or the building FA system LED/Graphic annunciator located in the FCC

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected but held



201 of 365 9/22/2014 2:48 PM


23.1.2

The requirements of Chapters 7, 10, 12, 17, 18, 21, 24, and 26 shall also apply, unless they are in conflict with thischapter.



The correlating committee makes reference to 23.1.2 and the phrase ", unless they are in conflict with this chapter." Requirements should not conflict. Where deviations from the requirements of other chapters are warranted they should be identified and addressed through appropriate allowances in the code language. The correlating committee directs the SIG-PRO committee to review the requirements in Chapter 23 with consideration to resolving any identified conflicts with other chapters. Where changes are made they should be done without introducing new material in the second draft phase. In addition the committee should consider rewording 23.1.2 to positive language. For example: The requirements of chapters x, y and z shall apply unless otherwise noted in this chapter.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement



Statement: The requirement has been modified to provide more positive language.


202 of 365 9/22/2014 2:48 PM


23.6.1 * SLC Zones

A single fault on a pathway connected to the addressable devices shall not cause the loss of the devices in morethan one zone.

23.6.1.1

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

23.6.1.2

For the purpose of this section, if a floor of the building is subdivided into multiple zones by fire or smoke barriersand the fire plan for the protected premises allows relocation of occupants from the zone of origin to another zoneon the same floor, each zone on the floor shall be considered a separate zone.

23.6.1.3 *

The requirements in 23.6.1 shall not apply to the following:

(1) Circuits between enclosures containing transponders and control units regardless of the number of initiatingdevices, notification appliances, or control relays that might be connected to those control units.

(2) Circuits connecting short-circuit fault isolation modules to enclosures containing transponders and control unitswhere the conductors are installed in metallic raceway or equivalently protected against mechanical injury andwhere the circuit does not exceed 3 ft (1 m) in length.

23.6.1.4

The loss of more than one zone shall be permitted on a documented performance-based design approach inaccordance with 7.3.7.4.

23.6.1.5 *

Performance-based designs submitted to the authority having jurisdiction for review and approval shall includedocumentation, in an approved format, of each performance objective and applicable scenario, together withtechnical substantiation used in establishing the proposed zone performance.


Titled the section to improve readability

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The revision is made for compliance with the manual of style. Also add new annex material as shown inthe attachment. The added annex material further clarifies the SLC zoning requirements.


203 of 365 9/22/2014 2:48 PM


A single fault on a pathway connected to the addressable devices shall not cause the loss of the devices in morethan one zone.


Zone as used in this section is ambiguous. Does the committee mean alarm zone or notification zone? A single intiiating device may be a zone. That would require that the SLC be Class X if serving more than one device. This is an excessive requirement. This is a design feature that should be driven by a risk analysis and not part of the minimum code requirements.

Related Item




Organization: Arup

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The term “zone” is not ambiguous in the section. Section 23.6.1.1 through 23.6.1.5 provide additionalinformation regarding what the intent of the term “zone” is. Additionally, 3.3.317 defines “zone” as “A definedarea within the protected premises. A zone can define an area from which a signal can be received, and areato which a signal can be sent, or an area from which a form of control can be executed.” There are devicesthat can be installed on an SLC that can perform these signals. The Task Group that developed the Inputstatement and the Committee that voted intended the term “zone” to apply to the SLC in this instance. Inaddition there is no requirement that a SLC must be configured as Class X. The SLC can be configured asClass A, B, N, X, or a hybrid of Classes which is up to the designer. Furthermore the SLC code requirement isno more restrictive or excessive than what has been required for IDCs or NACs. The SLC requirement isintended to restore an acceptable, minimal level of circuit survivability by preventing a single short fromcausing a catastrophic failure of the entire SLC that would disable all of, or a major portion of, a systemincluding all initiating, signaling, and emergency control functions.


204 of 365 9/22/2014 2:48 PM


A single fault on a pathway connected to the addressable devices shall not cause the loss of the devices in morethan one zone 50 addressable devices .


Return to the 2013 Edition text. There are several potential problems with this change. 1. The use of English is not clear. It appears that the “than” should not be struck out.2. The Technical Committee has not provided technical substantiation as to why this change is required. This would include documentation of known fire losses that have occurred when isolation devices installed to this level were not in place. With this edition, an isolation module would be required even if there is a single device within a zone. For a small to medium size building, these seems to be excessive. The designer of a system, after a risk analysis of the protected premises may still elect to include isolation devices in this manner, or even provide a Style 7 Circuit.

Related Item




Organization: Automatic Fire Alarm Association

Affilliation: Automatic Fire Alarm Association

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The term “than” has not been struck out. The section is clear as written. The Task Group and Committeeidentified that the “50 addressable devices” was much more restrictive than the current language describingSLC Zones. The current language provides designers with several options rather than one single option, i.e.,not being permitted to lose more than 50 addressable devices. Gathering information on specific fire losseswhere a shorted SLC contributed to a fire loss is difficult at best, however there are documented cases wherethe SLC has failed from fire damage prior to the activation of an alarm. More often the case is that a an SLCis shorted due to a single sheetrock screw, roofing screw, damaged wire, a single ground developing to aground short between conductors, or cut or damaged wire due to renovations or modifications to the building.Fire alarm servicing companies are extremely familiar with SLC failures due to shorts and can substantiatethat this type of failure occurs regularly. It is also common that a catastrophic SLC failure can be annunciatedas a single system fault masking the severity of the failure.


205 of 365 9/22/2014 2:48 PM


23.6.2 Class N Devices.

No area or zone shall be serviced solely by a single device where Class N pathways are deployed, such that asingle device failure would render an area or zone incapable of initiating input signals or receiving output 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.1

Where a device as referenced by 23.6.2 is serviced by only a single pathway, it shall terminate that pathway withno capability to connect additional endpoint devices to the pathway.

23.6.2. 2

Class N pathways shall be required to use Shared Pathway Level

3

as specified in Section 12.5.4 .

23.6.2.3

A single fault on a Class N pathway connected to the addressable devices shall not cause the loss of more thanone addressable device.


Titled the section to improve readability. Also moving the content of 23.6.2.2 to a new proposed section 23.6.3 so that a complex exception to the Shared Pathway Level 3 proposal can be presented.The proposal is the recommendation by the Correlating Committee Task Group members thatwas comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of thecommittees.Wayne MooreA.J. CapowskiJoe L. CollinsDan HoronVic HummMichael PallettCharles PughRobert SchifilitiAviv SiegelLarry ShudakBob ElliottPaul CrowleyJeff SilveiraJeff KnightAndrew Berezowski




Related Item





Street Address:

City:

State:

Zip:


206 of 365 9/22/2014 2:48 PM


Committee Statement

CommitteeAction:


Resolution: See SR 29 and SR 42

Statement: The revision added a title the section to improve readability. Also moving the content of 23.6.2.2 to a newproposed section 23.6.3 so that a complex exception to the Shared Pathway Level 3 proposal can bepresented. See SR 42 for section 23.6.3.


207 of 365 9/22/2014 2:48 PM



208 of 365 9/22/2014 2:48 PM

23.6.3 Class N Shared Pathways.

Class N pathways shall be required to use Shared Pathway Level 3 as specified in Section 12.5.4 except aspermitted by 23.6.3.1 through 23.6.3.7.

23.6.3.1

Shared pathways level 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.2.3 and whenapproved by an AHJ in consideration of the analysis, maintenance, and deployment plans.

23.6.3.1.1

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.2 Deployment Plan

23.6.3.2.1

All equipment connected to shared pathways, shall be documented in the deployment plan. Thedocumentation shall include manufacturer, model, listings, and intended purpose and reason for inclusionon the shared network. The deployment plan shall identify how and where each piece of equipment isconnected.

23.6.3.2.2

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

23.6.3.3 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.4 Management Organization

23.6.3.4.1

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

(a) contain members appropriately certified by each manufacturer of the equipment and devices deployedon shared pathways, to maintain such a network

(b) service and maintain all shared Class N pathways

(c) maintain the deployment and shared pathways plan for the lifetime of the shared pathways

23.6.3.4.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 lifeand property.

23.6.3.5 Analysis

23.6.3.5.1

The analysis shall determine and document communications capability as follows:

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

(b) the total bandwidth provided by the network,

(c) document future bandwidth requirements,

(d) the method of providing and maintaining the prioritization of life safety traffic over non-life safetytraffic.

23.6.3.5.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,

(c) secondary power capacities provided to maintain all life safety equipment with minimum operationalcapacity in accordance with 10.6.7.2.1(2),

(d) methods to disengage any non-life safety equipment in the event of emergency operation if required tosupport the minimum operational capacity requirements.


209 of 365 9/22/2014 2:48 PM

23.6.3.6 Maintenance Plan

The maintenance plan shall identify policy and procedures to monitor, maintain, test and control change ofthe shared pathways. Written procedures shall be presented in maintenance plans to govern:

(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 notices of impairment, and contingency plans for affectedsystems

(4) Upgrade procedures

(5) change control procedures, with consideration given to require an updated risk analysis if necessary

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

(7) maintenance and testing plans to ensure the minimum operational capacity with respect to secondarypower is maintained,

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

23.6.3.7 Other Risks

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


With respect to restricting Class N pathways to strictly Level 3 Shared Pathways, members of the TC felt that it may be counterproductive to provide zero possibility for qualified customers to share other high priority systems on this network. It may create a perception of obsolescence out of the gate to provide no path forward into the future where more and more customers may be qualified to manage integrated life safety networks.

There are other systems that are involved in live safety and security that can (where appropriate) utilize modern networks and can benefit from shared pathways including nurse call systems, access control systems, camera systems, and of course Mass Notification Systems. Less important may be the benefit of the aggregation of port costs, but rather real benefits may be realized in purposeful interoperation and/or common management for those life safety networks.

The management of networks will continue to develop as a discipline. There is already a growing trend to outsource network management, just as has happened with central stations for both fire and security. These companies can and will develop strong competencies with the real time management of life safety qualified networks. Companies will emerge that will be every bit as capable as the military, airport authorities, and the federal government in this regard, and able to back that up with qualifications.

We don’t propose that it is the role of NFPA72 to establish those qualifications. But it is important that NFPA72 should recognize that it is at least possible to share a life safety network between Fire, MNS, Access Control, Security, and Camera’s and provide an opening in this regard.

However, if NFPA72 does not present qualifications for organizations to use other classes of shared pathways, then we need to rely on others to evaluate suitability on a case by case basis and on a performance basis. This is the same situation that chapter 24 resolved by introducing the concept of a Risk Analysis for MNS.

By introducing a minimum level of documentation of analysis, maintenance plans, and deployment plans, the presentation of justification to an AHJ is at least possible and consideration can be given to shared pathway class 1 and 2 being allowed with a class C network.The proposal is the recommendation by the Correlating Committee Task Group members thatwas comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of thecommittees.Wayne MooreA.J. CapowskiJoe L. CollinsDan HoronVic HummMichael PallettCharles PughRobert SchifilitiAviv Siegel


210 of 365 9/22/2014 2:48 PM

Larry ShudakBob ElliottPaul CrowleyJeff SilveiraJeff KnightAndrew Berezowski




Public Comment No. 136-NFPA 72-2014 [New Section after 23.8.2.6.2]


Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: With respect to restricting Class N pathways to strictly Level 3 Shared Pathways, members of the TC felt thatit would be counterproductive to provide zero possibility for qualified customers to share other high prioritysystems on this network. It may create a perception of obsolescence out of the gate to provide no pathforward into the future where more and more customers may be qualified to manage integrated life safetynetworks. There are other systems that are involved in life safety and security that can (where appropriate)utilize modern networks and can benefit from shared pathways including nurse call systems, access controlsystems, camera systems, and of course Mass Notification Systems. Less important may be the benefit ofthe aggregation of port costs, but rather real benefits may be realized in purposeful inter-operation and/orcommon management for those life safety networks.

Annex 23.6.3.6(c) was added to further explain system impairment requirements.


211 of 365 9/22/2014 2:48 PM

Public Comment No. 136-NFPA 72-2014 [ New Section after 23.8.2.6.2 ]

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


Section 23.8.2.6 deals with fire alarm control units and the sharing of signaling line circuits with other premise operating systems. Since this is closely related to shared pathways, should the SLC implementation be class C it was the intention to draw the reader to the related material in the proposed section 23.6.3.The proposal is the recommendation by the Correlating Committee Task Group members thatwas comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of thecommittees.Wayne MooreA.J. CapowskiJoe L. CollinsDan HoronVic HummMichael PallettCharles PughRobert SchifilitiAviv SiegelLarry ShudakBob ElliottPaul CrowleyJeff SilveiraJeff KnightAndrew Berezowski




Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted


Statement: Section 23.8.2.6 deals with fire alarm control units and the sharing of signaling line circuits with otherpremise operating systems. Since this is closely related to shared pathways, should the SLCimplementation be class C it was the intention to draw the reader to the related material in the proposedsection 23.6.3.


212 of 365 9/22/2014 2:48 PM


23.8.5.9.1

Where fire pumps are required to be monitored and a building fire alarm system is installed, a pump running signalshall be permitted to be a supervisory or alarm signal be a supervisory signal .


This amendment is made to clarify the requirement for monitoring of the fire pump run signal. NFPA 72 has permissive language that does not provide clear direction as to what type of signal is required. The intent of this amendment is to make all of the fire pump signals supervisory. If the fire pump run is an alarm signal than if a water flow switch signal is acitvated than two signals will be transmited as an alarm signal to the monitoring station causing confusion to responders. A fire pump run signal with no water lfow is not an emergency response and the building owner should be notified to check the pump.

Related Item



Submitter Full Name: Kelly Nicolello

Organization: Western Regional Fire Code Dev

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The code is clear. It permits “fire pump running” signals annunciated at the fire alarm system control unit tobe reported as and annunciated as supervisory signals or alarm signals. The committee intended on thelanguage as such because there are AHJs that require “fire pump running” to report as an alarm signal.


213 of 365 9/22/2014 2:48 PM


23.16.2 * Power Supplies.

Primary battery(s) (dry cell) shall be permitted to be used as the sole power source for devices incorporating alow-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 the systemcontrol unit.

(2) The battery(s) shall be capable of operating the low-power radio transmitter/transceiver and its associateddevice 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 of troublesignal operation followed by the signaling of a single non-trouble response. The low battery signal shall bedistinctive from alarm, supervisory, tamper, and trouble signals; shall visibly identify the affected low-powerradio transmitter/transceiver; and, when silenced, shall automatically re-sound at least once every 4 hours.

(4) Catastrophic (open or short) battery failure shall cause a trouble signal identifying the affected low-power radiotransmitter/transceiver at the system control unit. When silenced, the trouble signal shall automaticallyre-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 affect any otherlow-power radio transmitter/transceiver.


See associated public comment 224 adding explanitory material to this paragraph.



Public Comment No. 224-NFPA 72-2014 [New Section after A.23.16] Proposed explanatory material

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: Add the attached annex material for A.23.16.2. The annex material would clarify that the intent of thisrequirement is not to prohibit the use of battery operated technology in combination devices but rather tolimit the regional impact from the failure of a battery.


214 of 365 9/22/2014 2:48 PM


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 or until confirmation that thereceiver/transceiver system control unit has received the alarm signal .


This requirement should be made consistent with 23.16.5 (4). There is no need to repeatedly transmit an alarm signal if it is known to have been received by the receiver/transceiver system control unit.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement


Resolution: Section 23.16.3.2 addresses input signals and 23.16.3.5(4) addresses output signals.


215 of 365 9/22/2014 2:48 PM


23.16.3.4

The maximum allowable response delay from activation of an initiating device to receipt and display by the systemcontrol unit shall occur within 10 seconds. Response time shall be in accordance with 10.12.1


Alarm signal response time is fundamentally addressed by Section 10.12.1

Related Item





Street Address:

City:

State:

Zip:


Committee Statement



Statement: Alarm signal response time is fundamentally addressed by Section 10.12.1


216 of 365 9/22/2014 2:48 PM


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 signal within200 seconds at the system control unit that individually identifies the affected device .


The affected device should be identified so that the affected portion of the system is known and so that the cause of the problem can be more quickly identified and addressed. This would be consistent with the 23.16.4.5 requirement to individually identify the removal of a device.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted


Statement: The affected device should be identified so that the affected portion of the system is known and so that thecause of the problem can be more quickly identified and addressed. This would be consistent with the23.16.4.5 requirement to individually identify the removal of a device.


217 of 365 9/22/2014 2:48 PM


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 signal within200 seconds 12 hours at the system control unit.



Linear_PublicInputForm_A.pdf PI Form

Public_Comments_C.pdf Revised version 5/8/14


Conclusion:The current UL985/217A fire alarm standards for residential applications are perfectly adequate to provide a reasonable level of protection at a reasonable cost. If the new NFPA 72-2013 updates to UL 985 system requirements go into effect, then there will be fewer fire protection alarms sold per installation with a more complicated / expensive system and ultimately less reliable central station reporting.

Current Text:NFPA 72-2013 Standard States:23.16.4 Monitoring for Integrity:23.16.4.2 The occurrence of any single fault that disables transmission between any low-power radio transmitter and the receiver/fire alarm control unit shall cause a latching trouble signal within 200 seconds.Exception: Until the expiration date for the exception of June 30, 2013, the time period for a low-power radio transmitter with only a single, connected alarm-initiating device shall be permitted to be increased to four times the minimum time interval permitted for a 1-second transmission up to the following:(1) 4 hours maximum for a transmitter seeing a single initiating device(2) 4 hours maximum for a retransmission device (repeater), where disabling of the repeater or its transmission does not prevent the receipt of signals to the receiver/fire alarm control unit from any initiating device transmitter.

23.16.4.5 Removal of a low-power radio transmitter from its installed location shall cause immediate transmission of a distinctive supervisory signal that indicates its removal and individually identifies the affected device.

Discussion on the Technical Issues:200 Second Status Business Requirements vs. Residential Requirements: 1. The 200 second inoperative transmitter requirement comes from the commercial fire and burglary requirements. In a commercial environment there are always concerns about purposeful tampering and/or damage to transmitters because of arson and/or burglary.2. In a residential environment, purposeful tampering is rarely an issue. From reading NFPA reports on residential fires, the most commonly found reason for deaths and injuries were the total lack of fire alarms or existing fire alarms where the batteries had been removed and never replaced.3. Current NFPA requirements for replacement stand alone fire alarms do not require tamper alarms or system monitoring (i.e. cross connects). There is some effort in work to require wired (i.e. cross connected) AC powered smoke alarms in new construction but this has not been implemented nationwide.4. Stand alone residential smoke alarms that include an integral audible annunciator and low power RF transmitter should be considered a smoke alarm accessory, rather than as a fire warning system. They will annunciate fire locally just as a stand alone smoke alarm would. They have an enhancement available with the RF transmitter that a central alarm console will provide a summary alarm and can wake the occupants during the night even if the local smoke alarm is not audible to the sleepers.5. Under the current NFPA-72 2013 requirements, if a smoke alarm were to have a fault at 9 PM, then every 200 seconds all night long the occupants would have to reset the low battery or missing status indicator until the fault was corrected. This is a guarantee that the console and smoke alarm will be disconnected or disabled. Most probably the occupants will demand that the offending components be permanently removed. For a residential application this would serve no good purpose nor does it make good sense.Battery Life / RF Clash Collisions:1. Currently most systems utilize a 1.1 hour status transmission in accordance with previous FCC Rules Part 15.231 or 15.249 requirements. This is done as a balance between good battery life, system reliability and not causing excessive


218 of 365 9/22/2014 2:48 PM

clashes or collisions to the RF spectrum.2. UL217A/985 requirements have implemented a number of mathematical statistical calculations and practical RF tests to confirm that the systems will have a high probability of receiving correct messages even when used with a maximum number of system transmitters. UL has also required a smoke alarm nominal battery life of greater than 1 year with many photoelectric smoke alarms having a theoretical life of about 3 years.3. If instead we now recalculate the system with a 200 second RF transmission scheme the transmitters will transmit about 20 times more often and the probability of clash / collisions will be much higher. Granted entirely new compressed RF formats and transmission schemes may be designed, but their reliability in the field has not been documented. All new compatible burglary, arm/disarm, flood, high/low ambient temperatures sensors, etc. will be required to complete the system. This is a much greater burden than just designing a new smoke alarm transmitter. It involves a compete redesign from the ground up for the console’s wireless technology.

Central Stations Will Be Inundated with Meaningless Warning Messages:1. Wireless smoke alarms now include a low battery and loss of status function when communicating to the alarm console.2. Currently a residential alarm system is allowed up to 12 hours to delay the low battery or loss of status message from a given RF fire alarm transmitter.3. Under normal circumstances the fire alarm transmitter has a low battery detector that will give a minimum of 7 days warning before the unit’s battery will cease to function.4. If the homeowner has a “chirping” low battery problem and removes the unit from the system, then every 200 seconds a “loss of status” message will be annunciated at the console and sent to the central station.5. If for example, the homeowners are away on vacation and a smoke alarm goes into a low battery condition:a. The central station will receive a new low battery report every 200 seconds until the homeowners can be contacted and a replacement battery installed.b. If the homeowners cannot be contacted, then for a minimum of 1 week the central station will continue to receive the low battery reports until the unit goes dead. Then they will continue to receive “loss of status” message every 200 seconds forever.c. Conclusion: There will be little useful information transmitted to the central station compared to before. They will be overwhelmed with units in the field sending trouble signals.

Additional Expenses for a More Complicated System:1. A faster data rate, new frequency band and/or mesh network of relay stations all imply a higher and more complicated level of technology.2. The higher level of technology will of necessity involve a more complicated set up and a higher level of system understanding of the installation personnel.3. Customers are expecting smaller, less obtrusive and easy to understand operations.4. This requirement will push the technology into the opposite direction with more stations, more complicated individual alarms, coasting higher amounts of money and troubles not being easily understood when system problems do occur.5. While it may be possible to get the minimum 1 year batter life from a smoke (and eventually CO alarms) with a minimum of 20 times more status signals and 2-way communications the battery life will be significantly reduced.

More Expensive Smoke/CO Alarms = Fewer Sales = Less Complete Fire Protection.1. With more complicated and expensive fire alarm systems, more residential customers will opt out of a monitored fire reporting system.2. From comments in work at UL, I believe that this 200 second requirement will also eventually be required of CO alarms.3. Customers will have the option of installing a $9.95 stand alone 10 year battery life alarm from a home improvement store vs. a $75 (or more) monitored alarm. For the monitored alarm the battery will only last slightly more than 1 year.4. This requirement will hurt the residential alarm industry. It will result in a significantly reduced or no installed fire warning system in many residences.5. It will not appreciably increase effective fire alarm security and will actaully harm future installed alarm systems.

Related Item



Submitter Full Name: JOHN KUIVINEN

Organization: LINEAR LLC

Street Address:

City:

State:

Zip:



219 of 365 9/22/2014 2:48 PM

Committee Statement

CommitteeAction:

Rejected

Resolution: SIG-PRO: There is no substantiation or empirical data to show that 12 hour monitoring is equal to or morereliable than 200 second monitoring. SIG-HOU: The TC has dealt with this material in SR-48 which modifiesthe requirements in Chapter 29 which is a more appropriate place to address residential applications.


220 of 365 9/22/2014 2:48 PM


23.16.4.5

Removal of a low-power radio transmitter/transceiver from its installed location shall cause immediate transmissionof a distinctive trouble signal that indicates its removal and individually identifies the affected device.



Linear_PublicInputForm_A.pdf PC Form

Public_Comments_C.pdf Revised Version 5/8/14


Conclusion:The current UL985/217A fire alarm standards for residential applications are perfectly adequate to provide a reasonable level of protection at a reasonable cost. If the new NFPA 72-2013 updates to UL 985 system requirements go into effect, then there will be fewer fire protection alarms sold per installation with a more complicated / expensive system and ultimately less reliable central station reporting.

Current Text:NFPA 72-2013 Standard States:23.16.4 Monitoring for Integrity:23.16.4.2 The occurrence of any single fault that disables transmission between any low-power radio transmitter and the receiver/fire alarm control unit shall cause a latching trouble signal within 200 seconds.Exception: Until the expiration date for the exception of June 30, 2013, the time period for a low-power radio transmitter with only a single, connected alarm-initiating device shall be permitted to be increased to four times the minimum time interval permitted for a 1-second transmission up to the following:(1) 4 hours maximum for a transmitter seeing a single initiating device(2) 4 hours maximum for a retransmission device (repeater), where disabling of the repeater or its transmission does not prevent the receipt of signals to the receiver/fire alarm control unit from any initiating device transmitter.

23.16.4.5 Removal of a low-power radio transmitter from its installed location shall cause immediate transmission of a distinctive supervisory signal that indicates its removal and individually identifies the affected device.

Discussion on the Technical Issues:200 Second Status Business Requirements vs. Residential Requirements: 1. The 200 second inoperative transmitter requirement comes from the commercial fire and burglary requirements. In a commercial environment there are always concerns about purposeful tampering and/or damage to transmitters because of arson and/or burglary.2. In a residential environment, purposeful tampering is rarely an issue. From reading NFPA reports on residential fires, the most commonly found reason for deaths and injuries were the total lack of fire alarms or existing fire alarms where the batteries had been removed and never replaced.3. Current NFPA requirements for replacement stand alone fire alarms do not require tamper alarms or system monitoring (i.e. cross connects). There is some effort in work to require wired (i.e. cross connected) AC powered smoke alarms in new construction but this has not been implemented nationwide.4. Stand alone residential smoke alarms that include an integral audible annunciator and low power RF transmitter should be considered a smoke alarm accessory, rather than as a fire warning system. They will annunciate fire locally just as a stand alone smoke alarm would. They have an enhancement available with the RF transmitter that a central alarm console will provide a summary alarm and can wake the occupants during the night even if the local smoke alarm is not audible to the sleepers.5. Under the current NFPA-72 2013 requirements, if a smoke alarm were to have a fault at 9 PM, then every 200 seconds all night long the occupants would have to reset the low battery or missing status indicator until the fault was corrected. This is a guarantee that the console and smoke alarm will be disconnected or disabled. Most probably the occupants will demand that the offending components be permanently removed. For a residential application this would serve no good purpose nor does it make good sense.Battery Life / RF Clash Collisions:1. Currently most systems utilize a 1.1 hour status transmission in accordance with previous FCC Rules Part 15.231 or 15.249 requirements. This is done as a balance between good battery life, system reliability and not causing excessive clashes or collisions to the RF spectrum.


221 of 365 9/22/2014 2:48 PM

2. UL217A/985 requirements have implemented a number of mathematical statistical calculations and practical RF tests to confirm that the systems will have a high probability of receiving correct messages even when used with a maximum number of system transmitters. UL has also required a smoke alarm nominal battery life of greater than 1 year with many photoelectric smoke alarms having a theoretical life of about 3 years.3. If instead we now recalculate the system with a 200 second RF transmission scheme the transmitters will transmit about 20 times more often and the probability of clash / collisions will be much higher. Granted entirely new compressed RF formats and transmission schemes may be designed, but their reliability in the field has not been documented. All new compatible burglary, arm/disarm, flood, high/low ambient temperatures sensors, etc. will be required to complete the system. This is a much greater burden than just designing a new smoke alarm transmitter. It involves a compete redesign from the ground up for the console’s wireless technology.

Central Stations Will Be Inundated with Meaningless Warning Messages:1. Wireless smoke alarms now include a low battery and loss of status function when communicating to the alarm console.2. Currently a residential alarm system is allowed up to 12 hours to delay the low battery or loss of status message from a given RF fire alarm transmitter.3. Under normal circumstances the fire alarm transmitter has a low battery detector that will give a minimum of 7 days warning before the unit’s battery will cease to function.4. If the homeowner has a “chirping” low battery problem and removes the unit from the system, then every 200 seconds a “loss of status” message will be annunciated at the console and sent to the central station.5. If for example, the homeowners are away on vacation and a smoke alarm goes into a low battery condition:a. The central station will receive a new low battery report every 200 seconds until the homeowners can be contacted and a replacement battery installed.b. If the homeowners cannot be contacted, then for a minimum of 1 week the central station will continue to receive the low battery reports until the unit goes dead. Then they will continue to receive “loss of status” message every 200 seconds forever.c. Conclusion: There will be little useful information transmitted to the central station compared to before. They will be overwhelmed with units in the field sending trouble signals.

Additional Expenses for a More Complicated System:1. A faster data rate, new frequency band and/or mesh network of relay stations all imply a higher and more complicated level of technology.2. The higher level of technology will of necessity involve a more complicated set up and a higher level of system understanding of the installation personnel.3. Customers are expecting smaller, less obtrusive and easy to understand operations.4. This requirement will push the technology into the opposite direction with more stations, more complicated individual alarms, coasting higher amounts of money and troubles not being easily understood when system problems do occur.5. While it may be possible to get the minimum 1 year batter life from a smoke (and eventually CO alarms) with a minimum of 20 times more status signals and 2-way communications the battery life will be significantly reduced.

More Expensive Smoke/CO Alarms = Fewer Sales = Less Complete Fire Protection.1. With more complicated and expensive fire alarm systems, more residential customers will opt out of a monitored fire reporting system.2. From comments in work at UL, I believe that this 200 second requirement will also eventually be required of CO alarms.3. Customers will have the option of installing a $9.95 stand alone 10 year battery life alarm from a home improvement store vs. a $75 (or more) monitored alarm. For the monitored alarm the battery will only last slightly more than 1 year.4. This requirement will hurt the residential alarm industry. It will result in a significantly reduced or no installed fire warning system in many residences.5. It will not appreciably increase effective fire alarm security and will actaully harm future installed alarm systems.

Related Item



Submitter Full Name: JOHN KUIVINEN

Organization: LINEAR LLC

Street Address:

City:

State:

Zip:


Committee Statement


222 of 365 9/22/2014 2:48 PM

CommitteeAction:

Rejected

Resolution: SIG-PRO: The need to monitor the location of the device is critical to system operation. SIG-HOU The textis required to ensure the requirement is satisfied. Removal of a this text will lessen the degree of safety.The TC also refers the submitter to SR-48.


223 of 365 9/22/2014 2:48 PM

Public Comment No. 211-NFPA 72-2014 [ Sections 23.16.4.6, 23.16.4.7 ]

Sections 23.16.4.6, 23.16.4.7

23.16.4.6

Reception of any unwanted (interfering) transmission by a retransmission device or by the receiver system controlunit for a continuous period of 20 seconds or more shall cause an audible and visible trouble indication at thesystem control unit. This indication shall identify the specific trouble condition as an interfering signal.

23.16.4.7

The indication required by 23.16.4.6 shall identify the specific trouble condition as an interfering signal.


Deleted redundant text.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted


Statement: The second sentence in 23.16.4.6 is redundant to the statement in 23.16.4.7. Additionally, the Manual ofStyle does not permit two requirements in the same numbered item.


224 of 365 9/22/2014 2:48 PM


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 Chapter 10, Chapter 12, Chapter 23, or 23.16.4 shall apply.

(3) The maximum allowable response delay from activation of an initiating device to activation of required alarmfunctions shall be 10 seconds. Response time shall be in accordance with 10.12.1.

(4) Each transceiver/system control unit shall automatically repeat activated response signals associated with lifesafety events at intervals not exceeding 60 seconds or until confirmation that the output device has receivedthe alarm signal.

(5) The remote devices shall continue to operate (latch-in) until manually reset at the system control unit.


Alarm signal response time is fundamentally addressed by Section 10.12.1

Related Item





Street Address:

City:

State:

Zip:


Committee Statement



Statement: Alarm signal response time is fundamentally addressed by Section 10.12.1


225 of 365 9/22/2014 2:48 PM


24.1.3

The requirements of Chapters 7, 10, 12, 17, 18, 21, 23, 26, and 27 shall also apply unless they are in conflict withthis chapter.



The correlating committee makes reference to 24.1.3 and the phrase ", unless they are in conflict with this chapter." Requirements should not conflict. Where deviations from the requirements of other chapters are warranted they should be identified and addressed through appropriate allowances in the code language. The correlating committee directs the SIG-ECS committee to review the requirements in Chapter 24 with consideration to resolving any identified conflicts with other chapters. Where changes are made they should be done without introducing new material in the second draft phase. In addition the committee should consider rewording 24.1.3 to positive language. For example: The requirements of chapters x, y and z shall apply unless otherwise noted in this chapter.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement



Statement: The statement was changed into positive language.


226 of 365 9/22/2014 2:48 PM


24.3.1* Emergency Message Content.

Based on the Emergency Response plan, emergency messages shall have a content that is:

(1) Appropriate for the intended message recipients

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

provides real-time information and instructions to people in a building, area, site, or installation.


The list should be added as annex material as it would be hard to enforce the terms "appropriate" and "Focused." Not sure how to upload annex material so use the below and create it at the TC. There is a report from the FPRF taking place and that material should also be used for this section.

A.24.3.1Messages shall be be both appropriate for the intended message recipients and focused on protective actions that the intended message recipients are to take.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The language has been revised to coincide with acceptable practices in accordance with the researchprovided to the committee. An annex reference to annex H (see SR-100) has been added while deleting thecurrent annex material. The paragraph has been renumbered to include all requirements for messagingunder 24.3.7.


227 of 365 9/22/2014 2:48 PM


24.3.3 * Microphone Use. 24.3.3.1 *

All users of systems that have microphones for live voice announcements shall be provided with posted instructionsfor using the microphone.


Editorial to comply with the Manual of Style

Related Item





Street Address:

City:

State:

Zip:


Committee Statement



Statement: Editorial change to comply with the NFPA Manual of Style.


228 of 365 9/22/2014 2:48 PM


24.3.6.4

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


This requirement was too general since class C is already allowed for shared networks level 3; the additional requirements should only apply to shared pathway levels 1 & 2. Since shared pathway level 3 requires all dedicated equipment, ancillary functions can be supported without the need for extra evaluation by the AHJ since the equipment being dedicated to the MNS would be listed for this purpose. It is only when we are sharing the network with other equipment/systems (that may provide ancillary functions via level 1 or 2 shared pathways) that additional requirements and AHJ specific approvals should apply.




Related Item

First Revision No. 305-NFPA 72-2013 [New Section after 24.3.5.3]




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: Editorial modification was made to the original comment for clarity.

Since section 23.6.3 creates requirements for analyzing and documenting a plan to utilize shared pathwaylevel 1 or 2 for life safety networks, this section (which deals with the same issues for MNS) was updated toinclude the reference to that 23.6.3.


229 of 365 9/22/2014 2:48 PM


24.3.6.4

The utilization of shared pathway levels, as specified in Section 12.5 , for Where Class N pathways used inemergency communica on systems to systems u lize shared pathway levels 1 & 2 as the means to support ancillaryfunctions, devices, or interconnected systems via common pathways, shall be determined , the shared pathwaysshall meet the requirements of 23.6.3 , be permitted by a risk analysis, and approved by the AHJ.


Since the proposed section 23.6.3 creates requirements for analyzing and documenting a plan to utilize shared pathway level 1 or 2 for life safety networks, this section (which deals with the same issues for MNS) was updated to include the reference to that 23.6.3.The proposal is the recommendation by the Correlating Committee Task Group members thatwas comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of thecommittees.Wayne MooreA.J. CapowskiJoe L. CollinsDan HoronVic HummMichael PallettCharles PughRobert SchifilitiAviv SiegelLarry ShudakBob ElliottPaul CrowleyJeff SilveiraJeff KnightAndrew Berezowski




Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: Editorial modification was made to the original comment for clarity.

Since section 23.6.3 creates requirements for analyzing and documenting a plan to utilize shared pathway


230 of 365 9/22/2014 2:48 PM

level 1 or 2 for life safety networks, this section (which deals with the same issues for MNS) was updated toinclude the reference to that 23.6.3.


231 of 365 9/22/2014 2:48 PM


24.3.7 Messages for One-Way Emergency Communications Systems.

24.3.7.1*

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

24.3.7.2*

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

24.3.7.3

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

24.3.7.4

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



The correlating committee direct the SIG-ECS committee to reconsider the action on FR 309. The introduction sentence for 24.3.8.1 and 24.3.8.2 as currently worded would require all of the listed systems.

Related Item






Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The section reference in the public comment is incorrect. The TC has responded to the correlatingcommittee notes in SR-85.


232 of 365 9/22/2014 2:48 PM


24.3.7.1 *

Messages Message content shall be developed for each scenario developed and documented in the emergencyresponse plan for each scenario established in the emergency response plan.


Messages content should be developed and documented as a part of an emergency response plan. A plan is to be used in the event of an emergency - so the plan should have already established the message content and present them clearly in the document. Without this clarification a plan could include a step to issue a "Immediate Evacuation" notice, without establishing in advance the exact words (content) to be used to accomplish this.

Related Item


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




Street Address:

City:

State:

Zip:


Committee Statement


Resolution: It is not the purview of NFPA 72 to dictate the content of the emergency plan.


233 of 365 9/22/2014 2:48 PM


24.3.7.2 *

A message template shall be developed for each message required Messages content shall be designed based ona pre-established message structure or template. Message templates shall be developed for each emergencytype, specific to the technological method of message delivery, to support the development of consistent andeffective message content required in 24.3.7.1.


The term "message template" is not defined or referenced in the annex. Overall this requirement is not clear and could easily be misinterpreted. I seems that this requirement was based on NIST Technical Note 1779. But even in that document message templates are not referenced other then very generally and in the context of future work. But I think it is a useful concept but out of context in NFPA72 without a whole lot more information then is in the annex or a reference to the NIST Technical Note. This proposal goes further in providing more context with respect to the terms used in NIST 1779.



Public Comment No. 218-NFPA 72-2014 [Section No. A.24.3.7.2]

Related Item






Street Address:

City:

State:

Zip:


Committee Statement


Resolution: The requirements are too strict.


234 of 365 9/22/2014 2:48 PM


24.3.8 * System Classification.

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

24.3.8.1

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

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

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

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

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

24.3.8.2

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

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

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

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

(4) Elevator emergency communications systems (see 24.5.4 11)

(5) Stairway communications systems (see 24.12 )


To correct references and to add the new reference to stairway communications

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The revised wording provides more clarity. The references were corrected and a new reference tostairway communications was added to complete the list of two-way systems.


235 of 365 9/22/2014 2:48 PM


24.3.8 * System Classification.

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

24.3.8.1

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

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

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

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

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

24.3.8.2


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

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

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

(4) Elevator emergency communications systems (see 24.5.4)


Revised wording provides more clarity.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The revised wording provides more clarity. The references were corrected and a new reference tostairway communications was added to complete the list of two-way systems.


236 of 365 9/22/2014 2:48 PM


24.3.8.2


(1) Emergency Voice Alarm Communication system ( see 24.4)

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

(3) Two-way, radio communications enhancement systems (see 24.5.2 9 )

(4) Two-way, Area of refuge (area of rescue assistance) emergency communications systems (see 24.5.3 10 )

(5) Two-way, Elevator landing emergency communications systems (see 24.5.4 11)

(6) Two-way, in building stairway communication system (see 24.12 )


The term in the IBC for the elevator landing 2-way communication system is Elevator Landing communication system (IBC 2009 and IBC 2012 Section 1007.8)This is a different communication system than the Elevator Car communication system required by the Elevator Code which does not have an interface with the building FA system.The referenced sections are corrected to include EVACS, and stairway communication systems.

Related Item

Public Input No. 388-NFPA 72-2013 [Section No. 24.3.6.8.1 [Excluding any Sub-Sections]]




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: Emergency voice alarm communications system is a one-way system. Elevator landing communicationsystem is not in the current or proposed code. The IBC does not define elevator landing communicationsystem.


237 of 365 9/22/2014 2:48 PM


24.3.11 Control Unit Listing for Mass Notification Systems.

Control units installed as part of a mass notification system shall be in compliance with this Code and at least oneof the following applicable standards such as :

(1) ANSI/UL 864, Standard for Control Units and Accessories for Fire Alarm Systems;

(2) ANSI/UL 2017, Standard for General-Purpose Signaling Devices and Systems; or

(3) ANSI/UL 2572, Mass Notification Systems.


Mass Notification systems have matured in technology as well as listings. UL 2572 has been published for several years now. It is important that the committee now recognize that products must be listed to be used for MNS. As a result, the committee should list that at least one of the applicable standards are necessary to be met in order to provide a level of system functionality and reliability. The committee needs to remove the words "such as" which could potentially allow basically any product to be used for MNS.

Related Item







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: Mass Notification systems have matured in technology as well as listings. UL 2572 has been published forseveral years now. It is important to recognize that products must be listed to be used for MNS. As a result,at least one of the applicable standards is necessary to be met in order to provide a level of systemfunctionality and reliability.

Annex material was added to explain the relationship of the standards with control units.


238 of 365 9/22/2014 2:48 PM


TITLE OF NEW CONTENT Risk Analysis Documentation

Add a new 24.3.11.10 and A24.3.11.10:

24.3.11.10 The risk analysis shall be documented to identify the methods, data sources, assumptions andconclusions that are the bases for design decisions.

A24.3.11.10 The management of change requires the design bases to be adequately captured and documented. This can be included in the design brief described in 24.7.6.6 or in a separate document. NFPA 551 Guide for theEvaluation of Fire Risk Assessments, Chapter 7 provides guidance on how the risk assessment should bedocumented.

Substatiation - FR #312 remeved the reference to the perfromanced based design section. Without the tie toSection 24.7, the requirement for documenting the risk analysis as part of the design is not clear. Section 7.3.6 onlyrequires “findings and considerations” be documented. Section 24.7 requires goals, objectives, performancecriteria and risk analysis be incorporated in the design documentation as part of the “design brief”. If 24.3.11.3 goesaway, additional guidance on documentation should be provided.


NFPA 72 does not provide adequate guidance or references on how the risk analysis that provides the bases for design decisions be documented. NFPA 551 was developed to help AHJ's evaluated risk analyses including how they are documented. NFPA 72 should reference the guide in its annex material.

Related Item



Submitter Full Name: Kenneth Dungan

Organization: Performance Design Technologie

Street Address:

City:

State:

Zip:


Committee Statement


Resolution: The recommended requirement is excessive for a minimum standard.


239 of 365 9/22/2014 2:48 PM


24.3.14.7

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

Exception: Level 1 shall be permitted where the building is the communication zones are separated by less than2-hour fire-rated construction.


This change is to specify the communication zones, since different buildings could have many different type of constructions per the associated building codes.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: When the building is rated less than 2 hour construction, the zones are rated less than 2 hourconstruction.


240 of 365 9/22/2014 2:48 PM


24.3.14.8.1 *

Where a two-way radio emergency radio communications enhancement system is used in lieu of a two-wayin-building wired emergency communications system provided , it shall have a pathway survivability of Level 1,Level 2, or Level 3. Level 1 pathway survivability shall be permitted in buildings having communication zonesseparted by less than 2-hours construction.

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

24.3.14.8.1.1

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

24.3.14.8.1.2

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


The emergency radio enhancement system is now a mandatory/required system to be installed in ALL high-rise buildings per the previous IBC-2009 and now the current IBC-2012. The wired 2-way communication system (phone-jack system) may be permitted by the AHJs, in lieu of the mandatory radio system. All new high-rise buildings in my jurisdiction (San Francisco) are being provided with Level 2 or Level 3 radio systems. The intent is to provide emergency personnel with a reliable and survivable communication system allowing them to use their portable radios within the building during fire emergency conditions. It is relatively easy to install all vertical components, in 2-hr rated shafts in new high-rise buildings, while the horizontal coax runs to the distributed antenna are typically installed in the floor slabs (embedded in 2 inches of concrete). Another option is to install the antenna in or adjacent the 2-HR vertical enclosure.Allowing level 1 survivability for radio systems, may be permitted in low-rise buildings where the communication zones are separated by less than 2-HR construction.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: Radio enhancement systems are not mandatory in all jurisdictions. See 24.3.14.4.1 which alreadycontains the language submitted.


241 of 365 9/22/2014 2:48 PM


24.3.14.8.2

Where a two-way radio communications enhancement system is used in lieu of a two-way in-building wiredemergency communications system provided , the design of the system shall be approved by the authority havingjurisdiction.


The radio enhancement system is the mandatory communication system in high-rise buildings per IBC 2009 and 2012 and NOT the wired phone-jack system

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: Radio enhancement systems are not mandatory in all jurisdictions. The requirement for approval isalready in Section 24.9 and the comment reference section is incorrect.


242 of 365 9/22/2014 2:48 PM

Public Comment No. 119-NFPA 72-2014 [ Section No. 24.3.14.9 [Excluding any Sub-Sections] ]

Where required by applicable building codes, Area of refuge (area of rescue assistance) and elevator landingemergency communications systems shall comply with 24.3.14.9.1 and 24.3.14.9.2.


Areas of refuge, are no longer required by current building codes in fully sprinklered buildings or in residential buildings. However, elevator landings 2-way communication systems are required in each elevator landing per IBC Section 1007.8. The elevator landing communication systems should be classified as ECS and shall have same requirements as area of refuge communication systems (which are no longer required)

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The IBC does not define elevator landing communications system and NFPA 72 cannot reclassify anysystem other than area refuge.


243 of 365 9/22/2014 2:48 PM


24.4.8* Relocation and Partial Evacuation.

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

24.4.8.1

New systems employing relocation or partial evacuation shall require documentation in accordance with Sections7.3, 7.4, and 7.5 in addition to the minimum documentation requirements of Sections 7.2 and 24.15.

24.4.8.2

Systems shall be provided with manual voice transmission capabilities selectively to one or more zones or on anall-call basis.

24.4.8.3

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

24.4.8.3.1

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

24.4.8.3.2

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

24.4.8.4

Where provided, loudspeakers in each enclosed stairway, each exit passageway, and each group of elevator carswithin a common hoistway shall be connected to separate notification zones for manual paging only.

24.4.8.4.1

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

24.4.8.4.2

Manually activated speakers shall be permitted in exit stair enclosures and exit passageways in buildings that haveemergency voice/alarm communications systems in accordance with 24.4.

24.4.8.5

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

24.4.8.5.1*

Fire alarm systems used for partial evacuation and relocation shall be designed and installed such that attack byfire within a signaling zone does not impair control and operation of the notification appliances outside theevacuation signaling zone.

24.4.8.5.2

Performance features provided to ensure operational reliability under adverse conditions shall be described andtechnical justification provided in the documentation submitted to the authority having jurisdiction with the analysisrequired in 23.4.3.1.

24.4.8.5.3*

All circuits necessary for the operation of the notification appliances shall be protected until they enter the signalingzone that they serve by the protection provided by the pathway survivability level required in 24.3.14.4.1 or byperformance alternatives approved by the authority having jurisdiction.

24.4.8.5.4

Where the separation of in-building fire emergency voice/alarm control equipment locations results in the portionsof the system controlled by one location being dependent upon the control equipment in other locations, thecircuits between the dependent controls shall be protected against attack by fire by the protection provided by thepathway survivability level required in 24.3.14.4.1 or by performance alternatives approved by the authority havingjurisdiction.

24.4.8.5.5

Protection of circuits between redundant control equipment locations that are not mutually dependent shall not berequired.


244 of 365 9/22/2014 2:48 PM

24.4.8.5.6

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

(1) A 2-hour fire-rated enclosure

(2) A 2-hour fire-rated room

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

24.4.8.5.7

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



The correlating committee directs the SIG-ECS committee to reconsider the action on FR 358. The removal of the term "evacuation" was done inconsistently throughout the revised section. It was deleted in some places and not in others. The changes should be made consistently. Also the terminology should be consistent with the terms for zones as defined in 3.3.320.

Related Item






Street Address:

City:

State:

Zip:


Committee Statement



Statement: The language has been modified to provide clarity and consistency.


245 of 365 9/22/2014 2:48 PM


24.5.2 * Two-Way Radio Communications Enhancement Systems.

24.5.2.1 General.

24.5.2.1.1 Non-Interference.

No amplification system capable of operating on frequencies or causing interference on frequencies assigned to thejurisdiction by the FCC shall be installed without prior coordination and approval of the authority having jurisdiction.The building manager/owner shall suspend and correct other equipment installations that degrade the performanceof the public safety radio system or public safety radio enhancement system.

24.5.2.1.2 Approval and Permit.

Plans shall be submitted for approval prior to installation. At the conclusion of successful acceptance testing, arenewable permit shall be issued for the public safety radio enhancement system where required by the authorityhaving jurisdiction.

24.5.2.2 Radio Coverage.

Radio coverage shall be provided throughout the building as a percentage of floor area as specified in

Installation and design

24.5.2.2.1

through 24.5.2.2.3 .

24.5.2.2.1 Critical Areas.

Critical areas, such as the fire command center(s), the fire pump room(s), exit stairs, exit passageways, elevatorlobbies, standpipe cabinets, sprinkler sectional valve locations, and other areas deemed critical by the authorityhaving jurisdiction, shall be provided with 99 percent floor area radio coverage.

24.5.2.2.2 General Building Areas.

General building areas shall be provided with 90 percent floor area radio coverage.

24.5.2.2.3 Amplification Components.

Buildings and structures that cannot support the required level of radio coverage shall be equipped with a radiatingcable system or a distributed antenna system (DAS) with FCC-certified signal boosters, or both, or with a systemthat is otherwise approved, in order to achieve the required adequate radio coverage.

24.5.2.3 Signal Strength.

24.5.2.3.1 Inbound.

A minimum inbound signal strength of -95 dBm, or other signal strength as required by the authority havingjurisdiction, shall be provided throughout the coverage area.

24.5.2.3.2 Outbound.

A minimum outbound signal strength of -95 dBm at the donor site, or other signal strength as required by theauthority having jurisdiction, shall be provided from the coverage area.

24.5.2.3.3 Isolation.

If a donor antenna exists, isolation shall be maintained between the donor antenna and all inside antennas andshall be a minimum of 15 dB above the signal booster gain under all operating conditions

All in buiding two way radio systems shall be dsigned and installed as per the requirements of NFPA 1221,Standard for the installation Maintenance and use of Emergency Services Communications Systems .

24.5.2. 4 * System Radio Frequencies.

The public safety radio enhancement system shall be capable of transmitting all public safety radio frequenciesassigned to the jurisdiction and be capable of using any modulation technology.

24.5. 2. 4.1 List of Assigned Frequencies.

The authority having jurisdiction shall maintain a list of all inbound/outbound frequency pairs for distribution tosystem designers.

24.5.2.4.2 * Frequency Changes.

Systems shall be capable of upgrade, to allow for instances where the jurisdiction changes or adds systemfrequencies, in order to maintain radio system coverage as originally designed.

24.5.2.5 System Components.


246 of 365 9/22/2014 2:48 PM

24.5.2.5.1 Component Approval.

Components utilized in the installation of the public safety radio enhancement system, such as repeaters,transmitters, receivers, signal boosters, cabling, and fiber-distributed antenna systems, shall be approved and shallbe compatible with the public safety radio system

2 All in-building two way radio systems shall be inspected, tested and maintained per th rerquirements of Chapter14 .

24.5.2. 5. 2 Component Enclosures .

All repeater, transmitter, receiver, signal booster components, and battery system components shall be contained ina NEMA 4- or 4X-type enclosure(s).

24.5.2.5. 3 External Filters.

Permanent external filters and attachments shall not be permitted.

24.5.2.5.4 Signal Booster Components.

If used, signal boosters shall meet the following requirements, as well as any other requirements determined by theauthority having jurisdiction:

(1)

(2) All signal boosters shall be compatible with both analog and digital communications simultaneously at thetime of installation. The authority having jurisdiction shall provide the maximum acceptable propagation delaystandard.

24.5.2.5.5 Power Supplies.

At least two independent and reliable power supplies shall be provided for all repeater, transmitter, receiver, andsignal booster components, one primary and one secondary.

24.5.2.5.5.1 Primary Power Source.

The primary power source shall be supplied from a dedicated branch circuit and comply with 10.6.5.1 .

24.5.2.5.5.2 * Secondary Power Source.

The secondary power source shall consist of one of the following:

(1) A storage battery dedicated to the system with at least 12 hours of 100 percent system operation capacityand arranged in accordance with 10.6.10 .

(2) An automatic-starting, engine-driven generator serving the dedicated branch circuit or the system with atleast 12 hours of 100 percent system operation capacity and storage batteries dedicated to the system withat least 2 hours of 100 percent system operation capacity and arranged in accordance with 10.6.11.3 .

24.5.2.5.5.3 Monitoring Integrity of Power Supplies.

Monitoring the integrity of power supplies shall be in accordance with 10.6.9 .

24.5.2.6 System Monitoring.

24.5.2.6.1 Fire Alarm System.

The public safety radio communications enhancement system shall include automatic supervisory and troublesignals for malfunctions of the signal booster(s) and power supply(ies) that are annunciated by the fire alarmsystem and comply with the following:

(1) The integrity of the circuit monitoring signal booster(s) and power supply(ies) shall comply with 10.6.9 andSection 12.6 .

(2) System and signal booster supervisory signals shall include the following:

(3) Antenna malfunction

(4) Signal booster failure

(5) Low-battery capacity indication when 70 percent of the 12-hour operating capacity has been depleted.

(6) Power supply signals shall include the following for each signal booster:

(7) Loss of normal ac power

(8) Failure of battery charger

* Signal boosters shall have FCC certification prior to installation.


247 of 365 9/22/2014 2:48 PM

24.5.2.6.2 * Dedicated Panel.

A dedicated monitoring panel shall be provided within the fire command center to annunciate the status of all signalbooster locations. The monitoring panel shall provide visual and labeled indication of the following for each signalbooster:

(1) Normal ac power

(2) Signal booster trouble

(3) Loss of normal ac power

(4) Failure of battery charger

(5) Low-battery capacity

24.5.2.7 Technical Criteria.

The authority having jurisdiction shall maintain a document of technical information specific to its requirements,which shall contain, as a minimum, the following:

(1) Frequencies required

(2) Location and effective radiated power (ERP) of radio sites used by the public safety radio enhancementsystem

(3) Maximum propagation delay (in microseconds)

(4) List of specifically approved system components

(5) Other supporting technical information necessary to direct system design

All inbuilding two way radio system design, operations, maintenence, testing and inspection documentation shallbe as per Chapter 7.


This proposal will eliminate any correlation issues between NFPA 72 and NFPA 1221. A task group was developed and worked on moving the requisite requirements for two way radio systems to a standard that has the technical membership to determine what is required in these buildings with these systems. The key components such as documentation, inspection, testing, and maintenance are referred back to NFPA 72 chapter 14 from the NFPA 1221 document.

Related Item








Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: In building communications systems are not public emergency communications that are covered by NFPA1221. The material presently in 24.9 is within the scope of NFPA 72 Chapter 24.


248 of 365 9/22/2014 2:48 PM


Where no listed loudspeaker exists for the to acheive the notification performance required by theemergency response plan, nonlisted devices shall be permitted to be connected to the loudspeaker circuitif their failure will not impair the operation of the mass notification system.


There may be situations where in order to achieve the goals of a emergency response plan, listed appliance are not available but appliances not-listed for fire are available. This is exactly the same situation that exists for initiating devices and the established language of this proposal is taken with (modification for loudspeakers) from 24.5.10.3.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: There may be situations where in order to achieve the intelligibility requirements, listed appliances are notavailable but non-listed appliances are available to meet the performance requirements of the code.


249 of 365 9/22/2014 2:48 PM


24.5.5 Documentation.

Mass notification systems shall require documentation in accordance with Sections 7.3 , 7.4 , and 7.5 in additionto the minimum documentation requirements of Sections 7.2 and 24.15 .


This is duplicate material. See Section 24.15.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement



Statement: This is duplicate material. See Section 24.15.


250 of 365 9/22/2014 2:48 PM


24.5.15.1

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


This exception is too general and negates the exception with more detail established in 24.5.15.6. Since 24.5.15.6 is part of 24.5.15, the exception is established and does not need to be repeated.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted


Statement: This exception is too general and negates the exception with more detail established in 24.5.15.6. Since24.5.15.6 is part of 24.5.15, the exception is established and does not need to be repeated.


251 of 365 9/22/2014 2:48 PM


Where no listed device exists for the visable no fica on required by the emergency response plan, nonlisteddevices shall be permi ed to be usedif their failure will not impair the opera on of the mass no fica on system.


There may be situations where in order to achieve the goals of a emergency response plan, listed appliance are not available but appliances not-listed for fire are available. This is exactly the same situation that exists for initiating devices and the established language of this proposal is taken directly from 24.5.10.3.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement


Resolution: The code already permits non-listed equipment as ancillary devices.


252 of 365 9/22/2014 2:48 PM


Where no listed device exists for the textual or graphical no fica on required by the emergency response plan,nonlisted devices shall be permi ed to be usedif their failure will not impair the opera on of the mass no fica on system.



Related Item





Street Address:

City:

State:

Zip:


Committee Statement




253 of 365 9/22/2014 2:48 PM


Where no listed device exists for the tactile notification required by the emergency response plan,nonlisted devices shall be permitted to be used if their failure will not impair the operation of the massnotification system.



Related Item





Street Address:

City:

State:

Zip:


Committee Statement




254 of 365 9/22/2014 2:48 PM


24.6.4 Emergency Command Center.

Refer to Section 24.13 for requirements of an emergency command center.



The correlating committee directs the SIG-ECS committee to reconsider their action on FR 333. By deleting existing 24.6.4 and it's title, the demoted paragraphs [formerly 24.6.4.1 and 24.6.4.2 - now 24.13.4 an 24.13.5] lack a title (required by the MOS). The committee should consider either reinstating the former subsection and title or adding new titles to the demoted paragraphs.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement



Statement: Change to comply with the NFPA Manual of Style.


255 of 365 9/22/2014 2:48 PM


24.10.4

All pathways between a remote area of refuge stations and the central control point shall be monitored for integritywith an effective date of January 1, 2019 .


This monitoring for integrity requirement is new with this code cycle. Manufacturer’s need time to incorporate this feature into their equipment offering to meet the code. The effective date gives the manufacture’s the necessary time to make engineering design changes and get approvals on their products prior to release.

Related Item




Organization: NEMA

Street Address:

City:

State:

Zip:

Submittal Date: Mon Apr 28 10:33:48 EDT 2014

Committee Statement


Resolution: The 2019 date is excessive. There are products that are available today to meet the requirements.


256 of 365 9/22/2014 2:48 PM


26.1.2

The requirements of Chapters 7, 10, 12, 14, and 23 shall also apply unless they are in conflict with this chapter.



The correlating committee makes reference to 26.1.2 and the phrase ", unless they are in conflict with this chapter." Requirements should not conflict. Where deviations from the requirements of other chapters are warranted they should be identified and addressed through appropriate allowances in the code language. The correlating committee directs the SIG-SSS committee to review the requirements in Chapter 26 with consideration to resolving any identified conflicts with other chapters. Where changes are made they should be done without introducing new material in the second draft phase. In addition the committee should consider rewording 26.1.2 to positive language. For example: The requirements of chapters x, y and z shall apply unless otherwise noted in this chapter.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement



Statement: The text has been revised to provide more positive code language.


257 of 365 9/22/2014 2:48 PM


26.2.2 * Alarm Signal Verification.

26.2.2.1

For applications other than those addressed under the scope of 29.7.9.2, supervising station personnel shallattempt to verify alarm signals prior to reporting them to the communication center where all the following conditionsexist:

(1)

(2) Documentation of the requirement for alarm signal verification is provided by the responsible fire department tothe supervising station and the protected premises.

(3) If the requirement for verification changes, the responsible fire department shall notify the supervising stationand the protected premises.

(4)

(5) Verification of a true fire is received from anyone on premises or verification of an unwanted alarm signal isreceived only from a pre-assigned list of authorized personnel within the protected premises.

(6)

(7)

(8)


This proposal resolves any confusion about the time allocated for Verification. We represented the International Association of Fire Chiefs (original proponents) when this section was added in the 2013 NFPA 72 process. It was unquestionably our intent to allow an extra 90 seconds for the Verification process. The logic is simple: If we require an extra function, we must allow extra time for it to be accomplished.

This was captured in our testimony and in our outreach information, such as excerpt from the IAFC – NFPA 72 Fact Sheet: Concept One: 90-Second Verification Delay The IAFC is proposing language that would allow a 90-second delay in notification in order for those monitoring a central station alarm in a commercial environment to determine if the alarm is false. It was our goal to essentially duplicate the extra 90-seconds allowed in the household section.

This intent was captured accurately in the annex material, which states: A.26.2.3.1(4) The 90-second allowance for a supervising station to call the protected premise to verify the validity of the received alarm signal is independent from the time allowed for the supervising station to initiate the retransmission to the communications center. However, there is some confusion in the industry about whether the annex material is consistent with the requirements in the body.

This proposal modifies the wording in the body of the standard to clarify that it allows an extra 90-seconds. This would be additionally reinforced by the existing Annex language to make the intent quite clear. This newly proposed language was written to be nearly identical that found in 29.7.9.2 for household systems, which is well accepted and understood to provide an additional 90-seconds.

While there are differing views about over the role of delays in alarm signals, it is critical to remember that this is an “Opt-in” requirement. Only those that purposely choose Verification will experience a delay. Those who do not “opt-in” are not affected.

For departments that do choose to “opt-in”, a local decision is being made that the benefit of Verification is worth the delay.

For example, some departments dispatch a single apparatus, Code 1 (non-emergency) on an automatic alarm incident. In this case, a 90-second delay is virtually inconsequential – and a reasonable decision could be made that the benefit of potentially confirming a working fire is well worth the trade-off. This typically upgrades the incident to a full first alarm assignment with 16-25 firefighters traveling Code 3 (based on effective firefighting force analyses conducted per NFPA

* Alarm signal verification is required by the responsible fire department for a specific protected premises.

* The verification process does not take longer delay the reporting by more than 90 seconds from the timethe alarm signal is received at the supervising station until the time that retransmission of the verified alarmsignal is initiated .

* Verified alarm signals are immediately retransmitted to the communications center and include informationthat the signal was verified at the protected premises to be an emergency.

* Alarm signals where verification is not conclusive are immediately retransmitted to the communicationscenter.

* Alarm signals that are verified as unwanted alarms shall be reported to the responsible fire department in amanner and at a frequency specified by the responsible fire department.


258 of 365 9/22/2014 2:48 PM

1710, etc.). This would dramatically increase both the speed and the size of the response force, and actually results in units arriving SOONER than they would without the Verification delay.

The challenge associated with automatic fire alarm dispatches continues to grow, making it important to address this issue. The following examples were pulled in a quick literature search:

A recent report by Roseville (CA) Fire Department looked at 10-years’ worth of automatic alarms (3,942 calls) and quantified the number of alarms that resulted in a hazard (fire, smoke, water flow, or hot object) that did not have a water flow or grill hood alarm, a reporting party at scene giving an update on conditions, or an otherwise reliable indicator that a fire was in progress. “The total number of alarms meeting these criteria in a period of ten (10) years was found to be two a total of two (2) incidents that meet the criteria.” In both cases, the incidents were small and were mitigated by the first company at the scene. Roseville Fire Dept., Fire Alarm Response Study, Feb 12, 2014.

Henderson, NV eliminated responses to unverified automatic fire alarms after a 2007 study found that 99.994 percent of 4,019 automatic alarm calls were false. http://www.lasvegassun.com/news/2008/feb/18/fire-alarm-doesnt-mean-fire-department-coming/

Las Vegas Fire & Rescue eliminated responses to unverified automatic alarms after an analysis looked at 3,700 automatic alarms. After pulling out incidents where other callers contacted 911 on the same incident, there were 3,400 incidents with an automatic alarm dispatch only. Not a single one of those 3,400 automatic alarm incidents involved a fire. http://www.riskinstitute.org/peri/component/option,com_bookmarks/Itemid,44/catid,29/navstart,0/task,detail/mode,0/id,779/search,r/

Tualatin Valley Fire & Rescue, found only 2 working fires upon arrival out of more than 10,000 commercial automatic alarm dispatches. http://www.etnews.org/docs/TVFR_Alarm_Verification.pdf

A study by the Charlottesville, Virginia, Fire Department concluded that less than 1% of fire alarm calls per year actually involve hazardous or emergency conditions upon the arrival of the fire department. http://www.cfdonline.org/CFD_FireAlarmPolicyFINAL.pdf

We urge the Committee to support this proposal which improves the clarity and usefulness of NFPA 72.

Respectfully submitted,

Stephen A. ForsterDivision Chief / Fire MarshalTualatin Valley Fire & Rescue

Jeffrey D. JohnsonChief (Ret.); Chief Executive Officer Western Fire Chiefs Association

Related Item


First Revision No. 36-NFPA 72-2013 [Section No. A.26.2.3.2]


Submitter Full Name: STEVE FORSTER

Organization: Tualatin Valley Fire & Rescue

Affilliation: Western Fire Chief's Association

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected


259 of 365 9/22/2014 2:48 PM

Resolution: The proposed change does not add clarity. The current code language is clear that the verification processadds a maximum of 90 seconds before alarm retransmission to the communication center is initiated.


260 of 365 9/22/2014 2:48 PM


26.2.3 Alarm Signal Preverification.

Where alarm signal verification is required by other governing laws, codes, or standards, or by other parts of thiscode, by the authority having jurisdiction, or by the responsible fire department in accordance with 26.2.2 , thesupervising station shall immediately notify the communications center that a fire alarm signal has been receivedand verification is in process.

26.2.3.1

Where alarm signal verification is required by the responsible fire department in accordance with 26.2.2 , thesupervising station shall immediately notify the communications center that a fire alarm signal has been receivedand verification is in process.


This proposed change resolves eliminates the Pre-Verification and the variety of problems associated with it. We were part of the International Association of Fire Chief’s (IAFC) working group who proposed Verification when it was added in the 2013 NFPA 72 process; it was never our intent to require Pre-Verification or the delays associated with it.

Pre-Verification is simply a bad idea. 911 centers are not equipped to handle “possible calls”. CAD programs are generally not set up to take calls that are FYI only, then deleted later. This is simply not practical, and it increases call volumes at overworked 911 centers.

Most importantly, a simple analysis of necessary functions reveals that Pre-Verification will delay automatic alarm dispatching by at least 6-7 minutes. It will take time for alarms to be retransmitted by the monitoring center; A26.2.1 acknowledges 90 seconds. Then the call needs to be answered at the PSAP (911 center); the national standard NFPA 1221 prescribes 95% of calls be answered in 15 seconds, and 99% of calls in 40 seconds. After the phone is answered, alarm and address information must be provided; NFPA 1221 prescribes 95% of this information to be processed in 106 seconds. Then 90 seconds is allocated for Verification, and a subsequent 90 seconds for another “immediate” retransmission back to the PSAP after Verification is complete. Adding this sequence up:

90 seconds for “immediate” Pre-Verification retransmission to PSAP15-40 seconds for PSAP to answer the phone106 seconds for PSAP to process the call90 seconds for Supervising Station Verification90 seconds for subsequent retransmission back to PSAP= 391 to 416 second delay (6.5 - 7minutes).

A 6 to 7 minute delay is inappropriate, is not good for the fire service or the public, and was never the intent of the proponents. This section should be eliminated in its entirety. If it is not, then the Committee should revise the section to acknowledge all of the above delays in the standard, allow time for each, and justify how or why such a requirement is prudent.

There was a public input (PI-166) to allow for a jurisdiction to "opt-out" of Pre-Verification; however this is not an adequate solution. The standard should not have such a poorly thought out concept included as the "base" requirement, then force an AHJ to "opt-out" of it. If the committee still believes that Pre-Verification is warranted under any condition given the significant delay and PSAP problems it causes, then it should make it an "Opt-in" function. But if it does so, then the Committee needs to recognize and specifically allow the long delay that it will entail.

Respectfully submitted,

Stephen A. ForsterDivision Chief / Fire MarshalTualatin Valley Fire & Rescue

Jeffrey D. JohnsonChief (Ret.); Chief Executive Officer Western Fire Chiefs Association

Related Item

First Revision No. 17-NFPA 72-2013 [Sections 26.2.2, 26.2.3]



261 of 365 9/22/2014 2:48 PM



Submitter Full Name: STEVE FORSTER

Organization: Tualatin Valley Fire & Rescue

Affilliation: Western Fire Chief's Association

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted


Statement: The process of preverification which was added to the 2013 edition of the code adds a confusing step to theverification process. As verification must be required by the responsible fire department to be employed, thedepartment understands there may be a delay in their receiving notification of an alarm condition at aspecified protected premises for up to an additional 90 seconds due to the verification process.

In addition, paragraphs 26.2.3 and 26.2.3.1 indicate the same requirement. Paragraph 26.2.3.1 is redundantand needs to be removed for code clarity.


262 of 365 9/22/2014 2:48 PM



Where alarm signal verification is required by other governing laws, codes, or standards, or by other parts of thiscode, by the authority having jurisdiction, or by the responsible fire department in accordance with 26.2.2 , thesupervising station shall immediately notify the communications center that a fire alarm signal has been receivedand verification is in process.

26.2.3.1



The process of preverification which was added to the 2013 edition of the code adds a cumbersome and confusing step to the verification process. The fire service input during the First Draft phase called for the removal of this requirement. It was pointed out in substantiation from the fire service that this step adds another 90 seconds to the retransmisison process. I am not certain that this is the case as the committee has not clearly spelled out how much is time alotted for preverifcation. Some feel that an additional 90 seconds is permitted for this step and others feel it is part of the 90 seconds for verification. Using either possibility would mean either 270 seconds or 180 seconds, respectively, when you include the 90 seconds already included for basic alarm signal retransmission. The task group chair for the group that worked on the original verification requirement has indicated that his group had never intended verification and retransmission to take longer than 90 seconds total. It was commented at the First Draft meeting that preverification and verification by the supervising station would take longer than the 90 seconds permitted for verification. So do we clarify the code to indicate 270 seconds of total time is permitted. As a fire service professional I would argue that this time is too long given the typical development of a fire. I recommend that the committee eliminate preverification from NFPA 72.

Related Item



Submitter Full Name: Warren Olsen

Organization: Fire Safety Consultants, Inc.

Affilliation: Illinois Fire Inspectors Association

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted





263 of 365 9/22/2014 2:48 PM


26

.

2.3.1



It appears that Sections 26.2.3 and 26.2.3.1 indicate the same requirement. 26.2.3.1 would be redundent and should be eliminated for code clarity.

Related Item






Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted





264 of 365 9/22/2014 2:48 PM

Public Comment No. 80-NFPA 72-2014 [ Section No. 26.5.3.1 [Excluding any Sub-Sections] ]

Alarm systems utilizing remote supervising station connections shall transmit alarm and supervisory signals to afacility meeting the requirements of either 26.5.3.1.1, 26.5.3.1.2, or 26.5.3.1.3, or 26 . 5.3.1.4.


Undo the first revision change because new paragraph 26.5.3.1.3 will be deleted.



Public Comment No. 76-NFPA 72-2014 [Section No. 26.5.3.1.3]



Related Item

First Correlating Revision No. 33-NFPA 72-2014 [Section No. 26.5.3.1 [Excluding any Sub-Sections]]


Submitter Full Name: David Blanken

Organization: Keltron Corporation

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: Listed central station facilities provide an acceptable alternative to governmental agencies monitoringremote stations signals.


265 of 365 9/22/2014 2:48 PM


26.5.3.1.3

Alarm, When permitted by the Authority Having Jurisdiction, alarm, supervisory, and trouble signals shall bepermitted to be received at a listed central supervising station.


Remote station fire alarm systems were originally established to allow the public sector to monitor fire alarm signals at a public entity. Until recently, private sector monitoring was permitted only by an exception in the Code. Where the public sector requires monitoring at a public entity such as a police or fire station or 9-1-1 communications center, there should be no conflicting allowances in NFPA 72. To allow the existing language to stand would not achieve the desired effect, because a jurisdiction can simply overrule the allowance to monitor at a central station. This change does not prohibit such monitoring, but would require the permission of the AHJ in order to do so.

Related Item



Submitter Full Name: Art Black

Organization: Carmel Fire Protection

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected



266 of 365 9/22/2014 2:48 PM


26.5.3.1.3

Alarm, supervisory, and trouble signals shall be permitted to be received at a listed central supervising station.


During the First Draft technical committee meeting a proposal was made from a committee member to permit signals to be received at a listed central supervising station under the rules of 26.5, Remote Supervising Station Service. There was no technical substantiation provided during committee discussion to warrant this change to a section of Chapter 26 that has historically dealt with requirements affecting first: Communication Centers, Fire Stations and Governmental Agencies; and then second: Alternate receiving locations where permitted by the AHJ. Discussion on this change seemed to center around a specific legal case which went in favor of plantiffs who successfully challenged an AHJ's ability to mandate that alarm signals be sent directly to the AHJ's communications center. Not discussed was a previous case argued several years before where another judge's ruling went the opposite way in favor of the AHJ. The committee seems to have based this revision on a specific legal case and not on any technical merit related to why the remote station rules should be changed to permit listed central station monitoring without AHJ approval.

National model codes specifically permit monitoring by an approved supervising station in accordance with NFPA 72. Depending on several factors, some AHJ's may be able to specifically name their approved supervising station of choice and others can not. NFPA 72 requirements should not be changed based on local contentious issues or modified to benefit one side of a legal argument.

Section 26.5 (and previous like sections in prior editions of the code) has long as established requirements for governmental monitoring in sections 26.5.3.1.1, and 26.5.3.1.2, except where an alternate location is permitted by the AHJ (26.5.3.1.3). Listed central stations provide a valuable service and the language of the 2013 edition, as well as previous editions, of NFPA 72 would allow their use in the Remote Supervising Station monitoring process where approved by the AHJ.

Listed central stations are also an element of Central Station Service where no other type of supervising station is permitted.

I urge the committee to remove this section or provide technical substantiation of why it has been added to the code.

Related Item






Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected



267 of 365 9/22/2014 2:48 PM


26.5.3.1.3



The new paragraph is inconsistent with paragraph 26.5.3.3 of the existing code. Paragraph 26.5.3.3 mandates the AHJ to set and enforce requirements restricting access to receiving equipment. The new paragraph permits any listed central station to provide remote station service regardless of AHJ approval, which effectively bypasses any AHJ requirements established by paragraph 26.5.3.3.



Public Comment No. 80-NFPA 72-2014 [Section No. 26.5.3.1 [Excluding any Sub-Sections]]

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected



268 of 365 9/22/2014 2:48 PM


26.5.3.1.3



The new paragraph is inconsistent with paragraph 26.5.3.2 of the existing code. Paragraph 26.5.3.2 states that trouble signals shall be permitted to be received at an approved location. The new paragraph permits any listed central station to receive trouble signals regardless of AHJ approval. In particular, only locations that have personnel on duty who are trained to handle remote supervising station trouble signals shall be approved locations. But, the new paragraph permits any listed central station to receive remote supervising station trouble signals without regard to the training of the personnel on duty.




Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected



269 of 365 9/22/2014 2:48 PM


26.5.3.1.3



The new paragraph is inconsistent with paragraph 10.3.1 of the existing code, which states that equipment shall be listed for the purpose for which it is used. Receiving equipment used to receive remote supervising station signals shall be listed to receive remote supervising station signals. The new paragraph permits any listed central station to receive remote supervising station signals without any oversight by the AHJ to ensure that the receiving equipment is properly listed. Receiving equipment listed only to receive central supervising station signals is not permitted to receive remote supervising station signals according to paragraph 10.3.1.




Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected



270 of 365 9/22/2014 2:48 PM

Public Comment No. 166-NFPA 72-2014 [ Section No. 26.6.4.1.4(B) ]

(B)

The following requirements shall apply to all combinations listed in 26.6.4.1.4(A):

(1) The means for supervising each channel shall be in a manner approved for the method of transmissionemployed.

(2) If a signal has not been processed over the subject channel in the previous 6 24 hours, a test signal shall beprocessed.

(3) The failure of either channel shall send a trouble signal on the other channel within 4 minutes.

(4) When one transmission channel has failed, all status change signals shall be sent over the other channel.

(5) The primary channel shall be capable of delivering an indication to the DACT that the message has beenreceived by the supervising station.

(6)

(7) Simultaneous transmission over both channels shall be permitted.

(8) Failure of telephone lines (numbers) shall be annunciated locally.


Referring to PI 335, I am submitting the following input.

The DACT technology was originally approved with 24 hour test. It has been effectively used since the early 1980’s and there is no body of evidence showing any poor performance, even though the PSTN has seen radical changes. For some time, the PSTN has had only 8 hours backup power with no adverse effects to DACT.

While the 24 hour requirement is not in line with the 6 hour requirement for newer technologies, the reasons stated below should convince the committee of reverting back to the 24 hour requirement.

Subsidiary station loading is built for the 24 hour test, increasing the test period by four times could overwhelm the current lines and equipment.

Middle of the night test timer failures will rarely generate a repaired system before the next business day. Coordination is required between subsidiary station, service company (if separate), customer and phone service provider.

The addition of three additional tests will ensure test signals during business “open” periods, creating customer dissatisfaction.

Except for extra ordinary and very rare exceptions, the current edition of NFPA 72 does not allow a DACT to be used without another technology. As such, there is assurance of communications integrity by having the extra path and also having the extra path supervise the DACT path.

Without doubt, DACT is a dying technology. POTS lines are being eliminated at record pace. It is likely that the 2019 NFPA code could eliminate it as an acceptable technology. To increase the test time in its waning life is an expense with little benefit and will create financial issues for subsidiary stations with no benefit to the subsidiary station or the protected premises system.

Related Item

Public Input No. 335-NFPA 72-2013 [Section No. 26.6.3.2.1.5]


Submitter Full Name: Louis Fiore

Organization: L. T. Fiore, Inc.

Street Address:

* The first attempt to send a status change signal shall use the primary channel.

Exception: When the primary channel is known to have failed.


271 of 365 9/22/2014 2:48 PM

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The six hour test was selected with care to correlate with other dual path technology requirementsconsidering the 8 hour battery backup requirements of the telecommunications industry.


272 of 365 9/22/2014 2:48 PM

Public Comment No. 51-NFPA 72-2014 [ Section No. 26.6.4.1.4(B) ]

(B)

The following requirements shall apply to all combinations listed in 26.6.4.1.4(A):

(1) The means for supervising each channel shall be in a manner approved for the method of transmissionemployed.

(2) If a signal has not been processed over the subject either channel in the previous 6 hours, a test signal shallbe processed.

(3) The failure of either channel shall send a trouble signal on the other channel within 4 minutes.

(4) When one transmission channel has failed, all status change signals shall be sent over the other channel.

(5) The primary channel shall be capable of delivering an indication to the DACT that the message has beenreceived by the supervising station.

(6)

(7) Simultaneous transmission over both channels shall be permitted.

(8) Failure of telephone lines (numbers) shall be annunciated locally.


There would likely be financial impact on manufacturers, the industry at large and users of a disappearing technology if a rules change regarding DACT operation is incorporated into the code. Another UL LISTING round for already 9th edition listed DACT’s would make the ones remaining available more costly and some manufacturers could drop needed models completely rather than further invest in a product facing certain decreasing sales. It would not seem to make sense to further restrict operational parameters of a disappearing technology soon to disappear from the code completely in the next couple of cycles. Now is the time to reverse the change in 2013 before its incorporation into UL 864 next edition.

A successful test signal transmission provides the same assurance of communications integrity as any other type of signal transmission. If any other type of signal transmission within a 6-hour period shall fulfill the requirement to verify the integrity of the reporting system, then a single test signal with the same 6-hour period should fulfill the requirement to verify the integrity of the reporting system. It should not be necessary to complete a test signal transmission on each transmission means every 6 hours.




Related Item

First Revision No. 33-NFPA 72-2013 [Section No. 26.6.3.2.1.4(B)]


Submitter Full Name: Steven Sargent


Street Address:

City:

State:

Zip:

Submittal Date: Fri Apr 25 11:37:45 EDT 2014

Committee Statement

Committee Rejected

* The first attempt to send a status change signal shall use the primary channel.

Exception: When the primary channel is known to have failed.


273 of 365 9/22/2014 2:48 PM

Action:

Resolution: As proposed, signals processed within the test time on a particular channel could prevent the otherchannel from being tested as intended.


274 of 365 9/22/2014 2:48 PM


26.6.4.1.5 DACT Transmission Means.

The following requirements shall apply to all DACTs:

(1) A DACT shall be connected to two separate means of transmission at the protected premises so that a singlepoint of failure on one means of transmission shall not affect the second means of transmission.

(2) The DACT shall be capable of selecting the operable means of transmission in the event of failure of the othermeans.

(3) The primary means of transmission shall be a telephone line (number) connected to the public switchednetwork.

(4)

(5) Each DACT shall be programmed to call a second receiver when the signal transmission sequence to the firstcalled line (number) is unsuccessful.

(6) Each transmission means DACT shall automatically initiate and complete a test signal transmissionsequence to its associated receiver at least once every 6 hours. A successful signal transmission sequence ofany other type, within the same 6-hour period, shall fulfill the requirement to verify the integrity of the reportingsystem, provided that signal processing is automated so that 6-hour delinquencies are individuallyacknowledged by supervising station personnel.

(7)


There would likely be financial impact on manufacturers, the industry at large and users of a disappearing technology if a rules change regarding DACT operation is incorporated into the code. Another UL LISTING round for already 9th edition listed DACT’s would make the ones remaining available more costly and some manufacturers could drop needed models completely rather than further invest in a product facing certain decreasing sales. It would not seem to make sense to further restrict operational parameters of a disappearing technology soon to disappear from the code completely in the next couple of cycles. Now is the time to reverse the change in 2013 before its incorporation into UL 864 next edition.

A successful test signal transmission provides the same assurance of communications integrity as any other type of signal transmission. If any other type of signal transmission within a 6-hour period shall fulfill the requirement to verify the integrity of the reporting system, then a single test signal with the same 6-hour period should fulfill the requirement to verify the integrity of the reporting system. It should not be necessary to complete a test signal transmission on each transmission means every 6 hours.



Public Comment No. 51-NFPA 72-2014 [Section No. 26.6.4.1.4(B)]

Related Item

First Revision No. 33-NFPA 72-2013 [Section No. 26.6.3.2.1.4(B)]


Submitter Full Name: Steven Sargent


Street Address:

City:

State:

Zip:

Submittal Date: Fri Apr 25 11:42:14 EDT 2014

Committee Statement

* The first transmission attempt shall utilize the primary means of transmission.

* If a DACT is programmed to call a telephone line (number) that is call forwarded to the line (number) of theDACR, a means shall be implemented to verify the integrity of the call forwarding feature every 4 hours.


275 of 365 9/22/2014 2:48 PM


Resolution: The submitter did not provide sufficient technical substantiation for the change.


276 of 365 9/22/2014 2:48 PM


27.1.4

The requirements of Chapters 10 and 14 shall also apply unless they are in conflict with this chapter.



The correlating committee makes reference to 27.1.4 and the phrase ", unless they are in conflict with this chapter." Requirements should not conflict. Where deviations from the requirements of other chapters are warranted they should be identified and addressed through appropriate allowances in the code language. The correlating committee directs the SIG-PRS committee to review the requirements in Chapter 27 with consideration to resolving any identified conflicts with other chapters. Where changes are made they should be done without introducing new material in the second draft phase. In addition the committee should consider rewording 27.1.4 to positive language. For example: The requirements of chapters x, y and z shall apply unless otherwise noted in this chapter.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement



Statement: The text is revised to provide more positive language.


277 of 365 9/22/2014 2:48 PM


27.3.7.4 Qualification.

27.3.7.4.1

Personnel shall demonstrate qualification by being trained and certified in public emergency alarm reportingsystem design, installation, or service (as appropriate).

27.3.7.4.2

Personnel who are trained and certified for the specific type of public emergency alarm reporting system andcomply with one the following shall be considered qualified:

(1) Personnel who are licensed or certified by a state or local authority, if applicable

(2)

(3) Personnel who are employed and qualified by an organization listed by a nationally recognized testinglaboratory for the design, installation, or servicing of systems within the scope of this chapter

(4)

27.3.7.4.3

Evidence of qualifications and/or certification shall be provided when requested by the authority having jurisdiction.A license or qualification listing shall be current in accordance with the requirements of the issuing authority ororganization.



The correlating committee makes reference to 27.3.7 Personnel Qualification including the modifications implemented by FR 279 and advises that qualification requirements from all other chapters are located in Chapter 10. The correlating committee directs the SIG-PRS committee to consider locating 27.3.7 to the Chapter 10 section on qualifications.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:


Resolution: SR-2-NFPA 72-2014 The committee has relocated all of 27.3.7 not just 27.3.7.4. This material needs to beretained together in context for proper incorporation in Chapter 10.

Statement: The committee has relocated 27.3.7 to new 10.5.6 in order to provide a consistent location for all personnelqualification requirements. The committee has added a "(SIG-PRS)" tag to this section to retain ownership.As a part of this change, all related annex material is to be moved into this new 10.5.6.

The committee has added a placeholder reference in 27.3.7 to point to 10.5.6.


* Personnel who are employed and certified by an equipment manufacturer for the specific type of system


278 of 365 9/22/2014 2:48 PM


27.5.3* Remote Communications Center.

Where the communications center is remotely located from the wired or wireless alarm processing equipment, therequirements of 27.5.3.1 through 27.5.3.8, in addition to all of the requirements of Section 27.5, shall apply.

27.5.3.1

All equipment shall be listed for its intended use and shall be installed in accordance with NFPA 70, NationalElectrical Code.

27.5.3.2

Alarm processing equipment located remote from the communications center shall be capable of providing basicdispatching information independent of the communications center.

27.5.3.3

The alarm processing equipment shall be located where it can be monitored for alarm and trouble conditions andshall be accessible to be manned in case of a pathway or communications failure with the communications center.

27.5.3.4

Wired or wireless alarm repeating systems used to repeat signals between a remote communication center andthe alarm processing equipment location shall meet the requirements of 27.5.3.4.1 through 27.5.3.4.7.

27.5.3.4.1

There shall be a minimum of two complete and independent alarm repeater systems, including batteries and powersupplies, to provide redundancy.

27.5.3.4.2

If the alarm repeater system is configured with one alarm repeater in standby mode, the system shall be capable ofdetecting a communications failure and shall automatically switch to the backup system without interruption or lossof any alarm or trouble transmission.

27.5.3.4.3

Alarm repeater systems shall not be used for any purpose other than alarm communications between thecommunications center and the alarm processing equipment.

27.5.3.4.4

If wireless alarm repeaters are used, they shall operate on a licensed frequency dedicated for this purpose and belicensed to a public entity. Unlicensed frequencies shall not be permitted.

27.5.3.4.5

The communications method used for the alarm repeater, wired or wireless, shall be two-way.

27.5.3.4.6

The public emergency alarm reporting system communications infrastructure shall be used to repeat alarm andtrouble signals between the alarm processing equipment and a remote communications center.

27.5.3.4.7

Where it is not possible to use the public emergency alarm reporting system communications infrastructure toprovide communications between the alarm processing equipment and the remote communications center, analternative repeater method shall be permitted and shall meet the requirements of 27.5.3.4.7.1 and 27.5.3.4.7.2.

27.5.3.4.7.1

If an alternative alarm repeater method is used it shall be publically owned, operated, and controlled.

27.5.3.4.7.2

The alternative alarm repeater method shall meet the requirements of 27.5.3, except 27.5.3.4.2 and 27.5.3.8 shallnot apply.

27.5.3.5

Pathways between the remote communications center and the alarm processing equipment shall be monitored forintegrity and shall be dedicated and not used for any other purpose.

27.5.3.6

When communications between the communications center and the alarm processing equipment fails, therequirements of 27.5.3.6.1 through 27.5.3.6.3 shall apply.

27.5.3.6.1

A pathway or communications trouble condition shall be detected and annunciated at both the communicationcenter and the alarm processing equipment location within 200 seconds and shall meet the requirements of27.5.2.4.


279 of 365 9/22/2014 2:48 PM

27.5.3.6.2

Visual and audible trouble alarm indications pertaining to a pathway or communications failure between thecommunications center and the alarm processing equipment location shall be distinct from all other trouble alarms.

27.5.3.6.3

The alarm processing equipment shall be manned by trained personnel until communications can bere-established.

27.5.3.7

Power supplies shall be provided in accordance with 27.5.2.5.



The correlating committee makes reference to 27.5.3 modified by the action on FR 280 and advises that the title of the section "Remote Communication Center" could be confused with a remote supervising station. The correlating committee directs the SIG-PRS committee to consider modifying the title to something like "Remotely Located Communications Center".

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The committee does not agree that there is confusion between the terms "remote communications center"and "remote supervising station." These terms are used in completely different chapters. The requirementsof 27.5.3 along with the related annex material in A.27.5.3 makes it clear what is meant by "remotecommunications center."


280 of 365 9/22/2014 2:48 PM


29.7.7.6

In a fire/burglar system, the operation shall be as follows:

(1) A fire alarm signal shall take precedence or be clearly recognizable over any other signal, even when thenon-fire alarm signal is initiated first.

(2) Distinctive alarm signals shall be used so that fire alarms can be distinguished from other functions, such asburglar alarms. The use of a common-sounding appliance for fire and burglar alarms shall be permitted wheredistinctive signals are used. The use of distinctive voice signals indicating the type of alarm shall be permitted.


The proposed change does indeed enhance what is already allowed in 29.3.5.2. It has the ability to save lives especially when children are involved. The intelligibility of short messages within 1.5 seconds misses the point. The extended message of a familiar voice, such as a parent, cannot be properly discerned in these brief 1.5 second slices of time.

Related Item

Public Input No. 603-NFPA 72-2013 [New Section after 29.3.5.2]


Submitter Full Name: Louis Fiore

Organization: L. T. Fiore, Inc.

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The current code language already permits voice as proposed in the Public Comment. The TC upholds itsresponse from the Public Input. The submitter has not provided any new or additional substantiation for theadditional text. The submitter is encouraged to provide additional documentation such as performancestandards, peer review studies, etc. in a future PI.


281 of 365 9/22/2014 2:48 PM


29.7.8 Wireless Devices.

29.7.8.1 Wireless Systems.

Household fire alarm systems utilizing low-power wireless transmission of signals within the protected dwelling unitshall comply with the requirements of Section 23.16.

29.7.8.2 Nonsupervised Wireless Interconnected Alarms.

29.7.8.2.1*

To ensure adequate transmission and reception capability, nonsupervised, low-power wireless alarms shall becapable of reliably communicating at a distance of 100 ft (30.5 m) indoors as tested to an equivalent open area testdistance, DEOAT between two devices in accordance with the following equations:

where Lb is the building attenuation factor, a value dependent on the frequency of the wireless transmission. The

building attenuation factor, Lb , represents the maximum attenuation value of typical floors and walls within a

majority of structures. The factor Lb shall assume four walls and two floors and be calculated as follows:

where:

Lw = attenuation value of a wall

= 2 × L 1 + L 2

Lf = attenuation value of a floor

= L 1 + L 2 + L 3 + L 4

L 1 = frequency-dependent attenuation value for 1/2 in. (13 mm) drywall

L 2 = frequency-dependent attenuation value for 11/2 in. (38 mm) structural lumber

L 3 = frequency-dependent attenuation value for 3/4 in. (19 mm) plywood

L 4 = frequency-dependent attenuation value for 1/2 in. (13 mm) glass/tile floor

29.7.8.2.2

Fire alarm signals shall have priority over all other signals.

29.7.8.2.3

The maximum allowable response delay from activation of an initiating device to receipt and alarm/display by thereceiver/control unit shall be 20 seconds.

29.7.8.2.4*

Wireless interconnected smoke alarms (in receive mode) shall remain in alarm as long as the originating unit(transmitter) remains in alarm.

29.7.8.2.5

The occurrence of any single fault that disables a transceiver shall not prevent other transceivers in the systemfrom operating.

29.7.8.3 Mesh Networks.

29.7.8.3.1

Wireless household fire alarm system networks shall meet the requirements of 29.7.8.1.

29.7.8.3.2

Devices used in any critical fire alarm signaling path of a mesh network shall be listed for fire alarm service.

29.7.8.3.3

Shared communications equipment used in supplementary (noncritical) signaling path(s) is permitted to be listedfor communications or information technology use.


282 of 365 9/22/2014 2:48 PM

29.7.8.3.4

All devices and appliances used in the critical fire alarm signaling path of a mesh network shall be listed for usetogether.

29.7.8.3.5

Where the mesh network is shared by other premise operating systems, its operation shall be in accordance withthe following:

(1) Network bandwidth shall be monitored to confirm that all communications between devices critical to theoperation of the fire alarm system take place within 20 seconds; failure shall be indicated within 200 seconds.

(2) All programming accepted by devices in the network shall ensure a fire alarm system alarm response time of20 seconds.

(3) All specified configurations of the network shall ensure a fire alarm system alarm response time of 20seconds.

(4) Failure of any equipment that is critical to the operation of the fire alarm system shall be indicated at theoperator interface of the fire alarm control unit by the annunciation of a trouble signal.

(5) The occurrence of any single fault that disables a transceiver shall not prevent other transceivers in thesystem from operating (formerly 29.7.8.2.5).



low_power_wireless_modifications.docx modifications to low power wireless


The current locations for household wireless resides inside chapter 26. Household fire systems using wireless has grown significantly over the last 10 years and the household committee should be responsible for the oversight of this type of household system.

The primary concern is the supervision characteristics as currently in place. RF technology offers the ability to provide fire alarm protection to almost any type of residence today. The concern is the timing requirements of supervisory check-ins. The use of 200 seconds may actually decrease the system reliability when requiring a senor to check-in every 60 seconds. The use of 200 seconds will increase the traffic of supervisory check-in to exceed over 3 million annually when considering the number of devices monitored. This will drive an increase of unwanted alarms when considering the staggering volume of data being transmitted. There are testing requirements currently in UL for 200 seconds. The ul 985 stp committee voiced similar concern on reliability and the changing the timing parameters. The support in opposition was unanimous with manufactures and users.

Related Item



Submitter Full Name: Richard Simpson

Organization: Vector Security Inc

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected but held

Resolution: The Public Comment includes important new material. It introduces new material to the extent to which thePublic Comment proposes a change that is new or substantial, the complexity of the issues raised andsufficient debate and public review has not taken place.


283 of 365 9/22/2014 2:48 PM

29.7.8.1* Special Requirements for Low-Power Radio (Wireless) Systems.

Household RF Requirements

29.7.8.1.1* Listing Requirements.

Compliance with Section 29.7.8.1 shall require the use of low-power rf radio equipment specifically listed for the purpose.

29.7.8.2 Power Supplies.

Primary battery(s) (dry cell) shall be permitted to be used as the sole power source for devices incorporating a low-power rf 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 the system control unit.

2. The battery(s) shall be capable of operating the low-power radio transmitter/transceiver and its associated 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 of trouble signal operation followed by the signaling of a single non-trouble response. 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, shall automatically re-sound at least once every 4 hours.

4. Catastrophic (open or short) battery failure shall cause a trouble signal identifying the affected low-power radio transmitter/transceiver at the system control unit. When silenced, the trouble signal shall 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 affect any other low-power radio transmitter/transceiver.

29.7.8.3 Alarm Signals.

29.7.8.3.1*

When a wireless initiating device is actuated, its low-power radio transmitter/transceiver shall automatically transmit an alarm signal.

29.7.8.3.2

Each low-power rf radio transmitter/transceiver shall automatically repeat alarm transmissions at intervals not exceeding 60 seconds until the initiating device is returned to its non-alarm condition.

29.7.8.3.3

Signals shall have priority in accordance with 23.8.4.6.

29.7.8.3.4

The maximum allowable response delay from activation of an initiating device to receipt and display by the system control unit shall occur within 10 seconds.

29.7.8.3.5*

A fire alarm signal from a low-power radio transmitter/transceiver shall latch at its system control unit until manually reset and shall identify the particular initiating device in alarm.

29.7.8.4 Monitoring for Integrity.

29.7.8.4.1

The low-power radio transmitter/transceiver shall be specifically listed as using a communication method that is highly resistant to misinterpretation of simultaneous transmissions and to interference (e.g., impulse noise and adjacent channel interference).

29.7.8.4.2

The occurrence of any single fault that disables communication between any low-power radio transmitter/transceiver and the receiver/transceiver system control unit shall cause a latching trouble signal within 200 seconds at the system control unit.

Each rf transmitter shall transmit sensor information at regular intervals as determined by the manufactures instructions.

29.7.8.4.2.1

Each rf transmitter shall be designed to operate in normal condition as part of the household system.

29.7.8.4.2.2

Each rf transmitter shall be capable of operating in degraded mode as a local device in the event of a single failure until the condition is restored.

29.7.8.4.2.3

In the event of multiple failed rf check-ins within the 4 hour window, the system control panel will annunciate a trouble condition and report a loss of rf supervisory to the supervising station.

29.7.8.4.3

A single fault on the signaling channel shall not cause an alarm signal or trouble signal

29.7.8.4.4

The periodic communication required to comply with 23.16.4.2 shall ensure successful alarm transmission capability.

29.7.8.4.4.1

Supervisory rf transmssion is data information shared with the system control unit updating current rf transmitter status.

29.7.8.4.4.2 RF Transmitters and System control units are tuned to operate at specific Radio Frequencies. Manufacturers instruction be followed for specifc RF programing and the failed supervisory events shall not exceed the 4 hour window

29.7.8.4.5

Removal of a low-power rf radio transmitter/transceiver from its installed location shall cause immediate transmission of a distinctive trouble signal that indicates its removal and individually identifies the affected device.

29.7.8.4.6

Reception of any unwanted (interfering) transmission by a retransmission device or by the receiver system control unit for a continuous period of 20 seconds or more shall cause an audible and visible trouble indication at the system control unit. This indication shall identify the specific trouble condition as an interfering signal.

29.7.8.4.7


29.7.8.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 notification appliances 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 Chapter 10, Chapter 12, Chapter 23, or 23.16.4 shall apply.

3. The maximum allowable response delay from activation of an initiating device to activation of required alarm functions shall be 10 seconds.

4. Each transceiver/system control unit shall automatically repeat activated response signals associated with life safety events at intervals not exceeding 60 seconds or until confirmation that the output device has received the alarm signal.

5. The remote devices shall continue to operate (latch-in) until manually reset at the system control unit.

29.7.8.6 RF Initiating Devices

29.7.8.6.1 Rf initiation devices are automatic devices detecting the present of smoke

29.7.8.6.2 RF Devices used to activate an RF Initiating devices shall be programmed as a supervisory signal



Household fire alarm systems utilizing low-power wireless transmission of signals within the protected dwelling unitshall comply with the requirements of Section 23.16, except as modified by 29 . 7.8.1.1.

29.7.8.1.1 The occurrence of any single fault that disables transmission between any low-power radiotransmitter/transciever and the receiver/fire alarm control unit shall cause a latching trouble single within 4 hours atthe household fire alarm control unit/operator interface in accordance with all of the following:

1) The low-power transmitter/transceiver serves a single initiating device

2) Each low-power transmitter/transceiver transmits a check-in signal a minimum of once each hour

3) Where disabling of any retransmission device (repeater) or its transmission does not prevent the receipt ofsignals at the receiver/household fire alarm control unit from any low-power radio transmitter/transceiver.

.


The intent of this public comment is to leave the existing monitoring for integrity (supervision) requirements of household fire alarm system utilizing low-power radio (wireless) transmitters unchanged from that in the 2010 edition and in effect prior to June 2013. Data has been presented that demonstrates an issue with the previous polling period in residential applications. In addition, the increased polling will adversly affect smoke and heat alarms meeting extended 10 year battery life.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The intent of this text is to leave the existing monitoring for integrity (supervision) requirements of householdfire alarm system utilizing low-power radio (wireless) transmitters unchanged from that in the 2010 editionand in effect prior to June 2013. No data has been presented that demonstrates an issue with the previouspolling period in residential applications. The TC adds an 80 minute check-in requirement to ensure at least3 polling attempts in 4 hours.


284 of 365 9/22/2014 2:48 PM



Household fire alarm systems utilizing low-power wireless transmission of signals within the protected dwelling unitshall comply with the requirements of Section 23.16.

1. Revise 29.7.8.1 to read as follows:

Exception: The time period for a low-power radio transmitter with only a single, connected alarm-initiating deviceshall be permitted to be increased to four times the minimum time interval permitted for a 1-second transmissionup to the following:

1) 4 hours maximum for a transmitter serving a single initiating device

2) 4 hours maximum for a retransmission device (repeater), where disabling of the repeater or itstransmission does not prevent the receipt of signals at the receiver/fire alarm control unit from anyinitiating device transmitter.


Based on the below information, the supervision requirements prior to June 30, 2013 for wireless household fire alarm systems should be reinstated in order to prevent a serious shortage of wireless household fire alarm system in the stream of commerce.

The intent of this Public Comment is to reinstate the monitoring for integrity (supervision) requirements of household fire alarm system utilizing low-power radio (wireless) transmitters as they were prior to the 2013 edition. In accordance with the Exception to 23.16.4.2 the supervision requirements of wireless transmitters changed on June 30, 2013 from a polling rate of one transmission per four hours to one transmission every 200 seconds. Reinstating the supervision requirements prior to June 30, 2013 for wireless household fire alarm systems will comply with the existing FCC rules. In accordance with Part 15, section 15.231 of the FCC rules there is no limit on the number of individual transmissions provided the total transmission time does not exceed two seconds per hour.

At present no data has been presented that demonstrates that increasing the existing polling rate to one transmission every 200 seconds for wireless household fire alarm systems will:• Solve an identified problem• Will enhance the safety of the general public • Elevate the reliability of a wireless household fire alarm systemTwo unintended consequences of not reinstating the supervision requirements prior to June 30, 2013 are:1. New installations: Insufficient supply of wireless household systems available in the stream of commerce for new installations. At present only one manufacturer offers a wireless household fire alarm system capable of 200 second polling. This one manufacturer offers the 200 second polling as an option. 2. Replacement of Existing Wireless Smoke Detectors: No supply of wireless smoke detectors in the stream of commerce capable of polling at 200 seconds for replacing the millions of installed smoke detectors.

Related Item



Submitter Full Name: JOHN SLOGICK

Organization: HONEYWELL SECURITY

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



285 of 365 9/22/2014 2:48 PM


Statement: The intent of this text is to leave the existing monitoring for integrity (supervision) requirements of householdfire alarm system utilizing low-power radio (wireless) transmitters unchanged from that in the 2010 editionand in effect prior to June 2013. No data has been presented that demonstrates an issue with the previouspolling period in residential applications. The TC adds an 80 minute check-in requirement to ensure at least3 polling attempts in 4 hours.


286 of 365 9/22/2014 2:48 PM


29.7.8.3 Mesh Wireless Household Networks.

29.7.8.3.1

Wireless household fire alarm system networks systems integrated within a wireless household network shall meetthe requirements of 29.7.8.1.

Exception: Single and multiple station smoke and heat alarms which are not part of a household fire warningsystem are not required to meet the requirements of 29.7.8. 1 and 29.7.8. 3.

29.7.8.3. 2

Devices used in any critical fire alarm signaling path of a mesh network a wireless household network shall belisted for fire alarm service.

29.7.8.3.3

Shared communications equipment used in supplementary (noncritical) signaling path(s) is permitted to be listed forcommunications or information technology use.

29.7.8.3.4

All devices and appliances used in the critical fire alarm signaling path of a mesh network a wirelesshousehold network shall be listed for use together.

29.7.8.3.5

Where the mesh network the wireless household network is shared by other premise operating systems, itsoperation shall be in accordance with the following:

(1) Network bandwidth shall be monitored to confirm that all communications between devices critical to theoperation of the fire alarm system take place within 20 10 seconds; failure shall be indicated within 200seconds.

(2) All programming accepted by devices in the network shall ensure a fire alarm system alarm response time of20 10 seconds.

(3) All specified configurations of the network shall ensure a fire alarm system alarm response time of 20 10seconds.


(5) The occurrence of any single fault that disables a transmitter/ transceiver shall not prevent othertransmitter/ transceivers in the system from operating (formerly 29 . 7.8.2.5).


Revisions are proposed in rsponse to comments voiced at the First Draft meeting. The changes inlcude replacing "mesh' with "wireless household" to make the requirement technology neutral; clarifying that the wireless household network requirements do not apply to smoke and heat alarm multiple station configurations; and that the response time for household fire alarm systems is 10 seconds rather than 20 seconds.

A companion proposal adding a defintion for wireless household networks was submitted.

Related Item





Street Address:

City:

State:

Zip:



287 of 365 9/22/2014 2:48 PM

Committee Statement


Resolution: Section 29.7.8.3 was deleted by SR-47.


288 of 365 9/22/2014 2:48 PM

Public Comment No. 201-NFPA 72-2014 [ Sections 29.7.8.3.2, 29.7.8.3.3, 29.7.8.3.4, 29.7.8.3.5 ]

Sections 29.7.8.3.2, 29.7.8.3.3, 29.7.8.3.4, 29.7.8.3.5

29.7.8.3.2


29.7.8.3.3

Shared communications equipment used in supplementary (noncritical) signaling path(s) is permitted to be listedfor communications or information technology use.

29.7.8.3.4


29.7.8.3.5

Where the mesh network is shared by other premise operating systems, its operation shall be in accordance withthe following:

(1) Network bandwidth shall be monitored to confirm that all communications between devices critical to theoperation of the fire alarm system take place within 20 seconds; failure shall be indicated within 200 seconds.

(2) All programming accepted by devices in the network shall ensure a fire alarm system alarm response time of20 seconds.

(3) All specified configurations of the network shall ensure a fire alarm system alarm response time of 20seconds.


(5) The occurrence of any single fault that disables a transceiver shall not prevent other transceivers in thesystem from operating (formerly 29.7.8.2.5 ).


As written, the mesh network requirements would create a level of supervision far in excess of what is currently required for single and multiple station devices. Section 29.7.8.3.5, for example, would require supervision comparable to a system when alarms are connected to non-fire related equipment.

Related Item



Submitter Full Name: Wendy Gifford

Organization: Consultant

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: While the TC had hoped to establish minimum guidelines for emerging wireless technologies, it becameevident during the comment and revision process that changes in these technologies and products areaccelerating. Drafting language that will ensures a level of safety and still allow for future innovation willrequire knowledge of communication techniques.


289 of 365 9/22/2014 2:48 PM

It was believed that many developers/manufacturers/suppliers/listing agencies would come forward withexpertise in the area during the Public Comment period. This was not the case. The TC deletes the text of29.7.8.3 as the concept is not sufficiently developed to move forward with requirements to the Code.

It is imperative to include wireless network communications experts beyond the life safety community inorder to develop effective and enforceable language. To write requirements prematurely risks unintendedconsequences for technological progress and life safety.


290 of 365 9/22/2014 2:48 PM


29.8.3.4 Specific Location Requirements.

The installation of smoke alarms and smoke detectors shall comply with the following requirements:

(1) Smoke alarms and smoke detectors shall not be located where ambient conditions, including humidity andtemperature, are outside the limits specified by the manufacturer's published instructions.

(2) Smoke alarms and smoke detectors shall not be located within unfinished attics or garages or in other spaceswhere temperatures can fall below 40ºF (4ºC) or exceed 100ºF (38ºC).

(3)

(4)

(5) Effective January 1, 2019, smoke alarms and smoke detectors used in household fire alarm systems installedbetween 6 ft (1.8 m) and 20 ft (6.1 m) along a horizontal flow path from a stationary or fixed cookingappliance shall be listed for resistance to common nuisance sources from cooking.

(6)

(7) Smoke alarms and smoke detectors shall not be installed within a 36 in. (910 mm) horizontal path from thesupply registers of a forced air heating or cooling system and shall be installed outside of the direct airflowfrom those registers.

(8) Smoke alarms and smoke detectors shall not be installed within a 36 in. (910 mm) horizontal path from the tipof the blade of a ceiling-suspended (paddle) fan.

(9) Where stairs lead to other occupiable levels, a smoke alarm or smoke detector shall be located so that smokerising in the stairway cannot be prevented from reaching the smoke alarm or smoke detector by anintervening door or obstruction.

(10) For stairways leading up from a basement, smoke alarms or smoke detectors shall be located on thebasement ceiling near the entry to the stairs.

(11)

(12) Smoke alarms and detectors installed in rooms with joists or beams shall comply with the requirements of17.7.3.2.4.

(13) Heat alarms and detectors installed in rooms with joists or beams shall comply with the requirements of17.6.3.


The Automatic Fire Alarm Association (AFAA) supports the Committee’s decision and substantiation to extend the effective date for a cooking resistant listing in section 29.8.3.4(5). Unwanted alarms are the leading cause of occupants disabling their smoke alarms and roughly 20% of all smoke alarms installed in U.S. homes have been disabled. The 20% number may be higher in high-risk areas, such as inner cities and rural communities. Disconnecting the power from a smoke alarm will leave the dwelling unit/building partially or completely unprotected. Unwanted alarms cause the fire departments time,

* Where the mounting surface could become considerably warmer or cooler than the room, such as a poorlyinsulated ceiling below an unfinished attic or an exterior wall, smoke alarms and smoke detectors shall bemounted on an inside wall.

* Smoke alarms and smoke detectors shall not be installed within an area of exclusion determined by a 10 ft(3.0 m) radial distance along a horizontal flow path from a stationary or fixed cooking appliance, unless listedfor installation in close proximity to cooking appliances. Smoke alarms and smoke detectors installedbetween 10 ft (3.0 m) and 20 ft (6.1 m) along a horizontal flow path from a stationary or fixed cookingappliance shall be equipped with an alarm-silencing means or use photoelectric detection.

Exception: Smoke alarms or smoke detectors that use photoelectric detection shall be permitted forinstallation at a radial distance greater than 6 ft (1.8 m) from any stationary or fixed cooking appliance whenthe following conditions are met:

(a) The kitchen or cooking area and adjacent spaces have no clear interior partitions or headers and

(b) The 10 ft (3.0 m) area of exclusion would prohibit the placement of a smoke alarm or smoke detectorrequired by other sections of this code.

* Smoke alarms and smoke detectors shall not be installed within a 36 in. (910 mm) horizontal path from adoor to a bathroom containing a shower or tub unless listed for installation in close proximity to suchlocations.

* For tray-shaped ceilings (coffered ceilings), smoke alarms and smoke detectors shall be installed on thehighest portion of the ceiling or on the sloped portion of the ceiling within 12 in. (300 mm) vertically down fromthe highest point.


291 of 365 9/22/2014 2:48 PM

money and endanger the lives fire fighters and the public. Every year several fire fighters and civilians lose their life during a false dispatch. Reducing unwanted alarm activations will enhance public life safety and reduce firefighter injuries. Therefore it is imperative that the required technical data is gathered to determine if repeatable performance test protocols can be added to the ANSI smoke detection products standards by the January 1, 2019 date.

Related Item




Organization: Automatic Fire Alarm Association

Affilliation: Automatic Fire Alarm Association

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The TC rejects the PC as the submitter has not provided any change to the text. However, the TCrecognizes their concurrence with the First Draft action.


292 of 365 9/22/2014 2:48 PM

Public Comment No. 128-NFPA 72-2014 [ New Section after A.3.3.66.19 ]

Device (Class N)

Class N devices includes 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., drycontact, audible/visual alert/notification, addressable speaker), that are required to provide the real-timefunctionality necessary for the protection of life and property. In this way a component connected to thenetwork used for non-critical functions (i.e., maintenance) may be differentiated and excluded from themonitoring for integrity requirements of class N.

Also in this way, transport equipment (e.g., switches, routers, hubs, media converters ) and otherequipment (e.g., printers, storage devices) may be differentiated from the requirements applied to class Ndevices, if they do not provide life safety specific environmental monitoring, inputs, or outputs for the lifesafety system. This is not to say that this equipment is not important to the overall operation of thesystem, just that this equipment is not considered a “device” in the context of Class N. Equipment thatdoes not meet the definition of a device may not be specifically supervised, but rather generallysupervised as they are part of the supervised pathways that service the Class N devices themselves.


Additional clarification for the definition of “device” as it relates to class N was warranted to both illustrate examples of what is a class N device and what is not and how the distinction is drawn.The proposal is the recommendation by the Correlating Committee Task Group members thatwas comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of thecommittees.Wayne MooreA.J. CapowskiJoe L. CollinsDan HoronVic HummMichael PallettCharles PughRobert SchifilitiAviv SiegelLarry ShudakBob ElliottPaul CrowleyJeff SilveiraJeff KnightAndrew Berezowski




Related Item





Street Address:

City:

State:

Zip:



293 of 365 9/22/2014 2:48 PM

Committee Statement

CommitteeAction:



Statement: With the addition of Class N pathways in the first draft, the term “device” was used with specificity in thecontext of Class N, but not defined. This revision also adds related annex to illustrate examples of what is aClass N device and how the distinction is drawn.


294 of 365 9/22/2014 2:48 PM

Public Comment No. 130-NFPA 72-2014 [ New Section after A.3.3.91 ]

Endpoint (Class N)

An endpoint device originates and/or terminates a communication stream, and does not forward it to other devices.

An FACU, ACU, ECCU endpoint originates and/or terminates a communication stream with autonomy. If data issent to, or received from other locations, that communications stream forms a new path. The new path may evenemploy a different communications protocol, and where permitted, have a different Pathway Class Designation asdefined in 12.3.

The exception in section 12.3.6(1) shows Class N communication paths do not require redundant paths whenconnected to a single endpoint device. However, connections to an FACU, ACU or ECCU must be redundant evenwhen those elements are an endpoint on a Class N communication path, with the excepted allowance of 20 feetinside a raceway or enclosure defined in 12.6.9.


Additional clarification for the definition of “endpoint” as it relates to class N was warranted to explain the distinction between endpoints that are devices and endpoints that are control units, and their relationship to communications.The proposal is the recommendation by the Correlating Committee Task Group members thatwas comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of thecommittees.Wayne MooreA.J. CapowskiJoe L. CollinsDan HoronVic HummMichael PallettCharles PughRobert SchifilitiAviv SiegelLarry ShudakBob ElliottPaul CrowleyJeff SilveiraJeff KnightAndrew Berezowski



Public Comment No. 129-NFPA 72-2014 [New Section after 3.3.92]

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

Committee Rejected but see related SR


295 of 365 9/22/2014 2:48 PM

Action:


Statement: With the addition of Class N pathways in the first draft, the term “endpoint” was used with specificity in thecontext of Class N, but not defined. Related annex material is also added.


296 of 365 9/22/2014 2:48 PM

Public Comment No. 35-NFPA 72-2014 [ Section No. A.3.3.131 ]

A.3.3.131 In-writing.

In-writing communication is a letter, fax, email, or other means of documented transfer of information from oneentity to another. This does not apply to written documents required, such as system layouts or marked drawings.


You cannot put an exception in an Annex item. Besides it is poorly worded:"This does not apply to written documents required, such as system layouts or marked drawings." Is it "written documents required" or "required written documents"? And, how can it sat that written documents are not written documents if the are written required documents?

Related Item





Street Address:

City:

State:

Zip:


Committee Statement



Statement: The second sentence was poorly written and included conflicting statements.


297 of 365 9/22/2014 2:48 PM


A.10.5.1.1

State and local licensure regulations should be followed to determine qualified personnel. Depending on the stateof local licensure regulations, qualified personnel may include, but not be limited to, one or more of the following:

(1) Personnel who are registered, licensed or certified by a state or local authority(2) Personnel who are certified by an organization acceptable to the authority having jurisdiction

(3) Personnel who are trained and certified by the manufacturer or the manufacturer's agent for fire alarm systemdesign and/or emergency communication system design of the specific type and brand of system and who areacceptable to the authority having jurisdiction





Public Comment No. 145-NFPA 72-2014 [Section No. 10.5.1.2]This PC deletes the text from the body of thecode


Public Comment No. 151-NFPA 72-2014 [New Section afterA.10.4.4]



Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected



298 of 365 9/22/2014 2:48 PM


A.10.5.2.1

State or local licensure regulations should be followed to determine qualified personnel. Depending on state or locallicensure regulations, qualified personnel may include, but not be limited to, one or more of the following:


(2) Personnel who are certified by an organization acceptable to the authority having jurisdiction

(3) Personnel who are trained and certified by the manufacturer or the manufacturer's agent for fire alarm systeminstallation and/or emergency communications system installation of the specific type and brand of system andwho are acceptable to the authority having jurisdiction







similar

Public Comment No. 150-NFPA 72-2014 [Section No. 10.5.2.2]This PC deleted the text from the body of thecode



Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected



299 of 365 9/22/2014 2:48 PM


A.10.4.4

The fire alarm control units that are to be protected are those that provide notification of a fire to the occupants andresponders. The term fire alarm control unit does not include equipment such as annunciators and addressabledevices. Requiring smoke detection at the transmitting equipment is intended to increase the probability that analarm signal will be transmitted to a supervising station prior to that transmitting equipment being disabled due tothe fire condition.

CAUTION: Exception No. 1 to 10.4.4 permits the use of a heat detector if ambient conditions are not suitable forsmoke detection. It is important to also evaluate whether the area is suitable for the control unit.

Where the area or room containing the control unit is provided with total smoke detection coverage, additionalsmoke detection is not required to protect the control unit. Where total smoke detection coverage is not provided,the Code intends that only one smoke detector is required at the control unit even when the area of the room wouldrequire more than one detector if installed according to the spacing rules in Chapter 17. The intent of selectivecoverage is to address the specific location of the equipment.

The location of the required detection should be in accordance with 17.7.3.2. 1.


The reference to 17.7.3.2.1 is incomplete. Placement of detectors in proximity to the equipment should be taken into account as permitted by 17.7.3.2.3.3.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: Changing the reference to 17.7.3.2 would include requirements for area detection and spacing. The intentof this requirement is for a single detector to protect the control unit.


300 of 365 9/22/2014 2:48 PM


A.10.4.4




The location of the required detection should be in accordance with 17.7.3.2.1 .


This is editorial to match the reference in 10.4.4.

Related Item



Submitter Full Name: John McCamish

Organization: NECA IBEW Electrical Training

Affilliation: IBEW

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: Changing the reference to 17.7.3.2 would include requirements for area detection and spacing. The intentof this requirement is for a single detector to protect the control unit.


301 of 365 9/22/2014 2:48 PM


A.10.4.4




The location of the required detection should be in accordance with 17.7.3.2.1.


The requirement to provide notification of a fire condition prior to a control unit(s) or equipment used for transmitting notification signals being attacked by fire is equally, or in some instances more critical in an ECS or MNS system. This is a "fundamental" requirement that should apply to all signaling system notification equipment located in areas that are not continuously occupied as specified in 10.4.4. Also see related Public Comment 72-71.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted


Statement: The requirement to provide notification of a fire condition prior to a control unit(s) or equipment used fortransmitting notification signals being attacked by fire is equally, or in some instances more critical in an ECSor MNS system. This is a "fundamental" requirement that should apply to all signaling system notificationequipment located in areas that are not continuously occupied as specified in 10.4.4. This correlates with therevisions in 10.4.4.


302 of 365 9/22/2014 2:48 PM


A.10.5.3

It is not the intent to require personnel performing simple inspections or operational tests of initiating devices torequire factory training or special certification, provided such personnel can demonstrate knowledge in these areas.

Qualified personnel may include, but not be limited to, one or more of the following:

(1) * Personnel who are trained and certified by the manufacturer or the manufacturer's agent for the specific typeand brand of system being serviced

(2) * Personnel who are certified by an organization acceptable to the authority having jurisdiction

(3) * Personnel, either individually or through employment, that is registered, licensed, or certified by a state orlocal authority to perform service on systems addressed within the scope of this Code

(4) Personnel who are employed and qualified by an organization listed by a testing laboratory for the servicing ofsystems within the scope of this Code







similar



similar

Public Comment No. 152-NFPA 72-2014 [Section No. 10.5.3]this PC deletes the text from the body of thecode

Related Item





Street Address:

City:

State:

Zip:


Committee Statement


Resolution: Mandatory material is retained in the main body of the document.


303 of 365 9/22/2014 2:48 PM

Public Comment No. 161-NFPA 72-2014 [ Section No. A.10.5.3.4(1) ]

A.10.5.3.4(1)

Factory training and certification is Certification by the manufacturer or the manufacturer's agent is intended toallow an individual to service equipment only for which he or she has specific brand and model training.





Public Comment No. 77-NFPA 72-2014 [Section No. 10.5.3.4] aligns with changes to the body of the code

Related Item





Street Address:

City:

State:

Zip:


Committee Statement


Resolution: The terms "factory trained and certified" is current verbiage used by UL.


304 of 365 9/22/2014 2:48 PM


A.10.5.3.4(2)

Nationally recognized fire alarm certification Certification programs might include those programs offered by theInternational Municipal Signal Association (IMSA), National Institute for Certification in Engineering Technologies(NICET), and the Electronic Security Association (ESA). NOTE: These organizations and the products or servicesoffered by them have not been independently verified by the NFPA, nor have the products or services beenendorsed or certified by the NFPA or any of its technical committees.





Public Comment No. 157-NFPA 72-2014 [Section No. 10.5.3.4] aligns annex with the body of the code

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: Current state and local licensing acknowledge and recognize that there are many state and localorganizations that provide continuing education that are acceptable to the authority having jurisdiction.


305 of 365 9/22/2014 2:48 PM


A.10.12. 3 2

The intent of this requirement is to ensure that hearing-impaired persons are alerted to seek additional informationregarding an emergency situation. Hearing-impaired persons might not be able to hear alerted by the speakernotification appliances that provide evacuation tones or voice instructions. It is intended that the speakers andvisible devices located in the same area be activated together whenever tones, recorded voice instructions, or livevoice instructions are being provided.


This annex material should be associated with 10.12.2 as indicated in the committee statement for FR-363

Related Item





Affilliation: SIG-ACC Strobe Operation TG

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted


Statement: This annex material should be associated with 10.12.2 as indicated in the committee statement forFR-363. The text was editorially revised.


306 of 365 9/22/2014 2:48 PM

Public Comment No. 181-NFPA 72-2014 [ Section No. A.10.13 ]

A.10.13

It is the intent that both visual and audible appliances are shut off when the notification appliance silence feature isactivated on the fire alarm control unit.

Per the ADA, it is important not to provide conflicting signals for the hearing or visually impaired.


The continuation of visible signals in a building when the fire alarm system is activated does not create conflicting signals and does not conlict withthe ADA. Some fire dpeartments wnat the visual signals to continue while investigation activies or fire fighting activies are carried out to preclude occupants from thinking that the fire alarm is clear. The Code allows various combination sof visible and audible signals. This annex material is incorrect and should be deleted.

Related Item

First Revision No. 263-NFPA 72-2013 [New Section after A.10.13]



Organization: Arup

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The existing text for 10.13 requires audible and visible occupant alerting notification appliances to beactivated and deactivated simultaneously. Explanatory material associated with the requirement isappropriate. No substantiation was provided to prove that the requirement is in conflict with ADArequirements.


307 of 365 9/22/2014 2:48 PM


A.10.13.2

Where it is desired to deactivate the notification appliances for fire service operations and also provide notificationthat the fire inside the building and signal evacuated occupants that an alarm is still active present , it isrecommended that a separate non ? silenceable notification zone be provided that is non-silenceable with on theexterior of the building. The audible and visible notification appliances outside each entrance to the protectedbuilding or space. These notification appliances located at the building entrances could serve as a warningsignal to prevent occupant re-entry during fire service operations reentry .


Revised wording for better clarity

Related Item

First Revision No. 263-NFPA 72-2013 [New Section after A.10.13]




Street Address:

City:

State:

Zip:


Committee Statement



Statement: Revised wording for improved clarity.


308 of 365 9/22/2014 2:48 PM

Public Comment No. 158-NFPA 72-2014 [ Section No. A.12.3.6(1) ]

A.12.3.6(1)


309 of 365 9/22/2014 2:48 PM

Class N consists of pathways between control equipment and devices. The pathways comprise metallic conductorcommunications cable, such as a 100 ohm balanced twisted-pair (e.g., Category 5E), including single-pair ormulti-pair cable, or other communications media such as optical fiber cable or wireless transmission, or acombination of two or more of these. Pathways consist of uninterrupted communications media between controlequipment and an endpoint device or of a network of multiple interconnected communications media pathwaysegments connecting multiple devices. Media pathway segments are created by the use of transmission equipmentsuch as Ethernet switches, wireless repeaters, or media converters that interrupt an otherwise continuous pathway.Requirements for Class N pathway transmission equipment are not covered in Chapter 12 but by other chapters inNFPA 72.

A network of pathway segments is also described as primary pathway segments, redundant pathway segments, ornondesignated pathway segments. Primary and redundant pathways, from control equipment to each device, areindependently and continuously verified for their ability to support end-to-end communications to and from eachendpoint device. Each device will be provided a primary pathway consisting of one or more pathway segments. Forprimary pathway segments that service more than one device, additional redundant pathway segments providealternate verified communication pathways to the devices. Should any primary pathway segment fail, communicationis supported by the redundant pathway segments. Should either a primary or redundant pathway segment fail,trouble will be indicated by virtue of the continuous verification of all primary and redundant pathway segments. Theredundant pathway segments are generally independent and do not normally share media with the primarypathways. However, there are exceptions, such as different frequencies for wireless or ring topologies. [SeeA.12.3.6(5).]

There is an opportunity to enhance the robustness of a Class N network by providing physically distinct pathwaysegments (i.e., an alternate conduit, or cable tray route, or wireless transmission frequency range, or a combinationof distinct media). It is also permissible to provide other nondesignated pathway segments. Additional pathwaysegments in excess of the minimum requirements of Class N increase the overall robustness of the network and areoften desirable. However, since these additional pathway segments exceed the minimum equipment standards,there is no intention to create an additional monitoring burden, so verification of these pathways is optional.

For Class N, where a conductor-based media is used, it is not the intention to monitor faults on individual conductorsbut rather to monitor the operational capability and performance of the pathway as a whole. Unlike Class C, wheremultiple pathways are not required, for Class N some pathway segments that carry communications for multipledevices (such as Ethernet uplinks or backbones) will have redundant pathway segments present. The intention isthat any one pathway segment can fail without a loss in operational capability to more than one device. For example,connections to control equipment (fire alarm control units, ACUs, or ECCUs), where any interruption incommunications could potentially affect all devices, would have redundant pathway segments. Additionally,backbone and uplink pathway segments that support communications for more than one device and are positionedbetween transmission equipment would also have a redundant pathway segment. But the requirement for redundantpathway segments does not apply to those pathway segments used to service a single device [see FigureA.12.3.6(1)(a) ] .

The term devices is used generically in this section to refer to endpoint devices, which include the following:

(1) Input components such as alarm initiating switches, sensors

(2) Output components such as Ethernet speakers (i.e., IEEE 802.3af PoE speakers), strobes, textual signage,audio amplifiers

Transmission equipment (e.g., media converters, Ethernet switches, patch panels, cross-connects) are notconsidered devices with respect to Class N pathways.

The audio amplifier example is included to explain a type of addressable device that can receive a digital audio inputfrom the Class N pathway but provide a notification appliance circuit (NAC) output to support Class A, B, or Xspeaker connections. Other similar devices are also possible to provide alternate class pathway connections forstrobes (NACs) or initiating devices (IDCs). From the perspective of the Class N pathway, this is considered anendpoint device. However, since these types of endpoints can support multiple notification appliance devices orinitiating devices, they are subject to the redundant pathway segment requirement and are provided with dualpathway connections.

Control equipment connected to a Class N network for communications with devices would generally utilizeredundant pathway segments. Control equipment connected to other control equipment on a Class N network wouldutilize redundant pathway segments if the control equipment was dependent on any of the pathway segments sothat a failure of a primary pathway segment in between control equipment could impair the operation of the controlequipment [see Figure A.12.3.6(1)(b) ] .

Another utilization of endpoints is permitted for devices providing two connection ports and supporting dual pathwaysegment connections. The description of endpoint devices is not intended to exclude devices that support dualpathway connections. Since these pathways are servicing a single device, only a single primary pathway connectionis required. The second pathway connection exceeds minimum equipment standards and is therefore not required to


310 of 365 9/22/2014 2:48 PM

be verified as a redundant pathway segment; it can be considered connected to a nondesignated pathway segment[see Figure A.12.3.6(1)(c) ] .

Figure A.12.3.6(1)(a) Class N Pathway Block Diagram.

Figure A.12.3.6(1)(b) Class N Pathway Block Diagram with Multiple Control Units.

Figure A.12.3.6(1)(c) Class N Pathway Block Diagram with Device with Dual Pathway Connection.


311 of 365 9/22/2014 2:48 PM

with subsequent subsections and drawings should be replaced with attached PDF. This material was created by the TCCTask Group on Networks.



Class_N_Annex_Submitted_by_Task_Group_May_13_.pdfA.12.3.6(1) text and drawings are included in PDF.


Revised for clarity and consistency with Code.

Related Item



Submitter Full Name: Daniel Horon

Organization: CADgraphics, Incorporated

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: Editorial and organizational changes were made for improved readability and clarity. Drawings werechanged to make the style more similar to Annex F.

Examples of a comparison between Class N and Class X and Class C were added. Also a clarificationthat class N is not required for supplemental reporting was added.


312 of 365 9/22/2014 2:48 PM

A.12.3.6(1) The Class N pathway designation is added to specifically address the use of modern network

infrastructure when used in fire alarm and emergency communication systems.

Ethernet network devices are addressable, but with an important distinction from device addresses on a

traditional SLC multi‐drop loop. A device with an Ethernet address is, in most cases, a physical endpoint

connected to a dedicated cable. Traditional SLC devices are all wired on the same communication line (in

parallel) similar to an old party‐line telephone system. By comparison, Ethernet’s network switches

direct each data packet to its intended recipient device like our modern phone systems.

A fundamental technical difference of Class N from Class A, B or X is that it has no requirement to report

a connection to ground unless the ground impairs the path. A practical concern, where using Ethernet, is

that it is reliable and secure, especially when life safety systems share the same pathways. See 23.6.3

Class N Shared Pathways.

As a visual model, Class N could be likened to a Class X [backbone], allowed to have Class C branch paths

to single endpoint devices. Therefore, every effort is made in this section to clearly distinguish the single

endpoint device from the transport equipment required to have redundant paths, like Class X.

Class N requires, redundant, monitored pathway segments to and from control equipment (fire alarm

control units, ACUs, or ECCUs), where any interruption in communications could potentially affect

multiple endpoint devices.

Typically, interconnected communications equipment such as Ethernet switches, wireless repeaters, or

media converters are used in combination to create pathways. Chapter 12 describes the required

behavior of Class N pathways. All equipment must meet the requirements of other chapters in NFPA 72.

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 and

allow two parallel connections. For compliance with Class N, a trouble must be reported if either of

these connections fails. [See Figure A.12.3.6(1)(a‐1).]

Class N networks may be specified for ancillary functions, but are not required for supplemental

reporting described in 23.12.4. [See Figure A.23.12.4.]

Class N pathways may use metallic conductor communications cable, such as a 100 ohm balanced

twisted pair (e.g., Category 5E), including single‐pair or multi‐pair cable, or other communications media

such as optical fiber cable or wireless transmission, or a combination of two or more such transport

mediums.

Where a conductor‐based media is used for Class N, the intention is not to monitor faults on individual

conductors, but rather to monitor the operational capability and performance of the pathway as a

whole. Similar to Class C, end‐to‐end verification is used in Class N.

Primary and required redundant pathways are independently and continuously verified for their ability

to support end‐to‐end communications to and from each endpoint device and its associated control

equipment. Pathway segments that service more than one device, must have at least one verified

redundant pathway segment. Should any primary pathway segment fail, communication is supported by

the redundant 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

primary pathways. However, there are exceptions, such as different frequencies for wireless

components, or ring topologies. [See Figure A.12.3.6(5).]

A Class N network may be made more reliable with physically distinct pathway segments (i.e., an

alternate conduit, 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 to have nonrequired segments. [See Figure A.12.3.6(1)(a‐3).] Additional

nonrequired pathway segments are allowed to be connected and not independently monitored for

integrity as long as two paths are monitored to meet the redundancy requirement of Class N.

Figure A.12.3.6(1)(a) Class N Pathway Block Diagrams.

SwitchFACU,ACU, orECCU

Switch

Switch Switch

Switch

Endpoint Devices

Switch

1 2

4 3

1 2

A redundant cable between two switches must have specialfunctionality in order to monitor integrity when a secondary

path is not in use.

20 Feet maximum insideenclosure or raceway

Endpoint Devices Group H

Endpoint Devices Group J

20 Feet maximum insideenclosure or raceway

Figure A.12.3.6(1)(a-1)

Figure A.12.3.6(1)(a-2) Endpoint Devices Group K

Nonrequired redundantpath segment

FACU,ACU, orECCU

Traditionally, NFPA has used the word device for input components, and term appliance for components

used 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 N

devices include:

(1) Input components such as alarm initiating modules switches and sensors,

(2) Output components such as output modules, Ethernet speakers (i.e., IEEE 802.3af PoE speakers),

intelligent strobes, textual signage, and intelligent audio amplifiers.

Transmission equipment components (e.g., media converters, Ethernet switches, patch panels,

cross‐connects) are connected to the Class N pathway merely to transport instructions between other

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 audio

input from the Class N pathway and then provide a notification appliance circuit (NAC) output with Class

A, B, or X pathways. Other endpoint devices may similarly provide alternate Class pathways for strobes

(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 support multiple

notification appliance devices or initiating devices, they are subject to the redundant pathway

requirement.

A single component may provide two distinct functions in a life safety system. For example, one

component may house both a fire sensor and a notification device. Or, an addressable input module

may provide for two distinct inputs from a waterflow switch and a tamper switch. Class N requires both

a primary and redundant path to these dual‐purpose components.

Class N connections between control equipment are required to have redundant monitored pathway

segments if a failure of a primary pathway segment in between control equipment could impair the

operation of the control equipment [see Figure A.12.3.6(1)(b) ].


Switch3

Figure A.12.3.6(1)(b)

Switch2

Switch1

FACU,ACU, orECCU

FACU,ACU, orECCU

FACU,ACU, orECCU

(1)

(2)

(3)

Class N is also permitted to include dual port devices that provide both transmission and input/output

functions. Endpoint devices may have multiple connection ports and support dual pathway segment

connections; thus the term endpoint device is not intended to prohibit more than one connection to a

device. Even with dual connections, where other devices depend on the path, primary and redundant

paths are required. But, where an endpoint device has two connection ports, and when a secondary

nonrequired connection is added, there is no requirement to separately supervise the nonrequired

redundant pathway segment [see Figure A.12.3.6(1)(c)].


A nonrequired redundant cable to an endpoint device is permitted, and does not require separate supervision.

Figure A.12.3.6(1)(c)

A.12.3.6(4)

Operational conditions of the pathway include factors such as latency, throughput, response time,

arrival rate, utilization, bandwidth, and loss. Life safety equipment connected to a Class N network

actively monitors some or all of the pathway’s operational conditions, so that an improperly installed or

configured pathway, or a subsequently degraded pathway or segment is detected by the life safety

equipment and reported as a trouble. The trouble condition is reported when operational conditions of

the pathway(s) have deteriorated to the point where the equipment is no longer capable of meeting its

minimum performance requirements, even if some level of communication to devices is still maintained.

Performance requirements include the activation of an alarm within 10 seconds, the reporting of a

trouble signal within 200 seconds, synchronization of strobes, and delivery of audio messages with

required intelligibility.

End‐to‐end communications might be operational under system idle conditions, but in the event of an

alarm, the increased load on a degraded pathway could cause a partial or complete failure to deliver

required life safety signals. Such predictable failure must be actively detected and reported.

A.12.3.6(5)

Devices with dual path connections are permitted to be connected in a daisy‐chain of devices on a ring.

Again, where Class N pathway segments support multiple devices, verified redundant pathway

segment(s) are required. This can be accomplished with a ring topology, as long as each segment of the

ring is verified as functional, and the failure of any one segment does not result in the loss of

functionality of more than one device. In this arrangement, primary and redundant pathway segments

share the same media, and provide two possible directions of communications in a ring topology [see

Figure A.12.3.6(5) ]. This daisy‐chain configuration is also permitted between multiple control units that

require verified primary and redundant pathway segments.

Endpoint Devices

Switch

To FACU

Figure A.23.12.4 Supplemental Reporting Network

Computer 2

Ethernet Network

Computer 1

Fire AlarmControl Unit

Brand Z


Brand Y


Brand X

Handheld

To UL ListedMonitoring

Proprietary SLCCommunications


Proprietary SLCCommunications


Proprietary SLCCommunicationsFigure A.23.12.4

Figure A.12.3.6(5) Class N Pathway Block Diagram with Daisy‐Chained Devices with Dual Pathway

Connection.

Communications continues from either direction in a ring topology.

Figure A.12.3.6(5)

Endpoint Devices

Switch 1

To FACU

Switch 2

with dual pathwayconnectors



313 of 365 9/22/2014 2:48 PM

A.12.3.6(1)


314 of 365 9/22/2014 2:48 PM

Class N consists of pathways between control equipment and devices. The pathways comprise

A.12.3.6(1) The Class N pathway designation is added to specifically address the use of modernnetwork infrastructure when used in fire alarm and emergency communication systems.

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.

A fundamental technical difference of Class N from Class A, B or X is that it has no requirement to reporta connection to ground unless the ground impairs the path. A practical concern, where using Ethernet, isthat it is reliable and secure, especially when life safety systems share the same pathways. See 23.6.3Class N Shared Pathways.

As a visual model, Class N could be likened to a Class X [backbone], allowed to have Class C branchpaths to single endpoint devices. Therefore, every effort is made in this section to clearly distinguish thesingle endpoint device from the transport equipment required to have redundant paths, like Class X.

Class N requires, redundant, monitored pathway segments to and from control equipment (fire alarmcontrol units, ACUs, or ECCUs), where any interruption in communications could potentially affectmultiple endpoint devices.

Typically, interconnected communications equipment such as Ethernet switches, wireless repeaters, ormedia converters are used in combination to create pathways. Chapter 12 describes the requiredbehavior of Class N pathways. All equipment must meet the requirements of other chapters in NFPA 72.

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-1).]

Class N networks may be specified for ancillary functions, but are not required for supplementalreporting described in 23.12.4. [See Figure A.23.12.4.]

Class N pathways may use metallic conductor communications cable, such as a 100 ohm balancedtwisted

-

pair (e.g., Category 5E), including single

-

pair or multi-pair cable, or other communications media such as optical fiber cable or wirelesstransmission, or a combination of two or more

of these. Pathways consist of uninterrupted communications media between control equipment and an endpointdevice or of a network of multiple interconnected communications media pathway segments connecting multipledevices. Media pathway segments are created by the use of transmission equipment such as Ethernet switches,wireless repeaters, or media converters that interrupt an otherwise continuous pathway. Requirements for Class Npathway transmission equipment are not covered in Chapter 12 but by other chapters in NFPA 72.A network ofpathway segments is also described as primary pathway segments, redundant pathway segments, ornondesignated pathway segments. Primary and redundant pathways, from control equipment to each device,

such transport mediums.

Where a conductor-based media is used for Class N, the intention is not to monitor faults on individualconductors, but rather to monitor the operational capability and performance of the pathway as a whole.Similar to Class C, 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 communications to and from each endpoint device

. Each device will be provided a primary pathway consisting of one or more pathway segments. For primarypathway segments

and its associated control equipment. Pathway segments that service more than one device,

additional redundant pathway segments provide alternate verified communication pathways to the devices

must have at least one verified redundant pathway segment . Should any primary pathway segment fail,communication is supported by the redundant pathway


315 of 365 9/22/2014 2:48 PM

segments. Should

segment(s.) Failure of either a primary or redundant pathway

segment fail, trouble will be indicated by virtue of the continuous verification of all primary and redundant pathwaysegments. The redundant

will indicate a trouble.

Redundant pathway segments are generally independent and do not normally share media with theprimary pathways. However, there are exceptions, such as different frequencies for wirelesscomponents, or ring topologies. [See Figure A.12.3.6(5).]

There is an opportunity to enhance the robustness of a

A Class N network

by providing

may be made more reliable with physically distinct pathway segments (i.e., an alternate conduit, or cabletray route, or wireless transmission frequency range, or a combination of distinct media).

It is also permissible to provide other nondesignated pathway segments. Additional pathway segments in excessof the minimum requirements of Class N increase the overall robustness of the network and are often desirable.However, since these additional pathway segments exceed the minimum equipment standards, there is nointention to create an additional monitoring burden, so verification of these pathways is optional.For Class N, wherea conductor-based media is used, it is not the intention to monitor faults on individual conductors but rather tomonitor the operational capability and performance of the pathway as a whole. Unlike Class C, where multiplepathways are not required, for Class N some pathway segments that carry communications for multiple devices(such as Ethernet uplinks or backbones) will have redundant pathway segments present. The intention is that anyone pathway segment can fail without a loss in operational capability to more than one device. For example,connections to control equipment (fire alarm control units, ACUs, or ECCUs), where any interruption incommunications could potentially affect all devices, would have redundant pathway segments. Additionally,backbone and uplink pathway segments that support communications for more than one device and are positionedbetween transmission equipment would also have a redundant pathway segment. But the requirement forredundant pathway segments does not apply to those pathway segments used to service a single device [see

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)(a-2).] Additional nonrequired pathway segments areallowed to be connected and not independently monitored for integrity as long as two paths aremonitored to meet the redundancy requirement of Class N.

Figure A.12.3.6(1)(a)

]

Class N Pathway Block Diagram .


With respect to Class N, the term device refers to an intelligent, addressable device that performs aprogrammable input or output function. Examples of Class N devices include:

Input components such as alarm initiating modules switches and sensors ,

sensors

(1) Output components such as output modules, Ethernet speakers (i.e., IEEE 802.3af PoE speakers),intelligent strobes, textual signage, and intelligent audio amplifiers .

Transmission equipment components (e.g., media converters, Ethernet switches, patch panels, cross

-

? connects) are connected to the Class N pathway merely to transport instructions between otherequipment. As such, they are not considered devices with respect to Class N pathways.

The

The audio amplifier

example is included to explain a type of

listed above is an example of an addressable device that can receive a digital audio input from the ClassN pathway

but

and then provide a notification appliance circuit (NAC) output

to support

with Class A, B, or X

speaker connections


316 of 365 9/22/2014 2:48 PM

pathways . Other

similar devices are also possible to provide alternate class pathway connections

endpoint devices may similarly provide alternate Class pathways for strobes (NACs) or initiating devices(IDCs). From the perspective of the Class N pathway, communications terminates at this

is considered an

endpoint device. However, since these types of endpoints can support multiple notification appliancedevices or initiating devices, they are subject to the redundant pathway

segment

requirement

and are provided with dual pathway connections

.

Control equipment connected to a Class N network for communications with devices would generally utilizeredundant pathway segments. Control equipment connected to other control equipment on a Class N networkwould utilize redundant pathway segments if the control equipment was dependent on any of the pathwaysegments so that

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)(b) ] .

Another utilization of endpoints is permitted for devices providing two connection ports and supporting dualpathway segment connections. The description of endpoint devices is not intended to exclude devices that supportdual pathway connections. Since these pathways are servicing a single device, only a single primary pathwayconnection is required. The second pathway connection exceeds minimum equipment standards and is thereforenot required to be verified as a redundant pathway segment; it can be considered connected to a nondesignatedpathway segment


Class N is also permitted to include dual port devices that provide both transmission and input/output functions.Endpoint devices may have multiple connection ports and support dual pathway segment connections; thus theterm endpoint device is not intended to prohibit more than one connection to a device. Even with dualconnections, where other devices depend on the path, primary and redundant paths are required. But, where anendpoint device has two connection ports, and when a secondary nonrequired connection is added, there is norequirement to separately supervise the nonrequired pathway segment [see Figure A.12.3.6(1)(c) ] .




317 of 365 9/22/2014 2:48 PM

Figure A.12.3.6(1)( c) Class N Pathway Block Diagram with Device with Dual Pathway Connection.



Final_Class_N_Pathway_Block_Diagrams_1.png

Figure A.12.3.6(1)(a-1) & Figure A.12.3.6(1)(a-2)

Final_Class_N_Pathway_Block_Diagram_with_Multiple_Control_Units_1.pngFigure A.12.3.6(1)(b)

Final_Class_N_Pathway_Block_Diagram_with_Device_with_Dual_Pathway_Connection_1.pngFigure A.12.3.6(1)(c)


318 of 365 9/22/2014 2:48 PM

Final_A12.3.6_1_with_drawings.docx

Complete text and drawings for A12.3.6(1) in word format


Editorial and organizational changes for improved readability and clarity. Drawing were changed to make the style more similar to Annex F.Added examples of a comparison between Class N and Class X and Class C. Also added a clarification that class N is not required for supplemental reporting.The proposal is the recommendation by the Correlating Committee Task Group members thatwas comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of thecommittees.Wayne MooreA.J. CapowskiJoe L. CollinsDan HoronVic HummMichael PallettCharles PughRobert SchifilitiAviv SiegelLarry ShudakBob ElliottPaul CrowleyJeff SilveiraJeff KnightAndrew Berezowski



Public Comment No. 191-NFPA 72-2014 [Section No. A.12.3.6(4)]





Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:





319 of 365 9/22/2014 2:48 PM



320 of 365 9/22/2014 2:48 PM



Ethernet network devices are addressable, but with an important distinction from device addresses on a

traditional SLC multi-drop loop. A device with an Ethernet address is, in most cases, a physical endpoint

connected to a dedicated cable. Traditional SLC devices are all wired on the same communication line

(in parallel) similar to an old party-line telephone system. By comparison, Ethernet’s network switches


A fundamental technical difference of Class N from Class A, B or X is that it has no requirement to report

a connection to ground unless the ground impairs the path. A practical concern, where using Ethernet, is

that it is reliable and secure, especially when life safety systems share the same pathways. See 23.6.3

Class N Shared Pathways.

As a visual model, Class N could be likened to a Class X [backbone], allowed to have Class C branch paths

to single endpoint devices. Therefore, every effort is made in this section to clearly distinguish the single

endpoint device from the transport equipment required to have redundant paths, like Class X.

Class N requires, redundant, monitored pathway segments to and from control equipment (fire alarm

control units, ACUs, or ECCUs), where any interruption in communications could potentially affect

multiple endpoint devices.

Typically, interconnected communications equipment such as Ethernet switches, wireless repeaters, or

media converters are used in combination to create pathways. Chapter 12 describes the required

behavior of Class N pathways. All equipment must meet the requirements of other chapters in NFPA 72.



allow two parallel connections. For compliance with Class N, a trouble must be reported if either of these connections fails. [See Figure A.12.3.6(1)(a-1).]

Class N networks may be specified for ancillary functions, but are not required for supplemental

reporting described in 23.12.4. [See Figure A.23.12.4.]

Class N pathways may use metallic conductor communications cable, such as a 100 ohm balanced

twisted pair (e.g., Category 5E), including single‐pair or multi‐pair cable, or other communications media

such as optical fiber cable or wireless transmission, or a combination of two or more such transport mediums.


conductors, but rather to monitor the operational capability and performance of the pathway as a




equipment. Pathway segments that service more than one device, must have at least one verified


SwitchFACU,

ACU, or

ECCU

Switch

Switch Switch

Switch

Endpoint Devices

Switch

1 2

4 3

1 2

A redundant cable between two switches must have special

functionality in order to monitor integrity when a secondary

path is not in use.

20 Feet maximum inside

enclosure or raceway





Figure A.12.3.6(1)(a-1)

Figure A.12.3.6(1)(a-2)

Switch

3

Figure A.12.3.6(1)(b)

Endpoint Devices Group K

Nonrequired redundant

path segment

Switch

2

Switch

1

FACU,

ACU, or

ECCU

FACU,

ACU, or

ECCU

FACU,

ACU, or

ECCU

FACU,

ACU, or

ECCU

(1)

(2)

(3)


trouble.

Redundant pathway segments are generally independent and do not normally share media with the

primary pathways. However, there are exceptions, such as different frequencies for wireless

components, or ring topologies. [See Figure A.12.3.6(5).]

A Class N network may be made more reliable with physically distinct pathway segments (i.e., an

alternate conduit, 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 to have nonrequired segments. [See Figure A.12.3.6(1)(a-2).] Additional

nonrequired pathway segments are allowed to be connected and not independently monitored for

integrity as long as two paths are monitored to meet the redundancy requirement of Class N.

Figure A.12.3.6(1)(a) Class N Pathway Block Diagrams.

With respect to Class N, the term device refers to an intelligent, addressable device that performs a

programmable input or output function. Examples of Class N devices include:

(1) Input components such as alarm initiating modules switches and sensors,

(2) Output components such as output modules, Ethernet speakers (i.e., IEEE 802.3af PoE speakers),

intelligent strobes, textual signage, and intelligent audio amplifiers.

Transmission equipment components (e.g., media converters, Ethernet switches, patch panels, cross‐

connects) are connected to the Class N pathway merely to transport instructions between other

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 audio

input from the Class N pathway and then provide a notification appliance circuit (NAC) output with Class

A, B, or X pathways. Other endpoint devices may similarly provide alternate Class pathways for strobes

(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 support multiple

notification appliance devices or initiating devices, they are subject to the redundant pathway

requirement.

Class N connections between control equipment are required to have redundant monitored pathway

segments if a failure of a primary pathway segment in between control equipment could impair the

operation of the control equipment [see Figure A.12.3.6(1)(b) ].


SwitchFACU,

ACU, or

ECCU

Switch

Switch Switch

Switch

Endpoint Devices

Switch

1 2

4 3

1 2

A redundant cable between two switches must have special

functionality in order to monitor integrity when a secondary

path is not in use.







Figure A.12.3.6(1)(a-1)

Figure A.12.3.6(1)(a-2)

Switch

3

Figure A.12.3.6(1)(b)

Endpoint Devices Group K

Nonrequired redundant

path segment

Switch

2

Switch

1

FACU,

ACU, or

ECCU

FACU,

ACU, or

ECCU

FACU,

ACU, or

ECCU

FACU,

ACU, or

ECCU

(1)

(2)

(3)

Class N is also permitted to include dual port devices that provide both transmission and input/output

functions. Endpoint devices may have multiple connection ports and support dual pathway segment

connections; thus the term endpoint device is not intended to prohibit more than one connection to a

device. Even with dual connections, where other devices depend on the path, primary and redundant

paths are required. But, where an endpoint device has two connection ports, and when a secondary

nonrequired connection is added, there is no requirement to separately supervise the nonrequired

redundant pathway segment [see Figure A.12.3.6(1)(c)].


A nonrequired redundant cable to an endpoint device is

permitted, and does not require separate supervision. Figure A.12.3.6(1)(c)

Endpoint Devices

Switch

To FACU



321 of 365 9/22/2014 2:48 PM

A.12.3.6(1)


322 of 365 9/22/2014 2:48 PM


Addi onal informa on concerning cabling and cabling infrastructure for Class N systems can be found in standards, such as

ANSI/BICI 005, Electronic Safety and Security (ESS) System Design and Implementa on Best Prac ces.”

A network of pathway segments is also described as primary pathway segments, redundant pathway segments, ornondesignated pathway segments. Primary and redundant pathways, from control equipment to each device, areindependently and continuously verified for their ability to support end-to-end communications to and from eachendpoint device. Each device will be provided a primary pathway consisting of one or more pathway segments. Forprimary pathway segments that service more than one device, additional redundant pathway segments providealternate verified communication pathways to the devices. Should any primary pathway segment fail,communication is supported by the redundant pathway segments. Should either a primary or redundant pathwaysegment fail, trouble will be indicated by virtue of the continuous verification of all primary and redundant pathwaysegments. The redundant pathway segments are generally independent and do not normally share media with theprimary pathways. However, there are exceptions, such as different frequencies for wireless or ring topologies. [SeeA.12.3.6(5).]

There is an opportunity to enhance the robustness of a Class N network by providing physically distinct pathwaysegments (i.e., an alternate conduit, or cable tray route, or wireless transmission frequency range, or a combinationof distinct media). It is also permissible to provide other nondesignated pathway segments. Additional pathwaysegments in excess of the minimum requirements of Class N increase the overall robustness of the network andare often desirable. However, since these additional pathway segments exceed the minimum equipment standards,there is no intention to create an additional monitoring burden, so verification of these pathways is optional.

For Class N, where a conductor-based media is used, it is not the intention to monitor faults on individualconductors but rather to monitor the operational capability and performance of the pathway as a whole. UnlikeClass C, where multiple pathways are not required, for Class N some pathway segments that carry communicationsfor multiple devices (such as Ethernet uplinks or backbones) will have redundant pathway segments present. Theintention is that any one pathway segment can fail without a loss in operational capability to more than one device.For example, connections to control equipment (fire alarm control units, ACUs, or ECCUs), where any interruptionin communications could potentially affect all devices, would have redundant pathway segments. Additionally,backbone and uplink pathway segments that support communications for more than one device and are positionedbetween transmission equipment would also have a redundant pathway segment. But the requirement forredundant pathway segments does not apply to those pathway segments used to service a single device [seeFigure A.12.3.6(1)(a)].





The audio amplifier example is included to explain a type of addressable device that can receive a digital audioinput from the Class N pathway but provide a notification appliance circuit (NAC) output to support Class A, B, or Xspeaker connections. Other similar devices are also possible to provide alternate class pathway connections forstrobes (NACs) or initiating devices (IDCs). From the perspective of the Class N pathway, this is considered anendpoint device. However, since these types of endpoints can support multiple notification appliance devices orinitiating devices, they are subject to the redundant pathway segment requirement and are provided with dualpathway connections.

Control equipment connected to a Class N network for communications with devices would generally utilizeredundant pathway segments. Control equipment connected to other control equipment on a Class N networkwould utilize redundant pathway segments if the control equipment was dependent on any of the pathwaysegments so that a failure of a primary pathway segment in between control equipment could impair the operationof the control equipment [see Figure A.12.3.6(1)(b) ].

Another utilization of endpoints is permitted for devices providing two connection ports and supporting dual pathwaysegment connections. The description of endpoint devices is not intended to exclude devices that support dualpathway connections. Since these pathways are servicing a single device, only a single primary pathway


323 of 365 9/22/2014 2:48 PM

connection is required. The second pathway connection exceeds minimum equipment standards and is thereforenot required to be verified as a redundant pathway segment; it can be considered connected to a nondesignatedpathway segment [see Figure A.12.3.6(1)(c)].





324 of 365 9/22/2014 2:48 PM


This will provide an avenue for those wanting more information about the networking base of Class N without the need of creating additional Appendix material down the road.This Public Comment was submitted on behalf of Jeff Silveira of BICSI.



Public Comment No. 174-NFPA 72-2014 [Section No. A.12.3.6(1)] Class N Annex Material


Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:






325 of 365 9/22/2014 2:48 PM



326 of 365 9/22/2014 2:48 PM

A.12.3.6(1)


327 of 365 9/22/2014 2:48 PM


A network of pathway segments is also described as primary pathway segments, redundant pathway segments, ornondesignated pathway segments. Primary and redundant pathways, from control equipment to each device, areindependently and continuously verified for their ability to support end-to-end communications to and from eachendpoint device. Each device will be provided a primary pathway consisting of one or more pathway segments. Forprimary pathway segments that service more than one device, additional redundant pathway segments providealternate verified communication pathways to the devices. Should any primary pathway segment fail,communication is supported by the redundant pathway segments. Should either a primary or redundant pathwaysegment fail, trouble will be indicated by virtue of the continuous verification of all primary and redundant pathwaysegments. The redundant pathway segments are generally independent and do not normally share media with theprimary pathways. However, there are exceptions, such as different frequencies for wireless or ring topologies. [SeeA.12.3.6(5).]

There is an opportunity to enhance the robustness of a Class N network by providing physically distinct pathwaysegments (i.e., an alternate conduit, or cable tray route, or wireless transmission frequency range, or a combinationof distinct media). It is also permissible to provide other nondesignated pathway segments. Additional pathwaysegments in excess of the minimum requirements of Class N increase the overall robustness of the network andare often desirable. However, since these additional pathway segments exceed the minimum equipment standards,there is no intention to create an additional monitoring burden, so verification of these pathways is optional.

For Class N, where a conductor-based media is used, it is not the intention to monitor faults on individualconductors but rather to monitor the operational capability and performance of the pathway as a whole. UnlikeClass C, where multiple pathways are not required, for Class N some pathway segments that carry communicationsfor multiple devices (such as Ethernet uplinks or backbones) will have redundant pathway segments present. Theintention is that any one pathway segment can fail without a loss in operational capability to more than one device.For example, connections to control equipment (fire alarm control units, ACUs, or ECCUs), where any interruptionin communications could potentially affect all devices, would have redundant pathway segments. Additionally,backbone and uplink pathway segments that support communications for more than one device and are positionedbetween transmission equipment would also have a redundant pathway segment. But the requirement forredundant pathway segments does not apply to those pathway segments used to service a single device [seeFigure A.12.3.6(1)(a)].

The term devices is used generically in this section to refer to endpoint devices, which include the following:Commonly, NFPA has used the word device for input components, and term appliance for components used innotification. With respect to Class N, the term device includes appliances and other intelligent, addressablecomponents that perform a programmable input or output function. Examples of Class N devices include:




The audio amplifier example is included to explain a type of addressable device that can receive a digital audioinput from the Class N pathway but provide a notification appliance circuit (NAC) output to support Class A, B, or Xspeaker connections. Other similar devices are also possible to provide alternate class pathway connections forstrobes (NACs) or initiating devices (IDCs). From the perspective of the Class N pathway, this is considered anendpoint device. However, since these types of endpoints can support multiple notification appliance devices orinitiating devices, they are subject to the redundant pathway segment requirement and are provided with dualpathway connections.

Control equipment connected to a Class N network for communications with devices would generally utilizeredundant pathway segments. Control equipment connected to other control equipment on a Class N networkwould utilize redundant pathway segments if the control equipment was dependent on any of the pathwaysegments so that a failure of a primary pathway segment in between control equipment could impair the operationof the control equipment [see Figure A.12.3.6(1)(b) ].

Another utilization of endpoints is permitted for devices providing two connection ports and supporting dual pathwaysegment connections. The description of endpoint devices is not intended to exclude devices that support dual


328 of 365 9/22/2014 2:48 PM

pathway connections. Since these pathways are servicing a single device, only a single primary pathwayconnection is required. The second pathway connection exceeds minimum equipment standards and is thereforenot required to be verified as a redundant pathway segment; it can be considered connected to a nondesignatedpathway segment [see Figure A.12.3.6(1)(c)].





329 of 365 9/22/2014 2:48 PM


This proposal was submitted after an email discussion by the Class N Correlating Committee Task Group members that was comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of the committees. There was no consensus reached on this proposal. Some suggested that unofficially, we have trended over the past 25 years to use “device” on the input side and “appliance” on the output side. Thus, initiating devices and notification appliances. And while this is true, it does not address the very many examples that can be found when the word "device" is used in some other context, including the context where both initiating devices and notification appliances are meant at the same time.

In the code we already refer to UPS’s as devices, radio transmitters as devices, circuit breaker locks as devices, overcurrent protection devices, emergency control interface devices, light output for signaling devices for hearing impaired, power supervisory devices, and generally fire alarm devices connected to fire alarm circuits. We also refer to “devices” for testing and maintenance requirements – which is not limited to initiating devices only. There are also requirements for power supplied to “devices” over an SLC that are intended to cover both addressable initiating devices and notification appliances – although the code only references these as “devices”.

So there is no rule that “devices” always means “initiating devices” – but if we want to state that traditionally or commonly the term is associated with initiating device it may be misleading and doing a disservice to generalize something that is not really true to people to who have not been deeply engaged with the code for many years.





Related Item





Street Address:

City:

State:

Zip:


330 of 365 9/22/2014 2:48 PM


Committee Statement

CommitteeAction:






331 of 365 9/22/2014 2:48 PM


A.12.3.6(4)

The operational conditions of the pathway include factors such as latency, throughput, response time, arrival rate,utilization, bandwidth, and loss. It is intended that the life safety equipment connected to a Class N networkactively monitor some or all of the pathway’s operational conditions, so that an improperly installed or configuredpathway, or a subsequently degraded pathway or network of pathway segments is detected by the life safetyequipment and reported as a trouble. This monitoring is intended to be continuous so that a degradation ofpathway performance over time is detected and reported. Trouble would be reported when operational conditionsof the pathway(s) have deteriorated to the point where the equipment is no longer capable of meeting its minimumperformance requirements, even if some level of communication to endpoint devices is still maintained. Examplesof performance requirements include the activation of an alarm within 10 seconds, the reporting of a trouble signalwithin 200 seconds, synchronization of strobes, and delivery of audio messages with required intelligibility.

It is possible to have a pathway where end-to-end communications are operational under system idle conditions,but in the event of an alarm, the increased load on a degraded pathway could cause a partial or complete failure todeliver required life safety signals. This is the situation that is intended to be actively detected and reported.


Editorial and organizational changes for improved readability and clarity.The proposal is the recommendation by the Correlating Committee Task Group members thatwas comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of thecommittees.Wayne MooreA.J. CapowskiJoe L. CollinsDan HoronVic HummMichael PallettCharles PughRobert SchifilitiAviv SiegelLarry ShudakBob ElliottPaul CrowleyJeff SilveiraJeff KnightAndrew Berezowski



Public Comment No. 174-NFPA 72-2014 [Section No. A.12.3.6(1)] Class N Annex material


Related Item





Street Address:

City:

State:

Zip:



332 of 365 9/22/2014 2:48 PM

Committee Statement



Statement: Editorial and organizational changes for improved readability and clarity.


333 of 365 9/22/2014 2:48 PM



334 of 365 9/22/2014 2:48 PM

A.12.3.6(5)

Devices with dual path connections are permitted to be connected

to createin a daisy ? chain of devices on a ring.

In this circumstance they cannot be considered endpoint devices because each pathway segment supportsmultiple devices; thereforeAgain, where Class N pathway segments support multiple devices , verified redundant pathway

segments would be necessarysegment(s) are required . This can be accomplished with a ring topology, as long as each segment of the ring isverified as functional, and the failure of any one segment does not result in the loss of functionality of more than onedevice. In this

circumstance the requirements for Class N are satisfied by allowing thearrangement, primary and redundant pathway segments

toshare the same media

by providing, and provide two possible directions of communications

onin a ring topology [see Figure A.12.3.6(5) ] . This

configuration is fully compliant with 12.3.6 (5).The daisydaisy? chain configuration is also

a permissible connection method forpermitted between multiple control units that require verified primary and redundant pathway segments.

Figure AFigure A .12.3.6(5)

ClassClass N Pathway Block Diagram with

DaisDaisy Chained Devices with Dual Pathway Connection.




335 of 365 9/22/2014 2:48 PM

Final_Class_N_Pathway_Block_Diagram_with_Daisy_Chained_Devices_with_Dual_Pathway_Connection.pngFigure a.12.3.6(5)


Editorial and organizational changes for improved readability and clarity. Drawing were changed to make the style more similar to Annex F.The proposal is the recommendation by the Correlating Committee Task Group members thatwas comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of thecommittees.Wayne MooreA.J. CapowskiJoe L. CollinsDan HoronVic HummMichael PallettCharles PughRobert SchifilitiAviv SiegelLarry ShudakBob ElliottPaul CrowleyJeff SilveiraJeff KnightAndrew Berezowski





Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: Editorial and organizational changes are made for improved readability and clarity. The drawing waschanged to make the style more similar to Annex F.


336 of 365 9/22/2014 2:48 PM

Public Comment No. 230-NFPA 72-2014 [ Section No. A.14.2.1.1 ]

A.14.2.1.1

Initial and re-acceptance inspections are performed to ensure compliance with approved design documentswhatever the quality or origin. This involves inspection to ensure that the correct equipment has been used andproperly located and installed. Ensuring compliance helps to assure both operational reliability and missionreliability. This concept applies to any type of system, not just fire alarm and signaling systems. At this stage of asystem’s life, the responsibilities for such inspections rest with the designers of the systems and with the variousapplicable authorities having jurisdiction.Special consideration should be given to occupancies that have individualswith intellectual disabilities. Special training for these individuals should be given to help them understand theaudible and visual signaling and what action(s) are expected to be followed


This is to alert Authorities Having Jurisdiction, building owners, property managers, testing and service personnel that additional training and notification be given to individuals with special needs and staff so that an understanding of what to expect during an alarm activation and testing of Protected Premise System’s and the actions that they should take during these conditions.

Related Item



Submitter Full Name: Jeffrey Knight

Organization: City of Newton Fire Department

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected but held

Resolution: This is new material that was not addressed at the First Draft. FR-296 is not related to the subjectmatter in this comment.


337 of 365 9/22/2014 2:48 PM


A.14.4.3.2 Table 14.4.3.2 Item 9.(d)Ohmic testing is a means to determine the state-of-health of a Valve-Regulated Lead-Acid (VRLA) battery’s cells bymeasuring some form of a cell’s internal resistance. Typically ohmic testing equipment use one of three techniques,conductance, impedance, or resistance, to make these measurements.

In simplest technical terms, ohmic technology is based on Ohm’s Law, which expresses the relationship betweenvolts, amperes, and ohms in an electrical circuit. Ohmic testing attempts to use voltage and current to determinethe resistive characteristic of a battery’s cells. As the cells in a battery age and start to lose capacity, the internalcomponents of the battery are undergoing a degradation process. The degradation of these components (plates,grids, internal connection straps) within the battery’s cells cause an increased resistance in the conduction paths ofthe cell, which in turn cause a change in the internal ohmic values. A measured increase in impedance orresistance, or a decrease in conductance, indicates the battery is losing its ability to produce the energy it wasdesigned to deliver when called upon to support the connected loads.

The key to effective application of ohmic testing is the appropriate trending of test results over time compared to abaseline or reference value. Studies have demonstrated that an individual battery produces a unique ohmic"signature" and the use of ohmic testing equipment to trend changes in this signature from installation through thelife of the battery is the most effective use of the technology. A program that involves ohmic testing on a regularinterval to note changes in the battery is a good maintenance practice.

An ohmic baseline reference value is a benchmark value based on data collected from known good batteries.Reference values can be determined from site specific measurement, or from testing a sample of new healthybatteries, or by using a generic baseline value to get started.

(1) The best baseline is one established on the installed battery within three to six months after installationand trend accordingly using good record keeping. Ideally the individual ohmic value should be measured atinstallation and again after the battery has been on float charge for at least 72 hours in order for it to reach ahigh state of stabilization. These initial “site-specific” values should be recorded and permanently affixed to thebattery as a baseline for subsequent tests over the life of the battery. The ohmic value will typically increasefor conductance and decrease for resistance and impedance between the initial installation and after being onfloat charge for 90 to 180 days (10% to 15% depending on battery type and size). Six months after installationmeasure and compare the ohmic readings to the readings taken at installation. Use whichever value isgreater for conductance or lower for resistance and impedance, as the baseline for that particular battery atthat site going forward.

(2) A sample of new healthy batteries in a fully charged state can be tested to obtain a baseline valuerepresentative of a new battery. A sample size of at least 30 batteries from one manufacturer with the samemake, model, amp-hour rating, age (within 6 months), and manufacturing lot is recommended. Record thefollowing information for the batteries:

(a) Battery manufacturer

(b) Model number

(c) Date of manufacture

(d) Manufacturing lot number (if available)

(e) Battery temperature

(f) Has the battery had a freshening charge or not

(g) Battery voltage

(h) Ohmic test value

Calculate the average ohmic value of the batteries. Do not include batteries that deviate more than 30%from the average because they could be outside of an acceptable range. Use the average value as abaseline starting point for this model battery.

(3) A generic baseline value for a specific battery model can often be found by contacting the ohmic testequipment manufacturer or from the battery manufacturer. While it is important to note that the use of genericreference values may not be as accurate, it is still possible to identify grossly failed batteries and significantchanges in battery condition by applying this method. Generic baseline values are typical averages to be used


338 of 365 9/22/2014 2:48 PM

as general guidelines and should only be used when no other data is available. When testing older batteriesfor which no initial site-specific ohmic value is available reference values can be obtained in the followingways:

(a) Contact the equipment or battery manufacturer for assistance

(b) Consult your company documentation to see if reference values were created for the battery you aretesting.

(c) Using ohmic readings of recently installed batteries of the same:

(d) Manufacturer and model of the battery

(e) Manufacturer and model of the alarm panel/system

(f) Charging circuit

(g) Temperature at time of measurements

(h) Calculate an average of the top 8 - 10 batteries and use this value as a baseline reference

As a battery ages and loses capacity, the internal ohmic values change. Although the change may not be perfectlyconsistent over all battery models and sizes, experience and extensive test data shows that a deviation of ohmicvalues from the established baseline by 30% or more for conductance and 40% or more for resistance orimpedance indicates that the actual battery capacity has dropped to 80% or lower. (For lead-acid batteries,capacity drops off rapidly once the 80% capacity point is reached in the lifetime curve, so this is known as the“knee” of the capacity vs. lifetime curve). This 80% capacity is the level at which battery manufacturers recommendbattery replacement. Figure A.14.4.3.2 9. (d) illustrates an ohmic trend of a 5-yr design life battery with an actualexpected service life of 3 years. Note that while battery Unit #1 still has good ohmic readings, it is desirable toreplace both units at the same time. If one unit fails at 1-1/2 yrs, it is likely the second unit will fail in one of the nextsemiannual tests. Full replacement ensures that all units will “float” together. One exception would be in the caseof “infant mortality” in which one of the units fails in the first year.

FIGURE A.14.4.3.2 9. (d) Example Ohmic Trend Analysis for a 24 Volt Battery Made Up of Two 12 Volt Units. Semiannual Measurements Show Unit #2 Failing Prematurely. For this Case Both Units Should beReplaced.

Ohmic testing can be a safe, simple, accurate, and reliable means of determining the state of health of valve-regulated lead-acid batteries. It is important however to understand some basic guidelines in order to maximize thebenefits and avoid possible misleading test results.

(1) Follow safety regulations: wear eye protection, remove metal jewelry, etc. prior to working with batteries.

(2) Conduct a visual inspection prior to testing. A cracked case, leaking terminal or post, or bulging battery shouldbe replaced, not tested.

(3) Temperature changes affect measured ohmic values and battery capacity. Ohmic measurements should betaken at 77°F (25°C), or within /- 10°F (5°C) of 77°F (25°C).

(4) For maximum accuracy and consistency, batteries should be tested when in a fully charged state.

(5) Check the battery charging current prior to test. The charging current should be stable and be within thenormal float current recommendations of the battery manufacturer for the battery model. If it is not, it is likelythat the batteries have recently been discharged and a test is not appropriate until this float current stabilizes.

(6) Whenever possible, ohmic readings should be taken each time with the same instrument, but as a minimumwith the same model. Changing models will skew the data and require re-establishing the base line.

(7) When test equipment is provided with an alert, set the ohmic baseline and/or thresholds prior to beginning thetest to provide an indication of any deviations from baseline.

(8) It is essential to take ohmic measurements at the battery terminal or post. For consistency and accuracysubsequent tests should always place probes or clamps at the same point while avoiding battery hardwaresuch as bolt heads or washers. Connecting on the hardware will influence the readings and may causereplacement of a healthy battery.

(9) Maintain good contact at the test point for the duration of the test. If the probe or clamp slips off during the testan incorrect reading will result.

(10) For batteries with fully insulated quick disconnect connectors, the battery may be taken offline by removing thequick disconnects from the battery terminals and then measuring and recording the internal ohmic value of thebattery.

(11) A battery tested online may display a different value than when tested offline due to the charger circuit and


339 of 365 9/22/2014 2:48 PM

load being across the battery. Always test the same way, either online or offline, to have consistent andmeaningful results.

(12) Do not condemn a battery based upon results of a single test without any trending data or an establishedbaseline for that specific battery.

(13) When one or more units in a battery fall outside the acceptable range from base line, replace the entire string.


This public input is submitted as part SIG-TMS Battery Task Group.







Related Item






Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected but held



340 of 365 9/22/2014 2:48 PM


A.14.4.3.2 Table 14.4.3.2 Item 9. (e)Battery capacity is determined by the mass of active material contained in the battery and is a measure of thebattery’s stored energy. The rated capacity of small VRLA batteries used in fire system applications is typicallymeasured in ampere-hours (Ah) where the ampere-hour rating is based on the battery’s capability to provide aconstant current at the nominal battery voltage for twenty hours. The rated capacity may vary from manufacturer tomanufacturer.

The actual battery capacity during service life can vary significantly from rated capacity due to aging, charging anddischarge cycles, temperature, and other factors. The unique failure modes of VRLA batteries due to aging andinternal degradation are attributed for a high failure rate where the actual battery capacity has degraded to 80percent of the manufacturer’s rated capacity. As a result, battery manufacturers often recommend replacementmuch sooner than the rated design life for critical systems.

A test of battery capacity is designed to determine if the battery is capable of continuing to deliver the voltage levelspecified by the manufacturer. The results of a capacity test can also be used to estimate where the battery is in itsservice life. A test of capacity is performed by applying a continuous load to the battery based on themanufacturer’s published discharge rates until voltage falls to specified levels. Although discharging the battery forcapacity testing concerns some, VRLA batteries are designed to handle numerous discharges within the limitsestablished by the battery manufacturer.

The discharge rate selected for testing should be representative of the duty cycle because at shorter test times thetest duration has a greater effect on the capacity calculation. For example, a one minute difference in actual testtime for a 5 minute discharge rate compared to a 3 hour discharge rate will result in a greater deviation of thecalculated capacity. The battery is also operating less efficiently at shorter discharge rates and the effects of agingand degradation may not be as prevalent during shorter discharges.

Fire alarm systems do not typically carry a sufficient load for the practical application of a load test because thebattery is sized for a duty cycle consisting of a standby period of 24 hours or more followed by five minutes in analarm condition. For this reason the panel loading will not likely align with published discharge rates, which isessential for test personnel to easily calculate capacity. In many installations, the fire system loading is inadequateto meet the functional requirements for capacity testing and in these cases a battery near failure could conceivablysatisfy the low discharge rate applied by the fire system.

In order to satisfy the load test requirements of Table 14.4.3.2 Item 9.(e), battery capacity testing can be performedin the following manner or in accordance with other methods such as those identified in IEEE Standard 1188:

(1) Referring to the battery manufacturer’s specifications, determine the load current for the 3 hour battery ratingto the selected end voltage, typically 1.67 volts per cell (10.2 volts for 12 volt system or 20.4 volts for 24 voltsystem).

(2) Record the battery temperature at the negative terminal.

(3) Disconnect the charger and connect a load bank to the battery terminals.

(4) Apply the constant current specified for the 3 hour rate to the battery. Once the constant current is appliedcontinue the test until the battery terminal voltage decreases to the specified end voltage.

(5) Stop the test when the selected end voltage is reached

(6) Record the actual test duration in minutes

(7) Disconnect the load bank and reconnect the charger

(8) Calculate percent battery capacity as follows:

%Capacity = (Tactual/180 x KT) x100

where:

Tactual = the test duration in minutes

KT = the temperature correction factor for the actual battery temperature at the start of the test from Table

A.14.4.3.2 9 (e). Additional Temperature Correction Factors can be obtained from IEEE 1188.

(1) Replace the battery if battery capacity is less than or equal to 80%. Replace the battery at the next scheduledtest interval if battery capacity is less than 85%.


341 of 365 9/22/2014 2:48 PM

Temperature °F KT

70 0.955

71 0.960

72 0.970

73 0.975

74 0.980

75 0.985

76 0.990

77 1.000

78 1.002

79 1.007

80 1.011

Table A.14.4.3.2.9. (e) Temperature Correction Factors.


This Public Input submitted as part of SIG-TMS Battery Task Group





Related Item






Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected but held



342 of 365 9/22/2014 2:48 PM



343 of 365 9/22/2014 2:48 PM

A.14.4.3.2


344 of 365 9/22/2014 2:48 PM

Table 14.4.3.2, Item 24. The extent of testing of a fire alarm or signaling system, including devices that were nottested, should be documented per the Test Plan in 14.2.10. NFPA 72 does not require testing of an emergencycontrol function, such as elevator recall, but does require testing of the emergency control function interface device,such as the relay powered by the fire alarm or signaling system. Where the emergency control function is not beingtested concurrent with the fire alarm or signaling system testing, measurement of the emergency control functioninterface device output should be verified using the proper test devices. This might require reading or observing thecondition of a relay, a voltage measurement, or the use of another type of test instrument. Once testing is complete,verification that any disabled or disconnected interface devices have been restored to normal is essential and thisverification should be documented in the testing results.

Testing of the emergency control functions themselves is outside of the scope of NFPA 72. A complete end-to-endtest that demonstrates the performance of emergency control functions activated by the fire alarm or signalingsystem might be required by some other governing laws, codes, or standards, or the authority having jurisdiction. Inthat situation, other applicable installation standards and design documents, not NFPA 72, would address testingand performance of the emergency control functions. NFPA 3, Recommended Practice for Commissioning andIntegrated Testing of Fire Protection and Life Safety Systems, provides guidance for integrated (end-to-end) testingof combined systems. The following excerpt from NFPA 3 includes guidance on when integrated testing should beperformed.

7.2 Test Frequency. [3:7.2]

7.2.1 In new construction, integrated testing of fire protection and life safety systems should occur following:

(1) Verification of completeness and integrity of building construction

(2) Individual system functional operation and acceptance as required in applicable installation standards tests

(3) Completion of pre-functional tests of integrated systems [3:7.2.1]

7.2.2 Existing fire protection and life safety systems should have periodic integrated testing. [3:7.2.2]

7.2.2.1 Integrated systems that were commissioned upon installation in accordance with Chapter 6 should haveintegrated testing at the interval specified in the commissioning plan. [3:7.2.2.1]

7.2.2.2 For integrated systems that were not commissioned, an integrated testing plan should be developed toidentify the appropriate extent and frequency of integrated system testing. [3:7.2.2.2]

7.2.3 In addition to periodic integrated testing, integrated system testing should be done when any of the followingevents occurs:

(1) New component fire protection or life safety systems are installed and interconnected to existing fire protectionand life safety systems.

(2) Existing fire protection or life safety systems are modified to become components of interconnected systems.

(3) Interconnections or sequence of operations of existing integrated fire protection and life safety systems aremodified. [3:7.2.3]

NFPA 3 also includes guidance on test methods for integrated testing. It is important to note that the appropriateNFPA standard would provide the acceptance criteria for the overall emergency control function operationrequirements including performance and test methods while NFPA 72 covers the required performance and testingof the emergency function interface device.

For instance, if an end-to-end test for a building with an engineered smoke control system is required by some othergoverning laws, codes, standards, or the authority having jurisdiction, the test protocol would have unique criteriafor the smoke control system design and a special inspector would be responsible for the overall operation andperformance of the smoke control system in accordance with the appropriate standard (NFPA 92, Standard forSmoke Control Systems, and NFPA 101, Life Safety Code) during the testing, including measuring pressuredifferentials and ensuring proper fan and damper operation. Refer to the following extract from NFPA 101 on smokecontrol:

9.3.2 The engineer of record shall clearly identify the intent of the system, the design method used, theappropriateness of the method used, and the required means of inspecting, testing, and maintaining the system. [101:9.3.2]

9.3.3 Acceptance testing shall be performed by a special inspector in accordance with Section 9.9. [ 101:9.3.3]

Even though the fire alarm or signaling system initiating device might activate the smoke control system, the actualtesting of the dampers and fan operation would be as required by the smoke control design and not part of the firealarm or signaling system.

Other emergency control operation requirements might be as follows: For fan shutdown and smoke damperoperation, the fan and damper operations would be in accordance with NFPA 90A, Standard for the Installation ofAir-Conditioning and Ventilating Systems, and NFPA 105, Standard for Smoke Door Assemblies and Other OpeningProtectives, respectively, and those equipment operations would be verified by those responsible for HVAC systems


345 of 365 9/22/2014 2:48 PM

in combination with the fire alarm system personnel. Guidance for elevator inspection and testing can be found inASME A.17.2, Guide for Inspection of Elevators, Escalators and Moving Walks. For elevator systems, the recallfunction, elevator power shutdown, and hat illumination would be done with the elevator mechanics present duringthe test. This operational test is often accomplished during routine periodic fire alarm testing. For fire door holderand fire shutter release, it would be expected that the emergency control function operation of the doors/shutterswould be verified in accordance with NFPA 80, Standard for Fire Doors and Other Opening Protectives, and NFPA101 during the test. In some cases, the door manufacturer representative might need to be present to reset theequipment.

Guidance on documenting and handling of faults, failures, and corrective action for integrated testing can be foundin 7.4.5 of NFPA 3.

Table 14.4.3.2 Item 22(a) and 22(b)

If during the course of the periodic test of audible appliances, it is suspected that alarm sound levels could be lowerthan the required minimum, the building system owner or the system owner's designated building representativeshould be notified in writing . Such notification will allow the building owner or designated building representative todetermine whether sound pressure level readings should be taken for the area(s) in question.


The revised wording of this First Revision addresses both the system owner and system owner's designated representative (which is the same terminology used in Chapter 14) and specifies the type of notification recommended.

Related Item

First Revision No. 297-NFPA 72-2013 [Section No. A.14.4.3.2]


Submitter Full Name: Joe Scibetta

Organization: BuildingReports

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted


Statement: Language was changed to use "system owner or the system owner's designated representative", whichcorrelates the terminology used in other locations within NFPA 72. The TC also added "in writing" to clarifythe medium of notification.


346 of 365 9/22/2014 2:48 PM


A.17.4.8

Some applications that do not require full area protection do require detection to initiate action when specific objectsor spaces are threatened by smoke or fire, such as at elevator landings that have ceilings in excess of 15 ft (4.6 m)and for protection of fire alarm control units. In high-ceiling areas, to achieve the desired initiation, such as forelevator recall and protection of fire alarm control units (FACUs), detection should be placed on the wall above andwithin 60 in. (1.52 m) from the top of the elevator door(s) or FACU.


The guidance given to locate a smoke detector 60 inches above the top of the elevator door or FACU is contradictory to the requirement of 17.7.3.2.1 that smoke detectors that are wall mounted be mounted within 12" of the ceiling. It is also noted in A.17.7.3.2.1 that detectors mounted closer to the ceiling will respond faster. In a room with a 20' ceiling and the FACU mounted at 6' above the finished floor (AFF), the guidance in this paragraph would have the smoke detector mounted at 11' AFF or 9' from the ceiling which would result in an extraordinary delay in activation of the smoke detector. I understand the concept of mounting a detector closer to an object that is a fire hazard, but in the case of elevator doors and FACU's we are not trying to detect fires originating at the elevator or FACU, we are trying to detect fires in the immediate vicinity of these items. There does not appear to be any technical justification to support the guidance in this annex material, and I recommend the last sentence be deleted as it directly conflicts with enforceable requirements in the body of the code.

Related Item

First Revision No. 72-NFPA 72-2013 [Sections 17.4.1, 17.4.2, 17.4.3, 17.4.4, 17.4.5, 17.4.6, 17...]


Submitter Full Name: Daniel Decker

Organization: Safety Systems, Inc.

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: The ceiling is not always the best location for an initiating device protecting a control panel, elevator, orspecific object.


347 of 365 9/22/2014 2:48 PM


A.17.12.2

The waterflow device or the combination of the waterflow devices and fire alarm system should be field adjustedconfigurable so that an alarm is initiated no more than 90 seconds after a sustained flow of at least 10 gpm (40L/min).

Features that should be investigated to minimize alarm response time include the following:

(1) Elimination of trapped air in the sprinkler system piping

(2) Use of an excess pressure pump

(3) Use of pressure drop alarm-initiating devices

(4) A combination thereof

Care should be used when choosing waterflow alarm-initiating devices for hydraulically calculated looped systemsand those systems using small orifice sprinklers. Such systems might incorporate a single point flow of significantlyless than 10 gpm (40 L/min). In such cases, additional waterflow alarm-initiating devices or the use of pressuredrop-type waterflow alarm-initiating devices might be necessary.

Care should be used when choosing waterflow alarm-initiating devices for sprinkler systems that use on–offsprinklers to ensure that an alarm is initiated in the event of a waterflow condition. On–off sprinklers open at apredetermined temperature and close when the temperature reaches a predetermined lower temperature. Withcertain types of fires, waterflow might occur in a series of short bursts of a duration of 10 seconds to 30 secondseach. An alarm-initiating device with retard might not detect waterflow under these conditions. An excess pressuresystem or a system that operates on pressure drop should be considered to facilitate waterflow detection onsprinkler systems that use on–off sprinklers.

Excess pressure systems can be used with or without alarm valves. The following is a description of one type ofexcess pressure system with an alarm valve.

An excess pressure system with an alarm valve consists of an excess pressure pump with pressure switches tocontrol the operation of the pump. The inlet of the pump is connected to the supply side of the alarm valve, and theoutlet is connected to the sprinkler system. The pump control pressure switch is of the differential type, maintainingthe sprinkler system pressure above the main pressure by a constant amount. Another switch monitors lowsprinkler system pressure to initiate a supervisory signal in the event of a failure of the pump or other malfunction.An additional pressure switch can be used to stop pump operation in the event of a deficiency in water supply.Another pressure switch is connected to the alarm outlet of the alarm valve to initiate a waterflow alarm signal whenwaterflow exists. This type of system also inherently prevents false alarms due to water surges. The sprinkler retardchamber should be eliminated to enhance the detection capability of the system for short duration flows.


I ask the committee to reconsider PI 267. The committee made the following statement:

The submitter’s text conflicts with the retard requirements of Chapter 17 and the 10 second allowance permitted by Chapter 23. Should the submitter desire to perform the timing function via the FACU, he should submit a public comment to Chapter 23.

The statement is not in conflict with the text in chapter 17 nor chapter 23.

17.12.2 Activation of the initiating device shall occur within 90 seconds of waterflow at the alarm-initiating device when flow occurs that is equal to or greater than that from a single sprinkler of the smallest orifice size installed in the system

Whether this is a mechanical delay built into the waterflow device, or an electronic delay built into an intelligent module or firmware delay built into the IDC of a fire control panel, isn't it the idea to reduce faults alarms cause by water surges?

The delay timer device built into waterflow device, is what the committee believes is the only acceptable method. I would argue that an intelligent module attached to a waterflow device, similar to an intelligent pull-station, is acceptable since the module is monitoring the waterflow device for flow and delays it from transmitting the alarm to the fire control panel. It delays the alarm activation until the delay timer setting programmed in the module has been reached. Then an alarm would be transmitted to the fire alarm system.


348 of 365 9/22/2014 2:48 PM

Finally, the attachment of a waterflow device directly to the IDC of fire alarm system and could work just like alarm verification for smoke detectors. The fire alarm system monitors the waterflow device for activity during the delay period, suppressing the alarm until the delay period has been reached. If flow is still detected at the conclusion of the delay period the system would activate the alarm.

None of this is in violation with chapter 23. Chapter 23 requires the activation of the alarm response to be done in 10 seconds. The alarm response timer is started once the fire alarm system goes into alarm.Thank you for your consideration.

Related Item



Submitter Full Name: JEFFERY VAN KEUREN

Organization: Edwards, A division UTC Fire and Security

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Accepted


Statement: The waterflow signal activation may be mechanical built into the waterflow device, electronic built into anintelligent module, or firmware built into the IDC of a fire control panel.


349 of 365 9/22/2014 2:48 PM


A.18.1

Notification appliances should be sufficient in quantity, audibility, intelligibility, and visibility so as to reliably conveythe intended information to the intended personnel during an emergency.

Notification appliances in conventional commercial and industrial applications should be installed in accordancewith the specific requirements of Section 18.4 and Section 18.5.

The Code recognizes that it is not possible to identify specific criteria sufficient to ensure effective occupantnotification in every conceivable application. If the specific criteria of Section 18.4 and Section 18.5 are determinedto be inadequate or inappropriate to provide the performance recommended, approved alternative approaches ormethods are permitted to be used. Special consideration should be given to occupancies that have individuals withintellectual disabilities. Special training for these individuals should be given to help them understand the audibleand visual signaling and what action(s) are expected to be followed


This is to alert Authorities Having Jurisdiction, building owners, property managers, testing and service personnel that additional training and notification be given to individuals with special needs and staff so that an understanding of what to expect during an alarm activation and testing of Protected Premise System’s and the actions that they should take during these conditions.

Related Item

First Revision No. 80-NFPA 72-2013 []


Submitter Full Name: Jeffrey Knight

Organization: City of Newton Fire Department

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The new text alerts Authorities Having Jurisdiction, building owners, property managers, testing and servicepersonnel that additional training and notification be given to individuals with special needs and staff so thatan understanding of what to expect during an alarm activation and testing of Protected Premise System’sand the actions that they should take during these conditions. This is important in occupancies wherepersons with cognitive disabilities are expected to be present, such as schools or other institutions.


350 of 365 9/22/2014 2:48 PM


A.21.1

Fire alarm systems, signaling systems, and emergency communications systems are often part of a large,integrated system serving a building or area. Figure A.21.1 shows examples of individual systems that might bepart of an integrated system.

A fire alarm system might monitor the status of one of the other individual systems or provide a form of output tocontrol another individual system, such as a smoke control system or an elevator controller.

In some cases, the fire alarm system shares information and control in two directions with another individualsystem. NFPA 72 covers only the fire alarm or signaling system in the circuits powered by it, not any part of theother individual systems.

See NFPA 3 and NFPA 4 for additional information on integrated systems.

Figure A.21.1 Integrated Systems.


NFPA 3 also addresses intergrated systems.

Related Item



Submitter Full Name: Kelly Nicolello

Organization: Western Regional Fire Code Dev

Street Address:

City:

State:

Zip:


Committee Statement



Statement: NFPA 3 was added to provide a more complete set of references.


351 of 365 9/22/2014 2:48 PM

Public Comment No. 87-NFPA 72-2014 [ Sections A.21.3.9, A.21.3.10 ]

Sections A.21.3.9, A.21.3.10

A.21.3.9

It should be noted that smoke detectors installed in hoistways can be a source of nuisance activation. Therefore,hoistways need smoke detectors specifically intended for those types of spaces (environments).

A.21.3.10

The objective of Phase I Emergency Recall Operation is to have the elevator automatically return to the recall levelbefore fire can affect the safe operation of the elevator. This includes both the safe mechanical operation of theelevator, as well as the delivery of passengers to a safe lobby location. Where ANSI/ASME A17.1/CSA B44, SafetyCode for Elevators and Escalators, specifies the use of smoke detectors, these devices are expected to provide theearliest response to situations that would require Phase I Emergency Recall Operations. The use of other automaticfire detection is only intended where smoke detection would not be appropriate due to the environment. Whereambient conditions prohibit the installation of smoke detectors, the selection and location of other automatic firedetection 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 lag characteristics. The consideration of a lowtemperature rating alone might not provide the earliest response. See A.21.4.1 and 21.4.2. Fixed temperatureheat detectors used for elevator (lobby) recall should have an FM Listed spacing rating of 25 feet or greaterand be installed within 24 inches of the elevator lobby sprinkler head.


I agree with the committee statement made on the first draft submission. However, the elevator recall function is just as important as elevator power shut down. Therefore the same level of care should be applied.

The FM Listed spacing rating should be used as it is more conservative than the UL Listed spacing rating. More time would be provided between elevator recall initiation and sprinkler activation.

Related Item



Submitter Full Name: DAVID SROKA

Organization: MASSACHUSETTS UNIV OF

Affilliation: None

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:


Resolution: SR-16-NFPA 72-2014 No technical substantiation was provided to recommend a 25 foot listed spacingfor heat detector spacing or for the 24 inch recommendation.

Statement: The added reference to A.21.3.10 provides addition guidance for heat detector installations.


352 of 365 9/22/2014 2:48 PM

Public Comment No. 200-NFPA 72-2014 [ 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) Occupant evacuation elevators will be provided for a relatively limited number of buildings, mainlyhigh-rise buildings. It is highly recommended that those involved with design and installation of thesesystems become familiar with available information such as ASME A17.1, Section 2.27 and itsnon-mandatory Appendix V “Building Features for Occupant Evacuation Operation”. It will be imperativethat a great amount of coordination be done between elevator and fire alarm system designers andinstallation contractors.

A.21.6.2.2.3

The manual means is intended in lieu of automatic initiating devices that are impaired or out of service and wouldotherwise have actuated to provide automatic initiation in accordance with 21.6.2.1 2 .1 ( 2 ) . Manual fire alarmboxes location throughout the building are not included because they are typically activated at locations remotefrom the fire and could lead to misinformation about the location of the fire.

A.21.6.2. 1.2 3

The fire alarm system uses the floor identification to automatically establish a contiguous block of floors for voicemessaging purposes. The elevator system also uses the floor iden fica on to determine the con guous block of floors to

be evacuated consistent with 21.6.2.1.2(B) . . So, that block would be the floor of alarm plus two floors above and two

floors below the floor of alarm for a total of 5 floors. 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 also used foroccupant notification. The output signals from the fire alarm system can be in the form of contact closures or serialcommunications. Coordination needs to be provided between the fire alarm system installer and the elevatorsystem installer.

A.21.6.2. 1.4 5

Messages need to be coordinated with the operation of the elevators so that occupants understand what to expectand how to react. Additional visual information will be provided in each elevator lobby by the elevator managementsystem to further inform occupants of the status of the elevators. It is especially important to address addi onal alarm

actua on(s) and the impact that has on expanding the block of floors and the corresponding messages that have to adjust to

the change.

Sample voice message content to be added to normal message (to be coordinated with dynamic signage providedby the elevator contractor) :







For further information on voice messaging strategies refer to “Incorporating Emergency Messaging Guidance intoPractice”

A.21.6.2. 1.4 5 (C)

This new message will require a signal from the elevator management system to the fire alarm system.

A.21.6.2.7 There are several instances where signals must be received from the elevator system. One of these iswhen the Phase I Emergency Recall key switch is used to manually initiate recall. In this case, the fire alarmsystem needs to know that it must cancel OEO programming. Another situation requiring a signal from the elevatorsystem is when, for whatever reason, the elevator system cannot provide the intended operation. In this case thefire alarm system needs to know so it does not provide incorrect messaging to a floor(s).




353 of 365 9/22/2014 2:48 PM

Proposed_New_Wording_for_Section_21.6_Annex_Material.docxAnnex Material - Tie with Public Comment #199


Renumbering and additional Annex material for correlation with ASME A17.1 Elevator and Escalator Safety Code, 2013 editionThis material ties with Public Comment #199



Public Comment No. 199-NFPA 72-2014 [Section No. 21.6]

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected but held



354 of 365 9/22/2014 2:48 PM

Proposed New Wording for Section 21.6 Annex Material (Tie together with Public Comment #199)

A.21.6 Occupant evacuation elevators will be provided for a relatively limited number of buildings, mainly

high-rise buildings. It is highly recommended that those involved with design and installation of these

systems become familiar with available information such as ASME A17.1, Section 2.27 and its non-mandatory

Appendix V “Building Features for Occupant Evacuation Operation”. It will be imperative that a great amount

of coordination be done between elevator and fire alarm system designers and installation contractors.

A.21.6.2.2.3 The manual means is intended in lieu of automatic initiating devices that could be impaired or

out of service and would otherwise have actuated to provide automatic initiation in accordance with

21.6.2.2.2. Manual fire alarm boxes location throughout the building 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.

A.21.6.2.3 The fire alarm system uses the floor identification to automatically establish a contiguous block of

floors for voice messaging purposes. The elevator system also uses the floor identification to determine the

contiguous block of floors to be evacuated. So, that block would be the floor of alarm plus two floors above

and two floors below the floor of alarm for a total of 5 floors. The established block of floors 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. Coordination needs to be provided between the fire

alarm system installer and the elevator system installer.

A.21.6.2.5 Messages need to be coordinated with the operation of the elevators so that occupants

understand what to expect and how to react. Additional visual information will be provided in each elevator

lobby by the elevator management system to further inform occupants of the status of the elevators. It is

especially important to address additional alarm actuation(s) and the impact that has on expanding the block

of floors and the corresponding messages that have to adjust to the change.

Sample voice message content to be added to normal message (to be coordinated with dynamic signage

provided by the elevator contractor):







For further information on voice messaging strategies refer to “Incorporating Emergency Messaging

Guidance into Practice”

A.21.6.2.5(C) This new message will require a signal from the elevator management system to the fire alarm

system.

A.21.6.2.7 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. In this case, the fire

alarm system needs to know that it must cancel OEO programming. 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).


Class C Zones

The exception of 23.6.2 is intended to permit consideration by the AHJ for where this requirement is inconsistentwith established practice and the risk of using Class C as compared to other pathway classes is acceptable. Forexample, for a floor that is subdivided into many zones like in a hotel, it may not be desirable to install two detectorsin each room. In comparison to a class A or B implementation, multiple detection devices are not usually requiredand a pathway failure would render failure of many detectors in many rooms. But for class C, even with only onedetector in each room, since a pathway failure would result in the loss of only the one detector, and the troublerequirements are the same, the class C implementation actually presents less risk even with one detector per room.


The exception of 23.6.2 was established without any guidance to the intention. The deliberation that was conducted during the task group discussion that resulted in this exception centered on hotel room examples and risks of failure in comparison to other pathway classes. Also when discussing risk during those meetings, a comparison to the risk should a class A or B pathway fail was often used for guidance. This annex material is intended to pass on these intentions and insights to people who may be reasonable asked to provide justification or judge the risks when considering the application of this exception.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:

Rejected

Resolution: Class C circuits are not addressed in the body of the code for SLCs in section 23.6.2 which isreferenced in the Public Comment.


355 of 365 9/22/2014 2:48 PM


A. 23.6.3.6 (c) The planned impairment process is used to control change in the system and informstakeholders. Any activities that may affect the performance of the network or impact conclusions of a riskanalysis should be presented to the organization referred to in 23.6.3.1.5 for approval. The organizationshould have a name (e.g., Life Safety Network Management Group). All stakeholders who may be affectedby network outages should have representation in the organization.

A committee, made up of members of the organization should meet on a regular basis, and report to theorganization. All planned impairments should have 7 days’ notice. An emergency impairment (one withless than 7 days’ notice) should meet very stringent standards for urgency. Outages and repair operationsare dealt with on a case by case basis with the Fire Marshal’s office and the Department of Public Safetyincluded based on the operational impact.

All proposed changes and outages are to be presented to the organization for authorization, schedulingand coordination. Once a change has been authorized and scheduled, an impairment notification is issuednotifying all affected users. If specific mitigation actions, such as fire watch, are required, they are to beincluded in the impairment notification.

Impairment notifications are issued through the Fire Marshal’s office, the Department of Public Safety, thePower Outages Group, or other groups depending on the systems affected.

A “Login Banner” is a programmable option for network switches and routers. This banner is the firstthing that comes up on the screen when you log into the equipment. Where practical, network equipmentused in life safety systems should have a login banner to notify service personnel that the network is apart of an active life safety system and any impairment shall be coordinated with the named organization.


It was felt that the reader would benefit from a practical discussion of an impairment process and change control process with respect to the responsibilities of the organization (e.g., Live Safety Management Group).The proposal is the recommendation by the Correlating Committee Task Group members thatwas comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of thecommittees.Wayne MooreA.J. CapowskiJoe L. CollinsDan HoronVic HummMichael PallettCharles PughRobert SchifilitiAviv SiegelLarry ShudakBob ElliottPaul CrowleyJeff SilveiraJeff KnightAndrew Berezowski




Related Item






356 of 365 9/22/2014 2:48 PM

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: With respect to restricting Class N pathways to strictly Level 3 Shared Pathways, members of the TC felt thatit would be counterproductive to provide zero possibility for qualified customers to share other high prioritysystems on this network. It may create a perception of obsolescence out of the gate to provide no pathforward into the future where more and more customers may be qualified to manage integrated life safetynetworks. There are other systems that are involved in life safety and security that can (where appropriate)utilize modern networks and can benefit from shared pathways including nurse call systems, access controlsystems, camera systems, and of course Mass Notification Systems. Less important may be the benefit ofthe aggregation of port costs, but rather real benefits may be realized in purposeful inter-operation and/orcommon management for those life safety networks.



357 of 365 9/22/2014 2:48 PM


A.23.12.4

Off-site logging of fire alarm data can be useful to preserve information in the face of fire or building failure tofacilitate accurate reconstruction of the event. It can also be beneficial to send data off-premises to incidentcommand personnel to enhance situational awareness and response decisions and to maintain safe and efficientoperations.



Final_Supplemental_Reporting_Network.png FigureA.23.12.4


Added Diagram to better illustrate the explanation of supplemental reporting provided in the proposed A.12.3.6(1) Public Comment.The proposal is the recommendation by the Correlating Committee Task Group members thatwas comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of thecommittees.Wayne MooreA.J. CapowskiJoe L. CollinsDan HoronVic HummMichael PallettCharles PughRobert SchifilitiAviv SiegelLarry ShudakBob ElliottPaul CrowleyJeff SilveiraJeff KnightAndrew Berezowski




Related Item





Street Address:

City:

State:

Zip:


Committee Statement




358 of 365 9/22/2014 2:48 PM

Statement: Added a diagram to better illustrate the explanation of supplemental reporting.


359 of 365 9/22/2014 2:48 PM

Public Comment No. 224-NFPA 72-2014 [ New Section after A.23.16 ]

A.23.16.2 This requirement is intended to limit the impact from the failure of a battery operated receiver/transmitterin a given space. This requirement is not intended to prevent a single device that contains multiple functionelements such as: a combination carbon monoxide and smoke detector, a detector with an independentlycontrollable sounder, a notification appliance with visible and audible elements, etc. This requirement is intended tolimit the number of functional elements to one of each independent type. For example the device could not consistof two pull stations or two relay outputs however, it could consist of one smoke detector with an independentlycontrollable relay output.


The annex material would clarify that the intent of this requirement is not to prohibit the use of wireless technology in combination devices but rather to limit the regional impact from the failure of a battery operated wireless device.




Related Item





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: Add the attached annex material for A.23.16.2. The annex material would clarify that the intent of thisrequirement is not to prohibit the use of battery operated technology in combination devices but rather tolimit the regional impact from the failure of a battery.


360 of 365 9/22/2014 2:48 PM


A.24.3.7.1

The fundamental structure of the prerecorded or live messages is critical for providing information and instructionsthat are intelligible. Prerecorded messages created in a controlled environment are considerably more intelligiblethan live messages and should be developed and provided to handle as many of the probable emergencies that aparticular facility will encounter.

The voice instructions (live or prerecorded) should be preceded by a tone to get attention and prepare the targetaudience for voice instructions. This tone should be differentiated for specific emergencies, based on the standardsfor that facility. The actual voice message (live or pre-recorded) should be delivered in a well-enunciated, clear,calm, and deliberate manner, using respectful language. Focus the message on the action to be taken andminimize wasting words on the cause. For the voice itself, best results will vary, depending on the specific location— for example, in outdoor applications, it has been shown that a male voice will provide better intelligibility, as thenaturally lower frequency of the male voice travels better. Inversely, in an interior application, where the backgroundambient noise is typically in the same lower frequencies, a female voice tends to penetrate better, as it is moredistinct from the ambient. Messages should be constructed using 2-second to 3-second bursts of information andbrief periods of quiet between the bursts of information. This methodology facilitates better processing ofinformation by the brain and minimizes the negative effects of reverberation and echo.

Generally, the emergency message should consist of an alert tone of 1 second to 3 seconds, followed by a voicemessage that is repeated at least three times. The alert tone can be used in between repeats of the voice message.

For live instructions, it is critical that the message be delivered in a clear and calm manner. When possible, thefollowing procedure is recommended:

(1) Think about what information must be delivered in the live announcement, keep it brief, and write down themessage

(2) Read the message out loud for a practice round in a clear and projecting voice

(3) When you are ready to announce, key the microphone and read the message at least three times

(4) When possible, use an alert tone, such as a Code 3, 1000 Hz signal preceding the message, and thenannounce over the live microphone

(5) Repeat the message a few times more as the emergency warrants

Additional information on this topic is availaible in the NIST Technical Note 1779, General Guidance on EmergencyCommunication Strategies for Buildings.


With the publication of NIST Technical Note 1779, General Guidance on Emergency Communication Strategies for Buildings, there is evidence presented related to the annex material presented here.

Related Item





Street Address:

City:

State:

Zip:


Committee Statement



361 of 365 9/22/2014 2:48 PM

Resolution: SR-98-NFPA 72-2014. See SR-100.

Statement: The new annex incorporates the material.


362 of 365 9/22/2014 2:48 PM


A.24.3.7.2

A well-crafted, evidence-based message (incentive to response) with content that includes the following:

(1) What: Guidance on what people should do

(2) When: An idea of when they need to act

(3) Where: Description of the location of the risk of hazard (who should be taking action and who should not be)

(4) Why: Information on the hazard and danger/consequences

(5) Who: The name of the source of the warning (who is giving it)

Warning style is also crucial and should be specific, consistent, certain, clear, and accurate with attention paid to thefrequency — the more it is repeated, the better.

Additional information on this topic is availaible in the NIST Technical Note 1779, General Guidance on EmergencyCommunication Strategies for Buildings.


With the publication of NIST Technical Note 1779, General Guidance on Emergency Communication Strategies for Buildings, there is evidence presented related to the annex material presented here.




Related Item





Street Address:

City:

State:

Zip:


Committee Statement


Resolution: SR-99-NFPA 72-2014. See SR-100.

Statement: The new annex incorporates the material.


363 of 365 9/22/2014 2:48 PM


A.26.2.2.1(4)

The 90-second allowance for a supervising station to call the protected premise to verify the validity of the receivedalarm signal is independent from the time allowed for the supervising station to initiate the retransmission to thecommunications center. A time line would show an alarm signal received at a supervising station at 0.0seconds. The verification process covered by 26.2.2.1 could take from 0.0 seconds up 90 seconds afterwhichthe retransmission of the alarm signal to the communications center could take an additional 90 seconds (0.0 secsplus 90 seconds plus 90 secs) for a total of 180 seconds.


The added text to the annex attempts to further clarify that the 90 seconds permitted to carry out verification occurs before the 90 seconds permitted for alarm signal retransmission. Public Comment #238 was submitted to address the removal of Preverification. Should Preverification be retained in th code the committee should address the time necessary for this act and whether it falls within or outside the 180 seconds permitted for verification and alarm signal retransmission.

Related Item






Street Address:

City:

State:

Zip:


Committee Statement



Statement: The annex material was revised to add clarity.


364 of 365 9/22/2014 2:48 PM


See proposed new text and graphics below.

***INSERT FIGURES HERE***



NFPA_72_A26-3-1_Publiccomment_mm.pdf PC Form

72_PC240_Baclawski_Figures.pdf Figures


The section and annex are not clear as to what they mean. A set of simple drawings added to the end of the annex paragraph A26.3.1 will help the reader better visualize the do’s and don’ts of wiring in this section

As a note, the body of the code suggest a Class A and Class B wiring of the circuit with isolators is acceptable. But, Class B alone is not acceptable without possibly losing more than one zone.

Related Item

First Revision No. 31-NFPA 72-2013 [Sections 26.6.3.1.6, 26.6.3.1.7]



Organization: NEMA

Street Address:

City:

State:

Zip:


Committee Statement

CommitteeAction:



Statement: The revision is made for compliance with the manual of style. Also add new annex material as shown inthe attachment. The added annex material further clarifies the SLC zoning requirements.


365 of 365 9/22/2014 2:48 PM

Second Revision No. 102-NFPA 72-2014 [ Global Comment ]

10.12.2Visible notification appliances, textual visible notification appliances, and speaker notification appliances located inthe same area shall be activated and deactivated as a group unless otherwise required by an ECS emergencyresponse plan. (SIG-ECS)10.12.3*Visible alarm strobe notification appliances shall not be activated when speaker notification appliances are used aspermitted by 24.3.6 for nonemergency paging. (SIG-ECS)


Submitter Full Name: Christopher Coache

Organization: National Fire Protection Assoc

Street Address:

City:

State:

Zip:

Submittal Date: Fri Jul 11 08:55:16 EDT 2014

Committee Statement

CommitteeStatement:

The annex material associated with 10.12.2 should be associated with 10.12.3 as indicated in thecommittee statement for FR-363.

ResponseMessage:



1 of 128 9/29/2014 10:17 AM


Revise the Annex F figures that include a smoke detector symbol (hexagon with a whisp of smoke) so thatthe new smoke detector symbol shown in the latest edition of NFPA 170 is used. The new symbol is ahexagon with the letter "S" as shown in Table 8.3 of the 2015 edition of NFPA 170. The Annex F figures areFigure F.2.3, F.2.4, F.2.5, F.2.6, F.2.7 and F.2.8.

Supplemental Information

File Name Description

G72-252r1.jpg

G72-49r1.jpg

G72-50r1.jpg

G72-51r1.jpg

G72-52r1.jpg

G72-53r1.jpg


Submitter Full Name: Lee Richardson


Street Address:

City:

State:

Zip:

Submittal Date: Thu Aug 28 08:52:49 EDT 2014

Committee Statement

CommitteeStatement:

NOTICE: This is a Second Revision developed by Staff for editorial purposes so that the smoke detectorsymbol used in Annex F is consistent with the symbol shown in the 2015 edition of NFPA 170. Committeereview has been deemed advisable and the Second Revision is being processed in accordance with section4.4.9.6.3 of the Regulations Governing the Development of NFPA Standards.

ResponseMessage:


2 of 128 9/29/2014 10:17 AM


Revise Figures A.17.6.3.1.1(c) and A.17.7.5.4.2.2(a) to replace the smoke detector symbol (a hexagon with awhisp of smoke) with the smoke detector symbol shown in Table 8.3 of the 2015 edition of NFPA 170 (ahexagon with the letter "S").



G72-216r1.jpg




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

NOTICE: This is a Second Revision developed by Staff for editorial purposes so that the smoke detectorsymbol used in Figures A.17.6.3.1.1(c) and A.17.7.5.4.2.2(a) is consistent with the symbol shown in the2015 edition of NFPA 170. Committee review has been deemed advisable and the Second Revision is beingprocessed in accordance with section 4.4.9.6.3 of the Regulations Governing the Development of NFPAStandards.

ResponseMessage:


3 of 128 9/29/2014 10:17 AM


Revise Figures A.29.5.1(a), A.29.5.1(b), A.29.5.1(c) and A.29.5.1(d) to replace the smoke detector symbol (ahexagon with a whisp of smoke) with the smoke detector symbol shown in Table 8.3 of the 2015 edition ofNFPA 170 (a hexagon with the letter "S").



G72-244r1.jpg

G72-88r1.jpg

G72-269r1.jpg

G72-180r1.jpg




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

NOTICE: This is a Second Revision developed by Staff for editorial purposes so that the smoke detectorsymbol used in Figures A.29.5.1(a) through A.29.5.1.(d) are consistent with the symbol shown in the 2015edition of NFPA 170. Committee review has been deemed advisable and the Second Revision is beingprocessed in accordance with section 4.4.9.6.3 of the Regulations Governing the Development of NFPAStandards.

ResponseMessage:


4 of 128 9/29/2014 10:17 AM


Add "SLC Zones." as a title to 23.6.1 also add attached annex material



72_SR_31_A.23.6.1_edited.docx


Submitter Full Name: [ Not Specified ]


Street Address:

City:

State:

Zip:

Submittal Date: Thu Jun 26 12:34:47 EDT 2014

Committee Statement

CommitteeStatement:

The revision is made for compliance with the manual of style. Also add new annex material as shown inthe attachment. The added annex material further clarifies the SLC zoning requirements.

ResponseMessage:




5 of 128 9/29/2014 10:17 AM


In Table 14.4.3.2 item 17(j)(2) through (5) change "Quarterly" to "Annually" in four (4) places.


Submitter Full Name: Richard Roux


Street Address:

City:

State:

Zip:

Submittal Date: Wed Jul 02 07:38:15 EDT 2014

Committee Statement

CommitteeStatement:

NFPA 72 establishes the requirements for fire alarm switch testing frequency. The statistical failure ratesof electronically supervised mechanical switches are extremely small. In a 3-year cycle, there was noevidence to suggest that more than an annual frequency was necessary.

ResponseMessage:




6 of 128 9/29/2014 10:17 AM

Second Revision No. 52-NFPA 72-2014 [ Section No. 2.3.4 ]



ISO 7731, Danger signals for work places — Auditory danger signals, 2003 (Reconfirmed 2009) .


Submitter Full Name: Barry Chase


Street Address:

City:

State:

Zip:

Submittal Date: Thu Jul 03 13:48:05 EDT 2014

Committee Statement

Committee Statement: Reference updated.

Response Message:



7 of 128 9/29/2014 10:17 AM


3.3.3 Accessible, Readily (Readily Accessible).

Capable of being reached quickly for operation, renewal, or inspections without requiring those to whom readyaccess is requisite to actions such as to use tools, to climb over or remove obstacles or to resort to portableladders, and so forth. [70, 2011 70: 100 ] (SIG-FUN)




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

NOTICE: This is a Second Revision developed by Staff for editorial purposes so that the extract definitionfrom the NEC is up to date with the definition in the 2014 edition of the NEC. Committee review has beendeemed advisable and the Second Revision is being processed in accordance with section 4.4.9.6.3 of theRegulations Governing the Development of NFPA Standards.

ResponseMessage:


8 of 128 9/29/2014 10:17 AM


3.3.11 Alarm.





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Change "action" to "response" to be consistent with the defined condition-signal-response modeladopted in the 2013 edition. We need to cascade the use of these three terms throughout the code.

ResponseMessage:



9 of 128 9/29/2014 10:17 AM

Second Revision No. 9-NFPA 72-2014 [ New Section after 3.3.66.22 ]

3.3.67* Device (Class N).

A supervised component of a life safety system that communicates with other components of life safety systemsand that collects environmental data or performs specific input or output functions necessary to the operation ofthe life safety system.

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) that are required to provide the real-time functionalitynecessary for the protection of life and property. In this way, a component connected to the network used fornoncritical functions (i.e., maintenance) can be differentiated and excluded from the monitoring for integrityrequirements 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 if they donot provide life safety–specific environmental monitoring, inputs, or outputs for the life safety system. This is notto say that this equipment is not important to the overall operation of the system, just that this equipment is notconsidered a “device” in the context of Class N. Equipment that does not meet the definition of a device cannotbe specifically supervised but rather generally supervised as they are part of the supervised pathways thatservice the Class N devices themselves.



72_SR_9_Class_N_definition_edited.docx




Street Address:

City:

State:

Zip:

Submittal Date: Wed Jun 25 12:45:18 EDT 2014

Committee Statement

CommitteeStatement:

With the addition of Class N pathways in the first draft, the term “device” was used with specificity in thecontext of Class N, but not defined. This revision also adds related annex to illustrate examples of what isa Class N device and how the distinction is drawn.

ResponseMessage:




10 of 128 9/29/2014 10:17 AM

Second Revision No. 10-NFPA 72-2014 [ New Section after 3.3.92 ]

3.3.94* Endpoint (Class N).




72_SR_10_Endpoint_Annex_material_edited.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

With the addition of Class N pathways in the first draft, the term “endpoint” was used with specificity inthe context of Class N, but not defined. Related annex material is also added.

ResponseMessage:




11 of 128 9/29/2014 10:17 AM



A documented set of actions to address the planning for, management of, and response to natural, technological,and man-made disasters and other emergencies. (SIG-ECS)




Street Address:

City:

State:

Zip:

Submittal Date: Tue Jul 08 11:30:34 EDT 2014

Committee Statement

CommitteeStatement:

An emergency plan includes an emergency response plan - plus other elements like a pre-plan and acommunications plan – that leads to the ECS needs assessment.

ResponseMessage:



12 of 128 9/29/2014 10:17 AM


3.3.124 Heat Alarm.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The TC changes SIG-IDS to SIG-HOU. The TC revises the definition to delete the example as it isnot required.

Response Message:



13 of 128 9/29/2014 10:17 AM

Second Revision No. 55-NFPA 72-2014 [ Section No. 3.3.129 [Excluding any Sub-Sections] ]

3.3.131* Impairment.





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Editorial correction.

Response Message:

Public Comment No. 34-NFPA 72-2014 [Section No. 3.3.129 [Excluding any Sub-Sections]]


14 of 128 9/29/2014 10:17 AM


3.3.170 Network.

3.3.170.1 Wired Network (Public Emergency Alarm Reporting Systems) .


3.3.170.2 Wireless Network (Public Emergency Alarm Reporting Systems) .





Street Address:

City:

State:

Zip:

Submittal Date: Tue Jun 17 09:43:23 EDT 2014

Committee Statement

CommitteeStatement:

The definitions for the terms “Wireless Network” and "wired network" are unique to the requirement ofChapter 27 and labels were added to recognize this distinction. Networks are used in other places in thecode and these definitions would not necessarily be applicable to the other usages.

ResponseMessage:



15 of 128 9/29/2014 10:17 AM


3.3.260 Signaling Zone.

See 3.3.320 , Zone.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The change was made to correlate with the changes made with SR-88.

Response Message:


16 of 128 9/29/2014 10:17 AM


3.3.274 Spacing.

A horizontally measured dimension related to used as a criterion in determining the allowable coverage ofdetectors devices . (SIG-IDS)




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

SIG-IDS: Spacing relates to more than just detectors.


Response Message:



17 of 128 9/29/2014 10:17 AM

Second Revision No. 91-NFPA 72-2014 [ Section No. 3.3.317.1 ]

3.3.320.2* Evacuation Signaling Zone.

An area consisting of one or more notification zones where signals are actuated simultaneously. (SIG-ECS)




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:


18 of 128 9/29/2014 10:17 AM


7.1.6

The requirements of other chapters shall also apply unless they are in conflict with Chapters 10 , 12 , 14 , 17 ,18 , 21 , 23 , 24 , 26 , and 27 shall apply unless otherwise noted in this chapter.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The section was revised to avoid the term "conflicts", since the code should not contain conflicts.

Response Message:



19 of 128 9/29/2014 10:17 AM


7.2.1*

Where documentation is required by the authority having jurisdiction, the following list shall represent theminimum documentation required for new fire alarm systems, supervising station and shared communicationequipment, and emergency communications systems, including new systems and additions or alterations toexisting systems:

(1)

(2) Riser diagram









(7) Battery capacity and de-rating calculations (where batteries are provided)





(11) Pathway diagrams between the control unit, and the supervising station and shared communicationsequipment

(12) Completed record of completion in accordance with 7.5.67.5.6 7.5.7 and 7.8.2




(16) Completed record of inspection and testing in accordance with 7.6.6 and 7.8.2




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

A requirement for documented power loss dB calculations is redundant to the requirements fordocumenting the minimum sound pressure levels that must be produced by the audible notification



20 of 128 9/29/2014 10:17 AM

appliances in the applicable covered areas and the requirement for voltage drop calculations for notificationappliance circuits. The definition of "notification appliance circuit" includes the pathway connecting anamplifier to one or more speakers.



ResponseMessage:




21 of 128 9/29/2014 10:17 AM


7.5.5

Owner’s manuals for emergency communications systems shall be in accordance with Section 24.15 .(SIG-ECS)




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The reference points to a section that points directly back to Chapter 7.

Response Message:



22 of 128 9/29/2014 10:17 AM


7.5.7 Site-Specific Software. (SIG-TMS)

Site-specific software documentation shall be in accordance with 14.6.1.2 . (SIG-TMS)

See SR-56

7.5.7.1

For software-based systems, a copy of the site-specific software shall be provided to the system owner or owner’sdesignated representative.

7.5.7.1.1

The site-specific software documentation shall include both the user passcode and either the systemprogramming password or specific instructions on how to obtain the programming password from the systemmanufacturer.

7.5.7.1.2

The passwords provided shall enable currently certified qualified programming personnel to access, edit,modify, and add to the existing system site-specific software.

7.5.7.2

A copy of the site-specific software shall be stored on-site in nonvolatile, nonerasable, nonrewritable memory.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Section 14.6.1.2 and related annex material has been relocated to become 7.5.8. Moving the requirementsfor site-specific software to Chapter 7.5.8 will improve usability of the Code by placing the site-specificsoftware documentation requirements in the “Documentation” chapter. A reference pointer to 7.5.8 hasbeen added to 14.6.1.2 by SR 56.


ResponseMessage:





23 of 128 9/29/2014 10:17 AM


7.7.2.6*





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The first draft text does not indicate who is responsible for maintaining electronic documents formats sothat they remain accessible. The building owner (or their representative) should be responsible for keepingthe formats current because the documents are their property. The revised text is clearer and indicates thatthe building owner or their representative is responsible.

ResponseMessage:




24 of 128 9/29/2014 10:17 AM


10.4.4*

In areas that are not continuously occupied, an automatic smoke detector shall be provided at the location of eachfire alarm control unit(s), notification appliance circuit power extenders extender(s) , and supervising stationtransmitting equipment. The location of the required detector shall be in accordance with 17.7.3.2 to providenotification of fire at that location .





Street Address:

City:

State:

Zip:

Submittal Date: Mon Jul 07 12:17:55 EDT 2014

Committee Statement

CommitteeStatement:

The text, "the location of the required detector shall be in accordance with 17.7.3.2," was deleted because itwould require full detection coverage for the area. The intent of 10.4.4 is to provide detection for a specifichazard at the equipment location so that fire is likely to be detected before the equipment is disabled. Therequirement to provide notification of a fire condition before equipment is disabled by fire should apply toemergency communication system signaling because of the analogous life safety purpose of ECS.

ResponseMessage:





25 of 128 9/29/2014 10:17 AM


10.5.1.1





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: This revision deletes the word "proper" from the section, because it is unnecessary.

Response Message:



26 of 128 9/29/2014 10:17 AM


10.5.1.2


Personnel who are registered, licensed, or certified by a state or local authority

Personnel who are certified by a nationally recognized certification organization acceptable to the authorityhaving jurisdiction

Personnel who are factory trained and certified for fire alarm system design and/or emergencycommunication system design of the specific type and brand of system and who are acceptable to theauthority having jurisdiction

10.5.1.3

Personnel shall provide documentation of their qualification by one or more of the following:

(1) State or local authority for registration, licensing, or certification

(2) Certification by an organization acceptable to the authority having jurisdiction

(3) Manufacturer's certification for the specific type and brand of system provided




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The TC maintains the requirement to follow state or local licensure regulations. The text has beenrevised to address the submitters concerns regarding the use of the term “nationally recognized” as beingoverly restrictive.

ResponseMessage:




27 of 128 9/29/2014 10:17 AM


10.5.1.5

System design trainees shall be under the direct supervision of a qualified system designer.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The section adds provision for trainees to develop the competence and experience required by theCode. This section is similar to 10.5.5.3.

ResponseMessage:



28 of 128 9/29/2014 10:17 AM


10.5.2.2




Personnel who are factory trained and certified for fire alarm system installation and/or emergencycommunications system installation of the specific type and brand of system and who are acceptable to theauthority having jurisdiction

10.5.2.3








Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The TC maintains the requirement to follow state or local licensure regulations. The text has beenrevised to address the concerns regarding the use of the term “nationally recognized” as being overlyrestrictive.

ResponseMessage:




29 of 128 9/29/2014 10:17 AM


10.5.2.4

System installation trainees shall be under the supervision of a qualified system installer.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:


ResponseMessage:



30 of 128 9/29/2014 10:17 AM


10.5.4.3



Personnel who meet the requirements of NFPA 1031, Standard for Professional Qualifications for FireInspector and Plan Examiner

Personnel who are assigned to perform plan reviews and inspections by the authority having jurisdiction

10.5.4.4

Personnel shall provide documentation of their qualifications by one or more of the following:


(2) Meeting the requirements of NFPA 1031

(3) Assignment by the authority having jurisdiction to perform plan reviews and inspections




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The TC maintains the requirement to follow state or local licensure regulations. The committee hasclarified the options permitted to demonstrate qualification.

ResponseMessage:



31 of 128 9/29/2014 10:17 AM

Second Revision No. 68-NFPA 72-2014 [ Section No. 10.6.5.1.1 ]

10.6.5.1.1



(2) An engine-driven generator or equivalent in accordance with 10.6.11.2, where a person trained in itsoperation is on duty at all times

(3) An engine-driven generator or equivalent arranged for cogeneration with an electric utility in accordance with10.6.11.2, where a person trained in its operation is on duty at all times




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The phrase "or equivalent" should not have been removed. While Chapter 1 has language permitting anequivalent means, the term is necessary here to provide immediate context. Without it an engine drivengenerator is the only implied choice and does not allow for other choices that are not connected to ordependent upon the utility.

ResponseMessage:



32 of 128 9/29/2014 10:17 AM

Second Revision No. 101-NFPA 72-2014 [ Section No. 10.11 ]

10.11* ECS Priority Signals Actuation Time .

Visible indication of priority signals shall be automatically indicated within 10 seconds at the fire alarm control unitor other designated location. (SIG-ECS) Actuation of alarm notification appliances or emergency voicecommunications, emergency control function interface devices, and annunciation at the protected premises shalloccur within 10 seconds after the activation of an initiating device.



72_SR_101_A.10.11_edited.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

SIG-ECS: The action at the first draft entirely deleted section 23.8.1.1 regarding signals. The lost annexmaterial from A.23.8.1.1 was added to A.10.11. The TC suggests that the Correlating Committee review10.12 as similar material to 10.11.


ResponseMessage:



33 of 128 9/29/2014 10:17 AM


12.3.8*

Class A, Class N, and Class X circuits using physical conductors (e.g., metallic, optical fiber) shall be installed sothat the primary and redundant, or outgoing and return conductors, exiting from and returning to the control unit,respectively, are routed separately. The outgoing and return (redundant) circuit conductors shall be permitted inthe same cable assembly (i.e., multiconductor cable), enclosure, or raceway only under the following conditions:

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

Single drops installed in raceway to individual devices or appliances

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)




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

"Class N" is deleted from this paragraph because it was inadvertently added during the First Draft. Theseparation requirements of this paragraph do not actually apply to Class N.

ResponseMessage:

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

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


34 of 128 9/29/2014 10:17 AM


14.2.2.2.4

In the event that any equipment is observed to be part of a recall program, the building owner system owner orthe system owner's designated representative shall be notified in writing .




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The wording of 14.2.2.2.4 was changed to be similar to the verbiage in the existing Section14.2.2.2.3.

Response Message:



35 of 128 9/29/2014 10:17 AM


14.4.5 Single- and Multiple-Station Smoke Alarms. (SIG-HOU)

14.4.5.1

Smoke Single- and multiple-station smoke alarms and all connected appliances shall be inspected, tested, andmaintained in accordance with 14.4.5 and the manufacturer's published instructions at least monthly . Theresponsibility for inspection, testing and maintenance shall be in accordance with 14.2.3 . (SIG-HOU)

14.4.5.2

Single- and multiple-station smoke Smoke alarms and shall be connected appliances shall be inspected andtested at least monthly replaced when they fail to respond to operability tests but shall not remain in servicelonger than 10 years from the date of manufacture, unless otherwise recommended by the manufacturer’spublished instructions . (SIG-HOU)

14.4.5.3*

Combination smoke/carbon monoxide alarms shall be replaced when the end-of-life signal activates or 10 yearsfrom the date of manufacture, whichever comes first. (SIG-HOU) The responsibility for inspection, testing, andmaintenance of smoke alarms and connected appliances shall be in accordance with 14.2.3 .

14.4.5.4

Where batteries are used as a source of energy for combination smoke/carbon monoxide alarms or single- andmultiple-station smoke alarms, the batteries shall be replaced in accordance with the alarm equipmentmanufacturer’s published instructions. (SIG-HOU) Smoke alarms shall be replaced when they fail to respond tooperability tests.

14.4.5.4.1

Smoke alarms shall not remain in service longer than 10 years from the date of manufacture, unless otherwiseprovided by the manufacturer’s published instructions.

14.4.5.5*

Combination smoke/carbon monoxide alarms shall be replaced when the end-of-life signal activates or 10 yearsfrom the date of manufacture, whichever comes first, unless otherwise provided by the manufacturer's publishedinstructions.

14.4.5.6

Where batteries are used as a source of energy for smoke alarms or combination smoke/carbon monoxidealarms or single- and multiple-station smoke alarms, the batteries shall be replaced in accordance with thealarm equipment manufacturer’s published instructions.



72_SR_51_A.14.4.5.3_edited.docx




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC clarifies the application of Section 14.4.5.

Response Message:


36 of 128 9/29/2014 10:17 AM


14.6.1.2 Site-Specific Software.

The requirements of 7.5.8 shall apply to site-specific software.

Moved by SR-53

14.6.1.2.1

For software-based systems, a copy of the site-specific software shall be provided to the system owner orowner’s designated representative. The site-specific software documentation shall include either the systemprogramming password or specific instructions on how to obtain the password from the system manufacturer.

14.6.1.2.1





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Moving the requirements for site-specific software to Chapter 7 with a reference to the appropriate sectionin Chapter 7 will improve usability of the Code by placing the site-specific software documentationrequirements in the “Documentation” chapter. It is understood that SIG-TMS will retain control of anychanges to the requirements. Refer to SR 53 for the relocated material.

ResponseMessage:


37 of 128 9/29/2014 10:17 AM


18.4.2.3

The signal shall be repeated for a period appropriate for the purposes of evacuation of the building, but for notless than 180 seconds. The minimum repetition time shall be permitted to be manually interrupted.

18.4.2.3.1

The minimum repetition time shall be permitted to be manually interrupted.

18.4.2.3.2

The minimum repitition time shall be permitted to be automatically interrupted for the transmission of massnotification messages in accordance with Chapter 24 .




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This statement seems inconsistent with the intention of MNS systems. Based on circumstances, MNS mayemploy automatic messages to direct occupants under various emergency situations. This section requiresthat evacuation signals may not be automatically interrupted for three minutes. In that time, people may haveresponded (or not responded) inappropriately because the nature of the emergency or the proper actionscould not be made clear to occupants in time. A reference to Chapter 24 was added for correlation. Inaddition, the section was revised to meet the Manual of Style.

ResponseMessage:



38 of 128 9/29/2014 10:17 AM


See SR-70

18.4.5.3*

Effective January 1, 2014, audible Audible appliances provided for the sleeping areas to awaken occupants shallproduce a low frequency alarm signal that complies with the following:

(1) The alarm signal shall be a square wave or provide equivalent awakening ability.

(2) The wave waveform shall have a fundamental frequency of 520 Hz ± 10 percent.

(3)



72_SR_70_A.18.4.5.3_3_edited.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The effective date was eliminated, since it has passed. Reference to product listing was added to ensurethat the correct waveform, frequency, and harmonics are included in the appliance performance.

ResponseMessage:


* The notification equipment shall be listed for producing the low frequency waveform.


39 of 128 9/29/2014 10:17 AM


18.5.3.2*

A The maximum light pulse duration shall be 0.2 second 20 milliseconds with a maximum duty cycle of 40percent.

Exception: Lights used to meet the requirements of 18.5.5.5 shall be permitted to be listed and labeled to havepulse durations up to 100 milliseconds.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This change is needed because research has shown that the use of longer pulse widths with lights ratedusing the concept of candela effective will result in poor detection performance. Longer pulse widths must becombined with some as yet undetermined increase in peak candela intensity in order to be effective.However, the research has shown that strobes rated using candela effective and that have pulse widths up to100 ms can be effective in corridor, direct viewing application. Thus the allowance for their use in corridorswas needed. Additional work is being done to determine how the code should be modified to have aperformance metric that will work for lights with both long and short pulse durations.

ResponseMessage:





40 of 128 9/29/2014 10:17 AM


21.1* Application.


21.1.1

The requirements of Chapters 7, 10, 17, 18, 23, 24, and 26 shall apply, unless they are otherwise noted inconflict with this chapter.

21.1.2


21.1.3





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The revisions were made to use more positive language.

Response Message:



41 of 128 9/29/2014 10:17 AM


21.3.4

Each initiating device used to initiate fire fighters' service recall Phase I Emergency Recall Operation shall becapable of initiating elevator recall when all other devices on the same initiating device circuit have been manuallyor automatically placed in the alarm condition.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The committee revised the text to be consistent with ASME A17.1 and other parts of this code (alsorevised during the first draft for the same reason).

ResponseMessage:


42 of 128 9/29/2014 10:17 AM


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 thisCode or by other codes and standards shall be required to be accessible for repair, service, testing, andmaintenance from outside the elevator's hoistway.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Paragraph 21.3.5 added by FR 138 is deleted to resolve potential conflicts with building andconstruction code requirement.

ResponseMessage:



43 of 128 9/29/2014 10:17 AM


21.3.6

Smoke detectors shall not be installed in unsprinklered elevator hoistways unless they are installed to activate theelevator hoistway smoke relief equipment or to protect elevator control spaces or elevator machineryspaces initiate Phase I Emergency Recall Operation as required in 21.3.13.121.3.15.1 (2) and21.3.13.221.3.15.2 (2).




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Revised wording more appropriately describes the operation. Smoke detectors really do not "protect"... but they do "initiate".

ResponseMessage:



44 of 128 9/29/2014 10:17 AM


21.3.7*

When sprinklers are installed required in elevator pits, automatic fire detection hoistways by other codes orstandards, fire alarm initiating devices shall be installed to initiate elevator recall 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 shall apply:



(3) Outputs to the elevator controller(s) shall comply with 21.3.1321.3.15 .




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The text is revised to better correlate with the requirements of ASME A17.1 and to clarify theinstallation requirements of NFPA 72.

ResponseMessage:



45 of 128 9/29/2014 10:17 AM


21.3.8*

Smoke detectors shall not be installed in elevator pits hoistways to initiate elevator recall unless the smokedetector is listed for the environment.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The term "pit" has been replaced with "hoistway" because the pit is part of the hoistway. The changealso better correlates with the related annex material.

ResponseMessage:



46 of 128 9/29/2014 10:17 AM


21.3.10

When actuated, any fire alarm initiating device that has initiated is used to initiate elevator Phase 1 EmergencyRecall Operation shall also be annunciated at the building fire alarm control unit or at the fire alarm control unitdescribed in 21.3.2.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The revised text provides consistent terminology throughout the requirement.

Response Message:



47 of 128 9/29/2014 10:17 AM


21.3.11

Actuation from the elevator hoistway, elevator machine room, elevator machinery space, elevator control space,or elevator control room smoke detectors or other automatic fire detection as permitted by 21.3.921.3.10 shallcause separate and distinct visible annunciation at the building fire alarm control unit or at the fire alarm controlunit described in 21.3.2 to alert fire fighters and other emergency personnel that the elevators are no longer safeto use .




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The proposed change eliminates unnecessary wording that is not part of the actual requirement.

Response Message:



48 of 128 9/29/2014 10:17 AM


21.3.14

Where lobby detectors are used for other than initiating elevator recall, the signal initiated by the detector shallalso initiate an alarm signal.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The change removes a potential conflict with 21.3.13.

Response Message:



49 of 128 9/29/2014 10:17 AM


21.3.13.3* Visual Warning Elevator Warning Signal .

For each elevator or group of elevators, an output(s) shall be provided to the elevator controller for the purposeof causing the elevator visual warning signal to operate in response to any of the following:

(1) Activation of the elevator machine room, elevator machinery space, elevator control space, or elevatorcontrol room initiating devices identified in 21.3.13.121.3.15.1 (2) or 21.3.13.221.3.15.2 (2)

(2) Activation of the elevator hoistway initiating devices identified in 21.3.13.121.3.15.1 (3) or21.3.13.221.3.15.2 (3)




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Revised wording more clearly describes the requirement. Editorial changes were made clarify that anyof the outputs will cause the warning signal.

ResponseMessage:



50 of 128 9/29/2014 10:17 AM


21.4.2*

If heat detectors are used to shut down elevator power prior to sprinkler operation, they shall be placed within 24in. (610 mm) of each sprinkler head and be installed in accordance with the requirements of Chapter 17.Alternatively, engineering methods, such as those specified in Annex B, shall be permitted to be used to selectand place heat detectors to ensure response prior to any sprinkler head operation under a variety of fire growthrate scenarios.

21.4.2.1

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




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: There is no term "Sprinkler Head" in the Sprinkler Code NFPA 13.

Response Message:



51 of 128 9/29/2014 10:17 AM



Where one or more elevators are specifically designated and marked as fire service access elevators, theconditions specified in 21.5.1and 21.5.2 shall apply. for the elevators, associated lobbies, and machine roomsshall be continuously monitored and displayed during any such use.

21.5.1*


Availability of main and emergency power to operate the elevator(s), elevator controller(s), and machineroom (if provided) ventilation

Temperature and presence of smoke in associated lobbies and machine room (if provided)

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

21.5.2

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

21.5.3

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




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Elevator system annunciators already provide some of these elements so repeating the information isduplicative and unnecessary. The revised wording would make it permissive to provide this information onthe fire alarm system. Changes were also made to provide consistency of terminology with therequirements in ASME A17.1.

ResponseMessage:


Public Comment No. 110-NFPA 72-2014 [Section No. 21.5 [Excluding any Sub-Sections]]




52 of 128 9/29/2014 10:17 AM


23.1.2

The requirements of Chapters 77, 10, 12, 17, 18, 21, 24, and 26 shall also apply, unless they are otherwisenoted in conflict with this chapter.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The requirement has been modified to provide more positive language.

Response Message:



53 of 128 9/29/2014 10:17 AM


23.6.1.4

The loss of more than one zone shall be permitted on a documented performance-based design approach inaccordance with 7.3.7.4 .




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The text is revised to remove a circular reference between 7.3.7.4 and 23.6.1.4.

Response Message:



54 of 128 9/29/2014 10:17 AM



Class N pathways shall be required to use shared pathway Level 3 as specified in 12.5.4 except as permittedby 23.6.3.1 through 23.6.3.7 .

23.6.3.1

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.2.3 and whenapproved by an AHJ in consideration of the analysis, maintenance, and deployment plans.

23.6.3.1.1

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

23.6.3.2 Deployment Plan.

23.6.3.2.1

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

23.6.3.2.1.1

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

23.6.3.2.1.2

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

23.6.3.2.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.3 Change Control Plan.

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

23.6.3.4 Management Organization.

23.6.3.4.1

An organization shall be established and maintained to manage the life safety network and shall perform thefollowing tasks:

(1) Contain members appropriately certified by each manufacturer of the equipment and devices deployed onshared 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.4.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, anddocumented and appropriate steps are taken during outages to provide alternate protection of life and property.

23.6.3.5 Analysis.

23.6.3.5.1


(1) Calculation of minimum required bandwidth such that all life safety systems can be guaranteed to operatesimultaneously 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


55 of 128 9/29/2014 10:17 AM

23.6.3.5.2


(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 required tosupport the minimum operational capacity requirements

23.6.3.6 Maintenance Plan.

23.6.3.6.1

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

23.6.3.6.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)


(3)


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

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

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

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

23.6.3.7 Other Risks.




72_SR_42_A.23.6.3.6_c_edited.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

With respect to restricting Class N pathways to strictly Level 3 Shared Pathways, members of the TC felt thatit would be counterproductive to provide zero possibility for qualified customers to share other high prioritysystems on this network. It may create a perception of obsolescence out of the gate to provide no pathforward into the future where more and more customers may be qualified to manage integrated life safetynetworks. There are other systems that are involved in life safety and security that can (where appropriate)

* Service outage impairment process with notices of impairment and contingency plans for affectedsystems


56 of 128 9/29/2014 10:17 AM

utilize modern networks and can benefit from shared pathways including nurse call systems, access controlsystems, camera systems, and of course Mass Notification Systems. Less important may be the benefit of theaggregation of port costs, but rather real benefits may be realized in purposeful inter-operation and/orcommon management for those life safety networks.


ResponseMessage:




57 of 128 9/29/2014 10:17 AM





23.6.2.1


23.6.2.2

Class N pathways shall be required to use Shared Pathway Level 3 as specified in Section 12.5.4 .A single faulton a Class N pathway connected to the addressable devices shall not cause the loss of more than oneaddressable device.

23.6.2.3





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The revision added a title the section to improve readability. Also moving the content of 23.6.2.2 to a newproposed section 23.6.3 so that a complex exception to the Shared Pathway Level 3 proposal can bepresented. See SR 42 for section 23.6.3.

ResponseMessage:



58 of 128 9/29/2014 10:17 AM

Second Revision No. 28-NFPA 72-2014 [ New Section after 23.8.2.6.2 ]

23.8.2.6.3

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




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Section 23.8.2.6 deals with fire alarm control units and the sharing of signaling line circuits with otherpremise operating systems. Since this is closely related to shared pathways, should the SLCimplementation be class C it was the intention to draw the reader to the related material in the proposedsection 23.6.3.

ResponseMessage:



59 of 128 9/29/2014 10:17 AM


23.16.2* Power Supplies.

Primary 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:



(3) A low battery signal shall be transmitted before the device is no longer capable of providing 7 days of troublesignal operation followed by the signaling of a single non-trouble response. The low battery signal shall bedistinctive from alarm, supervisory, tamper, and trouble signals; , shall visibly identify the affected low-powerradio transmitter/transceiver; , and, when silenced, shall automatically re-sound at least once every 4 hours.

(4) Catastrophic (open or short) battery failure shall cause a trouble signal identifying the affected low-powerradio transmitter/transceiver at the system control unit. When silenced, the trouble signal shall automaticallyre-sound at least once every 4 hours.








Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Add the attached annex material for A.23.16.2. The annex material would clarify that the intent of thisrequirement is not to prohibit the use of battery operated technology in combination devices but rather tolimit the regional impact from the failure of a battery.

ResponseMessage:


Public Comment No. 224-NFPA 72-2014 [New Section after A.23.16]


60 of 128 9/29/2014 10:17 AM


23.16.3.4

The maximum allowable response delay from activation of an initiating device to receipt and display by thesystem control unit shall occur within 10 seconds. Response time shall be in accordance with 10.12.1 .




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Alarm signal response time is fundamentally addressed by Section 10.12.1

Response Message:



61 of 128 9/29/2014 10:17 AM


23.16.4.2





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The affected device should be identified so that the affected portion of the system is known and so thatthe cause of the problem can be more quickly identified and addressed. This would be consistent with the23.16.4.5 requirement to individually identify the removal of a device.

ResponseMessage:



62 of 128 9/29/2014 10:17 AM

Second Revision No. 34-NFPA 72-2014 [ Sections 23.16.4.6, 23.16.4.7 ]

23.16.4.6


23.16.4.7





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The second sentence in 23.16.4.6 is redundant to the statement in 23.16.4.7. Additionally, the Manualof Style does not permit two requirements in the same numbered item.

ResponseMessage:

Public Comment No. 211-NFPA 72-2014 [Sections 23.16.4.6, 23.16.4.7]


63 of 128 9/29/2014 10:17 AM





(2) All monitoring for integrity requirements of Chapter Chapters 10, Chapter 12, Chapter 23, or 23.16.4 shallapply.

(3) The maximum allowable response delay from activation of an initiating device to activation of required alarmfunctions shall be 10 seconds. Response time shall be in accordance with 10.12.1 .

(4) Each transceiver/system control unit shall automatically repeat activated response signals associated withlife safety events at intervals not exceeding 60 seconds or until confirmation that the output device hasreceived the alarm signal.





Street Address:

City:

State:

Zip:


Committee Statement


Response Message:



64 of 128 9/29/2014 10:17 AM


24.1.3

The requirements of Chapters 7, 10, 12, 17, 18, 21, 23, 26, and 27 shall also apply unless they are otherwisenoted in conflict with this chapter.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The statement was changed into positive language.

Response Message:



65 of 128 9/29/2014 10:17 AM


24.3.6.2* Emergency Message Content.

Emergency messages shall have a content that is:

Appropriate for the intended message recipients

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

Based on the emergency response plan, emergency messages shall have content that provides information andinstructions to people in the building, area, site, or installation.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The language has been revised to coincide with acceptable practices in accordance with the researchprovided to the committee. An annex reference to annex H (see SR-100) has been added while deletingthe current annex material. The paragraph has been renumbered to include all requirements for messagingunder 24.3.7.

ResponseMessage:



66 of 128 9/29/2014 10:17 AM


24.3.1 Intelligible Voice Messages.

Emergency communications systems shall be capable of the reproduction of prerecorded, synthesized, or live(e.g., microphone, telephone handset, and radio) messages with voice intelligibility in accordance with Chapter18 .

24.3.1.1*


24.3.1.2*

Where no listed loudspeaker exists to achieve the intelligibilty requirements of the Code for a notification zone,nonlisted loudspeakers shall be permitted to be installed to achieve the intelligibilty for that notification zone.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

There may be situations where in order to achieve the intelligibility requirements, listed appliances arenot available but non-listed appliances are available to meet the performance requirements of the code.

ResponseMessage:



67 of 128 9/29/2014 10:17 AM


24.3.2* Microphone Use.

All users of systems that have microphones for live voice announcements shall be provided with postedinstructions for using the microphone.

24.3.3.1





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Editorial change to comply with the NFPA Manual of Style.

Response Message:



68 of 128 9/29/2014 10:17 AM


24.3.5.4

The utilization of shared pathway levels, as specified in Section 12.5 , for Class N pathways used in emergencycommunication systems Where emergency communications systems utilize Class N pathways that are alsoshared pathway Level 1 or Level 2 as a means to support ancillary functions, devices, or interconnected systemsvia common pathways, shall be determined by a risk analysis , the shared pathways shall meet the requirementsof 26.6.3 . and approved by the AHJ.

24.3.5.4.1

In addition to the requirements of 23.6.3 , a risk analysis shall be performed and approved by the AHJ.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Editorial modification was made to the original comment for clarity.

Since section 23.6.3 creates requirements for analyzing and documenting a plan to utilize shared pathwaylevel 1 or 2 for life safety networks, this section (which deals with the same issues for MNS) was updatedto include the reference to that 23.6.3.

ResponseMessage:




69 of 128 9/29/2014 10:17 AM


24.3.7* System Classification.

Emergency communications systems (ECS) shall consist of two classifications of systems, be designated asone-way and or two-way.

24.3.7.1

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

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

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

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

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

24.3.7.2

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

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

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

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

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

(5) Stairway communications systems (see Section 24.12 )




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The revised wording provides more clarity. The references were corrected and a new reference tostairway communications was added to complete the list of two-way systems.

ResponseMessage:




70 of 128 9/29/2014 10:17 AM


24.3.10* Control Unit Listing for Mass Notification Systems.

Control units installed as part of a mass notification system shall be in compliance with this Code and at least oneof the following applicable standards: such as ANSI/UL 864, Standard for Control Units and Accessories forFire Alarm Systems; ANSI/UL 2017, Standard for General-Purpose Signaling Devices and Systems ; orANSI/UL 2572, Mass Notification Systems .

(1) ANSI/UL 864, Standard for Control Units and Accessories for Fire Alarm Systems

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

(3) ANSI/UL 2572, Mass Notification Systems .







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Mass Notification systems have matured in technology as well as listings. UL 2572 has been published forseveral years now. It is important to recognize that products must be listed to be used for MNS. As a result,at least one of the applicable standards is necessary to be met in order to provide a level of systemfunctionality and reliability.


ResponseMessage:



71 of 128 9/29/2014 10:17 AM


24.3.13.4.1

For systems employing relocation or partial evacuation, a Level 2 or Level 3 pathway survivability shall berequired.

Exception No. 1: Level 1 shall be permitted where notification or evacuation zones are separated by less than2-hour fire-rated construction.

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




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:


72 of 128 9/29/2014 10:17 AM


24.4.1.2

If acceptable to the authority having jurisdiction, the system shall permit the application of an automaticevacuation signal to one or more evacuation signaling zones and, at the same time, shall permit manual voicepaging to the other evacuation signaling zones selectively or in any combination.




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:


73 of 128 9/29/2014 10:17 AM


24.4.5.6

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




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:


74 of 128 9/29/2014 10:17 AM




24.4.8.1


24.4.8.2

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

24.4.8.3


24.4.8.3.1


24.4.8.3.2

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

24.4.8.4


24.4.8.4.1


24.4.8.4.2

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

24.4.8.5


24.4.8.5.1*


24.4.8.5.2


24.4.8.5.3*

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

24.4.8.5.4

Where the separation of in-building fire emergency voice/alarm control equipment locations results in the portionsof the system controlled by one location being dependent upon the control equipment in other locations, thecircuits between the dependent controls shall be protected against attack by fire by the protection provided by thepathway survivability level required in 24.3.14.4.1 24.3.13.4.1 or by performance alternatives approved by theauthority having jurisdiction.

24.4.8.5.5



75 of 128 9/29/2014 10:17 AM

24.4.8.5.6

Where the separation of the in-building fire emergency voice/alarm control equipment occurs as in 24.4.8.5.4, andwhere the circuits are run through junction boxes, terminal cabinets or control equipment, such as system controlunits, power supplies and amplifiers, and where cable integrity is not maintained, these components shall, inaddition to the pathway survivability required by 24.3.14.4.1 24.3.13.4.1 , be protected by using one of thefollowing methods:

(1) A 2-hour fire- – rated enclosure

(2) A 2-hour fire- – rated room


24.4.8.5.7





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The language has been modified to provide clarity and consistency.

Response Message:



76 of 128 9/29/2014 10:17 AM


24.4.9 Evacuation Signal Zoning.

24.4.9.1*

Undivided fire or smoke areas shall not be divided into multiple evacuation notification signaling zones.

24.4.9.2

If multiple notification appliance circuits are provided within a single evacuation signaling zone, all of thenotification appliances within the zone shall be arranged to activate or deactivate simultaneously, eitherautomatically or by actuation of a common manual control.

24.4.9.3

Where there are different notification appliance circuits within an evacuation a signaling zone that performseparate functions, such as presignal and general alarm signals, and pre-discharge predischarge and dischargesignals, they shall not be required to activate or deactivate simultaneously.




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:


77 of 128 9/29/2014 10:17 AM



Mass notification systems shall require documentation in accordance with Sections 7.3 , 7.4 , and 7.5 inaddition to the minimum documentation requirements of Sections 7.2 and 24.15 .




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: This is duplicate material. See Section 24.15.

Response Message:



78 of 128 9/29/2014 10:17 AM


24.5.14.1

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




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This exception is too general and negates the exception with more detail established in 24.5.15.6. Since24.5.15.6 is part of 24.5.15, the exception is established and does not need to be repeated.

ResponseMessage:



79 of 128 9/29/2014 10:17 AM

Second Revision No. 97-NFPA 72-2014 [ Sections 24.13.4, 24.13.5 ]

24.13.4 Power Supplies.

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

24.13.4.1

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

24.13.4.2

The power supply for the emergency command center for emergency communications systems shall include anuninterrupted power source with capacity sufficient to support the emergency response plan established for thespecific premises.

24.13.5





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Change to comply with the NFPA Manual of Style.

Response Message:



80 of 128 9/29/2014 10:17 AM


26.1.2

The requirements of Chapters 77, 10, 12, 14, and 23 shall also apply unless they are otherwise noted inconflict with this chapter.




Street Address:

City:

State:

Zip:

Submittal Date: Mon Jun 23 19:47:29 EDT 2014

Committee Statement

Committee Statement: The text has been revised to provide more positive code language.

Response Message:



81 of 128 9/29/2014 10:17 AM



Where alarm signal verification is required by other governing laws, codes, or standards, or by other parts of thiscode, by the authority having jurisdiction, or by the responsible fire department in accordance with 26.2.2 , thesupervising station shall immediately notify the communications center that a fire alarm signal has beenreceived and verification is in process.

26.2.3.1

Where alarm signal verification is required by the responsible fire department in accordance with 26.2.2 , thesupervising station shall immediately notify the communications center that a fire alarm signal has beenreceived and verification is in process.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The process of preverification which was added to the 2013 edition of the code adds a confusing step to theverification process. As verification must be required by the responsible fire department to be employed, thedepartment understands there may be a delay in their receiving notification of an alarm condition at aspecified protected premises for up to an additional 90 seconds due to the verification process.


ResponseMessage:





82 of 128 9/29/2014 10:17 AM


27.1.4

The requirements of Chapters 10 and 14 shall also apply unless they are otherwise noted in conflict with thischapter.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The text is revised to provide more positive language.

Response Message:



83 of 128 9/29/2014 10:17 AM


10.5.6 Public Emergency Alarm Reporting System Personnel Qualification. (SIG-PRS)

10.5.6.1 System Designer.

10.5.6.1.1

Public emergency alarm reporting system plans and specifications shall be developed in accordance with thisCode by persons who are qualified in the proper design, application, installation, and testing of public emergencyalarm reporting systems.

10.5.6.1.2

The system design documents shall include the name and contact information of the system designer.

10.5.6.2 System Installer.

Installation personnel shall be qualified in the installation, inspection, and testing of public emergency alarmreporting systems.


Service personnel shall be qualified in the service, inspection, maintenance, and testing of public emergencyalarm reporting systems.


10.5.6.4.1


10.5.6.4.2



(2)


(4)

10.5.6.4.3

Evidence of qualifications and/or certification shall be provided when requested by the authority havingjurisdiction. A license or qualification listing shall be current in accordance with the requirements of the issuingauthority or organization.



SR-2_legislative_changes_for_moved_text.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The committee has relocated 27.3.7 to new 10.5.6 in order to provide a consistent location for allpersonnel qualification requirements. The committee has added a "(SIG-PRS)" tag to this section to retain




84 of 128 9/29/2014 10:17 AM

ownership. As a part of this change, all related annex material is to be moved into this new 10.5.6.


ResponseMessage:



85 of 128 9/29/2014 10:17 AM

Second Revision No. 4-NFPA 72-2014 [ Section No. 27.6.3.2.1.1 ]

27.6.3.2.1.1

The requirements of Chapter 10 , in addition to those of Chapters 14 and 17 , shall apply to auxiliary alarmsystems unless they conflict with the requirements of 27.6.3.2 .




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The requirements of this paragraph appear to be addressing requirements for a protected premises firealarm system. Requirements for these system fall outside the scope of Chapter 27. Deleting the paragraphremoves ambiguous and potentially conflicting requirements. This change helps to resolve a concern raisedby PC 94.

ResponseMessage:


86 of 128 9/29/2014 10:17 AM



Household fire alarm systems utilizing low-power wireless transmission of signals within the protected dwellingunit shall comply with the requirements of Section 23.16, except as modified by 29.7.8.1.1 .

29.7.8.1.1

The requirements of 23.16.4.2 shall not apply where periodic monitoring for integrity complies with all of thefollowing:

(1) Each low-power transmitter/transceiver shall transmit check-in signals at intervals not exceeding 80minutes.

(2) Any transmission interruption between a low-power radio transmitter/transceiver and the receiver/firealarm control unit exceeding 4 hours shall cause a latching trouble signal at the household fire alarmcontrol unit/operator interface.

(3) Low-power transmitters/transceivers shall be limited to serving a single initiating device; however, a singleinitiating device shall be permitted to send multiple types of alarm signals.

(4) Redundant retransmission devices (repeaters) shall be provided such that disconnecting or failure of anysingle retransmission device (repeater) does not interrupt communications between any low-powertransmitter/transceiver and the receiver/fire alarm control unit.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The intent of this text is to leave the existing monitoring for integrity (supervision) requirements of householdfire alarm system utilizing low-power radio (wireless) transmitters unchanged from that in the 2010 editionand in effect prior to June 2013. No data has been presented that demonstrates an issue with the previouspolling period in residential applications. The TC adds an 80 minute check-in requirement to ensure at least3 polling attempts in 4 hours.

ResponseMessage:




87 of 128 9/29/2014 10:17 AM



29.7.8.3.1

Wireless household fire alarm system networks shall meet the requirements of 29.7.8.1 .

29.7.8.3.2


29.7.8.3.3

Shared communications equipment used in supplementary (noncritical) signaling path(s) is permitted to belisted for communications or information technology use.

29.7.8.3.4


29.7.8.3.5

Where the mesh network is shared by other premise operating systems, its operation shall be in accordancewith the following:

Network bandwidth shall be monitored to confirm that all communications between devices critical to theoperation of the fire alarm system take place within 20 seconds; failure shall be indicated within 200seconds.

All programming accepted by devices in the network shall ensure a fire alarm system alarm responsetime of 20 seconds.

All specified configurations of the network shall ensure a fire alarm system alarm response time of 20seconds.

Failure of any equipment that is critical to the operation of the fire alarm system shall be indicated at theoperator interface of the fire alarm control unit by the annunciation of a trouble signal.

The occurrence of any single fault that disables a transceiver shall not prevent other transceivers in thesystem from operating (formerly 29.7.8.2.5 ).




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

While the TC had hoped to establish minimum guidelines for emerging wireless technologies, it becameevident during the comment and revision process that changes in these technologies and products areaccelerating. Drafting language that will ensures a level of safety and still allow for future innovation willrequire knowledge of communication techniques.




88 of 128 9/29/2014 10:17 AM

ResponseMessage:

Public Comment No. 201-NFPA 72-2014 [Sections 29.7.8.3.2, 29.7.8.3.3, 29.7.8.3.4, 29.7.8.3.5]


89 of 128 9/29/2014 10:17 AM


29.8.1.4*

The supplier or installing contractor shall provide the system owner or other responsible parties with the following:

(1) An instruction booklet illustrating typical installation layouts

(2) Instruction charts describing the operation, method, and frequency of testing and maintenance offire-warning equipment

(3) Printed information for establishing an emergency evacuation plan

(4) Printed information to inform system owners where they can obtain repair or replacement service, and whereand how parts requiring regular replacement, such as batteries or bulbs, can be obtained within 2 weeks

(5) Information noting both of the following:

(a) Unless otherwise recommended by the manufacturer's published instructions, smoke alarms shall bereplaced when they fail to respond to tests.

(b) Smoke alarms installed in one- and two-family dwellings shall not remain in service longer than 10years from the date of manufacture.



A.29.8.1.4_Form.docx Figure for A.29.8.1.4





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC adds new annex text. The TC relocated text from CI-56 to this section.

Response Message:


90 of 128 9/29/2014 10:17 AM

Second Revision No. 72-NFPA 72-2014 [ Section No. A.3.3.131 ]






Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The second sentence was poorly written and included conflicting statements.

Response Message:



91 of 128 9/29/2014 10:17 AM


A.10.4.4

The fire alarm control units that are to be protected are those that provide notification of a fire to the occupantsand responders. The term fire alarm control unit does not include equipment such as annunciators andaddressable devices. Requiring smoke detection at the transmitting equipment is intended to increase theprobability that an alarm signal will be transmitted to a supervising station prior to that transmitting equipmentbeing disabled due to the fire condition.


Where the area or room containing the control unit is provided with total smoke detection coverage, additionalsmoke detection is not required to protect the control unit. Where total smoke detection coverage is not provided,the Code intends that only one smoke detector is required at the control unit even when the area of the roomwould require more than one detector if installed according to the spacing rules in Chapter 17. The intent ofselective coverage is to address the specific location of the equipment.





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The requirement to provide notification of a fire condition prior to a control unit(s) or equipment used fortransmitting notification signals being attacked by fire is equally, or in some instances more critical in an ECSor MNS system. This is a "fundamental" requirement that should apply to all signaling system notificationequipment located in areas that are not continuously occupied as specified in 10.4.4. This correlates withthe revisions in 10.4.4.

ResponseMessage:



92 of 128 9/29/2014 10:17 AM


A.10.12.2





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This annex material should be associated with 10.12.2 as indicated in the committee statement forFR-363. The text was editorially revised.

ResponseMessage:



93 of 128 9/29/2014 10:17 AM


A.10.13.2

Where it is desired to deactivate the notification appliances for fire service operations and also provide notificationthat the fire inside the building and signal evacuated occupants that an alarm is still active present , it isrecommended that a separate non-silenceable notification zone be provided that is non-silenceable on theexterior of the building. The audible and visible notification appliances located at the building entrances withaudible and visible notification appliances outside each entrance to the protected building or space. Thesenotification appliances could serve as a warning signal to prevent occupant re-entry during fire serviceoperations .




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Revised wording for improved clarity.

Response Message:



94 of 128 9/29/2014 10:17 AM

Second Revision No. 25-NFPA 72-2014 [ Section No. A.12.3.6(1) ]


95 of 128 9/29/2014 10:17 AM

A.12.3.6(1)


96 of 128 9/29/2014 10:17 AM

Class N consists of pathways between control equipment and devices. The pathways comprise metallicconductor communications cable, such as a 100 ohm balanced twisted-pair (e.g., Category 5E), includingsingle-pair or multi-pair cable, or other communications media such as optical fiber cable or wirelesstransmission, or a combination of two or more of these. Pathways consist of uninterrupted communications mediabetween control equipment and an endpoint device or of a network of multiple interconnected communicationsmedia pathway segments connecting multiple devices. Media pathway segments are created by the use oftransmission equipment such as Ethernet switches, wireless repeaters, or media converters that interrupt anotherwise continuous pathway. Requirements for Class N pathway transmission equipment are not covered inChapter 12 but by other chapters in NFPA 72.

A network of pathway segments is also described as primary pathway segments, redundant pathway segments,or nondesignated pathway segments. Primary and redundant pathways, from control equipment to each device,are independently and continuously verified for their ability to support end-to-end communications to and fromeach endpoint device. Each device will be provided a primary pathway consisting of one or more pathwaysegments. For primary pathway segments that service more than one device, additional redundant pathwaysegments provide alternate verified communication pathways to the devices. Should any primary pathwaysegment fail, communication is supported by the redundant pathway segments. Should either a primary orredundant pathway segment fail, trouble will be indicated by virtue of the continuous verification of all primary andredundant pathway segments. The redundant pathway segments are generally independent and do not normallyshare media with the primary pathways. However, there are exceptions, such as different frequencies for wirelessor ring topologies. [See A.12.3.6(5).]

There is an opportunity to enhance the robustness of a Class N network by providing physically distinct pathwaysegments (i.e., an alternate conduit, or cable tray route, or wireless transmission frequency range, or acombination of distinct media). It is also permissible to provide other nondesignated pathway segments.Additional pathway segments in excess of the minimum requirements of Class N increase the overall robustnessof the network and are often desirable. However, since these additional pathway segments exceed the minimumequipment standards, there is no intention to create an additional monitoring burden, so verification of thesepathways is optional.

For Class N, where a conductor-based media is used, it is not the intention to monitor faults on individualconductors but rather to monitor the operational capability and performance of the pathway as a whole. UnlikeClass C, where multiple pathways are not required, for Class N some pathway segments that carrycommunications for multiple devices (such as Ethernet uplinks or backbones) will have redundant pathwaysegments present. The intention is that any one pathway segment can fail without a loss in operational capabilityto more than one device. For example, connections to control equipment (fire alarm control units, ACUs, orECCUs), where any interruption in communications could potentially affect all devices, would have redundantpathway segments. Additionally, backbone and uplink pathway segments that support communications for morethan one device and are positioned between transmission equipment would also have a redundant pathwaysegment. But the requirement for redundant pathway segments does not apply to those pathway segments usedto service a single device [see Figure A.12.3.6(1)(a) ] .


Input components such as alarm initiating switches, sensors

Output components such as Ethernet speakers (i.e., IEEE 802.3af PoE speakers), strobes, textualsignage, audio amplifiers


The audio amplifier example is included to explain a type of addressable device that can receive a digital audioinput from the Class N pathway but provide a notification appliance circuit (NAC) output to support Class A, B, orX speaker connections. Other similar devices are also possible to provide alternate class pathway connections forstrobes (NACs) or initiating devices (IDCs). From the perspective of the Class N pathway, this is considered anendpoint device. However, since these types of endpoints can support multiple notification appliance devices orinitiating devices, they are subject to the redundant pathway segment requirement and are provided with dualpathway connections.

Control equipment connected to a Class N network for communications with devices would generally utilizeredundant pathway segments. Control equipment connected to other control equipment on a Class N networkwould utilize redundant pathway segments if the control equipment was dependent on any of the pathwaysegments so that a failure of a primary pathway segment in between control equipment could impair the operationof the control equipment [see Figure A.12.3.6(1)(b) ] .

Another utilization of endpoints is permitted for devices providing two connection ports and supporting dualpathway segment connections. The description of endpoint devices is not intended to exclude devices thatsupport dual pathway connections. Since these pathways are servicing a single device, only a single primarypathway connection is required. The second pathway connection exceeds minimum equipment standards and is


97 of 128 9/29/2014 10:17 AM

therefore not required to be verified as a redundant pathway segment; it can be considered connected to anondesignated pathway segment [see Figure A.12.3.6(1)(c) ] .





98 of 128 9/29/2014 10:17 AM

The Class N pathway designation is added to specifically address the use of modern network infrastructure whenused 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 a traditionalSLC multi-drop loop. A device with an Ethernet address is, in most cases, a physical endpoint connected to adedicated cable. Traditional SLC devices are all wired on the same communication line (in parallel), similar to anold party-line telephone system. By comparison, Ethernet’s network switches direct each data packet to itsintended 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 and Class X, andequipment redundancy described in 12.3.7 , is not inherently required of Class N. In other words, failure of asingle switch is permitted take down a class N segment and is only required to report the loss of communication.Where redundant path segments are intended to have survivability similar to Class A or Class X, the physicalseparation requirements and overall equipment redundancy must be specified in addition to the Class Ndesignation.

As a visual model, Class N could be likened to a redundant pathway backbone, allowed to have Class C branchpaths to single endpoint devices. Therefore, every effort is made in this section to clearly distinguish the singleendpoint device from the transport equipment required to have redundant paths.

Class N requires redundant, monitored pathway segments to and from control equipment (fire alarm control units,ACUs, or ECCUs) where any interruption in communications could potentially affect multiple endpoint devices.Typically, interconnected communications equipment such as Ethernet switches, wireless repeaters, or mediaconverters are used in combination to create pathways. Chapter 12 describes the required behavior of Class Npathways. All equipment must meet the requirements of other chapters in NFPA 72 (such as, but not limited to,requirements pertaining to secondary power supplies, equipment listings, and environment conditions).

Redundant pathways, isolated from ground, are actually common practice in robust Ethernet designs. Managednetwork switches commonly have specific uplink ports that are intended for load sharing and allow two parallelconnections. For compliance with Class N, a trouble must be reported if either of these connections fails. [SeeFigure 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 twisted pair(e.g., Category 5E), including single-pair or multi-pair cable, or other communications media, such as optical fibercable or wireless transmission, or a combination of two or more such transport mediums.

Where a conductor-based media is used for Class N, the intention is not to monitor faults on individualconductors but rather to monitor the operational capability and performance of the pathway as a whole. Similar toClass C, end-to-end verification is used in Class N.

Primary and required redundant pathways are independently and continuously verified for their ability to support


99 of 128 9/29/2014 10:17 AM

end-to-end communications to and from each endpoint device and its associated control equipment. Pathwaysegments that service more than one device must have at least one verified redundant pathway segment. Shouldany primary pathway segment fail, communication is supported by the redundant pathway segment(s.) Failure ofeither 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). Inaddition to the required primary segments and redundant segments, a Class N pathway is permitted to havenonrequired segments. [See Figure A.12.3.6(1)(c) .] Additional nonrequired pathway segments are allowed to beconnected and not independently monitored for integrity as long as two paths are monitored to meet theredundancy requirement of Class N.

Figure A.12.3.6(1)(a) Class N Pathway Block Diagram – Example 1.

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 components usedin notification. With respect to Class N, the term device includes appliances and other intelligent, addressablecomponents that perform a programmable input or output function. Examples of Class N devices include thefollowing:

(1) Input components such as alarm initiating modules switches and sensors

(2) Output components such as output modules, Ethernet speakers (i.e., IEEE 802.3af PoE speakers),intelligent strobes, textual signage, and intelligent audio amplifiers

Transmission equipment components (e.g., media converters, Ethernet switches, patch panels, cross-connects)are connected to the Class N pathway merely to transport instructions between other equipment. As such, theyare not considered devices with respect to Class N pathways.


100 of 128 9/29/2014 10:17 AM

The audio amplifier listed above is an example of an addressable device that can receive a digital audio inputfrom the Class N pathway and then provide a notification appliance circuit (NAC) output with Class A, B, or Xpathways. Other endpoint devices can similarly provide alternate class pathways for strobes (NACs) or initiatingdevices (IDCs). From the perspective of the Class N pathway, communications terminates at this endpoint device.However, since these types of endpoints can support multiple notification appliance devices or initiating devices,path segments are subject to the redundant pathway requirement unless protected in an enclosure or racewayless than 20 ft (6 m) in length. [See Figure 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 pathway segments ifa failure of a primary pathway segment in between control equipment could impair the operation of the controlequipment. [See Figure A.12.3.6(1)(d) .]

Figure A.12.3.6(1)(d) Class N Pathway Block Diagram with Multiple Control Units.

Class N is also permitted to include dual port devices that provide both transmission and input/output functions.Endpoint devices can have multiple connection ports and support dual pathway segment connections; thus theterm endpoint device is not intended to prohibit more than one connection to a device. Even with dualconnections, where other devices depend on the path, primary and redundant paths are required. But, where anendpoint device has two connection ports, and when a secondary nonrequired connection is added, there is norequirement to separately supervise the nonrequired redundant pathway segment. [See Figure A.12.3.6(1)(e) .]

Figure A.12.3.6(1)(e)



72_SR_25_A.12.3.6_1_edited.docx




101 of 128 9/29/2014 10:17 AM


Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Editorial and organizational changes were made for improved readability and clarity. Drawings werechanged to make the style more similar to Annex F.


ResponseMessage:






102 of 128 9/29/2014 10:17 AM


A.12.3.6(4)

The operational conditions of the pathway include factors such as latency, throughput, response time, arrival rate,utilization, bandwidth, and loss. It is intended that the life safety equipment connected to a Class N networkactively monitor some or all of the pathway’s operational conditions, so that an improperly installed or configuredpathway, or a subsequently degraded pathway or network of pathway segments is detected by the life safetyequipment and reported as a trouble. This monitoring is intended to be continuous so that a degradation ofpathway performance over time is detected and reported. Trouble would be reported when operational conditionsof the pathway(s) have deteriorated to the point where the equipment is no longer capable of meeting itsminimum performance requirements, even if some level of communication to endpoint devices is still maintained.Examples of performance requirements include the activation of an alarm within 10 seconds, the reporting of atrouble signal within 200 seconds, synchronization of strobes, and delivery of audio messages with requiredintelligibility.

It is possible to have a pathway where end-to-end communications are operational under system idle conditions,but in the event of an alarm, the increased load on a degraded pathway could cause a partial or complete failureto deliver required life safety signals. This is the situation that is intended to be actively detected and reported.

Operational conditions of the pathway include factors such as latency, throughput, response time, arrival rate,utilization, bandwidth, and loss. Life safety equipment connected to a Class N network actively monitors some orall of the pathway’s operational conditions so that an improperly installed or configured pathway or asubsequently degraded pathway or segment is detected by the life safety equipment and reported as a trouble.The trouble condition is reported when operational conditions of the pathway(s) have deteriorated to the pointwhere the equipment is no longer capable of meeting its minimum performance requirements, even if some levelof communication to devices is still maintained. Performance requirements include the activation of an alarmwithin 10 seconds, the reporting of a trouble signal within 200 seconds, and delivery of audio messages withrequired intelligibility. End-to-end communications might be operational under system idle conditions, but in theevent of an alarm, the increased load on a degraded pathway could cause a partial or complete failure to deliverrequired life safety signals. Such predictable failure must be actively detected and reported.







Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Editorial and organizational changes for improved readability and clarity.

Response Message:



103 of 128 9/29/2014 10:17 AM


A.12.3.6(5)

Devices with dual path connections are permitted to be connected to create a daisy chain of devices on a ring. Inthis circumstance they cannot be considered endpoint devices because each pathway segment supports multipledevices; therefore, verified redundant pathway segments would be necessary. This can be accomplished with aring topology, as long as each segment of the ring is verified as functional, and the failure of any one segmentdoes not result in the loss of functionality of more than one device. In this circumstance the requirements forClass N are satisfied by allowing the primary and redundant pathway segments to share the same media byproviding two possible directions of communications on a ring topology [see Figure A.12.3.6(5) ] . Thisconfiguration is fully compliant with 12.3.6 (5).

The daisy chain configuration is also a permissible connection method for multiple control units that requireverified primary and redundant pathway segments.

Figure A.12.3.6(5) Class N Pathway Block Diagram with Dais Chained Devices with Dual PathwayConnection.

Devices with dual path connections are permitted to be connected in a daisy-chain of devices on a ring. Again,where Class N pathway segments support multiple devices, verified redundant pathway segment(s) are required.This can be accomplished with a ring topology, as long as each segment of the ring is verified as functional, andthe failure of any one segment does not result in the loss of functionality of more than one device. In thisarrangement, primary and redundant pathway segments share the same media, and provide two possibledirections of communications in a ring topology [see Figure A.12.3.6(5) ] . This daisy-chain configuration is alsopermitted between multiple control units that require verified primary and redundant pathway segments.

Figure A.12.3.6(5) Class N Pathway Block Diagram with Daisy-Chained Devices with Dual PathwayConnection.



104 of 128 9/29/2014 10:17 AM






Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Editorial and organizational changes are made for improved readability and clarity. The drawing waschanged to make the style more similar to Annex F.

ResponseMessage:



105 of 128 9/29/2014 10:17 AM

Second Revision No. 45-NFPA 72-2014 [ Section No. A.14.4.3.2 ]


106 of 128 9/29/2014 10:17 AM

A.14.4.3.2


107 of 128 9/29/2014 10:17 AM

Table 14.4.3.2, Item 24. The extent of testing of a fire alarm or signaling system, including devices that were nottested, should be documented per in accordance with the Test Plan in 14.2.10. NFPA 72 does not require testingof an emergency control function, such as elevator recall, but does require testing of the emergency controlfunction interface device, such as the relay powered by the fire alarm or signaling system. Where the emergencycontrol function is not being tested concurrent with the fire alarm or signaling system testing, measurement of theemergency control function interface device output should be verified using the proper test devices. This mightrequire reading or observing the condition of a relay, a voltage measurement, or the use of another type of testinstrument. Once testing is complete, verification that any disabled or disconnected interface devices have beenrestored to normal is essential, and this verification should be documented in the testing results.

Testing of the emergency control functions themselves is outside of the scope of NFPA 72. A complete end-to-endtest that demonstrates the performance of emergency control functions activated by the fire alarm or signalingsystem might be required by some other governing laws, codes, or standards, or the authority having jurisdiction.In that situation, other applicable installation standards and design documents, not NFPA 72, would addresstesting and performance of the emergency control functions. NFPA 3, Recommended Practice forCommissioning and Integrated Testing of Fire Protection and Life Safety Systems , provides guidance forintegrated (end-to-end) testing of combined systems. The following excerpt from NFPA 3 includes guidance onwhen integrated testing should be performed.









7.2.3 In addition to periodic integrated testing, integrated system testing should be done when any of thefollowing events occurs:




NFPA 3 also includes guidance on test methods for integrated testing. It is important to note that the appropriateNFPA standard would provide the acceptance criteria for the overall emergency control function operationrequirements, including performance and test methods, whileNFPA 72 covers the required performance andtesting of the emergency function interface device.

For instance, if an end-to-end test for a building with an engineered smoke control system is required by someother governing laws, codes, standards, or the authority having jurisdiction, the test protocol would have uniquecriteria for the smoke control system design, and a special inspector would be responsible for the overalloperation and performance of the smoke control system in accordance with the appropriate standard (NFPA 92,Standard for Smoke Control Systems , and NFPA 101, Life Safety Code ) during the testing, includingmeasuring pressure differentials and ensuring proper fan and damper operation. Refer to the following extractfrom NFPA 101 on smoke control:

9.3.2 System Designer. The engineer of record shall clearly identify the intent of the system, the design methodused, the appropriateness of the method used, and the required means of inspecting, testing, and maintaining thesystem. [101:9.3.2]

9.3.3 Acceptance Testing. Acceptance testing shall be performed by a special inspector in accordance withSection 9.9 9.13 . [101:9.3.3]

Even though the fire alarm or signaling system initiating device might activate the smoke control system, theactual testing of the dampers and fan operation would be as required by the smoke control design and not part ofthe fire alarm or signaling system.

Other emergency control operation requirements might be as follows: For fan shutdown and smoke damperoperation, the fan and damper operations would be in accordance with NFPA 90A, Standard for the Installationof Air-Conditioning and Ventilating Systems , and NFPA 105, Standard for Smoke Door Assemblies and Other


108 of 128 9/29/2014 10:17 AM

Opening Protectives , respectively, and those equipment operations would be verified by those responsible forHVAC systems in combination with the fire alarm system personnel. Guidance for elevator inspection and testingcan be found in ASME A.17.2, Guide for Inspection of Elevators, Escalators and Moving Walks. For elevatorsystems, the recall function, elevator power shutdown, and hat illumination would be done with the elevatormechanics present during the test. This operational test is often accomplished during routine periodic fire alarmtesting. For fire door holder and fire shutter release, it would be expected that the emergency control functionoperation of the doors/shutters would be verified in accordance with NFPA 80, Standard for Fire Doors andOther Opening Protectives , and NFPA 101 during the test. In some cases, the door manufacturer representativemight need to be present to reset the equipment.



If during the course of the periodic test of audible appliances, it is suspected that alarm sound levels could belower than the required minimum, the building system owner or the system owner's designated buildingrepresentative should be notified in writing . Such notification will allow the building owner or designated buildingrepresentative to determine whether sound pressure level readings should be taken for the area(s) in question.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Language was changed to use "system owner or the system owner's designated representative", whichcorrelates the terminology used in other locations within NFPA 72. The TC also added "in writing" to clarifythe medium of notification.

ResponseMessage:



109 of 128 9/29/2014 10:17 AM


A.17.12.2

The waterflow device or the combination of the waterflow devices and fire alarm system should be fieldadjusted configurable so that an alarm is initiated no more than 90 seconds after a sustained flow of at least 10gpm (40 L/min).






Care should be used when choosing waterflow alarm-initiating devices for hydraulically calculated looped systemsand those systems using small orifice sprinklers. Such systems might incorporate a single point flow ofsignificantly less than 10 gpm (40 L/min). In such cases, additional waterflow alarm-initiating devices or the use ofpressure drop-type waterflow alarm-initiating devices might be necessary.



An excess pressure system with an alarm valve consists of an excess pressure pump with pressure switches tocontrol the operation of the pump. The inlet of the pump is connected to the supply side of the alarm valve, andthe outlet is connected to the sprinkler system. The pump control pressure switch is of the differential type,maintaining the sprinkler system pressure above the main pressure by a constant amount. Another switchmonitors low sprinkler system pressure to initiate a supervisory signal in the event of a failure of the pump or othermalfunction. An additional pressure switch can be used to stop pump operation in the event of a deficiency inwater supply. Another pressure switch is connected to the alarm outlet of the alarm valve to initiate a waterflowalarm signal when waterflow exists. This type of system also inherently prevents false alarms due to water surges.The sprinkler retard chamber should be eliminated to enhance the detection capability of the system for shortduration flows.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The waterflow signal activation may be mechanical built into the waterflow device, electronic built intoan intelligent module, or firmware built into the IDC of a fire control panel.

ResponseMessage:



110 of 128 9/29/2014 10:17 AM

Second Revision No. 77-NFPA 72-2014 [ Section No. A.18.1 ]

A.18.1


Notification appliances in conventional commercial and industrial applications should be installed in accordancewith the specific requirements of Section Sections 18.4 and Section 18.5.

The Code recognizes that it is not possible to identify specific criteria sufficient to ensure effective occupantnotification in every conceivable application. If the specific criteria of Section Sections 18.4 and Section 18.5 aredetermined to be inadequate or inappropriate to provide the performance recommended, approved alternativeapproaches or methods are permitted to be used.

Designers and AHJs are advised to consider alternative means in occupancies that have individuals withcognitive disabilities. In addition, persons responsible for evacuation planning should consider specific training forindividuals with cognitive disabilities to familiarize them with audible and visual signals and what responses arenecessary based on their capabilities and any alternative means used.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The new text alerts Authorities Having Jurisdiction, building owners, property managers, testing and servicepersonnel that additional training and notification be given to individuals with special needs and staff so thatan understanding of what to expect during an alarm activation and testing of Protected Premise System’sand the actions that they should take during these conditions. This is important in occupancies wherepersons with cognitive disabilities are expected to be present, such as schools or other institutions.

ResponseMessage:

Public Comment No. 229-NFPA 72-2014 [Section No. A.18.1]


111 of 128 9/29/2014 10:17 AM


A.21.1






Figure A.21.1 Integrated Systems. (Courtesy of R.P. Schifiliti Associates, Inc)




112 of 128 9/29/2014 10:17 AM

G72-352_3_.jpg




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: NFPA 3 was added to provide a more complete set of references.

Response Message:



113 of 128 9/29/2014 10:17 AM

Second Revision No. 16-NFPA 72-2014 [ Sections A.21.3.9, A.21.3.10 ]

A.21.3.8


A.21.3.9

The objective of Phase I Emergency Recall Operation is to have the elevator automatically return to the recalllevel before fire can affect the safe operation of the elevator. This includes both the safe mechanical operation ofthe elevator, as well as the delivery of passengers to a safe lobby location. Where ANSI/ASME A17.1/CSA B44,Safety Code for Elevators and Escalators, specifies the use of smoke detectors, these devices are expected toprovide the earliest response to situations that would require Phase I Emergency Recall Operations. The use ofother automatic fire detection is only intended where smoke detection would not be appropriate due to theenvironment. Where ambient conditions prohibit the installation of smoke detectors, the selection and location ofother automatic fire detection should be evaluated to ensure the best response is achieved. When heat detectorsare used, consideration should be given to both detector temperature and time lag characteristics. Theconsideration of a low temperature rating alone might not provide the earliest response. It should be noted thatsmoke detectors installed in hoistways can be a source of nuisance activation. Therefore, hoistways need smokedetectors specifically intended for those types of spaces (environments).




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The added reference to A.21.3.10 provides addition guidance for heat detector installations.

Response Message:

Public Comment No. 87-NFPA 72-2014 [Sections A.21.3.9, A.21.3.10]


114 of 128 9/29/2014 10:17 AM


A.23.12.4

Off-site logging of fire alarm data can be useful to preserve information in the face of fire or building failure tofacilitate accurate reconstruction of the event. It can also be beneficial to send data off-premises to incidentcommand personnel to enhance situational awareness and response decisions and to maintain safe and efficientoperations. Off-site logging of fire alarm data can be useful to preserve information in the face of fire or buildingfailure to facilitate accurate reconstruction of the event. It can also be beneficial to send data off-premises toincident command personnel to enhance situational awareness and response decisions and to maintain safe andefficient operations. Figure A.23.12.4 shows an example of a network to accomplish these goals.

Figure A.23.12.4 Supplemental Reporting Network.







Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Added a diagram to better illustrate the explanation of supplemental reporting.

Response Message:



115 of 128 9/29/2014 10:17 AM


A.24.3.6.1

The fundamental structure of the prerecorded or live messages is critical for providing information andinstructions that are intelligible. Prerecorded messages created in a controlled environment are considerablymore intelligible than live messages and should be developed and provided to handle as many of the probableemergencies that a particular facility will encounter.

The voice instructions (live or prerecorded) should be preceded by a tone to get attention and prepare the targetaudience for voice instructions. This tone should be differentiated for specific emergencies, based on thestandards for that facility. The actual voice message (live or pre-recorded) should be delivered in awell-enunciated, clear, calm, and deliberate manner, using respectful language. Focus the message on the actionto be taken and minimize wasting words on the cause. For the voice itself, best results will vary, depending on thespecific location — for example, in outdoor applications, it has been shown that a male voice will provide betterintelligibility, as the naturally lower frequency of the male voice travels better. Inversely, in an interior application,where the background ambient noise is typically in the same lower frequencies, a female voice tends to penetratebetter, as it is more distinct from the ambient. Messages should be constructed using 2-second to 3-secondbursts of information and brief periods of quiet between the bursts of information. This methodology facilitatesbetter processing of information by the brain and minimizes the negative effects of reverberation and echo.

Generally, the emergency message should consist of an alert tone of 1 second to 3 seconds, followed by a voicemessage that is repeated at least three times. The alert tone can be used in between repeats of the voicemessage.


Think about what information must be delivered in the live announcement, keep it brief, and write down themessage

Read the message out loud for a practice round in a clear and projecting voice

When you are ready to announce, key the microphone and read the message at least three times

When possible, use an alert tone, such as a Code 3, 1000 Hz signal preceding the message, and thenannounce over the live microphone

Repeat the message a few times more as the emergency warrants

See Annex G .




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The new annex incorporates the material.

Response Message:



116 of 128 9/29/2014 10:17 AM


A.24.3.6.3


What: Guidance on what people should do

When: An idea of when they need to act

Where: Description of the location of the risk of hazard (who should be taking action and who should notbe)

Why: Information on the hazard and danger/consequences

Who: The name of the source of the warning (who is giving it)

Warning style is also crucial and should be specific, consistent, certain, clear, and accurate with attention paid tothe frequency — the more it is repeated, the better.

See Annex G .




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:



117 of 128 9/29/2014 10:17 AM

Second Revision No. 7-NFPA 72-2014 [ Section No. A.26.2.2.1(1) ]

A.26.2.2.1(1)

It is recognized that individual fire departments will have preference on whether verification is used in certainoccupancies based on many variables such as department-specific staffing or response protocols, occupancystaffing, and occupancy risk. This section allows the fire authority to specifically select those occupancies whereverification is allowed. It should be understood that the use of the alarm verification process could delay theresponse to the alarm by up to an additional 90 seconds.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The text added to the annex material provides a cautionary statement to the use of the alarmverification process.

Response Message:


118 of 128 9/29/2014 10:17 AM


A.26.2.2.1(4)

The 90-second allowance for a supervising station to call the protected premise to verify the validity of thereceived alarm signal is independent from in addition to the time allowed for the supervising station to initiate theretransmission to the communications center.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The annex material was revised to add clarity.

Response Message:



119 of 128 9/29/2014 10:17 AM

Second Revision No. 100-NFPA 72-2014 [ New Section after G.3 ]

Annex G Guidelines for Emergency Communication Strategies for Buildings and Campuses

This annex is not part of the requirements of this NFPA document but is included for informational purposesonly.

G.1

The material in this annex is based on the National Institute of Standards and Technology (NIST) and FireProtection Research Foundation research Guidance Document: Emergency Communication Strategies forBuildings , by Erica Kuligowski, Ph.D. and H. Omori, 2014, as adapted by the NFPA ECS TC.

The purpose of this annex is to provide guidance to system designers, building managers, and/or buildingemergency personnel responsible for emergency communication on how to create and disseminate messagesusing basic communication modes (audible and/or visual technology). The guidance provided here is takendirectly from a report published by the National Institute of Standards and Technology, which was based on areview of 162 literature sources from a variety of social science and engineering disciplines (Kuligowski et al.2012) and the prioritization of the specific findings extracted from each literature source.

This document first presents guidance on how to create and disseminate emergency information in the face of

rapid-onset disasters 1 — providing guidance on the dissemination of alert signals, the creation of the warningmessage, the formatting of messages for both visual and audible means, and the dissemination of the warningmessage. This document then provides examples of emergency messages (i.e., message templates) for fivedifferent types of emergency scenarios. These message templates can be altered to fit the needs of youroccupants, as well as the type of emergency that has occurred and type of technology used to disseminate thealerts/messages.

G.2 Guidance on Emergency Communication Strategies.

This section provides guidance for managers, emergency personnel, alarm system manufacturers,codes/standards committees, or others responsible for emergency communication on the ways in which alertsand warning messages should be created, formatted, and disseminated. The guidance is divided into two mainparts: guidance on alerts and guidance on warning messages. Although these two parts often get confused, it isimportant to distinguish between the purpose of an alert and a warning message.

An alert is meant to grab peoples’ attention, notifying them that an emergency is taking place and that thereis important information, which will be provided to them. The purpose of a warning message is to give that

important information to occupants.

Guidance on the construction and dissemination of both alerts and warnings is provided here.

G.2.1 Alerts.

It is imperative to disseminate an alert to let occupants know that a warning message will follow. Regardless ofwhether the warning message is provided audibly, visually, or via tactile means, an alert is necessary to gainpeople’s attention and should be provided separately from the warning message. An effective alert shouldinclude the following characteristics:

(1) Alerts should be significantly different from ambient sounds.

(2) Buildings should reduce background noise when initiating audible alerts.

(3) Flashing, rather than static lights, preferably one standard color for all buildings, can be used to gainattention to visual warning messages.

(4) There are additional methods to alert occupants to an emergency: disruption of routine activities, tactilemethods, social networks, and face-to-face.

(5) An alert signal should be accompanied by a clear, consistent, concise, and candid warning message.

(6) If selected, an alert should be tested for its success in getting occupants’ attention in the event of anemergency and used as part of building- or campus-wide training.

G.2.2 Warnings.

Warning messages should provide information to the occupants on the state of the emergency and what theyare supposed to do in response to this emergency. The warning message should come after an alert signal isgiven and can be provided via visual or audible means. However, before such guidance on message format forvisual and audible messages can be provided, it is vital to provide guidance on the content of the warningmessage itself.


120 of 128 9/29/2014 10:17 AM

G.2.2.1 The Message.


121 of 128 9/29/2014 10:17 AM

Regardless of the method used to disseminate the warning message, there are certain characteristics that arerequired of an effective warning message. These are included here:

(1) Message Content.

(a) A warning message should contain five important topics to ensure that occupants have sufficientinformation to respond.

i. Who is providing the message? (i.e., the source of the message)

ii. What should people do? (i.e., what actions occupants should take in response to theemergency and, if necessary, how to take these actions)

iii. When do people need to act? (In rapid-onset events, the “when” is likely to be “immediately.”)

iv. Where is the emergency taking place? (i.e., who needs to act and who does not)

v. Why do people need to act? (including a description of the hazard and itsdangers/consequences)

(b) The source of the message should be someone who is perceived as credible by the occupants

(c) Building managers, campus managers, and emergency personnel should understand the affectedpopulation and, from this understanding, develop a database of possible trusted sources (as well asbackup sources).

(2) Message Structure.

(a) Message order for short messages (e.g., 90-characters) should be the following:

i. Source

ii. Guidance on what people should do

iii. Hazard (why)

iv. Location (where)

v. Time.

(b) Message order for longer messages should be the following:

i. Source

ii. Hazard

iii. Location

iv. Guidance

v. Time

(c) Numbered lists can help to chronologically organize multiple steps in a process

(d) For limited message length, message writers could draft the message in a bulleted form; each ofthe five topics in the warning should be separated as its own bullet point

(e) Distinct audiences should be addressed separately in the message (or in multiple messages)

(3) Message Language (or Wording).

(a) Messages should be written using short, simple words, omitting unnecessary words or phrases.

(b) Messages should be written using active voice, present tense, avoiding hidden verbs.

(c) Messages should be written using short, simple, and clear sentences, avoiding double negativesand exceptions to exceptions; main ideas should be placed before exceptions and conditions.

(d) Emergency messages should be written at a sixth grade reading level or lower. An emergencymessage can be evaluated for its reading level using computer software and/or a simplecalculation.

(e) Emergency messages should be written without the use of jargon and false cognates.

(f) Emergency messages should be provided in the language of the predominant affected populace. Ifthere is a possibility of isolated groups that do not speak the predominant language, multilingualmessages should be provided. It is expected that small groups of transients unfamiliar with thepredominant language will be picked up in the traffic flow in the event of an emergency and are notlikely to be in an isolated situation.


122 of 128 9/29/2014 10:17 AM

(4) Multiple Messages.

(a) Building managers, campus managers, and emergency personnel should anticipate the need towrite more than one emergency message throughout a disaster, including feedback messages orupdates.

(b) In update messages, occupants should be told why the information has changed, to ensure that thenew message is viewed as credible.

(c) Provide feedback messages after a “non-event” to inform occupants that the alert signal andwarning system operated and worked as planned and the reasons why the event did not occur.

(d) Building managers, campus managers, and emergency personnel should test emergencymessages with the affected population.

(5) Visual Warnings.

(a) Messages that are displayed visually will have different capabilities and limitations than thosedisseminated audibly. Message creators should consider different factors and make different typesof decisions based upon the dissemination method. The first consideration is the type of visualtechnology that will be used to disseminate the messages, which can include textual visualdisplays, SMS text messages, computer pop-ups, email, Internet websites, news (TV broadcast), orstreaming broadcast over the web. Depending upon the technology chosen to display visualwarning messages, guidance is provided here on message displays to enable occupants to see ornotice the displayed warning, understand the warning, perceive warning credibility and risk, andrespond appropriately.

(6) Noticing and Reading the Warning.

(a) Place the emergency sign in a location where people will notice it and be able to read it from theiroriginal (pre-emergency) location.

(b) Signs will be reliably conspicuous within 15 degrees of the direct line of sight.

(c) Text is easier to read when written with a mixture of upper and lower case letters rather than theuse of all capitals.

(d) The recommended relationship for older adults with lower visual acuity is D = 100 * h, providing amore conservative result, and ensuring that a larger population will be able to read the emergencymessage.

(e) A stroke-to-width ratio of the letters is suggested as 1:5 (generally), with a ratio of 1:7 suggested forlighter letters on a darker background.

(f) Building managers, campus managers, or emergency personnel should consult the ADA Standardsfor Accessible Design (U.S. Department of Justice 2010) for additional requirements on signage.

(g) Contrast between the text and the background should be at least 30 percent, althoughrecommended values could be as high as 60 percent.

(h) The use of pictorials (in lieu of or in addition to text) can also bring attention to the sign.

(i) Message providers should ensure that emergency information is not blocked by other signs orinformation.

(7) Comprehending, Believing, and Personalizing the Warning.

(a) Printed text should accompany symbols or pictorials used in visual warnings; a minimum number ofwords should be used to accompany graphics.

(b) Diagrams that display a series of sequential steps are more successful for comprehension of aprocess than one single graphic.

(c) A color-contrasted word or statement should be used for text that should be read first and/or beperceived as more urgent than the rest, unless color is used for other reasons (e.g. bilingual text).

(d) A warning message can increase in perceived credibility and risk if occupants are shown thatothers are also responding.

(e) Simultaneously displayed text (discrete messages) is preferred rather than a sequentially displayedmessage.

(f) Simultaneously displayed text can also be used for bilingual messages, especially if care is taken todifferentiate the text of one language from the text of the other language.

(g) Limit the use of flashing words on visual message displays.


123 of 128 9/29/2014 10:17 AM

(8) Audible Warnings.

(a) There are specific warning technologies that only (or primarily) affect the aural sense, includingpublic address systems (voice notification systems), automated voice dialing, satellite/AM/FM radiobroadcasts, satellite/off-air television broadcasts, and tone alert radios. Whereas visualtechnologies can limit message length, audible warnings are often limited only by the attentioncapabilities of the audience. In other words, an audible message can play for long periods of timewith these technology types, and the message creator and source must be careful to provide allimportant information in an appropriate length of time.

(b) In this section, guidance will be given for methods to increase the likelihood that an individual willperceive, or hear, the message. Following this, guidance will be provided that can increasecomprehension of the message for audible messages, as well as the ways in which to increasecredibility and risk assessment of the event when the warning is presented audibly.

(9) Perception.

(a) Other, non-alert/warning voices in the background should be reduced or eliminated.

(b) Any voice announcements should also be accompanied by simultaneous visual text.


(a) Letters are more difficult to identify in speech than numbers, which are more difficult than colors.

(b) Message speakers (or sources) should not be heavily accented and should speak with a rate ofapproximately 175 words per minute.

(c) Audible warnings can be delivered using a live voice, dynamic voice (generated by text-to-speechsoftware), or using pre-recorded voice.

(d) The live voice and dynamic voice methods provide the benefit of messages that can be updatedwith new information while also conveying an appropriate level of urgency, if necessary.

(e) Dynamic and pre-recoded voice methods provide the benefits of easily repeating the playedmessages for longer periods of time and not relying on the voice announcer training or stress levelwhile delivering the message.

(f) For the voice itself, best results will vary, depending on the specific location — for example, inoutdoor applications, it has been shown that a male voice will provide better intelligibility, as thenaturally lower frequency of the male voice travels better. Inversely, in an interior application, wherethe background ambient noise is typically in the same lower frequencies, a female voice tends topenetrate better, as it is more distinct from the ambient.

(g) Urgency measures should be used selectively to emphasize the more dangerous, immediate,life-threatening situations (since overuse can lead to non-response in future disasters).

(11) Dissemination of the Warning Message.

(a) Use multiple channels to disseminate the warning message, including visual, audible, and tactilemeans.

(b) A warning message should be repeated at least once, with some research advocating for messagerepetition of at least three times.

(c) Messages should be stated in full, and then repeated in full, rather than repeating statements withinthe same message.

(d) Warning messages should be repeated at intervals, rather than consecutively.

(e) Warning messages should be disseminated as early as possible.

(f) Face-to-face communication should accompany other audible or visual technologies.

(g) Messages should be disseminated using a combination of both push and pull technologies.

(h) Push communication 2 is most important to use for alert signals as well as initial warningmessages.

G.3 Emergency Message Templates.


124 of 128 9/29/2014 10:17 AM

Rapid-onset emergencies often come with little warning and can have a major impact on communities. In orderto provide clear, effective instructions for a threatened population, it is important to create message templatesahead of time for a variety of different emergencies.

This section provides examples of message templates for five types of emergency, using various forms ofemergency communication technology. All bracketed text can be altered and replaced with text that better suitsthe needs of the occupants, emergency scenario, emergency response strategies, and the technology beingused. Please see Kuligowski and Omori (2014) for more information on the process associated with thedevelopment of these templates. Each template follows the guidance presented in this document.

G.3.1 Scenario 1 — Fire in a building, partial evacuation strategy, building-wide public address announcements.

Scenario 1 is a fire located on the 10th floor of a 20-story building. Individuals are unable to use elevators in thisscenario, except for those who are unable to negotiate the stairs, in which case building staff or fire fighters willassist them using the freight elevator(s).

Protective actions: Occupants on floors 9, 10, and 11 are told to evacuate to the 8th floor (two floors below thefire floor). All other occupants are provided with a message to remain on their floor. Therefore, in this scenario,two different types of messages are required to be provided simultaneously to occupants, depending upon thefloor on which they are located: one message will be disseminated to floors 9, 10, and 11, while a differentmessage will be disseminated simultaneously to all other floors.

Technology used to disseminate the message: The building-wide public address system, which is capable ofproviding different messages to different floors (using a live voice or a dynamic voice).

G.3.1.1 Message Templates for Scenario 1:

(1) Building-wide announcement to Floors 9, 10, and 11: “Attention [floors 9, 10, and 11]. This is your[Building Safety Officer, Joe Smith]. A fire has been reported on the [10th floor] of the building. Everyoneon the [9th, 10th, and 11th floors] should move to the [8th floor] to be protected from heat and smoke,since heat and smoke can creep into nearby floors during a fire. Use the stairs immediately. Do not usethe elevators. Those who need help getting to the 8th floor, please wait inside the stairwell [or go to thefreight elevator lobby].”

(2) Building-wide announcement to all other floors: “Attention. This is your [Building Safety Officer, JoeSmith]. A fire has been reported on the [10th floor] of the building. Please wait on your floor. At this time,you are safer remaining on your floor than leaving the building, because this building is designed toconfine the fire [e.g., locally or to the 10th floor only]. Do not use the elevators for any reason. We will giveyou further instructions, if the situation changes.”

G.3.2 Scenario 2 — Fire in a building, full evacuation strategy, building-wide public address announcement, andcell phone text message.

Scenario 2 is a fire located on the second floor of a 20-story building in which smoke is traveling up thebuilding’s air-conditioning/venting system, causing the need for a full-building evacuation. Individuals are unableto use elevators in this scenario, except for those who are unable to negotiate the stairs, in which case buildingstaff or fire fighters will assist them using the freight elevator(s).

Protective actions: Occupants on all floors are requested to evacuate the building, known as a full-buildingevacuation.

Technologies used to disseminate the message: The building-wide public address system, which is capable ofproviding different messages to different floors (using a live voice or a dynamic voice). Also, a 90-character textmessage alert to cell phone users in the building.


(1) Building-wide public address system: “Attention. This is [Chief Smith from the Springfield FireDepartment]. A fire has been reported on the [second floor] of the building. Everyone must leave thebuilding now to avoid contact with the fire’s heat and smoke. Go NOW to your closest stair and leave thebuilding. People who cannot use the stairs should go to the freight elevator lobby for help.”

(2) Cell phone text message (90 characters): “Evacuate building now. It is on fire. Go to freight elevator if youneed help.”

Note: A description of the hazard (a more detailed “why” statement) is not included in this message due tocharacter limits. Also, the source is not listed. It is possible that the source will already be identified in the“From” or “FRM” line of the text message. If message contents are limited, there is always the option to send afollow-up text message that provides more information or that continues the previous message. Also rememberthat some phones (i.e. non-smart phones) could display longer text messages in reverse chronological order.


125 of 128 9/29/2014 10:17 AM

G.3.3 Scenario 3 — Tornado imminent on a college campus, campus-wide audible messaging system, andTwitter message.

Scenario 3 is a tornado imminent on a college campus.

Protective actions: The individuals on the college campus are instructed to “shelter in place.” Additionally, theNational Weather Service provides examples of protective actions (included below):

Example 1: “TAKE COVER NOW. FOR YOUR PROTECTION MOVE TO AN INTERIOR ROOM ON THELOWEST FLOOR OF A STURDY BUILDING.”

Example 2: “TAKE COVER NOW. MOVE TO AN INTERIOR ROOM ON THE LOWEST FLOOR OF A STURDYBUILDING. AVOID WINDOWS. IF IN A MOBILE HOME...A VEHICLE OR OUTDOORS...MOVE TO THECLOSEST SUBSTANTIAL SHELTER AND PROTECT YOURSELF FROM FLYING DEBRIS.”

Example 3: “THE SAFEST PLACE TO BE DURING A TORNADO IS IN A BASEMENT. GET UNDER AWORKBENCH OR OTHER PIECE OF STURDY FURNITURE. IF NO BASEMENT IS AVAILABLE...SEEKSHELTER ON THE LOWEST FLOOR OF THE BUILDING IN AN INTERIOR HALLWAY OR ROOM SUCH AS ACLOSET. USE BLANKETS OR PILLOWS TO COVER YOUR BODY AND ALWAYS STAY AWAY FROMWINDOWS.”

IF IN MOBILE HOMES OR VEHICLES...EVACUATE THEM AND GET INSIDE A SUBSTANTIAL SHELTER. IFNO SHELTER IS AVAILABLE...LIE FLAT IN THE NEAREST DITCH OR OTHER LOW SPOT AND COVERYOUR HEAD WITH YOUR HANDS.”

(Examples found here: http://www.nws.noaa.gov/view/validProds.php?prod=TOR)

Technologies used to disseminate the message: A campus-wide siren system with audible messaging

capabilities. Also, a 140-character Twitter 3 message should be disseminated as well for this emergency.


(1) Campus-wide audible messaging system): Alert tone precedes message [siren]. “This is [Joan Smith,Chief of Campus Police]. A tornado has been sighted on the ground at [20th Street and MockingbirdLane]. The tornado is strong and is moving toward the college campus at high speeds (with winds over160 mph). High winds and large, flying debris can flatten a building in a storm of this magnitude. Takeshelter now. Get inside now, go to the lowest level, and get away from windows. Stay there until furtherinstructions.”

(2) Twitter message (140 characters): “Take shelter inside a building NOW. Go to the lowest level, get awayfrom windows. Strong tornado near campus.” [Include hashtag in 140 characters.]

Note: The source of the message is not included in this Twitter message since the source will be evident fromthe Twitter message layout.

G.3.4 Scenario 4 — Chemical spill in a building, building-wide public address announcements, andbuilding-wide email messages.

Scenario 4 is a chemical spill in a 40-story office building. The event was an accident and occurred on the 1stfloor of the building. There is the possibility of the chemical negatively affecting individuals on the lower floors ofthe building. Individuals are unable to use elevators in this scenario. For those who are unable to negotiate thestairs, only one freight elevator will be used with fire-fighter assistance.

Protective actions: Occupants are advised to perform different actions based upon the floor on which they arelocated. First, occupants on the first floor are advised to evacuate the building. At the same time, occupants onfloors 2 through 10 are advised to travel to locations higher in the building — preferably to floors 20 through 30.Concurrently, occupants on floors 11 and above are advised to remain in place. Therefore, in this scenario,three different types of messages are required to be provided simultaneously to occupants, depending upon thefloor on which they are located: one message will be disseminated to the first floor, one message will bedisseminated to floors 2 through 10, and a third message will be disseminated to all other floors.

Technologies used to disseminate the message: The building public address system, which is capable ofproviding different message to different floors (using a live voice or a dynamic voice). Additionally, an emailmessage (through the company’s email system) should be disseminated to employees on floors 2 through 10 torelocate to a higher floor. [ Note: Do not worry about an email to other employees, although in an actualemergency, that would be necessary. ]


126 of 128 9/29/2014 10:17 AM

G.3.4.1

(1) Building-wide public address system: [first floor occupants] “This is your [Building Manager, Joe Smith]. Adangerous chemical has spilled on the first floor. The chemical makes it difficult to see and can causetrouble breathing. Evacuate immediately.”

(2) Building-wide public address system: [floors 2 through 10] “This is your [Building Manager, Joe Smith]. Adangerous chemical has spilled on the first floor. The chemical makes it difficult to see and can causetrouble breathing. Immediately use the stairs to relocate to the [20th through 30th floors], and then wait forfurther instructions. If you can’t use the stairs on your own, go to the freight elevator and wait for help.Relocate now.”

(3) Building-wide public address system: [floors 11 and above] “This is your [Building Manager, Joe Smith]. Adangerous chemical has spilled on the first floor. The chemical makes it difficult to see and can causetrouble breathing. People on [floors 1 through 10] are being evacuated. Please stay on your floor. You aresafer remaining where you are than if you try to leave the building. The chemical will not reach people onfloors 11 and above. You would possibly be exposed to the chemical if you tried to leave the building. Donot use the elevators for any reason. We will give you further instructions if the situation changes.”

Note: Provide emails with the same messages as listed above.

G.3.5 Scenario 5 — Violent event in an airport, airport-wide visual messaging screens, and cell phone textmessage.

The fifth scenario is a violent event. Specially, the emergency involves an active shooter that has been identifiedin a major U.S. airport.

Example protective action: Occupants should evacuate the airport through all accessible doors, including doorsfrom the gate waiting areas onto the tarmac area.

Technologies used to disseminate the message (along with example character limits that can be typical forthese types of technologies): A 90-character text message alert to individuals’ phones within the airport. Also,airport-wide visual messaging screens (limit message to 60 words or less) can be used to alert individuals interminals where the shooter is NOT located.


(1) Airport-wide visual messaging screens: “This is Los Angeles Police. Evacuate the terminal NOW. Followdirections from airport security. Shots have been fired near Gate 22.”

(2) Cell phone text message (90 characters): “Leave NOW. Follow airport security. Shots fired! Policereport: Shooter in Terminal A.”

Note: A description of the hazard (a more detailed “why” statement) is not included in this message due tocharacter limits. If message contents are limited, there is always the option to send a follow-up text messagethat provides more information or that continues the previous message. Also remember that some phones (i.e.,non-smart phones) could display longer text messages in reverse chronological order.

G.4 Future Direction.

The purpose of this report is to provide guidance to system designers, building managers, and buildingemergency personnel responsible for emergency communication on how to create and disseminate effectivemessages using basic communication modes (audible vs. visual technology), as well as examples ofemergency messages (message templates) for five different types of emergency scenarios. START (2013)contains additional message templates for similar types of rapid-onset events for both limited- and unlimited-character length dissemination technologies. Additionally, Kuligowski and Omori (2014) provide guidance onhow to test the effectiveness of these messages.

As with any document, there are gaps in the research that hinder the ability to provide guidance on certaintopics, including message length and repetition. This guidance document focuses specifically on textualmessage creation, creating room for additional guidance on the development and testing of visual symbols thatcould be used instead of, or in addition to, textual emergency messages. In the future, as research gaps areaddressed, additional editions of this document would be useful to enhance the findings and guidance providedhere.


127 of 128 9/29/2014 10:17 AM

G.5 References.

Kuligowski, E.D., S.M.V. Gwynne, K.M. Butler, B.L. Hoskins, and C.R. Sandler, 2012. Developing EmergencyCommunication Strategies for Buildings . Technical Note 1733, National Institute of Standards and Technology:Gaithersburg, MD.

Kuligowski, E.D. and Omori, H., 2014. General Guidance on Emergency Communication Strategies forBuildings, 2nd Edition . NIST Technical Note 1827, National Institute of Standards and Technology:Gaithersburg, MD.

U.S. Department of Justice, September 2010. 2010 ADA Standards for Accessible Design . Washington, DC:DOJ. http://www.ada.gov/2010ADAstandards_index.htm.

START (National Consortium for the Study of Terrorism and Responses to Terrorism), 2013. Task 2.9: Phase IIInterim Report on Results from Experiments, Think-out-Louds, and Focus Groups. University of Maryland,College Park: College Park, MD.

G.6 Footnotes.

1 Rapid-onset emergencies are those emergencies that occur with no or almost no (in the case of minutes)notice, rather than slow-onset events (i.e., emergencies in which the occurrence is known hours or even days inadvance). These different emergency types require different sets of emergency messages and disseminationtechniques to allow building occupants to receive information in a timely manner, resulting in efficient and saferpublic response.

2 Push technologies are those that do not require individuals to take extra effort to receive the alert or warningmessage (e.g., public address systems or text messages), whereas pull technologies require the individual toseek additional information to acquire the alert/message (e.g., Internet websites).

3 Certain commercial entities, equipment, or materials are identified in this document in order to describe anexperimental procedure or concept adequately. Such identification is not intended to imply recommendation orendorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities,materials, or equipment identified are necessarily the best available for the purpose.



72_SR_100_Annex_H_edited.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This annex provides valuable guidance with regard to message content, delivery, and development that isnecessary for a properly designed emergency communications system. This builds on the material includedin FCR 32 which includes reference to NIST Technical Note 1779 which was subsequently issued asTechnical Note 1827.

This annex is based on the Fire Protection Research Foundation Final Report Guidance Document:Emergency Communication Strategies for Buildings which has been modified by the committee to complywith the NFPA manual of style for annex material.

ResponseMessage:


128 of 128 9/29/2014 10:17 AM

NFPA 72 Second Revisions

Document Sort ‐ 102 SRs

SR TC Section Description PC FR PI Notes

102 ECS A.10.12.2 (global)

Moved annex material 19 FR 363 ‐ The global revision was made to document ECS acceptance of relocation of the annex material. See also FUN SR 74 that accepted PC 20 making similar change (w/text edits). CC must adjudicate. [Not in FUN scope.]

105 TMS Annex F (global)

Editorial Update FCR 36 Updated smoke detector symbol in Annex F wiring figures with latest NFPA 170

106 IDS Figure A.17.6.3.1(c) (global)

Editorial Update FCR 36 Updated smoke detector symbol in annex figure with latest NFPA 170

107 HOU Figures A.29.5.1(a) through A.29.5.1(d) (global)

Editorial Update FCR 36 Updated smoke detector symbol in annex figures with latest NFPA 170

31 PRO 23.6.1 (global) + annex

Added title 132 240

FR 31 PI 304

46 TMS 14.4.3.2 (global)

Table Item 17(J) frequencies

124 172

FR 302 ‐

52 NAS 2.3.4 ISO 7731 100 FR 1 PI 254

104 FUN 3.3.3 Readily Accessible FR 88 Extract update – NFPA 70

54 FUN 3.3.11 Alarm 30 FR 161 PI 144

9 PRO 3.3.66.22 (after) + annex

Class N Device 127 128

FR 99 PI 270

10 PRO 3.3.92 (after) + annex

Endpoint (Class N)l 129 130

FR 99 PI 270

78 ECS 3.3.92 Emergency Response Plan

32 FR 345 PI 64

49 HOU 3.3.122 Heat alarm 33 FR 44 ‐ HOU changed ownership from IDS to HOU

55 FUN 3.3.129 Impairment 34 FR 244 PI 149

1 PRS 3.3.168 Network 131 FR 277 ‐

92 ECS 3.3.260 Signaling zone ‐ (See SR 88)

57 IDS 3.3.271 Spacing 37 FR 74 ‐

91 ECS 3.3.317.1 Evacuation zone ‐ (See SR 88)

58 FUN 7.1.6 “conflicts” 88 CCN 23 ‐

59 FUN 7.2.1 Minimum documentation

55 180

FR 267 CCN 1

PI 258 PI 122 PI 21 more

79 ECS 7.5.5 Owners’ manual 220 FR 316 FCR 12

PI 444 PI 628

53 TMS 7.5.8 14.5.1.2.1 relocation 40 FR 294 PI 597 See also SR 56


9 89

60 FUN 7.7.2.6 Electronic Documents 11 239

FR 275 PI 234 PI 604

61 FUN 10.4.4 FACU Protection 12 68 71

FR 247 PI 109

62 FUN 10.5.1.1 Personnel 154 ‐ PI 349

63 FUN 10.5.1.2 Designer 73 155

‐ PI 349

64 FUN 10.5.1.4 (after)

Trainees 142 ‐ PI 349

65 FUN 10.5.2.2 Installers 74 156

‐ PI 349

66 FUN 10.5.2.3 (after)

Trainees 143 ‐ PI 349

67 FUN 10.5.4.3 Inspectors 159 FCR 15 PI 169

68 FUN 10.6.5.1.1 Power source 45 FR 251 PI 474

101 ECS 10.11 + annex

Actuation time 42 ‐ PI 99

41 PRO 12.3.8 Class A & X NA FR 105 ‐

44 TMS 14.2.2.2.4 Impairments/ recalls 85 FR 296 PI 294

51 HOU 14.4.5 + annex

Smoke alarms NA FR 51 ‐

56 TMS 14.6.1.2.1 Reference to 7.5.8 89 ‐ ‐ Also see SR 53

69 NAS 18.4.2.3 Signal Reps/ MNS 227 FR 316 PI 385

70 NAS 18.4.5.3 + annex

Low Frequency 22 ‐ PI 239

71 NAS 18.5.3.2 Pulse Duration 3 83 111

‐ PI 222

23 PRO 21.1 “conflicts” 60 FR 222 CCN 8

PI 566

12 PRO 21.3.4 Phase I recall operation NA (FR 140, FR 299)

11 PRO 21.3.5 Exterior access to devices in hoistway

61 FR 138 CCN 7

13 PRO 21.3.7 Detectors in hoistway 176 ‐ PI 53

14 PRO 21.3.8 Elevator pit 102 ‐ PI 247

15 PRO 21.3.9 Detectors in hoistway 103 ‐ PI 139

17 PRO 21.3.11 Phase I recall annunciation (any device)

104 ‐ PI 179

18 PRO 21.3.12 Phase I recall annunciation (hoistway or machine room devices)

105 FR 141 PI 260

19 PRO 21.3.14 Lobby detector ‐ alarm 107 ‐ PI 259

20 PRO 21.3.15.3 Visual warning 178 FR 231 PI 274


21 PRO 21.4.2 Elevator shutdown 109 ‐ PI 221

22 PRO 21.5 Fire service access elevators

179 110 112

‐ PI 269 PI 378 PI 379

38 PRO 23.1.2 “conflicts” 91 CCN 25 ‐

30 PRO 23.6.1.4 Zones documentation 56 FR 268 CCN 3

PI 365 PI 565

42 PRO 23.6.2 (after) + annex

Class N shared pathways

135 139

FR 122 PI 285 PI 286 PI 287 PI 288

29 PRO 23.6.2 Class N devices 133 FR 122 PI 285 PI 286 PI 287

28 PRO 23.8.2.6.2 Class N shared equipment

136 FR 122 PI 285 PI 286 PI 287

39 PRO 23.16.2 + annex

Wireless power supply 224 221

FR 240 PI 572

40 PRO 23.16.3.4 Wireless response time 206 FR 241 PI 576

33 PRO 23.16.4.2 Wireless trouble 208 FR 242 PI 578

34 PRO 23.16.4.6 23.16.4.7

Wireless trouble 211 FR 242 PI 578

35 PRO 23.16.5 Wireless output signals 202 FR 243 PI 594

81 ECS 24.1.3 “conflicts” 92 CCN 26 ‐

82 ECS 24.3.1 + annex

Emergency Messages 41 ‐ PI 383 Relocation to 24.3.7.2

87 ECS 24.3.2 + annex

Intelligibility – speaker listing

215 ‐ PI 499

83 ECS 24.3.3 Microphone use 123 FR 304 PI 383

84 ECS 24.3.6.4 Class N pathways 137 138

FR 305 PI 497

85 ECS 24.3.8 System classification 125 177

FR 309 PI 413

86 ECS 24.3.11 + annex

Control unit listing 43 FR 311 PI 417 PI 499

93 ECS 24.3.14.4.1 Signaling zones ‐ ‐ ‐ To correlate with SR 88

94 ECS 24.4.1.2 Signaling zones ‐ ‐ ‐ To correlate with SR 88

95 ECS 24.4.5.6 Signaling zones ‐ ‐ ‐ To correlate with SR 88

88 ECS 24.4.8 Signaling zones 63 FR 358 PI 385

96 ECS 24.4.9 Signaling zones ‐ ‐ ‐ To correlate with SR 88

89 ECS 24.5.5 Documentation 175 FR 336 PI 445 PI 631 PI 632

90 ECS 24.5.15.1 Mounting of Controls 210 FR 319 ‐

97 ECS 24.13.4 24.13.5

Power supplies 64 FR 333 CCN 31

PI 431

8 SSS 26.1.2 “conflicts” 93 CCN 27 ‐

5 SSS 26.2.3 Pre‐verification 188 238

FR 17 PI 143 PI 166


195

103 PRS 27.1.4 “conflicts” 94 ‐ ‐

2 PRS 27.3.7 Personnel qualification 65 FR 279 CCN 4

‐

4 PRS 27.6.3.2.1.1 “conflicts” 94 ‐ ‐

48 HOU 29.7.8.1 Wireless systems 82 222

‐ PI 587

47 HOU 29.7.8.3 Mesh networks 201 FR 58 PI 453

50 HOU 29.8.1.4 + annex

Installation documentation

‐ ‐ CI 56

72 FUN A.3.3.131 “In‐writing” 35 FR 165 ‐

73 FUN A.10.4.4 FACU Protection 72 ‐ PI 109

74 FUN A.10.12.3 Occupant notification 20 FR 363 ‐ See SR 102 CC will need to adjudicate

75 FUN A.10.13.2 Appliance deactivation 14 FR 263 ‐

25 PRO A.12.3.6(1) Class N pathways 158 174 196 197

‐ PI 290

32 PRO A.12.3.6(4) Class N pathways 191 FR 103 ‐

27 PRO A.12.3.6(5) Class N pathways 193 FR 103 ‐

45 TMS A.14.4.3.2 Table Item 22 86 FR 297 PI 276

76 IDS A.17.12.2 Waterflow 121 ‐ PI 267

77 NAS A.18.1 Intellectual disabilities 229 FR 80 PI 412

24 PRO A.21.1 Integrated systems 28 FR 222 PI 566

16 PRO A.21.3.9 A.21.3.10

Smoke detectors in hoistway

87 ‐ PI 518

37 PRO A.23.12.4 Supplementary off‐site 194 ‐ PI 290

98 ECS A.24.3.7.1 Message content 217 ‐ PI 384

99 ECS A.24.3.7.2 Message content 218 ‐ PI 384

7 SSS A.26.2.2.1(1) Alarm verification NA ‐ ‐ See SR 6

6 SSS A.26.2.2.1(4) Alarm verification 198 FR 17 PI 164 PI 166

100 ECS G.3 (after) New Annex H FCR 32 CI 343

PI 384

26 Not used

36 Not used

43 Not used

80 Not used


10.12.2Visible notification appliances, textual visible notification appliances, and speaker notification appliances located inthe same area shall be activated and deactivated as a group unless otherwise required by an ECS emergencyresponse plan. (SIG-ECS)10.12.3*Visible alarm strobe notification appliances shall not be activated when speaker notification appliances are used aspermitted by 24.3.6 for nonemergency paging. (SIG-ECS)




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The annex material associated with 10.12.2 should be associated with 10.12.3 as indicated in thecommittee statement for FR-363.

ResponseMessage:



1 of 128 9/29/2014 10:17 AM


Revise the Annex F figures that include a smoke detector symbol (hexagon with a whisp of smoke) so thatthe new smoke detector symbol shown in the latest edition of NFPA 170 is used. The new symbol is ahexagon with the letter "S" as shown in Table 8.3 of the 2015 edition of NFPA 170. The Annex F figures areFigure F.2.3, F.2.4, F.2.5, F.2.6, F.2.7 and F.2.8.



G72-252r1.jpg

G72-49r1.jpg

G72-50r1.jpg

G72-51r1.jpg

G72-52r1.jpg

G72-53r1.jpg




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

NOTICE: This is a Second Revision developed by Staff for editorial purposes so that the smoke detectorsymbol used in Annex F is consistent with the symbol shown in the 2015 edition of NFPA 170. Committeereview has been deemed advisable and the Second Revision is being processed in accordance with section4.4.9.6.3 of the Regulations Governing the Development of NFPA Standards.

ResponseMessage:


2 of 128 9/29/2014 10:17 AM


Revise Figures A.17.6.3.1.1(c) and A.17.7.5.4.2.2(a) to replace the smoke detector symbol (a hexagon with awhisp of smoke) with the smoke detector symbol shown in Table 8.3 of the 2015 edition of NFPA 170 (ahexagon with the letter "S").



G72-216r1.jpg




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

NOTICE: This is a Second Revision developed by Staff for editorial purposes so that the smoke detectorsymbol used in Figures A.17.6.3.1.1(c) and A.17.7.5.4.2.2(a) is consistent with the symbol shown in the2015 edition of NFPA 170. Committee review has been deemed advisable and the Second Revision is beingprocessed in accordance with section 4.4.9.6.3 of the Regulations Governing the Development of NFPAStandards.

ResponseMessage:


3 of 128 9/29/2014 10:17 AM


Revise Figures A.29.5.1(a), A.29.5.1(b), A.29.5.1(c) and A.29.5.1(d) to replace the smoke detector symbol (ahexagon with a whisp of smoke) with the smoke detector symbol shown in Table 8.3 of the 2015 edition ofNFPA 170 (a hexagon with the letter "S").



G72-244r1.jpg

G72-88r1.jpg

G72-269r1.jpg

G72-180r1.jpg




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

NOTICE: This is a Second Revision developed by Staff for editorial purposes so that the smoke detectorsymbol used in Figures A.29.5.1(a) through A.29.5.1.(d) are consistent with the symbol shown in the 2015edition of NFPA 170. Committee review has been deemed advisable and the Second Revision is beingprocessed in accordance with section 4.4.9.6.3 of the Regulations Governing the Development of NFPAStandards.

ResponseMessage:


4 of 128 9/29/2014 10:17 AM


Add "SLC Zones." as a title to 23.6.1 also add attached annex material







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The revision is made for compliance with the manual of style. Also add new annex material as shown inthe attachment. The added annex material further clarifies the SLC zoning requirements.

ResponseMessage:




5 of 128 9/29/2014 10:17 AM

Replace the last sentence at the bottom of A23.6.1 with:

See the definition of zone (3.3.317) and Figure A.23.6.1(a).A through Figure A.23.6.1(d).D for additional

clarification.

Figure A.23.6.1(a).A depicts a Class B SLC with four4 zones. 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 or open occurs beyond the isolators, only one1 zone will be affected.

Note: Section 23.6.2.3 (2) (Lee: x‐ref ok?) allows an un‐isolated circuit in metallic raceway or

other equivalently protected method that does not exceed 3 ft. (1 m) in length.

Figure A.23.6.1(a).A Class B Isolation Method.

See Note

Formatted: Font: Italic

Figure A.23.6.1(b).B depicts a Class A SLC with four4 zones. 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 or open occurs, only one1 zone will be affected. If a single open occurs, no

devices will be affected.

Note: The two2 isolation modules shown at the FACP are not required if the panel SLC controller

is internally isolated from shorts between to (Lee: two?) outgoing and return termination points.

Figure A.23.6.1(b).B Class A Isolation Method.

See Note See Note

Figure A.23.6.1(c).C. depicts a hybrid Class A SLC loop with Class B SLC branches serving four4 zones that

is designated 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

one1 zone will be affected. If a single open occurs, it mightmay affect only one1 zone.

Note: The two2 isolation modules shown at the FACP are not required if the panel SLC controller is

internally isolated from shorts between to (Lee: two?) outgoing and return termination points.

Figure A.23.6.1(c).C Hybrid Isolation Method.

See Note

Figure A.23.6.1(d).D depicts an incorrect Class B SLC configuration with four4 zones. If a single short or

open occurs, one1 or more zones could be affected depending on the location of the single short.

Figure A.23.6.1(d).D Incorrect use of Isolators on an SLC.


In Table 14.4.3.2 item 17(j)(2) through (5) change "Quarterly" to "Annually" in four (4) places.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

NFPA 72 establishes the requirements for fire alarm switch testing frequency. The statistical failure ratesof electronically supervised mechanical switches are extremely small. In a 3-year cycle, there was noevidence to suggest that more than an annual frequency was necessary.

ResponseMessage:




6 of 128 9/29/2014 10:17 AM




ISO 7731, Danger signals for work places — Auditory danger signals, 2003 (Reconfirmed 2009) .




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Reference updated.

Response Message:



7 of 128 9/29/2014 10:17 AM


3.3.3 Accessible, Readily (Readily Accessible).

Capable of being reached quickly for operation, renewal, or inspections without requiring those to whom readyaccess is requisite to actions such as to use tools, to climb over or remove obstacles or to resort to portableladders, and so forth. [70, 2011 70: 100 ] (SIG-FUN)




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

NOTICE: This is a Second Revision developed by Staff for editorial purposes so that the extract definitionfrom the NEC is up to date with the definition in the 2014 edition of the NEC. Committee review has beendeemed advisable and the Second Revision is being processed in accordance with section 4.4.9.6.3 of theRegulations Governing the Development of NFPA Standards.

ResponseMessage:


8 of 128 9/29/2014 10:17 AM


3.3.11 Alarm.





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Change "action" to "response" to be consistent with the defined condition-signal-response modeladopted in the 2013 edition. We need to cascade the use of these three terms throughout the code.

ResponseMessage:



9 of 128 9/29/2014 10:17 AM


3.3.67* Device (Class N).

A supervised component of a life safety system that communicates with other components of life safety systemsand that collects environmental data or performs specific input or output functions necessary to the operation ofthe life safety system.

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) that are required to provide the real-time functionalitynecessary for the protection of life and property. In this way, a component connected to the network used fornoncritical functions (i.e., maintenance) can be differentiated and excluded from the monitoring for integrityrequirements 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 if they donot provide life safety–specific environmental monitoring, inputs, or outputs for the life safety system. This is notto say that this equipment is not important to the overall operation of the system, just that this equipment is notconsidered a “device” in the context of Class N. Equipment that does not meet the definition of a device cannotbe specifically supervised but rather generally supervised as they are part of the supervised pathways thatservice the Class N devices themselves.



72_SR_9_Class_N_definition_edited.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

With the addition of Class N pathways in the first draft, the term “device” was used with specificity in thecontext of Class N, but not defined. This revision also adds related annex to illustrate examples of what isa Class N device and how the distinction is drawn.

ResponseMessage:




10 of 128 9/29/2014 10:17 AM

3.3.X 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) that are required to provide the real-time functionality necessary for the protection of life and property. In this way, a component connected to the network used for noncritical functions (i.e., maintenance) can be differentiated and 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 if they do not provide life safety–specific environmental monitoring, inputs, or outputs for the life safety system. This is not to say that this equipment is not important to the overall operation of the system, just that this equipment is not considered a “device” in the context of Class N. Equipment that does not meet the definition of a device cannot be specifically supervised but rather generally supervised as they are part of the supervised pathways that service the Class N devices themselves.


3.3.94* Endpoint (Class N).




72_SR_10_Endpoint_Annex_material_edited.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

With the addition of Class N pathways in the first draft, the term “endpoint” was used with specificity inthe context of Class N, but not defined. Related annex material is also added.

ResponseMessage:




11 of 128 9/29/2014 10:17 AM

3.3.X Endpoint (Class N). An endpoint device originates and/or terminates a communication stream and does not forward it to other devices.

An FACU, ACU, ECCU endpoint originates and/or terminates a communication stream with autonomy. If data is sent to or received from other locations, that communications stream forms a new path. The new path could even employ a different communications protocol and, where permitted, have a different pathway 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 when connected to a single endpoint device. However, a connection to an FACU, ACU, or ECCU must be redundant even when those elements are an endpoint on a Class N communication path, with the excepted allowance of 20 ft (6 m) inside a raceway or enclosure defined in 12.6.9.



A documented set of actions to address the planning for, management of, and response to natural, technological,and man-made disasters and other emergencies. (SIG-ECS)




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

An emergency plan includes an emergency response plan - plus other elements like a pre-plan and acommunications plan – that leads to the ECS needs assessment.

ResponseMessage:



12 of 128 9/29/2014 10:17 AM


3.3.124 Heat Alarm.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The TC changes SIG-IDS to SIG-HOU. The TC revises the definition to delete the example as it isnot required.

Response Message:



13 of 128 9/29/2014 10:17 AM

Second Revision No. 55-NFPA 72-2014 [ Section No. 3.3.129 [Excluding any Sub-Sections] ]

3.3.131* Impairment.





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Editorial correction.

Response Message:

Public Comment No. 34-NFPA 72-2014 [Section No. 3.3.129 [Excluding any Sub-Sections]]


14 of 128 9/29/2014 10:17 AM


3.3.170 Network.

3.3.170.1 Wired Network (Public Emergency Alarm Reporting Systems) .


3.3.170.2 Wireless Network (Public Emergency Alarm Reporting Systems) .





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The definitions for the terms “Wireless Network” and "wired network" are unique to the requirement ofChapter 27 and labels were added to recognize this distinction. Networks are used in other places in thecode and these definitions would not necessarily be applicable to the other usages.

ResponseMessage:



15 of 128 9/29/2014 10:17 AM


3.3.260 Signaling Zone.

See 3.3.320 , Zone.




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:


16 of 128 9/29/2014 10:17 AM


3.3.274 Spacing.

A horizontally measured dimension related to used as a criterion in determining the allowable coverage ofdetectors devices . (SIG-IDS)




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

SIG-IDS: Spacing relates to more than just detectors.


Response Message:



17 of 128 9/29/2014 10:17 AM


3.3.320.2* Evacuation Signaling Zone.

An area consisting of one or more notification zones where signals are actuated simultaneously. (SIG-ECS)




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:


18 of 128 9/29/2014 10:17 AM


7.1.6

The requirements of other chapters shall also apply unless they are in conflict with Chapters 10 , 12 , 14 , 17 ,18 , 21 , 23 , 24 , 26 , and 27 shall apply unless otherwise noted in this chapter.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The section was revised to avoid the term "conflicts", since the code should not contain conflicts.

Response Message:



19 of 128 9/29/2014 10:17 AM


7.2.1*

Where documentation is required by the authority having jurisdiction, the following list shall represent theminimum documentation required for new fire alarm systems, supervising station and shared communicationequipment, and emergency communications systems, including new systems and additions or alterations toexisting systems:

(1)

(2) Riser diagram









(7) Battery capacity and de-rating calculations (where batteries are provided)





(11) Pathway diagrams between the control unit, and the supervising station and shared communicationsequipment

(12) Completed record of completion in accordance with 7.5.67.5.6 7.5.7 and 7.8.2




(16) Completed record of inspection and testing in accordance with 7.6.6 and 7.8.2




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

A requirement for documented power loss dB calculations is redundant to the requirements fordocumenting the minimum sound pressure levels that must be produced by the audible notification



20 of 128 9/29/2014 10:17 AM

appliances in the applicable covered areas and the requirement for voltage drop calculations for notificationappliance circuits. The definition of "notification appliance circuit" includes the pathway connecting anamplifier to one or more speakers.



ResponseMessage:




21 of 128 9/29/2014 10:17 AM


7.5.5

Owner’s manuals for emergency communications systems shall be in accordance with Section 24.15 .(SIG-ECS)




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The reference points to a section that points directly back to Chapter 7.

Response Message:



22 of 128 9/29/2014 10:17 AM


7.5.7 Site-Specific Software. (SIG-TMS)

Site-specific software documentation shall be in accordance with 14.6.1.2 . (SIG-TMS)

See SR-56

7.5.7.1

For software-based systems, a copy of the site-specific software shall be provided to the system owner or owner’sdesignated representative.

7.5.7.1.1

The site-specific software documentation shall include both the user passcode and either the systemprogramming password or specific instructions on how to obtain the programming password from the systemmanufacturer.

7.5.7.1.2

The passwords provided shall enable currently certified qualified programming personnel to access, edit,modify, and add to the existing system site-specific software.

7.5.7.2





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Section 14.6.1.2 and related annex material has been relocated to become 7.5.8. Moving the requirementsfor site-specific software to Chapter 7.5.8 will improve usability of the Code by placing the site-specificsoftware documentation requirements in the “Documentation” chapter. A reference pointer to 7.5.8 hasbeen added to 14.6.1.2 by SR 56.


ResponseMessage:





23 of 128 9/29/2014 10:17 AM


7.7.2.6*





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The first draft text does not indicate who is responsible for maintaining electronic documents formats sothat they remain accessible. The building owner (or their representative) should be responsible for keepingthe formats current because the documents are their property. The revised text is clearer and indicates thatthe building owner or their representative is responsible.

ResponseMessage:




24 of 128 9/29/2014 10:17 AM


10.4.4*

In areas that are not continuously occupied, an automatic smoke detector shall be provided at the location of eachfire alarm control unit(s), notification appliance circuit power extenders extender(s) , and supervising stationtransmitting equipment. The location of the required detector shall be in accordance with 17.7.3.2 to providenotification of fire at that location .





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The text, "the location of the required detector shall be in accordance with 17.7.3.2," was deleted because itwould require full detection coverage for the area. The intent of 10.4.4 is to provide detection for a specifichazard at the equipment location so that fire is likely to be detected before the equipment is disabled. Therequirement to provide notification of a fire condition before equipment is disabled by fire should apply toemergency communication system signaling because of the analogous life safety purpose of ECS.

ResponseMessage:





25 of 128 9/29/2014 10:17 AM


10.5.1.1





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: This revision deletes the word "proper" from the section, because it is unnecessary.

Response Message:



26 of 128 9/29/2014 10:17 AM


10.5.1.2




Personnel who are factory trained and certified for fire alarm system design and/or emergencycommunication system design of the specific type and brand of system and who are acceptable to theauthority having jurisdiction

10.5.1.3








Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The TC maintains the requirement to follow state or local licensure regulations. The text has beenrevised to address the submitters concerns regarding the use of the term “nationally recognized” as beingoverly restrictive.

ResponseMessage:




27 of 128 9/29/2014 10:17 AM


10.5.1.5

System design trainees shall be under the direct supervision of a qualified system designer.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:


ResponseMessage:



28 of 128 9/29/2014 10:17 AM


10.5.2.2




Personnel who are factory trained and certified for fire alarm system installation and/or emergencycommunications system installation of the specific type and brand of system and who are acceptable to theauthority having jurisdiction

10.5.2.3








Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The TC maintains the requirement to follow state or local licensure regulations. The text has beenrevised to address the concerns regarding the use of the term “nationally recognized” as being overlyrestrictive.

ResponseMessage:




29 of 128 9/29/2014 10:17 AM


10.5.2.4

System installation trainees shall be under the supervision of a qualified system installer.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:


ResponseMessage:



30 of 128 9/29/2014 10:17 AM


10.5.4.3



Personnel who meet the requirements of NFPA 1031, Standard for Professional Qualifications for FireInspector and Plan Examiner

Personnel who are assigned to perform plan reviews and inspections by the authority having jurisdiction

10.5.4.4

Personnel shall provide documentation of their qualifications by one or more of the following:


(2) Meeting the requirements of NFPA 1031

(3) Assignment by the authority having jurisdiction to perform plan reviews and inspections




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The TC maintains the requirement to follow state or local licensure regulations. The committee hasclarified the options permitted to demonstrate qualification.

ResponseMessage:



31 of 128 9/29/2014 10:17 AM


10.6.5.1.1



(2) An engine-driven generator or equivalent in accordance with 10.6.11.2, where a person trained in itsoperation is on duty at all times

(3) An engine-driven generator or equivalent arranged for cogeneration with an electric utility in accordance with10.6.11.2, where a person trained in its operation is on duty at all times




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The phrase "or equivalent" should not have been removed. While Chapter 1 has language permitting anequivalent means, the term is necessary here to provide immediate context. Without it an engine drivengenerator is the only implied choice and does not allow for other choices that are not connected to ordependent upon the utility.

ResponseMessage:



32 of 128 9/29/2014 10:17 AM


10.11* ECS Priority Signals Actuation Time .

Visible indication of priority signals shall be automatically indicated within 10 seconds at the fire alarm control unitor other designated location. (SIG-ECS) Actuation of alarm notification appliances or emergency voicecommunications, emergency control function interface devices, and annunciation at the protected premises shalloccur within 10 seconds after the activation of an initiating device.



72_SR_101_A.10.11_edited.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

SIG-ECS: The action at the first draft entirely deleted section 23.8.1.1 regarding signals. The lost annexmaterial from A.23.8.1.1 was added to A.10.11. The TC suggests that the Correlating Committee review10.12 as similar material to 10.11.


ResponseMessage:



33 of 128 9/29/2014 10:17 AM

A.10.11 Actuation of an initiating device is usually the instant at which a complete digital signal

is achieved at the device, such as a contact closure. For smoke detectors or other automatic

initiating devices, which can involve signal processing and analysis of the signature of fire

phenomena, actuation means the instant when the signal analysis requirements are completed by

the device or fire alarm control unit software. A separate fire alarm control unit contemplates a

network of fire alarm control units forming a single large system as defined in Section 23.8. For

some analog initiating devices, actuation is the moment that the fire alarm control unit interprets

that the signal from an initiating device has exceeded the alarm threshold programmed into the

fire alarm control unit. For smoke detectors working on a system with alarm verification, where

the verification function is performed in the fire alarm control unit, the moment of actuation of

smoke detectors is sometimes determined by the fire alarm control unit.

It is not the intent of this paragraph to dictate the time frame for the local fire safety devices to

complete their function, such as fan wind-down time, door closure time, or elevator travel time.


12.3.8*

Class A, Class N, and Class X circuits using physical conductors (e.g., metallic, optical fiber) shall be installed sothat the primary and redundant, or outgoing and return conductors, exiting from and returning to the control unit,respectively, are routed separately. The outgoing and return (redundant) circuit conductors shall be permitted inthe same cable assembly (i.e., multiconductor cable), enclosure, or raceway only under the following conditions:

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

Single drops installed in raceway to individual devices or appliances

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)




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

"Class N" is deleted from this paragraph because it was inadvertently added during the First Draft. Theseparation requirements of this paragraph do not actually apply to Class N.

ResponseMessage:

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

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


34 of 128 9/29/2014 10:17 AM


14.2.2.2.4

In the event that any equipment is observed to be part of a recall program, the building owner system owner orthe system owner's designated representative shall be notified in writing .




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The wording of 14.2.2.2.4 was changed to be similar to the verbiage in the existing Section14.2.2.2.3.

Response Message:



35 of 128 9/29/2014 10:17 AM


14.4.5 Single- and Multiple-Station Smoke Alarms. (SIG-HOU)

14.4.5.1

Smoke Single- and multiple-station smoke alarms and all connected appliances shall be inspected, tested, andmaintained in accordance with 14.4.5 and the manufacturer's published instructions at least monthly . Theresponsibility for inspection, testing and maintenance shall be in accordance with 14.2.3 . (SIG-HOU)

14.4.5.2

Single- and multiple-station smoke Smoke alarms and shall be connected appliances shall be inspected andtested at least monthly replaced when they fail to respond to operability tests but shall not remain in servicelonger than 10 years from the date of manufacture, unless otherwise recommended by the manufacturer’spublished instructions . (SIG-HOU)

14.4.5.3*

Combination smoke/carbon monoxide alarms shall be replaced when the end-of-life signal activates or 10 yearsfrom the date of manufacture, whichever comes first. (SIG-HOU) The responsibility for inspection, testing, andmaintenance of smoke alarms and connected appliances shall be in accordance with 14.2.3 .

14.4.5.4

Where batteries are used as a source of energy for combination smoke/carbon monoxide alarms or single- andmultiple-station smoke alarms, the batteries shall be replaced in accordance with the alarm equipmentmanufacturer’s published instructions. (SIG-HOU) Smoke alarms shall be replaced when they fail to respond tooperability tests.

14.4.5.4.1

Smoke alarms shall not remain in service longer than 10 years from the date of manufacture, unless otherwiseprovided by the manufacturer’s published instructions.

14.4.5.5*

Combination smoke/carbon monoxide alarms shall be replaced when the end-of-life signal activates or 10 yearsfrom the date of manufacture, whichever comes first, unless otherwise provided by the manufacturer's publishedinstructions.

14.4.5.6

Where batteries are used as a source of energy for smoke alarms or combination smoke/carbon monoxidealarms or single- and multiple-station smoke alarms, the batteries shall be replaced in accordance with thealarm equipment manufacturer’s published instructions.







Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC clarifies the application of Section 14.4.5.

Response Message:


36 of 128 9/29/2014 10:17 AM

A.14.4.5.3 It is intended that smoke alarms and connected appliances be considered as a

“fire protection system” for the purpose of applying the responsibility provisions in

14.2.3.

A.14.4.5.5 Carbon monoxide alarm replacement is covered under NFPA 720.


14.6.1.2 Site-Specific Software.

The requirements of 7.5.8 shall apply to site-specific software.

Moved by SR-53

14.6.1.2.1

For software-based systems, a copy of the site-specific software shall be provided to the system owner orowner’s designated representative. The site-specific software documentation shall include either the systemprogramming password or specific instructions on how to obtain the password from the system manufacturer.

14.6.1.2.1





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Moving the requirements for site-specific software to Chapter 7 with a reference to the appropriate sectionin Chapter 7 will improve usability of the Code by placing the site-specific software documentationrequirements in the “Documentation” chapter. It is understood that SIG-TMS will retain control of anychanges to the requirements. Refer to SR 53 for the relocated material.

ResponseMessage:


37 of 128 9/29/2014 10:17 AM


18.4.2.3

The signal shall be repeated for a period appropriate for the purposes of evacuation of the building, but for notless than 180 seconds. The minimum repetition time shall be permitted to be manually interrupted.

18.4.2.3.1

The minimum repetition time shall be permitted to be manually interrupted.

18.4.2.3.2

The minimum repitition time shall be permitted to be automatically interrupted for the transmission of massnotification messages in accordance with Chapter 24 .




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This statement seems inconsistent with the intention of MNS systems. Based on circumstances, MNS mayemploy automatic messages to direct occupants under various emergency situations. This section requiresthat evacuation signals may not be automatically interrupted for three minutes. In that time, people may haveresponded (or not responded) inappropriately because the nature of the emergency or the proper actionscould not be made clear to occupants in time. A reference to Chapter 24 was added for correlation. Inaddition, the section was revised to meet the Manual of Style.

ResponseMessage:



38 of 128 9/29/2014 10:17 AM


See SR-70

18.4.5.3*

Effective January 1, 2014, audible Audible appliances provided for the sleeping areas to awaken occupants shallproduce a low frequency alarm signal that complies with the following:

(1) The alarm signal shall be a square wave or provide equivalent awakening ability.

(2) The wave waveform shall have a fundamental frequency of 520 Hz ± 10 percent.

(3)



72_SR_70_A.18.4.5.3_3_edited.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The effective date was eliminated, since it has passed. Reference to product listing was added to ensurethat the correct waveform, frequency, and harmonics are included in the appliance performance.

ResponseMessage:


* The notification equipment shall be listed for producing the low frequency waveform.


39 of 128 9/29/2014 10:17 AM

A.18.4.5.3(3) For the purposes of awakening, the low frequency signal can be

produced by a listed stand-alone appliance or by a listed system consisting of a

recorded waveform delivered through an amplifier and loudspeaker.


18.5.3.2*

A The maximum light pulse duration shall be 0.2 second 20 milliseconds with a maximum duty cycle of 40percent.

Exception: Lights used to meet the requirements of 18.5.5.5 shall be permitted to be listed and labeled to havepulse durations up to 100 milliseconds.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This change is needed because research has shown that the use of longer pulse widths with lights ratedusing the concept of candela effective will result in poor detection performance. Longer pulse widths must becombined with some as yet undetermined increase in peak candela intensity in order to be effective.However, the research has shown that strobes rated using candela effective and that have pulse widths up to100 ms can be effective in corridor, direct viewing application. Thus the allowance for their use in corridorswas needed. Additional work is being done to determine how the code should be modified to have aperformance metric that will work for lights with both long and short pulse durations.

ResponseMessage:





40 of 128 9/29/2014 10:17 AM

A.18.5.3.2 New research using lights with longer pulse durations shows that the existing tables for indirect signaling [Table 18.5.5.4.1(a) and Table 18.5.5.4.1(b)] are inadequate to assure reliable notification. Until additional work is done and incorporated into this Code, lights used for indirect signaling and having effective intensities specified in Table 18.5.5.4.1(a) or Table 18.5.5.4.1(b) need to be short duration, high intensity to be effective for the specified area of coverage. This limitation does not apply to direct signaling such as that used in corridors per in accordance with 18.5.5.5. For direct signaling in corridors (18.5.5.5), longer pulse appliances (up to 100 ms) (SI?), such as LED lights, have been shown to be effective. Longer pulse durations might also be effective in large volume spaces that use direct signaling, as discussed in A.18.5.4.


21.1* Application.


21.1.1

The requirements of Chapters 7, 10, 17, 18, 23, 24, and 26 shall apply, unless they are otherwise noted inconflict with this chapter.

21.1.2


21.1.3





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The revisions were made to use more positive language.

Response Message:



41 of 128 9/29/2014 10:17 AM


21.3.4

Each initiating device used to initiate fire fighters' service recall Phase I Emergency Recall Operation shall becapable of initiating elevator recall when all other devices on the same initiating device circuit have been manuallyor automatically placed in the alarm condition.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The committee revised the text to be consistent with ASME A17.1 and other parts of this code (alsorevised during the first draft for the same reason).

ResponseMessage:


42 of 128 9/29/2014 10:17 AM


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 thisCode or by other codes and standards shall be required to be accessible for repair, service, testing, andmaintenance from outside the elevator's hoistway.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Paragraph 21.3.5 added by FR 138 is deleted to resolve potential conflicts with building andconstruction code requirement.

ResponseMessage:



43 of 128 9/29/2014 10:17 AM


21.3.6

Smoke detectors shall not be installed in unsprinklered elevator hoistways unless they are installed to activate theelevator hoistway smoke relief equipment or to protect elevator control spaces or elevator machineryspaces initiate Phase I Emergency Recall Operation as required in 21.3.13.121.3.15.1 (2) and21.3.13.221.3.15.2 (2).




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Revised wording more appropriately describes the operation. Smoke detectors really do not "protect"... but they do "initiate".

ResponseMessage:



44 of 128 9/29/2014 10:17 AM


21.3.7*

When sprinklers are installed required in elevator pits, automatic fire detection hoistways by other codes orstandards, fire alarm initiating devices shall be installed to initiate elevator recall 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 shall apply:



(3) Outputs to the elevator controller(s) shall comply with 21.3.1321.3.15 .




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The text is revised to better correlate with the requirements of ASME A17.1 and to clarify theinstallation requirements of NFPA 72.

ResponseMessage:



45 of 128 9/29/2014 10:17 AM


21.3.8*

Smoke detectors shall not be installed in elevator pits hoistways to initiate elevator recall unless the smokedetector is listed for the environment.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The term "pit" has been replaced with "hoistway" because the pit is part of the hoistway. The changealso better correlates with the related annex material.

ResponseMessage:



46 of 128 9/29/2014 10:17 AM


21.3.10

When actuated, any fire alarm initiating device that has initiated is used to initiate elevator Phase 1 EmergencyRecall Operation shall also be annunciated at the building fire alarm control unit or at the fire alarm control unitdescribed in 21.3.2.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The revised text provides consistent terminology throughout the requirement.

Response Message:



47 of 128 9/29/2014 10:17 AM


21.3.11

Actuation from the elevator hoistway, elevator machine room, elevator machinery space, elevator control space,or elevator control room smoke detectors or other automatic fire detection as permitted by 21.3.921.3.10 shallcause separate and distinct visible annunciation at the building fire alarm control unit or at the fire alarm controlunit described in 21.3.2 to alert fire fighters and other emergency personnel that the elevators are no longer safeto use .




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The proposed change eliminates unnecessary wording that is not part of the actual requirement.

Response Message:



48 of 128 9/29/2014 10:17 AM


21.3.14

Where lobby detectors are used for other than initiating elevator recall, the signal initiated by the detector shallalso initiate an alarm signal.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The change removes a potential conflict with 21.3.13.

Response Message:



49 of 128 9/29/2014 10:17 AM


21.3.13.3* Visual Warning Elevator Warning Signal .

For each elevator or group of elevators, an output(s) shall be provided to the elevator controller for the purposeof causing the elevator visual warning signal to operate in response to any of the following:

(1) Activation of the elevator machine room, elevator machinery space, elevator control space, or elevatorcontrol room initiating devices identified in 21.3.13.121.3.15.1 (2) or 21.3.13.221.3.15.2 (2)

(2) Activation of the elevator hoistway initiating devices identified in 21.3.13.121.3.15.1 (3) or21.3.13.221.3.15.2 (3)




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Revised wording more clearly describes the requirement. Editorial changes were made clarify that anyof the outputs will cause the warning signal.

ResponseMessage:



50 of 128 9/29/2014 10:17 AM


21.4.2*

If heat detectors are used to shut down elevator power prior to sprinkler operation, they shall be placed within 24in. (610 mm) of each sprinkler head and be installed in accordance with the requirements of Chapter 17.Alternatively, engineering methods, such as those specified in Annex B, shall be permitted to be used to selectand place heat detectors to ensure response prior to any sprinkler head operation under a variety of fire growthrate scenarios.

21.4.2.1

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




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: There is no term "Sprinkler Head" in the Sprinkler Code NFPA 13.

Response Message:



51 of 128 9/29/2014 10:17 AM



Where one or more elevators are specifically designated and marked as fire service access elevators, theconditions specified in 21.5.1and 21.5.2 shall apply. for the elevators, associated lobbies, and machine roomsshall be continuously monitored and displayed during any such use.

21.5.1*


Availability of main and emergency power to operate the elevator(s), elevator controller(s), and machineroom (if provided) ventilation

Temperature and presence of smoke in associated lobbies and machine room (if provided)

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

21.5.2

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

21.5.3

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




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Elevator system annunciators already provide some of these elements so repeating the information isduplicative and unnecessary. The revised wording would make it permissive to provide this information onthe fire alarm system. Changes were also made to provide consistency of terminology with therequirements in ASME A17.1.

ResponseMessage:


Public Comment No. 110-NFPA 72-2014 [Section No. 21.5 [Excluding any Sub-Sections]]




52 of 128 9/29/2014 10:17 AM


23.1.2

The requirements of Chapters 77, 10, 12, 17, 18, 21, 24, and 26 shall also apply, unless they are otherwisenoted in conflict with this chapter.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The requirement has been modified to provide more positive language.

Response Message:



53 of 128 9/29/2014 10:17 AM


23.6.1.4

The loss of more than one zone shall be permitted on a documented performance-based design approach inaccordance with 7.3.7.4 .




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The text is revised to remove a circular reference between 7.3.7.4 and 23.6.1.4.

Response Message:



54 of 128 9/29/2014 10:17 AM



Class N pathways shall be required to use shared pathway Level 3 as specified in 12.5.4 except as permittedby 23.6.3.1 through 23.6.3.7 .

23.6.3.1

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.2.3 and whenapproved by an AHJ in consideration of the analysis, maintenance, and deployment plans.

23.6.3.1.1

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

23.6.3.2 Deployment Plan.

23.6.3.2.1

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

23.6.3.2.1.1

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

23.6.3.2.1.2

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

23.6.3.2.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.3 Change Control Plan.

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

23.6.3.4 Management Organization.

23.6.3.4.1

An organization shall be established and maintained to manage the life safety network and shall perform thefollowing tasks:

(1) Contain members appropriately certified by each manufacturer of the equipment and devices deployed onshared 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.4.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, anddocumented and appropriate steps are taken during outages to provide alternate protection of life and property.

23.6.3.5 Analysis.

23.6.3.5.1


(1) Calculation of minimum required bandwidth such that all life safety systems can be guaranteed to operatesimultaneously 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


55 of 128 9/29/2014 10:17 AM

23.6.3.5.2


(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 required tosupport the minimum operational capacity requirements

23.6.3.6 Maintenance Plan.

23.6.3.6.1

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

23.6.3.6.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)


(3)


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

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

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

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

23.6.3.7 Other Risks.




72_SR_42_A.23.6.3.6_c_edited.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

With respect to restricting Class N pathways to strictly Level 3 Shared Pathways, members of the TC felt thatit would be counterproductive to provide zero possibility for qualified customers to share other high prioritysystems on this network. It may create a perception of obsolescence out of the gate to provide no pathforward into the future where more and more customers may be qualified to manage integrated life safetynetworks. There are other systems that are involved in life safety and security that can (where appropriate)

* Service outage impairment process with notices of impairment and contingency plans for affectedsystems


56 of 128 9/29/2014 10:17 AM

utilize modern networks and can benefit from shared pathways including nurse call systems, access controlsystems, camera systems, and of course Mass Notification Systems. Less important may be the benefit of theaggregation of port costs, but rather real benefits may be realized in purposeful inter-operation and/orcommon management for those life safety networks.


ResponseMessage:




57 of 128 9/29/2014 10:17 AM

A.23.6.3.6.2(3) The planned impairment process is used to control change in the system and inform stakeholders. Any activities that can affect the performance of the network or impact conclusions of a risk analysis should be presented to the organization referred to in 23.6.4.3 for approval. The organization should have a name (e.g., Life Safety Network Management Group). All stakeholders who could be affected by network outages should have representation in the organization.

A committee made up of members of the organization should meet on a regular basis and report to the organization. All planned impairments should have 7 days’ notice. An emergency impairment (one with less than 7 days’ notice) should meet very stringent standards for urgency. Outages and repair operations are dealt with on a case by case basis with the fire marshal’s office, and the Department of Public Safety is included based on the operational impact.

All proposed changes and outages are to be presented to the organization for authorization, scheduling, and coordination. Once a change has been authorized and scheduled, an impairment notification is issued notifying all affected users. If specific mitigation actions, such as fire watch, are required, they are to be included in the impairment notification.

Impairment notifications are issued through the fire marshal’s office, the Department of Public Safety, the Power Outages Group, or other groups depending on the systems affected.

A “login banner” is a programmable option for network switches and routers. This banner is the first thing that comes up on the screen when you log into the equipment. Where practical, network equipment used in life safety systems should have a login banner to notify service personnel that the network is a part of an active life safety system and any impairment should be coordinated with the named organization.





23.6.2.1


23.6.2.2

Class N pathways shall be required to use Shared Pathway Level 3 as specified in Section 12.5.4 .A single faulton a Class N pathway connected to the addressable devices shall not cause the loss of more than oneaddressable device.

23.6.2.3





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The revision added a title the section to improve readability. Also moving the content of 23.6.2.2 to a newproposed section 23.6.3 so that a complex exception to the Shared Pathway Level 3 proposal can bepresented. See SR 42 for section 23.6.3.

ResponseMessage:



58 of 128 9/29/2014 10:17 AM

Second Revision No. 28-NFPA 72-2014 [ New Section after 23.8.2.6.2 ]

23.8.2.6.3

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




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Section 23.8.2.6 deals with fire alarm control units and the sharing of signaling line circuits with otherpremise operating systems. Since this is closely related to shared pathways, should the SLCimplementation be class C it was the intention to draw the reader to the related material in the proposedsection 23.6.3.

ResponseMessage:



59 of 128 9/29/2014 10:17 AM


23.16.2* Power Supplies.

Primary 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:



(3) A low battery signal shall be transmitted before the device is no longer capable of providing 7 days of troublesignal operation followed by the signaling of a single non-trouble response. The low battery signal shall bedistinctive from alarm, supervisory, tamper, and trouble signals; , shall visibly identify the affected low-powerradio transmitter/transceiver; , and, when silenced, shall automatically re-sound at least once every 4 hours.

(4) Catastrophic (open or short) battery failure shall cause a trouble signal identifying the affected low-powerradio transmitter/transceiver at the system control unit. When silenced, the trouble signal shall automaticallyre-sound at least once every 4 hours.








Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Add the attached annex material for A.23.16.2. The annex material would clarify that the intent of thisrequirement is not to prohibit the use of battery operated technology in combination devices but rather tolimit the regional impact from the failure of a battery.

ResponseMessage:


Public Comment No. 224-NFPA 72-2014 [New Section after A.23.16]


60 of 128 9/29/2014 10:17 AM

A.23.16.2 This requirement is intended to limit the impact from the failure of a battery operated

receiver/transmitter in a given space. This requirement is not intended to prevent a single device that

contains multiple function elements, such as a combination carbon monoxide and smoke detector, a

detector with an independently controllable sounder, a notification appliance with visible and audible

elements, and so forth. This requirement is intended to limit the number of functional elements to one

of each independent type. For example, two manual fire alarm boxes could not rely on a single battery.


23.16.3.4

The maximum allowable response delay from activation of an initiating device to receipt and display by thesystem control unit shall occur within 10 seconds. Response time shall be in accordance with 10.12.1 .




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:



61 of 128 9/29/2014 10:17 AM


23.16.4.2





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The affected device should be identified so that the affected portion of the system is known and so thatthe cause of the problem can be more quickly identified and addressed. This would be consistent with the23.16.4.5 requirement to individually identify the removal of a device.

ResponseMessage:



62 of 128 9/29/2014 10:17 AM

Second Revision No. 34-NFPA 72-2014 [ Sections 23.16.4.6, 23.16.4.7 ]

23.16.4.6


23.16.4.7





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The second sentence in 23.16.4.6 is redundant to the statement in 23.16.4.7. Additionally, the Manualof Style does not permit two requirements in the same numbered item.

ResponseMessage:

Public Comment No. 211-NFPA 72-2014 [Sections 23.16.4.6, 23.16.4.7]


63 of 128 9/29/2014 10:17 AM





(2) All monitoring for integrity requirements of Chapter Chapters 10, Chapter 12, Chapter 23, or 23.16.4 shallapply.

(3) The maximum allowable response delay from activation of an initiating device to activation of required alarmfunctions shall be 10 seconds. Response time shall be in accordance with 10.12.1 .

(4) Each transceiver/system control unit shall automatically repeat activated response signals associated withlife safety events at intervals not exceeding 60 seconds or until confirmation that the output device hasreceived the alarm signal.





Street Address:

City:

State:

Zip:


Committee Statement


Response Message:



64 of 128 9/29/2014 10:17 AM


24.1.3

The requirements of Chapters 7, 10, 12, 17, 18, 21, 23, 26, and 27 shall also apply unless they are otherwisenoted in conflict with this chapter.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The statement was changed into positive language.

Response Message:



65 of 128 9/29/2014 10:17 AM


24.3.6.2* Emergency Message Content.

Emergency messages shall have a content that is:

Appropriate for the intended message recipients

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

Based on the emergency response plan, emergency messages shall have content that provides information andinstructions to people in the building, area, site, or installation.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The language has been revised to coincide with acceptable practices in accordance with the researchprovided to the committee. An annex reference to annex H (see SR-100) has been added while deletingthe current annex material. The paragraph has been renumbered to include all requirements for messagingunder 24.3.7.

ResponseMessage:



66 of 128 9/29/2014 10:17 AM

A.24.3.1 See Annex H.


24.3.1 Intelligible Voice Messages.


24.3.1.1*


24.3.1.2*

Where no listed loudspeaker exists to achieve the intelligibilty requirements of the Code for a notification zone,nonlisted loudspeakers shall be permitted to be installed to achieve the intelligibilty for that notification zone.







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

There may be situations where in order to achieve the intelligibility requirements, listed appliances arenot available but non-listed appliances are available to meet the performance requirements of the code.

ResponseMessage:



67 of 128 9/29/2014 10:17 AM

A.24.3.2.1 In certain situations, it is important to provide a distributed sound level with minimal sound intensity variations to achieve an intelligible voice message. This differs from past fire alarm design practice that used fewer notification appliances but with each having greater sound pressure output levels. Nonemergency system design practice is to use more speakers and less sound intensity from each speaker. Besides improving intelligibility of the message, this approach minimizes annoyance to building occupants from the system and lessens the likelihood of tampering with the system by occupants because of speakers being too loud. In other applications, such as outdoor signaling where reverberation is not a problem, intelligibility can be achieved by using fewer appliances or clusters of appliances covering larger areas. Intelligibility is a complex function of the source audio, the acoustic response of the architectural features and materials of the immediate vicinity, and the dynamics created by the room’s occupants. Refer to Annex D for more information on speech intelligibility and how it is predicted. Spacing speakers closely can be an intelligibility-enhancing technique but can occasionally lead to opposite results when improperly designed. There are several techniques using directionality features that do not use closely spaced speakers but rather use the room/space acoustic response in their favor.

A.24.3.2.2 In certain acoustically challenging areas, listed fire alarm speakers might not be capable of

producing an intelligible message. Non–fire alarm listed speakers are permitted to be installed in these

limited areas. A failure of a non‐listed speaker should not disrupt the operation of listed fire alarm

speakers and operation of the fire alarm or mass notification control equipment. Typically, a dedicated

speaker circuit and other audio components such as amplifiers could be necessary to meet this

functionality.


24.3.2* Microphone Use.


24.3.3.1





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Editorial change to comply with the NFPA Manual of Style.

Response Message:



68 of 128 9/29/2014 10:17 AM


24.3.5.4

The utilization of shared pathway levels, as specified in Section 12.5 , for Class N pathways used in emergencycommunication systems Where emergency communications systems utilize Class N pathways that are alsoshared pathway Level 1 or Level 2 as a means to support ancillary functions, devices, or interconnected systemsvia common pathways, shall be determined by a risk analysis , the shared pathways shall meet the requirementsof 26.6.3 . and approved by the AHJ.

24.3.5.4.1

In addition to the requirements of 23.6.3 , a risk analysis shall be performed and approved by the AHJ.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Editorial modification was made to the original comment for clarity.

Since section 23.6.3 creates requirements for analyzing and documenting a plan to utilize shared pathwaylevel 1 or 2 for life safety networks, this section (which deals with the same issues for MNS) was updatedto include the reference to that 23.6.3.

ResponseMessage:




69 of 128 9/29/2014 10:17 AM


24.3.7* System Classification.

Emergency communications systems (ECS) shall consist of two classifications of systems, be designated asone-way and or two-way.

24.3.7.1

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

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

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

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

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

24.3.7.2

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

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

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

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

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

(5) Stairway communications systems (see Section 24.12 )




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The revised wording provides more clarity. The references were corrected and a new reference tostairway communications was added to complete the list of two-way systems.

ResponseMessage:




70 of 128 9/29/2014 10:17 AM


24.3.10* Control Unit Listing for Mass Notification Systems.

Control units installed as part of a mass notification system shall be in compliance with this Code and at least oneof the following applicable standards: such as ANSI/UL 864, Standard for Control Units and Accessories forFire Alarm Systems; ANSI/UL 2017, Standard for General-Purpose Signaling Devices and Systems ; orANSI/UL 2572, Mass Notification Systems .

(1) ANSI/UL 864, Standard for Control Units and Accessories for Fire Alarm Systems

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

(3) ANSI/UL 2572, Mass Notification Systems .







Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Mass Notification systems have matured in technology as well as listings. UL 2572 has been published forseveral years now. It is important to recognize that products must be listed to be used for MNS. As a result,at least one of the applicable standards is necessary to be met in order to provide a level of systemfunctionality and reliability.


ResponseMessage:



71 of 128 9/29/2014 10:17 AM

A24.3.11 A fire alarm control unit that is listed in accordance with ANSI/UL 864 or ANSI/UL

2017 can be used for MNS. A control unit only listed in accordance with ANSI/UL 2572 or

ANSI/UL 2017 cannot be used as a fire alarm control unit.


24.3.13.4.1

For systems employing relocation or partial evacuation, a Level 2 or Level 3 pathway survivability shall berequired.

Exception No. 1: Level 1 shall be permitted where notification or evacuation zones are separated by less than2-hour fire-rated construction.

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




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:


72 of 128 9/29/2014 10:17 AM


24.4.1.2

If acceptable to the authority having jurisdiction, the system shall permit the application of an automaticevacuation signal to one or more evacuation signaling zones and, at the same time, shall permit manual voicepaging to the other evacuation signaling zones selectively or in any combination.




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:


73 of 128 9/29/2014 10:17 AM


24.4.5.6

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




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:


74 of 128 9/29/2014 10:17 AM




24.4.8.1


24.4.8.2

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

24.4.8.3


24.4.8.3.1


24.4.8.3.2

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

24.4.8.4


24.4.8.4.1


24.4.8.4.2

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

24.4.8.5


24.4.8.5.1*


24.4.8.5.2


24.4.8.5.3*

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

24.4.8.5.4

Where the separation of in-building fire emergency voice/alarm control equipment locations results in the portionsof the system controlled by one location being dependent upon the control equipment in other locations, thecircuits between the dependent controls shall be protected against attack by fire by the protection provided by thepathway survivability level required in 24.3.14.4.1 24.3.13.4.1 or by performance alternatives approved by theauthority having jurisdiction.

24.4.8.5.5



75 of 128 9/29/2014 10:17 AM

24.4.8.5.6

Where the separation of the in-building fire emergency voice/alarm control equipment occurs as in 24.4.8.5.4, andwhere the circuits are run through junction boxes, terminal cabinets or control equipment, such as system controlunits, power supplies and amplifiers, and where cable integrity is not maintained, these components shall, inaddition to the pathway survivability required by 24.3.14.4.1 24.3.13.4.1 , be protected by using one of thefollowing methods:

(1) A 2-hour fire- – rated enclosure

(2) A 2-hour fire- – rated room


24.4.8.5.7





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The language has been modified to provide clarity and consistency.

Response Message:



76 of 128 9/29/2014 10:17 AM


24.4.9 Evacuation Signal Zoning.

24.4.9.1*

Undivided fire or smoke areas shall not be divided into multiple evacuation notification signaling zones.

24.4.9.2

If multiple notification appliance circuits are provided within a single evacuation signaling zone, all of thenotification appliances within the zone shall be arranged to activate or deactivate simultaneously, eitherautomatically or by actuation of a common manual control.

24.4.9.3

Where there are different notification appliance circuits within an evacuation a signaling zone that performseparate functions, such as presignal and general alarm signals, and pre-discharge predischarge and dischargesignals, they shall not be required to activate or deactivate simultaneously.




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:


77 of 128 9/29/2014 10:17 AM



Mass notification systems shall require documentation in accordance with Sections 7.3 , 7.4 , and 7.5 inaddition to the minimum documentation requirements of Sections 7.2 and 24.15 .




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: This is duplicate material. See Section 24.15.

Response Message:



78 of 128 9/29/2014 10:17 AM


24.5.14.1

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




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This exception is too general and negates the exception with more detail established in 24.5.15.6. Since24.5.15.6 is part of 24.5.15, the exception is established and does not need to be repeated.

ResponseMessage:



79 of 128 9/29/2014 10:17 AM

Second Revision No. 97-NFPA 72-2014 [ Sections 24.13.4, 24.13.5 ]

24.13.4 Power Supplies.

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

24.13.4.1

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

24.13.4.2


24.13.5





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Change to comply with the NFPA Manual of Style.

Response Message:



80 of 128 9/29/2014 10:17 AM


26.1.2

The requirements of Chapters 77, 10, 12, 14, and 23 shall also apply unless they are otherwise noted inconflict with this chapter.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The text has been revised to provide more positive code language.

Response Message:



81 of 128 9/29/2014 10:17 AM



Where alarm signal verification is required by other governing laws, codes, or standards, or by other parts of thiscode, by the authority having jurisdiction, or by the responsible fire department in accordance with 26.2.2 , thesupervising station shall immediately notify the communications center that a fire alarm signal has beenreceived and verification is in process.

26.2.3.1

Where alarm signal verification is required by the responsible fire department in accordance with 26.2.2 , thesupervising station shall immediately notify the communications center that a fire alarm signal has beenreceived and verification is in process.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The process of preverification which was added to the 2013 edition of the code adds a confusing step to theverification process. As verification must be required by the responsible fire department to be employed, thedepartment understands there may be a delay in their receiving notification of an alarm condition at aspecified protected premises for up to an additional 90 seconds due to the verification process.


ResponseMessage:





82 of 128 9/29/2014 10:17 AM


27.1.4

The requirements of Chapters 10 and 14 shall also apply unless they are otherwise noted in conflict with thischapter.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The text is revised to provide more positive language.

Response Message:



83 of 128 9/29/2014 10:17 AM


10.5.6 Public Emergency Alarm Reporting System Personnel Qualification. (SIG-PRS)

10.5.6.1 System Designer.

10.5.6.1.1

Public emergency alarm reporting system plans and specifications shall be developed in accordance with thisCode by persons who are qualified in the proper design, application, installation, and testing of public emergencyalarm reporting systems.

10.5.6.1.2

The system design documents shall include the name and contact information of the system designer.

10.5.6.2 System Installer.

Installation personnel shall be qualified in the installation, inspection, and testing of public emergency alarmreporting systems.


Service personnel shall be qualified in the service, inspection, maintenance, and testing of public emergencyalarm reporting systems.


10.5.6.4.1


10.5.6.4.2



(2)


(4)

10.5.6.4.3

Evidence of qualifications and/or certification shall be provided when requested by the authority havingjurisdiction. A license or qualification listing shall be current in accordance with the requirements of the issuingauthority or organization.



SR-2_legislative_changes_for_moved_text.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The committee has relocated 27.3.7 to new 10.5.6 in order to provide a consistent location for allpersonnel qualification requirements. The committee has added a "(SIG-PRS)" tag to this section to retain




84 of 128 9/29/2014 10:17 AM

ownership. As a part of this change, all related annex material is to be moved into this new 10.5.6.


ResponseMessage:



85 of 128 9/29/2014 10:17 AM

SR-2 legislative changes 10.5.6 Public Emergency Alarm Reporting System Personnel Qualification. (SIG-PRS) 27.3.7.110.5.6.1 System Designer. 27.3.7.1.110.5.6.1.1 Public emergency alarm reporting system plans and specifications shall be developed in accordance with this Code by persons who are qualified in the proper design, application, installation, and testing of public emergency alarm reporting systems. 27.3.7.1.210.5.6.1.2 The system design documents shall include the name and contact information of the system designer. 27.3.7.210.5.6.2 System Installer. Installation personnel shall be qualified in the installation, inspection, and testing of public emergency alarm reporting systems. 27.3.7.310.5.6.3 Service Personnel. Service personnel shall be qualified in the service, inspection, maintenance, and testing of public emergency alarm reporting systems. 27.3.7.410.5.6.4 Qualification. 27.3.7.4.110.5.6.4.1 Personnel shall demonstrate qualification by being trained and certified in public emergency alarm reporting system design, installation, or service (as appropriate). 27.3.7.4.210.5.6.4.2 Personnel who are trained and certified for the specific type of public emergency alarm reporting system and comply with one the following shall be considered qualified:

1. Personnel who are licensed or certified by a state or local authority, if applicable 2. * Personnel who are certified by a nationally recognized certification organization

acceptable to the authority having jurisdiction 3. Personnel who are employed and qualified by an organization listed by a nationally

recognized testing laboratory for the design, installation, or servicing of systems within the scope of this chapter

4. * Personnel who are employed and certified by an equipment manufacturer for the specific type of system

27.3.7.4.310.5.6.4.3 Evidence of qualifications and/or certification shall be provided when requested by the authority having jurisdiction. A license or qualification listing shall be current in accordance with the requirements of the issuing authority or organization.

Second Revision No. 4-NFPA 72-2014 [ Section No. 27.6.3.2.1.1 ]

27.6.3.2.1.1

The requirements of Chapter 10 , in addition to those of Chapters 14 and 17 , shall apply to auxiliary alarmsystems unless they conflict with the requirements of 27.6.3.2 .




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The requirements of this paragraph appear to be addressing requirements for a protected premises firealarm system. Requirements for these system fall outside the scope of Chapter 27. Deleting the paragraphremoves ambiguous and potentially conflicting requirements. This change helps to resolve a concern raisedby PC 94.

ResponseMessage:


86 of 128 9/29/2014 10:17 AM



Household fire alarm systems utilizing low-power wireless transmission of signals within the protected dwellingunit shall comply with the requirements of Section 23.16, except as modified by 29.7.8.1.1 .

29.7.8.1.1

The requirements of 23.16.4.2 shall not apply where periodic monitoring for integrity complies with all of thefollowing:

(1) Each low-power transmitter/transceiver shall transmit check-in signals at intervals not exceeding 80minutes.

(2) Any transmission interruption between a low-power radio transmitter/transceiver and the receiver/firealarm control unit exceeding 4 hours shall cause a latching trouble signal at the household fire alarmcontrol unit/operator interface.

(3) Low-power transmitters/transceivers shall be limited to serving a single initiating device; however, a singleinitiating device shall be permitted to send multiple types of alarm signals.

(4) Redundant retransmission devices (repeaters) shall be provided such that disconnecting or failure of anysingle retransmission device (repeater) does not interrupt communications between any low-powertransmitter/transceiver and the receiver/fire alarm control unit.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The intent of this text is to leave the existing monitoring for integrity (supervision) requirements of householdfire alarm system utilizing low-power radio (wireless) transmitters unchanged from that in the 2010 editionand in effect prior to June 2013. No data has been presented that demonstrates an issue with the previouspolling period in residential applications. The TC adds an 80 minute check-in requirement to ensure at least3 polling attempts in 4 hours.

ResponseMessage:




87 of 128 9/29/2014 10:17 AM



29.7.8.3.1

Wireless household fire alarm system networks shall meet the requirements of 29.7.8.1 .

29.7.8.3.2


29.7.8.3.3

Shared communications equipment used in supplementary (noncritical) signaling path(s) is permitted to belisted for communications or information technology use.

29.7.8.3.4


29.7.8.3.5

Where the mesh network is shared by other premise operating systems, its operation shall be in accordancewith the following:

Network bandwidth shall be monitored to confirm that all communications between devices critical to theoperation of the fire alarm system take place within 20 seconds; failure shall be indicated within 200seconds.

All programming accepted by devices in the network shall ensure a fire alarm system alarm responsetime of 20 seconds.

All specified configurations of the network shall ensure a fire alarm system alarm response time of 20seconds.

Failure of any equipment that is critical to the operation of the fire alarm system shall be indicated at theoperator interface of the fire alarm control unit by the annunciation of a trouble signal.

The occurrence of any single fault that disables a transceiver shall not prevent other transceivers in thesystem from operating (formerly 29.7.8.2.5 ).




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

While the TC had hoped to establish minimum guidelines for emerging wireless technologies, it becameevident during the comment and revision process that changes in these technologies and products areaccelerating. Drafting language that will ensures a level of safety and still allow for future innovation willrequire knowledge of communication techniques.




88 of 128 9/29/2014 10:17 AM

ResponseMessage:

Public Comment No. 201-NFPA 72-2014 [Sections 29.7.8.3.2, 29.7.8.3.3, 29.7.8.3.4, 29.7.8.3.5]


89 of 128 9/29/2014 10:17 AM


29.8.1.4*

The supplier or installing contractor shall provide the system owner or other responsible parties with the following:

(1) An instruction booklet illustrating typical installation layouts

(2) Instruction charts describing the operation, method, and frequency of testing and maintenance offire-warning equipment

(3) Printed information for establishing an emergency evacuation plan

(4) Printed information to inform system owners where they can obtain repair or replacement service, and whereand how parts requiring regular replacement, such as batteries or bulbs, can be obtained within 2 weeks

(5) Information noting both of the following:

(a) Unless otherwise recommended by the manufacturer's published instructions, smoke alarms shall bereplaced when they fail to respond to tests.

(b) Smoke alarms installed in one- and two-family dwellings shall not remain in service longer than 10years from the date of manufacture.



A.29.8.1.4_Form.docx Figure for A.29.8.1.4





Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC adds new annex text. The TC relocated text from CI-56 to this section.

Response Message:


90 of 128 9/29/2014 10:17 AM

INSTALLATION FORM SINGLE- AND MULTIPLE-STATION SMOKE ALARMS AND

HOUSEHOLD FIRE ALARM SYSTEMS

This form is to be completed at the time of installation,/final inspection of any household fire alarm system and single- or

multiple-station smoke alarms. It is be permitted to modify this form as required to provide a more complete and/or clear

record.

Insert N/A in all unused lines.

Attach additional sheets, data, or calculations as necessary to complete form.

Form Completion Date: ___________________ Supplemental Pages Attached ____________________

1. PROPERTY INFORMATION

Property Owner: ___________________________________________________________________________________________________

Address: ________________________________________________________________________________________________________________________

Phone: ________________________________ E-Mail: ___________________________Other: _______________________________________

2. INSTALLATION, CONTRACTOR, AND MONITORING INFORMATION

Installation Contractor: ______________________________________________________________________________________________

Address:____________________________________________________________________________________________________________


2.1 Type of Off-Premises Notification

Monitoring Organization: __________________________________________________________________________________________

Address: ___________________________________________________________________________________________________________


Account Number_________________________________________ Means of Transmission ___________________________________

3. DESCRIPTION OF SYSTEM OR SERVICE

NFPA 72 Edition: _______________

3.1 Type of System

Single-Station Multiple-Station

Household Fire Alarm System

3.2 Number of Devices

Single-Station Smoke Alarms: ______________________ Multiple-Station Smoke Alarms: _________________________

Single-Station Heat Alarms: ______________________ Multiple-Station Heat Alarms: _________________________

System Smoke Detectors: __________________________ System Heat Detectors: ___________________________________

Waterflow Switches: _______________________________________________________________________________________________

Notification Appliances: _____________________________________ Type: ______________________________________________

Interfaced/Other Equipment: _____________________________________________________________________________________

3.3 Location (L) and Date (D) of Devices

Device type, location and manufacture date of devices (date shown on back of devices)

_____________________________ ___________________________ __________________________ _________________________

_____________________________ ___________________________ __________________________ _________________________

_____________________________ ___________________________ __________________________ _________________________

Electrical Panel (L): ___________________________________ Breaker Number: ___________________________

Household Fire Alarm Panel (L): _____________________________________ Battery Back-up (D): _______________________

Plug in Transformer (L): ___________________________________________________________________________________________

Relay for Interconnection (L): _____________________________________________________________________________________

4. PREPARED BY

Signed: _______________________ Printed Name: ___________________________________ Date: _______________________

Title: ______________________________________ Organization: ______________________________________________________

Figure A.29.8.1.4 Installation Form Single- And Multiple-Station Smoke Alarms And Household Fire Alarm Systems

A.29.8.1.4 Where a form is required by the AHJ

to document the installation of a household fire

alarm system or single- or multiple-station

alarms, Figure A.29.8.1.4 can be used to

document the record of completion.

FIGURE A.29.8.1.4 Installation Form Single-

and Multiple-Station Smoke Alarms and

Household Fire Alarm Systems.







Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The second sentence was poorly written and included conflicting statements.

Response Message:



91 of 128 9/29/2014 10:17 AM


A.10.4.4

The fire alarm control units that are to be protected are those that provide notification of a fire to the occupantsand responders. The term fire alarm control unit does not include equipment such as annunciators andaddressable devices. Requiring smoke detection at the transmitting equipment is intended to increase theprobability that an alarm signal will be transmitted to a supervising station prior to that transmitting equipmentbeing disabled due to the fire condition.


Where the area or room containing the control unit is provided with total smoke detection coverage, additionalsmoke detection is not required to protect the control unit. Where total smoke detection coverage is not provided,the Code intends that only one smoke detector is required at the control unit even when the area of the roomwould require more than one detector if installed according to the spacing rules in Chapter 17. The intent ofselective coverage is to address the specific location of the equipment.





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The requirement to provide notification of a fire condition prior to a control unit(s) or equipment used fortransmitting notification signals being attacked by fire is equally, or in some instances more critical in an ECSor MNS system. This is a "fundamental" requirement that should apply to all signaling system notificationequipment located in areas that are not continuously occupied as specified in 10.4.4. This correlates withthe revisions in 10.4.4.

ResponseMessage:



92 of 128 9/29/2014 10:17 AM


A.10.12.2





Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This annex material should be associated with 10.12.2 as indicated in the committee statement forFR-363. The text was editorially revised.

ResponseMessage:



93 of 128 9/29/2014 10:17 AM


A.10.13.2

Where it is desired to deactivate the notification appliances for fire service operations and also provide notificationthat the fire inside the building and signal evacuated occupants that an alarm is still active present , it isrecommended that a separate non-silenceable notification zone be provided that is non-silenceable on theexterior of the building. The audible and visible notification appliances located at the building entrances withaudible and visible notification appliances outside each entrance to the protected building or space. Thesenotification appliances could serve as a warning signal to prevent occupant re-entry during fire serviceoperations .




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Revised wording for improved clarity.

Response Message:



94 of 128 9/29/2014 10:17 AM



95 of 128 9/29/2014 10:17 AM

A.12.3.6(1)


96 of 128 9/29/2014 10:17 AM

Class N consists of pathways between control equipment and devices. The pathways comprise metallicconductor communications cable, such as a 100 ohm balanced twisted-pair (e.g., Category 5E), includingsingle-pair or multi-pair cable, or other communications media such as optical fiber cable or wirelesstransmission, or a combination of two or more of these. Pathways consist of uninterrupted communications mediabetween control equipment and an endpoint device or of a network of multiple interconnected communicationsmedia pathway segments connecting multiple devices. Media pathway segments are created by the use oftransmission equipment such as Ethernet switches, wireless repeaters, or media converters that interrupt anotherwise continuous pathway. Requirements for Class N pathway transmission equipment are not covered inChapter 12 but by other chapters in NFPA 72.

A network of pathway segments is also described as primary pathway segments, redundant pathway segments,or nondesignated pathway segments. Primary and redundant pathways, from control equipment to each device,are independently and continuously verified for their ability to support end-to-end communications to and fromeach endpoint device. Each device will be provided a primary pathway consisting of one or more pathwaysegments. For primary pathway segments that service more than one device, additional redundant pathwaysegments provide alternate verified communication pathways to the devices. Should any primary pathwaysegment fail, communication is supported by the redundant pathway segments. Should either a primary orredundant pathway segment fail, trouble will be indicated by virtue of the continuous verification of all primary andredundant pathway segments. The redundant pathway segments are generally independent and do not normallyshare media with the primary pathways. However, there are exceptions, such as different frequencies for wirelessor ring topologies. [See A.12.3.6(5).]

There is an opportunity to enhance the robustness of a Class N network by providing physically distinct pathwaysegments (i.e., an alternate conduit, or cable tray route, or wireless transmission frequency range, or acombination of distinct media). It is also permissible to provide other nondesignated pathway segments.Additional pathway segments in excess of the minimum requirements of Class N increase the overall robustnessof the network and are often desirable. However, since these additional pathway segments exceed the minimumequipment standards, there is no intention to create an additional monitoring burden, so verification of thesepathways is optional.

For Class N, where a conductor-based media is used, it is not the intention to monitor faults on individualconductors but rather to monitor the operational capability and performance of the pathway as a whole. UnlikeClass C, where multiple pathways are not required, for Class N some pathway segments that carrycommunications for multiple devices (such as Ethernet uplinks or backbones) will have redundant pathwaysegments present. The intention is that any one pathway segment can fail without a loss in operational capabilityto more than one device. For example, connections to control equipment (fire alarm control units, ACUs, orECCUs), where any interruption in communications could potentially affect all devices, would have redundantpathway segments. Additionally, backbone and uplink pathway segments that support communications for morethan one device and are positioned between transmission equipment would also have a redundant pathwaysegment. But the requirement for redundant pathway segments does not apply to those pathway segments usedto service a single device [see Figure A.12.3.6(1)(a) ] .


Input components such as alarm initiating switches, sensors

Output components such as Ethernet speakers (i.e., IEEE 802.3af PoE speakers), strobes, textualsignage, audio amplifiers


The audio amplifier example is included to explain a type of addressable device that can receive a digital audioinput from the Class N pathway but provide a notification appliance circuit (NAC) output to support Class A, B, orX speaker connections. Other similar devices are also possible to provide alternate class pathway connections forstrobes (NACs) or initiating devices (IDCs). From the perspective of the Class N pathway, this is considered anendpoint device. However, since these types of endpoints can support multiple notification appliance devices orinitiating devices, they are subject to the redundant pathway segment requirement and are provided with dualpathway connections.

Control equipment connected to a Class N network for communications with devices would generally utilizeredundant pathway segments. Control equipment connected to other control equipment on a Class N networkwould utilize redundant pathway segments if the control equipment was dependent on any of the pathwaysegments so that a failure of a primary pathway segment in between control equipment could impair the operationof the control equipment [see Figure A.12.3.6(1)(b) ] .

Another utilization of endpoints is permitted for devices providing two connection ports and supporting dualpathway segment connections. The description of endpoint devices is not intended to exclude devices thatsupport dual pathway connections. Since these pathways are servicing a single device, only a single primarypathway connection is required. The second pathway connection exceeds minimum equipment standards and is


97 of 128 9/29/2014 10:17 AM

therefore not required to be verified as a redundant pathway segment; it can be considered connected to anondesignated pathway segment [see Figure A.12.3.6(1)(c) ] .





98 of 128 9/29/2014 10:17 AM

The Class N pathway designation is added to specifically address the use of modern network infrastructure whenused 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 a traditionalSLC multi-drop loop. A device with an Ethernet address is, in most cases, a physical endpoint connected to adedicated cable. Traditional SLC devices are all wired on the same communication line (in parallel), similar to anold party-line telephone system. By comparison, Ethernet’s network switches direct each data packet to itsintended 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 and Class X, andequipment redundancy described in 12.3.7 , is not inherently required of Class N. In other words, failure of asingle switch is permitted take down a class N segment and is only required to report the loss of communication.Where redundant path segments are intended to have survivability similar to Class A or Class X, the physicalseparation requirements and overall equipment redundancy must be specified in addition to the Class Ndesignation.

As a visual model, Class N could be likened to a redundant pathway backbone, allowed to have Class C branchpaths to single endpoint devices. Therefore, every effort is made in this section to clearly distinguish the singleendpoint device from the transport equipment required to have redundant paths.

Class N requires redundant, monitored pathway segments to and from control equipment (fire alarm control units,ACUs, or ECCUs) where any interruption in communications could potentially affect multiple endpoint devices.Typically, interconnected communications equipment such as Ethernet switches, wireless repeaters, or mediaconverters are used in combination to create pathways. Chapter 12 describes the required behavior of Class Npathways. All equipment must meet the requirements of other chapters in NFPA 72 (such as, but not limited to,requirements pertaining to secondary power supplies, equipment listings, and environment conditions).

Redundant pathways, isolated from ground, are actually common practice in robust Ethernet designs. Managednetwork switches commonly have specific uplink ports that are intended for load sharing and allow two parallelconnections. For compliance with Class N, a trouble must be reported if either of these connections fails. [SeeFigure 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 twisted pair(e.g., Category 5E), including single-pair or multi-pair cable, or other communications media, such as optical fibercable or wireless transmission, or a combination of two or more such transport mediums.

Where a conductor-based media is used for Class N, the intention is not to monitor faults on individualconductors but rather to monitor the operational capability and performance of the pathway as a whole. Similar toClass C, end-to-end verification is used in Class N.

Primary and required redundant pathways are independently and continuously verified for their ability to support


99 of 128 9/29/2014 10:17 AM

end-to-end communications to and from each endpoint device and its associated control equipment. Pathwaysegments that service more than one device must have at least one verified redundant pathway segment. Shouldany primary pathway segment fail, communication is supported by the redundant pathway segment(s.) Failure ofeither 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). Inaddition to the required primary segments and redundant segments, a Class N pathway is permitted to havenonrequired segments. [See Figure A.12.3.6(1)(c) .] Additional nonrequired pathway segments are allowed to beconnected and not independently monitored for integrity as long as two paths are monitored to meet theredundancy requirement of Class N.

Figure A.12.3.6(1)(a) Class N Pathway Block Diagram – Example 1.

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 components usedin notification. With respect to Class N, the term device includes appliances and other intelligent, addressablecomponents that perform a programmable input or output function. Examples of Class N devices include thefollowing:

(1) Input components such as alarm initiating modules switches and sensors

(2) Output components such as output modules, Ethernet speakers (i.e., IEEE 802.3af PoE speakers),intelligent strobes, textual signage, and intelligent audio amplifiers

Transmission equipment components (e.g., media converters, Ethernet switches, patch panels, cross-connects)are connected to the Class N pathway merely to transport instructions between other equipment. As such, theyare not considered devices with respect to Class N pathways.


100 of 128 9/29/2014 10:17 AM

The audio amplifier listed above is an example of an addressable device that can receive a digital audio inputfrom the Class N pathway and then provide a notification appliance circuit (NAC) output with Class A, B, or Xpathways. Other endpoint devices can similarly provide alternate class pathways for strobes (NACs) or initiatingdevices (IDCs). From the perspective of the Class N pathway, communications terminates at this endpoint device.However, since these types of endpoints can support multiple notification appliance devices or initiating devices,path segments are subject to the redundant pathway requirement unless protected in an enclosure or racewayless than 20 ft (6 m) in length. [See Figure 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 pathway segments ifa failure of a primary pathway segment in between control equipment could impair the operation of the controlequipment. [See Figure A.12.3.6(1)(d) .]

Figure A.12.3.6(1)(d) Class N Pathway Block Diagram with Multiple Control Units.

Class N is also permitted to include dual port devices that provide both transmission and input/output functions.Endpoint devices can have multiple connection ports and support dual pathway segment connections; thus theterm endpoint device is not intended to prohibit more than one connection to a device. Even with dualconnections, where other devices depend on the path, primary and redundant paths are required. But, where anendpoint device has two connection ports, and when a secondary nonrequired connection is added, there is norequirement to separately supervise the nonrequired redundant pathway segment. [See Figure A.12.3.6(1)(e) .]

Figure A.12.3.6(1)(e)







101 of 128 9/29/2014 10:17 AM


Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Editorial and organizational changes were made for improved readability and clarity. Drawings werechanged to make the style more similar to Annex F.


ResponseMessage:






102 of 128 9/29/2014 10:17 AM



Class N networks can be specified for ancillary functions but are not required for supplemental reporting

described in 23.12.4. (See Figure A.12.3.6(5).

Ethernet network devices are addressable but with an important distinction from device addresses on a

traditional SLC multi‐drop loop. A device with an Ethernet address is, in most cases, a physical endpoint

connected to a dedicated cable. Traditional SLC devices are all wired on the same communication line (in

parallel), similar to an old party‐line telephone system. By comparison, Ethernet’s network switches


Class N uses redundant paths as a means to compensate for Ethernet wiring that does not report a

single connection to ground, a basic requirement of Class B. Thus, the physical separation of Class A and

Class X, and equipment redundancy described in 12.3.7, is not inherently required of Class N. In other

words, failure of a single switch is permitted take down a class N segment and is only required to report

the loss of communication. Where redundant path segments are intended to have survivability similar

to Class A or Class X, the physical separation requirements and overall equipment redundancy must be

specified 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 C

branch paths to single endpoint devices. Therefore, every effort is made in this section to clearly

distinguish the 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

control units, ACUs, or ECCUs) where any interruption in communications could potentially affect

multiple endpoint devices. Typically, interconnected communications equipment such as Ethernet

switches, wireless repeaters, or media converters are used in combination to create pathways. Chapter

12 describes the required behavior of Class N pathways. All equipment must meet the requirements of

other chapters in NFPA 72 (such as, but not limited to, requirements pertaining to secondary power

supplies, equipment listings, and environment conditions).



allow two parallel connections. For compliance with Class N, a trouble must be reported if either of

these connections fails. [See Figure A.12.3.6(1)(a).]

Class N pathways can use metallic conductor communications cable, such as a 100 ohm balanced

twisted pair (e.g., Category 5E), including single‐pair or multi‐pair cable, or other communications

media, such as optical fiber cable or wireless transmission, or a combination of two or more such

transport mediums.


conductors but rather to monitor the operational capability and performance of the pathway as a




equipment. Pathway segments that service more than one device must have at least one verified



trouble.


A.12.3.6(4)

The operational conditions of the pathway include factors such as latency, throughput, response time, arrival rate,utilization, bandwidth, and loss. It is intended that the life safety equipment connected to a Class N networkactively monitor some or all of the pathway’s operational conditions, so that an improperly installed or configuredpathway, or a subsequently degraded pathway or network of pathway segments is detected by the life safetyequipment and reported as a trouble. This monitoring is intended to be continuous so that a degradation ofpathway performance over time is detected and reported. Trouble would be reported when operational conditionsof the pathway(s) have deteriorated to the point where the equipment is no longer capable of meeting itsminimum performance requirements, even if some level of communication to endpoint devices is still maintained.Examples of performance requirements include the activation of an alarm within 10 seconds, the reporting of atrouble signal within 200 seconds, synchronization of strobes, and delivery of audio messages with requiredintelligibility.

It is possible to have a pathway where end-to-end communications are operational under system idle conditions,but in the event of an alarm, the increased load on a degraded pathway could cause a partial or complete failureto deliver required life safety signals. This is the situation that is intended to be actively detected and reported.

Operational conditions of the pathway include factors such as latency, throughput, response time, arrival rate,utilization, bandwidth, and loss. Life safety equipment connected to a Class N network actively monitors some orall of the pathway’s operational conditions so that an improperly installed or configured pathway or asubsequently degraded pathway or segment is detected by the life safety equipment and reported as a trouble.The trouble condition is reported when operational conditions of the pathway(s) have deteriorated to the pointwhere the equipment is no longer capable of meeting its minimum performance requirements, even if some levelof communication to devices is still maintained. Performance requirements include the activation of an alarmwithin 10 seconds, the reporting of a trouble signal within 200 seconds, and delivery of audio messages withrequired intelligibility. End-to-end communications might be operational under system idle conditions, but in theevent of an alarm, the increased load on a degraded pathway could cause a partial or complete failure to deliverrequired life safety signals. Such predictable failure must be actively detected and reported.







Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Editorial and organizational changes for improved readability and clarity.

Response Message:



103 of 128 9/29/2014 10:17 AM

A.12.3.6(4) Operational conditions of the pathway include factors such as latency, throughput, response

time, arrival rate, utilization, bandwidth, and loss. Life safety equipment connected to a Class N network

actively monitors some or all of the pathway’s operational conditions so that an improperly installed or

configured pathway or a subsequently degraded pathway or segment is detected by the life safety

equipment and reported as a trouble. The trouble condition is reported when operational conditions of

the pathway(s) have deteriorated to the point where the equipment is no longer capable of meeting its

minimum performance requirements, even if some level of communication to devices is still maintained.

Performance requirements include the activation of an alarm within 10 seconds, the reporting of a

trouble signal within 200 seconds, and delivery of audio messages with required intelligibility.

End‐to‐end communications might be operational under system idle conditions, but in the event of an

alarm, the increased load on a degraded pathway could cause a partial or complete failure to deliver

required life safety signals. Such predictable failure must be actively detected and reported.


A.12.3.6(5)

Devices with dual path connections are permitted to be connected to create a daisy chain of devices on a ring. Inthis circumstance they cannot be considered endpoint devices because each pathway segment supports multipledevices; therefore, verified redundant pathway segments would be necessary. This can be accomplished with aring topology, as long as each segment of the ring is verified as functional, and the failure of any one segmentdoes not result in the loss of functionality of more than one device. In this circumstance the requirements forClass N are satisfied by allowing the primary and redundant pathway segments to share the same media byproviding two possible directions of communications on a ring topology [see Figure A.12.3.6(5) ] . Thisconfiguration is fully compliant with 12.3.6 (5).

The daisy chain configuration is also a permissible connection method for multiple control units that requireverified primary and redundant pathway segments.

Figure A.12.3.6(5) Class N Pathway Block Diagram with Dais Chained Devices with Dual PathwayConnection.

Devices with dual path connections are permitted to be connected in a daisy-chain of devices on a ring. Again,where Class N pathway segments support multiple devices, verified redundant pathway segment(s) are required.This can be accomplished with a ring topology, as long as each segment of the ring is verified as functional, andthe failure of any one segment does not result in the loss of functionality of more than one device. In thisarrangement, primary and redundant pathway segments share the same media, and provide two possibledirections of communications in a ring topology [see Figure A.12.3.6(5) ] . This daisy-chain configuration is alsopermitted between multiple control units that require verified primary and redundant pathway segments.

Figure A.12.3.6(5) Class N Pathway Block Diagram with Daisy-Chained Devices with Dual PathwayConnection.



104 of 128 9/29/2014 10:17 AM






Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Editorial and organizational changes are made for improved readability and clarity. The drawing waschanged to make the style more similar to Annex F.

ResponseMessage:



105 of 128 9/29/2014 10:17 AM

A.12.3.6(5)

Devices with dual path connections are permitted to be connected in a daisy‐chain of devices on a ring.

Again, where Class N pathway segments support multiple devices, verified redundant pathway

segment(s) are required. This can be accomplished with a ring topology, as long as each segment of the

ring is verified as functional, and the failure of any one segment does not result in the loss of

functionality of more than one device. In this arrangement, primary and redundant pathway segments

share the same media, and provide two possible directions of communications in a ring topology [see

Figure A.12.3.6(5) ]. This daisy‐chain configuration is also permitted between multiple control units that

require verified primary and redundant pathway segments.

Figure A.12.3.6(5) Class N Pathway Block Diagram with Daisy‐Chained Devices with Dual Pathway

Connection.

Endpoint Devices

Switch

Communications continues from either direction in a ring topology.

Figure A.12.3.6(5)

To FACU

Switch

with dual pathwayconnectors

Formatted: Indent: Left: -0.01", Hanging: 0.01", SpaceAfter: 0.2 pt, Line spacing: Multiple 1.11 li



106 of 128 9/29/2014 10:17 AM

A.14.4.3.2


107 of 128 9/29/2014 10:17 AM

Table 14.4.3.2, Item 24. The extent of testing of a fire alarm or signaling system, including devices that were nottested, should be documented per in accordance with the Test Plan in 14.2.10. NFPA 72 does not require testingof an emergency control function, such as elevator recall, but does require testing of the emergency controlfunction interface device, such as the relay powered by the fire alarm or signaling system. Where the emergencycontrol function is not being tested concurrent with the fire alarm or signaling system testing, measurement of theemergency control function interface device output should be verified using the proper test devices. This mightrequire reading or observing the condition of a relay, a voltage measurement, or the use of another type of testinstrument. Once testing is complete, verification that any disabled or disconnected interface devices have beenrestored to normal is essential, and this verification should be documented in the testing results.

Testing of the emergency control functions themselves is outside of the scope of NFPA 72. A complete end-to-endtest that demonstrates the performance of emergency control functions activated by the fire alarm or signalingsystem might be required by some other governing laws, codes, or standards, or the authority having jurisdiction.In that situation, other applicable installation standards and design documents, not NFPA 72, would addresstesting and performance of the emergency control functions. NFPA 3, Recommended Practice forCommissioning and Integrated Testing of Fire Protection and Life Safety Systems , provides guidance forintegrated (end-to-end) testing of combined systems. The following excerpt from NFPA 3 includes guidance onwhen integrated testing should be performed.









7.2.3 In addition to periodic integrated testing, integrated system testing should be done when any of thefollowing events occurs:




NFPA 3 also includes guidance on test methods for integrated testing. It is important to note that the appropriateNFPA standard would provide the acceptance criteria for the overall emergency control function operationrequirements, including performance and test methods, whileNFPA 72 covers the required performance andtesting of the emergency function interface device.

For instance, if an end-to-end test for a building with an engineered smoke control system is required by someother governing laws, codes, standards, or the authority having jurisdiction, the test protocol would have uniquecriteria for the smoke control system design, and a special inspector would be responsible for the overalloperation and performance of the smoke control system in accordance with the appropriate standard (NFPA 92,Standard for Smoke Control Systems , and NFPA 101, Life Safety Code ) during the testing, includingmeasuring pressure differentials and ensuring proper fan and damper operation. Refer to the following extractfrom NFPA 101 on smoke control:

9.3.2 System Designer. The engineer of record shall clearly identify the intent of the system, the design methodused, the appropriateness of the method used, and the required means of inspecting, testing, and maintaining thesystem. [101:9.3.2]

9.3.3 Acceptance Testing. Acceptance testing shall be performed by a special inspector in accordance withSection 9.9 9.13 . [101:9.3.3]

Even though the fire alarm or signaling system initiating device might activate the smoke control system, theactual testing of the dampers and fan operation would be as required by the smoke control design and not part ofthe fire alarm or signaling system.

Other emergency control operation requirements might be as follows: For fan shutdown and smoke damperoperation, the fan and damper operations would be in accordance with NFPA 90A, Standard for the Installationof Air-Conditioning and Ventilating Systems , and NFPA 105, Standard for Smoke Door Assemblies and Other


108 of 128 9/29/2014 10:17 AM

Opening Protectives , respectively, and those equipment operations would be verified by those responsible forHVAC systems in combination with the fire alarm system personnel. Guidance for elevator inspection and testingcan be found in ASME A.17.2, Guide for Inspection of Elevators, Escalators and Moving Walks. For elevatorsystems, the recall function, elevator power shutdown, and hat illumination would be done with the elevatormechanics present during the test. This operational test is often accomplished during routine periodic fire alarmtesting. For fire door holder and fire shutter release, it would be expected that the emergency control functionoperation of the doors/shutters would be verified in accordance with NFPA 80, Standard for Fire Doors andOther Opening Protectives , and NFPA 101 during the test. In some cases, the door manufacturer representativemight need to be present to reset the equipment.



If during the course of the periodic test of audible appliances, it is suspected that alarm sound levels could belower than the required minimum, the building system owner or the system owner's designated buildingrepresentative should be notified in writing . Such notification will allow the building owner or designated buildingrepresentative to determine whether sound pressure level readings should be taken for the area(s) in question.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

Language was changed to use "system owner or the system owner's designated representative", whichcorrelates the terminology used in other locations within NFPA 72. The TC also added "in writing" to clarifythe medium of notification.

ResponseMessage:



109 of 128 9/29/2014 10:17 AM


A.17.12.2

The waterflow device or the combination of the waterflow devices and fire alarm system should be fieldadjusted configurable so that an alarm is initiated no more than 90 seconds after a sustained flow of at least 10gpm (40 L/min).






Care should be used when choosing waterflow alarm-initiating devices for hydraulically calculated looped systemsand those systems using small orifice sprinklers. Such systems might incorporate a single point flow ofsignificantly less than 10 gpm (40 L/min). In such cases, additional waterflow alarm-initiating devices or the use ofpressure drop-type waterflow alarm-initiating devices might be necessary.



An excess pressure system with an alarm valve consists of an excess pressure pump with pressure switches tocontrol the operation of the pump. The inlet of the pump is connected to the supply side of the alarm valve, andthe outlet is connected to the sprinkler system. The pump control pressure switch is of the differential type,maintaining the sprinkler system pressure above the main pressure by a constant amount. Another switchmonitors low sprinkler system pressure to initiate a supervisory signal in the event of a failure of the pump or othermalfunction. An additional pressure switch can be used to stop pump operation in the event of a deficiency inwater supply. Another pressure switch is connected to the alarm outlet of the alarm valve to initiate a waterflowalarm signal when waterflow exists. This type of system also inherently prevents false alarms due to water surges.The sprinkler retard chamber should be eliminated to enhance the detection capability of the system for shortduration flows.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The waterflow signal activation may be mechanical built into the waterflow device, electronic built intoan intelligent module, or firmware built into the IDC of a fire control panel.

ResponseMessage:



110 of 128 9/29/2014 10:17 AM


A.18.1


Notification appliances in conventional commercial and industrial applications should be installed in accordancewith the specific requirements of Section Sections 18.4 and Section 18.5.

The Code recognizes that it is not possible to identify specific criteria sufficient to ensure effective occupantnotification in every conceivable application. If the specific criteria of Section Sections 18.4 and Section 18.5 aredetermined to be inadequate or inappropriate to provide the performance recommended, approved alternativeapproaches or methods are permitted to be used.

Designers and AHJs are advised to consider alternative means in occupancies that have individuals withcognitive disabilities. In addition, persons responsible for evacuation planning should consider specific training forindividuals with cognitive disabilities to familiarize them with audible and visual signals and what responses arenecessary based on their capabilities and any alternative means used.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The new text alerts Authorities Having Jurisdiction, building owners, property managers, testing and servicepersonnel that additional training and notification be given to individuals with special needs and staff so thatan understanding of what to expect during an alarm activation and testing of Protected Premise System’sand the actions that they should take during these conditions. This is important in occupancies wherepersons with cognitive disabilities are expected to be present, such as schools or other institutions.

ResponseMessage:



111 of 128 9/29/2014 10:17 AM


A.21.1






Figure A.21.1 Integrated Systems. (Courtesy of R.P. Schifiliti Associates, Inc)




112 of 128 9/29/2014 10:17 AM

G72-352_3_.jpg




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: NFPA 3 was added to provide a more complete set of references.

Response Message:



113 of 128 9/29/2014 10:17 AM

Second Revision No. 16-NFPA 72-2014 [ Sections A.21.3.9, A.21.3.10 ]

A.21.3.8


A.21.3.9

The objective of Phase I Emergency Recall Operation is to have the elevator automatically return to the recalllevel before fire can affect the safe operation of the elevator. This includes both the safe mechanical operation ofthe elevator, as well as the delivery of passengers to a safe lobby location. Where ANSI/ASME A17.1/CSA B44,Safety Code for Elevators and Escalators, specifies the use of smoke detectors, these devices are expected toprovide the earliest response to situations that would require Phase I Emergency Recall Operations. The use ofother automatic fire detection is only intended where smoke detection would not be appropriate due to theenvironment. Where ambient conditions prohibit the installation of smoke detectors, the selection and location ofother automatic fire detection should be evaluated to ensure the best response is achieved. When heat detectorsare used, consideration should be given to both detector temperature and time lag characteristics. Theconsideration of a low temperature rating alone might not provide the earliest response. It should be noted thatsmoke detectors installed in hoistways can be a source of nuisance activation. Therefore, hoistways need smokedetectors specifically intended for those types of spaces (environments).




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The added reference to A.21.3.10 provides addition guidance for heat detector installations.

Response Message:

Public Comment No. 87-NFPA 72-2014 [Sections A.21.3.9, A.21.3.10]


114 of 128 9/29/2014 10:17 AM


A.23.12.4

Off-site logging of fire alarm data can be useful to preserve information in the face of fire or building failure tofacilitate accurate reconstruction of the event. It can also be beneficial to send data off-premises to incidentcommand personnel to enhance situational awareness and response decisions and to maintain safe and efficientoperations. Off-site logging of fire alarm data can be useful to preserve information in the face of fire or buildingfailure to facilitate accurate reconstruction of the event. It can also be beneficial to send data off-premises toincident command personnel to enhance situational awareness and response decisions and to maintain safe andefficient operations. Figure A.23.12.4 shows an example of a network to accomplish these goals.

Figure A.23.12.4 Supplemental Reporting Network.







Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: Added a diagram to better illustrate the explanation of supplemental reporting.

Response Message:



115 of 128 9/29/2014 10:17 AM

A.23.12.4 Off-site logging of fire alarm data can be useful to preserve information in the face of fire or building failure to facilitate accurate reconstruction of the event. It can also be beneficial to send data off-premises to incident command personnel to enhance situational awareness and response decisions and to maintain safe and efficient operations. Figure A.23.12.4 shows an example of a network to accomplish these goals. Figure A.23.12.4 Supplemental Reporting Network.

Computer 2

Ethernet Network

Computer 1


Brand Z


Brand Y


Brand X

Handheld

To ListedMonitoring

To ListedMonitoring

To ListedMonitoring

Figure A.23.12.4


A.24.3.6.1

The fundamental structure of the prerecorded or live messages is critical for providing information andinstructions that are intelligible. Prerecorded messages created in a controlled environment are considerablymore intelligible than live messages and should be developed and provided to handle as many of the probableemergencies that a particular facility will encounter.

The voice instructions (live or prerecorded) should be preceded by a tone to get attention and prepare the targetaudience for voice instructions. This tone should be differentiated for specific emergencies, based on thestandards for that facility. The actual voice message (live or pre-recorded) should be delivered in awell-enunciated, clear, calm, and deliberate manner, using respectful language. Focus the message on the actionto be taken and minimize wasting words on the cause. For the voice itself, best results will vary, depending on thespecific location — for example, in outdoor applications, it has been shown that a male voice will provide betterintelligibility, as the naturally lower frequency of the male voice travels better. Inversely, in an interior application,where the background ambient noise is typically in the same lower frequencies, a female voice tends to penetratebetter, as it is more distinct from the ambient. Messages should be constructed using 2-second to 3-secondbursts of information and brief periods of quiet between the bursts of information. This methodology facilitatesbetter processing of information by the brain and minimizes the negative effects of reverberation and echo.

Generally, the emergency message should consist of an alert tone of 1 second to 3 seconds, followed by a voicemessage that is repeated at least three times. The alert tone can be used in between repeats of the voicemessage.


Think about what information must be delivered in the live announcement, keep it brief, and write down themessage

Read the message out loud for a practice round in a clear and projecting voice

When you are ready to announce, key the microphone and read the message at least three times

When possible, use an alert tone, such as a Code 3, 1000 Hz signal preceding the message, and thenannounce over the live microphone

Repeat the message a few times more as the emergency warrants

See Annex G .




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:



116 of 128 9/29/2014 10:17 AM


A.24.3.6.3


What: Guidance on what people should do

When: An idea of when they need to act

Where: Description of the location of the risk of hazard (who should be taking action and who should notbe)

Why: Information on the hazard and danger/consequences

Who: The name of the source of the warning (who is giving it)

Warning style is also crucial and should be specific, consistent, certain, clear, and accurate with attention paid tothe frequency — the more it is repeated, the better.

See Annex G .




Street Address:

City:

State:

Zip:


Committee Statement


Response Message:



117 of 128 9/29/2014 10:17 AM


A.26.2.2.1(1)

It is recognized that individual fire departments will have preference on whether verification is used in certainoccupancies based on many variables such as department-specific staffing or response protocols, occupancystaffing, and occupancy risk. This section allows the fire authority to specifically select those occupancies whereverification is allowed. It should be understood that the use of the alarm verification process could delay theresponse to the alarm by up to an additional 90 seconds.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

The text added to the annex material provides a cautionary statement to the use of the alarmverification process.

Response Message:


118 of 128 9/29/2014 10:17 AM


A.26.2.2.1(4)

The 90-second allowance for a supervising station to call the protected premise to verify the validity of thereceived alarm signal is independent from in addition to the time allowed for the supervising station to initiate theretransmission to the communications center.




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The annex material was revised to add clarity.

Response Message:



119 of 128 9/29/2014 10:17 AM

Second Revision No. 100-NFPA 72-2014 [ New Section after G.3 ]

Annex G Guidelines for Emergency Communication Strategies for Buildings and Campuses

This annex is not part of the requirements of this NFPA document but is included for informational purposesonly.

G.1

The material in this annex is based on the National Institute of Standards and Technology (NIST) and FireProtection Research Foundation research Guidance Document: Emergency Communication Strategies forBuildings , by Erica Kuligowski, Ph.D. and H. Omori, 2014, as adapted by the NFPA ECS TC.

The purpose of this annex is to provide guidance to system designers, building managers, and/or buildingemergency personnel responsible for emergency communication on how to create and disseminate messagesusing basic communication modes (audible and/or visual technology). The guidance provided here is takendirectly from a report published by the National Institute of Standards and Technology, which was based on areview of 162 literature sources from a variety of social science and engineering disciplines (Kuligowski et al.2012) and the prioritization of the specific findings extracted from each literature source.

This document first presents guidance on how to create and disseminate emergency information in the face of

rapid-onset disasters 1 — providing guidance on the dissemination of alert signals, the creation of the warningmessage, the formatting of messages for both visual and audible means, and the dissemination of the warningmessage. This document then provides examples of emergency messages (i.e., message templates) for fivedifferent types of emergency scenarios. These message templates can be altered to fit the needs of youroccupants, as well as the type of emergency that has occurred and type of technology used to disseminate thealerts/messages.

G.2 Guidance on Emergency Communication Strategies.

This section provides guidance for managers, emergency personnel, alarm system manufacturers,codes/standards committees, or others responsible for emergency communication on the ways in which alertsand warning messages should be created, formatted, and disseminated. The guidance is divided into two mainparts: guidance on alerts and guidance on warning messages. Although these two parts often get confused, it isimportant to distinguish between the purpose of an alert and a warning message.

An alert is meant to grab peoples’ attention, notifying them that an emergency is taking place and that thereis important information, which will be provided to them. The purpose of a warning message is to give that

important information to occupants.


G.2.1 Alerts.

It is imperative to disseminate an alert to let occupants know that a warning message will follow. Regardless ofwhether the warning message is provided audibly, visually, or via tactile means, an alert is necessary to gainpeople’s attention and should be provided separately from the warning message. An effective alert shouldinclude the following characteristics:



(3) Flashing, rather than static lights, preferably one standard color for all buildings, can be used to gainattention to visual warning messages.

(4) There are additional methods to alert occupants to an emergency: disruption of routine activities, tactilemethods, social networks, and face-to-face.

(5) An alert signal should be accompanied by a clear, consistent, concise, and candid warning message.

(6) If selected, an alert should be tested for its success in getting occupants’ attention in the event of anemergency and used as part of building- or campus-wide training.

G.2.2 Warnings.

Warning messages should provide information to the occupants on the state of the emergency and what theyare supposed to do in response to this emergency. The warning message should come after an alert signal isgiven and can be provided via visual or audible means. However, before such guidance on message format forvisual and audible messages can be provided, it is vital to provide guidance on the content of the warningmessage itself.


120 of 128 9/29/2014 10:17 AM

G.2.2.1 The Message.


121 of 128 9/29/2014 10:17 AM

Regardless of the method used to disseminate the warning message, there are certain characteristics that arerequired of an effective warning message. These are included here:


(a) A warning message should contain five important topics to ensure that occupants have sufficientinformation to respond.


ii. What should people do? (i.e., what actions occupants should take in response to theemergency and, if necessary, how to take these actions)

iii. When do people need to act? (In rapid-onset events, the “when” is likely to be “immediately.”)


v. Why do people need to act? (including a description of the hazard and itsdangers/consequences)

(b) The source of the message should be someone who is perceived as credible by the occupants

(c) Building managers, campus managers, and emergency personnel should understand the affectedpopulation and, from this understanding, develop a database of possible trusted sources (as well asbackup sources).



i. Source


iii. Hazard (why)


v. Time.


i. Source

ii. Hazard

iii. Location

iv. Guidance

v. Time


(d) For limited message length, message writers could draft the message in a bulleted form; each ofthe five topics in the warning should be separated as its own bullet point

(e) Distinct audiences should be addressed separately in the message (or in multiple messages)


(a) Messages should be written using short, simple words, omitting unnecessary words or phrases.


(c) Messages should be written using short, simple, and clear sentences, avoiding double negativesand exceptions to exceptions; main ideas should be placed before exceptions and conditions.

(d) Emergency messages should be written at a sixth grade reading level or lower. An emergencymessage can be evaluated for its reading level using computer software and/or a simplecalculation.


(f) Emergency messages should be provided in the language of the predominant affected populace. Ifthere is a possibility of isolated groups that do not speak the predominant language, multilingualmessages should be provided. It is expected that small groups of transients unfamiliar with thepredominant language will be picked up in the traffic flow in the event of an emergency and are notlikely to be in an isolated situation.


122 of 128 9/29/2014 10:17 AM


(a) Building managers, campus managers, and emergency personnel should anticipate the need towrite more than one emergency message throughout a disaster, including feedback messages orupdates.

(b) In update messages, occupants should be told why the information has changed, to ensure that thenew message is viewed as credible.

(c) Provide feedback messages after a “non-event” to inform occupants that the alert signal andwarning system operated and worked as planned and the reasons why the event did not occur.

(d) Building managers, campus managers, and emergency personnel should test emergencymessages with the affected population.


(a) Messages that are displayed visually will have different capabilities and limitations than thosedisseminated audibly. Message creators should consider different factors and make different typesof decisions based upon the dissemination method. The first consideration is the type of visualtechnology that will be used to disseminate the messages, which can include textual visualdisplays, SMS text messages, computer pop-ups, email, Internet websites, news (TV broadcast), orstreaming broadcast over the web. Depending upon the technology chosen to display visualwarning messages, guidance is provided here on message displays to enable occupants to see ornotice the displayed warning, understand the warning, perceive warning credibility and risk, andrespond appropriately.


(a) Place the emergency sign in a location where people will notice it and be able to read it from theiroriginal (pre-emergency) location.


(c) Text is easier to read when written with a mixture of upper and lower case letters rather than theuse of all capitals.

(d) The recommended relationship for older adults with lower visual acuity is D = 100 * h, providing amore conservative result, and ensuring that a larger population will be able to read the emergencymessage.

(e) A stroke-to-width ratio of the letters is suggested as 1:5 (generally), with a ratio of 1:7 suggested forlighter letters on a darker background.

(f) Building managers, campus managers, or emergency personnel should consult the ADA Standardsfor Accessible Design (U.S. Department of Justice 2010) for additional requirements on signage.

(g) Contrast between the text and the background should be at least 30 percent, althoughrecommended values could be as high as 60 percent.

(h) The use of pictorials (in lieu of or in addition to text) can also bring attention to the sign.

(i) Message providers should ensure that emergency information is not blocked by other signs orinformation.


(a) Printed text should accompany symbols or pictorials used in visual warnings; a minimum number ofwords should be used to accompany graphics.

(b) Diagrams that display a series of sequential steps are more successful for comprehension of aprocess than one single graphic.

(c) A color-contrasted word or statement should be used for text that should be read first and/or beperceived as more urgent than the rest, unless color is used for other reasons (e.g. bilingual text).

(d) A warning message can increase in perceived credibility and risk if occupants are shown thatothers are also responding.

(e) Simultaneously displayed text (discrete messages) is preferred rather than a sequentially displayedmessage.

(f) Simultaneously displayed text can also be used for bilingual messages, especially if care is taken todifferentiate the text of one language from the text of the other language.



123 of 128 9/29/2014 10:17 AM


(a) There are specific warning technologies that only (or primarily) affect the aural sense, includingpublic address systems (voice notification systems), automated voice dialing, satellite/AM/FM radiobroadcasts, satellite/off-air television broadcasts, and tone alert radios. Whereas visualtechnologies can limit message length, audible warnings are often limited only by the attentioncapabilities of the audience. In other words, an audible message can play for long periods of timewith these technology types, and the message creator and source must be careful to provide allimportant information in an appropriate length of time.

(b) In this section, guidance will be given for methods to increase the likelihood that an individual willperceive, or hear, the message. Following this, guidance will be provided that can increasecomprehension of the message for audible messages, as well as the ways in which to increasecredibility and risk assessment of the event when the warning is presented audibly.

(9) Perception.




(a) Letters are more difficult to identify in speech than numbers, which are more difficult than colors.

(b) Message speakers (or sources) should not be heavily accented and should speak with a rate ofapproximately 175 words per minute.

(c) Audible warnings can be delivered using a live voice, dynamic voice (generated by text-to-speechsoftware), or using pre-recorded voice.

(d) The live voice and dynamic voice methods provide the benefit of messages that can be updatedwith new information while also conveying an appropriate level of urgency, if necessary.

(e) Dynamic and pre-recoded voice methods provide the benefits of easily repeating the playedmessages for longer periods of time and not relying on the voice announcer training or stress levelwhile delivering the message.

(f) For the voice itself, best results will vary, depending on the specific location — for example, inoutdoor applications, it has been shown that a male voice will provide better intelligibility, as thenaturally lower frequency of the male voice travels better. Inversely, in an interior application, wherethe background ambient noise is typically in the same lower frequencies, a female voice tends topenetrate better, as it is more distinct from the ambient.

(g) Urgency measures should be used selectively to emphasize the more dangerous, immediate,life-threatening situations (since overuse can lead to non-response in future disasters).


(a) Use multiple channels to disseminate the warning message, including visual, audible, and tactilemeans.

(b) A warning message should be repeated at least once, with some research advocating for messagerepetition of at least three times.

(c) Messages should be stated in full, and then repeated in full, rather than repeating statements withinthe same message.




(g) Messages should be disseminated using a combination of both push and pull technologies.

(h) Push communication 2 is most important to use for alert signals as well as initial warningmessages.

G.3 Emergency Message Templates.


124 of 128 9/29/2014 10:17 AM

Rapid-onset emergencies often come with little warning and can have a major impact on communities. In orderto provide clear, effective instructions for a threatened population, it is important to create message templatesahead of time for a variety of different emergencies.

This section provides examples of message templates for five types of emergency, using various forms ofemergency communication technology. All bracketed text can be altered and replaced with text that better suitsthe needs of the occupants, emergency scenario, emergency response strategies, and the technology beingused. Please see Kuligowski and Omori (2014) for more information on the process associated with thedevelopment of these templates. Each template follows the guidance presented in this document.

G.3.1 Scenario 1 — Fire in a building, partial evacuation strategy, building-wide public address announcements.

Scenario 1 is a fire located on the 10th floor of a 20-story building. Individuals are unable to use elevators in thisscenario, except for those who are unable to negotiate the stairs, in which case building staff or fire fighters willassist them using the freight elevator(s).

Protective actions: Occupants on floors 9, 10, and 11 are told to evacuate to the 8th floor (two floors below thefire floor). All other occupants are provided with a message to remain on their floor. Therefore, in this scenario,two different types of messages are required to be provided simultaneously to occupants, depending upon thefloor on which they are located: one message will be disseminated to floors 9, 10, and 11, while a differentmessage will be disseminated simultaneously to all other floors.

Technology used to disseminate the message: The building-wide public address system, which is capable ofproviding different messages to different floors (using a live voice or a dynamic voice).


(1) Building-wide announcement to Floors 9, 10, and 11: “Attention [floors 9, 10, and 11]. This is your[Building Safety Officer, Joe Smith]. A fire has been reported on the [10th floor] of the building. Everyoneon the [9th, 10th, and 11th floors] should move to the [8th floor] to be protected from heat and smoke,since heat and smoke can creep into nearby floors during a fire. Use the stairs immediately. Do not usethe elevators. Those who need help getting to the 8th floor, please wait inside the stairwell [or go to thefreight elevator lobby].”

(2) Building-wide announcement to all other floors: “Attention. This is your [Building Safety Officer, JoeSmith]. A fire has been reported on the [10th floor] of the building. Please wait on your floor. At this time,you are safer remaining on your floor than leaving the building, because this building is designed toconfine the fire [e.g., locally or to the 10th floor only]. Do not use the elevators for any reason. We will giveyou further instructions, if the situation changes.”

G.3.2 Scenario 2 — Fire in a building, full evacuation strategy, building-wide public address announcement, andcell phone text message.

Scenario 2 is a fire located on the second floor of a 20-story building in which smoke is traveling up thebuilding’s air-conditioning/venting system, causing the need for a full-building evacuation. Individuals are unableto use elevators in this scenario, except for those who are unable to negotiate the stairs, in which case buildingstaff or fire fighters will assist them using the freight elevator(s).

Protective actions: Occupants on all floors are requested to evacuate the building, known as a full-buildingevacuation.

Technologies used to disseminate the message: The building-wide public address system, which is capable ofproviding different messages to different floors (using a live voice or a dynamic voice). Also, a 90-character textmessage alert to cell phone users in the building.


(1) Building-wide public address system: “Attention. This is [Chief Smith from the Springfield FireDepartment]. A fire has been reported on the [second floor] of the building. Everyone must leave thebuilding now to avoid contact with the fire’s heat and smoke. Go NOW to your closest stair and leave thebuilding. People who cannot use the stairs should go to the freight elevator lobby for help.”

(2) Cell phone text message (90 characters): “Evacuate building now. It is on fire. Go to freight elevator if youneed help.”

Note: A description of the hazard (a more detailed “why” statement) is not included in this message due tocharacter limits. Also, the source is not listed. It is possible that the source will already be identified in the“From” or “FRM” line of the text message. If message contents are limited, there is always the option to send afollow-up text message that provides more information or that continues the previous message. Also rememberthat some phones (i.e. non-smart phones) could display longer text messages in reverse chronological order.


125 of 128 9/29/2014 10:17 AM

G.3.3 Scenario 3 — Tornado imminent on a college campus, campus-wide audible messaging system, andTwitter message.


Protective actions: The individuals on the college campus are instructed to “shelter in place.” Additionally, theNational Weather Service provides examples of protective actions (included below):

Example 1: “TAKE COVER NOW. FOR YOUR PROTECTION MOVE TO AN INTERIOR ROOM ON THELOWEST FLOOR OF A STURDY BUILDING.”

Example 2: “TAKE COVER NOW. MOVE TO AN INTERIOR ROOM ON THE LOWEST FLOOR OF A STURDYBUILDING. AVOID WINDOWS. IF IN A MOBILE HOME...A VEHICLE OR OUTDOORS...MOVE TO THECLOSEST SUBSTANTIAL SHELTER AND PROTECT YOURSELF FROM FLYING DEBRIS.”

Example 3: “THE SAFEST PLACE TO BE DURING A TORNADO IS IN A BASEMENT. GET UNDER AWORKBENCH OR OTHER PIECE OF STURDY FURNITURE. IF NO BASEMENT IS AVAILABLE...SEEKSHELTER ON THE LOWEST FLOOR OF THE BUILDING IN AN INTERIOR HALLWAY OR ROOM SUCH AS ACLOSET. USE BLANKETS OR PILLOWS TO COVER YOUR BODY AND ALWAYS STAY AWAY FROMWINDOWS.”

IF IN MOBILE HOMES OR VEHICLES...EVACUATE THEM AND GET INSIDE A SUBSTANTIAL SHELTER. IFNO SHELTER IS AVAILABLE...LIE FLAT IN THE NEAREST DITCH OR OTHER LOW SPOT AND COVERYOUR HEAD WITH YOUR HANDS.”


Technologies used to disseminate the message: A campus-wide siren system with audible messaging

capabilities. Also, a 140-character Twitter 3 message should be disseminated as well for this emergency.


(1) Campus-wide audible messaging system): Alert tone precedes message [siren]. “This is [Joan Smith,Chief of Campus Police]. A tornado has been sighted on the ground at [20th Street and MockingbirdLane]. The tornado is strong and is moving toward the college campus at high speeds (with winds over160 mph). High winds and large, flying debris can flatten a building in a storm of this magnitude. Takeshelter now. Get inside now, go to the lowest level, and get away from windows. Stay there until furtherinstructions.”

(2) Twitter message (140 characters): “Take shelter inside a building NOW. Go to the lowest level, get awayfrom windows. Strong tornado near campus.” [Include hashtag in 140 characters.]

Note: The source of the message is not included in this Twitter message since the source will be evident fromthe Twitter message layout.

G.3.4 Scenario 4 — Chemical spill in a building, building-wide public address announcements, andbuilding-wide email messages.

Scenario 4 is a chemical spill in a 40-story office building. The event was an accident and occurred on the 1stfloor of the building. There is the possibility of the chemical negatively affecting individuals on the lower floors ofthe building. Individuals are unable to use elevators in this scenario. For those who are unable to negotiate thestairs, only one freight elevator will be used with fire-fighter assistance.

Protective actions: Occupants are advised to perform different actions based upon the floor on which they arelocated. First, occupants on the first floor are advised to evacuate the building. At the same time, occupants onfloors 2 through 10 are advised to travel to locations higher in the building — preferably to floors 20 through 30.Concurrently, occupants on floors 11 and above are advised to remain in place. Therefore, in this scenario,three different types of messages are required to be provided simultaneously to occupants, depending upon thefloor on which they are located: one message will be disseminated to the first floor, one message will bedisseminated to floors 2 through 10, and a third message will be disseminated to all other floors.

Technologies used to disseminate the message: The building public address system, which is capable ofproviding different message to different floors (using a live voice or a dynamic voice). Additionally, an emailmessage (through the company’s email system) should be disseminated to employees on floors 2 through 10 torelocate to a higher floor. [ Note: Do not worry about an email to other employees, although in an actualemergency, that would be necessary. ]


126 of 128 9/29/2014 10:17 AM

G.3.4.1

(1) Building-wide public address system: [first floor occupants] “This is your [Building Manager, Joe Smith]. Adangerous chemical has spilled on the first floor. The chemical makes it difficult to see and can causetrouble breathing. Evacuate immediately.”

(2) Building-wide public address system: [floors 2 through 10] “This is your [Building Manager, Joe Smith]. Adangerous chemical has spilled on the first floor. The chemical makes it difficult to see and can causetrouble breathing. Immediately use the stairs to relocate to the [20th through 30th floors], and then wait forfurther instructions. If you can’t use the stairs on your own, go to the freight elevator and wait for help.Relocate now.”

(3) Building-wide public address system: [floors 11 and above] “This is your [Building Manager, Joe Smith]. Adangerous chemical has spilled on the first floor. The chemical makes it difficult to see and can causetrouble breathing. People on [floors 1 through 10] are being evacuated. Please stay on your floor. You aresafer remaining where you are than if you try to leave the building. The chemical will not reach people onfloors 11 and above. You would possibly be exposed to the chemical if you tried to leave the building. Donot use the elevators for any reason. We will give you further instructions if the situation changes.”


G.3.5 Scenario 5 — Violent event in an airport, airport-wide visual messaging screens, and cell phone textmessage.

The fifth scenario is a violent event. Specially, the emergency involves an active shooter that has been identifiedin a major U.S. airport.

Example protective action: Occupants should evacuate the airport through all accessible doors, including doorsfrom the gate waiting areas onto the tarmac area.

Technologies used to disseminate the message (along with example character limits that can be typical forthese types of technologies): A 90-character text message alert to individuals’ phones within the airport. Also,airport-wide visual messaging screens (limit message to 60 words or less) can be used to alert individuals interminals where the shooter is NOT located.


(1) Airport-wide visual messaging screens: “This is Los Angeles Police. Evacuate the terminal NOW. Followdirections from airport security. Shots have been fired near Gate 22.”

(2) Cell phone text message (90 characters): “Leave NOW. Follow airport security. Shots fired! Policereport: Shooter in Terminal A.”

Note: A description of the hazard (a more detailed “why” statement) is not included in this message due tocharacter limits. If message contents are limited, there is always the option to send a follow-up text messagethat provides more information or that continues the previous message. Also remember that some phones (i.e.,non-smart phones) could display longer text messages in reverse chronological order.

G.4 Future Direction.

The purpose of this report is to provide guidance to system designers, building managers, and buildingemergency personnel responsible for emergency communication on how to create and disseminate effectivemessages using basic communication modes (audible vs. visual technology), as well as examples ofemergency messages (message templates) for five different types of emergency scenarios. START (2013)contains additional message templates for similar types of rapid-onset events for both limited- and unlimited-character length dissemination technologies. Additionally, Kuligowski and Omori (2014) provide guidance onhow to test the effectiveness of these messages.

As with any document, there are gaps in the research that hinder the ability to provide guidance on certaintopics, including message length and repetition. This guidance document focuses specifically on textualmessage creation, creating room for additional guidance on the development and testing of visual symbols thatcould be used instead of, or in addition to, textual emergency messages. In the future, as research gaps areaddressed, additional editions of this document would be useful to enhance the findings and guidance providedhere.


127 of 128 9/29/2014 10:17 AM

G.5 References.

Kuligowski, E.D., S.M.V. Gwynne, K.M. Butler, B.L. Hoskins, and C.R. Sandler, 2012. Developing EmergencyCommunication Strategies for Buildings . Technical Note 1733, National Institute of Standards and Technology:Gaithersburg, MD.

Kuligowski, E.D. and Omori, H., 2014. General Guidance on Emergency Communication Strategies forBuildings, 2nd Edition . NIST Technical Note 1827, National Institute of Standards and Technology:Gaithersburg, MD.

U.S. Department of Justice, September 2010. 2010 ADA Standards for Accessible Design . Washington, DC:DOJ. http://www.ada.gov/2010ADAstandards_index.htm.

START (National Consortium for the Study of Terrorism and Responses to Terrorism), 2013. Task 2.9: Phase IIInterim Report on Results from Experiments, Think-out-Louds, and Focus Groups. University of Maryland,College Park: College Park, MD.

G.6 Footnotes.

1 Rapid-onset emergencies are those emergencies that occur with no or almost no (in the case of minutes)notice, rather than slow-onset events (i.e., emergencies in which the occurrence is known hours or even days inadvance). These different emergency types require different sets of emergency messages and disseminationtechniques to allow building occupants to receive information in a timely manner, resulting in efficient and saferpublic response.

2 Push technologies are those that do not require individuals to take extra effort to receive the alert or warningmessage (e.g., public address systems or text messages), whereas pull technologies require the individual toseek additional information to acquire the alert/message (e.g., Internet websites).

3 Certain commercial entities, equipment, or materials are identified in this document in order to describe anexperimental procedure or concept adequately. Such identification is not intended to imply recommendation orendorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities,materials, or equipment identified are necessarily the best available for the purpose.



72_SR_100_Annex_H_edited.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

This annex provides valuable guidance with regard to message content, delivery, and development that isnecessary for a properly designed emergency communications system. This builds on the material includedin FCR 32 which includes reference to NIST Technical Note 1779 which was subsequently issued asTechnical Note 1827.

This annex is based on the Fire Protection Research Foundation Final Report Guidance Document:Emergency Communication Strategies for Buildings which has been modified by the committee to complywith the NFPA manual of style for annex material.

ResponseMessage:


128 of 128 9/29/2014 10:17 AM

Annex H Guidelines for Emergency Communication Strategies for

Buildings and Campuses

H.1 The material in this annex is based on the National Institute of Standards and Technology (NIST) and

Fire Protection Research Foundation research Guidance Document: Emergency Communication

Strategies for Buildings, by Erica Kuligowski, Ph.D. and H. Omori, 2014, as adapted by the NFPA ECS TC.

The purpose of this annex is to provide guidance to system designers, building managers, and/or

building emergency personnel responsible for emergency communication on how to create and

disseminate messages using basic communication modes (audible and/or visual technology). The

guidance provided here is taken directly from a report published by the National Institute of

Standards and Technology, which was based on a review of 162 literature sources from a variety

of social science and engineering disciplines (Kuligowski et al. 2012) and the prioritization of

the specific findings extracted from each literature source.

This document first presents guidance on how to create and disseminate emergency information

in the face of rapid-onset disasters1 — providing guidance on the dissemination of alert signals,

the creation of the warning message, the formatting of messages for both visual and audible

means, and the dissemination of the warning message. This document then provides examples of

emergency messages (i.e., message templates) for five different types of emergency scenarios.

These message templates can be altered to fit the needs of your occupants, as well as the type of

emergency that has occurred and type of technology used to disseminate the alerts/messages.

H.2 Guidance on Emergency Communication Strategies.

This section provides guidance for managers, emergency personnel, alarm system manufacturers,

codes/standards committees, or others responsible for emergency communication on the ways in

which alerts and warning messages should be created, formatted, and disseminated. The

guidance is divided into two main parts: guidance on alerts and guidance on warning messages.

Although these two parts often get confused, it is important to distinguish between the purpose of

an alert and a warning message.

An alert is meant to grab peoples’ attention, notifying them that an emergency is taking

place and that there is important information, which will be provided to them.

The purpose of a warning message is to give that important information to occupants.


H.2.1 Alerts. It is imperative to disseminate an alert to let occupants know that a warning message will follow.

Regardless of whether the warning message is provided audibly, visually, or via tactile means, an

alert is necessary to gain people’s attention and should be provided separately from the warning

message. An effective alert should include the following characteristics:

1 Rapid-onset emergencies are those emergencies that occur with no or almost no (in the case of minutes) notice,

rather than slow-onset events (i.e., emergencies in which the occurrence is known hours or even days in advance).

These different emergency types require different sets of emergency messages and dissemination techniques to

allow building occupants to receive information in a timely manner, resulting in efficient and safer public response.



(3) Flashing, rather than static lights, preferably one standard color for all buildings, can

be used to gain attention to visual warning messages.

(4) There are additional methods to alert occupants to an emergency: disruption of

routine activities, tactile methods, social networks, and face-to-face.

(5) An alert signal should be accompanied by a clear, consistent, concise, and candid

warning message.

(6) If selected, an alert should be tested for its success in getting occupants’ attention in

the event of an emergency and used as part of building- or campus-wide training.

H.2.2 Warnings.

Warning messages should provide information to the occupants on the state of the emergency

and what they are supposed to do in response to this emergency. The warning message should

come after an alert signal is given and can be provided via visual or audible means. However,

before such guidance on message format for visual and audible messages can be provided, it is

vital to provide guidance on the content of the warning message itself.

H.2.2.1 The Message.

Regardless of the method used to disseminate the warning message, there are certain

characteristics that are required of an effective warning message. These are included here:


(a) A warning message should contain five important topics to ensure that occupants have

sufficient information to respond.


ii. What should people do? (i.e., what actions occupants should take in response to the

emergency and, if necessary, how to take these actions)

iii. When do people need to act? (In rapid-onset events, the “when” is likely to be

“immediately.”)


v. Why do people need to act? (including a description of the hazard and its

dangers/consequences)

(b) The source of the message should be someone who is perceived as credible by the

occupants

(c) Building managers, campus managers, and emergency personnel should understand

the affected population and, from this understanding, develop a database of possible

trusted sources (as well as backup sources).



i. Source


iii. Hazard (why)


v. Time.


i. Source

ii. Hazard

iii. Location

iv. Guidance

v. Time


(d) For limited message length, message writers could draft the message in a bulleted

form; each of the five topics in the warning should be separated as its own bullet point

(e) Distinct audiences should be addressed separately in the message (or in multiple

messages)


(a) Messages should be written using short, simple words, omitting unnecessary words or

phrases.


(c) Messages should be written using short, simple, and clear sentences, avoiding double

negatives and exceptions to exceptions; main ideas should be placed before exceptions

and conditions.

(d) Emergency messages should be written at a sixth grade reading level or lower. An

emergency message can be evaluated for its reading level using computer software and/or

a simple calculation.


(f) Emergency messages should be provided in the language of the predominant affected

populace. If there is a possibility of isolated groups that do not speak the predominant

language, multilingual messages should be provided. It is expected that small groups of

transients unfamiliar with the predominant language will be picked up in the traffic flow

in the event of an emergency and are not likely to be in an isolated situation.


(a) Building managers, campus managers, and emergency personnel should anticipate the

need to write more than one emergency message throughout a disaster, including

feedback messages or updates.

(b) In update messages, occupants should be told why the information has changed, to

ensure that the new message is viewed as credible.

(c) Provide feedback messages after a “non-event” to inform occupants that the alert

signal and warning system operated and worked as planned and the reasons why the

event did not occur.

(d) Building managers, campus managers, and emergency personnel should test

emergency messages with the affected population.


Messages that are displayed visually will have different capabilities and limitations than those

disseminated audibly. Message creators should consider different factors and make different

types of decisions based upon the dissemination method. The first consideration is the type of

visual technology that will be used to disseminate the messages, which can include textual visual

displays, SMS text messages, computer pop-ups, email, Internet websites, news (TV broadcast),

or streaming broadcast over the web. Depending upon the technology chosen to display visual

warning messages, guidance is provided here on message displays to enable occupants to see or

notice the displayed warning, understand the warning, perceive warning credibility and risk, and

respond appropriately.


(a) Place the emergency sign in a location where people will notice it and be able to read

it from their original (pre-emergency) location.


(c) Text is easier to read when written with a mixture of upper and lower case letters

rather than the use of all capitals.

(d) The recommended relationship for older adults with lower visual acuity is D = 100 *

h, providing a more conservative result, and ensuring that a larger population will be able

to read the emergency message.

(e) A stroke-to-width ratio of the letters is suggested as 1:5 (generally), with a ratio of 1:7

suggested for lighter letters on a darker background.

(f) Building managers, campus managers, or emergency personnel should consult the

ADA Standards for Accessible Design (U.S. Department of Justice 2010) for additional

requirements on signage.

(g) Contrast between the text and the background should be at least 30 percent, although

recommended values could be as high as 60 percent.

(h) The use of pictorials (in lieu of or in addition to text) can also bring attention to the

sign.

(i) Message providers should ensure that emergency information is not blocked by other

signs or information.


(a) Printed text should accompany symbols or pictorials used in visual warnings; a

minimum number of words should be used to accompany graphics.

(b) Diagrams that display a series of sequential steps are more successful for

comprehension of a process than one single graphic.

(c) A color-contrasted word or statement should be used for text that should be read first

and/or be perceived as more urgent than the rest, unless color is used for other reasons

(e.g.. bilingual text).

(d) A warning message can increase in perceived credibility and risk if occupants are

shown that others are also responding.

(e) Simultaneously displayed text (discrete messages) is preferred rather than a

sequentially displayed message.

(f) Simultaneously displayed text can also be used for bilingual messages, especially if

care is taken to differentiate the text of one language from the text of the other language.



There are specific warning technologies that only (or primarily) affect the aural sense, including

public address systems (voice notification systems), automated voice dialing, satellite/AM/FM

radio broadcasts, satellite/off-air television broadcasts, and tone alert radios. Whereas visual

technologies can limit message length, audible warnings are often limited only by the attention

capabilities of the audience. In other words, an audible message can play for long periods of time

with these technology types, and the message creator and source must be careful to provide all

important information in an appropriate length of time.

In this section, guidance will be given for methods to increase the likelihood that an individual

will perceive, or hear, the message. Following this, guidance will be provided that can increase

comprehension of the message for audible messages, as well as the ways in which to increase

credibility and risk assessment of the event when the warning is presented audibly.

(9) Perception.



Comprehending, Believing, and Personalizing the Warning.

(a) Letters are more difficult to identify in speech than numbers, which are more difficult

than colors.

(b) Message speakers (or sources) should not be heavily accented and should speak with

a rate of approximately 175 words per minute.

(c) Audible warnings can be delivered using a live voice, dynamic voice (generated by

text-to-speech software), or using pre-recorded voice.

(d) The live voice and dynamic voice methods provide the benefit of messages that can

be updated with new information while also conveying an appropriate level of urgency, if

necessary.

(e) Dynamic and pre-recoded voice methods provide the benefits of easily repeating the

played messages for longer periods of time and not relying on the voice announcer

training or stress level while delivering the message.

(f) For the voice itself, best results will vary, depending on the specific location — for

example, in outdoor applications, it has been shown that a male voice will provide better

intelligibility, as the naturally lower frequency of the male voice travels better. Inversely,

in an interior application, where the background ambient noise is typically in the same

lower frequencies, a female voice tends to penetrate better, as it is more distinct from the

ambient.

(g) Urgency measures should be used selectively to emphasize the more dangerous,

immediate, life-threatening situations (since overuse can lead to non-response in future

disasters).


(a) Use multiple channels to disseminate the warning message, including visual, audible,

and tactile means.

(b) A warning message should be repeated at least once, with some research advocating

for message repetition of at least three times.

(c) Messages should be stated in full, and then repeated in full, rather than repeating

statements within the same message.




(g) Messages should be disseminated using a combination of both push and pull

technologies.

(h) Push communication2 is most important to use for alert signals as well as initial

warning messages.

H.3 Emergency Message Templates. Rapid-onset emergencies often come with little warning and can have a major impact on

communities. In order to provide clear, effective instructions for a threatened population, it is important

to create message templates ahead of time for a variety of different emergencies.

This section provides examples of message templates for five types of emergency, using various

forms of emergency communication technology. All bracketed text can be altered and replaced

with text that better suits the needs of the occupants, emergency scenario, emergency response

strategies, and the technology being used. Please see Kuligowski and Omori (2014) for more

information on the process associated with the development of these templates. Each template

follows the guidance presented in this document.

H.3.1 Scenario 1 — Fire in a building, partial evacuation strategy, building-wide public

address announcements.

Scenario 1 is a fire located on the 10th floor of a 20-story building. Individuals are unable to use

elevators in this scenario, except for those who are unable to negotiate the stairs, in which case

building staff or fire fighters will assist them using the freight elevator(s).

Protective actions: Occupants on floors 9, 10, and 11 are told to evacuate to the 8th floor (two

floors below the fire floor). All other occupants are provided with a message to remain on their

floor. Therefore, in this scenario, two different types of messages are required to be provided

simultaneously to occupants, depending upon the floor on which they are located: one message

will be disseminated to floors 9, 10, and 11, while a different message will be disseminated

simultaneously to all other floors.

2 Push technologies are those that do not require individuals to take extra effort to receive the alert or warning

message (e.g., public address systems or text messages), whereas pull technologies require the individual to seek

additional information to acquire the alert/message (e.g., Internet websites).

Technology used to disseminate the message: The building-wide public address system, which is

capable of providing different messages to different floors (using a live voice or a dynamic

voice).

H.3.1.1 Message Templates for Scenario 1:

(1) Building-wide announcement to Floors 9, 10, and 11: “Attention [floors 9, 10, and 11].

This is your [Building Safety Officer, Joe Smith]. A fire has been reported on the [10th

floor] of the building. Everyone on the [9th, 10th, and 11th floors] should move to the

[8th floor] to be protected from heat and smoke, since heat and smoke can creep into

nearby floors during a fire. Use the stairs immediately. Do not use the elevators. Those

who need help getting to the 8th floor, please wait inside the stairwell [or go to the freight

elevator lobby].”

(2) Building-wide announcement to all other floors: “Attention. This is your [Building Safety

Officer, Joe Smith]. A fire has been reported on the [10th floor] of the building. Please

wait on your floor. At this time, you are safer remaining on your floor than leaving the

building, because this building is designed to confine the fire [e.g., locally or to the 10th

floor only]. Do not use the elevators for any reason. We will give you further instructions,

if the situation changes.”

H.3.2 Scenario 2 — Fire in a building, full evacuation strategy, building-wide public

address announcement, and cell phone text message.

Scenario 2 is a fire located on the second floor of a 20-story building in which smoke is traveling

up the building’s air-conditioning/venting system, causing the need for a full-building

evacuation. Individuals are unable to use elevators in this scenario, except for those who are

unable to negotiate the stairs, in which case building staff or fire fighters will assist them using

the freight elevator(s).

Protective actions: Occupants on all floors are requested to evacuate the building, known as a

full-building evacuation.

Technologies used to disseminate the message: The building-wide public address system, which

is capable of providing different messages to different floors (using a live voice or a dynamic

voice). Also, a 90-character text message alert to cell phone users in the building.


(1) Building-wide public address system: “Attention. This is [Chief Smith from the

Springfield Fire Department]. A fire has been reported on the [second floor] of the

building. Everyone must leave the building now to avoid contact with the fire’s heat and

smoke. Go NOW to your closest stair and leave the building. People who cannot use the

stairs should go to the freight elevator lobby for help.”

(2) Cell phone text message (90 characters): “Evacuate building now. It is on fire. Go to

freight elevator if you need help.”

Note: A description of the hazard (a more detailed “why” statement) is not included in this

message due to character limits. Also, the source is not listed. It is possible that the source will

already be identified in the “From” or “FRM” line of the text message. If message contents are

limited, there is always the option to send a follow-up text message that provides more

information or that continues the previous message. Also remember that some phones (i.e. non-

smart phones) could display longer text messages in reverse chronological order.

H.3.3 Scenario 3 — Tornado imminent on a college campus, campus-wide audible

messaging system, and Twitter message.


Protective actions: The individuals on the college campus are instructed to “shelter in place.”

Additionally, the National Weather Service provides examples of protective actions (included

below):

Example 1: “TAKE COVER NOW. FOR YOUR PROTECTION MOVE TO AN INTERIOR

ROOM ON THE LOWEST FLOOR OF A STURDY BUILDING.”

Example 2: “TAKE COVER NOW. MOVE TO AN INTERIOR ROOM ON THE LOWEST

FLOOR OF A STURDY BUILDING. AVOID WINDOWS. IF IN A MOBILE HOME...A

VEHICLE OR OUTDOORS...MOVE TO THE CLOSEST SUBSTANTIAL SHELTER AND

PROTECT YOURSELF FROM FLYING DEBRIS.”

Example 3: “THE SAFEST PLACE TO BE DURING A TORNADO IS IN A BASEMENT.

GET UNDER A WORKBENCH OR OTHER PIECE OF STURDY FURNITURE. IF NO

BASEMENT IS AVAILABLE...SEEK SHELTER ON THE LOWEST FLOOR OF THE

BUILDING IN AN INTERIOR HALLWAY OR ROOM SUCH AS A CLOSET. USE

BLANKETS OR PILLOWS TO COVER YOUR BODY AND ALWAYS STAY AWAY

FROM WINDOWS.”

IF IN MOBILE HOMES OR VEHICLES...EVACUATE THEM AND GET INSIDE A

SUBSTANTIAL SHELTER. IF NO SHELTER IS AVAILABLE...LIE FLAT IN THE

NEAREST DITCH OR OTHER LOW SPOT AND COVER YOUR HEAD WITH YOUR

HANDS.”


Technologies used to disseminate the message: A campus-wide siren system with audible

messaging capabilities. Also, a 140-character Twitter3 message should be disseminated as well

for this emergency.


(1) Campus-wide audible messaging system): Alert tone precedes message [siren]. “This is

[Joan Smith, Chief of Campus Police]. A tornado has been sighted on the ground at [20th

Street and Mockingbird Lane]. The tornado is strong and is moving toward the college

campus at high speeds (with winds over 160 mph). High winds and large, flying debris

3 Certain commercial entities, equipment, or materials are identified in this document in order to describe an

experimental procedure or concept adequately. Such identification is not intended to imply recommendation or

endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities,

materials, or equipment identified are necessarily the best available for the purpose.

can flatten a building in a storm of this magnitude. Take shelter now. Get inside now, go

to the lowest level, and get away from windows. Stay there until further instructions.”

(2) Twitter message (140 characters): “Take shelter inside a building NOW. Go to the lowest

level, get away from windows. Strong tornado near campus.” [Include hashtag in 140

characters.]

Note: The source of the message is not included in this Twitter message since the source will be

evident from the Twitter message layout.

H.3.4 Scenario 4 — Chemical spill in a building, building-wide public address

announcements, and building-wide email messages.

Scenario 4 is a chemical spill in a 40-story office building. The event was an accident and

occurred on the 1st floor of the building. There is the possibility of the chemical negatively

affecting individuals on the lower floors of the building. Individuals are unable to use elevators

in this scenario. For those who are unable to negotiate the stairs, only one freight elevator will be

used with fire-fighter assistance.

Protective actions: Occupants are advised to perform different actions based upon the floor on

which they are located. First, occupants on the first floor are advised to evacuate the building. At

the same time, occupants on floors 2 through 10 are advised to travel to locations higher in the

building — preferably to floors 20 through 30. Concurrently, occupants on floors 11 and above

are advised to remain in place. Therefore, in this scenario, three different types of messages are

required to be provided simultaneously to occupants, depending upon the floor on which they are

located: one message will be disseminated to the first floor, one message will be disseminated to

floors 2 through 10, and a third message will be disseminated to all other floors.

Technologies used to disseminate the message: The building public address system, which is

capable of providing different message to different floors (using a live voice or a dynamic voice).

Additionally, an email message (through the company’s email system) should be disseminated to

employees on floors 2 through 10 to relocate to a higher floor. [Note: Do not worry about an

email to other employees, although in an actual emergency, that would be necessary.]


(1) Building-wide public address system: [first floor occupants] “This is your [Building

Manager, Joe Smith]. A dangerous chemical has spilled on the first floor. The chemical

makes it difficult to see and can cause trouble breathing. Evacuate immediately.”

(2) Building-wide public address system: [floors 2 through 10] “This is your [Building


makes it difficult to see and can cause trouble breathing. Immediately use the stairs to

relocate to the [20th through 30th floors], and then wait for further instructions. If you

can’t use the stairs on your own, go to the freight elevator and wait for help. Relocate

now.”

(3) Building-wide public address system: [floors 11 and above] “This is your [Building


makes it difficult to see and can cause trouble breathing. People on [floors 1 through10]

are being evacuated. Please stay on your floor. You are safer remaining where you are

than if you try to leave the building. The chemical will not reach people on floors 11 and

above. You would possibly be exposed to the chemical if you tried to leave the building.

Do not use the elevators for any reason. We will give you further instructions if the

situation changes.”


H.3.5 Scenario 5 — Violent event in an airport, airport-wide visual messaging screens, and

cell phone text message.

The fifth scenario is a violent event. Specially, the emergency involves an active shooter that has

been identified in a major U.S. airport.

Example protective action: Occupants should evacuate the airport through all accessible doors,

including doors from the gate waiting areas onto the tarmac area.

Technologies used to disseminate the message (along with example character limits that can be

typical for these types of technologies): A 90-character text message alert to individuals’ phones

within the airport. Also, airport-wide visual messaging screens (limit message to 60 words or

less) can be used to alert individuals in terminals where the shooter is NOT located.


(1) Airport-wide visual messaging screens: “This is Los Angeles Police. Evacuate the

terminal NOW. Follow directions from airport security. Shots have been fired near Gate

22.”

(2) Cell phone text message (90 characters): “Leave NOW. Follow airport security. Shots

fired! Police report: Shooter in Terminal A.”

Note: A description of the hazard (a more detailed “why” statement) is not included in this

message due to character limits. If message contents are limited, there is always the option to

send a follow-up text message that provides more information or that continues the previous

message. Also remember that some phones (i.e., non-smart phones) could display longer text

messages in reverse chronological order.

H.4 Future Direction.

The purpose of this report is to provide guidance to system designers, building managers, and

building emergency personnel responsible for emergency communication on how to create and

disseminate effective messages using basic communication modes (audible vs. visual

technology), as well as examples of emergency messages (message templates) for five different

types of emergency scenarios. START (2013) contains additional message templates for similar

types of rapid-onset events for both limited- and unlimited-character length dissemination

technologies. Additionally, Kuligowski and Omori (2014) provide guidance on how to test the

effectiveness of these messages.

As with any document, there are gaps in the research that hinder the ability to provide guidance

on certain topics, including message length and repetition. This guidance document focuses

specifically on textual message creation, creating room for additional guidance on the

development and testing of visual symbols that could be used instead of, or in addition to, textual

emergency messages. In the future, as research gaps are addressed, additional editions of this

document would be useful to enhance the findings and guidance provided here.

H.5 References.

Kuligowski, E.D., S.M.V. Gwynne, K.M. Butler, B.L. Hoskins, and C.R. Sandler, 2012.

Developing Emergency Communication Strategies for Buildings. Technical Note 1733, National

Institute of Standards and Technology: Gaithersburg, MD.

Kuligowski, E.D. and Omori, H., 2014. General Guidance on Emergency Communication

Strategies for Buildings, 2nd Edition. NIST Technical Note 1827, National Institute of Standards

and Technology: Gaithersburg, MD.

U.S. Department of Justice, September 2010. 2010 ADA Standards for Accessible Design.

Washington, DC: DOJ. http://www.ada.gov/2010ADAstandards_index.htm.

START (National Consortium for the Study of Terrorism and Responses to Terrorism), 2013.

Task 2.9: Phase II Interim Report on Results from Experiments, Think-out-Louds, and Focus

Groups. University of Maryland, College Park: College Park, MD.

H.6 Footnotes.

1 Rapid-onset emergencies are those emergencies that occur with no or almost no (in the case of

minutes) notice, rather than slow-onset events (i.e., emergencies in which the occurrence is

known hours or even days in advance). These different emergency types require different sets of

emergency messages and dissemination techniques to allow building occupants to receive

information in a timely manner, resulting in efficient and safer public response.

2 Push technologies are those that do not require individuals to take extra effort to receive the

alert or warning message (e.g., public address systems or text messages), whereas pull

technologies require the individual to seek additional information to acquire the alert/message

(e.g., Internet websites).

3 Certain commercial entities, equipment, or materials are identified in this document in order to

describe an experimental procedure or concept adequately. Such identification is not intended to

imply recommendation or endorsement by the National Institute of Standards and Technology,

nor is it intended to imply that the entities, materials, or equipment identified are necessarily the

best available for the purpose.