[EAS] Sage update coming in Sept.

[Sean Donelan]

On Thu, 18 Jul 2019, Mike McCarthy wrote:
> If the box will accept a forward inhibit closure which the automation
> system can delay the sending of a pending alert until the inhibit is
> lifted....except for EAN/EAT and NPT. All others could be externally
> inhibited to their time limit.
>
> Then you might get some buy-in for some alerts as they won't barge in over
> revenue producing spots in a more friendly configuration.

If you aren't paying for support, its just a favor. That's business. 
The three EAS box variants I've worked with have different automation 
strengths and quirks.  I haven't worked with GR's box.

On the other hand, there doesn't seem to be agreement between automation 
vendors and EAS vendors exactly how the entire alert life-cycle is 
supposed to work.  It always seems to be a kludge and duct tape on both 
sides for anything more complicated than triggering a RWT.

See my recurring rant about the lack of published guidance by FEMA and 
FCC. SBE, CableLabs, ATIS and each of the EAS and automation vendors have 
a mental model how its supposed to work; but they are each slightly 
different.