About
Connect with AWARE
Touchstone Consulting Group - An SRA Company
CAP
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 »
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 »
This post is Part 2 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.
As in Part 1 of our series, this installment will continue a look at new and changed rules in the Report and Order (R&O). [xxx] below denotes the R&O paragraph which discusses the noted language.
Continue reading »
This post is Part 1 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.
As a follow-on to our preliminary synopsis of the FCC Report and Order, this five-part series will take a more in-depth look at the new rules. Two of the highlights of the new CAP EAS rules might be the best and the worst decisions made in the ruling, both of which deal with how CAP alerts are converted for presentation as legacy EAS messages on broadcast stations and cable systems. First the good news…
Continue reading »
