24
Using the WITSML™ protocol for analysis in Drillworks – past case studies and current applications Drew Swanson May 11, 2006

Using the WITSML™ protocol for analysis in Drillworks – past case studies and current applications Drew Swanson May 11, 2006

Embed Size (px)

Citation preview

Using the WITSML™ protocol for analysis in Drillworks – past case studies and current applications

Drew SwansonMay 11, 2006

Outline

• Who is Knowledge Systems and what is Drillworks

• Importance of Real-time Decision Making

• 4 WITSML Case Studies

• Current WITSML Project and Drillworks

Software

– • Advanced geomechanics and geopressure

technologies

• Relational database used to store, manage and share pressure-related data

Services– Planning

• Pre-drill pore pressure analysis

• Wellbore stability analysis• Borehole trajectory planning• Mud weight optimization

– Surveillance• Wellsite monitoring• Real-time model updating• Remote operations• WITSML data transmission

– KnowledgeManagement

• Pressworks database

implementation

• Data loading

• Connector building

• Quality assurance

Using WITSML to avoid NPT

• 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)

Anatomy of an Operations Decision

VA

LUE

TIME

Creating Actionable Information from Data

Reduce NPT with Real-time Surveillance

•Acquire quality data

•Transport data to observers

•Convert data to information

•Communicate information to decision-makers

Case Study #1 Background

• 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

Configuration

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

Configuration

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 Study #3 Background

• Client in case #2 switched LWD vendors

• Scenario typically causes multitude of data transfer issues

• Requires significant work on both sides to regain connections

Configuration

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 Study #4 Background

• 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

Configuration

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

Current WITSML Project and Drillworks

WITSML Status at Knowledge Systems

• WITSML connection to Drillworks happening everyday around the world

• One client in Houston (Mid-size) has 3 rigs running today with WITSML to

Drillworks in GOM

• Another client in North Sea has 2 rigs connecting via WITSML to

Operations Center

• No longer theory…Contributing to the bottom line right now!

* SPE Paper 99466