[EAS] ETRS Reporting

[Sean Donelan]

On Tue, 27 Sep 2016, Ed Czarnecki wrote:
> So, on the automated reported concept (whether it goes through IPAWS as a
> proxy, a direct report to an FCC server, or wherever) would require a number
> of changes to the ETRS report, standing up an govt automated collection
> process, and adding new software to EAS devices (and BTW, who absorbs this
> unfunded mandate?).

One of those unintended consequences. When I was a Federal employee, under 
the Paperwork Reduction Act I could not survey more than 10 people about
any topic, without obtaining OMB approval. Conducting a survey of more 
than 10 people usually took 12+ months to set up and get the approvals.

The split between FCC, FEMA and NWS makes reporting and management of EAS, 
WEA and IPAWS a challenge.  FEMA talks to emergency managers, FCC talks to 
mass media and industry, NWS issues most of the alerts.

There is nothing preventing industry from voluntarily creating a better 
system for tracking and reporting EAS information.  The Alabama State 
Broadcast Association supposedly has create its own system which 
automatically uploads FTP files from Alabama stations about EAS tests in 
the state.

Trilithic has very nice compliance and reporting software for collecting
data from its EAS boxes. It is popular for nation-wide companies which 
need to track EAS operations from 100+ EAS boxes.

>From a technical perspective, its "just a small matter of programming." 
Post an XML file through IPAWS at FEMA, send an email to a mailbox at FCC 
or upload an FTP file.  Hire Nielsen/Arbitron to collect airchecks or 
diary data about alerts over the air.

But from a management and policy perspective, government reporting is a 
huge can of worms. CTIA, NCTA and NAB have been pretty consistent at 
opposing or watering down every proposed reporting rule or industry 
survey.