WIS3 Breakout #2 Emergency Management Panel 2014 Workshop on Information Sharing and Safeguarding Standards (WIS3) Elysa Jones, Chair OASIS Emergency Management Technical Committee OASIS Organization for the Advancement of Structured Information Standards Emergency Management Technical Committee Wade Witmer Deputy Director, Integrated Public Alert and Warning System (IPAWS) Division, National Continuity Programs Office, Department of Homeland Security Gary Ham Contract System Architect to FEMA IPAWS Don McGarry MITRE Contract Support to DHS Science & Technology

Emergency Management Prepare – Respond – Recover – Mitigate Television Radio Cell Phone Computer Home Phone Public Signage/Siren CAP Workshop 2013

EDXL Family of Standards Current EDXL Standards  Common Alerting Protocol (CAP)  EDXL-Distribution Element (DE)  EDXL-Hospital Availability Exchange (HAVE)  EDXL-Resource Messaging (RM) EDXL Standards Under Development  EDXL-Situation Reporting (SitRep)  EDXL-Tracking of Emergency Patients (TEP)  EDXL-Tracking of Emergency Clients (TEC)  EDXL-Reference Information Model (RIM)

EDXL Standards Development Process

The Integrated Public Alert and Warning System (IPAWS) Get Alerts, Stay Alive 2014 Workshop on Information Sharing and Safeguarding Standards (WIS3) Wade Witmer FEMA IPAWS Division

What is IPAWS? IPAWS is a National System for Local Alerting –supports sending of local alerts from local, state, tribal, territorial officials during emergencies and from the President in the event of a catastrophic national emergency. –provides authenticated emergency alert and information messaging from emergency officials to the public through: radio and television via the Emergency Alert System cellular phones via Wireless Emergency Alerts NOAA All Hazards Weather Radio via IPAWS-NOAA gateway Internet applications and websites via the IPAWS Public Feed –FEMA, tasked by DHS, is responsible for: Development, operation, integration and maintenance of the IPAWS which includes the EAS, WEA, NOAA HazCollect, and public alerts feed components plus future connections for alerting TBD. 6

7 IPAWS is Not: –Not a subscription based mass notification system –Not an ETN or reverse dial phone system –Not an SMS or sign up system –Not a paging or limited distribution notification system e.g. can’t send a recall notice to a select group of employees IPAWS is for: –Emergency Alert and Warning information i.e. - urgent information impacting public safety e.g. - not meant for messaging about changes to trash collection schedule –Alerting all citizens in an given area IPAWS Can: –Activate EAS Radio and TV stations –Alert all (WEA capable) cell phones in a defined geographic area, even when cell networks are congested –Send a warning message for broadcast over NOAA Weather Radio IPAWS does not know your phone number or your location!

8 Public end-user devices IPAWS Architecture – emergency alert information sharing enabled by data standards Alert Dissemination Channels (private sector systems) Emergency Alert System Wireless Emergency Alerts Internet Services NOAA HazCollect Local State Territorial Tribal Federal* ETN NWS CAP messages IPAWS compliant CAP Alert Origination Tools IPAWS OPEN Future Technologies? Alerting Authorities * Includes NOAA State / Local Unique Alerting Systems Siren Emergency RBDS Subscription Mass Notification Systems web sites, apps widgets, social media Alert Aggregator & Gateways the Message Router (Open Platform for Emergency Networks) (Private Sector Systems) (State and Local Systems) (FEMA Systems)

What the IPAWS-OPEN does A Gateway to “Alert Dissemination Channels” Alert Aggregation: 1.Authenticates sender A.Web Service Security B.Digital Signature 2.Validates message format 3.Verifies alert is within sender’s permissions A.Alert type sent is authorized B.Alert area is within area of jurisdiction C.Alert distribution channel approved 4.Hands off alert messages to IPAWS Alert Dissemination Channels: EAS, WEA, NOAA Weather Radio, Internet Apps 9

IPAWS Alert Dissemination Channels: Emergency Alert System 20,000+ TV, Radio, Cable, Satellite stations privately owned and operated EAS participation defined by 47 CFR Part 11 Wireless Emergency Alerts 56 wireless carriers participating participation defined by 47 CFR Part 10 National Weather Service NOAA All-Hazards Weather Radio Network 1000 radio transmitters broadcasting on reserved weather frequencies Internet Services Internet or subscription type services/apps that monitor and retrieve alerts from IPAWS 10

Common Alerting Protocol (CAP); the IPAWS enabler  Structured, organized way to arrange data about alert events –Standardized format simplifies message exchange and utility across diverse networks through web messages exchanged via the Internet  Open international data standard available to all vendors, users, organizations –Developed and maintained by the Organization for the Advancement of Structured Information Standards (OASIS) –Adopted by FEMA, US Department of Defense, Public Safety Canada –Supported by a growing list of vendor products.  IPAWS uses: –CAP v1.2 Standard and the IPAWS Specification to the CAP Standard, CAP v1.2 IPAWS USA Profile v1.0

12 Alerting Authorities 216 County level w/ Public Alerting (185 County level in process for Public Alerting) 42 State level w/ Public Alerting (11 in process) 2 Territory w/ Public Alerting NOAA National Weather Service (NWS); since Jun 2012: ~850,000 NWS CAP messages processed by IPAWS ~9,500 NWS Wireless Emergency Alerts sent National Center for Missing and Exploited Children (AMBER Alerts) ~99 Wireless Emergency Alerts sent since Dec 2012 Alert Dissemination Channels (public alerting systems) Snapshot - IPAWS Users and Connections Status as of Feb2014 Emergency Alert System Wireless Emergency Alerts Internet Services NOAA Local State Territorial Federal IPAWS OPEN Over 20,000 EAS participants monitoring the IPAWS EAS Feed 56 Cellular Carriers connected Millions of handsets deployed All Hazards NOAA Weather Radio network 33 vendors with access to monitor IPAWS Public Alerts Feed Note: FEMA is not an Alerting Authority. FEMA doesn’t send Alerts. See list at:

13 Alerting Authority tools 62 different vendor’s IPAWS alerting tools are currently in use by state/local authorities using: CAP v1.2 Standard and the IPAWS Specification to the CAP Standard, CAP v1.2 IPAWS USA Profile v1.0 IPAWS-compatible alerting tools: Digitally signed CAP messages IPAWS OPEN The Internet Tools have wide variety of different look and feel Users find a tool that fits unique operational plans and use cases Some tools do not support all capabilities available via IPAWS Alerting Tool CAP messages

For more information  the IPAWS inbox:  IPAWS Website:  EMI Independent Study Course IS-247a:  EMI Independent Study Course IS-248: =IS =IS-248  Mailing list for IPAWS Webinar notices: DHSFEMA_165 DHSFEMA_165 14

Wade Witmer Deputy Director IPAWS Division National Continuity Programs, Prevention & National Preparedness U.S. Department of Homeland Security 500 C Street SW, Room 506 Washington, DC Office Antwane Johnson Division Director IPAWS National Continuity Programs, Prevention & National Preparedness U.S. Department of Homeland Security 500 C Street SW, Room 506 Washington, DC Office Contact Information 15 Mark Lucero Engineering Branch Chief IPAWS Division National Continuity Programs, Prevention & National Preparedness U.S. Department of Homeland Security 500 C Street SW, Room 506 Washington, DC Office

The Integrated Public Alert and Warning System (IPAWS) Standards Used in the IPAWS 2014 Workshop on Information Sharing and Safeguarding Standards (WIS3) Gary Ham - CTR FEMA IPAWS Division

17 Public end-user devices IPAWS Architecture – emergency alert information sharing enabled by data standards Alert Dissemination Channels (private sector systems) Emergency Alert System Wireless Emergency Alerts Internet Services NOAA HazCollect Local State Territorial Tribal Federal* ETN NWS CAP messages IPAWS compliant CAP Alert Origination Tools IPAWS OPEN Future Technologies? Alerting Authorities * Includes NOAA State / Local Unique Alerting Systems Siren Emergency RBDS Subscription Mass Notification Systems web sites, apps widgets, social media Alert Aggregator & Gateways the Message Router (Open Platform for Emergency Networks) (Private Sector Systems) (State and Local Systems) (FEMA Systems)

CAP Related Standards 1.OASIS Common Alerting Protocol Version 1.2, July 1, OASIS Common Alerting Protocol Version 1.2 USA Integrated Public Alert and Warning System Profile Version 1.0, Committee Specification 01, October 13, EAS-CAP Industry Group (ECIG) Recommendations for CAP EAS Implementation Guide – Version 1.0, May 17, OASIS Common Alerting Protocol Version 1.0, March

Other Data Standards 1.OASIS Emergency Data Exchange Language (EDXL) Distribution Element, v1.0, OASIS Standard EDXL-DE v1.0, 1 May National Weather Service Instruction , Text Product Formats and Codes, February 12, J-STD-101 Joint ATIS/TIA CMAS Federal Alert Gateway to CMSP Gateway Interface Specification, October

XML Related Standards 1.XML-Schema Version Simple Object Access Protocol (SOAP) Version Web Service Definition Language (WSDL) Version WS-Security Version 1.1 using x.509 Certificates 5.Representational State Transfer (REST) over HTTPS 6.Atom Syndication Format (IEF RFC4287) 20

IPAWS and NIEM 1.CAP is a recognized National Information Exchange Model (NIEM) external standard. To reuse in NIEM IEPD use the NIEM Adapter wrapping on CAP. 2.EDXL-DE can be used to wrap any NIEM IEP. 3.NIEM facets can be used for categorization inside DE elements.

NIEM In a Wrapper The graphic is from “An Introduction to NIEM.” An EDXL – Distribution Element Qualifies here

EDXL-DE 1.0 Structure Actual IEP goes here Actual IEP goes here “NIEMable” content item role metadata IEP identifier goes here “NIEMable” distribution metadata goes here “NIEMable” specific address goes here “NIEMable” geocode goes here Use of NIEM Elements in EDXL-DE

Questions? Gary Ham Member, OASIS Emergency Management Technical Committee (EM-TC) Contract System Architect to FEMA IPAWS

HS SEDI is a trademark of the U.S. Department of Homeland Security (DHS) The HS SEDI FFRDC is managed and operated by The MITRE Corporation for DHS Don NIEM Exchanges for First Responders March 26, 2014

HS SEDI is a trademark of the U.S. Department of Homeland Security (DHS) The HS SEDI FFRDC is managed and operated by The MITRE Corporation for DHS SEDI Task Objectives  Enable cross-organization information sharing for first responders through the modernization / application of data standards –Engage with end users to investigate the common gaps across the HSE –Evaluate the feasibility of closing gaps through the application of data standards –Share and transition the resulting technical best practices, architectures, and application strategies with end users in the HSE  Task Alignment With DHS Strategy –S&T Mission: “Strengthen the ability of first responders to protect the homeland and respond to disasters” –FRG Strategic Outcome: “Help First Responders Share Data and Critical Information” | 26 |

HS SEDI is a trademark of the U.S. Department of Homeland Security (DHS) The HS SEDI FFRDC is managed and operated by The MITRE Corporation for DHS Interoperability: Technical Goals Develop Exchanges and Architectures that: –Are scalable  For large scale / catastrophic level incidents  For large number of CAD systems  Easy to incorporate new systems –Are open & easy to implement –Guarantee interoperability  Address findings  Leverage NIEM –Can be applied broadly across emergency management  General Situational Awareness  Mission Ready Package information sharing  Automatic aid  Mutual aid  CAD-to-CAD | 27 |

HS SEDI is a trademark of the U.S. Department of Homeland Security (DHS) The HS SEDI FFRDC is managed and operated by The MITRE Corporation for DHS Interoperability: Approach Apply the Loose-Coupler concept –Have core, strictly defined, set of information  Little to no flexibility  Should represent intersection of information sharing needs  E.g.: What/When/Where –Allow community extensions that are flexible  Enables user organizations to communicate individualized information specific to their operations and needs within themselves or with similar organizations –Organizations can ignore the community extensions, reducing the amount of coordination necessary to successfully exchange core information | 28 |

HS SEDI is a trademark of the U.S. Department of Homeland Security (DHS) The HS SEDI FFRDC is managed and operated by The MITRE Corporation for DHS Interoperability: Technical Details  What –OWL Taxonomy –Examples  Incident.Fire.Home  Resource.Suppression.FireEngine –Will map to NIMS Resources –Will be usable by organizations using disparate typing schemes  Where –Embedded GML using strategies from Geo4NIEM –Address –National Grid  When –Formatted time stamp in UTC | 29 |

HS SEDI is a trademark of the U.S. Department of Homeland Security (DHS) The HS SEDI FFRDC is managed and operated by The MITRE Corporation for DHS Near-Term Paths Forward  Use EDXL-DE as a common message wrapper –Develop US Profile for EDXL-DE to reduce complexity –Use NIEM Code Lists to address localization issues  Develop loose-coupler IEPDs for “advertisement” –Incident Message –Resource Message  Use EDXL-RM for resource request / requisition –Develop US Profile for EDXL-RM to reduce complexity –Use NIEM Code Lists to address localization issues  Mission Ready Packages –Loose coupler concept applied to MRP advertisement –EDXL-RM applied to complete descriptions of MRPs | 30 |

HS SEDI is a trademark of the U.S. Department of Homeland Security (DHS) The HS SEDI FFRDC is managed and operated by The MITRE Corporation for DHS Concurrent Efforts for Engagement  OGC Application Schema / SOS  Next-Gen / GeoPriv  APCO EIDD  APCO Automated Secure Alarm Protocol (ASAP)  NFPA Apparatus Standards  CJIS Requirements for LE  PulsePoint  ROSS  Mutualaid.net | 31 |

HS SEDI is a trademark of the U.S. Department of Homeland Security (DHS) The HS SEDI FFRDC is managed and operated by The MITRE Corporation for DHS Questions?

References and Resources Alerts, Warnings & Response to Emergencies (AWARE) CAP: ITU Recommendation X.1303 Video CAUSE Main Film Preview Distributing Emergency Data Using Messaging Standards - E. Jones, IAEM Bulletin, Oct EDXL Sharp - EDXL Webinars - OASIS EDXL Standards LinkedIn Group - Emergency-Data-Exchange-Language http:// Emergency-Data-Exchange-Language Public CAP Feeds - Why Emergency Managers Should Care about Data Standards - E. Jones, IAEM Bulletin, Sept XML Cover Pages - XML and Emergency Management,