[EAS] ETRS Reporting

Ed Czarnecki ed.czarnecki at monroe-electronics.com
Tue Sep 27 10:16:55 CDT 2016


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?).

- the automated reporting function on the EAS device would require the user
to input (correctly) all the required station identifying info (Form 1) on
the device.  I'm not a big fan of having all that identifying info on the
appliance, but it could be done.

- a success/fail ping back from the EAS device would be limited to reception
of the alert, authentication, processing and forwarding.  Getting a report
back on success/failure downstream of the EAS device is quite a different
matter. 

- Form 3 reporting may still need to be manual, unless the FCC amend the
desired information to fit an automated report.  The how's and why's of a
why test may have had an issue upstream or downstream may not be something
that the EAS device can easily "sense".

- in the ultimate iteration of this concept, there could be no humans at
all.  FEMA issues test.  EAS device processes test and automatically reports
back to FCC PSHSB server.  If the test is not reported, or report is
incorrect, FCC PSHSB server pings an Enforcement Bureau server (the FCC
enforcement bot).  Enforcement bot automatically issues NAL and deducts the
fine from your online banking account.  

Technology.  It's a beautiful thing.



More information about the EAS mailing list