1 / 33

WIS3 Breakout #2 Emergency Management Panel

WIS3 Breakout #2 Emergency Management Panel. OASIS Organization for the Advancement of Structured Information Standards Emergency Management Technical Committee.

malha
Download Presentation

WIS3 Breakout #2 Emergency Management Panel

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. WIS3 Breakout #2 Emergency Management Panel OASISOrganization for the Advancement of Structured Information Standards Emergency Management Technical Committee • Wade WitmerDeputy 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 2014 Workshop on Information Sharing and Safeguarding Standards (WIS3) Elysa Jones, Chair OASIS Emergency Management Technical Committee elysajones@yahoo.com

  2. CAP Workshop 2013 Emergency ManagementPrepare – Respond – Recover – Mitigate Television Radio Cell Phone Computer Home Phone Public Signage/Siren

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

  4. EDXL Standards Development Process

  5. 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 IPAWS@dhs.gov www.fema.gov/IPAWS

  6. What is IPAWS? • IPAWS is a National Systemfor 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: IPAWS does not know your phone number or your location! • Not a subscription based mass notification system • Not an ETN or reverse dial phone system • Not an SMS or email 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 allcitizens 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

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

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

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

  11. Common Alerting Protocol (CAP); theIPAWS 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) http://www.oasis-open.org • 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. Snapshot - IPAWS Users and Connections Status as of Feb2014 See list at: http://www.fema.gov/integrated-public-alert-warning-system-authorities 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) Local Over 20,000 EAS participants monitoring the IPAWS EAS Feed Emergency Alert System State All Hazards NOAA Weather Radio network NOAA Territorial IPAWS OPEN Wireless Emergency Alerts Federal 56 Cellular Carriers connected Millions of handsets deployed Internet Services 33 vendors with access to monitor IPAWS Public Alerts Feed Note: FEMA is not an Alerting Authority. FEMA doesn’t send Alerts.

  13. IPAWS-compatible alerting tools: • 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 • 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 IPAWS OPEN CAP messages The Internet Digitally signed CAP messages

  14. For more information Email the IPAWS inbox: IPAWS@dhs.gov IPAWS Website:http://www.fema.gov/ipaws/ EMI Independent Study Course IS-247a:https://training.fema.gov/EMIWeb/IS/is247a.asp EMI Independent Study Course IS-248:http://training.fema.gov/EMIWeb/IS/courseOverview.aspx?code=IS-248 Mailing list for IPAWS Webinar notices:http://service.govdelivery.com/service/subscribe.html?code=USDHSFEMA_165 14

  15. Contact Information 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 20472 202.646.4383 Office Antwane.Johnson@fema.dhs.gov IPAWS@dhs.gov 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 20472 202.646.2523 Office Wade.Witmer@fema.dhs.gov IIPAWS@dhs.gov 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 20472 202.646-1386Office Mark.Lucero@fema.dhs.gov IIPAWS@dhs.gov 15

  16. 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 IPAWS@dhs.gov www.fema.gov/IPAWS

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

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

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

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

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

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

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

  24. Questions? Gary Ham Member, OASIS Emergency Management Technical Committee (EM-TC) Contract System Architect to FEMA IPAWS gary.ham@associates.fema.dhs.gov

  25. NIEM Exchanges for First Responders Don McGarry dmcgarry@mitre.org @dpmcgarry March 26, 2014

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

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

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

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

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

  31. Concurrent Efforts for Engagement • OGC Application Schema / SOS • Next-Gen 9-1-1 / GeoPriv • APCO EIDD • APCO Automated Secure Alarm Protocol (ASAP) • NFPA Apparatus Standards • CJIS Requirements for LE • PulsePoint • ROSS • Mutualaid.net

  32. Questions?

  33. References and Resources • Alerts, Warnings & Response to Emergencies (AWARE) - http://www.awareforum.org/category/cap/ • CAP: ITU Recommendation X.1303 Video - http://www.youtube.com/watch?v=n0iKp60jjtY • CAUSE Main Film Preview - http://vimeo.com/planetworks/review/32382855/cb73fb3182 • Distributing Emergency Data Using Messaging Standards - E. Jones, IAEM Bulletin, Oct 2009 - http://www.oasis-emergency.org/node/47 • EDXL Sharp - http://edxlsharp.codeplex.com/ • EDXL Webinars - https://www.oasis-open.org/events/webinars • OASIS EDXL Standards LinkedIn Group - http://www.linkedin.com/groups/OASIS-Emergency-Data-Exchange-Language-3355540 • Public CAP Feeds - http://www.incident.com/cookbook/index.php/Public_CAP_Feeds • Why Emergency Managers Should Care about Data Standards - E. Jones, IAEM Bulletin, Sept. 2009 - http://www.oasis-emergency.org/node/46 • XML Cover Pages - XML and Emergency Management, http://xml.coverpages.org/emergencyManagement.html

More Related