1 / 19

NWS and Partner Involvement in IPAWS, CMAS, and CAP

NWS and Partner Involvement in IPAWS, CMAS, and CAP. June 22, 2010 NWS Partners Meeting Silver Spring, MD Herb White Herbert.White@noaa.gov. Overview. Review of IPAWS, CMAS, and CAP Current and Future NWS Involvement Current and Future Partner Involvement Questions and Answers.

alia
Download Presentation

NWS and Partner Involvement in IPAWS, CMAS, and CAP

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. NWS and Partner Involvement inIPAWS, CMAS, and CAP June 22, 2010 NWS Partners Meeting Silver Spring, MD Herb White Herbert.White@noaa.gov

  2. Overview • Review of IPAWS, CMAS, and CAP • Current and Future NWS Involvement • Current and Future Partner Involvement • Questions and Answers

  3. Alert messages sent in Common Alerting Protocol (CAP). CAP is a standards based Alert Message data exchange format. Other

  4. IPAWS ArchitectureStandards based Alert Message aggregation, shared/trusted access & distribution, and alerts delivered to devices and consumer technologies Emergency Managers Alert messages produced in CAP format using IPAWS compliant 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 NOAA CAP message aggregation, authentication, adaption State / Local Unique Alerting Systems (e.g. ETN, Siren, Signage systems) IP distribution networks

  5. Snippets from a CAP Message • Programmer friendly • Easy to parse and reuse • Can make many products • Focus on content • Enables decision support technologies • Low cost of entry <event>Flash Flood Warning</event> <urgency>Immediate</urgency> <severity>Severe</severity> <certainty>Likely</certainty> <effective>2010-06-03T14:00:00-05:00</effective><expires>2010-06-03T17:00:00-05:00</expires> <senderName>NWS Memphis (Western Tennessee, Eastern Arkansas and Northern Mississippi)</senderName> <headline>Flash Flood Warning issued June 03 at 2:00PM CDT expiring June 03 at 5:00PM CDT by NWS Memphis</headline> <description>DOPPLER RADAR ESTIMATES 1 TO 3 INCHES OF RAINFALL HAS OCCURRED OVER THE PAST HOUR…</description> <instruction>MOST FLOOD DEATHS OCCUR IN AUTOMOBILES. NEVER DRIVE YOUR VEHICLE INTO AREAS WHERE THE WATER COVERS THE ROADWAY…TURN AROUND...DONT DROWN</instruction> <polygon>+36.20,-88.93 +36.18,-88.91 +36.05,-88.84 +35.99,-89.17 +35.99,-89.19 +35.98,-89.21 +35.94,-89.30 +36.17,-89.31 +36.21,-89.04 +36.20,-88.96 +36.22,-88.95 +36.20,-88.93</polygon>

  6. Commercial Mobile Alerting System(CMAS) Available to public as early as 2012 Capabilities • Cell tower broadcast (point to multi-point) • Geographic Targeting of Alerts to county level • Text limited to 90 characters (first generation) • Streaming Audio (future) • Streaming Video (future) • Downloadable Multimedia (future) • Public opt-out rather than opt-in

  7. CMAS Architecture

  8. Current NWS Involvement • CAP 1.1 feeds made available at weather.gov/alerts • Working with CAP standards body - OASIS • OASIS membership • Technical and adoption subcommittees • Review of CAP 1.2 • Feedback to DHS/FEMA on IPAWS and CMAS requirements • Working on FCC EAS rule change subcommittees • Outreach • Partners Meetings • Interoperability demonstrations at emergency manager related events • Industry events (i.e., AMS, NAB, Consumer Electronics Show, etc.)

  9. Future NWS Involvement • NWS CAP User Guide to be released summer 2010 • Experimental CAP Push (TBD) • Once CAP 1.2 approved as OASIS standard, special team to begin work on CAP 2.0 • Feedback to DHS/FEMA on IPAWS and CMAS requirements (need to be more specific) • Changes to Code of Federal Regulations (CFR) Part 11 (EAS) • Outreach • Partners Meetings • Shared booth space and interoperability demonstrations with DHS/FEMA and private sector at emergency management conferences • Industry events (i.e., AMS, NAB, Consumer Electronics Show, etc.)

  10. Current Partner Involvement • EAS-CAP Industry Group (ECIG) • Alerting Solutions, Inc. • Communications Laboratories, Inc. • iBiquity Digital Corporation • Monroe Electronics, Inc. • MyStateUSA • Sage Alerting Systems, Inc. • SpectraRep, LLC • TFT, Inc. • Trilithic, Inc. • Warning Systems, Inc. • ECIG Recommendations For a CAP EAS Implementation Guide • Interoperability demonstrations and conference booth space • Weather enterprise partners?

  11. Future Partner Involvement • Special team to work on CAP 2.0 • Interoperability demonstrations and conference booth space • Increase in sales of innovative CAP compliant alerting devices and services

  12. Areas of Opportunity for Innovation • Alerts on cell phones and consumer navigation systems • Graphical and/or text oriented • Interactive/customizable • Route user away from threats • Cell phone applications (i.e., iPhone, Android, etc.) • Decision support tools • Integration with social media (i.e., more transactional than traditional one-way delivery of information) • Others

  13. Outcomes We hope that you are: • More knowledgeable about evolving interoperability and public alerting efforts • Thinking about coming opportunities to: • Leverage CAP • Get the right message to the right people • Help people make the best possible life, property, and economic decisions

  14. Contacts CMAS: Denis Gusty, Deputy Branch Chief, Office of Interoperability and Compatibility, DHS Science and Technology Directorate Denis.Gusty@dhs.gov www.cmasforum.com/ www.fcc.gov/pshs/services/cmas.html IPAWS: Antwane V. Johnson, Division Director, NCP IPAWS, DHS/FEMA Antwane.Johnson@dhs.gov www.fema.gov/emergency/ipaws/ NWS: Herb White, Dissemination Services Manager, OCWWS, NOAA/NWS Herbert.White@noaa.gov www.weather.gov/alerts-beta/ Q & A

  15. Supporting Information

  16. Common Alerting Protocol (CAP) Drivers • Public Safety • Interoperability enables the American people to receive alert and warning information through as many means as possible • FEMA Integrated Public Alert and Warning System (IPAWS) - Commercial Mobile Alert System (CMAS) • Commercial Weather Sector • Low cost of entry • Can make many products from same easy to parse message • Minimal issues when NWS makes changes • NWS efficiency and agility • Greater focus on content of message and less on mechanics • Minimal impact on users when NWS changes necessary • Enables/facilitates decision support and related technologies

  17. IPAWS, CMAS, and CAPHow it all fits • Integrated Public Alert and Warning System (IPAWS) resulted from Executive Order 13407 requiring 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.” • Owned by Department of Homeland Security (DHS) and FEMA with direction from the FCC • IPAWS Projects • Commercial Mobile Alerting System (CMAS) • EAS Modernization and Expansion Project • Digital Emergency Alert System (DEAS) • Geo-Targeted Alerting System (GTAS) • NOAA Weather Radio Improvement Program (WRIP) • Inventory and Evaluation (I&E) • Radio Broadcast Data System (RBDS) Focus on Interoperability using Common Alerting Protocol (CAP). CAP is a standards based Alert Message data exchange format.

  18. Commercial Mobile Alert System (CMAS) • National capability to deliver geographically targeted Presidential and imminent threat alerts (e.g., hurricanes, tornadoes, etc) and child abduction emergencies through mobile devices (cell phones) • Origins in Warning, Alert, and Response Network (WARN) Act of 2006 • DHS/FEMA and stakeholder involvement (wireless carriers, equipment manufacturers, Government agencies, broadcast associations, emergency management, safety organizations, and other experts) • Wireless carrier participation voluntary, but all majors participating • Available to public as early as 2012

More Related