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

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
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).
Page 2 – April 24, 2020
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)
at…
a Weather Warning was
locations identified
1pm
Issued
2 - active
2pm
3pm
Continued
1 - active, 1 - ended
Ended
1 - ended
• How many ALERTS in this scenario?
• Answer: It depends on whose point of view.
Page 3 – April 24, 2020
Lesson 2) Defining “Message”
• There is confusion over what a MESSAGE is
(still not thinking CAP yet)
at…
Warning Status
1pm
Issued
2pm
Continued
Ended
3pm
Referenced Locations
2 - active
1 - active, 1- ended
1 - ended
• How many MESSAGES in this scenario?
• Answer: It depends on whose point of view
Page 4 – April 24, 2020
When we start thinking CAP
• If I create one CAP file for each time listed, then by CAP’s
definition there are 3 messages…
at…
CAP message
Referenced Locations
1pm
<msgType>alert
2 - active
2pm
<msgType>update
1 - active, 1- ended
3pm
<msgType>cancel
1 - ended
• 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)
Page 5 – April 24, 2020
The Audience Experience
1pm CAP message has 1
2pm
2 audience message
messages
• The 3pm
• 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
Audience
Message
1:
Message
“Run for1:
“It’s
over”
Cover”
at…
2pm
1pm
3pm
Audience
Audience
Message
1:
Message
“Run for2:
“It’s
over”
Cover”
CAP message
<msgType>alert
<msgType>update
<msgType>cancel
Referenced Locations
2 - ended
1
active 1 - ended
active,
Page 6 – April 24, 2020
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>
Page 7 – April 24, 2020
- <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>
Lesson 3)
Customizing Supplementary Information in CAP
• Last mile distributors in public alerting tend to want
customized alert message presentation information
- <alert>
<info>
<headline>tsunami warning in effect for southwest Vancouver coastline</headline>*
</info>
</alert>
*Such as headline being constrained to say 140 characters.
• Emergency managers in peer to peer alerting tend to
want customized subject event information
- <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
Page 8 – April 24, 2020
Customized Information
The info block with Vancouver could have:
Alert Message
Supplemental Info
Headline
Wave Height
Tsunami warning in effect
SMS text
Tsunami warning
15 meters
Wave Arrival Time
1:02pm
Audience
Message 1:
“Tsunami
warning in effect”
TVcrawler
Arrival Direction
WARNING: Tsunami approaching
From 280 degrees N
The info block with Victoria could have:
Alert Message
Supplemental Info
Headline
Wave Height
Tsunami warning in effect
SMS Text
Tsunami Warning
15 meters
Wave Arrival \time
1:05pm
TVCrawler
Arrival direction
WARNING: Tsunami approaching
From 350 degrees N
Page 9 – April 24, 2020
Audience
Message 2:
“Tsunami
warning in effect”
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
<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>
<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>
Page 10 – April 24, 2020
Example: Province of Alberta
• Alberta coordinates
a CAP system with
their downstream
broadcast partners
• Alberta aggregates
Env. Can. CAP;
inserts their own
layer, and reoriginates the CAP
message to their
LMD partners
- <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>
Page 11 – April 24, 2020
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
Profile
Constraint
Optional CAP element constrained to being a required element (i.e.
<language>, <expires>)
Profile
Constraint
Optional CAP elements <eventCode> and <geocode> constrained to a
predefined community list (published and versioned)
Profile
Constraint
Declare an optional <parameter> element as required for community
use as defined by the community
Layer
Extension
CAP message extended to include several geo-targeting schemes (i.e.
<geocode>)
Layer
Extension
CAP message extended to include customized audience messages by
medium (i.e. <parameter>)
Layer
Extension
CAP message extended to provide supplemental subject event details
(i.e. <parameter>)
Page 12 – April 24, 2020
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…
Page 13 – April 24, 2020
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 client’s
needs
- <alert>
<identifier>2.49.0.1.124.4a8ca858.2013</identifier>
<msgType>Update</msgType>
<sent>2pm</sent>
- <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>
Page 14 – April 24, 2020
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 client’s
needs
- <alert>
<identifier>2.49.0.1.124.4a8ca858.2013</identifier>
<msgType>Update</msgType>
<sent>2pm</sent>
<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>
Page 15 – April 24, 2020
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 client’s
needs
- <alert>
<identifier>x1475b</identifier>
<identifier>2.49.0.1.124.4a8ca858.2013</identifier>
<msgType>Update</msgType>
<sent>2pm</sent>
<code>layer:SOREM:1.0</code>
<code>layer:EC-MSC-SMC:1.0</code>
<code>layer:AEMA:1.0</code>
<info>
<senderName>Environment Canada</senderName>
<senderName>Alberta</senderName>
<parameter>
<valueName>layer:EC-MSC-SMC:1.0:Alert_Type</valueName>
<valueName>layer:AEMA:1.0:TvCrawler</valueName>
<value>warning</value>
<value>Tornado
warning for Edmonton and surrounding area.
</parameter>
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>
Page 16 – April 24, 2020
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
Page 17 – April 24, 2020