RESQML™ update, Reservoir and Earth Modeling Data Exchange Standard Status

1. RESQML™ update, Reservoir and Earth Modeling Data Exchange Standard Status Jean Francois Rainaud, IFP Energies Nouvelles London Conference, 31st May 2011

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

3. 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

4. E&P business processes 3D RESERVOIR MODELLING & SIMULATION DECISION DATA • Towards better integration for: • Better understanding & better risk assessment at all levels • Reducing the cycle time « data to decision »

5. Reservoir interpretation, modeling and simulation activity require a wide range of disparate disciplines & tools. To Facilitate Integrated Workflows GEOPHYSICISTS Seismic interpretation GEOLOGISTS RESERVOIR ENGINEERS

6. To Improve Robustness of Data Transfers Multi-company, multi-application data transfer • 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

7. RESCUE and the move to RESQML 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 RESCUE MODEL REPRESENTATION 7

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

9. RESQML v1.0 – Already More than RESCUE on Workflow & Usage H F Interpretation Activities Dynamic Reservoir Simulation Static Reservoir Modeling H F G G H F G 3D Grids Horizons H G Faults F G RESQML file(s) Filled 3D Grids 9

10. RESQML Top Level Document [1:1] [0:1] PropertyGroupSet [0:1] SpatialReferenceSet [1:1] [0:1] [0:1] PropertyKindSet AreaOfInterest InterfaceFeatureSet GriddedVolumeSet

11. 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)

12. RESQML Top Level Document F H G G RESQML v1.0 – Exchanged Information [0:1] [1:1] PropertyGroupSet [0:1] SpatialReferenceSet [0:1] [1:1] [0:1] PropertyKindSet AreaOfInterest GriddedVolumeSet InterfaceFeatureSet [0:*] [0:*] [0:*] gridSet [0:1] pointSets curves grid2D triangles hybridGrid2D [1:*] [0:1] RootGrid G Non-Standard AdjacencySet [1:*] [1:1] BlockedWellSet G G LocalGrid ExplicitRepresentation Horizon Fault IJ CoordinateLine Support

13. RESQML v1.0 - Document Architecture coordinate system (CRS) definitions metadata description GML XSD schema Dublin Core XSD schema Production data Well data WITSML XSD schema PRODML XSD schema HDF5 specs RESQML XSD schema Processed by proprietarylibraries. Processed by HDF libraries. Data Structure Giga-Cell Models data storage Refers to XML file HDF file(s) RESQML DOCUMENT : DocumentTITLE.resqml + DocumentTITLE.resqml.h5 13

14. RESQML document - part 1: XML file High readability for humans… High capability to be processed by computers. Fitted for long term archives CRS definitions CRS1 CRS2 CRS3 CRS4 Interface definitions Horizon1 References a path in the associated HDF file Horizon2

15. RESQML document - part 2: HDF file(using HDFview) Set of representations Set of points (X,Y,Z) structured in a 2D array • De facto long term accessibility • Viewer/Editor provided byHDF Group: HDFview • Multi-platform Application with easy access to the data. Set of triangles defined by 3 indexes of vertices. Set of points (X, Y, Z)

16. HDF5 Storage Performance • Comparison of HDF5 storage efficiency with storage for active cells only 3 Reservoir Models

17. 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

18. Import implementation JAVA RESQML Datamodel RESQML XSD SCHEMAS AutomaticJAVA classes generation(JAXB) Mapping in JAVA RESQML Datamodel Instance SismageDatamodel Instance AutomaticDatamodelgeneration and validation (JAXB) Non automatic work : around 15 man-day AssistedDatamodelgeneration (JAVA HDF API) RESQML file HDF file 18

19. Export implementation JAVA RESQML Datamodel RESQML XSD SCHEMAS AutomaticJAVA classes generation(JAXB) Mapping in JAVA RESQML Datamodel Instance SismageDatamodel Instance Non automatic work : around 15 man-day Automatic XML file generation and validation (JAXB) Assisted HDF file generation (JAVA HDF API) RESQML file HDF file 19

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

21. Demonstrating the implementation of V1Alwyn reservoir modelling & simulation workflow • ALWYN INTERPRETATION DATA SET • 1 geodesy • 3 horizons • 4 faults • Well markers • metadata (bibliography, creator name, creation date, contributor name, ...) Structural modeling (Skua) Gridding (Petrel) Seismic interpretation (Sismage) QC • OUTPUT DATA SET • Simulated Reservoir Model (grid & properties) • metadata (creator name, creation date, contributor name, ...) Static property modeling and upscaling (Open-Flow) Dynamic reservoir fluid flow simulation (Imex) 21

22. Data Exchanges Overview 22

23. QC of all steps (RESQML import back in Seismic Interpretation Package) Structural model (red lines) Vs Interpretation (points) Grid geometry and layering Vs Structural model and interpretation Final (simulation) Grid & properties Vs Structural model and seismic 23

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

25. 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

26. 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 metadata • Support for partial model transfer & updates • Support for workflow integration with WITSML and PRODML Objects • Topological assemblage for multiscale geometry. • Unstructured grids • Support for additional processes (geomechanical modelling, 3D/4D seismic integration…) • Support for Activity management (scenarios). 27

28. 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…

29. RESQML ROAD MAP

30. 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

31. Summary : what we have today Complete replacement for RESCUE features • 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

32. 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.

33. 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

35. 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

36. Thank you! Questions????