[EAS] Overlap/monitoring issue

[Paul Campbell]

Ultimately, this is what I'm shooting for here. I need someone in a similar county-overlap situation to tell me how they're dealing with this. Again, the problem isn't prioritizing TOR's over FFW's or whatever, it's dealing with multiple TOR's kicking out other TOR's from two different monitor inputs, one of which happens to be my state relay. Unless the NWS is willing to simulcast TOR's on both transmitters whenever my problem child area is involved (which they won't do, which has already been explained), the only solution I can see is hoping that the Sage can be modified with a firmware update that would allow a filter to be constructed based on Input #. This is really a sorta perfect storm of an issue here, as it's dealing with an LP-1, a SR, and two NWS transmitters. 

------------------------------

Message: 8
From: "Adrienne  Abbott" <nevadaeas at charter.net>
Content-Type: text/plain; 	charset="iso-8859-1"

So how do the stations in Tornado Alley handle the situation? We get one, maybe two tornado warnings a year here in Nevada but a whole lot of SVR's and FFW's. What happens in places like Norman, OK, where dozens of TOR warnings are issued every week during tornado season along with the SVR's and FFW's? What kind of EAS equipment do the broadcasters and cable operators use? How do they program the filters and is that working for them?
Do they have some way to give a higher priority to TOR warnings over SVR's or FFW's or does that happen at the NWS? What can those of us who aren't in Kansas learn from the way they do EAS?

Adrienne Abbott
Nevada EAS Chair

Kevin asked: Just asking - Does the Monroe / Digital Alert box offer a solution?

There must be a method of drawing parallels with multi-incoming alerts in a rapid manner. Perhaps something like 'Rules' (in popular mail clients) could be added to the ENDECs?