Agenda Technical Committee on Protected Premises Fire Alarm Systems June 25-27, 2014 La Jolla, CA

Agenda Technical Committee on Protected Premises Fire Alarm Systems June 25-27, 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 UL Update on Fire Resistive Cable (tentative) 14-6-7 Task Group Reports 14-6-8 Public Comments and Second Revisions [Enclosures] 14-6-9 Review of Committee Inputs [Enclosure] 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-0700 www.nfpa.org MEETING MINUTES NFPA TECHNICAL COMMITTEE ON PROTECTED PREMISES FIRE ALARM SYSTEMS (SIG-PRO) First Draft Meeting, September 09-11, 2013 St. Louis Union Station, St. Louis, MO Item No. Subject 13-9-1 Call to Order and Welcome (8:04 AM) Chair Merton Bunker called the meeting to order at 8:04 AM. 13-9-2 Approve Agenda Motion to approve the Agenda, seconded, and approved. 13-9-3 Approve Meeting Minutes from San Antonio, TX, March 2013 Motion to approve the Minutes from 03-2013, seconded, and approved. 13-9-4 Introduction of Members Those present introduced themselves (see attached Attendance Sheet for all attendees, Principles, Alternates, and Guests). A number of guests participated during the committee meeting over the 2½ days including: Mr. Bob Schifiliti, TCC Chair Mr. Bruce Fraser, SIG ECS 13-9-5 Staff Remarks & Presentations Mr. Lee Richardson (NFPA Staff) provided presentations on the following: Overview of the New Process Strategy to Improve Correlation Assignment of Technical Committee Responsibility

o Goal: minimize the number of committees working on the same chapter o Chapter 12 is now completely under the purview of SIG PRO 13-9-6 Task Group Work Review of Public Inputs In order to maximize the time the committee had to review the various Public Inputs, Mr. Merton Bunker, SIG PRO Committee Chair assigned task groups to review the Public Inputs, provide a recommendation on acting on the Public Inputs (i.e., Move to First Revision, Move to Resolve, etc.), and present the recommendation to the Committee for discussion. Task Groups below are identified in the order that each group of Public Inputs were addressed. Task Group 2: Circuits and Pathways: Horon, Capowski, Hayes, Weiss-Ishai, Novak, Shudak, Ruchala (Task Group Chair) Task Group 1: Definitions, Documentation, and System Requirements: Barrett, Hopple, Harris, Humm, Martorano, Shah, Olenick, Crowley, Doyle, Belliveau (Task Group Chair) Task Group 3: Emergency Controls: Doliber, Dix, Bisker, Leszczak, LeBlanc, Kuhta, Struck, Burkhart, Willms, Hammerberg (Task Group Chair) In addition to processing of all Public Inputs, the committee entertained discussions from the following Committee Members and guests on the following: Mr. Larry Shudak discussed alarm receipt capability during a fault condition Mr. Vic Humm discussed the possibility of adding new networking definitions The term required annunciators appeared in the code approximately three (3) times and the ambiguity was removed Chapter 2 references were reviewed and updated where required Mr. Bruce Fraser (SIG ECS) provided some insight on the current language of ASME A17.1/CSA B44Safety Code for Elevators and Escalators to ensure that NFPA 72 is not providing conflicting requirements Mr. Bill Hopple discussed whether the committee feels that the definition of a detector should change and discussed the protection of control units for dedicated function fire alarm control units Mr. Tom Hammerberg discussed some definitions that could be revised 13-9-7 Processing Schedule Mr. Lee Richardson (NFPA Staff) provided dates for the NFPA 72 document cycle. NFPA 72 (A2015) Meeting Dates CC FD Meeting (Tampa*) 01-07-2014 though 01-09-2014 Posting of First Draft Report 03-07-2014 Comment Closing Date 05-16-2014 TC SD Meeting 1 (Indy* or Omaha*) 06-23-2014 through 06-27-2014 {SIG-IDS, SIG-NAS, SIG-SSS, SIG-HOU and SIG-PRS} TC SD Meeting 2 (Indy* or Omaha*) 07-14-2014 through 07-18-2014 {SIG-PRO, SIG-FUN, SIG-ECS and SIG-TMS}

CC SD Meeting (San Diego*) 11-4-2014 through 11-06-2014 Posting of Second Draft Report 01-16-2015 NITMAM Closing Date 03-06-2015 Posting of CAMs 05-01-2015 Annual Meeting (Chicago) 06-22-2015 through 06-25-2015 *Tentative location - pending venue availability 13-9-8 Other Business No Other Business documented at this time. Mr. Lee Richardson (NFPA Staff) to review the processing schedule above and possibly recommend days be added to the Committee Meetings to review and process comments received on the First Draft document. 13-9-9 Adjournment Mr. Merton Bunker thanked the committee members for their hard work in reviewing and processing all the Public Inputs that were presented to the group. A motion to adjourn was moved, seconded, voted on and approved. The meeting was adjourned. The meeting spanned two (2 ½) days, 09-09-2013, 09-10-2013 and 09-11-2013. Respectfully submitted, Leonard Belliveau, Jr. NFPA 72, SIG-PRO Secretary

38 of 346 5/19/2014 11:24 AM Public Comment No. 235-NFPA 72-2014 [ Global Input ] Delete references to the National Electrical code article 760 or any specific article, and just use the wording as per the National Electrical Code. Statement of Problem and Substantiation for Public Comment The direct reference to only article 760 is leading to confusion as some persons do not understand how the NEC is arranged. Articles in chapters 1-4 apply to ALL wiring including Fire alarm and signaling circuits. Chapters 5-7 modify the requirements of chapters 1-4 therefore article 760 is not designed to be a stand alone chapter and should not be referred to as if it is. Chapter 8 is designed to be a stand alone chapter, except when specifically referenced back to a previous chapter. Related Item First Revision No. 92-NFPA 72-2013 [Section No. 12.2.4.2] Public Input No. 514-NFPA 72-2013 [Section No. 12.2.4.2] Submitter Information Verification Submitter Full Name: Thomas Parrish Organization: Telgian Corporation Street Address: City: State: Zip: Submittal Date: Fri May 16 15:13:48 EDT 2014

75 of 346 5/19/2014 11:24 AM Public Comment No. 147-NFPA 72-2014 [ New Section after 3.3.60 ] New Definition 3.x * cross-connect. An apparatus which enables the connection of network and telecommunications cabling from devices, systems or equipment to the network and telecommunications cabling of other systems or equipment. Statement of Problem and Substantiation for Public Comment Substantiation (FCR 17) With the addition of Class N, some terminology used to express telecommunications and network concepts specifically within the context of Class N were not defined. This change is to reduce ambiguity when this term is encountered both within the text of this document and within real-world application. Related Item First Correlating Revision No. 17-NFPA 72-2014 [Global Input] Submitter Information Verification Submitter Full Name: Jeff Silveira Organization: BICSI Street Address: City: State: Zip: Submittal Date: Wed May 14 11:50:29 EDT 2014

http://submittals.nfpa.org/terraviewweb/formlaunch?id=/terraview/c... 1 of 2 5/27/2014 2:17 PM Public Comment No. 128-NFPA 72-2014 [ New Section after A.3.3.66.19 ] Device (Class N) Class N devices includes components connected to a class N network that monitor the environment (e.g., smoke, heat, contact closure, manual in case of fire pull), and/or provide some output(s), (e.g., dry contact, audible/visual alert/notification, addressable speaker), that are required to provide the real-time functionality necessary for the protection of life and property. In this way a component connected to the network used for non-critical functions (i.e., maintenance) may be differentiated and excluded from the monitoring for integrity requirements of class N. Also in this way, transport equipment (e.g., switches, routers, hubs, media converters ) and other equipment (e.g., printers, storage devices) may be differentiated from the requirements applied to class N devices, if they do not provide life safety specific environmental monitoring, inputs, or outputs for the life safety system. This is not to say that this equipment is not important to the overall operation of the system, just that this equipment is not considered a device in the context of Class N. Equipment that does not meet the definition of a device may not be specifically supervised, but rather generally supervised as they are part of the supervised pathways that service the Class N devices themselves. Statement of Problem and Substantiation for Public Comment Additional clarification for the definition of device as it relates to class N was warranted to both illustrate examples of what is a class N device and what is not and how the distinction is drawn. The proposal is the recommendation by the Correlating Committee Task Group members that was comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of the committees. Wayne Moore A.J. Capowski Joe L. Collins Dan Horon Vic Humm Michael Pallett Charles Pugh Robert Schifiliti Aviv Siegel Larry Shudak Bob Elliott Paul Crowley Jeff Silveira Jeff Knight Andrew Berezowski Related Public Comments for This Document Related Comment Public Comment No. 127-NFPA 72-2014 [New Section after 3.3.66.22] Related Item First Revision No. 99-NFPA 72-2013 [New Section after 12.3.5] Relationship Submitter Information Verification Submitter Full Name: Michael Pallett Organization: Telecor Inc. Street Address: City:

http://submittals.nfpa.org/terraviewweb/formlaunch?id=/terraview/c... 2 of 2 5/27/2014 2:17 PM State: Zip: Submittal Date: Tue May 13 19:43:55 EDT 2014 Copyright Assignment I, Michael Pallett, hereby irrevocably grant and assign to the National Fire Protection Association (NFPA) all and full rights in copyright in this Public Comment (including both the Proposed Change and the Statement of Problem and Substantiation). I understand and intend that I acquire no rights, including rights as a joint author, in any publication of the NFPA in which this Public Comment in this or another similar or derivative form is used. I hereby warrant that I am the author of this Public Comment and 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 and the terms and conditions contained therein. I understand and intend that, by checking this box, I am creating an electronic signature that will, upon my submission of this form, have the same legal force and effect as a handwritten signature

48 of 346 5/19/2014 11:24 AM Public Comment No. 127-NFPA 72-2014 [ New Section after 3.3.66.22 ] Device (Class N) A supervised component of a life safety system, that communicates with other components of life safety systems, and that collects environmental data, or performs specific input or output functions necessary to the operation of the life safety system. Statement of Problem and Substantiation for Public Comment With the addition of Class N pathways in the first draft, the term device was used specifically in the context of Class N, but not defined. The proposal is the recommendation by the Correlating Committee Task Group members that was comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of the committees. Wayne Moore A.J. Capowski Joe L. Collins Dan Horon Vic Humm Michael Pallett Charles Pugh Robert Schifiliti Aviv Siegel Larry Shudak Bob Elliott Paul Crowley Jeff Silveira Jeff Knight Andrew Berezowski Related Item First Revision No. 99-NFPA 72-2013 [New Section after 12.3.5] Submitter Information Verification Submitter Full Name: Michael Pallett Organization: Telecor Inc. Street Address: City: State: Zip: Submittal Date: Tue May 13 19:19:25 EDT 2014

7 of 346 5/19/2014 11:24 AM Public Comment No. 31-NFPA 72-2014 [ Section No. 3.3.90 ] 3.3.90 * Emergency Control Functions. Building, fire, and emergency control elements or systems that are initiated by the fire alarm or signaling system and either increase the level of life safety for occupants or control the spread of the harmful effects of fire or other dangerous products. (SIG-PRO) Statement of Problem and Substantiation for Public Comment Removes unnecessary and limiting qualifiers. Related Item First Revision No. 124-NFPA 72-2013 [Section No. 3.3.91] Submitter Information Verification Submitter Full Name: Robert Schifiliti Organization: R. P. Schifiliti Associates, I Street Address: City: State: Zip: Submittal Date: Thu Apr 03 08:53:53 EDT 2014

51 of 346 5/19/2014 11:24 AM Public Comment No. 130-NFPA 72-2014 [ New Section after A.3.3.91 ] Endpoint (Class N) An endpoint device originates and/or terminates a communication stream, and does not forward it to other devices. An FACU, ACU, ECCU endpoint originates and/or terminates a communication stream with autonomy. If data is sent to, or received from other locations, that communications stream forms a new path. The new path may even employ a different communications protocol, and where permitted, have a different Pathway Class Designation as defined in 12.3. The exception in section 12.3.6(1) shows Class N communication paths do not require redundant paths when connected to a single endpoint device. However, connections to an FACU, ACU or ECCU must be redundant even when those elements are an endpoint on a Class N communication path, with the excepted allowance of 20 feet inside a raceway or enclosure defined in 12.6.9. Statement of Problem and Substantiation for Public Comment Additional clarification for the definition of endpoint as it relates to class N was warranted to explain the distinction between endpoints that are devices and endpoints that are control units, and their relationship to communications. The proposal is the recommendation by the Correlating Committee Task Group members that was comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of the committees. Wayne Moore A.J. Capowski Joe L. Collins Dan Horon Vic Humm Michael Pallett Charles Pugh Robert Schifiliti Aviv Siegel Larry Shudak Bob Elliott Paul Crowley Jeff Silveira Jeff Knight Andrew Berezowski Related Public Comments for This Document Related Comment Public Comment No. 129-NFPA 72-2014 [New Section after 3.3.92] Related Item First Revision No. 99-NFPA 72-2013 [New Section after 12.3.5] Relationship Submitter Information Verification Submitter Full Name: Michael Pallett Organization: Telecor Inc. Street Address: City: State: Zip:

50 of 346 5/19/2014 11:24 AM Public Comment No. 129-NFPA 72-2014 [ New Section after 3.3.92 ] Endpoint (Class N) The end of a pathway where a single addressable device or a control unit (FACU, ACU, or ECCU) is connected. Statement of Problem and Substantiation for Public Comment With the addition of Class N pathways in the first draft, the term endpoint was used specifically in the context of Class N, but not defined. The proposal is the recommendation by the Correlating Committee Task Group members that was comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of the committees. Wayne Moore A.J. Capowski Joe L. Collins Dan Horon Vic Humm Michael Pallett Charles Pugh Robert Schifiliti Aviv Siegel Larry Shudak Bob Elliott Paul Crowley Jeff Silveira Jeff Knight Andrew Berezowski Related Item First Revision No. 99-NFPA 72-2013 [New Section after 12.3.5] Submitter Information Verification Submitter Full Name: Michael Pallett Organization: Telecor Inc. Street Address: City: State: Zip: Submittal Date: Tue May 13 20:02:40 EDT 2014

76 of 346 5/19/2014 11:24 AM Public Comment No. 148-NFPA 72-2014 [ New Section after 3.3.158 ] New Definition 3.x * media converter. A network device that connects two dissimilar types of cabling media, such as balanced twisted-pair cabling and coaxial cabling, or balanced twisted-pair cabling and optical fiber cabling. Statement of Problem and Substantiation for Public Comment Substantiation (FCR 17) With the addition of Class N, some terminology used to express telecommunications and network concepts specifically within the context of Class N were not defined. This change is to reduce ambiguity when this term is encountered both within the text of this document and real-world application. Related Item First Correlating Revision No. 17-NFPA 72-2014 [Global Input] Submitter Information Verification Submitter Full Name: Jeff Silveira Organization: BICSI Street Address: City: State: Zip: Submittal Date: Wed May 14 11:59:21 EDT 2014

77 of 346 5/19/2014 11:24 AM Public Comment No. 149-NFPA 72-2014 [ New Section after 3.3.243 ] New Definition 3.x * ring topology. A physical or logical arrangement of a system or network in which nodes are connected in a point-to-point serial fashion and forming an unbroken circular configuration. Each node receives and retransmits the signal to the next node. Statement of Problem and Substantiation for Public Comment Substantiation (FCR 17) With the addition of Class N, some terminology used to express telecommunications and network concepts specifically within the context of Class N were not defined. This change is to reduce ambiguity when this term is encountered both within the text of this document and within real-world application. Related Item First Correlating Revision No. 17-NFPA 72-2014 [Global Input] Submitter Information Verification Submitter Full Name: Jeff Silveira Organization: BICSI Street Address: City: State: Zip: Submittal Date: Wed May 14 12:02:29 EDT 2014

03 of 346 5/19/2014 11:24 AM Public Comment No. 162-NFPA 72-2014 [ New Section after 3.3.286 ] New Definition 3.x * switch (class N). A device that provides a centralized point of connection for network enabled equipment, enabling communications between all connected elements. A connection port on a switch represents a separate communications channel, and a switch may perform additional functions, such as port monitoring and communication (message) management. A switch is an integral part of a local area network (LAN), Statement of Problem and Substantiation for Public Comment With the addition of Class N, some terminology used to express telecommunications and network concepts specifically within the context of Class N were not defined. This change is to reduce ambiguity when this term is encountered both within the text of this document and within real-world application. Related Item First Correlating Revision No. 17-NFPA 72-2014 [Global Input] Submitter Information Verification Submitter Full Name: Jeff Silveira Organization: BICSI Street Address: City: State: Zip: Submittal Date: Wed May 14 13:13:59 EDT 2014

29 of 346 5/19/2014 11:24 AM Public Comment No. 165-NFPA 72-2014 [ New Section after 3.3.305 ] New Definition 3.x * uplink (class N): A cabling connection between switches in a network. An uplink may also be known as a "trunk" or backbone. Statement of Problem and Substantiation for Public Comment Substantiation (FCR 17) With the addition of Class N, some terminology used to express telecommunications and network concepts specifically within the context of Class N were not defined. This change is to reduce ambiguity when this term is encountered both within the text of this document and within real-world application. Related Item First Correlating Revision No. 17-NFPA 72-2014 [Global Input] Submitter Information Verification Submitter Full Name: Jeff Silveira Organization: BICSI Street Address: City: State: Zip: Submittal Date: Wed May 14 13:55:24 EDT 2014

6 of 346 5/19/2014 11:24 AM Public Comment No. 56-NFPA 72-2014 [ Section No. 7.3.7.4 ] 7.3.7.4 Performance-based design documentation for signaling line circuit zoning shall be in accordance with 23.6.1.4 and 23.6.1.5. (SIG-PRO) Statement of Problem and Substantiation for Public Comment CC NOTE: The following CC Note No. 3 appeared in the First Draft Report as First Revision No. 268, and is also related to Public Input No. 365 and 565. The correlating committee makes reference to 7.3.7.4 introduced by FR 127. The correlating committee directs the SIG-PRO committee to reconsider the action on this FR to clear up the circular references that exist between 7.3.7.4 and its reference to 23.6.1.4 and the reference in 23.6.1.4 back to 7.3.7.4. Related Item First Revision No. 268-NFPA 72-2013 [Section No. 7.3.7.3] Public Input No. 365-NFPA 72-2013 [New Section after 7.3.7.3] Public Input No. 565-NFPA 72-2013 [Section No. 7.3.7.3] Submitter Information Verification 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: Wed Apr 30 09:13:21 EDT 2014

67 of 346 5/19/2014 11:24 AM Public Comment No. 184-NFPA 72-2014 [ Section No. 12.3.6 ] 12.3.6 Class N. A pathway shall be designated as Class N when it performs as follows: (1) * It includes two or more pathways where operational capability of the primary pathway and a redundant pathway to each device shall be verified through end-to-end communication. Exception: When only one device is served, only one pathway shall be required. (2) A loss of intended communications between endpoints shall be annunciated as a trouble signal. (3) A single open, ground, short, or combination of faults on one pathway shall not affect any other pathway. (4) (5) * Conditions that affect the operation of the primary pathway(s) and redundant pathway(s) shall be annunciated as a trouble signal when the system s minimal operational requirements cannot be met. * Primary and redundant pathways shall not be permitted to share traffic over the same physical segment. Statement of Problem and Substantiation for Public Comment This section and designation should either be delted or only included in Annex material. The code is specifying performance that isn't required by any codes or standards and can't be applied without the expnatory material of the Annex. The annex material should also be delted becasue it conflicts with the perofrmance criteria stated. The diagrams inthe Annex material show both redundant paths to converge in single switches which is lost would render both paths unusable. There is nothing to preclude a designer to design for this performance. It doesn't need to be incorproated in NFPA 72. Related Item First Revision No. 99-NFPA 72-2013 [New Section after 12.3.5] Submitter Information Verification Submitter Full Name: Raymond Grill Organization: Arup Street Address: City: State: Zip: Submittal Date: Wed May 14 21:10:52 EDT 2014

89 of 346 5/19/2014 11:24 AM Public Comment No. 158-NFPA 72-2014 [ Section No. A.12.3.6(1) ] A.12.3.6(1)

90 of 346 5/19/2014 11:24 AM Class N consists of pathways between control equipment and devices. The pathways comprise metallic conductor communications cable, such as a 100 ohm balanced twisted-pair (e.g., Category 5E), including single-pair or multi-pair cable, or other communications media such as optical fiber cable or wireless transmission, or a combination of two or more of these. Pathways consist of uninterrupted communications media between control equipment and an endpoint device or of a network of multiple interconnected communications media pathway segments connecting multiple devices. Media pathway segments are created by the use of transmission equipment such as Ethernet switches, wireless repeaters, or media converters that interrupt an otherwise continuous pathway. Requirements for Class N pathway transmission equipment are not covered in Chapter 12 but by other chapters in NFPA 72. A network of pathway segments is also described as primary pathway segments, redundant pathway segments, or nondesignated pathway segments. Primary and redundant pathways, from control equipment to each device, are independently and continuously verified for their ability to support end-to-end communications to and from each endpoint device. Each device will be provided a primary pathway consisting of one or more pathway segments. For primary pathway segments that service more than one device, additional redundant pathway segments provide alternate verified communication pathways to the devices. Should any primary pathway segment fail, communication is supported by the redundant pathway segments. Should either a primary or redundant pathway segment fail, trouble will be indicated by virtue of the continuous verification of all primary and redundant pathway segments. The redundant pathway segments are generally independent and do not normally share media with the primary pathways. However, there are exceptions, such as different frequencies for wireless or ring topologies. [See A.12.3.6(5).] There is an opportunity to enhance the robustness of a Class N network by providing physically distinct pathway segments (i.e., an alternate conduit, or cable tray route, or wireless transmission frequency range, or a combination of distinct media). It is also permissible to provide other nondesignated pathway segments. Additional pathway segments in excess of the minimum requirements of Class N increase the overall robustness of the network and are often desirable. However, since these additional pathway segments exceed the minimum equipment standards, there is no intention to create an additional monitoring burden, so verification of these pathways is optional. For Class N, where a conductor-based media is used, it is not the intention to monitor faults on individual conductors but rather to monitor the operational capability and performance of the pathway as a whole. Unlike Class C, where multiple pathways are not required, for Class N some pathway segments that carry communications for multiple devices (such as Ethernet uplinks or backbones) will have redundant pathway segments present. The intention is that any one pathway segment can fail without a loss in operational capability to more than one device. For example, connections to control equipment (fire alarm control units, ACUs, or ECCUs), where any interruption in communications could potentially affect all devices, would have redundant pathway segments. Additionally, backbone and uplink pathway segments that support communications for more than one device and are positioned between transmission equipment would also have a redundant pathway segment. But the requirement for redundant pathway segments does not apply to those pathway segments used to service a single device [see Figure A.12.3.6(1)(a) ]. The term devices is used generically in this section to refer to endpoint devices, which include the following: (1) Input components such as alarm initiating switches, sensors (2) Output components such as Ethernet speakers (i.e., IEEE 802.3af PoE speakers), strobes, textual signage, audio amplifiers Transmission equipment (e.g., media converters, Ethernet switches, patch panels, cross-connects) are not considered devices with respect to Class N pathways. The audio amplifier example is included to explain a type of addressable device that can receive a digital audio input from the Class N pathway but provide a notification appliance circuit (NAC) output to support Class A, B, or X speaker connections. Other similar devices are also possible to provide alternate class pathway connections for strobes (NACs) or initiating devices (IDCs). From the perspective of the Class N pathway, this is considered an endpoint device. However, since these types of endpoints can support multiple notification appliance devices or initiating devices, they are subject to the redundant pathway segment requirement and are provided with dual pathway connections. Control equipment connected to a Class N network for communications with devices would generally utilize redundant pathway segments. Control equipment connected to other control equipment on a Class N network would utilize redundant pathway segments if the control equipment was dependent on any of the pathway segments so that a failure of a primary pathway segment in between control equipment could impair the operation of the control equipment [see Figure A.12.3.6(1)(b) ].

91 of 346 5/19/2014 11:24 AM Another utilization of endpoints is permitted for devices providing two connection ports and supporting dual pathway segment connections. The description of endpoint devices is not intended to exclude devices that support dual pathway connections. Since these pathways are servicing a single device, only a single primary pathway connection is required. The second pathway connection exceeds minimum equipment standards and is therefore not required to be verified as a redundant pathway segment; it can be considered connected to a nondesignated pathway segment [see Figure A.12.3.6(1)(c) ]. Figure A.12.3.6(1)(a) Class N Pathway Block Diagram. Figure A.12.3.6(1)(b) Class N Pathway Block Diagram with Multiple Control Units. Figure A.12.3.6(1)(c) Class N Pathway Block Diagram with Device with Dual Pathway Connection.

92 of 346 5/19/2014 11:24 AM with subsequent subsections and drawings should be replaced with attached PDF. This material was created by the TCC Task Group on Networks. Additional Proposed Changes File Name Description Approved Class_N_Annex_Submitted_by_Task_Group_May_13_.pdf Statement of Problem and Substantiation for Public Comment Revised for clarity and consistency with Code. Related Item Public Input No. 290-NFPA 72-2013 [New Section after A.12.3.5] Submitter Information Verification A.12.3.6(1) text and drawings are included in PDF. Submitter Full Name: Daniel Horon Organization: CADgraphics, Incorporated Street Address: City: State: Zip: Submittal Date: Wed May 14 12:56:33 EDT 2014

A.12.3.6(1) The Class N pathway designation is added to specifically address the use of modern network infrastructure when used in fire alarm and emergency communication systems. Ethernet network devices are addressable, but with an important distinction from device addresses on a traditional SLC multi drop loop. A device with an Ethernet address is, in most cases, a physical endpoint connected to a dedicated cable. Traditional SLC devices are all wired on the same communication line (in parallel) similar to an old party line telephone system. By comparison, Ethernet s network switches direct each data packet to its intended recipient device like our modern phone systems. A fundamental technical difference of Class N from Class A, B or X is that it has no requirement to report a connection to ground unless the ground impairs the path. A practical concern, where using Ethernet, is that it is reliable and secure, especially when life safety systems share the same pathways. See 23.6.3 Class N Shared Pathways. As a visual model, Class N could be likened to a Class X [backbone], allowed to have Class C branch paths to single endpoint devices. Therefore, every effort is made in this section to clearly distinguish the single endpoint device from the transport equipment required to have redundant paths, like Class X. Class N requires, redundant, monitored pathway segments to and from control equipment (fire alarm control units, ACUs, or ECCUs), where any interruption in communications could potentially affect multiple endpoint devices. Typically, interconnected communications equipment such as Ethernet switches, wireless repeaters, or media converters are used in combination to create pathways. Chapter 12 describes the required behavior of Class N pathways. All equipment must meet the requirements of other chapters in NFPA 72. Redundant pathways, isolated from ground, are actually common practice in robust Ethernet designs. Managed network switches commonly have specific uplink ports that are intended for load sharing and allow two parallel connections. For compliance with Class N, a trouble must be reported if either of these connections fails. [See Figure A.12.3.6(1)(a 1).] Class N networks may be specified for ancillary functions, but are not required for supplemental reporting described in 23.12.4. [See Figure A.23.12.4.] Class N pathways may use metallic conductor communications cable, such as a 100 ohm balanced twisted pair (e.g., Category 5E), including single pair or multi pair cable, or other communications media such as optical fiber cable or wireless transmission, or a combination of two or more such transport mediums. Where a conductor based media is used for Class N, the intention is not to monitor faults on individual conductors, but rather to monitor the operational capability and performance of the pathway as a whole. Similar to Class C, end to end verification is used in Class N. Primary and required redundant pathways are independently and continuously verified for their ability to support end to end communications to and from each endpoint device and its associated control equipment. Pathway segments that service more than one device, must have at least one verified redundant pathway segment. Should any primary pathway segment fail, communication is supported by the redundant pathway segment(s.) Failure of either a primary or redundant pathway will indicate a trouble.

Redundant pathway segments are generally independent and do not normally share media with the primary pathways. However, there are exceptions, such as different frequencies for wireless components, or ring topologies. [See Figure A.12.3.6(5).] A Class N network may be made more reliable with physically distinct pathway segments (i.e., an alternate conduit, or cable tray route, or wireless transmission frequency range, or a combination of distinct media). In addition to the required primary segments and redundant segments, a Class N pathway is permitted to have nonrequired segments. [See Figure A.12.3.6(1)(a 3).] Additional nonrequired pathway segments are allowed to be connected and not independently monitored for integrity as long as two paths are monitored to meet the redundancy requirement of Class N. Figure A.12.3.6(1)(a) Class N Pathway Block Diagrams. 20 Feet maximum inside enclosure or raceway FACU, ACU, or ECCU Switch Switch 1 2 A redundant cable between two switches must have special functionality in order to monitor integrity when a secondary path is not in use. Figure A.12.3.6(1)(a-1) Endpoint Devices 20 Feet maximum inside enclosure or raceway FACU, ACU, or ECCU Switch Switch 1 2 Nonrequired redundant path segment Endpoint Devices Group H Switch Switch 4 3 Figure A.12.3.6(1)(a-2) Endpoint Devices Group K Endpoint Devices Group J

Traditionally, NFPA has used the word device for input components, and term appliance for components used in notification. With respect to Class N, the term device includes appliances and other intelligent, addressable components that perform a programmable input or output function. Examples of Class N devices include: (1) Input components such as alarm initiating modules switches and sensors, (2) Output components such as output modules, Ethernet speakers (i.e., IEEE 802.3af PoE speakers), intelligent strobes, textual signage, and intelligent audio amplifiers. Transmission equipment components (e.g., media converters, Ethernet switches, patch panels, cross connects) are connected to the Class N pathway merely to transport instructions between other equipment. As such, they are not considered devices with respect to Class N pathways. The audio amplifier listed above is an example of an addressable device that can receive a digital audio input from the Class N pathway and then provide a notification appliance circuit (NAC) output with Class A, B, or X pathways. Other endpoint devices may similarly provide alternate Class pathways for strobes (NACs) or initiating devices (IDCs). From the perspective of the Class N pathway, communications terminates at this endpoint device. However, since these types of endpoints can support multiple notification appliance devices or initiating devices, they are subject to the redundant pathway requirement. A single component may provide two distinct functions in a life safety system. For example, one component may house both a fire sensor and a notification device. Or, an addressable input module may provide for two distinct inputs from a waterflow switch and a tamper switch. Class N requires both a primary and redundant path to these dual purpose components. Class N connections between control equipment are required to have redundant monitored pathway segments if a failure of a primary pathway segment in between control equipment could impair the operation of the control equipment [see Figure A.12.3.6(1)(b) ]. Figure A.12.3.6(1)(b) Class N Pathway Block Diagram with Multiple Control Units. Switch 1 FACU, ACU, or ECCU (1) FACU, ACU, or ECCU Switch 2 (2) Switch 3 FACU, ACU, or ECCU Figure A.12.3.6(1)(b) (3)

Class N is also permitted to include dual port devices that provide both transmission and input/output functions. Endpoint devices may have multiple connection ports and support dual pathway segment connections; thus the term endpoint device is not intended to prohibit more than one connection to a device. Even with dual connections, where other devices depend on the path, primary and redundant paths are required. But, where an endpoint device has two connection ports, and when a secondary nonrequired connection is added, there is no requirement to separately supervise the nonrequired redundant pathway segment [see Figure A.12.3.6(1)(c)]. Figure A.12.3.6(1)(c) Class N Pathway Block Diagram with Device with Dual Pathway Connection. To FACU Switch Endpoint Devices A nonrequired redundant cable to an endpoint device is permitted, and does not require separate supervision. Figure A.12.3.6(1)(c) A.12.3.6(4) Operational conditions of the pathway include factors such as latency, throughput, response time, arrival rate, utilization, bandwidth, and loss. Life safety equipment connected to a Class N network actively monitors some or all of the pathway s operational conditions, so that an improperly installed or configured pathway, or a subsequently degraded pathway or segment is detected by the life safety equipment and reported as a trouble. The trouble condition is reported when operational conditions of the pathway(s) have deteriorated to the point where the equipment is no longer capable of meeting its minimum performance requirements, even if some level of communication to devices is still maintained. Performance requirements include the activation of an alarm within 10 seconds, the reporting of a trouble signal within 200 seconds, synchronization of strobes, and delivery of audio messages with required intelligibility. End to end communications might be operational under system idle conditions, but in the event of an alarm, the increased load on a degraded pathway could cause a partial or complete failure to deliver required life safety signals. Such predictable failure must be actively detected and reported. A.12.3.6(5) Devices with dual path connections are permitted to be connected in a daisy chain of devices on a ring. Again, where Class N pathway segments support multiple devices, verified redundant pathway segment(s) are required. This can be accomplished with a ring topology, as long as each segment of the ring is verified as functional, and the failure of any one segment does not result in the loss of functionality of more than one device. In this arrangement, primary and redundant pathway segments share the same media, and provide two possible directions of communications in a ring topology [see Figure A.12.3.6(5) ]. This daisy chain configuration is also permitted between multiple control units that require verified primary and redundant pathway segments.

Figure A.12.3.6(5) Class N Pathway Block Diagram with Daisy Chained Devices with Dual Pathway Connection. To FACU Switch 1 Switch 2 Endpoint Devices with dual pathway connectors Communications continues from either direction in a ring topology. Figure A.12.3.6(5) Figure A.23.12.4 Supplemental Reporting Network To UL Listed Monitoring Computer 1 Fire Alarm Control Unit Brand X Proprietary SLC Communications To UL Listed Monitoring Ethernet Network Computer 2 Fire Alarm Control Unit Brand Y To UL Listed Monitoring Proprietary SLC Communications Handheld Fire Alarm Control Unit Brand Z Figure A.23.12.4 Proprietary SLC Communications

51 of 346 5/19/2014 11:24 AM Public Comment No. 174-NFPA 72-2014 [ Section No. A.12.3.6(1) ]

52 of 346 5/19/2014 11:24 AM A.12.3.6(1)

Class N consists of pathways between control equipment and devices. The pathways comprise A.12.3.6(1) The Class N pathway designation is added to specifically address the use of modern network infrastructure when used in fire alarm and emergency communication systems. Ethernet network devices are addressable, but with an important distinction from device addresses on a traditional SLC multi-drop loop. A device with an Ethernet address is, in most cases, a physical endpoint connected to a dedicated cable. Traditional SLC devices are all wired on the same communication line (in parallel) similar to an old party-line telephone system. By comparison, Ethernet s network switches direct each data packet to its intended recipient device like our modern phone systems. A fundamental technical difference of Class N from Class A, B or X is that it has no requirement to report a connection to ground unless the ground impairs the path. A practical concern, where using Ethernet, is that it is reliable and secure, especially when life safety systems share the same pathways. See 23.6.3 Class N Shared Pathways. As a visual model, Class N could be likened to a Class X [backbone], allowed to have Class C branch paths to single endpoint devices. Therefore, every effort is made in this section to clearly distinguish the single endpoint device from the transport equipment required to have redundant paths, like Class X. Class N requires, redundant, monitored pathway segments to and from control equipment (fire alarm control units, ACUs, or ECCUs), where any interruption in communications could potentially affect multiple endpoint devices. Typically, interconnected communications equipment such as Ethernet switches, wireless repeaters, or media converters are used in combination to create pathways. Chapter 12 describes the required behavior of Class N pathways. All equipment must meet the requirements of other chapters in NFPA 72. Redundant pathways, isolated from ground, are actually common practice in robust Ethernet designs. Managed network switches commonly have specific uplink ports that are intended for load sharing and allow two parallel connections. For compliance with Class N, a trouble must be reported if either of these connections fails. [See Figure A.12.3.6(1)(a-1).] Class N networks may be specified for ancillary functions, but are not required for supplemental reporting described in 23.12.4. [See Figure A.23.12.4.] Class N pathways may use metallic conductor communications cable, such as a 100 ohm balanced twisted - pair (e.g., Category 5E), including single - pair or multi-pair cable, or other communications media such as optical fiber cable or wireless transmission, or a combination of two or more of these. Pathways consist of uninterrupted communications media between control equipment and an endpoint device or of a network of multiple interconnected communications media pathway segments connecting multiple devices. Media pathway segments are created by the use of transmission equipment such as Ethernet switches, wireless repeaters, or media converters that interrupt an otherwise continuous pathway. Requirements for Class N pathway transmission equipment are not covered in Chapter 12 but by other chapters in NFPA 72.A network of pathway segments is also described as primary pathway segments, redundant pathway segments, or nondesignated pathway segments. Primary and redundant pathways, from control equipment to each device, such transport mediums. Where a conductor-based media is used for Class N, the intention is not to monitor faults on individual conductors, but rather to monitor the operational capability and performance of the pathway as a whole. Similar to Class C, end-to-end verification is used in Class N. Primary and required redundant pathways are independently and continuously verified for their ability to support end -? to - 53 of 346 5/19/2014 11:24 AM

? end communications to and from each endpoint device. Each device will be provided a primary pathway consisting of one or more pathway segments. For primary pathway segments and its associated control equipment. Pathway segments that service more than one device, additional redundant pathway segments provide alternate verified communication pathways to the devices must have at least one verified redundant pathway segment. Should any primary pathway segment fail, communication is supported by the redundant pathway segments. Should segment(s.) Failure of either a primary or redundant pathway segment fail, trouble will be indicated by virtue of the continuous verification of all primary and redundant pathway segments. The redundant will indicate a trouble. Redundant pathway segments are generally independent and do not normally share media with the primary pathways. However, there are exceptions, such as different frequencies for wireless components, or ring topologies. [See Figure A.12.3.6(5).] There is an opportunity to enhance the robustness of a A Class N network by providing may be made more reliable with physically distinct pathway segments (i.e., an alternate conduit, or cable tray route, or wireless transmission frequency range, or a combination of distinct media). It is also permissible to provide other nondesignated pathway segments. Additional pathway segments in excess of the minimum requirements of Class N increase the overall robustness of the network and are often desirable. However, since these additional pathway segments exceed the minimum equipment standards, there is no intention to create an additional monitoring burden, so verification of these pathways is optional.for Class N, where a conductor-based media is used, it is not the intention to monitor faults on individual conductors but rather to monitor the operational capability and performance of the pathway as a whole. Unlike Class C, where multiple pathways are not required, for Class N some pathway segments that carry communications for multiple devices (such as Ethernet uplinks or backbones) will have redundant pathway segments present. The intention is that any one pathway segment can fail without a loss in operational capability to more than one device. For example, connections to control equipment (fire alarm control units, ACUs, or ECCUs), where any interruption in communications could potentially affect all devices, would have redundant pathway segments. Additionally, backbone and uplink pathway segments that support communications for more than one device and are positioned between transmission equipment would also have a redundant pathway segment. But the requirement for redundant pathway segments does not apply to those pathway segments used to service a single device [see In addition to the required primary segments and redundant segments, a Class N pathway is permitted to have nonrequired segments. [See Figure A.12.3.6(1)(a-2).] Additional nonrequired pathway segments are allowed to be connected and not independently monitored for integrity as long as two paths are monitored to meet the redundancy requirement of Class N. Figure A.12.3.6(1)(a) ] Class N Pathway Block Diagram. The term devices is used generically in this section to refer to endpoint devices, which include the following: With respect to Class N, the term device refers to an intelligent, addressable device that performs a programmable input or output function. Examples of Class N devices include: Input components such as alarm initiating modules switches and sensors, sensors (1) Output components such as output modules, Ethernet speakers (i.e., IEEE 802.3af PoE speakers), intelligent strobes, textual signage, and intelligent audio amplifiers. Transmission equipment components (e.g., media converters, Ethernet switches, patch panels, cross 54 of 346 5/19/2014 11:24 AM

-? connects) are connected to the Class N pathway merely to transport instructions between other equipment. As such, they are not considered devices with respect to Class N pathways. The The audio amplifier example is included to explain a type of listed above is an example of an addressable device that can receive a digital audio input from the Class N pathway but and then provide a notification appliance circuit (NAC) output to support with Class A, B, or X speaker connections pathways. Other similar devices are also possible to provide alternate class pathway connections endpoint devices may similarly provide alternate Class pathways for strobes (NACs) or initiating devices (IDCs). From the perspective of the Class N pathway, communications terminates at this is considered an endpoint device. However, since these types of endpoints can support multiple notification appliance devices or initiating devices, they are subject to the redundant pathway segment requirement and are provided with dual pathway connections. Control equipment connected to a Class N network for communications with devices would generally utilize redundant pathway segments. Control equipment connected to other control equipment on a Class N network would utilize redundant pathway segments if the control equipment was dependent on any of the pathway segments so that Class N connections between control equipment are required to have redundant monitored pathway segments if a failure of a primary pathway segment in between control equipment could impair the operation of the control equipment [see Figure A.12.3.6(1)(b) ]. Another utilization of endpoints is permitted for devices providing two connection ports and supporting dual pathway segment connections. The description of endpoint devices is not intended to exclude devices that support dual pathway connections. Since these pathways are servicing a single device, only a single primary pathway connection is required. The second pathway connection exceeds minimum equipment standards and is therefore not required to be verified as a redundant pathway segment; it can be considered connected to a nondesignated pathway segment Figure A.12.3.6(1)(b) Class N Pathway Block Diagram with Multiple Control Units. Class N is also permitted to include dual port devices that provide both transmission and input/output functions. Endpoint devices may have multiple connection ports and support dual pathway segment connections; thus the term endpoint device is not intended to prohibit more than one connection to a device. Even with dual connections, where other devices depend on the path, primary and redundant paths are required. But, where an endpoint device has two connection ports, and when a secondary nonrequired connection is added, there is no requirement to separately supervise the nonrequired pathway segment [see Figure A.12.3.6(1)(c) ]. Figure A.12.3.6(1)(a) Class N Pathway Block Diagram. 55 of 346 5/19/2014 11:24 AM

56 of 346 5/19/2014 11:24 AM Figure A.12.3.6(1)(b) Class N Pathway Block Diagram with Multiple Control Units. Figure A.12.3.6(1)( c) Class N Pathway Block Diagram with Device with Dual Pathway Connection.

57 of 346 5/19/2014 11:24 AM Additional Proposed Changes Final_Class_N_Pathway_Block_Diagrams_1.png File Name Description Approved Figure A.12.3.6(1)(a-1) & Figure A.12.3.6(1)(a-2) Figure Final_Class_N_Pathway_Block_Diagram_with_Multiple_Control_Units_1.png A.12.3.6(1)(b) Final_Class_N_Pathway_Block_Diagram_with_Device_with_Dual_Pathway_Connection_1.png Figure A.12.3.6(1)(c) Final_A12.3.6_1_with_drawings.docx Statement of Problem and Substantiation for Public Comment Complete text and drawings for A12.3.6(1) in word format Editorial and organizational changes for improved readability and clarity. Drawing were changed to make the style more similar to Annex F. Added examples of a comparison between Class N and Class X and Class C. Also added a clarification that class N is not required for supplemental reporting.the proposal is the recommendation by the Correlating Committee Task Group members that was comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of the committees. Wayne Moore A.J. Capowski Joe L. Collins Dan Horon Vic Humm Michael Pallett Charles Pugh Robert Schifiliti Aviv Siegel Larry Shudak

58 of 346 5/19/2014 11:24 AM Bob Elliott Paul Crowley Jeff Silveira Jeff Knight Andrew Berezowski Related Item Public Input No. 290-NFPA 72-2013 [New Section after A.12.3.5] Submitter Information Verification This PC has not been submitted yet

A.12.3.6(1) The Class N pathway designation is added to specifically address the use of modern network infrastructure when used in fire alarm and emergency communication systems. Ethernet network devices are addressable, but with an important distinction from device addresses on a traditional SLC multi-drop loop. A device with an Ethernet address is, in most cases, a physical endpoint connected to a dedicated cable. Traditional SLC devices are all wired on the same communication line (in parallel) similar to an old party-line telephone system. By comparison, Ethernet s network switches direct each data packet to its intended recipient device like our modern phone systems. A fundamental technical difference of Class N from Class A, B or X is that it has no requirement to report a connection to ground unless the ground impairs the path. A practical concern, where using Ethernet, is that it is reliable and secure, especially when life safety systems share the same pathways. See 23.6.3 Class N Shared Pathways. As a visual model, Class N could be likened to a Class X [backbone], allowed to have Class C branch paths to single endpoint devices. Therefore, every effort is made in this section to clearly distinguish the single endpoint device from the transport equipment required to have redundant paths, like Class X. Class N requires, redundant, monitored pathway segments to and from control equipment (fire alarm control units, ACUs, or ECCUs), where any interruption in communications could potentially affect multiple endpoint devices. Typically, interconnected communications equipment such as Ethernet switches, wireless repeaters, or media converters are used in combination to create pathways. Chapter 12 describes the required behavior of Class N pathways. All equipment must meet the requirements of other chapters in NFPA 72. Redundant pathways, isolated from ground, are actually common practice in robust Ethernet designs. Managed network switches commonly have specific uplink ports that are intended for load sharing and allow two parallel connections. For compliance with Class N, a trouble must be reported if either of these connections fails. [See Figure A.12.3.6(1)(a-1).] Class N networks may be specified for ancillary functions, but are not required for supplemental reporting described in 23.12.4. [See Figure A.23.12.4.] Class N pathways may use metallic conductor communications cable, such as a 100 ohm balanced twisted pair (e.g., Category 5E), including single pair or multi pair cable, or other communications media such as optical fiber cable or wireless transmission, or a combination of two or more such transport mediums. Where a conductor based media is used for Class N, the intention is not to monitor faults on individual conductors, but rather to monitor the operational capability and performance of the pathway as a whole. Similar to Class C, end to end verification is used in Class N. Primary and required redundant pathways are independently and continuously verified for their ability to support end to end communications to and from each endpoint device and its associated control equipment. Pathway segments that service more than one device, must have at least one verified redundant pathway segment. Should any primary pathway segment fail, communication is supported by

Switch 2 Switch 1 the redundant pathway segment(s.) Failure of either a primary or redundant pathway will indicate a trouble. FACU, ACU, or ECCU Figure A.12.3.6(1)(b) FACU, ACU, or ECCU Redundant pathway segments are generally independent and do not normally share media with the (1) primary pathways. However, there are exceptions, such as different frequencies for wireless components, or ring topologies. [See Figure A.12.3.6(5).] A Class N network may be made more reliable with physically distinct pathway segments (i.e., an alternate conduit, or cable tray route, or wireless transmission frequency range, or a combination of distinct media). In addition to the required primary segments and redundant segments, a Class N (2) pathway is permitted to have nonrequired Switch segments. FACU, [See Figure A.12.3.6(1)(a-2).] Additional 3 ACU, or nonrequired pathway segments are allowed to be connected and not independently monitored for ECCU integrity as long as two paths are monitored to meet the redundancy requirement of Class N. Figure A.12.3.6(1)(a) Class N Pathway Block Diagrams. (3) 20 Feet maximum inside enclosure or raceway FACU, ACU, or ECCU Switch Switch 1 2 A redundant cable between two switches must have special functionality in order to monitor integrity when a secondary path is not in use. Figure A.12.3.6(1)(a-1) Endpoint Devices 20 Feet maximum inside enclosure or raceway FACU, ACU, or ECCU Switch Switch 1 2 Nonrequired redundant path segment Endpoint Devices Group H Switch Switch 4 3 Figure A.12.3.6(1)(a-2) Endpoint Devices Group K Endpoint Devices Group J

With respect to Class N, the term device refers to an intelligent, addressable device that performs a programmable input or output function. Examples of Class N devices include: (1) Input components such as alarm initiating modules switches and sensors, (2) Output components such as output modules, Ethernet speakers (i.e., IEEE 802.3af PoE speakers), intelligent strobes, textual signage, and intelligent audio amplifiers. Transmission equipment components (e.g., media converters, Ethernet switches, patch panels, crossconnects) are connected to the Class N pathway merely to transport instructions between other equipment. As such, they are not considered devices with respect to Class N pathways. The audio amplifier listed above is an example of an addressable device that can receive a digital audio input from the Class N pathway and then provide a notification appliance circuit (NAC) output with Class A, B, or X pathways. Other endpoint devices may similarly provide alternate Class pathways for strobes (NACs) or initiating devices (IDCs). From the perspective of the Class N pathway, communications terminates at this endpoint device. However, since these types of endpoints can support multiple notification appliance devices or initiating devices, they are subject to the redundant pathway requirement. Class N connections between control equipment are required to have redundant monitored pathway segments if a failure of a primary pathway segment in between control equipment could impair the operation of the control equipment [see Figure A.12.3.6(1)(b) ]. Figure A.12.3.6(1)(b) Class N Pathway Block Diagram with Multiple Control Units. Switch 1 FACU, ACU, or ECCU (1) FACU, ACU, or ECCU Switch 2 (2) Switch 3 FACU, ACU, or ECCU Figure A.12.3.6(1)(b) (3)

Class N is also permitted to include dual port devices that provide both transmission and input/output functions. Endpoint devices may have multiple connection ports and support dual pathway segment connections; thus the term endpoint device is not intended to prohibit more than one connection to a device. Even with dual connections, where other devices depend on the path, primary and redundant paths are required. But, where an endpoint device has two connection ports, and when a secondary nonrequired connection is added, there is no requirement to separately supervise the nonrequired redundant pathway segment [see Figure A.12.3.6(1)(c)]. Figure A.12.3.6(1)(c) Class N Pathway Block Diagram with Device with Dual Pathway Connection. To FACU Switch Endpoint Devices A nonrequired redundant cable to an endpoint device is permitted, and does not require separate supervision. Figure A.12.3.6(1)(c)

83 of 346 5/19/2014 11:24 AM Public Comment No. 196-NFPA 72-2014 [ Section No. A.12.3.6(1) ]

84 of 346 5/19/2014 11:24 AM A.12.3.6(1)

85 of 346 5/19/2014 11:24 AM Class N consists of pathways between control equipment and devices. The pathways comprise metallic conductor communications cable, such as a 100 ohm balanced twisted-pair (e.g., Category 5E), including single-pair or multi-pair cable, or other communications media such as optical fiber cable or wireless transmission, or a combination of two or more of these. Pathways consist of uninterrupted communications media between control equipment and an endpoint device or of a network of multiple interconnected communications media pathway segments connecting multiple devices. Media pathway segments are created by the use of transmission equipment such as Ethernet switches, wireless repeaters, or media converters that interrupt an otherwise continuous pathway. Requirements for Class N pathway transmission equipment are not covered in Chapter 12 but by other chapters in NFPA 72. Addi onal informa on concerning cabling and cabling infrastructure for Class N systems can be found in standards, such as ANSI/BICI 005, Electronic Safety and Security (ESS) System Design and Implementa on Best Prac ces. A network of pathway segments is also described as primary pathway segments, redundant pathway segments, or nondesignated pathway segments. Primary and redundant pathways, from control equipment to each device, are independently and continuously verified for their ability to support end-to-end communications to and from each endpoint device. Each device will be provided a primary pathway consisting of one or more pathway segments. For primary pathway segments that service more than one device, additional redundant pathway segments provide alternate verified communication pathways to the devices. Should any primary pathway segment fail, communication is supported by the redundant pathway segments. Should either a primary or redundant pathway segment fail, trouble will be indicated by virtue of the continuous verification of all primary and redundant pathway segments. The redundant pathway segments are generally independent and do not normally share media with the primary pathways. However, there are exceptions, such as different frequencies for wireless or ring topologies. [See A.12.3.6(5).] There is an opportunity to enhance the robustness of a Class N network by providing physically distinct pathway segments (i.e., an alternate conduit, or cable tray route, or wireless transmission frequency range, or a combination of distinct media). It is also permissible to provide other nondesignated pathway segments. Additional pathway segments in excess of the minimum requirements of Class N increase the overall robustness of the network and are often desirable. However, since these additional pathway segments exceed the minimum equipment standards, there is no intention to create an additional monitoring burden, so verification of these pathways is optional. For Class N, where a conductor-based media is used, it is not the intention to monitor faults on individual conductors but rather to monitor the operational capability and performance of the pathway as a whole. Unlike Class C, where multiple pathways are not required, for Class N some pathway segments that carry communications for multiple devices (such as Ethernet uplinks or backbones) will have redundant pathway segments present. The intention is that any one pathway segment can fail without a loss in operational capability to more than one device. For example, connections to control equipment (fire alarm control units, ACUs, or ECCUs), where any interruption in communications could potentially affect all devices, would have redundant pathway segments. Additionally, backbone and uplink pathway segments that support communications for more than one device and are positioned between transmission equipment would also have a redundant pathway segment. But the requirement for redundant pathway segments does not apply to those pathway segments used to service a single device [see Figure A.12.3.6(1)(a)]. The term devices is used generically in this section to refer to endpoint devices, which include the following: (1) Input components such as alarm initiating switches, sensors (2) Output components such as Ethernet speakers (i.e., IEEE 802.3af PoE speakers), strobes, textual signage, audio amplifiers Transmission equipment (e.g., media converters, Ethernet switches, patch panels, cross-connects) are not considered devices with respect to Class N pathways. The audio amplifier example is included to explain a type of addressable device that can receive a digital audio input from the Class N pathway but provide a notification appliance circuit (NAC) output to support Class A, B, or X speaker connections. Other similar devices are also possible to provide alternate class pathway connections for strobes (NACs) or initiating devices (IDCs). From the perspective of the Class N pathway, this is considered an endpoint device. However, since these types of endpoints can support multiple notification appliance devices or initiating devices, they are subject to the redundant pathway segment requirement and are provided with dual pathway connections. Control equipment connected to a Class N network for communications with devices would generally utilize redundant pathway segments. Control equipment connected to other control equipment on a Class N network would utilize redundant pathway segments if the control equipment was dependent on any of the

86 of 346 5/19/2014 11:24 AM pathway segments so that a failure of a primary pathway segment in between control equipment could impair the operation of the control equipment [see Figure A.12.3.6(1)(b)]. Another utilization of endpoints is permitted for devices providing two connection ports and supporting dual pathway segment connections. The description of endpoint devices is not intended to exclude devices that support dual pathway connections. Since these pathways are servicing a single device, only a single primary pathway connection is required. The second pathway connection exceeds minimum equipment standards and is therefore not required to be verified as a redundant pathway segment; it can be considered connected to a nondesignated pathway segment [see Figure A.12.3.6(1)(c)]. Figure A.12.3.6(1)(a) Class N Pathway Block Diagram. Figure A.12.3.6(1)(b) Class N Pathway Block Diagram with Multiple Control Units. Figure A.12.3.6(1)(c) Class N Pathway Block Diagram with Device with Dual Pathway Connection.

87 of 346 5/19/2014 11:24 AM Statement of Problem and Substantiation for Public Comment This will provide an avenue for those wanting more information about the networking base of Class N without the need of creating additional Appendix material down the road. This Public Comment was submitted on behalf of Jeff Silveira of BICSI. Related Public Comments for This Document Related Comment Public Comment No. 174-NFPA 72-2014 [Section No. A.12.3.6(1)] Related Item Public Input No. 290-NFPA 72-2013 [New Section after A.12.3.5] Relationship Class N Annex Material Submitter Information Verification Submitter Full Name: Michael Pallett Organization: Telecor Inc. Street Address: City: State: Zip: Submittal Date: Thu May 15 22:29:49 EDT 2014

88 of 346 5/19/2014 11:24 AM Public Comment No. 197-NFPA 72-2014 [ Section No. A.12.3.6(1) ]

89 of 346 5/19/2014 11:24 AM A.12.3.6(1)

90 of 346 5/19/2014 11:24 AM Class N consists of pathways between control equipment and devices. The pathways comprise metallic conductor communications cable, such as a 100 ohm balanced twisted-pair (e.g., Category 5E), including single-pair or multi-pair cable, or other communications media such as optical fiber cable or wireless transmission, or a combination of two or more of these. Pathways consist of uninterrupted communications media between control equipment and an endpoint device or of a network of multiple interconnected communications media pathway segments connecting multiple devices. Media pathway segments are created by the use of transmission equipment such as Ethernet switches, wireless repeaters, or media converters that interrupt an otherwise continuous pathway. Requirements for Class N pathway transmission equipment are not covered in Chapter 12 but by other chapters in NFPA 72. A network of pathway segments is also described as primary pathway segments, redundant pathway segments, or nondesignated pathway segments. Primary and redundant pathways, from control equipment to each device, are independently and continuously verified for their ability to support end-to-end communications to and from each endpoint device. Each device will be provided a primary pathway consisting of one or more pathway segments. For primary pathway segments that service more than one device, additional redundant pathway segments provide alternate verified communication pathways to the devices. Should any primary pathway segment fail, communication is supported by the redundant pathway segments. Should either a primary or redundant pathway segment fail, trouble will be indicated by virtue of the continuous verification of all primary and redundant pathway segments. The redundant pathway segments are generally independent and do not normally share media with the primary pathways. However, there are exceptions, such as different frequencies for wireless or ring topologies. [See A.12.3.6(5).] There is an opportunity to enhance the robustness of a Class N network by providing physically distinct pathway segments (i.e., an alternate conduit, or cable tray route, or wireless transmission frequency range, or a combination of distinct media). It is also permissible to provide other nondesignated pathway segments. Additional pathway segments in excess of the minimum requirements of Class N increase the overall robustness of the network and are often desirable. However, since these additional pathway segments exceed the minimum equipment standards, there is no intention to create an additional monitoring burden, so verification of these pathways is optional. For Class N, where a conductor-based media is used, it is not the intention to monitor faults on individual conductors but rather to monitor the operational capability and performance of the pathway as a whole. Unlike Class C, where multiple pathways are not required, for Class N some pathway segments that carry communications for multiple devices (such as Ethernet uplinks or backbones) will have redundant pathway segments present. The intention is that any one pathway segment can fail without a loss in operational capability to more than one device. For example, connections to control equipment (fire alarm control units, ACUs, or ECCUs), where any interruption in communications could potentially affect all devices, would have redundant pathway segments. Additionally, backbone and uplink pathway segments that support communications for more than one device and are positioned between transmission equipment would also have a redundant pathway segment. But the requirement for redundant pathway segments does not apply to those pathway segments used to service a single device [see Figure A.12.3.6(1)(a)]. The term devices is used generically in this section to refer to endpoint devices, which include the following: Commonly, NFPA has used the word device for input components, and term appliance for components used in notification. With respect to Class N, the term device includes appliances and other intelligent, addressable components that perform a programmable input or output function. Examples of Class N devices include: (1) Input components such as alarm initiating switches, sensors (2) Output components such as Ethernet speakers (i.e., IEEE 802.3af PoE speakers), strobes, textual signage, audio amplifiers Transmission equipment (e.g., media converters, Ethernet switches, patch panels, cross-connects) are not considered devices with respect to Class N pathways. The audio amplifier example is included to explain a type of addressable device that can receive a digital audio input from the Class N pathway but provide a notification appliance circuit (NAC) output to support Class A, B, or X speaker connections. Other similar devices are also possible to provide alternate class pathway connections for strobes (NACs) or initiating devices (IDCs). From the perspective of the Class N pathway, this is considered an endpoint device. However, since these types of endpoints can support multiple notification appliance devices or initiating devices, they are subject to the redundant pathway segment requirement and are provided with dual pathway connections. Control equipment connected to a Class N network for communications with devices would generally utilize

91 of 346 5/19/2014 11:24 AM redundant pathway segments. Control equipment connected to other control equipment on a Class N network would utilize redundant pathway segments if the control equipment was dependent on any of the pathway segments so that a failure of a primary pathway segment in between control equipment could impair the operation of the control equipment [see Figure A.12.3.6(1)(b)]. Another utilization of endpoints is permitted for devices providing two connection ports and supporting dual pathway segment connections. The description of endpoint devices is not intended to exclude devices that support dual pathway connections. Since these pathways are servicing a single device, only a single primary pathway connection is required. The second pathway connection exceeds minimum equipment standards and is therefore not required to be verified as a redundant pathway segment; it can be considered connected to a nondesignated pathway segment [see Figure A.12.3.6(1)(c)]. Figure A.12.3.6(1)(a) Class N Pathway Block Diagram. Figure A.12.3.6(1)(b) Class N Pathway Block Diagram with Multiple Control Units. Figure A.12.3.6(1)(c) Class N Pathway Block Diagram with Device with Dual Pathway Connection.

92 of 346 5/19/2014 11:24 AM Statement of Problem and Substantiation for Public Comment This proposal was submitted after an email discussion by the Class N Correlating Committee Task Group members that was comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of the committees. There was no consensus reached on this proposal. Some suggested that unofficially, we have trended over the past 25 years to use device on the input side and appliance on the output side. Thus, initiating devices and notification appliances. And while this is true, it does not address the very many examples that can be found when the word "device" is used in some other context, including the context where both initiating devices and notification appliances are meant at the same time. In the code we already refer to UPS s as devices, radio transmitters as devices, circuit breaker locks as devices, overcurrent protection devices, emergency control interface devices, light output for signaling devices for hearing impaired, power supervisory devices, and generally fire alarm devices connected to fire alarm circuits. We also refer to devices for testing and maintenance requirements which is not limited to initiating devices only. There are also requirements for power supplied to devices over an SLC that are intended to cover both addressable initiating devices and notification appliances although the code only references these as devices. So there is no rule that devices always means initiating devices but if we want to state that traditionally or commonly the term is associated with initiating device it may be misleading and doing a disservice to generalize something that is not really true to people to who have not been deeply engaged with the code for many years. Related Public Comments for This Document Related Comment Public Comment No. 174-NFPA 72-2014 [Section No. A.12.3.6(1)] Public Comment No. 196-NFPA 72-2014 [Section No. A.12.3.6(1)] Related Item Public Input No. 290-NFPA 72-2013 [New Section after A.12.3.5] Relationship Class N Annex Material Class N Annex Material Submitter Information Verification Submitter Full Name: Michael Pallett Organization: Telecor Inc. Street Address: City:

93 of 346 5/19/2014 11:24 AM State: Zip: Submittal Date: Thu May 15 22:38:29 EDT 2014

75 of 346 5/19/2014 11:24 AM Public Comment No. 191-NFPA 72-2014 [ Section No. A.12.3.6(4) ] A.12.3.6(4) The operational conditions of the pathway include factors such as latency, throughput, response time, arrival rate, utilization, bandwidth, and loss. It is intended that the life safety equipment connected to a Class N network actively monitor some or all of the pathway s operational conditions, so that an improperly installed or configured pathway, or a subsequently degraded pathway or network of pathway segments is detected by the life safety equipment and reported as a trouble. This monitoring is intended to be continuous so that a degradation of pathway performance over time is detected and reported. Trouble would be reported when operational conditions of the pathway(s) have deteriorated to the point where the equipment is no longer capable of meeting its minimum performance requirements, even if some level of communication to endpoint devices is still maintained. Examples of performance requirements include the activation of an alarm within 10 seconds, the reporting of a trouble signal within 200 seconds, synchronization of strobes, and delivery of audio messages with required intelligibility. It is possible to have a pathway where end-to-end communications are operational under system idle conditions, but in the event of an alarm, the increased load on a degraded pathway could cause a partial or complete failure to deliver required life safety signals. This is the situation that is intended to be actively detected and reported. Statement of Problem and Substantiation for Public Comment Editorial and organizational changes for improved readability and clarity. The proposal is the recommendation by the Correlating Committee Task Group members that was comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of the committees. Wayne Moore A.J. Capowski Joe L. Collins Dan Horon Vic Humm Michael Pallett Charles Pugh Robert Schifiliti Aviv Siegel Larry Shudak Bob Elliott Paul Crowley Jeff Silveira Jeff Knight Andrew Berezowski Related Public Comments for This Document Related Comment Public Comment No. 174-NFPA 72-2014 [Section No. A.12.3.6(1)] Related Item First Revision No. 103-NFPA 72-2013 [Global Input] Relationship Class N Annex material Submitter Information Verification Submitter Full Name: Michael Pallett Organization: Telecor Inc. Street Address: City:

76 of 346 5/19/2014 11:24 AM State: Zip: Submittal Date: Thu May 15 18:08:06 EDT 2014

78 of 346 5/19/2014 11:24 AM Public Comment No. 193-NFPA 72-2014 [ Section No. A.12.3.6(5) ]

79 of 346 5/19/2014 11:24 AM A.12.3.6(5) Devices with dual path connections are permitted to be connected to create in a daisy? chain of devices on a ring. In this circumstance they cannot be considered endpoint devices because each pathway segment supports multiple devices; therefore Again, where Class N pathway segments support multiple devices, verified redundant pathway segments would be necessary segment(s) are required. This can be accomplished with a ring topology, as long as each segment of the ring is verified as functional, and the failure of any one segment does not result in the loss of functionality of more than one device. In this circumstance the requirements for Class N are satisfied by allowing the arrangement, primary and redundant pathway segments to share the same media by providing, and provide two possible directions of communications on in a ring topology [see Figure A.12.3.6(5) ]. This configuration is fully compliant with 12.3.6 (5).The daisy daisy? chain configuration is also a permissible connection method for permitted between multiple control units that require verified primary and redundant pathway segments. Figure A Figure A.12.3.6(5) Class Class N Pathway Block Diagram with Dais Daisy Chained Devices with Dual Pathway Connection. Additional Proposed Changes

80 of 346 5/19/2014 11:24 AM File Name Description Ap Final_Class_N_Pathway_Block_Diagram_with_Daisy_Chained_Devices_with_Dual_Pathway_Connection.png Figure a.12.3.6(5) Statement of Problem and Substantiation for Public Comment Editorial and organizational changes for improved readability and clarity. Drawing were changed to make the style more similar to Annex F. The proposal is the recommendation by the Correlating Committee Task Group members that was comprised of TC members from Chapters 10, 14, 23, 24 and 26 as well as individuals outside of the committees. Wayne Moore A.J. Capowski Joe L. Collins Dan Horon Vic Humm Michael Pallett Charles Pugh Robert Schifiliti Aviv Siegel Larry Shudak Bob Elliott Paul Crowley Jeff Silveira Jeff Knight Andrew Berezowski Related Public Comments for This Document Related Comment Public Comment No. 174-NFPA 72-2014 [Section No. A.12.3.6(1)] Public Comment No. 191-NFPA 72-2014 [Section No. A.12.3.6(4)] Related Item First Revision No. 103-NFPA 72-2013 [Global Input] Relationship Class N Annex Material Class N Annex Material Submitter Information Verification Submitter Full Name: Michael Pallett Organization: Telecor Inc. Street Address: City: State: Zip: Submittal Date: Thu May 15 21:41:54 EDT 2014

0 of 346 5/19/2014 11:24 AM Public Comment No. 17-NFPA 72-2014 [ New Section after 12.6.16 ] 12.6.17 Where fire alarm control units are interconnected by an auxiliary alarm, supervisory, or trouble relay that uses clip-on or slide-on type terminals, the circuit shall be configured to provide supervision of the terminals so that their detachment from the auxiliary relay will result in a trouble indication at the master fire alarm control unit. EW CONTENT Type your content here... Additional Proposed Changes File Name Description Approved NFPA_571.pdf Clip-on terminal strip Statement of Problem and Substantiation for Public Comment Statement of Problem and Substantiation for Public Input Several fire alarm panel manufacturers utilize "slip-on" or "clip-on" terminal strips for ease of maintenance. When this type terminal strip is used on output contacts for circuits supervised by another panel, the terminal strip can be removed without generating a signal. If the terminal strip is removed to facilitate service, it could be accidentally left off and prevent the transmission of signals. Related Item Public Input No. 571-NFPA 72-2013 [New Section after 12.6.17] Submitter Information Verification Submitter Full Name: Herbert Hurst Organization: Savannah River Nuclear Solutio Street Address: City: State: Zip: Submittal Date: Wed Mar 19 13:30:10 EDT 2014

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

0 of 346 5/19/2014 11:24 AM Public Comment No. 60-NFPA 72-2014 [ Section No. 21.1 ] 21.1* Application. The provisions of Chapter 21 shall cover the minimum requirements and methods for emergency control function interfaces to fire alarm systems and emergency communications systems in accordance with this chapter. 21.1.1 The requirements of Chapters 7, 10, 17, 18, 23, 24, and 26 shall apply, unless they are in conflict with this chapter. 21.1.2 The requirements of Chapter 14 shall apply. 21.1.3 The requirements of this chapter shall not apply to Chapter 29 unless otherwise stated. Statement of Problem and Substantiation for Public Comment CC NOTE: The following CC Note No. 8 appeared in the First Draft Report as First Revision No. 222, and is also related to Public Input No. 566. The correlating committee makes reference to 21.1.1 and the phrase ", unless they are in conflict with this chapter." Requirements should not conflict. Where deviations from the requirements of other chapters are warranted they should be identified and addressed through appropriate allowances in the code language. The correlating committee directs the SIG-PRO committee to review the requirements in Chapter 21 with consideration to resolving any identified conflicts with other chapters. Where changes are made they should be done without introducing new material in the second draft phase. In addition the committee should consider rewording 21.1.1 to positive language. For example: The requirements of chapters x, y and z shall apply unless otherwise noted in this chapter. Related Item First Revision No. 222-NFPA 72-2013 [Section No. 21.1] Public Input No. 566-NFPA 72-2013 [Section No. 21.1] Submitter Information Verification 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: Wed Apr 30 09:26:22 EDT 2014

5 of 346 5/19/2014 11:24 AM Public Comment No. 28-NFPA 72-2014 [ Section No. A.21.1 ] A.21.1 Fire alarm systems, signaling systems, and emergency communications systems are often part of a large, integrated system serving a building or area. Figure A.21.1 shows examples of individual systems that might be part of an integrated system. A fire alarm system might monitor the status of one of the other individual systems or provide a form of output to control another individual system, such as a smoke control system or an elevator controller. In some cases, the fire alarm system shares information and control in two directions with another individual system. NFPA 72 covers only the fire alarm or signaling system in the circuits powered by it, not any part of the other individual systems. See NFPA 3 and NFPA 4 for additional information on integrated systems. Figure A.21.1 Integrated Systems. Statement of Problem and Substantiation for Public Comment NFPA 3 also addresses intergrated systems. Related Item First Revision No. 222-NFPA 72-2013 [Section No. 21.1] Submitter Information Verification Submitter Full Name: Kelly Nicolello Organization: Western Regional Fire Code Dev Street Address: City: State: Zip: Submittal Date: Tue Apr 01 18:29:00 EDT 2014