[EAS] Sage Required Update

[Dave Kline]

On Tue, Oct 8, 2019 at 3:01 AM Mike McCarthy <towers at mre.com> wrote:
>
> I just checked the site and there is an updated post from 10/7 which said
> the "September" version will be released in the next few days.
>
> That leaves 30 days (as of this morning) for the entire pool of 3644 users
> to update their boxes in order to maintain IPAWS connectivity if the Nov.
> 8 date is to be enforced.
>
> I am signed up to receive their updates.
>
> For the roughly 1/2 of stations/cable systems out there with managed a
> engineering department, it's not such a big deal time wise. It's the
> singleton/ma-pa/small/hyper-spread operations which are going to suffer
> when their already overloaded contract guy can't get to all the far flung
> clients/sites for a couple weeks..or more....unless the box has a pinhole
> to the outside world. Few do...
>
> MM

The short turn-a-round is not the fault of stations.
If you can't get the upgrade done in time through no fault of your own
(and it better be a solid argument for that) then you need to note in
your logs why you haven't received the alerts.

If it were my station, I'd do the pre-purchase right now and schedule
the contract engineer as soon as the upgrade is actually available.
(I wouldn't want to schedule the engineer to come in based on a
proposed release date.)
Keep a receipt for the purchase and a record of having scheduling the
engineer and any delays in his being able to be there when scheduled.
If the update is late in being installed and you miss a test, then you
at least have something to show you made a good faith effort if anyone
really bothers to check up on you.

-------------------------------------
Dave Kline - Solder Jockey
-------------------------------------