introduction & problem description

EDXL Specifications Are Key to Net-Centric Interoperability for NCOIC

Rapid Response-Humanitarian Activities

Net-Centric Operations Industry Consortium (NCOIC)

Emergency ServicesOperational

Net-Centric Pattern

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

1

2

Introduction & Problem DescriptionThe 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

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


4

Playbook ApproachStep by Step Walkthrough of IncidentShows What Service Needs to be Deployed at each Phase

of an IncidentUses SOA Ecosystem Paradigm in Easy to Understand

Pragmatic CommunicationsBuilds on User Experience over Time

Continuous Improvement Built InIncludes After Action AnalyticsCurrently not Planned, but Needs to be Done—Fits Game

Approach


5

One Structure for All EDXL-Based Emergency Services


6

Net-Centric PrinciplesExplicitness—Emphasize Clarity & PrecisionUbiquity—Use Technologies with Wide AcceptanceDynamism—Emphasize AdaptabilityGlobalism—Use Terms & Data that’s Understood WidelyRelationship Management—Speak to your Audience’s

InterestsPragmatism—Emphasize What Works.Entity Primacy—Emphasize the Functionality of the Service.


7

ActorsEmergency 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


8

Common Operating Picture (COP): Single Gateway: All Services


9

Network Challenge: Combine Mobile Ad-hoc Networks (MANETs) with DHS-FEMA OPEN Style

ArchitectureMaximum Simplicity, Flexibility & AdaptabilityAccess Control NecessarySingle COP NecessaryEDXL-DE Core Routing Functionality


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.


11

Suggested Emergency Services Framework


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/




introduction & problem description

Documents

edxlbased emergency

edxl messages

emergency communication

edxl suite of specifications

edxlresource messaging

service needs

netcentric interoperability

distinct service