I was a little surprised to not hear or see many comments after the big, first national EAS exercise. I did however read one “interesting” article about it that was divided into the old good new/bad news categories.
The good news? The test was delivered successfully to both the Primary Entry Point (PEP) stations and via the National Public Radio (NPR) Squawk Channel, a background channel used to supplement the feed of the over-the-air PEP stations.
The bad news? Unfortunately most areas of the country reported there were issues with double audio being delivered, with a second EAS Header Code starting about 15 seconds into the alert and double audio continuing for the duration of the 30-second test. While some PEP stations reported the test sounded fine, other PEP stations sent the EAS Header Code but had no audio of the test in states such as Minnesota and Indiana, and other PEP stations such as the one in Utah never received the test.
The comment I thought was amazing was this one…It was also reported that the system used for originating the test at FEMA had a clock that was apparently running 3 minutes fast, as the test was issued at 2:00PM ET but the time stamp said it was issued at 2:03PM ET. Huh?!?!?!?!
While it seems FEMA has some issues to iron out with the test origination, there were positive reports from many states across the country that received the test and forwarded it out to all stations in the state properly. So while the audio was less than desirable, it is encouraging to hear of many states that have a well-functioning State EAS Network which will be ready to relay a hopeful cleaner test the next time around.
FEMA will be spending the next few weeks gathering test result data from the test’s participants, and feedback from all of the stakeholders. Under the FCC’s rules, test participants have 45 days from the date of the test to analyze their data and provide a full report to the FCC on the scope and reach of the test.
In the meantime, FEMA is also interested in hearing from any stakeholders who want to share feedback about how the test worked and suggestions for improvement. You can reach FEMA at email@example.com with any tips, suggestions or input you may have.