OASIS Organization for the Advancement of Structured Information

OASIS Organization for the Advancement of Structured Information Standards Emergency Management Presentation Guidelines

Presentation Purpose n Education and orientation l l n By members By prospective members Promotional briefings l l By members By prospective members n Ex. To their mgmt, for approval to join OASIS

Slide Decks to be produced n n n Technical Committee (TC) overviews Sub-Committee (SC) overviews Work product overviews

Maintenance Schedule n Updated bi-annually l n As of March 31 and September 30 Updated by Emergency Management Adoption (EMA) Collateral SC l Updates provided by/solicited from respective TC and SC’s

Targets n n 1 -2 slide introductions Up to 10 slide product overviews

Technical Committee Introduction Page n n n Mission statement Vision statement Primary beneficiaries of TC’s efforts

TC intro example Emergency Management (EM) Technical Committee (TC) n Mission l n Vision l n Create emergency-related standards for data interoperability. Issue once, for distribution to all with a need to know, and authority to receive. Primary Beneficiaries l Public safety officials, broadcasters, vendors

Sub-Committee (SC) and Work Product Listing n Sub-Committee l l Purpose Work product listing n Work product sub-products

SC and work product listing example EM TC Sub-Committee (SC) and Work Product Listing n Message and Notification (Msg. Not) l Purpose n l Incident communications within emergency management community, and for delivery to the public Work Products: n n Common Alerting Protocol (CAP) Emergency Data Exchange Language (EDXL) • • Distribution Element (DE) Resource Messaging (RM) Hospital Availability (HAVE) Situation Report (Sit. Rep)

Work Product Overview n Work product introduction l n n n Purpose statement, current version, status Adoption Benefits summary Features summary Timeline Additional information l Focus on clarity, highlight key feature, implementation challenges, etc.

Product introduction example Common Alerting Protocol (CAP) n Purpose l n Current version l n Open, non-proprietary digital message format for all types of alerts and notifications, public, restricted and private. Supports routing, filtering and conversion to other formats. v 1. 1 Errata 28 August 2006 Status l l v 1. 2 at technical committee review stage. ETA Q 2 2010 v 2. 0 efforts to commence when v 1. 2 completed

Product adoption example CAP Adoption n n International Telecommunications Union (ITU) standard #___ US Integrated Public Alert and Warning System (IPAWS) Canadian National Alert Aggregation and Dissemination (NAAD) system Canadian Multi-Agency Situational Awareness System (MASAS) initiative

Product benefits example CAP Benefits n n Issue an alert once for distribution through a multitude of systems Easily converted into last mile formats, including SMS, RSS, etc. Single system can be used to support alerts of all urgencies, severities and certainties Messages may be filtered based on urgency, severity and certainty, category, location, etc.

Product features example CAP Features n n n n Public, private and restricted messaging Updates and cancels Actual, testing and exercises Every alert defined by urgency, severity and certainty Categorized to common themes. Ex. Meteorological Alert area may be defined using GIS, and or geocodes Supports resources Adaptable to specific user communities

Product timeline example CAP Timeline n n n n Conceived and developed by Art Botterell Endorsed and sponsored for standardization by US Partnership for Public Warning (PPW) 1. 0 published March 2004 1. 1 published October 2005 1. 1 Errata published October 2007 ITU Adoption ___ 1. 2 ETA April 2010 2. 0 ETA 2012

Product additional information example CAP is in the background profile: CAP-CP: Location: 0. 3 1301006 NBMASASui 10286 DAllport 2009 -07 -17 T 23: 49: 40. 0436089+00: 00 Exercise Public fr-CA profile: CAP-CP: 0. 3 Routier - Fermeture de route Alert Monitor Immediate en-CA Minor Roadway - Roadway Closure Observed Monitor Doug Allport Immediate 2009 -07 -18 T 12: 00+00: 00 Minor 2009 -07 -19 T 12: 00+00: 00 Observed Doug Allport Doug Allport Routier - Fermeture de route - Doug Allport, Exercise 2009 -07 -18 T 12: 00+00: 00 http: //www. gnb. ca/0113/index-e. asp 2009 -07 -19 T 12: 00+00: 00 Transport Doug Allport This is a test Road Closure Alert profile: CAP-CP: Event: 0. 3 Free form text field road. Close More free form text here http: //www. gnb. ca/0113/index-e. asp NB DOT 888 -5555 layer: CAPAN: event. Location: point Transport 45. 2449203344103, -66. 11091613769532 profile: CAP-CP: Event: 0. 3 road. Close 1301006 - Saint John CAP-CP: Location: 0. 3 layer: CAPAN: event. Location: point 1301006 45. 2449203344103, -66. 11091613769532 1301006 - Saint John Issuer interfaces with form, IVR, custom application, etc. Issuing Application produces CAP Aggregator collects and shares CAP Distributor converts CAP to common and proprietary protocols Recipient interfaces with common products and services. Ex. Television, phone, . . .

Product additional information example CAP is adaptable n US Integrated Public Warning System Profile l n Canadian Profile of CAP (CAP-CP) l n Defines event codes and location code references and requirements, in support of Emergency Alert System and other legacy systems Defines event codes and location code references and requirements in support of national needs, including automated translation Canadians are including event location references using CAPAN CAP Event Location Layer

Presentation Summary n Purpose l l n Education and orientation Promotional briefings Slide decks l l l Technical Committee (TC) introductions TC SC/work product listings Product overviews