The present disclosure applies to selective activated tubing profiles for well completion.
A mono-bore typically refers to a well drilled as a single-diameter hole from the surface casing to total depth. A mono-bore well can be drilled in less time than other designs. The mono-bore approach results in a greater casing diameter in the lateral, which facilitates larger completion volumes and higher flow rates into the well. The larger diameter lateral also provides for an easier re-entry into the well in the future. The mono-bore uses only one drill bit type and one bottom hole assembly configuration to reach total depth.
The present disclosure describes techniques that can be used for completing wells with a mono-bore completion. Aspects of the present disclosure provide oil, gas, and water well operators with the ability to install mono-bore (invariable diameter) completion that is supplemented with an ad-hoc retractable landing profile. Three different modes of operations can be used to deploy the landing profiles by means of mechanical, and/or hydraulic, and/or electrical activation.
In some implementations, a computer-implemented method includes the following. A tubular joint for a well string can include an elongated tube that includes an inner surface and an outer surface; a thrusting element affixed to the inner surface of the tubular joint; a landing pad disposed along the tubular joint, the landing pad secured to the thrusting element by a spring; wherein the landing pad is configured to move outward from the outer surface relative to the thrusting element.
The described implementations are implementable using a computer-implemented method; a non-transitory, computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer-implemented system including a computer memory interoperably coupled with a hardware processor configured to perform the computer-implemented method/the instructions stored on the non-transitory, computer-readable medium.
The subject matter described in this specification can be implemented in particular implementations, so as to realize one or more of the following advantages. For example, aspects of the disclosure provide a way to maintain consistent internal diameter throughout the length of the tubing string, which can facilitate the running of large tools through the string to carry out operations in the lower completion. In addition to providing accessibility, aspects of the embodiments can reduce the risk of scale precipitation, which can occur in conventional landing profiles. Scale precipitation in the downhole well tubulars increases at each pressure drop interval. Because tubular sections with different internal diameters (restrictions) are classified as pressure drop areas, maintaining a constant internal diameter can reduce the risk of scale precipitation. The landing pads described herein allow for a constant internal diameter while also securing the tubular in the wellbore.
In addition, maintaining constant tubular internal diameter also lowers the risk of having the tool being stuck downhole. The accessibility gained from running the completion is valuable, especially for mature wells that went through multiple workovers that led to installing more casing strings; hence wells will be completed with slim tubing sizes such as 2⅜″ and 2⅞″. Thus, maintaining the constant tubular internal diameter also mitigates the risk getting stuck or losing well intervention tools can result.
The details of one or more implementations of the subject matter of this specification are set forth in the Detailed Description, the accompanying drawings, and the claims. Other features, aspects, and advantages of the subject matter will become apparent from the Detailed Description, the claims, and the accompanying drawings.
Like reference numbers and designations in the various drawings indicate like elements. Figures are not drawn to scale.
The following detailed description describes techniques for completing a well adding a tubing joint that includes an adjustable (ad-hoc retractable) landing profile into the tubing string for a mono-bore completion, including slim mono-bore completions. Various modifications, alterations, and permutations of the disclosed implementations can be made and will be readily apparent to those of ordinary skill in the art, and the general principles defined may be applied to other implementations and applications, without departing from scope of the disclosure. In some instances, details unnecessary to obtain an understanding of the described subject matter may be omitted so as to not obscure one or more described implementations with unnecessary detail and inasmuch as such details are within the skill of one of ordinary skill in the art. The present disclosure is not intended to be limited to the described or illustrated implementations, but to be accorded the widest scope consistent with the described principles and features.
Aspects of this disclosure are directed to devices and techniques to complete wells, including wells with slim mono-bore completion. The tubing described herein includes selectively activated landing pads to install and secure mono-bore (invariable diameter) completion for production wells, including oil, gas, and water wells. The selectively activated landing pads result in tubing with an ad-hoc adjustable landing profile. The selectively activated landing profile of the tubing facilitates consistent internal diameter throughout the length of the tubing string, which is useful for running large tools down string to carry out operations in the lower completion. In addition to providing accessibility, aspects of the embodiments can reduce the risk of scale precipitation which usually occurs in conventional landing profiles. Three different modes of operations are used to deploy the landing profiles by means of mechanical, hydraulic, and/or electrical activation. Various embodiments and implementation choices are described below.
The tubing 100 can include a first flange 106a disposed at a first distal end of the tubing 100. The tubing 100 can also include a second flange 106b disposed at a second distal end of the tubing 100, opposite the first distal end. The flanges 106a and 106b can be used as couplings for other sections of tubing or other components in the completion. The flanges 106a and 106b also define a first outer diameter of the tubing 100 (shown in
The tubing 100 also includes one or more landing pads, here shown with four landing pads 104a, 104b, 104c, and 104d. The landing pads 104a-d are movable in a radial direction relative to the tubing 100 to secure the tubing 100 in the wellbore. In addition, the landing pads 104a-d are designed (and sized) to not obstruct the passage of tools and production materials through the tubing 100 at least during operation of the well and when the landing pads 104a-d are extended outwards towards the surface of the wellbore. The landing pads 104a-d are shown to be arranged at equidistant locations around the circumference of the tubing surface 102. The landing pads 104a-d can be installed on 1-3 feet of tubing joints. The tubing joints can be threaded to the tubing when designing and running the well tubular during the well completion phase.
The operation of the landing pads 104a-d is illustrated in more detail in
In
The landing pad 304 (which is similar to landing pads 104a-b) is shown. Landing pad 304 can house a shifting key 310. Shifting key 310 can move in an axial direction parallel to the centerline 302. Shifting key 310 can include a notch or other receiver to receive a downhole shifting tool 320. Downhole shifting tool 320 can be controlled by an operator at the surface using a wireline 322.
The tubing 300 includes a thrusting element 306. Thrusting element 306 is rigidly affixed to a surface of the tubing 300, such as the inner surface 108 or a side-wall surface formed by inner surface 108 and outer surface 102. The thrusting element 306 need not be an integral part of the tubing 300. Thrusting element 306 can be installed into the cavity by a threaded screw or both or other securing member. The landing pad 304 is connected to the thrusting member 306 by a spring 308. The spring 308 has sufficient spring tension to hold the landing pad 304 in place when the thrusting member is not being interacted with.
In
If the tubing 300 is to be repositioned or removed, the operator can use the downhole shifting tool to shift the shifting key away from the thrusting element 306. The spring tension of spring 308 can retract the landing pad 304 away from the wellbore surface radially towards the outer surface 102 of the tubing 300.
The landing pad 404 (which is similar to landing pads 104a-b) is shown. Landing pad 404 can house a motor 410. Motor 410 drive a rod or screw or other linear driving element 412 radially towards or away from thrusting element 406. The motor 410 can be an electric motor or a hydraulic motor. The motor 410 can be controlled using a control line 414. Control line 422 can be a wired or wireless signal that can control electric motor. Or control line 414 can be a hydraulic control line that either controls hydraulic fluid from the surface to the motor 410 or causes local hydraulic fluid to actuate a rod or screw or other linear driving element 412 to push or retract from the thrusting element 406.
The tubing 400 includes a thrusting element 406. Thrusting element 306 is rigidly affixed to a surface of the tubing 400, such as the inner surface 108 or a side-wall surface formed by inner surface 108 and outer surface 102. The landing pad 404 is connected to the thrusting member 406 by a spring 408. The spring 408 has sufficient spring tension to hold the landing pad 404 in place when the thrusting member is not being interacted with.
In
At 502, a tubing that includes a selectively activated landing profile can be introduced into a wellbore. The tubing can be introduced into the wellbore by conventional methodologies. The tubing can have the landing pads retracted for this step so that the tubing can be positioned at a desired location in the wellbore without the landing pads interfering with the surface of the wellbore. From 502, method 500 proceeds to 504.
At 504, after the tubing is positioned at the desired location in the wellbore, the landing pads can be extended. The landing pads can be extended such that one or more landing pads contacts a corresponding surface of the wellbore. The landing pads can be extended using a downhole shifting tool coupled to a control device on the surface by a wireline. The landing pads can be extended using a motor, such as an electric motor or hydraulic motor, controlled by a controller at the surface, either by a wireline or wireless communications link. The hydraulic motor can also include a hydraulic line for hydraulic fluid to travel to the hydraulic motor under pressure. The electric motor can include a power line to the surface to supply power to the electric motor.
A landing pad is extended by pushing against a thrusting element that is coupled to the landing pad by a spring and rigidly affixed to a surface of the tubing. By pushing on the stationary thrusting profile, the landing pad moves against the tension of the spring in an outward direction relative the tubing and towards the wellbore surface. The tension can be maintained by frictional forces of the shifting key wedged in place or by the static nature of the motor. From 504, method 500 proceeds to 506.
At 506, the landing pads contacting the surface of the wellbore secure the tubing in place within the wellbore. From 506, method 500 proceeds to 508.
At 508, more tubing is added as described here, in addition to other elements by conventional techniques, to complete the wellbore completion. From 508, method 500 proceeds to 510.
At 510, if desired, the landing pads can be retracted using the shifting key and tool or electric motor. The tubing can then be repositioned in or removed from the wellbore.
The computer 602 can serve in a role as a client, a network component, a server, a database, a persistency, or components of a computer system for performing the subject matter described in the present disclosure. The illustrated computer 602 is communicably coupled with a network 630. In some implementations, one or more components of the computer 602 can be configured to operate within different environments, including cloud-computing-based environments, local environments, global environments, and combinations of environments.
At a top level, the computer 602 is an electronic computing device operable to receive, transmit, process, store, and manage data and information associated with the described subject matter. According to some implementations, the computer 602 can also include, or be communicably coupled with, an application server, an email server, a web server, a caching server, a streaming data server, or a combination of servers.
The computer 602 can receive requests over network 630 from a client application (for example, executing on another computer 602). The computer 602 can respond to the received requests by processing the received requests using software applications. Requests can also be sent to the computer 602 from internal users (for example, from a command console), external (or third) parties, automated applications, entities, individuals, systems, and computers.
Each of the components of the computer 602 can communicate using a system bus 603. In some implementations, any or all of the components of the computer 602, including hardware or software components, can interface with each other or the interface 604 (or a combination of both) over the system bus 603. Interfaces can use an application programming interface (API) 612, a service layer 613, or a combination of the API 612 and service layer 613. The API 612 can include specifications for routines, data structures, and object classes. The API 612 can be either computer-language independent or dependent. The API 612 can refer to a complete interface, a single function, or a set of APIs.
The service layer 613 can provide software services to the computer 602 and other components (whether illustrated or not) that are communicably coupled to the computer 602. The functionality of the computer 602 can be accessible for all service consumers using this service layer. Software services, such as those provided by the service layer 613, can provide reusable, defined functionalities through a defined interface. For example, the interface can be software written in JAVA, C++, or a language providing data in extensible markup language (XML) format. While illustrated as an integrated component of the computer 602, in alternative implementations, the API 612 or the service layer 613 can be stand-alone components in relation to other components of the computer 602 and other components communicably coupled to the computer 602. Moreover, any or all parts of the API 612 or the service layer 613 can be implemented as child or sub-modules of another software module, enterprise application, or hardware module without departing from the scope of the present disclosure.
The computer 602 includes an interface 604. Although illustrated as a single interface 604 in
The computer 602 includes a processor 605. Although illustrated as a single processor 605 in
The computer 602 also includes a database 606 that can hold data for the computer 602 and other components connected to the network 630 (whether illustrated or not). For example, database 606 can be an in-memory, conventional, or a database storing data consistent with the present disclosure. In some implementations, database 606 can be a combination of two or more different database types (for example, hybrid in-memory and conventional databases) according to particular needs, desires, or particular implementations of the computer 602 and the described functionality. Although illustrated as a single database 606 in
The computer 602 also includes a memory 607 that can hold data for the computer 602 or a combination of components connected to the network 630 (whether illustrated or not). Memory 607 can store any data consistent with the present disclosure. In some implementations, memory 607 can be a combination of two or more different types of memory (for example, a combination of semiconductor and magnetic storage) according to particular needs, desires, or particular implementations of the computer 602 and the described functionality. Although illustrated as a single memory 607 in
The application 608 can be an algorithmic software engine providing functionality according to particular needs, desires, or particular implementations of the computer 602 and the described functionality. For example, application 608 can serve as one or more components, modules, or applications. Further, although illustrated as a single application 608, the application 608 can be implemented as multiple applications 608 on the computer 602. In addition, although illustrated as internal to the computer 602, in alternative implementations, the application 608 can be external to the computer 602.
The computer 602 can also include a power supply 614. The power supply 614 can include a rechargeable or non-rechargeable battery that can be configured to be either user- or non-user-replaceable. In some implementations, the power supply 614 can include power-conversion and management circuits, including recharging, standby, and power management functionalities. In some implementations, the power-supply 614 can include a power plug to allow the computer 602 to be plugged into a wall socket or a power source to, for example, power the computer 602 or recharge a rechargeable battery.
There can be any number of computers 602 associated with, or external to, a computer system containing computer 602, with each computer 602 communicating over network 630. Further, the terms “client,” “user,” and other appropriate terminology can be used interchangeably, as appropriate, without departing from the scope of the present disclosure. Moreover, the present disclosure contemplates that many users can use one computer 602 and one user can use multiple computers 602.
In embodiments, the computer 602 can be used to control the actuation of the landing pads when the tubular joint is in the wellbore. The computer 602 can, for example, be used by an operator to control a downhole wireline shifting tool to operate the shifting key to engage or disengage the landing pad(s). Likewise, the operator can use computer 602 to control the electric or hydraulic motor to extend or retract the landing pad(s). The computer 602 can be any type of computer, including a stationary computer, mobile computer, mobile communications devices, or other computational and communications system.
Implementations of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, in tangibly embodied computer software or firmware, in computer hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Software implementations of the described subject matter can be implemented as one or more computer programs. Each computer program can include one or more modules of computer program instructions encoded on a tangible, non-transitory, computer-readable computer-storage medium for execution by, or to control the operation of, data processing apparatus. Alternatively, or additionally, the program instructions can be encoded in/on an artificially generated propagated signal. For example, the signal can be a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to a suitable receiver apparatus for execution by a data processing apparatus. The computer-storage medium can be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of computer-storage mediums.
The terms “data processing apparatus,” “computer,” and “electronic computer device” (or equivalent as understood by one of ordinary skill in the art) refer to data processing hardware. For example, a data processing apparatus can encompass all kinds of apparatuses, devices, and machines for processing data, including by way of example, a programmable processor, a computer, or multiple processors or computers. The apparatus can also include special purpose logic circuitry including, for example, a central processing unit (CPU), a field-programmable gate array (FPGA), or an application specific integrated circuit (ASIC). In some implementations, the data processing apparatus or special purpose logic circuitry (or a combination of the data processing apparatus or special purpose logic circuitry) can be hardware- or software-based (or a combination of both hardware- and software-based). The apparatus can optionally include code that creates an execution environment for computer programs, for example, code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of execution environments. The present disclosure contemplates the use of data processing apparatuses with or without conventional operating systems, such as LINUX, UNIX, WINDOWS, MAC OS, ANDROID, or IOS.
A computer program, which can also be referred to or described as a program, software, a software application, a module, a software module, a script, or code, can be written in any form of programming language. Programming languages can include, for example, compiled languages, interpreted languages, declarative languages, or procedural languages. Programs can be deployed in any form, including as stand alone programs, modules, components, subroutines, or units for use in a computing environment. A computer program can, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data, for example, one or more scripts stored in a markup language document, in a single file dedicated to the program in question, or in multiple coordinated files storing one or more modules, sub programs, or portions of code. A computer program can be deployed for execution on one computer or on multiple computers that are located, for example, at one site or distributed across multiple sites that are interconnected by a communication network. While portions of the programs illustrated in the various figures may be shown as individual modules that implement the various features and functionality through various objects, methods, or processes, the programs can instead include a number of sub-modules, third-party services, components, and libraries. Conversely, the features and functionality of various components can be combined into single components as appropriate. Thresholds used to make computational determinations can be statically, dynamically, or both statically and dynamically determined.
The methods, processes, or logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output. The methods, processes, or logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, for example, a CPU, an FPGA, or an ASIC.
Computers suitable for the execution of a computer program can be based on one or more of general and special purpose microprocessors and other kinds of CPUs. The elements of a computer are a CPU for performing or executing instructions and one or more memory devices for storing instructions and data. Generally, a CPU can receive instructions and data from (and write data to) a memory.
Graphics processing units (GPUs) can also be used in combination with CPUs. The GPUs can provide specialized processing that occurs in parallel to processing performed by CPUs. The specialized processing can include artificial intelligence (AI) applications and processing, for example. GPUs can be used in GPU clusters or in multi-GPU computing.
A computer can include, or be operatively coupled to, one or more mass storage devices for storing data. In some implementations, a computer can receive data from, and transfer data to, the mass storage devices including, for example, magnetic, magneto optical disks, or optical disks. Moreover, a computer can be embedded in another device, for example, a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device such as a universal serial bus (USB) flash drive.
Computer readable media (transitory or non-transitory, as appropriate) suitable for storing computer program instructions and data can include all forms of permanent/non-permanent and volatile/nonvolatile memory, media, and memory devices. Computer readable media can include, for example, semiconductor memory devices such as random access memory (RAM), read only memory (ROM), phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices. Computer readable media can also include, for example, magnetic devices such as tape, cartridges, cassettes, and internal/removable disks. Computer readable media can also include magneto optical disks and optical memory devices and technologies including, for example, digital video disc (DVD), CD ROM, DVD+/-R, DVD-RAM, DVD-ROM, HD-DVD, and BLU-RAY. The memory can store various objects or data, including caches, classes, frameworks, applications, modules, backup data, jobs, web pages, web page templates, data structures, database tables, repositories, and dynamic information. Types of objects and data stored in memory can include parameters, variables, algorithms, instructions, rules, constraints, and references. Additionally, the memory can include logs, policies, security or access data, and reporting files. The processor and the memory can be supplemented by, or incorporated into, special purpose logic circuitry.
Implementations of the subject matter described in the present disclosure can be implemented on a computer having a display device for providing interaction with a user, including displaying information to (and receiving input from) the user. Types of display devices can include, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), a light-emitting diode (LED), and a plasma monitor. Display devices can include a keyboard and pointing devices including, for example, a mouse, a trackball, or a trackpad. User input can also be provided to the computer through the use of a touchscreen, such as a tablet computer surface with pressure sensitivity or a multi-touch screen using capacitive or electric sensing. Other kinds of devices can be used to provide for interaction with a user, including to receive user feedback including, for example, sensory feedback including visual feedback, auditory feedback, or tactile feedback. Input from the user can be received in the form of acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to, and receiving documents from, a device that the user uses. For example, the computer can send web pages to a web browser on a user's client device in response to requests received from the web browser.
The term “graphical user interface,” or “GUI,” can be used in the singular or the plural to describe one or more graphical user interfaces and each of the displays of a particular graphical user interface. Therefore, a GUI can represent any graphical user interface, including, but not limited to, a web browser, a touch-screen, or a command line interface (CLI) that processes information and efficiently presents the information results to the user. In general, a GUI can include a plurality of user interface (UI) elements, some or all associated with a web browser, such as interactive fields, pull-down lists, and buttons. These and other UI elements can be related to or represent the functions of the web browser.
Implementations of the subject matter described in this specification can be implemented in a computing system that includes a back end component, for example, as a data server, or that includes a middleware component, for example, an application server. Moreover, the computing system can include a front-end component, for example, a client computer having one or both of a graphical user interface or a Web browser through which a user can interact with the computer. The components of the system can be interconnected by any form or medium of wireline or wireless digital data communication (or a combination of data communication) in a communication network. Examples of communication networks include a local area network (LAN), a radio access network (RAN), a metropolitan area network (MAN), a wide area network (WAN), Worldwide Interoperability for Microwave Access (WIMAX), a wireless local area network (WLAN) (for example, using 802.11 a/b/g/n or 802.20 or a combination of protocols), all or a portion of the Internet, or any other communication system or systems at one or more locations (or a combination of communication networks). The network can communicate with, for example, Internet Protocol (IP) packets, frame relay frames, asynchronous transfer mode (ATM) cells, voice, video, data, or a combination of communication types between network addresses.
The computing system can include clients and servers. A client and server can generally be remote from each other and can typically interact through a communication network. The relationship of client and server can arise by virtue of computer programs running on the respective computers and having a client-server relationship.
Cluster file systems can be any file system type accessible from multiple servers for read and update. Locking or consistency tracking may not be necessary since the locking of exchange file system can be done at application layer. Furthermore, Unicode data files can be different from non-Unicode data files.
While this specification contains many specific implementation details, these should not be construed as limitations on the scope of what may be claimed, but rather as descriptions of features that may be specific to particular implementations. Certain features that are described in this specification in the context of separate implementations can also be implemented, in combination, in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations, separately, or in any suitable sub-combination. Moreover, although previously described features may be described as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can, in some cases, be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.
Particular implementations of the subject matter have been described. Other implementations, alterations, and permutations of the described implementations are within the scope of the following claims as will be apparent to those skilled in the art. While operations are depicted in the drawings or claims in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed (some operations may be considered optional), to achieve desirable results. In certain circumstances, multitasking or parallel processing (or a combination of multitasking and parallel processing) may be advantageous and performed as deemed appropriate.
Moreover, the separation or integration of various system modules and components in the previously described implementations should not be understood as requiring such separation or integration in all implementations. It should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
Accordingly, the previously described example implementations do not define or constrain the present disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of the present disclosure.
Furthermore, any claimed implementation is considered to be applicable to at least a computer-implemented method; a non-transitory, computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system including a computer memory interoperably coupled with a hardware processor configured to perform the computer-implemented method or the instructions stored on the non-transitory, computer-readable medium.