[sbe-eas] WA: This is a test. happy Friday!

[Dave Turnmire]

Part of the selling point of the Common Alerting Protocol (CAP), was to 
allow alert originators to quickly send alerts via different alerting 
technologies, with a minimum amount of retyping.  And it works fairly 
well in that regard. But... as is so often the case... there is two 
sides of that "ease of use" coin... it also makes it easier to send an 
improper alert using multiple alerting technologies, etc.

"To Error is Human.  To REALLY screw it up requires a computer"

Dave

On 8/17/2024 5:08 PM, Aaron Read wrote:
> Ah, so from these replies (thank you all) it is easier for a human to 
> mistakenly send alerts to both the WEA ecosystem and the EAS ecosystem 
> (by the vector of IPAWS) than I realized.  I thought those were 
> usually two very different software interfaces but I'm understanding 
> that not only aren't they very different...they're not even TWO 
> software interfaces; it's all done in one program.  YIKES.  No wonder 
> fuckups like this happen so often.
>
>
> ____________________
> Aaron Read
> www.friedbagels.com <http://www.friedbagels.com>
> 401-519-0230 office
>
>
> On Sat, Aug 17, 2024 at 6:05 PM Rob Dale <rdale at skywatch.org> wrote:
>
>     Correct - a WEA can't "leak" into EAS.
>
>     But the monthly proficiency demonstration requires users to send a
>     message to both the EAS and WEA channel on the test server.
>
>     To do that just requires the user to check the "WEA" box AND the
>     "EAS" box.
>
>     If that's done in the real world, then bad things can happen :)
>     Because as you noted some things that are pure tests in WEA are
>     actual live messages (RMT) in EAS.
>
>     Rob
>
>
>>     On Aug 17, 2024, at 5:58 PM, Aaron Read
>>     <readaaron at friedbagels.com> wrote:
>>
>>     
>>     I am very confused: WEA may use codes similar to what EAS uses,
>>     but I was under the impression they are NOT the same.  There's no
>>     possible way a test in WEA could end up on EAS (except through
>>     *significant* user error) because they're completely different
>>     systems, data flow & infrastructure...right?
>>
>>
>>     ____________________
>>     Aaron Read
>>     www.friedbagels.com <http://www.friedbagels.com>
>>     401-519-0230 office
>>
>>
>>     On Fri, Aug 16, 2024 at 11:00 PM Rob Dale <rdale at skywatch.org> wrote:
>>
>>         It was first sent at an RMT WEA Test which may mess up EAS
>>         but won’t go to cell phones (unless they turned on
>>         state/local tests.)
>>
>>         It was next sent as a DMO which I was under the impression
>>         never goes to cell phones?
>>
>>         Did one or both go as a live test to all?
>>
>>         Rob
>>
>>
>>>         On Aug 16, 2024, at 10:55 PM, Lowell Kiesow
>>>         <lkiesow at knkx.org> wrote:
>>>
>>>         
>>>         It might be smarter to test with an event code such as RWT
>>>         or DMO, so that no damage is done when released to the wild.
>>>
>>>         Lowell Kiesow
>>>         Chief Engineer
>>>         *88* <http://knkx.org/>*.* <http://www.jazz24.org/>*5 FM
>>>         KNKX* <http://knkx.org/>**●***J*azz24.org*
>>>         <http://www.jazz24.org/>*
>>>         lkiesow at knkx.org <mailto:lkiesow at knkx.org> ●
>>>         knkx.org <http://knkx.org>
>>>
>>>
>>>         On Fri, Aug 16, 2024 at 7:16 PM Sean Donelan
>>>         <sean at donelan.com> wrote:
>>>
>>>
>>>             200166,EMD (WA) - Emergency Management Division
>>>             (WMD),Washington Emergency
>>>             Management Division accidently transmitted a statewide
>>>             test WEA Friday
>>>             evening.
>>>
>>>
>>>
>>>             WA Emergency Management
>>>             Welp. Shoot. As an emergency management agency, we
>>>             regularly send test
>>>             alerts to ensure our employees are proficient and the
>>>             test alert system
>>>             works. They’re normally sent in a “test” environment.
>>>             Tonight an alert was
>>>             accidently sent outside of that test
>>>             environment._______________________________________________
>>>             sbe-eas mailing list
>>>             sbe-eas at sbe.org
>>>             https://pairlist7.pair.net/mailman/listinfo/sbe-eas
>>>
>>>         _______________________________________________
>>>         sbe-eas mailing list
>>>         sbe-eas at sbe.org
>>>         https://pairlist7.pair.net/mailman/listinfo/sbe-eas
>>         _______________________________________________
>>         sbe-eas mailing list
>>         sbe-eas at sbe.org
>>         https://pairlist7.pair.net/mailman/listinfo/sbe-eas
>>
>>     _______________________________________________
>>     sbe-eas mailing list
>>     sbe-eas at sbe.org
>>     https://pairlist7.pair.net/mailman/listinfo/sbe-eas
>     _______________________________________________
>     sbe-eas mailing list
>     sbe-eas at sbe.org
>     https://pairlist7.pair.net/mailman/listinfo/sbe-eas
>
>
> _______________________________________________
> sbe-eas mailing list
> sbe-eas at sbe.org
> https://pairlist7.pair.net/mailman/listinfo/sbe-eas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist7.pair.net/pipermail/sbe-eas/attachments/20240822/7c8dd6c1/attachment.htm>