{"text_format":"1","workbook":"xlsx","n_sheets":6,"sheets":["Instructions","Self-Assessment","Element Descriptions"," Legacy NG911 Scorecard","Acronyms","Data Backend"],"not_rendered":{"charts":0,"images":4,"macros":1,"external_links":1,"defined_names":7,"comments":2,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Instructions","index":0,"n_rows":64,"n_cols":2,"rows_kept":64,"cut":false,"hidden":false,"merged":[[3,0,3,9]]}
[]
[]
[]
["Next Generation 911 Self-Assessment Tool"]
[]
[null,"Introduction"]
[null,"This Next Generation 911 Self-Assessment Tool enables emergency communications centers (ECCs)/public safety answering points (PSAPs) administrators and oversight personnel to evaluate their center’s NG911 Maturity State. ECC/PSAP administrators and practitioners can use the Tool to strengthen their understanding of NG911 elements, increase their awareness of NG911 maturity continuum position, assist in planning NG911 transition steps, and enable a consistent terminology for NG911 maturity state. "]
[null,"The Tool includes some technical questions which may require collaboration with leadership, technical staff and/or vendors to answer. No tool can detail each ECC/PSAP's implementation exactly, so answers should be an effort to best reflect current implementation and progress. Tool results are for use by the ECC/PSAP completing the questionnaire and are shared only at their discretion."]
[null,"Built on stakeholder feedback from multiple levels of government, industry, and academia, the Tool embodies the work of the SAFECOM-NCSWIC NG911 Working Group members, FCC’s TFOPA, and the National 911 Program."]
[]
[null,"Self-Assessment Tab Instructions"]
[null,"1. After enabling macros, select your organization’s implementation characterization in row 3, noting the following definitions. For federal and academic institutions, select the option that best characterizes your organization:\n    - Regional: All intrastate or interstate organizations that are multi-jurisdictional\n    - State: All state, commonwealth, and territorial organizations\n    - Local: All remaining city, town, county, village, parish, tribal, and municipal organizations"]
[null,"2. For each section (Governance, Architecture, Security):\n    - Click on subsection headings for hyperlinked descriptions:                                                                                                                                                                          "]
[null,"* Governance subsections:Structure Design & Framework, Strategic Planning, Coordination, Funding & Resources"]
[null,"* Architecture subsections:Routing & Location, Geographic Information Systems Data, Next Generation Core Service Elements, Network, PSAP Call Handling System & Applications, Operational Planning, Optional Interfaces"]
[null,"* Security subsections:Identification & Discovery, Assessment & Prioritization, Implementation & Operation, Monitoring &"]
[null,"Evaluation, Testing & Analysis, Improvement & Evolution"]
[null,"3. For each question:"]
[null,"    - Answer question provided in Column B by selecting one of the dropdown options in Column C"]
[null,"    - Hover over any question for more detail if the nature of the question is unclear and additional text may appear"]
[null,"    - Language clarifications:"]
[null,"       * “Planning” refers to the preparation for transitioning from Legacy 911 to NG911"]
[null,"       * “Executed” refers to an action that has been accomplished, regardless of whether or not the ECC/PSAP is "]
[null,"responsible for the action. For instance, many ECC/PSAPs provide planning input to state, county, or others that execute "]
[null,"the tasks on behalf of the ECC/PSAP"]
[]
[null,"Self-Assessment Tab Results"]
[null,"This Self-Assessment Tool is intended strictly for educational purposes of ECC/PSAPs. Results of the tool are for use by the ECC/PSAP performing the self-assessment. The tool does not share any results with any entity, as sharing is at the discretion of the ECC/PSAP performing the assessment. For convenience, a \"Complete Assessment and Export to PDF\" button is included to create a shareable and printable version of the completed tool. This document will appear under the same name as this spreadsheet in the \"Documents\" folder."]
[null,"Section results:Once questions in any section (Governance, Architecture, Security) are answered, a maturity state designation for that section will appear as the last row of the section."]
[null,"Overall result:Once all questions are answered, an overall maturity state designation will appear in cell C8."]
[]
[null,"Next Generation 9-1-1 Definition "]
[null,"Next Generation 9-1-1 (NG911) is defined as \"an Internet Protocol (IP)-based system comprised of managed Emergency Services IP networks (ESInets), functional elements (applications), databases, and call handling systems (CHS) that replicate traditional E9-1-1 features and functions and provides additional capabilities. NG9-1-1 is designed to provide access to emergency services from all connected communications sources, and provide multimedia data capabilities for Public Safety Answering Points (PSAPs) and other emergency service organizations.\" (TFOPA)\n"]
[null,"ECC/PSAP Definition"]
[null,"The terms defining the Nation’s 911 and public safety communications centers have matured over time. The Next Generation 911 Self-Assessment Tool references the term “ECC/PSAP”. For purposes of this document, “ECC/PSAP” is meant to encompass the following definitions:"]
[null,"* Public Safety Answering Point (PSAP):a center “where 911 requests are answered, evaluated, and processed to determine whether dispatch of field responders is needed, and in what form.” (TFOPA)"]
[null,"* Emergency Communication Center (ECC):“a facility with capabilities that include intelligence collection and monitoring, 911 multimedia traffic processing, full scale dispatch, and incident command capabilities.” (APCO Project 43)"]
[null,"* 911 Communication Center:“a facility that is designated by a governmental authority to perform the functions of a PSAP and perform one or more of the following functions:"]
[null,"(1) process and analyze 911 Requests for Emergency Assistance and other gathered information; "]
[null,"(2) dispatch appropriate Emergency Response Providers; "]
[null,"(3) transfer or exchange 911 Requests for Emergency Assistance and other gathered information with other "]
[null,"Emergency Communciations Centers and Emergency Responders Providers;"]
[null,"(4) analyze any communications received from Emergency Response Providers; and "]
[null,"(5) perform incident command functions.” (NENA)"]
[null,"* Public Safety Communications Center (PSCC):“a public safety entity where 911 or other emergency calls for service are processed and public safety resources are dispatched.” (APCO/NENA ANS1.107.1.2015)"]
[null,"The Tool uses the “ECC/PSAP” term to better encompass the nature of the Nation’s 911 and public safety communications centers. The processes and procedures to transition to NG911 do not depend on these terms; therefore, the Self-Assessment Tool answers are not impacted by use of any specific term."]
[]
[null,"Additional Tabs"]
[null,"1. Element Descriptions\n    - Defines in detail the scope and various areas of interest for the Self-Assessment Tool\n2. Acronyms\n    - Provides a comprehensive listing of all referenced acronyms within the Self-Assessment Tool"]
[]
[null,"Additional Resources"]
[null,"APCO Project 43"]
[null,"Federal Communications Commission (FCC) Communications Security, Reliability and Interoperability Council (CISRIC) Best Practices"]
[null,"National Institute for Standards and Technology (NIST) Cybersecurity Framework, Version 1.1"]
[null,"NENA Master Glossary"]
[null,"NENA NG911 Security Audit Checklist (75-502)"]
[null,"NENA NG911 Security Information Document"]
[null,"NENA Security for NG911 Standard (75-001)"]
[null,"SAFECOM-NCSWIC NG911 Working Group: Cyber Risks to Next Generation 9-1-1"]
[null,"TFOPA Working Group 1 Report: Optimal Cybersecurity Approach for PSAPs"]
[null,"TFOPA Working Group 2 Report: NG9-1-1 Readiness Scorecard"]
[]
[]
[null,"For questions, comments, or concerns, please contact the NG911 Working Group."]

{"sheet":"Self-Assessment","index":1,"n_rows":197,"n_cols":4,"rows_kept":197,"cut":false,"hidden":false,"merged":[[105,0,105,3],[7,0,7,3],[148,0,148,2],[146,0,146,2],[36,0,36,2],[43,0,43,2],[100,0,100,2],[97,0,97,2],[87,0,87,2],[74,0,74,2],[116,0,116,2],[125,0,125,2],[130,0,130,2],[70,0,70,2],[107,0,107,2],[111,0,111,2],[0,0,0,1],[10,0,10,2],[23,0,23,2],[32,0,32,2],[66,0,66,2],[57,0,57,2],[2,2,2,3],[1,2,1,3],[9,0,9,3],[191,0,191,2],[188,0,188,2],[182,0,182,2],[160,0,160,2],[136,0,136,2],[145,1,145,6],[141,0,141,2],[155,0,155,2],[149,0,149,2]]}
[]
[null,null,"Dropdown Options"]
[1,"Please choose the description that best characterizes your ECC/PSAP:","Local: All remaining city, town, county, village, parish, tribal, and municipal organizations"]
[]
[null,null,"Overall Maturity State"]
[null,null,{"$f":"IF(OR(C104=\"Legacy\",C145=\"Legacy\",C197=\"Legacy\"),\"Legacy\",IF(OR(C104=\"Foundational\",C145=\"Foundational\",C197=\"Foundational\"),\"Foundational\",IF(OR(C104=\"Transitional\",C145=\"Transitional\",C197=\"Transitional\"),\"Transitional\",IF(AND(C111=\"Yes, a LIS or its equivalent is implemented with each OSP\",C104=\"Intermediate\",C145=\"Intermediate\",C197=\"Intermediate\"),\"Jurisdictional End State\",IF(AND(C104=\"Intermediate\",C145=\"Intermediate\",C197=\"Intermediate\"),\"Intermediate\",\"#N/A\")))))","v":"#N/A"}]
[]
["Governance"]
[null,null,"Dropdown Options"]
["CHARACTERIZE IF YOUR ORGANIZATION HAS:"]
["State Governance Structure Design & Framework",null,null,"Maturity State"]
[29,{"$f":"'Data Backend'!A3","v":"Established a name, authority, and purpose for a formalized 911 governance body that: a) solidifies the body’s legal standing and purpose; b) indicates its authority and any amendments to prior authorities; and c) confirms any concurrent jurisdictional bounds, if applicable:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$4:$B$6,MATCH($C12,'Data Backend'!$A$4:$A$6,0)),\"\")","v":""}]
[30,{"$f":"'Data Backend'!A7","v":"Established the governance body’s oversight authority—including any rule-making authority—aligning activities to overarching strategies and plans, and maintaining fiduciary and fiscal compliance:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$8:$B$10,MATCH($C13,'Data Backend'!$A$8:$A$10,0)),\"\")","v":""}]
[31,{"$f":"'Data Backend'!A11","v":"Regulations, a charter, and/or bylaws that build upon the legal authority or set an agreed-upon authority, concurring with all jurisdictions where applicable:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$12:$B$14,MATCH($C14,'Data Backend'!$A$12:$A$14,0)),\"\")","v":""}]
[32,{"$f":"'Data Backend'!A15","v":"A reporting mechanism for the governance body to notify the public and all appropriate government agencies/bodies on accomplishments, issues, and future priorities to enhance 911/NG911:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$16:$B$18,MATCH($C15,'Data Backend'!$A$16:$A$18,0)),\"\")","v":""}]
[33,{"$f":"'Data Backend'!A19","v":"A membership listing of 911 governance authorities’ representatives:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$20:$B$22,MATCH($C16,'Data Backend'!$A$20:$A$22,0)),\"\")","v":""}]
[34,{"$f":"'Data Backend'!A23","v":"Defined roles, responsibilities, and functions (e.g., voting, non-voting, and ex-officio) for members of the governance authority:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$24:$B$26,MATCH($C17,'Data Backend'!$A$24:$A$26,0)),\"\")","v":""}]
[35,{"$f":"'Data Backend'!A27","v":"A 911 Administrator (and appropriate support) to execute 911 services (e.g., operations, training, and performance standards):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$28:$B$30,MATCH($C18,'Data Backend'!$A$28:$A$30,0)),\"\")","v":""}]
[36,{"$f":"'Data Backend'!A31","v":"An ongoing mechanism to encourage collaboration among NG911 and other public safety governance bodies (e.g., broadband, other jurisdictions) to promote interoperability:"}]
[37,{"$f":"'Data Backend'!A35","v":"A governance authority that collaborates and engages with all applicable Statewide Interoperability Coordinators (SWICS):"}]
[38,{"$f":"'Data Backend'!A39","v":"A governance authority that collaborates and engages with all applicable state 911 administrators:"}]
[39,{"$f":"'Data Backend'!A43","v":"A governance authority that collaborates and engages with broadband authorities:"}]
[40,{"$f":"'Data Backend'!A47","v":"A governance authority that collaborates and engages with all applicable neighboring jurisdictions:"}]
["State Governance Strategic Planning",null,null,"Maturity State"]
[41,{"$f":"'Data Backend'!A52","v":"Established requirements for compliance with standards and policy for state-funded ECC/PSAP operations:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$53:$B$55,MATCH($C25,'Data Backend'!$A$53:$A$55,0)),\"\")","v":""}]
[42,{"$f":"'Data Backend'!A56","v":"Developed a 911/NG911 plan:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$57:$B$60,MATCH($C26,'Data Backend'!$A$57:$A$60,0)),\"\")","v":""}]
[43,{"$f":"'Data Backend'!A61","v":"Developed joint 911/NG911 MOU/As for multi-jurisdictional cooperation:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$62:$B$65,MATCH($C27,'Data Backend'!$A$62:$A$65,0)),\"\")","v":""}]
[44,{"$f":"'Data Backend'!A66","v":"Established a state entity with authority to collaboratively plan the entire or certain components of the NG911 system (e.g., ESInet, databases):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$67:$B$70,MATCH($C28,'Data Backend'!$A$67:$A$70,0)),\"\")","v":""}]
[45,{"$f":"'Data Backend'!A71","v":"Aligned the governance body with the Statewide Communications Interoperability Plan (SCIP):"}]
[46,{"$f":"'Data Backend'!A74","v":"Aligned the governance body with available NG911 initiatives and strategic plans:"}]
[47,{"$f":"'Data Backend'!A77","v":"Updated the governance body periodically to reflect changes to NG911 emergency communications goals and objectives:"}]
[48,{"$f":"'Data Backend'!A80","v":"Developed reporting procedures on 911/NG911 progress to appropriate authorities:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$81:$B$83,MATCH($C32,'Data Backend'!$A$81:$A$83,0)),\"\")","v":""}]
["State Governance Coordination",null,null,"Maturity State"]
[49,{"$f":"'Data Backend'!A85","v":"Implemented a statewide NG911 entity (e.g., NG911 governance board, SIGB, SIEC) with coordination, advisory, and support responsibility for all ECC/PSAPs within the state:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$86:$B$89,MATCH($C34,'Data Backend'!$A$86:$A$89,0)),\"\")","v":""}]
[50,{"$f":"'Data Backend'!A90","v":"The statewide NG911 entity is represented on a statewide body coordinating all emergency communications:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$91:$B$94,MATCH($C35,'Data Backend'!$A$91:$A$94,0)),\"\")","v":""}]
[51,{"$f":"'Data Backend'!A95","v":"A liaison to provide guidance on NG911 policies, funding, and operation and technical developments:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$96:$B$98,MATCH($C36,'Data Backend'!$A$96:$A$98,0)),\"\")","v":""}]
["State Governance Funding & Resources",null,null,"Maturity State"]
[52,{"$f":"'Data Backend'!A100","v":"Enough resources (e.g. staff, funding) to carry out its NG911 mandate:"}]
[53,{"$f":"'Data Backend'!A103","v":"The authority to collect and disburse NG911 funds:"}]
[54,{"$f":"'Data Backend'!A106","v":"Reviewed authorities for tasks and responsibilities related to enforcing laws, rules, and regulations regarding NG911 service and funds, based on statutes, executive orders, or regulations:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$107:$B$109,MATCH($C40,'Data Backend'!$A$107:$A$109,0)),\"\")","v":""}]
[55,{"$f":"'Data Backend'!A110","v":"A current dedicated, protected funding mechanism to address 911 operating costs and NG911 investment costs:"}]
[56,{"$f":"'Data Backend'!A113","v":"Promoted economies of scale by instituting cooperative purchasing agreements or offering master purchasing agreements for the acquisition of NG911 capabilities:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$114:$B$116,MATCH($C42,'Data Backend'!$A$114:$A$116,0)),\"\")","v":""}]
[57,{"$f":"'Data Backend'!A117","v":"Defined, by policy, the state's role in NG911 procurement and management:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$118:$B$120,MATCH($C43,'Data Backend'!$A$118:$A$120,0)),\"\")","v":""}]
["Regional Governance Structure Design & Framework",null,null,"Maturity State"]
[2,{"$f":"'Data Backend'!A124","v":"Established a name, authority, and purpose for a formalized 911 governance body that: a) solidifies the body’s legal standing and purpose; b) indicates its authority and any amendments to prior authorities; and c) confirms any concurrent jurisdictional bounds, if applicable:"},"Implemented and using",{"$f":"IFERROR(INDEX('Data Backend'!$B$125:$B$127,MATCH($C45,'Data Backend'!$A$125:$A$127,0)),\"\")","v":"Intermediate"}]
[3,{"$f":"'Data Backend'!A128","v":"Established the governance body’s oversight authority—including any rule-making authority—aligning activities to overarching strategies and plans, and maintaining fiduciary and fiscal compliance:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$129:$B$131,MATCH($C46,'Data Backend'!$A$129:$A$131,0)),\"\")","v":""}]
[4,{"$f":"'Data Backend'!A132","v":"Regulations, a charter, and/or bylaws that build upon the legal authority or set an agreed-upon authority, concurring with all jurisdictions where applicable:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$133:$B$135,MATCH($C47,'Data Backend'!$A$133:$A$135,0)),\"\")","v":""}]
[5,{"$f":"'Data Backend'!A136","v":"A reporting mechanism for the governance body to notify the public and all appropriate government agencies/bodies on accomplishments, issues, and future priorities to enhance 911/NG911:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$137:$B$139,MATCH($C48,'Data Backend'!$A$137:$A$139,0)),\"\")","v":""}]
[6,{"$f":"'Data Backend'!A140","v":"A mutually agreed-upon body that provides administrative support or another mechanism to share these responsibilities:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$141:$B$143,MATCH($C49,'Data Backend'!$A$141:$A$143,0)),\"\")","v":""}]
[7,{"$f":"'Data Backend'!A144","v":"A membership listing of 911 governance authorities’ representatives:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$145:$B$147,MATCH($C50,'Data Backend'!$A$145:$A$147,0)),\"\")","v":""}]
[8,{"$f":"'Data Backend'!A148","v":"Defined roles, responsibilities, and functions (e.g., voting, non-voting, and ex-officio) for members of the governance authority:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$149:$B$151,MATCH($C51,'Data Backend'!$A$149:$A$151,0)),\"\")","v":""}]
[9,{"$f":"'Data Backend'!A152","v":"A 911 Administrator (and appropriate support) to execute 911 services (e.g., operations, training, and performance standards):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$153:$B$155,MATCH($C52,'Data Backend'!$A$153:$A$155,0)),\"\")","v":""}]
[10,{"$f":"'Data Backend'!A156","v":"Encouragement of participation by relevant entities’ senior officials, if applicable:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$157:$B$160,MATCH($C53,'Data Backend'!$A$157:$A$160,0)),\"\")","v":""}]
[11,{"$f":"'Data Backend'!A161","v":"A governance authority that collaborates and engages with all applicable Statewide Interoperability Coordinators (SWICS):"}]
[12,{"$f":"'Data Backend'!A165","v":"A governance authority that collaborates and engages with all applicable 911 administrators:"}]
[13,{"$f":"'Data Backend'!A169","v":"A governance authority that collaborates and engages with broadband authorities:"}]
[14,{"$f":"'Data Backend'!A173","v":"A governance authority that collaborates and engages with all applicable neighboring jurisdictions:"}]
["Regional Governance Strategic Planning",null,null,"Maturity State"]
[15,{"$f":"'Data Backend'!A178","v":"Determined requirements for, process for, and extent of collaboration/cooperation among all relevant entities:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$179:$B$181,MATCH($C59,'Data Backend'!$A$179:$A$181,0)),\"\")","v":""}]
[16,{"$f":"'Data Backend'!A182","v":"Common policies and standards for the operation of ECC/PSAPs (e.g., SOPs, accountability, reporting, etc.):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$183:$B$185,MATCH($C60,'Data Backend'!$A$183:$A$185,0)),\"\")","v":""}]
[17,{"$f":"'Data Backend'!A186","v":"Developed 911/NG911 plan:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$187:$B$190,MATCH($C61,'Data Backend'!$A$187:$A$190,0)),\"\")","v":""}]
[18,{"$f":"'Data Backend'!A191","v":"Developed joint 911/NG911 MOU/As for multi-jurisdictional cooperation:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$192:$B$195,MATCH($C62,'Data Backend'!$A$192:$A$195,0)),\"\")","v":""}]
[19,{"$f":"'Data Backend'!A196","v":"Executed strategic planning for NG911 system requirements (e.g., NIEM, standards):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$197:$B$200,MATCH($C63,'Data Backend'!$A$197:$A$200,0)),\"\")","v":""}]
[20,{"$f":"'Data Backend'!A201","v":"Executed strategic planning for NG911 accountability and reporting:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$202:$B$205,MATCH($C64,'Data Backend'!$A$202:$A$205,0)),\"\")","v":""}]
[21,{"$f":"'Data Backend'!A206","v":"Executed strategic planning for system interoperability (e.g., GIS, CAD):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$207:$B$210,MATCH($C65,'Data Backend'!$A$207:$A$210,0)),\"\")","v":""}]
[22,{"$f":"'Data Backend'!A211","v":"Implemented strategic and tactical NG911 plans to be adopted by member jurisdictions:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$212:$B$214,MATCH($C66,'Data Backend'!$A$212:$A$214,0)),\"\")","v":""}]
["Regional Governance Coordination",null,null,"Maturity State"]
[23,{"$f":"'Data Backend'!A216","v":"Developed a regional NG911 entity (e.g., NG911 governance board, council of governments, NG911 subcommittee) with coordination, advisory, or support responsibility for participating ECC/PSAPs within the region:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$217:$B$220,MATCH($C68,'Data Backend'!$A$217:$A$220,0)),\"\")","v":""}]
[24,{"$f":"'Data Backend'!A221","v":"Elected/appointed a member to act as a liaison with other state, regional, and local governance bodies and interested parties:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$222:$B$225,MATCH($C69,'Data Backend'!$A$222:$A$225,0)),\"\")","v":""}]
[25,{"$f":"'Data Backend'!A226","v":"A liaison to provide guidance on NG911 policies, funding, and operation and technical developments:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$227:$B$229,MATCH($C70,'Data Backend'!$A$227:$A$229,0)),\"\")","v":""}]
["Regional Governance Funding & Resources",null,null,"Maturity State"]
[26,{"$f":"'Data Backend'!A231","v":"Enough resources (e.g. staff, funding) to carry out its NG911 mandate:"}]
[27,{"$f":"'Data Backend'!A234","v":"Promoted economies of scale by instituting cooperative purchasing agreements or offering master purchasing agreements for the acquisition of NG911 capabilities:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$235:$B$237,MATCH($C73,'Data Backend'!$A$235:$A$237,0)),\"\")","v":""}]
[28,{"$f":"'Data Backend'!A238","v":"Developed a regional resource allocation plan which may include funding-related investment decisions and potential funding methods:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$239:$B$242,MATCH($C74,'Data Backend'!$A$239:$A$242,0)),\"\")","v":""}]
["Local Governance Structure Design & Framework",null,null,"Maturity State"]
[58,{"$f":"'Data Backend'!A246","v":"Established a name, authority, and purpose for a formalized 911 governance body that: a) solidifies the body’s legal standing and purpose; b) indicates its authority and any amendments to prior authorities; and c) confirms any concurrent jurisdictional bounds, if applicable:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$247:$B$249,MATCH($C76,'Data Backend'!$A$247:$A$249,0)),\"\")","v":""}]
[59,{"$f":"'Data Backend'!A250","v":"Established the governance body’s oversight authority—including any rule-making authority—aligning activities to overarching strategies and plans, and maintaining fiduciary and fiscal compliance:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$251:$B$253,MATCH($C77,'Data Backend'!$A$251:$A$253,0)),\"\")","v":""}]
[60,{"$f":"'Data Backend'!A254","v":"Regulations, a charter, and/or bylaws that build upon the legal authority or set an agreed-upon authority, concurring with all jurisdictions where applicable:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$255:$B$257,MATCH($C78,'Data Backend'!$A$255:$A$257,0)),\"\")","v":""}]
[61,{"$f":"'Data Backend'!A258","v":"A reporting mechanism for the governance body to notify the public and all appropriate government agencies/bodies on accomplishments, issues, and future priorities to enhance 911/NG911:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$259:$B$261,MATCH($C79,'Data Backend'!$A$259:$A$261,0)),\"\")","v":""}]
[62,{"$f":"'Data Backend'!A262","v":"A membership listing of 911 governance authorities’ representatives:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$263:$B$265,MATCH($C80,'Data Backend'!$A$263:$A$265,0)),\"\")","v":""}]
[63,{"$f":"'Data Backend'!A266","v":"Defined roles, responsibilities, and functions (e.g., voting, non-voting, and ex-officio) for members of the governance authority:"},null,{"$f":"IFERROR(INDEX('Data Backend'!B267:B269,MATCH(C81,'Data Backend'!A267:A269,0)),\"\")","v":""}]
[64,{"$f":"'Data Backend'!A270","v":"A 911 Administrator (and appropriate support) to execute 911 services (e.g., operations, training, and performance standards):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$271:$B$273,MATCH($C82,'Data Backend'!$A$271:$A$273,0)),\"\")","v":""}]
[65,{"$f":"'Data Backend'!A274","v":"An ongoing mechanism to encourage collaboration among NG911 and other public safety governance bodies (e.g., broadband, other jurisdictions) to promote interoperability:"}]
[66,{"$f":"'Data Backend'!A278","v":"A governance authority that collaborates and engages with all applicable Statewide Interoperability Coordinators (SWICS):"}]
[67,{"$f":"'Data Backend'!A282","v":"A governance authority that collaborates and engages with all applicable 911 administrators:"}]
[68,{"$f":"'Data Backend'!A286","v":"A governance authority that collaborates and engages with broadband authorities:"}]
[69,{"$f":"'Data Backend'!A290","v":"A governance authority that collaborates and engages with all applicable neighboring jurisdictions:"}]
["Local Governance Strategic Planning",null,null,"Maturity State"]
[70,{"$f":"'Data Backend'!A295","v":"Executed strategic planning for NG911 system requirements (e.g., NIEM, standards):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$296:$B$299,MATCH($C89,'Data Backend'!$A$296:$A$299,0)),\"\")","v":""}]
[71,{"$f":"'Data Backend'!A300","v":"Executed strategic planning for NG911 accountability and reporting:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$301:$B$304,MATCH($C90,'Data Backend'!$A$301:$A$304,0)),\"\")","v":""}]
[72,{"$f":"'Data Backend'!A305","v":"Executed strategic planning for system interoperability (e.g., GIS, CAD):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$306:$B$309,MATCH($C91,'Data Backend'!$A$306:$A$309,0)),\"\")","v":""}]
[73,{"$f":"'Data Backend'!A310","v":"Developed a 911/NG911 plan:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$311:$B$314,MATCH($C92,'Data Backend'!$A$311:$A$314,0)),\"\")","v":""}]
[74,{"$f":"'Data Backend'!A315","v":"Developed joint 911/NG911 MOU/As for multi-jurisdictional cooperation:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$316:$B$319,MATCH($C93,'Data Backend'!$A$316:$A$319,0)),\"\")","v":""}]
[75,{"$f":"'Data Backend'!A320","v":"Aligned the governance body with the Statewide Communications Interoperability Plan (SCIP):"}]
[76,{"$f":"'Data Backend'!A323","v":"Aligned the governance body with available NG911 initiatives and strategic plans:"}]
[77,{"$f":"'Data Backend'!A326","v":"Updated the governance body periodically to reflect changes to NG911 emergency communications goals and objectives:"}]
[78,{"$f":"'Data Backend'!A329","v":"Developed reporting procedures on 911/NG911 progress to appropriate authorities:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$330:$B$332,MATCH($C97,'Data Backend'!$A$330:$A$332,0)),\"\")","v":""}]
["Local Governance Coordination",null,null,"Maturity State"]
[79,{"$f":"'Data Backend'!A334","v":"Coordinated with other ECC/PSAPs to address challenges associated with the evolving emergency communications landscape:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$335:$B$337,MATCH($C99,'Data Backend'!$A$335:$A$337,0)),\"\")","v":""}]
[80,{"$f":"'Data Backend'!A338","v":"A liaison to provide guidance on NG911 policies, funding, and operation and technical developments:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$339:$B$341,MATCH($C100,'Data Backend'!$A$339:$A$341,0)),\"\")","v":""}]
["Local Governance Funding & Resources",null,null,"Maturity State"]
[81,{"$f":"'Data Backend'!A343","v":"Enough resources (e.g. staff, funding) to carry out its NG911 mandate:"}]
[82,{"$f":"'Data Backend'!A346","v":"Promoted economies of scale by instituting cooperative purchasing agreements or offering master purchasing agreements for the acquisition of NG911 capabilities:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$347:$B$349,MATCH($C103,'Data Backend'!$A$347:$A$349,0)),\"\")","v":""}]
[null,"Governance Maturity State:",{"$f":"IF(OR(AND(C3=\"State: All state, commonwealth, and territorial organizations\",COUNTIF(D12:D43,\"Legacy\")),AND(C3=\"Regional: All intrastate or interstate organizations that are multijurisdictional\",COUNTIF(D45:D74,\"Legacy\")),AND(C3=\"Local: All remaining city, town, county, village, parish, tribal, and municipal organizations\",COUNTIF(D76:D103,\"Legacy\"))),\"Legacy\",IF(OR(AND(C3=\"State: All state, commonwealth, and territorial organizations\",COUNTIF(D12:D43,\"Foundational\")),AND(C3=\"Regional: All intrastate or interstate organizations that are multijurisdictional\",COUNTIF(D45:D74,\"Foundational\")),AND(C3=\"Local: All remaining city, town, county, village, parish, tribal, and municipal organizations\",COUNTIF(D76:D103,\"Foundational\"))),\"Foundational\",IF(OR(AND(C3=\"State\",COUNTIF(D12:D43,\"Transitional\")),AND(C3=\"Regional: All intrastate or interstate organizations that are multijurisdictional\",COUNTIF(D45:D74,\"Transitional\")),AND(C3=\"Local: All remaining city, town, county, village, parish, tribal, and municipal organizations\",COUNTIF(D76:D103,\"Transitional\"))),\"Transitional\",IF(OR(AND(C3=\"State: All state, commonwealth, and territorial organizations\",COUNTIF(D12:D43,\"Intermediate\")),AND(C3=\"Regional: All intrastate or interstate organizations that are multijurisdictional\",COUNTIF(D45:D74,\"Intermediate\")),AND(C3=\"Local: All remaining city, town, county, village, parish, tribal, and municipal organizations\",COUNTIF(D76:D103,\"Intermediate\"))),\"Intermediate\",\"#N/A\"))))","v":"#N/A"}]
[]
["Architecture"]
[null,null,"Dropdown Options"]
["Routing & Location ",null,null,"Maturity State"]
[83,{"$f":"'Data Backend'!A352","v":"Accurately, factually, and consistently characterize the 911 call routing currently in use and planning/funding sought:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$353:$B$356,MATCH($C109,'Data Backend'!$A$353:$A$356,0)),\"\")","v":""}]
[84,{"$f":"'Data Backend'!A357","v":"Characterize the Automatic Location Information (ALI)/Location Object use in database management systems (DBMS):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$358:$B$361,MATCH($C110,'Data Backend'!$A$358:$A$361,0)),\"\")","v":""}]
[85,{"$f":"'Data Backend'!A362","v":"Specify if a LIS or its equivalent is implemented with each originating service provider (OSP) for every ECC/PSAP within your jurisdiction:"}]
["Geographic Information System (GIS) Data ",null,null,"Maturity State"]
[86,{"$f":"'Data Backend'!A366","v":"Characterize to what extent a NG911 dataset has been created:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$367:$B$370,MATCH($C113,'Data Backend'!$A$367:$A$370,0)),\"\")","v":""}]
[87,{"$f":"'Data Backend'!A371","v":"Specify the usage of Emergency Call Routing Function (ECRF) in GIS data formatting:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$372:$B$375,MATCH($C114,'Data Backend'!$A$372:$A$375,0)),\"\")","v":""}]
[88,{"$f":"'Data Backend'!A376","v":"Specify the usage of Policy Routing Function (PRF):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$377:$B$380,MATCH($C115,'Data Backend'!$A$377:$A$380,0)),\"\")","v":""}]
[89,{"$f":"'Data Backend'!A381","v":"Indicate if the data is formatted for Location Verification Function (LVF) use:"}]
["Next Generation Core Service (NGCS) Elements",null,null,"Maturity State"]
[90,{"$f":"'Data Backend'!A385","v":"Characterize the implementation of Legacy Selective Router Gateway (LSRG):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$386:$B$389,MATCH($C118,'Data Backend'!$A$386:$A$389,0)),\"\")","v":""}]
[91,{"$f":"'Data Backend'!A390","v":"Specify if a LVF has been provided:"}]
[92,{"$f":"'Data Backend'!A393","v":"Characterize the implementation of ESRP:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$394:$B$397,MATCH($C120,'Data Backend'!$A$394:$A$397,0)),\"\")","v":""}]
[93,{"$f":"'Data Backend'!A398","v":"Characterize the implementation of Emergency Call Routing Function (ECRF):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$399:$B$401,MATCH($C121,'Data Backend'!$A$399:$A$401,0)),\"\")","v":""}]
[94,{"$f":"'Data Backend'!A402","v":"Characterize the implementation of a Legacy Network Gateway (LNG):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$403:$B$406,MATCH($C122,'Data Backend'!$A$403:$A$406,0)),\"\")","v":""}]
[95,{"$f":"'Data Backend'!A407","v":"Characterize the implementation of a Legacy ECC/PSAP Gateway (LPG):"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$408:$B$410,MATCH($C123,'Data Backend'!$A$408:$A$410,0)),\"\")","v":""}]
[96,{"$f":"'Data Backend'!A411","v":"Characterize the implementation of Border Control Function (BCF) capabilities:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$412:$B$414,MATCH($C124,'Data Backend'!$A$412:$A$414,0)),\"\")","v":""}]
[97,{"$f":"'Data Backend'!A415","v":"Specify if logging capabilities have been fully implemented and maintained:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$416:$B$417,MATCH($C125,'Data Backend'!$A$416:$A$417,0)),\"\")","v":""}]
["Network (OSE & ESInets)",null,null,"Maturity State"]
[98,{"$f":"'Data Backend'!A423","v":"Characterize the implementation of an Ingress network:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$424:$B$427,MATCH($C127,'Data Backend'!$A$424:$A$427,0)),\"\")","v":""}]
[99,{"$f":"'Data Backend'!A428","v":"Characterize the Egress process of your ECC/PSAP:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$429:$B$431,MATCH($C128,'Data Backend'!$A$429:$A$431,0)),\"\")","v":""}]
[100,{"$f":"'Data Backend'!A432","v":"Specify whether traditional ALI data circuits are used:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$433:$B$434,MATCH($C129,'Data Backend'!$A$433:$A$434,0)),\"\")","v":""}]
[101,{"$f":"'Data Backend'!A435","v":"Specify if multiple NG core services, including call hand-offs and transfers, are interconnected with neighboring ESInets:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$436:$B$437,MATCH($C130,'Data Backend'!$A$436:$A$437,0)),\"\")","v":""}]
["ECC/PSAP Call Handling System & Applications",null,null,"Maturity State"]
[102,{"$f":"'Data Backend'!A439","v":"Characterize the call handling system in use:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$440:$B$443,MATCH($C132,'Data Backend'!$A$440:$A$443,0)),\"\")","v":""}]
[103,{"$f":"'Data Backend'!A444","v":"Specify whether mapping occurs:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$445:$B$446,MATCH($C133,'Data Backend'!$A$445:$A$446,0)),\"\")","v":""}]
[104,{"$f":"'Data Backend'!A447","v":"Specify if Text-to-911 (Short Message Service) has been implemented:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$448:$B$449,MATCH($C134,'Data Backend'!$A$448:$A$449,0)),\"\")","v":""}]
[105,{"$f":"'Data Backend'!A450","v":"Specify whether the system routes multimedia information:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$451:$B$452,MATCH($C135,'Data Backend'!$A$451:$A$452,0)),\"\")","v":""}]
[106,{"$f":"'Data Backend'!A453","v":"Specify whether logging and recording of NG911 multimedia data has been implemented:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$454:$B$455,MATCH($C136,'Data Backend'!$A$454:$A$455,0)),\"\")","v":""}]
["Operational Planning",null,null,"Maturity State"]
[107,{"$f":"'Data Backend'!A457","v":"Indicate whether the 911 Plan has been updated:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$458:$B$460,MATCH($C138,'Data Backend'!$A$458:$A$460,0)),\"\")","v":""}]
[108,{"$f":"'Data Backend'!A461","v":"Characterize current NG911 operational planning and procedures:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$462:$B$464,MATCH($C139,'Data Backend'!$A$462:$A$464,0)),\"\")","v":""}]
[109,{"$f":"'Data Backend'!A465","v":"Characterize current assessments of staffing needs based on NG911 transition:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$466:$B$469,MATCH($C140,'Data Backend'!$A$466:$A$469,0)),\"\")","v":""}]
[110,{"$f":"'Data Backend'!A470","v":"Characterize the process of training staff based on NG911 transition:"},null,{"$f":"IFERROR(INDEX('Data Backend'!$B$471:$B$473,MATCH($C141,'Data Backend'!$A$471:$A$473,0)),\"\")","v":""}]
["Optional Interfaces",null,null,"Maturity State"]
[111,{"$f":"'Data Backend'!A475","v":"Specify whether a computer-aided dispatch (CAD) is in use:"}]
[112,{"$f":"'Data Backend'!A478","v":"Specify whether a broadband field network is in use:"}]
[null,"Architecture Maturity State:",{"$f":"IF(COUNTIF(D109:D144,\"Legacy\")>0,\"Legacy\",IF(COUNTIF(D109:D144,\"Foundational\")>0,\"Foundational\",IF(COUNTIF(D109:D144,\"Transitional\")>0,\"Transitional\",IF(COUNTIF(D109:D144,\"Intermediate\")>0,\"Intermediate\",\"#N/A\"))))","v":"#N/A"}]
[]
["Security"]
[null,null,"Dropdown Option"]
["INDICATE IF YOUR ORGANIZATION HAS:"]
["Security Identification & Discovery",null,null,"Maturity State"]
[113,{"$f":"'Data Backend'!A484","v":"Inventoried all existing systems and applications:"},null,{"$f":"IF(C151=\"\",\"N/A\",IF(C151=\"Yes\",1,0))","v":"N/A"}]
[114,{"$f":"'Data Backend'!A485","v":"Classified all assets:"},null,{"$f":"IF(C152=\"\",\"N/A\",IF(C152=\"Yes\",1,0))","v":"N/A"}]
[115,{"$f":"'Data Backend'!A486","v":"Identified owners of communications infrastructure assets:"},null,{"$f":"IF(C153=\"\",\"N/A\",IF(C153=\"Yes\",1,0))","v":"N/A"}]
[116,{"$f":"'Data Backend'!A487","v":"Identified applicable laws, regulations, and requirements:"},null,{"$f":"IF(C154=\"\",\"N/A\",IF(C154=\"Yes\",1,0))","v":"N/A"}]
[117,{"$f":"'Data Backend'!A488","v":"Determined existing vulnerabilities:"},null,{"$f":"IF(C155=\"\",\"N/A\",IF(C155=\"Yes\",1,0))","v":"N/A"}]
["Security Assessment & Prioritization",null,null,"Maturity State"]
[118,{"$f":"'Data Backend'!A490","v":"Conducted a risk assessment:"},null,{"$f":"IF(C157=\"\",\"N/A\",IF(C157=\"Yes\",1,0))","v":"N/A"}]
[119,{"$f":"'Data Backend'!A491","v":"Established security controls:"},null,{"$f":"IF(C158=\"\",\"N/A\",IF(C158=\"Yes\",1,0))","v":"N/A"}]
[120,{"$f":"'Data Backend'!A492","v":"Developed remediation plans:"},null,{"$f":"IF(C159=\"\",\"N/A\",IF(C159=\"Yes\",1,0))","v":"N/A"}]
[121,{"$f":"'Data Backend'!A493","v":"Prioritized the execution of remediation plans, mitigations, and improvements:"},null,{"$f":"IF(C160=\"\",\"N/A\",IF(C160=\"Yes\",1,0))","v":"N/A"}]
["Security Implementation & Operation",null,null,"Maturity State"]
[122,{"$f":"'Data Backend'!A495","v":"Documented necessary policies, procedures, and controls for effective security:"},null,{"$f":"IF(C162=\"\",\"N/A\",IF(C162=\"Yes\",1,0))","v":"N/A"}]
[123,{"$f":"'Data Backend'!A496","v":"Administered access control:"},null,"N/A"]
[124,{"$f":"'Data Backend'!A497","v":"Provided security awareness training and techniques:"},null,"N/A"]
[125,{"$f":"'Data Backend'!A498","v":"Implemented auditing and accountability:"},null,"N/A"]
[126,{"$f":"'Data Backend'!A499","v":"Established a baseline configuration and configuration management controls:"},null,"N/A"]
[127,{"$f":"'Data Backend'!A500","v":"Implemented contingency planning for continuity of operations:"},null,"N/A"]
[128,{"$f":"'Data Backend'!A501","v":"Implemented identification and authentication controls:"},null,"N/A"]
[129,{"$f":"'Data Backend'!A502","v":"Coordinated activities for security incident response:"},null,"N/A"]
[130,{"$f":"'Data Backend'!A503","v":"Evaluated maintenance impacts on security controls:"},null,"N/A"]
[131,{"$f":"'Data Backend'!A504","v":"Implemented media protection controls:"},null,"N/A"]
[132,{"$f":"'Data Backend'!A505","v":"Implemented personnel security controls:"},null,"N/A"]
[133,{"$f":"'Data Backend'!A506","v":"Implemented physical and environmental protection controls:"},null,"N/A"]
[134,{"$f":"'Data Backend'!A507","v":"Developed a security plan:"},null,"N/A"]
[135,{"$f":"'Data Backend'!A508","v":"Implemented information security program management:"},null,"N/A"]
[136,{"$f":"'Data Backend'!A509","v":"Established a risk management plan:"},null,"N/A"]
[137,{"$f":"'Data Backend'!A510","v":"Achieved authorization for security controls:"},null,"N/A"]
[138,{"$f":"'Data Backend'!A511","v":"Planned for system and services acquisition:"},null,"N/A"]
[139,{"$f":"'Data Backend'!A512","v":"Accounted for system and communications protection controls:"},null,"N/A"]
[140,{"$f":"'Data Backend'!A513","v":"Provided system and information integrity controls:"},null,"N/A"]
[141,{"$f":"'Data Backend'!A514","v":"Executed remediation plans:"},null,"N/A"]
[142,{"$f":"'Data Backend'!A515","v":"Implemented controls for conformance for known laws, regulations, and contractual obligations:"},null,"N/A"]
["Security Monitoring & Analysis",null,null,"Maturity State"]
[143,{"$f":"'Data Backend'!A517","v":"Developed a baseline of the current environment:"},null,{"$f":"IF(C184=\"\",\"N/A\",IF(C184=\"Yes\",1,0))","v":"N/A"}]
[144,{"$f":"'Data Backend'!A518","v":"Implemented security event logging:"},null,"N/A"]
[145,{"$f":"'Data Backend'!A519","v":"Implemented security metrics capture:"},null,"N/A"]
[146,{"$f":"'Data Backend'!A520","v":"Implemented compliance evaluation:"},null,"N/A"]
[147,{"$f":"'Data Backend'!A521","v":"Evaluated control effectiveness:"},null,"N/A"]
["Security Testing & Evaluation",null,null,"Maturity State"]
[148,{"$f":"'Data Backend'!A523","v":"Performed security audits:"},null,{"$f":"IF(C190=\"\",\"N/A\",IF(C190=\"Yes\",1,0))","v":"N/A"}]
[149,{"$f":"'Data Backend'!A524","v":"Updated contingency plans with respect to security controls:"},null,"N/A"]
["Security Improvement & Evolution",null,null,"Maturity State"]
[150,{"$f":"'Data Backend'!A526","v":"Developed and implemented policies for regular security reassessment:"},null,{"$f":"IF(C193=\"\",\"N/A\",IF(C193=\"Yes\",1,0))","v":"N/A"}]
[151,{"$f":"'Data Backend'!A527","v":"Developed and implemented policies for re-evaluation of the security management program:"},null,"N/A"]
[152,{"$f":"'Data Backend'!A528","v":"Developed and implemented policies for evolving security training and awareness:"},null,"N/A"]
[153,{"$f":"'Data Backend'!A529","v":"Developed and implemented policies for short- and long-term capacity planning:"},null,"N/A"]
[null,"Security Maturity State:",{"$f":"IF(AND(SUM(D151:D182)=30,SUM(D184:D196)>0),\"Intermediate\",IF(SUM(D151:D182)=30,\"Transitional\",IF(AND(SUM(D151:D160)=9,SUM(D162:D182)<21),\"Foundational\",IF(AND(COUNTIF(D151:D196,\"N/A\")=0,SUM(D151:D160)>=0),\"Legacy\",\"#N/A\"))))","v":"#N/A"}]

{"sheet":"Element Descriptions","index":2,"n_rows":52,"n_cols":1,"rows_kept":52,"cut":false,"hidden":false,"merged":[]}
["NG911 Self-Assessment Tool"]
["Scorecard Explanation"]
["The NG911 Self-Assessment Tool provides 911 authority stakeholders an understanding of essential elements within each NG911 implementation maturity state (state, regional, and local). With this understanding 911 authority stakeholders can better plan for the technical, operational, and financial needs associated with their NG911 transition.\n\nThe NG911 Self-Assessment Tool is broken down into the following areas of interest:\nGovernance\n  a) Structure Design & Framework     b) Strategic Planning     c) Coordination     d) Funding & Resources\nArchitecture\n  a) Routing & Location     b) Geographic Information Systems Data     c) Next Generation Core Service Elements     d) Network (Originating Service Environments & ESInets)     e) ECC/PSAP Call Handling System and Applications   f) Operational Planning    g) Optional Interfaces\nSecurity\n  a) Identification & Discovery     b) Assessment & Prioritization     c) Implementation & Operation     d) Monitoring & Evaluation     e) Testing & Analysis     f) Improvement & Evolution\n\nEach “area of interest” is broken down by a set of essential elements. The self-assessment elements identify either functional capabilities, architecture implementation, or operational capabilities. Functional and operational capabilities are either defined by legacy 911 capabilities or those capabilities defined by the NENA i3 standard. Architecture implementation is defined by either legacy compatibility or alignment to the NENA i3 standard. Section 4 provides important additional detail on the “areas of interest” under General Considerations, and as it relates to Operational Impacts of NG911.\n\nFor all elements, \"planning\" refers to the preparation for transitioning from Legacy 911 to NG911."]
[]
["Governance"]
["Governance addresses the structured oversight of the 911 authorities and identifies whether there is a governing body with documented and tracked planning and implementation efforts. Coordination indicates whether all participating entities within the jurisdictional scope have agreed upon cooperation and go-forward strategies and plans. Funding and Resources indicate that the funding and resources necessary to execute the NG911 plan have been identified or a strategy is in place to secure those funds and resources at necessary points during the plan execution. Governance structure is ongoing, providing the coordination and administration of the entire NG911 service system after implementation."]
[]
["Architecture"]
["Routing & Location"]
["Routing and location defines the systematic approach that is used to determine 911 call routing and the supporting data functions. Legacy 911 calls are processed by relating the calling telephone number to an Emergency Services Number (ESN) that then defines the primary and secondary ECC/PSAPs. NG911 utilizes geospatial routing by using the caller’s location information and a set of ECC/PSAP jurisdictional polygons to determine the primary ECC/PSAP. A “pure” NG911 implementation assumes OSPs have changed the means by which they deliver 911 calls, but it is not realistic or expected that Originating Service Providers will change together or even all complete their changes any time soon. Therefore, the model is complicated by mechanisms to “transition” from legacy methods to NG911 methods. The legacy ALI DBMS provides location information based on the caller’s telephone number and its equivalent is required until all OSPs deliver location information with their 911 call setup messages or provide LIS capabilities."]
[]
["GIS Data"]
["GIS Data is a fundamental element of NG911 call routing but is not utilized for Legacy 911 call routing. These selection items define steps to plan, process, and utilize GIS data for NG911. Selection items are included that represent the NENA i3 functional elements that receive and utilize GIS data to complete call routing functions. The exchange of jurisdictional boundaries indicates an automated mechanism where an ESInet ECRF (or Forest Guide function) automatically keeps a neighboring ESInet ECRF (or Forest Guide function) updated with its jurisdictional polygons to allow for 911 call hand-offs and call transfers. GIS data is also utilized with NG911 for the validation (LVF) function and to support mapping services for the ECC/PSAPs."]
[]
["NG911 Core Service Elements"]
["The central Core Services functions provide the logical processing interactions between the delivery of calls and data from the OSE, additional data, and delivery to ECC/PSAPs, and provide the features to support management of how the NG911 service accomplishes this under normal and abnormal conditions. NG Core Service Element capabilities are an itemized list of the functional capabilities defined by the NENA i3 architecture."]
[]
["Network (OSE and ESInet)"]
["The network area capabilities represent the various technology mechanisms for connecting external entities to either a legacy selective router or functions within an ESInet for the purposes of processing 911 calls. Legacy call circuit mechanisms are primarily TDM based technology (e.g., SS7, CAMA) and NG911 moves to IP-based technology with application specific protocols such as SIP and RTP. In some cases, IP technology can be deployed as a replacement for a legacy TDM technology before completely embracing the NENA i3 defined functional interface model, such as an OSP using IP technology call delivery to an ESInet IP Selective Router without including a location object representing the caller’s location. E2 Location uses legacy wireless capabilities to retrieve location information and may be required until all OSPs that allow location update transactions deliver callers' location information at call setup time. ESInet to ESInet connections may occur as neighboring jurisdictions implement ESInets and exchange 911 calls and any multimedia or other data in an interoperable fashion."]
[]
["ECC/PSAP Call Handling System and Applications"]
["Legacy Call Handling Systems (CHS) are defined by their use of Centralized Automatic Message Accounting (CAMA) trunk interfaces and legacy ALI interfaces. At some point, as PSAPs implement NG911, they will upgrade to call handling equipment that uses an IP-based system and optionally may include replacing the legacy CAMA TDM circuits with the ATIS-defined IP- based transitional Request for Assistance Interface (RFIA) protocol. The Call Handling Functional Element is concerned with the details of managing calls and all related communication from the caller. It includes the interfaces, devices, and applications used by call managers. It receives and may display the content of multimedia calls such as text and video to the ECC/PSAP."]
[]
["Operational Planning"]
["Operational planning addresses aspects of execution, oversight, plan management, and efforts to support on-going evolution with the planning of NGCS, ESInet, and ECC/PSAP operations."]
[]
["Optional Interfaces"]
["\"Optional Interfaces\" addresses services and interfaces that interconnect with the ESInet but apply beyond NG Core Services primary functions, although these functions may otherwise appear necessary and prudent. Any and all optional interfaces must comply with all applicable commonly accepted standards and shall not interfere with or impact the function or security of the NG911 systems."]
[]
["Security"]
["Security includes protective capabilities, operations, and best practices expected at the ESInet, the NGCS functional elements, ECC/PSAP, and all external facing interfaces. Based on the TFOPA Working Group 1 Final Report Cybersecurity Lifecycle Roadmap and the Working Group 2 Next Generation 911 Readiness Scorecard, for ECC/PSAPs to be considered at a Foundational maturity state, they must answer all questions in the \"Security Identification & Discovery\" and \"Security Assessment & Priority\" with \"Yes.\" Similarly, to be considered at a Transitional maturity state, ECC/PSAPs must meet Foundational state requirements and choose \"Yes\" for all of the \"Security Implementation & Operation\" questions. To be considered at the Intermediate state, ECC/PSAPs must meet the Transitional state requirements and should be doing some, if not all, of the actions covered in the \"Security Monitoring & Analysis\" section."]
[]
["Security Identification & Discovery"]
["The primary foundation of effective cybersecurity is the identification of the communications infrastructure assets: hardware, software, product tools, and systems within the organization. This phase is where all security lifecycles should start. No other security work can take place until an organization has taken a formal inventory of their environment. It is impossible to secure what is not known to exist. This allows the organization to begin classifying their systems in order to prioritize future resolution and identifying those responsible for resolving security issues as they are identified."]
[]
["Security Assessment & Prioritization"]
["The management of organizational risk is a key element in the organization’s information security program and provides an effective framework for selecting the security controls necessary to protect individuals, operations, and assets of the organization. This phase establishes the security controls for the information system based on its categorization, assessment of risk, and local conditions. Although an organization may not have completed classifying their assets or identifying owners of the assets, they may begin probing their systems for vulnerabilities. Discovery of vulnerabilities is a natural part of conducting an overall risk assessment. As vulnerabilities are discovered they should be fed into a larger risk assessment process to evaluate risks to the organization. At this point disaster recovery and business continuity processes should start being developed and tested if they do not exist. Note that the lack of a good and functioning business continuity testing plan should be considered a significant risk to an organization. As vulnerabilities are discovered and fed into a general risk assessment, gaps and findings will be identified. Organizations should begin identifying security controls that close these gaps in preparation for Security Implementation and Operation. Additionally, organizations should have completed their inventory process and start recognizing what the normal operational flow of their environments should be. This allows the organization to begin to baseline their current environment."]
[]
["Security Implementation & Operation"]
["This stage is focused on the application of identified and applicable security controls adhering to all relevant laws, regulations, and customer requirements. It involves the people, processes, and technology for the secure operation of information systems in accordance with the acceptable level of organizational risk. Organizations should now have completed their initial risk assessment and identified a set of security controls intended to address vulnerabilities and identified risks. This allows the organization to develop a formal and documented remediation plan while they continue to baseline their environment. With a documented set of remediation plans the organization should now be in a position to prioritize how the plan is executed. Key considerations to take into account may be based on information gathered in previous phases. For example, what are the most at risk systems, what systems have the most critical information based on classification, what controls are the easiest to implement, etc. Organizations should also begin documenting and enacting policies and processes that will aid them in reducing the likelihood of recurring security issues. For example, if patching was identified as a security control that was needed for an organization, what policy or practice can be put into place to help keep lack of patching from becoming a problem in the future? It is also important that organizations begin collecting log information from critical and sensitive parts of their environment. This will set the groundwork for the identification of security related events and the measurement of security effectiveness."]
[]
["Security Monitoring & Analysis"]
["The intention of this phase is to examine and analyze the operational environment and to report on the security state of the organization. The purpose of the assessment is to determine if controls are implemented adequately and operating appropriately and as intended with the desired outcome."]
[]
["Security Testing & Evaluation"]
["Auditing the performance and effectiveness of security controls, as well as instituting supportive policy, plans, and procedures is necessary."]
[]
["Security Improvement & Evolution"]
["Based on output from previous phases, the organization can make informed decisions on the suitability of implementing new controls or changing existing controls to continually improve the security posture. Identification of areas of improvement and best practices is essential. Focus is given to security training and awareness, allowing the organization to continue to evolve."]
[]
["NG911 Self Assessment Matrix"]
["Explanation\nThe Next Generation 911 (NG911) Self-Assessment Matrix is defined in the Federal Communication Commission Task Force on Optimal Safety Answering Point Architecture (TFOPA) Working Group 2 Phase II Supplement Report: NG911 Readiness Scorecard. The NG911 Self-Assessment Matrix is to be completed by a ECC/PSAP to help define their current 911 implementation state and communicate consistently the “readiness” of their system.\n\nThe SAFECOM/NCSWIC NG911 Working Group is piloting the use of the Self-Assessment and has created this editable version of the Self-Assessment Matrix, based on the matrix available in the TFOPA report. Completed self-assessments should serve as a ECC/PSAP’s guide to understanding their status per the NG911 Readiness Scorecard (as defined by TFOPA) and will not be used to form opinions or conclusions about capability or merit.\n\nUsed in conjunction with the legacy NG911 Readiness Scorecard, the NG911 Self-Assessment Matrix enables a 911 Authority Stakeholder (or designee) to determine its current status within the NG911 implementation continuum and assist a 911 Authority in identifying the steps necessary to reach the next NG911 implementation maturity state. A 911 Authority completes the Self-Assessment Matrix by filling in the current implementation status of specific functions, components, policies, and processes and comparing their status against the NG911 Readiness Scorecard Maturity Continuum to identify in which NG911 implementation state they fit."]

{"sheet":" Legacy NG911 Scorecard","index":3,"n_rows":70,"n_cols":14,"rows_kept":70,"cut":false,"hidden":true,"merged":[[0,0,0,10],[1,1,1,6],[1,8,1,10]]}
["Next Generation 9-1-1 Self-Assessment ScoreCard "]
[null,"NG911 Implementation Maturity State",null,null,null,null,null,null,"NG911 Maturity State Self Assessment"]
["Governance ","Legacy","Foundational","Transitional","Intermediate","i3 End State - Jurisdictional","i3 End State - National",null,"Status","Maintained/Provided by","Notes"]
["Governance Structure Design & Framework","Optional","X","X","X","X","X"]
["Strategic Planning","Optional","Optional","X","X","X","X"]
["Coordination","Optional","Optional","X","X","X","X"]
["Funding & Resources","Optional","X","X","X","X","X"]
["Routing & Location ",null,null,null,null,null,null,null,null,null,null,null,null,"Status Levels"]
["Selective (ESN) Routing","X","X",null,null,null,null,null,null,null,null,null,null,"Planning"]
["IP Selective (ESN) Routing",null,null,"X",null,null,null,null,null,null,null,null,null,"Implementation"]
["Geospatial Routing (utilizing best available location)",null,null,null,"X","X","X",null,null,null,null,null,null,"Complete"]
["ALI DBMS","X","X","X","X"]
["LIS",null,null,null,"Optional","X","X"]
["National Forest Guide contains Jurisdictional ESInet Authoritative Boundary",null,null,null,null,"Optional","X"]
["If applicable, Hierarchical Forest Guides Populated",null,null,null,null,"Optional","X"]
["GIS Data "]
["NG911 Dataset Creation Project Planned",null,"X"]
["NG911 Dataset Creation Project in-Progress",null,"X","Optional"]
["NG911 Dataset Complete",null,null,null,"X","X","X"]
["Data formatted for Location Verification Function (LVF)",null,null,"Optional","Optional","X","X"]
["Data formatted for Emergency Call Routing Function (ECRF)",null,null,"Optional","X","X","X"]
["Data formatted for Policy Routing Function (PRF)",null,null,"Optional","X","X","X"]
["Jurisdictional Boundaries exported to neighboring ESInets",null,null,null,null,"Optional","X"]
["NG Core Service Elements "]
["Legacy Selective Router Gateway (LSRG)",null,null,"Optional","X","Optional","Optional"]
["Location Verification Function (LVF)",null,null,"Optional","Optional","X","X"]
["Emergency Services Routing Proxy (ESRP)",null,null,"Optional","X","X","X"]
["Emergency Call Routing Function (ECRF)",null,null,"Optional","X","X","X"]
["Legacy Network Gateway (LNG)",null,null,"Optional","X","Optional","Optional"]
["Legacy PSAP Gateway (LPG)",null,null,"Optional","X","Optional","Optional"]
["Border Control Function (BCF)",null,null,"Optional","X","X","X"]
["Logging ",null,null,null,"X","X","X"]
["Network "]
["OSP/OSE *",null,null,"X","X","X","X"]
["Ingress Network - Non-IP","X","X","X","X"]
["Egress Network - Non-IP","X","X"]
["Traditional ALI Data Circuits","X","X","X"]
["Ingress - IP  (ESInet)",null,null,"Optional","X","X","X"]
["Egress - IP (ESInet)",null,null,"X","X","X","X"]
["Interconnects beyond ESInet boundary *",null,null,null,"X","X","X"]
["E2 Circuits","X","X","X","X"]
["Neighboring ESInet Interconnection for Call Hand-offs and Transfers",null,null,null,"Optional","Optional","X"]
["PSAP Call Handling System & Applications"]
["Legacy Call Handling System ","X","X"]
["IP based Call Handling System",null,null,"X"]
["i3 PSAP (Terminating ESRP) Multimedia Call Handling System",null,null,"Optional","X","X","X"]
["Mapping",null,null,"X","X","X","X"]
["Text-to-9-1-1 (SMS)",null,null,"X","X","X","X"]
["Multimedia",null,null,null,"X","X","X"]
["Logging & Recording",null,null,null,"X","X","X"]
["Security"]
["Identification/Discovery",null,"X","X","X","X","X"]
["Assess/Prioritize",null,"X","X","X","X","X"]
["Implement/Operate",null,null,"X","X","X","X"]
["Monitor/Analyze",null,null,"Optional","X","X","X"]
["Operations"]
["NG911 Operational Planning in Progress",null,"X"]
["Amount of Staff Needed",null,"X"]
["NG911 Operational Procedures Developed ",null,null,"Optional","X","X","X"]
["NG911 Operation Procedures Implemented",null,null,"Optional","X","X","X"]
["Training Staff",null,"Optional","X","X","X","X"]
["9-1-1 Plan Update","Optional","X"]
["Optional Interfaces"]
["CAD",null,null,"Optional","Optional","Optional","Optional"]
["Broadband Field Network",null,null,"Optional","Optional","Optional","Optional"]
["Additional Data ",null,null,null,"Optional","Optional","Optional"]
["Personal Information Data",null,null,null,"Optional","Optional","Optional"]
[]
["NENA Glossary"]
["https://c.ymcdn.com/sites/www.nena.org/resource/resmgr/standards/NENA-ADM-000.21-2017_FINAL_2.pdf"]

{"sheet":"Acronyms","index":4,"n_rows":46,"n_cols":2,"rows_kept":46,"cut":false,"hidden":false,"merged":[]}
["Acronym","Term"]
["ALI","Automatic Location Information"]
["BCF","Border Control Function"]
["CAD","Computer-Aided Dispatch"]
["CAMA","Centralized Automatic Message Accounting"]
["CHS","Call Handling System"]
["DBMS","Database Management System"]
["DMZ","Demilitarized Zone"]
["ECC","Emergency Communications Center"]
["ECRF","Emergency Call Routing Function"]
["ESInet","Emergency Services Internet Protocol Network"]
["ESN","Emergency Services Number"]
["ESRP","Emergency Services Routing Proxy"]
["FCC","Federal Communications Commission"]
["FirstNet","First Responder Network Authority"]
["GIS","Geographic Information Systems"]
["LIS","Location Information Server"]
["LMR","Land Mobile Radio"]
["LNG","Legacy Network Gateway"]
["LPG","Legacy Public Safety Answering Point Gateway"]
["LSRG","Legacy Selective Router Gateway"]
["LTE","Long-Term Evolution"]
["LVF","Location Verification Function"]
["MOA","Memorandum of Agreement"]
["MOU","Memorandum of Understanding"]
["NENA","National Emergency Number Association"]
["NGCS","Next Generation Core Service"]
["NG911","Next Generation 911"]
["NIEM","National Information Exchange Model"]
["OSE","Originating Service Environment"]
["OSP","Originating Service Provider"]
["POC","Person/Point of Contact"]
["PRF","Policy Routing Function"]
["PSAP","Public Safety Answering Point"]
["RFIA","Request for Assistance Interface"]
["RTP","Real-Time Transport Protocol"]
["SICP","Statewide Interoperability Communications Plan"]
["SIEC","Statewide Interoperability Executive Committee"]
["SIGB","Statewide Interoperability Governing Body"]
["SIP","Session Initiation Protocol"]
["SMS","Short Message Service"]
["SOP","Standard Operating Procedure"]
["SS7","Signaling System No. 7"]
["SWIC","Statewide Interoperability Coordinator"]
["TDM","Time-Division Multiplexing"]
["TFOPA","Task Force on Optimal Public Safety Answering Point Architecture"]

{"sheet":"Data Backend","index":5,"n_rows":529,"n_cols":3,"rows_kept":529,"cut":false,"hidden":true,"merged":[[130,4,130,5],[141,4,141,5],[70,0,70,1],[79,0,79,1],[244,0,244,1],[249,0,249,1],[253,0,253,1],[84,0,84,1],[89,0,89,1],[94,0,94,1],[98,0,98,1],[99,0,99,1],[215,0,215,1],[220,0,220,1],[112,0,112,1],[151,0,151,1],[124,4,124,5],[168,0,168,1],[172,0,172,1],[131,0,131,1],[135,0,135,1],[143,0,143,1],[147,0,147,1],[155,0,155,1],[418,0,418,1],[431,0,431,1],[422,0,422,1],[417,0,417,1],[427,0,427,1],[406,0,406,1],[410,0,410,1],[414,0,414,1],[392,0,392,1],[401,0,401,1],[473,0,473,1],[474,0,474,1],[477,0,477,1],[464,0,464,1],[437,0,437,1],[438,0,438,1],[443,0,443,1],[434,0,434,1],[469,0,469,1],[456,0,456,1],[446,0,446,1],[449,0,449,1],[452,0,452,1],[455,0,455,1],[460,0,460,1],[26,0,26,1],[42,0,42,1],[51,0,51,1],[123,0,123,1],[127,0,127,1],[73,0,73,1],[76,0,76,1],[102,0,102,1],[30,0,30,1],[55,0,55,1],[60,0,60,1],[65,0,65,1],[46,0,46,1],[38,0,38,1],[34,0,34,1],[122,0,122,1],[50,0,50,1],[116,0,116,1],[139,0,139,1],[176,0,176,1],[195,0,195,1],[200,0,200,1],[0,0,0,1],[2,0,2,1],[121,0,121,1],[243,0,243,1],[6,0,6,1],[10,0,10,1],[1,0,1,1],[177,0,177,1],[185,0,185,1],[190,0,190,1],[14,0,14,1],[18,0,18,1],[22,0,22,1],[105,0,105,1],[109,0,109,1],[83,0,83,1],[160,0,160,1],[164,0,164,1],[205,0,205,1],[230,0,230,1],[181,0,181,1],[210,0,210,1],[214,0,214,1],[342,0,342,1],[341,0,341,1],[328,0,328,1],[345,0,345,1],[356,0,356,1],[370,0,370,1],[309,0,309,1],[314,0,314,1],[325,0,325,1],[332,0,332,1],[333,0,333,1],[337,0,337,1],[365,0,365,1],[351,0,351,1],[350,0,350,1],[225,0,225,1],[229,0,229,1],[265,0,265,1],[281,0,281,1],[384,0,384,1],[389,0,389,1],[375,0,375,1],[380,0,380,1],[364,0,364,1],[361,0,361,1],[383,0,383,1],[397,0,397,1],[233,0,233,1],[237,0,237,1],[257,0,257,1],[245,0,245,1],[269,0,269,1],[319,0,319,1],[322,0,322,1],[273,0,273,1],[277,0,277,1],[299,0,299,1],[304,0,304,1],[289,0,289,1],[285,0,285,1],[293,0,293,1],[294,0,294,1],[261,0,261,1]]}
["State Governance"]
["Governance Structure Design & Framework",null,"Regional: All intrastate or interstate organizations that are multijurisdictional"]
["Established a name, authority, and purpose for a formalized 911 governance body that: a) solidifies the body’s legal standing and purpose; b) indicates its authority and any amendments to prior authorities; and c) confirms any concurrent jurisdictional bounds, if applicable:",null,"State: All state, commonwealth, and territorial organizations"]
["Planning to develop","Foundational","Local: All remaining city, town, county, village, parish, tribal, and municipal organizations"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Established the governance body’s oversight authority—including any rule-making authority—aligning activities to overarching strategies and plans, and maintaining fiduciary and fiscal compliance:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Regulations, a charter, and/or bylaws that build upon the legal authority or set an agreed-upon authority, concurring with all jurisdictions where applicable:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["A reporting mechanism for the governance body to notify the public and all appropriate government agencies/bodies on accomplishments, issues, and future priorities to enhance 911/NG911:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["A membership listing of 911 governance authorities’ representatives:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Defined roles, responsibilities, and functions (e.g., voting, non-voting, and ex-officio) for members of the governance authority:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["A 911 Administrator (and appropriate support) to execute 911 services (e.g., operations, training, and performance standards):"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["An ongoing mechanism to encourage collaboration among NG911 and other public safety governance bodies (e.g., broadband, other jurisdictions) to promote interoperability:"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["A governance authority that collaborates and engages with all applicable Statewide Interoperability Coordinators (SWICS):"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["A governance authority that collaborates and engages with all applicable state 911 administrators:"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["A governance authority that collaborates and engages with broadband authorities:"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["A governance authority that collaborates and engages with all applicable neighboring jurisdictions:"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["Governance Strategic Planning"]
["Established requirements for compliance with standards and policy for state-funded ECC/PSAP operations:"]
["Planning to establish","Foundational"]
["Established","Transitional"]
["Implemented","Intermediate"]
["Developed a 911/NG911 plan:"]
["Not planning to develop","Legacy"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Developed joint 911/NG911 MOU/As for multi-jurisdictional cooperation:"]
["Not planning to develop","Legacy"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Established a state entity with authority to collaboratively plan the entire or certain components of the NG911 system (e.g., ESInet, databases):"]
["Do not plan to establish","Legacy"]
["Planning to establish","Foundational"]
["Established","Transitional"]
["Implemented","Intermediate"]
["Aligned the governance body with the Statewide Communications Interoperability Plan (SCIP):"]
["Yes","N/A"]
["No","N/A"]
["Aligned the governance body with available NG911 initiatives and strategic plans:"]
["Yes","N/A"]
["No","N/A"]
["Updated the governance body periodically to reflect changes to NG911 emergency communications goals and objectives:"]
["Yes","N/A"]
["No","N/A"]
["Developed reporting procedures on 911/NG911 progress to appropriate authorities:"]
["Planning to develop reporting procedures","Foundational"]
["Developed reporting procedures","Transitional"]
["Developed and submitting reports","Intermediate"]
["Governance Coordination"]
["Implemented a statewide NG911 entity (e.g., NG911 governance board, SIGB, SIEC) with coordination, advisory, and support responsibility for all ECC/PSAPs within the state:"]
["Not planning to develop","Legacy"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented","Intermediate"]
["The statewide NG911 entity is represented on a statewide body coordinating all emergency communications:"]
["No statewide body coordinating emergency communications","Legacy"]
["Planning to integrate NG911 entity into statewide body","Foundational"]
["NG911 entity included in statewide body","Transitional"]
["NG911 entity actively participating in statewide body","Intermediate"]
["A liaison to provide guidance on NG911 policies, funding, and operation and technical developments:"]
["Planning to identify a liaison","Foundational"]
["Identified a liaison","Transitional"]
["Liaison providing guidance","Intermediate"]
["Governance Funding & Resources"]
["Enough resources (e.g. staff, funding) to carry out its NG911 mandate:"]
["No","N/A"]
["Yes","N/A"]
["The authority to collect and disburse NG911 funds:"]
["No","N/A"]
["Yes","N/A"]
["Reviewed authorities for tasks and responsibilities related to enforcing laws, rules, and regulations regarding NG911 service and funds, based on statutes, executive orders, or regulations:"]
["Planning to review authorities","Foundational"]
["Have reviewed authorities","Transitional"]
["Have reviewed authorities and implemented policy","Intermediate"]
["A current dedicated, protected funding mechanism to address 911 operating costs and NG911 investment costs:"]
["No","N/A"]
["Yes","N/A"]
["Promoted economies of scale by instituting cooperative purchasing agreements or offering master purchasing agreements for the acquisition of NG911 capabilities:"]
["No","Foundational"]
["Yes","Intermediate"]
["N/A","N/A"]
["Defined, by policy, the state's role in NG911 procurement and management:"]
["Planning to review role","Foundational"]
["Have reviewed role","Transitional"]
["Have reviewed role and implemented policy","Intermediate"]
[]
["Regional Governance"]
["Governance Structure Design & Framework"]
["Established a name, authority, and purpose for a formalized 911 governance body that: a) solidifies the body’s legal standing and purpose; b) indicates its authority and any amendments to prior authorities; and c) confirms any concurrent jurisdictional bounds, if applicable:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Established the governance body’s oversight authority—including any rule-making authority—aligning activities to overarching strategies and plans, and maintaining fiduciary and fiscal compliance:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Regulations, a charter, and/or bylaws that build upon the legal authority or set an agreed-upon authority, concurring with all jurisdictions where applicable:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["A reporting mechanism for the governance body to notify the public and all appropriate government agencies/bodies on accomplishments, issues, and future priorities to enhance 911/NG911:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["A mutually agreed-upon body that provides administrative support or another mechanism to share these responsibilities:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["A membership listing of 911 governance authorities’ representatives:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Defined roles, responsibilities, and functions (e.g., voting, non-voting, and ex-officio) for members of the governance authority:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["A 911 Administrator (and appropriate support) to execute 911 services (e.g., operations, training, and performance standards):"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Encouragement of participation by relevant entities’ senior officials, if applicable:"]
["Planning to encourage","Foundational"]
["Encouraged","Transitional"]
["Encouraged and utilizing","Intermediate"]
["Not applicable","N/A"]
["A governance authority that collaborates and engages with all applicable Statewide Interoperability Coordinators (SWICS):"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["A governance authority that collaborates and engages with all applicable 911 administrators:"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["A governance authority that collaborates and engages with broadband authorities:"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["A governance authority that collaborates and engages with all applicable neighboring jurisdictions:"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["Governance Strategic Planning"]
["Determined requirements for, process for, and extent of collaboration/cooperation among all relevant entities:"]
["Planning to establish collaboration/cooperation","Foundational"]
["Established collaboration/cooperation","Transitional"]
["Active participation in collaboration/cooperation","Intermediate"]
["Common policies and standards for the operation of ECC/PSAPs (e.g., SOPs, accountability, reporting, etc.):"]
["Planning to adopt common policies and standards","Foundational"]
["Identified necessary common policies and standards","Transitional"]
["Implemented common policies and standards","Intermediate"]
["Developed 911/NG911 plan:"]
["Not planning to develop","Legacy"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Developed joint 911/NG911 MOU/As for multi-jurisdictional cooperation:"]
["Not planning to develop","Legacy"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Executed strategic planning for NG911 system requirements (e.g., NIEM, standards):"]
["No plans","Legacy"]
["Planning to develop","Foundational"]
["Developing plan(s)","Transitional"]
["Adopted and implemented plan(s)","Intermediate"]
["Executed strategic planning for NG911 accountability and reporting:"]
["No plans","Legacy"]
["Planning to develop","Foundational"]
["Developing plan(s)","Transitional"]
["Adopted and implemented plan(s)","Intermediate"]
["Executed strategic planning for system interoperability (e.g., GIS, CAD):"]
["No plans","Legacy"]
["Planning to develop","Foundational"]
["Developing plan(s)","Transitional"]
["Adopted and implemented plan(s)","Intermediate"]
["Implemented strategic and tactical NG911 plans to be adopted by member jurisdictions:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented","Intermediate"]
["Governance Coordination"]
["Developed a regional NG911 entity (e.g., NG911 governance board, council of governments, NG911 subcommittee) with coordination, advisory, or support responsibility for participating ECC/PSAPs within the region:"]
["Not planning to develop a regional NG911 entity","Legacy"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented","Intermediate"]
["Elected/appointed a member to act as a liaison with other state, regional, and local governance bodies and interested parties:"]
["Not planning to elect or appoint member to liaison","Legacy"]
["Planning to elect or appoint","Foundational"]
["Developed procedures to elect or appoint","Transitional"]
["Elected or appointed","Intermediate"]
["A liaison to provide guidance on NG911 policies, funding, and operation and technical developments:"]
["Planning to identify a liaison","Foundational"]
["Identified a liaison","Transitional"]
["Liaison providing guidance","Intermediate"]
["Funding & Resources"]
["Enough resources (e.g. staff, funding) to carry out its NG911 mandate:"]
["No","N/A"]
["Yes","N/A"]
["Promoted economies of scale by instituting cooperative purchasing agreements or offering master purchasing agreements for the acquisition of NG911 capabilities:"]
["No","Foundational"]
["Yes","Intermediate"]
["N/A","N/A"]
["Developed a regional resource allocation plan which may include funding-related investment decisions and potential funding methods:"]
["Not planning to develop a plan","Legacy"]
["Planning to develop a plan","Foundational"]
["Developed plan","Transitional"]
["Implemented plan","Intermediate"]
[]
["Local Governance"]
["Governance Structure Design & Framework"]
["Established a name, authority, and purpose for a formalized 911 governance body that: a) solidifies the body’s legal standing and purpose; b) indicates its authority and any amendments to prior authorities; and c) confirms any concurrent jurisdictional bounds, if applicable:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Established the governance body’s oversight authority—including any rule-making authority—aligning activities to overarching strategies and plans, and maintaining fiduciary and fiscal compliance:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Regulations, a charter, and/or bylaws that build upon the legal authority or set an agreed-upon authority, concurring with all jurisdictions where applicable:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["A reporting mechanism for the governance body to notify the public and all appropriate government agencies/bodies on accomplishments, issues, and future priorities to enhance 911/NG911:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["A membership listing of 911 governance authorities’ representatives:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Defined roles, responsibilities, and functions (e.g., voting, non-voting, and ex-officio) for members of the governance authority:"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["A 911 Administrator (and appropriate support) to execute 911 services (e.g., operations, training, and performance standards):"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["An ongoing mechanism to encourage collaboration among NG911 and other public safety governance bodies (e.g., broadband, other jurisdictions) to promote interoperability:"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["A governance authority that collaborates and engages with all applicable Statewide Interoperability Coordinators (SWICS):"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["A governance authority that collaborates and engages with all applicable 911 administrators:"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["A governance authority that collaborates and engages with broadband authorities:"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["A governance authority that collaborates and engages with all applicable neighboring jurisdictions:"]
["Yes","N/A"]
["No","N/A"]
["N/A","N/A"]
["Governance Strategic Planning"]
["Executed strategic planning for NG911 system requirements (e.g., NIEM, standards):"]
["No plans","Legacy"]
["Planning to develop","Foundational"]
["Developing plan(s)","Transitional"]
["Adopted and implemented plan(s)","Intermediate"]
["Executed strategic planning for NG911 accountability and reporting:"]
["No plans","Legacy"]
["Planning to develop","Foundational"]
["Developing plan(s)","Transitional"]
["Adopted and implemented plan(s)","Intermediate"]
["Executed strategic planning for system interoperability (e.g., GIS, CAD):"]
["No plans","Legacy"]
["Planning to develop","Foundational"]
["Developing plan(s)","Transitional"]
["Adopted and implemented plan(s)","Intermediate"]
["Developed a 911/NG911 plan:"]
["Not planning to develop","Legacy"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Developed joint 911/NG911 MOU/As for multi-jurisdictional cooperation:"]
["Not planning to develop","Legacy"]
["Planning to develop","Foundational"]
["Developed","Transitional"]
["Implemented and using","Intermediate"]
["Aligned the governance body with the Statewide Communications Interoperability Plan (SCIP):"]
["Yes","N/A"]
["No","N/A"]
["Aligned the governance body with available NG911 initiatives and strategic plans:"]
["Yes","N/A"]
["No","N/A"]
["Updated the governance body periodically to reflect changes to NG911 emergency communications goals and objectives:"]
["Yes","N/A"]
["No","N/A"]
["Developed reporting procedures on 911/NG911 progress to appropriate authorities:"]
["Planning to develop reporting procedures","Foundational"]
["Developed reporting procedures","Transitional"]
["Developed and submitting reports","Intermediate"]
["Governance Coordination"]
["Coordinated with other ECC/PSAPs to address challenges associated with the evolving emergency communications landscape:"]
["Planning to develop","Foundational"]
["Developed procedures for coordination","Transitional"]
["Implemented procedures and actively coordinating","Intermediate"]
["A liaison to provide guidance on NG911 policies, funding, and operation and technical developments:"]
["Planning to identify a liaison","Foundational"]
["Identified a liaison","Transitional"]
["Liaison providing guidance","Intermediate"]
["Governance Funding & Resources"]
["Enough resources (e.g. staff, funding) to carry out its NG911 mandate:"]
["No","N/A"]
["Yes","N/A"]
["Promoted economies of scale by instituting cooperative purchasing agreements or offering master purchasing agreements for the acquisition of NG911 capabilities:"]
["No","Foundational"]
["Yes","Intermediate"]
["N/A","N/A"]
[]
["Routing & Location"]
["Accurately, factually, and consistently characterize the 911 call routing currently in use and planning/funding sought:"]
["Using ESN routing and not actively planning replacement","Legacy"]
["Using ESN routing and actively planning replacement","Foundational"]
["Using both ESN routing and geospatial routing","Transitional"]
["Implemented geospatial routing (using best available location)","Intermediate"]
["Characterize the Automatic Location Information (ALI)/Location Object use in database management systems (DBMS):"]
["Using ALI and not planning to implement Location Object","Legacy"]
["Using ALI and planning to implement Location Object","Foundational"]
["Potentially using two different methods (either ALI or Location Object)","Transitional"]
["Processing with Location Object","Intermediate"]
["Specify if a LIS or its equivalent is implemented with each originating service provider (OSP) for every ECC/PSAP within your jurisdiction:"]
["No, a LIS or its equivalent has only been implemented with some OSPs (or not at all)","N/A"]
["Yes, a LIS or its equivalent is implemented with each OSP","N/A"]
["GIS Data"]
["Characterize to what extent a NG911 dataset has been created:"]
["Not planning to create a NG911 dataset","Legacy"]
["Planning to implement a NG911 dataset","Foundational"]
["Implementing the creation of a NG911 dataset","Transitional"]
["Dataset is complete and implemented","Intermediate"]
["Specify the usage of Emergency Call Routing Function (ECRF) in GIS data formatting:"]
["Using ESN routing and not planning to implement geospatial ","Legacy"]
["Using ESN routing and planning to implement geospatial routing","Foundational"]
["ECRF is optional and planning to implement geospatial routing","Transitional"]
["Implemented ECRF and using geospatial routing","Intermediate"]
["Specify the usage of Policy Routing Function (PRF):"]
["Not using PRF and not planning to implement policy routing rules","Legacy"]
["Not planning to use PRF but planning to implement policy routing rules","Foundational"]
["Not using PRF but have developed draft policy routing rules","Transitional"]
["Implemented PRF and using policy routing rules","Intermediate"]
["Indicate if the data is formatted for Location Verification Function (LVF) use:"]
["Yes","N/A"]
["No","N/A"]
["NG911 Core Service Elements"]
["Characterize the implementation of Legacy Selective Router Gateway (LSRG):"]
["Not planning to implement a LSRG at this time","Foundational"]
["Planning to implement a LSRG","Transitional"]
["Implemented and using a LSRG or an alternate process","Intermediate"]
["N/A","Intermediate"]
["Specify if a LVF has been provided:"]
["Yes","N/A"]
["No","N/A"]
["Characterize the implementation of ESRP:"]
["Not planning to implement an ESRP","Legacy"]
["Planning to implement an ESRP","Foundational"]
["Beginning to implement an ESRP, but ESRP does not conduct all routing","Transitional"]
["Implemented an ESRP, and geospatial routing is in place","Intermediate"]
["Characterize the implementation of Emergency Call Routing Function (ECRF):"]
["Not planning to implement an ECRF at this time","Foundational"]
["Beginning to implement an ECRF, but ECRF does not conduct all routing","Transitional"]
["Implemented an ECRF, and geospatial routing is in place","Intermediate"]
["Characterize the implementation of a Legacy Network Gateway (LNG):"]
["Not planning to implement a LNG at this time","Foundational"]
["Planning to implement a LNG","Transitional"]
["Implemented a LNG","Intermediate"]
["N/A","N/A"]
["Characterize the implementation of a Legacy ECC/PSAP Gateway (LPG):"]
["Not planning to implement a LPG at this time","Foundational"]
["LPG is considered optional","Transitional"]
["Implemented a LPG","Intermediate"]
["Characterize the implementation of Border Control Function (BCF) capabilities:"]
["Not planning to implement a BCF at this time","Foundational"]
["BCF is considered part of the design and will imlement","Transitional"]
["Implemented a BCF","Intermediate"]
["Specify if logging capabilities have been fully implemented and maintained:"]
["Yes","Intermediate"]
["No","Transitional"]
["Network (OSE and ESInet)"]
["Characterize the service of Originating Service Provider (OSP):"]
["Served by local exchange carrier (LEC) only","Foundational"]
["Served by LEC and an OSP","Transitional"]
["Served by multiple OSPs","Intermediate"]
["Characterize the implementation of an Ingress network:"]
["Not planning to implement an Ingress network","Legacy"]
["Using local exchange carrier that delivers non-IP traffic","Foundational"]
["Transitioning to an IP-based network but still completing with multiple OSPs  (i.e., direct wireless traffic into ESInets), delivering both TDM and IP traffic","Transitional"]
["Delivering both TDM and IP traffic and accepts both IP and non-IP traffic in an Ingress environment with multiple OSPs that process geospatial data","Intermediate"]
["Characterize the Egress process of your ECC/PSAP:"]
["Using non-IP Egress only","Foundational"]
["Using non-IP Egress and IP Egress (without next generation headers that enable i3 call routing)","Transitional"]
["Using non-IP Egress and IP Egress (with next generation headers that enable i3 call routing)","Intermediate"]
["Specify whether traditional ALI data circuits are used:"]
["Yes","Transitional"]
["No","N/A"]
["Specify if multiple NG core services, including call hand-offs and transfers, are interconnected with neighboring ESInets:"]
["Yes","Intermediate"]
["No","N/A"]
["ECC/PSAP Call Handling System & Applications"]
["Characterize the call handling system in use:"]
["Legacy system and not planning for an IP-based system","Legacy"]
["Planning to transition to an IP-based system","Foundational"]
["Using an IP-based system, and might be planning for an interoperable multimedia system","Transitional"]
["Using a singularly connected interoperable multimedia system","Intermediate"]
["Specify whether mapping occurs:"]
["Yes","Intermediate"]
["No","N/A"]
["Specify if Text-to-911 (Short Message Service) has been implemented:"]
["Yes","Intermediate"]
["No","Transitional"]
["Specify whether the system routes multimedia information:"]
["Yes","Intermediate"]
["No","This response does not impact maturity state"]
["Specify whether logging and recording of NG911 multimedia data has been implemented:"]
["Yes","Intermediate"]
["No","This response does not impact maturity state"]
["Operational Planning"]
["Indicate whether the 911 Plan has been updated:"]
["Yes","Foundational"]
["No","Legacy"]
["Not required","N/A"]
["Characterize current NG911 operational planning and procedures:"]
["Currently planning NG911 operational procedures","Foundational"]
["Developed NG911 operational procedures and beginning to implement","Transitional"]
["Developed NG911 operational procedures and fully implemented within the ECC/PSAP's control","Intermediate"]
["Characterize current assessments of staffing needs based on NG911 transition:"]
["Has not been started","Legacy"]
["Analyzed and determined the required staffing needs","Foundational"]
["Started hiring required staffing","Transitional"]
["Hired all required staffing","Intermediate"]
["Characterize the process of training staff based on NG911 transition:"]
["Planning processes to train staff","Foundational"]
["Initiated staff training processes","Transitional"]
["Completed current staff training processes","Intermediate"]
["Optional Interfaces"]
["Specify whether a computer-aided dispatch (CAD) is in use:"]
["Yes","N/A"]
["No","N/A"]
["Specify whether a broadband field network is in use:"]
["Yes","N/A"]
["No","N/A"]
[]
["Security","Yes"]
["Security Identification & Discovery","No"]
["Inventoried all existing systems and applications:"]
["Classified all assets:","Yes"]
["Identified owners of communications infrastructure assets:","No"]
["Identified applicable laws, regulations, and requirements:"]
["Determined existing vulnerabilities:","Yes"]
["Security Assessment & Prioritization","No"]
["Conducted a risk assessment:"]
["Established security controls:","Yes"]
["Developed remediation plans:","No"]
["Prioritized the execution of remediation plans, mitigations, and improvements:"]
["Security Implementation & Operation","Yes"]
["Documented necessary policies, procedures, and controls for effective security:","No"]
["Administered access control:"]
["Provided security awareness training and techniques:","Yes"]
["Implemented auditing and accountability:","No"]
["Established a baseline configuration and configuration management controls:"]
["Implemented contingency planning for continuity of operations:"]
["Implemented identification and authentication controls:"]
["Coordinated activities for security incident response:"]
["Evaluated maintenance impacts on security controls:"]
["Implemented media protection controls:"]
["Implemented personnel security controls:"]
["Implemented physical and environmental protection controls:"]
["Developed a security plan:"]
["Implemented information security program management:"]
["Established a risk management plan:"]
["Achieved authorization for security controls:"]
["Planned for system and services acquisition:"]
["Accounted for system and communications protection controls:"]
["Provided system and information integrity controls:"]
["Executed remediation plans:"]
["Implemented controls for conformance for known laws, regulations, and contractual obligations:"]
["Security Monitoring & Analysis"]
["Developed a baseline of the current environment:"]
["Implemented security event logging:"]
["Implemented security metrics capture:"]
["Implemented compliance evaluation:"]
["Evaluated control effectiveness:"]
["Security Testing & Evaluation"]
["Performed security audits:"]
["Updated contingency plans with respect to security controls:"]
["Security Improvement & Evolution"]
["Developed and implemented policies for regular security reassessment:"]
["Developed and implemented policies for re-evaluation of the security management program:"]
["Developed and implemented policies for evolving security training and awareness:"]
["Developed and implemented policies for short- and long-term capacity planning:"]