1 / 10

Timothy Putprush Baltimore, MD September 30, 2009

Federal Emergency Management Agency (FEMA) Integrated Public Alert and Warning System Presentation to the OASIS Interoperability Summit. Timothy Putprush Baltimore, MD September 30, 2009. Table Of Contents. IPAWS Vision IPAWS Architecture and Role of CAP CAP OASIS Process and Status

umay
Télécharger la présentation

Timothy Putprush Baltimore, MD September 30, 2009

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. Federal Emergency Management Agency (FEMA) Integrated Public Alert and Warning System Presentation to the OASIS Interoperability Summit Timothy Putprush Baltimore, MD September 30, 2009

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

  3. IPAWS Vision - 2009 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

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

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

  6. OASIS CAP v1.2 IPAWS Profile Status OASIS CAP v1.2 Profile Standard OASIS Emergency Management Technical Committee (EMTC) Draft Standard Draft Standard OASIS CAP Profile Sub Committee Draft Standard OASIS Publishes Sub-version 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

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

  8. 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.) 13407 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

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

  10. Standards Tentative Timeline Activities 2009 2010 2011 Planning Draft 2nd Qtr 3rd Qtr 4th Qtr 1st Qtr 2nd Qtr 3rd Qtr 4th Qtr 1st Qtr IPAWS Standards Phase I OASIS IPAWS CAP v1.2 Profile OASIS CAP v1.2 Standard OASIS CAP v2.0 Standard FEMAIPAWS CAP v1.2 to EAS Implementation Guide Requirements OASIS IPAWS CAP v1.2 to EAS Implementation Guide Implementation Guide FCC Rulemaking* IPAWS Conformity Assessment Program IPAWS Conformity Assessment Program Phase I CA Phase II IPAWS Standards Phase II IPAWS CAP Profile Updates • CAP Profile – FCC Part 11 Rulemaking* • Network Management • Video Messages CAP Implementation Guide Updates • CAP Implementation Guides – FCC Part 11 Rulemaking* • Network Management • Video Messages • Multiple Languages • Special Needs • Video Messages IPAWS Standards Phase III EDXL-DE Message Security Federated Identity Management – FEMA Enterprise IMS * Or Alternate Strategy for Enforcement 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

More Related