Transcript No Drilling Surprises

SPE 74480
WITSML: 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 Objects
Subscribe/Publish Paradigm
WITSML API - Interfaces
CLIENT APPLICATION
using the ITEM
Interface
CLIENT APPLICATION
using the DOCUMENT
Interface
CLIENT APPLICATION
using the STORE
Interface
CLIENT APPLICATION
using the REALTIME
Subscriber Interface
WMLI_function_call
WMLD_function_call
WMLS_function_call
WMLR_function_call
CALL
DATA
ITEM
CALL
XML
Document
XML
Document
WMLD (Document Interface) API Implementation
WMLD_function_call
WMLD_function_call
SOAP
XML
Document
Remote WMLS (Store Interface)
API Implementation
CALL
XML
Document
XML
Document
Local WMLS (Store Interface)
API Implementation
IMPLEMENTATION-SPECIFIC FORMAT
REMOTE
PERSISTENT
STORE
(black box)
CALL
SOAP
Realtime Subscriber
Interface (WMLR)
API Implementation
WMLD_function_call
CALL
WMLP_function_call
CALL
CALL
WMLI (Item Interface)
API Implementation
CALL
CLIENT APPLICATION
using the REALTIME
Publisher Interface
LOCAL
PERSISTENT
STORE
(black box)
POST
Realtime Publisher
(WMLP)
API Implementation
WITSML API - Network Protocol Data Object Access
CLIENT
APPLICATION
Invokes
WMLI_GetObject()
Individual Data Items accessible by subsequent calls to WMLI
WMLI (ITEM)
GetObject
Implementation
Invokes
WMLD_GetDocument()
XML
WMLD(DOCUMENT)
GetDocument
Implementation
Invokes
WMLS_GetFromStore
via SOAP
XML
XML
SOAP Client
SOAP Server
Invokes
WMLS_GetFromStore
SOAP RPC over HTTP over TCP/IP
XML
retrieves WITSML
object and returns it
as XML
PERSISTENT
STORE
(black box)
WMLS (Store)
GetFromStore
Implementation
WITSML API - Network Protocol Realtime Transfer - Subscribe
CLIENT
APPLICATION
WMLR (REALTIME
SUBSCRIBER)
Subscribe
Implementation
Invokes
WMLR_Subscribe()
Invokes
WMLP_Subcribe()
via SOAP
SOAP Server
SOAP Client
Invokes
WMLP_Subscribe()
SOAP RPC over HTTP over TCP/IP
stores subscriber
information
WMLP
(REALTIME
PUBLISHER)
Subscribe
Implementation
WITSML API - Network Protocol Realtime Transfer - Publish
retrieves subscriber
information
Invokes
WMLP_Publish()
Web Server
WMLR (REALTIME
SUBSCRIBER)
HTTP Listener
WMLR (REALTIME
SUBSCRIBER)
Publish Implementation
Invokes
WMLR_Publish()
Stores or forwards
received data
HTTP POST
Sends data via HTTP
POST to subscriber
PUBLISHER
APPLICATION
WMLP (REALTIME
PUBLISHER)
Publish Implementation
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 wellcentric 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