WITSML® Enables Synchronous Remote Modeling and Surveillance via the Internet
William Standifird, Vice President Operations
Outline
• Creating a Functional Wellbore
• Challenges
• Proposed Solution
• Case Studies of Real-Time Applications
Creating a Functional Wellbore
SAFE OPERATING ENVELOPE
The Cost of Wellbore Problems
• Stuck Pipe
• Kick
• Lost Circulation
• Sloughing Shale
• Flows
• Wellbore Instability
• 41% of total NPT• US $8B+ Annually
James K. Dodson Co. 1993-2002 Year NPT Analysis
(Offshore, Jan 2004)
PLANNED ACTUAL
FPG
PPG
PPG
FPG
>2ppg
<1ppg
Example of Common Drilling Problem
Preferred Solution = Real-time Surveillance
•Acquire quality data
•Transport data to observers
•Convert data to information
•Communicate information to decision-makers
Creating Actionable Information from Data
Anatomy of an Operations Decision
VA
LUE
TIME
Anatomy of an Operations Decision
Case-1 Environment
• Deepwater Well offshore Trinidad
• Significant uncertainty in subsurface environment
• High potential for unscheduled events related to uncertainty
• Need for real-time geomechanics modeling
• Operator domain expert is not offshore deployable resource
• Unplanned requirement ~ low budget & short fuse
WITSML Server v1.2
Sensor
Sensor Aggregator Application
PorePressure Expert & Application
Sensor
Sensor
WIT
S
Geomechanics Expert &
Application
BP OfficePOS Trinidad
Constellation-1 DeepWater Trinidad
BP OfficeHouston Texas
WITSML Client v1.2
WITSML Server v1.2
WITSML
INTRANET
WIT
SM
LLOW BANDWIDTHLINK
Case-1 Schematic
Case-1 Installation
• Baker Hughes Inteq installed WITSML v1.2 server in Port of Spain
• <30 Minutes in BP Houston Offices
– Installed Drillworks ConnectML on client PC
– IP Address, UN, Pass, Configuration for server connection
– Configure Drillworks data links to ConnectML
– Expert begins modeling using real-time data
– Expert activates WITSML server to make interpretation
available to rig
Case-2 Environment
• Deepwater Gulf of Mexico Well
• Narrow PP FP envelope (high risk of influx or losses)
• High potential for pressure related unscheduled events
• Client requested expert synchronous surveillance from
Houston offices
• Replace WITS with WITSML
LOW BANDWIDTHLINK
WITSML Server v1.2
Sensor
Sensor Aggregator Application
Sensor
Sensor
Client OfficeHouston Texas
Ocean Amirante DeepWater Gulf of Mexico
WITSML Client v1.2
INTRANET
WIT
SM
L
Case-2 Schematic
PorePressure Application and Expert
Case-2 Installation
• Baker Hughes Inteq installed WITSML v1.2 server
• <30 Minutes in Client Houston Offices
– Installed Drillworks ConnectML on client PC
– IP Address, UN, Pass, Configuration for server connection
– Configure Drillworks data links to ConnectML
– Expert begins modeling using real-time data
Case-3 Environment
• Client in case #2 switched LWD vendors
LOW BANDWIDTHLINK
WITSML Server v1.2
Sensor
Sensor Aggregator Application
Sensor
Sensor
Client OfficeHouston Texas
Ocean Amirante DeepWater Gulf of Mexico
WITSML Client v1.2
INTRANET
WIT
SM
L
Case-3 Schematic
PorePressure Application and Expert
Case-3 Installation
• Schlumberger installed WITSML v1.2 server
• <10 minutes to reconfigure system
– IP Address, UN, Pass, Configuration for server connection
– Configure Drillworks data links to ConnectML
– Expert ready for modeling using real-time data before first tools
run in hole
Case-4 Environment
• Shelf project in Gulf of Mexico
• Precise casing set requirements due to PP ramp
• Limited rig space for additional personnel
• Economics would not support onsite analyst
• Client requested synchronous remote surveillance
LOW BANDWIDTHLINK
WITSML Server v1.2
Sensor
Sensor Aggregator Application
Sensor
Sensor
Schlumberger OfficePride Georgia
Gulf of Mexico Shelf
WITSML Client v1.2
INTRANET
WIT
SM
L
Case-4 Schematic
PorePressure Application and Expert
KSI OfficeSugar Land Texas
Case-4 Installation
• Schlumberger installed WITSML v1.2 server
– No apparent delay, unknown install time
• <30 minutes to configure WITSML client system
– IP Address, UN, Pass, Configuration for server connection
– Configure Drillworks data links to ConnectML
– Expert ready for modeling
Lessons Learned
• WITSML updates slower than WITS
– Internet time versus direct cable time
• Concurrent use of proprietary system (Riglink, Interact) aids in
monitoring data dead zones
• System is still imperfect, and requires companies to collaborate on
problems
• WITSML must be planned before a project.
– Connections attempted as after thoughts have failed.
Key Accomplishments
• Technology
– Short connect and configure time of <30 minutes
– No special hardware or IT involvement required
– Low cost
– Secure synchronous and asynchronous data
exchange
– Omni-directional, multi-user data movement
– Portable
Key Accomplishments
Operations
– Maximum utilization of bandwidth, data and expertise
– Cross discipline collaboration
– Delivered the right information to the right people, at
the right time
– Better decisions resulting from right time, expert
analysis
Progress?
• Multiple connections with two major service
providers
• Successful test with Halliburton 11/05
• Operators becoming more aggressive in their
insistence on WITSML
Using WITSML to Reduce Trouble Time
Transport
CommunicateConvert
Acquire