Timothy Putprush Baltimore, MD September 30, 2009 Federal Emergency Management Agency (FEMA) Integrated Public Alert and Warning System Presentation to the OASIS Interoperability Summit

1 Table Of Contents  IPAWS Vision  IPAWS Architecture and Role of CAP  CAP OASIS Process and Status  FEMA Adoption of CAP  Next Steps  Process and Timeline

2 IPAWS Vision To build and maintain an effective, reliable, integrated, flexible, and comprehensive system that enables the American people to receive alert and warning information through as many means as possible. The IPAWS will provide the President the ability to address the American people in situations of war, terrorist attack, natural disaster, or other hazards. The IPAWS will provide local, state, and federal alert and warning authorities integrated services and capabilities enabling them to alert and warn their respective communities, via multiple communications methods of any hazard impacting public safety and well-being The IPAWS will: Diversify and modernize the Emergency Alert System Create an interoperability framework by establishing or adopting standards such as the Common Alerting Protocol (CAP) Integrate with and provide federal, state, and local alert and warning message access to multiple broadcast and other communications pathways to enable alert and warning messages to reach the public through as many means as possible Partner with NOAA to enable seamless integration of message transmission through National networks. Enable alert and warning to those with disabilities and those without an understanding of the English language Allow the President of the United States to speak to the American people under all emergency circumstances

3 Message Disseminators Emergency Managers IPAWS compliant CAP Alert Origination Tools IPAWS Vision Architecture Standards Based Alert Message data exchange format, alert message aggregation, shared, trusted access & distribution networks, alerts delivered to more public interface devices State Emergency Alert System Cellular Broadcast Federal Local State / Local Unique Alerting Systems (e.g. ETN, Siren, Signage systems) Internet Services IPAWS NOAA Public IP access networks IP distribution networks Digital EAS PBS AM FM Satellite Radio; Digital Analog Cable Satellite TV Cellular Phones Web Browsers, widgets, web sites message aggregation, authentication, adaption Cellular Carriers Networks

4 Practitioner Require- ments OASIS Standards Process Federal Require- ments FEMA CAP v1.2 IPAWS Profile Process Overview IPAWS CAP V1.2 Profile CAP Standards Profile Analysis IPAWS Requirements Industry Alliance CAP Profile Recommendations Industry Require- ments IPAWS Conformity Assessment Next Generation EAS Products FCC Rule Making These paths have required long timelines and feedback into the process Multiple inputs feed into the CAP process The CAP Profile will be used several ways RFIs and Demonstrations IPAWS EAS CAP Process

5 OASIS CAP v1.2 IPAWS Profile Status OASIS Emergency Management Technical Committee (EMTC) Draft Standard OASIS Publishes OASIS CAP Profile Sub Committee Draft Standard Sub-version Draft Standard OASIS CAP v1.2 Profile Standard OASIS Public Comment Review OASIS CAP v1.2 IPAWS Profile Status –First 60-day Comment Period ended on May 2, 2009 –Additional 15-day Comment Period to address changes ran from July 27- Aug 11, 2009 –EMTC voted the CAP v1.2 IPAWS Profile to become a committee draft standard on Aug 25, 2009 –FEMA expects the CAP v1.2 Profile to become a published standard by Sept 2009

6 FEMA Adoption of CAP Proposed Conditions to be satisfied before IPAWS adoption of the CAP Standard: –Stand-up IPAWS Conformance Lab and begin testing –Develop CAP to EAS Implementation Guide for CAP to EAS Translation –Demonstrate delivery of federal message in OASIS IPAWS CAP v1.2 Profile format to a National Primary Entry Point Station –Propose and start OASIS process on IPAWS CAP Security Requirements

7 Next Steps - There are more challenges ahead  FEMA recognizes that the FCC does not require specific security requirements, multiple languages, alerts & warnings for the visually and hearing impaired communities, or video media types for Next Generation EAS  FEMA feels that it is reasonable to consider adopting the OASIS IPAWS CAP Profile when it is standardized by OASIS  The community has made it known to FEMA that CAP-to-EAS Translation Specifications and security guidance are necessary for a sound implementation of the Next Generation EAS  The Executive Order (E.O.) requires IPAWS to address security, multiple languages, and alerts & warnings for the visually and hearing impaired communities. In addition, the President’s office has requested support for video media types.  Therefore, FEMA intends on pursuing additional requirements to address these outstanding issues for Next Generation EAS

8 Next Steps after OASIS CAP v1.2 Profile Standard  CAP to EAS Translation Specifications – Implementation Guides –Draft implementation guide specifications created September 09 –Draft Analysis of required changes to FCC Part 11 rules created September 09  CAP Phase II –Multiple languages (Update: Canada conference take aways) –Alerts for manual or hearing impaired (Update: Atlanta conference take aways) –Video messages  CAP Phase III –EDXL-DE Message Security –Federated Identity Management

9 Activities IPAWS Standards Phase I IPAWS Conformity Assessment Program Standards Tentative Timeline IPAWS Standards Phase II IPAWS Standards Phase III Jan 2010 – FEMA adopts CAP v1.1/1.2, IPAWS CAP 1.2 Profile, and Implementation Guide Jan 2011 – FEMA IPAWS meets industry needs for Standards and Protocols * Or Alternate Strategy for Enforcement nd Qtr 3 rd Qtr 4 th Qtr 1 st Qtr 2 nd Qtr 3 rd Qtr 4 th Qtr 1 st Qtr OASIS IPAWS CAP v1.2 Profile OASIS CAP v2.0 Standard OASIS CAP v1.2 Standard OASIS IPAWS CAP v1.2 to EAS Implementation Guide Implementation Guide FCC Rulemaking* FEMAIPAWS CAP v1.2 to EAS Implementation Guide Requirements EDXL-DE Message Security CAP Implementation Guides – FCC Part 11 Rulemaking* Network Management Video Messages Federated Identity Management – FEMA Enterprise IMS CAP Profile – FCC Part 11 Rulemaking* Network Management Video Messages Multiple Languages Special Needs Video Messages IPAWS Conformity Assessment Program Phase I IPAWS CAP Profile Updates CAP Implementation Guide Updates CA Phase II Planning Draft