WITSML Project

1
WITSML Project
POSC Update, 10 April 2002 - John Shields, Baker
Hughes
2
Current Trends and Factors

• Wells are being drilled faster
• Well targets are becoming more complex
• Need for integration between drillers, geologists
  and reservoir engineers
• Shortage of experts in oil companies and
  service companies
• Geographical factors

3
Previous Systems

• WITS Wellsite Information Transfer
  Specification 1980s
• Logs in LIS/LAS/DLIS
• Statoil sponsored Sperry-OpenWorks connection
• Statoil DART also used by BP

4
Project Organisation

• Sponsors
• BP Statoil
• Participants
• Baker Hughes
• Halliburton/Landmark
• Schlumberger/SIS
• NPSi

5
WITSML Project Goal

• The right time seamless flow of well site data
  between operators and service companies to speed
  and enhance decision-making.
• DomainDrilling, Completion, Well Services

6
Data Transfer
7
Project Timing Status

• Initiation of Project - Oct 2000
• Data Objects defined May 2001
• July 2001 Working prototype
• Data object design finalized Oct 2001
• Current Status
• Statoil testing WITSML API with Landmark Baker
  Hughes in North Sea
• Schlumberger developing commercial products
• 3rd parties also developing WITSML based products

8
Project Meetings Calgary May 2001
9
Project Meetings Austin, Aug 2001
10
Software Design Decisions

• Web Based W3C Standards
• Wide area networking
• cross platform
• XML data formats
• Platform and language independent
• SOAP for Programming Interface
• Web server based
• Platform and language independent
• API Prototype in MS Visual BASIC
• Aimed at encouraging smaller companies to adopt
  the standard

11
Open Sourced Deliverables

• Definition of Data Objects Catalogs
• Example WITSML data files
• Validation tool for WITSML files
• API Implementation
• Documentation

12
Data Objects

• Wellbore Geometry
• Casing Scheme
• Open Hole
• Daily Operations
• Fluids Report
• Cement Job
• Log
• Real Time
• Mud Logging
• Capability

• Well
• Wellbore
• Rig
• Rig Equipment
• Pump
• Location
• Trajectory
• Target
• Tubular Assembly
• Bit Record
• Wellbore Geometry
• Casing Scheme
• Open Hole

13
Well Data Object

• ltwitsmlwells xmlnswitsml"http//www.witsml.org/
  schemas/110" xmlnsxsi"http//www.w3.org/2001/XML
  Schema-instance" xsischemaLocation"http//www.wi
  tsml.org/schemas/110 http//www.witsml.org/schemas
  /110/obj_Well.xsd" witsmlversion"1.1.0"gt
• ltwitsmlwell witsmluidWell"W-12"gt
• ltwitsmlnameLegalgtCompany Legal
  Namelt/witsmlnameLegalgt
•   ltwitsmlnumLicensegtCompany License
  Numberlt/witsmlnumLicensegt
•   ltwitsmlnumGovtgtGovt-Numberlt/witsmlnumGo
  vtgt
•   ltwitsmldTimLicensegt2001-05-15T132000.0
  00lt/witsmldTimLicensegt
•   ltwitsmlfieldgtBig Fieldlt/witsmlfieldgt
•   ltwitsmlcountrygtUSlt/witsmlcountrygt
•   ltwitsmlstategtTXlt/witsmlstategt
•   ltwitsmlcountygtMontgomerylt/witsmlcountygt
  
•   ltwitsmlregiongtRegion Namelt/witsmlregion
  gt

14
API Modules Store Interface

• Store Interface remote access via SOAP
• Defined in WSDL
• GetCap Get server capabilities
• AddToStore Add new objects
• GetFromStore Retrieve objects
• DeleteFromStore Remove objects
• UpdateInStore Update objects
• GetVersion Get API version

15
API Modules - Other Interfaces

• Realtime Interface
• Publisher/Subscriber model
• Subscriber can query publisher capabilities
• Data delivered via HTTP POST
• Utility Interfaces internal use on Server
• Document Interface
• Item Interface

16
API GetFromStore

• API GetFromStore Query Template
• ltwitsmlwellsgt
• ltwitsmlwell uidWellgt
• ltwitsmlnameLegal /gt
• ltwitsmlnumLicense /gt
• lt/witsmlwellgt
• lt/witsmlwellsgt

17
API DeleteFromStore

• API DeleteFromStore Query Template
• ltwellsgt
• ltwell uidWell123/gt
• ltwell uidWell456/gt
• lt/wellsgt

18
Web Site

• Web Site www.witsml.org
• Details of object schemas
• Documentation
• Downloadable API implementation
• Feedback discussion

19
Future

• Data standard maintained by POSC
• Discussions ongoing
• Integration with PWLS and WellLogML
• New Domains
• Completions and Production
• Initial meeting 18 Oct 2001 in Houston
• More Sponsors
• Other major oil companies have been approached to
  sponsor future development of WITSML

20
Problems

• Application Domain Understanding
• Generic API not as intuitive as a more domain
  specific API
• Terminology issues
• SOAP technology tools still developing
• Different SOAP implementations not compatible.
  Microsoft/Sun/Apache APIS
• XML Schema still evolving
• Validation APIs still immature or not available