Technical Computings View of WITSML

1
Technical Computings View of WITSML

• Robert Aydelotte
• November 2004

2
Technical Computing is . . .

• The dynamic convergence of science, data and
  business workflows
• Its focus is TECHNOLOGY, not computing
• It must be driven by Engineers and Geoscientists
  who understand our upstream business

TC
WITSML
3
ExxonMobil has Standardized . . .

• Driven by the merger
• Experience
• Get Common Before We Get Best
• time and cost constraints
• Standardization does generate value
• reduced expense despite business growth
• and Creates Opportunity
• consistency is the fulcrum of improvement
• Current Effort
• Optimization is being actively driven by
  ExxonMobils view of what we want our technical
  computing system to become

WITSML
4
Workflow Driven Optimization
WITSML
5
WITSML more than just Rig Site data

• Addresses basic issues like . . .
• What does this data mean? ? Gives common
  definitions
• How is this data identified? ? Creates common
  context
• How do I read/write the data? ? Provides common
  format, structure and rules
• Where do I put the data? Where can I get the
  data? ? Provides common services
• How do I change or extend the standard? ?
  Provides community for change
• Where do I start? Who can I work with? ?
  Provides community of experience

6
Getting down and muddy with WITSML

• Mudlog Data Content
• Objective Extend the WITSML Mudlog object to
  contain additional annotation and lithology
  information
• Use Case Team Small focus group (ExxonMobil,
  BHI, POSC, Geologix, and Petrolink) starting with
  ExxonMobil extension submissions
• WITSML Extensions Recommended extensions in
  WITSML 1.2.1 have been accepted by the Technical
  Committee (pending testing)
• Additional WITSML Involvement
• Invitation information has been sent to other
  companies that expressed an interest in possible
  pilot work
• Presently engaging mudlogging companies, software
  development and other operating companies in
  testing
• Mudlog Process Pilot
• Objective To support/improve/simplify the work
  practices of Operations Geology in generating,
  distributing and receiving Mudlog data
• First Candidate an ExxonMobil operating unit is
  using this WITSML Mudlog object on a well
  currently being drilled

7
Where to improve in WITSML

• Multiple implementations of well deviation data
  have been created including WITSML, UKOOA, POSC,
  PPDM, US MMS, various operators and many vendors
• Different phases of data life cycle supported
• planned data
• acquisition data
• processed (actual) data
• archived data
• Create more consistent and correct geospatial
  well locations and wellbore paths, including
  transformations and processing requirements
• depth and azimuth references
• geodetic co-ordinate reference systems (EPSG)
• surface locations
• well path (trajectory) data

8
Taking WITSML to completion

• WellSchematicML
• drafted as an opportunity
• pre-dated WITSML and XML Schema
• Draft recently Updated by POSC using WITSML
  style
• both planned and as-run data
• tubulars, cement, operating intervals
  (perforations, etc.), monitoring, control, lift
  and wellhead equipment, device configurations and
  operating settings
• Work in Progress
• first draft being reviewed
• use cases being developed

9
More stuff of interest
FluidReportML to POSC for standardization