Presentation is loading. Please wait.

Presentation is loading. Please wait.

Presented 23 June 2009 at Joint Meeting of MeteoAlarm and the WIS CAP Implementation Workshop on Identifiers by Eliot Christian Identifiers and the Common.

Similar presentations


Presentation on theme: "Presented 23 June 2009 at Joint Meeting of MeteoAlarm and the WIS CAP Implementation Workshop on Identifiers by Eliot Christian Identifiers and the Common."— Presentation transcript:

1 Presented 23 June 2009 at Joint Meeting of MeteoAlarm and the WIS CAP Implementation Workshop on Identifiers by Eliot Christian Identifiers and the Common Alerting Protocol (CAP) World Meteorological Organization (WMO) Observing and Information Systems Department WMO Information System (WIS)

2 June 23, 2009Common Alerting Protocol (CAP) 2 Outline What is CAP? Why and How would MeteoAlarm use CAP? What are the issues with Identifiers?

3 June 23, 2009Common Alerting Protocol (CAP) 3 What is CAP? The Common Alerting Protocol (CAP) is a standard message format designed for All-Media, All-Hazard, communications: over any and all media (television, radio, telephone, fax, highway signs, , Web sites, RSS "Blogs",...) about any and all kinds of hazard (Weather, Fires, Earthquakes, Volcanoes, Landslides, Child Abductions, Disease Outbreaks, Air Quality Warnings, Beach Closings, Transportation Problems, Power Outages,...) to anyone: the public at large; designated groups (civic authority, responders, etc.); specific people

4 June 23, 2009Common Alerting Protocol (CAP) 4 Structure of a CAP Alert CAP Alert messages contain: Text values for human readers, e.g., "headline", "description", "instruction", "area description", etc. Coded values useful for filtering, routing, and automated translation to human languages

5 June 23, 2009Common Alerting Protocol (CAP) 5 Filtering and Routing Criteria Date/Time Geographic Area (polygon, circle, geographic codes) Status (Actual, Exercise, System, Test) Scope (Public, Restricted, Private) Type (Alert, Update, Cancel, Ack, Error)

6 June 23, 2009Common Alerting Protocol (CAP) 6 Filtering and Routing Criteria Event Categories (Geo, Met, Safety, Security, Rescue, Fire, Health, Env, Transport, Infra, Other) Urgency: Timeframe for responsive action (Immediate, Expected, Future, Past, Unknown) Severity: Level of threat to life or property (Extreme, Severe, Moderate, Minor, Unknown) Certainty: Probability of occurrence (Very Likely, Likely, Possible, Unlikely, Unknown)

7 June 23, 2009Common Alerting Protocol (CAP) 7 Typical CAP-based Alerting System

8

9 June 23, 2009Common Alerting Protocol (CAP) 9 The CAP Standard (X.1303) Compatible with legacy as well as newer transports (WMO messages, news wires, digital TV, Web Services,...) Flexible geographic targeting Phased and delayed effective time, expiration Message update and cancellation features May include inline digital images and audio Approved by OASIS as Version 1.1 (2005) Adopted as ITU Recommendation X.1303 (2006) Significant uptake, many implementations

10 June 23, 2009Common Alerting Protocol (CAP) 10 "The Plenipotentiary Conference [...] resolves to instruct the Directors of the Bureaux [...] to promote implementation by appropriate alerting authorities of the international content standard for all-media public warning, in concert with ongoing development of guidelines by all ITU Sectors for application to all disaster and emergency situations" ITU Resolution 136

11 June 23, 2009Common Alerting Protocol (CAP) 11 "Washington, D.C. - The Federal Communications Commission today adopted [an Order that] requires [Emergency Alert System (EAS)] participants to accept messages using Common Alerting Protocol (CAP) [...] The use of CAP will help to ensure the efficient and rapid transmission of EAS alerts [...] in a variety of formats (including text, audio and video) and via different means (broadcast, cable, satellite, and other networks) [...] In addition, the Order expands the EAS system by requiring participation by wireline video providers." U.S. Federal Communications Commission

12 June 23, 2009Common Alerting Protocol (CAP) 12 WMO Congress (2007) requested Secretary-General to improve the exchange of high priority data and products in support of a virtual all hazards network WMO Executive Council (2008) requested Commission for Basic Systems to follow up on CAP implementation as a matter of urgency WMO Executive Council (2009) asked the Secretariat, and invited all Members and Regional Associations, to spare no efforts in ensuring that the implementation of CAP benefits all user communities World Meteorological Organization

13 June 23, 2009Common Alerting Protocol (CAP) 13 Outline What is CAP? Why and How would MeteoAlarm use CAP? What are the issues with Identifiers?

14 June 23, 2009Common Alerting Protocol (CAP) 14 Why would MeteoAlarm Use CAP? Convergence on common standards makes any warning system more effective and efficient MeteoAlarm CAP messages would be more easily processed by software that handles CAP already Immediate Benefit: enhanced dissemination of MeteoAlarm messages Longer-term Benefit: Easier integration of MeteoAlarm with newer systems that use CAP

15 How would MeteoAlarm Use CAP? DWD SchemaCAP SchemaNotes date-time & source for multiple alerts, useful for RSS Channel of CAP alerts " //alert/info/headline //alert/info/areaDesc the event type and criticality should be indicated in the headline //alert/info/area/altitude //alert/info/area/ceiling Covert altitude between meters and feet //alert/info/responseType //alert/info/urgency //alert/info/severity //alert/info/certainty //alert/info/instruction generate the CAP element values based on DWD "crit" and "maxLevel" attribute values //alert/info/sender //alert/info/senderName //alert/info/contact generate the CAP element values from a look-up table using the DWD "src" attribute value A message in CAP format could be generated automatically for each MeteoAlarm message, in a way similar to the following DWD example

16 Crosswalk of CAP and DWD DWD SchemaCAP SchemaNotes using "issued" and "tz" attributes //alert/info/expires UTC using "valid" and "tz" attributes //warnings/area/warn/gewitter//alert/info/eventlook-up using "gewitter" and "level" //warnings/area/warn/ //alert/info/parameter/ valueName //alert/info/parameter/value Example CAP parameter: wind level 1 value as it is //warnings/area/warn/text//alert/info/descriptionuse value as it is //alert/statusvalue "Actual" //alert/msgTypevalue "Alert" //alert/scopevalue "Public" //alert/info/categoryvalue "Met" //alert/info/area/polygon //alert/info/area/geocode/ value generate CAP element values from a look-up table using the DWD area "class" and "id" attribute values

17 June 23, 2009Common Alerting Protocol (CAP) 17 Outline What is CAP? Why and How would MeteoAlarm use CAP? What are the issues with Identifiers?

18 June 23, 2009Common Alerting Protocol (CAP) 18 What are the Issues with Identifiers? A few CAP elements allow free text (unconstrained values) for identifiers, BUT: Some identifiers are harder to communicate (e.g., UUID with 32 hexadecimal characters, 550e84ac-e29b-41d4-a ) Harmonized identifiers could enhance the common understanding of message contents Harmonized identifiers are useful for aggregating across systems and over time

19 June 23, 2009Common Alerting Protocol (CAP) 19 The CAP Workshop on Identifiers As input to the relevant OASIS and ITU committees, the CAP Implementation Workshop on Identifiers is developing a Draft "Implementors Note" concerning: general requirements such as simplicity, usability, flexibility, extensibility, scalability, and deployability considerations about distributed versus centralized management approaches of various identifier schemes considerations about long-term reliability of identifier registrars, and the availability of high-performance tools for discovering attributes of any given identifier suggestions on some specific CAP identifiers

20 June 23, 2009Common Alerting Protocol (CAP) 20 Likely Suggestions on Identifiers Different alerting authorities and carriers using CAP operationally could harmonize identifiers of: particular CAP messages e.g., T23:56:38-04:00 = alert for Butler county, Alabama, 22 June at 11:56:38 alerting authorities (organizations and policies) e.g., = United States National Weather Service particular hazard threats/events e.g., GLIDE.TC MEX = GLIDE identifier for tropical storm Andres, in MexicoTC MEX

21 June 23, 2009Common Alerting Protocol (CAP) 21 MeteoAlarm input on these matters would be Very Welcome!

22 June 23, 2009Common Alerting Protocol (CAP) 22 References CAP "flyer" WIS-CAP_Geneva2008/flyer2008.doc CAP Implementation Workshop on Identifiers WIS-CAP_Geneva2009/DocPlan.html OASIS Emergency Management TC Contact Eliot Christian


Download ppt "Presented 23 June 2009 at Joint Meeting of MeteoAlarm and the WIS CAP Implementation Workshop on Identifiers by Eliot Christian Identifiers and the Common."

Similar presentations


Ads by Google