1. Project Review POSC / WITSML Mudlog SIG - April 27, 28 2004 Agenda:
Presented by
Cary Fico (ExxonMobil)
Participants:
John Lottinville (BHI)
Jim Theriot (POSC)
Agenda:
Project Status & Examples
Next Steps
Project Resources
POSC Presentation Mudlog SIG Apr 2004.ppt

2. Complexity of Mudlog Data Content from Different Sources / Operations
Gas & Hydrocarbon Data
hydrocarbon shows; staining, fluorescence, cut
total gas, gas chromatograph analysis (component concentrations), gas ratios
H2S & CO2
Cuttings & Lithologic Data
lith description rock type, color, texture etc., visual porosity
interpreted log and lithology percentage log
Mud Data
composition, volume,
temp, resistivity, mud wt (in/out)
Drilling & Operation Data
hole depth, ROP
bit info: bit trips, type, no.,WOB, RPM
drilling parameter changes, drilling rate exponent
pump pressure, mud rate, mud pump stroke counts
coring points, DST, LOT
MWD / LWD

3. Mudlog Data Definitions
(Partial List)
Approximately 175 types of information

4. POSC / WITSML Meeting: Sep 18, 19 2003
POSC / WITSML Meeting: Mudlog Initiative Agreed upon as high priority.
Interested Parties:
Shell [Linda Dodge]
BP [Matthew Kirkman]
Statoil [Oivind Berrgraf]
ExxonMobil (Cary Fico)
Paradigm [John Turvill]
Datalog [David Tonner]
Baker Hughes Inteq [John Lottinville, John Shields]
Halliburton Sperry Sun [Robert Schave]
Petrolink [Nick Williams]
SDC Geologix [Samit Sengupta]
POSC (Alna Doniger, Jim Theriot)
Landmark (Marcus Ridgway)

5. Mudlog Worksessions: Dec 2003 - Apr 2004
Core Work Team
POSC (Jim Theriot)
Baker Hughes Inteq [John Lottinville]
ExxonMobil (Cary Fico)
Early Discussions
SDC Geologix [Samit Sengupta]
Datalog [David Tonner] ??
Mudlog Data Definitions
Map to WITSML Elements
Propose New Elements
‘Cold Eyes’ Review of Data & Elements
Review of Other Implementations
Data Flow / Process Data Exchange
Data ‘Packaging’

6. Annotation Style of Information
Mudlog Data Elements
WITSML Element - New - Mudlog Annotation
<?xml version="1.0" encoding="UTF-8" ?>
- <w:mudLogs xmlns:w="
- <w:mudLog>
- <w:annotation>
<w:annotationType>Midnight_Depth</w:annotationType>
<w:mdDepth uom="ft">11695</w:mdDepth>
<w:text>12/7/02</w:text>
</w:annotation>
<w:annotationType>Core_Interval</w:annotationType>
<w:mdTop uom="ft">9000</w:mdTop>
<w:mdBottom uom="ft">9090</w:mdBottom>
<w:text>Core #3. Core 81/2 “ from 9000 MD to 9090 MD,
recovered 98%</w:text>
Casing Point
Midnight Depth
Bit Change
Bit Parameters
Short Trip
Gen Engr Comment
Core Interval
Sidewall Core
Gas Peaks
Show Report
Circulation System Comments
Steam Sill Results
Gen Chromatograph Comment
Lithlog Log Comment
General Mudlog Comment
Directional Survey Comment
MudCheck Paramertes
Wireling Log Run
Etc...
annotation type
mdTop - uom & depth; mdBottom - uom & depth
or mdDepth - uom & depth
text

7. Curve Style Information
Mudlog Curve Data
WITSML Elements - logHeader, logCurveInfo, logData
Curve Data
Drilling Ops
ROP
RPM
Torque
WOB
Hookload
SPM
Pump Pressure
Dxc
Gas
Total Gas
Reference Gas
C1, C2, C3 ...
Etc.
log.xsd
logHeader
logCurveInfo
mnemonic - use spreadsheet ‘curve mnemonic’
units
mnemonic index
nullValue
classPOSC - Property Type Name (PWLS classification)
mnemAlias - not needed
curveDescription - use spreadsheet ‘Description’
logData

8. Examples:
Annotation
Lithology
Interpreted Interval
Mixed Interval
Directional Survey
Survey Object
Log / Curve Objects
Lithology Qualifier
Hydrocarbon Show
Discrete Value Data
Mudlog Data Definitions
Map to WITSML Elements
Propose New Elements
‘Cold Eyes’ Review of Data & Elements
Review of Other Implementations
Data Flow / Process Data Exchange
Data ‘Packaging’

9. Business View: Complexity of Capturing and Distributing Mudlog Data
Rig
Rig Server
HTTP
Mudloggers or WSG
Server
Cuttings lithology & show
Screens
descriptions,
calcimetry ,
shale density
On-line plots
Contractor
Reports
Drilling
(DOC, XLS)
Real-time
Analysis
Log Image
Sensors
(PDF, PDS)
HTTP
Engineer
Raw
Comments &
Reports
(DOC, XLS)
Data
Observations
Multiplex
Mudlogger’s
Time
Log Image
Data
Edited
(PDF, TIFF)
Database
disk
Depth
Samples/
Geol
Data File
(ASCII, LAS)
Cores
Ops
transported
Data
/FE
Bus. Unit
from
disk
wellsite
Generalized Data Flow Model (Changes with time, technology and organizational roles)
WSG Lithology &
Show Descriptions
from SWC and cores
Network
WITS
WSG ,
Reports
HTTP
Comments &
Wellsite
(DOC, XLS)
Observations
HTTP
Geologist
Log Image
(PDF)
Archive
QA/QC
HTTP
Screens
Memory
Real-time
On-line plots
Tools
Data
HTTP
Ext Links
Raw
Engineer
Reports
(DOC, XLS)
Data
Comments &
Data
LWD/MWD
Observations
Log Image
disk
Multiplex
(PDF, PDS,
Database
Edited
TIFF)
Gov
Partners/
Data File
(ASCII, LAS)
Tools
Engineer
Raw
Comments &
Data
Data
Observations
Log Image
disk
(PDF, PDS)
Wireline
Edited
Multiplex
Database
Data File
(DLIS, LAS)
Real-time
Screens
On-line plots
Rig Server

10. Mudlog Format / Media Standards
Data Transfer, Usage and Display
Data Type
Recommended Format
Curves & Associated Data
Log Image
Log Drawing File (Geo)
Files / Reports Etc.
Physical Media
LAS 3 (LAS 2+, XML)
.PDF (.PDS, .TIFF)
.ODF
.xls, .doc, .mdb
Needs to be worked with data providers, database & apps vendors ? ?

11. Next Steps & Project Resource Review
ExxonMobil, BHI, POSC, Datalog, Geologix, Landmark, ??
‘Cold Eyes’ Review Mudlog Data Content, Mapping to WITSML Elements
Propose Mudlog data process as seen in ‘Business View’ - how data is generated, captured, distributed, used
Data ‘Packaging’ (Multiple Objects / Multiple Data Streams)
Use of WITSML Server - Publish, Subscribe ...
Service Provider and Application Vendor Specifications
Tentative Pilot Project 4th Qtr: pending scope and commitment
Organizational Acceptance & Use
Future Potential ( ?)
Core Analysis / Reports WITSML Object
Fluid Reports WITSML Object
Formation Evaluation / Log WITSML Object
Operations Report / Daily Drilling WITSML Object
Real Time Data WITSML Data Object

12. Thank - You

13. Benefits Why Standardized Formats ? (Data Content)
Ensure complete data set; with at least minimal data + information
Expedite data receipt & loading, data search & tracking
Expedite transfer and integration of data for Engineers & Geoscientists
Simplify the Complexity - WITSML benefits achieved through data schema standards applied across different processes (as provided by service providers and internal departments) that generate or modify data; eliminate need for point to point specifications for data exchange
Business Benefits
Reduce administration costs
Reduce loss of data & cost associated with re-order, time searching or re-creating data
Reduces time & costs associated with data loading into repositories and applications
Improves data quality by ensuring data is complete and fit for business use.
Improved decision making i.e more comprehensive information readily available when needed in a useable format.