CAP in Environment Canada Norm Paulsen Environment Canada September 2015

Page 2 – December 12, 2015 Environment Canada - an Issuer of Public Alerts Environment Canada issues to the Public approximately thousand warnings for weather related hazards every year Each of these warnings produces on average 6 to 7 updates. This results in (20,000 x 7) = 140,000 distinct warning messages per year Each message has to be duplicated as we have 2 official languages So for the traditional audiences we serve, we produce approximately K WMO formatted warning bulletins every year We produce CAP messages for all of these

Page 3 – December 12, 2015 Simple Issuer – Distributor relationship -We send out an Alert Message -Our Distribution Partners Present the Alert Message to the Public

Page 4 – December 12, 2015 What EC (as an issuer) wants… - An easy way to get our message out - A solution that works for all Distributors - CAP enabled those requirements

Page 5 – December 12, 2015 Community of Issuers/Distributors In Theory…. In Reality… GAP

Page 6 – December 12, 2015 So what is the GAP? (1 of 2) As an issuer interested in multi-channel alerting we want… –The Alert information to be complete and up to date ▪Multiple language requirements (English, French, other…) ▪Multiple medium requirements (Audio, Video, Text, …) ▪“Out of date” information no longer present –Our two known Distributor platform types are equally served… ▪“Instantaneous” -> includes SMS, s, bulletins, etc… (basically those where the message is deposited). The user gets the message when they come into range of the presentation form (even if it is out of date) ▪“Continuous” -> includes dynamic battleboards, most types of crawlers, banners etc… (basically those where the information is kept up to date). The user only gets real time information when they come into range of the presentation

Page 7 – December 12, 2015 What is the GAP? (2 of 2) We generally find that the Distributors want… –The Alert information to be complete and up to date ▪In the language of their medium (English, French, other…) ▪In a form specific for their medium (Audio, Video, Text, …) ▪In a form that accommodates their platform type (instantaneous, continuous, or both) ▪Information content that fits their clientele's preferences (often a subset of the full information) So the GAP is the difference between…. –The desire for an up to date database of information and… –The customization of the information for a particular medium

Page 8 – December 12, 2015 CAP itself doesn’t judge! The CAP schema provides a fairly complete structure for almost all the basic alert information ▪CAP 2.0 is being discussed but not much new is being requested CAP-XML allows for customization by allowing the free form fields (,, etc…) ▪populated with strings without limits or constraints So the GAP is not a CAP thing but a “choice of practice”

Page 9 – December 12, 2015 Simple Issuer – Distributor relationship -A is fully “un-customized” -B is fully “customized” -Who fills in the GAP? A B

Page 10 – December 12, 2015 Can the GAP be bridged? Yes, but it requires… –Someone to step up and take ownership of the problem –Someone to represent the communities involved –Someone to see it through, and then manage change over time In Canada, we are struggling to find that Someone –The “cost” (time, money and resources) is the hurdle to ownership

Page 11 – December 12, 2015 Issuer – Distributor relationship with an Aggregator that also Re-originates -There is no entity C in Canada to take the A form of the CAP message and re-originate the various B forms to serve the various client groups A C B

Page 12 – December 12, 2015 What we are left with…. -1) The Issuer having to originate distinct CAP messages per client group -Our content, but their structural constraints and limitations -No Change Management entity to lead change -Dealing with individual requests for change -Managing multiple routing configurations -Consistency of message across platforms is complicated -Cross indexing message for performance evaluation B

Page 13 – December 12, 2015 Or…. -1) The Issuer originating 1 CAP message without a C in between -Our content, but their structural constraints and limitations (better contained) -No Change Management entity to lead (no change) -Dealing with individual requests for change (better contained) -Managing multiple routing configurations (much easier) -Consistency of message across platforms is compounded (much easier) -Cross indexing message for performance evaluation (much easier) B

Page 14 – December 12, 2015 How we do this..? In 1 single CAP message file we treat… –, and as our own element where we want to provide our “story” –, and as a means to address the client group customization –Multiple, and as a means to address multiple client group customizations

Page 15 – December 12, 2015 (Sample Message) Our Story… At 12:24 p.m. MDT, Environment Canada meteorologists are tracking a severe thunderstorm that is possibly producing a tornado. Damaging winds, large hail and locally intense rainfall are also possible. This is a dangerous and potentially life- threatening situation. Tornado warnings are issued when imminent or occurring thunderstorms are likely to produce or are producing tornadoes. To report severe weather, send an to or tweet reports to #ABStorm. Take cover immediately, if threatening weather approaches. If you hear a roaring sound or see a funnel cloud, swirling debris near the ground, flying debris, or any threatening weather approaching, take shelter immediately. Go indoors to a room on the lowest floor, away from outside walls and windows, such as a basement, bathroom, stairwell or interior closet. Leave mobile homes, vehicles, tents, trailers and other temporary or free-standing shelter, and move to a strong building if you can. As a last resort, lie in a low spot and protect your head from flying debris. Lightning kills and injures Canadians every year. Remember, when thunder roars, go indoors!

Page 16 – December 12, 2015 Client Group 1 Customization (Broadcaster)… layer:SOREM:1.0:Broadcast_Text At 12:24 p.m. MDT Environment Canada has issued a Tornado Warning for Southern Alberta near the towns of Fort MacLeod and Lethbridge. Damaging winds, large hail and locally intense rainfall are also possible. Take cover immediately, if threatening weather approaches. Seek additional information through local channels.

Page 17 – December 12, 2015 Client Group 2 Customization (Cellular)… layer:SOREM:1.0:Mobile_Text Environment Canada has issued a Tornado Warning for Southern Alberta

Page 18 – December 12, 2015 How Google Represents our Story

Page 19 – December 12, 2015 Thanks Norm Paulsen Service Strategies and Standards Section | Section des stratégies et des normes de service. National Services Operation Division | Division des services opérationnels nationaux Weather & Environmental Prediction and Services Directorate | Direction des prévisions & services météorologiques et environnementaux Meteorological Service of Canada | Service météorologique du Canada Environment Canada | Environnement Canada 4905 Dufferin St. Toronto, Ontario M3H5T4 Tel: Fax: