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

2. Energistics Standards General Presentation
Energistics Standards scope
WITSML
PRODML
Well Bore (Borehole)
Static Information
RESQML
SEG
Copyright © 2017 Open Geospatial Consortium

3. 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 Witsml)
And complete documentation with UML design (XMI file)

4. Original WITSML Business Challenge
Service/technology providers:
Drilling environment consists of
Many services & technical solutions
Each provides a vital part of the operation
Each operates under their own system, environment, corporation
Operators:
Operator challenge:
Consistent view of services
Conform to corporate standards (Security, audits, reporting, etc.)
Allow:
Sharing with partners
Data management
Integration
Copyright © 2017 Open Geospatial Consortium

5. Copyright © 2017 Open Geospatial Consortium
WITSML Scope
Distinct classes of objects
Reference objects – Well and Wellbore
Growing objects – Log (time,depth), Trajectory, Mudlog
Snapshots in time – with “report” information
Communications process
Simplify problem: point to point
Any number of point to point steps in a larger communications chain of events
Solution requires
Mechanism for communicating between 2 end points
Object definitions for the transfer of data
Reference
Well 1532-e
Growing
Reports
Copyright © 2017 Open Geospatial Consortium

6. Copyright © 2017 Open Geospatial Consortium
WITSML V Data Objects
Attachment
OpsReport
WellboreGeology+6
BhaRun
Rig
WellboreMarkerSet
CementJob
Rig Utilization
WellboreMarker
CementJobEvaluation
Risk
WellCompletion
CRS moved to common
StimJob
WellboreCompletion
StimJobStage
DownholeComponent
DataAssurance: common
SurveyProgram
WellCMLedger
And 6 part_ wrappers
Trajectory
DrillReport
ToolErrorModel
FluidsReport
ToolErrorTermSet
Log
Tubular
ChannelSet
Well
Channel
Wellbore
DepthRegImage
WellboreGeometry
MudLogReport
Copyright © 2017 Open Geospatial Consortium

7. WITSML Object Organization & Identification
Hierarchical with well at the top
Names & UUIDs
Uniqueness within context of parent (0,* relationships)
Copyright © 2017 Open Geospatial Consortium

8. RESQML Wellbore Interpretation communication From the Driller to the Reservoir Engineer
Slide 8
1. Create a permanent reference geometry:
the Wellbore Frame along the Wellbore Trajectory
Use a single scale: MD
Make sure the origin of the log data is specified
Convert to Local CRS for RESQML
Choose sampling interval for each log type
2. Attach Properties to this reference geometry:
Sorry dear drillers and production engineers, the truth is that for the reservoir engineer, the well is simple. It consists in a 1D line from surface to bottom, on which are « hung » geological, petro physical, and reservoir information just as Christmas hanging ornaments (individual data values) and garlands ( data valid on an interval).
So we need our Christmas tree for that.
Because we know that positioning is the nervous center of this process, we make sure we work on a unique positioning of the information by importing first the WITSMLTrajectory. We use the Global CRS and datum of the WITMLS data set. We know that you might use different rigs along the various data acquisition, so we make sure we convert to the same datum. Would need requires (grid purposes for example), we convert this trajectory to the local CRS of the study.
The WITMSL Trajectory object ( the final driller validated one) is imported as Stations positions and vectors for dip and azimuths at these stations. The construction lets the reservoir engineer choose from different interpolation algorithms in between these stations, although we know that proper MD positioning only comes from reconstructing the path using the Minimum Curvature algorithm.
Once this is created we can attach the data values: MD
Properties may be on the ticks (nodes), or between ticks (intervals)

9. N Md Values N Values N+1 Values
Slide 9
WELLBORE FRAME APPROACH
Property Kind B
Log Curve
Value given
on each INTERVAL
Property Kind A
Log Curve
Value given
on each NODE
Measured Depth
N Md Values
Value
52.5
5.2
3.6
17.8
77.6 12 24 35 47
52.5
4.4
95.3
27.8
NODE
INTERVAL
We call the construction made from the WITSML Trajectory the WELLBOREFRAME.
Once the path is reconstructed, we sample it the way we need the log, or other kind of well data to be positioned.
The nodes are referencing the spot values
and the segments are used for interval values such as geological intervals.
N Values
N+1 Values

10. N Md Values N String N+1 String
Slide 10
UUID of a Strati Limit
Value given as a string on each NODE
UUID of a Strati Unit
Value given as a string on each INTERVAL
Connecting to Stratigraphy
Measured Depth
N Md Values
FRAME
MARKERS
UNITS
Brent
Dunlin
Talbert
Ranoch T1 12 24 35 47
Top
Dunlin
Talbert
Ranoch
Top T1
NODE
INTERVAL
Similarly, we connect the Stratigraphy information , consisting of markers and Units to Nodes for the first, Segments for the second.
N String
N+1 String

11. Wellbore in the Resqml FIRP
FEATURE
INTERPRETATION
REPRESENTATION
PROPERTIES
Copyright © 2017 Open Geospatial Consortium

12. Welbore Representation (localisation)
Copyright © 2017 Open Geospatial Consortium

13. Detail on Continuous, Comment and Categorical Properties
PROPERTY KIND
QUANTITY CLASS
UNIT OF MEASURE
Each of these property Object correspond to one WellboreRepresentation Frame (nb of Mds and localisation)
which defines the size of the numerical tables handling the property Values
For Property Values :
On continuous property you can store Logs ( ex: pressure) ,
On Comment property you can store Descriptive strings ans UUIDs,
On Categorical Property you can store a list of Ids corresponding of elements in a Lookup Table
Copyright © 2017 Open Geospatial Consortium

14. Example realised recently for Civil engeneering
One example with a String look up table for Geology (litho) description
String lookup 0:GL Sandstone
String lookup 1:Argilite
String lookup 2:HE Sandstone
String lookup 3:Breccia
String lookup 4:Micashist
String lookup 5:Fe Sandstone
String lookup 6:Quartzschist
String lookup 7:Carb Sandstone
String lookup 8:Schist
String lookup 9:Unknown
The string Look Up Tables are not part of the RESQML Standard , They can be defined by a other way (by GeoSciML by example). The the names and the definitions should in this case be refered by standard external resource;
One other example with continuous properties (pressure)
Copyright © 2017 Open Geospatial Consortium

15. Copyright © 2017 Open Geospatial Consortium
Conclusion
Energistics standards are more and used in the Petroleum industry
When we designed these standards we tried to listen to all other existing initiative and do our best to be open (even if sometimes the petroleum people are pragmatic first).
WITSML is more designed to handle the real time measurements. RESQML is more involved to handle interpretations. But both are totally compatible and integrated
To prepare the future evaluations we experimented an exchange geologic and geotechnical Wellbore ( Borehole) informations. And it was sucessful.
Thank you for your attention .. We are actually ready for collaboration.
Copyright © 2017 Open Geospatial Consortium