The Latest NENA Standards: An Overview

Slides:



Advertisements
Similar presentations
EMS Checklist (ISO model)
Advertisements

Brian Rosen Chair, Long Term Definition WG.  i1 = document older strategies for VoIP into  i2 = standard way to support VoIP on current E9-1-1.
CIP Cyber Security – Security Management Controls
NENA Development Conference | October 2014 | Orlando, Florida Committee Status Overview Pete Eggimann, DSC Co-Chair Jim Shepard, DSC Co-Chair NENA: The.
Capability Cliff Notes Series PHEP Capability 4—Emergency Public Information and Warning What Is It And How Will We Measure It?
IS 700.a NIMS An Introduction. The NIMS Mandate HSPD-5 requires all Federal departments and agencies to: Adopt and use NIMS in incident management programs.
1 Continuity Planning for transportation agencies.
Security Controls – What Works
TEL382 Greene Chapter /27/09 2 Outline What is a Disaster? Disaster Strikes Without Warning Understanding Roles and Responsibilities Preparing For.
Understanding Multiagency Coordination IS-701.A – February 2010 Visual 2.1 Unit 2: Understanding Multiagency Coordination.
Copyright © Center for Systems Security and Information Assurance Lesson Eight Security Management.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
EASTERN MICHIGAN UNIVERSITY Continuity of Operations Planning (COOP)
Continuity of Operations Planning COOP Overview for Leadership (Date)
Chapter 4 Interpreting the CMM. Group (3) Fahmi Alkhalifi Pam Page Pardha Mugunda.
ENP Study Group Disaster Planning Session #6 BROUGHT TO YOU BY: THE FLORIDA NENA EDUCATION COMMITTEE.
PSAP Service Capability Assessment Tool Session A Joint Effort of APCO and NENA Presented June 10, 2009 for Discussion & Feedback by: Tom Breen, ENP.
Module 3 Develop the Plan Planning for Emergencies – For Small Business –
Federal Aviation Administration Federal Aviation Administration 1 Presentation to: Name: Date: Federal Aviation Administration AMHS Security Security Sub-Group.
NENA Development Conference | October 2014 | Orlando, Florida Emergency Incident Data Document (EIDD) Transfer Protocols Jerry Schlesinger, PMP – City.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
 Working Group 2: Optimal Approach to NG9-1-1 Architecture Implementation by PSAPs Status Report September 29, 2015.
New River Valley Emergency Communications Regional Authority
Welcome to the NENA Development Conference. Thank You to Our Sponsors!
Building Blocks for the NG9-1-1 PSAP MICHAEL SMITH - DSS CORP. RICK BLACKWELL, ENP - GREENVILLE COUNTY, SC.
Sharing Incident Information Using the Emergency Incident Data Document MICHAEL SMITH - DSS CORP. RICK BLACKWELL, ENP - GREENVILLE COUNTY, SC.
NG9-1-1 Core Architecture: i3 v3 TERRY REESE BRIAN ROSEN.
What Is an Incident? An incident is an occurrence, caused by either human or natural phenomena, that requires response actions to prevent or minimize.
Maintaining and Sustaining System Integrity Configuration Management for Transportation Management Systems Configuration management (CM) describes a series.
Next Generation Decision Maker Webinar October 7,
First-Time Orientation Committee Open House. First Timer Orientation Committee Open House Welcome to the NDC! Introducing Jim Shepard, ENP– Co-Chair of.
California Department of Public Health / 1 CALIFORNIA DEPARTMENT OF PUBLIC HEALTH Standards and Guidelines for Healthcare Surge during Emergencies How.
The member organizations of the National Public Safety Telecommunications Council are grateful to the Department of Homeland Security’s Science and Technology.
1 Federal Emergency Management Agency Charlie Hoffman Disaster Operations Directorate Chief, DEC Programs Disaster Emergency Communications National Public.
Business Continuity Steven S. Keleman, CPM. Emergency Management Prevention Response Preparation Mitigation Recovery.
Peer Resource Network Occupational Health & Safety Program Requirements Introduce facilitator Updated: 2017.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Technical Standards: Paving the Way to NG9-1-1
NATIONAL INCIDENT MANAGEMENT SYSTEM (NIMS)
Defining Map Services in NG9-1-1
Utilizing Your Business Continuity Plan.
How GIS will support Ng911 in Indiana
Software Project Configuration Management
Disaster and Emergency Planning
OAIS Producer (archive) Consumer Management
Incident Management & Business Continuity
Emergency Operations Plan
Crisis Management Plan Overview
Developing NG9-1-1 PSAP System Standards
Preparing for the Future
Fundamentals of ISO.
Continuity of Operations Planning Introduction & Practical Application – PART TWO Kelly Keenan, MPH May 14, 2015.
Software Configuration Management
Description of Revision
TSMO Program Plan Development
Standards and Certification Training
Emergency Planning Steps
Communication and Consultation with Interested Parties by the RB
Building Emergency Evacuation Plan (BEEP) Training for Building Emergency Coordinators and Alternates.
EMS Checklist (ISO model)
MODULE B - PROCESS SUBMODULES B1. Organizational Structure
Continuity of Operations Planning
Engineering Processes
Unit 3 Overview This unit introduces you to the Incident Command System (ICS) Functional Areas and roles of the Incident Commander and Command Staff.
Chapter 3: Project Integration Management
Internal Control Internal control is the process designed and affected by owners, management, and other personnel. It is implemented to address business.
Project Management Method and PMI ® PMBOK ® Roles
{Project Name} Organizational Chart, Roles and Responsibilities
Building Emergency Evacuation Plan (BEEP) Training for Building Emergency Coordinators and Alternates.
Presentation transcript:

The Latest NENA Standards: An Overview Jim Shepard, ENP

Quick Primer on Nomenclature How to decipher a document’s title. Example: NENA-STA-010.2-2016, Detailed Functional and Interface Standards for the NENA i3 Solution Version Sequence # starting at .1 for the original Origin: Usually either “NENA” or “NENA/APCO” Type: “ADM” = Administrative “INF” = “Informational” “REF” = “Reference” “REQ” = “Requirements” “STA” = “Standards” Document Sequence # starting at 1 The year the NENA Board Approved Title

Documents Published in the Past Year 09/18/2015: NENA-INF-014.1-2015, NENA Information Document for Development of Site/Structure Address Point GIS Data for 9-1-1 11/12/2015: NENA-ADM-001.2-2015, NENA Development Group Organizational Structure 11/12/2015: NENA-ADM-002.3-2015, NENA Document Development & Approval Process 11/12/2015: NENA-INF-017.2-2015, PSAP Disaster & Contingency Plans Model Recommendation 01/15/2016: NENA/APCO-REQ-001.1.1-2016, NG9-1-1 PSAP Requirements Document 03/10/2016: NENA-REQ-002.1-2016, NENA Next Generation 9-1-1 Data Management Requirements 03/31/2016: NENA-STA-013.2-2016 , NENA Public Safety Communications & Railroad Interaction Standard Operating Procedures 09/10/2016: NENA-STA-010.2-2016, Detailed Functional and Interface Standards for the NENA i3 Solution 09/10/2016: NENA-INF-019.2-2016, Hazard and Vulnerability Analysis

NENA-INF-014.1-2015 Site/Structure Address Point GIS Data for 9-1-1 A guide for those developing site/structure address point data in a GIS for use in 9-1-1 and NG9-1-1. Site/structure address points represent addresses assigned by the local addressing authority, which may not reflect the addresses used in commercial or United States Postal Service (USPS) databases. The intent is to provide guidelines for site/structure address point GIS data development to support the needs of public safety applications, including: NG9-1-1 Location Validation NG9-1-1 Call Routing 9-1-1 Map Display Computer Aided Dispatch (CAD) Vehicle Routing Emergency Notification Chairs: Cheryl Benjamin Richard Kelly

NENA-ADM-001.2-2015, NENA Development Group Organizational Structure Describes the Organizational Structure of the NENA Development Group. This structure defines the role, function and relationship of the NENA Development Committees that address the complex operations and technology issues related to the provision and management of emergency communications services. Chairs: DSC Leadership DSC Advisor

NENA-ADM-002.3-2015, NENA Document Development & Approval Process Describes the process and procedures that apply to the NENA Development Group (NDG). These procedures have been developed to clearly define the method of developing consensus documents by the NDG to provide information, define requirements and develop NENA standards for the public safety industry. Use of this document will ensure that all processes and procedures are adhered to in the managing of the Development Group process. Procedures contained in this document will: Ensure a uniform method for developing NENA documents Ensure that processes are followed that allow for issue submission and tracking Ensure that appropriate documentation and follow-up procedures are adhered to Allow all Development Group members to thoroughly understand the Committee process Allow all Development Group leaders and members to understand their roles and responsibilities Allow for a standard development process similar to other Standards Development Organizations (SDO) Allow for a smoother referral process to other Standards Development Organizations (SDO) Chairs: DSC Leadership DSC Advisor

NENA-INF-017.2-2015, PSAP Disaster & Contingency Plans Model Recommendation Serve as a reference to a contingency planning section of a Standard Operating Procedure (SOP) for use by Communications Centers and/or PSAP Authorities as guidance in the formulation of an agency SOP. Each agency is unique in its resources and operations and as such, this document should be modified and/or updated to meet the requirements and legal obligations of differing modes of operations. This document includes best practices, guidelines and procedures on: Staffing IT Security Redundant Systems Situations requiring evacuation Evacuation Procedures Return to Normal Operations Chairs: Terri Costello RPL Cheryl LeSage ENP

NENA/APCO-REQ-001.1.1-2016, NG9-1-1 PSAP Requirements Document This technical requirements document introduces requirements for a NG9-1-1 Public Safety Answering Point (PSAP) that is capable of receiving IP-based signaling and media for delivery of emergency calls conformant to the latest version of the NENA i3 Architecture document. This document is issued as NENA/APCO recommended requirements for functions and interfaces between an i3 PSAP and NG9-1-1 Core Services, and among Functional Elements associated with the i3 PSAP. This document is primarily intended to drive the development of more standards that meet the technical requirements specified herein. Chairs: Michael Smith Rick Blackwell

NENA-REQ-002.1-2016, NG9-1-1 Data Management Requirements This document defines discrepancy report and the performance reports associated with processes within the Next Generation 9-1-1 (NG9-1-1) system. The intent is to provide 9-1-1 Authorities, vendors, Communication Service Providers (CSP), and other interested parties with guidelines for communicating issues or status of various elements within the system. The components of the document are Discrepancy Report Requirements and Performance Statistic Report Requirements. Chairs: Kathy Liljequist

NENA-STA-013.2-2016, Railroad Interaction Standard Operating Procedures This document provides guidance and relevant information for operational interaction between public safety answering points (PSAPs), public safety communications, railroad call centers, railroad-sworn personnel in the field, and related railroad responders. This Standard is intended to aid Public Safety Answering Points (PSAP), railroad communication centers, and railroad personnel in the development and implementation of standard operating procedures for emergency communications protocols pertaining to railroad and railroad related emergencies. Chairs: Lisa Dodd, ENP Marc Berryman, ENP

NENA-STA-010.2-2016, Detailed Functional & Interface Standards for the i3 Solution This specification builds upon prior NENA publications including i3 requirements and architecture documents. While the requirements and architecture documents describe high level concepts, the present document describes only the detailed functional and external interfaces to those functional elements. This document provides a baseline to other NG9-1-1 related specifications. This document describes the "end state” that has been reached after a migration from legacy TDM circuit-switched telephony, and the legacy E9-1-1 system built to support it, to an all IP-based telephony system with a corresponding IP-based Emergency Services IP network. Chairs: Brian Rosen Steve O’Conor, ENP

NENA-INF-019.2-2016, Hazard and Vulnerability Analysis This document is provided to assist PSAPs with the development of Hazard and Vulnerability Analyses. These analyses are essentially audits that provide planning tools to prevent, prepare for, respond to and recover from incidents that have the potential to adversely affect the PSAPs ability to perform its critical functions. This document is intended as a guide for PSAP staff to review the hazards and their individual vulnerability to hazards, which may adversely impact the PSAPs ability to serve their communities. This document is not intended as a template, but as a guide to the process of hazard and vulnerability analysis. Chairs: Terri Costello RPL Cheryl LeSage, ENP