Energistics Standards Presentation 2 : Geomodeling

Slides:



Advertisements
Similar presentations
Lecture # 2 : Process Models
Advertisements

Completion Object Overview June 2013 WITSML/PRODML Standards.
SYSE 802 John D. McGregor Module 2 Session 2 Method Tailoring.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Overview 1. 2 WITSML Special Interest Group Members A set of Data Exchange and Web Services Standards First published in 2001 Version 1.4 due in Q3 50+
RESQML™ for 3D/4D Reservoir Characterization
1 Agenda Introduction Energistics Standards Panorama / History / Participants Web Services Interoperability Standards v1.0 WITSML Version 1.x Services.
An Introduction to Software Architecture
AIXM Users’ Conference, March Implementing AIXM in Instrument Flight Procedures Automation Presenter: Iain Hammond MacDonald, Dettwiler &
Role of the Chair OGP - update by Richard Wylde Geodetic Advisor, ExxonMobil Chair OGP Geomatics Committee User needs on energy and minerals data and services.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Coming up: Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
EuroRoadS for JRC Workshop Lars Wikström, Triona Editor of EuroRoadS deliverables D6.3, D6.6, D6.7.
® Sponsored by GroundWater ML 2 IE (GW2IE) GroundWater ML 2 IE (GW2IE) Progress Report 95th OGC Technical Committee Boulder, Colorado USA Bruce Simons.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 10 Use Case Design.
Technical Team WITSML SIG Dubai - November 2008 John Shields / Gary Masters.
Interoperable sharing of groundwater data across international boarders is essential for the proper management of global water resources. However storage.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Distribution and components. 2 What is the problem? Enterprise computing is Large scale & complex: It supports large scale and complex organisations Spanning.
Basic Concepts of Component- Based Software Development (CBSD) Model-Based Programming and Verification.
Geophysical SIG Towards reduced cycle time In Geophysical Work Processes.
C. Huc/CNES, D. Boucon/CNES-SILOGIC Producer-Archive Interface Specification.
Develop Use Cases Evaluate Existing Models Develop/Extend Model Test ModelDocument 1. Commercial This use-case involves identifying the location and properties.
Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Requirement Engineering Virtusa Training Group 2004 Trainer: Ojitha Kumanayaka Duration : 1 hour.
WIGOS Data model – standards introduction.
Geography Markup Language (GML). GML What is GML? – Scope  The Geography Markup Language is  a modeling language for geographic information  an encoding.
Software Design Process. What is software? mid-1970s executable binary code ‘source code’ and the resulting binary code 1990s development of the Internet.
Develop Use Cases Evaluate Existing Models Develop/Extend Model Test ModelDocument Use Cases 1. Commercial This use-case involves identifying the location.
® Hosted by IIT Bombay Department of Science & Technology Sponsored By OGC Land and Infrastructure InfraGML Proposal: OGC r1 87th OGC Technical Committee.
Elaboration popo.
102nd OGC Technical Committee Delft, The Netherlands
Articulating Your Practice C3 - Session #3
AIXM 5 UML to XSD.
UML Diagrams By Daniel Damaris Novarianto S..
Component and Deployment Diagrams
A Web Services Journey on the .NET Bus
Energistics Standards Presentation 1 : Wellbores
104th OGC Technical Committee – GeoScience DWG session
Unified Modeling Language
Physical Structure of GDB
OO Methodology OO Architecture.
Distribution and components
SYSTEMS ANALYSIS Chapter-2.
Architecture Components
GeoScience DWG Welcome
UML Diagrams Jung Woo.
Updates on boreholes in EPOS Borehole UML model
Borehole update: simpleFeature exchange, conceptual UML model
QGIS / GDAL GML application schema support update : use case on French Groundwater Information Network (GIN) BRGM – S.Grellet OGC Hydro DWG Workshop 2017.
Articulating Your Practice C3 - Session #3
Updates on models exchanges in EPOS
Overview of the XBRL-US Financial Reporting Taxonomy Framework
Advanced Database Models
Updates on boreholes in EPOS: architecture, BoreholeView
Setting interoperability between BIM and Geomodelling
The Re3gistry software and the INSPIRE Registry
Technical update 19 of December 2016
Object Oriented Analysis and Design
Completion Object Overview
Software engineering -1
Analysis models and design models
104th OGC Technical Committee – GeoScience DWG session
An Introduction to Software Architecture
For University Use Only
Semantic Markup for Semantic Web Tools:
Session 3: Information Modelling and Information Communities
MSDI training courses feedback MSDIWG10 March 2019 Busan
May 9th, 2019 IHO HSSC 11: Cape Town
UML  UML stands for Unified Modeling Language. It is a standard which is mainly used for creating object- oriented, meaningful documentation models for.
QoS Metadata Status 106th OGC Technical Committee Orléans, France
Presentation transcript:

Energistics Standards Presentation 2 : Geomodeling 104th OGC Technical Committee – GeoScience DWG session Southampton, United Kingdom Jean-francois RAINAUD IFP En 14th September 2017 Copyright © 2017 Open Geospatial Consortium

Energistics Standards General Presentation Energistics Standards scope PRODML WITSML Geomodeling RESQML SEG Copyright © 2017 Open Geospatial Consortium

Slide 3 What is RESQML? RESQML is a data exchange standard, designed primarily for reservoir model data. It is based on XML, coupled with the HDF5 standard for large array data. Replaces RESCUE. RESQML is seen as robust way for geoscientists and engineers to share reservoir model data and information across the subsurface toolkit portfolio. SPE-185761-MS # RESQML Version 2.0.1 Makes it Easier To Update a Reservoir Model # JF RAINAUD

RESQML V2.0.1: The Objects Exchanged Slide 4 RESQML V2.0.1: The Objects Exchanged FEATURE (0,*) INTERPRETATION (0,*) REPRESENTATION The RESQML V2.0.1 includes significant new capabilities (Verney et al. 2014, Legg et al. 2015) with overarching design objectives to: Improve the richness and usability of existing domain objects, for example, adding more flexible grid representations. Add new domain objects to better support: 1) subsurface work flows, for example, v2.0.1 now includes wells and “organizations” (which make it possible to group objects together into structural, stratigraphic, and earth model objects); and 2) the more sophisticated capabilities of the software packages used in those work flows. Add relationships: 1) among data objects and 2) to key data “outside” the model, for example RESQML horizon 2D grid coordinates (I/J) based on seismic data coordinates (inline/xline) of an external SEGY file. Support traceability of data objects (with use of UUIDs) and more flexible work flows; for example, by supporting partial model updates (updating only those pieces of the model that have changed). The feature/interpretation/representation/properties knowledge hierarchy (referred to informally as "FIRP") is a new concept in RESQML; it makes data organization more precise and data exchange more efficient. To establish a “knowledge hierarchy,” asset team members specify relationships between instances of data objects using a RESMQL mechanism called a data object reference (DOR (0,*) PROPERTIES SPE-185761-MS # RESQML Version 2.0.1 Makes it Easier To Update a Reservoir Model # JF RAINAUD

RESQML Relationships: How They are Implemented Slide 5 RESQML Relationships: How They are Implemented One-Column Format : In this example (beginning at the left), the feature (UUID 0000) has 2 interpretations (UUIDs 0001 and 1001); interpretation 0001 has 2 representations (UUIDs 0002 and 1002), and representation 0002 has 2 properties (UUIDs 0003 and 1003).   SPE-185761-MS # RESQML Version 2.0.1 Makes it Easier To Update a Reservoir Model # JF RAINAUD

Zip File : . epc Hdf_File. h5 EPC Slide 6 Energistics Packaging Conventions (EPC) Zip File : . epc Title : mytitle Identifier : myUuidUrn Creator : Energistics … Hdf_File. h5 Wellbore Well Hdf data structures H1 F2 STRUCTURED BINARY DATA Trajectory Log EarthModel1 Interp1 Interp2 localCRS1 Rep1 Rep2 Can be formatted using Can be packaged into Container ship photo from wikipedia : http://fr.wikipedia.org/wiki/Fichier:CMA_CGM_Marco_Polo_arriving_Port_of_Hamburg_-_16._01._2014.jpg Licence : Creative Commons paternité – partage à l’identique 3.0 (non transposée) EPC EPC SPE-185761-MS # RESQML Version 2.0.1 Makes it Easier To Update a Reservoir Model # JF RAINAUD

The Data Exchange Partial Exchange Slide 7 The Data Exchange Partial Exchange To transfer a RESQML data object—in correct context—without all of its associated data objects and/or data. Do this when the model/data objects have been previously transferred and now you only want to transfer new or updated data. SPE-185761-MS # RESQML Version 2.0.1 Makes it Easier To Update a Reservoir Model # JF RAINAUD

Energistics Standards General Presentation Energistics V2.* Standards Delivery : One common Set of XSD (Xml Schemas) containing : Main constructions including relationships & Link to external resources (hdf5) Base types CRS Coordinate reference system for Geolocalisation With a mandatory use of CRS with respect of OGC standards EPSG Code ( using GML behind) or direct USE of GML (mainly for trajectories). Property Kind Units of measure Common enumerations And, in the common enumerations, a reuse of GeosciML lithology definitions One set of XSD (XML Schema) for each standard (here Resqml) And complete documentation and UML design (XMI file)

RESQML versus Classical Exchanges (1/2) The concept of Representation is important to capture : The Representation of an Object is a topology (which can be expressed by ni,nj only by example ) on which a geometry is associated Usually, Software exchange Only Representation + Properties In Resqml we emphasize the fact that we should exchange more than only Representations and properties of the objects, but also the knowledge attached to Interpretations. In Resqml we emphasize also the fact that we can exchange also the relationships between the Interpretations. Copyright © 2017 Open Geospatial Consortium

RESQML versus Classical Exchanges (2/2) For Individual Element exchange, Resqml can gather several Representation on one interpretation: Example for a fault Interpretation : picked polylines, triangulated surface, 2D grid, CellFaceConnectionset in a Grid) At this Interpretation level, Resqml can attach all the Knowledge corresponding to Example, on a Geological Unit : GeologicUnitComposition (GeosciML lithology), geologicUnit3DShape, GeologicUnitaMaterialEmplacement. Also Resqml can gather and organize several Individual elements in a global Interpretation object. Example StructuralOrganization, StratigraphicColumn, RockFluidOrg. And at the end an EarthModelInterpretation will gather all the elements used to set it up. Copyright © 2017 Open Geospatial Consortium

RESQML Representation versus GML For the localisation issues, Resqml is using GML directly or indirectly (through EPSG). Representation exchanged are: pointsets3D, polylines, 2D grids, planes, triangulated surfaces (TIN) and several types of volume Representation ( BREP framework and several 3D Grids) For topology and geometry, at the very beginning, we started to describe our representations in GML (with the concepts of faces by example). For performance reasons, the team did not go in this direction : we decided to serialize the information in tables/arrays into hdf5 file and establish only relationships from xml description and binary data. But, the UML model is done is such a way that we can add more representations if needed without breaking the model ( by example GML ones). Copyright © 2017 Open Geospatial Consortium

Examples of Complex Representations Copyright © 2017 Open Geospatial Consortium

Resqml 3D Grid representations Copyright © 2017 Open Geospatial Consortium

Resqml Structural Model Representation Copyright © 2017 Open Geospatial Consortium

Copyright © 2017 Open Geospatial Consortium Conclusion Energistics standards are more and used in the Petroleum industry. Witsml is already adopted, for Resqml we are in deep in the adoption phase When we designed these standards we tried to listen to all other existing initiative and did our best to be open But as you could see, we did not choose to represent topology and geometry by using GML . Nevertheless, if necessary, the model can accept such a « not breaking » evolution RESQML is designed not only to exchange individual representations, but also knowledge gained during interpretation and complex geomodel setup. To prepare future evaluations we experimented also the exchange of geologic and geotechnical modeling informations (geological limits, MNT, Breaking lines) etc. and it was successful. Thank you for your attention .. We are actually ready for a lot of more explanations and further collaboration. Copyright © 2017 Open Geospatial Consortium