Agenda Technical Committee on Emergency Communications ... · Agenda Technical Committee on...

Agenda Technical Committee on

Emergency Communications Systems June 24-25, 2014

La Jolla, CA

Item No. Subject 14-6-1 Call to Order (8:00 A.M) 14-6-2 Roll Call 14-6-3 Approval of Agenda 14-6-4 Approval Meeting Minutes – September 2013 [Enclosure] 14-6-5 Staff Remarks & Using the New Process [Staff] 14-6-6 Task Group Reports 14-6-7 Public Comments and Second Revisions [Enclosures] 14-6-8 Review of Committee Inputs [Enclosure] 14-6-9 UL Update on Fire Resistant Cable – Wednesday AM 14-6-10 Other Business 14-6-11 Adjournment

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

Technical Committee on Emergency Communication Systems

2016 First Draft Meeting Minutes St. Louis, MO

September 9, 10, & 11 2013

Wayne Moore-Chair

A. TC meeting called to order by Chair Wayne Moore at 8:10 AM-Monday 9th

B. Introductions of all present, no guests (except for floating NFPA staff)

C. Sign in sheets gathered by NFPA staff, see attached

D. Agenda was reviewed and Approved, see attached roster of attendees

E. Meeting Minutes for Pre First Draft were Approved

F. Discussion/presentation on Strategy to improve Correlation, by NFPA staff

G. Rodger Reiswig has obtained a seat on NFPA 1600

H. NFPA Staff requested three areas to be worked

a. Chapter 7 review ECS concerns [ no action needed]

b. Chapter 2 and references; review for current editions and content [created

FR for updates]

c. Chapter 3 definitions for ECS [created FR with changes]

I. Richard Roux, NFPA staff presented the new NFPA Process updates and

schedule for the next ECS meetings in this cycle

J. Day one broke for lunch at noon, resumed at 1:15 PM

a. First day ended at 5:30 PM

K. Day two session started at 8:05 AM

a. Lunch break at Noon, restarted at 1:00

b. Day 2 ended at 6:10 PM

L. Day three opened at 8:00 AM

a. Session Closed by Chair at 11:20 AM

M. Task Groups updated/formed in this meeting and cycle: New TG’s noted

Task Group Scope Chair Members

Documentation Review Ch 24 documentation

requirements and recommend reduction in duplicative material and relocate

some material to appropriate locations for improved flow.

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

Bruce Fraser Andrew Woodward, Rodger Reiswig, Sean Remke

Numbering of Sections Review Ch 24 numbering and

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

usability. Report: See above for comments,

CLOSED

Bruce Fraser Andrew Woodward, Rodger Reiswig, Sean Remke

Risk Analysis Where do we make this mandatory?

Is required for MNS System. Impacts on Combination Systems

where MNS is involved.

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

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

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

Siegel, Bruce Fraser

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

Develop language and PI

Report: Submitted PI’s CLOSED

Scott Lacey Ray Hansen, Waymon Jackson

Req for Monitoring FA and MNS Stand Alone Systems

Develop Language and PI Report: Submitted PI’s

CLOSED

Scott Lacey Derek Matthews, Ray Hansen

Test Schedule for Elevator Define and prepare PI

Report: Submitted PI’s

CLOSED

Bruce Fraser Wayne Moore

Test Schedule Area of Refuge Communication Systems

Rodger Reiswig Derek Mathews, Dan Finnegan, Waymon Jackson

Clean up 14.4.3.2; LSC 101 7.2.12 Develop PI

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

CLOSED

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

guidance and direction Develop PI

Report: Submitted PI’s

Dan Finnegan John Fuoto, Wayne Moore

Technology for Providing

Intelligibility May need to allow non-Fire listed

products for certain applications……

Report: TG submitted PI’s

John Fuoto

Mike Pallett , Denise Pappas, Andrew Woodward, Wayne

Moore, Derek Mathews, Dan Finnegan, Joe Collins

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

Annex Develop PI

Report: Need some outside SME on

this topic, need placeholder into document CLOSED

Charlie Hall Waymon Jackson, Joe Dafin, Jim Chambers

24.4.2.8 Review Evacuation Signals

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

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

CLOSED

Dan Finnegan Mike Pallett, Jim Mongeau

Prescriptive vs Performance Base for Risk Analysis

Develop PI

Report: PI’s submitted CLOSED

Sean Remke Ray Hansen, Waymon Jackson, Bruce Fraser

Area of Refuge Compare actual requirements with other

two way requirements

Mike Pallett Derek Mathews Needs to work with Rodgers

task group


LCD screens that would be primary visual notification appliances

Review and develop PI


Mike Pallett

Derek Mathews

Review of First Draft Document NEW (9.09.13)

Review FD accuracy as printed, including Correlation

Bruce Fraser

Bruce Fraser-Chair John Fannin Joe Collins

Review Communication Systems for Elevator and Stairs NEW (9.11.13)

Overlap of Systems-Recommendations

Bruce Fraser

Joe Ripp, Andrew Woodward Jim Mongeau, Mike Pallett,

Submitted Daniel P Finnegan

Secretary ECS TC

NFPA 72 SIG‐ECS First Draft Meeting

September 9‐11, 2013

Principals in Attendance: Wayne Moore Daniel Finnegan Peter Binkley Joe Collins Joseph Dafin John Fannin Bruce Fraser John Fuoto Charles Hahl Raymond Hansen Scott Lacey Robert Libby Derek Mathews James Mongeau Michael Pallett Joseph Ranaudo Rodger Reiswig Sean Remke Aviv Siegel James Simpson Andrew Woodward

Alternates in Attendance Raymond Grill David Madole Denise Pappas Thomas Parrish Joseph Ripp

Guests in Attendance Bob Schifiliti Josh Elvove Susan Ballester Chris Coache Staff Liaison: Richard Roux

Public Comment No. 32-NFPA 72-2014 [ Section No. 3.3.92 ]

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)

Statement of Problem and Substantiation for Public Comment

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

First Revision No. 345-NFPA 72-2013 [Section No. 3.3.93]

Submitter Information Verification

Submitter Full Name: Robert Schifiliti

Organization: R. P. Schifiliti Associates, I

Street Address:

City:

State:

Zip:

Submittal Date: Thu Apr 03 09:05:25 EDT 2014

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

38 of 346 5/19/2014 11:24 AM


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]


Submitter Full Name: Michael Pallett

Organization: Telecor Inc.

Street Address:

City:

State:

Zip:

Submittal Date: Fri May 16 13:31:45 EDT 2014


325 of 346 5/19/2014 11:24 AM

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 alarmcontrol unit or other designated location. (SIG-ECS) Actuation Time. Actuation of alarm notificationappliances or emergency voice communications, emergency control function interface devices, andannunciation at the protected premises shall occur within 10 seconds after the activation of an initiatingdevice.

A.23.8.1.1 Actuation of an initiating device is usually the instant at which a complete digital signal isachieved at the device, such as a contact closure. For smoke detectors or other automatic initiatingdevices, which can involve signal processing and analysis of the signature of fire phenomena, actuationmeans the instant when the signal analysis requirements are completed by the device or fire alarm controlunit software. A separate fire alarm control unit contemplates a network of fire alarm control units forming asingle large system as defined in Section 23.8. For some analog initiating devices, actuation is the momentthat the fire alarm control unit interprets that the signal from an initiating device has exceeded the alarmthreshold programmed into the fire alarm control unit. For smoke detectors working on a system with alarmverification, where the verification function is performed in the fire alarm control unit, the moment ofactuation 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 completetheir function, 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

Public Input No. 99-NFPA 72-2013 [Section No. 10.11]


Submitter Full Name: Rodger Reiswig

Organization: Tyco/SimplexGrinnell

Street Address:

City:

State:

Zip:

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


46 of 346 5/19/2014 11:24 AM


10.12 Alarm Signals.


5 of 346 5/19/2014 11:24 AM

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 theactivation of public or private alarm notification appliances.

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

10.12.3 *

Actuation of alarm notification appliances or emergency voice communications, emergency controlfunction interface devices, and annunciation at the protected premises shall occur within 10 seconds afterthe activation of an initiating

devicedevice in accordance with the required sequence of operations .

10.12.

2 4

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

10.12.3 5 *

Visible alarm strobe notification appliances shall not be activated when speaker notification appliances areused as permitted 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 otherthan the interconnection of control units shall not affect previously transmitted unacknowledged alarmsignals.

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 orless until 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)


6 of 346 5/19/2014 11:24 AM


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 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]


Submitter Full Name: Andrew Berezowski

Organization: Honeywell Inc.

Street Address:

City:

State:

Zip:

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


7 of 346 5/19/2014 11:24 AM


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 theactivation of an initiating device.

10.12.2*

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

10.12.3*

Visible alarm strobe notification appliances shall not be activated when speaker notification appliances areused as permitted 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

The subsequent occurrence of a fault on an initiating device circuit or a signaling line circuit used for otherthan the interconnection of control units shall not affect previously transmitted unacknowledged alarmsignals.

10.12.8

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

10.12.8.1

The audible and visible alarm signal at the control unit only shall automatically reactivate every 24 hours orless until 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.


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

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


Submitter Full Name: Andrew Berezowski

Organization: Honeywell Inc.

Affilliation: SIG-ACC Strobe Operation TG

Street Address:

City:

State:

Zip:

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


30 of 346 5/19/2014 11:24 AM


24.1.3

The requirements of Chapters 7, 10, 12, 17, 18, 21, 23, 26, and 27 shall also apply unless they are inconflict with this chapter.


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

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

Correlating Committee Note No. 26-NFPA 72-2014 [Section No. 24.1.3]


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:48:39 EDT 2014


96 of 346 5/19/2014 11:24 AM


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

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




Street Address:

City:

State:

Zip:



45 of 346 5/19/2014 11:24 AM


24.3.3 * Microphone Use. 24.3.3.1 *

All users of systems that have microphones for live voice announcements shall be provided with postedinstructions for using the microphone.


Editorial to comply with the Manual of Style

Related Item

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


Submitter Full Name: Bruce Fraser

Organization: Fraser Fire Protection Service

Street Address:

City:

State:

Zip:

Submittal Date: Tue May 13 14:28:59 EDT 2014


131 of 346 5/19/2014 11:24 AM

Public Comment No. 137-NFPA 72-2014 [ Section No. 24.3.6.4 ]

24.3.6.4

The utilization of shared pathway levels 1 and 2 , as specified in Section 12.5, for Class N pathways usedin emergency communication systems to support ancillary functions, devices, or systems via commonpathways, shall be 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:



163 of 346 5/19/2014 11:24 AM


24.3.6.4

The utilization of shared pathway levels, as specified in Section 12.5 , for Where Class N pathways usedin emergency communica on systems to systems u lize shared pathway levels 1 & 2 as the means tosupport ancillary functions, devices, or interconnected systems via common pathways, shall bedetermined , the shared pathways shall meet the requirements of 23.6.3 , be permitted by a risk analysis, andapproved 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 Public Comments for This Document

Related Comment Relationship

Public Comment No. 137-NFPA 72-2014 [Section No. 24.3.6.4]

Related Item





Street Address:

City:

State:

Zip:



164 of 346 5/19/2014 11:24 AM


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


CC NOTE: The following CC Note No. 9 appeared in the First Draft Report as First Revision No. 309, and is also related to Public Input No. 413.

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


Public Input No. 413-NFPA 72-2013 [Section No. 24.3.7]




Street Address:

City:

State:

Zip:

Submittal Date: Wed Apr 30 09:32:51 EDT 2014


62 of 346 5/19/2014 11:24 AM


24.3.7.1 *

Messages Message content shall be developed for each scenario developed and documented inthe emergency response 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:


Copyright Assignment

I, Michael Pallett, hereby irrevocably grant and assign to the National Fire Protection Association (NFPA) all and full rights incopyright in this Public Comment (including both the Proposed Change and the Statement of Problem and Substantiation). Iunderstand and intend that I acquire no rights, including rights as a joint author, in any publication of the NFPA in which thisPublic Comment in this or another similar or derivative form is used. I hereby warrant that I am the author of this Public Commentand that I have full power and authority to enter into this copyright assignment.

By checking this box I affirm that I am Michael Pallett, and I agree to be legally bound by the above Copyright Assignment andthe terms and conditions contained therein. I understand and intend that, by checking this box, I am creating an electronicsignature that will, upon my submission of this form, have the same legal force and effect as a handwritten signature

National Fire Protection Association Report http://submittals.nfpa.org/TerraViewWeb/FormLaunch?id=/TerraView/C...

1 of 1 5/28/2014 11:08 AM

Public Comment No. 217-NFPA 72-2014 [ Section No. A.24.3.7.1 ]

A.24.3.7.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 areconsiderably more intelligible than live messages and should be developed and provided to handle asmany of the probable emergencies that a particular facility will encounter.

The voice instructions (live or prerecorded) should be preceded by a tone to get attention and prepare thetarget audience for voice instructions. This tone should be differentiated for specific emergencies, based onthe standards 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 theaction to be taken and minimize 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 malevoice 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 lowerfrequencies, a female voice tends to penetrate better, as it is more distinct from the ambient. Messagesshould be constructed using 2-second to 3-second bursts of information and brief periods of quiet betweenthe bursts of information. This methodology facilitates better processing of information by the brain andminimizes 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 avoice message that is repeated at least three times. The alert tone can be used in between repeats of thevoice message.

For live instructions, it is critical that the message be delivered in a clear and calm manner. When possible,the following procedure is recommended:

(1) Think about what information must be delivered in the live announcement, keep it brief, and writedown the message

(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 onEmergency Communication 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:


321 of 346 5/19/2014 11:24 AM



322 of 346 5/19/2014 11:24 AM


24.3.7.2 *

A message template shall be developed for each message required Messages content shall bedesigned based on a pre-established message structure or template. Message templates shall bedeveloped for each emergency type, specific to the technological method of message delivery, tosupport the development of consistent and effective 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.

Related Public Comments for This Document

Related Comment Relationship

Public Comment No. 218-NFPA 72-2014 [Section No. A.24.3.7.2]

Related Item






Street Address:

City:

State:

Zip:






1 of 1 5/28/2014 11:10 AM

Public Comment No. 218-NFPA 72-2014 [ Section No. A.24.3.7.2 ]

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 shouldnot 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 attentionpaid to the frequency — the more it is repeated, the better.

Additional information on this topic is availaible in the NIST Technical Note 1779, General Guidance onEmergency Communication 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:



323 of 346 5/19/2014 11:24 AM


24.3.8 * System Classification.

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

24.3.8.1

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

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

(2) In-building mass notification systems (see 24.4.3 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:



144 of 346 5/19/2014 11:24 AM


24.3.8 * System Classification.

Emergency communications systems (ECS) shall consist of two classifications of systems, one shall bedesignated as 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:

Submittal Date: Wed May 14 17:56:40 EDT 2014


261 of 346 5/19/2014 11:24 AM


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 (see24.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]]


Submitter Full Name: Sagiv Weiss-Ishai

Organization: San Francisco Fire Department

Street Address:

City:

State:

Zip:

Submittal Date: Mon May 12 19:04:03 EDT 2014


127 of 346 5/19/2014 11:24 AM


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 atleast one of 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


Public Input No. 417-NFPA 72-2013 [Section No. 24.3.10]

Public Input No. 499-NFPA 72-2013 [Section No. 24.4.3.24]




Street Address:

City:

State:

Zip:



47 of 346 5/19/2014 11:24 AM

Public Comment No. 122-NFPA 72-2014 [ New Section after 24.3.12.3 ]

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 anddocumented. This can be included in the design brief described in 24.7.6.6 or in a separate document. NFPA 551 Guide for the Evaluation of Fire Risk Assessments, Chapter 7 provides guidance on how the riskassessment should be documented.

Substatiation - FR #312 remeved the reference to the perfromanced based design section. Without the tieto Section 24.7, the requirement for documenting the risk analysis as part of the design is not clear. Section 7.3.6 only requires “findings and considerations” be documented. Section 24.7 requires goals,objectives, performance criteria and risk analysis be incorporated in the design documentation as part ofthe “design brief”. If 24.3.11.3 goes away, 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

First Revision No. 312-NFPA 72-2013 [Section No. 24.3.11.3]


Submitter Full Name: Kenneth Dungan

Organization: Performance Design Technologie

Street Address:

City:

State:

Zip:



130 of 346 5/19/2014 11:24 AM


24.3.14.7

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

Exception: Level 1 shall be permitted where the building is the communication zones are separated byless than 2-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:



123 of 346 5/19/2014 11:24 AM

Public Comment No. 117-NFPA 72-2014 [ Section No. 24.3.14.8.1 ]

24.3.14.8.1 *

Where a two-way radio emergency radio communications enhancement system is used in lieu of atwo-way in-building wired emergency communications system provided , it shall have a pathwaysurvivability of Level 1, Level 2, or Level 3. Level 1 pathway survivability shall be permitted in buildingshaving communication zones separted by less than 2-hours construction.

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

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 avalue determined 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:



124 of 346 5/19/2014 11:24 AM

Public Comment No. 118-NFPA 72-2014 [ Section No. 24.3.14.8.2 ]

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 authorityhaving jurisdiction.


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:



125 of 346 5/19/2014 11:24 AM

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) andelevator landing emergency communications systems shall comply with 24.3.14.9.1 and24.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:



I, Sagiv Weiss-Ishai, hereby irrevocably grant and assign to the National Fire Protection Association (NFPA) all and full rights incopyright in this Public Comment (including both the Proposed Change and the Statement of Problem and Substantiation). Iunderstand and intend that I acquire no rights, including rights as a joint author, in any publication of the NFPA in which thisPublic Comment in this or another similar or derivative form is used. I hereby warrant that I am the author of this Public Commentand that I have full power and authority to enter into this copyright assignment.

By checking this box I affirm that I am Sagiv Weiss-Ishai, and I agree to be legally bound by the above Copyright Assignmentand the terms and conditions contained therein. I understand and intend that, by checking this box, I am creating an electronicsignature that will, upon my submission of this form, have the same legal force and effect as a handwritten signature


1 of 1 5/28/2014 12:29 PM


24.4.8* Relocation and Partial Evacuation.

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

24.4.8.1

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

24.4.8.2

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

24.4.8.3

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

24.4.8.3.1

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

24.4.8.3.2

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

24.4.8.4

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

24.4.8.4.1

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

24.4.8.4.2

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

24.4.8.5

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

24.4.8.5.1*

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

24.4.8.5.2

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

24.4.8.5.3*

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


63 of 346 5/19/2014 11:24 AM

24.4.8.5.4

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

24.4.8.5.5

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

24.4.8.5.6

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

(1) A 2-hour fire-rated enclosure

(2) A 2-hour fire-rated room

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

24.4.8.5.7

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


CC NOTE: The following CC Note No. 10 appeared in the First Draft Report as First Revision No. 358, and is also related to Public Input No. 385.

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

First Revision No. 358-NFPA 72-2013 [Section No. 24.4.2.8]





Street Address:

City:

State:

Zip:



64 of 346 5/19/2014 11:24 AM


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 frequenciesassigned to the jurisdiction by the FCC shall be installed without prior coordination and approval of theauthority having jurisdiction. The building manager/owner shall suspend and correct other equipmentinstallations that degrade the performance of the public safety radio system or public safety radioenhancement system.

24.5.2.1.2 Approval and Permit.

Plans shall be submitted for approval prior to installation. At the conclusion of successful acceptancetesting, a renewable permit shall be issued for the public safety radio enhancement system where requiredby the authority having 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,elevator lobbies, standpipe cabinets, sprinkler sectional valve locations, and other areas deemed critical bythe authority having 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 aradiating cable system or a distributed antenna system (DAS) with FCC-certified signal boosters, or both,or with a system that 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 bythe authority 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 antennasand shall 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 radiofrequencies assigned 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 distributionto system 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.


340 of 346 5/19/2014 11:24 AM

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 approvedand shall be compatible with the public safety radio system

2 All in-building two way radio systems shall be inspected, tested and maintained per th rerquirements ofChapter 14 .

24.5.2. 5. 2 Component Enclosures .

All repeater, transmitter, receiver, signal booster components, and battery system components shall becontained in a 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 requirementsdetermined by the authority having jurisdiction:

(1)

(2) All signal boosters shall be compatible with both analog and digital communications simultaneously atthe time of installation. The authority having jurisdiction shall provide the maximum acceptablepropagation delay standard.

24.5.2.5.5 Power Supplies.

At least two independent and reliable power supplies shall be provided for all repeater, transmitter,receiver, and signal 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 operationcapacity and arranged in accordance with 10.6.10 .

(2) An automatic-starting, engine-driven generator serving the dedicated branch circuit or the systemwith at least 12 hours of 100 percent system operation capacity and storage batteries dedicated tothe system with at least 2 hours of 100 percent system operation capacity and arranged inaccordance 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.

* Signal boosters shall have FCC certification prior to installation.


341 of 346 5/19/2014 11:24 AM

24.5.2.6.1 Fire Alarm System.

The public safety radio communications enhancement system shall include automatic supervisory andtrouble signals for malfunctions of the signal booster(s) and power supply(ies) that are annunciated by thefire alarm system and comply with the following:

(1) The integrity of the circuit monitoring signal booster(s) and power supply(ies) shall comply with10.6.9 and Section 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 beendepleted.

(6) Power supply signals shall include the following for each signal booster:

(7) Loss of normal ac power

(8) Failure of battery charger

24.5.2.6.2 * Dedicated Panel.

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

(1) Normal ac power

(2) Signal booster trouble

(3) Loss of normal ac power

(4) Failure of battery charger

(5) Low-battery capacity

24.5.2.7 Technical Criteria.

The authority having jurisdiction shall maintain a document of technical information specific to itsrequirements, 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 radioenhancement system

(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 inspectiondocumentation shall be 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


342 of 346 5/19/2014 11:24 AM



Public Input No. 264-NFPA 72-2013 [Section No. 24.5.2.3.1]

Public Input No. 265-NFPA 72-2013 [Section No. 24.5.2.3.2]


Submitter Full Name: Thomas Parrish

Organization: Telgian Corporation

Street Address:

City:

State:

Zip:



343 of 346 5/19/2014 11:24 AM


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 theloudspeaker circuit if 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:



318 of 346 5/19/2014 11:24 AM


24.5.5 Documentation.

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 .


This is duplicate material. See Section 24.15.

Related Item

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




Street Address:

City:

State:

Zip:

Submittal Date: Wed May 14 16:39:02 EDT 2014


259 of 346 5/19/2014 11:24 AM


24.5.15.1

Unless otherwise established through the emergency response plan, controls Controls that are intended tobe accessed 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:



313 of 346 5/19/2014 11:24 AM


Where no listed device exists for the visable no fica on required by the emergency responseplan, nonlisted devices 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:






1 of 1 5/28/2014 12:35 PM


Where no listed device exists for the textual or graphical no fica on required by the emergencyresponse 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:



316 of 346 5/19/2014 11:24 AM

Public Comment No. 214-NFPA 72-2014 [ New Section after 24.5.20 ]

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 themass notification system.



Related Item





Street Address:

City:

State:

Zip:



317 of 346 5/19/2014 11:24 AM


24.6.4 Emergency Command Center.

Refer to Section 24.13 for requirements of an emergency command center.


CC NOTE: The following CC Note No. 31 appeared in the First Draft Report as First Revision No. 333.

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:



65 of 346 5/19/2014 11:24 AM


24.10.4

All pathways between a remote area of refuge stations and the central control point shall be monitored forintegrity with 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



Submitter Full Name: VINCE BACLAWSKI

Organization: NEMA

Street Address:

City:

State:

Zip:

Submittal Date: Mon Apr 28 10:33:48 EDT 2014


53 of 346 5/19/2014 11:24 AM

Committee Input No. 339-NFPA 72-2013 [ Section No. 2.2 ]

This was a First Revision that has been modified or deleted as the result of First CorrelatingRevision: FCR-36-NFPA 72-2014

2.2 NFPA Publications.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Submitter Full Name: Richard Roux

Organization: National Fire Protection Assoc

Street Address:

City:

State:

Zip:

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

Committee Statement

Committee Statement: The TC updates 2.2 effective dates.

Response Message:


6 of 68 5/29/2014 9:03 AM

Ballot Results

This item has passed ballot

28 Eligible Voters

2 Not Returned

25 Affirmative All

0 Affirmative with Comments

1 Negative with Comments

0 Abstention

Not Returned

Aron, Oded

Ulizio, Robert Anthony

Affirmative All

Binkley, Peter

Bridgett, Daniel

Chambers, Thomas M.

Collins, Joe L.

Dafin, Joseph

Fannin III, John C.

Finnegan, Daniel P.

Fraser, Bruce

Fuoto, John S.

Hahl, Charles E.

Hansen, Raymond N.

Jackson, Waymon

Leng, Minfei M.

Libby, Robert J.

Mathews, Derek D.

Mongeau, James

Moore, Wayne D.

Pallett, Michael

Parrish, Thomas J.

Ranaudo, Joseph

Reiswig, Rodger

Scott, Jeffrey A.

Siegel, Aviv

Simpson, James P.

Woodward, Andrew B.

Negative with Comment

Lacey, Scott

We are citing several documents with issue dates of 2016 that will not be voted on until after NFPA 72 is voted onand printed. We should not be referencing documents of the future.


7 of 68 5/29/2014 9:03 AM

Committee Input No. 347-NFPA 72-2013 [ Section No. 7.3.6 ]


7.3.6 * Risk Analysis Documentation. (SIG-ECS)

7.3.6.1

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

7.3.6.2

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

7.3.6.3

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

7.3.6.4

Risk analyses for mass notification systems shall be documented in accordance with 7.3.6 and 24.3.11.

Supplemental Information

File Name Description

Attachment_for_FR_347.EC_edits.docx




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

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

ResponseMessage:

Ballot Results


28 Eligible Voters

2 Not Returned

26 Affirmative All



0 Abstention


9 of 68 5/29/2014 9:03 AM

Not Returned

Aron, Oded


Affirmative All

Binkley, Peter

Bridgett, Daniel

Chambers, Thomas M.

Collins, Joe L.

Dafin, Joseph

Fannin III, John C.

Finnegan, Daniel P.

Fraser, Bruce

Fuoto, John S.

Hahl, Charles E.

Hansen, Raymond N.

Jackson, Waymon

Lacey, Scott

Leng, Minfei M.

Libby, Robert J.

Mathews, Derek D.

Mongeau, James

Moore, Wayne D.

Pallett, Michael

Parrish, Thomas J.

Ranaudo, Joseph

Reiswig, Rodger

Scott, Jeffrey A.

Siegel, Aviv

Simpson, James P.

Woodward, Andrew B.


10 of 68 5/29/2014 9:03 AM

Committee Input No. 337-NFPA 72-2013 [ Section No. 7.5.9 ]


7.5.9

Owner’s Manual.

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

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

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

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

(4) Detailed description of routine maintenance and testing as required and recommended and as wouldbe provided under a maintenance contract, including testing and maintenance instructions for eachtype of device installed, which includes the following:

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

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

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

(8) Service directory, including a list of names and telephone numbers of those who provide service forthe system

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

7.5.10

Documentation of central station service shall be in accordance with 26.3.4. (SIG-SSS)




Street Address:

City:

State:

Zip:


Committee Statement

Committee Statement: The TC adds new 7.5.8 which is incorporated from 24.8.3.

The TC adds item (6).


11 of 68 5/29/2014 9:03 AM

Response Message:


Ballot Results


28 Eligible Voters

2 Not Returned

26 Affirmative All



0 Abstention

Not Returned

Aron, Oded


Affirmative All

Binkley, Peter

Bridgett, Daniel

Chambers, Thomas M.

Collins, Joe L.

Dafin, Joseph

Fannin III, John C.

Finnegan, Daniel P.

Fraser, Bruce

Fuoto, John S.

Hahl, Charles E.

Hansen, Raymond N.

Jackson, Waymon

Lacey, Scott

Leng, Minfei M.

Libby, Robert J.

Mathews, Derek D.

Mongeau, James

Moore, Wayne D.

Pallett, Michael

Parrish, Thomas J.

Ranaudo, Joseph

Reiswig, Rodger

Scott, Jeffrey A.

Siegel, Aviv

Simpson, James P.

Woodward, Andrew B.


12 of 68 5/29/2014 9:03 AM

Committee Input No. 204-NFPA 72-2013 [ New Section after 7.7.1.4 ]

7.7.1.5 Emergency Communication system and fire alarm system as-built plans and other relateddocumentation shall be permitted to be maintained together, including the appearance of both systems onthe same drawings. (SIG-ECS)


Submitter Full Name: [ Not Specified ]

Organization: [ Not Specified ]

Street Address:

City:

State:

Zip:

Submittal Date: Fri Sep 13 13:18:21 EDT 2013

Committee Statement

CommitteeStatement:

This new paragraph is incorporated from Chapter 24 into Chapter 7 as documentation. It is theintent to tag the section as SIG-ECS to keep it their responsibility.

ResponseMessage:

Ballot Results

This item has not been balloted


13 of 68 5/29/2014 9:03 AM

Committee Input No. 361-NFPA 72-2013 [ Section No. A.7.8.2 ]


58 of 68 5/29/2014 9:03 AM

A.7.8.2


59 of 68 5/29/2014 9:03 AM

Examples of completed record of completion forms are shown in Figure A.7.8.2(a) through FigureA.7.8.2(f) , and a risk analysis checklist form can be found in Figure A . 7.8.2(g).

Figure A.7.8.2(a) Example of Completed System Record of Completion.

Figure A.7.8.2(a) Continued

Figure A.7.8.2(a) Continued


60 of 68 5/29/2014 9:03 AM

Figure A.7.8.2(b) Example of Completed Emergency Communications System SupplementaryRecord of Completion.

Figure A.7.8.2(b) Continued


61 of 68 5/29/2014 9:03 AM

Figure A.7.8.2(b) Continued

Figure A.7.8.2(c) Example of Completed Power Systems Supplementary Record of Completion.


62 of 68 5/29/2014 9:03 AM

Figure A.7.8.2(c) Continued

Figure A.7.8.2(d) Example of Completed Notification Appliance Power Panel SupplementaryRecord of Completion.


63 of 68 5/29/2014 9:03 AM

Figure A.7.8.2(e) Example of Completed Interconnected Systems Suplementary Record ofCompletion.

Figure A.7.8.2(f) Example of Completed Deviations from Adopted Codes and StandardsSupplementary Record of Completion.


64 of 68 5/29/2014 9:03 AM

Figure A.7.8.2(g) Risk Analysis Checklist.

Figure A.7.8.2(g) Continued


65 of 68 5/29/2014 9:03 AM


Submitter Full Name: Lee Richardson


Street Address:

City:

State:

Zip:

Submittal Date: Mon Oct 07 11:04:32 EDT 2013

Committee Statement

CommitteeStatement:

The reference to Figure A.7.8.2(g) is causing confusion and it is suggested that the CC review thisand possibly relocate Figure A.7.8.2(g) to a different Chapter 7 section. The Risk Analysis Checklistonly appears in the annex (under the purview of SIG-ECS - see A.24.3.11) and because of thisthere is confusion in the numbering since there is no 7.8.2(g) in the Code text.

The Risk Analysis Checklist in A.7.8.2(g) is not considered part of Record of Completion so thechecklist needs to be relocated to appropriate existing Section 7.3.6 Risk Analysis Documentationas Annex material. The TC deletes Figure A.7.8.2(g) from A.7.8.2. See FR 347 for new location.

ResponseMessage:

Ballot Results

This item has not been balloted


66 of 68 5/29/2014 9:03 AM

Committee Input No. 343-NFPA 72-2013 [ New Section after A.24.3.1 ]


A 24.3.1

When a rapid on-set emergency occurs, it is not always sufficient to simply initiate alarmnotification appliances. Individuals may not know what the alarm signal means (or even hear it)and as a result may not respond appropriately to the warning signal. Mass notification andemergency communication systems have been designed and installed to be used to disseminateaudible and visual messages in the event of an emergency. Such systems are based uponguidance and requirements provided in international codes and standards.

There is limited guidance on how to use emergency communication systems and massnotification systems in the most effective manner. For example, buildings often use thesesystems to disseminate pre-recorded, general emergency voice alarm messages that leaveoccupants wanting and needing further information before effectively responding. As the use ofnewer technologies including mobile devices with multiple message delivery platforms (e.g.,SMS text, internet, email, social networking), guidance on message content and disseminationbecomes even more critical to ensure effective and safe response of building occupants duringan emergency .

However, for any specific application, there are characteristics that any emergency messageshould have in order to be effective. Messages being appropriate means that the messagesshould get the attention of the recipients in a timely manner, the messages are credible to therecipients, and comprehensible by the intended recipients. Being comprehensible means thatthe language, method of delivery and content of the message are such that the intendedmessage recipients should be able to understand the message in enough time to be able todecide to take the appropriate response to the message.

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

The following referenced document describes the process in which people receive and processinformation in order to take action during rapid on-set emergencies. The document presentsguidance on how to create and disseminate emergency information in the face of rapid-onsetdisasters – 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 disseminationof the warning message. This document is focused on emergency notification within buildings,however, many of the general principles apply to outdoor and wide-area notification as well.




Street Address:

City:

State:

Zip:


Committee Statement

CommitteeStatement:

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


67 of 68 5/29/2014 9:03 AM

ResponseMessage:


Ballot Results


28 Eligible Voters

2 Not Returned

26 Affirmative All



0 Abstention

Not Returned

Aron, Oded


Affirmative All

Binkley, Peter

Bridgett, Daniel

Chambers, Thomas M.

Collins, Joe L.

Dafin, Joseph

Fannin III, John C.

Finnegan, Daniel P.

Fraser, Bruce

Fuoto, John S.

Hahl, Charles E.

Hansen, Raymond N.

Jackson, Waymon

Lacey, Scott

Leng, Minfei M.

Libby, Robert J.

Mathews, Derek D.

Mongeau, James

Moore, Wayne D.

Pallett, Michael

Parrish, Thomas J.

Ranaudo, Joseph

Reiswig, Rodger

Scott, Jeffrey A.

Siegel, Aviv

Simpson, James P.

Woodward, Andrew B.


68 of 68 5/29/2014 9:03 AM

Agenda Technical Committee on Emergency Communications ... · Agenda Technical Committee on...

Documents

Transcript of Agenda Technical Committee on Emergency Communications ... · Agenda Technical Committee on...