Approved For Public Release. Distribution Unlimited. Case #09-4342 IC.NET (Incident Command Net) Don...

Approved For Public Release. Distribution Unlimited. Case #09-4342

IC.NET(Incident Command Net)

Don McGarry • E146315-838-2669 • [email protected]

First Responder Collaboration & Integration

© 2009 The MITRE Corporation. All rights reservedApproved For Public Release. Distribution Unlimited. Case #09-4342

My Background

Practicing Paramedic in New York State since 2001– 3 years full-time– Currently part-time

Paramedic Instructor for State University of New York Upstate Medical University

FEMA certified in Incident Command System, National Incident Management System, & National Response Framework

Ph.D. Candidate in Electrical & Computer Engineering – Syracuse University

2


The Problem

Hazard on I-81 Bridge. All vehicles

enter from Mattydale exit.

Voice over Radio /Chat Message

Voice / Telephone

Voice / Telephone

Voice / TelephoneVoice / Telephone

Voice over Radio /Dispatch Message




County EMS Unit

County EMS Dispatch

County FireDispatch

County PDDispatch

City FireDispatch

City EMSDispatch

County PD Unit

County FD UnitCity FD Unit

City EMS Unit


IC.NET Problem Statement

Incident Managers rely on radio communication & handwritten notes/reports for Situational Awareness during large scale events– Difficult to maintain a common operating picture– In-briefing of new staff is cumbersome– Information is sent ad-hoc to third & forth responders

Most regions have software-based Computer Aided Dispatch (CAD) or disaster management systems with computers in field units– Systems are generally not interoperable among regions– Existing standards are narrow in scope, or are too

heavyweight to be used during large scale events– Field sensor data is not sent on a real-time basis through an

open platform

4


Incident Management Spectrum

* Leonard, H. B. and Howitt, A. M., Against Desperate Peril: High Performance in Emergency Preparation and Response, forthcoming in Communicable Crisis, edited by D. E. Gibbons. Leonard and Howitt, professors at Harvard’s Kennedy School of Government, have researched the characteristics of novel crises and have distinguished sudden crises from emergent crises.

House Fires2-Vehicle Accidents

Wild FiresN-Vehicle Accidents

Major EarthquakesMajor Hurricanes

Industrial AccidentsAirplane CrashesExplosions (bombs)

Pandemic FluCyber AttackAgriculture Attack

Nuclear Attack

Re

sp

on

se

Co

mp

lex

ity

Incident Complexity

Novel, Emergent*Predictable MostMost Least Least

• High situational awareness• Authority-based leadership• (Pattern) Recognitional decision-making• Modest customization• Execution of trained/practiced scripts

• Low situational awareness• Collaborative leadership• Improvisation and execution of

untested actions (Fault Tolerance)• Multiple levels of government• Strong political component• Dynamic Communities of Interest

We Need Tools That Scale

From This To This

http://en.wikipedia.org/wiki/Image:Spectrum4websiteEval.png


Constraint: Incident Command System

Pen & Paper / Organizational SystemA standardized on-scene emergency management construct

derived to ensure:– The safety of responders and others

– The achievement of tactical objectives

– The efficient use of resources

Represents "best practices" and has become the standard for emergency management across the country.

Is a key feature of the National Incident Management System (NIMS).

6


Our Focus: EMS Chain of Action

Size-Up(Assess)

TriageField

Treatment

Determine Disposition

Transport Disposition


Approach

Direct engagement with First Responders– Determine operational needs

– Monthly brainstorming sessions to evaluate content

– Analysis of real field systems and real field data

– Evaluation of proposed ideas to digitize business processes

Data modeling based on First Responder requirements– Identification of common data elements / exchange patterns

– Mapping to data elements to existing standards

– Existing standards evaluation

– Identification of data model gaps, development of placeholder loose couplers

Design & implementation of messaging platform– Routing and exposure messaging architecture

– Joint Interoperability testbed on MITRE DMZ

8


What Distinguishes IC.NET

Studies have been done on CAD system interoperability– These studies focused on vendor-specific CAD to CAD

communication, not general CAD to CAD interoperability or CAD to Mobile Data Terminal (MDT) communication

– MDT’s are the systems that First Responders know how to use and will bring them to a mutual aid event

– The First Responder Community and FEMA have expressed a desire to have interoperability at the MDT layer

– Research on how to apply data standards to this layer is needed along with a functional prototype for proof of concept

Most current systems don’t capture First Responder Sensor Data – This research will include ways to capture, transmit, and expose this data to a common operating picture (COP)

Existing systems use explicit delivery to individuals through manual configuration – IC.NET seeks to automate this process based on the state of the ICS structure along with predefined role information

9


Stakeholder Engagement

Central New York First Responders– Monthly feedback/brainstorming sessions

– Participation on Handshake / Testbed / Prototyping

LAFD / SDFD– Integration with legacy CAD

– Prototyping of interoperable CAD / MDT solution

– Integration with COTS vendors / CBRNE sensors

– Participation in incidents / exercises

OASIS– Research efforts can also produce technology transfer

– Provide SME and technical expertise to support DHS OIC

DHS– Support Virtual USA vision

– Support C2 interoperability for First Responder systems10


IC.NET FY10 Vision

11

LAFD

CAD

LAFD

MDT

ADASHIEOC

MITRE

MDT

SAFECBRN

E Sensor

s

Solace XML Route

r

COTS Vis.

WW Vis.

& C2

SD CAD

IC.NET Test Tool

LA Hospital

s

Evotec

HAITI

CMU

DM

IC.NET on MITRE DMZ / Joint Interoperability Testbed

New Vendor

s

OASIS Partner

s

Virtual USA

Images

First Responder On-Scene NetworkLifepak

12Digital Pen

Field Sensors

Google (VA) / ESRI

(VIPER)= via plugin

= via standards


General Architectural Requirements

Standard data “envelope” for distributing data– Simple to implement / Easy to use– Ability to distribute without processing content– Support for machine-based processing of metadata

Standard payloads to be carried in the envelope– Use cases developed from consultation with SME– Data model driven from use cases

Platform to route and expose payload data– Field-able prototype for proof of concept, interoperability

testing, validation of data model– 24x7 joint interoperability testbed with OASIS partners, COTS

vendors, DHS, and SPAWAR

12


Breakdown of EDXL-DE Structure

This diagram illustrates the basic components that makeup a DE message

DE messages are able to carry one or more payloads of data

IC.NET will use the OASIS standard EDXL v1.0 messageAll EDXL standards are designed to be carried in the DE

13

ED

XL-

DE

Mes

sage

“Type” of Message

Date / Time Message Sent

Sender Information

Recipient Information

Geographical Information

XML / Non-XML Payloads


IC.NET Payloads

EDXL-HAVE – Hospital Availability:– OASIS Standard v1.0– MITRE is currently supporting development of EDXL-DE v2.0

Situational Representation:– Incident & Unit Information– MITRE is currently supporting development of EDXL-SitRep

standard in OASIS

Tracking of Emergency Patients:– Patient, Triage, Treatment, and Transport Information– MITRE is will be supporting development of EDXL-TEP

standard once it reaches OASIS

Resource Messaging– Unit information– Unit tasking

14


Platform / Architecture Features

Research goal is to automate the exposure of data to the ICS structure based on pre-defined business processes

Leverage the “context” of the ICS structure to have message exposure system determine:– Who are the appropriate customers for a message?– What level of detail should I expose to each customer?

Message exposure system needs to examine both the content of the messages and the state command structure

Messages should be ingested and exposed using both pub/sub and request/reply messaging

Message delivery should be guaranteed, despite network conditions

Architecture needs to provide a simple mechanism to add both consumers & producers of data

15


IC.NET High Level Architecture

16


Dynamic Data Composability

17

LAFD

CAD

LAFD

MDT

ADASHIEOC

LA Hospitals

IC.NET

Field Hospital

Existing Users

1. New Field Hospital

wants to receive pertinent

data feeds

2. Field Hospital system

posts EDXL-DE /

Message to POST Endpoint

3. IC.NET system adds

field hospital to model

4. IC.NET returns xAL

object with dynamically

created REST & pub/sub

Endpoints for Field Hospital

5. Field Hospital will

now receive data feeds

from existing users


Dynamic Data Federation

18

IC.NET for

Local Jurisdiction

1. Local jurisdiction has incident

and wants to connect with other

neighboring jurisdictions

2. Routing rules are updated

and DE pub/sub endpoints

are connected

3. Other Local jurisdiction

now has bilateral C2 information

sharing capabilities

4. Local jurisdiction

now can receive all

of neighboring area’s

shared data

IC.NET in Neighboring

Area

Solace Router

FEMA DM-

OPEN

FEMAIPAWS

Network Layer

5. This works with ANY

EDXL-DE – based system!


Current Status

Technical– EDXL - Library implementation – Transition to Open Source

– EDXL - Test tool development – Transition to Open Source

– MEXL – Design & Library Implementation

– Ingestion / Exposure Services

– Routing service with pub/sub messaging

Outreach– OASIS Technical Committee Voting member

– Supporting technical effort for EDXL standards development

– Chair W3C Decisions Incubator Activity

– LAFD & SDFD Engagement

– Interoperability Testbed

– DHS / FEMA Engagement

19


IC.NET – Incident Command Net

ObjectivesPrincipal Investigators Donald McGarry

Organizations E146

HLSC / SEDI

Level of Effort 1.8 Staff Years

Status: New

Research & develop a data model for the First Responder Domain

Develop enterprise messaging services to support dynamic message routing and orchestration

Develop agile end-user applications to support changing and expanding National Response events for enhanced situational awareness

Participate in Mass Casualty Incident Drills

Activities

Create better situational awareness for Incident Command & Supervising Facilities

Develop prototype tools for National Emergency Response Scenarios

Drive standards development and adoption for / with DHS


IC.NET DEMO

21


References

FEMA (2008). National Response Framework. Retrieved from the FEMA Web site: http://www.fema.gov/pdf/emergency/nrf/nrf-core.pdf

Gorman, J. (2005). Parlez | UML. Driving Development with Use Cases. Retrieved from the ParlezUML Web site: http://www.parlezuml.com/tutorials/usecases/usecases.pdf

Jain, S. et. al. (2007). Towards Standards For Integrated Gaming And Simulation For Incident Management. SCSC.

Truong, H. et. al. (2009). On Modeling, Collecting and Utilizing Context Information for Disaster Responses in Pervasive Environments. CASTA ‘09.

United States Department of Homeland Security [DHS] (2009). Emergency Data Exchange Language (EDXL) Project Initiation Document (PID) For the Tracking of Emergency Victims (EDXL-TEV) Messaging Standard PHASE I - Tracking of Emergency Patients (EDXL-TEP). Retrieved from the Evotec inc. Web site: http://www.evotecinc.com/TEP/index.php?dir=&file=EDXL-TEP%20Project%20Initiation%20Document%20%28PID%29%20v4%201.pdf

22

http://www.fema.gov/pdf/emergency/nrf/nrf-core.pdf

http://www.parlezuml.com/tutorials/usecases/usecases.pdf

http://www.evotecinc.com/TEP/index.php?dir=&file=EDXL-TEP%20Project%20Initiation%20Document%20(PID)%20v4%201.pdf

http://www.evotecinc.com/TEP/index.php?dir=&file=EDXL-TEP%20Project%20Initiation%20Document%20(PID)%20v4%201.pdf


References

Brady, T. (2003). Emergency Management: Capability Analysis of Critical Incident Response. Proceedings of the 2003 Winter Simulation Conference.

Chen, R. et. al. (2008). Coordination in Emergency Response Management. Communications of the ACM, 51(5), 66-73

Chipman, R. et. al. (2008). Network Based Information Sharing Between Emergency Operations Center. IEEE Xplore.

Emergency Interoperability Consortium [EIC] (2009). The Emergency Interoperability Consortium. Retrieved from the EIC Web site: http://www.eic.org/

Fawcett, Dr. J (2009). Syracuse University. UML Notation. Retrieved from the Syracuse University Web site: http://www.ecs.syr.edu/faculty/fawcett/handouts/cse681/presentations/notation.ppt

Federal Emergency Management Agency [FEMA] (2009). About the National Incident Management System (NIMS). Retrieved from the FEMA Web site: http://www.fema.gov/emergency/nims/AboutNIMS.shtm

FEMA (2009). Disaster Management Interoperability Services – Open Platform for Emergency Networks (OPEN). Retrieved from the Disaster Help Web site: http://www.disasterhelp.gov/disastermanagement/open/index.shtm

FEMA (2008). Incident Command System (ICS), Review Materials. Retrieved from the FEMA Independent Study Web site: http://training.fema.gov/EMIWeb/IS/ICSResource/assets/reviewMaterials.pdf

23

http://www.eic.org/

http://www.ecs.syr.edu/faculty/fawcett/handouts/cse681/presentations/notation.ppt

http://www.fema.gov/emergency/nims/AboutNIMS.shtm

http://www.disasterhelp.gov/disastermanagement/open/index.shtm

http://training.fema.gov/EMIWeb/IS/ICSResource/assets/reviewMaterials.pdf


References

FEMA (2008). IS-100 Introduction to Incident Command System ICS-100 Instructor & Student Guide. Retrieved from the FEMA Independent Study Web site: http://training.fema.gov/EMIWeb/IS/is100alst.asp

FEMA (2008). IS-200 ICS for Single Resources and Initial Action Incidents ICS-200 Instructor & Student Guide. Retrieved from the FEMA Independent Study Web site: http://training.fema.gov/EMIWeb/IS/is200alst.asp

FEMA (2009). IS-700 NIMS An Introduction Instructor & Student Guide. Retrieved from the FEMA Independent Study Web site: http://training.fema.gov/EMIWeb/IS/is700alst.asp

Leonard, H. B. and Howitt, A. M., Against Desperate Peril: High Performance in Emergency Preparation and Response, forthcoming in Communicable Crisis, edited by D. E. Gibbons. Leonard and Howitt, professors at Harvard’s Kennedy School of Government, have researched the characteristics of novel crises and have distinguished sudden crises from emergent crises.

Mulgund, et. al. The MITRE Corp. (2008). N2CI Architecture.

Organization for the Advancement of Structured Information Standards (OASIS) (2005). Common Alerting Protocol (CAP) 1.1 OASIS Standard. Retrieved from the OASIS Web site: http://www.oasis-open.org/committees/download.php/15135/emergency-CAPv1.1-Corrected_DOM.pdf

OASIS (2006). Emergency Data Exchange Language Distribution Element (EDXL-DE) 1.0 OASIS Standard. Retrieved from the OASIS Web site: http://docs.oasis-open.org/emergency/edxl-de/v1.0/EDXL-DE_Spec_v1.0.pdf

24

http://training.fema.gov/EMIWeb/IS/is100alst.asp



http://www.oasis-open.org/committees/download.php/15135/emergency-CAPv1.1-Corrected_DOM.pdf

http://www.oasis-open.org/committees/download.php/15135/emergency-CAPv1.1-Corrected_DOM.pdf

http://docs.oasis-open.org/emergency/edxl-de/v1.0/EDXL-DE_Spec_v1.0.pdf


References

OASIS (2008). Emergency Data Exchange Language Hospital Availability Exchange (EDXL-HAVE) 1.0 Public Review Draft. Retrieved from the OASIS Web site: http://docs.oasis-open.org/emergency/edxl-have/pr05/emergency_edxl_have-1.0-spec-pr05.pdf

OASIS (2008). Emergency Data Exchange Language Resource Messaging (EDXL-RM) 1.0 Public Review Draft. Retrieved from the OASIS Web site: http://docs.oasis-open.org/emergency/edxl-rm/v1.0/pr02/EDXL-RM-SPEC-V1.0.pdf

OASIS (2009). Emergency Data Exchange Language (EDXL) Requirements Statement and draft Messaging Specification for the Situation Reporting Messaging Standard (EDXL-SitRep). Retrieved from the OASIS Web site: http://www.oasis-open.org/apps/org/workgroup/emergency-msg/download.php/32999/EDXL-SitRep-Rqmts-MsgSpec020209.pdf

OASIS (2009). The Distribution Element:The Basic Steps to Package and Address Your Emergency Information. Retrieved from the OASIS Web site: http://www.oasis-open.org/apps/org/workgroup/emergency/download.php/34264/EDXL-DE-Basics-WhitePaper-18Aug09-r2.doc

FEMA (2008). IS-800 National Response Framework, An Introduction Instructor & Student Guide. Retrieved from the FEMA Independent Study Web site: http://training.fema.gov/EMIWeb/IS/is800blst.asp

FEMA (2008). National Incident Management System. Retrieved from the FEMA Web site: http://www.fema.gov/emergency/nims/

FEMA (2009). National Incident Management System Supporting Technology Evaluation Program. Retrieved from the NIMS-STEP Web site: https://www.nimsstep.org/Default.asp

25

http://docs.oasis-open.org/emergency/edxl-have/pr05/emergency_edxl_have-1.0-spec-pr05.pdf

http://docs.oasis-open.org/emergency/edxl-have/pr05/emergency_edxl_have-1.0-spec-pr05.pdf

http://docs.oasis-open.org/emergency/edxl-rm/v1.0/pr02/EDXL-RM-SPEC-V1.0.pdf

http://www.oasis-open.org/apps/org/workgroup/emergency-msg/download.php/32999/EDXL-SitRep-Rqmts-MsgSpec020209.pdf

http://www.oasis-open.org/apps/org/workgroup/emergency-msg/download.php/32999/EDXL-SitRep-Rqmts-MsgSpec020209.pdf

http://www.oasis-open.org/apps/org/workgroup/emergency/download.php/34264/EDXL-DE-Basics-WhitePaper-18Aug09-r2.doc

http://www.oasis-open.org/apps/org/workgroup/emergency/download.php/34264/EDXL-DE-Basics-WhitePaper-18Aug09-r2.doc

http://training.fema.gov/EMIWeb/IS/is800blst.asp

http://www.fema.gov/emergency/nims/

https://www.nimsstep.org/Default.asp


BACKUP SLIDES

26


Industry Partners

27


First Responder Partners

28


MITRE Partners

Warfighter Widgets – Kelly Gerschefske E54ACoT for DNDO Messaging – Paul Gonsalves E146Digital Pen – Qian Hu – G063EREN – David Siegrist – G154SLFC Study – Kim Warren – N010CID Support – Gerardo Garcia – N010VIPER Support – Mike French – N161Breckford / Decision Support – Percy Schmidt – E541Virtual USA Support – Neal Rothleder – E541

29


What is IC.NET?

IC.NET (Incident Command Net)– Original research idea proposed by PI during FY09 MIP– MITRE MSR starting in FY10– Research idea to bring interoperability to First Responders

Objectives– Operational needs from First Responders– Data modeling– Standards development / support– Common platform for data exchange– Platform to drive standards adoption

30


Future Work

Expand Data Model– Fire Units– Police Units– Police Information

Connection to additional “interested parties”– Local government– CI/KR– DOT

Handling LEIS / CUIConnection between DoD / Civilian SystemsExpanding data model to include wider band of incident

command system“Intelligent” message processing routing

31


Underlying Architecture Issues

32

CAD

MDT

Incident Managemen

t

COTS / Custom Vis.

HAZMATSenso

r Data

IMINT

ICS Tools

SA / COP Tools

COTS / Custom Vis.

COTS / Custom Vis.

COTS / Custom Vis.

COTS / Custom Vis.

COTS / Custom Vis.

What about???

Cellular

Smartphones

Twitter WebUnanticipated

Users

New Producers New Consumers

Proprietary / Legacy / Non-Standard Data Formats


Research Topics / Questions

Development & analysis of the data model for the First Responder Domain– General Breadth Analysis– Specific Depth Analysis for EMS

Do existing standards cover the data model?How can we improve existing standards / develop

standards to fill gaps?How can we connect systems that are currently disparate

using standards?How do we orchestrate data flow between systems in a

system that is feasible for First Responder deployment?How can we apply CCoD concepts to support the First

Responder mission?

33


Sample Triage Algorithm

No more than 30 seconds per patient

No treatment other than airway positioning and major bleeding control

Patients categorizes into 3 priorities or dead

Individuals can also be affected persons– Not injured but

affected by disaster

34

Approved For Public Release. Distribution Unlimited. Case #09-4342 IC.NET (Incident Command Net) Don...

Documents

Transcript of Approved For Public Release. Distribution Unlimited. Case #09-4342 IC.NET (Incident Command Net) Don...