technical committee on public emergency service ... · 09/28/2016 puf-aaa kennethj.link, jr....

TECHNICAL COMMITTEE ON

Public Emergency Service Communication

AGENDA

First Draft Meeting for NFPA 1221

October 19th-21st, 2016

Embassy Suites by Hilton Phoenix Tempe

9 AM -5 PM Day One-9 AM

1. Welcome. Stephen Verbil, Chair

2. Introductions and Update of Committee Roster. (Attached)

3. Approval of Pre-First Draft Meeting Minutes for NFPA 1221 from April 6th, 2016.

(Attached)

4. Staff Updates.

a. Committee membership update.

b. Annual 2018 revision cycle schedule review

c. First Draft Process Presentation

5. Formation of Task Groups

6. Assignment of Public Inputs (Attached) to Task Groups

7. Committee Review and Vote on Task Group Reports

8. Other/New Business

9. Schedule Next Meeting

10. Adjournment

Address List No PhonePublic Emergency Service Communication PUF-AAA

Curt Floyd09/28/2016

PUF-AAAStephen VerbilChairConnecticut Department of Emergency Services & PublicProtection1111 Country Club Road Middletown, CT 06457

E 4/1/1993PUF-AAA

Douglas M. AikenPrincipalLakes Region Mutual Fire Aid9 Bentley RoadMoultonborough, NH 03254International Municipal Signal AssociationAlternate: Jeffrey G. Knight

U 1/1/1992

PUF-AAAWilliam AmbrefePrincipalCity of BeverlyMunicipal Inspection56 Water StreetBeverly, MA 01915-5027

E 7/29/2005PUF-AAA

Charles M. BerdanPrincipalSmokeater Consulting8698 Elk Grove Boulevard, Suite 1FMB 115Elk Grove, CA 95624

SE 4/1/1997

PUF-AAAChristopher CarverPrincipalNational Emergency Number Association1700 Diagonal Road, Suite 500Alexandria, VA 22314National Emergency Number AssociationAlternate: Ty Wooten

U 08/03/2016PUF-AAA

Thomas DibernardoPrincipalSunrise Fire Rescue10440 West Oakland Park BoulevardSunrise, FL 33351

E 10/29/2012

PUF-AAAJay Dornseif, IIIPrincipalPriority Dispatch Corporation110 South Regent Street, Suite 500Salt Lake City, UT 84111

SE 7/28/2006PUF-AAA

Jerry EisnerPrincipalRedSky Technologies Inc. 333 N. Michigan Avenue, #1600Chicago, IL 60601

IM 07/29/2013

PUF-AAAJohn A. FacellaPrincipalPanther Pines Consulting, LLCPO Box 1295Raymond, ME 04071

SE 10/27/2009PUF-AAA

Debbie FoxPrincipalLouisville KY EMA Metrosafe410 South Fifth StreetLouisville, KY 40202

U 10/23/2013

PUF-AAAMark KrizikPrincipalMotorola, Inc.1301 East Algonquin Road (IL02-1254)Schaumburg, IL 60196

M 3/15/2007PUF-AAA

Steve LeesePrincipalAPCO International351 North Williamson BoulevardDaytona Beach, FL 32114Association of Public-Safety Communications OfficialsInternational Inc.

U 10/23/2013

PUF-AAAMinfei M. LengPrincipalBird Technologies GroupTXRX Systems 8625 Industrial ParkwayAngola, NY 14006

M 04/05/2016PUF-AAA

Scott LheureuxPrincipalPurvis Systems Inc.1272 West Main RoadMiddletown, RI 02842

M 10/23/2013

1



PUF-AAAKenneth J. Link, Jr.PrincipalUS Department of Homeland SecurityFederal Emergency Management AdministrationNDMS HHS16 Parkerson RoadEdison, NJ 08817

SE 07/29/2013PUF-AAA

Christopher H. LombardPrincipalSeattle Fire DepartmentSpecial Operations/Communications301 2nd Avenue SouthSeattle, WA 98104Alternate: Benjamin Mellon

U 4/5/2001

PUF-AAANathan D. McClure, IIIPrincipalAECOM Building Engineering20715 Timberlake Road, Suite 106Lynchburg, VA 24502

SE 7/29/2005PUF-AAA

Matthew MeierPrincipalCode Consultants2043 Woodland Parkway, Suite 300St. Louis, MO 63146

SE 12/08/2015

PUF-AAACarolina Y. MilanPrincipalVandenberg AFB Emergency Communication Center1172 Iceland Avenue, Bldg. 10660Vandenberg AFB, CA 93437

U 03/07/2013PUF-AAA

Thomas J. ParrishPrincipalTelgian Corporation15771 W-M36Pinckney, MI 48169-9717Alternate: Warren Burns

SE 8/2/2010

PUF-AAAToivo SariPrincipalCypress Creek Emergency Medical Services7111 Five ForksSpring, TX 77379

U 07/29/2013PUF-AAA

Keith D. SimpkinsPrincipalCounty of ChesterDepartment of Emergency Services911 Division601 Westtown Road, Suite 012West Chester, PA 19701

U 10/28/2014

PUF-AAAEvan E. Stauffer, Jr.Principal2800 Larkin RoadUpper Chichester, PA 19061-2204

SE 1/01/1982PUF-AAA

Rex Strickland, IIIPrincipalFairfax County Fire & Rescue Department4100 Chain Bridge Road, 4th Floor - Comm.Fairfax, VA 22030International Association of Fire Fighters

L 07/29/2013

PUF-AAAWilliam J. WattersPrincipalVerisk Analytics/Insurance Services Office, Inc.545 Washington BoulevardJersey City, NJ 07310-1607

I 04/08/2015PUF-AAA

Warren BurnsAlternateTelgian Corporation2615 South Industrial Park AvenueTempe, AZ 85282-1821Principal: Thomas J. Parrish

SE 08/17/2015

PUF-AAAJeffrey G. KnightAlternateCity of Newton Fire Department1164 Centre StreetNewton Centre, MA 02459-1539International Municipal Signal AssociationPrincipal: Douglas M. Aiken

U 10/20/2010PUF-AAA

Benjamin MellonAlternateSeattle Fire Department301 2nd Avenue SouthSeattle, WA 98104Principal: Christopher H. Lombard

U 03/07/2013

2



PUF-AAATy WootenAlternateNational Emergency Number Association1700 Diagonal Road, Suite 500Alexandria, VA 22314National Emergency Number AssociationPrincipal: Christopher Carver

U 10/23/2013PUF-AAA

Curt FloydStaff LiaisonNational Fire Protection Association1 Batterymarch ParkQuincy, MA 02169-7471

06/03/2014

3

NFPA 1221 Technical Committee Meeting Notes, 4/6/16, Quincy, MA

Called to Order at 0818 hours by Chair Steve Verbil

Start of the 2019 Edition Revision process. This is a Pre-First Draft

Meeting

o Goals

Vision of the next revision by the Chair

Create Task Groups

NFPA staff welcomed the group and gave a Facility Safety presentation

Members Present:

o Stephen Verbil - Chair

o Curt Floyd - NFPA

o Evan Stauffer

o William Watters

o Tovio Sari

o Mark Krizik

o Warren Burns –

Alternate to Tom

Parish

o Robert McMullen –

guest of Tom

DiBernardo

o Chris Lombard

o Jerry Eisner

o Tom DiBernardo

o John Facella

o Chuck Berdan

o Matthew Meier

o Keith Simpkins

o Bill Ambrefe

o Chris Carver –

Alternate for Ty

Wooten

o On Phone:

o Doug Aiken

o Carolina Milan

o Steve Leese

o Jay Dornseif

2

o Jeff Knight o Nate McClure

NFPA Overview

o New vision – increasing global outreach

o First Draft Schedule

Public Input Deadline 6/29/16

First Draft Ballot Out 1/25/17

Need to set first draft meeting – between July and

November

o Chair wants as much public input as possible

o Have to deal with the TIA we approved last cycle.

TIA – MLTS ALI - Eisner reviewed his proposal. Because this is a pre-draft

meeting, no motions or voting can occur. Aiken is not opposed to the

language, but feels this is out of the scope of the committee. Berdan

asked that this be a topic of discussion today. Carver added that apps are

a new technology that needs to be addressed. ATIS? General discussion

on the scope of the committee and it’s relationship to APCO and NENA

standards.

Welcome by Ken Willette NFPA Manager Public Fire Division

New Business

o Review of 9-1-1 failures recently – Eric County, Century Link,

etc.

o NFPA 1802 – new committee – portable radios – Facella reports

that they finished their first rough draft. Hopefully out for public

input the end of this year, first of next year.

o Lombard wants to add more discussion items:

text to 9-1-1

3

NPSTIC – 9-1-1 across national borders – Canada and

Mexico – how to transfer calls

Telephone CPR – tremendous save rate if it’s used

o NFPA 72 – Aikens reported that the Correlating Committee for

NFPA 72 looked at moving in-building antenna standards to

1221. They completely support it. Discussion on the benefits

and application of the standard.

o NG9-1-1 – What do we want to codify in 1221 about NG9-1-1?

Discussion on current state-owned examples in New England.

Issue related to capacity – what is the burst-capacity

needed?

Text – SMS is best effort delivery, which can be a problem.

LIS – Location Information Service – discussion on

differences with legacy ANI databases

o Generator Testing – 1221 refers to NFPA 110, which removed

the requirement of weekly load testing, and it’s now monthly.

Verbil getting questions about why the change.

Discussion on the frequency testing. Need to look at 110

standards.

Discussion about a requirement for 72 hour test every

three years.

o Call Processing

Lombard getting questions about 90 second 99% of the

time requirement. Also 7.2.2 has some components that

shouldn’t fall under the 90 seconds – CPR, penetrating

trauma, etc. Maybe set up a subset of EMD… NFPA 1710

also has some studies from NIST that stress the

4

importance of a shorter time. General discussion on when

dispatch starts.

NEAD database – a grant will be awarded today to develop

this database and tools on how to pinpoint a wireless calls.

An application that looks like ALI. Should be completed in

9 months. Discussion on how many sources of location

data is available.

o Task Group Assignments

Call Processing – Dornseif – Chair, Lombard, Sari, Carver,

Milan, Simpkins, DiBernardo, Leese, Berdan. Discussion

about in-person meeting with such a large committee.

Scope – Berdan - Chair, Eisner, Meier, Aiken, McClure.

Leese, Carver. Discussion on whether the Standards

Council needs to approve before we start work on the rest

of the document. Need to get this done ASAP so the rest

of the task groups. Definition of “public emergency

service communications system” needs to be worked on.

Disaster Resiliency – Stauffer - Chair, DiBernardo, Verbil,

Amberfe.

Cyber Security – Facella – Chair, Sari, Kriszk, McClure,

Lombard, Meier.

NG9-1-1 – Eisner - Chair, Berdan, Leese, Milan, Carver,

Simpkins. Won’t start until Scope is approved.

Task Groups have to have a public proposal into NFPA

before June 29th. Don’t want to wait until 1st Draft

Meeting.

RF – Facella – Chair, DiBernardo, Meier, Aiken

5

Next meeting: October 19-21. Tentatively the Embassy Suites in

Tempe, AZ.

Discussion on BDAs (Chapter 9). Facella, Meier and DiBernardo will

meet off-line to discuss possible changes.

First Net – Aiken gave an update.

Meeting adjourned at 1512 hours.

Respectfully Submitted,

Charles Berdan and Curt Floyd

Public Input No. 153-NFPA 1221-2016 [ Global Input ]

References to NFPA 72 requirements for Two-Way Radio Communications Enhancement Systemsshall be deleted from each section and the associated annex, all requirements for Two-Way RadioCommunications Enhancement Systems have been relacated to this document and the exerptedsections of NFPA 72 may have been deleted.

Statement of Problem and Substantiation for Public Input

References to NFPA 72 requirements for Two-Way Radio Communications Enhancement Systems shall be deleted from each section and the associated annex, all requirements for Two-Way Radio Communications Enhancement Systems.have been relocated to this document and the exerpted sections of NFPA 72 may have been deleted.

Submitter Information Verification

Submitter Full Name: Thomas Parrish

Organization: Telgian Corporation

Street Address:

City:

State:

Zip:

Submittal Date: Wed Jun 29 15:19:45 EDT 2016

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

1 of 189 7/22/2016 1:15 PM


When NFPA 70 is referenced do not reference a specific section unless there is a technical reasonto do that. Rather change the references to the applicable sections of NFPA 70.


This could lead to confusion as to application of NFPA 70 and how it functions under article 90.




Street Address:

City:

State:

Zip:



2 of 189 7/22/2016 1:15 PM


Per the Regs, the Technical Committee is required to review and reconsider the new defintions andcorresponding Annex A material that resulted from TIA 16-1 (Log #117).

Additional Proposed Changes

File Name Description Approved

TIA_1221_16_1.pdf TIA 16-1 (Log #1171)


Note: This public input originates from TIA 16-1 (Log #1171) issued by the Standards Council on August 18, 2015 and per the Regs, the resulting text of the TIA must be reconsidered by the Technical Committee during the next revision cycle.


Submitter Full Name: TC PUF-AAA

Organization: NFPA

Street Address:

City:

State:

Zip:

Submittal Date: Wed Apr 06 11:18:05 EDT 2016


3 of 189 7/22/2016 1:15 PM

Public Input No. 30-NFPA 1221-2016 [ Section No. 1.2 [Excluding any Sub-Sections] ]

The purpose of this standard shall be as follows:

(1) To specify operations, facilities, and communications systems that receive alarms from events fromthe public

(2) To provide requirements for the retransmission of such alarms events to the appropriate emergencyresponse agencies

(3) To provide requirements for dispatching of appropriate emergency response personnel

(4) To establish the required levels of performance and quality of installations of emergency servicescommunications systems


The use of "alarm" in this document is a artifact of 1221 when it was a fire alarm box standard and used strictly by fire departments. The change to a generic "emergency response" standard necessitates the change from "alarm" to "event" to make the standard more acceptable to non-fire agencies.


Submitter Full Name: Charles Berdan

Organization: Smokeater Consulting

Street Address:

City:

State:

Zip:

Submittal Date: Fri Jun 24 12:19:40 EDT 2016


4 of 189 7/22/2016 1:15 PM

Public Input No. 93-NFPA 1221-2016 [ New Section after 2.3 ]

2.3.8 APCO/NENA Documents

APCO/NENA-INF-005 Emergency Incident Data Document (EIDD) , February 2014


The industry is quickly adopting the APCO/NENA Emergency Incident Data Document (EIDD) (https://www.nena.org/?EIDD) as the preferred method for exchanging incident data between systems (such as between CAD systems). This is inserted into the reference list for the sake of the comment to the CAD section.BTW, I have tried to edit the "Submitter Name" to identify myself, but it does not allow me to change it. My name is Randy Richmond.


Submitter Full Name: [ Not Specified ]

Organization: Zetron, Inc.

Street Address:

City:

State:

Zip:

Submittal Date: Tue Jun 28 12:10:35 EDT 2016


5 of 189 7/22/2016 1:15 PM

Public Input No. 6-NFPA 1221-2016 [ Section No. 2.3.1 ]

2.3.1 ASTM Publications.

ASTM International, 100 Barr Harbor Drive, P.O. Box C700, West Conshohocken, PA 19428-2959.

ASTM E84, Standard Test Method for Surface Burning Characteristics of Building Materials,2014 2015 .


Date updates.


Submitter Full Name: Timothy Earl

Organization: GBH International

Street Address:

City:

State:

Zip:

Submittal Date: Tue Jan 05 10:25:42 EST 2016


6 of 189 7/22/2016 1:15 PM


2.3.6 UL Publications.

Underwriters Laboratories Inc., 333 Pfingsten Road, Northbrook, IL 60062-2096.

ANSI/UL 752, Standard for Bullet-Resistant Equipment, 2005, Revised 2010 2015 .


This proposal updates the UL Standards to the current referenced edition.


Submitter Full Name: Ronald Farr

Organization: UL LLC

Street Address:

City:

State:

Zip:



7 of 189 7/22/2016 1:15 PM


3.3.1* Alarm.

A signal or message from a person or device indicating the existence of an emergency or other situationthat requires action by an emergency response agency.

3.3.1.1* Alarm Data.

Digital information related to an alarm that contains the physical location of the alarm , callback number ofthe reporting party/system, and other explanatory information.






Street Address:

City:

State:

Zip:



8 of 189 7/22/2016 1:15 PM


3.3.6* Automatic Location Identification (ALI).

A series of data elements that informs the recipient of the location of the alarm an event .






Street Address:

City:

State:

Zip:



9 of 189 7/22/2016 1:15 PM


3.3.6* Automatic Location Identification (ALI).

A series of data elements that informs the recipient of the location of the alarm The automatic display at thePSAP of the caller’s telephone number, the address/location of the telephone and supplementaryemergency services information of the location from which a call originates .


The definition of ANI/ALI is new to this revision. I propose to harmonize the definition with that used by the National Emergency Number Association (NENA) from their Master Glossary (http://www.nena.org/?page=Glossary). This will prevent perpetuating a multitude of different definitions used in public safety communications.




Street Address:

City:

State:

Zip:



10 of 189 7/22/2016 1:15 PM


3.3.7* Automatic Number Identification (ANI).

A series of alphanumeric characters that informs the recipient of the source of the alarm an event .






Street Address:

City:

State:

Zip:



11 of 189 7/22/2016 1:15 PM



A series of alphanumeric characters that informs the recipient of the source of the alarm an event .






Street Address:

City:

State:

Zip:



12 of 189 7/22/2016 1:15 PM



A series of alphanumeric characters that informs the recipient of the source of the alarm Telephone numberassociated with the access line from which a call originates .


The definition of ANI/ALI is new to this revision. I propose to harmonize the definition with that used by the National Emergency Number Association (NENA) from their Master Glossary (http://www.nena.org/?page=Glossary). This will prevent perpetuating a multitude of different definitions used in public safety communications.




Street Address:

City:

State:

Zip:



13 of 189 7/22/2016 1:15 PM


3.3.12 CAD Terminal Workstation .

An electronic device that combines a keyboard and a display screen to allow exchange of informationbetween a telecommunicator and one or more computers in the system/network A computer system with agraphic user interface, keyboard, mouse and display monitor to facilitate input, retrieval and storage of calland dispatch information by a telecommunicator .


Revised definition to correspond with currently deployed CAD technology


Submitter Full Name: David Hammond

Organization: Mission Critical Partners

Street Address:

City:

State:

Zip:



14 of 189 7/22/2016 1:15 PM


3.3.13 Call Detail Recording (CDR).

A system that provides a record of each metadata for each call, including automatic number identification(ANI), trunk number, and answering attendant number; and the time of seizure, answer, anddisconnect/transfer.


Revised definition to correspond with currently deployed CAD technology.




Street Address:

City:

State:

Zip:



15 of 189 7/22/2016 1:15 PM


3.3.24* Computer-Aided Dispatch (CAD).

A combination of hardware and software that provides data entry, makes resource recommendations, andnotifies and tracks those resources before, during, and after alarms events , preserving records of thosealarms events and status changes for later analysis.






Street Address:

City:

State:

Zip:



16 of 189 7/22/2016 1:15 PM


3.3.36 Dispatching.

See 3.3.41, Emergency Alarm Event Processing/Dispatching.






Street Address:

City:

State:

Zip:



17 of 189 7/22/2016 1:15 PM


3.3.41* Emergency Alarm Event Processing/Dispatching.

A process by which an alarm event answered at the communications center creates a call for service andis transmitted to emergency response facilities (ERFs) or to emergency response units (ERUs) in the field.






Street Address:

City:

State:

Zip:



18 of 189 7/22/2016 1:15 PM

Public Input No. 145-NFPA 1221-2016 [ New Section after 3.3.42 ]

3.3.43 Emergency Power Supply System

A system consisting of a UPS, rectifier plant, engine driven generator and transfer switch designed tomonitor preferred and alternate load power source and provide desired switching of the load; and allnecessary control equipment to make the system functional. Emergency Power Supply Systems aredescribed in NFPA 110, Chapter 4.


Add definition of Emergency Power Supply System along with directing the user to the NFPA 110 Standard, and provide recommendations regarding the Class, Type and Level of the EPSS for Emergency Communications Facilities.

Related Public Inputs for This Document

Related Input Relationship

Public Input No. 25-NFPA 1221-2016 [Section No. 4.7.3]Common requirements relating to emergencypower supply system

Public Input No. 26-NFPA 1221-2016 [Section No. 4.7.4.1]Common requirements relating to emergencypower supply system

Public Input No. 27-NFPA 1221-2016 [Section No. 4.7.4.2[Excluding any Sub-Sections]]

Common requirements relating to emergencypower supply system




Street Address:

City:

State:

Zip:



19 of 189 7/22/2016 1:15 PM


3.3.44* Emergency Response Facility (ERF).

A structure or a portion of a structure that houses emergency response agency equipment or personnel forresponse to alarms events .






Street Address:

City:

State:

Zip:



20 of 189 7/22/2016 1:15 PM


3.3.46 Engine Driven Generator

A generator driven by an internal combustion engine providing emergency power in the event of a loss ofprimary power source.


Add definition of engine-driven generator to coincide with paragraphs in 4.7.4 Engine-Driven Generators and corresponding to requirements of an emergency power system as described in NFPA 110 Chapter 4.




Street Address:

City:

State:

Zip:



21 of 189 7/22/2016 1:15 PM


Event.

An emergency or other situation that requires action by an emergency response agency.

Event Data.

Digital information related to an event that contains the physical location of the event, callback number ofthe reporting party/system, and other explanatory information.






Street Address:

City:

State:

Zip:



22 of 189 7/22/2016 1:15 PM


3.3.53 Logging Voice Recorder.

A device that records voice conversations and automatically logs the time and date of such conversations;normally, a multichannel alarm and dispatch information. Alarm and dispatch information may includevoice, ANI, ALI, dispatch records, date, time, and other incident specific details: normally, a mulitchanneldevice that keeps a semipermanent semi-permanent record of operations.


Update to title and definition to reflect the current practices of recording all information pertaining to an event on a common platform to improve record recall and retention in the recording system.




Street Address:

City:

State:

Zip:



23 of 189 7/22/2016 1:15 PM


3.3.60 Monitoring for Integrity.

Automatic monitoring of circuits and other system components for the existence of defects or faults thatinterfere with receiving or transmitting data related to an alarm event .






Street Address:

City:

State:

Zip:



24 of 189 7/22/2016 1:15 PM


3.3.62* Multiple Line Telephone System (MLTS).

A system designed to aggregate more than one incoming voice communication channel for use by morethan one telephone. This includes network and premises based systems. E.g., Centrex, VoIP, as well asPBX, Hybrid, and Key Telephone Systems.


The definition of MLTS is new to this revision. I propose to more closely harmonize the definition with that used by the National Emergency Number Association (NENA) from their Master Glossary (http://www.nena.org/?page=Glossary). This will prevent perpetuating a multitude of different definitions used in public safety communications.




Street Address:

City:

State:

Zip:



25 of 189 7/22/2016 1:15 PM


3.3.64* Notification.

The time at which an event or alarm is received and acknowledged at a communications center.






Street Address:

City:

State:

Zip:



26 of 189 7/22/2016 1:15 PM


3.3.66 Operations Room.

The room in the communications center where events and alarms are received and processed andcommunications with emergency response personnel are conducted.






Street Address:

City:

State:

Zip:



27 of 189 7/22/2016 1:15 PM


3.3.71 Permanent Visual Record (Recording).

An immediately readable, not easily alterable print, slash, or punch record of all occurrences of statuschange

Audit Trail

A permanent, unalterable, readable record of each transaction taken in a CAD system. The record shallrecord date/time, user ID, initiating workstation ID, action taken. The record shall be made whether thetransaction is successful or not .


Recommend replacing the definition of Permanent Visual Record with the term and definition of "Audit Trail". The term and definition of "permanent visual record' appears to be outdated. The intent of this permanent record may be better reflected in the current audit trails maintained in CAD systems.




Street Address:

City:

State:

Zip:



28 of 189 7/22/2016 1:15 PM


Single-Point Facility Ground

A grounding system that provides a common earth reference for the grounding all electrical, structural,building and communications systems; providing an equilateral ground plane for the systems, facility andsite.


The single-point facility grounding system is critical to continued operations of emergency communications systems during adverse conditions. Separate or disparate earth references for electrical, structural, building and communications systems can cause harm to personnel, loss of life, loss of equipment and facility damage due to lightning strike or large power surge. The implementation of a single-point facility ground system is the best solution to help mitigate harm to personnel, critical infrastructure and equipment from lightning strikes and power surge in emergency communications facilities.

As referenced in NFPA 1221 A.4.7.7, the Army Technical Manual TM5-690 provides a good description of the need for a single-point facility ground for emergency communications facilities in Chapter 1, Paragraph D, included here in part:"The recommended grounding and bonding practices are designed to: (1) accomplish adequate fault and lightning protection, (3) support reliable signal and data transmission without noise coupling via safety grounds, (4) maintain the integrity of electromagnetic interference (EMI) control and electromagnetic pulse (EMP) hardness measures

The need for TEMPEST measures in a NFPA1221 Emergency Communications facility probably does not apply to most PSAPs, therefore item 2 from the original document was not included in this list.



Public Input No. 28-NFPA 1221-2016 [Section No. 4.9]




Street Address:

City:

State:

Zip:



29 of 189 7/22/2016 1:15 PM

Public Input No. 43-NFPA 1221-2016 [ Section No. 4.1.5.3.1 ]

4.1.5.3.1

The plan shall include the ability to reroute incoming event and alarm traffic to the alternate center and toprocess and dispatch alarms events at that center.






Street Address:

City:

State:

Zip:



30 of 189 7/22/2016 1:15 PM

Public Input No. 44-NFPA 1221-2016 [ Section No. 4.1.5.4 ]

4.1.5.4*

When operations are from the alternate communications center, receipt, transfer, processing, anddispatching of alarms and events in accordance with the requirements of this standard shall not bedependent on the functioning of any equipment at the primary communications center.






Street Address:

City:

State:

Zip:



31 of 189 7/22/2016 1:15 PM


4.7.3 Emergency Power Source Supply System .

4.7.3.1

The emergency power source shall power supply system shall consist of one or more engine-drivengenerators installed in accordance with NFPA 70, Article 701.

4.7.3.2

Upon failure of primary power, transfer to the standby emergency source shall emergency supplysystem shall be automatic.


Revise title and wording to coordinate with terminology used in NFPA 110, Standard for Emergency and Standby Power Systems. Maintaining common terminology to avoid potential conflict or confusion of requirements between standards.



Public Input No. 145-NFPA 1221-2016 [New Section after 3.3.42]




Street Address:

City:

State:

Zip:



32 of 189 7/22/2016 1:15 PM


4.7.4.1

Engine-driven generators shall conform with the provisions of Section 4.7, NFPA 37 and withNFPA 37 NFPA 110 .


Revised the term "engine generator" to "engine-driven generator" in keeping with the use of the term in this section. Incorporating compliance with NFPA 110 coordinates the performance requirements of the NFPA 110 with the installation and use requirements of NFPA 37.







Street Address:

City:

State:

Zip:



33 of 189 7/22/2016 1:15 PM

Public Input No. 27-NFPA 1221-2016 [ Section No. 4.7.4.2 [Excluding any Sub-Sections]

]

Engine-driven generators shall conform with the provisions of NFPA 110, Type 10, Level 1,Class 75 Class 72 .


Current text indicates a Class 75 engine-driven generator, or 75 hours of operating time before needing to be refueled or recharged (Reference NFPA 110, Paragraph 4.2). Changing the classification rating to Class 72 brings this requirement in line with NFPA 1221, Paragraph 4.7.4.12 which requires "Fuel to operate an engine-driven generator for 72 hours at full load...".







Street Address:

City:

State:

Zip:



34 of 189 7/22/2016 1:15 PM


4.7.7.1

The single-point facility grounding electrode system should, wherever possible, incorporate a buildingground ring in addition to the typical electrical service entrance ground electrode. In addition, thesingle-point facility grounding system shall, when possible, include the following to improve the dissipationcapabilities of the single-point facility ground:

Ground radials

Tower ground ring (where applicable)

Bonding laterals (where applicable)


The installation of a building ground ring may be considered optional on a typical building. However it is an important element of the single-point facility ground for an emergency communications facility. The building ground ring, and where applicable, tower ground ring, bonding laterals and grounding radials, improve the dissipation of lightning strikes at the facility.







Street Address:

City:

State:

Zip:



35 of 189 7/22/2016 1:15 PM


4.7.7.2

The single-point facility grounding system shall be designed and installed to provide not more than 10ohms earth reference, unless otherwise approved by the AHJ.


Emergency communications facilities, especially those with adjacent tower structures will benefit from the lower recommendation of 10 ohms earth reference as specified in the Army TM 5-690 referenced in A.4.7.7. The additional grounding recommended by this standard assist in the rapid dissipation of any lightning strikes, therefore providing improved protection for personnel, equipment and the facility.







Street Address:

City:

State:

Zip:



36 of 189 7/22/2016 1:15 PM


4.7.7.3

Telecommunications equipment, two-way radio systems, computers and other electronic equipmentdetermined by the AHJ to be essential to the operation of the communications center shall be bonded to thesingle-point facility ground system in accordance with NFPA 70, Article 647.


Revise number to be subordinate to suggested revised content in 4.7.7



Public Input No. 134-NFPA 1221-2016 [Section No.4.7.7]

Additional requirements for single-point faciltygrounding system

Public Input No. 135-NFPA 1221-2016 [NewSection after 4.7.7]







Street Address:

City:

State:

Zip:



37 of 189 7/22/2016 1:15 PM


4.7.7 * Single-Point Facility Grounding System.

Telecommunications equipment, two-way radio systems, computers, and other electronic equipmentdetermined by the AHJ to be essential to the operation of the communications center shall be bonded tothe Provide a single-point (common) facility ground grounding system for emergency communicationsfacilities in accordance with NFPA 70 NFPA 70 , Article 647 250 .


Statement clarifies the requirement to provide a single-point (common) facility grounding system in compliance with NFPA 70, Article 250.







Street Address:

City:

State:

Zip:



38 of 189 7/22/2016 1:15 PM

Public Input No. 28-NFPA 1221-2016 [ Section No. 4.9 ]

4.9 * Lightning.

Buildings that house communications centers shall have lightning protection that complies with NFPA 780.Lightning protection systems shall be bonded to the single-point facility grounding system.


Clarify requirement that the lightning protection systems are to be incorporated as part of the single-point facility grounding system for emergency communications facilities.



Public Input No. 29-NFPA 1221-2016[New Section after 3.3.93]

Common requirements supporting the implementation of asingle-point facility grounding system.




Street Address:

City:

State:

Zip:



39 of 189 7/22/2016 1:15 PM


5.3.4

All raceways or ducts entering buildings from underground duct systems shall be effectively sealed with anidentified sealing with sealing compound or other means acceptable to the AHJ to prevent moisture orgases from the underground duct system from entering the building. Cables entering building shall beinstalled in accordance with the requirements of NFPA 70, Article 770 and Article 800.


The word “identified” appears extraneous in this sentence as it does not indicate any standard or specification for which the compound is to be identified.

Adding reference to the requirements of NFPA 70 Article 770 and 800 coordinates the requirements of this section with the more complete requirements of the NEC.




Street Address:

City:

State:

Zip:



40 of 189 7/22/2016 1:15 PM


5.3.6

Cable joints Cable splices shall be made to provide and maintain: conductivity , optical continuity forfiber-optic cable insulation, and protection of all metallic conductors, shelds or armor; and continuityof fiber optic strands. The splice enclosure shall provide protection to the splices that is at least equal tothat afforded by the cables that are joined.


Revise the term “joints” to “splices” in keeping with adjacent paragraphs. Clarify/expound upon the requirement for protecting the cable splices. The phrase “optical continuity for fiber optic cable insulation” may not be accurate and is not clear on what it is intended to achieve.




Street Address:

City:

State:

Zip:



41 of 189 7/22/2016 1:15 PM

Public Input No. 83-NFPA 1221-2016 [ Section No. 5.5.2 [Excluding any Sub-Sections] ]

Where installed in buildings, conductors and fiber-optic cables shall be installed in accordance withNFPA 70 in any one of the following wiring methods:

(1) Electrical metallic tubing

(2) Intermediate metal conduit

(3) Rigid metal conduit

(4) Surface metal raceways

(5) Reinforced thermosetting resin conduit (RTRC)

(6) Cable Trays


The requirement to install all conductors and fiber optic cables in conduit or surface metal raceway may be cost prohibitive for many installations. The protection afforded by a cable tray system is sufficient for most inside plant cable installations. The additional protection of a continuous conduit system should be considered for specific applications in areas where cables may be subject to more extreme hazards.




Street Address:

City:

State:

Zip:



42 of 189 7/22/2016 1:15 PM


6.1.4

A publicly accessible means for reporting alarms events to the communications center shall be providedon the exterior of the ERF.






Street Address:

City:

State:

Zip:



43 of 189 7/22/2016 1:15 PM


6.5.1

Lighting shall be provided to enable personnel to operate communications equipment that is used for thereceipt of alarms and events .






Street Address:

City:

State:

Zip:



44 of 189 7/22/2016 1:15 PM


7.3.1.1*

The AHJ shall ensure that there are sufficient telecommunicators available to effect the prompt receipt andprocessing of alarms and events needed to meet the requirements of Section 7.4.






Street Address:

City:

State:

Zip:



45 of 189 7/22/2016 1:15 PM


Ninety-five percent of alarms events received on emergency lines shall be answered within 15 seconds,and 99 percent of alarms events received on emergency lines shall be answered within 40 seconds.(For documentation requirements, see 12.5.2 .)






Street Address:

City:

State:

Zip:



46 of 189 7/22/2016 1:15 PM


Ninety-five percent of alarms received on emergency lines shall be answered by a person within15 seconds, and 99 percent of alarms shall be answered by a person within 40 seconds. Automatedanswering of 9-1-1 lines by a pre-recorded system is prohibited. (For documentation requirements, see12.5.2.)


No 9-1-1 calls, by standard, should be put into a system that the caller believes they are on hold without initially having personal contact with a telecommunicator first.


Submitter Full Name: Chris Truty

Organization: Tri Lakes Monument FPD

Street Address:

City:

State:

Zip:

Submittal Date: Tue Jan 19 11:29:45 EST 2016


47 of 189 7/22/2016 1:15 PM


With the exception of the call types identified

in 7in 7 .4.2.2 ,

90 percent ofand for those calls where a response is required, emergency alarm processing

shall be completed within 64 seconds, and 95 percent of alarm processing shall be completed within106 seconds.will result the initial unit(s) being dispatched within 60 seconds 90 percent of the time, and 106 seconds95 percent of the time. (For documentation requirements,

seesee 12.5.2 .)


The portion of the standard that states "...alarm processing shall be completed..." has been misleading as to the original intent of the committee. The intent was in recognition that, while certain call types (see recommended changes to 7.4.2.2) dictate help should be sent as soon as possible (even with incomplete information), 9-1-1 call takers should continue to collect pertinent, call-related information as needed, without being penalized. Related studies pertaining to rapid dispatch of initial units include work done for NFPA 1710 (NIST studies on fire growth).


Submitter Full Name: Christopher Lombard

Organization: Seattle Fire Department

Street Address:

City:

State:

Zip:



48 of 189 7/22/2016 1:15 PM


With the exception of the call types identified in 7.4.2.2, 90 percent of emergency alarm processing shall becompleted within 64 seconds, and 95 percent of alarm processing shall be completed within106 seconds notification (dispatch) to responding units of the incident, call-type,and location shall be madewithin 64 seconds for 90 percent of emergency alarms and within 106 seconds for 95 percent of alarms .(For documentation requirements, see 12.5.2.)


This change is language is essential to clarify the time requirements for Communications Centers. Current use of the word "dispatch completed" implies that the call is able to be terminated at that point, with all information having been obtained. This does not recognize the ability of agencies to provide an initial dispatch and then remain on the line with the caller to obtain additional information or to provide pre-arrival instructions. The call is often not terminated (completed) until the arrival of resources, particularly with EMS calls. In addition, this revision to the language clarifies the importance of Dispatchers processing fire calls quickly and lessons confusion about the information required for an initial dispatch. (some call-taking programs require caller's name and call-back number before the call can be released, which adds a delay in the dispatch of resources)


Submitter Full Name: Christopher Carver

Organization: Natl Emerg Number Assoc

Street Address:

City:

State:

Zip:

Submittal Date: Thu Jun 23 12:32:25 EDT 2016


49 of 189 7/22/2016 1:15 PM


With the exception of the call types identified in 7.4.2.2, 90 percent of emergency alarm event processingshall be completed within 64 seconds, and 95 percent of alarm processing of emergencyevent processing shall be completed within 106 seconds. (For documentation requirements, see 12.5.2.)






Street Address:

City:

State:

Zip:



50 of 189 7/22/2016 1:15 PM

Public Input No. 15-NFPA 1221-2016 [ New Section after 7.4.2.2 ]

7.4.2.2 currently lists exceptions to standard 7.4.2 to allow additional processing time for incidentsthat may require more interrogation, etc. What if a single incident contains multiple exceptions to7.4.2? For example, you have a language issue, there is trouble with the caller providing anaddress, and the call requires EMD.

Although I agree that these types of exceptions should be given additional time, many of theseexceptions are difficult to measure. Is there any guidance or technology suggestions that can beprovided by NFPA or other agencies measuring these exceptions? At this time, we are measuringbased on signal type. We currently provide EMD on all medical calls, so those signals are alreadymeasured under 7.4.2.2. However, if we have a vehicle fire (or any other signal normally measuredunder 7.4.2) that involves an exception listed under 7.4.2.2 (e.g., address issue), and thereforeneeds to be measured under that standard instead, what are some methods that can be usedbeyond manually reviewing calls that failed the standard or searching CAD comments for commonphrases?


Clarification of the measurement requirements and/ or methods for standard 7.4.2.2 exceptions, including instances where multiple exceptions apply.


Submitter Full Name: Jenna Diplacido

Organization: Broward County

Affilliation: Office of Regional Communications and Technology

Street Address:

City:

State:

Zip:

Submittal Date: Mon Jun 13 14:00:51 EDT 2016


51 of 189 7/22/2016 1:15 PM


TITLE OF NEW CONTENT

For medical calls where a patient is determined to be unconscious/unresponsive and not breathing,bystander CPR shall be confirmed, or telephone CPR shall be initiated, and continued until emergencyresponders arrive at the patient.


Early initiation of CPR, within minutes of arrest, has been shown to increase patient survivability to hospital-discharge by almost 5% for every 30 seconds earlier that CPR starts.




Street Address:

City:

State:

Zip:



52 of 189 7/22/2016 1:15 PM


7.4.2.2

Emergency alarm processing for the following call types shall be completed within 90 seconds 90 percentof the time and within 120 seconds 99 percent of the time:

(1) Calls requiring emergency medical dispatch questioning and pre-arrival medical and medicalinstructions

(2) Calls requiring language translation

(3) Calls requiring the use of a TTY/TDD device or audio/video relay services

(4) Calls of criminal activity that require information vital to emergency responder safety prior todispatching units

(5) Hazardous material incidents

(6) Technical rescue

(7) Calls that require determining the location of the alarm due to insufficient information

(8) Calls received by text message

(9)



PC_10_Held.pdf PC 10 - Held


See attached document for the substantiation submitted with Public Comment NO. 10 that was held last cycle.


Submitter Full Name: TC PUF-AAA

Organization: NFPA

Street Address:

City:

State:

Zip:

Submittal Date: Wed Apr 06 12:00:50 EDT 2016


53 of 189 7/22/2016 1:15 PM


7.4.2.2

Emergency alarm processing for the following call types shall be completed within 90 seconds 90 percentof the time and within 120 seconds 99 percent of the time:

(1)

(2) Calls requiring

emergency medical dispatch questioning and pre-arrival medical instructions









The following emergency medical dispatch call types SHOULD be subject to the more stringent time standards listed in 7.4.2.-Penetrating chest trauma-Stroke-Cardiac related events-Seizures-Unconscious/unresponsive patients-Allergic reactions




Street Address:

City:

State:

Zip:



54 of 189 7/22/2016 1:15 PM


7.4.2.2

Emergency alarm processing Notification (dispatch) to responding units of the incident, call-type,andlocation for the following call - types shall be completed within 90 seconds 90 percent made within 90seconds, 90 percent of the time and within 120 seconds 99 percent 120 seconds 99 percent of thetime : . (For documentation requirements, see 12.5.2 .)

(1) Calls requiring emergency medical dispatch questioning and pre-arrival medical instructions








(9) Calls received from outside the normal area of responsibility or service area

(10) Calls requring use of the NENA PSAP Registry to determine appropriate PSAP and/or TransferLocation

(11) Calls received during a significant disaster which severely and significantly depletes availableresource; impacts local infrastructure and may result in changes to normal dispatch proceedures


This change in language clarifies the term "completion of dispatch" to acknowledge that many serious calls can be dispatched with the dispatcher remaining on the line to provide pre-arrival or other instructions. In addition, the 3 added special cases are common events that impact the processing time of communications centers and which should not degrade their ability to meet standards.


Submitter Full Name: Christopher Carver

Organization: Natl Emerg Number Assoc

Street Address:

City:

State:

Zip:

Submittal Date: Thu Jun 23 12:43:00 EDT 2016


55 of 189 7/22/2016 1:15 PM


7.4.2.2

Emergency alarm event processing for the following call types shall be completed within 90 seconds90 percent of the time and within 120 seconds 99 percent of the time:

(1) Calls requiring emergency medical dispatch questioning and pre-arrival medical instructions






(7) Calls that require determining the location of the alarm event due to insufficient information







Street Address:

City:

State:

Zip:



56 of 189 7/22/2016 1:15 PM

Public Input No. 51-NFPA 1221-2016 [ Sections 7.4.4, 7.4.5 ]

Sections 7.4.4, 7.4.5

7.4.4*

Where alarms events are transferred from the primary public safety answering point (PSAP) to asecondary answering point, the transfer procedure shall not exceed 30 seconds for 95 percent of allalarms events processed. (For documentation requirements, see 12.5.2.)

7.4.4.1

The PSAP shall transfer alarms events as follows:

(1) The alarm event shall be transferred directly to the telecommunicator.

(2) The answering transferring agency shall remain on the line until it is certain that the transfer iseffected.

(3) The transfer procedure shall be used on emergency 9-1-1 calls.

7.4.5

All alarms events , including requests for additional resources, shall be transmitted to the identifiedemergency response units over the required dispatch systems.






Street Address:

City:

State:

Zip:



57 of 189 7/22/2016 1:15 PM


7.4.7*

Records of the dispatch of emergency response units to alarms events shall be maintained in accordancewith the records retention policy of the AHJ and shall identify the following:

(1) Unit designation for each emergency response unit (ERU) dispatched

(2) Time of dispatch acknowledgment by each ERU responding

(3) Enroute time of each ERU

(4) Time of arrival of each ERU at the scene

(5) Time of patient contact, if applicable

(6) Time each ERU is returned to service






Street Address:

City:

State:

Zip:



58 of 189 7/22/2016 1:15 PM


7.4.9

The first emergency response unit that arrives at the location of the alarm event shall provide a briefpreliminary report on observed conditions to the communications center.






Street Address:

City:

State:

Zip:



59 of 189 7/22/2016 1:15 PM


Alarms Events that are transmitted over the required dispatch circuit(s) shall be automatically recorded,including the dates and times of transmission.






Street Address:

City:

State:

Zip:



60 of 189 7/22/2016 1:15 PM


7.7* Quality Assurance/Improvement.

Communications centers shall establish a quality assurance/improvement program to ensure theconsistency and effectiveness of alarm event processing.






Street Address:

City:

State:

Zip:



61 of 189 7/22/2016 1:15 PM


8.1* Telephone Receiving Equipment.

The provisions of Chapter 8 shall apply to facilities and equipment that are needed to receivealarms events .






Street Address:

City:

State:

Zip:



62 of 189 7/22/2016 1:15 PM


When a PSAP receives an emergency call for a location that is not in its jurisdiction or a call for an agencynot under the control of the PSAP, the PSAP shall transfer the call directly to the responsiblecommunications center, when possible. When transferring to another PSAP, a tandem transfer must beused so the caller ALI will follow the call.


When transferring to another PSAP by doing a tandem transfer the ALI will follow the call. The ALI will not follow the call if an administrative transfer is used.




Street Address:

City:

State:

Zip:



63 of 189 7/22/2016 1:15 PM


8.3.9

The PSAP shall have the ability to receive TEXT messages from the cell phone carriers.


As PSAPs prepare to support Next Generation 9-1-1 they must plan and install their systems to accept TEXT messages and other forms of content from the local cell phone carries. The ability to accept TEXT messages is one of the first steps in supporting NG9-1-1.




Street Address:

City:

State:

Zip:



64 of 189 7/22/2016 1:15 PM


On-Site Notification

The MLTS shall provide support for a mechanism of on-site notification that immediately provides on-sitestaff with the location of any device placing an emergency call to 9-1-1.


Calls to 9-1-1 are only a single facet to the problem. Access to the facility, deploying local assistance and situational awareness to the emergent event are critical points to any emergency. In most commercial buildings, 1st responders require assistance from local staff to respond to the site of the emergency. Notifying these responders is critical to the 9-1-1 call flow process.



Public Input No. 2-NFPA 1221-2015 [Section No. 8.6.2] Supportive requirement


Submitter Full Name: Mark Fletcher, ENP

Organization: Avaya

Street Address:

City:

State:

Zip:

Submittal Date: Sat Dec 19 14:57:34 EST 2015


65 of 189 7/22/2016 1:15 PM


LOCAL TERMINATION RESTRICTION / EXCEPTIONS

Except as allowed below, an MLTS Manager shall not install, configure, or maintain an MLTS to engage inLocal Termination of 9-1-1 calls.

(a)WHEN PERMITTED.—An MLTS Manager may configure an MLTS to locally terminate 9-1-1 calls if andonly if all of the following conditions obtain during periods in which the facility or facilities served by anMLTS are occupied:

(1)The point of termination to which an MLTS is configured to divert 9-1-1 calls is provisioned withredundant communications links from the MLTS, dimensioned in accordance with telecommunicationsindustry standards and best practices, to accommodate call volumes and call arrival patterns that can bereasonably anticipated on the basis of an historical traffic study or industry standards, if no historical datais available, for the facility or facilities served by the MLTS.

(2)The point of termination to which the MLTS is configured to divert 9-1-1 calls is staffed on a continuousbasis with qualified personnel trained as public safety telecommunicators in accordance with or in excessof the training requirements of the local Public Safety Answering Point to which a 9-1-1 call wouldotherwise be delivered if not locally terminated.

(3)The point of termination to which the MLTS is configured to divert 9-1-1 calls is provisioned with ameans of directly dispatching qualified emergency responders including duly authorized and sworn lawenforcement personnel, firefighters, and EMS units trained and equipped in accordance with the prevailingstandards of the community or communities within which the MLTS provides service to end users.

(4)The MLTS is configured to automatically re-route calls via the Public-Switched Telephone Network,using the dial-string “9-1-1”, to the local Public Safety Answering Point that would otherwise serve astation if it were operated by a local telephone subscriber in the event that a diverted call is not answeredwithin 25 seconds or the point of termination cannot be reached due to network or system failure oroverload.


When an MLTS operator intercepts or locally terminates an emergency call attempt from callers on the system, they must ensure that the response to those calls will be the same or greater than that would be provided by routing directly to 9-1-1 call takers. System redundancies must be utilized to ensure termination, overflow and alternate routing capabilities must also be provided to circumvent network issues, and staff must maintain the appropriate level of traingin and certification.



Organization: Avaya

Street Address:

City:

State:

Zip:



66 of 189 7/22/2016 1:15 PM


8.6.1*

Every MLTS shall be designed to allow any extension to dial 9-1-1 without the need to dial any digit toobtain a dial tone an outside line .


Most modern MLTSs will provide "dial tone" even before obtaining an outside line.




Street Address:

City:

State:

Zip:



67 of 189 7/22/2016 1:15 PM


8.6.2*

The MLTS shall outpulse or signal the public switched telephone network with a dialable telephone numberthat, when dialed, will reach the original 9-1-1 caller or alternatively a station that has knowledge of the9-1-1 call event and location through an adequate means of on-site notification .


Specifically requiring a callback to reach the originating station would require each device to have assigned to it a unique dial-able public telephone number and associated ALI record.This also assumes the device and individual is capable of answering a return call, that the area has remained safe and the individual making the call is still present, and the device itself has not been compromised by the emergent event. Building staff are in a much better position to respond to any questions from 9-1-1 personnel, and if alerted, can respond to the location of the incident to provide assistance.



Public Input No. 3-NFPA 1221-2015 [New Section after 8.6]



Organization: Avaya

Street Address:

City:

State:

Zip:



68 of 189 7/22/2016 1:15 PM


8.6.3.1*

The ALI associated with the ANI of used by the MLTS extension shall be sufficient to direct a response tothe 9-1-1 caller in an efficient manner and include, at a minimum, the civic address, building number, andfloor, except as provided in 8.6.3.2.


Use of the word 'of' in the original text suggests that each individual station has specific ANI associated directly with it. To retain uniqueness, directly associated ANI requires a unique Direct Inward Dial Telephone number be associated with each specific device. This is in direct conflict with the ability to use a zone or area based ANI/ALI record.



Organization: Avaya

Street Address:

City:

State:

Zip:

Submittal Date: Tue May 10 19:59:09 EDT 2016


69 of 189 7/22/2016 1:15 PM

Public Input No. 150-NFPA 1221-2016 [ Chapter 9 ]

Chapter 9 Dispatching Systems


70 of 189 7/22/2016 1:15 PM

Changes are summarized below:

9. 3 Radio Dispatching Systems.

9.3.1 General.

9.3. 1 .1 *

All radio communications shall comply with the rules and regulations governing wireless communicationsin the country of operation.

9.3.1.2

The communications center shall be equipped for radio communications with ERUs using subscriberradios.

9.3.1.2.1

Radio communication systems shall be designed to provide no less than 95 percent coverage of thejurisdictional area as defined by the AHJ, 95 percent of the time, with a 95 percent confidence factor.

9.3.1.2.2 *

Radio subscriber and outdoor coverage shall be sufficient to provide a delivered audio quality (DAQ) of3.0 for analog or digital systems.

9.3.1.3 *

A communications radio channel, separate from the radio dispatch channel, shall be provided for on-scenetactical communications.

9.3.1.4 *

At a minimum, the tactical communications channel identified in 9.3.1.3 shall be capable of operating inanalog simplex mode.

9.3.1.5 *

Trunked system talk groups shall be permitted to be used to provide on-scene tactical communications ifdesired by the AHJ, and but the provisions of 9.3.1.3 and 9.3.1.4 shall still apply.

9.3.1.6 *

Communications system design shall be such that a portable radio is capable of operating within thedispatch area outside of buildings without the use of mobile radio frequency (RF) amplifiers.

9.3.1.7

If the radio includes scanning capability, it shall have an automatic priority feature that causes the radioreceiver to revert automatically to its primary channel when the primary channel is being used.

9.3.1.8

A visual indication shall be provided indicating that the subscriber radio equipment is turned on.

9.3.1.9

With the exception of mobile and portable radios, radio antenna systems shall include surge arresters.

9.3.1.10

Radio communications equipment shall be capable of transmitting a distinctive alert tone for emergencytraffic as required in NFPA 1561.

9.3.2 Signaling and Control Systems.

9.3.2.1

Signaling and control systems that are used to alert a specific ERF(s) shall initiate distinctiveannouncement tones for various voice alarms.

9.3.2.2

Signaling and control systems shall use both polling and automatic transmission communications methodsand shall support redundant designs as required in 9.1.1.4.

9.3.2.3

If used for signal and control systems, Internet protocol (IP) wide-area networks shall comply with thefollowing [j1] :


71 of 189 7/22/2016 1:15 PM

(1) They shall comply with the communication methods of 9.3.2.2.

(2) If the primary network connector connection fails during operations, switchover to the secondnetwork connection shall be automatic, with audible and visual indicators to the telecommunicator.

(3) *The network path used shall be under the control of the AHJ [j2] .

9.3.3 Conventional Two-Way Voice Systems.

9.3.3.1 * Analog System Requirements.

Systems shall be equipped with a coded squelch system to minimize the reception of on-channel signals or interference.

9.3.3.2 Digital Conventional System Requirements.

Digital conventional systems shall comply with ANSI/TIA-102.BAAA, FDMA [j3] Common AirInterface .

9.3.3.3 Call Indicator.

A call indicator shall be provided for each conventional channel controller from the control center console.

9.3.4 Trunked Two-Way Voice Systems.

9.3.4.1 * Signaling Channel Concept.

9.3.4.1.1

The trunked system shall operate using a dedicated signaling control channel protocol concept embodiedin either a distinct RF channel used for control signaling only or embedded control signals in the voicechannels such that a dedicated RF channel for control signaling is not necessary but the same result iseffected affected . [j4]

9.3.4.1.2

System control messages and calls and mobile requests for service shall be transmitted to and from thesystem on the signaling channel.

9.3.4.1.3

Each unit shall send its unique discrete address identification to the system each time the unit transmits,regardless of whether the system is operating in the message trunking mode or transmission trunkingmode.

9.3.4.1.4

Mobile and portable units shall be capable of operating on at least five radio channels.

9.3.4.1.5 *

Mobile and portable units shall be capable of scanning trunked talkgroups and conventional channels witha user-selectable priority.

9.3.4.1.6

A system controller shall automatically assign all channels so that all system users (field units and consoledispatchers) shall have access to all voice channels via a system priority protocol.

9.3.4.1.7

Channel access time in single-site systems, assuming a channel is available, shall be less than 1 ⁄ 2 0.5 second [j5] .

9.3.4.1.8 * Priority Levels.

9.3.4.1.8.1

A minimum of eight levels of operational talkgroup priority shall be incorporated into the system.

9.3.4.1.8.2

Dispatch consoles shall be capable of elevating the operational priority of a talkgroup by one increment tofacilitate channel assignments in critical situations.

9.3.4.1.9 * Emergency Priority.

9.3.4.1.9.1

All field units in the system shall be capable of gaining access to the system within ¹ ⁄2 [j6] second ofactivation of an instantaneous emergency switch.


72 of 189 7/22/2016 1:15 PM

9.3.4.1.9.2

When a field unit activates the emergency function of the radio unit, the field unit ID shall be displayed atthe dispatch terminal, console, or both [j7] , and an audible alert shall be activated.

9.3.4.1.9.3

A separate voice channel from the dispatch voice channel shall be immediately assigned to handle theemergency communications regardless of system loading.

9.3.4.1.10 * Failure of Trunking System.

9.3.4.1.10.1

If the trunking system control fails, the system, at a minimum, shall revert to conventional repeateroperation while in failover mode [j8] .

9.3.4.1.10.2

ERUs that share trunked radio systems with other emergency or nonemergency services shall operate ona channel that is not shared with nonemergency users.

9.3.4.1.10.3

Standard operating guidelines shall be written to explain to field units, first responders, and radiodispatchers on the trunked radio system how to detect that the system is in failover mode and what revisedoperational procedures they are to adopt when the trunked system is in failover mode [j9] .

9.3.4.1.11 * Queuing of Request for Voice Channel.

9.3.4.1.11.1

If all available talking channels are assigned, the second- and lower precedence–level requests for atalking channel shall be placed in a queue according to the priority levels involved.

9.3.4.1.11.2

The queue shall cause the system to assign talking channels as they become available on a priority-levelbasis.

9.3.4.1.11.3

If multiple talkgroups with the same priority are in the queue, they shall be assigned a channel on a first-in-first-out (FIFO) basis.

9.3.4.1.11.4

The queuing protocol shall process and assign channels to requesting units that have been involved inrecent conversations [j10] before processing and assigning channels to units not involved in any recentconversations, assuming both talkgroups have equal priorities.

9.3.4.1.12

When any unit is placed into a system-busy queue, the unit requesting the channel shall be notifiedautomatically by the system when it assigns a channel to the unit.

9.3.4.1.13

All units operating within the same talkgroup shall receive both sides of every conversation addressed toor from the talkgroup.

9.3.4.1.14

Where required by the AHJ for mobile or portable units, the system shall provide a means for selectivelyalerting one unit from another unit or from a dispatch location.

9.3.4.1.15 Continuous Talkgroup Affiliation Notification.

9.3.4.1.15.1

The system shall broadcast a continuous update of the talkgroup channel assignments to all field unitswhose radios are turned on and are within the system’s coverage area .

9.3.4.1.15.2

Units that become activated during a n ongoing talkgroup conversation, or units that leave the systemcoverage and return, shall use the continuous update to immediately affiliate with their assigned talkgroup.

9.3.4.1.16 *

Whenever a field unit leaves the coverage of the signaling channel and attempts to access the system


73 of 189 7/22/2016 1:15 PM

using the push-to-talk (PTT) button, a n distinctive audible alert shall be sounded so that the userknows that they are outside the system’s coverage area .

9.3.4.1.17 * Individual Unit Disable.

9.3.4.1.17.1

Hardware and software that allow disablement of any mobile or portable unit(s) currently operating on thesystem shall be provided , to provide for system security in case units become lost or stolen .

9.3.4.1.17.2

Disablement of such a unit(s) shall be possible even if the system manager terminal or the console isinoperative.

9.3.4.1.18 *

The system shall allow a n AHJ authorized telecommunicator to initiate a change in the operatingtalkgroup of any field unit from a system manager terminal.

9.3.4.1.19 *

Where telephone interconnect has been provided as a part of the system, the system shall be configuredso that no telephone call prevents or delays any dispatch communications required by the AHJ.

9.3.4.1.20 Monitoring for Integrity.

9.3.4.1.20.1

A subsystem dedicated to monitoring the trunked system infrastructure backbone shall be provided.

9.3.4.1.20.2

Fault and status information, including information on the condition of base station repeaters andcontrollers, shall be accessible from a system manager terminal.

9.3.4.1.20.3

A means shall be provided that is capable of recording system problems as they occur including type ofproblem, date and time .

9.3.4.1.21 Console Call Indicator.

9.3.4.1.21.1

A call indicator shall be provided for each talkgroup controlled from the control center console.

9.3.4.1.21.2

When a channel is selected, the call indicator shall flash when audio is available being received from afield unit .

9.3.4.1.22

When required by the AHJ, the console shall operate in the full duplex mode so that a telecommunicatorcan simultaneously transmit to a trunked talkgroup and receive their response without releasing the PTTbutton.

9.3.4.1.23 Console Trunked Busy Indication.

9.3.4.1.23.1

If the telecommunicator attempts to make a call and all trunked channels are busy, a visual alert shall beinitiated at the console.

9.3.4.1.23.2

When the channel becomes available, the console shall automatically alert the telecommunicator with anaudible tone and “hold” the channel for the telecommunicator for 2 seconds to 4 seconds to allow thetelecommunicator time to activate a PTT for the appropriate talkgroup.

9.3.4.1.24 * Console Dispatch Preemption.

9.3.4.1.24.1

The system shall be configured so that no “busy” indication is received by a telecommunicator attemptingto access a talkgroup required for dispatch of an alarm.

9.3.4.1.24.2

If necessary, the requirement of 9.3.4.1.24.1 shall be met by preemption of the lowest-priority


74 of 189 7/22/2016 1:15 PM

communication on the system at the time of attempted access to the talkgroup.

9.3.4.1.25

The telecommunicator shall have the following capabilities:

(1) The telecommunicator shall be able to designate a higher tactical priority for certain talkgroups whichare controlled at their workstation.

(2) Designation of higher tactical priority shall be achieved by means of a switch on that talkgroup ’sappearance.

9.3.4.2 * Digital Trunked System Requirements.

Digital trunked systems shall comply with ANSI/TIA-102.BAAA, FDMA Common Air Interface , orTIA-102.BBAB, Project 25 Phase 2 Two-Slot Time Division Multiple Access Physical Layer ProtocolSpecification ; and with TIA-102.BBAC Project 25 Phase 2 Two-Slot TDMA Media Access Control LayerDescription and shall meet the requirements in 9.3.4. 1 [j11] .

9.3.5 * Two-Way Mobile Equipment.

9.3.5.1

All emergency response units shall be equipped with a two-way mobile radio that is capable ofcommunicating with the communications center [j12] .

9.3.5.2

Mobile radios shall be equipped with a visual transmit indicator.

9.3.5.3

All mobile radios shall be equipped with a carrier control timer that disables the transmitter and signals theoperator with a distinctive tone after a time predetermined by the AHJ.

9.3.5.4

Mobile radios and associated equipment shall be manufactured for the environment in which they are tobe used.

9.3.5.5

Mobile radios shall be capable of multiple-channel operation to enable on-scene simplex radiocommunications that are independent of dispatch channels to meet the requirements of 9.3.1.3 .

9.3.5.6

Spare mobile radio units shall be provided for emergency response units as follows:

(1) Minimum of one spare unit for each model not directly interchangeable [j13]

(2) Minimum of one spare unit for each 20 units, or fraction thereof, in service

9.3.6 * Two-Way Portable Equipment.

9.3.6.1

All ERUs shall be equipped with a portable radio that is capable of two-way communication with thecommunications center.

9.3.6.2

Portable radios shall be manufactured for the environment in which they are to be used and shall be of asize and construction that allow their operation with the use of one hand. For use in fire fighting applications including exterior, interior, and wildland, portable radios should meet NFPA 1802 standard[j14] .

9.3.6.3

Portable radios that are equipped with key pads that control radio functions shall have a means for theuser to disable the keypad to prevent inadvertent use.

9.3.6.4

All portable radios shall be equipped with a carrier control timer that disables the transmitter and signalsthe operator with a distinctive tone after a time predetermined by the AHJ.

9.3.6.5

Portable radios shall be capable of multiple-channel operation to enable on-scene simplex radiocommunications that are independent of dispatch channels to meet the requirements of 9.3.1.3 .


75 of 189 7/22/2016 1:15 PM

9.3.6.6

Portable radios shall be designed to allow channels to be changed and other radio functions controlledwhile emergency response personnel are wearing gloves of the type used in emergency responsefunctions . The glove size tested shall be large.

9.3.6.7

Single-unit battery chargers for portable radios shall be capable of fully charging the radio battery while theradio is in the receiving mode.

9.3.6.8

Battery chargers for portable radios shall automatically revert to maintenance charge when the battery isfully charged.

9.3.6.9

Battery chargers shall be capable of charging batteries in a manner that is independent of and external tothe portable radio [j15] .

9.3.6.10

Spare batteries shall be maintained in quantities that allow continuous operation during normal shifts or incase of a major incident as determined by the AHJ.

9.3.6.11

A minimum of one spare portable radio shall be provided for each 10 units, or fraction thereof, in service.

9.3.6.12 *

Portable radios used by first responders who might encounter hazardous locations because of thepresence of explosive gas or explosive dust atmospheres shall be rated as intrinsically safe for operationin such atmospheres by a nationally recognized testing laboratory, if determined necessary by the AHJ.

9.3.7 * Mobile Command Vehicles.

Vehicles that are used in command or communications functions shall meet the requirements ofNFPA 1901.

9.3.8 Backhaul [j16] Microwave Radio Systems.

9.3.8.1 General Requirements.

Microwave radio systems used for backhaul shall meet the following minimum requirements:

(1) The microwave radio shall be suitable for two-frequency, full-duplex operation.

(2) *The microwave radio shall be suitable for operating in network configurations offering ring or starprotection.

(3) The microwave radio shall include a transmitter, a receiver, a modem, a power supply, an automaticswitching device, a multiplexer, service channels/orderwire, and all associated interconnections [j17] .

(4) The microwave radio shall allow full access to all modules for normal system maintenance.

(5) All replaceable/plug-in modules shall be accessible.

9.3.8.2 Recovery and Protection.

9.3.8.2.1

Receivers shall provide both manual and fade initiated automatic errorless switching.

9.3.8.2.2

Recovery of a system from RF signal loss shall take place within 250 milliseconds after a valid signal isrestored.

9.3.8.2.3

The system shall be designed so that protection circuits and units not in service or operation can be testedand repaired without affecting on-line system operation.

9.3.8.2.4

Partial or complete failure of protection control or switching equipment shall not render the microwave linkinoperable.

9.3.8.3 Electromagnetic Interference.


76 of 189 7/22/2016 1:15 PM

9.3.8.3.1

The microwave equipment shall be operationally compatible with public safety communications equipmentco-located in the same equipment location.

9.3.8.3.2 *

The microwave equipment shall be capable of meeting full specifications when operating in the vicinity ofcommercial AM and FM radio and TV transmitters.

9.3.8.4 Environmental Considerations.

Microwave systems equipment shall function properly in the environmental conditions and at altitudes inwhich it is installed.

9.3.8.5 Microwave System Network Management.

9.3.8.5.1 * General.

The microwave system shall have sufficient alarm, control, and metering capabilities to detect defective orfailing components.

9.3.8.5.2 Fault and Failure History Log.

9.3.8.5.2.1

The microwave radio shall maintain an electronic file that records the date and time and type of fault/action of all fault and failure conditions and switching actions.

9.3.8.5.2.2

The file shall be downloadable for on-site review and for electronic communication s to others atremote locations .

9.3.8.5.3 Fault and Failure Indications.

Fault and failure conditions shall be displayed at the site and at a remotely monitored location.

9.3.8.5.4 External Alarms.

Each microwave radio assembly shall accommodate at least four (4) external site/housekeeping alarminputs.

9.4 Radio Alerting Systems.

9.4.1 General.

9.4.1.1

Radio alerting systems shall include one or more of the following:

(1) Voice receivers

(2) Coded receivers

(3) Noncoded receivers

(4) Numeric receivers

(5) Alphanumeric devices

(6) Two-way alphanumeric devices

9.4.1.2

Where radio home alerting receivers, portable radios, pagers, and similar radio devices are used toreceive alarms or are used on-scene, they shall conform to the requirements of this standard.

9.4.1.3

Where portable two-way radio equipment is used to receive fire alarms, such units shall be equipped toreceive a coded alert.

9.4.2 Radio Paging Systems and Pagers.

9.4.2.1 *

The paging system shall be under the direct control of the AHJ where used as a method of emergencydispatch.

9.4.2.2

No part of the paging system shall utilize the public Internet for any portion of its operation when used as a


77 of 189 7/22/2016 1:15 PM

method of emergency dispatch.

9.4.2.3

Page-encoding equipment shall be located in the communications center where used as a method ofemergency dispatch [j18] .

9.4.2.4

The paging system shall comply with the general requirements for radio systems as outlined in thisdocument.

9.4.2.5

Pagers shall audibly indicate a low-battery condition.

9.4.2.6

Alphanumeric pagers shall support the maximum text message that can be sent from the communicationscenter.

9.4.2.7 *

Coded receivers shall audibly indicate the presence of an unacknowledged message.

9.4.2.8

Alphanumeric devices and two-way alphanumeric devices shall audibly indicate the presence of an unreadmessage.

9.4.2.9

Two-way alphanumeric devices shall automatically transmit an acknowledgment when the device hasreceived and stored a message.

9.4.2.10

Two-way alphanumeric devices shall automatically transmit an acknowledgment when the responding userhas read the message.

9.4.2.11 *

Two-way alphanumeric devices shall be capable of providing and transmitting multiple-choice replies,manually selected by the user.

9.4.2.12 *

Status of the two-way alphanumeric devices, including messages sent and acknowledged, shall bemonitored in the operations room.

9.4.3 * Alerting Receivers.

Where radio alerting receivers are used to receive emergency dispatch messages, they shall be providedwith two sources of power.

9.5 Outside Audible Alerting Devices.

9.5.1

Outside audible alerting devices used to indicate an emergency shall be located to alert all emergencyresponse personnel expected to respond [j19] . r oot of 2 again??

9.5.2

Coded alerting devices shall operate at speeds of at least one actuation per second, with three or fourrounds of coded signals required where outside alerting devices are operated for summoning emergencypersonnel.

9.5.3

Compressed air alerting devices shall have a distinctive tone. If coded, the duration of the blast shall beneither less than ¹⁄ 2 [j20] second nor longer than ¹¹⁄2 seconds, with silent intervals of 1 to ¹¹⁄2 times theblast duration.

9.5.3.1

Storage tanks shall meet the following criteria:

(1) Storage tanks shall comply with ASME specifications for unfired pressure vessels.

(2) Storage tanks shall be equipped with safety relief valves.


78 of 189 7/22/2016 1:15 PM

(3) Storage tank size shall be such that, at 85 percent of working pressure, eight times the largestnumber of blasts assigned to any signal but not fewer than 50 blasts shall be capable of being sounded.

9.5.4

Compressors shall have the capacity to fill storage tanks to working pressure within 30 minutes.

9.5.4.1

Piping of ferrous materials shall be provided with scale traps that are accessible for cleaning.

9.5.4.2

All piping shall be arranged to allow inspection and repair.

9.5.5 IP Devices.

Where adopted by the AHJ, IP-enabled devices (e.g., smartphones, tablets, laptops) shall comply with therules and regulations governing wireless communications in the country of operation.

9.5.5.1

The communications center shall be equipped for IP-enabled two-way communications with the ERUsusing IP-enabled devices as determined by the AHJ.

9.5.5.2

IP-enabled devices shall be capable of fully charging the battery while in use.

9.6 Two-Way RadioCommunications Enhancement Systems.

9.6.1

All system components shall be designed, installed, tested, inspected, and maintained in accordance withthe manufacturers’ published instructions and the requirements of Section 9.6.

9.6.2

Pathway survivability levels shall be as described in Section 5.10. [ 72: 24.3.13.1]

9.6.2.1

Two-way radio communications enhancement systems shall comply with 9.6.2.1.1 through 9.6.2.1.4.[ 72: 24.3.13.8]

9.6.2.1.1 *

Where a two-way radio communications enhancement system is used in lieu of a two-way in-buildingwired emergency communications system, it shall have a pathway survivability of Level 1, Level 2, or Level3. [ 72: 24.3.13.8. 1 [j21] [j22] ]

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

9.6.2.1.1.1

The feeder and riser coaxial cables and any fiber optic cables shall be rated as plenum cables.[ 72: 24.3.13.8.1.1]

9.6.2.1.1.2

The feeder coaxial cables shall be connected to the riser coaxial cable using hybrid coupler devices of avalue determined by the overall design. [ 72: 24.3.13.8.1.2]

9.6.2.1.2

Where a two-way radio communications enhancement system is used in lieu of a two-way in-buildingwired emergency communications system, the design of the system shall be approved by the AHJ.[ 72: 24.3.13.8.2]

9.6.2.1.3 *

Riser coaxial cables shall be rated as riser cables and routed through a 2-hour–rated enclosure. Thesame holds true for any fiber optic cables used. [ 72: 24.3.13.8.3]

9.6.2.1.4

The connection between the riser and feeder coaxial cables shall be made within the 2-hour–ratedenclosure, and passage of the feeder cable in and out of the 2-hour–rated enclosure shall be fire-stoppedto 2-hour ratings. The same holds true for any fiber optic cables used. [ 72: 24.3.13.8.4]


79 of 189 7/22/2016 1:15 PM

9.6.3 *

Systems shall have lightning protection that complies with NFPA 780.

9.6.4

Systems that are used to comply with the requirements of Section 9.6 shall be tested in accordance with11.3.9 and 11.3.9.1.

9.6.5 Non-Interference and Non-Public Safety System Degradation.

9.6.5.1

No amplification system capable of operating on frequencies or causing interference on to frequenciesassigned to the jurisdiction by the licensing authority of the country of jurisdiction shall be installed withoutprior coordination and approval of the AHJ.

9.6.5.2

The building manager/owner shall suspend and correct equipment installations that degrade theperformance of the public safety radio system or public safety radio enhancement system.

9.6.5.3

Systems that share infrastructure with non-public safety services shall ensure that the coverage andperformance of the public safety communications channels are not degraded below the level ofperformance identified in 9.6.7 and 9.6.8, regardless of the amount of traffic carried by the non-publicsafety services.

9.6.6 Approval and Permit.

9.6.6.1

Plans shall be submitted for approval prior to installation.

9.6.6.2

At the conclusion of successful acceptance testing, a renewable permit shall be issued for the publicsafety radio enhancement system where required by the AHJ.

9.6.7 * Radio Coverage.

9.6.7.1

Radio coverage shall be provided throughout the building as a percentage of floor area as specified insection below [j23] through section on amplification components.

9.6.7.2

The system shall adhere to the maximum acceptable propagation delay standard provided by the AHJ.

9.6.7.3

Radio coverage shall be determined by the AHJ.

9.6.7.4 Critical Areas.

Critical areas, including fire command centers, fire pump rooms, exit stairs, exit passageways, elevatorlobbies, standpipe cabinets, sprinkler sectional valve locations, and other areas deemed critical by theAHJ, shall be provided with 99 percent floor area radio coverage.

9.6.7.5 General Building Areas.

General building areas shall be provided with 90 percent floor area radio coverage.

9.6.7.6 Amplification Components.

Buildings and structures that cannot support the required level of radio coverage shall be equipped with asystem that includes RF emitting devices that are certified by the radio licensing authority to achieve therequired adequate radio coverage.

9.6.8 * Signal Strength.

9.6.8.1 * Inbound.

A minimum inbound signal strength sufficient to provide usable voice communications, as specified by theAHJ, shall be provided throughout the coverage area. The inbound signal level shall be sufficient toprovide a minimum of DAQ 3.0 for either analog or digital signals.

9.6.8.2 Outbound.


80 of 189 7/22/2016 1:15 PM

A minimum outbound strength sufficient to provide usable voice communications, as specified by the AHJ,shall be provided throughout the coverage area. The outbound signal level shall be sufficient to provide aminimum of DAQ 3.0 for either analog or digital signals.

9.6.9 Isolation.

If a donor antenna exists, isolation shall be maintained between the donor antenna and all inside antennasto a minimum of 20 dB under all operating conditions.

9.6.10 System Radio Frequencies.

The public safety radio enhancement system shall be capable of transmitting all radio frequencies usedby public safety agencies , assigned to the jurisdiction as required by the AHJ assigned to thejurisdiction , and be capable of using any modulation technology in current use by the public safetyagencies in the jurisdiction as .

9.6.10.1 List of Assigned Frequencies.

The AHJ shall maintain a list of all inbound/outbound frequency pairs for distribution to system designers.

9.6.10.2 * Frequency Changes.

Systems shall be upgradeable to allow for instances where the jurisdiction changes or adds systemfrequencies to maintain radio system coverage as it was originally designed [j24] .

9.6.11 System Components.

9.6.11.1 * Component Approval.

RF emitting devices and cabling used in the installation of the public safety two-way radio communicationsenhancement systems shall be approved by the AHJ, and all RF emitting devices shall have thecertification of the radio licensing authority of that country and be suitable for public safety use prior toinstallation.

9.6.11.2 Component Enclosures.

All repeater, transmitter, receiver, signal booster components, optical to RF and RF to optical converters,external filters, and battery system components shall be contained in a NEMA4- or NEMA4X-typeenclosure(s).

9.6.11.3 RF Emitting Devices.

RF emitting devices shall meet the following requirements in addition to any other requirementsdetermined by the AHJ:

(1) RF emitting devices shall have the certification of the radio licensing authority in the country ofjurisdiction prior to installation.

(2) All RF emitting devices shall be compatible with both analog and digital communications, as requiredto be used by the radio licensing authority in the country of jurisdiction and the AHJ, simultaneously atthe time of installation.

9.6.12 Power Supplies.

At least two independent and reliable power supplies shall be provided for all RF emitting devices and anyother active electronic components of the system: one primary and one secondary.

9.6.12.1 Primary Power Source.

The primary power source shall be supplied from a dedicated branch circuit and comply with NFPA 72 .

9.6.12.2 Secondary Power Source.

The secondary power source shall consist of one of the following:

(1) A storage battery dedicated to the system with 12 hours of 100 percent system operation capacity

(2) An alternative power source of 12 hours at 100 percent system operation capacity as approved by theAHJ

9.6.12.3 Monitoring Integrity of Power Supplies.

Monitoring the integrity of power supplies shall be in accordance with 9.1.2.2.

9.6.13 System Monitoring.

9.6.13.1 Fire Alarm System.

The system shall include automatic supervisory signals for malfunctions of the two-way radio


81 of 189 7/22/2016 1:15 PM

communications enhancement systems that are annunciated by the fire alarm system in accordance withNFPA 72, and shall comply with the following:

(1) Monitoring for integrity of the system shall comply with NFPA 72 , Chapter 10.

(2) System supervisory signals shall include the following:

(a) Donor antenna malfunction

(b) Active RF emitting device failure

(c) Low-battery capacity indication when 70 percent of the 12-hour operating capacity has been depleted

(d) Any active [j25] s S ystem component failure

(3) Power supply supervisory signals shall include the following for each RF emitting device and activesystem component s :

(a) Loss of normal ac power

(b) Failure of battery charger

(4) The communications link between the fire alarm system and the two-way radio communicationsenhancement system must be monitored for integrity.

9.6.13.2 Dedicated Panel.

(1) A dedicated monitoring panel shall be provided within the fire command center to annunciate thestatus of all RF emitting devices and active system component locations [j26] . The monitoring panelshall provide visual and labeled indications of the following for each system component and RF emittingdevice:

(1) Normal ac power

(2) Loss of normal ac power

(3) Battery charger failure

(4) Low battery capacity (to 70 percent depletion)

(5) Donor antenna malfunction

(6) Active RF emitting device malfunction

(7) Active s S y y stem component malfunction

(2) The communications link between the dedicated monitoring panel and the two-way radiocommunications enhancement system must be monitored for integrity.

9.6.14 Technical Criteria.

The AHJ shall maintain a document of technical information specific to its requirements . This technicalinformation shall be kept in a secure place accessible to maintenance personnel but not accessible to thepublic. It that shall contain, as a minimum, the following:

(1) Frequencies required for the in-building enhancement system

(2) Location and effective radiated power (ERP) of radio sites used by the public safety radioenhancement system

(3) Maximum propagation delay (in microseconds)

(4) List of specifically approved system components

(5) Other supporting

[j1] Are we saying we are allowing the use of the public Internet for system control?? Given all of thesecurity issues of today with SCADA systems and the like, this seems like a very bad idea to sanction.This section ought to say such control and signaling systems shall be part of a private WAN controlledby the AHJ and not part of or connected to the public Internet.

[j2] Is this saying that the IP network is in fact a private WAN and not the public Internet? If yes,reword to make it more obvious.

[j3] This makes this a US centric standard. Is that what is desired?

[j4] I believe this needs to be re-written to state that only P25 Ph 1 or 2 trunking is suitable for publicsafety. Right now there are many competing systems being offered included TETRA, MPT 1327(analog), DMR, Nextden, OpenSky, etc. For purposes of interoperability mandating one air interface


82 of 189 7/22/2016 1:15 PM

makes sense. HOWEVER, this will make international adoption of the 1221 standard moreproblematic, so this needs discussion. See also 9.3.4.2 which specifies P25 trunking. Needsdiscussion.

[j5] Did we mean 0.5 sec??

[j6] Was this meant to be 0.5 sec??

[j7] I am not sure why there is a distinction between a dispatch terminal and a console??

[j8] The Annex material for this item needs to be re-done to reflect: a) some systems provide for 2levels of failover: first to isolated trunked sites, then to standalone repeater operation. In both cases,there is a significant reduction in traffic handling capability of the system, and field units need trainingand annual practice on how they will operate under such failover conditions.

[j9] Annual testing in failover mode for at least 1 hour to practice what to do-could be done onnon-emergency channels as a training exercise.

[j10] Do we want to specify a time frame-within 10 seconds or so?

[j11] Needs review

[j12] We are mandating using a mobile radio. If the system is designed for portable in the car use, orvehicles are equipped for ‘Convert-com’ operation, does this make sense?

[j13] I’m not sure this still makes sense. As long as they have 1 spare for every 20, the units can bereplaced. Many manufacturers use the Can-buss protocol which means the control head wiring wouldnot have to be replaced.

[j14] This standard should be issued within the 3 year time frame of our rev cycle. That standard willhave many specific provisions for fire that should supercede anything in 1221.

[j15] Meaning of this is unclear.

[j16] Need to add a definition

[j17] We are getting into a fair amount of detail here. Why??

[j18] A provision should be added to require a backup encoder at a different location to allow forpaging FRUs in case the main encoder at dispatch fails. Many agencies already provide for this.

[j19] Is this meant to cover sirens and the like? Almost no one uses it anymore except for severeweather and such.

[j20] Why are we using the square root 0f 2again?

[j21] Do we need to comment about fiber optic cable is included here or is it obvious? Also we needto add the issue raised in Sunrise FL re a sprinklered plenum area with cables within that area shouldbe considered having the required survivability rating. Check other paragraphs to ensure this iscovered similarly.

[j22] As defined in NFPA 72 sect. 12.4, the pathway survivability ratings 1-3 include sprinklers, 2hours, or both (in 3). Questions have arisen with regard to 1 hour and sprinklers, which seems to bemore survivability than Level 1 and hence is covered here. But a clarification might need to beconsidered because some have been confused.

[j23] Need paragraph references

[j24] Not easily done at VHF because of filters and non-standard Tx to Rx spacings. Maybe specifythis as applying to UHF, 700, 800 where the Tx to Rx is well defined??

[j25] Need to define this in the definitions section.

[j26] Do we mean which active component at which location??

END OF SUGGESTED CHANGES

9.1 Fundamental Requirements of Alarm Dispatching Systems.

9.1.1* General.


83 of 189 7/22/2016 1:15 PM

9.1.1.1

An alarm dispatching system shall be designed, installed, operated, and maintained to provide for thereceipt and retransmission of alarms.

9.1.1.2

The transmission of any trouble signal shall not interfere with the transmission and receipt of alarms.

9.1.1.3

The required number of dispatching circuits shall be in accordance with 9.1.1.3.1 through 9.1.1.3.3.

9.1.1.3.1

Jurisdictions that receive 730 alarms or more per year shall provide two separate and dedicated dispatchcircuits as follows:

(1) Separate primary and secondary dispatch circuits shall be provided for transmitting alarms.

(2) The failure of any component of the primary circuit shall not affect the operation of the secondarycircuit and vice versa.

9.1.1.3.2*

Jurisdictions that receive fewer than 730 alarms per year shall provide a minimum of one dedicateddispatch circuit for transmitting alarms.

9.1.1.3.3*

A circuit that terminates at a telephone handset only shall not be considered as fulfilling the requirementsfor a dispatch circuit. (See 9.2.2.2.)

9.1.1.4

The primary dispatch circuit shall be provided with one of, or a combination of, the following:

(1) Wired circuit, monitored for integrity in accordance with 9.1.2 through 9.1.2.4.3

(2)

(3)

(4)

(5) Microwave carrier channel, monitored for integrity in accordance with 9.1.2 through 9.1.2.5.2, with thefollowing features:

(6) Redundant transceivers at both ends of each microwave path

(7) Automatic switchover to the second transceiver if the first transceiver fails during operation

(8) Polling or self-interrogating digital data radio channel with the following features:

(9)

(10) Monitoring for integrity in accordance with 9.1.2 through 9.1.2.5.2


(12) Dedicated telephone circuit that is monitored for integrity in accordance with 9.1.2 through 9.1.2.4.3,excluding the following:

(13) Telephone connection through a public-switched telephone network

(14) Nondedicated phone lines

(15) Trunked radio system in compliance with 9.1.1.4(2) or 9.1.1.4(4)

9.1.1.5

* Nontrunked voice radio channel with duplicate system elements, with the following features:

Monitored for integrity as required by 9.1.2.6

In the event of a failure of the primary system, a means to switch to the secondary system thatis immediately available to the telecommunicator

* Redundant transceivers at each installed location


84 of 189 7/22/2016 1:15 PM

The secondary dispatch circuit shall not be required to be monitored for integrity.

9.1.1.5.1

The secondary dispatch circuit shall be provided with one of, or a combination of, the following:

(1) A wired circuit

(2)

(3) If radio is used for both the primary and secondary dispatch circuits, the following shall apply:

(4) The primary dispatch circuit shall comply with 9.1.1.4 .

(5)

(6) An approved dedicated telephone circuit

(7) Where a telephone dispatch circuit is used as a primary dispatch circuit, a telephone circuit shallnot be used as the required secondary dispatch circuit.

(8) A telephone connection through a public-switched telephone network via a regular dial-upmodem and nondedicated telephone line shall not be considered to be an approved dispatchcircuit.

(9)

9.1.1.6*

Where voice transmission is used as a dispatch method, the announcement for the emergency responseshall be preceded by an audible warning or alerting signal that differentiates the emergency from routinevoice traffic.

9.1.1.7

Alarms shall be retransmitted to ERFs or to ERUs in the field from the location at which alarms arereceived.

9.1.1.7.1

Alarms transmitted from the communications center shall be automatically received at ERFs and ERUs.

9.1.1.7.2

Dispatch methods shall provide for the operation of houselights or other auxiliary functions at the ERF asrequired by the AHJ.

9.1.1.8

Alarms that are transmitted over the required dispatch circuit(s) shall have the dates and times oftransmission automatically recorded at the communications center.

9.1.1.9

Audible devices shall be installed throughout the ERF to ensure that all emergency response personnel arealerted to alarms.

9.1.1.10

Equipment shall be provided to allow personnel to alert all other personnel in the ERF.

9.1.1.11

A means of acknowledging receipt of an alarm from the emergency response personnel to thetelecommunicator shall be provided.

9.1.2* Monitoring for Integrity.

Primary dispatch circuits and devices upon which transmission and receipt of alarms depend shall bemonitored constantly to provide prompt warning of trouble that impacts operation.

* A designated radio channel

* The secondary dispatch circuit shall consist of a separate radio system operating on aseparate channel with a separate receiver for the secondary circuit at each ERF.

* The dispatch signal circuit path for the secondary dispatch circuit specified in 9.1.1.5.1 (4)(a) shallbe separate and independent of the dispatch signal circuit path of the primary dispatch circuit from thedispatch console to separate control/relay switching equipment connection ports at the ERF.


85 of 189 7/22/2016 1:15 PM

9.1.2.1*

A polling or self-interrogating radio system shall be monitored hourly for integrity to ensure system reliability.

9.1.2.2

The primary and secondary power sources supplied to all required circuits and devices of the system shallbe monitored for integrity.

9.1.2.3

Trouble signals shall actuate an audible device and a visual signal located at a constantly attended location.

9.1.2.4

The audible alert trouble signals from the fault and failure monitoring mechanism shall be distinct from theaudible alert emergency alarm signals.

9.1.2.4.1

The audible trouble signal shall be permitted to be common to several monitored circuits and devices.

9.1.2.4.2

A switch for silencing the audible trouble signal shall be permitted if the visual signal continues to operateuntil the silencing switch is restored to the designated normal position.

9.1.2.4.3

The audible trouble signal shall respond to faults that occur on all other circuits prior to the restoration of thesilencing switch to the “normal” position.

9.1.2.5

Where dispatch systems use computer diagnostic software, monitoring of the primary dispatch circuitcomponents shall be routed to a dedicated terminal(s) that meets the following requirements:

(1) It shall be labeled and identified as “dispatch circuit integrity status.”

(2) It shall be located within the communications center.

(3) It shall not be used for routine dispatch activities.

9.1.2.5.1

The computer diagnostic software shall be capable of displaying and testing each circuit that can beelectronically monitored from the dispatch console to the station control unit or junction relay switchingequipment in the ERF.

9.1.2.5.2

Any fault or failure condition within the dispatch circuit path shall be displayed on the dedicated terminalscreen in a prominent (highlighted) fashion that satisfies the visual trouble signal requirement, and with anaudible trouble signal, referenced in 9.1.2.4 through 9.1.2.5.2, that actuates and sounds in accordancewith the type of dispatch circuit that is being monitored.

9.1.2.6*

The radio communications system shall be monitored in the following ways:

(1) Monitoring for integrity shall detect faults and failures in the radio communications system.

(2) Detected faults and failures in the radio communications system shall cause audible and visualindications to be provided to the telecommunicator and radio system manager at the time of signalactivation.

9.1.2.6.1

Monitoring for integrity of portable radios and radio equipment installed in an ERF and in emergencyresponse vehicles shall not be required.

9.2 Wired Dispatching Systems.

9.2.1 Wired Circuits — General.


86 of 189 7/22/2016 1:15 PM

9.2.1.1*

A separate tie circuit shall be provided from the communications center to each alternate communicationscenter or a PSAP.

9.2.1.2

Equipment shall be designed and installed so that it is capable of performing its intended function over therange of 85 percent to 110 percent of its rated voltage.

9.2.1.3

The normal operation of the system shall not require the use of a ground return to provide any essentialfunction.

9.2.1.3.1

Circuits that extend outside the communications center shall test free of grounds.

9.2.1.3.2

The ground connection shall be permitted to be used to provide function under abnormal line conditionswhere such use would not prevent the reception or transmission of a signal under normal conditions if thecircuit were accidentally grounded.

9.2.1.4

A public alarm reporting system circuit that enters an ERF and that is connected to automatic recording andsounding equipment shall be permitted to be one of the two required dispatch circuits.

9.2.1.5

In jurisdictions where fewer than 730 alarms per year are received or where all stations have recording andsounding devices that respond to each public reporting circuit, the second dispatch circuit shall not berequired; only the circuit that is monitored for integrity shall be required.

9.2.1.6

The following requirements shall apply to systems in which an alarm from a fire alarm box is automaticallytransmitted to fire stations and, if used, is transmitted to supplementary alerting devices (Type B system):

(1) Equipment shall be installed to automatically transmit alarms that are received from any publicreporting circuit to all emergency response facilities and, where employed, to outside soundingdevices.

(2) Control equipment shall allow any or all circuits to be individually connected to or disconnected fromthe repeating mechanism.

(3) Coded transmitting devices that use metal conductors shall be provided with a means to transfer thesignal from one dispatch circuit to another.

9.2.1.7

A wired dispatch circuit that is part of a public alarm reporting system shall meet the requirements ofNFPA 72 .

9.2.1.8

A wired circuit shall not be connected to alarm instruments in more than five emergency response facilities.

9.2.1.9

Coded signals shall be transmitted as follows:

(1) At a minimum rate of two strokes per second

(2) Over separate circuits at a rate that is suitable for such devices where outside alerting devices areemployed

9.2.1.10

Where wired voice dispatch circuits are used, each circuit shall be dedicated to each emergency responsefacility.


87 of 189 7/22/2016 1:15 PM

9.2.1.11

For coded and telegraphic systems, a permanent record that indicates the exact location from which thealarm is being received and an audible signal shall be required to indicate the receipt of an alarm.

9.2.1.12

Where telegraphic retransmission is used, the telecommunicator shall be permitted to enter dates andtimes manually where approved by the AHJ.

9.2.2 Telephone Circuits.

9.2.2.1

A telephone circuit that is used as one of the dispatch circuits shall meet the requirement in 9.1.1.4.

9.2.2.2

Where the primary or secondary dispatch circuit is a telephone dispatch circuit, it shall have voiceamplification with the following capabilities:

(1) It shall be equipped with a loudspeaker(s).

(2) The use of a handset shall automatically disconnect the loudspeaker(s) from the circuit(s).

9.3 Radio Dispatching Systems.

9.3.1 General.

9.3.1.1*

All radio communications shall comply with the rules and regulations governing wireless communications inthe country of operation.

9.3.1.2

The communications center shall be equipped for radio communications with ERUs using subscriberradios.

9.3.1.2.1

Radio communication systems shall be designed to provide no less than 95 percent coverage of thejurisdictional area as defined by the AHJ, 95 percent of the time, with a 95 percent confidence factor.

9.3.1.2.2*

Radio and outdoor coverage shall be sufficient to provide a delivered audio quality (DAQ) of 3.0 for analogor digital systems.

9.3.1.3*

A communications radio channel, separate from the radio dispatch channel, shall be provided for on-scenetactical communications.

9.3.1.4*

At a minimum, the tactical communications channel identified in 9.3.1.3 shall be capable of operating inanalog simplex mode.

9.3.1.5*

Trunked system talk groups shall be permitted to be used to provide on-scene tactical communications ifdesired by the AHJ, and the provisions of9.3.1.3 and 9.3.1.4 shall still apply.

9.3.1.6*

Communications system design shall be such that a portable radio is capable of operating within thedispatch area without the use of mobile radio frequency (RF) amplifiers.

9.3.1.7

If the radio includes scanning capability, it shall have an automatic priority feature that causes the radioreceiver to revert automatically to its primary channel when the channel is being used.

9.3.1.8

A visual indication shall be provided indicating that the radio equipment is turned on.


88 of 189 7/22/2016 1:15 PM

9.3.1.9

With the exception of mobile and portable radios, radio antenna systems shall include surge arresters.

9.3.1.10

Radio communications equipment shall be capable of transmitting a distinctive alert tone for emergencytraffic as required in NFPA 1561.

9.3.2 Signaling and Control Systems.

9.3.2.1

Signaling and control systems that are used to alert a specific ERF(s) shall initiate distinctiveannouncement tones for various voice alarms.

9.3.2.2

Signaling and control systems shall use both polling and automatic transmission communications methodsand shall support redundant designs as required in 9.1.1.4.

9.3.2.3

If used for signal and control systems, Internet protocol (IP) wide-area networks shall comply with thefollowing:

(1) They shall comply with the communication methods of 9.3.2.2.

(2) If the primary network connector fails during operations, switchover to the second network connectionshall be automatic, with audible and visual indicators to the telecommunicator.

(3)

9.3.3 Conventional Two-Way Voice Systems.

9.3.3.1* Analog System Requirements.

Systems shall be equipped with a coded squelch system to minimize interference.

9.3.3.2 Digital Conventional System Requirements.

Digital conventional systems shall comply with ANSI/TIA-102.BAAA, FDMA Common Air Interface.


A call indicator shall be provided for each conventional channel controller from the control center console.

9.3.4 Trunked Two-Way Voice Systems.

9.3.4.1* Signaling Channel Concept.

9.3.4.1.1

The trunked system shall operate using a dedicated signaling control channel protocol concept embodied ineither a distinct RF channel used for control signaling only or embedded control signals in the voicechannels such that a dedicated RF channel for control signaling is not necessary but the same result iseffected.

9.3.4.1.2

System control messages and calls and mobile requests for service shall be transmitted to and from thesystem on the signaling channel.

9.3.4.1.3

Each unit shall send its unique discrete address identification to the system each time the unit transmits,regardless of whether the system is operating in the message trunking mode or transmission trunkingmode.

9.3.4.1.4

Mobile and portable units shall be capable of operating on at least five radio channels.

9.3.4.1.5*

Mobile and portable units shall be capable of scanning trunked talkgroups and conventional channels with auser-selectable priority.

* The network path used shall be under the control of the AHJ.


89 of 189 7/22/2016 1:15 PM

9.3.4.1.6

A system controller shall automatically assign all channels so that all system users (field units and consoledispatchers) shall have access to all voice channels via a system priority protocol.

9.3.4.1.7

Channel access time in single-site systems, assuming a channel is available, shall be less than 1⁄2 second.

9.3.4.1.8* Priority Levels.

9.3.4.1.8.1

A minimum of eight levels of operational talkgroup priority shall be incorporated into the system.

9.3.4.1.8.2

Dispatch consoles shall be capable of elevating the operational priority of a talkgroup by one increment tofacilitate channel assignments in critical situations.

9.3.4.1.9* Emergency Priority.

9.3.4.1.9.1

All field units in the system shall be capable of gaining access to the system within 1⁄2 second of activationof an instantaneous emergency switch.

9.3.4.1.9.2

When a field unit activates the emergency function of the radio unit, the field unit ID shall be displayed atthe dispatch terminal, console, or both, and an audible alert shall be activated.

9.3.4.1.9.3

A voice channel shall be immediately assigned to handle the emergency communications regardless ofsystem loading.

9.3.4.1.10* Failure of Trunking System.

9.3.4.1.10.1

If the trunking system control fails, the system, at a minimum, shall revert to conventional operation while infailover mode.

9.3.4.1.10.2

ERUs that share trunked radio systems with other emergency or nonemergency services shall operate on achannel that is not shared with nonemergency users.

9.3.4.1.10.3

Standard operating guidelines shall be written to explain to field units, first responders, and radiodispatchers on the trunked radio system how to detect that the system is in failover mode and what revisedoperational procedures they are to adopt when the trunked system is in failover mode.

9.3.4.1.11* Queuing of Request for Voice Channel.

9.3.4.1.11.1

If all available talking channels are assigned, the second- and lower precedence–level requests for a talkingchannel shall be placed in a queue according to the priority levels involved.

9.3.4.1.11.2

The queue shall cause the system to assign talking channels as they become available on a priority-levelbasis.

9.3.4.1.11.3

If multiple talkgroups with the same priority are in the queue, they shall be assigned a channel on a first-in-first-out (FIFO) basis.

9.3.4.1.11.4

The queuing protocol shall process and assign channels to requesting units that have been involved inrecent conversations before processing and assigning channels to units not involved in any recentconversations, assuming both talkgroups have equal priorities.


90 of 189 7/22/2016 1:15 PM

9.3.4.1.12

When any unit is placed into a system-busy queue, the unit requesting the channel shall be notifiedautomatically by the system when it assigns a channel to the unit.

9.3.4.1.13

All units operating within the same talkgroup shall receive both sides of every conversation addressed to orfrom the talkgroup.

9.3.4.1.14

Where required for mobile or portable units, the system shall provide a means for selectively alerting oneunit from another unit or from a dispatch location.

9.3.4.1.15 Continuous Talkgroup Affiliation Notification.

9.3.4.1.15.1

The system shall broadcast a continuous update of the talkgroup channel assignments to field units.

9.3.4.1.15.2

Units that become activated during a conversation, or units that leave the system coverage and return, shalluse the continuous update to immediately affiliate with their assigned talkgroup.

9.3.4.1.16*

Whenever a field unit leaves the coverage of the signaling channel and attempts to access the systemusing the push-to-talk (PTT) button, an audible alert shall be sounded.

9.3.4.1.17* Individual Unit Disable.

9.3.4.1.17.1

Hardware and software that allow disablement of any mobile or portable unit(s) currently operating on thesystem shall be provided.

9.3.4.1.17.2

Disablement of such a unit(s) shall be possible even if the system manager terminal or the console isinoperative.

9.3.4.1.18*

The system shall allow a telecommunicator to initiate a change in the operating talkgroup of any field unitfrom a system manager terminal.

9.3.4.1.19*

Where telephone interconnect has been provided as a part of the system, the system shall be configuredso that no telephone call prevents or delays any dispatch communications required by the AHJ.

9.3.4.1.20 Monitoring for Integrity.

9.3.4.1.20.1

A subsystem dedicated to monitoring the trunked system infrastructure backbone shall be provided.

9.3.4.1.20.2

Fault and status information, including information on the condition of base station repeaters andcontrollers, shall be accessible from a system manager terminal.

9.3.4.1.20.3

A means shall be provided that is capable of recording system problems as they occur.

9.3.4.1.21 Console Call Indicator.

9.3.4.1.21.1

A call indicator shall be provided for each talkgroup controlled from the control center console.

9.3.4.1.21.2

When a channel is selected, the call indicator shall flash when audio is available.


91 of 189 7/22/2016 1:15 PM

9.3.4.1.22

When required by the AHJ, the console shall operate in the full duplex mode so that a telecommunicatorcan simultaneously transmit to a trunked talkgroup and receive their response without releasing the PTTbutton.

9.3.4.1.23 Console Trunked Busy Indication.

9.3.4.1.23.1

If the telecommunicator attempts to make a call and all trunked channels are busy, a visual alert shall beinitiated at the console.

9.3.4.1.23.2

When the channel becomes available, the console shall automatically alert the telecommunicator with anaudible tone and “hold” the channel for the telecommunicator for 2 seconds to 4 seconds to allow thetelecommunicator time to activate a PTT for the appropriate talkgroup.

9.3.4.1.24* Console Dispatch Preemption.

9.3.4.1.24.1

The system shall be configured so that no “busy” indication is received by a telecommunicator attempting toaccess a talkgroup required for dispatch of an alarm.

9.3.4.1.24.2

If necessary, the requirement of 9.3.4.1.24.1 shall be met by preemption of the lowest-prioritycommunication on the system at the time of attempted access to the talkgroup.

9.3.4.1.25

The telecommunicator shall have the following capabilities:

(1) The telecommunicator shall be able to designate a higher tactical priority for certain talkgroups at theirworkstation.

(2) Designation of higher tactical priority shall be achieved by means of a switch on that talkgroupappearance.

9.3.4.2* Digital Trunked System Requirements.

Digital trunked systems shall comply with ANSI/TIA-102.BAAA, FDMA Common Air Interface, orTIA-102.BBAB, Project 25 Phase 2 Two-Slot Time Division Multiple Access Physical Layer ProtocolSpecification; and with TIA-102.BBAC Project 25 Phase 2 Two-Slot TDMA Media Access Control LayerDescription and shall meet the requirements in 9.3.4.1.

9.3.5* Two-Way Mobile Equipment.

9.3.5.1

All emergency response units shall be equipped with a two-way mobile radio that is capable ofcommunicating with the communications center.

9.3.5.2

Mobile radios shall be equipped with a visual transmit indicator.

9.3.5.3

All mobile radios shall be equipped with a carrier control timer that disables the transmitter and signals theoperator with a distinctive tone after a time predetermined by the AHJ.

9.3.5.4

Mobile radios and associated equipment shall be manufactured for the environment in which they are to beused.

9.3.5.5

Mobile radios shall be capable of multiple-channel operation to enable on-scene simplex radiocommunications that are independent of dispatch channels.


92 of 189 7/22/2016 1:15 PM

9.3.5.6

Spare mobile radio units shall be provided for emergency response units as follows:

(1) Minimum of one spare unit for each model not directly interchangeable

(2) Minimum of one spare unit for each 20 units, or fraction thereof, in service

9.3.6* Two-Way Portable Equipment.

9.3.6.1

All ERUs shall be equipped with a portable radio that is capable of two-way communication with thecommunications center.

9.3.6.2

Portable radios shall be manufactured for the environment in which they are to be used and shall be of asize and construction that allow their operation with the use of one hand.

9.3.6.3

Portable radios that are equipped with key pads that control radio functions shall have a means for the userto disable the keypad to prevent inadvertent use.

9.3.6.4

All portable radios shall be equipped with a carrier control timer that disables the transmitter and signals theoperator with a distinctive tone after a time predetermined by the AHJ.

9.3.6.5

Portable radios shall be capable of multiple-channel operation to enable on-scene simplex radiocommunications that are independent of dispatch channels.

9.3.6.6

Portable radios shall be designed to allow channels to be changed while emergency response personnelare wearing gloves.

9.3.6.7

Single-unit battery chargers for portable radios shall be capable of fully charging the radio battery while theradio is in the receiving mode.

9.3.6.8

Battery chargers for portable radios shall automatically revert to maintenance charge when the battery isfully charged.

9.3.6.9

Battery chargers shall be capable of charging batteries in a manner that is independent of and external tothe portable radio.

9.3.6.10

Spare batteries shall be maintained in quantities that allow continuous operation as determined by the AHJ.

9.3.6.11

A minimum of one spare portable radio shall be provided for each 10 units, or fraction thereof, in service.

9.3.6.12*

Portable radios used by first responders who might encounter hazardous locations because of thepresence of explosive gas or explosive dust atmospheres shall be rated as intrinsically safe for operation insuch atmospheres by a nationally recognized testing laboratory, if determined necessary by the AHJ.

9.3.7* Mobile Command Vehicles.

Vehicles that are used in command or communications functions shall meet the requirements ofNFPA 1901.

9.3.8 Microwave Systems.


93 of 189 7/22/2016 1:15 PM


Microwave radio systems shall meet the following minimum requirements:


(2)

(3) The microwave radio shall include a transmitter, a receiver, a modem, a power supply, an automaticswitching device, a multiplexer, service channels/orderwire, and all associated interconnections.



9.3.8.2 Recovery and Protection.

9.3.8.2.1

Receivers shall provide both manual and fade initiated automatic errorless switching.

9.3.8.2.2

Recovery of a system from RF signal loss shall take place within 250 milliseconds after a valid signal isrestored.

9.3.8.2.3

The system shall be designed so that protection circuits and units not in service or operation can be testedand repaired without affecting on-line system operation.

9.3.8.2.4

Partial or complete failure of protection control or switching equipment shall not render the microwave linkinoperable.

9.3.8.3 Electromagnetic Interference.

9.3.8.3.1

The microwave equipment shall be operationally compatible with public safety communications equipmentco-located in the same equipment location.

9.3.8.3.2*

The microwave equipment shall be capable of meeting full specifications when operating in the vicinity ofcommercial AM and FM radio and TV transmitters.

9.3.8.4 Environmental Considerations.

Microwave systems equipment shall function properly in the environmental conditions and at altitudes inwhich it is installed.

9.3.8.5 Microwave System Network Management.

9.3.8.5.1* General.

The microwave system shall have sufficient alarm, control, and metering capabilities to detect defective orfailing components.

9.3.8.5.2 Fault and Failure History Log.

9.3.8.5.2.1

The microwave radio shall maintain an electronic file that records the date and time of all fault and failureconditions and switching actions.

9.3.8.5.2.2

The file shall be downloadable for on-site review and electronic communications to others.

9.3.8.5.3 Fault and Failure Indications.

Fault and failure conditions shall be displayed at the site and at a remotely monitored location.

9.3.8.5.4 External Alarms.

Each microwave radio assembly shall accommodate external site/housekeeping alarm inputs.

* The microwave radio shall be suitable for operating in network configurations offering ring or starprotection.


94 of 189 7/22/2016 1:15 PM

9.4 Radio Alerting Systems.

9.4.1 General.

9.4.1.1

Radio alerting systems shall include one or more of the following:

(1) Voice receivers

(2) Coded receivers

(3) Noncoded receivers

(4) Numeric receivers

(5) Alphanumeric devices

(6) Two-way alphanumeric devices

9.4.1.2

Where radio home alerting receivers, portable radios, pagers, and similar radio devices are used to receivealarms or are used on-scene, they shall conform to the requirements of this standard.

9.4.1.3

Where portable two-way radio equipment is used to receive fire alarms, such units shall be equipped toreceive a coded alert.

9.4.2 Radio Paging Systems and Pagers.

9.4.2.1*

The paging system shall be under the direct control of the AHJ where used as a method of emergencydispatch.

9.4.2.2

No part of the paging system shall utilize the public Internet for any portion of its operation when used as amethod of emergency dispatch.

9.4.2.3

Page-encoding equipment shall be located in the communications center where used as a method ofemergency dispatch.

9.4.2.4

The paging system shall comply with the general requirements for radio systems as outlined in thisdocument.

9.4.2.5

Pagers shall audibly indicate a low-battery condition.

9.4.2.6

Alphanumeric pagers shall support the maximum text message that can be sent from the communicationscenter.

9.4.2.7*

Coded receivers shall audibly indicate the presence of an unacknowledged message.

9.4.2.8

Alphanumeric devices and two-way alphanumeric devices shall audibly indicate the presence of an unreadmessage.

9.4.2.9

Two-way alphanumeric devices shall automatically transmit an acknowledgment when the device hasreceived and stored a message.

9.4.2.10

Two-way alphanumeric devices shall automatically transmit an acknowledgment when the responding userhas read the message.


95 of 189 7/22/2016 1:15 PM

9.4.2.11*

Two-way alphanumeric devices shall be capable of providing and transmitting multiple-choice replies,manually selected by the user.

9.4.2.12*

Status of the two-way alphanumeric devices, including messages sent and acknowledged, shall bemonitored in the operations room.

9.4.3* Alerting Receivers.

Where radio alerting receivers are used to receive emergency dispatch messages, they shall be providedwith two sources of power.

9.5 Outside Audible Alerting Devices.

9.5.1

Outside audible alerting devices used to indicate an emergency shall be located to alert all emergencyresponse personnel expected to respond.

9.5.2

Coded alerting devices shall operate at speeds of at least one actuation per second, with three or fourrounds of coded signals required where outside alerting devices are operated for summoning emergencypersonnel.

9.5.3

Compressed air alerting devices shall have a distinctive tone. If coded, the duration of the blast shall beneither less than 1⁄2 second nor longer than 1 1⁄2 seconds, with silent intervals of 1 to 1 1⁄2 times the blastduration.

9.5.3.1

Storage tanks shall meet the following criteria:

(1) Storage tanks shall comply with ASME specifications for unfired pressure vessels.

(2) Storage tanks shall be equipped with safety relief valves.

(3) Storage tank size shall be such that, at 85 percent of working pressure, eight times the largest numberof blasts assigned to any signal but not fewer than 50 blasts shall be capable of being sounded.

9.5.4

Compressors shall have the capacity to fill storage tanks to working pressure within 30 minutes.

9.5.4.1

Piping of ferrous materials shall be provided with scale traps that are accessible for cleaning.

9.5.4.2

All piping shall be arranged to allow inspection and repair.

9.5.5 IP Devices.

Where adopted by the AHJ, IP-enabled devices (e.g., smartphones, tablets, laptops) shall comply with therules and regulations governing wireless communications in the country of operation.

9.5.5.1

The communications center shall be equipped for IP-enabled two-way communications with the ERUsusing IP-enabled devices as determined by the AHJ.

9.5.5.2

IP-enabled devices shall be capable of fully charging the battery while in use.

9.6 Two-Way RadioCommunications Enhancement Systems.

9.6.1

All system components shall be designed, installed, tested, inspected, and maintained in accordance withthe manufacturers’ published instructions and the requirements of Section 9.6.


96 of 189 7/22/2016 1:15 PM

9.6.2

Pathway survivability levels shall be as described in Section 5.10. [72:24.3.13.1]

9.6.2.1

Two-way radio communications enhancement systems shall comply with 9.6.2.1.1 through 9.6.2.1.4.[72:24.3.13.8]

9.6.2.1.1*

Where a two-way radio communications enhancement system is used in lieu of a two-way in-building wiredemergency communications system, it shall have a pathway survivability of Level 1, Level 2, or Level 3.[72:24.3.13.8.1]

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

9.6.2.1.1.1

The feeder and riser coaxial cables shall be rated as plenum cables. [72:24.3.13.8.1.1]

9.6.2.1.1.2

The feeder coaxial cables shall be connected to the riser coaxial cable using hybrid coupler devices of avalue determined by the overall design. [72:24.3.13.8.1.2]

9.6.2.1.2

Where a two-way radio communications enhancement system is used in lieu of a two-way in-building wiredemergency communications system, the design of the system shall be approved by the AHJ.[72:24.3.13.8.2]

9.6.2.1.3*

Riser coaxial cables shall be rated as riser cables and routed through a 2-hour–rated enclosure.[72:24.3.13.8.3]

9.6.2.1.4

The connection between the riser and feeder coaxial cables shall be made within the 2-hour–ratedenclosure, and passage of the feeder cable in and out of the 2-hour–rated enclosure shall be fire-stoppedto 2-hour ratings. [72:24.3.13.8.4]

9.6.3*

Systems shall have lightning protection that complies with NFPA 780.

9.6.4

Systems that are used to comply with the requirements of Section 9.6 shall be tested in accordance with11.3.9 and 11.3.9.1.

9.6.5 Non-Interference and Non-Public Safety System Degradation.

9.6.5.1

No amplification system capable of operating on frequencies or causing interference on frequenciesassigned to the jurisdiction by the licensing authority of the country of jurisdiction shall be installed withoutprior coordination and approval of the AHJ.

9.6.5.2

The building manager/owner shall suspend and correct equipment installations that degrade theperformance of the public safety radio system or public safety radio enhancement system.

9.6.5.3

Systems that share infrastructure with non-public safety services shall ensure that the coverage andperformance of the public safety communications channels are not degraded below the level ofperformance identified in 9.6.7 and 9.6.8, regardless of the amount of traffic carried by the non-publicsafety services.

9.6.6 Approval and Permit.


97 of 189 7/22/2016 1:15 PM

9.6.6.1

Plans shall be submitted for approval prior to installation.

9.6.6.2

At the conclusion of successful acceptance testing, a renewable permit shall be issued for the public safetyradio enhancement system where required by the AHJ.

9.6.7* Radio Coverage.

9.6.7.1

Radio coverage shall be provided throughout the building as a percentage of floor area as specified insection below through section on amplification components.

9.6.7.2

The system shall adhere to the maximum acceptable propagation delay standard provided by the AHJ.

9.6.7.3

Radio coverage shall be determined by the AHJ.

9.6.7.4 Critical Areas.

Critical areas, including fire command centers, fire pump rooms, exit stairs, exit passageways, elevatorlobbies, standpipe cabinets, sprinkler sectional valve locations, and other areas deemed critical by the AHJ,shall be provided with 99 percent floor area radio coverage.

9.6.7.5 General Building Areas.

General building areas shall be provided with 90 percent floor area radio coverage.

9.6.7.6 Amplification Components.

Buildings and structures that cannot support the required level of radio coverage shall be equipped with asystem that includes RF emitting devices that are certified bythe radio licensing authority to achieve therequired adequate radio coverage.

9.6.8* Signal Strength.

9.6.8.1* Inbound.

A minimum inbound signal strength sufficient to provide usable voice communications, as specified by theAHJ, shall be provided throughout the coverage area. The inbound signal level shall be sufficient to providea minimum of DAQ 3.0 for either analog or digital signals.

9.6.8.2 Outbound.

A minimum outbound strength sufficient to provide usable voice communications, as specified by the AHJ,shall be provided throughout the coverage area. The outbound signal level shall be sufficient to provide aminimum of DAQ 3.0 for either analog or digital signals.

9.6.9 Isolation.

If a donor antenna exists, isolation shall be maintained between the donor antenna and all insideantennasto a minimum of 20 dB under all operating conditions.

9.6.10 System Radio Frequencies.

The public safety radio enhancement system shall be capable of transmitting all radio frequencies, asrequired by the AHJ assigned to the jurisdiction, and be capable of using any modulation technology incurrent use by the public safety agencies in the jurisdiction.

9.6.10.1 List of Assigned Frequencies.

The AHJ shall maintain a list of all inbound/outbound frequency pairs for distribution to system designers.

9.6.10.2* Frequency Changes.

Systems shall be upgradeable to allow for instances where the jurisdiction changes or adds systemfrequencies to maintain radio system coverage as it was originally designed.

9.6.11 System Components.


98 of 189 7/22/2016 1:15 PM

9.6.11.1* Component Approval.

RF emitting devices and cabling used in the installation of the public safety two-way radio communicationsenhancement systems shall be approved by the AHJ, and all RF emitting devices shall have thecertification of the radio licensing authority and be suitable for public safety use prior to installation.

9.6.11.2 Component Enclosures.

All repeater, transmitter, receiver, signal booster components, external filters, and battery systemcomponents shall be contained in a NEMA4- or NEMA4X-type enclosure(s).

9.6.11.3 RF Emitting Devices.

RF emitting devices shall meet the following requirements in addition to any other requirements determinedby the AHJ:

(1) RF emitting devices shall have the certification of the radio licensing authority prior to installation.

(2) All RF emitting devices shall be compatible with both analog and digital communications, as requiredto be used by the radio licensing authority and the AHJ, simultaneously at the time of installation.

9.6.12 Power Supplies.

At least two independent and reliable power supplies shall be provided for all RF emitting devices and anyother components of the system: one primary and one secondary.

9.6.12.1 Primary Power Source.

The primary power source shall be supplied from a dedicated branch circuit and comply with NFPA 72.

9.6.12.2 Secondary Power Source.

The secondary power source shall consist of one of the following:

(1) A storage battery dedicated to the system with 12 hours of 100 percent system operation capacity

(2) An alternative power source of 12 hours at 100 percent system operation capacity as approved by theAHJ

9.6.12.3 Monitoring Integrity of Power Supplies.

Monitoring the integrity of power supplies shall be in accordance with 9.1.2.2.

9.6.13 System Monitoring.

9.6.13.1 Fire Alarm System.

The system shall include automatic supervisory signals for malfunctions of the two-way radiocommunications enhancement systems that are annunciated by the fire alarm system in accordance withNFPA 72,and shall comply with the following:

(1) Monitoring for integrity of the system shall comply with NFPA 72, Chapter 10.

(2) System supervisory signals shall include the following:

(3) Donor antenna malfunction

(4) Active RF emitting device failure

(5) Low-battery capacity indication when 70 percent of the 12-hour operating capacity has beendepleted

(6) System component failure

(7) Power supply supervisory signals shall include the following for each RF emitting device and systemcomponent:

(8) Loss of normal ac power

(9) Failure of battery charger

(10) The communications link between the fire alarm system and the two-way radio communicationsenhancement system must be monitored for integrity.


99 of 189 7/22/2016 1:15 PM

9.6.13.2 Dedicated Panel.

(1) A dedicated monitoring panel shall be provided within the fire command center to annunciate thestatus of all RF emitting devices and system component locations. The monitoring panel shall providevisual and labeled indications of the following for each system component and RF emitting device:

(a) Normal ac power

(b) Loss of normal ac power

(c) Battery charger failure

(d) Low battery capacity (to 70 percent depletion)

(e) Donor antenna malfunction

(f) Active RF emitting device malfunction

(g) System component malfunction

(2) The communications link between the dedicated monitoring panel and the two-way radiocommunications enhancement system must be monitored for integrity.

9.6.14 Technical Criteria.

The AHJ shall maintain a document of technical information specific to its requirements that shall contain,as a minimum, the following:

(1) Frequencies required

(2) Location and effective radiated power (ERP) of radio sites used by the public safety radioenhancement system

(3) Maximum propagation delay (in microseconds)

(4) List of specifically approved system components

(5) Other supporting technical information necessary to direct system design


I am the Chair of the RF Task Group of the NFPA 1221 Committee. Our TG reviewed the radio section of Chapter 9, and found numerous items in the current edition that were unclear, and we propose changes to those items. Also, with respect to the In-Building Enhancements section, there were some inadvertent omissions in the current 2016 edition, for example to more explicitly include fiber optic cables in DAS systems, and suggestions for adding this are included. We believe our suggestions merit consideration to improve the quality of this section on radio.


Submitter Full Name: John Facella

Organization: Panther Pines Consulting LLC

Affilliation: NFPA 1221 Committee member

Street Address:

City:

State:

Zip:



100 of 189 7/22/2016 1:15 PM


9.1 Fundamental Requirements of Alarm Event Dispatching Systems.

9.1.1* General.

9.1.1.1

An alarm event dispatching system shall be designed, installed, operated, and maintained to provide forthe receipt and retransmission of alarms events .

9.1.1.2

The transmission of any trouble signal shall not interfere with the transmission and receipt of alarms.

9.1.1.3

The required number of dispatching circuits shall be in accordance with 9.1.1.3.1 through 9.1.1.3.3.

9.1.1.3.1

Jurisdictions that receive 730 alarms events or more per year shall provide two separate and dedicateddispatch circuits as follows:

(1) Separate primary and secondary dispatch circuits shall be provided for transmitting alarms events .

(2) The failure of any component of the primary circuit shall not affect the operation of the secondarycircuit and vice versa.

9.1.1.3.2*

Jurisdictions that receive fewer than 730 alarms events per year shall provide a minimum of one dedicateddispatch circuit for transmitting alarms.

9.1.1.3.3*

A circuit that terminates at a telephone handset only shall not be considered as fulfilling the requirementsfor a dispatch circuit. (See 9.2.2.2.)


101 of 189 7/22/2016 1:15 PM

9.1.1.4

The primary dispatch circuit shall be provided with one of, or a combination of, the following:

(1) Wired circuit, monitored for integrity in accordance with 9.1.2 through 9.1.2.4.3

(2)

(3)

(4)

(5) Microwave carrier channel, monitored for integrity in accordance with 9.1.2 through 9.1.2.5.2, with thefollowing features:

(6) Redundant transceivers at both ends of each microwave path


(8) Polling or self-interrogating digital data radio channel with the following features:

(9)

(10) Monitoring for integrity in accordance with 9.1.2 through 9.1.2.5.2


(12) Dedicated telephone circuit that is monitored for integrity in accordance with 9.1.2 through 9.1.2.4.3,excluding the following:

(13) Telephone connection through a public-switched telephone network

(14) Nondedicated phone lines

(15) Trunked radio system in compliance with 9.1.1.4(2) or 9.1.1.4(4)

9.1.1.5

The secondary dispatch circuit shall not be required to be monitored for integrity.

* Nontrunked voice radio channel with duplicate system elements, with the following features:

Monitored for integrity as required by 9.1.2.6

In the event of a failure of the primary system, a means to switch to the secondary system thatis immediately available to the telecommunicator

* Redundant transceivers at each installed location


102 of 189 7/22/2016 1:15 PM

9.1.1.5.1

The secondary dispatch circuit shall be provided with one of, or a combination of, the following:

(1) A wired circuit

(2)

(3) If radio is used for both the primary and secondary dispatch circuits, the following shall apply:

(4) The primary dispatch circuit shall comply with 9.1.1.4 .

(5)

(6) An approved dedicated telephone circuit

(7) Where a telephone dispatch circuit is used as a primary dispatch circuit, a telephone circuit shallnot be used as the required secondary dispatch circuit.

(8) A telephone connection through a public-switched telephone network via a regular dial-upmodem and nondedicated telephone line shall not be considered to be an approved dispatchcircuit.

(9)

9.1.1.6*

Where voice transmission is used as a dispatch method, the announcement for the emergency responseshall be preceded by an audible warning or alerting signal that differentiates the emergency from routinevoice traffic.

9.1.1.7

Alarms Events shall be retransmitted to ERFs or to ERUs in the field from the location at which alarmsevents are received.

9.1.1.7.1

Alarms Events transmitted from the communications center shall be automatically received at ERFs andERUs.

9.1.1.7.2

Dispatch methods shall provide for the operation of houselights or other auxiliary functions at the ERF asrequired by the AHJ.

9.1.1.8

Alarms Events that are transmitted over the required dispatch circuit(s) shall have the dates and times oftransmission automatically recorded at the communications center.

9.1.1.9

Audible devices shall be installed throughout the ERF to ensure that all emergency response personnel arealerted to alarms events .

9.1.1.10

Equipment shall be provided to allow personnel to alert all other personnel in the ERF.

9.1.1.11

A means of acknowledging receipt of an alarm event from the emergency response personnel to thetelecommunicator shall be provided.

9.1.2* Monitoring for Integrity.

Primary dispatch circuits and devices upon which transmission and receipt of events and alarms dependshall be monitored constantly to provide prompt warning of trouble that impacts operation.

* A designated radio channel

* The secondary dispatch circuit shall consist of a separate radio system operating on aseparate channel with a separate receiver for the secondary circuit at each ERF.

* The dispatch signal circuit path for the secondary dispatch circuit specified in 9.1.1.5.1 (4)(a) shallbe separate and independent of the dispatch signal circuit path of the primary dispatch circuit from thedispatch console to separate control/relay switching equipment connection ports at the ERF.


103 of 189 7/22/2016 1:15 PM

9.1.2.1*

A polling or self-interrogating radio system shall be monitored hourly for integrity to ensure system reliability.

9.1.2.2

The primary and secondary power sources supplied to all required circuits and devices of the system shallbe monitored for integrity.

9.1.2.3

Trouble signals shall actuate an audible device and a visual signal located at a constantly attended location.

9.1.2.4

The audible alert trouble signals from the fault and failure monitoring mechanism shall be distinct from theaudible alert emergency alarm signals.

9.1.2.4.1

The audible trouble signal shall be permitted to be common to several monitored circuits and devices.

9.1.2.4.2

A switch for silencing the audible trouble signal shall be permitted if the visual signal continues to operateuntil the silencing switch is restored to the designated normal position.

9.1.2.4.3

The audible trouble signal shall respond to faults that occur on all other circuits prior to the restoration of thesilencing switch to the “normal” position.

9.1.2.5

Where dispatch systems use computer diagnostic software, monitoring of the primary dispatch circuitcomponents shall be routed to a dedicated terminal(s) that meets the following requirements:

(1) It shall be labeled and identified as “dispatch circuit integrity status.”

(2) It shall be located within the communications center.

(3) It shall not be used for routine dispatch activities.

9.1.2.5.1

The computer diagnostic software shall be capable of displaying and testing each circuit that can beelectronically monitored from the dispatch console to the station control unit or junction relay switchingequipment in the ERF.

9.1.2.5.2

Any fault or failure condition within the dispatch circuit path shall be displayed on the dedicated terminalscreen in a prominent (highlighted) fashion that satisfies the visual trouble signal requirement, and with anaudible trouble signal, referenced in 9.1.2.4 through 9.1.2.5.2, that actuates and sounds in accordancewith the type of dispatch circuit that is being monitored.

9.1.2.6*

The radio communications system shall be monitored in the following ways:

(1) Monitoring for integrity shall detect faults and failures in the radio communications system.

(2) Detected faults and failures in the radio communications system shall cause audible and visualindications to be provided to the telecommunicator and radio system manager at the time of signalactivation.

9.1.2.6.1

Monitoring for integrity of portable radios and radio equipment installed in an ERF and in emergencyresponse vehicles shall not be required.


The use of "alarm" in this document is a artifact of 1221 when it was a fire alarm box standard and used strictly by fire departments. The change to a generic "emergency response" standard necessitates the change from "alarm"


104 of 189 7/22/2016 1:15 PM

to "event" to make the standard more acceptable to non-fire agencies.




Street Address:

City:

State:

Zip:



105 of 189 7/22/2016 1:15 PM


9.1.1.8

Alarms that are transmitted over the required dispatch circuit(s) shall have the dates and times oftransmission automatically recorded at the communications center. The source of the date and time shallbe the Master Time Source.


The Master Time Source is a new item in the definitions. This is an appropriate place to refer to it. By having time/date stamps referenced to a global source it makes the logged event data more useful for troubleshooting or for legal purposes.




Street Address:

City:

State:

Zip:



106 of 189 7/22/2016 1:15 PM


9.2.1.5

In jurisdictions where fewer than 730 alarms events per year are received or where all stations haverecording and sounding devices that respond to each public reporting circuit, the second dispatch circuitshall not be required; only the circuit that is monitored for integrity shall be required.






Street Address:

City:

State:

Zip:



107 of 189 7/22/2016 1:15 PM


9.3.1.2.2*

Radio and communications systems shall provide sufficient outdoor coverage shall be sufficient to , withsufficient excess signal strength to penetrate the buildings in that area. At a minimum, radio systems shallprovide a delivered audio quality (DAQ) of 3.0 for analog or digital systems .



NFPA_1221_proposed.docx Rationale statement


Emergency services personnel operate wherever service is needed. A high percentage of that service is delivered within the walls of structures. Radio communications are a vital link in the delivery of service and therefore require system coverage inside structures. Note: It is not the intent to require radio signal to locations not intended for human occupation. (e.g silos, tanks, other permit entry locations.) These are IDLH environments and would be covered by 9.3.1.5.1.


Submitter Full Name: John Lenihan

Organization: Los Angeles County Fire Dept

Street Address:

City:

State:

Zip:



108 of 189 7/22/2016 1:15 PM


9.3.1.2.2 *

Radio and outdoor coverage shall be sufficient to provide a delivered audio quality (DAQ) of 3.0 4 foranalog or digital systems.


TIA TSB-88.3-D Annex A identifies a DAQ of 3.4 for Public Safety radio systems and DAQ 3.0 for less critical radio systems. Emergency services radio systems are capable of achieving this higher standard and new system should be designed with the higher DAQ to provide the best possible communications channel.




Street Address:

City:

State:

Zip:



109 of 189 7/22/2016 1:15 PM


TITLE OF NEW CONTENT

9.3.1.5.1 Trunked systems talk groups shall not be used where personnel are operating in ImmediatelyDangerous to Life and Health (IDLH) environments. Conventional half-duplex or simplex channels meet thisrequirement.



NFPA_1221_proposed.docx Rationale


Firefighters operating in IDLH environments are encapsulated in protective gear that limits dexterity, visibility, and access to their radios. Such environments require radio communication as part of the responder’s personal safety and many State Occupational Health organizations require it by statute.Many radio system are challenged to penetrate today’s modern construction and energy efficiency building materials.Trunked system talk groups rely on a control channel to allow the radio to transmit and receive. If the control channel is lost or corrupted, radio communication is lost. It is unrealistic to expect firefighters operating in these conditions to retrieve their radio to execute a change.



Public Input No. 18-NFPA 1221-2016 [Section No. 9.3.1.5]




Street Address:

City:

State:

Zip:



110 of 189 7/22/2016 1:15 PM


9.3.1.5*

Trunked system talk groups shall may be permitted to be used to provide on-scene tacticalcommunications if desired by the AHJ, and the provisions of9.3.1.3 and 9.3.1.4 shall still apply.



NFPA_1221_proposed.docx Rationale for changes


Firefighters operating in IDLH environments are encapsulated in protective gear that limits dexterity, visibility, and access to their radios. Such environments require radio communication as part of the responder’s personal safety and many State Occupational Health organizations require it by statute.Many radio system are challenged to penetrate today’s modern construction and energy efficiency building materials.Trunked system talk groups rely on a control channel to allow the radio to transmit and receive. If the control channel is lost or corrupted, radio communication is lost. It is unrealistic to expect firefighters operating in these conditions to retrieve their radio to execute a change.



Public Input No. 19-NFPA 1221-2016 [New Section after 9.3.1.5]




Street Address:

City:

State:

Zip:



111 of 189 7/22/2016 1:15 PM



A visual incoming call indicator shall be provided for each conventional channel controller from the controlcenter console.


This is an attempt to make this requirement less ambiguous so as to ease compliance verification by ISO agents.BTW, I have tried to edit the "Submitter Name" to identify myself, but it does not allow me to change it. My name is Randy Richmond.




Street Address:

City:

State:

Zip:



112 of 189 7/22/2016 1:15 PM



A call indicator shall be provided for each conventional channel controller from the control center consoleto indicate when the channel is busy .


Recommend added wording to clarify the purpose of the call indicator for conventional radio resources.




Street Address:

City:

State:

Zip:



113 of 189 7/22/2016 1:15 PM


9.3.4.1.13

All units operating within the same talkgroup shall receive both sides of every conversation addressed to orfrom the talkgroup. The exception being that ERU radios are not expected to receive while transmitting.






Street Address:

City:

State:

Zip:



114 of 189 7/22/2016 1:15 PM

Public Input No. 108-NFPA 1221-2016 [ Section No. 9.3.4.1.15.2 ]

9.3.4.1.15.2

Units that become activated during a conversation, or units that leave the system coverage and return (i.e."late entry") , shall use the continuous update to immediately affiliate with their assigned talkgroup.


This comment is to aid fire departments in harmonizing the common LMR industry term "late entry" with this issue.BTW, I have tried to edit the "Submitter Name" to identify myself, but it does not allow me to change it. My name is Randy Richmond.




Street Address:

City:

State:

Zip:



115 of 189 7/22/2016 1:15 PM

Public Input No. 95-NFPA 1221-2016 [ New Section after 9.3.4.1.17.2 ]

9.3.4.1.17.3

Hardware and software that allow re-enablement of a disabled mobile or portable radio unit(s) currentlyoperating on the system shall be provided.


Suggested addition to ensure a radio that has been disabled can be re-enabled in the same way. The reason for disabling a radio (e.g. lost radio, stuck transmitter) may be rectified, resulting in a need to re-enable.




Street Address:

City:

State:

Zip:



116 of 189 7/22/2016 1:15 PM


9.3.4.1.20.3

A means shall be provided that is capable of recording system problems as they occur. The problem logshall include the date and time of the event based on the Master Time Source.


The Master Time Source is a new item in the definitions. This is an appropriate place to refer to it. By having time/date stamps referenced to a global source it makes the logged event data more useful for troubleshooting or for legal purposes.




Street Address:

City:

State:

Zip:



117 of 189 7/22/2016 1:15 PM


9.3.4.1.21.1

A visual incoming call indicator shall be provided for each talkgroup controlled from the control centerconsole.






Street Address:

City:

State:

Zip:



118 of 189 7/22/2016 1:15 PM


9.3.4.1.24.1

The system shall be configured so that no “busy” indication is received by a telecommunicator attempting toaccess a talkgroup required for dispatch of an alarm event .






Street Address:

City:

State:

Zip:



119 of 189 7/22/2016 1:15 PM



Microwave radio systems shall meet the following minimum requirements:


(2)

(3) The microwave radio shall include a transmitter, a receiver, a modem, a power supply, an automaticswitching device, a multiplexer, service channels/orderwire, and all associated interconnections.



(6) Each microwave hop shall be designed to meet or exceed a one way end-to-end annual qualityperformance (BER = 10-3) of 99.995 percent at the required capacity.

(7) Each microwave hop shall be designed to meet or exceed a one way end-to-end annual reliabilityperformance (BER = 10-6) of 99.999 percent at the required capacity


Added metrics for quality and reliable performance of the microwave radios at the desired bandwidth. These metrics help ensure the path is engineered to withstand transient atmospheric conditions, such as rain fade, to provide uninterrupted communications.




Street Address:

City:

State:

Zip:


* The microwave radio shall be suitable for operating in network configurations offering ring or starprotection.


120 of 189 7/22/2016 1:15 PM


9.4.1.2

Where radio home alerting receivers, portable radios, pagers, and similar radio devices are used to receivealarms events or are used on-scene, they shall conform to the requirements of this standard.






Street Address:

City:

State:

Zip:



121 of 189 7/22/2016 1:15 PM


9.4.1.3

Where portable two-way radio equipment is used to receive fire alarms events , such units shall beequipped to receive a coded alert.






Street Address:

City:

State:

Zip:



122 of 189 7/22/2016 1:15 PM


9.4.2.3

Page-encoding equipment shall be located in the communications center or an associated Public SafetyRadio Sytsem site where used as a method of emergency dispatch.


Many paging encoders are co-located with transmitters at remote radio sites rather than dispatch centers.BTW, I have tried to edit the "Submitter Name" to identify myself, but it does not allow me to change it. My name is Randy Richmond.




Street Address:

City:

State:

Zip:



123 of 189 7/22/2016 1:15 PM


9.6.2.1.3*

Riser coaxial cables shall be rated as riser cables and routed through a 2-hour–rated enclosure.[ 72: 24.3.13.8.3] meet thge building survivability requirements


This requirement could result in 2 hour wiring being installed in a building that only has a 1 hour fire rating. requiring the surviability requirements to apply eliminates this issue.




Street Address:

City:

State:

Zip:



124 of 189 7/22/2016 1:15 PM


9.6.13.2 Dedicated Panel annunciation .

(1) A dedicated monitoring panel shall annunciator shall be provided within the fire command center toannunciate the status of all RF emitting devices and system component locations. The monitoringpanel shall This device shall provide visual and labeled indications of the following for each systemcomponent and RF emitting device:

(a) Normal ac power

(b) Loss of normal ac power

(c) Battery charger failure

(d) Low battery capacity (to 70 percent depletion)

(e) Donor antenna malfunction

(f) Active RF emitting device malfunction

(g) System component malfunction

(2) The communications link between this device and the dedicated monitoring panel and the two-wayradio communications enhancement system must be monitored for integrity.


This requirement has been interpreted that a separate panel needed to be installed in the building just for this requirement. The intent of this requirement was to have separate annunciation of these signals so that they did not get lost in all of the other signals being displayed from the fire alarm system. installation of a separate system would meet this requirement but was not the intent of this code section when included in NFPA 1221.




Street Address:

City:

State:

Zip:



125 of 189 7/22/2016 1:15 PM


Inspection Testing and Maintenance requirements of Two-Way Radio CommunicationsEnhancement Systems

Establish Acceptance testing requirements

Establish periodic inspection requirements

Establish Periodic testing requirements

Establish required documentation for Periodic testing and inspections


When transferred from NFPA 72 the requirements for acceptance and periodic testing requirements were lost between the documents, this PI allows the committee a manor to restore these requirements under this document.




Street Address:

City:

State:

Zip:



126 of 189 7/22/2016 1:15 PM


CAD systems shall provide network isolation necessary to preserve bandwidth for the efficient operation ofthe system and processing of alarms events .






Street Address:

City:

State:

Zip:



127 of 189 7/22/2016 1:15 PM


10.3.5.3

The CAD system should provide for secure external access for troubleshooting and upgrades from aremote location.


Providing for the ability of remote login to troubleshooting saves time for the repair of system problems and could reduce the total cost of ownership. The capability of remote access must be secure and meet all applicable federal, state and local security requirements.




Street Address:

City:

State:

Zip:



128 of 189 7/22/2016 1:15 PM


10.4 Alarm Event Data Exchange.

10.4.1

The CAD system shall have the capability to allow alarm event data exchange between the CAD systemand other CAD systems.

10.4.1.1*

Alarm Event data exchange between two PSAPs shall comply with the elements contained in 10.4.1.2through 10.4.1.7.

10.4.1.2

Alarm Event data elements for alarm event processing shall contain the following items from the sendingCAD system:

(1) Street address or intersection of event

(2) Latitude/longitude of event

(3) Reporting party name

(4) Reporting party address

(5) Reporting party callback number

(6) Event type

(7) Any remarks entered to that point

10.4.1.3

The new alarm information shall display as a pending event in the receiving CAD system.

10.4.1.4

The receiving CAD system shall automatically send a confirmation message to the sending CAD systemthat it received the call.

10.4.1.5

It shall be up to the AHJ to decide whether or not to use or display this information.

10.4.1.6

The sending CAD shall continue to send updates related to the event as needed until the event isterminated by either agency.

10.4.1.7

The sending dispatchers shall be able to send and receive administrative (not tied to an incident) messagesto the receiving dispatchers.

10.4.1.8

The sending CAD shall send status changes on all units that the sending CAD has jointly identified to thereceiving CAD without dispatcher intervention.

10.4.1.9

The requirements in 10.4.1.3 to 10.4.1.8 shall also apply conversely to the receiving CAD.

10.4.1.10

Each CAD system shall be set up with conversion tables that can translate event types from one system tothe other.


129 of 189 7/22/2016 1:15 PM

10.4.2

The CAD system shall have the capability to allow alarm event data exchange between the CAD systemand supervising stations.

10.4.3

The CAD system shall have the capability to allow alarm event data exchange between the CAD systemand 9-1-1 databases.

10.4.4*

The CAD system shall have the capability to allow event data exchange between the CAD system andother systems as required and approved by the AHJ.

10.4.5

CAD systems that are connected to third-party systems to receive alarms events directly shall haveagreements in place with the third-party providers to monitor the system for integrity.






Street Address:

City:

State:

Zip:



130 of 189 7/22/2016 1:15 PM


The CAD system shall have the capability to allow alarm data exchange between the CAD system and otherCAD systems. The recommended method for data exchange should be the NENA/APCO EmergencyIncident Data Document (EIDD)


The industry is quickly adopting the APCO/NENA Emergency Incident Data Document (EIDD) (https://www.nena.org/?EIDD) as the preferred method for exchanging incident data between systems (such as between CAD systems). BTW, I have tried to edit the "Submitter Name" to identify myself, but it does not allow me to change it. My name is Randy Richmond.




Street Address:

City:

State:

Zip:



131 of 189 7/22/2016 1:15 PM


10.4.1.1 *

Alarm data exchange between two PSAPs or more PSAPs shall comply with the elements contained in10.4.1.2 through 10.4.1.7.


Regional based CAD system are established between more than 2 PSAPs. Data sharing is performed to provide situational awareness and event operations among multiple PSAPs.




Street Address:

City:

State:

Zip:



132 of 189 7/22/2016 1:15 PM


10.4.1.2

Alarm data elements for alarm processing shall contain the following items from the sending CAD system:

(1) Street address or intersection of event

(2) Latitude/longitude of event

(3) Reporting party name

(4) Reporting party address

(5) Reporting party callback number

(6) Event type

(7) Any remarks entered to that point

(8) ID of sending PSAP

(9) ID of sending dispatcher


Identifying the sending PSAP and sending dispatcher allows for callbacks and the ability to clarify the event, or information contained in the event.




Street Address:

City:

State:

Zip:



133 of 189 7/22/2016 1:15 PM


10.5.5.4

A default printer may be assigned to any device on the CAD network or mobile device.


Allowing the assignment of a default printer will alleviate the need to identify a printer for a printing assignment.




Street Address:

City:

State:

Zip:



134 of 189 7/22/2016 1:15 PM


Software that is a part of the CAD system shall provide data entry; provide resource recommendations,notification, and tracking; store records relating to all alarms events and all other calls for service andstatus changes; and track those resources before, during, and after alarms events , preserving records ofthose alarms events and status changes for later analysis.






Street Address:

City:

State:

Zip:



135 of 189 7/22/2016 1:15 PM


10.5.7

Where the CAD system is a primary or secondary dispatch circuit for ERFs and ERUs, it shall provide anaudible notification of alarms events and shall be permitted to provide a visual notification of alarmsevents and other calls for service.

10.5.7.1

If voice announcement is used, it shall be preceded by an audible warning or alerting signal thatdifferentiates the alarm event or emergency from any other voice messages carried by the system.

10.5.7.2*

If text messages are used, they shall be accompanied by audible warning or alerting signal(s) that notifyERF or ERU personnel that an alarm event or emergency message has been transmitted.

10.5.7.3

Printers located in an ERF as a part of the dispatch system shall be capable of printing a completedemergency message in less than 30 seconds.






Street Address:

City:

State:

Zip:



136 of 189 7/22/2016 1:15 PM


10.5.8

All equipment shall be bonded to the single-point facility ground to normalize ground potential between thedemarcation points and the communications center equipment.


Differences in grounding potential may cause communication circuit errors and possible power instability. This practice is in keeping with maintaining a single-point facility ground throughout the building and connected equipment.




Street Address:

City:

State:

Zip:



137 of 189 7/22/2016 1:15 PM


10.5. 7 5 . 3 5

Printers located in an ERF as a part of the dispatch system shall be capable of printing a completedemergency message in less than 30 seconds.


The content of this requirement appears to be better aligned in the 10.5.5 Printers Section.




Street Address:

City:

State:

Zip:



138 of 189 7/22/2016 1:15 PM


10.7.1

The backup procedures shall include scheduled failover and recovery operations by the communicationscenter to in-place backup systems. Sufficient testing should occur on the backup systems to verify thecompleteness and accuracy of the backup and recovery data and process, including switching back to theprimary system.


To have backup and disaster recovery system in place is very important. However, those systems are not beneficial if the data is incomplete or corrupted. The restoration process must be verified through testing either in live operation or on a standalone test system. Valuable information on the time it takes to switch to the backup system and return to the primary system will be obtained from the testing procedure.

This is mentioned in A.10.7. The subject is important enough to be elevated to a primary section in Chapter 10.



Public Input No. 129-NFPA 1221-2016 [New Section after 10.7]




Street Address:

City:

State:

Zip:



139 of 189 7/22/2016 1:15 PM


10.7.2

Backups may be accomplished on tape, DVD writer, or disk storage arrays in a redundant array ofindependent disks (RAID) configuration. The AHJ should establish a schedule for the routine backup ofdata as well as periodic testing of the stored data system for effectiveness and completeness. Incorporatingmultiple backup methods is preferred, augmented by the off-site storage of backup files.


Move content from Appendix A informative to become part of the Standard. Backup and data recovery verification is important. The data is not beneficial if it is shown to be incomplete or corrupted at the time when it is needed for restoration. These recommendations are useful and should be included as part of the standard.



Public Input No. 101-NFPA 1221-2016[New Section after 10.7]

Related topic regarding backup of stored files to improve overallrecords retention and management




Street Address:

City:

State:

Zip:



140 of 189 7/22/2016 1:15 PM


10.9.3

History log data shall not be deleted or overwritten without the knowledge and consent of the AHJ.


Although unlimited storage is preferable, it is often not practical. Data logs are important and often required to be stored for longer than 100 days by legal requirements.







Street Address:

City:

State:

Zip:



141 of 189 7/22/2016 1:15 PM


10.9.4

The capability should exist to move data to alternate, long-term storage for retrieval. Access to thedata should be restricted through security measures enabled by the AHJ.


Provision must be made to store the data for longer periods if it is not possible to retain on-line.



Public Input No. 102-NFPA 1221-2016 [New Sectionafter 10.9.2]

Related to requirements for long term storage ofrecorded data.




Street Address:

City:

State:

Zip:



142 of 189 7/22/2016 1:15 PM


10.11.2

MDC’s may include any IP-enabled device (e.g., smartphones, tablets, laptops).


As communications technology advances most devices are currently, or will be IP-enabled. Policies must reflect the addition of IP-enabled devices.




Street Address:

City:

State:

Zip:



143 of 189 7/22/2016 1:15 PM


10.11.5.2

Required connections Where hard-wired connections are required connections between the MDC andother essential system components shall , the connections shall be fastened so as to not come looseunder normal operating conditions.


Wording revised to clarify the connection requirement for installed hard-wired devices versus temporary connections with wireless devices. Wireless devices are being employed to improve accessibility to data, reduce restrictions on installation and to reduce ownership costs related to installation and maintenance.




Street Address:

City:

State:

Zip:



144 of 189 7/22/2016 1:15 PM


10.11.5.4 *

The MDCs shall provide the following functionality:

(1) The ability to power on and off

(2) A visual indication that the unit is energized

(3) The ability to adjust display intensity

(4) An emergency alert button that transmits a distress signal to the operations room

(5) The ability to toggle between daytime and nighttime display.


The glare of a light background, even adjusted to a low intensity, at night will light up anyone viewing the display and create a possible dangerous situation. The glare on the windows can create a hazardous situation with driving or attempting to view outside of the vehicle. A nighttime display will reverse the background from a light to a dark background, and reverse the features and annotations to a lighter text. The darker background does not cast as much glare as the light background.




Street Address:

City:

State:

Zip:



145 of 189 7/22/2016 1:15 PM


10.11.5.7

The MDC system should utilize both private and commercial wireless connection capabilities.


The ability of MCD to roam between available systems is critical for continued communications when traveling at the edge of private systems and when moving in and around obstacles that may limit wireless coverage from the private system. Coverage of wireless system is limited by distance and obstacle penetration. As the MCD roams between systems, the connection should not be lost or require intervention by the user to switch between providers.



Public Input No. 114-NFPA 1221-2016 [New Section after 10.11.5.6]




Street Address:

City:

State:

Zip:



146 of 189 7/22/2016 1:15 PM


10.11.5.8

The MDC system should accommodate roaming with seamless transitions between wireless systems.


The ability of MCD to roam between available systems is critical for continued communications when traveling at the edge of private systems and when moving in and around obstacles that may limit wireless coverage from the private system. Coverage of wireless system is limited by distance and obstacle penetration. As the MCD roams between systems, the connection should not be lost or require intervention by the user to switch between providers.



Public Input No. 113-NFPA 1221-2016 [NewSection after 10.11.5.6]

Two new sections related to roaming between private andpublic communications systems




Street Address:

City:

State:

Zip:



147 of 189 7/22/2016 1:15 PM


10.12.4

Integrated mapping should be a function available to the MDC with similar functionality as a CADworkstation.


Field users of the MDC require situational awareness provided with an integrated mapping system.




Street Address:

City:

State:

Zip:



148 of 189 7/22/2016 1:15 PM


10.13 Virtual Environment


Add new Section on Virtual Environment to address the current and future requirements of operating in virtual computing and storage environments.




New Section to address the provision for working withina virtual environment






Street Address:

City:

State:

Zip:



149 of 189 7/22/2016 1:15 PM


10.13.1

The CAD system should be designed to allow for the deployment of virtual servers at the discretion of theAHJ.


Virtualization of servers, workstations and storage devices can result in a lower cost of ownership due to reduced hardware, operating system implementation and maintenance costs. When configured properly, virtualization also provides internal redundancy and recovery capabilities.




Street Address:

City:

State:

Zip:



150 of 189 7/22/2016 1:15 PM


10.13.2

The CAD system should be designed to allow for the deployment of virtual workstations at the discretion ofthe AHJ.






New Section to address the provision for working withina virtual environment




Street Address:

City:

State:

Zip:



151 of 189 7/22/2016 1:15 PM


10.13.3

The CAD system should be is designed to allow for the deployment of virtual storage at the discretion ofthe AHJ.






New Section to address the requirement of working in avirtual environment





Street Address:

City:

State:

Zip:



152 of 189 7/22/2016 1:15 PM


10.14 Action History


Recording action history is a critical function of CAD. The topic should be moved from Annex D.3 to a primary section in Chapter 10.



Public Input No. 123-NFPA1221-2016 [New Section after10.12.3]

Part of Action HIstory Section, recommended to be relocated frominformative Annex A to a new section as part of the standard










Street Address:

City:

State:

Zip:



153 of 189 7/22/2016 1:15 PM


10.14.1

The CAD system should record a history (audit trail) of the following actions taken with the items:

(1)Creation

(2)Change, including modification, deletion, or supplementation

(3)Disposition, including close-out, archiving, and transfer

(4)Inquiry to external data sources









Street Address:

City:

State:

Zip:



154 of 189 7/22/2016 1:15 PM


10.14.12

Each entry in the history should include the following:

(1) Coordinated universal time (UTC) of action

(2) Identification of the individual performing the action

(3) Identification of the device on which the action was performed

(4) Effects of action on the characteristics of the items









Street Address:

City:

State:

Zip:



155 of 189 7/22/2016 1:15 PM


10.14.3

The history record (audit trail) shall be accessible by the AHJ for inquiry and reporting purposes.


For the action history to be beneficial, the data must be available for review and reporting.







Street Address:

City:

State:

Zip:



156 of 189 7/22/2016 1:15 PM


10.14.14

The Action History function shall meet all federal, state and local requirements for recording and reporting.


The ability to audit certain functions of the action history is mandated by law enforcement agencies.







Street Address:

City:

State:

Zip:



157 of 189 7/22/2016 1:15 PM


12.5.2.1

A management information system (MIS) program shall track incoming calls and dispatched alarms eventsand provide real-time information and strategic management reports.






Street Address:

City:

State:

Zip:



158 of 189 7/22/2016 1:15 PM


Chapter 13 Data Security Cybers ecurity

13.1 * Data Security Cybersecurity Plan.

Communications centers shall develop, implement, and utilize a comprehensive defense in depth processand plan to ensure total data cybersecurity. The defense in depth approach shall encompass people,technology, and operations and shall provide a framework for safeguarding the vital mission of public safetycommunications centers, including the CAD systems and IP-based NG9-1-1 systems, and the public safetywireless networks used by first responders, including any IP-enabled wireless devices, whether used onpublic safety or public wireless carrier networks.

13.1.1

The plan shall include the items required by 13.1.2 through 13.1.12.

13.1.2

The plan shall include a policy statement from the AHJ detailing the requirements and goals of the plan.

13.1.3 *

The plan shall require the assignment of responsibilities for the performance of security functions.

13.1.4 *

The plan shall specify training and education requirements for employees and shall include a continuingeducation plan component.

13.1.5 *

The communications center shall implement control provisions for access to physical premises, access toradio subscriber units into the radio system, and personnel access to various portions of the networks andcomputers.

13.1.6 *

The communications center shall implement network security provisions to prevent unauthorized personsfrom gaining access to the public safety IP network, the public safety phone network, the land mobile radionetwork, and any other networks that operate within or under the control of the communications center thatare required for the receipt or processing of alarms and to prevent unauthorized use of public safetyhandheld IP-enabled devices used on either a public safety network or a public wireless carrier network.

13.1.7 *

The communications center shall implement computer security provisions to prevent attacks on the center’scomputers and servers.

13.1.8 *

The communications center shall implement software patch management provisions to ensure that allsoftware is periodically updated with the latest improvements to facilitate better security.

13.1.9 *

The AHJ shall implement data disaster recovery procedures to ensure rapid recovery of databases,servers, and similar equipment used in the communications center, in the public safety wireless network,and for local storage of important information.

13.1.10 *

The communications center shall implement logging and auditing provisions to allow for the investigation ofsecurity or operational problems.


159 of 189 7/22/2016 1:15 PM

13.1.11 *

The AHJ shall implement a vulnerability management process to assess periodically the ability of the publicsafety communications systems, including communications centers, wireless networks, and wired ITnetworks.

13.1.12 *

The communications center shall implement environmental and physical security provisions to ensure that itcan monitor various physical aspects of the public safety communications system at all locations, such asphysical entry, fire or smoke, power supply performance, base radio performance, and other parameters asjudged necessary by the AHJ.

13.2 * Testing Security.

The plan shall include methods and procedures, including schedules, for testing of the system for securitybreaches or failures, with the frequency of testing to be determined by the AHJ.

13.3 Testing Records.

Testing records of the plan shall be maintained in accordance with Section 12.7.


Recommend that this section be updated to reflect a cybersecurity focus instead of focusing simply on the data component. Protecting data is critical, however attacks on the communications infrastructure are necessary to ensure continued operations of the emergency communications facility.



Public Input No. 140-NFPA 1221-2016 [Section No. 13.1.8]




Street Address:

City:

State:

Zip:



160 of 189 7/22/2016 1:15 PM


Chapter 13 Data Security


161 of 189 7/22/2016 1:15 PM

Suggested changes to Chapter 13 , Data Security:

This entire chapter, as well as the extensive Annex material, needs complete review and re-writing, in lightof the many cyber attacks now occurring, especially against public safety agencies including lawenforcement .

Some needed changes include:

(1) Specifically calling out implementation of at least the first four of the SANS Critical Security Controls,which now even the NSA has mentioned (SANS Newsbytes of 17 June 2016) as their starting pointfor an attack

(2) Bi-annual user training to avoid phishing and social engineering attacks (stop-think-click, etc.)

(3) No use of public safety computers for Internet email and general Internet surfing

(4) Consider banning use of thumb drives

(5) No computer games or personal pictures allowed on PS computers

(6) Explain issue of geo-coded pictures

(7) Explain dangers of GPS location coordinates of PS ERUs sent unencrypted over the air

(8) Patch policies

(9) AHJ have a policy on bring your own device (BYOD)

(10) Annex material to suggest moving to 2 factor authentication for PSAP telecommunicators at theirstation, 1 factor following H below, but in Annex suggest moving to 2 factor using tokens for agencies

(11) Reference to HIPPA standards for EMS

(12) AHJ must have a policy of changing passwords at least every 3 months, strong passwords only to beused of at least 8 characters including some numbers and special characters, no PWs stored onsticky notes on keyboards, no sharing of PWs, PWs must be unique to the PS computer, etc.

(13) Consideration of vulnerability testing (penetration) for larger agencies, at least annually

(14) Mention in the Annex the suggestion that active system monitoring for intrusion be done for largeragencies

(15) Daily backup and recovery of data records to avoid being ‘ransomed’

(16) Annex reference IACP and other organizations that have specific cyber sites for information for publicsafety

(17) Add warnings about using the ‘cloud’, probably in the Annex?

(18) Chapter 13’s title of Data Security seems a bit limiting. Perhaps we change the title of Chapter 13 tobe “System Security”? Data security is one element of an overall security plan for protection of acustomer’s system. It has implications of sensitive material at rest or in transit but doesn’t conveyother aspects of a system security program. Can we consider changing the name?

(19) The NIST document Framework for Improving Critical Infrastructure Cybersecurity (Version 1.0,February 12, 2014) should probably replace the reference in E2.2 (1), as it is no longer a preliminaryframework, but a published one.

(20) In our opinion, the NIST document does a pretty good job of lying out at a high level how agenciesshould approach the security of their system. The five categories of Identify, Protect, Detect, Respondand Recover are a comprehensive outline for how agencies should evaluate and protect theircommunications systems. To that end, when you read through the current Chapter 13, one cancategorize the different sections in this Chapter into one of the five elements of the NIST framework. Isee it as follows:

13.1.2 (policy statement) = identify/plan

13.1.3 (assignment of responsibilities) = identify/plan

13.1.4 (training) = identify/plan

13.1.5 (control physical access) = protect

13.1.6 (control network access) = protect


162 of 189 7/22/2016 1:15 PM

13.1.7 (computer security) = protect

13.1.8 (patch management) = protect

13.1.9 (disaster recovery) = recover

13.1.10 (logging) = respond

13.1.11 (vulnerability management) = identify

13.1.12 (monitoring) = detect

When you look at these 12 sections, you get a sense that the 1221 document stresses the importance ofidentifying and planning, which is good, and there is certainly the emphasis on protection, but maybe alittle more can be mentioned regarding identifying and responding to a security breach of some sort? As adispatch center manager/fire chief, etc., I probably don’t know the first thing about how to respond in realtime to someone that might be launching a cyber attack on a radio system or a computer network thathosts the dispatch consoles or CAD application or 911 call taking applications of a dispatch center, or aransom attack, or a denial of service attack. When that unfortunate thing happens, what to do? Who tocall? Do we want to offer a bit more information as to where to turn when/if something like this happens?

U. Do we want to add a section in 1221 making a recommendation to agencies that purchase hardware,software or interface connections (think alarm system operators having a connection to the dispatchcenter) from vendors request from those vendors certification or other proof that their hardware, softwareor interface is protected from outside attacks? I’m thinking software application providers in particular whocan be especially vulnerable and behind the curve as to the protections they put in place against outsideattacks. Should the agencies should ask for assurance up-front that the stuff they are buying has somelevel of protection?

V. Do we want to add some up-front material of all of the areas an agency should think about whenattempting to evaluate their vulnerabilities of their communications system? Maybe the 1221 documenttriggers them to ask a particular vendor for information regarding their protection mechanisms only to findout they are not as protected as they might think? A list of suggested areas to consider might be:

Radio network/dispatch consoles/paging/CAD

Alarm reporting systems (e.g. private like ADT, or public like schools, public buildings, etc.)

WiFi networks inside fire stations, etc. that are tied back into the dispatch center network

Fire Station Alerting applications

Video Surveillance networks and applications

Generator/UPS power sources with network connections

Others….

W. Another area of attack that is popular is an attacker leaving a USB thumb drive at a Starbucks or otherpublic area and then an unsuspecting person picks it up and plugs it into their computer to snoop as towhat is on the drive and then a virus attack or other malware is launched into the computer/network.Dispatch centers should have thumb drive or other media scanning tools in place at dispatch centers, firestations, etc. Should we mention/suggest that?

X. Perhaps we also include in the up-front material for Chapter 13 the fact that cyber attacks and othertypes of security breaches is a constantly-evolving environment. The ability for a fire department ordispatching agency to keep abreast of the latest forms of attack can be overwhelming. As such, agenciesshould strongly consider employing the services of a security consultant to assist in addressing all theareas of concern listed here in 1221. This would be Annex material.

Y. Looking through the guidance documents for something like requirements for: personnel components,facility/building components, monitoring, etc. Guidelines he sent were Safecom/NSCWIC Cyber PanelDiscussion, IAB Cyber Center, and 12/2013 IAB Cyberspace Security Continuum.

Z. Need to add references to NG911 cyber security in the NENA standards.

AA. Explain the dangers of using public WiFi connections for Internet access from fire apparatus,ambulances, law enforcement vehicles.

END OF SUGGESTED CHANGES

13.1 * Data Security Plan.


163 of 189 7/22/2016 1:15 PM

Communications centers shall develop, implement, and utilize a comprehensive defense in depth processand plan to ensure total data security. The defense in depth approach shall encompass people, technology,and operations and shall provide a framework for safeguarding the vital mission of public safetycommunications centers, including the CAD systems and IP-based NG9-1-1 systems, and the public safetywireless networks used by first responders, including any IP-enabled wireless devices, whether used onpublic safety or public wireless carrier networks.

13.1.1

The plan shall include the items required by 13.1.2 through 13.1.12.

13.1.2

The plan shall include a policy statement from the AHJ detailing the requirements and goals of the plan.

13.1.3*

The plan shall require the assignment of responsibilities for the performance of security functions.

13.1.4*

The plan shall specify training and education requirements for employees and shall include a continuingeducation plan component.

13.1.5*

The communications center shall implement control provisions for access to physical premises, access toradio subscriber units into the radio system, and personnel access to various portions of the networks andcomputers.

13.1.6*

The communications center shall implement network security provisions to prevent unauthorized personsfrom gaining access to the public safety IP network, the public safety phone network, the land mobile radionetwork, and any other networks that operate within or under the control of the communications center thatare required for the receipt or processing of alarms and to prevent unauthorized use of public safetyhandheld IP-enabled devices used on either a public safety network or a public wireless carrier network.

13.1.7*

The communications center shall implement computer security provisions to prevent attacks on the center’scomputers and servers.

13.1.8*

The communications center shall implement software patch management provisions to ensure that allsoftware is periodically updated with the latest improvements to facilitate better security.

13.1.9*

The AHJ shall implement data disaster recovery procedures to ensure rapid recovery of databases,servers, and similar equipment used in the communications center, in the public safety wireless network,and for local storage of important information.

13.1.10*

The communications center shall implement logging and auditing provisions to allow for the investigation ofsecurity or operational problems.

13.1.11*

The AHJ shall implement a vulnerability management process to assess periodically the ability of the publicsafety communications systems, including communications centers, wireless networks, and wired ITnetworks.

13.1.12*

The communications center shall implement environmental and physical security provisions to ensure that itcan monitor various physical aspects of the public safety communications system at all locations, such asphysical entry, fire or smoke, power supply performance, base radio performance, and other parameters asjudged necessary by the AHJ.


164 of 189 7/22/2016 1:15 PM

13.2* Testing Security.

The plan shall include methods and procedures, including schedules, for testing of the system for securitybreaches or failures, with the frequency of testing to be determined by the AHJ.

13.3 Testing Records.

Testing records of the plan shall be maintained in accordance with Section 12.7.


I am the Chair of the NFPA 1221 Cyber Task Group. The proposed changes were created as a result of the Cyber Task Group's review of the current Chapter 13 Data Security. We believe that the threat level of cyber attacks has increased substantially in 3 years, meriting a complete review of the entire section, including adding more detail on many items not previously covered or sparsely covered such as cloud computing, advanced persistent threats (APTs), etc.


Submitter Full Name: John Facella

Organization: Panther Pines Consulting LLC

Affilliation: NFPA 1221 Committee member

Street Address:

City:

State:

Zip:



165 of 189 7/22/2016 1:15 PM


13.1.6*

The communications center shall implement network security provisions to prevent unauthorized personsfrom gaining access to the public safety IP network, the public safety phone network, the land mobile radionetwork, and any other networks that operate within or under the control of the communications center thatare required for the receipt or processing of alarms events and to prevent unauthorized use of publicsafety handheld IP-enabled devices used on either a public safety network or a public wireless carriernetwork.






Street Address:

City:

State:

Zip:



166 of 189 7/22/2016 1:15 PM


13.1.8 *

The communications center shall implement software patch management provisions to ensure that allsoftware is periodically updated with the latest improvements maintained with all updates released andrecommended by the system manufacturer to facilitate better security.


The frequency of system attacks demands that software patches that provide improved security should be installed as soon as the patch is made available by a verified source. Scheduled updates should be conducted for patches that do not immediately affect the security and critical functions of the system.



Public Input No. 138-NFPA 1221-2016[Chapter 13]

Refocus the data security section to the current, and pressingissue of overall cybersecurity

Public Input No. 139-NFPA 1221-2016[New Section after 13.3]

Refocus the data security section to the current, and pressingissue of overall cybersecurity




Street Address:

City:

State:

Zip:



167 of 189 7/22/2016 1:15 PM


13.4

New systems or upgrades to existing systems shall be designed and implemented using a ‘security-by-design’ process to incorporate cybersecurity measures as part of the system.


Developing security as part of the system design process provides more thorough protection of the system than a security application or measures developed after the system is in operation.



Public Input No. 140-NFPA 1221-2016 [Section No. 13.1.8]




Street Address:

City:

State:

Zip:



168 of 189 7/22/2016 1:15 PM


14.3 * Permitted Uses.

Systems shall be used for alerting the public to natural and man-made events, including tornadoes,hurricanes, floods, fire, and chemical releases, Alert systems are used to warn the public ofdangers, provide information, and to provide recommended actions to the public regarding events that canbe expected to result in loss of life, endanger public health, or destroy property. These events may include,but are not imited to tornadoes, hurricanes, floods, fire, and chemical releases.


The current text speaks to the reasons why (causes) that may initiate the use of the public alert system. The suggested revisions to the text are intended to clarify why an alert is issued and what the public will receive from the alert (warning, information, recommended actions).







Street Address:

City:

State:

Zip:



169 of 189 7/22/2016 1:15 PM


14.4 Permitted Systems S ystems .

The following types of systems shall be permitted employed for alerting the public :

(1) Automated telecommunications dial-out systems delivering recorded voice messages

(2) Automated telecommunications dial-out systems with signals transmitted to a PASAA

(3)

(4) Wireless systems with a PASAA

(5) Paging systems with a PASAA

(6) Siren systems with loudspeakers

(7) Integrated public alert and warning system (IPAWS)

(8) In the event that these systems are not available, the AHJ may employ alternate communicationssystems that meet the immediate need for communicating with the public


The title "Permitted Systems" indicates that these are the only systems that may be used to alert the public during an event. Any system the meets the need of the AHJ and the public the AHJ needs to reach should be allowed. The current text may cause an AHJ to not investigate all options.







Street Address:

City:

State:

Zip:


* Radio broadcast systems and tone alert systems using a PASAA


170 of 189 7/22/2016 1:15 PM

Public Input No. 68-NFPA 1221-2016 [ Section No. A.3.3.1 ]

A.3.3.1

Alarm.

All incoming calls on designated emergency telephone lines should be considered emergency alarms untilanswered by a telecommunicator. If a telecommunicator determines that the reason for the call is not anemergency as defined in 3.3.40 , the call will not count against the performance requirements of 7.4.2 . Atrouble or supervisory signal is not an indication of an alarm. (See also 3.3.105 , Trouble Signal.)

Alarms are events received by electronic signal, i.e. fire alarm boxes, central station alarms, automatic crashnotification.






Street Address:

City:

State:

Zip:



171 of 189 7/22/2016 1:15 PM


A.3.3.40 Emergency.

The AHJ of the responding agency can determine which types of alarms events qualify as an emergency.






Street Address:

City:

State:

Zip:



172 of 189 7/22/2016 1:15 PM


A.3.3.41 Emergency Alarm Event Processing/Dispatching.

This term includes caller interrogation and resource selection [determination of which emergency responseunit (ERU) will respond] up to the start of the ERF notification process.






Street Address:

City:

State:

Zip:



173 of 189 7/22/2016 1:15 PM

Public Input No. 69-NFPA 1221-2016 [ New Section after A.3.3.44 ]

A.3.3.x Event.

All incoming calls on designated emergency telephone lines should be considered emergencyevents until answered by a telecommunicator. If a telecommunicator determines that the reason forthe call is not an emergency as defined in 3.3.40 , the call will not count against the performancerequirements of 7.4.2 . A trouble or supervisory signal is not an indication of an event. (Seealso 3.3.105 , Trouble Signal.)






Street Address:

City:

State:

Zip:



174 of 189 7/22/2016 1:15 PM

Public Input No. 72-NFPA 1221-2016 [ Section No. A.7.3.1.1 ]

A.7.3.1.1

In jurisdictions receiving fewer than 730 alarms events per year (an average of two alarms events per24-hour period), provision of a dedicated telecommunicator might not be necessary where alternate meansapproved by the AHJ can effect the prompt receipt and processing of alarms events in accordance withSection 7.4. Telecommunicator staffing is an important issue in achieving prompt receipt and processing ofalarms events . Consider the following two concepts of communications center operations:

(1) Vertical Center. A single telecommunicator performs both the call-taking and dispatching functions.

(2) Horizontal Center. Different telecommunicators perform the call-taking and dispatching functions.

Telecommunicators working in a vertical center are known to engage in multitasking that can inhibit theirability to perform assigned job functions. Routine evaluation of telecommunicator staffing, number ofinbound emergency and nonemergency calls, and other operational statistics are necessary to allow aprompt receipt and processing of alarms events .






Street Address:

City:

State:

Zip:



175 of 189 7/22/2016 1:15 PM


A.7.4.1

Statistical analysis for performance measurement should be completed over a period of 1 month as shownin Figure A.7.4.1(a) and Figure A.7.4.1(b).

Figure A.7.4.1(a) Alarm Time Line Where Primary PSAP Is Communications Center.

During last revision cycle, both figures were changed to say "alarm processing begins when theemergency call for service is created..." This conflicts with the wording describing EmergencyAlarm Processing/ Dispatching- A process by which an alarm answered at the communicationscenter creates a call for service and is transmitted to emergency response facilities (ERFs) or to

emergency response units (ERUs) in the field. This process is also supposed to includeinterrogation, which would include the first question asked by the call taker. If the intention is foralarms to still be measured beginning at the time of call answer, please correct the wording to say

"Alarm processing begins at the time the call is answered...” If the intention is to begin themeasurement at another time, can the actual standard language for 3.3.41 and A.3.3.41 be

modified as well to indicate what point of measurement is considered the "call for service beingcreated."

Figure A.7.4.1(b) Alarm Time Line Where Primary PSAP Is Other Than Communications Center.


Correction to Explanatory material that conflicts with standard wording.





Street Address:

City:

State:

Zip:



176 of 189 7/22/2016 1:15 PM


A.7.4.1

Statistical analysis for performance measurement should be completed over a period of 1 month as shownin Figure A.7.4.1(a) and Figure A.7.4.1(b).

Figure A.7.4.1(a) Alarm Event Time Line Where Primary PSAP Is Communications Center.

Figure A.7.4.1(b) Alarm Event Time Line Where Primary PSAP Is Other Than CommunicationsCenter.

Diagrams need to be changed - replace "Alarm" with "Event"






Street Address:

City:

State:

Zip:



177 of 189 7/22/2016 1:15 PM

Public Input No. 17-NFPA 1221-2016 [ New Section after A.7.4.3 ]

Reference to the below section:

A7.4.3 Alarms should be retransmitted to emergency response personnel as soon as the location andgeneral nature of the emergency have been ascertained by the telecommunicator.

Can the above section in bold be added/ clarified in standard language somewhere and not just theexplanatory material? It seems the intent of this 7.4.3 section is to focus on the scene safety aspect andthe fact that additional interrogation may be required prior to dispatching the call; however, the verbiageclearly states that once a location and general nature are determined the call should be retransmitted. Sodoes that mean if there are no scene safety concerns, that the call should be immediately dispatched toFire Rescue once these 2 pieces of information are obtained? I am unable to find any standard languagerecommending this form of call processing. If the intention is to obtain the location and nature, thentransmit the call, is there an exception for agencies that use EMD protocols/Q&A to identify thesub-determinant prior to dispatching?


Clarify wording that is used in the explanatory material that is not currently referenced in the standard language.





Street Address:

City:

State:

Zip:



178 of 189 7/22/2016 1:15 PM


A.7.4.3

Alarms Events should be retransmitted to emergency response personnel as soon as the location andgeneral nature of the emergency have been ascertained by the telecommunicator. However, for somealarms events involving criminal activity, the safety of emergency response personnel could require thetelecommunicator to ascertain additional information from the caller, such as a description(s) of thesuspect(s), a description(s) of the vehicle(s), the direction of travel, and the weapon(s) involved, whichcould make compliance with the 60-second time limit impractical. Therefore, the AHJ for each lawenforcement agency served by the communications center should establish time frames for the dispatch oflaw enforcement personnel in accordance with the corresponding agency's SOPs.






Street Address:

City:

State:

Zip:



179 of 189 7/22/2016 1:15 PM

Public Input No. 75-NFPA 1221-2016 [ Sections A.9.1.1, A.9.1.1.3.2, A.9.1.1.3.3 ]

Sections A.9.1.1, A.9.1.1.3.2, A.9.1.1.3.3

A.9.1.1

Communications centers that dispatch for volunteers or paid-call personnel have the responsibility ofsummoning such personnel at any hour of the day or night. Personnel can be summoned by the use of thetelephone or radio, supplementing sirens or horns that provide an outside alarm. Alarms Events can betelephoned to the central telephone office where the telephone telecommunicator can start a siren oroperate an air horn to indicate that there is an alarm event . In areas where a communications center is notattended 24 hours a day, telephone companies can provide a telephone line that connects to specialtelephones that are located in places of business or residences selected by the jurisdiction. The jurisdictionthen arranges to activate the alarms telephone lines . In emergency response agencies that have anemergency response facility desk attendant, the telephone central telecommunicator can call the ERF, andthe attendant can sound the outside alarm to call volunteers. If there is a code-sounding siren or air horn,coded signals can be sent. Usually a transmitting apparatus is used to send out the code.

If radio equipment is used, a receiver with selective calling equipment can be placed in the home of eachvolunteer or call person. Selective signaling is accomplished on a group-call principle, allowing thevolunteer or call forces to be divided into several groups that can be summoned as a whole or as individualgroups to handle a particular incident. Pagers are commonly used for this purpose, since they can becarried anywhere. Pagers can include either a tone alarm, a voice receiver, or a digital display.

A.9.1.1.3.2

In jurisdictions receiving fewer than 730 alarms events per year (average of two alarms events per24-hour period), a second dedicated dispatch circuit might not be necessary.

A.9.1.1.3.3

When an alarm event is transmitted to an ERF, it should be audible throughout the ERF, without the timedelay caused by a responder going to a telephone instrument, picking up the handset, and then relaying theinformation to other affected responders.






Street Address:

City:

State:

Zip:



180 of 189 7/22/2016 1:15 PM

Public Input No. 76-NFPA 1221-2016 [ Section No. A.9.3.4.1.24 ]

A.9.3.4.1.24

In the design and operation of a trunked radio system, dispatching of alarms events has to have priorityover all other communications and is equal in priority to emergency messages from the field. For thisreason, when units are dispatched over radio, the necessary priority is high enough to require “ruthlesspreemption,” which is the seizure and re-use of channels already in use by other conversations previouslydefined as lower in priority.






Street Address:

City:

State:

Zip:



181 of 189 7/22/2016 1:15 PM


A.10.4.1. 1 2

Other data elements that could be used, based on the functionality needed by the AHJ, are the following:

(1) Units responding from sending agency

(2) Status changes from units (ongoing)


The nature of the explanatory material associated with A.10.4.1.1 appears to refer to 10.4.1.2. If so, this item should be renumbered to A.10.4.1.2 and the associated reference changed to 10.4.1.2.




Street Address:

City:

State:

Zip:



182 of 189 7/22/2016 1:15 PM


A.10.5.7.2

The requirements for audible notification for all text message activations regarding alarms or otheremergencies events apply even if there are other methods of notification installed and used at the ERF.






Street Address:

City:

State:

Zip:



183 of 189 7/22/2016 1:15 PM

Public Input No. 127-NFPA 1221-2016 [ New Section after B.1 ]

B.2 Trunked Radio Sharing - Memorandum of Understanding

See Figure B.2.



Trunked_Radio_Sharing_MoU_Template.pdf


In addition to sharing of frequencies, systems operators may choose to share trunked radio channels in order to promote communications and interoperability between using agencies. This template provides a baseline for a memorandum of understanding between such using agencies.




Street Address:

City:

State:

Zip:



184 of 189 7/22/2016 1:15 PM

Public Input No. 128-NFPA 1221-2016 [ Section No. C.1.2.1 ]

C.1.2.1 Number of 9-1-1 Centers.

The number of 9-1-1 emergency reporting communications centers or PSAPs is one of the key factors thatshould be considered in the planning of a 9-1-1 system. If multiple answering points are located throughoutthe system (jurisdiction), many factors can influence the way in which 9-1-1 calls are handled. For instance,telephone company and jurisdiction boundaries are rarely coincident. Therefore, calls are routed toimproper answering points, and time delays are encountered in handling or rerouting the 9-1-1 calls.

Having a single answering point minimizes the boundary problem; however, other functions, such asdispatch, become more difficult.

During the planning of a 9-1-1 system, many factors should be considered. The administrative andoperational procedures of the answering bureau and the available 9-1-1 system features should bereviewed carefully.


Revise wording in keeping with current definitions in Chapter 3, Reference 3.3.20




Street Address:

City:

State:

Zip:



185 of 189 7/22/2016 1:15 PM


C.1.2.6 Computer-Aided Dispatching (CAD) Systems.

Many jurisdictions employ or are considering a CAD system. Several enhanced 9-1-1 system featurescomplement CAD systems and should be carefully considered in the planning of a 9-1-1 system with a CADinterface. To comply with 7.4.1, 7.4.2, and Section 12.5, it is essential that the CDR and the dispatchinginterface for each alarm event capture the following:

(1) Time of seizure

(2) Time of answer

(3) Time of disconnect or transfer

(4) Time of notification

(5) Time of initial dispatch processing

(6) Time of dispatch completion






Street Address:

City:

State:

Zip:



186 of 189 7/22/2016 1:15 PM


C.1.2.7 Fire Emergency Call Handling.

In most cases, current systems, most emergency calls are connected directly to the PSAP ( 9-1-1 fire callsare call and dispatch center) and not routed directly to fire dispatch centers. The first-response centersare required to reroute the calls to the appropriate fire communications center. Therefore EmergencyResponse Agencies. In most cases the PSAP dispatches Emergency Response Agencies directly. In veryfew instances the PSAP may reroute the call to another PSAP or Emergency Response Agency. In eithercase , 9-1-1 features that minimize call-handling time ( especially internal and rerouting) should shall beconsidered in the planning of a 9-1-1 system.


The current trend of consolidating communications centers (PSAPs) the occurrence of transferring calls to alternate dispatch locations is becoming the exception rather than the norm. The critical message in this item is that whether the calls are rerouted internally (call taker to dispatcher) or externally (other PSAP or Emergency Response Agency) call handling time is critical to the success of the response. Therefore, any 9-1-1 system design must incorporate strict requirements for call processing and handling.




Street Address:

City:

State:

Zip:



187 of 189 7/22/2016 1:15 PM

Public Input No. 80-NFPA 1221-2016 [ Section No. D.1.1.1 ]

D.1.1.1

Alarm Event times should also include, as a minimum, the following characteristics:

(1) Source

(2) Priority

(3) Type






Street Address:

City:

State:

Zip:



188 of 189 7/22/2016 1:15 PM

Public Input No. 79-NFPA 1221-2016 [ Section No. D.4 ]

D.4 Automated Exchange of Digital Information.

The automated exchange of digital information related to alarm objects events between thecommunications center and external systems should be accomplished in accordance with standardspublished by the National Emergency Number Association (NENA) and the Association of Police PublicSafety Communications Officials, International (APCO).

The automated exchange of digital information between communications centers should be accomplishedin accordance with standards published by APCO.

The automated exchange of information between the communications center and transportation informationsystems should be accomplished in accordance with standards registered with the IEEE IntelligentTransportation Systems (ITS) Data Registry.






Street Address:

City:

State:

Zip:



189 of 189 7/22/2016 1:15 PM