ArcGIS Exploration Framework Implementation:

A PETRONAS Approach

Mohd. Zukhairi B Abd. Latef

GIS Team Lead, Data Management Petroleum Management Unit, PETRONAS

zukhairi_latef@petronas.com.my

PETRONAS

01 May 2012

“Delivering spatial information to create value for exploration opportunities”

2012 ESRI Petroleum GIS Conference 30 Apr – 2 May Houston, Texas

Cautionary Statement All rights reserved. No part of this document may be reproduced, stored in a retrieval system or transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise) without the permission of the copyright owner. PETRONAS makes no representation or warranty, whether expressed or implied, as to the accuracy or completeness of the facts presented. PETRONAS disclaims responsibility from any liability arising out of reliance on the contents of this publication. ©2012 PETROLIAM NASIONAL BERHAD (PETRONAS)

• Introduction

• Exploration Project Data Lifecycle & Challenges

• ArcGIS Exploration Framework Overview

• Examples from exploration projects

• Conclusions & Opportunities

Outlines

Who we are in E&P – Spatial DM & GIS

• Manage Geospatial Data (ArcSDE, Corporate SS DB) – Data model, DQM, Geodetic Integrity, GIGS

• Integrate GIS with E&P Databases & deliver through GIS (PiriGIS™, ArcGIS, others) including mapping/cartographic services

• Lead & drive GIS technology in PMU to support E&P

• Data custodian for Domestic E&P assets through PPGUA – Spatial Data Governance

Source: www.petronas.com

Objectives

1. To provide standards from Data Management to End-Users (Exploration) to structure data directories based on GIS theme or categories

2. To pre-requisite for archiving GIS Project into proper database management system for future data usage and sharing

Standard package/components rolled-out at PETRONAS for ArcGIS Desktop users in Dec. 2011

ArcGIS Exploration Framework

• Ensuring data is kept up-to-date • A consistent evaluation with clear audit trail is applied

throughout exploration lifecycle • Data are available for ongoing exploration evaluation process

§ In April 2011, PMU through Data Management & Petroleum Resource Exploration have embarked on an initiative/project to manage, archive and deliver EXPLORATION datasets in structured and easily accessible manner.

§ The goal is to have a structured datasets, managed in single database to: § Support PETRONAS exploration activities

§ As input to attract new investors during block evaluation with complete

regional/play datasets

Malaysia Gravity & Magnetic Data Archive & Management

into GIS

Exploration GIS Database & System Development for Basin

Assessment & Promotion

2011 GIS for Exploration Initiatives (Domestic)

A History Behind…….

Exploration Project Data Lifecycle

Project Created

Data Identification

• Technical reports

• Seismic Coverage (2D/3D)

• Wells • Previous

Interpretation Projects

• Regional Studies

• Basin Studies • Prospect &

Lead Studies • Acquisition

Data Management & GIS

G&G Project Data Creation

(mapping)

• Use existing data

• Load new data

Interpretation & Reporting

• New data generated

• Technical reports

• Maps

Corporate Databases

• Any ArcGIS data for this area? • I need regional geology layer to

see the structures.. • How do I get play map for this

basin? • I have a map from the report, can

anyone digitize this contour map for me?

• Can you share this map in ArcGIS format?

• Can I copy your shapefiles?

Challenges in current exploration data and mapping …

Cultural data duplicated in all mapping applications – different versions, outdated, inconsistent

Layers from digitized sources do not reach databases i.e. play/prospect map from partners (PSC’s), project teams, etc

Poor update procedures E&P is producing data files with inconsistent content – styles, symbology, CRS, templates, etc

Value of project data in interpretation/playmap does not reach other teams – individual desktop (C drive)

Geopolitics Seismic Interpreted MAPS

Well

Front-End (Users)

ArcGIS Desktop

Petrel 2011 Users (Future)

PiriGIS Users (Under revision)

GIS Map Services

GIS Map Services

GIS Layers/Data Corporate Spatial

Database (Master)

Master data held in Data Management, TCDM (-ro- to end users –rw- to Data Management)

ArcGIS Server (Previously SDE)

• All Spatial Feature Classes implemented under schema with Local and Global CRS

• Spatial Feature Classes must followed our Data Model or other specific industry data model

• Final version of data (QC/QA)

Back-End (Spatial Data Management)

10_Global

20_Corporate

Oracle Client

ArcCatalog

Overview of ArcGIS Framework – Back to Front End

Interface (Structured Folders)

• GIS Layers deliver in .lyr file

• Layer organized by data types with pre-defined symbology

Roll-Out: ArcGIS Exploration Framework Components

ArcGIS Framework

A Consistent directory –

Theme-based, CRS, Map Templates

Standard Exploration Tool using

ArcGIS AddIns

Standard GIS Project Data

Sharing

Unified Spatial Theme with Standard

PETRONAS Spatial Data

Model (PSDM)

• Layer Categorization • Prospect/Leads

Information • ArcGIS Framework

Admin. Module

1 3

2

4

01_Administrative_Boundaries 02_Environmental 03_Geotechnical (Developing) 04_Geology 05_Geophysics 06_Hydrocarbon_Occurences 07_Hydrography 08_Oceanography (Developing) 09_Imagery 10_Project_Data 11_Safety_Operations 12_Topography 13_Wells

Unified Spatial Theme/Categories with standard PETRONAS Spatial Data Model (PSDM)

• Currently 11 Themes in SDE, Layer Files – Adding 2 additional Themes. Workflow, Process & Guidelines established

• Based on end-user input & data management approach - as much adopt industry standards i.e. SSDM

• Attributes/Domains are based on industry practices i.e. Hydrocarbon Occurences > Discovered Resources – based on SPE Resource Definition (Developing)

• Data standardization allows an easy application of a standard map symbology

1

Unified Spatial Theme/Categories with standard PETRONAS Spatial Data Model (PSDM)

Environmental

Geology

Geophysics

Hydrocarbon Occurrences

Hydrography

Imagery

Infrastructure

Regional Studies

Administrative_Boundaries

1. Country Based (Malaysia, Indonesia, Iraq, etc)

2. Theme Based (Geology, Geophysics, etc)

>500 Layers (Petroleum Geology) >1000 Layers (Previous Study)

1

Theme Data Layers Administrative Boundaries PSC Blocks, Open Blocks, International Boundary, State Boundary,

Gazetted area, Offshore limits

Environmental ESI, Coral Reef, oil spill, environmental sensitivity index

Geology Subsurface, lithology, basins, geochemistry, fault, play map

Geophysics Seismic 2D, Seismic 3D, Gravity Magnetics, 4D, CSEM/Seabed Logging, Seabed Surveys

Hydrocarbon Occurrences Field Outlines, Ring Fence, Play, Prospect/Leads

Hydrography Bathymetry

Imagery SAR, GeoCover 2000, SPOT 2.5, Ikonos 0.8m,

Infrastructures Platforms, Pipelines, Cables, Subsea facilities

Project Data Petrel, OpenWorks

Safety Operations Offshore activities, NOOP, NTM

Topography Coastlines, Topography, Elevation models, LIDAR

Wells Well information, well deviation

Consistent Directory based on Data Theme/Categories

• Applied throughout SDE, Folders, Map Services

• Working & Published Folders

2

01_Global

02_Corporate

03_Project

00_Automation

X:\pmu_exploration_GIS

• Tools/middleware which related to geoprocessing • Including standard folder template, mapping template, symbology, etc

• Data include 3rd party datasets procured globally • i.e. IHSE, Tellus, GETECH, etc

• Regional and local level data from previous study/projects (including purchased data)

• Dynamic data subject to regular update • possible to push to 20_Corporate layers

Coordinate System: WGS-84

Coordinate System: WGS-84 & Local

Coordinate System: Local

Coordinate Transformation

template

• Covers entire world

• Master data held in TCDM – source from Master GIS Database

• Read-Only (RO)

• Access via Layer File (*.lyr)

• Data owner (i.e. IHSE, Tellus, GETECH) is responsible for quality, GIS team to track metadata

• Data covers regional scale

• Data split by Country/regions

• Read-Only (RO)

• Access via Layer File (*.lyr)

• Data owner (i.e. Line dept.) is responsible for quality, GIS team to track metadata

• Populate from PSC Submission, Surveys, Projects, Services Providers, etc

• Data covers at small scale; basin, prospect, field, etc

• Projects split by basins/provinces

• Standard Template for project. File Geodatabase will be main format for GIS datasets

• Involved subsurface geoscience applications data – middleware/integration needed

Standard Windows Folder Structure

-RO- -RO- -RW- (Project Entitlement)

-RO-

• Folder accessibility managed by ArcGIS Framework Administrative Module

• Assign by Group in PMU

2

ArcGIS Framework Administrative Module: Layer Categorization & Prospect Information Tool

Administration: 1. User Entitlements – layers, folders, group 2. Tool restrictions 3. User Activities Tracking

User Register (ArcGIS Framework)

- Folder Entitlement - Project Entitlement

- Tool Entitlement

Framework Package Deliver

Project Data Lifecycle

3

ArcGIS Framework Desktop User Interface: Geology Layers

Layer Categorization Tool

ArcGIS Framework Toolbar

3

Geology Layers: Defined by Regional, Basin, Play, Prospect

Regional Geology

Basin/Play

Prospect

3

Play Maps Data from Previous Study: Build a “story” of the area

• Data to help build up a story: • Why is there (not

hydrocarbon) in an area? • Where are the accumulations? • Where is the source/kitchen?

3

Portfolio Management Tool (Prospect & Lead Information): Centralized, consistent and sharing

Workflow

ArcMap tool

3

Project Data Sharing

• Project folder will be managed by GIS users – following GIS project template

• Data covers at small and large scale; basin, prospect, field, etc

• Project split by basin/provinces

• Standard template for project for ArcGIS end-users to store and manage GIS project in shared folders – to be archive at the end of project

• Naming convention of project folder must follow standard

4

Project Data Sharing Workflow & Lifecycle

Start Project

• Set-up CRS • Naming

Convention • Project

Metadata • Copy PSDM

template

GIS Project

• Create/edit data • Georeferencing/

digitizing • Attributes • Mapping

Final Archival

• Final version of data/layers

• Final version of maps

• Archive into Corporate Layers/SDE

4

ALL IN PSDM (Project)

1

2

3

• GIS Team • Focal GIS Staff

• Geoscientists (Users)

• GIS Team • Focal GIS Staff

• Project Data • Cultural from Corporate Layers

Example: Basin Study – Malacca Straits 4

Fractured basement dominated within the SE Malay Basin area

Example: Fractured basement study in Malay Basin 4

Portfolio Management (Prospect/Leads)

Resources Data (Spreadsheet)

Prospect Database (ArcGIS)

Maps (Prospect Outlines)

Integrate Maps & Data

Prospect information

ArcMap Portfolio Management Tool

4

Example: Petrel Integration (Pilot)

Petrel Gridding and visualization

Export point through ArcMap

• Workflow established (import/export) • Serve cultural data through map

services based on spatial data categories

4

Conclusions Value Add

§ Standard GIS data management and delivery were introduced to manage these datasets – Theme/Category, Folder Structures, Published Layers

§ GIS Project Lifecycle Guideline and Workflow introduced in exploration – create, archive and share across organization

§ Standardize workflow for portfolio management (prospect & lead) using ArcGIS – clear data audit & QC by explorationists

§ New ways promoting our Malaysia Blocks using GIS – standard exploration package during data review from potential investors

Opportunities….

• Standard Legend & Symbology for Geology Layers (>1500 Layers)

• ArcGIS Online (Cloud) for Exploration Map Services – based on Theme/Categories, Regional & Project Datasets

• Petrel-ArcGIS Project Data Integration

• Exploration Project Data Management (Structures & Interoperability) – RESQML?

Back-to-Basic of GIS: Geodetic Integrity