1. 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

2. 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

3. 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

4. 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

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

6. 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

7. 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

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

9. 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

10. 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

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

12. 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_servi ces_operational_pattern/ https://www.ncoic.org/technology/deliverables/emergency_servi ces_operational_pattern/ 3/25/2014 NCOIC Emergency Services Operational Pattern for OASIS Emegency Management TC 12