[EAS] Sage Update Available

[Mike McCarthy]

Same here. Simply note any compliance defects, the underlying reason(s),
and most importantly, actions attempted/taken to remedy the defect in each
week's Station Log.  Provide any supporting documentation as well. Such as
a copy of a PO ordering the update from.....and any positive internal
correspondence.  As I recall, a licensee has a lot of latitude in the time
line to correct the defects....like up to 90 days with proper
documentation and sustained effort.

The philosophy I have understood with the FCC is while they care about
compliance, they also seriously consider licensee attempts at same and
recognize there will be blips where not everything goes smoothly.

Never mind I am sure they are acutely aware of the very time compressed 
release of the certificates which impact everyone.  Not just Sage users.

I applaud Sage as they have simply taken the opportunity to combine a
bunch of things into a single necessary effort. Thus compacting multiple
updates and time needed for each.

MM

On Mon, November 4, 2019 8:38 am, Richard Rudman wrote:
> Tom took the words right out of my mouth, but with a slight adjustment.
> I am recommending that clients put an along the lines Tom describes in
> their weekly EAS logs.
>
> Richard Rudman