standards and oil spill response

®

Applying Open Standards

in Oil Spill Responses

George Percivall, OGC Chief Engineer

TECTERRA Geomatics Showcase 2013

5 November 2013

Copyright © 2013, Open Geospatial Consortium

OGC®

Pipeline map: Any incidents near you?From small to large-scale spills to fires, explosions and worker deaths

By Michael Pereira, CBC News Last Updated: October 22, 2013


OGC®

Deepwater Horizon – Gulf of Mexico, April 2010

BP Deepwater Horizon Oil Sill, Incident Specific Preparedness Review (ISPR), Final Report January 2011


OGC®

Oil Industry Response to Deepwater Horizon

• Oil and Gas Producers (OGP) formed a 3-year Joint Industry Project (JIP) funded by oil industry members.

• Oil Spill Response JIP managed by IPIECA for OGP based on its long-standing experience with Oil Spill Response

• OSR JIP composed of several Work Programs (WPs)– WP1 - In-Water Surveillance

– WP2 - Surface Surveillance

– WP3 - Modelling & Prediction

– WP4 - Metocean Databases

– WP5 - GIS/Mapping and Common Operating Picture


http://oilspillresponseproject.org/

http://oilspillresponseproject.org/

OGC®

OSR JIP WP5 GIS/Mapping and Common Operating Picture

• Produce a Recommended Practice for GIS/Mapping– Support of Oil Spill response using of GIS technology – Geo-information in a “Common Operating Picture” for management

of the response

• OGP and IPIECA choose OGC to lead an open process to develop a recommended practice based on open standards

• The OGC Interoperability Program– An essential part of OGC’s fast, effective, inclusive user-driven

process to develop, evolve, test, demonstrate and promote OGC Standards.


OGC®

OGC IP Introduction


Link to Video: http://www.opengeospatial.org/ogc/programs/ip

http://www.opengeospatial.org/ogc/programs/ip



®

OGC Interoperability Program

Concept Development


5 November 2013


OGC®

OGC Concept Development

• Initiative to assess emerging technologies & architectures to support interoperability initiatives and open standards.

• Process– 1. Request for Information (RFI)

• Wide request for input on relevant technologies and open standards • RFI contains draft Recommended Practice

– 2. Engineering Workshops • Workshop to discuss and advance the concepts in the RFI• Workshop participants selected from the RFI Responses

– 3. Reference Architecture and Feasibility Report• Engineering Report of open standards and architecture views • Describe implementations indicating feasibility and maturity


OGC®

OGC Concept Development example:Fusion Standards Study and Recommendation

• Fusion: “Processes of combining data and information to improve detection, identification, and characterization of entities”– “To-Be” fusion environment based on open standards

• Steps– Request for Information (RFI) – Workshop to consider RFI responses– Engineering Report

• Recommendations for advancing fusion based on open standards.• http://portal.opengeospatial.org/files/?artifact_id=41573

• Follow-on– Implementation in OGC Testbeds and Sponsoring Agency

Copyright © 2010, Open Geospatial Consortium, Inc.

http://portal.opengeospatial.org/files/?artifact_id=41573



®

OGP/IPIECAOil Spill Response COPConcept Development


5 November 2013


OGC®

OGP-IPIECA Oil Spill Response COP

• Oil Spill Response Common Operating Picture 1. Request for Information (RFI) – Responses due 30 October

2. Engineering Workshops – December in UK, January in USA

3. Prepare a Reference Architecture and Feasibility Report, 2014

• Team – OGP (International Association of Oil and Gas Producers)– IPIECA (Global oil and gas association for environmental and

social issues) – Resource Data Inc.– OGC


OGC®

Oil Spill Response COP: Draft Recommendation in the RFI

• Oil Spill Response Enterprise Viewpoint – Deepwater Horizon – COP Definition, Users and Scenarios

• Geospatial Information Viewpoint– Base map and reference information– Drill and incident specific information

• Delivering Geo Information Viewpoint– Web services – Schemas and encodings– Disconnected users– Records retention


OGC®

Deepwater Horizon Review

• Barriers to total awareness during the Deepwater Horizon:– Lack of agreement on data needed to be tracked and transmitted;– Vast geography of the response area of operations;– Lack of availability of appropriate interoperable communications;– Limited ability to push real-time data thru the response organization– Different computing standards.

• “Incompatibility of proprietary databases and software used by private sector appeared to be a hindrance to developing a universal Common Operating Picture (COP)”– Integrating data from multiple, restricted sources slowed the

development of a complete and an accurate COP


BP Deepwater Horizon Oil Sill, Incident Specific Preparedness Review (ISPR), Final Report January 2011

OSR Enterprise Viewpoint

OGC®


RFI Candidate definition of OSR COP

• A COP is established and maintained by gathering, collating, synthesizing, and disseminating of incident information to all appropriate parties involved in an incident.

• Achieving a COP allows on−scene and off−scene personnel to have the same information about the incident, including the availability and location of resources, personnel, and status of requests for assistance.

• Additionally, a COP offers an overview of an incident thereby providing incident information which enables the Incident Commander (IC), Unified Command (UC), and supporting agencies and organizations to make effective, consistent, and timely decisions.

• In order to maintain situational awareness, communications and incident information must be updated continually.

• Having a COP during an incident helps to ensure consistency for all emergency management/response personnel engaged in an incident.


OGC®


Common Operating Picture

GeoSpatial COP


OGC®


Scenarios for use of COP

• Command Section – COP used in daily command briefings during a response. – Adapted to meet the particular needs of a response due to the

physical environment and political environment.

• Planning Section– COP used to communicate plans to other teams on response.

• Operations Section– COP to communicate to the actual field crews completing the tasks.

• Legal Team Use – COP provides historical response data used in long-term litigation


Government of AlbertaAlberta Emergency Management Agency

Government of Alberta Provincial Operations Centre (POC) Use of Common Operating Picture

Dave Galea, Executive Director Public Safety Initiatives Alberta Emergency Management Agency, Ministry of Municipal Affairs

Government of AlbertaAlberta Emergency Management Agency

Government of Alberta use of COP • COP ensures all leaders across government have current

situational awareness based on verified information. – Lead organization (ministry or agency) is responsible for creating

and distributing an information document for senior officials and decision makers called common operating picture report (COPR).

– AEMA has defined the information contained in a COPR

• COP used to good effect since 2011 when Provincial Operations Centre activated to Level 2+– GoA Rainbow Pipeline / Slave Lake first– Wildfires May 2011– Pace Oil Event 2012– Plains Midstream 2012– Mackenzie County Wildfires 2012– Shaw Court IT Outage 2012 (GoA Business Continuity event)

OGC®


Geo-Information Viewpoint - considerations

• Origin of Spill– Wellhead, pipeline, infrastructure (refinery or terminal), Vessel – Land-based vs. Marine– Arctic vs. Temperate, Desert or Tropical

• Scope/Size – Tiered Response– IPIECA defines multi-tiered model for preparedness and response to

an oil spill incident based on size and location of spill

• Private (Operator sensitive) vs. Public use• Availability of geospatial info dependent on location

Geospatial Information Viewpoint

OGC®


Organization of Geospatial Information

• Base map and reference information– this information typically exists in some form prior to the occurrence

of a spill incident, and may be gathered and updated routinely as newer information becomes available. Base map and reference information may not be pertinent to a specific incident.

• Incident-specific information– this includes all of the relevant information that is generated

following a spill incident, and pertains specifically to that incident.


OGC®

Base map and reference information

• Administrative Boundaries & References Information• Bathymetry & Hydrography• Topography• Imagery & Remote Sensing• Natural Resources, Habitats, & Managed Areas• Navigation & Marine Infrastructure• Public Safety & Terrestrial Infrastructure• Oil and Gas Infrastructure• Response Planning• Restoration• Weather, Oceanography & Natural Hazards



OGC®

Environmental Sensitivity Index (ESI) map symbology defined by IPECA-477


OGC®

Drill and incident specific information

• Abstract, Spill Summary & Reporting• Damage Assessment• Oil Spill Response Operations• Operator Services & Support



OGC®

Emergency Response using Web Services


Delivering Geo Information Viewpoint

See Video (from 0:45 to end) http://www.youtube.com/watch?v=UUtFUGT3VaE&list=PLQsQNjNIDU862xKukmrpDkkjNI55syDGN&index=17

http://www.youtube.com/watch?v=UUtFUGT3VaE&list=PLQsQNjNIDU862xKukmrpDkkjNI55syDGN&index=17







OGC®


Delivering Geospatial Information

• Interoperability architecture• Web service delivery to users• Schemas, metadata and encodings• Real-time feeds and Alerts• Disconnected user operations• Records retention and provenance


OGC®

OSR COP delivery architecture



OGC®

Web service delivery to users

• Context sharing– OGC Context Document

• Web mapping services– OGC WMS, WMTS

• Portrayal and symbols– OGC SLD, SE

• Access to features and coverages– OGC WFS, WCS

• Catalog/registry services– OGC CSW

• User identity and management services



OGC®

Information schemas, metadata and encodings

• Metadata – for services and long-term archives– ISO 19115:2003 – Geographic Information – Metadata. – Energistics developing an Energy Industry Profile of ISO 19115-1

• Encoding formats– Open standards for encoding feature data include OGC Geography

Markup Language (GML), JSON– Open standards for encoding coverage data include NetCDF, HDF,

GRIB, BUFR and TIFF

• Application schemas– Computer-readable data description for data management– Common and correct understanding of the data for diverse users



OGC®

© 2013 Open Geospatial Consortium

Geospatial Data Application Schemas

– UML frequently used to specify conceptual schemas for geographic information using ISO 19000 series

– Encoding rules support conversions of such schemas to implementation schemas, e.g. to GML application schemas

• Potential Oil Spill Applications Schemas– OGP Seabed Survey Data

Model (SSDM) – Consider environmental

data model development– Define a focus group with

the needed expertise

https://portal.opengeospatial.org/files/?artifact_id=46324




OGC®

Inputs to the Response Center

• Real-time feeds– Real-time and near-real-time sensing of the spill incident provides

situational awareness for the response center. – Examples:

• Weather and Vessel tracking (AIS)• Sensor observations including imagery and video• Remotely Operated Vehicles, airborne and space-borne platforms

– OGC Sensor Web Enablement (SWE)

• Alerts– Receives and send alerts which become part of COP– Common Alerting Protocol (CAP) and Emergency Data Exchange

Language (EDXL) maintained by OASIS



OGC®


Disconnected user operations

• Mobile unit provision– Use Case

• Before deployment, mobile device is provisioned with COP information • Support queries on stored COP while disconnected. • Updates made while disconnected, synced later to Response Center

– OGC GeoPackage

• Printed maps from COP– Produce large format printed maps at regular intervals, at the

Response Center– Map templates and format, ensuring maps provide clear and

unambiguous cartographic symbols


OGC®


Records retention and provenance

• Maintain accurate and comprehensive incident files, including complete record of major steps taken to resolve the incident for legal, analytical, and historical purposes

• “Snapshots” of the COP and the response center database need to be made on a periodic basis and transferred to a location remote from the Response Center.

• Documenting the provenance of information with metadata – W3C provenance (PROV) specifications may be applicable


OGC®

GEOSS Oil Spill Scenario


http://www.ogcnetwork.net/pub/ogcnetwork/GEOSS/AI_Pilot_Demo/index.html?movie=7


http://www.ogcnetwork.net/pub/ogcnetwork/GEOSS/AI_Pilot_Demo/index.html?movie=7

OGC®

OGP-IPIECA Oil Spill Response COP

• Schedule– Request for Information:

• Responses by 30 Oct. • Still open to input

– Engineering Workshops• December in UK• January in USA

– Reference Architecture and Feasibility Report, early 2014

Responses to RFI• ASA Science• Astrium• EMSA• Environmental Resource Mgmt• Esri• ExactEarth• Finland SYKE• GeoCento• IHO• MDA• NOAA ERMA • NAPSG• Oceaneering• Primal Innovation Technologies• Quantum Spatial • SINTEF • Witt Obriens


standards and oil spill response

Technology