1 / 18

OASIS Organization for the Advancement of Structured Information Standards

OASIS Organization for the Advancement of Structured Information Standards. Emergency Management Presentation Guidelines. Presentation Purpose. Education and orientation By members By prospective members Promotional briefings By members By prospective members

kylee
Télécharger la présentation

OASIS Organization for the Advancement of Structured Information Standards

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OASISOrganization for the Advancement of Structured Information Standards Emergency Management Presentation Guidelines

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

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

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

  5. Targets • 1-2 slide introductions • Up to 10 slide product overviews

  6. Technical Committee Introduction Page • Mission statement • Vision statement • Primary beneficiaries of TC’s efforts

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

  8. Sub-Committee (SC) and Work Product Listing • Sub-Committee • Purpose • Work product listing • Work product sub-products

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

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

  11. Product introduction example Common Alerting Protocol (CAP) • Purpose • 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. • Current version • v1.1 Errata 28 August 2006 • Status • v1.2 at technical committee review stage. ETA Q2 2010 • v2.0 efforts to commence when v1.2 completed

  12. Product adoption example CAP Adoption • 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

  13. Product benefits example CAP Benefits • 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.

  14. Product features example CAP Features • 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

  15. Product timeline example CAP Timeline • 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

  16. Product additional information example CAP is in the background <?xml version="1.0" encoding="utf-8"?> <alert xmlns="urn:oasis:names:tc:emergency:cap:1.1"> <identifier>NBMASASui10286</identifier> <sender>DAllport</sender> <sent>2009-07-17T23:49:40.0436089+00:00</sent> <status>Exercise</status> <scope>Public</scope> <code>profile:CAP-CP:0.3</code> <msgType>Alert</msgType> <info> <language>en-CA</language> <event>Roadway - Roadway Closure</event> <responseType>Monitor</responseType> <urgency>Immediate</urgency> <severity>Minor</severity> <certainty>Observed</certainty> <audience>Doug Allport</audience> <onset>2009-07-18T12:00:00+00:00</onset> <expires>2009-07-19T12:00:00+00:00</expires> <senderName>Doug Allport</senderName> <headline>This is a test Road Closure Alert</headline> <description>Free form text field</description> <instruction>More free form text here</instruction> <web>http://www.gnb.ca/0113/index-e.asp</web> <contact>NB DOT 888-555-5555</contact> <category>Transport</category> <eventCode> <valueName>profile:CAP-CP:Event:0.3</valueName> <value>roadClose</value> </eventCode> <parameter> <valueName>layer:CAPAN:eventLocation:point</valueName> <value>45.2449203344103,-66.11091613769532</value> </parameter> <area> <areaDesc>1301006 - Saint John</areaDesc> <geocode> <valueName>profile:CAP-CP:Location:0.3</valueName> <value>1301006</value> </geocode> </area> </info> <info> <language>fr-CA</language> <event>Routier - Fermeture de route</event> <responseType>Monitor</responseType> <urgency>Immediate</urgency> <severity>Minor</severity> <certainty>Observed</certainty> <audience>Doug Allport</audience> <onset>2009-07-18T12:00:00+00:00</onset> <expires>2009-07-19T12:00:00+00:00</expires> <senderName>Doug Allport</senderName> <headline>Routier - Fermeture de route - Doug Allport, Exercise</headline> <web>http://www.gnb.ca/0113/index-e.asp</web> <category>Transport</category> <eventCode> <valueName>profile:CAP-CP:Event:0.3</valueName> <value>roadClose</value> </eventCode> <parameter> <valueName>layer:CAPAN:eventLocation:point</valueName> <value>45.2449203344103,-66.11091613769532</value> </parameter> <area> <areaDesc>1301006 - Saint John</areaDesc> <geocode> <valueName>CAP-CP:Location:0.3</valueName> <value>1301006</value> </geocode> </area> </info> </alert> Issuer interfaces with form, IVR, custom application, etc. Aggregator collects and shares CAP Issuing Application produces CAP Recipient interfaces with common products and services. Ex. Television, phone, ... Distributor converts CAP to common and proprietary protocols

  17. Product additional information example CAP is adaptable • US Integrated Public Warning System Profile • Defines event codes and location code references and requirements, in support of Emergency Alert System and other legacy systems • Canadian Profile of CAP (CAP-CP) • 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

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

More Related