[EAS] CAP EAS Logging Question

[Darryl Parker]

Adrienne,

The TFT EAS911+, EAS911, and EAS3320 comply with Part 11 provisions of 11.33(a)(4), 11.34(f), and 11.34(g). These units permit users to comply with Part 11 provisions in 11.38(a), 11.38(b), 11.51(m)(2), 11.52(e)(2), 11.54(a)(3), 11.61(a)(2)(D)(ii) and 11.61(a)(3)(iv).

It is important to remember that there is a difference between receiving an EAS message (either via CAP or RF monitoring) and forwarding/sending an EAS message. Basically, any received message, whether from CAP or RF monitoring, must be logged. Any transmitted message must also be logged. Whether a received message is transmitted is a different argument, usually set by filter parameters in the EAS or CAP decoder.

Regards,
Darryl E.Parker
TFT, Inc.
San Jose, California 95131-1708 USA
Tel: (1) 408-943-9323, Extension 223
www.TFTInc.com

-----Original Message-----
From: eas-bounces at radiolists.net [mailto:eas-bounces at radiolists.net] On Behalf Of Adrienne Abbott

All-

This is a question about EAS logging requirements and the changes which CAP
has made in our documentation practices. Nevada has three Operational Areas
and no broadcast signal covers more than one of them, so statewide tests
have not existed until now, with the acquisition of CAP software. 

Now I am finding that when an RWT is issued by the City of Henderson in
southern Nevada, it shows up in the Sage ENDECS in northern Nevada. The same
thing happens when officials in the Reno area issue CAP RWT's. 
[Darryl Parker] ...
Do other EAS units like DASDEC and Trilithic operate the same way?

[Darryl Parker] ...

Adrienne Abbott

Nevada EAS Chair