SPE 74480WITSML: Technology to Business (T2B) for the Oilfield

J.Holt, SPE, BP plc; I. Haarstad, SPE, Statoil; J.A. Shields, SPE, Baker Hughes; J.P. James, Schlumberger; D. Seiler, SPE, Halliburton Energy Services

“A New Information Transfer Standard”

History

• Amoco Critical Drilling Facility and Advanced Drilling Facility

• Chevron Data Center• Mobil Data Center• WITS (Wellsite Information Transfer

Specification)• DART (Data Automation Real Time)• Proprietary Systems

Project Goal

• The “right time” seamless flow of well site data between operators and service companies to speed and enhance decision-making.

Domain:Drilling, Completion, Well Services

Existing Standards

• WITS– Designed, implemented, and established as an

industry standard in the mid eighties– A binary file format for transferring wellsite drilling

data– No standard programming interface– Limited data objects– It was great for it’s time, but times have changed.

Potential Scenarios

Project Timing

• Initiation of Project - Oct 2000• Data Objects defined May 2001• July 2001 – Working prototype• Wider industry roll-out at SPE Forum + Austin

workshop 21/22nd Aug 2001• Data standard design freeze 1st Oct, 2001• January 2002 – Commercial offering by three

major service companies and at least one small or midsize company

Project Organization

• Steering Board• Technical Teams

– Data Objects– IT Architecture

• Program Manager

Companies involved to date:BP, Statoil,Halliburton, Schlumberger, BHI

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

Open Sourced Deliverables

• Definition of Data Objects & Catalogs• Example WITSML files• Validation tool for WITSML files• Example code to read and write simple

WITSML data files• Documentation

WITSML API

• Interface Definition

• Prototype Implementation

WITSML API - Interfaces

• STORE (WMLS) Interface: Provides access to Persistent Store

Returns/Accepts entire WITSML Data Objects as XML Documents

• DOCUMENT (WMLD) Interface: Routes to Local or Remote STORE (WMLS) Interface Returns/Accepts entire WITSML Data Objects as XML Documents

WITSML API - Interfaces

• ITEM (WMLI) Interface: Provides access to WITSML Data Object at individual data item level

(isolates application from XML) Provides synchronous validation against schema

• REALTIME (WMLR and WMLP) Interfaces: Transport of REALTIME WITSML Data ObjectsSubscribe/Publish Paradigm

WITSML API - Interfaces

WMLI (Item Interface)API Implementation

WMLD (Document Interface) API Implementation

Realtime SubscriberInterface (WMLR)

API Implementation

CLIENT APPLICATION

LOCALPERSISTENT

STORE(black box)

WMLI_function_call WMLD_function_call WMLR_function_call

WMLD_function_call

CALL DATAITEM

CALL XMLDocument

XMLDocument

CALL CALL

using the ITEMInterface

using the DOCUMENTInterface

using the REALTIMESubscriber Interface

CLIENT APPLICATION

Local WMLS (Store Interface)API Implementation

CLIENT APPLICATIONusing the STORE

Interface

WMLS_function_call

CALL

XMLDocument

WMLD_function_call

XMLDocument

CALLCALL XMLDocument

Remote WMLS (Store Interface)API Implementation

REMOTEPERSISTENT

STORE(black box)

IMPLEMENTATION-SPECIFIC FORMAT

WMLD_function_call

SOAP

Realtime Publisher(WMLP)

API Implementation

CLIENT APPLICATIONusing the REALTIME

Publisher Interface

WMLP_function_call

CLIENT APPLICATION

CALL

SOAP

POST

WITSML API - Network Protocol - Data Object Access

WMLS (Store)GetFromStore

Implementation

PERSISTENTSTORE

(black box)

CLIENTAPPLICATION

InvokesWMLI_GetObject()

WMLI (ITEM)GetObject

Implementation

WMLD(DOCUMENT)GetDocument

Implementation

InvokesWMLD_GetDocument()

InvokesWMLS_GetFromStore

via SOAP

SOAP Client

SOAP ServerInvokes

WMLS_GetFromStore

retrieves WITSMLobject and returns it

as XML

XML

XML

SOAP RPC over HTTP over TCP/IP

XML

XML

Individual Data Items accessible by subsequent calls to WMLI

WITSML API - Network Protocol - Realtime Transfer - Subscribe

WMLP(REALTIMEPUBLISHER)

SubscribeImplementation

CLIENTAPPLICATION

InvokesWMLR_Subscribe()

WMLR (REALTIMESUBSCRIBER)

SubscribeImplementation

InvokesWMLP_Subcribe()

via SOAP

SOAP Client

SOAP Server

InvokesWMLP_Subscribe()

stores subscriberinformation

SOAP RPC over HTTP over TCP/IP

WMLP (REALTIMEPUBLISHER)

Publish Implementation

Web ServerPUBLISHER

APPLICATION

WMLR (REALTIMESUBSCRIBER)

Publish Implementation

InvokesWMLP_Publish()

retrieves subscriberinformation

Sends data via HTTPPOST to subscriberHTTP POSTInvokes

WMLR_Publish()

Stores or forwardsreceived data

WMLR (REALTIMESUBSCRIBER)HTTP Listener

WITSML API - Network Protocol - Realtime Transfer - Publish

Data Objects

• Well• Wellbore• Rig

– Rig Equipment– Pump

• Location• Units• Trajectory• Target• Bit Record

• Bottom Hole Assembly• Wellbore Geometry

– Casing Scheme– Open Hole

• Daily Operations• Fluids Report• Cement Job• Log• Real Time• Mud Logging

Future

• Data standard owned by on oilfield standards organisation– Still under discussion– Now has its own web presence– Seek alignment with other XML efforts such as

WellLogML

• Steering Board will continue– Original companies plus others

Completions & Workovers

• Define objects applicable to the completion and workover domain

• Objects will be consistent with existing WITSML objects

• Objects will cover the requirements for life-of-well

Production Operations

• Define objects applicable to the well-centric production domain

• Objects will be consistent with existing WITSML objects

• Surface production facilities will not be included in this phase

Production Operations

• Data object Examples• “Smart” completion data – sensor and

actuator data, equipment settings• Well test data• Artificail lift operating parameters• Valve, sleeve and choke positions• Flow, pressures and temperatures

Further Information

• Web Site: www.witsml.org– Full details of object schemas– Documentation– Downloadable API components