1 / 26

Using Incident Management Message Sets

Using Incident Management Message Sets. October 13, 1999 Andy Schoka Fred Dion. Briefing Goal. Build a constituency for the use of “tabletop exercises” to further the understanding of the interactions between and among the IEEE P1512 Standard’s Incident Management message sets

sheryl
Download Presentation

Using Incident Management Message Sets

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using Incident Management Message Sets October 13, 1999 Andy Schoka Fred Dion

  2. Briefing Goal • Build a constituency for the use of “tabletop exercises” to further the understanding of the interactions between and among the IEEE P1512 Standard’s Incident Management message sets • Intent is to support and help advance the development of IM “tabletop exercises” by fostering awareness, content familiarization and completeness, and application

  3. Approach • Develop and implement Incident Management electronic Table Top (e-TTop) exercises • Develop incident event scenarios starting with simple ones and going to progressively more involved ones • For a scenario, establish “players”, their simulated “organization”, and their roles and provide them the scenario and the message sets • Scenarios structured in time and activity/action with participation across the Internet

  4. Approach (continued) • Play • Exercise triggered via first sent message • Players respond per their responsibilities and information in received messages • Players decide whether or not they need to send message(s), to whom, and with what content • Players keep notes and comments • Messages are logged • Run to completion

  5. Approach (concluded) • Assess scenario: i.e.,operationally, within its limits, did it provide a useful context for exercising the message sets? • Evaluate the messages used in the exercise • Completeness • Effectiveness • Facileness • Utility • Identify potential improvements and enhancements as well problem areas and disconnects

  6. Incident Management Phases • Notification • Frequently via telephony • 911/Public Safety Answering Point (PSAP) • Coming: Automated Crash Notification (ACN) • Confirmation • Response, i.e.,dispatching resources • Traffic and routing information • Assembling of resources • Clearing the incident • Drawdown, i.e., releasing resources • Closure, i.e., ending the incident

  7. To Be Noted The graphics that follow this slide should be interpreted as follows. The icons used in the graphics represent the organizations that house and/or command the resources depicted by the icons. The Incident Management Messages flow between those organizations’ message centers/dispatches. Therefore, the Incident Management Messages shown going to an icon should be understood as going to the message center/dispatch that houses the depicted resource, not the resource itself. That message center/dispatch will send information to the requisite resource(s) by word-of-mouth, telephone, wireless radio, or any other means that suffice. For example: Law Enforcement Hqs Dispatch Cruiser wireless IM Msg comm. Dispatch sends Incident Management message to Police Dispatch which then contacts a police cruiser and provides it information and instructions. This briefing is focused on the center-to-center IM messaging and does not address the other communications.

  8. e-TTOP EXERCISE Phases: notification, confirmation PSAP ACN Citizen Crash info Voice conversation and GPS Accident at... Location vehicle TMC New Incident Incident Desc. Event Msg (NIE) Call in 1 1 1 Msg (IDX) NIE Msg. 1 1 IDX Msg. Law Enforcement NIE Msg. 1 NIE Msg. Fire and Rescue INTERNET 1 1 IDX Msg. 1 IDX Msg. NIE Msg. NIE Msg. 1 1 IDX Msg. 1 1 IDX Msg. Emergency Medical Services Hospital Emergency Dept

  9. New Incident Event (NIE) Net Message Date: 7/28/1999 From: Dispatch To: EMS, FIRE, HOSP, Police, Traffic Management Center Msg ID: 4 Msg Sequence #: 1 Header: Incident ID #: SCP1234567 Optional Items: Basics: Incident Location, LRMS ANY: 15 meters south of State Highway 57/County Road 634 intersection. Estimate 1, Reliability: 100% (GPS location via Automated Crash Notification) and (county official witness) Status: 1:15 PM car exiting off eastbound lane state highway 57 onto county road 634 southbound crossed the road, hit a telephone pole, came to a stop with car on the shoulder of the road and intruding about two meters into the northbound lane. Telephone pole damaged. Impact (opt): Lane Configuration: Lanes blocked: northbound lane Shoulders blocked: right shoulder northbound lane Route Sets (detours): Time (issue stamp): Time (generalized): 1:17 PM Count: 0 Issue-type (choose one of the following; create, update, or delete): create Author (opt): John Doe Qual (opt): Reliability: 100%

  10. Incident Description (IDX) Net Message Date: 7/28/1999 From: Dispatch To: EMS, FIRE, HOSP, Police, Traffic Management Center Msg ID: 1 Msg Sequence #:1 Header: Incident #: SCD1234567 Optional Items: Basics (opt): Incident Location, LRMS ANY: 15 meters south of State Highway 57/County Road 634 intersection. Estimate 1, Reliability: 100% (GPS location via Automated Crash Notification) and (county official witness) Status: Car driver injured/unconscious Optional Items: Time (opt) (generalized, UTC simple time): 1:19PM IDX Message Parts: event-times; description; severity; vehicles; vehMAYDAY; impact; reports; response; assigned-Resources; scene-staging; evacuation; facilities; file-Transfer; ... Assigned Resources(9): EMS, Fire, HOSP, Police Time (issue stamp): Time (generalized): 1:19 PM Count: 0 Issue-type (choose one of the following; create, update, or delete): create Author (opt): John Doe

  11. IDX Update Messages e-TTOP EXERCISE Phases: response, assembling resources (1) PSAP Public Incident ACN Description Msg. 1 “Accident at ….” TMC vehicle Public Affairs 2 Response 2 IDX Msg. Hqs. Law Enforcement . . Fire and Rescue 2 INTERNET 2 IDX Msg. IDX Msg. 2 IDX Msg. 2 IDX Msg. Emergency Medical Services Hospital Emergency Dept

  12. Incident Description (IDX) Net Message Date: 7/28/1999 From: EMS [ FIRE, HOSP, Police, TMC, send, separately, their similar messages] To: Dispatch, FIRE, HOSP, Police, Traffic Management Center Msg ID: 1 Msg Sequence #:2 Header: Incident #: SCP1234567 Optional Items: Basics (opt): Incident Location, LRMS ANY: 15 meters south of State Highway 57/County Road 634 intersection. Estimate 1, Reliability: 100% (GPS location via Automated Crash Notification) and (county official witness) Status: Car driver injured/unconscious Optional Items: Time (opt) (generalized, UTC simple time): 1:21 PM IDX Submessage (response) [Response Status Other (Text)]: EMS being dispatched to incident location Time (issue stamp): Time (generalized): 1:21 PM Count: 1 Issue-type (choose one of the following; create, update, or delete): update Author (opt): EMS dispatch

  13. e-TTOP EXERCISE Phases: clearing the incident (1) PSAP Public Incident ACN Description Msg. 2 “Accident at ….” TMC vehicle Public Affairs IDX Update 3 IDX Msg. 3 Traffic and Hqs. Law Routing info Enforcement . . Fire and Rescue 3 INTERNET 3 IDX Msg. Update IDX Msg. Update 3 IDX Msg. 3 IDX Msg. Update Update Emergency Medical Services Hospital Emergency Dept

  14. Incident Description (IDX) Net Message Date: 7/28/1999 From: Traffic Management Center To: Dispatch, EMS, FIRE, HOSP, Police Msg ID: 1 Msg Sequence #:3 Header: Incident #: SCP1234567 Optional Items: Basics (opt): Incident Location, LRMS ANY: 15 meters south of State Highway 57/County Road 634 intersection. Estimate 1, Reliability: 100% (GPS location via Automated Crash Notification) and (county official witness) Status: Car driver injured/unconscious Optional Items: Time (opt) (generalized, UTC simple time): 1:22 PM IDX Message Parts: event-times; description; severity; vehicles; vehMAYDAY; impact; reports; response; assigned-Resources; scene-staging; evacuation; facilities; file-Transfer; ... IDX Submessage (impact, route) (Text): Proposed route all services; take County 611 west, 672 north, State 57 east, to incident location at 634 Time (issue stamp): Time (generalized): 1:22 PM Count: 2 Issue-type (choose one of the following; create, update, or delete): update Author (opt):TMC dispatch

  15. e-TTOP EXERCISE Phase: clearing the incident (2) Dispatch Public Incident TMC Desc. msg. Update 3 Fire Company released IDX Incident Desc. 3 4 Msg (IDX) 4 Update Update Public Affairs Fire and Rescue IDX INTERNET 4 Law Release Fire Company 4 IDX Update IDX Update Enforcement 4 4 Emergency Medical IDX Update Hospital Emergency Services Dept.

  16. Incident Description (IDX) Net Message Date: 7/28/1999 From: Dispatch To: EMS, FIRE, HOSP, Police, Traffic Management Center Msg ID: 1 Msg Sequence #: 4 Header: Incident #: SCP1234567 Optional Items: Basics (opt): Incident Location, LRMS ANY: 15 meters south of State Highway 57/County Road 634 intersection. Estimate 1, Reliability: 100% Status: No fire hazard, no spills, no HAZMAT; fire company has been released Optional Items: Time (opt) (generalized, UTC simple time): 1:55 PM IDX Message Parts: event-times; description; severity; vehicles; vehMAYDAY; impact; reports; response; assigned-Resources; scene-staging; evacuation; facilities; file-Transfer; ... Assigned Resources(9): EMS, Fire, Hospital, Police Time (issue stamp): Time (generalized): 1:42 PM Count: 3 Issue-type (choose one of the following; create, update, or delete): update Author (opt): John Doe

  17. e-TTOP EXERCISE Phases: clearing the incident (3) PSAP Public Incident Description Msg. 4 “Accident at ….” TMC Public Affairs IDX Update 5 IDX Msg. 5 Traffic and Hqs. Law Routing info Enforcement . . Fire and Rescue 5 INTERNET 5 IDX Msg. Update IDX Msg. Update 5 IDX Msg. 5 IDX Msg. Update Update Emergency Medical Services Hospital Emergency Dept

  18. Incident Description (IDX) Net Message Date: 7/28/1999 From: Traffic Management Center To: Dispatch, EMS, FIRE, HOSP, Police Msg ID: 1 Msg Sequence #:5 Header: Incident #: SCP1234567 Optional Items: Basics (opt): Incident Location, LRMS ANY: 15 meters south of State Highway 57/County Road 634 intersection. Estimate 1, Reliability: 100% (GPS location via Automated Crash Notification) and (county official witness) Status: Car driver injured/unconscious Optional Items: Time (opt) (generalized, UTC simple time): 1:55 PM IDX Message Parts: event-times; description; severity; vehicles; vehMAYDAY; impact; reports; response; assigned-Resources; scene-staging; evacuation; facilities; file-Transfer; ... IDX Submessage (impact, route) (Text): Proposed route all services; County 634 south open to official vehicles Time (issue stamp): Time (generalized): 1:55 PM Count: 4 Issue-type (choose one of the following; create, update, or delete): update Author (opt):TMC dispatch

  19. e-TTOP EXERCISE Phase: clearing the incident (concluded) Dispatch Public Incident TMC Desc. msg. 5 Emergency Med. at hospital IDX Incident Desc. 3 6 Msg Emergency Med at hospital 6 Update Public Affairs 6 IDX INTERNET Update Law 6 IDX Update IDX IDX Enforcement 6 Update 6 Update Emergency Medical Hospital

  20. Incident Description (IDX) Net Message Date: 7/28/1999 From: Dispatch To: EMS, FIRE, HOSP, Police, Traffic Management Center Msg ID: 1 Msg Sequence #: 6 Header: Incident #: SCP1234567 Optional Items: Basics (opt): Incident Location, LRMS ANY: 15 meters south of State Highway 57/County Road 634 intersection. Estimate 1, Reliability: 100% Status: EMS has arrived at HOSP Optional Items: Time (opt) (generalized, UTC simple time): 2:14 PM IDX Message Parts: event-times; description; severity; vehicles; vehMAYDAY; impact; reports; response; assigned-Resources; scene-staging; evacuation; facilities; file-Transfer; ... Assigned Resources(9): EMS, Fire, Hospital, Police Time (issue stamp): Time (generalized): 2:14 PM Count: 5 Issue-type (choose one of the following; create, update, or delete): update Author (opt): John Doe

  21. e-TTOP EXERCISE Phases: drawdown Dispatch Public Incident TMC Desc. msg. 6 Incident cleared IDX Incident Desc. 7 3 Msg: release 7 resources Update Public Affairs Fire and 7 Rescue IDX INTERNET Update Law 7 Release IDX Police 7 Update Release 5 7 5 Emergency Emergency Medical Enforcement Medical Hospital

  22. Incident Description (IDX) Net Message Date: 7/28/1999 From: Dispatch To: EMS, FIRE, HOSP, Police, Traffic Management Center Msg ID: 1 Msg Sequence #:7 Header: Incident #: SCP1234567 Optional Items: Basics (opt): Incident Location, LRMS ANY: 15 meters south of State Highway 57/County Road 634 intersection. Estimate 1, Reliability: 100% Status: release EMS and Police Optional Items: Time (opt) (generalized, UTC simple time): 2:52 PM IDX Message Parts: event-times; description; severity; vehicles; vehMAYDAY; impact; reports; response; assigned-Resources; scene-staging; evacuation; facilities; file-Transfer; ... Assigned Resources(9): EMS, Fire, Hospital, Police Time (issue stamp): Time (generalized): 2:52 PM Count: 6 Issue-type (choose one of the following; create, update, or delete): update Author (opt): John Doe

  23. e-TTOP EXERCISE Phases: closure Dispatch Public Incident TMC Desc. msg. 7 Incident closed Close Incident Event 3 1 Msg (CIE) 1 Public Affairs Fire and 1 Rescue INTERNET CIE Msg. Law 1 CIE Msg. CIE Msg. Enforcement 1 CIE Msg. 1 Emergency Medical Hospital

  24. Close Incident Event (CIE) Net Message Date: 7/28/1999 From: Dispatch To: EMS, FIRE, HOSP, Police, Traffic Management Center Msg ID: 7 Msg Sequence #: 1 Header: Incident ID #: SCP1234567 Optional Items: incident closed, Dispatch is ending its activity/action in re this incident event Time (issue stamp): Time (generalized): 3:12 PM Count: 0 Issue-type (choose one of the following; create, update, or delete): create Author (opt): John Doe

  25. Message Time/Flow Release fire company Dispatch Summon resources M e s s a g e s Response msgs Dispatch Incident report Time

  26. Implementation and Resources • Implementation • Develop message templates (possibly in html) • Internet (e-TTop) • Web site • benefits • Facilitation (coordinates player interaction) • Resources • People (and their TIME!) • Hosts(participants and organizations) • Hardware/software • PCs, printers, telephones, fax machines, fast ISP • Browsers, html capability

More Related