1 / 17

Lessons Learned End to End CAP Alerting Systems

Lessons Learned End to End CAP Alerting Systems. WMO CAP Implementers Workshop Geneva, Switzerland Norm Paulsen Environment Canada April 24, 2013. Introduction. Environment Canada, as an issuer of weather warnings, distributed over 100,000 CAP messages last year

shaquille-charles
Download Presentation

Lessons Learned End to End CAP Alerting Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lessons LearnedEnd to End CAP Alerting Systems WMO CAP Implementers Workshop Geneva, Switzerland Norm Paulsen Environment Canada April 24, 2013

  2. Introduction • Environment Canada, as an issuer of weather warnings, distributed over 100,000 CAP messages last year • These went to numerous end clients (Emergency Managers & Last Mile Distributors) • The feedback has been significant and can be categorized into the following… • the working relationships with partners in “getting the warning out” • effective messaging for the target audience • supplemental event information for emergency managers • This presentation discusses… • some lessons learned • some example practices we employ • Profiles and Layers (mostly layers).

  3. Lesson 1) Defining “Alert” • There is confusion over what an ALERT is • Example: a typical series of Env. Can. warning messages (not yet in CAP form) • How many ALERTS in this scenario? • Answer: It depends on whose point of view. Issued 2 - active 1pm Continued 1 - active, 1 - ended 2pm 3pm Ended 1 - ended

  4. Lesson 2) Defining “Message” • There is confusion over what a MESSAGE is (still not thinking CAP yet) • How many MESSAGES in this scenario? • Answer: It depends on whose point of view Issued 1pm 2 - active 1 - active, 1- ended 2pm Continued 1 - ended Ended 3pm

  5. When we start thinking CAP • If I create one CAP file for each time listed, then by CAP’s definition there are 3 messages… • But CAP is a protocol for exchanging messages between alerting technologies – not exchanging directly with the human element • Recall that the human element still has 2,3, or 4 messages to consider in this example (let’s call these audience messages) 2 - active 1pm <msgType>alert 1 - active, 1- ended <msgType>update 2pm 1 - ended <msgType>cancel 3pm

  6. The Audience Experience The 3pm CAP message has 1 audience message The 2pm CAP message has 2 audience messages The 1pm CAP message has 1 audience message • The audience messages are distinguishable in space • The audience (public) certainly wants the right audience message for the right place (think web, cell phones, sirens, broadcasts, etc…) • I used active/ended but what if the difference was Severity = Extreme vs. Severity = Severe Audience Message 1: “Run for Cover” Audience Message 1: “Run for Cover” Audience Message 1: “It’s over” 1pm 2pm 3pm Audience Message 1: “Run for Cover” Audience Message 2: “It’s over” <msgType>update <msgType>alert <msgType>cancel 1 - ended 2 - active 1 - active, 1 - ended

  7. Audience Messages Appear in Separate <info> Blocks - <alert> <msgType>Alert</msgType> <sent>1pm</sent> -<info> <responseType>Monitor</responseType> <event>Tornado</event> <urgency>Immediate</urgency> <severity>Severe</severity> <certainty>Observed</certainty> <expires>3pm</expires> <headline>Tornado warning in effect</headline> - <area> <areaDesc>Penticton</areaDesc> </area>   </info> - <info> <responseType>Monitor</responseType> <event>Tornado</event> <urgency>Immediate</urgency> <severity>Severe</severity> <certainty>Observed</certainty> <expires>3pm</expires> <headline>Tornado warning in effect</headline> - <area> <areaDesc>Kelowna</areaDesc> </area> </info> </alert> - <alert> <msgType>Update</msgType> <sent>2pm</sent> -<info> <responseType>Monitor</responseType> <event>Tornado</event> <urgency>Immediate</urgency> <severity>Severe</severity> <certainty>Observed</certainty> <expires>4pm</expires> <headline>Tornado warning in effect</headline> - <area> <areaDesc>Penticton</areaDesc> </area>   </info> - <info> <responseType>AllClear</responseType> <event>Tornado</event> <urgency>Past</urgency> <severity>Minor</severity> <certainty>Observed</certainty> <expires>3pm</expires> <headline>Tornado warning ended</headline> - <area> <areaDesc>Kelowna</areaDesc> </area> </info> </alert> - <alert> <msgType>Cancel</msgType> <sent>3pm</sent> - <info> <responseType>AllClear</responseType> <event>Tornado</event> <urgency>Past</urgency> <severity>Minor</severity> <certainty>Observed</certainty> <expires>4pm</expires> <headline>Tornado warning ended</headline> - <area> <areaDesc>Penticton</areaDesc> </area> </info> </alert>

  8. Lesson 3) Customizing Supplementary Information in CAP • Last mile distributors in public alerting tend to want customized alert message presentation information • Emergency managers in peer to peer alerting tend to want customized subject event information -<alert> <info> <headline>tsunami warning in effect for southwest Vancouver coastline</headline>* </info> </alert> *Such as headline being constrained to say 140 characters. -<alert> <info> <parameter> <valueName>Wave_Arrival_Time</valueName>* <value>1:02pm</value> </parameter> </info> </alert> *Parameter value for wave arrival time could be a community defined standard

  9. Customized Information The info block with Vancouver could have: Tsunami warning in effect 15 meters Audience Message 1: “Tsunami warning in effect” Tsunami warning 1:02pm WARNING: Tsunami approaching From 280 degrees N The info block with Victoria could have: Audience Message 2: “Tsunami warning in effect” Tsunami warning in effect 15 meters Tsunami Warning 1:05pm WARNING: Tsunami approaching From 350 degrees N

  10. A Single Supplementary Information Solution <parameter> <valueName>layer:EC-MSC-SMC:1.0:Alert_Type</valueName> <value>warning</value> </parameter> <area> <geocode> <valueName>layer:EC-MSC-SMC:1.0:CLC</valueName> <value>062300</value> </geocode> </area> • An Alert issuer in Canada accommodates both client groups by using a concept known as a “layer”. • We consider a collection of supplementary information elements a layer • We use existing CAP elements (mechanisms) to realize these layers in CAP • We are basically extending the suite of information to the end client <parameter> <valueName>layer:SOREM:1.0:Broadcast_Immediately</valueName> <value>No</value> </parameter> <eventCode> <valueName>profile:CAP-CP:Event:0.4</valueName> <value>snowfall</value> </eventCode>

  11. Example: Province of Alberta -<alert> <identifier>x1475b</identifier> <msgType>Update</msgType> <sent>2pm</sent> <code>layer:AEMA:1.0</code> </info> <senderName>Alberta</senderName> <headline>Tornado warning updated by Environment Canada</headline> <parameter> <valueName>layer:AEMA:1.0:TvCrawler</valueName> <value>Tornado warning for Edmonton and surrounding area. Warning in effect until 2pm</value> </parameter> <parameter> <valueName>layer:AEMA:1.0:SMSText</valueName> <value>Tornado Warning</value> </parameter> <parameter> <valueName>layer:AEMA:1.0:WebPageBanner</valueName> <value>Tornado Warning in effect</value> </parameter> </info> </alert> • Alberta coordinates a CAP system with their downstream broadcast partners • Alberta aggregates Env. Can. CAP; inserts their own layer, and re-originates the CAP message to their LMD partners

  12. CAP, EDXL and OASIS • OASIS is working through a formalization of the mechanisms of Constraints (Profiles) and Extensions (Layers) on a broader scale (EDXL) • CAP already has informal these mechanisms in place to handle the concepts of profiles and layers (some examples below) • Retaining Interoperability is key

  13. Lesson 4) File Customization • Depending on the end client, there are different pieces of information that are of interest • This suggests a different CAP message for each end client…or… • using layers, the all inclusive CAP message can be constructed and the end client can retrieve for themselves the information of interest to them • In Env. Can., the “all info” message is easier to do – we just put everything we have into the CAP message, but the LMD may still have issues with… • languages • number of info blocks • community standards • relevant audience message • multiple information providers • etc… • However, because of profiles and layers, and using basic XML principles, we can easily customize CAP XML at this stage and solve these issues…

  14. XML File Customization - <alert> <identifier>2.49.0.1.124.4a8ca858.2013</identifier> <msgType>Update</msgType> <sent>2pm</sent> • Use one operation to create the all inclusive CAP message and then customize that CAP message • Take the CAP message file and copy it and customize it to a specific end client’s needs - <info> <senderName>Environment Canada</senderName> <responseType>AllClear</responseType> <event>Tornado</event> <urgency>Past</urgency> <severity>Minor</severity> <certainty>Observed</certainty> <expires>3pm</expires> <headline>Tornado warning ended</headline> - <area> <areaDesc>Kelowna</areaDesc> </area> </info> -<info> <senderName>Environment Canada</senderName> <responseType>Monitor</responseType> <event>Tornado</event> <urgency>Immediate</urgency> <severity>Severe</severity> <certainty>Observed</certainty> <expires>4pm</expires> <headline>Tornado warning in effect</headline> - <area> <areaDesc>Penticton</areaDesc> </area>   </info> </alert>

  15. XML File Customization (2) - <alert> <identifier>2.49.0.1.124.4a8ca858.2013</identifier> <msgType>Update</msgType> <sent>2pm</sent> • Use one operation to create the all inclusive CAP message and then customize that CAP message • Take the CAP message file and copy it and customize it to a specific end client’s needs <info> <senderName>Environment Canada</senderName> <language>English</language> <event>tornado</event> <expires>4pm</expires> <headline>tornado warning in effect</headline> - <area> <areaDesc>Penticton</areaDesc> </area>   </info> -<info> <senderName>Environnement Canada</senderName> <language>French</language> <event>tornade</event> <expires>4pm</expires> <headline>alerte de tornade en vigueur</headline> - <area> <areaDesc>Penticton</areaDesc> </area>   </info> </alert>

  16. XML File Customization (3) -<alert> <msgType>Update</msgType> <sent>2pm</sent> <code>layer:SOREM:1.0</code> <identifier>x1475b</identifier> <identifier>2.49.0.1.124.4a8ca858.2013</identifier> • Use one operation to create the all inclusive CAP message and then customize that CAP message • Take the CAP message file and copy it and customize it to a specific end client’s needs <code>layer:EC-MSC-SMC:1.0</code> <code>layer:AEMA:1.0</code> <info> <senderName>Environment Canada</senderName> <senderName>Alberta</senderName> <info> <parameter> <valueName>layer:EC-MSC-SMC:1.0:Alert_Type</valueName> <value>warning</value> </parameter> <parameter> <valueName>layer:AEMA:1.0:TvCrawler</valueName> <value>Tornado warning for Edmonton and surrounding area. Warning in effect until 2pm</value> </parameter> <parameter> <valueName>layer:SOREM:1.0:Broadcast_Immediately</valueName> <value>No</value> </parameter> <headline>Tornado warning in effect</headline> <instruction>Run for the hills</headline> </info> </alert>

  17. Conclusions • Define your terms, starting with Alerts, CAP Messages, Audience Messages and Subject Events • Use Controlled constraints and extension mechanisms if necessary to accommodate your supplemental needs • Customize your CAP Message after the file has been created using general XML practices • Customization can occur anywhere in the message trail

More Related