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

The purpose and scope of this document is to provide guidance to help [[9-1-1 Authority|9-1-1 Authorities]] create a smooth, timely and efficient project management approach and transition plan to accomplish implementation of [[NG9-1-1 (Next Generation 9-1-1) Services|NG9-1-1]]. A considerable trove of written material and standards exists about the topic of NG9-1-1 within NENA, [[APCO (Association of Public Safety Communications Officials)|APCO]], and other standards and industry organizations. An oft stated question is, “where does one start to gain a more complete understanding of all the materials?” This reference document can assist in answering this question. To navigate amongst the many NG9‑1‑1 reference materials, which are dispersed in various online web site locations, can be a daunting task for a new reader to the subject of NG9-1-1, and sometimes even so for a seasoned industry professional. Various topic areas relevant to NG9‑1‑1 are listed in this document to orient a [[9-1-1 Authority]] person in search of context specific information. The topic area contains a very brief description and a list of references is given. The references contain a pointer to the most relevant portions of the referenced document for a reader to focus on to gather an understanding of that topic area. The reference pointers are just a beginning shortcut for a reader to focus on, as only a complete reading of the materials referenced can fully provide the background information a reader should understand to make an orderly and progressive transition to NG9-1-1.

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 [[SSPService Provider|System Service Provider]] (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.