Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "Lessons Learned End to End CAP Alerting Systems WMO CAP Implementers Workshop Geneva, Switzerland Norm Paulsen Environment Canada April 24, 2013."— Presentation transcript:

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

2 Page 2 – February 22, 2014 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 Page 3 – February 22, 2014 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. at…a Weather Warning waslocations identified 1pm Issued2 - active Ended3pm Continued1 - active, 1 - ended 2pm 1 - ended

4 Page 4 – February 22, 2014 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 at…Warning StatusReferenced Locations 1pm Issued 2 - active Ended 3pm Continued 1 - active, 1- ended 2pm 1 - ended

5 Page 5 – February 22, 2014 When we start thinking CAP If I create one CAP file for each time listed, then by CAPs 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 (lets call these audience messages) at…CAP messageReferenced Locations 1pm alert 2 - active cancel 3pm update 1 - active, 1- ended 2pm 1 - ended

6 Page 6 – February 22, 2014 The Audience Experience 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 at… CAP message Referenced Locations alert 2 - active 1pm2pm update 1 - active, 1 - ended 3pm cancel 1 - ended The 1pm CAP message has 1 audience messageThe 2pm CAP message has 2 audience messagesThe 3pm CAP message has 1 audience message Audience Message 1: Run for Cover Audience Message 2: Its over Audience Message 1: Run for Cover Audience Message 1: Its over

7 Page 7 – February 22, 2014 Audience Messages Appear in Separate Blocks - Alert 1pm - Monitor Tornado Immediate Severe Observed 3pm Tornado warning in effect - Penticton - Monitor Tornado Immediate Severe Observed 3pm Tornado warning in effect - Kelowna - Update 2pm - Monitor Tornado Immediate Severe Observed 4pm Tornado warning in effect - Penticton - AllClear Tornado Past Minor Observed 3pm Tornado warning ended - Kelowna - Cancel 3pm - AllClear Tornado Past Minor Observed 4pm Tornado warning ended - Penticton

8 Page 8 – February 22, 2014 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 - tsunami warning in effect for southwest Vancouver coastline * *Such as headline being constrained to say 140 characters. - Wave_Arrival_Time * 1:02pm *Parameter value for wave arrival time could be a community defined standard

9 Page 9 – February 22, 2014 Alert MessageSupplemental Info HeadlineWave Height SMS TextWave Arrival \time TVCrawlerArrival direction Customized Information Alert MessageSupplemental Info HeadlineWave Height SMS textWave Arrival Time TVcrawlerArrival Direction 1:02pm From 280 degrees N 15 meters The info block with Vancouver could have: Audience Message 1: Tsunami warning in effect Audience Message 2: Tsunami warning in effect Tsunami warning in effect WARNING: Tsunami approaching Tsunami warning The info block with Victoria could have: 1:05pm From 350 degrees N 15 metersTsunami warning in effect WARNING: Tsunami approaching Tsunami Warning

10 Page 10 – February 22, 2014 A Single Supplementary Information Solution 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 layer:EC-MSC-SMC:1.0:Alert_Type warning layer:EC-MSC-SMC:1.0:CLC layer:SOREM:1.0:Broadcast_Immediately No profile:CAP-CP:Event:0.4 snowfall

11 Page 11 – February 22, 2014 Example: Province of Alberta 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 - x1475b Update 2pm layer:AEMA:1.0 Alberta Tornado warning updated by Environment Canada layer:AEMA:1.0:TvCrawler Tornado warning for Edmonton and surrounding area. Warning in effect until 2pm layer:AEMA:1.0:SMSText Tornado Warning layer:AEMA:1.0:WebPageBanner Tornado Warning in effect

12 Page 12 – February 22, 2014 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 ProfileConstraintOptional CAP element constrained to being a required element (i.e., ) ProfileConstraintOptional CAP elements and constrained to a predefined community list (published and versioned) ProfileConstraintDeclare an optional element as required for community use as defined by the community LayerExtensionCAP message extended to include several geo-targeting schemes (i.e. ) LayerExtensionCAP message extended to include customized audience messages by medium (i.e. ) LayerExtensionCAP message extended to provide supplemental subject event details (i.e. )

13 Page 13 – February 22, 2014 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 Page 14 – February 22, 2014 XML File Customization 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 clients needs a8ca Update 2pm - Environment Canada AllClear Tornado Past Minor Observed 3pm Tornado warning ended - Kelowna - Environment Canada Monitor Tornado Immediate Severe Observed 4pm Tornado warning in effect - Penticton

15 Page 15 – February 22, 2014 XML File Customization (2) 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 clients needs a8ca Update 2pm Environment Canada English tornado 4pm tornado warning in effect - Penticton - Environnement Canada French tornade 4pm alerte de tornade en vigueur - Penticton

16 Page 16 – February 22, 2014 XML File Customization (3) 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 clients needs - Update 2pm layer:SOREM:1.0 layer:EC-MSC-SMC:1.0:Alert_Type warning layer:SOREM:1.0:Broadcast_Immediately No Tornado warning in effect Run for the hills layer:EC-MSC-SMC:1.0 Environment Canada layer:AEMA:1.0 layer:AEMA:1.0:TvCrawler Tornado warning for Edmonton and surrounding area. Warning in effect until 2pm x1475b Alberta a8ca

17 Page 17 – February 22, 2014 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


Download ppt "Lessons Learned End to End CAP Alerting Systems WMO CAP Implementers Workshop Geneva, Switzerland Norm Paulsen Environment Canada April 24, 2013."

Similar presentations


Ads by Google