[EAS] Sage update coming in Sept.

[Mike McCarthy]

As is the case with most things industry these days, there is a lot of
bubblegum and bailing wire lash-ups which do the job. We're no different.

Admittedly, the now nearly 23 year old system was developed at the cusp of
computing ability. Frankly, I'd love to have the Sage boxes have AoIP GPIO
(and a 2nd NIC for the AoIP subnet) so the automation systems can native
machine GPIO and SNMP for flagging/controlling alerts.  ***And*** the type
of alert for customization.

A smart system would flag the automation system for say a Flash Flood
Warning.  The automation system would run a macro, politely interrupt with
an intro of a Flash Flood Warning, and then trigger the box to forward.
The EAS box would then respond back with a true EOM after the third EOM
databurst and the automation would resume where it left off.

A less elegant way is to use the inhibit which can be more readily done on
most systems using a toggled closure.

None of this level of integration was really viable 20 years ago at the
dawn of walk-away systems.  But it is now....

MM

On Fri, July 19, 2019 2:29 am, Sean Donelan wrote:
>
> 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.