Recommendations of the Emergency Communications Task Force · PREFACE Task Force Background The Emergency Communications Task Force (hereafter, “Task Force”)1 was jointly formed

APCO International

IJIS Institute

August 2013

Lead Authors

Steve Wisely, APCO International

Donald Gabbin, IJIS Institute

Paul Wormeli, IJIS Institute

RECOMMENDATIONS OF THE EMERGENCY COMMUNICATIONS TASK FORCE

Recommendations of the Emergency Communications Task Force

Emergency Communications Task Force Page i

ACKNOWLEDGEMENTS The IJIS Institute and APCO International are sincerely grateful to the Emergency Communications Task Force members who volunteered time, expertise, and leadership to support the work of this important endeavor. We are appreciative of the input, participation, and knowledge of the following individuals:

TASK FORCE

MEMBER TITLE ORGANIZATION

James Lipinski North American Solution Architect

Accenture Police Business Services

Adam Thiel Fire Chief Alexandria Fire Department (Virginia)

Eddie Reyes Deputy Chief Alexandria Police Department (Virginia)

Crystal McDuffie Communications Center & 9-1-1 Services Manager

APCO International

Steve Wisely Senior Project Coordinator, Comm Center & 9-1-1 Services

APCO International

Jorge Hurtado Project Manager / Senior Engineering Manager

CACI International

Phil Ardire Senior Network Engineer CACI International

Donna Dugger Communications Supervisor Center Police Department (Texas)

Jon Hannan Fire Chief Charlotte Fire Department (North Carolina)

Joseph Barasoain

Operations Chief City of Alexandria Department of Public Safety Emergency Communications & Management

Jerry Schlesinger RegJIN Project Manager City of Portland – Portland Police Bureau

John Rosati Vice President, Sales & Marketing

Communications International

Eric Kutner Founder Emergency Response Design Group (ERDG)

Nate Daniels VP Data Integration FATPOT Technologies

Randy Kent Project Manager IJIS Institute

Todd Crago Solutions Architect InterAct Public Safety

Cameron Smith CIP Business Manager Intergraph Government Solutions

Jeff Dunne Chief Scientist, Cyber Assessments

Johns Hopkins University Applied Physics Laboratory

Jason Hutchens Motorola Solutions

Ahsan Baig Manager, Information Systems Office of Information Technology, City of Oakland (California)

Dr. Carolyn Wong

Senior Research Staff RAND Corporation

John Hollywood Director RAND Corporation; National Law Enforcement and Corrections Technology Center (NLECTC) Information and Geospatial Technologies Center

Michael Weins, PMP, ENP

Director RCC Consultants, Inc.


Emergency Communications Task Force Page ii

TASK FORCE

MEMBER TITLE ORGANIZATION

Bonnie Maney Public Safety Training Manager & Information Sharing Specialist

SEARCH, National Consortium for Justice Information and Statistics

Steven Hoggard Program Manager Spillman Technologies

Judd Cain Executive Vice President, Global Managed Networks and Services

Tait Communications

Scott Jones Director, Managed Services Marketing and Business Development

Tait Communications

Maj. David Mulholland

Commander, Technical Services

United States Park Police


Emergency Communications Task Force Page iii

CONTENTS

ACKNOWLEDGEMENTS ......................................................................................................................................... I

CONTENTS .............................................................................................................................................................. III

PREFACE .................................................................................................................................................................... 1

Task Force Background ................................................................................................................................... 1

Task Force Goals ................................................................................................................................................ 1

Evolution of Previous Efforts .......................................................................................................................... 2

2003-2006 .............................................................................................................................................................................................. 2 2009 ........................................................................................................................................................................................................... 2 2010-2011 .............................................................................................................................................................................................. 2 Other Related Efforts ......................................................................................................................................................................... 3

INTRODUCTION ...................................................................................................................................................... 3

RECOMMENDATIONS ............................................................................................................................................ 5

#1—Simplify and standardize the exchange of information between CAD and RMS. ................. 5

#2—Support and develop specifications and standards for critical information exchanges. . 6

#3—Create a universal standard for CAD information exchanges. .................................................. 7

#4—Develop a new and innovative model of mobility for emergency responders. ..................... 8

APPENDICES .......................................................................................................................................................... 10

Public Safety Communications Connections Matrix ............................................................................. 10

Lead Organizations ......................................................................................................................................... 19

About the IJIS Institute .................................................................................................................................................................... 19 About APCO International ............................................................................................................................................................. 19

Acronyms and Abbreviations ....................................................................................................................... 19


Emergency Communications Task Force Page 1

PREFACE

Task Force Background The Emergency Communications Task Force (hereafter, “Task Force”)1 was jointly formed by the IJIS Institute and the Association of Public-Safety Communications Officials (APCO) International as a follow-on to earlier efforts to explore the needs for standards in relation to sharing information across jurisdictional and service boundaries in emergency communications. Both of the sponsoring organizations for this Task Force have come to realize that there are a variety of efforts underway to improve information sharing; and, with the advent of major changes, such as the introduction of Next Generation 9-1-1 (NG9-1-1) and First Responder Network Authority (FirstNet), there are strong reasons to have a coordinated and broadly reaching collaboration on what needs to be done to move toward effective implementation of these powerful new concepts. Accordingly, the primary purpose of the Task Force was to define the scope and priority of issues relevant to information sharing and standards-based interoperability for NG9-1-1 and related emergency communications and data management technology solutions. The Task Force sought input from industry and all levels of government—Federal, state, local, tribal, and territorial—to define the context of national standards. An inaugural meeting of the Task Force was held on January 23, 2013 at the IJIS Institute’s 2013 Industry Briefing in Arlington, Virginia. The nearly 20 members of the new Task Force attended the first meeting. Task force members considered the major issues within Emergency Communications that the IJIS Institute and APCO International should address. The Task Force was intended to work for approximately six months, during which time the members would work to prioritize exchanges and to determine how to most effectively pursue next generation emergency communications interoperability. The recommendations that comprise that majority of this document are based on the consensus belief that these are the highest priority tasks that APCO International and the IJIS Institute should undertake.

Task Force Goals Based on the agreement of the members, the goals of the Task Force are to:

1) Prepare a general assessment of next generation communications and data management technology capabilities specific to communications and data management in the emergency response domain and define critical information sharing issues.

2) Identify and assess information sharing and interoperability architectures and align national standards that can apply in a national context.

3) Identify stakeholder organizations and their roles in the adoption and use of national standards for information sharing and interoperability.

4) Prioritize national issues and determine urgent critical actions.

1 A full list of acronyms and abbreviations is included in this document.



Evolution of Previous Efforts This section details some of the historical efforts undertaken by APCO International, the IJIS Institute, and others. It is important to note that both the IJIS Institute and APCO International have been involved in numerous previous efforts related to computer-aided dispatch (CAD) functionality and standards, as well as efforts related to ensuring that emergency communications continues to leverage national standards. While much of this work has been reactionary, the work of the Task Force takes a forward-looking approach at identifying how standards will continue to play a role as NG9-1-1 and other new technologies continue to manifest themselves. By pursuing the recommendations as suggested, emergency communications officials and those that desire to share information with them, would benefit from being in a position to effectively plan for the rigors and demands of next generation requirements and needs rather than being forced to react to them.

2003-2006 The Standard Functional Specifications for Law Enforcement CAD Systems document was developed in conjunction with the International Association of Chiefs of Police’s (IACP) Law Enforcement Information Technology Standards Council (LEITSC): to provide a starting point for law enforcement agencies to use when developing CAD Request For Proposals (RFP); to provide a basis for software providers to use in their release planning; and, to promote system interoperability (e.g. CAD-to-CAD). LEITSC was a collaborative effort of the National Organization of Black Law Enforcement Executives (NOBLE), the National Sheriffs’ Association (NSA), the Police Executive Research Forum (PERF), and the IACP to bring a national perspective to these issues. The work was managed under the direction of the IACP, with support from the IJIS Institute. This document focused on CAD functionality to support law enforcement operations.

2009 The Public Safety Data Interoperability (PSDI) Project identified the need to expand the original LEITSC document to include CAD functions that support fire service and Emergency Medical Services (EMS) dispatching, resulting in the release of the Revision Assessment for the Incorporation of Fire and EMS Functions into the Law Enforcement CAD Functional Specifications. This revision assessment provided the basis for determining the level of effort required to incorporate fire and EMS functional requirements into the existing Standard Functional Specifications for Law Enforcement CAD Systems document, and specifically described fire and EMS CAD functionality that would need to be added. It also made numerous suggestions to modify the existing language and structure. Finally, it served as a supplement to the existing document for those needing a more complete list of base CAD functionality.

2010-2011 In response to the issues identified in the revision assessment document, APCO International and the IJIS Institute, on behalf of the Bureau of Justice Assistance (BJA), launched the Unified CAD (UCAD) Project in 2010. The UCAD Project was formed to create the Unified CAD Functional Requirements (UCADFR)—a detailed, comprehensive and unified set of functional requirements for CAD systems.

https://it.ojp.gov/documents/LEITSC_Law_Enforcement_CAD_Systems.pdf

http://ijis.org/docs/ijis_CADFS_Rev_Assm_20100128.pdf

http://ijis.org/docs/ijis_CADFS_Rev_Assm_20100128.pdf

http://www.ijis.org/docs/Unified_CAD_Functional_Requirements_FINAL.pdf

http://www.ijis.org/docs/Unified_CAD_Functional_Requirements_FINAL.pdf



The project committee was comprised of 22 subject matter experts from various stakeholder disciplines (i.e. emergency communications, law enforcement, fire service, EMS, and industry). The UCADFR can be an invaluable resource to these communities by supporting the planning, acquisition and management of full-featured CAD software applications. The UCADFR identifies and describes over 130 CAD functions in 11 different topic areas and provides information on future issues for CAD systems, such as NG9-1-1 and Broadband/LTE (Long-Term Evolution).

Other Related Efforts

FirstNet CAD will be a key component in the integration of new and robust resources like the FirstNet national broadband network. FirstNet is intended to provide a nationwide broadband network for emergency first responders based on a set of common standards to ensure interoperability across public safety and police agencies at state, local, and Federal levels.

Emergency Incident Data Document A planned component of the NG9-1-1 initiative is the development of a national, standardized, NG9-1-1 National Information Exchange Model (NIEM)-conformant, data exchange model called the Emergency Incident Data Document (EIDD). The EIDD exchange is planned to support not only the data required by NG9-1-1 but also to support CAD data relevant for Public Safety Answering Points (PSAP) to share [for CAD-to-CAD call transfers, unit updates, situational awareness, CAD-to-RMS (Records Management Systems), etc.]. This exchange will greatly enhance public safety interoperability and will likely be one of the most valuable and significant projects to advance information sharing for the more than 6,000 primary and secondary public safety communication centers, along with the first responders and emergency management agencies they support. The EIDD project is spearheaded by the National Emergency Number Association (NENA) and APCO International. The promise of EIDD is that it will be the superset, standardized model that has the ability to provide broad scale CAD data sharing and to link the so-called data silos, both large and small.

INTRODUCTION Any discussion of information sharing in emergency communications inevitably begins to focus on the functions that need to be inherent in a responsive CAD system. A CAD system is:

The principal application used by public safety agencies to manage law enforcement, fire, and EMS incidents from the initial time an incident is reported to the conclusion of the incident;

Used to track the status and location of resources, and for post-incident analysis of the response; and,

The point of origin for incident information that is then typically forwarded to an RMS.



A CAD system consists of either a single software application or a suite of integrated software packages used to: initiate a public safety call for service (CFS) record; recommend the resources to be dispatched; maintain the status of responding units and resources in the field; and, manage the incident. It is typically used by emergency communications dispatchers, call takers, and telecommunicators in public-safety communications centers. Modern CAD systems are usually extended out to field personnel (responders) through their mobile data computers (MDC), remote connections, and/or other devices, such as smartphones and tablets. The CAD system is one of the most important tools utilized by a PSAP, making it a mission critical system. The lives of citizens and public safety personnel heavily depend on the CAD system consistently performing at its maximum operational effectiveness and reliability. Although a CAD system is just one of many systems that public safety departments utilize, it is often considered the heart of public safety operations. Following are a few of many reasons for this:

1) Virtually all law enforcement, fire, and EMS incidents flow through the CAD system. CAD systems are designed to support the dispatch function, and incident, location, and resource information are all captured as part of the process.

2) Many public safety technology systems, such as 9-1-1, Geographic Information System (GIS)/Mapping, Automatic Vehicle Location (AVL), MDCs, RMS, and data mining applications are either an integrated part of, or are interfaced with, the CAD system.

3) The CAD system is often the primary connection CAD users have to external systems, including neighboring and remote CAD systems, local and regional RMS, and for records checks of state and federal criminal databases such as the Department of Motor Vehicles (DMV), Nlets (The International Justice & Public Safety Network), or the Federal Bureau of Investigation’s (FBI) National Crime Information Center (NCIC), Interstate Identification Index (III; or, Triple I), Integrated Automated Fingerprint Identification System (IAFIS), or National Data Exchange (N-DEx).

4) The CAD system is the primary tool used for public safety resource management. CAD systems consist of several modules that provide a variety of services and functions at multiple levels within a public safety communications center. These services include call input, call dispatching, call status maintenance, event notes, resource unit status and tracking, and call resolution and disposition.

Further, CAD systems include interfaces that permit the software to provide services to dispatchers, call-takers, and field personnel with respect to incident command and the control and use of radio and telephony equipment, Emergency Medical Dispatch (EMD), external RMS, and other internal and external systems, as well as other services and functions. Given the significant role that CAD systems play in the delivery of emergency services and their key role as the supporting infrastructure for emergency communications, the Task Force was adamant about the need to solve some of the most pressing and pervasive problems that have inhibited information sharing across jurisdictions and within agencies.



In this awareness, the Task Force makes the following four (4) recommendations for action by the Boards of APCO International and the IJIS Institute:

1) Simplify and standardize the exchange of information between CAD and RMS.

2) Support and develop specifications and standards for critical information exchanges.

3) Create a universal standard for CAD information exchanges.

4) Develop a new and innovative model of mobility for emergency responders.

RECOMMENDATIONS

#1—Simplify and standardize the exchange of information between CAD and RMS. The Task Force believes it is essential for APCO International and the IJIS Institute to collaborate on removing the remaining barriers to interoperability in both intra- and inter-agency RMS/CAD exchanges. We believe that the cost of CAD and RMS today is unnecessarily inflated by the difficulty of exchanging the needed information between these systems – particularly when they have been acquired from different companies. As the importance of greater situational awareness grows, and as agencies seek to implement modern practices such as real-time crime centers, we can no longer afford the complex and costly system interfaces of the past that were, and are, mostly “one-offs.” This work would include setting clear and unquestionable American National Standards Institute (ANSI) standards for the exchanges between CAD and RMS, covering the entire data component sets that the business exchanges mandate. The development efforts should be the pilots for complying with the proposed standard for building information exchange standards under Recommendation 3. There is also a need for: developing common ways of incorporating NIEM, the Global Reference Architecture (GRA), and Information Exchange Package Documentation (IEPDs); limiting the need for agency customization; and, using improved processes to work with agencies to define interoperability. NIEM should be engaged going forward to determine the need and feasibility for NIEM standards to be extended and harmonized to ensure consistent data treatment of elements of information across IEPDs. It is also essential to provide standard guideline suggestions for NIEM and other key standard compliance, at a minimum, in acquisition guides for agencies, listing the standards with which an RMS/CAD system should comply. Specific RFP language, updated to reflect the most recent key standards, would also be of use. It is essential to define and set the standards for the interconnection between systems in a way that provides for a common standard approach to the movement of data, while maintaining the flexibility of either system to sustain its purpose. We note that it is insufficient to simply insist on NIEM conformance, as its very flexibility keeps us from establishing clear and certain standards for information exchange that must be developed if costs for these systems are to be controlled.



The Task Force believes that the partnership of APCO International and the IJIS Institute could find a clear path to providing education and guidance to software providers to help them guide agencies through their information exchange needs (and resulting use cases) in order to determine and prioritize interoperability requirements cooperatively rather than simply to ask agencies for their interoperability requirements. The Task Force views the development of a standard for information exchanges between CAD and RMS as an important first step but notes that there is a critical need to address information exchanges between CAD systems – across the range of CAD products and across jurisdictions. This CAD-to-CAD interaction is also complicated by the need to address the information exchanges across first responder services and mutual aid policies. While this issue has been addressed in prior efforts to create a common standard, no such standard has emerged—and the Task Force urges the IJIS Institute and APCO International to add this requirement to the future action plans.

#2—Support and develop specifications and standards for critical information exchanges. After considering 36 separate information exchanges, the Task Force concluded that a subset of 11 of these were important enough to continued improvement in operations that the full force and support of APCO International and the IJIS Institute should be applied to create extensions to the model RMS/CAD standard (Recommendation 1) to support these exchanges, test them, develop them to meet ANSI criteria, and then provide certification testing on them. We emphasize that the 11 exchanges be supported through extensions of the RMS/CAD standard identified under Recommendation 1, as well as comply with the new standard for building emergency communications exchange standards under Recommendation 3. In creating these extensions, modifications over the base RMS/CAD standard should be kept to a minimum, and should be strictly limited to those needed to address role and environmental differences. Efforts will be needed to ensure consistency across the extensions. This approach will be much more tractable, and will support far more interoperability than developing 11 different standards. The specific information exchanges for which we urge action by APCO International and the IJIS Institute are the following:

CAD - CAD (other jurisdiction)

CAD - EMS Mobile

CAD - EMS RMS

CAD - EOC

CAD - Fire Mobile

CAD - Fire RMS

CAD - Fusion Center

CAD - LE Mobile

CAD - LE RMS

CAD - NG9-1-1

LE RMS - LE Mobile



These exchanges may be broadly categorized as:

Ensuring information sharing between CAD, RMS, and mobile units within and across agencies;

Ensuring information sharing between CAD and state and regional EOCs and fusion centers; and,

Ensuring that CAD can receive and exploit the new types of information supported by NG9-1-1.

These 11 information exchanges form a highest-priority emergency communications network centered on CAD systems, as shown in the following figure:

CAD

NG 9-1-1

LE Mobile Fire RMS

EMS RMSCAD (other jurisdiction)

LE RMS

Fire Mobile

EMS Mobile

EOC Fusion Center

#3—Create a universal standard for CAD information exchanges. The Task Force believes it is now possible to create a single standard for constructing information exchanges in emergency communications. We strongly recommend: that the IJIS Institute and APCO International Boards undertake projects to develop such a universal standard; that this standard then be put through the processes required to become an ANSI standard under APCO International’s ANSI process; and, that the IJIS Institute incorporate this standard in its Springboard program so as to create a national capability to certify software providers that can pass independent certification of conformance testing for products they claim to be compliant. We further submit that existing governance processes and bodies should be enabled to support and sustain such a standard so that it might mature and respond to such changes in operations and technology – as may become part of the practice and discipline of emergency communications. Some of the characteristics that may be required in such a standard are:

1) The interface supports bidirectional data flow 2) Data format independent (e.g. voice, video, data, etc.) 3) XML based/NIEM-conformant, supporting GRA 4) Built on EIDD work that is in progress 5) Data transport independent (e.g. TCP/IP, SIP, radio, etc.) 6) Data sent from a single source can be targeted to one or many recipients



7) Data received by a single recipient can be from one or many senders 8) Each endpoint in the data exchange (sender, receiver) can be authenticated if required 9) Sender can determine who can receive its data 10) Recipient can determine who they receive data from 11) Supports encrypted communication based on endpoint identities 12) Supports prioritization by sender (e.g. the sender can assign a priority code to data) 13) Supports prioritization by receiver (e.g. the receiver can determine what order they want to

prioritize incoming data) 14) Data is time stamped and synchronized; multiple data flows can be combined and presented in

chronological order if necessary 15) Supports proof of delivery

#4—Develop a new and innovative model of mobility for emergency responders. The work of first responders is inherently done in the field and is field- focused. In order to support this, it is critical we move to a model that supports enhanced mobility, interoperability, and integration. Increasing the efficiency and effectiveness of law enforcement, fire, and EMS responders in the field can be accomplished by creating an integrated mobile capability that drives making data readily available to field personnel using a wide variety of mobile devices. For example, it has been proven that a police officer’s effectiveness in identifying stolen vehicles is increased by a factor of 10 or more by providing license plate readers (LPRs) to officers while they are on patrol. An LPR can identify stolen vehicle plates in a matter of seconds in the background as law enforcement officers routinely drive around/patrol their assigned districts. The equivalent time for officers to manually identify a stolen car as it drives by is a much more intensive process that requires positive action and research by officers. The efficiency/effectiveness multiplier can be significantly increased by immediately downloading stolen vehicle information through expedited data exchanges between regional and local RMS and the devices and software resident in officer’s vehicles. Similarly, it is well known in the field that fire and EMS personnel can become much more effective in their respective assignments when data pertaining to their work is readily available. Firefighters need immediate and complete information (e.g. premises, points of entry, chemical storage unit locations, etc.). EMS responders can be much more effective in preliminary response to a patient when they know more about the patient’s medical history (e.g. allergies, etc.). These needs, when coupled with the revolutionary technology innovations that we have seen in the past decade, suggest that it is time to create a new concept of operations for the deployment of mobile devices and their interconnectivity though the variety of emerging networks and higher speed exchange capabilities. Further, the rapidly emerging technologies associated with the new mobility concepts will have impact on the operational practices of mobile workers—and, these paradigm shifts must be recognized in defining new requirements for the introduction of the newer generations of technology. The Task Force believes that the IJIS Institute and APCO International could continue their partnership and, under this topic, develop a new concept of operations (ConOps) and a new design for the application of technology, and undertake a demonstration project to test and explore such further development.



Finally, the Task Force believes that an ongoing assessment of current issues as they develop justifies the continuation of some form of deliberative body, such as a task force or advisory committees, where both APCO International and the IJIS Institute can continue to have a sound footing for undertaking projects serving the entire emergency management community. We suggest to the Boards of Directors that ongoing studies of this nature will benefit the whole field, as technologists and practitioners collaborate on the development of forward motion.



APPENDICES

Public Safety Communications Connections Matrix The matrix below shows the connections between entities and the public safety need to support these connections.

CONNECTION

BETWEEN

WHAT

ENTITIES

PUBLIC SAFETY NEED

FREQUENCY

SINGLE

PROVIDER

CURRENT FREQUENCY

MULTI-PROVIDER

DATA/ INFORMATION

SAMPLES

REFERENCE

STANDARDS SPECIFIC TO

CONNECTION

CURRENT TOOLS

FOR DATA REPRESENTATION (IEPD/ SERVICE/

STANDARD)

TECHNICAL

ISSUES SPECIFIC TO THE

CONNECTION

POLICY &

PRIVACY ISSUES SPECIFIC

CONNECTION

KPI, OUTCOME &

MISSION

IMPROVEMENT

OPPORTUNITY, FUTURE NEEDS,

VISION

CAD - NG9-1-1

Critical Universal Universal Equivalent of today’s ANI/ALE, Need to use the

same GIS data as used for routing

calls, Need to be able to handle

streaming media.

EIDD, Others in NENA 08-003 (i3

specifications)

NENA/APCO working on emergency

incident data document (EIDD) American National

Standar (ANS)

Critical need for implementation of

NG9-1-1

Must be CJIS security compliant

CAD - Clock Sync

None Universal Universal Provides time sync information to CAD systems

IETF RFC 5905: Network Time

Protocol; NENA 08-003

Several other standards exits

inlcuding proprietary vendor

formats, which should be resisted.

FirstNet and i3 will provide time

synch informtion though network

interfaces. These should be

available and provide less

reliance on local time

synchronization clocks in the

future.

It is critical that all devices and application

software in a public safety

communication center are time

synchronized with each other

The interface for obtaining time synchronization information off networks will become more and more prevalent over time thereby reducing reliance on local clocks providing the information.



CONNECTION

BETWEEN

WHAT

ENTITIES

PUBLIC SAFETY NEED

FREQUENCY

SINGLE

PROVIDER

CURRENT FREQUENCY

MULTI-PROVIDER

DATA/ INFORMATION

SAMPLES

REFERENCE


CONNECTION

CURRENT TOOLS


STANDARD)

TECHNICAL


CONNECTION

POLICY &


CONNECTION

KPI, OUTCOME &

MISSION

IMPROVEMENT


VISION

CAD - Media (news)

Desired Occasional Common Publishing filtered emergency

incident information to data portals (internet and

Intranet sites) that are accessible to the news media and the public.

Publishing emergency notification

information such as boil water

orders, hazardous waste spills, etc.

OASIS Common Alerting Protool

(CAP) 1.2 can be adapted to

provide this kind of information. Other alerting protocols exist

and can also be used (NENA 56-003 Emergency

Notification Systems, etc.)

OASIS CAP 1.2 Filtering data sufficiently to

reduce verbal call to communication

centers, while maintaining

required confidentiality and not interfering with

emergency responses

Confidential and tactical

information needs to be filtered out

of the data exchanged through this connection

Increases communication center efficiency by reducing calls from the media regarding active and past emergency events



CONNECTION

BETWEEN

WHAT

ENTITIES

PUBLIC SAFETY NEED

FREQUENCY

SINGLE

PROVIDER

CURRENT FREQUENCY

MULTI-PROVIDER

DATA/ INFORMATION

SAMPLES

REFERENCE


CONNECTION

CURRENT TOOLS


STANDARD)

TECHNICAL


CONNECTION

POLICY &


CONNECTION

KPI, OUTCOME &

MISSION

IMPROVEMENT


VISION

CAD - LE Mobile

Critical Common Common Dispatch assignment and

information about assigned

emergency events, general

message (BOLOs,

meetings, officer safety, etc.), status and

location updates, query/response, updated incident

information, disposition codes, text messaging,

viewing streaming NG9-1-1 media.

EIDD, Others in NIEM are available)



Standar (ANS)

Bandwidth availabilituy

Data should be encrypted to meet

CJIS standards and to maintain

the confidentiality of tactical and

sensitive information

Increases officer and dispatch center efficiency, provides relevant information directly to emergency responders



CONNECTION

BETWEEN

WHAT

ENTITIES

PUBLIC SAFETY NEED

FREQUENCY

SINGLE

PROVIDER

CURRENT FREQUENCY

MULTI-PROVIDER

DATA/ INFORMATION

SAMPLES

REFERENCE


CONNECTION

CURRENT TOOLS


STANDARD)

TECHNICAL


CONNECTION

POLICY &


CONNECTION

KPI, OUTCOME &

MISSION

IMPROVEMENT


VISION

CAD - LE RMS

Critical Common Occasional Initial Incident Report; Active incidents search; Location based incident information; Warrant Info; Premise history; Arrest info; Cross-jurisdictional info concerning names, addresses, incident types; Roster; Incident numbers

Unified CAD Functional Requirements (will be a standard soon); NEMSIS EIDD

APCO Disposition Codes; APCO Incident Type Codes; 2-3 reference IEPDs; EIDD in development (will be a standard)

Confidentiality of exchanged information





Officer productivity tool as it diminishes redundant data entry and eliminates potential errors.

CAD - Fusion Center

Important Common Common Completed incident information along with real time event information in specialized cases (terrorist activity)

CAP, EIDD and many version of NIEM conformant exchanges



Standar (ANS)

Timeliness of the data





Increased potential for "connecting the dots" when data is shared among multiple agencies

CAD - Fire RMS

Critical Common Common Incident and inspection information

NFIRS 5.x several NIEM conformant exchanges are available

timeliness of the data and availability of the information to responders in the field

Data should be encrypted to maintain the

confidentiality of tactical and


Useful for statistical analysis and for in the field response information



CONNECTION

BETWEEN

WHAT

ENTITIES

PUBLIC SAFETY NEED

FREQUENCY

SINGLE

PROVIDER

CURRENT FREQUENCY

MULTI-PROVIDER

DATA/ INFORMATION

SAMPLES

REFERENCE


CONNECTION

CURRENT TOOLS


STANDARD)

TECHNICAL


CONNECTION

POLICY &


CONNECTION

KPI, OUTCOME &

MISSION

IMPROVEMENT


VISION

CAD - Fire Mobile




message (general announcements, meetings, safety

issues, etc.), status and





Several proprietary formats are used today, which should be replaced by standard interfaces

Bandwidth availability




Increases fire fighter and dispatch center efficiency, provides relevant information directly to emergency responders

CAD - Hospital

Important Occasional Occasional Hospital diversion information, applied patient procedures and vital stats transferred to receiving hospital

NEMSIS Several proprietary formats are used today, which should be replaced by standard interfaces





Increases hospital and responder efficiency (Dr/ER personnel aware of patient’s conditions and applied protocols prior to receipt, appropriate hospitals identified quickly, etc.)

CAD - EMS RMS

Critical



CONNECTION

BETWEEN

WHAT

ENTITIES

PUBLIC SAFETY NEED

FREQUENCY

SINGLE

PROVIDER

CURRENT FREQUENCY

MULTI-PROVIDER

DATA/ INFORMATION

SAMPLES

REFERENCE


CONNECTION

CURRENT TOOLS


STANDARD)

TECHNICAL


CONNECTION

POLICY &


CONNECTION

KPI, OUTCOME &

MISSION

IMPROVEMENT


VISION

CAD - EMS Mobile




message (general announcements, meetings, safety

issues, etc.), status and










Increases fire fighter and dispatch center efficiency, provides relevant information directly to emergency responders

CAD - EOC Critical Occasional Occasional informing EOC of appropriate incidents in real time, updating information as it is received

CAP, EIDD and many version of NIEM conformant exchanges





Increases coordination and response of specialized resources. Downstream notification of major events (e.g. homeland security, FEMS, etc.)



CONNECTION

BETWEEN

WHAT

ENTITIES

PUBLIC SAFETY NEED

FREQUENCY

SINGLE

PROVIDER

CURRENT FREQUENCY

MULTI-PROVIDER

DATA/ INFORMATION

SAMPLES

REFERENCE


CONNECTION

CURRENT TOOLS


STANDARD)

TECHNICAL


CONNECTION

POLICY &


CONNECTION

KPI, OUTCOME &

MISSION

IMPROVEMENT


VISION

CAD - CAD (other jurisdiction)

Critical Occasional Occasional Sharing incident information for mutual and automatic aid, sharing status and location information of share emergency resources



Interagency agreements for shared resources




Makes the entire public safety response system more efficient thorugh the sharing of resources. Expensive emergency resources and facilities can be shared rather than purchasing or building new ones.



CONNECTION

BETWEEN

WHAT

ENTITIES

PUBLIC SAFETY NEED

FREQUENCY

SINGLE

PROVIDER

CURRENT FREQUENCY

MULTI-PROVIDER

DATA/ INFORMATION

SAMPLES

REFERENCE


CONNECTION

CURRENT TOOLS


STANDARD)

TECHNICAL


CONNECTION

POLICY &


CONNECTION

KPI, OUTCOME &

MISSION

IMPROVEMENT


VISION

LE RMS - LE Mobile

Critical Occasional Occasional Query/response. Alerting responding officers to relevant information, notification of stolen items (vehicles, guns, etc.), descriptive information about people, vehicles, locations, and property items, wanted persons, incarcerated individuals, protection orders,field based reporting and report approval.



bandwidth, amount of information to present, user interface, etc.

Data must be encrypted to maintain the



Increases officer efficiency by extending available information to them in the field

LE RMS - LE State Databases

Important Common Common monthly uniform crime reports, daily NDEX submissions

NDEX IEPD and others are available in NIEM

Should standardize on one interface across all states





LE RMS - LE Federal Databases

Important Occasional Occasional NDEX, LINXNW -- Incident data

NDEX IEPD, LINXNW IEPD and others

Should standardize on one interface across all states







CONNECTION

BETWEEN

WHAT

ENTITIES

PUBLIC SAFETY NEED

FREQUENCY

SINGLE

PROVIDER

CURRENT FREQUENCY

MULTI-PROVIDER

DATA/ INFORMATION

SAMPLES

REFERENCE


CONNECTION

CURRENT TOOLS


STANDARD)

TECHNICAL


CONNECTION

POLICY &


CONNECTION

KPI, OUTCOME &

MISSION

IMPROVEMENT


VISION

LE RMS - Fusion Center

Important Common Common general offense reports, arrests, and other CJIS information

Several NIEM IEPDs are available

Should standardize on one interface across all fusion centers





Fire RMS - Fire Mobile

Important Common Occasional Incident information and updates

EIDD Standardize across EMS, Fire, and Health


Data should be encrypted to maintain the confidentiality of tactical and sensitive information

EMS RMS - EMS Mobile

Important Common Rare EIDD Standardize across EMS, Fire, and Health



Hospital - EMS Mobile

Important Occasional Common Hospital status, closure, reroute

EIDD Standardize across EMS, Fire, and Health





Lead Organizations

About the IJIS Institute The IJIS Institute unites the private and public sectors to improve mission-critical information sharing for those who protect and serve our communities. The IJIS Institute provides training, technical assistance, national scope issue management, and program management services to help government fully realize the power of information sharing. Founded in 2001 as a 501(c)(3) nonprofit corporation with national headquarters on The George Washington University Virginia Science and Technology Campus in Ashburn, Virginia, the IJIS Institute has grown to nearly 200 member and affiliate companies across the United States. For more information on the IJIS Institute, visit the website at: http://www.ijis.org/; follow on Twitter: @ijisinstitute; read the IJIS Factor Blog; or, join LinkedIn at: Justice and Public Safety Information Sharing.

About APCO International APCO International is the world’s largest organization of public safety communications professionals. It serves the needs of public safety communications practitioners worldwide - and the welfare of the general public as a whole - by providing complete expertise, professional development, technical assistance, advocacy and outreach.

Mission The Association of Public-Safety Communications Officials (APCO) is an international leader committed to providing complete public safety communications expertise, professional development, technical assistance, advocacy and outreach to benefit our members and the public.

Vision APCO International commits to strengthen our communities by empowering and educating public safety communications professionals.

Acronyms and Abbreviations ACRONYM OR ABBREVIATION DEFINITION

ANSI American National Standards Institute

APCO Association of Public-Safety Communications Officials

AVL Automatic Vehicle Location

BJA Bureau of Justice Assistance

CAD computer-aided dispatch

CFS call for service

ConOps concept of operations

DMV Department of Motor Vehicles

EIDD Emergency Incident Data Document

EMD Emergency Medical Dispatch

EMS Emergency Medical Services

ERDG Emergency Response Design Group

http://www.ijis.org/

https://twitter.com/ijisinstitute

http://www.ijis.org/EDblog/

http://www.linkedin.com/groups/Justice-Public-Safety-Information-Sharing-4104229?trk=myg_ugrp_ovr

http://www.linkedin.com/groups/Justice-Public-Safety-Information-Sharing-4104229?trk=myg_ugrp_ovr

http://www.apcointl.org/



ACRONYM OR ABBREVIATION DEFINITION

FBI Federal Bureau of Investigation

FirstNet First Responder Network Authority

GIS Geographic Information System

GRA Global Reference Architecture

IACP International Association of Chiefs of Police

IAFIS Integrated Automated Fingerprint Identification System (FBI)

IEPD Information Exchange Package Documentation

III (or, “Triple I”)

Interstate Identification Index (FBI)

LEITSC Law Enforcement Information Technology Standards Council (IACP)

LPR license plate reader

LTE Long-Term Evolution

MDC mobile data computer

NCIC National Crime Information Center (FBI)

N-DEx National Data Exchange

NENA National Emergency Number Association

NG9-1-1 Next Generation 9-1-1

NIEM National Information Exchange Model

NLECTC National Law Enforcement and Corrections Technology Center

Nlets The International Justice & Public Safety Network

NOBLE National Organization of Black Law Enforcement Executives

NSA National Sheriffs' Association

PDA personal digital assistant

PERF Police Executive Research Forum

PSAP public safety answering points

PSDI Public Safety Data Interoperability

RFP Request For Proposal

RMS records management systems

SEARCH National Consortium for Justice Information and Statistics

Task Force Emergency Communications Task Force

UCAD Unified CAD

UCADFR Unified CAD Functional Requirements

Documents

Recommendations of the Emergency Communications Task Force · PREFACE Task Force Background The Emergency Communications Task Force (hereafter, “Task Force”)1 was jointly formed