Download - AGENDA TECHNICAL CORRELATING COMMITTEE ON … · agenda . technical correlating committee on . signaling systems for the protection of life and property . april 12-14, 2011 . holiday

AGENDA

TECHNICAL CORRELATING COMMITTEE ON SIGNALING SYSTEMS FOR THE PROTECTION OF LIFE AND PROPERTY

APRIL 12-14, 2011 HOLIDAY INN RIVERWALK, SAN ANTONIO

Item No. Subject 11-4-1 Call to Order (8:00 A.M., April 12, 2011) 11-4-2 Roll Call 11-4-3 Staff Remarks 11-4-4 Approval Meeting Minutes September 21, 2010 [Enclosure] 11-4-5 Approval of Agenda 11-4-6 Update on Standards Council Actions [L. Richardson] 11-4-7 Update on Mid-Cycle FI and TIA Activities [L. Richardson] 11-4-8 NFPA 720 Chair Report [T. Norton] 11-4-9 NFPA 72 Chair Reports

1) SIG-FUN [S. Clary] 2) SIG-TMS [J. Moore] 3) SIG-IDS [D. OConnor] 4) SIG-NAS [R. Grill] 5) SIG-PRO [M. Bunker] 6) SIG-ECS [W. Moore] 7) SIG-SSS [W. Olsen] 8) SIG-PRS [J. Knight] 9) SIG-HOU [L. Dallaire]

11-4-10 Terminology Task Groups See Minutes Item 10-9-7

1) Glossary of Terms [J. McNamara] 2) Alarm, Supervisory, Trouble [A. Berezowski] 3) Control Locations [D. Aiken] 4) Emergency Plan Terms

11-4-11 New Chapter on Plans and Documentation 1) Placement 2) Ownership

11-4-12 Review of Proposals for TCC Action Notes A - Individual TC Reports on Proposal

1) SIG-FUN (Ch 1 & 10) 2) SIG-TMS (Ch 14, Ann D, Ann G) 3) SIG-IDS (Ch 17) 4) SIG-NAS (Ch 18) 5) SIG-PRO (Ch 12, 21, 23, Ann C) 6) SIG-ECS (Ch 24) 7) SIG-SSS (Ch 26) 8) SIG-PRS (Ch 27) 9) SIG-HOU (Ch 29)

B - Entire Report on Proposals 11-4-13 TCC Task Group Reports (other than Agenda Item 11-4-10)

1) Water Flow Switch Testing Frequency See Minutes Item 10-9-6 [T. Norton]

2) Review of NFPA 550 See Minutes Item 10-9-12 [L. Nielson] 3) Joint TG on Wiring [S. Clary] 4) Low Frequency Requirements See Minutes Item 10-9-14(7) [W.

Moore or designee] 11-4-14 TCC Liaison Reports

1) NFPA 25 [T. Norton] 2) NFPA 101 [W. Moore]

11-4-15 ITM Summit (next steps) 11-4-16 Fire Detection and Alarm Research Council Research Priorities 11-4-17 Chair Training 11-4-18 25-Year Pins 11-4-19 Old Business See Minutes Item 10-9-14

1) FPRF Messaging Strategies 2) Radio Transmission Paths [L. Fiore] 3) NFPA 170 [J. Mundy] 4) Tracking of Code Adoptions [L. Richardson]

11-4-20 New Business

11-4-21 Adjournment (3:00 P.M., April 14, 2011)

1

Meeting Minutes of the

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

September 21, 2010 (Indianapolis, IN)

Item 10-9-1 Call to Order Chair Robert P. Schifiliti (R.P. Schifiliti Associates, Inc.) called the meeting to order at 8:00 AM ET. Item 10-9-2a Roll Call In addition to the chair, the following TCC members were present: Aiken, Douglas M. (P) International Municipal Signal Association Berezowski, Andrew G. (P) National Electrical Manufacturers Association Boyer, Robert J. (P) Edwards, a UTC Company Fannin, John C., III (P) SafePlace Corporation Fiore, Louis T. (P) Central Station Alarm Association Fraser, Bruce (P) Fraser Fire Protection Services Humm, Vic (P) Vic Humm & Associates Klein, David (P) International Association of Fire Chiefs Larrimer, Peter A. (P) U.S. Department of Veterans Affairs Leber, Fred M. (P) Leber/Rubes Incorporated Mundy, James M. Jr. (P) Automatic Fire Alarm Association, Inc Norton, Thomas F. (P) US Naval Historical Center Reiswig, Rodger (P) Tyco International Smith, Tom G. (P) National Electrical Contractors Association Brooks, Jeffrey (A) Tyco International Hammerberg, Thomas P. (A) Automatic Fire Alarm Association, Inc McNamara, Jack (A) National Electrical Manufacturers Association Shudak, Larry (VA) Underwriters Laboratories Inc. Van Overmeiren, Frank (A) FP&C Consultants, Inc Bunker, Merton W., Jr. (NV PRO Chair) US Department of State Dallaire, L.J. (NV HOU Chair) US Architect of the Capitol Grill, Raymond A. (NV NAS Chair) Arup Fire Knight, Jeffrey G. (NV PRS Chair) City of Newton Fire Department Moore, J. Jeffrey (NV TMS Chair) Hughes Associates, Inc Moore, Wayne D. (NV ECS Chair) Hughes Associates, Inc OConnor, Daniel J. (NV IDS Chair) Aon/Schirmer Engineering Corp Olsen, Warren E. (NV SSS Chair) Fire Safety Consultants, Inc. The following TCC members were not present: Black, Art (P) Carmel Fire Dept/Carmel Fire Protection

2

Nielson, Lynn (P) City of Henderson Wenzel, Larry (P) Hughes Associates, Inc Bukowski, Dick W. (A) Rolf Jensen & Associates Valois, Earl A. (A) International Association of Fire Chiefs Clary, Shane M. (NV FUN Chair) Bay Alarm Company Reiss, Martin H. (NV Safety to Life CC) The RJA Group, Inc. Stauffer, Evan E. (NV Public Emer Serv) US Department of the Navy Wilson, Dean K. (NV Member Emeritus) Hughes Associates, Inc. The following NFPA Staff was present: Richardson, Lee F. (Secretary) NFPA Roux, Richard NFPA Burke, William NFPA Item 10-9-2b Approval of Agenda It was moved, seconded and voted unanimously affirmative that the agenda for this meeting of the Technical Correlating Committee on Signaling Systems for the Protection of Life and Property be approved. Item 10-9-3 Staff Remarks NFPA staff provided opening remarks including a review of NFPA regulations regarding special experts, essential patent claims, basic meeting procedures and cycle schedules for NFPA 72 and NFPA 720. An integrated NFPA 72 and NFPA 720 TCC schedule was provided and will be added to the Ecommittee page for the TCC. There was a general question on electronic signature requirements for proposals submitted electronically (by email). NFPA staff was requested to investigate and report back. [Subsequently, NFPA Staff determined that electronic signatures must be in the form of an actual signature placed electronically on the proposal form (e.g. pasting a scanned pdf or a jpeg onto the signature space).] Item 10-9-4 Approval of April 7, 2010 Meeting Minutes It was noted that minutes should be amended to show Jim Mundy in attendance. It was moved, seconded and voted unanimously affirmative that the minutes of the April 7, 2010 meeting of the Technical Correlating Committee on Signaling Systems for the Protection of Life and Property be approved as amended. The amended meeting minutes are enclosed. Item 10-9-5 Document Information and Ecommittee Pages

3

NFPA staff provided a live demonstration of the NFPA 72 document information page and the Ecommittee page. It was noted that agendas, meeting notices and meeting minutes are now being placed on the document information page. The subject of having web-based meetings versus face-to-face meetings was discussed. It was agreed that these types of meetings can be productive where the agenda is not too long or for smaller groups. However, it was also agreed that the ROP and ROC meetings for NFPA 72 should continue to be face-to-face. Item 10-9-6 Update on ITM Summit An overview of the ITM Summit activities was provided highlighting some of the significant points presented in the ITM Summit Meeting Minutes and Standards Council Summary. The primary objective of the summit was to come up with a plan outlining how to assure all aspects of end-to-end testing of fire safety systems is to be achieved while avoiding conflicts within the scopes of different systems/committees. Among the points presented was the concept that the scope and purpose of initial versus periodic inspection/testing may be different and the methods used to accomplish the two categories of inspection/testing may be better addressed in different ways. Another key point was the recognition that from a practical standpoint end-to-end testing would probably require an allowance to perform well-designed segmented testing as well as integrated end-to-end testing. One reason for this is that it may be detrimental or disruptive to repetitively operate interfaced equipment. Another reason is that coordination of qualified personnel or legal restrictions on which personnel are permitted to perform certain aspects of testing can be issues. It was recognized that there needs to be a means to keep track of segments of testing that is accomplished and segments that remain to be accomplished. There also needs to be a means to verify that components disconnected or bypassed to accomplish segmented testing are returned their proper in-service condition. As a part of the ITM summit discussions it was recognized that coordination of the interrelationship between different system/equipment standards was probably best achieved by having cross-representation on different committees. The TCC has official liaisons on the following committees: Tom Norton (NV) NFPA 25, INM-AAA, Inspection, Testing and Maintenance of Water

Based Systems Wayne Moore (NV) NFPA 101, SAF-AAC, Safety to Life [TCC] Shane Clary (NV Alt) NFPA 101, SAF-AAC, Safety to Life [TCC] It was noted that many other members of the TCC also serve on other technical committees. An impromptu survey was conducted of the TCC members present to identify their committee service affiliations. See attached list. It was pointed out that the final recommendation to the Standards Council still needs to be developed. This will likely require at least one more meeting (or teleconference) of key participants to consider and draft the final recommendations.

4

As an offshoot of TCC discussions on the ITM Summit, it was suggested that testing required for water flow switches should be investigated to try to reduce the frequency of actually flowing water required by both NFPA 72 and NFPA 25. Frequent testing by flowing water introduces air into the piping which can promote corrosion. A TCC task group was formed (Task Group on Sprinkler Water Flow) to pursue this. Task group members include Tom Norton (Chair), Jeff Moore and Jim Mundy. Item 10-9-7 Glossary of Terms Several categories of terminology were discussed by the TCC including: 1) Glossary of terms definitions in general 2) Terminology related to the meaning and use of different alarm signals (fire, CO, Security,

and others) along with their occasional designation as supervisory signals. 3) Terminology related to control locations, including Fire Command Center, Central

Control Point, Central Control Station, Emergency Control Center, Controls, and others.

4) Terminology related to emergency plans, including Exit Plan, Fire Safety Plan, Evacuation Plan, Relocation Plan and others

TCC task groups were appointed to review issues and develop proposals for these categories as follows: 1) Task Group on Glossary of Terms review terms in NFPA 72 and NFPA 720 for

correlation within these documents and for correlation with the NFPA Glossary of Terms (GOT). The task group should investigate the preferred and not preferred status and work with the Glossary of Terms Technical Advisory Committee to resolve concerns. Task group members include Frank Van Overmeiren (chair) and Jack McNamara. Additional task group members should include a member from each technical committee.

2) Task Group on Alarm, Supervisory and Trouble Signal Terminology review terms in NFPA 72 and NFPA 720 for correlation within the documents and with the GOT. In some cases alarm signals have been treated as supervisory signals in order to avoid unnecessary occupant notification. In addition issues have been raised recently concerning the different types of alarm signals and how they should be addressed in the code so that proper distinction and response is provided. Task group members include Andrew Berezowski (chair), Wayne Moore, Larry Shudak, Ray Grill, and Dave Klein. The two primary GOT Task Group members are also included.

3) Task Group on Control Locations Terminology - review terms in NFPA 72 and NFPA 720 for correlation within these documents and for correlation with the NFPA Glossary of Terms (GOT). Terminology should be consistent throughout the documents and clear distinctions should be made where similar terms are used for different control locations. Task group members include Doug Aiken (chair), Wayne Moore, and Jeff Knight.

4) Task Group on Emergency Plan Terminology - review terms in NFPA 72 and NFPA 720 for correlation within these documents and for correlation with the NFPA Glossary of Terms (GOT). Terminology should be consistent throughout the documents and clear distinctions should be made where similar terms are used for different plans. [Task group members have not yet been assigned.]

Item 10-9-8 AFAA Webinar

5

The TCC had a working lunch and viewed the AFAA Webinar on The Demise of the Dialer which provided a brief historical review of dialers (old tape dialers not code compliant), digital alarm communicator systems (DACS), radio systems and the current transition to IP communicators. The focus of the webinar was on DACS and how the public switched telephone network has changed from plain old telephone service (POTS) originally characterized by the use of copper conductors from end to end to networks that use packet switching (VoIP technology). The concept of reliability was introduced the speed with which we know the communications link is down including active systems (more liable) and passive systems (less reliable). Item 10-9-9 Communications Methods Following the AFAA webinar NFPA staff provided a short presentation on 2010 Code changes relative to supervising station communications methods. This presentation was primarily developed as a means to help AHJs understand what is required for DACS with regard to the use of non-traditional telephone service (managed facilities-based voice networks) and the separate requirements for IP communicators and radio systems. The requirements for these systems have been difficult to understand especially as they relate to number of channels required, requirements for secondary power for non-fire alarm system components and the pedigree requirements for commercial communication equipment used as a part of the communication pathway. These are areas that need to be made clearer to Code users. Recent reliability discussions have focused on secondary power supply capacity (24 hours versus 8 hours). It was suggested that performance for these system may need to focus more on availability than reliability. Perhaps newer techniques for system supervision (heart beat system) may need to be explored. It was also suggested that subject of communications reliability (availability) might be something that the Fire Protection Research Foundation could help with. Item 10-9-10 Committee Chair Reminders Several topics were discussed in anticipation of the upcoming pre-ROP and ROP meetings: 1) Chapters with multiple committee responsibility (such as Chapter 3, 10, and 12) are

becoming more common in the Code. Note that the committee acronym is shown at the end of paragraphs where the committee responsibility is different than the committee with primary responsibility. Committee chairs need to be mindful of this in dealing with proposals.

2) The TCC discussed the possibility of having a new chapter on Plans and Documentation. This was a concept first introduced with the reorganization of the code last cycle. There was general agreement that such as change may be helpful to users (especially AHJs) in recognizing responsibilities for system documentation. Each committee chair was requested to have a task group go through their respective chapter(s) and identify documentation requirements and prepare a separate section to address documentation requirements to be placed temporarily within their chapter. The TCC will subsequently address the placement of the various requirements within a single new chapter. It was anticipated that the new chapter be under the general purview of the Fundamentals

6

committee. As such it was requested that the Fundamentals committee develop an initial framework and front matter for the chapter. It was also suggested that since documentation requirements will be somewhat based on the type of system, a flowchart might be helpful to determine the extent of document needed.

3) The subject of committee chair training was addressed. NFPA is sponsoring extensive committee chair training to help chairs become more familiar with NFPA regulations and procedures (current and planned) and to help chairs become more effective in running meetings and organizing committee work. This training has already been attended by several chairs and has been very well received by participants. The TCC requested that all chairs attend this periodic training prior to the ROP meetings in January.

4) It was requested that each committee chair have a task group review Chapter 14 for requirements related to systems and equipment addressed by their chapter. The committee should make sure that equipment and features are adequately addressed and provide proposals to update relevant parts of Chapter 14 where needed to address both current and anticipated equipment and features. Chairs were reminded that consideration should be given to whether inspection and test methods should be addressed differently for acceptance testing versus periodic testing. In addition and as a consequence of related discussions it was suggested that ITM committee assign a task group to update Annex G.

Item 10-9-11 25-Year Pins No report was provided. Item 10-9-12 Review of NFPA 550 At previous TCC meeting it was suggested that there was a need to review NFPA 550 and provide update proposals. NFPA 550, Guide to Fire Safety Concepts Tree, is in the Fall 2011 cycle, the proposal closing date was May 28, 2010, and the Report on Proposals is expected to be out by December 22, 2010. A TCC task group was assigned to review the proposals and generate comments as needed. Task group members include Lynn Nielson (chair), Dan OConnor and Ken Dungan. Item 10-9-13 TCC Joint Task Group on Wiring No report was provided. The 2011 edition of NFPA 70, National Electrical Code, is at the end of the cycle. Item 10-9-14 New Business Several topics were addressed under new business: 1) The Fire Protection Research Foundation (FPRF) the midst of organizing a project to

provide guidance on messaging strategies for voice communications systems. The initial stage would be to do a literature review on the subject and hopefully provide some recommendations in time for incorporation on the next edition of NFPA 72. This work would be done by NIST (Erica Kuligowski), however funding has become an issue. Kathleen Almand has requested feedback on the funding issue. [It is noted that the funding issue was subsequently resolved as a research grant was approved from DHS.]

7

2) Lou Fiore indicated that some questions have been raised regarding the methods used to test and document the availability and performance of radio transmission paths especially when mesh networks are involved. Some work has been done with the Amateur Radio Relay League to find a means to resolve these concerns.

3) The concern was raised that the phrase listed for the purpose (see 10.3.1) may not be developed as fully as needed in some applications so that the intended requirement is clear. Committees should review their chapters for situations where additional clarification is warranted. The intended purpose needs to be made clear (listed for the purpose of what) and in some cases the code needs to be clearer about when listing is required.

4) Jim Mundy suggested that the NFPA 72 committees pay closer attention to the requirements in NFPA 170, Standard for Fire Safety and Emergency Symbols. Recently a task group of the committee (of which Jim is a member) proposed some revisions to fire alarm symbols used design documents. Jim encouraged NFPA 72 committees to review the changes and terminologies proposed for NFPA 170 (especially for correlation with NFPA 72) and provide comments accordingly. The comment closing deadline for NFPA 170 is March 4, 2011. [The proposal was subsequently forwarded to all NFPA 72 chairs.]

5) It was requested that each committee take a look at the structure of their chapter to see if improvements can be made in the organization and number of paragraphs. In some cases paragraph numbers are excessively long. Note that NFPA Manual of Style permits up to six digits but committees should strive to keep numbering shorter if possible. The intent here is to improve the flow of requirements and enhance the usability of the document. An outline of section/paragraph numbers with associated titles (up to four digits) was provided to each committee for their use in this effort.

6) The question was raised concerning the tracking of code adoptions for NFPA 72. It was requested that NFPA implement some form of tracking.

7) The need for cleanup and correlation of code requirements related to providing low frequency tones was identified. A task group was appointed to review the requirements and prepare proposals as needed. Task group members include Wayne Moore (or ECS designee) (chair), Vic Humm, Peter Larrimer, Ray Grill (or NAS designee).

Item 10-9-15 Adjournment The meeting was adjourned at approximately 4:00 PM. Respectfully Submitted Lee F. Richardson Staff Liaison and Secretary

8

NFPA 72 TCC Members Membership on Other Committees

Document Committee TCC Member NFPA 1 Uniform Fire Code FCC-AAA Fire Code Wayne Moore NFPA 3, Recommended Practice on Commissioning and Integrated Testing of Fire Protection and Life Safety Systems

CMF-AAA, Commissioning Fire Protection Systems

Tom Norton Roger Reiswig

NFPA 13, Standard for the Installation of Sprinkler Systems

AUT-AAC, Automatic Sprinkler Systems [TCC]

Ray Grill

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

INM-AAA, Inspection, Testing and Maintenance of Water Based Systems

Peter Larrimer Tom Norton*

NFPA 70, National Electrical Code NEC-AAC, National Electrical Code [TCC] NEC-P16, Code-Making Panel 16

Merton Bunker Jack McNamara

NFPA 76, Standard for the Fire Protection of Telecommunications Facilities

TEL-AAA, Telecommunications

Tom Norton Rodger Reiswig

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

AIC-AAA, Air Conditioning Merton Bunker Tom Hammerburg

NFPA 92, Standard for Smoke Management Systems

SMO-AAA, Smoke Management Systems Larry Shudak

NFPA 92A, Standard for Smoke-Control Systems Utilizing Barriers and Pressure Differences


NFPA 92B, Standard for Smoke Management Systems in Malls, Atria, and Large Spaces


NFPA 99, Standard for Health Care Facilities

HEA-FUN, Fundamentals Jack McNamara Frank Van Overmeiren

NFPA 101, Life Safety Code SAF-AAC, Safety to Life [TCC] SAF-HEA, Health Care Occupancies SAF-BSF, Building Service and Fire Protection Equipment SAF-FUN, Fundamentals SAF-DET, Detention and Correctional Occupancies

Shane Clary* Wayne Moore* Peter Larrimer Dan OConnor Bob Boyer Ray Grill Tom Hammerberg Peter Larrimer Rodger Reiswig Larry Shudak Tom Hammerberg Rodger Reiswig Jack McNamara

NFPA 101A, Guide on Alternative Approaches to Life Safety

SAF-ALS, Alternate Approaches to Life Safety Peter Larrimer

NFPA 170, Standard for Fire Safety and Emergency Symbols

FIS-AAA, Fire Safety and Emergency Symbols Jim Mundy

NFPA 551, Guide for the Evaluation of Fire Risk Assessments

FIR-AAA, Fire Risk Assessment Methods Rodger Reiswig

9

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

SIG-CAR, Carbon Monoxide Detection

Jeff Brooks Lou Fiore Jeff Knight Jim Mundy Tom Norton Rodger Reiswig

NFPA 730, Guide for Premises Security PMM-AAA, Premises Security John Fannin Lou Fiore Wayne Moore Tom Smith Rodger Reiswig

NFPA 731, Standard for the Installation of Electronic Premises Security Systems

PMM-AAA, Premises Security John Fannin Lou Fiore Wayne Moore Tom Smith Rodger Reiswig

NFPA 909, Code for the Protection of Cultural Resource Properties - Museums, Libraries, and Places of Worship

CUL-AAA Cultural Resources Wayne Moore Fred Leber

NFPA 914: Code for Fire Protection of Historic Structures

CUL-AAA Cultural Resources Fred Leber Wayne Moore

NFPA 1221, Standard for the Installation, Maintenance, and Use of Emergency Services Communications Systems

PUF-AAA, Public Emergency Service Communication

Doug Aiken Jeff Knight

NFPA 1600, Standard on Disaster/Emergency Management and Business Continuity Programs

EMB-AAA, Emergency Management and Business Continuity

John Fannin

ASME A17.1, Safety Code for Elevators and Escalators

Emergency Operations Committee Merton Bunker Bruce Fraser Tom Norton

* Official Signaling Systems Liaison

Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-1 Log #CP1 SIG-ECS

_______________________________________________________________________________________________Technical Committee on Emergency Communication Systems,

Review entire document to: 1) Update any extracted material by preparing separate proposals todo so, and 2) review and update references to other organizations documents, by preparing proposal(s) as required.

To conform to the NFPA Regulations Governing Committee Projects.

Affirmative: 261 Binkley, P.

_______________________________________________________________________________________________72-2 Log #CP2 SIG-FUN

_______________________________________________________________________________________________Technical Committee on Fundamentals of Fire Alarm and Signaling Systems,



The committee reviewed the extracted material, and referenced documents as requested.

Affirmative: 27 Negative: 11 McNamara, J.

MUNDY, JR., J.: Entire document is acceptable with exceptions noted in other voting comments.

1Printed on 3/18/2011

Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-2a Log #CP210 SIG-FUN


Create a new 1.6 and Annex A.1.6.1 to read as follows:1.6 Fire Risk Analysis.1.6.1* A fire risk analysis shall be permitted to be used to determine the protection of the fire alarm and signaling

system based on its location, building features, and anticipated risk tolerances where specifically permitted by this Code.1.6.2 The fire risk analysis conducted in Section 1.6.1 shall be documented.A.1.6.1 See NFPA 551, Guide for the Evaluation of Fire Risk Assessments, for additional guidance.Renumber accordingly.

The addition of this information will address the use of risk analysis throughout the code.


BEREZOWSKI, A.: We disagree with the substantiation. Risk analysis is only referred to in connection with ECS andshould remain under the purview of ECS.BONIFAS, R.: Introduction into the code of a "risk analysis" is a whole new concept that exposes the entire code

process to undefined interpretations of the code. It would be followed by limitations as to who is qualified to make such"risk analysis". This is a "slippery slope" that would result in endless challenges of system design and code complianceby a "battle of conflicting experts" as to the validity of the "risk analysis".CLARY, S.: I do not agree that a risk analysis should be performed for the protection of a control unit. The expense of

performing the risk analysis would in most cases be more than the cost of installing the detection device. Is the next stepto require a risk analysis for the installation of a manual or automatic fire detection system?MUNDY, JR., J.: Acceptable means of risk analysis is only acceptable when it utilizes the performance criteria for

design as detailed in Chapters 17, 18, 24, Appendices A & B. Language proposed by the Technical Committee appearsto be a substitution as alternative language permitting removal of the exception under the proposed exception undersection 10.15. All analyses should conform totally with the Chapters and Appendices cited herein-before


Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-2a Log #CP210 SIG-FUN


Create a new 1.6 and Annex A.1.6.1 to read as follows:1.6 Fire Risk Analysis.1.6.1* A fire risk analysis shall be permitted to be used to determine the protection of the fire alarm and signaling

system based on its location, building features, and anticipated risk tolerances where specifically permitted by this Code.1.6.2 The fire risk analysis conducted in Section 1.6.1 shall be documented.A.1.6.1 See NFPA 551, Guide for the Evaluation of Fire Risk Assessments, for additional guidance.Renumber accordingly.

The addition of this information will address the use of risk analysis throughout the code.


BEREZOWSKI, A.: We disagree with the substantiation. Risk analysis is only referred to in connection with ECS andshould remain under the purview of ECS.

BONIFAS, R.: Introduction into the code of a "risk analysis" is a whole new concept that exposes the entire codeprocess to undefined interpretations of the code. It would be followed by limitations as to who is qualified to make such"risk analysis". This is a "slippery slope" that would result in endless challenges of system design and code complianceby a "battle of conflicting experts" as to the validity of the "risk analysis".

CLARY, S.: I do not agree that a risk analysis should be performed for the protection of a control unit. The expense ofperforming the risk analysis would in most cases be more than the cost of installing the detection device. Is the next stepto require a risk analysis for the installation of a manual or automatic fire detection system?

MUNDY, JR., J.: Acceptable means of risk analysis is only acceptable when it utilizes the performance criteria fordesign as detailed in Chapters 17, 18, 24, Appendices A & B. Language proposed by the Technical Committee appearsto be a substitution as alternative language permitting removal of the exception under the proposed exception undersection 10.15. All analyses should conform totally with the Chapters and Appendices cited herein-before

_______________________________________________________________________________________________72-3 Log #CP3 SIG-HOU

_______________________________________________________________________________________________Technical Committee on Single- and Multiple-Station Alarms and Household Fire Alarm Systems,



Affirmative: 243 Cantrell, D., Dantzler, D., Pecht, F.


Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-4 Log #CP4 SIG-IDS

_______________________________________________________________________________________________Technical Committee on Initiating Devices for Fire Alarm and Signaling Systems,



In section 2.2 update the references as follows:Revise the edition date for NFPA 10 to become 2010.Revise the edition date for NFPA 92A to become 2009.Revise the edition date for NFPA 92B to become 2009.In Section B.6.5 update the references as follows:

For reference (22) change "19th" to "20th" edition and "2003" to "2008"For reference (35) change "2006" to "2009"For reference (41) change "Third" to "Forth" edition and "2002" to "2008"For reference (50) change "2006" to "2009"For reference (51) change "2005" to "2010"For reference (52) change "2007" to "2010"In Section H.1.2.15 update the references the same as specified above for B.6.5

1) No extracts were found that were the responsibility of the SIG-IDS Committee.2) References have been updated as shown in the committee action text.

Affirmative: 242 Aho, W., Marrion, C.

_______________________________________________________________________________________________72-5 Log #CP5 SIG-NAS

_______________________________________________________________________________________________Technical Committee on Notification Appliances for Fire Alarm and Signaling Systems,



Affirmative: 22


Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-6 Log #CP6 SIG-PRO

_______________________________________________________________________________________________Technical Committee on Protected Premises Fire Alarm and Signaling Systems,



Revise the follow sections to read as follows:2.2 NFPA StandardsNFPA 601, 2005 2010 edition.

, 2008 2011 edition.2.3.1 ANSI PublicationsANSI/ASME A17.1ab/CSA B44ab, , 2008 2009.

Separate outputs from the fire alarm systems to the elevator controller(s) shall be provided to implementelevator Phase I Emergency Recall Operation in accordance with Section 2.27 of ANSI/ASME A17.1ab/CSA B44ab,

, as required in 21.3.12.1 through 21.3.12.3.The required status indicator shall display an illuminated green light and the message Elevators available for

occupant evacuation while the elevators are operating under normal service and the fire alarm system is in an alarmcondition, but before Phase I Emergency Recall Operation in accordance with ANSI/ASME A.17.1ab/CSA B44ab,

, has been initiated.The required status indicator shall display an illuminated red light and the message Elevators out of service,

use exit stairs once the elevators are under Phase I or Phase II operation in accordance with ANSI/ASMEA17.1ab/CSA B44ab, .

The terms , , , and are defined in ,, and ANSI/ASME A17.1ab/CSA B44b.

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 of theelevator, as well as the delivery of passengers to a safe lobby location. Where ANSI/ASME A17.1ab/CSA B44ab,

, specifies the use of smoke detectors, these devices are expected to providethe earliest response to situations that would require Phase I Emergency Recall Operations.The use of other automatic fire detection is only intended where smoke detection would not be appropriate due to the

environment. Where ambient conditions prohibit the installation of smoke detectors, the selection and location of otherautomatic fire detection should be evaluated to ensurethe best response is achieved. When heat detectors are used, consideration should be given to both detectortemperature and time lag characteristics. The consideration of a low temperature rating alone might not provide theearliest response.

Where initiating devices are located in the elevator hoistway at or below the lowest level of recall,ANSI/ASME A17.1 ab /CSA B44 ab, , requires that the elevator be sent to theupper recall level. Note that the lowest level of recall could be the designated level or alternate level as determinedby the local authority for the particular installation. Also note that the elevator hoistway, as defined in ASME A.17.1,includes the elevator pit.

ANSI/ASME A17.1 ab /CSA B44 ab, , requires differentiationbetween separate hoistways that share a common elevator machine room. For instance, in a situation where there ismore than one single hoistway sharing the same elevator machine room, a separate signal must be derived from eachhoistway.H1.1 NFPA Publications

, 2008 2011 edition.

ANSI/ASME A17.1 ab /CSA B44 ab, , 2008.

These documents were revised to reflect the most current editions of each.

Affirmative: 282 Waller, B., Wenzel, Jr., F.


Report on Proposals June 2012 NFPA 72

_______________________________________________________________________________________________72-7 Log #CP7 SIG-PRS

_______________________________________________________________________________________________Technical Committee on Public Emergency Reporting Systems,



Add "IMSA Official Wire and Cable Specifications, 1998" to Chapter 2The committee reviewed Chapter 2 and Annex H for referenced documents and added one

reference. Extracted material was reviewed with no changes.

Affirmative: 193 Allen, G., Dupuis, R., Fisher, E.

_______________________________________________________________________________________________72-8 Log #CP8 SIG-SSS

_______________________________________________________________________________________________Technical Committee on Supervising Station Fire Alarm and Signaling Systems,



Update all referenced NFPA documents associated with Chapter 26 to the latest edition.There are no extracts related to this committee's responsibility. The 2008 edition of UL 827 is

currently the latest edition.

Affirmative: 251 Colby, S.


Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-9a Log #574 SIG-PRO

_______________________________________________________________________________________________Thomas P. Hammerberg, Automatic Fire Alarm Association, Inc.

Add new text to read as follows:2.2 NFPA Publications.NFPA 750, Standard For Water Mist Fire Protection Systems, 2010 Edition.

Since Water Mist fire suppression systems have been approved and installed in a wide range ofsprinkler applications globally and their alarm and detection devices and installation must adhere to NFPA 72requirements, the NFPA 750 Standard on Water Mist Fire Protection Systems should be included in NFPA 72 as aReferenced Publication. NFPA 72 is referenced in Chapter 2 of NFPA 750 now and they should complement oneanother as reference documents.

Also, since there is a generic reference in NFPA 72 to Fire Suppression System Other Than Sprinklers in sectionssuch as 23.8.5.7 and 23.8.5.8 and Water Mist Systems may satisfy that requirement on a job, NFPA 750 should beincluded as a document of reference.

The committee understands other proposals may add a reference to NFPA 750. The TCC isrequested to review this proposal to determine if a reference is necessary. This committee is accepting this contingentupon acceptance of other proposals.

Affirmative: 282 Waller, B., Wenzel, Jr., F.

_______________________________________________________________________________________________72-9b Log #CP208 SIG-FUN


Add to existing code text 2.2:NFPA 170, .

See the action taken on Proposal 72-154a (Log #582).


FRABLE, D.: See my statement on Proposal 72-154a.HANCOCK, J.: NFPA 170 is currently under a significant revision of symbols per a SIG-FUN committee member that

serves on the NFPA 170 committee. The current symbols used in the standard are not widely used for fire alarmsystem designs in all areas. The revised symbols included in the next edition of NFPA 170 were not provided forSIG-FUN review. In addition, the basis for for standardized symbology has not been established. Standardizedsymbology is already being used in some companies and locations, and the requirement to change symbology wouldnot add value.


Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-10 Log #20 SIG-HOU

_______________________________________________________________________________________________John F. Bender, Underwriters Laboratories Inc.

Update the references to the following ANSI Publications:ANSI/UL 217, , 2006, revised 2008 2010. (SIG-HOU)ANSI/UL 268, , 2006 2009. (SIG-HOU)ANSI/UL 864, , 2003, revised 2006 2010.

(SIG-ECS, SIG-HOU)ANSI/UL 985, , 2000, revised 2003 2008. (SIG-HOU)ANSI/UL 2017, , 2000 2008, revised 2004 2009.

(SIG-ECS)Update referenced standards to the most recent revisions and add ANSI approval designation to

ANSI/UL 2017. The revisions to UL 217 include clarification of Smoldering Smoke Test wood stick amount andorientation new surge tests, a reference to NFPA 302 in Scope and addition of lower beam limits for flammable liquidfuel fire. UL 268 is the first publication of the common UL and ULC standard for Smoke Detectors for Fire AlarmSystems. National differences are identified in the new standard. UL 864 has been revised to include Fail-Safe FireRelease Devices. UL 985 reflects the recent reaffirmation as an American National Standard. The revisions of ANSI/UL2017 are to address universal upkeep of UL Standards for Safety. These revisions are considered to benon-substantive.


_______________________________________________________________________________________________72-11 Log #20b SIG-ECS

_______________________________________________________________________________________________John F. Bender, Underwriters Laboratories Inc.

Update the references to the following ANSI Publications:ANSI/UL 217, , 2006, revised 2008 2010. (SIG-HOU)ANSI/UL 268, , 2006 2009. (SIG-HOU)ANSI/UL 864, , 2003, revised 2006 2010.

(SIG-ECS, SIG-HOU)ANSI/UL 985, , 2000, revised 2003 2008. (SIG-HOU)ANSI/UL 2017, , 2000 2008, revised 2004 2009.

(SIG-ECS)Update referenced standards to the most recent revisions and add ANSI approval designation to

ANSI/UL 2017. The revisions to UL 217 include clarification of Smoldering Smoke Test wood stick amount andorientation new surge tests, a reference to NFPA 302 in Scope and addition of lower beam limits for flammable liquidfuel fire. UL 268 is the first publication of the common UL and ULC standard for Smoke Detectors for Fire AlarmSystems. National differences are identified in the new standard. UL 864 has been revised to include Fail-Safe FireRelease Devices. UL 985 reflects the recent reaffirmation as an American National Standard. The revisions of ANSI/UL2017 are to address universal upkeep of UL Standards for Safety. These revisions are considered to benon-substantive.

Affirmative: 261 Binkley, P.


Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-11a Log #CP703 SIG-PRS


Extract the definition of emergency response facility (ERF) from NFPA 1221 Section 3.3.36 and itsassociated annex material.

The definition will support the use of the term in the document.


_______________________________________________________________________________________________72-11b Log #CP707 SIG-PRS


Revise definition titles as follows:3.3.8.1 Auxiliary Alarm Box3.3.8.4 Master Alarm BoxCreate new definitions as follows:Wireless Network. The method of communications used in a Public Emergency Alarm Reporting System when it

consists of a wireless type of communications infrastructure. (PRS)Wired Network. The method of communications used in a Public Emergency Alarm Reporting System when it

consists of a wired type of communications infrastructure. (PRS)

The revisions to the titles are to be consistent with the terms used in Chapter 27. The new definitionsreflect the use of the terms used in Chapter 27



Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-12 Log #3 SIG-SSS

_______________________________________________________________________________________________

Wayne D. Moore, Hughes Associates, Inc.

A physical facilities-based network capable oftransmitting real time signals with formats unchanged that is managed, operated, and maintained by the service providerto ensure service quality and reliability from the subscriber location to public switched telephone network (PSTN)interconnection points or other MFVN peer networks.

Managed Facilities-based Voice Network service isfunctionally equivalent to traditional PSTN-based services provided by authorized common carriers (public utilitytelephone companies) with respect to dialing, dial plan, call completion, carriage of signals and protocols, and loopvoltage treatment and provides all of the following features:

(1) A loop start telephone circuit service interface(2) Pathway reliability that is assured by proactive management, operation, and maintenance by the MFVN

provider(3) 8 hours of standby power supply capacity for MFVN communications equipment either located at the protected

premises or field deployed. Industry standards followed by the authorized common carriers (public utility telephonecompanies), and the other communications service providers that operate MFVNs, specifically engineer the selection ofthe size of the batteries, or other permanently located standby power source, in order to provide 8 hours of standbypower with a reasonable degree of accuracy. Of course, over time, abnormal ambient conditions and battery aging canalways have a potentially adverse effect on battery capacity. The MFVN field-deployed equipment typically monitors thecondition of the standby battery and signals potential battery failure to permit the communications service provider totake appropriate action.

(4) 24 hours of standby power supply capacity for MFVN communications equipment located at the communicationservice providers central office.

(5) Installation of network equipment at the protected premises with safeguards to prevent unauthorized access tothe equipment and its connections

When providing telephone service to a new customer, MFVN providers give notice to the telephone service subscriberof the need to have any connected alarm system tested by authorized fire alarm service personnel in accordance withChapter 14 to make certain that all signal transmission features have remained operational. These features include theproper functioning of line seizure and the successful transmission of signals to the supervising station. In this way, theMFVN providers assist their new customers in complying with a testing procedure similar to that outlined in 26.2.3 forchanges to providers of supervising station service.

The evolution of the deployment of telephone service has moved beyond the sole use of metallic conductorsconnecting a telephone subscribers premises with the nearest telephone service providers control and routing point(Wire Center). In the last 25 years, telephone service providers have introduced a variety of technologies to transportmultiple, simultaneous telephone calls over shared communications pathways. In order to facilitate the furtherdevelopment of the modernization of the telephone network, the authorized common carriers (public utility telephonecompanies) have transitioned their equipment into a Managed Facilities-based Voice Network (MFVN) capable ofproviding a variety of communications services in addition to the provision of traditional telephone service.

Similarly, the evolution of digital communications technology has permitted entities other than the authorized commoncarriers (public utility telephone companies) to deploy robust communications networks and offer a variety ofcommunications services, including telephone service.

These alternate service providers fall into two broad categories. The first category includes those entities which haveemulated the Managed Facilities-based Voice Network (MFVN) provided by the authorized common carriers. Thesecond category includes those entities that offer telephone service using means that do not offer the rigorous qualityassurance, operational stability, and consistent features provided by a Managed Facilities-based Voice Network.

The Code intends to only recognize the use of the telephone network transmission of alarm, supervisory, trouble, andother emergency signals by means of Managed Facilities-based Voice Networks.

For example, the Code intends to permit an MFVN to provide facilities-based telephone (voice) service that interfaceswith the premises fire alarm or emergency signal control unit through a digital alarm communicator transmitter (DACT)


Report on Proposals June 2012 NFPA 72using a loop start telephone circuit and signaling protocols fully compatible with and equivalent to those used in publicswitched telephone networks. The loop start telephone circuit and associated signaling can be provided throughtraditional copper wire telephone service (POTSplain old telephone service) or by means of equipment that emulatesthe loop start telephone circuit and associated signaling and then transmits the signals over a pathway using packetswitched (IP) networks or other communications methods that are part of a Managed Facilities-based Voice Network.

Providers of Managed Facilities-based Voice Networks have disaster recovery plans to address both individualcustomer outages and wide spread events such as tornados, ice storms or other natural disasters, which includespecific network power restoration procedures equivalent to those of traditional landline telephone services.

. An assembly of communications facilities and central office equipmentoperated jointly by authorized service providers that provides the general public with the ability to establish transmissionchannels via discrete dialing. (SIG-SSS)

A loop start telephone circuit is an analog telephone circuit that supportsLoop Start Signaling as specified in either Telcordia

or in Telcordia .

An assembly of communications equipment and telephoneservice providers that utilize Managed Facilities-based Voice Networks (MFVN) to provide the general public with theability to establish communications channels via discrete dialing codes. (SIG-SSS)

A managed facilities voice network (MFVN) shall be permitted to be connected to a DACT when thefollowing conditions are met:

(1)*The DACT shall be connected and perform as required in 26.6.3.2.1.3.(2) The power supply battery backup of all MFVN equipment shall be provided with 8 hours of secondary power supply

capacity.(3) The DACT test signal shall be transmitted at least monthly.(4) The managed facilities voice network shall meet the following conditions:(a) Manage and maintain their network to ensure end-to end service quality and reliability.(b) Provide a service that is functionally equivalent to PSTN-based services with respect to dialing, dial plan, call

completion, carriage of alarm signals and protocols, and loop voltage treatment.(c) Provide real time transmission of voice signals and deliver alarm formats unchanged.(d) Preserve primary line seizure for alarm signals transmission.(e) Have disaster recovery plans to address both individual customer outages and wide spread events such as

tornados, ice storms or other natural disasters, which include specific network power restoration procedures equivalentto those of traditional landline telephone services.

The Technical Correlating Committee for the Protection of Life and Property has prepared thisTentative Interim Amendment (TIA) as a means of last resort to correlate differing actions and resulting differingrequirements between Chapter 26 and Chapter 29 of the proposed NFPA 72-2010, National Fire Alarm and SignalingCode.

The evolution of technology, equipment, processes, and procedures to provide subscriber telephone service toindustrial, commercial, and residential customers has fundamentally changed. NFPA 72 and its predecessor documentshave long treated the telephone infrastructure as a black box. Appropriately, NFPA 72 has never attempted topromulgate regulations for an industry over which it has no reasonable way in which to exercise control or verifycompliance. Rather, NFPA 72 has accepted the operational integrity and functional reliability of the telephonecommunications infrastructure as a transmission pathway for fire alarm, supervisory, trouble, and other emergencysignals.

Since the adoption of the 2007 edition of NFPA 72, the deployment of subscriber telephone service by an increasingnumber of service providers as alternatives to the service offerings of the authorized common carriers (public utilitytelephone companies) has promoted an increasing number of inquiries from Authorities Having Jurisdiction (AHJs) as tothe acceptability of such alternate service for signal transmission.

Accordingly, interested parties submitted public proposals and public comments during the 2010 revision cycle ofNFPA 72. These proposals and comments were submitted to Chapter 26, Supervising Station Alarm Systems, and toChapter 29, Single and Multiple Station Alarms and Household Fire Alarm Systems. Each Technical Committeeresponded differently to these public proposals and public comments.

The Technical Committee for Chapter 26 rejected language that would recognize the equivalency of certain alternatetelephone service technology. The Technical Committee for Chapter 29 accepted the equivalency of certain alternate


Report on Proposals June 2012 NFPA 72telephone service technology.

In attempting to correlate the differing actions by the Technical Committees for the two chapters, the TechnicalCorrelating Committee determined that the underlying issues would require greater study and a more in-depth analysisthan could be reasonably performed during the meetings of the Technical Correlating Committee. The TechnicalCorrelating Committee appointed a Task Group with a broad and balanced representation from the authorized commoncarriers (public utility telephone companies), the alternate service providers, and from the Chapter 26 TechnicalCommittee and Technical Correlating Committee. The result of the task groups work indicated that Paragraph29.7.8.1.5 added in Chapter 29 by Comment 72-440 needed to be deleted. The Chapter 29 TC Chair was then advisedof the task groups work and understands the need for correlation.

This Task Group has completed its work and has developed this TIA.During the deliberations of the Task Group, certain key information regarding subscriber telephone service has

emerged. In writing text for inclusion in Annex A, the Task Group has attempted to summarize this information.Because the impact of the burgeoning number of alternate service providers for subscriber telephone service will

continue to grow, the Technical Correlating Committee and its Task Group believe that the adoption of this TIA is of anemergency nature in accordance with 5.2(b) and 5.2(f) of NFPA Regulations Governing Committee Projects. This mattersimply cannot wait for resolution during the next revision cycle of NFPA 72. Non-traditional voice services were notthoroughly and appropriately referenced in the most recent revision process. This will result in an adverse impact onprotected individuals, businesses, as well as alarm and voice service providers. Currently AHJs are applying differentstandards in different jurisdictions and for different service providers. Specific guidance from NFPA is critically needed.

Affirmative: 23 Negative: 1 Abstain: 11 Colby, S.

MARTS, R.: The FCC does not require 8 hours.

PAPIER, I.: Digital communication technology was grudgingly by the NFPA 71 TC during the 1980s based on acomplete package of attributes that were part of the regulated PSTN. It was understood by the committee thatacceptance was predicated on all elements being present. Unfortunately deregulation has resulted in many of theseelements not being there. The proper response should have been disallowing DACT. Instead the elimination of theseelements was used as an excuse to accept MFVN. I have yet to see a study of MFVN similar then what was done forPOTS to be accepted by the NFPA 71 TC.


Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-13 Log #3a SIG-HOU

_______________________________________________________________________________________________

Wayne D. Moore, Hughes Associates, Inc.

A physical facilities-based network capable oftransmitting real time signals with formats unchanged that is managed, operated, and maintained by the service providerto ensure service quality and reliability from the subscriber location to public switched telephone network (PSTN)interconnection points or other MFVN peer networks.

Managed Facilities-based Voice Network service isfunctionally equivalent to traditional PSTN-based services provided by authorized common carriers (public utilitytelephone companies) with respect to dialing, dial plan, call completion, carriage of signals and protocols, and loopvoltage treatment and provides all of the following features:

(1) A loop start telephone circuit service interface(2) Pathway reliability that is assured by proactive management, operation, and maintenance by the MFVN

provider(3) 8 hours of standby power supply capacity for MFVN communications equipment either located at the protected

premises or field deployed. Industry standards followed by the authorized common carriers (public utility telephonecompanies), and the other communications service providers that operate MFVNs, specifically engineer the selection ofthe size of the batteries, or other permanently located standby power source, in order to provide 8 hours of standbypower with a reasonable degree of accuracy. Of course, over time, abnormal ambient conditions and battery aging canalways have a potentially adverse effect on battery capacity. The MFVN field-deployed equipment typically monitors thecondition of the standby battery and signals potential battery failure to permit the communications service provider totake appropriate action.

(4) 24 hours of standby power supply capacity for MFVN communications equipment located at the communicationservice providers central office.

(5) Installation of network equipment at the protected premises with safeguards to prevent unauthorized access tothe equipment and its connections

When providing telephone service to a new customer, MFVN providers give notice to the telephone service subscriberof the need to have any connected alarm system tested by authorized fire alarm service personnel in accordance withChapter 14 to make certain that all signal transmission features have remained operational. These features include theproper functioning of line seizure and the successful transmission of signals to the supervising station. In this way, theMFVN providers assist their new customers in complying with a testing procedure similar to that outlined in 26.2.3 forchanges to providers of supervising station service.

The evolution of the deployment of telephone service has moved beyond the sole use of metallic conductorsconnecting a telephone subscribers premises with the nearest telephone service providers control and routing point(Wire Center). In the last 25 years, telephone service providers have introduced a variety of technologies to transportmultiple, simultaneous telephone calls over shared communications pathways. In order to facilitate the furtherdevelopment of the modernization of the telephone network, the authorized common carriers (public utility telephonecompanies) have transitioned their equipment into a Managed Facilities-based Voice Network (MFVN) capable ofproviding a variety of communications services in addition to the provision of traditional telephone service.

Similarly, the evolution of digital communications technology has permitted entities other than the authorized commoncarriers (public utility telephone companies) to deploy robust communications networks and offer a variety ofcommunications services, including telephone service.

These alternate service providers fall into two broad categories. The first category includes those entities which haveemulated the Managed Facilities-based Voice Network (MFVN) provided by the authorized common carriers. Thesecond category includes those entities that offer telephone service using means that do not offer the rigorous qualityassurance, operational stability, and consistent features provided by a Managed Facilities-based Voice Network.

The Code intends to only recognize the use of the telephone network transmission of alarm, supervisory, trouble, andother emergency signals by means of Managed Facilities-based Voice Networks.

For example, the Code intends to permit an MFVN to provide facilities-based telephone (voice) service that interfaceswith the premises fire alarm or emergency signal control unit through a digital alarm communicator transmitter (DACT)


Report on Proposals June 2012 NFPA 72using a loop start telephone circuit and signaling protocols fully compatible with and equivalent to those used in publicswitched telephone networks. The loop start telephone circuit and associated signaling can be provided throughtraditional copper wire telephone service (POTSplain old telephone service) or by means of equipment that emulatesthe loop start telephone circuit and associated signaling and then transmits the signals over a pathway using packetswitched (IP) networks or other communications methods that are part of a Managed Facilities-based Voice Network.

Providers of Managed Facilities-based Voice Networks have disaster recovery plans to address both individualcustomer outages and wide spread events such as tornados, ice storms or other natural disasters, which includespecific network power restoration procedures equivalent to those of traditional landline telephone services.

. An assembly of communications facilities and central office equipmentoperated jointly by authorized service providers that provides the general public with the ability to establish transmissionchannels via discrete dialing. (SIG-SSS)

A loop start telephone circuit is an analog telephone circuit that supportsLoop Start Signaling as specified in either Telcordia

or in Telcordia .

An assembly of communications equipment and telephoneservice providers that utilize Managed Facilities-based Voice Networks (MFVN) to provide the general public with theability to establish communications channels via discrete dialing codes. (SIG-SSS)

A managed facilities voice network (MFVN) shall be permitted to be connected to a DACT when thefollowing conditions are met:

(1)*The DACT shall be connected and perform as required in 26.6.3.2.1.3.(2) The power supply battery backup of all MFVN equipment shall be provided with 8 hours of secondary power supply

capacity.(3) The DACT test signal shall be transmitted at least monthly.(4) The managed facilities voice network shall meet the following conditions:(a) Manage and maintain their network to ensure end-to end service quality and reliability.(b) Provide a service that is functionally equivalent to PSTN-based services with respect to dialing, dial plan, call

completion, carriage of alarm signals and protocols, and loop voltage treatment.(c) Provide real time transmission of voice signals and deliver alarm formats unchanged.(d) Preserve primary line seizure for alarm signals transmission.(e) Have disaster recovery plans to address both individual customer outages and wide spread events such as

tornados, ice storms or other natural disasters, which include specific network power restoration procedures equivalentto those of traditional landline telephone services.

The Technical Correlating Committee for the Protection of Life and Property has prepared thisTentative Interim Amendment (TIA) as a means of last resort to correlate differing actions and resulting differingrequirements between Chapter 26 and Chapter 29 of the proposed NFPA 72-2010, National Fire Alarm and SignalingCode.

The evolution of technology, equipment, processes, and procedures to provide subscriber telephone service toindustrial, commercial, and residential customers has fundamentally changed. NFPA 72 and its predecessor documentshave long treated the telephone infrastructure as a black box. Appropriately, NFPA 72 has never attempted topromulgate regulations for an industry over which it has no reasonable way in which to exercise control or verifycompliance. Rather, NFPA 72 has accepted the operational integrity and functional reliability of the telephonecommunications infrastructure as a transmission pathway for fire alarm, supervisory, trouble, and other emergencysignals.

Since the adoption of the 2007 edition of NFPA 72, the deployment of subscriber telephone service by an increasingnumber of service providers as alternatives to the service offerings of the authorized common carriers (public utilitytelephone companies) has promoted an increasing number of inquiries from Authorities Having Jurisdiction (AHJs) as tothe acceptability of such alternate service for signal transmission.

Accordingly, interested parties submitted public proposals and public comments during the 2010 revision cycle ofNFPA 72. These proposals and comments were submitted to Chapter 26, Supervising Station Alarm Systems, and toChapter 29, Single and Multiple Station Alarms and Household Fire Alarm Systems. Each Technical Committeeresponded differently to these public proposals and public comments.

The Technical Committee for Chapter 26 rejected language that would recognize the equivalency of certain alternatetelephone service technology. The Technical Committee for Chapter 29 accepted the equivalency of certain alternate


Report on Proposals June 2012 NFPA 72telephone service technology.

In attempting to correlate the differing actions by the Technical Committees for the two chapters, the TechnicalCorrelating Committee determined that the underlying issues would require greater study and a more in-depth analysisthan could be reasonably performed during the meetings of the Technical Correlating Committee. The TechnicalCorrelating Committee appointed a Task Group with a broad and balanced representation from the authorized commoncarriers (public utility telephone companies), the alternate service providers, and from the Chapter 26 TechnicalCommittee and Technical Correlating Committee. The result of the task groups work indicated that Paragraph29.7.8.1.5 added in Chapter 29 by Comment 72-440 needed to be deleted. The Chapter 29 TC Chair was then advisedof the task groups work and understands the need for correlation.

This Task Group has completed its work and has developed this TIA.During the deliberations of the Task Group, certain key information regarding subscriber telephone service has

emerged. In writing text for inclusion in Annex A, the Task Group has attempted to summarize this information.Because the impact of the burgeoning number of alternate service providers for subscriber telephone service will

continue to grow, the Technical Correlating Committee and its Task Group believe that the adoption of this TIA is of anemergency nature in accordance with 5.2(b) and 5.2(f) of NFPA Regulations Governing Committee Projects. This mattersimply cannot wait for resolution during the next revision cycle of NFPA 72. Non-traditional voice services were notthoroughly and appropriately referenced in the most recent revision process. This will result in an adverse impact onprotected individuals, businesses, as well as alarm and voice service providers. Currently AHJs are applying differentstandards in different jurisdictions and for different service providers. Specific guidance from NFPA is critically needed.


_______________________________________________________________________________________________72-13a Log #CP902 SIG-TMS

_______________________________________________________________________________________________Technical Committee on Testing and Maintenance of Fire Alarm and Signaling Systems,

Add a new definition and associated annex material as follows:Published installation and operating documentation provided for each

product or component. The documentation includes directions and necessary information for the intended installation,maintenance, and operation of the product or component. (SIG-TMS)

A.3.3.x Manufacturers applicable documentation may be subject to revision.

The term "manufacturer's published instructions" is used in a number of requirements without beingdefined. The recommendation defines what is covered by this term and provides annex material to support thedefinition.

Affirmative: 272 Harrod, P., Sheets, R.

HURST, JR., H.: Manufacturer's Instructions typically include product specifications and the agency listings.Consideration should be given to the addition of this documentation as part of the definition.


Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-14 Log #38 SIG-FUN

_______________________________________________________________________________________________William K. Hopple, Hopple & Company / Rep. California Automatic Fire Alarm Association

Add the following three extracted definitions from NFPA 70, 2011 into NFPA 72, Chapter 3, Section3.3 General Definitions and renumber Section 3.3 as needed.

Accessible (as applied to equipment). Admitting close approach; not guarded by locked doors, elevation, or othereffective means. [70:Article 100]

Accessible (as applied to wiring methods). Capable of being removed or exposed without damaging the buildingstructure or finish or not permanently closed in by the structure or finish of the building. [70:Article 100]

Accessible, Readily (Readily Accessible). Capable of being reached quickly for operation, renewal, or inspectionswithout requiring those to whom ready access is requisite to climb over or remove obstacles or to resort to portableladders, and so forth. [70:Article 100]

NFPA 72 uses the term "accessible" and "readily accessible" numerous occasions but it is not definedas it relates to equipment and wiring methods and immediate access for operations. I believe it is appropriate to provideextracted definitions for several reasons: (1) to provide proper guidance of the intent, and (2) to provide the intent withina sole-source document. Authorities Having Jurisdiction (AHJ) would not have to carry "other" documents dealing with"accessible" elements of Fire Alarm Systems.

Requests for interpretations or proposed revisions of the 3 proposed definitions should be referred to the committeeresponsible for the source document. In this case, NFPA 70, CMP 1.

Affirmative: 281 McNamara, J.


Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-15 Log #39 SIG-PRO

_______________________________________________________________________________________________Anthony J. Capowski, Tyco Safety Products

Add new text to read as follows:3.3.xx Either a means of providing power or a connection between locations (see 3.3.174).

This proposal is the output of the task group on Wiring established at the SIG-PRO pre-ROP Meeting.The wiring task group was asked to look at the terms circuit and path and to harmonize them. The term circuit is usedover 800 times in the text of NFPA 72. Some of that use is superseded by the term path and some is not. Otherusage (e.g. Signaling Line Circuit) could be switched to path, but would result in a confusing change in nomenclaturethroughout the document. The easiest resolution to this is to define circuit in terms of path so that the terms can beused relatively interchangeably. The exception to this are circuits that provide power. This results in the first part of thedefinition.

The term circuit does appear in the NFPA Glossary of Terms, as defined in NFPA 1221, Standard for the Installation,Maintenance, and Use of Emergency Services Communications System). There it is defined as The conductor, orradio channel, and associated equipment that are used to perform a specific function in connection with an alarmsystem. This definition cannot be used here, as we are trying toharmonize with path, and because it does not considerpower supply circuits.

Affirmative: 27 Negative: 12 Waller, B., Wenzel, Jr., F.

NOVAK, J.: This proposal should be rejected. Circuit is a commonly used and accepted term. NFPA 70, the NationalElectrical Code has never defined the term circuit for that reason. Section 3.1 of the Code states thatMerriam-Webster's Collegiate Dictionary, 11th Edition, shall be the source for ordinarily accepted meanings within thecontext in which they are used when not defined by the Code. The definition found in the dictionary is virtually identicalto the proposed text. It is defined by the dictionary as "the complete path of an electric current including usually thesource of electric energy" and "a two-way communication path between points." The proposed definition does not addadditional clarity to the concept, therefore making this unnecessary.


Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-16 Log #436 SIG-FUN

_______________________________________________________________________________________________Robert P. Schifiliti, R. P. Schifiliti Associates, Inc.

This proposal delete section 10.19 in its entirety, revises 14.2.1.2, adds new definitions and adds anew .It is proposed that the definitions and the new chapter be the responsibility of SIG-TMS.Revise 14.2.1.2 as follows:14.2.1.2 Impairments14.2.1.2.1 * The requirements of Section 10.19 Chapter 15 shall be applicable when a system is impaired.14.2.1.2.2 System defects and malfunctions deficiencies shall be corrected.14.2.1.2.3 * If a defect or malfunction critical deficiency is not corrected at the conclusion of system inspection, testing,or maintenance, the system owner or the owners designated representative shall be informed of the impairment inwriting within 24 hours.A.14.2.1.2.1 See 3.3.x for definitions of critical and non-critical deficiencies and 3.3.y for the definition of impairment.A.14.2.1.2.3 Every effort should be made to correct all deficiencies as soon as possible and to avoid extendedimpairments. Notification of impairments at the end of testing should not be construed to allow a delay in notification formore that than one day where system testing takes days or weeks to be completed.Add new definitions and annex text:

. A condition of that interferes with the service or reliability for which the part, system or equipmentwas intended.

. A deficiency that could cause a threat to life, property or mission if the part, system orequipment fails to operate as intended when required.

. A deficiency that would not cause a threat to life, property or mission if the part, systemor equipment fails to operate as intended when required.

A critical deficiency is one that might cause a system to fail its life safety, property protection or missioncontinuity goals. A Non-critical Deficiency is an inconvenience or might result in a degraded mode of operation thatwould not affect life safety, property protection or mission protection. A deficiency in a supplementary might benon-critical. The failure of a circuit board that controls occupant notification would be a critical deficiency and wouldrequire emergency impairment procedures. A failure of a loudspeaker in a large space with many loudspeakers wouldprobably be a non-critical failure and would not require impairment management procedures.

. A condition where a system or unit or portion thereof is out of order, and the condition can result inthe system or unit not functioning when required.

. Temporarily shutting down a system as part of performing the routine inspection, testing, andmaintenance on that system while under constant attendance by qualified personnel, and where the system can berestored to service quickly, should not be considered an impairment. Good judgment should be considered for thehazards presented.

A condition where a system or portion thereof is out of order due to an unexpecteddeficiency, such as physical damage to a control unit or wiring.

A condition where a system or a portion thereof is out of service due to work that hasbeen planned in advance, such as the addition of new devices or appliances or reprogramming of system software.Add a new

This chapter shall provide the minimum requirements for a fire alarm or signaling system impairmentmanagement program. Measures shall be taken during the impairment to ensure that increased risks are minimized andthe duration of the impairment is limited.

An impairment management program shall be implemented immediately upon discovery of a critical deficiency.See 3.3.y for definitions of different types of impairments.

See 3.3.x for definitions of critical and non-critical deficiencies.The impairment management program shall remain in effect until all critical deficiencies have been corrected.Non-critical deficiencies shall be corrected.Where explicit written permission of the authority having jurisdiction is sought and obtained, supplemental,

non-required equipment or features may be removed to eliminate non-critical deficiencies.Where required by the authority having jurisdiction, impairment management programs shall be submitted for

review and approval.


Report on Proposals June 2012 NFPA 72Impairment management programs or procedures required by other governing laws, codes,

or standards shall be followed.A record of the impairment and all work done to correct the impairment and to inspect and test the repairs shall

be maintained by the system owner or designated representative for a period of 1 year from the date the impairment iscorrected.

The property owner shall assign an impairment coordinator to comply with the requirements of this chapter.In the absence of a specific designee, the property owner shall be considered the impairment coordinator.Where the lease, written use agreement, or management contract specifically grants the responsibility and the

authority for inspection, testing, and maintenance of the fire alarm or signaling system(s) to the tenant, managementfirm, or managing individual, the tenant, management firm, or managing individual shall assign a person as impairmentcoordinator.

A tag shall be used to indicate that a system, or part thereof, is impaired or has been removed from service.A clearly visible tag alerts building occupants, authorities and emergency forces that all or part of a system is

out of service. The tag should be plainly visible, and of sufficient size [typically 4 in. 6 in. (100 mm 150 mm)]. The tagshould identify which system or part thereof is impaired, the date and time the impairment began, and the name of theImpairment Coordinator. Figure A.15.3.1 illustrates a typical impairment tag.

The tag shall be posted at the main control unit and at each remote annunciator and each emergency servicesinterface indicating which system, or part thereof, has been impaired or removed from service.

The authority having jurisdiction shall be permitted to specify where tag(s) are to be placed.

All preplanned impairments shall be authorized by the impairment coordinator.Before authorization is given, the impairment coordinator shall be responsible for verifying that the following

procedures have been implemented:(1) The extent and expected duration of the impairment have been determined.(2) The areas or buildings involved have been inspected and the increase in risk resulting from the impairment has beendetermined.(3) Recommendations for risk reduction during the impairment have been submitted to management or the propertyowner/manager.(4) Where a required system is out of service for more than 10 hours in a 24-hour period, the impairment coordinatorshall arrange for one of the following:(a) Evacuation of the building or portion of the building affected by the system out of service(b)*An approved fire watch(c)*Establishment of a system or procedure to perform the function of the impaired system(5) The affected fire department or emergency team has been notified.(6) The insurance carrier, the alarm company, property owner/ manager, and other authorities having jurisdiction havebeen notified.(7) The supervisors in the areas to be affected have been notified.(8) A tag impairment system has been implemented.(9) All necessary personnel, tools and materials have been assembled on the impairment site.

The need for temporary protection, termination of hazardous operations, and increased frequency of inspectionsin the areas involved should be determined. All work possible should be done in advance to minimize the length of theimpairment. Where possible, temporary systems or procedures should be used to mitigate the impairment. Forexample, the use of roving fire watch personnel equipped with bullhorns could mitigate an impairment to a detection andalarm system. Fire detection and alarm systems should not be removed from service just because a building is not inuse. However, for buildings that undergo season changes, the authority having jurisdiction might permit changes to thesystem to allow it to function in a degraded mode for the unoccupied season. For example a system might be allowedto use heat detectors in place of smoke detectors in areas where the heat can be turned off safely. Where a system thathas been out of service for a prolonged period, such as in the case of idle or vacant properties, is returned to service,qualified personnel should be retained to inspect and test the systems.

Emergency impairments include but are not limited to loss of primary power that might last more than 12 hours,lightning, surge or transient voltage damage to equipment, and faults on circuits or pathways.

When emergency impairments occur, emergency action shall be taken to minimize potential injury and damage.The Impairment Coordinator shall implement the steps outlined in Section 15.5.


Report on Proposals June 2012 NFPA 72When all impaired equipment is restored to normal working order, the impairment

coordinator shall verify that the following procedures have been implemented:(1) All inspections and tests, including acceptance and reacceptance tests, have been conducted to verify that affectedsystems are operational.(2) Supervisors have been advised that protection is restored.(3) The fire department or emergency team has been advised that protection is restored.(4) The property owner/manager, insurance carrier, alarm company, and other authorities having jurisdiction have beenadvised that protection is restored.(5) The impairment tag has been removed.

This new chapter is modeled on Chapter 15 in NFPA 25. The purpose is to provide owners, operatorsand contractors with specific guidance and minimum requirements for commonly accepted impairment managementprocedures. In many cases the text is identical to that in NFPA 25, but is not being extracted so that this committee willbe able to change it as needed. In many locations additional requirements have been added to be specific to fire alarmand signaling systems. New definitions are proposed to make specific requirements in the new chapter clear andmeaningful. The new definitions are modeled on the preferred definitions from the NFPA Glossary of terms, butchanged slightly to be more exact or to be more generic. The requirements of existing 2010 section 10.19 are allincorporated in the proposed new chapter. The proposal includes revisions to existing 2010 section 14.2.1.2 tocoordinate with the new chapter.

The committee contends that this material belongs under the jurisdiction of the SIG-TMScommittee, and that they should be responsible for the content and the definitions.

Affirmative: 281 McNamara, J.


Report on Proposals June 2012 NFPA 72_______________________________________________________________________________________________72-17 Log #436a SIG-TMS

_______________________________________________________________________________________________Robert P. Schifiliti, R. P. Schifiliti Associates, Inc.

This proposal delete section 10.19 in its entirety, revises 14.2.1.2, adds new definitions and adds anew .It is proposed that the definitions and the new chapter be the responsibility of

Download - AGENDA TECHNICAL CORRELATING COMMITTEE ON … · agenda . technical correlating committee on . signaling systems for the protection of life and property . april 12-14, 2011 . holiday

Top Related