Sharing Incident Information Using the Emergency Incident Data Document MICHAEL SMITH - DSS CORP. RICK BLACKWELL, ENP - GREENVILLE COUNTY, SC.

Slides:



Advertisements
Similar presentations
Initial Planning Conference Initial Planning Conference [DATE]
Advertisements

Marin County Emergency Medical Services Excellent Care – Every Patient, Every Time Marin County Multiple Patient Management Plan Training Module June 2013.
Airport Emergency Plan - Overview
Major Incident Process
Public Health Seattle & King County Incident Command System Overview May 2004.
N  E  R  R  T  C National Emergency Response & Rescue Training Center LRGVDC Multi-Agency Coordination Center (MACC)
THE INTERNATIONAL SOCIETY OF FIRE SERVICE INSTRUCTORS Electronic INSTRUCT-O-GRAM Program The “Safety Engine” Concept – Part 1.
NENA Development Conference | October 2014 | Orlando, Florida NG9-1-1 PSAP Requirements and Standards Michael Smith, DSS Mike Vislocky, Network Orange.
1 E-911 Services Board Meeting General Business Meeting May 23,
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.
Prepared by: Beatrice Powell April 2012 Modified by: Sue Dawson September 2012.
Accident Prevention Programs What Will We Talk About? What is an accident? What is an accident prevention program? Basic elements of a program Where.
Initial Planning Conference [Date]
I-295 / I-76 / NJ 42 Incident Management Task Force in New Jersey
Contractor Safety Training | Westbrook | 1 Emergency Response.
Network security policy: best practices
National Incident Management System Introduction and Overview NIMS.
1 Introducing BSI Health & Safety Self-assessment Online.
Personnel Accountability Purpose: Identify a system of firefighter accountability on site of an incident and account for all firefighters, at any given.
IS-700.A: National Incident Management System, An Introduction
ENP Study Group Disaster Planning Session #6 BROUGHT TO YOU BY: THE FLORIDA NENA EDUCATION COMMITTEE.
P-1 Nuclear Power Plant Shut Down. P-2 Most Dangerous Reactors: A Compendium of Reactor Risk Assessments Units 1 & 2 “Reactors remain unstable and difficult.
Interoperability Tests for IEC Scott Neumann November 12, 2009.
ESW 7 – NENA ICE Testing NG9-1-1 Interoperability Testing −Background -Need -Response: NENA-sponsored NG9-1-1 Interop Testing −NENA Industry Collaboration.
1 NEMESIS North East Minnesota Enforcement and and Safety Information System.
Traffic Incident Management Focus State Initiative: Program-Level Performance Measurement Workshops Talking Operations Webcast February 22, 2006.
NENA Development Conference | October 2014 | Orlando, Florida Emergency Incident Data Document (EIDD) Transfer Protocols Jerry Schlesinger, PMP – City.
Building Information Exchange with First Responders (BIEFR) David Holmberg, NIST June 11, 2009 Slides credit to Alan Vinh.
Law Enforcement Information Technology Standards Council (LEITSC) Project Status Update Global Advisory Committee November 2, 2006.
Draft-rosen-ecrit-emergency- framework-00 Brian Rosen NeuStar CPa
Course Summary IS-701.A – February 2010 Visual 6.1 Unit 6: Course Summary.
Developing Plans and Procedures
Next Generation Standards, Transitions and Challenges Brian Rosen Senior Director, Neustar Chair, Long Term Definition WG, NENA.
Working Group 1: NG9-1-1 December 16, 2011 Laurie Flaherty Brian Fontes WG 1 Co-Chairs.
Rev.04/2015© 2015 PLEASE NOTE: The Application Review Module (ARM) is a system that is designed as a shared service and is maintained by the Grants Centers.
Welcome to the NENA Development Conference. Thank You to Our Sponsors!
1 Adoption of GJXDM for the JIN Scott Came Director of Systems and Technology SEARCH December 19, 2006.
Building Blocks for the NG9-1-1 PSAP MICHAEL SMITH - DSS CORP. RICK BLACKWELL, ENP - GREENVILLE COUNTY, SC.
National Information Exchange Model (NIEM) Executive Introduction November 29, 2006 Thomas O’Reilly NIEM Program Management Office.
NG9-1-1 Core Architecture: i3 v3 TERRY REESE BRIAN ROSEN.
Dearborn Fire Department Response to Haz-Mat Incidents & How to Request the Haz-Mat Team.
Introduction to SEMS and Basic ICS. Goals of Training Basic Understanding: The California Standardized Emergency Management System (SEMS) in place to.
I - 1 Nuclear Plant Situation Crisis Prevention, Response for the Baltic States: Organizations, Policies and Procedures Nuclear Plant Crisis.
Partial Notifications IETF 56 SIMPLE WG draft-lonnfors-simple-presinfo-deliv-reqs-00 draft-lonnfors-simple-partial-notify-00 Mikko Lönnfors
Kenneth Chelst, Ph.D. Leonard Matarese, M.P.A. City of Plymouth Emergency Services Data Analysis and Alternatives.
Exercise Presentation. WELCOME AND INTRODUCTIONS.
Pandemic Flu Tabletop Exercise (TTX) [insert date of exercise] Public Health – Seattle & King County [insert your agency logo]
Fire Service Incidents. Today’s fire service does much more than fight fires. The Fire Service has become the primary source of emergency response and.
Emergency Services Communications Firefighter II.
Jerry Schlesinger PMP Henry Unger
The Emergency Incident Data Document (EIDD)
Technical Standards: Paving the Way to NG9-1-1
Anne Arundel County Fire Department
The Latest NENA Standards: An Overview
Smart Phone App for Road Rangers
Understanding & Defining Additional Data Interfaces in NG9-1-1
Risk Assessment Meeting
Coordinating with Station Emergency Response Agencies
STRATEGIES FOR fire & EMS Efficiencies
Developing NG9-1-1 PSAP System Standards
Emergencies & Emergency Response
Essentials of Fire Fighting Chapter 3 — Fire Department Communications
The COG “Cookbook” Course Lesson 1 - Introduction to COG Basics
The Public Safety Broadband Network (FirstNet) & NG9-1-1
Diane Harris, CF APMP, ENP April Heinze, ENP Wendi Lively, ENP
Managing NG9-1-1 what could go wrong?
Area and Regional Medical Coordination
DSC Governance Sub Group Recommendations
Final Design Authorization
Unit 6: Incident Resource Management
Presentation transcript:

Sharing Incident Information Using the Emergency Incident Data Document MICHAEL SMITH - DSS CORP. RICK BLACKWELL, ENP - GREENVILLE COUNTY, SC

What we’ll cover Basic overview of what the EIDD is Status of EIDD development Potential operational impacts of using EIDDs

What is an EIDD Emergency Incident Data Document – a standardized “container” for sharing Incident information XML, for you “techies”…

Status of EIDD Development Joint NENA/APCO WG finalizing the EIDD ANS ◦ ANS document in final stage of being edited ◦ EIDD IEPD (mapping spreadsheet and XML Schema) – created and updated by SEARCH. A few tweaks remain. Will be adjusted to support external schemas (PIDF-LO, etc.) by WG ◦ Sample EIDD XML instances need to be added to document by WG ◦ Once this work is completed, entire package will be released for internal and then public review ◦ EIDD specific registries need to be created and managed at designated site ◦ Expected approval and full implementation – 1 st quarter of 2016

What can it carry? Header has Incident ID, Timestamp and other critical information Agent information Agency information Split/Merge information Link information Incident information Call information Updated callback number information

What can it carry? (continued) Dispatch information Disposition information Notes Person information Additional Data information Vehicle information Location information Emergency Resource information Alarms and Sensors Data

Test Events IJIS/APCO Springboard initiative ◦ Over 15 public safety vendors participating ◦ Primary focus is CAD to CAD data exchanges ◦ IJIS will create EIDD use cases and implement a test harness for each use case ◦ Participating vendors will exchange EIDDs through test harness ◦ IJIS will provide feedback to WG on any recommended EIDD changes NENA ICE 7 event ◦ In the planning stage ◦ Will test NG9-1-1 related EIDD data exchanges ◦ Feedback provided to WG on any recommended EIDD changes

What is it used for? - some simple cases - Call arrives, EIDD is sent to the logger Call is transferred, EIDD is included Normal dispatch, EIDD included with request

HOW DOES IT WORK? Normal Operations EIDDs sent internally

What is it used for? Multi-agency Incident ◦ When any on agency’s state of the Incident changes, it updates the other Agencies by sending an EIDD containing the changes Outages, outside agency assistance

HOW DOES IT WORK? Minor outage affecting local PSAP EIDDs sent between PSAPs

HOW DOES IT WORK? Major outage affecting a large local area EIDDs sent between PSAPs and to Federal/State Emergency Management Agencies

What is it used for? Out of area dispatch: A PSAP receives a call from the brother of an accident victim. The call comes to the brother, who calls The incident is in California, the brother is in New York. While processing the call, the call is lost. The primary PSAP that received the call needs to inform the PSAP whose jurisdiction includes the incident location about the call. It sends an EIDD to the California PSAP.

What is it used for? Self Dispatch: A major incident is in progress. A small fire department decides that it will go help out. It sends an EIDD to the primary agency handling the incident that it is sending a crew and equipment. Consider both the case that the self-dispatching agency does know the IncidentID of the Incident it is self-dispatching to as well as the case that it does not.

What is it used for? Request for a specific service: A major fire is in progress and an additional long reach ladder truck is needed. The agency fighting the fire does not have the required unit. It requests availability of that piece of equipment from all of its neighbors by sending EIDDs to them, with the incident details and the specific request. Two agencies respond that they have the requested unit and can assist. The primary agency replies to one of them requesting dispatch and the other that it is not needed at this time.

Incident Data Exchange The IDE facilitates EIDD exchange Internally and Externally It is the front door of the PSAP for EIDDs So every Agency needs one Transport mechanisms being worked on

When are they sent? Any significant change in Incident status triggers an EIDD Updates contain just the changes Any EIDD that is sent must be logged How might this impact monitoring and reporting?

What about limiting updates? You should be able to subscribe to Incident updates when you need to. You should also be able to “throttle” updates per your needs

Querying Incident Status You may want to query for the status of an Incident – everything that is known This query may be internal or external It may or may not be followed by a subscription to updates

What about controlling content? A major incident is in progress. The policy of an agency handling the event is to notify the press of such incidents. However, the content of the EIDD is different for the press than it would be for another agency getting EIDDs. The press recipient EIDD has fewer elements than the normal EIDD the agency would send.

What about controlling content? Applies to EIDDs sent to other agencies as well. What can/should you send? What are the consequences of sending data, or of not sending it? Next, we’ll discuss policy and statutory implications

What are the issues? Who gets what? What can be shared? Who controls data access?

What about collaboration? A “Collaboration” Functional Element is defined for the PSAP – it will support sending EIDDs, media, etc. Should help with mutual aid, but what are the issues?

EIDDs to Responders A standardized container Will allow interoperability with Mobile Computer Systems, and other devices What are the issues?

Questions / Comments ?