Pages
Stay In Touch
More
(c) Copyright Touchstone Consulting Group
This post is the last in a 5-part series of reports on the contents of the FCC Fifth Report and Order released on January 10, 2012, which amends the Emergency Alert System (EAS) rules to accommodate Common Alerting Protocol (CAP) messages.
Stop by the EAS Category on the AWARE Forum for previous posts in this series on the new CAP EAS rules introduced in the Report and Order (R&O). In this final look at the R&O, we will detail the various items that FCC declined to make a decision on at this point. In addition, the Commission made several interesting statements regarding their apparent view on legacy EAS going forward. [xxx] below denotes the R&O paragraph which discusses the noted language. Also below, the use of the word “SAME” means Specific Area Message Encoding, the technical name for the legacy EAS protocol originally coined by the National Weather Service. Continue reading »
Earlier this month, I attended the Consumer Electronics Show (CES) in Las Vegas. This event receives a significant amount of attention from both technology and mainstream news sources, so a recap of the new TVs (which were amazing), Ultrabooks (I want one), and other gizmos (do we need a six-foot-tall iPod dock?) isn’t really useful. However there is one theme I want to key in on. I didn’t quite see it while I was walking the exhibit floor, but realized it after discussing the event with colleagues.
Broadcast is dead.
Google rolled out Google Public Alerts on Google Maps today. They are currently displaying data from NOAA, NWS, and USGS. Google is using CAP to format the alerts and is encouraging all agencies that send alerts to adopt CAP. They are also looking to solicit data from local originators and eventually incorporate those alerts into Google Public Alerts.
Google has also created an Alert Hub that aggregates alerts and allows other people to develop ways to redistribute them.
At first glance this development looks pretty slick. Check it out, and let us know what you think!
This post is Part 4 of 5 in a series of reports on the contents of the FCC Fifth Report and Order released on January 10, 2012, which amends the Emergency Alert System (EAS) rules to accommodate Common Alerting Protocol (CAP) messages.
For previous posts in this 5-part series on the new CAP EAS rules introduced in the Report and Order (R&O), check out the EAS Category on the AWARE Forum. In this edition of our series we will address rules of interest to State Emergency Communications Committees (SECCs). [xxx] below denotes the R&O paragraph which discusses the noted language. Also below, the use of the word “SAME” means Specific Area Message Encoding, the technical name for the legacy EAS protocol originally coined by the National Weather Service. Continue reading »
This post is Part 3 of 5 in a series of reports on the contents of the FCC Fifth Report and Order released on January 10, 2012, which amends the Emergency Alert System (EAS) rules to accommodate Common Alerting Protocol (CAP) messages.
Part 1 and Part 2 of our series dealt with new CAP EAS rules added by the Report and Order (R&O). Here in Part 3, we will take a look at what the FCC left the same, updating of an often-used acronym, and four rules that the Commission eliminated. [xxx] below denotes the R&O paragraph which discusses the noted language. Continue reading »
