[EAS] Hawaii - mandatory evacuation - was there EAS triggered?

Harold Price hprice at sagealertingsystems.com
Mon May 7 19:45:00 CDT 2018


Dave Turnmire said: "By my reading "between the lines"... the authors 
of the ECIG CAP EAS Implementation guide hoped this requirement would 
have been tossed long ago:"

Indeed we did.

The arguments in favor have been a potentially more concise and 
quicker to the point message.

The arguments against have been that it further relies on the skills 
of the message originator to write a message that includes all of the 
important elements - including start time, and locations.  Non-CAP 
derived messages will still need the required text as that is all 
that is available.  This will happen less as we move to a CAP-first philosophy.

Other points to make - The actual event code might not be of interest 
to the public (is it important that the public see CEM vs CDW vs EVI, 
etc.)?  The actual description of the emergency is better.  A list of 
counties might not be important to the public, if a better 
description can be had.  Still, it is important to take into 
consideration what EAS-only devices might see - Al Kenyon mentioned 
that Evacuate Immediate might not be the right choice in many cases.

I continue to bring up removing the boilerplate in various venues - 
there is another round of the FCC's CSRIC advisory group that is 
discussing future alerting, and I'll bring it up again.

In addition to removing the boilerplate from the video crawl, we 
should also remove it from the Text to Speech string when CAP 
description/instruction is available.

Harold

At 06:16 PM 5/7/2018, Dave Turnmire wrote:
>On 5/7/2018 5:29 AM, Al Kenyon wrote:
>>I'm planning to recommend
>>that the Commission consider removing the requirement for video service
>>providers to display EAS header based text if alerting authority generated
>>message text is available. That way the visual message display and audio
>>message can contain the exact same information.
>A BIG amen to that.  And while they are at it, they should drop the 
>requirement for the corresponding audio message if a voice file is 
>present.  At best, it irritates/confuses the listener with them 
>potentially mentally or literally "tuning out" before you get to the 
>important audio... that which emergency management created.  At 
>worst... for various technical reasons the emergency management 
>audio actually gets truncated so it can't be heard...
>
>By my reading "between the lines"... the authors of the ECIG CAP EAS 
>Implementation guide hoped this requirement would have been tossed long ago:



More information about the EAS mailing list