Working Group 2 Report: Optimal 9-1-1 Service Architecture FEDERAL COMMUNICATIONS COMMISSION TASK FORCE ON OPTIMAL PUBLIC SAFETY ANSWERING POINT ARCHITECTURE (TFOPA) DECEMBER 10, 2015
Jan 19, 2016
Working Group 2 Report: Optimal 9-1-1 Service Architecture
FEDERAL COMMUNICATIONS COMMISSION
TASK FORCE ON OPTIMAL PUBLIC SAFETY ANSWERING POINT ARCHITECTURE (TFOPA)
DECEMBER 10, 2015
2
Section 1/2: Executive Summary and Introduction Dave Holl
Section 3: Current PSAP Decentralized Environment Mary Boyd
Section 4: PSAP Optimization Environment Mario Derango, Jeff Wittek
Section 5: ESInet Optimization Considerations and Factors Chuck Vick
Section 6: Access and NG9-1-1 Core Service Implementation Roger Hixson
Section 7: Governance Laurie Flaherty
Section 8: NG9-1-1 Planning and Transition Considerations Dave Holl, Tony Montani
Section 9: Findings and Considerations Dave Holl
REPORT TABLE OF CONTENTSPRESENTERS
3
Working Group 2 Report: Optimal 9-1-1 Service Architecture
SECTION 1 & 2
EXECUTIVE SUMMARY AND INTRODUCTION
4
Public Safety Answering Points (PSAPs) are the gateway for access to emergency services for the public
Over 5900 PSAPs nationallyMore than 240 million emergency calls
annually to 9-1-1 nationallyWhile 9-1-1 continues to perform
admirably, communication technologies have evolved presenting new challenges and requirements for the 9-1-1 community
EVOLUTION OF NEXT GENERATION 9-1-1 SYSTEMS
5
Founded on time-division multiplexing (TDM) circuit switched voice services technology, wireline phone systems managed by telephone companies are the platform for making and receiving calls to 9-1-1
Internet Protocol (IP) network based technologies are now replacing the TDM (legacy) system
Known as the “TDM-to-IP” transition, the copper infrastructure across the nation will eventually be completely replaced by IP enabled systems
CURRENT 9-1-1 SYSTEM IMPLEMENTED OVER 40 YEARS AGO
6
Estimates as of November 2013 indicated that nearly 38% of all U.S. households currently rely on wireless as their primary phone service
This reliance on wireless technology results in about 70% of all 9-1-1 calls being placed from wireless phones annually
Despite the enhanced multi-media capability of wireless and VoIP devices, a 9-1-1 caller can currently only employ the voice capability or, in limited jurisdictions, text
TRANSITIONS ARE NOT NEW IN THE TECHNOLOGY REALM
7
Legacy 9-1-1 systems are not capable of receiving the various forms of multi-media common among everyday telephone users today
9-1-1 Authorities have operated legacy 9-1-1 in relatively independent and isolated operational environments
Implementation of NG9-1-1 will require a significant change to current roles and responsibilities
CHALLENGE FOR POLICY MAKERS AND
9-1-1 AUTHORITIES
8
This report introduces the expanded nature of NG9-1-1 as including what we term the Originating Service Environment (OSE)
This environment includes IP call set-up, location determination, validation and delivery to ESInets across the country
Implementation of the NG9-1-1 architecture will require many 9-1-1 Authorities to begin evolving a vision of collaboration as they develop new models of 9-1-1 service delivery
EXPANDED NATURE OF NG9-1-1
9
Developed with the intent to help clarify and educate decision-makers tasked with the critical responsibility to move from the current legacy 9-1-1 operational model to the Next Generation 9-1-1 configuration framework.
Working Group 2 divided their work into four distinct areas of the emerging NG9-1-1 environment: Emergency Services IP transport network (ESInet) Access and NG9-1-1 Core Services (NGCS), PSAP Terminating Equipment/Call-taking Support
subsystems - Computer Aided Dispatch (CAD), Management Information Systems (MIS), Dispatching Equipment, etc.
Governance
WG2 REPORT
10
11
ULTIMATE GOAL OF NG9-1-1 DEPLOYMENT
The development and implementation of a standardized nationwide, interconnected “system of systems” for 9-1-1 emergency communications
NG9-1-1 systems in their transition and end states can allow and support significantly enhanced: redundancy real-time and alternate call routing improved call transfer capabilities multi-media capability additional data, and back-up improvements
Discusses several potential architectural models for transitioning 9-1-1 Authority systems through the implementation and deployment of “Next Generation 9-1-1” (NG9-1-1) technology
It explores some of the basic operational and architectural possibilities available as well as the technical components, requirements, challenges and opportunities associated with deployment of NG9-1-1 systems, with significant focus on options for maximizing cost-effectiveness and effi ciency
The new paradigm of NG9-1-1 will be based upon system roles in an emergency services ecosystem
THIS REPORT
12
13
NG9-1-1 EcoSystem
14
NEW ROLES AND RESPONSIBILITIES
Inevitably new roles and responsibilities will emerge as Originating Service Providers (OSPs) evolve to an Originating Service Environment (OSE) and Next Generation 9-1-1 Core Services (NGCS) are developed and implemented
9-1-1 Authorities, existing in the legacy environment, will also change as broadening of role and responsibilities occurs as more multi-jurisdictional, regional, statewide, or even multi-state relationships are organized
15
16
NG9-1-1 DEPLOYMENT
Deploying Next Generation 9-1-1 capabilities is not a question of ‘if’, but rather ‘when’ the transition will occur
A primary message in this report is that NG9-1-1 architecture can be customized to support almost any configuration of PSAP operations
Factors that affect these configurations include financial, political, governmental and operational considerations
17
Working Group 2 Report: Optimal 9-1-1 Service Architecture
SECTION 3
CURRENT PSAP DECENTRALIZED ENVIRONMENT
18
The decentralized PSAP environment of today is prone to fragmentation and costly duplication
In the typical legacy environment, PSAP equipment and software are predominantly located within the boundary of each PSAP (though remote positions associated with a particular PSAP may be present).
A simplified diagram that follows illustrates the connections:
CURRENT DECENTRALIZED PSAP LEGACY ENVIRONMENT
19
PSAP
Call Taker System
Map Display
Logging & Reporting
Computer Aided
Dispatch
Legacy E9-1-1 Selective Router
E9-1-1 ALI
Database
MSAG and Legacy Data Management
OSP
ANIALI
Controller
SRDBCAMA
AsyncALI Bid
TDM
Subscriber Records
20
In a legacy environment operations of a PSAP are typically handled within the confines of the PSAP itself and are dependent on serving those agencies identified within the PSAPs 9-1-1 Service Plan
Local telecommunications interoperability among PSAPs operating in this environment is limited to the transfer of calls to another PSAP that has been pre-identified by the PSAPs involved, and arranged through the serving Local Exchange Company (LEC)
LEGACY PSAPS OPERATE INDEPENDENTLY AND
AUTONOMOUSLY
21
Optimization: Making the best, of anything. A lot of people think PSAP optimization means
consolidation. However, in a decentralized environment PSAPs can make the best of that environment in several ways. They can judge that decision based on:
Does it make sense: Operationally Financially Politically
Done correctly, they can optimize operations by: Sharing systems Joint purchasing Shared networks Shared staff
PSAP OPTIMIZATION CONSIDERATIONS
22
Working Group 2 Report: Optimal 9-1-1 Service Architecture
SECTION 4
PSAP OPTIMIZATION ENVIRONMENT
23
Assumes that Next Generation 9-1-1 Core Services and the ESInet have been considered
Whether deployed at the County, Regional or State level, the NG9-1-1 environment provides PSAP’s the flexibility to configure call flow and applications in a manner not previously available
It is not necessary for the Customer Processing Equipment (CPE) to be of the same manufacturer, and in larger deployments; e.g., regional or State, it is assumed that numerous CPE vendors will be in use
BASIS OF PSAP OPTIMIZATION
24
As NG9-1-1 becomes a reality, it will allow PSAPs the capability to organize and dynamically utilize partner PSAPs to assist during heavy call traffi c situations and/or outages
Several optimization models are discussed in the report:Shared Services (Centralized)HybridCentralized Call Taking CenterConsolidation by DisciplineVirtual
OPTIMIZED PSAP OPERATIONAL MODELS
25
ON-PREMISE DEDICATED INFRASTRUCTURE ARCHITECTURE
MODEL EXAMPLE
26
SAMPLE HOSTED, SHARED INFRASTRUCTURE
ARCHITECTURE MODEL
27
COMBINING DEDICATED ON-PREMISE AND SHARED SERVICES
28
Financial Solution costs (e.g., equipment, capital expenditure/operational expense)
Interoperability Functional interoperabilityGeographic interoperability: local, county, multi-county, state, national
Data sharingSurvivability/Reliability (Operational)
Level of service redundancyLevel of geo-diversity
KEY OPTIMIZATION FACTORS IN A JURISDICTION’S CONSIDERATION OF THE
OPTIMIZATION MODELS
29
Elasticity/ ScalabilityAbility to adapt to unanticipated peak loads
Ability to bring on additional jurisdictions without re-architecting
SecurityInformation SecurityCyber-attack resiliency
Operational Staffi ng Technical Support
CONT…
30
Working Group 2 Report: Optimal 9-1-1 Service Architecture
SECTION 5
ESINET OPTIMIZATION
CONSIDERATIONS AND FACTORS
31
“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 functional processes can be deployed, including, but not restricted to, those necessary for providing NG9-1-1 services…” NENA document 08-506 “Emergency Services IP Network
Design”
ESINET
32
ESInets deployed today are primarily used for delivery of limited NG9-1-1 Services such as legacy Selective Router and ALI replacement
This limited ESInet Architecture norm will change as the NENA i3 vision is realized with Originating Service Providers (OSPs) providing data feeds, enhanced service providers establish interconnections with ESInets across the United States and ESInets become interconnected
ESINET EVOLUTION
33
ESInets consist of the following categories of capabilities. For the purposes of ESInet discussions and brevity, these categories are abstracted from generally accepted networking models:TransportInternet Protocol (IP) ServicesManagement InfrastructureSecurity Infrastructure
ESINET CATEGORIES OF CAPABILITY
34
Local ESInet - local authority elects to host Next Generation Core Services (NGCS) within existing PSAP datacenters or facilities and maintains their own ESInet
Shared-Hosted ESInet - a regional entity authority (group of PSAPs, county, multiple counties or state) elects to host Next Generation Core Services (NGCS) on a shared ESInet
Hybrid ESInet - some elements of the Shared Hosted ESInet are combined with elements that are contracted
Contracted, Managed ESInet - This is a “shared” network between multiple served PSAP tenants, which could scale from small region to nationwide. The ESInet managed service vendor builds and maintains the ESInet
ESINET USE CASES
35
HOSTED SHARED ESINET DEPLOYMENT MODELS
36
The ESInet should be monitored 24x7 by a Network Operations Center with visibility across the network
Network elements should be alarmed Priority should be established for network
alarms with service impacts taking top priority
Potential service disruptions such as the loss of redundancy should also be prioritized
Clear rules and responsibilities need to be established and to the extent possible one party have accountability for coordinating across these entities for maintenance and restoral efforts
NETWORK MONITORING & OPERATIONAL METRICS
37
Emergency communication networks strive to be reliable with high availability
Five nine’s (99.999%) is the goal for availability of these networks and is achieved through various means focused on diversity, redundancy, and alternate routing
While five nine’s is the generally accepted minimum availability service level, it should be noted that this equates to only 5.26 minutes of unscheduled downtime or service unavailability annually
ESINET RELIABILITY
38
Working Group 2 Report: Optimal 9-1-1 Service Architecture
SECTION 6
ACCESS AND NG911 CORE SERVICE
IMPLEMENTATION
39
NG9-1-1 implies routing a call based on a caller’s location information as provided by the Originating Service Environments (OSE) (a combination of Originating Service Provider, Network Access Provider, Location Information Provider and SmartPhone Apps provider).
A 9-1-1 service system in its simplest form is illustrated in the following diagram:
NG9-1-1 SERVICE SYSTEM
40
9-1-1 SERVICE SYSTEM IN ITS SIMPLEST FORM
ESInet
RouteCall
Originating Service
Environment
PSAP
PSAP Boundaries
GIS
IP PSAP
“Call”
Location Destination
“Call”
9-1-1 Call with
Location Information
Location Location
41
Additional complexity is added when it is necessary to determine the responsible Public Safety Authority, as illustrated below (e.g., where the OSP’s territory potentially covers multiple PSAPs or Public Safety Authority regions)
9-1-1 SERVICE SYSTEM COVERING MULTIPLE AUTHORITY REGIONS
42
WHERE THE OSP’S TERRITORY POTENTIALLY COVERS MULTIPLE PSAPS
OR PUBLIC SAFETY AUTHORITY REGIONS
ESInet
RouteCall
Originating Services
Environment
PSAP
PSAP Boundaries
GIS
IP PSAP
“Call”
Location Destination
“Call”9-1-1 Call with
Location Information
Location
Location
Forest Guide
GIS
RoutingInstructions
1
2
3
4
5
43
NG9-1-1 architecture concepts and functional services do not assume that the Originating Service Environment (OSE) necessarily knows who the PSAP and/or 9-1-1 Authority is for a given geographic area
In the legacy model the service area of TDM switches was coincident with one (or a few) PSAP(s)
In an IP based world, the user could be in any PSAP and 9-1-1 Authority’s jurisdiction
SPECIFIC NG9-1-1 ACCESS IMPLEMENTATION OPTIONS
44
NG9-1-1 requires services that make it possible to determine the appropriate 9-1-1 Authority’s NG9-1-1 network, in order to then be routed to the appropriate PSAP within that NG9-1-1 system
The OSE has several operations that require interaction with a Public Safety Authority:Validate Location InformationDetermine the appropriate Public Safety Authority to receive a 9-1-1 call or message
Obtain a copy of the rules to validate location information (LVF function)
SPECIFIC NG9-1-1 ACCESS IMPLEMENTATION OPTIONS
45
In order to determine the appropriate Public Safety Authority an NG9-1-1 service (i.e., Forest Guide) is provided that allows OSEs to query and determine the responsible Public Safety Authority or representative of the Public Safety Authority
The general Forest Guide concept is a tree structure where an OSE queries at the level for which they know the subscriber/user resides.
CALL ROUTING AND FOREST GUIDES
46
GIS DATA AND SECURITY SERVICES FOUNDATION
47
The concept of Forest Guides requires cooperative sharing of the respective geographic polygons that define Public Safety Authority’s service area
These mechanisms are complex and have many issues to resolve with respect to sharing and change management
The need to dynamically determine responsible Public Safety Authorities is a NENA i3 end-state architecture requirement
COOPERATIVE SHARING OF GEOGRAPHIC POLYGONS
48
STATE FOREST GUIDE HIERARCHICAL ROLL UP
49
FOREST GUIDE HIERARCHICAL DATA ROLL UP
50
The NENA i3 vision Long Term architecture standard changes the processing model for 9-1-1 calls and defines different responsibilities for both the 9-1-1 Service Provider and the OSE
The biggest changes evolve around the use of Geographical Information System (GIS) technology and the OSE providing the caller’s location
NENA I3 VISION
NENA I3 NG9-1-1 VISION
51
52
Working Group 2 Report: Optimal 9-1-1 Service Architecture
SECTION 7
GOVERNANCE
53
The first 9-1-1 systems were responsible for a specific area or region and operated independent of each other, governance was naturally decentralized
The advent of NG9-1-1 will change the 9-1-1 governance model and basic elements of the 911 “culture”
NG9-1-1 increases the opportunity for PSAPs to share resources and to cooperate and collaborate at multiple levels with potentially greater economic and technical effi ciencies
MOVING FROM INDEPENDENT TO INTERCONNECTED 9-1-1
The extent to which any jurisdiction can address resource sharing is dependent on its willingness to share not only resources, but also dedicated control of infrastructure and operations.
NG9-1-1 supports standardized operational models that promote resource sharing and interoperability.
With migration to NG9-1-1, many more combinations and permutations of roles, relationships, and considerations are required
MOVING FROM INDEPENDENT TO INTERCONNECTED 9-1-1
54
PSAP managers, 9-1-1 Authorities and their governing bodies, will ultimately have to decide whether to remain independent or share resources, and are responsible for the consequences of those decisions
If they decide that for certain technical, operational or financial aspects, there’s value in working together, it will become important to establish the parameters and processes of their business relationship
MOVING THE SHARING PROCESS FORWARD
55
56
NG9-1-1 decision-makers have competing priorities and limited funds. As a result, an analysis of those costs and benefits can assist in making the best implementation choice for their jurisdiction
Some of the factors in this cost benefit analysis process may include infrastructure design, quality of service, resiliency, redundancy, reliability, and operational effi ciency
Best practices in these elements are in place and/or evolving
NG9-1-1 SHARING OPPORTUNITIES ANALYSIS
VALUE PROPOSITION CONSIDERATIONS
57
NENA describes a “9-1-1 Authority” as a:
. . . State, County, Regional or other governmental entity responsible for 9-1-1 service operations. For example, this could be a county/parish or city government, a special 9-1-1 or Emergency Communications District, a Council of Governments or other similar body.
9-1-1 AUTHORITIES
58
59
Single 9-1-1 Authority – can provision a NG9-1-1 system. Then governance, oversight and operation of the system is logically the responsibility of that entity.
Multiple 9-1-1 Authorities - multiple 9-1-1 authorities may be engaged, and new intergovernmental arrangements must be developed to oversee the service environment desired – arrangements that provide a fair and equal role for all the 9-1-1 authority stakeholders involved.
MULTIPLE 9-1-1 AUTHORITY ARRANGEMENTS
60
Migration to NG9-1-1 provides the opportunity for PSAPs and jurisdictions to share resources at a level not possible in the legacy environment
The nature of existing governance models, and the relationships between and among jurisdictions, will directly impact how, and to what extent, the NG9-1-1 model is deployed and the extent to which their citizens will realize its benefits
NEW FORMS OF 9-1-1 AUTHORITY BENEFITS
61
Working Group 2 Report: Optimal 9-1-1 Service Architecture
SECTION 8
NG9-1-1 PLANNING AND TRANSITION CONSIDERATIONS
The movement toward nationwide Next Generation 9-1-1 continues to be an evolving process
Most PSAPs continue to function in ‘Legacy 9-1-1’ configurations, a number can be considered to be ‘Transitional’
As of the time of this report no 9-1-1 Authority has attained a ‘Fully Functional NG9-1-1’ implementation
NG9-1-1 TRANSITION
62-D
NG9-1-1 TRANSITION STEPS
NG9-1-1
Legacy 9-1-1
Transitional NG9-1-1
NG9-1-1 Transitional Steps
63-D
The operating domains - OSE, NG9-1-1 Core Services Providers, and PSAPs operate together to provide complete 9-1-1 services
OSE delivers “calls” to NG9-1-1 Core Services Providers who route those requests for assistance to the proper PSAPs
These operating domains are interconnected via the ESInet, which provides IP transport and other networking services
A diagram of this NG9-1-1 Services System Environment follows:
NG9-1-1 SYSTEM SERVICES ENVIRONMENT
64-D
NG9-1-1 SYSTEM SERVICES ENVIRONMENT
NG9-1-1 Core Services Providers
OSEs
Access Providers&
CommunicationsService
Providers
ESInet ESInet
PSAPs
Performing Local Operational
Responsibilities
NG9-1-1 System Services Environment
65-D
Ultimately, 9-1-1 Authorities need to make decisions necessary to begin the transition process
In most cases, these governance decisions will not be made by single PSAP Authorities even though they currently may have self-contained legacy 9-1-1 systems
Instead, new coalitions and collaborations of cooperative PSAP Authorities, at various levels, will need to evolve and work together to achieve economies of scale
NEW COLLABORATIVE PSAP AUTHORITIES WILL NEED TO
EMERGE
66-D
The evolution strategy from legacy 9-1-1 to NG9-1-1 is critical to 9-1-1 Authorities due to the complexities involved and costs imposed by duplication
Conversion delays, which create a combined legacy network and Next Generation 9-1-1 architecture, will require funding overlapping systems
The 9-1-1 Authority will bear larger costs while the two-system hybrid architecture remains in place
THE ESCALATED COST OF DELAYED EVOLUTION TO NG9-1-1
67-T
DUAL ENVIRONMENT WHERE THE LEGACY SELECTIVE ROUTER IS MAINTAINED AND PSAPS ARE SERVED BY EITHER THE LEGACY SELECTIVE ROUTER OR NG9-1-1
CORE SERVICES
Selective Routing between IP PSAPs and TDM PSAPs will be complicated and costly since dual networks are required and TDM signaling is not IP capable.
IP or TDMPSAP
1...
IP or TDMPSAP
n...
Legacy 9-1-1 Selective
Routing Tandem1...
Legacy 9-1-1 Selective
Routing Tandemn...
OSP/OSE1 ...
OSP/OSEn ...
NG9-1-1 Core Services or IP Selective Router
1...
TDM PSAP
1...
TDM PSAP
n...
NG9-1-1 Core Services or IP Selective Router
n...
68-T
An important understanding in this transition planning process will be for the 9-1-1 Authority to have a true appreciation for what is involved in the NG9-1-1 ecosystem from a technology and functionality position
In NG9-1-1 configurations, through the establishment of Emergency Services IP networks, NG9-1-1 Core Services can reside anywhere on the network and can be economically shared in collaborative environments as depicted in the following diagram:
TRANSITIONAL NG9-1-1
69-T
TRANSITION TO NG9-1-1
IP or TDMPSAP
1...
IP or TDMPSAP
n...
OSP/OSE1 ...
OSP/OSEn ...
NG9-1-1 Core Services or IP Selective Router
1...
NG9-1-1 Core Services or IP Selective Router
n...
IP or TDMPSAP
2...
IP or TDMPSAP
3...
70-T
9-1-1 Authorities should develop an in-depth NG9-1-1 transition plan
With proper planning, Next Generation 9-1-1 Core Services, as described in Working Group 2’s report, can be implemented in a reasonable time frame
Through economies of scale 9-1-1 Authorities can minimize transitional costs and maintain positive outcomes with maximum fiscal responsibility
NG9-1-1 TRANSITION PLANNING ESSENTIAL
71-T
9-1-1 Authorities need to develop an understanding of the steps appropriate for them and their specific situation
There are three primary capabilities or “Foundation Elements” that must be established: ESInet IP PSAPGIS Data Preparation
These elements do not necessarily need to be accomplished simultaneously or in any particular order, but will be driven by the 9-1-1 Authorities goals and NG9-1-1 transition plan
NG9-1-1 FOUNDATIONAL ELEMENTS
72-D
Foundation Elements
Establish i3 core functions while managing transitional elements
Interoperate with changing Telecommunications Industry
(LVF, E-CSCF, IMS, NNI, IETF, Internet)
i3 NENA vision end-state fully
realized
Advanced Applications and Data Services
Additional Requests for Assistance Types
PUBLIC SAFETY MIGRATION STEPS TO NG9-1-1
Many paths and steps to the long term NG9-1-1 vision
Establish ESINet Infrastructure(IP Network and Softswitch)
IP PSAP
GIS Data Preparation (Location Validation, Routing, Service Identification)
Evolution of the overall environment(s)(Roles, Regulations, Tariffs, Funding, Incumbents, FCC, State…)
Carrier’s establish LIS and deliver a routable PIDF-LO
with call setup
i3 vision issue resolutions
Today Months Years Many Years73-D
NG9-1-1 DEPLOYMENT CHART
ESInet deployment
Deployed locally, operated regionally according to state standardsIntegrated technology supports multiple PSAPs Based upon NENA i3 standards
GIS data
Statewide GIS Repository created for LVF & ECRF NG9-1-1 GIS database createdBased upon NENA i3 standards
Security
Security plan implemented and deployedCSRIC and NGSEC integrated into state planBased upon NENA i3 standards
NG9-1-1 Core Services
ESRP/ECRF/PRF
Applications
Identify and deploy enhanced applicationsIntegrate with NG9-1-1, PSAP and other operating environments, as appropriate.Based upon NENA i3 standards 74-D
PSAPs should work with their 9-1-1 Authority to create an overall plan and progression chart for their particular situation
In cases where there is no established 9-1-1 Authority, PSAPs should first address their organizational approach and financial capabilities to move forward
A plan should include the basic migration steps explained above and move toward the more detailed functional capabilities and functional elements
NG9-1-1 MIGRATION AND DEPLOYMENT PLANNING
75-D
76
Working Group 2 Report: Optimal 9-1-1 Service Architecture
SECTION 9
SUMMARY, FINDINGS,
CONSIDERATIONS, AND
CONCLUSION
77
This work is not exhaustive Additional guidance needs to be developed
to best make use of this information, and we encourage the Federal Communications Commission to charter such efforts as part of the 2016 TFOPA initiative
Potential topics to be explored could be:potential costs of transition comparative early developer use cases additional study of access for people with speech and hearing disabilities
integration of applications which provide access to the 9-1-1 system
SUMMARY
78
The Working Group is aware that communications and communications technologies like the Internet of Things (IoT), Over The Top apps (OTT), analytics, and other new networking technologies continue to rapidly evolve and will eventually become part of the public safety ecosystem
As the public safety technology ecosystem expands, how the new technologies and capabilities will be integrated into the NG9-1-1 environment and effect emergency responses will be an important consideration for future study and analysis
SUMMARY
79
As Working Group 2’s report illustrates, the aspects of transitioning 9-1-1 services from the current legacy environment to the NG9-1-1 environment will present a myriad of technical, operational, and political choices for both governments and the public safety community at all levels
The deployments of NG9-1-1 will require increased coordination and partnerships among governments and public safety stakeholders
THE NG9-1-1 CHALLENGE
80
An overall goal of the report was to educate 9-1-1 Authorities and policy offi cials so they have an understanding of NG9-1-1, its components, capabilities, deployment options, and potential benefits
Factors that affect these configurations include financial, political, governmental and operational considerations
THE NG9-1-1 CHALLENGE
81
As NG9-1-1 accelerates and matures, current roles and responsibilities among all entities involved in providing 9-1-1 services will be impacted by the impending technology choices and changes
Effective communications and coordination with political and public safety agency leadership and the general public will be important in addressing concerns and managing expectations
CURRENT ROLES AND RESPONSIBILITIES WILL BE
IMPACTED WITH NEW CHOICES
82
Armed with this understanding, 9-1-1 Authorities and decision-makers will be able to apply that knowledge to ongoing objective and collaborative dialogues that will enable them to craft a NG9-1-1 plan that meets the needs of their jurisdictions, ensuring all citizens including persons with disabilities have direct access to 9-1-1
It was not the intent of the Working Group to recommend a particular configuration for the deployment of NG9-1-1, therefore the report is absent a “one-size fits all” architectural recommendation
FINDINGS & CONSIDERATIONS
83
A primary message in this report is that NG9-1-1 architecture can be customized to support almost any configuration of PSAP operations
The Working Group did feel it important to identify key “Findings and Considerations” contained in the report that 9-1-1 Authorities might consider to assist in the planning and deployment of a NG9-1-1 system
The following represents an outline of the highlights of those twenty-nine (29) considerations:
FINDINGS & CONSIDERATIONS
84
Policy/Regulation (7) Impacts of the changing roles from Legacy to Next Generation 9-1-1
Governance (7)The need to evolve new governance structures
Architectural/Technical (6)Adopt and implement new infrastructure
Standard/Best Practices (6)Continue and accelerate standard development
Education/Training (3)Comprehensive outreach and education is needed
FINDINGS & CONSIDERATIONS
85
QUESTIONS OR COMMENTS