EDXL Specifications Are Key to Net- Centric Interoperability for NCOIC Rapid Response-Humanitarian Activities 3/25/2014 NCOIC Emergency Services Operational.

Slides:

Advertisements

Similar presentations

Using PHINMS and Web-Services for Interoperability The findings and conclusions in this presentation are those of the author and do not necessarily represent.

Advertisements

National HIT Agenda and HIE John W. Loonsk, M.D. Director of Interoperability and Standards Office of the National Coordinator Department of Health.

Service Oriented Architecture Reference Model

1 Emergency Response Management Systems (ERMS)versus(ERSM) Emergency Response Systems Management: Identifying the Critical Path to Improved Decision Support.

Disaster Management Civil-Military Coordination

SOA for EGovernment 1 Emergency Services Enterprise Framework: A Service-Oriented Approach Sukumar Dwarkanath COMCARE Michael Daconta Oberon Associates.

Homeland Security Information Network-Emergency Management (HSIN-EM) Fire Service Community Overview Technologies for Critical Incident Preparedness Conference.

SADC Course in Statistics Choosing appropriate methods for data collection.

IAEA Training in Emergency Preparedness and Response Module L-051 General Concepts of Exercises to Test Preparedness Lecture.

Overview of Web Services

IS-700.A: National Incident Management System, An Introduction

PROF. MAULIK PATEL CED, GPERI Mobile Computing Gujarat Power Engineering and Research Institute 1 Prepared By: Prof. Maulik Patel.

NIMS Resource Management IS-700.A – January 2009 Visual 5.1 NIMS Command and Management Unit 5.

Healthcare Emergency Coalitions: An Ebola Preparedness Perspective Michael Clark, MD J. Marc Liu, MD, MPH Medical Advisors-Wisconsin Hospital Emergency.

New River Valley Emergency Communications Regional Authority Purpose: Consolidate 911 Operations and Establish Regional Radio System to Improve Interoperability.

Southwest Florida. SW Florida MRC Major Activities Mass casualty events Mass prophylaxis clinics Disaster mental health Special needs shelters Public.

Overview of OASIS SOA Reference Architecture Foundation (SOA-RAF)

Connecting People With Information DoD Net-Centric Services Strategy Frank Petroski October 31, 2006.

OASIS Reference Model for Service Oriented Architecture 1.0

Notion of a Project Notes from OOSE Slides - modified.

Live dashboards for Progress built by anyone, available anywhere. Introducing DataPA OpenAnalytics Nick Finch CTO.

FIRE DEPARTMENT ORGANIZATION State of Georgia BASIC FIRE FIGHTER TRAINING COURSE.

Unit 3: Command & Control IC/IMT Interface

EMERGENCY MEDICAL SERVICES (EMS). Emergency Medical Services (EMS) Responsibilities Include Providing emergency medical aid, triage, and decontamination.

Desired Quality Characteristics in Cloud Application Development Leah Riungu-Kalliosaari.

The National Incident Management System Presented by Peter Shebell Department of Homeland Security NOTE: Each speaker may substitute his or her organization.

Technician Module 2 Unit 8 Slide 1 MODULE 2 UNIT 8 Prevention, Intelligence & Deterrence.

© TecSec® Incorporated 2003 Threat Notification Model for Federal, State and Local Authorities Threat Notification Model for Federal, State and Local Authorities.

Module 3 Develop the Plan Planning for Emergencies – For Small Business –

CSE 303 – Software Design and Architecture

1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.

COMCARE1 Emergency Services Enterprise Framework: A Service-Oriented Approach Sukumar Dwarkanath, Technical Director, COMCARE Emergency Services SDO Workshop.

Disasters and Emergencies The Role of The Chaplain in the world of Emergency Management.

. Traffic Flow Management System Benefits Flexibility for Future Growth: TFMS provides a modern software architecture to meet future growth and support.

111 Notion of a Project Notes from OOSE Slides – a different textbook used in the past Read/review carefully and understand.

Emergency Data Exchange Language (EDXL) International Free Open.

1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.

The School Nurse’s Role in Incidents. Visual 2 Emergency Procedure Development Nurses’ responsibilities may include:  Identifying potential problems.

Omaha – Council Bluffs 2010 Traffic Forum. What is Traffic Incident Management? Traffic Incident Management Refers to the coordinated, preplanned, procedures.

OASIS Organization for the Advancement of Structured Information Standards Emergency Management Presentation Guidelines.

2 October 2007 Improving Rapid Emergency First Response with SOA 4 th SOA for E-Government Conference 1 Improving Rapid Emergency Response Systems with.

Information Technology Division Executive Office for Administration and Finance Service Oriented Architecture An Enterprise Approach to Enabling the Business.

Chapter 2 Object-Oriented Paradigm Overview. Getting Acquainted with the Class Project Read the requirements specification carefully Make note of any.

Haiti Earthquake Earthquake in Haiti. Haiti Earthquake – After Action Review Search and rescue operations Overall safety and law enforcement Sustainment.

11 June 2009Connectivity Week – OASIS: Integrated Emergency Management1 Integrated Emergency Management Overview

National Incident Management System (NIMS)

3 Unit 3. 3  Discuss the purpose of the National Incident Management System (NIMS).  Discuss the utility of NIMS at a fire incident.  Describe the.

Session 161 National Incident Management Systems Session 16 Slide Deck.

© Drexel University Software Engineering Research Group (SERG) 1 The OASIS SOA Reference Model Brian Mitchell.

Components of an EMS System Information Adapted from:

Emergency Data Exchange Language (EDXL) Internationally Available Free Standards Open and Non-Proprietary.

OASIS Organization for the Advancement of Structured Information Standards Emergency Management Presentation Guidelines.

23 May 2006 SOA for E-Gov Interoperability at Work: Improving Rapid First Response 1 SOA for E-Government Interoperability at Work: Improving Rapid First.

NATIONAL INCIDENT MANAGEMENT SYSTEM Department of Homeland Security Executive Office of Public Safety.

Bringing DoD Technologies to Law Enforcement Applications James Sim Drakontas LLC NIJ Demonstration Project: Situational Awareness Tools.

Emergency Data Exchange Language (EDXL) Internationally Available Free Standards Open and Non-Proprietary.

Visual 1.1 G0191: ICS/EOC Interface Workshop. Visual 1.2 G0191: ICS/EOC Interface Workshop Unit 1: Course Introduction.

Service Oriented Architecture Enabling the Agile and Flexible Business of the 21 st Century.

Models of the OASIS SOA Reference Architecture Foundation Ken Laskey Chair, SOA Reference Model Technical Committee 20 March 2013.

Harris County Case Study.  Aligning plans with emergency support functions (ESFs) can facilitate an efficient and effective response to emergencies.

Center of Excellence PEACE OPERATIONS COMMAND & CONTROL AND COMMAND & CONTROL AND TRANSITION ISSUES Lt Col (R) John Derick Osman Center of Excellence in.

Communication, Documentation and Scene Safety

Second SDO Emergency Services Coordination Workshop

Emergency Management: Incident, Resource, and Supply Chain Management

Maturity by Type of Interoperability

High Level Architectural View

Service Oriented Architecture + SOAP

Prevention, Intelligence

Emergency Management: Incident, Resource, and Supply Chain Management

Themes for the future... Simple complex systems Well behaved systems

Presentation transcript:

EDXL Specifications Are Key to Net- Centric Interoperability for NCOIC Rapid Response-Humanitarian Activities 3/25/2014 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC 1

The complexity and difficulty of emergency communications among jurisdictions and between jurisdictions and the public require a balance between timeliness and completeness within the variety of messages (alerting, logistics, situational awareness, etc.) for rapid and accurate decision making. 3/25/2014 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC 2

Breaks Down into Appropriate Types of Communications (e.g. EDXL-CAP for Alerting, EDXL- Resource Messaging for Logistics, EDXL-HAVE for Hospital Availability Snapshots, etc). Each Emergency Communication Type Becomes a Distinct Service in Service Oriented Architecture (SOA) Ecosystem. Uses EDXL-DE for Routing all Emergency Communication Types for Consistency, Reliability & Trust/Security 3/25/2014 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC 3

Step by Step Walkthrough of Incident Shows What Service Needs to be Deployed at each Phase of an Incident Uses SOA Ecosystem Paradigm in Easy to Understand Pragmatic Communications Builds on User Experience over Time Continuous Improvement Built In Includes After Action Analytics Currently not Planned, but Needs to be DoneFits Game Approach 3/25/2014 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC 4

3/25/2014 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC 5

ExplicitnessEmphasize Clarity & Precision UbiquityUse Technologies with Wide Acceptance DynamismEmphasize Adaptability GlobalismUse Terms & Data thats Understood Widely Relationship ManagementSpeak to your Audiences Interests PragmatismEmphasize What Works. Entity PrimacyEmphasize the Functionality of the Service. 3/25/2014 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC 6

Emergency Responders Law Enforcement/Military Firefighters Emergency Medical Technicians Logistical Personnel Affected Public Non-Injured or Slightly-Injured, who may or may not need to be transported to shelter Injured requiring emergency medical triage, treatment and transport to a field hospital or community hospital IT Personnel Software Engineers or Providers Data Center technicians Emergency Mgt. Standards Developers 3/25/2014 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC 7

3/25/2014 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC 8

Maximum Simplicity, Flexibility & Adaptability Access Control Necessary Single COP Necessary EDXL-DE Core Routing Functionality 3/25/2014 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC 9

EDXL Can Keep It Simple. One Specification = One Service. Service Description Should Clearly Define What it Can Do. Also What it Cant Do. Having Different EDXL Specifications-Services Provides Flexibility and Adaptability. Jurisdictions can Pick & Choose as Needed. 3/25/2014 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC 10

3/25/2014 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC 11

Each EDXL Specification is Basis for One Emergency Service. Playbook Approach Provides Step by Step Aid for EDXL-Based Emergency Communications. Will Capitalize on Single Structure for all Services. All Communications use EDXL-DE. Single COP Unifies Interfaces to Individual Services. Will Satisfy both NCOIC and OASIS EM TC Purposes. Uses NCOIC Principles. Provides EDXL Training Platform. There are Engaging Challenges on Both Sides. Pattern available at ces_operational_pattern/ ces_operational_pattern/ 3/25/2014 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC 12