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
 FEMA Adoption of CAP
 Next Steps
 Process and Timeline
1
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
2
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
Emergency
Managers
Message
Disseminators
Emergency Alert System
IP access
networks
Federal
State
Digital EAS
IPAWS
Cellular Broadcast
Internet Services
Local
IPAWS compliant
CAP Alert
Origination Tools
Public
message
aggregation,
authentication,
adaption
PBS
AM FM Satellite Radio;
Digital Analog Cable Satellite
TV
Cellular
Carriers
Networks
Cellular
Phones
Web Browsers,
widgets, web
sites
NOAA
State / Local Unique
Alerting Systems
IP distribution
networks
(e.g. ETN, Siren, Signage
systems)
3
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
Requirements
Industry
Requirements
These paths have required long timelines
and feedback into the process
Federal
Requirements
OASIS
Standards
Process
FCC
Rule Making
IPAWS
Conformity
Assessment
Next Generation
EAS Products
The CAP Profile will be used several ways
4
OASIS CAP v1.2 IPAWS Profile Status
OASIS CAP Profile
Sub Committee
Draft Standard
Sub-version
OASIS Emergency
Management
Technical Committee
(EMTC) Draft
Standard
Draft
Standard
OASIS Publishes
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
5
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
6
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
7
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
8
Standards Tentative Timeline
Planning Draft
Activities
2009
2nd Qtr
2010
3rd Qtr
4th Qtr
1st Qtr
2nd Qtr
2011
3rd Qtr
4th Qtr
1st Qtr
OASIS IPAWS
CAP v1.2 Profile
OASIS CAP
v1.2 Standard
IPAWS Standards Phase I
FEMAIPAWS CAP v1.2 to
EAS Implementation
Guide Requirements
IPAWS Conformity
Assessment Program
OASIS CAP v2.0 Standard
OASIS IPAWS CAP v1.2 to EAS
Implementation Guide
IPAWS Conformity Assessment Program Phase I
IPAWS CAP Profile Updates
IPAWS Standards Phase II
Implementation Guide FCC Rulemaking*
CAP Implementation Guide
Updates
CA Phase II
CAP Profile – FCC Part 11 Rulemaking*
• Network Management
• Video Messages
CAP Implementation Guides – FCC Part 11 Rulemaking*
• Multiple Languages
• Special Needs
• Video Messages
• Network Management
• Video Messages
EDXL-DE Message Security
IPAWS Standards Phase III
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
9
Descargar

No Slide Title