UTCS Post Implementation Project

1
Standardize Vendor Mudlog Formats A Simple
Request or Is It ?
A brief overview on standardizing the exchange of
Mudlog Data within ExxonMobil Operations Geology
Cary Fico, ExxonMobil Exploration Company Robert
Corwin, ExxonMobil Exploration Company Tim
Herrett, Cambrian Consultants America Inc.
WITSML Forum Sept 18-19, 2003
2
Agenda
Conceptual Data Flow Mudlog Complexity Data
Content, Generation Distribution ExxonMobil
Efforts Benefits Next Steps
3
Conceptual Data Flow for Definitive Data
Data Provision (Well-site)
To Analyst
Data Content ?
Standard Data Format ?
To Apps
Data Loading Tools Processes ?
Apps Usage Display ?
Transfer Tools ?
Cataloging Process ?
Data Model Changes ?

• Why ?
• Ensure complete data set validated set at
  source
• Expedite data receipt loading
• Expedite data search tracking
• Expedite transfer and integration of data for
  Engineers Geoscientists

4
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

5
Complexity of Capturing and Distributing Mudlog
Data with Varying Media and Formats
Rig
HTTP

Rig Server
Server
Mudloggers or WSG
Cuttings lithology show
Screens
descriptions,
calcimetry
,
Drilling
shale density
Reports
Contractor
(DOC, XLS)
On-line plots
Analysis
Real-time
Log Image
HTTP
(PDF, PDS)
Sensors
Engineer
Reports
(DOC, XLS)
Raw
Comments
Data
Observations
Data
Mudloggers
Time
Log Image
Multiplex
(PDF, TIFF)
disk
Edited
Database
Geol
Samples/
Depth
Ops
Cores
Data File
(ASCII, LAS)
transported
Bus. Unit
/FE
Data
from
Generalized Data Flow Model
disk
wellsite
WSG Lithology
Show Descriptions
from SWC and cores
Network
E-Mail,
WITS
WSG
Reports
HTTP
(DOC, XLS)
Wellsite
Comments
(Changes with time, technology and organizational
roles)
HTTP
Observations
Geologist
Log Image

(PDF)
Archive
HTTP
QA/QC
Screens
On-line plots
Real-time
Memory
HTTP
Tools
Data
Ext Links
Reports
(DOC, XLS)
Engineer
Raw
Data
Comments
Data
Observations
disk
LWD/MWD
Log Image
(PDF, PDS,
Multiplex
Database
TIFF)
Edited
Partners/
Gov
Data File
(ASCII, LAS)
Tools
Engineer
Data
Comments
Raw
disk
Log Image
Observations
(PDF, PDS)
Data
Edited
Wireline
Multiplex
Database
Data File
(DLIS, LAS)
Real-time
Screens
On-line plots
Rig Server
6
Mudlogging Curve Definitions (Partial List)
Impact on Data Models, Access Display
7
Mudlogging Annotation Definitions (Partial List)
Impact on Data Models, Access Display
Primary
Pressure
Temper
Mudlog
Complog
Drilling
Gasratio
Element
Lithlog
Association
2.1
2.1
2.1
1
2.1
3.1
Center of column
recovered interval
Sidewall core
Symbol
Coring
Own column w/
Triangle, point to right, black filled
2.1
2.1
3.1
Right side of column in contact with track
cores
for recovery, no fill for non-
border. Variable placement in SWC track
recovery
or in WFT track on Complog???
Mudlogging,
Symbol
Lithology
Own column
Each lith has percentage and fills
2.3
2.2
2.2
2.2
Fills Column
appropriate column width,
Cuttings lithology
sequence??
(percent)
Gas Peaks
Comment
Gas
THA (TOTgas)
Text giving gas peak type and
3
1
5
1
3
4
Offset from left hand side of track
magnitude
8
Mudlogging Displays
9
ExxonMobil Vendor Format Efforts Mudlog

• Completed
• Mudlog Data Content Defined (_at_ 100 curves
• and 75 annotations).
• Several Display Templates Recommended
• (Mudlog, Pressure, Gas etc.)
• In Progress / To Do
• Opening up our work effort to service providers
  and
• industry efforts for feedback and ways to
  implement
• Aligning internal data repositories, data loading
  and
• export routines to/from corporate repositories
  and applications
• Address or incorporate additional standards
  related to log / curve identification
• (mnemonics), domestic and international unique
  well IDs, lithology legends, symbols and lith
  descriptions and abbreviations, consistent code
  values etc., etc.

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

11
Next Steps

• Map Mudlog data content structure (i.e. curve,
  discrete, annotation data) to WITSML data object
  and component schemas
• For example Log data object, Mud Log data
  object, Operations Report data object etc.
• Identify existing components and possible need
  for extension of WITSML standard including style
  sheet

Concerns/Issues Any standardization effort has
uncertainties associated with inter-organizational
responsibilities and industry alignment in
regards to process / data flows, information
quality assessment and timeliness of delivery of
a solution.