1 / 29

RESQML™ for 3D/4D Reservoir Characterization

RESQML™ for 3D/4D Reservoir Characterization. Michael J. King Senior Advisor, BP America, Inc. Energistics Standards Seminar SPE Digital Energy Conference 6 April 2009. Outline. Introduction RESCUE Consortium History, Membership, Workflow RESQML™ in Energistics Context and Structure

tirzah
Download Presentation

RESQML™ for 3D/4D Reservoir Characterization

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. RESQML™ for3D/4D Reservoir Characterization Michael J. King Senior Advisor, BP America, Inc. Energistics Standards SeminarSPE Digital Energy Conference 6 April 2009

  2. Outline Introduction RESCUE Consortium History, Membership, Workflow RESQML™ in Energistics Context and Structure RESQML™ Roadmap Requirements, Use Cases, Evolution Discussion / Questions? 2

  3. Introduction

  4. Why Build A 3D Reservoir Model? • 3D Detailed Geologic Static Model • Understanding the resource in place • Understanding the play type • Well targeting • Upscaled Flow Simulation Model • Performance prediction in the absence of dynamic data • Starting point for a history match when dynamic data is available • Prediction of reserves per well • Prediction of new processes in anexisting field 3D Reservoir Modelling Workflow (After Roxar RMS)

  5. High Frequency Low Frequency Sensor Data SCADA Systems OPC Domain Application A Application B Application C Application etc. PRODML™ Domain Drilling Systems Maintenance Systems WITSML™ Domain Maintenance Domain Position in the E&P Business Processes Business Processes After Chevron, ExxonMobil 30 Geoscience Data Reservoir Models De facto Standards,RESQML™ Domain Many Production Applications

  6. RESCUE Consortium 6

  7. RESCUE Consortium – 1 / 3 Initiated in 1995, RESCUE is a Joint Industry Project managed by Energistics (formerly POSC). The acronym 'RESCUE' stands for REServoir Characterization Using Epicentre http://www.posc.org/rescue The purpose was to provide aforum for the development ofan open standard for thetransfer of data from“geomodels to upscalers”, specifically through the use of the POSC Epicenter data model 7

  8. RESCUE Consortium – 2 / 3 Delivery of the standard replaced Epicenter with a collection of binary flat files to describe: Structural Framework: Faults & Horizons 3D Grids: Static and Simulation Wells: Especially Log Data To ensure a commonimplementation a set ofClass Libraries weredeveloped under contractto the RESCUE project,and are the vehicle of choice for implementing an API to the RESCUE standard. 8

  9. RESCUE Consortium – 3 / 3 • RESCUE Organization • Mike Castleberg, Program Manager • Rod Hanks, Class Libraries • Oil Company Chair • Oil Company Sponsors • Shell, BP, Total, StatoilHydro • Vendors • 20+ Current Members delivering commercialapplications with RESCUE readers &/or writers • ILAB’s “Interactive Laboratories” • Multi-vendor testing and development • Oil company guidance • Genuine collaboration

  10. RESCUE in the Workflow Initial Scope: Static to Dynamic RESCUE provides for the transfer of the 3D Reservoir Model from the “Static” to the “Dynamic” Domain • RESCUE • 3D Grid is the primary data • Faults / Horizons / Wells associated with the grid • Provides a link from Geologic to Simulation Vendors • Workflow has been extended to support better multi-vendor reservoir characterization 3D Reservoir Modelling Workflow (After Roxar RMS)

  11. RESCUE in Use • Deepwater GOM Appraisal • Large Structure • Partially Subsalt • Structurally Complex • Potentially Complex Channel Architecture • Faults & Fault Seal? • Connected Volumes? • Reserves per Well? • Performance Prediction? • RESCUE used to combine multiple analyses since no one application could provide adequate technical assessment • Partial updates can be managed in RESCUE now, but it takes user skill and specific application experience

  12. RESQML™ in Energistics 12

  13. Energistics Subject Areas RESQML™ SIG initiated 1 Jan 2009 • RESQML + WITSML • Real-time updates of 3Dreservoir models while drilling Asset/DataManagementSIG eRegulatory SIG AssetManagement <RESQML/>SIG • RESQML + PRODML • Rapid integration ofproduction history to validate&/or calibrate models Reservoir Reservoir Production ProductionGeology Geology SIG Engineering Engineering Geology Expl Petrophysics Petrophysics Petroleum Petroleum ExplGeology Geology Engineering Engineering • Industry Services SIG • Technical Architecture • Energy Identity Trust Drilling Drilling Production Production Facilities Facilities Engineering Engineering Engineering Engineering Engineering Engineering Completion & Drilling Drilling Completion & Production Production Geophysics Workover Operations Geophysics Operations Workover Operations Operations Geophysics SIG <WITSML/> <PRODML/> SIG SIG

  14. RESQML™ Team Structure • Steering Committee • Scope, Direction, Marketing • Use Case Team • Workflows, Processes, and Requirements • RESCUE • Maintenance of the existing libraries (v37.7) • Technical Teams • Infrastructure • Binary, ASCII to Binary, Shared Utilities • Wells • WITSML with RESQML extensions • Structural “Earth Model” • Faults, Horizons & Structural Framework • GRID “Reservoir Model” • 3D Grids, Properties & Cell Connections • Discretized: Faults, Horizons & Well Perforations

  15. RESQML™ Roadmap & Requirements 15

  16. RESQML™ Requirements • Support for partial model transfer and updates • Enhanced integration with 3D/4D Seismic data • Commercial / Life of Field data integrity • Managing Risk & Uncertainty • Geomechanical Support • Giga-Cell Models • Unstructured Grids

  17. RESQML™ Roadmap • RESCUE v37 remains the standard in production use until RESQML™ enabled applications render it obsolete • 2009: Version 0.0 • As of today, we are four months into the new Energistics SIG and are making good progress towards an XML-based standard based on relatively simple models • 2009: Version 1.0 • By year end, first standard published for vendor comment & prototype implementation • 2010: Version 1.N • Revisions of 1.0 plus new features • 2010/11: Version 2.0 • First release in commercial vendor tools

  18. RESQML™ Roadmap - Structural • Version 1.0 • Faults and Horizons transferred as individual objects • Version 2.0 • Faults and Horizons in a Structural Framework • Rich set of representations, e.g., tri-surfaces, 2d grids, scattered data, etc. • Discretized faults,horizon & structureon the GRID • Version 3.0 • Multiple realizations • Enhanced metadata • Rule based (?)

  19. RESQML™ Roadmap - GRID • Version 1.0 • Single / Multiple Corner Point Grids • Numerical Local Grid Refinement • Straight / Piecewise Linear / Spline Coordinate Lines • Multiple layering schemes • Static and Dynamic cell properties, with packing • Non-Standard Adjacency (Pinch-out & Faults) • Version 2.0 • Geometric Local Grid Refinement & Coarsening • Seismic Volumes / Tartan Simulation Grids • Node based properties (geomechanics & seismic) • Version 3.0 • Radial Grids • Streamline-based unstructured grids • Unstructured Cell Indexing and Truncated Grids • 2.5D and 3D PEBI Grids

  20. Energistics Subject Areas Asset/DataManagementSIG eRegulatory SIG AssetManagement <RESQML/> Reservoir Reservoir Production Production SIG Geology SIG Engineering Engineering Geology Geology Expl Expl Petrophysics Petrophysics Petroleum Petroleum Geology Geology Engineering Engineering • Industry Services SIG • Technical Architecture • Energy Identity Trust Drilling Drilling Production Production Facilities Facilities Engineering Engineering Engineering Engineering Engineering Engineering Completion & Drilling Drilling Completion & Production Production Geophysics Workover Operations Geophysics Operations Workover Operations Operations Geophysics SIG <WITSML/> <PRODML/> SIG SIG 20

  21. Discussion & Questions? 21

  22. Backup! 22

  23. High Frequency Low Frequency Sensor Data SCADA Systems OPC Domain Application A Application B Application C Application etc. PRODML™ Domain Drilling Systems Maintenance Systems WITSML™ Domain Maintenance Domain Discussion & Questions? Business Processes After Chevron, ExxonMobil 30 Geoscience Data Reservoir Models De facto Standards,RESQML™ Domain Many Production Applications

  24. RESQML™ Requirements – 1a / 5 • What Have We Learned from RESCUE? • Work processes, not a single “Static to Dynamic” Workflow • Also “Static to Static” and “Dynamic to Static” transfers • Support for partial model transfers & updates • Structural description in Application-1 • Properties in Application-2 • Well design in Application-3 • Upscaling in Application-4 • Dynamic Predictions in Application-5 • Transfer predictions back to the static model • Review Performance Against Predictions in Application-6 • Update description back in Applications-1,2,…

  25. RESQML™ Requirements – 1b / 5 • Partial updates can be managed in RESCUE now, but it takes user skill and specific application experience • Deepwater GOM Appraisal • Large Structure • Partially Subsalt • Structurally Complex • Potentially Complex Channel Architecture • Faults & Fault Seal? • Connected Volumes? • Reserves per Well? • Performance Prediction? • RESCUE used to combine multiple analyses since no one application could provide adequate technical assessment

  26. RESQML™ Requirements – 2 / 5 • Commercial Requirements are More Rigorous • Sarbanes-Oxley has increased the rigor which we must document reserves, with supporting data & interpretations • “7 Years + Life of Field” has increased the need for Vendor & Application neutral data formats • The use of Markup Languageallows RESQML™ to representsignificantly more metadata oninterpretations and data sourcesthan does RESCUE.

  27. RESQML™ Requirements – 3 / 5 • Managing Risk and Uncertainly • Markup language provides extensions to our current data structures to support multiple reservoir models • Examples: • Here is a collection of 10 equi-likely reservoir models • Here is a most-likely and a standard distribution “Top Reservoir” map which honors all of our well data. • Please create 100 equi-likely Top Reservoir maps • Extensions: • Representation by Value • Representation by a Collection • Representation by a Rule

  28. RESQML™ Requirements – 4 / 5 • Giga-cell Models • Successful continued infill development of mature producing reservoirs requires more detail, higher resolution, and better Static  Dynamic integration • Example: SPE 116675 • “From Mega-Cell to Giga-Cell Reservoir Simulation”Ali Dogru et.al., Saudi Arabian Oil Company • 109 cell dynamic simulation models • 1010-1011 cell static geologic models • RESCUE interchange formats have not been optimized for systems of this size • 107-108 cell static geologic models are common

  29. RESQML™ Requirements – 5 / 5 • Additional Classes of Models • 4D Seismic exceptionally useful forreservoir surveillance and management • Geomechanical models extend from thesurface to beyond the reservoir • Seismic Volumes • Tartan Simulation Grids • Unstructured Grids • Streamline simulation models are basedon 1D streamlines embedded in a 3D space • Unstructured Cell Indexing and Truncated Grids are in current use by several 3D Static modeling applications to describe complex structures, especially reverse faults • 2.5D and 3D PEBI grids are in use in the Simulation Domain

More Related