NENA NG9-1-1 Go-To Handbook: Difference between revisions

This is an early statement of expectations. At a minimum, the agencies expected to have access to the NG9-1-1 system should be identified. The scale of the project, such as regional or state level, must be considered (see Governance). If the network is intended to transport more than 9-1-1 calls, (e.g., [[NCIC (National Crime Information Center)|NCIC]], IP radio, Poison Control), specify exactly what other emergency services applications are intended to be supported on the network. This helps establish the network engineering criteria for the systems involved. Resource and cost sharing may occur at basic network levels, and must be factored into this analysis.

For Data Inventory and Standardization, data sources should be identified for use in the development of this project. For example, while the Master Street Address Guide ([[MSAG (Master Street Address Guide)|MSAG]]) is required as a data source, this project will require migration from tabular data to a combination of tabular and spatial data. A clear understanding of the source of all required data, including spatial/mapping data stored in a Geographic Information System ([[GIS (Geographic Information System)|GIS]]), ownership, responsibility and maintenance must be established.

For the geographic area being served, an analysis of existing broadband infrastructure must be developed. The analysis should be as complete as possible and include both private and public facilities. Record both the network architecture design and signaling used for each identified source of bandwidth and associate each with the user-stakeholder location. Where possible, note areas that lack physical diversity, so they can be analyzed further for possible remedies to lessen the risk of service failures. Consider how this area will interconnect with adjoining networks. Assess the need to interconnect with the E9-1-1 System Service Provider for routing and bridging of 9119-1-1 calls. This may be needed when originating carriers remain supported by the legacy Selective Router and the appropriate Public Safety Answering Points ([[PSAP (Public Safety Answering Point)|PSAPs]]) have transitioned to the NG9-1-1 system. It may also be necessary if calls are to be bridged between PSAPs supported by the NG9-1-1 system and those remaining on the legacy emergency system.

If there is no central repository for information regarding the equipment and software inventories within the PSAP, one must be assembled. Going beyond just [[Call Handling]] application, this inventory should be as granular as reasonably possible, and may include items such as types of Computer Aided Dispatch ([[CAD (Computer Aided Dispatch)|CAD]]), other public safety applications, mobile data applications, control of radio consoles and related administrative communications, used in the PSAP operational environment. These documents must be kept open for updates on a regular basis. This activity supports overall planning, and includes identifying opportunities to share resources, and assists in ensuring interoperability.

Creation of a plan for deploying and testing, even if incomplete must begin prior to the “Acquisition” phase of the project. Reasonably estimate the amount of effort not only for the public agencies including central 9-1-1 Authority groups, but the provider community as well. Assess the interaction and testing that may be required with the [[SSP]] (there may be more than one). Use a methodical approach to deployment and expect a thorough test period prior to going live with any installation. This plan, including specific test scripts must be in written form. Initially the test scripts might be high level. But before testing begins, those high-level scripts will need to be detailed and shared with all impacted stakeholders. Everyone involved in testing must understand their role and responsibility.

* Are existing liability protection statutes or regulations in place to cover all services and<br />information that may be delivered over NG9-1-1 systems and shared among emergency response entities (e.g., voice, sensors, images and other data, video, medical records, and any new, not yet developed, product or service)?