[EAS] EAS Logging

[Clay Freinwald]

Re. how to handled logging with the Sage - 

I take care of that chore with a small AM/FM.  However the class of station
preclude me(a contractor) from being the Chief Operator - Therefore - I
print out the logs from both Sages once-per-week and attached them to the
Chief Operator Log.   On this log I have check boxes to make sure that they
are - 

1- Receiving tests (RWT'S) from the State CAP system (MyStateUSA) 
2- Receiviing messages (tests etc) from FEMA/IPAWS
3- Forwarding RMT's and other 'real' events
4- Initiating RWT's

This allows me to, as required, to look up-stream if something is missing
etc.

Logging to a computer is fine - Just as long as you have something that can
be quickly put into paper form for the FCC Inspector remembering that he
will come by when the only person in the building was asking last week -
'would you like fries with that.....'     

Having the Sage advise you and/or your smart phone etc as to EAS Status is
great - However - all that will not cut when the Commish comes to the front
desk and you are on vacation.

Another thing - The Inspector will likely ask to see the logs and may ask
that an RWT be transmitted - Again - When Alice Airhead is the only one in
the building.

Clay Freinwald
Also the SECC Chair for Washington State.

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

Branched this to a new topic.

A few comments on EAS message logging as it applies to Sage ENDEC 3644.....

If you keep paper logs, be sure to print the unit's internal stored list of
EAS messages every week or so. The internal buffer will eventually fill up
and old messages are discarded. Not sure what the stored message limit is,
it might be dependent on the size of the messages rather than an absolute
message count.

The ENDEC appears to support direct-attached printers (serial and USB).
We do not use this method at our LP station, but I'm sure it appeals to a
few other users.

Better method (IMO) is to store EAS messages on a computer. Do this one of
two ways. Configure the 3644 to e-mail EAS traffic to an account with lots
of storage. Each message results in one e-mail and an MP3 audio file if you
have chosen this option. Or, configure the 3644 to FTP the messages to an
account on a computer with a lot of free storage. Each EAS message results
in one small TXT file being FTP'd to the target computer and an MP3 audio
file if you have chosen this option.

We have selected both e-mail and FTP at this location. The e-mail is so I
can see EAS traffic on my smartphone. The FTP repository is our "official"
log of EAS activations, etc. Once a week, I look at the ENDEC's pretty
web-based log and make a notation in the station log based on what was seen.
Once a year we spin the received FTP files off to DVD and file it.

[snip]

I print out my Sage logs once a month. In June, a rainy month here in the
east, the log ran to 18 pages.  Two of my stations share a decoder, and the
filters in the Sage are set to monitor traffic for 12 counties.
Yet I'll get NWS warnings for counties outside this area.  (they're logged,
but ignored).  Must be a quirk in the Sage.

[end]

__________________________________________________________
The EAS Forum Discussion List is hosted by the BWWG (Broadcast Warning
Working Group). http://eas.radiolists.net Please invite your friends to join
our Forum! The sign up is at:
http://lists.radiolists.net/mailman/listinfo/eas
___________________________________________________________