RESQML™ update, Reservoir and Earth Modeling

Data Exchange Standard Status

Jean Francois Rainaud, IFP Energies Nouvelles

London Conference, 31st May 2011

Outline

• Motivation• RESQML V1.0 Document• Demonstrating the implementation of V1 • Roadmap• Summary

Motivation: Why RESQML?

• Reservoir modeling data standard:– To facilitate integrated workflows– Multiple applications with multiple vendors across

multiple petro-technical domains• Robust workflows for the larger vendors• Innovation opportunities for the smaller vendors• Multiple use cases for the business

– Business requires increased traceability• Meta-data as important as the data

– Models are bigger and more complex

$

DA

TA

P

RO

CE

SS

ING

&

VA

LID

AT

ION

DA

TA

A

CQ

UIS

ITIO

N

DA

TA

AN

AL

YS

ISIN

TE

RP

RE

TA

TIO

N

& S

YN

TH

ES

IS

GE

OM

OD

EL

LIN

G

RE

SE

RV

OIR

S

IMU

LA

TIO

N &

P

RE

/PO

ST

P

RO

CE

SS

ING

FIE

LD

M

AN

AG

EM

EN

T &

«

SU

RF

AC

E»

A

RC

HIT

EC

TU

RE

EC

ON

OM

Y

DA

TA

P

RO

CE

SS

ING

&

VA

LID

AT

ION

DA

TA

A

CQ

UIS

ITIO

N

DA

TA

AN

AL

YS

ISIN

TE

RP

RE

TA

TIO

N

& S

YN

TH

ES

IS

GE

OM

OD

EL

LIN

G

RE

SE

RV

OIR

S

IMU

LA

TIO

N &

P

RE

/PO

ST

P

RO

CE

SS

ING

FIE

LD

M

AN

AG

EM

EN

T &

«

SU

RF

AC

E»

A

RC

HIT

EC

TU

RE

EC

ON

OM

Y

E&P business processesD

AT

A

DE

CIS

ION

3D RESERVOIR MODELLING & SIMULATION

Towards better integration for:

Better understanding & better risk assessment at all levels

Reducing the cycle time « data to decision »

<RESQML> ® Domain coverage (graphic adapted from Roxar's IRAP/RMS).

Seismic interpretation

• Reservoir interpretation, modeling and simulation activity require a wide range of disparate disciplines & tools.

To Facilitate Integrated Workflows

To Improve Robustness of Data Transfers

• Horizon data was OK• Damaged in transfer:

– Horizons/ wells / grids relative positioning

– Windows/Linux binary file formats

– Well trajectories lost depth reference

• 200+ onshore wells

– 3D Grid inverted in depth / elevation

Multi-company, multi-application data transfer

RESCUE and the move to RESQML

7

RESCUE MODEL REPRESENTATION

• 1995: RESCUE– A consortium of more than 20 sponsoring

petroleum companies and application vendors – C++ libraries describing the reservoir in a neutral

format– Limitations: no contextual data, no relationship

between objects still loss of data along the workflow

• 2009: New Technologies Give Rise to New Solutions:– XML unlocks new possibilities for data integration

and application interoperability– Launch of RESQML Special Interest Group within

the RESQML consortium

• 2011: January Release of RESQML v1.0– June Planned V1.1

Outline

• Introduction• RESQML V1.0 Document• Demonstrating the implementation of V1 • Roadmap• Summary

RESQML v1.0 – Already More than RESCUE on Workflow & Usage

9

Interpretation Activities

Static Reservoir Modeling

Dynamic Reservoir Simulation

HH FF

HH FF GHH FF GGGG

RESQML file(s)

HH

FFHorizons

Faults GGGG 3D Grids

Filled 3D Grids

RESQML Top Level Document

SpatialReferenceSet

InterfaceFeatureSet

GriddedVolumeSet

[0:1]

AreaOfInterest

[0:1]

[1:1]

[0:1]

PropertyKindSet

[1:1]PropertyGroupSet

[0:1]

RESQML Document Structure

• Robust yet flexible– Spatial Reference Set is required– No other document sets are required

• Data Object Traceability– Unique GUID’s and Dublin Core meta-data

• Structural data: InterfaceFeatureSet– Horizons and Faults

• 3D discretized data: GriddedVolumeSet– Grids, Properties, Adjacency, and Blocked Wells

• Generic and standard property management system to ease cross vendors mapping– (Parent Pty /specialization/names/ SI Units/ limits)

RESQML Top Level Document

SpatialReferenceSet

InterfaceFeatureSet

GriddedVolumeSet

[0:1]

AreaOfInterest

[0:1]

[1:1][0:1]

PropertyKindSet

[0:1]

gridSet

RootGrid

BlockedWellSet

Non-Standard AdjacencySet

Horizon Fault

[0:*] [0:*]

[1:*]

[0:*]

[0:1]

[0:1]

PropertyGroupSet

[1:1]

LocalGrid

[1:*]

ExplicitRepresentation

[1:1]

RESQML v1.0 – Exchanged Information

HH FF

GG

GG

pointSetscurvesgrid2DtriangleshybridGrid2D

IJ CoordinateLine Support

GG

GG GG

XML file

GML XSD schema

HDF5specs

WITSML XSD schema

PRODML XSD schema

RESQML XSD schema

Structure DataProcessed by proprietary libraries.

Dublin Core XSD schema

HDF file(s)

Processed by HDF libraries.

Refers to

RESQML v1.0 - Document Architecture

13

coordinate system (CRS) definitions

metadata description

Production dataWell data

Giga-Cell Models data storage

RESQML DOCUMENT : DocumentTITLE.resqml + DocumentTITLE.resqml.h5

RESQML document - part 1: XML file

• High readability for humans…

• High capability to be processed by computers.

• Fitted for long term archives

CRS definitionsCRS1

CRS2

CRS3

CRS4

Interface definitionsHorizon1

Horizon2

References a path in the associated HDF file

RESQML document - part 2: HDF file(using HDFview)

Set of triangles defined by 3 indexes of vertices.

Set of points (X, Y, Z)

Set of points (X,Y,Z) structured in a 2D array

Set of representations

• De facto long term accessibility

• Viewer/Editor provided byHDF Group: HDFview

• Multi-platform Application with easy access to the data.

HDF5 Storage Performance

• Comparison of HDF5 storage efficiency with storage for active cells only

3 Reservoir Models

An example :Implementing RESQML V1 Import/Export into TOTAL in-house geosciences platform (Sismage)• 2 needed ToolKits:

– Proxy Generator:

•Automatic creation of classes (and their attributes and relations) corresponding to the RESQML data model which is described in XSD schemas.

•Automatic serialization (write instances from memory to file) and deserialization (read instances from file to memory) in XML.

•XML file validation against the RESQML XSD schemas.•Using : MS XSD , JAXB, EMF, GSOAP, etc…

– HDF5

•For I/O binary operations (coordinates, property values, etc…)•Efficient for large data, open source, no cost, regularly maintained,

•Multi platforms 32/64 bits: exists for C/C++, .NET, JAVA, Fortran, Windows, Linux, etc

• Sismage Platform : Java 64 bits•HDF5: Java 64 bits version• JAXB : distributed within JAVA

• Implementing time: 2x3 weeks for I/O

Import implementation

18

RESQMLXSD

SCHEMAS

JAVARESQML

Datamodel

Mapping inJAVA

HDFfile

RESQMLfile

RESQML Datamodel Instance

Sismage Datamodel Instance

Automatic JAVA classes

generation (JAXB)

Automatic Datamodel generationand validation

(JAXB)

Non automatic work : around 15 man-day

Assisted Datamodel generation

(JAVA HDF API)

Export implementation

19

RESQMLXSD

SCHEMAS

JAVARESQML

Datamodel

Mapping inJAVA

HDFfile

RESQMLfile

RESQML Datamodel Instance

Sismage Datamodel Instance

Automatic JAVA classes

generation (JAXB)

AutomaticXML file

generation

and validation(JAXB)

Non automatic work : around 15 man-dayAssisted

HDF file generation

(JAVA HDF API)

Outline

• Introduction• RESQML V1.0 Document• Demonstrating the implementation of V1 • Roadmap• Summary

Demonstrating the implementation of V1Alwyn reservoir modelling & simulation workflow

21

Seismic interpretation (Sismage)

Structural modeling(Skua)

Gridding(Petrel)

Static property modeling and upscaling

(Open-Flow)

Dynamic reservoir fluid flow simulation

(Imex)

OUTPUT DATA SET

Simulated Reservoir Model (grid & properties)

metadata (creator name, creation date, contributor name, ...)

QC

ALWYN INTERPRETATION

DATA SET

1 geodesy

3 horizons

4 faults

Well markers

metadata (bibliography, creator name, creation date, contributor name, ...)

Data Exchanges Overview

22

QC of all steps (RESQML import back in Seismic Interpretation Package)

23

Structural model (red lines)VsInterpretation (points)

Grid geometry and layeringVsStructural model and interpretation

Final (simulation) Grid & propertiesVsStructural model and seismic

Outline

• Introduction• RESQML V1.0 Document• Demonstrating the implementation of V1 • Roadmap• Summary

Roadmap: Short term Delivery Plan

• RESQML V1 : Independent features exchange. – Published January 2011– Release of RESQML data standard to application

vendors– 3 ILAB’s/year used for development

• Application development during 2011:– V1.1 to be published in June to achieve V1.0– V1.1 will be Included of in next application

development cycle for 2011/2012 (?) release• Delivery will depend on your specific vendors

• RESQML V2 Specifications : Earth model relationships management between features. Early 2012

1st Business Objective : Consistent Earth Models exchanges

27

RESQML Future Developpements

Assemblage of Consistent Earth Models ( relationships between features)Complete feature handling, data representation & explicit metadataSupport for partial model transfer & updates Support for workflow integration with WITSML and PRODML ObjectsTopological assemblage for multiscale geometry.Unstructured gridsSupport for additional processes (geomechanical modelling, 3D/4D seismic integration…)Support for Activity management (scenarios).

Roadmap: RESQML V2+ Development Plan

• Association with WITSML and PRODML Objects (EnergyML manifest)

• Relationships management Objects– Structural/Stratigraphic frameworks of horizons +

faults– Earth models of structure + grid– Multiple scenarios, realizations, …

• Additional 3D Grid representations– Unstructured or abstract representations for 2D/3D

PEBI, XY-OT, streamlines, …• Simplified and efficient representations

– XY regular, 3D Seismic, parametric grids, – Automatic Certification…

RESQML ROAD MAP

Outline

• Introduction• RESQML V1.0 Document• Demonstrating the implementation of V1 • Roadmap• Summary

RESQML Standard answer the need for a standards-based approach towards geosciences applications interoperability

Easy to implement Conservative Fast export / import

We encourage all geosciences application vendors & petroleum companies to adopt, implement & deliver

Summary : what we have today

• RESQML V1 tested , ready for industrial implementation:– Guided by Petroleum companies Practical Use cases– Tested by vendors on these use cases for robust data

transfers– Automatic use of GUID’s and metadata for traceability and

workflow flexibility• with STRUCTURAL

– Horizon/faults an more• and GRIDS:

– Coordinate line description able to represent any Corner point cells meshes.

– Introduction of topologic description to remove ambiguities in geometric interpretation

Complete replacement for RESCUE features

Summary : what we have for the future

• An "Object Oriented" certified consensual representation for :– Horizons, Faults (interfaces) and Rock features (volumes)

• Some interesting and simple utilities to dialog with patrimonial and project data bases – A way to automatically update it in order to follow the future

evolution – A way to manage the relationships of the Objects with their

representations in several databases with the use of GUID’s – A way to record the process used to obtain these

representation all along the worklow whatever could be the authors.

• More important : A dialog actually and open with the users and the vendors to focus on the more efficient and useful manner to work together on complex loops and workflows.

RESQML SIG: Member Companies

• Austin GeoModeling• BP• Chevron• Computer Modeling Group• Dynamic Graphics, Inc.• Halliburton• IFP Energies Nouvelles• JOA Oil & Gas BV

• ONGC• Paradigm• Pioneer Natural Resources• Roxar• Schlumberger• Shell• Total• Transform Software &

Services

Resources

• For more information about RESQML and Energistics:www.Energistics.org

• SPE135280: Reservoir Modeling: From RESCUE To RESQML™Michael J. King, Texas A&M University, Paulo Ballin, BP America, Inc., Chakib Bennis, Institut Français du Pétrole, David Heath, Transform Software, Allan Hiebert, Computer Modeling Group, William McKenzie, Chevron, Jean-Francois Rainaud, Institut Français du Pétrole, Jana Schey, Energistics

• SPE143846: Using RESQML™ for Shared Earth Model Data Exchanges between Commercial Modelling Applications and In-House Developments, Demonstrated on Actual Subsurface Data Francis Morandini, Bruno Michel and Philippe Verney, Total; Jean-Francois Rainaud, IFP; Laurent Deny and Jean-Claude Dulac, Paradigm; Tony Fitzpatrick, Schlumberger; Rob Eastick, CMG; Lisa Towery, BP

Thank you!

Questions????