1 / 12

Introduction & Problem Description

Net-Centric Operations Industry Consortium (NCOIC) Emergency Services Operational Net-Centric Pattern. EDXL Specifications Are Key to Net-Centric Interoperability for NCOIC Rapid Response-Humanitarian Activities. Introduction & Problem Description.

maeve
Télécharger la présentation

Introduction & Problem Description

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. Net-Centric Operations Industry Consortium (NCOIC) Emergency ServicesOperationalNet-Centric Pattern EDXL Specifications Are Key to Net-Centric Interoperability for NCOIC Rapid Response-Humanitarian Activities NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC

  2. Introduction & Problem Description The complexity and difficulty of emergency communicationsamong 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. NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC

  3. Why EDXL? 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 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC

  4. Playbook Approach • 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 Done—Fits Game Approach NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC

  5. One Structure for All EDXL-Based Emergency Services NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC

  6. Net-Centric Principles Explicitness—Emphasize Clarity & Precision Ubiquity—Use Technologies with Wide Acceptance Dynamism—Emphasize Adaptability Globalism—Use Terms & Data that’s Understood Widely Relationship Management—Speak to your Audience’s Interests Pragmatism—Emphasize What Works. Entity Primacy—Emphasize the Functionality of the Service. NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC

  7. Actors • 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 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC

  8. Common Operating Picture (COP): Single Gateway: All Services NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC

  9. Network Challenge: Combine Mobile Ad-hoc Networks (MANETs) with DHS-FEMA OPEN Style Architecture Maximum Simplicity, Flexibility & Adaptability Access Control Necessary Single COP Necessary EDXL-DE Core Routing Functionality NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC

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

  11. Suggested Emergency Services Framework NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC

  12. Summary: Emergency Services • 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 https://www.ncoic.org/technology/deliverables/emergency_services_operational_pattern/ NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC

More Related