Drill pipe depth, trip speed, and RPM sensor using computer vision
The integration of a computer vision-equipped RCD with MPD systems addresses the reliance on rig-based data by accurately measuring drill string parameters, enhancing operational efficiency and compatibility with different rigs.
Patent Information
- Application Number
- US19/381910
- Authority / Receiving Office
- US · United States
- Patent Type
- Applications(United States)
- Current Assignee / Owner
- Priority Date
- 2024-11-12
- Filing Date
- 2025-11-06
- Publication Date
- 2026-11-12
AI Technical Summary
Current managed pressure drilling (MPD) systems rely heavily on rig-based data for downhole pressure control, increasing rig-up time and complicating operations, and lack sensors to accurately measure parameters like pipe speed and rotations per minute (RPM) for precise pressure management.
Implement a rotating control device (RCD) equipped with computer vision sensors, including a camera and ultrasonic distance sensors, to track drill string anomalies and determine parameters like RPM, block speed, and wellbore depth, enabling real-time monitoring and control of drilling operations.
Enhances the precision and efficiency of MPD by reducing dependency on rig data, allowing smoother rig-up processes and unlocking additional software modules, thereby improving compatibility with various rigs and enhancing operational control.
Smart Images

Figure US20260357666A1-D00000_ABST
Abstract
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 719,219, filed on Nov. 12, 2024, which is incorporated by reference.BACKGROUND
[0002] Managed pressure drilling (MPD) is an adaptive drilling method used to precisely control the annular pressure throughout a wellbore. After determining the downhole pressure environment, drillers manage wellbore pressure constrained by the limits of formation properties. The annular pressure is kept slightly above the pore pressure to prevent the influx of formation fluids into the wellbore, but it is maintained below the fracture initiation pressure. Rapid corrective actions can often be implemented to deal with observed pressure variations. The MPD process may utilize a variety of techniques including adjusting mud density, modifying fluid rheology, adjusting the annular fluid level, controlling circulating friction, and incorporating hole geometry in the well construction.
[0003] The downhole pressure environment is determined based upon data from the rig. This data dependency often increases rig-up time and adds layers of complication, which often involves additional support personnel. Therefore, what is needed is an improved system and method for monitoring and controlling MPD.SUMMARY
[0004] A method for performing a managed pressure drilling (MPD) operation is disclosed. The method includes positioning a sensor proximate to a drill string. The method also includes identifying an area on the drill string using the sensor. The method also includes tracking the area on the drill string using the sensor. Tracking the area includes determining an amount and a direction of movement over time. The method also includes determining one or more drilling parameters based upon the movement over time.
[0005] A computing system is also disclosed. The computing system includes one or more processors and a memory system. The memory system includes one or more non-transitory computer-readable media storing instructions that, when executed by at least one of the one or more processors, cause the computing system to perform operations. The operations include positioning a rotating control device (RCD) around a drill string. The RCD is configured to form a seal with the drill string while the drill string rotates. The method also includes positioning a sensor in a location where the sensor is able to capture images of the drill string. The location can be on the RCD or anywhere on the rig's structure such as rig floor, substructure, or derrick. The sensor includes a camera configured to capture the images of the drill string. The operations also include identifying an area on the drill string using the sensor. The area includes a visual anomaly. The visual anomaly includes a recess, a protrusion, and / or a color variation. The operations also include tracking the area on the drill string using the sensor. Tracking the area includes determining an amount and a direction of movement over time. The operations also include determining one or more drilling parameters based upon the movement over time. The movement is along an X-axis and / or Y-axis. The one or more parameters include a number of rotations per minute (RPM) of the drill string, a block speed of the drill string, a depth of a drill bit, a depth of a wellbore, a tripping-in speed, a tripping-out speed, or a combination thereof.
[0006] A non-transitory computer-readable medium is also disclosed. The medium stores instructions that, when executed by one or more processors of a computing system, cause the computing system to perform operations. The operations include positioning a rotating control device (RCD) around a drill string. The RCD is positioned above a blow-out preventer (BOP). The RCD is configured to form a seal with the drill string while the drill string rotates. The operations also include positioning a sensor in a location where the sensor is able to capture images of the drill string. The location can be on the RCD or anywhere on the rig's structure such as rig floor, substructure or derrick. The sensor includes a camera configured to capture the images of the drill string. The camera is configured to capture the images as the drill string moves in and out through the RCD. The sensor also includes first and second distance sensors positioned on opposite sides of the camera. The first and second distance sensors include ultrasonic distance sensors that are configured to measure first and second distances from drill string. The sensor also includes a processing unit that is configured to process the images and the first and second distances. The operations also include tripping the drill string into the wellbore. The operations also include identifying an area on the drill string using the sensor while the drill string is being tripped into the wellbore. The area includes a visual anomaly. The visual anomaly includes a recess, a protrusion, and / or a color variation. The operations also include tracking the area on the drill string using the sensor. Tracking the area includes determining an amount and a direction of movement over time. The operations also include determining one or more drilling parameters based upon the movement over time. The movement is along an X-axis and / or Y-axis. The one or more parameters include a number of rotations per minute (RPM) of the drill string, a block speed of the drill string, a depth of a drill bit, a depth of the wellbore, and a tripping-in speed or a tripping-out speed. The operations also include displaying the movement over the time and the one or more parameters. The operations also include performing an action in response to the one or more parameters.
[0007] It will be appreciated that this summary is intended merely to introduce some aspects of the present methods, systems, and media, which are more fully described and / or claimed below. Accordingly, this summary is not intended to be limiting.BRIEF DESCRIPTION OF THE DRAWINGS
[0008] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present teachings and together with the description, serve to explain the principles of the present teachings. In the figures:
[0009] FIG. 1 illustrates an example of a system that includes various management components to manage various aspects of a geologic environment, according to an embodiment.
[0010] FIGS. 2A and 2B illustrate photographs of tubular members with uneven (e.g., rough) outer surfaces, according to an embodiment.
[0011] FIG. 3 illustrates a block diagram of the sensor, according to an embodiment.
[0012] FIG. 4 illustrates two images captured at different times that show the tracked area in two different locations (e.g., due to movement of the tubular members), according to an embodiment.
[0013] FIG. 5 illustrates a flowchart of a method for performing a managed pressure drilling (MPD) operation, according to an embodiment.
[0014] FIG. 6 illustrates a schematic side view of the MPD operation being performed, according to an embodiment.
[0015] FIG. 7 illustrates a schematic view of a computing system for performing at least a portion of the method(s) described herein, according to an embodiment.DETAILED DESCRIPTION
[0016] Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings and figures. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be apparent to one of ordinary skill in the art that the present disclosure may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
[0017] It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first object or step could be termed a second object or step, and, similarly, a second object or step could be termed a first object or step, without departing from the scope of the present disclosure. The first object or step, and the second object or step, are both, objects or steps, respectively, but they are not to be considered the same object or step.
[0018] The terminology used in the description herein is for the purpose of describing particular embodiments and is not intended to be limiting. As used in this description and the appended claims, the singular forms “a,”“an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and / or” as used herein refers to and encompasses any possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,”“including,”“comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. Further, as used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context.
[0019] Attention is now directed to processing procedures, methods, techniques, and workflows that are in accordance with some embodiments. Some operations in the processing procedures, methods, techniques, and workflows disclosed herein may be combined and / or the order of some operations may be changed.System Overview
[0020] FIG. 1 illustrates an example of a system 100 that includes various management components 110 to manage various aspects of a geologic environment 150 (e.g., an environment that includes a sedimentary basin, a reservoir 151, one or more faults 153-1, one or more geobodies 153-2, etc.). For example, the management components 110 may allow for direct or indirect management of sensing, drilling, injecting, extracting, etc., with respect to the geologic environment 150. In turn, further information about the geologic environment 150 may become available as feedback 160 (e.g., optionally as input to one or more of the management components 110).
[0021] In the example of FIG. 1, the management components 110 include a seismic data component 112, an additional information component 114 (e.g., well / logging data), a processing component 116, a simulation component 120, an attribute component 130, an analysis / visualization component 142 and a workflow component 144. In operation, seismic data and other information provided per the components 112 and 114 may be input to the simulation component 120.
[0022] In an example embodiment, the simulation component 120 may rely on entities 122. Entities 122 may include earth entities or geological objects such as wells, surfaces, bodies, reservoirs, etc. In the system 100, the entities 122 can include virtual representations of actual physical entities that are reconstructed for purposes of simulation. The entities 122 may include entities based on data acquired via sensing, observation, etc. (e.g., the seismic data 112 and other information 114). An entity may be characterized by one or more properties (e.g., a geometrical pillar grid entity of an earth model may be characterized by a porosity property). Such properties may represent one or more measurements (e.g., acquired data), calculations, etc.
[0023] In an example embodiment, the simulation component 120 may operate in conjunction with a software framework such as an object-based framework. In such a framework, entities may include entities based on pre-defined classes to facilitate modeling and simulation. A commercially available example of an object-based framework is the MICROSOFT® .NET® framework (Redmond, Washington), which provides a set of extensible object classes. In the .NET® framework, an object class encapsulates a module of reusable code and associated data structures. Object classes can be used to instantiate object instances for use in by a program, script, etc. For example, borehole classes may define objects for representing boreholes based on well data.
[0024] In the example of FIG. 1, the simulation component 120 may process information to conform to one or more attributes specified by the attribute component 130, which may include a library of attributes. Such processing may occur prior to input to the simulation component 120 (e.g., consider the processing component 116). As an example, the simulation component 120 may perform operations on input information based on one or more attributes specified by the attribute component 130. In an example embodiment, the simulation component 120 may construct one or more models of the geologic environment 150, which may be relied on to simulate behavior of the geologic environment 150 (e.g., responsive to one or more acts, whether natural or artificial). In the example of FIG. 1, the analysis / visualization component 142 may allow for interaction with a model or model-based results (e.g., simulation results, etc.). As an example, output from the simulation component 120 may be input to one or more other workflows, as indicated by a workflow component 144.
[0025] As an example, the simulation component 120 may include one or more features of a simulator such as the ECLIPSE™ reservoir simulator (SLB, Houston Texas), the INTERSECT™ reservoir simulator (SLB, Houston Texas), etc. As an example, a simulation component, a simulator, etc. may include features to implement one or more meshless techniques (e.g., to solve one or more equations, etc.). As an example, a reservoir or reservoirs may be simulated with respect to one or more enhanced recovery techniques (e.g., consider a thermal process such as SAGD, etc.).
[0026] As an example, the simulation component 120 may include one or more features of a simulator such as SYMMETRY™ software (SLB, Houston, Texas). More particularly, SYMMETRY™ may process workflows in a single integrated environment with accurate thermodynamic fluid representation and consistent modeling across multiple disciplines including process, production, and HSE. The simulator integrates steady-state and transient (e.g., dynamic) analyses that can be tailored for each domain. This approach enables users to optimize processes in upstream, midstream, and downstream sectors while maximizing profits and minimizing capital expenditures. It may also help reduce emissions, energy consumption, and waste.
[0027] As an example, the simulation component 120 may include one or more features of a simulator such as PIPESIM™ (SLB, Houston, Texas). More particularly, PIPESIM™ is steady-state multiphase flow simulator that incorporates the three areas of flow modeling: multiphase flow, heat transfer and fluid behavior.
[0028] As an example, the simulation component 120 may include one or more features of a simulator such as OLGA™ (SLB, Houston, Texas). More particularly, OLGA™ is a dynamic multiphase flow simulator that models transient flow (e.g., time-dependent behaviors) to maximize production potential. Transient modeling is a component for feasibility studies and field development design. Dynamic simulation is useful in deep water and is used in both offshore and onshore developments to investigate transient behavior in pipelines and wellbores. Transient simulation with the OLGA™ simulator provides an added dimension to steady-state analysis by predicting system dynamics, such as time-varying changes in flow rates, fluid compositions, temperature, solids deposition, and operational changes.
[0029] In an example embodiment, the management components 110 may include features of a commercially available framework such as the PETREL® seismic to simulation software framework (SLB, Houston, Texas). The PETREL® framework provides components that allow for optimization of exploration and development operations. The PETREL® framework includes seismic to simulation software components that can output information for use in increasing reservoir performance, for example, by improving asset team productivity. Through use of such a framework, various professionals (e.g., geophysicists, geologists, and reservoir engineers) can develop collaborative workflows and integrate operations to streamline processes. Such a framework may be considered an application and may be considered a data-driven application (e.g., where data is input for purposes of modeling, simulating, etc.).
[0030] In an example embodiment, various aspects of the management components 110 may include add-ons or plug-ins that operate according to specifications of a framework environment. For example, a commercially available framework environment marketed as the OCEAN® framework environment (SLB, Houston, Texas) allows for integration of add-ons (or plug-ins) into a PETREL® framework workflow. The OCEAN® framework environment leverages .NET® tools (Microsoft Corporation, Redmond, Washington) and offers stable, user-friendly interfaces for efficient development. In an example embodiment, various components may be implemented as add-ons (or plug-ins) that conform to and operate according to specifications of a framework environment (e.g., according to application programming interface (API) specifications, etc.).
[0031] FIG. 1 also shows an example of a framework 170 that includes a model simulation layer 180 along with a framework services layer 190, a framework core layer 195 and a modules layer 175. The framework 170 may include the commercially available OCEAN® framework where the model simulation layer 180 is the commercially available PETREL® model-centric software package that hosts OCEAN® framework applications. In an example embodiment, the PETREL® software may be considered a data-driven application. The PETREL® software can include a framework for model building and visualization.
[0032] As an example, a framework may include features for implementing one or more mesh generation techniques. For example, a framework may include an input component for receipt of information from interpretation of seismic data, one or more attributes based at least in part on seismic data, log data, image data, etc. Such a framework may include a mesh generation component that processes input information, optionally in conjunction with other information, to generate a mesh.
[0033] In the example of FIG. 1, the model simulation layer 180 may provide domain objects 182, act as a data source 184, provide for rendering 186 and provide for various user interfaces 188. Rendering 186 may provide a graphical environment in which applications can display their data while the user interfaces 188 may provide a common look and feel for application user interface components.
[0034] As an example, the domain objects 182 can include entity objects, property objects and optionally other objects. Entity objects may be used to geometrically represent wells, surfaces, bodies, reservoirs, etc., while property objects may be used to provide property values as well as data versions and display parameters. For example, an entity object may represent a well where a property object provides log information as well as version information and display information (e.g., to display the well as part of a model).
[0035] In the example of FIG. 1, data may be stored in one or more data sources (or data stores, generally physical data storage devices), which may be at the same or different physical sites and accessible via one or more networks. The model simulation layer 180 may be configured to model projects. As such, a particular project may be stored where stored project information may include inputs, models, results and cases. Thus, upon completion of a modeling session, a user may store a project. At a later time, the project can be accessed and restored using the model simulation layer 180, which can recreate instances of the relevant domain objects.
[0036] In the example of FIG. 1, the geologic environment 150 may include layers (e.g., stratification) that include a reservoir 151 and one or more other features such as the fault 153-1, the geobody 153-2, etc. As an example, the geologic environment 150 may be outfitted with any of a variety of sensors, detectors, actuators, etc. For example, equipment 152 may include communication circuitry to receive and to transmit information with respect to one or more networks 155. Such information may include information associated with downhole equipment 154, which may be equipment to acquire information, to assist with resource recovery, etc. Other equipment 156 may be located remote from a well site and include sensing, detecting, emitting or other circuitry. Such equipment may include storage and communication circuitry to store and to communicate data, instructions, etc. As an example, one or more satellites may be provided for purposes of communications, data acquisition, etc. For example, FIG. 1 shows a satellite in communication with the network 155 that may be configured for communications, noting that the satellite may additionally or instead include circuitry for imagery (e.g., spatial, spectral, temporal, radiometric, etc.).
[0037] FIG. 1 also shows the geologic environment 150 as optionally including equipment 157 and 158 associated with a well that includes a substantially horizontal portion that may intersect with one or more fractures 159. For example, consider a well in a shale formation that may include natural fractures, artificial fractures (e.g., hydraulic fractures) or a combination of natural and artificial fractures. As an example, a well may be drilled for a reservoir that is laterally extensive. In such an example, lateral variations in properties, stresses, etc. may exist where an assessment of such variations may assist with planning, operations, etc. to develop a laterally extensive reservoir (e.g., via fracturing, injecting, extracting, etc.). As an example, the equipment 157 and / or 158 may include components, a system, systems, etc. for fracturing, seismic sensing, analysis of seismic data, assessment of one or more fractures, etc.
[0038] As mentioned, the system 100 may be used to perform one or more workflows. A workflow may be a process that includes a number of worksteps. A workstep may operate on data, for example, to create new data, to update existing data, etc. As an example, a workstep may operate on one or more inputs and create one or more results, for example, based on one or more algorithms. As an example, a system may include a workflow editor for creation, editing, executing, etc. of a workflow. In such an example, the workflow editor may provide for selection of one or more pre-defined worksteps, one or more customized worksteps, etc. As an example, a workflow may be a workflow implementable in the PETREL® software, for example, that operates on seismic data, seismic attribute(s), etc. As an example, a workflow may be a process implementable in the OCEAN® framework. As an example, a workflow may include one or more worksteps that access a module such as a plug-in (e.g., external executable code, etc.).Drill Pipe Depth, Trip Seed, and RPM Sensor Using Computer Vision
[0039] The present disclosure includes a rotating control device (RCD) that may be used in / on an oil and gas rig. The RCD is a pressure-control device used during drilling for the purpose of making a seal around the drill string while the drill string rotates. This device is intended to contain hydrocarbons or other wellbore fluids and prevent their release to the atmosphere. The RCD is coupled to (e.g., existing) MPD equipment. Computer vision may allow determination of parameters that are dependent upon the rig, such as pipe speed and pipe rotations per minute (RPM). This may allow a user to have a smoother rig-up process, reduce dependency on the rig for operations, and / or unlock more modules in the MPD software (e.g., swab / surge). This may also make the MPD system more compatible with different rigs.
[0040] Currently, the MPD system relies upon depth-based data (e.g., hole depth, bit depth, trip in and out speeds) for the hydraulics engine. There is not currently an MPD-deployed sensor that measures / determines these values. This data is currently acquired from the rig.
[0041] FIGS. 2A and 2B illustrate tubular members 200 with uneven (e.g., rough) outer surfaces, according to an embodiment. The tubular members 200 may be or include a drill pipe, a drill string, a liner, a casing, or a combination thereof. The sensor may detect and track a random artifact, sign, or formation on the drill pipe. Then, the RCD may determine the speed of the tracked artifact both in X axis and Y axis based on the tracked artifact or sign. This helps to compute the rotary speed of the pipe (e.g., RPM) as well as the vertical speed of the pipe (e.g., block speed). With further transformation of this data, the RCD may determine bit depth, hole depth, block position, tripping-in speed, tripping-out speed, or a combination thereof.
[0042] FIG. 3 illustrates a block diagram of a sensor 300, according to an embodiment. In one embodiment, the sensor 300 may be mounted on the RCD. In other embodiments, the sensor 300 may instead be mounted anywhere with a clear line of sight to the tubular member (e.g., drill pipe) 200. The sensor 300 may provide a field of vision of the tubular member (e.g., drill pipe) 200 as it moves in and out through the RCD. The sensor 300 may include a zone-rated camera 310, ultrasonic distance sensors (US. D.S.) 320A, 320B, and a processing unit 330. The camera 310 may capture images or videos at a specific frame rate. The processing unit 330 may then identify one or more artifacts in the images and track their movement over several frames. Based on the tracking, the processing unit 330 may determine the movement and time.
[0043] FIG. 4 illustrates images captured at different times that show a tracked area 400 in two different locations (e.g., due to movement of the tubular members 200), according to an embodiment. The rig parameters may then be determined based on these two raw values.
[0044] FIG. 5 illustrates a flowchart of a method 500 for performing a managed pressure drilling (MPD) operation, according to an embodiment. An illustrative order of the method 500 is provided below; however, one or more portions of the method 500 may be performed in a different order, simultaneously, repeated, or omitted. At least a portion of the method 500 may be performed with a computing system (described below). FIG. 6 illustrates a schematic side view of the MPD operation being performed, according to an embodiment.
[0045] The method 500 may include positioning a rotating control device (RCD) 610 around a drill string 200, as at 505. The RCD 610 may be positioned above a blow-out preventor (BOP) 620. The RCD 610 is configured to form a seal with the drill string 200 while the drill string 200 moves (e.g., vertically or rotates).
[0046] The method 500 may also include positioning a sensor 300 in a location where the sensor 300 is able to capture images of the drill string 200, as at 510. The sensor 300 is shown in two locations in FIG. 6: (1) mounted to the RCD 610 and (2) mounted on the rig's sub-structure. Although not shown, the sensor 300 may also or instead be mounted on / to the rig floor, the derrick, the doghouse, or the BOP 620. The prerequisite of the mounting location would be to be able to capture an unobstructed image of the drill string 200. As mentioned above, the sensor 300 may include the camera 310. The camera 310 may be configured to capture the images of the drill string 200 as the drill string 200 moves in and / or out through the RCD 610. The sensor 300 may also include one or more (e.g., first and second) distance sensors 320A, 320B positioned on opposite sides of the camera 310. The first and second distance sensors 320A, 320B may be or include ultrasonic distance sensors that are configured to measure first and second distances from the drill string 200. The sensor 300 may also include a processing unit 330 that is configured to process the images and the first and second distances.
[0047] The method 500 may also include tripping the drill string 200, the sensor 300, and / or the RCD 610 into the wellbore, as at 515. In an example, this may include tripping the drill string 200 into the wellbore while the sensor 300 and the RCD 610 remain above the wellbore (e.g., at the surface). Tripping in may include generating and / or transmitting a signal that instructs or causes the tripping-in to occur.
[0048] The method 500 may also include identifying an area 400 on the drill string 200 using the sensor 300, as at 520. The area 400 may be or include a visual anomaly. For example, the visual anomaly may be or include a recess, a protrusion, and / or a color variation. The area 400 may be identified using the processing unit 330 in the sensor 300 (i.e., the identification may occur downhole).
[0049] The method 500 may also include tracking the area 400 on the drill string 200 using the sensor 300, as at 525. Tracking the area 400 may include determining an amount and / or a direction of movement over time. The area 400 may be tracked using the processing unit 330 in the sensor 300 (i.e., the tracking may occur downhole).
[0050] The method 500 may also include determining one or more drilling parameters based upon the movement over time, as at 530. The movement may be along an X-axis and / or Y-axis. The one or more parameters may be or include a number of rotations per minute (RPM) of the drill string 200, a block speed of the drill string 200, a depth of a drill bit, a depth of the wellbore, a tripping-in speed, a tripping-out speed, or a combination thereof.
[0051] The method 500 may also include displaying the movement over the time and the one or more parameters, as at 535.
[0052] The method 500 may also include performing an action in response to the one or more parameters, as at 540. The action may be or include generating and / or transmitting a signal (e.g., using a computing system) that instructs or causes a physical action to occur at a wellsite. The wellsite action may also or instead include performing the physical action at the wellsite. The physical action may include reducing a back pressure in the wellbore while drilling in response to the number of RPM increasing. In another example, the action may include increasing the back pressure in the wellbore while drilling in response to the number of RPM decreasing. In another example, the action may include determining the back pressure in the wellbore in response to a change in the depth of the bit and / or the depth of the wellbore. The back pressure may be determined based upon a hydraulic simulation profile. In another example, the action may include reducing the back pressure in the wellbore in response to an increase in the block speed while tripping into the wellbore. In another example, the action may include increasing the back pressure in the wellbore in response to a decrease in the block speed while tripping into the wellbore. In another example, the action may include increasing the back pressure in the wellbore in response to the increase in the block speed while tripping out of the wellbore. In another example, the action may include decreasing the back pressure in the wellbore in response to the decrease in the block speed while tripping out of the wellbore.Exemplary Computing System
[0053] In some embodiments, the methods of the present disclosure may be executed by a computing system. FIG. 7 illustrates an example of such a computing system 700, in accordance with some embodiments. The computing system 700 may include a computer or computer system 701A, which may be an individual computer system 701A or an arrangement of distributed computer systems. The computer system 701A includes one or more analysis modules 702 that are configured to perform various tasks according to some embodiments, such as one or more methods disclosed herein. To perform these various tasks, the analysis module 702 executes independently, or in coordination with, one or more processors 704, which is (or are) connected to one or more storage media 706. The processor(s) 704 is (or are) also connected to a network interface 707 to allow the computer system 701A to communicate over a data network 709 with one or more additional computer systems and / or computing systems, such as 701B, 701C, and / or 701D (note that computer systems 701B, 701C and / or 701D may or may not share the same architecture as computer system 701A, and may be located in different physical locations, e.g., computer systems 701A and 701B may be located in a processing facility, while in communication with one or more computer systems such as 701C and / or 701D that are located in one or more data centers, and / or located in varying countries on different continents).
[0054] A processor may include a microprocessor, microcontroller, processor module or subsystem, programmable integrated circuit, programmable gate array, or another control or computing device.
[0055] The storage media 706 may be implemented as one or more computer-readable or machine-readable storage media. Note that while in the example embodiment of FIG. 7 storage media 706 is depicted as within computer system 701A, in some embodiments, storage media 706 may be distributed within and / or across multiple internal and / or external enclosures of computing system 701A and / or additional computing systems. Storage media 706 may include one or more different forms of memory including semiconductor memory devices such as dynamic or static random access memories (DRAMs or SRAMs), erasable and programmable read-only memories (EPROMs), electrically erasable and programmable read-only memories (EEPROMs) and flash memories, magnetic disks such as fixed, floppy and removable disks, other magnetic media including tape, optical media such as compact disks (CDs) or digital video disks (DVDs), BLURAY® disks, or other types of optical storage, or other types of storage devices. Note that the instructions discussed above may be provided on one computer-readable or machine-readable storage medium, or may be provided on multiple computer-readable or machine-readable storage media distributed in a large system having possibly plural nodes. Such computer-readable or machine-readable storage medium or media is (are) considered to be part of an article (or article of manufacture). An article or article of manufacture may refer to any manufactured single component or multiple components. The storage medium or media may be located either in the machine running the machine-readable instructions, or located at a remote site from which machine-readable instructions may be downloaded over a network for execution.
[0056] In some embodiments, computing system 700 contains one or more method execution module(s) 708. In the example of computing system 700, computer system 701A includes the method execution module 708. In some embodiments, a single method execution module may be used to perform some aspects of one or more embodiments of the methods disclosed herein. In other embodiments, a plurality of method execution modules may be used to perform some aspects of methods herein.
[0057] It should be appreciated that computing system 700 is merely one example of a computing system, and that computing system 700 may have more or fewer components than shown, may combine additional components not depicted in the example embodiment of FIG. 7, and / or computing system 700 may have a different configuration or arrangement of the components depicted in FIG. 7. The various components shown in FIG. 7 may be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and / or application specific integrated circuits.
[0058] Further, the steps in the processing methods described herein may be implemented by running one or more functional modules in information processing apparatus such as general purpose processors or application specific chips, such as ASICs, FPGAs, PLDs, or other appropriate devices. These modules, combinations of these modules, and / or their combination with general hardware are included within the scope of the present disclosure.
[0059] Computational interpretations, models, and / or other interpretation aids may be refined in an iterative fashion; this concept is applicable to the methods discussed herein. This may include use of feedback loops executed on an algorithmic basis, such as at a computing device (e.g., computing system 700, FIG. 7), and / or through manual control by a user who may make determinations regarding whether a given step, action, template, model, or set of curves has become sufficiently accurate for the evaluation of the subsurface three-dimensional geologic formation under consideration.
[0060] The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or limiting to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. Moreover, the order in which the elements of the methods described herein are illustrated and described may be re-arranged, and / or two or more elements may occur simultaneously. The embodiments were chosen and described in order to best explain the principles of the disclosure and its practical applications, to thereby enable others skilled in the art to best utilize the disclosed embodiments and various embodiments with various modifications as are suited to the particular use contemplated.
Claims
1. A method for performing a managed pressure drilling (MPD) operation, the method comprising:positioning a sensor proximate to a drill string;identifying an area on the drill string using the sensor;tracking the area on the drill string using the sensor, wherein tracking the area comprises determining an amount and a direction of movement over time; anddetermining one or more drilling parameters based upon the movement over time.
2. The method of claim 1, wherein the sensor comprises a camera configured to capture images of the drill string.
3. The method of claim 2, further comprising positioning a rotating control device (RCD) around the drill string, wherein the RCD is configured to form a seal with the drill string while the drill string rotates, and wherein the camera is configured to capture the images as the drill string moves in and out through the RCD.
4. The method of claim 3, wherein the sensor is positioned on the RCD.
5. The method of claim 1, further comprising tripping the drill string into a wellbore, wherein the area is identified while the drill string is being tripped into the wellbore.
6. The method of claim 1, wherein the area comprises a visual anomaly.
7. The method of claim 6, wherein the visual anomaly comprises a recess, a protrusion, and / or a color variation.
8. The method of claim 1, wherein the movement is along an X-axis and / or Y-axis, and wherein the one or more parameters comprise a number of rotations per minute (RPM) of the drill string, a block speed of the drill string, a depth of a drill bit, a depth of a wellbore, a tripping-in speed, a tripping-out speed, or a combination thereof.
9. The method of claim 1, further comprising displaying the movement over the time and the one or more parameters.
10. The method of claim 1, further comprising varying a back pressure in a wellbore in response to the one or more parameters.
11. A computing system, comprising:one or more processors; anda memory system comprising one or more non-transitory computer-readable media storing instructions that, when executed by at least one of the one or more processors, cause the computing system to perform operations, the operations comprising:positioning a rotating control device (RCD) around a drill string, wherein the RCD is configured to form a seal with the drill string while the drill string rotates;positioning a sensor in a location where the sensor is able to capture images of the drill string, wherein the sensor is positioned on the RCD or a rig structure, wherein the sensor comprises a camera configured to capture the images of the drill string;identifying an area on the drill string using the sensor, wherein the area comprises a visual anomaly, and wherein the visual anomaly comprises a recess, a protrusion, and / or a color variation;tracking the area on the drill string using the sensor, wherein tracking the area comprises determining an amount and a direction of movement over time; anddetermining one or more drilling parameters based upon the movement over time, wherein the movement is along an X-axis and / or Y-axis, and wherein the one or more parameters comprise a number of rotations per minute (RPM) of the drill string, a block speed of the drill string, a depth of a drill bit, a depth of a wellbore, a tripping-in speed, a tripping-out speed, or a combination thereof.
12. The computing system of claim 11, wherein the sensor also comprises first and second distance sensors positioned on opposite sides of the camera, wherein the first and second distance sensors comprise ultrasonic distance sensors that are configured to measure first and second distances from drill string, and wherein the sensor also comprises a processing unit that is configured to process the images and the first and second distances.
13. The computing system of claim 11, wherein the operations further comprise displaying the movement over the time and the one or more parameters.
14. The computing system of claim 11, wherein the operations further comprise performing an action in response to the one or more parameters.
15. The computing system of claim 14, wherein the action comprises generating and / or transmitting a signal that recommends, instructs, or causes a physical action to occur, and wherein the physical action comprises varying a back pressure in the wellbore.
16. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a computing system, cause the computing system to perform operations, the operations comprising:positioning a rotating control device (RCD) around a drill string, wherein the RCD is positioned above a blow-out preventer (BOP), and wherein the RCD is configured to form a seal with the drill string while the drill string rotates;positioning a sensor in a location where the sensor is able to capture images of the drill string, wherein the sensor is positioned on the RCD, a rig floor, a rig substructure, or a derrick, wherein the sensor comprises a camera configured to capture the images of the drill string, wherein the camera is configured to capture the images as the drill string moves in and out through the RCD, wherein the sensor also comprises first and second distance sensors positioned on opposite sides of the camera, wherein the first and second distance sensors comprise ultrasonic distance sensors that are configured to measure first and second distances from drill string, and wherein the sensor also comprises a processing unit that is configured to process the images and the first and second distances;tripping the drill string into the wellbore;identifying an area on the drill string using the sensor while the drill string is being tripped into the wellbore, wherein the area comprises a visual anomaly, and wherein the visual anomaly comprises a recess, a protrusion, and / or a color variation;tracking the area on the drill string using the sensor, wherein tracking the area comprises determining an amount and a direction of movement over time;determining one or more drilling parameters based upon the movement over time, wherein the movement is along an X-axis and / or Y-axis, and wherein the one or more parameters comprise a number of rotations per minute (RPM) of the drill string, a block speed of the drill string, a depth of a drill bit, a depth of the wellbore, and a tripping-in speed or a tripping-out speed;displaying the movement over the time and the one or more parameters; andperforming an action in response to the one or more parameters.
17. The non-transitory computer-readable medium of claim 16, wherein the action comprises:decreasing a back pressure in the wellbore while drilling in response to the number of RPM increasing; orincreasing the back pressure in the wellbore while drilling in response to the number of RPM decreasing.
18. The non-transitory computer-readable medium of claim 16, wherein the action comprises:decreasing a back pressure in the wellbore in response to an increase in the block speed while tripping into the wellbore; orincreasing the back pressure in the wellbore in response to a decrease in the block speed while tripping into the wellbore.
19. The non-transitory computer-readable medium of claim 16, wherein the action comprises:decreasing a back pressure in the wellbore in response to the decrease in the block speed while tripping out of the wellbore; orincreasing the back pressure in the wellbore in response to the increase in the block speed while tripping out of the wellbore.
20. The non-transitory computer-readable medium of claim 16, wherein the action comprises determining a back pressure in the wellbore in response to a change in the depth of the bit and / or the depth of the wellbore, and wherein the back pressure is determined based upon a hydraulic simulation profile.
