[EAS] Blue Alerts Are Back

[Sean Donelan]

On Fri, 19 May 2017, Adrienne Abbott wrote:
> Why can't they just use one of the existing Event Codes like LEW instead of
> creating a new code which will require broadcasters to pay for an upgrade
> their equipment?

Historically, new event codes have been "voluntary."  People are still 
using EAS equipment and firmware, which doesn't support the 2002 event 
codes.  Some EAS equipment, such as Sage ENDEC 3644, supports adding new 
event codes and new FIPS codes as part of the configuration file, without 
needing new firmware.

The advantage of using a distinct event code for Blue Alerts - Allows 
broadcasters to filter out Blue Alerts from other events; and either 
broadcast or not broadcast those alerts automatically.

The disadvantage of using distinct event codes is lack of training of 
alert orginators, and confusion in state/local plans about sending alerts.

In practical terms, this is mostly a political speech.  News broadcasters 
already cover any attacks on law enforcement officers with significant 
resources. It won't change news coverage. Non-news broadcasters 
generally don't cover any breaking news, and probably won't cover Blue 
Alerts, Amber Alerts, tornados, or any other non-mandatory interruptions.

The biggest, and continuing problem, with all IPAWS and EAS alerts is lack 
of training of local originators.  Although they are getting better, many 
IPAWS and local EAS alert originators have problems creating useful alert 
text and activating their systems.