IPAWS Overview

1
Integrated Public Alert and Warning System
(IPAWS) Overview and Commercial Mobile Alert
System CMAS Introduction
August 2009
2
IPAWS Overview and CMAS Introduction

• What is IPAWS
• Why IPAWS
• Who
• IPAWS Architecture (Where)
• What is CMAS
• How CMAS Looks and Feels
• CMAS Timeline
• Questions

3
What is IPAWS?

• The Integrated Public Alert and Warning System
  (IPAWS) is the nations next-generation
  infrastructure of alert and warning networks
  expanding upon the traditional audio-only radio
  and television Emergency Alert System (EAS) by
  providing one message over more media to more
  people before, during, and after a disaster. 
• The vision of IPAWS builds and maintains 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. 
• IPAWS ensures the President can alert and warn
  the public under all conditions.  IPAWS will
  provide federal, state, territorial, tribal, and
  local warning authorities the capabilities to
  alert and warn their respective communities of
  all hazards impacting public safety and
  well-being via multiple communications pathways.

4
Why IPAWS?

• Since 2004, FEMA has served as the Executive
  Office lead agency for developing IPAWS. 
• In June 2006, the President signed the Public
  Alert and Warning System Executive Order 13407 to
  drive the creation of a more effective,
  reliable, integrated, flexible, and comprehensive
  system that enables the American people to
  receive alert and warning information through as
  many means as possible. 
• In response, FEMA established the IPAWS Program
  Management Office (PMO) in April 2007.

5
IPAWS Supporting Stakeholders
6
IPAWS Projects

• The current IPAWS projects are categorized into
  the areas of systems engineering, integration and
  implementation.   
• EAS Modernization and Expansion Project
• Digital Emergency Alert System (DEAS)
• Standards and Protocols Project (CAP)
• Commercial Mobile Alert System (CMAS)
• Geo-Targeted Alerting System (GTAS)
• NOAA Weather Radio Improvement Program (WRIP)
• Inventory and Evaluation (IE)
• Radio Broadcast Data System (RBDS)
• Updates and more available at http//www.fema.gov/
  emergency/ipaws/

7
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
IP access networks
Emergency Alert System
Federal

AM FM Satellite Radio Digital Analog Cable
Satellite TV
Digital EAS
PBS
IPAWS
State
Commercial Mobile Alert System
Cellular Phones
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
8
What is the Commercial Mobile Alert System (CMAS)?

• Commercial Mobile Alert System (CMAS) is one of
  many IPAWS systems intended to provide services
  to emergency operations centers so they can warn
  the relevant public of imminent threats to life
  and property through geographically targeted
  messages using Commercial Mobile Service
  Providers (CMSP)
• FEMA and DHS ST are working with the Alliance
  for Telecommunications Industry Solutions (ATIS),
  and the Telecommunications Industry Association
  (TIA) to finalize interface specifications
  between FEMA CMAS gateway and CMSP gateways
• CMAS will facilitate dissemination of 3 types of
  alerts
• Presidential Alerts
• Imminent Threat Alerts
• America's Missing Broadcast Emergency Response
  (AMBER) Alerts

9
How CMAS Works
10
CMAS Capabilities

• Centralized Reference Architecture
• Four Service Profiles
• Text
• Streaming Audio (future capability)
• Streaming Video (future capability)
• Downloaded Multimedia (future capability)
• Geographic Targeting of Alerts to county level
• Public opt-out rather than opt-in service
• 90-character text limit
• Authentication to ensure trusted source
• Optional Regular Monthly Testing

11
Planning Schedule for Initial CMAS
Development.Federal Alert Gateway Timeline for
Testing in 1Q FY12
10 Month Interval between Government Interface
Specifications Available and Start of
Development and Testing
18 Month CMAS Development, Testing Deployment
Aug 10
Jan 12
Oct
11
Apr 12
Jul 12
Jan
09
Apr
09
Oct
09
Jan
10
Apr
10
Jul
10
Oct
10
Jan
11
Apr
11
Jul 11
Jul 09
Mar
09
Feb 11
Nov 11
Feb 12
Federal Alert Gateway Available for Testing
with CMSP Gateway
FEMA Industry Standard Adoption
FEMA CMAS Requirements Kickoff
Integration of Federal CMAS Entities
FEMA CMAS Planning Kickoff
Design Engineering
Planning
System Implementation
Integration Test
Operations Maintenance
Requirements Analysis
12
(No Transcript)