911 data dictionary · 2020. 7. 6. · 911 data dictionary version 1.0 | 2020 1 1 1.0 executive...

911 Data Dictionary Administrative Data for 911 Decision-Making

The first activity of the 911 DataPath Initiative

Version 1.0 | 2020

911 Data Dictionary Version 1.0 | 2020

i

Table of Contents

1.0 Executive Summary ................................................................................................................ 1 1.1 Overview ................................................................................................................................ 1 1.2 What the Data Dictionary Contains & How to Use It ........................................................... 2 1.3 What the Dictionary Isn’t ...................................................................................................... 3

2.0 Contributors ........................................................................................................................... 4

3.0 Introduction ........................................................................................................................... 5 3.1 A Common Language for 911 Data ....................................................................................... 5 3.2 How this Data Dictionary Can Help ...................................................................................... 7 3.3 Why & How the Data Dictionary was Developed ................................................................. 8 3.4 Scope & Use of the Data Dictionary ................................................................................... 12

4.0 Dictionary Organization ........................................................................................................ 14 4.1 Dictionary Contents ............................................................................................................. 14 4.2 Terms & Definitions ............................................................................................................ 14 4.3 Data Schema ........................................................................................................................ 16

5.0 Data Component Summaries ................................................................................................ 17

APPENDIX 1: 911 Terms & Definitions ...................................................................... Appendix 1 - 1

APPENDIX 2: Associations, Organizations & Other Stakeholder Entities… ................. Appendix 2 - 1

APPENDIX 3: Useful Resources ................................................................................. Appendix 3 - 1


1

1.0 Executive Summary 1

1.1 Overview 2

Every day, across the nation, decisions about the infrastructure, management, delivery, and 3 improvement of 911 emergency services must be considered and made. In any decision-making 4 situation, you need the support of reliable data—5 data that illustrates the importance of the 911 story 6 that needs to be told. For those who administer 911 7 environments, that data can be the difference 8 between getting crucial funding, procuring the right 9 technical solution, or influencing industry change. 10

In a national landscape composed of independent 11 911 environments, it is difficult to know whether 12 decisions are being based on data and evidence that 13 are consistently defined and truly representative of 14 real, measurable circumstances and needs. Data that 15 is inconsistently reported, aggregated, analyzed, 16 and interpreted can skew perceptions and invite increased risk to day-to-day administration and 17 operations, and migration toward Next Generation 911 (NG911). The bottom line—the 911 18 community should speak the same language. When data elements mean the same thing across the 19 911 community, stakeholders can exchange information knowing precisely what is being requested 20 and what to provide. 21

This data dictionary is a first step toward establishing a common and consistent data “language” 22 the 911 community can use to share data for the purpose of administrative decision-making and 23 NG911 planning, funding, and transition. When data elements mean the same thing across the 911 24 community, stakeholders can exchange information knowing precisely what is being requested and 25 what to provide. 26

Creation of this data dictionary is part of the National 911 Program’s 911 DataPath Initiative, which 27 addresses 911 data-centric recommendations made to the 911 community by the Federal 28 Communications Commission’s (FCC) Task Force on Optimal Public Safety Answering Point 29 (PSAP) Architecture (TFOPA), and strategic 911 data-related goals and objectives described in 30 two documents recently created by the 911 stakeholder community and published by the National 31 911 Program: (1) the NG911 Roadmap: Pathways Toward Nationwide Interconnection of 911 32 Services; and (2) the 911 Data & Information Sharing: A Strategic Plan. Collectively, these 33 recommendations, goals, and objectives point to an ideal “future state” of secure, automated 911 34 data and information sharing in a nationwide NG911 system. 35

When the 911 community shares uniformly defined

data, it can tell a stronger story when justifying funding, identifying

operational needs, and identifying technical 911

system requirements.


2

1.2 What the Data Dictionary Contains & How to Use It 36

As the first data dictionary of a series, this document includes data element names and definitions 37 pertaining to 911 environment administration. Data elements are organized by the components/ 38 described below in Table 1. Categorically, the data elements included in this dictionary were 39 identified by its development team as “critical and will speed the adoption of NG911,” and 40 “important and is needed in today’s 911 environment.” Many of these elements are already 41 collected and shared today by the 911 community through various avenues (e.g., the National 911 42 Profile database, FCC reports, TFOPA NG911 readiness measures). 43

Table 1

DATA COMPONENT SUMMARY OF CONTENTS & POTENTIAL UTILITY

Data Component Header

§ Contains data elements about the agency providing data and information (e.g., jurisdiction, point of contact [POC] information, the timeframe of relevance, data sharing classification)

§ Should be referenced and appended to any data component exchanged

Emergency Communications Center (ECC)/PSAP Data Component

§ Contains data elements about individual ECCs/PSAPs (e.g., ECC/PSAP location/address, type, level of service, ESInet, workforce, calls, local fees, budgets)

§ Can be used as a reference when defining, requesting, reporting, or exchanging data specific to an individual center

State/Regional Data Component

§ Contains data elements about State/Regional 911 programs (e.g., jurisdiction identification, workforce, population and geographic size served, training, jurisdiction fees, jurisdiction status, jurisdiction-wide ECC/PSAP summary, jurisdiction-wide call summary, local fees summary)

§ Can be used as a reference when defining, requesting, reporting, or exchanging data about a State or Regional 911 program; certain State/Regional data elements can be referenced aggregations of data elements contained in the ECC/PSAP Data Component

NG911 System Data Component

§ Contains data elements about ESInet and Next Generation Core Services (NGCS) deployment and use

§ Can be used as a reference when defining, requesting, reporting, or exchanging data about deployment and implementation of NG911 technologies

This dictionary is a reference document—the lists of data elements can be helpful when identifying administrative data you

may need. You can reference the data definitions to help articulate, with specificity, what you mean when requesting,

reporting, analyzing, or exchanging certain data.


3

Use of this data dictionary is intended to be voluntary, flexible, scalable, and multidimensional. 44 Stakeholders can reference this dictionary for data elements that may inform a variety of queries, 45 decisions, and activities, including: 46

§ Collection and aggregation of ECC/PSAP, jurisdictional, and landscape data that enables 47 evaluation of nationwide transition to NG911; rulemaking and policy setting, decision-48 making made about 911 environment investments, administration, funding, operations, 49 technology, and infrastructure; development of NG911 plans; NG911 implementation; and 50 operational improvement; and 51

§ Collection and comparison of differences in jurisdictional 911 environments, how other 52 911 environments have addressed pervasive NG911 challenges, and cost and budget 53 elements factored by various 911 environments. 54

1.3 What the Dictionary Isn’t 55

The dictionary is not intended to represent any mandates or data sharing requirements/expectations 56 of the 911 environment. It is not a national data collection effort on behalf of any public or private 57 agency. It is not intended to be a one-time or annual survey. 58

Data elements in this dictionary are not exhaustive of 911 administrative needs. It defines data 59 elements already collected and shared by the community and will be updated as data and 60 information needs evolve. Therefore, it will be treated as a living document and will be updated by 61 the 911 community as needed. Data dictionaries that address other specific 911 topics (e.g., funding 62 data, call data) will be developed in the future. 63

For the purpose of this dictionary, the term “administrative” is not used as a formal data classification. Rather, it is used

conceptually—data elements contained can inform administrative decisions about various aspects of 911 service delivery.


4

2.0 Contributors 64

The National 911 Program convened a team of 911 stakeholders to shape, inform, and drive 65 activities involved in the development of this data dictionary and its complementary 66 implementation plan. This team included the following 911 administrators, ECC/PSAP managers, 67 originating service providers (OSPs), 911 system providers, data policy experts, and National 911 68 association representatives: 69

§ Michelle Bland, Senior Vice President of Operations, NGA 911 70 § Gar Clarke, Geospatial & Broadband Program Manager, State of New Mexico 71 § Rob Farmer, Strategic Alliances, Business Development, NICE Public Safety 72 § Valeria Ferrell, Senior Product Manager, CentralSquare Technologies 73 § Shelly Guenther, Senior Program Manager, NGA 911 74 § April Heinze, 911 & PSAP Operations Director, National Emergency Number Association 75 § John Hunt, Senior Public Safety Advisor & 911 Specialist, FirstNet 76 § Jerry Jaskulski, NG911 Working Group Federal Lead, Cybersecurity & Infrastructure 77

Security Agency, U.S. Department of Homeland Security 78 § Gary Johnson, Manager, Marquette County, Michigan, Central Dispatch 79 § Audrey Kenny, Director/911 Coordinator, Buck County Department of Emergency 80

Communications, Pennsylvania 81 § Steve McMurrer, 911 System Administrator, Fairfax County, Virginia 82 § Gerry Means, Senior Network Engineer, NG11 Services, State of North Carolina 83 § Liz Phillips, Public Safety Assistant Director, University of Kansas 84 § Deb Rozeboom, Geographic Information System (GIS) Solutions Engineer, GeoComm 85 § Jonathan Sansone, Business Applications Specialist, Virginia Beach Emergency 86

Communications and Citizen Services 87 § Dan Sawicki, Principal Consultant, Business Planning and Operations, Motorola Solutions 88 § Brooks Shannon, Vice President of Product Management, RapidDeploy 89 § Gerard Strein, EM2P Systems Engineer, U.S. Army Armament Research Development and 90

Engineering Center 91

Without the generous contribution of their experience and expertise, the completion of this 92 document would not have been possible. 93


5

3.0 Introduction 94

3.1 A Common Language for 911 Data 95

Every day, across the nation, administrative decisions about the infrastructure, management, 96 delivery, and improvement of 911 emergency services must be considered and made. In a national 97 landscape composed of independent 911 environments, it is difficult to know whether decisions are 98 being based on data and evidence that are consistently defined and truly representative of real, 99 measurable circumstances and needs. Data that is inconsistently reported, aggregated, analyzed, 100 and interpreted can skew perceptions and invite increased risk to day-to-day administration and 101 operations, and migration toward NG911. 102

In any decision-making situation, you need the support of reliable data—data that illustrates the 103 importance of the 911 story you need to tell. That data—whether national, state, and local 911 104 statistics; technical data about your 911 system; or insights into your workforce—can be the 105 difference between getting the funding you need, the technical solution you want, or the industry 106 change you are seeking. That data also can greatly impact how you support or are supported by 107 other jurisdictional 911 environments when collaboration is required. Improved visibility that 108 informs decisions, operations, and collaborative efforts (Figure 1 below) has been identified by the 109 911 community as a significant need.1 110

1 Information presented in Figure 1 was extrapolated from 911 stakeholders who responded to NHTSA’s Request for Information: Nationally Uniform 911 Data System. Among other questions, NHTSA asked the 911 community to provide feedback on how the implementation of a nationally uniform 911 data system may be of most benefit to the stakeholder and how it could be beneficial in implementing NG911.

Figure 1


6

In order to get the right data for your needs and to know how to ask for it, the 911 community needs 111 to speak the same language. You need data you can rely on that means the same thing to everyone 112 with whom you work. For example, when we talk about NG911 deployment across the country, 113 we should all know exactly what it means and exactly how data is used to define NG911 maturity—114 how far your 911 system has progressed toward end-state NG911 implementation. This is 115 particularly essential for decisions that are made about national NG911 funding initiatives. When 116 requesting funding for NG911 systems, it is important to illustrate funding gaps with evidence—117 statistical data and vital 911 system information that demonstrate the true characteristics of what is 118 and what is not occurring throughout the 911 community. 119

With just this first set of 911 data, 911 stakeholders can begin to pursue a variety of efforts that 120 address jurisdictional and national 911 issues, including but not limited to: 121

§ Building Congressional testimony on NG911 funding needs; 122 § Making the best decisions about a 911 system’s administration, operations, technology, or 123

infrastructure; 124 § Proposing legislation that addresses 911 service delivery requirements; 125 § Developing a jurisdiction’s first NG911 Plan; and 126 § Assessing NG911 training costs for a jurisdiction’s workforce127

A Case for Consistent 911 Data

A national 911 organization that administers NG911 grant programs may base its funding decisions on an aggregate of data reporting by individual 911 environments. If analyzing how data depicts overall progress toward NG911, it is important that each state’s data represents the same qualifiers.

For example, the National 911 program collects annual data from 911 environments across the nation. Provision of such data by jurisdictions is voluntary and data is self-reported. When using the data to evaluate levels of NG911 transition on a national scale, variations can occur in how 911 stakeholders report their level of maturity in the category of NGCS elements. If one stakeholder gauges and reports their level of NGCS maturity based on the procurement of NGCS while another gauges and reports maturity based on levels of NGCS implementation, the accuracy of national-scale analysis is then compromised.

Playing out this scenario, this inconsistency in reporting presents potential challenges for the 911 community. A 911 funding agency may review the data and extrapolate that progress is more prevalent and advanced than anticipated, thus justifying fewer funds for the 911 community.

Figure 2


7

3.2 How this Data Dictionary Can Help 128

As the first data dictionary of a series, this document includes data element names and definitions 129 pertaining to 911 environment administration. Categorically, the data elements included in this 130 dictionary were identified by its development team as “critical and will speed the adoption of 131 NG911,” and “important and is needed in today’s 911 environment.” These elements are already 132 surveyed and shared today by the 911 community through various avenues (e.g., the National 911 133 Profile database, FCC reports, TFOPA NG911 readiness measures). 134

Data elements included are organized by the following components (which are described further in 135 Section 3.4: Scope & Use of the Data Dictionary on page 13): 136

§ Data Component Header 137 § ECC/PSAP Data Component 138 § State/Regional Data Component 139 § NG911 System Data Component 140

Stakeholders can reference this dictionary for data elements that may inform a variety of queries, 141 decisions, and activities, as described below in Figure 3. 142

Figure 3


8

3.3 Why & How the Data Dictionary was Developed 143

3.3.1 Background 144 How does this data dictionary fit into the bigger picture of 911 data and information sharing in the 145 advent of NG911? In 2016, the TFOPA recommended creation of a nationally uniform 911 data 146 system to help the 911 community transition to NG911 operations. The TFOPA also identified the 147 need for detailed, consistently measured, specific and well-documented standardized data. This 148 need was highlighted by each of the three TFOPA working groups in different contexts (Table 2 149 below). In response, the Program asked the 911 community what a “nationally uniform 911 data 150 system” should mean. The community expressed that access to 911 system information would help 151 jurisdictions operate more efficiently and better collaborate with other 911 systems. 152

Table 2

In an effort to address TFOPA recommendations, the National 911 Program set in motion several 153 efforts to support 911 community collaboration on NG911 strategic planning and implementation. 154 Figure 4 on the next page depicts these milestones and describes how they collectively point toward 155 a future that enables secure, automated 911 data and information sharing in a nationwide NG911 156 system-of-systems. 157

2 Working Group 1 Final Report, 43. https://transition.fcc.gov/pshs/911/TFOPA/TFOPA_WG1_FINAL_Report-121015.pdf 3 Working Group 2 Final Report, 105. https://transition.fcc.gov/pshs/911/TFOPA/TFOPA_WG2_FINAL_Report-121015.pdf 4 Working Group 2 Final Report, 107. https://transition.fcc.gov/pshs/911/TFOPA/TFOPA_WG2_FINAL_Report-121015.pdf 5 Working Group 3 Final Report, Optimal Resource Allocation, 7. https://transition.fcc.gov/pshs/911/TFOPA/TFOPA_WG3-Final-Report-09282015.pdf

WORKING GROUPS RECOMMENDATIONS

TFOPA WORKING GROUP #1 Optimal Cybersecurity Approach for PSAPs

“…the first step in workforce planning, Define and Identify, emphasizes the collection of workforce data that defines the workforce and the identification of positions/roles within the workforce with specific role-based competencies and proficiency levels. This activity in turn establishes the knowledge, skills, and abilities (KSAs) that are the attributes required to perform a job and are generally demonstrated through qualifying experience, education, or training.”2

TFOPA WORKING GROUP #2 Optimal Approach to NG911 Architecture Implementation

“Legacy terminology is not always as precise as it needs to be; and in this transformative time in the evolution of 9-1-1, terminology that applies to NG9-1-1 should be more detailed and specific.”3 “There is a need for detailed, consistently measured, specific and well-documented standardized data to support decisions related to how shared governance agreements will be developed and executed. Additional research by the TFOPA is needed to define common elements of PSAP cost, and potential cost savings.”4

TFOPA WORKING GROUP #3 Optimal Approach to NG911 Resource Allocation for PSAPs

“The quality and accuracy of 911 data at all levels of government can be improved. Better and complete data on all aspects of 911 funding will facilitate federal and state efforts to set appropriate and sustainable levels of funding for this critical public service. Currently, the accuracy and quality of data submitted to the FCC for incorporation into the agency’s annual report to Congress, required by the Net 911 Act,2 is deficient. State and regional 911 authorities must work with PSAPs to improve the accuracy of the data submitted to the FCC.”5


9

Figure 4


10

3.3.2 Development 158 The National 911 Program convened a team of 911 administrators, ECC/PSAP representatives, 159 originating service providers, 911 system providers, data policy experts, and national associations 160 to guide the Data Uniformity Project and spearhead the development of this data dictionary and its 161 implementation plan. 162

Collection of Data. The team first compiled and reviewed data elements that are already collected 163 by/from the 911 community via surveys and direct interaction (Table 3 below). 164

Table 3

Prioritization of Data. Once data elements were pulled from the sources listed in Table 3, the 165 stakeholder team sorted and prioritized the data elements based on the extent to which each element 166 informs adoption of and transition to NG911. Elements were assessed based on the following 167 characterizations: 168

• It is critical and will speed the adoption of NG911; 169 • It is important and is needed in today’s 911 environment; 170 • It will be needed in the future (> 2 years out); 171 • It is informational, and would be nice to collect; or 172 • Unsure. 173

6 National 911 Profile Database: https://www.911.gov/project_911profiledatabase.html 7 NHTSA RFI, Nationally Uniform 911 Data System, https://www.govinfo.gov/content/pkg/FR-2016-06-30/pdf/2016-15368.pdf 8 FCC TFOPA Working Group 2, Phase II Supplemental Report, NG9-1-1 Readiness Scorecard https://transition.fcc.gov/pshs/911/TFOPA/TFOPA_WG2_Supplemental_Report-120216.pdf

RESOURCE SCOPE

National 911 Profile Database6

Data points and basic demographic information that help characterize a state’s 911 operations, protocols and progress toward NG911 implementation (e.g., number of ECCs/PSAPs, number of each type of 911 call answered per year, the number of ECCs/PSAPs capable of processing 911 calls using NG911 infrastructure, how the capability to respond to text-to-911 calls is progressing).

FCC Eleventh Annual Report to Congress on State Collection and Distribution of 911 and Enhanced 911 Fees and Charges

Funding mechanism authorities, how state 911 fees are used; fees collected and diverted/transferred; NG911 services and expenditures, cybersecurity expenditures.

NHTSA Request for Information: Nationally Uniform 911 Data System7

911 community feedback on computer-aided dispatch (CAD) and/or ECC/PSAP and/or 911 system data presently collected; additional data that would be beneficial to staffing, budgeting, testing, contract compliance, performance metrics, planning, governance, and quality improvement activities; data elements considered essential related to information handled by telecommunicators, and administration and operation of an ECC/PSAP or jurisdictional 911 system.

TFOPA Working Group 2 Phase II Supplemental Report, NG9-1-1 Readiness Scorecard8

Levels of maturity—legacy, foundational, transitional, intermediate, i3 End State-Jurisdictional, i3 End State-National—in the areas of NG911 governance, routing and location, GIS data, NGCS elements, networks, ECC/PSAP call handling system and applications, security, operations, and optional interfaces.


11

Once data elements were filtered, the team 174 identified and integrated additional data elements 175 relevant to NG911 transition and administrative 176 priorities. 177 Defining the Data Elements. The team worked 178 together to review each data item and came to 179 consensus on data element terms/names, 180 definitions, and sources. Current standards that 181 drive how specific data elements are described, 182 used, and packaged, were identified and cited 183 where appropriate. 184

To facilitate wide-spread and long-term adoption 185 of the data dictionary, the team aligned how data was defined with parameters of the National 186 Information Exchange Model (NIEM)—a reference model that serves as a common vocabulary 187 that enables organizations to share data with others. 188

Obtaining 911 Community Validation. The stakeholder team worked with the National 911 189 Program to engage the 911 community via two tracks of activity: 190

1. Webinars were conducted to raise awareness of the 911 DataPath Initiative and the creation 191 of this data dictionary. Participant input was sought on how to approach building a common 192 data language for the 911 community and priority considerations related to widespread, 193 long-term adoption. 194

2. A public feedback session was held from July 7–31, 2020. Stakeholders had the 195 opportunity to review the draft data dictionary and its complementary plan for 196 implementation, and provide feedback on the extent to which data elements provide basic 197 information needed for NG911 transition, whether data elements were clearly and 198 accurately defined, and what the 911 community should do now to implement the data 199 dictionary and move closer to secure, automated information sharing within and among 200 911 systems on a national scale. 201

3.3.2 Next Steps 202 Engagement efforts to raise awareness and generate 203 interest in this early version of the dictionary will 204 continue. As the 911 community comes together to 205 refine its contents, the dictionary will be submitted to 206 an accredited standards development organization for 207 review and standardization processing. More 208 information about how this dictionary will be 209 implemented can be found in The 911 DataPath 210 Implementation Framework. 211

Other 911 data dictionary components also will be 212 released in the future. Figure 5 provides examples of 213 future data areas/dictionary releases identified by this 214 dictionary’s development team. Future releases may 215 dive deeply into funding data, call data, workforce 216

Data elements pertaining to NG911 transition and 911

administration were prioritized because they are

foundational and can be used as a basis for compiling

future dictionaries focused on specific aspects of 911.

Potential Data Topics for Future Dictionaries

• Funding data • Call data • Audio and video data • ECC/PSAP size ranges • Emergency medical dispatch • Call-handling quality assurance • Staff training status • Personnel costs • Administrative costs • Dispatch costs

Figure 5


12

data, and so on. Each subsequent document will focus on a specific data topic that will be identified 217 and prioritized by the 911 community during various mechanisms for obtaining stakeholder 218 feedback. As the language used for 911 data becomes more homogenized across the nation, 219 discussions, information exchange, collaborations, negotiations, and other avenues for engaging 220 about 911 services will become easier and clearer. 221

3.4 Scope & Use of the Data Dictionary 222

The data dictionary is intended to be a living document and can be used as a reference point for 223 911 basic data that informs multiple needs for information. Table 4 below lists just a fraction of 224 areas each of the data dictionary’s components address. 225

Table 4

This data dictionary does not represent a formal surveying mechanism in any way. It does not 226 represent mandates or expectations of 911 environments to share information with the federal 227 government or any other entity. This resource is intended to be used by local, state, tribal, and 228 nontraditional 911 systems for their own benefit.229

COMPONENT SCOPE CAN BE USEFUL INFORMATION FOR...


Data points that describe the agency that compiled the data component, including jurisdiction, jurisdiction type, point of contact, data sharing classification, effective dates of data

This provides data on the source of the data and allowable uses and timeframe of the data included. The user of the data can use this to determine how the data can be used or shared. The system can use the information to apply the user role and access rules.

Individual ECC/PSAP Data Component

Data points including ECC/PSAP location/address, type, level of service, ESInet, workforce, calls, local fees, budgets

§ An ECC/PSAP Manager who is gathering comparison data in preparation to inform and justify funding for staffing-This dictionary provides a reference point for delineating the number and type of staff positions at the ECC/PSAP.

§ A 911 State 911 Administrator/Coordinator who is gathering data to compile their annual report to the state's 911 authority board and help secure funding for statewide NG911 planning-This dictionary provides a reference point for identifying what single ECC/PSAP data might be needed and how the data can be aggregated at the State/Region level.

§ A federal committee that is analyzing the breadth and depth of investments that may be needed to help 911 programs across the nation transition to NG911. This dictionary provides a reference point for how to identify and define the data that is needed from 911 programs nationwide.


Data points including jurisdiction identification, workforce, population and geographic size served, training, jurisdiction fees, jurisdiction status, jurisdiction-wide ECC/PSAP summary, jurisdiction-wide call summary, local fees summary


Data points related to ESInet and NGCS deployment and use


13

Future data dictionaries will be built by the same parameters; each will contain data elements that 230 inform a unique aspect of 911 services. Therefore, this first dictionary does not list or define data 231 elements that are comprehensive to the entire 911 service lifecycle. Additional data components 232 can be added and adopted by the 911 community, it is anticipated that the community will drive 233 the standardization of data terms and definitions through consultation and acceptance by American 234 National Standards Institute (ANSI)-accredited standards setting organizations. 235

This data dictionary is intended to be a living document and its use is intended to be voluntary, flexible, scalable, and

multidimensional. Refer to this document when you want, use the data elements you need, and augment it with the

additional data elements you use.


14

4.0 Dictionary Organization 236

4.1 Dictionary Contents 237

This dictionary consists of the following documentation: 238

1. This document, 911 Data Dictionary: Administrative Data for 911 Decision-Making—239 Addresses the value of 911 data consistency, provides general information about why and 240 how the data dictionary was created, and describes the dictionary’s contents and 241 organization. 242

2. The Microsoft Excel workbook, 911 Administrative Data List—Contains a spreadsheet 243 that defines each individual data element; identifies primary, secondary, and tertiary 244 sources for each element; specifies data format parameters, and provides reference 245 standards where they are applicable. 246

3. Schema documentation—Extensible Markup Language (XML) and JavaScript Object 247 Notation (JSON) sample files. 248

4.2 Terms & Definitions 249

This document uses data-centric terms as they are used and defined under NIEM. Most significant 250 is how the terms, “data element” and “data component” are used, which is described in Table 5 251 below and on the next page. Other terms are used and defined in specific context of this document’s 252 purpose. 253

Table 5

9 More information about 911 authority structures is available in the document, State & Territory 911 Authority Structures, developed by NASNA in collaboration with the National 911 Program.

TERM DEFINITION

911 administrator Individual responsible for overseeing the overall health of 911 environments, systems, and funding for a specific jurisdiction.

911 authority Entity that is ultimately responsible for the geographic planning, coordination, and funding of 911 environments. Authorities could be state agencies, regional entities, federal entities, or even individual PSAPs (particularly in states that operate under a single statewide system and PSAP9).

911 environment All elements involved in 911 service delivery for a specific community (e.g., policy and legislation, governance, operational functions, workforce).

911 system Technology infrastructure that supports a 911 environment (e.g., Next Generation Core Services [NGCS], Emergency Services IP Network (ESInet), CAD, call-handling equipment, logging and reporting systems, map displays, radio networks, Geographic Information Systems [GIS], databases)


15

Table 6 (cont.)

Data elements included in this first dictionary (specifically in the 911 Administrative Data List 254 workbook) are organized by the following components: 255

§ Data Component Header 256 § ECC/PSAP Data Component 257 § State/Regional Data Component 258 § NG911 System Data Component 259

Each data component is comprised of individual data elements that can be used as singular data 260 points or can be aggregated with other data points to culminate a multidimensional story. Each of 261 the data component’s elements are defined as described in Figure 6. 262

How specific stakeholders throughout the 911 community interpret 911-, NG911-, and data- and 263 information-related terminology varies to significant degrees. In an effort to maintain continuity of 264 terms and definitions that are already ubiquitous among 911 stakeholders, this data dictionary 265 aligns with existing glossaries and standards that have been widely adopted by the 911 community 266 (refer to Appendix 1: Terms & Definitions, and Appendix 2: Associations, Organizations & Other 267

Administrative data

911 environment oversight and management (e.g. policymaking, NG911 planning, fiscal management, reporting).

Common Ubiquitously present, used, or exercised across an expansive demographic.

Data element Any unit of data defined for processing; defined by size (characters) and type (e.g., alphanumeric, numeric only, true/false, date). A specific set of values or range of values may also be part of the definition.

Data component A collection of data elements logically grouped together by properties and types. Components are often referred to by their qualified names (example: 911:Header)

Jurisdiction Localities, regions, towns, rural communities, states, and tribal organizations with the legal responsibility for 911.

National Of importance, relevance, or impact to the Nation as a whole (the term, as used throughout this plan, is not intended to refer to national/federal government or agency).

State U.S. states, commonwealths, territories, or tribal communities.

Figure 6


16

Stakeholder Entities Relevant to 911). Appendices 1 and 2 are not exhaustive lists of 911 terms, 268 acronyms, and abbreviations; rather, it addresses terms used frequently throughout this document 269 and the meanings and context they are intended to convey. 270

4.3 Data Schema 271

Figure 7 on the next page represents sample sections of a XML and JSON schema that can be used 272 to express a common language and exchange format for exchange of individual ECC/PSAP 911 273 data across the network of functional elements, agencies, and technical equipment. In other words, 274 the schema defines a shared vocabulary and a NIEM-based exchange file format to be used for 275 information exchange across a network of NG911 connected entities and end points. 276

This schema provide a means for defining the structure, content, and semantics of XML documents 277 to exchange across multiple end points so they can exchange information in a standard format, 278 similarly to a schema that describes the data that can be contained in a database (e.g., table structure, 279 field names, data types, constraints). In regard to 911 data where multiple stakeholders own 280 different databases and technologies, XML provides the means to allow data to be exposed and 281 consumed regardless of technology platforms used. Therefore, this XML schema will define the 282 structure of the XML documents to exchange across 911 system end points, along with rules for 283 data content and semantics (e.g., what fields an element can contain, which sub elements it can 284 contain, validation rules, how many items can be present, type and values that can be placed into 285 each element or attribute). 286

(This section of page intentionally left blank.)


17

Sample XML Data Schema Section

<xs:element name="Header"> <xs:complexType> <xs:sequence> <xs:element name="SOURCE" type="xs:string"/> <xs:element name="SOURCE_TYPE" type="xs:string"/> <xs:element name="SOURC_PSAP" type="xs:string"/> <xs:element name="SOURCE_LNAME" type="xs:string"/> <xs:element name="SOURCE_FNAME" type="xs:string"/> <xs:element name="SOURCE_TITLE" type="xs:string"/> <xs:element name="SOURCE_EMAIL" type="xs:string"/> <xs:element name="SOURCE_PHONE" type="xs:integer"/> <xs:element name="Date_Time_of_Data_Start" type="xs:dateTime"/> <xs:element name="Date_Time_of_Data_End" type="xs:dateTime"/> <xs:element name="Data_Sharing_Classification_TLP" type="xs:string"/> <xs:element name="Data_Sharing_Classification_TLP_Detail" type="xs:string"/> <xs:element name="Notes" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element>

Sample JSON Data Schema Section

{ "$schema": "http://json-schema.org/draft-07/schema#", "$id": "http://911domain.com/draft-07/schema#", "title": "911 JSON Schema", "type": "object", "properties": { "HEADER": { "required": ["SOURCE", "SOURCE_TYPE", "SOURC_PSAP", "SOURCE_LNAME", "SOURCE_FNAME", "SOURCE_TITLE", "SOURCE_EMAIL", "SOURCE_PHONE", "Date_Time_of_Data_Start", "Date_Time_of_Data_End", "Data_Sharing_Classification_TLP"], "type": "object", "properties": { "SOURCE":{ "type": "string", "description": "Jurisdiction name associated with the account used to submit data", "minLength":1, "maxLength":300 },

Figure 7


18

5.0 Data Component 287

Summaries 288

Table 6 below summarizes the data elements included in each component, highlights their unique 289 considerations, and identifies the where they can be found in the 911 Administrative Data List. The 290 spreadsheet contains definitions for each data element included and provides information on sources and 291 relevant standards. 292

Table 6

COMPONENT SCOPE


Data points that describe the agency that compiled the data component, including jurisdiction, jurisdiction type, point of contact, data sharing classification, effective dates of data

§ Serves as the header component for all 911 data components.

§ Contains information on the source of the data, the ECCs/PSAPs included in the data set, and limits on sharing the data.

§ By using the data classification, a jurisdiction can submit multiple data sets with differing levels of sharing to enhance the amount that can be shared.

Individual ECC/PSAP Data Component

Data points including PSAP location/address, type, level of service, ESInet, workforce, calls, local fees, budgets

§ Developed to use to collect data from ECCs/PSAPs, by state, or by regional authorities.

§ The ECC/PSAP data component should be prepared for each physical or logical individual ECC/PSAP. For example, an ECC/PSAP with a remote back-up would prepare one for the ECC/PSAP and one for their back-up. An ECC/PSAP running two sites simultaneously would prepare two also. An ECC/PSAP that uses their neighboring jurisdiction as a back-up would only need one. This also can include private secondary ECCs/PSAPs or dispatch centers.


Data points including jurisdiction identification, workforce, population and geographic size served, training, jurisdiction fees, jurisdiction status, jurisdiction-wide PSAP summary, jurisdiction-wide call summary, local fees summary

§ Developed to share data from a state or region authority to other authorities or national organizations.

§ Contains summary data from ECCs/PSAPs in the state or region.


Data points related to ESInet and NGCS deployment and use; developed to share data on the NG911 systems between authorities, states, regions, and national organizations.

911 Data Dictionary—Appendix 1 Version 1.0 | 2020

Appendix 1 - 1

APPENDIX 1: 911 Terms & 293

Definitions294

TERM DEFINITION

911 (or 9-1-1) A three-digit telephone number to facilitate the reporting of an emergency requiring a response by a public safety agency.

911 authority A state, county, regional, or other governmental entity responsible for 911 service operations. For example, this could be a county/parish or city government, a special 911 or Emergency Communications District, a Council of Governments or other similar body.

911 “call”

A generic term used to include any type of Request for Emergency Assistance (RFEA); a 911 call is not limited to voice. This may include a session established by signaling with two-way, real-time media and involves a human making a request for help. We sometimes use “voice call,” “video call” or “text call” when specific media is of primary importance. The term “non-human-initiated call” refers to a one-time notification or series of data exchanges established by signaling with at most one-way media, and typically does not involve a human at the “calling” end. The term “call” also can be used to refer to either a “voice call,” “video call”, “text call” or “data-only call”, because they are handled the same way through most of NG911.

911 fund The fund established by state statute that is specifically used to fund 911 activities and/or infrastructure.

911 service area The geographic area that has been granted authority by a state or local governmental body to provide 911 services.

911 state plan A document prepared, maintained, implemented, and updated by a state that provides a comprehensive plan for operating a statewide 911 system that communicates 911 call information across networks and among PSAPs, addresses all aspects of the statewide 911 system, and describes the allowable uses of revenue in the 911 fund.

911 system

A coordinated system of technologies used by a collaborative group of people to operate an efficient and effective network for accepting, processing, and delivering emergency information to facilitate an emergency response. A set of networks, services, software applications, databases, customer premises equipment (CPE) components, and operations and management procedures required to provide 911 service. This may include commercial, governmental, and human resources.

Access provider An access provider is any organization that arranges for an individual or an organization to have access to the internet.

Additional data Data that further describes the nature of how a call was placed, the person(s) associated with the device placing the call, or the location the call was placed from. There are three types of additional data: for the call, for the caller, and for the location.

Agency In NG911, an organization that is connected directly or indirectly to the ESInet. Public safety agencies are examples. An entity such as a company that provides a service in the ESInet also can be an agency. Agencies have identifiers and credentials that allow them access to services and data.

Agent In NG911, an agent is an authorized person—an employee, contractor or volunteer, who has one or more roles in an agency. An agent also can be an automaton in some circumstances (e.g., an interactive media response [IMR] answering a call).


Appendix 1 - 2

TERM DEFINITION

Alternate routing The capability of routing 911 calls to a designated alternate location(s) if all 911 trunks are busy or out of service. May be activated upon request or automatically, if detectable, when 911 equipment fails or the PSAP itself is disabled.

Automatic location identification (ALI)

The automatic display at the PSAP of the caller’s address/location of the telephone and supplementary emergency services information of the location from which a call originates.

Automatic number identification (ANI)

The automatic display at the PSAP of the caller’s telephone number associated with the access line from which a call originates.

Basic 911 An emergency telephone system that automatically connects 911 callers to a designated answering point. Call routing is determined by the originating telephone central office only. Basic 911 may or may not support ANI and/or ALI.

Call handling Functional element concerned with the details of the management of calls. It handles all communication from the caller. It includes the interfaces, devices and applications utilized by the agents to handle the call.

Call routing The capability to selectively route the 911 call to the appropriate PSAP.

Call-taker An agent of a PSAP who answers and processes emergency calls. Synonymous with the term, “telecommunicator.”

Call taking The act of processing a call for emergency assistance up to the point that the call is ready for dispatch, including the use of equipment, call classification, location of a caller, and determination of the appropriate response level for emergency responders.

Carrier The business entity providing service to a customer base, typically for a fee. Examples of carriers and associated services are public switched telephone network (PSTN) service by a local exchange carrier (LEC), voice over Internet Protocol (VoIP) service by a VoIP provider; email service provided by an internet service provider (ISP).

Commercial call center A privately operated call center, which answers emergency and/or nonemergency calls.

Commercial mobile radio service (CMRS)

An FCC designation for any carrier or licensee whose wireless network is connected to the PSTN.

CMRS connection Each mobile handset telephone number assigned to a CMRS subscriber with a place of primary use in-state.

CMRS provider An entity, whether facilities-based or non-facilities-based, that is licensed by the FCC to provide CMRS or that resells CMRS within a state.

Computer-aided dispatch (CAD)

A computer-based system that aids PSAP telecommunicators by automating selected dispatching and record-keeping activities.

Continuity of operations (COOP)

The ability to continue operations during and after a service-impacting event through a specific set of procedures designed to reduce the damaging consequences of unexpected events resulting in the loss of 911 capabilities.

Customer premises equipment (CPE)

Communications or terminal equipment located in the customer’s facilities—terminal equipment at a PSAP.

Database An organized collection of information, typically stored in computer systems, comprised of fields, records (data), and indexes. In 911, such databases include the Master Street Address Guide (MSAG), telephone number/emergency service number (ESN), and telephone customer records.

Data exchange The process of exchanging 911 data between service providers and the database management system provider.


Appendix 1 - 3

TERM DEFINITION

Dispatch system Functional element used to assign appropriate resources (emergency responders) to an incident, monitor the response and relay relevant information updates. Tracks and logs all transactions associated with the emergency response.

Enhanced 911 (E911) A telephone system that includes network switching, database and PSAP premises elements capable of providing ALI data, selective routing, selective transfer, fixed transfer, and a callback number. The term also includes any enhanced 911 service so designated by the FCC in its Report and Order in WC Docket Nos. 04-26 and 05-196, or any successor proceeding.

Emergency medical services (EMS)

A service providing out-of-hospital acute care and transport to definitive care, for patients with illnesses and injuries that the patient believes constitute a medical emergency.

Emergency services IP network (ESInet)

An ESInet is a managed IP network that is used for emergency services communications, and which can be shared by all public safety agencies. It provides the IP transport infrastructure upon which independent application platforms and core services can be deployed, including, but not restricted to, those necessary for providing NG911 services. ESInets may be constructed from a mix of dedicated and shared facilities. ESInets may be interconnected at local, regional, state, federal, national and international levels to form an IP-based inter-network (network of networks). The term ESInet designates the network, not the services that ride on the network.

First Responder Network Authority (FirstNet)

Signed into law on February 22, 2012, the Middle Class Tax Relief and Job Creation Act created the First Responder Network Authority (FirstNet). The law gives FirstNet the mission to build, operate and maintain the first high-speed, nationwide wireless broadband network dedicated to public safety. FirstNet will provide a single interoperable platform for emergency and daily public safety communications. http://www.firstnet.gov/

Geographic information system (GIS)

A system for capturing, storing, displaying, analyzing and managing data and associated attributes that are spatially referenced.

i3 solution NENA i3 is a term for the NENA NG911 system architecture that standardizes the structure and design of functional elements which make up the set of software services, databases, network elements, and interfaces needed to process multi-media emergency calls and data for NG911.

Interconnectivity The capability of disparate systems to be joined by connections between parts and elements.

Interlocal services agreement

An agreement among governmental jurisdictions or privately-owned systems, or both, within a specified area to share 911 system costs, maintenance responsibilities, and other considerations.

Internet of Things (IoT) A network of physical internet-connected devices embedded with electronics, sensors, and software able to collect and exchange data with other linked devices.

Internet Protocol (IP) The method by which digital data is sent from one computer to another on the internet or other networks.

Interoperability The capability of disparate communications systems to seamlessly interconnect and work together as a collective system.

Landline Colloquial term for PSTN access via an actual copper or fiber-optic transmission line that travels underground or on telephone poles. Used to differentiate the “wireless” connectivity of a cellular or Personal Communication System (PCS).

Legacy network gateway (LNG)

An NG911 functional element that provides an interface between a non-IP originating network and a NGCS-enabled network.


Appendix 1 - 4

TERM DEFINITION

Legacy PSAP gateway (LPG)

The Legacy PSAP Gateway (LPG) is a signaling and media interconnection point between an ESInet and a legacy PSAP. It plays a role in the delivery of emergency calls that traverse an i3-compliant ESInet to get to a legacy PSAP, as well as in the transfer and alternate routing of emergency calls between legacy PSAPs and NG911 PSAPs. The LPG supports an IP (i.e., Session Initiation Protocol [SIP]) interface toward the ESInet on one side, and a traditional multi-frequency (MF) or enhanced MF interface (comparable to the interface between a traditional selective router and a legacy PSAP) on the other.

Local exchange carrier A telecommunications carrier under the state/local Public Utilities Act that provides local exchange telecommunications services. Also known as incumbent local exchange carriers, alternate local exchange carriers, competitive local exchange carriers, competitive access providers, certified local exchange carriers, and local service providers.

Location information server (LIS)

A functional element in an IP-capable originating network that provides locations of endpoints (i.e., calling devices). A LIS can provide location by reference, or location by value, and, if the latter, in geo or civic forms. A LIS can be queried by an endpoint for its own location, or by another entity for the location of an endpoint. In either case, the LIS receives a unique identifier that represents the endpoint, for example an IP address, circuit-ID or Media Access Control (MAC) address and returns the location (value or reference) associated with that identifier. The LIS is also the entity that provides the dereferencing service, exchanging a location reference for a location value.

Master Street Address Guide (MSAG)

A database of street names and house number ranges within their associated communities defining emergency service zones (ESZs) and their associated ESNs to enable proper routing of 911 calls.

Memorandum of agreement (MOA)

A memorandum of agreement (MOA) or cooperative agreement is a document written between parties to cooperatively work together on an agreed-upon project or meet an agreed-upon objective.

Memorandum of understanding (MOU)

A memorandum of understanding (MOU) is a document that expresses mutual accord on an issue between two or more parties.

Mutual-aid agreement Written agreement between agencies and/or jurisdictions by which they agree to assist one another upon request, by furnishing personnel and equipment.

National Incident Management System (NIMS)

A standardized approach to incident management developed by DHS. It is intended to facilitate coordination between all responders (including all levels of government with public, private, and non-governmental organizations). https://www.fema.gov/national-incident-management-system

National Information Exchange Model (NIEM)

A community-driven, standards-based, national model for structured information sharing. www.niem.gov

Next Generation 911 (NG911) services

“Next Generation 9-1-1 services" means an IP-based system comprised of hardware, software, data, and operational policies and procedures that:

a) provides standardized interfaces from emergency call and message services to support emergency communications;

b) processes all types of emergency calls, including voice, data, and multimedia information;

c) acquires and integrates additional emergency call data useful to call routing and handling;

d) delivers the emergency calls, messages, and data to the appropriate public safety answering point and other appropriate emergency entities;

e) supports data or video communications needs for coordinated incident response and management; and

f) provides broadband service to public safety answering points or other first responder entities.

REF: Middle Class Tax Relief and Job Creation Act of 2012


Appendix 1 - 5

TERM DEFINITION

Order of authority A formal order by the state or local authority that authorizes public agencies or public safety agencies to provide 911 service in a geographical area.

Prepaid wireless telephone service

Telephone service authorized by the purchase of CMRS, either exclusively or in conjunction with other services. This service must be paid for in advance and is sold in units or dollars whose number or dollar value declines with use and is known on a continuous basis.

Private 911 emergency answering point

An answering point operated by non-public safety entities with functional alternative and adequate means of signaling and directing response to emergencies. Includes training to individuals intercepting calls for assistance that is in accordance with applicable local emergency telecommunications requirements. Private 911 emergency answering points are an adjunct to public safety response and as such must provide incident reporting to the public safety emergency response centers per local requirements.

Proprietary information Subscriber lists, technology descriptions, technical information, or trade secrets that are developed, produced, or received internally by a communications service provider or by a communications service provider’s employees, directors, officers, or agents.

Public safety agency A functional division of a public agency that provides firefighting, law enforcement, medical or other services to respond to and manage emergency incidents.

Public safety answering point (PSAP)

An entity responsible for receiving 911 calls and processing those calls according to a specific operational policy.

• Primary PSAP: A PSAP to which 911 calls are routed directly from the 911 Control Office.

• Secondary PSAP: A PSAP to which 911 calls are transferred from a primary PSAP. • Alternate PSAP: A PSAP designated to receive calls when the primary PSAP is unable

to do so. • Consolidated PSAP: A facility where multiple public safety agencies choose to operate

as a single 911 entity. • Legacy PSAP: A PSAP that cannot process calls received via i3-defined call interfaces

(IP-based calls) and still requires the use of centralized automatic message accounting (CAMA) or integrated services digital network (ISDN) trunk technology for delivery of 911 emergency calls.

• Serving PSAP: The PSAP to which a call normally would be routed. • NG911 PSAP: This term is used to denote a PSAP capable of processing calls and

accessing data services as defined in NENA’s i3 specification, NENA NENA-STA-010, and referred to therein as an “i3 PSAP.”

Service provider An entity providing one or more of the following 911 elements: network, CPE, or database service.

Standards development organization (SDO)

An entity whose primary activities are developing, coordinating, promulgating, revising, amending, reissuing, interpreting, or otherwise maintaining standards that address the interests of a wide base of users outside the standards development organization.

Subscriber A person who purchases a communications service and is able to receive it or use it periodically over time.

Telecommunication The transmission, between and among points specified by the user, or information of the user’s choosing, without change in the form of content of the information sent and received, regardless of the facilities, equipment or technology used.


Appendix 1 - 6

TERM DEFINITION

Virtual PSAP

An operational model directly enabled through NG911 features and/or network-hosted PSAP equipment in which telecommunicators are geographically dispersed, rather than working from the same physical location. Remote access to the PSAP applications by the dispersed telecommunicators requires the appropriate network connections, security, and workstation equipment at the remote location. Unified communications applications supporting voice, data, instant messaging, and video communications between telecommunicators may be used to enable the telecommunicators to work cooperatively from diverse locations. The virtual workplace may be a logical combination of physical PSAPs, or an alternate work environment such as a satellite facility, or any combination of the above. Workers interoperate via IP connectivity.

Voice communications service

The transmission, conveyance, or routing of real-time, two-way voice communications to a point, or between or among points, or through any electronic, radio, satellite, cable, optical, microwave, wireline, wireless, or other medium or method, regardless of the protocol used, including interconnected VoIP service.

Voice over Internet Protocol (VoIP)

Technology that permits delivery of voice calls and other real-time multimedia sessions over IP networks.


Appendix 2 - 1

APPENDIX 2: Associations, 295

Organizations & Other 296

Stakeholder Entities 297

Relevant to 911 298

NAME/ACRONYM DESCRIPTION WEBSITE

Alliance for Telecommunications Industry Solutions (ATIS)

A U.S.-based organization that is committed to rapidly developing and promoting technical and operations standards for the communications and related information technologies industry worldwide using a pragmatic, flexible and open approach.

https://www.atis.org/

American National Standards Institute (ANSI)

Entity that coordinates the development and use of voluntary consensus standards in the United States and represents the needs and views of U.S. stakeholders in standardization forums around the globe.

www.ansi.org

American Registry for Internet Numbers (ARIN)

An organization that provides services related to the technical coordination and management of internet number resources.

https://www.arin.net/

Association of Public-Safety Communications Officials (APCO)

APCO is the world’s oldest and largest not-for-profit professional organization dedicated to the enhancement of public safety communications.

http://www.apcointl.org/

Commission on Accreditation for Law Enforcement Agencies (CALEA)

Created in 1979 as a credentialing authority through the joint efforts of law enforcement's major executive associations:

• International Association of Chiefs of Police (IACP)

• National Organization of Black Law Enforcement Executives (NOBLE)

• National Sheriffs' Association (NSA) • Police Executive Research Forum (PERF).

The purpose of CALEA’s accreditation programs is to improve the delivery of public safety services, primarily by: maintaining a body of standards, developed by public safety practitioners, covering a wide range of up-to-date public safety initiatives; establishing and administering an accreditation process; and recognizing professional excellence.

http://www.calea.org/


Appendix 2 - 2


Communications Security, Reliability, and Interoperability Council (CSRIC) (formerly known as the Network Reliability and Interoperability Council [NRIC])

An advisory body of the FCC that provides recommendations to the FCC to ensure, among other things, optimal security and reliability of communications systems, including telecommunications, media, and public safety.

https://www.fcc.gov/about-fcc/advisory-committees/communications-security-reliability-and-interoperability-council-0

CTIA—The Wireless Association

CTIA represents the U.S. wireless communications industry. From carriers and equipment manufacturers to mobile app developers and content creators, CTIA brings together a dynamic group of companies that enable consumers to lead a 21st Century connected life.

https://www.ctia.org/

Emergency Services Interconnection Forum (ESIF)

An open, technical/operational forum, under the auspices of ATIS, with the voluntary participation of interested parties to identify and resolve recognized 911 interconnection issues.

https://www.atis.org/01_committ_forums/esif/

Federal Communications Commission (FCC)

An independent U.S. government agency overseen by Congress, the FCC regulates interstate and international communications by radio, television, wire, satellite and cable in all 50 states, the District of Columbia and U.S. territories.

https://www.fcc.gov/

Federal Geographic Data Committee (FGDC)

An interagency committee that promotes the coordinated development, use, sharing, and dissemination of geospatial data on a national basis.

https://www.fgdc.gov/

First Responder Network Authority (FirstNet)

Signed into law on February 22, 2012, the Middle Class Tax Relief and Job Creation Act created FirstNet. The law gives FirstNet the mission to build, operate and maintain the first high-speed, nationwide wireless broadband network dedicated to public safety. FirstNet will provide a single interoperable platform for emergency and daily public safety communications.

http://www.firstnet.gov/

Industry Council for Emergency Response Technologies (iCERT)

iCERT’s mission is to serve as the voice of the commercial sector in the emergency response technologies field. iCERT members assist public policymakers and government emergency communications professionals as they address complex choices regarding advanced communications technology alternatives in the years ahead. Through advocacy, research, and in coordination with the public sector, iCERT plays a vital role in the development and deployment of emergency response technologies.

https://www.theindustrycouncil.org/

Institute of Electrical and Electronic Engineers (IEEE)

A publishing and standards-making body responsible for many telecom and computing standards.

https://www.ieee.org/


Appendix 2 - 3


Integrated Justice Information Systems Institute (IJIS)

The IJIS Institute, a 501(c)(3) nonprofit corporation, represents industry’s leading companies that collaborate with local, state, tribal, and federal agencies to provide technical assistance, training, and support services for information exchange and technology initiatives. The mission of the IJIS Institute is to unite the private and public sectors to improve critical information sharing for those who provide public safety and administer justice in our communities.

www.ijis.org

International Academies of Emergency Dispatch (IAED)

A non-profit, standards-setting organization, formerly known as the National Academies of Emergency Dispatch (NAED), promoting safe and effective emergency dispatch services worldwide.

http://www.emergencydispatch.org/

International Committee for Information Technology Standards (INCITS)

A U.S.-based standards development organization dedicated to the creation of information technology standards.

www.incits.org

International Organization for Standardization (ISO)

An independent, non-governmental international organization with a membership of 161 national standards bodies.

www.iso.org

International Telecommunication Union (ITU)

The telecommunications agency of the United Nations established to provide worldwide standard communications practices and procedures. Formerly the Consultative Committee for International Telephony and Telegraphy (CCITT).

https://www.itu.int/en/about/Pages/default.aspx

Internet Architecture Board (IAB)

The IAB is the committee charged with oversight of the technical and engineering development of the internet by the Internet Society (ISOC). It oversees numerous task forces, of which the most important are the Internet Engineering Task Force (IETF) and the Internet Research Task Force (IRTF). The body that eventually became the IAB originally was formed by the DOD’s Defense Advanced Research Projects Agency (DARPA), under the name Internet Configuration Control Board, in 1979; it eventually became the Internet Advisory Board in September 1984, and then the Internet Activities Board in May 1986 (the name was changed, while keeping the same acronym). It finally became the Internet Architecture Board, under ISOC, in January 1992, as part of the internet’s transition from a U.S. government entity to an international public entity.

https://www.iab.org/

Internet Assigned Numbers Authority (IANA)

IANA is the entity that oversees global IP address allocation; Domain Name System (DNS) root zone management, and other IP assignments.

www.iana.org

Internet Corporate for Assigned Names and Numbers (ICANN)

Authority for public domain addresses and uniform resource locators (URLs), including related policies and databases.

https://www.icann.org/

Internet Engineering Steering Group (IESG)

The IESG is a body composed of the IETF chair and area directors.

https://www.ietf.org/about/groups/iesg/

Internet Engineering Task Force (IETF)

Lead standards-setting authority for internet-related protocols.

https://www.ietf.org/


Appendix 2 - 4


National 911 Program

The National 911 Program's mission is to provide federal leadership and coordination in supporting and promoting optimal 911 services. This federal "home" for 911 plays a critical role by coordinating federal efforts that support 911 services across the nation.

https://www.911.gov/

National Association of Search and Rescue (NASAR)

Non-profit association dedicated to advancement of professional, literary and scientific knowledge and training in the search-and-rescue field.

http://www.nasar.org/

National Association of State 911 Administrators (NASNA)

An association that represents state 911 programs in the field of emergency communications.

www.nasna911.org

National Center for Missing and Exploited Children (NCMEC)

The National Center for Missing and Exploited Children® opened in 1984 to serve as the nation’s clearinghouse on issues related to missing and sexually exploited children.

www.missingkids.com

National Emergency Number Association (NENA)

NENA is a not-for-profit corporation established in 1982 to further the goal of “One Nation–One Number.” NENA is a networking source and promotes research, planning and training. NENA strives to educate, set standards, and provide certification programs, legislative representation and technical assistance for implementing and managing 911 systems.

www.nena.org

National Exchange Carrier Association (NECA)

A membership association of U.S. local telecommunications companies dedicated to keeping customers connected on state-of-the-art communications networks.

www.neca.org

National Fire Protection Association (NFPA)

A global nonprofit organization, established in 1896, devoted to eliminating death, injury, property and economic loss due to fire, electrical and related hazards.

www.nfpa.org

National Highway Traffic Safety Administration (NHTSA)

NHTSA is a U.S. executive branch agency that is part of the Department of Transportation. It describes its mission as "Save lives, prevent injuries, reduce vehicle-related crashes." The National 911 Program is housed under NHTSA.

www.nhtsa.gov

National Information Standards Organization (NISO)

NISO is a non-profit association accredited by the American National Standards Institute (ANSI); it identifies, develops, maintains, and publishes technical standards to manage information in our changing and evermore digital environment. NISO standards apply both traditional and new technologies to the full range of information-related needs, including retrieval, re-purposing, storage, metadata, and preservation.

http://www.niso.org

National Institute of Standards and Technology (NIST)

A part of the U.S. Department of Commerce (DOC) that oversees the operation of the U.S. National Bureau of Standards. NIST works with industry and government to advance measurement science and to develop standards in support of industry, commerce, scientific institutions, and all branches of government. Its mission is to promote innovation and industrial competitiveness.

www.nist.gov


Appendix 2 - 5


National Integration Center (NIC)

DHS’s National Integration Center (NIC) is responsible for managing the implementation and administration of the National Incident Management System (NIMS).

https://www.fema.gov/fema-technical-assistance-program

National Joint Telecommunicator Emergency Response Taskforce (TERT) Initiative (NJTI)

A partnership between APCO and NENA that has worked to develop the many facets of a TERT program and to help states lacking an active TERT program to develop one. TERT involves a comprehensive program that includes assistance to individual states in developing programs that would lead to the establishment of predetermined and selected trained teams of individuals who can be mobilized quickly and deployed to assist communications centers during disasters.

www.njti-tert.org

National Suicide Prevention Lifeline

The National Suicide Prevention Lifeline is a national network of local crisis centers that provides free and confidential emotional support to people in suicidal crisis or emotional distress 24 hours a day, 7 days a week.

https://suicidepreventionlifeline.org/

National Telecommunications and Information Administration (NTIA)

NTIA is the executive branch agency that is principally responsible for advising the president on telecommunications and information policy issues. NTIA’s programs and policymaking focus largely on expanding broadband internet access and adoption in America, expanding the use of spectrum by all users, and ensuring that the internet remains an engine for continued innovation and economic growth.

https://www.ntia.doc.gov/

North American Network Operators Group (NANOG)

A governing body that provides guidance and instructions for the design of an IP network. NANOG typically is involved in the best current operational practices for IPv6 planning.

https://www.nanog.org/about/home

North American Numbering Plan Administration (NANPA)

The organization that has overall administrative responsibility of the North American Numbering Plan (NANP), an integrated telephone numbering plan serving 20 North American countries that share its resources.

www.nationalnanpa.com

Open Geospatial Consortium (OGC)

A standards development organization that promulgates standards for the global geospatial community.

http://www.opengeospatial.org/

Open Mobile Alliance (OMA) A standards development organization that develops standards for the mobile phone industry.

www.openmobilealliance.org

Organization for Advancement of Structured Information Standards (OASIS)

A standards development organization that promulgates standards for data interchange.

www.oasis-open.org

Packet Technologies and Services Committee (PTSC)

PTSC is an ATIS standards committee that develops standards related to services, architectures, signaling, network interfaces, next generation carrier interconnect, cybersecurity, and government emergency telecommunications service within next-generation networks.

https://www.atis.org/01_committ_forums/ptsc/

Urban and Regional Information Systems Association (URISA)

A non-profit association of professionals using GIS and other information technologies to solve challenges in U.S. state and local government agencies.

http://www.urisa.org/

299


Appendix 3 - 1

APPENDIX 3: Useful Resources 300

Federal Rules, Regulations & Laws 301 • Wireless Communications and Public Safety Act of 1999 (PL 106-81) 302 • Enhance 911 Service Act of 2004 (PL 108-494) 303 • New and Emerging Technologies 911 Improvement Act of 2008 304 • Food, Conservation and Energy Act of 2008 (“Farm Bill”) (PL 110-246) 305 • Implementing Recommendations of the 9/11 Commission Act of 2007 (PL 110-53) 306

Reports 307 • FCC TFOPA Adopted Final Report 308 • TFOPA Working Group 1 Supplemental Report—Optimal Cybersecurity Approach for PSAPs 309 • TFOPA Working Group 2 Supplemental Report—Phase II Supplemental Report: NG9-1-1 Readiness 310

Scorecard 311 • TFOPA Working Group 3 Supplemental Report—Funding Sustainment Model 312 • APCO Report—Project 43: Broadband Implications for the PSAP 313 • Government Accountability Office (GAO) Report to Congressional Committees: 911 Services Most States 314

Used 911 Funds for Intended Purposes, but FCC Could Improve Its Reporting on States’ Use of Funds 315 • FCC Emergency Access Advisory Committee (EAAC) Working Group 7 Report—Recommendations on 316

Timeline Alignment 317 • Canadian Radio-television and Telecommunications Commission, A Report on Matters Related to 318

Emergency 911 319

Guidance & Research Documents 320 • Information Sharing and Analysis Organization (ISAO) ISAO 100-2: Guidelines for Establishing an 321

Information Sharing and Analysis Organization (ISAO) 322 • National 911 Program State Assessment Handbook: A Guide for States Participating in the Statewide 911 323

System Assessment Process 324 • National 911 Program State Assessment Guidelines Synopsis Chart 325 • National 911 Program Next Generation 911 (NG911) Standards Identification and Review 326 • NG911 & FirstNet: Together Building the Future of Public Safety Communications (A Guide for State & 327

Local Authorities) 328 • National 911 Program Next Generation 911 (NG9-1-1) Interstate Playbook 329 • National 911 Program Next Generation 911 (NG9-1-1) Interstate Playbook, Chapter 2 330


Appendix 3 - 2

Databases & Resource Repositories 331 • APCO Standards to Download 332 • NASNA How to Start a State 911 Program 333 • NASNA State 911 Contacts 334 • NASNA 911 Regionalization—Tools and Information 335 • National 911 Program Documents & Tools 336 • National 911 Profile Database 337 • NENA Company Identifier Program 338 • NENA Standards & Other Documents 339