[EAS] FW: Max Length of EAS Messages

[Amy Sebring]

A single CAP alert may be used for relay to both EAS and CMAS if it 
meets the criteria of both systems.  The CMAS message is derived from 
the CAP elements that Ed describes, while the EAS message is derived 
from the description and instruction elements.

There is also a headline element that could be used locally from the 
same CAP alert to trigger other alerting systems such as signs, Tweets, etc.

The idea is one alert, many channels.

ajs

Ed Czarnecki wrote:

>Clay and Jim - The CMAS message may well be a separate message from the EAS
>one.  A CMAS Alert Message processed by a mobile carrier is limited to 90
>alphanumeric text characters.  The CMAS protocol message is generated by the
>IPAWS aggregator/gateway information CAP message received from the
>state/county/local alert originator..
>
>So, while CAP will be delivered to TV/Radio/Cable EAS Participants, the
>mobile carriers will get a separately formatted CMAS protocol message.  CAP
>is not delivered to the mobile carrier gateway, nor to the mobile device.
>Also, not all "EAS" alerts would meet the threshold of getting CMAS status
>(only presidential and "imminent threat to life & property").
>
>One way to look at is that the CMAS alert is intended to get people
>attention of a person with a very basic alert.  The person would then be
>implicitly expected to seek out other media for confirmation of the alert
>and more information.
>
>The CMAS formatted alert would be constrained - within 90 characters - to
>the following content:
>- event type or category
>- area affected
>- response description (i.e. "shelter" or "evacuate")
>- Expiration time (as e.g. "until 11:30 PM EDT)
>- Sending agency
>
>Here is a link to an image on the Aware Forum capturing a CMAS test message
>from NYC on 2/16/12:
>http://www.freedomsphoenix.com/Uploads/145/Graph/Alertmsg.jpg
>
>Image appears to be a Droid X2 on the Verizon network.
>
>  
>