SYSTEMS AND METHODS FOR CONTROL OF WELLBORE CONVEYANCE

Description

BACKGROUND OF THE DISCLOSURE

Exploring, drilling, and completing hydrocarbon and other wells are generally complicated, time consuming and ultimately very expensive endeavors. As such, tremendous emphasis is often placed on well applications and monitoring that rely heavily on periodic intervention for sake of well management. For example, various wireline (WL), tractoring, coiled tubing (CT) and other types of interventions are often periodically introduced to the well throughout the life of the well. These interventions may be aimed at acquiring well condition information, directing a well cleanout, installation of downhole devices or a variety of other applications.

By way of example, WL or CT systems may operate based on lowering various components or downhole tools into a wellbore. The speed at which the WL or CT is advanced within the wellbore is critical for ensuring that failure limits of various components are not reached. Typically, the speed of conveyance of these systems is controlled by conveyance operations personnel monitoring surface speed and loading measurements, and progressing the system artificially slow (e.g., slower than can safely be operated) to ensure that equipment is not damaged. Thus, the speed of a conveyance system is controlled based on the intuition, knowledge, and experience of the operators with no real empirical rationale or guidance. Accordingly, it may be advantageous to identify safe limits for operational speeds and loads of conveyance systems, and to operate the conveyance systems at or near these limits to improve efficiency, safety, and operational costs.

SUMMARY

In some embodiments, a method of operating a conveyance system implemented in a wellbore includes receiving surface measurements including one or more of surface load measurements, surface speed measurements, or depth of tool measurements for the conveyance system. The method includes, with a failure model, generating a threshold including at least one of a maximum run-in-hole speed, a maximum pull-out-of-hole speed, a maximum load, a minimum load, or a maximum depth of tool for the conveyance system. The method further includes adjusting movement of the conveyance system based on identifying that the surface measurements surpass the threshold.

In some embodiments, a method of operating a conveyance system implemented in a wellbore includes receiving depth of tool measurements, and identifying an operational status of the conveyance system. The method includes, based on the depth of tool measurements and the operational status, generating, with a failure model, a surface load threshold associated with a load on the conveyance system. The method further includes receiving surface load measurements for the conveyance system, and adjusting a speed of the conveyance system to maintain the surface load measurements within the surface load threshold.

In some embodiments, a conveyance system includes a derrick, a conveyance line partially positioned within a wellbore and being conveyed from a drum, an injector head for conveying the conveyance line into and out of the wellbore, and a plurality of surface sensors. The system further includes at least one processor, memory in electronic communication with the at least one processor, and instructions stored in the memory, the instructions being executable by the at least one processor to receive surface measurements from the plurality of surface sensors, including one or more of surface load measurements, surface speed measurements, or depth of tool measurements for the conveyance system. The instructions are executable to, with a failure model, generate a threshold including at least one of a maximum run-in-hole speed, a maximum pull-out-of-hole speed, a maximum load, a minimum load, or a maximum depth of tool for the conveyance system. The instructions are further executable to adjust, automatically and without user input, a speed of the conveyance line based on identifying that the surface measurements surpass the threshold.

This summary is provided to introduce a selection of concepts that are further described in the detailed description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in limiting the scope of the claimed subject matter. Additional features and aspects of embodiments of the disclosure will be set forth herein, and in part will be obvious from the description, or may be learned by the practice of such embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and other features of the disclosure can be obtained, a more particular description will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. For better understanding, the like elements have been designated by like reference numbers throughout the various accompanying figures. While some of the drawings may be schematic or exaggerated representations of concepts, at least some of the drawings may be drawn to scale. Understanding that the drawings depict some example embodiments, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

FIG. 1 is an example of a conveyance system, according to at least one embodiment of the present disclosure;

FIG. 2-1 illustrates an example environment in which a conveyance control system is implemented, according to at least one embodiment of the present disclosure;

FIG. 2-2 illustrates an example implementation of a conveyance control system as described herein, according to at least one embodiment of the present disclosure;

FIG. 3-1 illustrates an example case for an example surface measurement expressed with uncertainty as well as an associated threshold expressed with uncertainty, according to at least one embodiment of the present disclosure;

FIG. 3-2 illustrates an example case for an example surface measurement expressed with uncertainty as well as an associated threshold expressed with uncertainty, according to at least one embodiment of the present disclosure;

FIG. 4 illustrates an example case of the conveyance control system implementing a downhole conveyance device to operate the conveyance system with a threshold, according to at least one embodiment of the present disclosure;

FIG. 5 is a flow diagram illustrating an example flow for a functionality of the conveyance control system for controlling an operation of the conveyance system as describe herein, according to at least one embodiment of the present disclosure;

FIG. 6 illustrates a flow diagram for a method or a series of acts for operating a conveyance system implemented in a wellbore as described herein, according to at least one embodiment of the present disclosure; and

FIG. 7 illustrates certain components that may be included within a computing system.

DETAILED DESCRIPTION

This disclosure generally relates to systems and methods for controlling the operation of a conveyance system. For example, conveyance systems may be deployed within a wellbore for implementing one or more downhole tools to perform an intervention or evaluation operation. These downhole tools may be conveyed into, moved within, and retrieved from the wellbore using a wireline, coiled tubing, drill pipes, etc. While it is desirable to run conveyance as fast as possible to reduce operational cost, safety must also be a top priority to avoid damage to conveyance equipment, for example, due to such anomalies as stuck pipe events.

Traditionally, conveyance is controlled manually with operators constantly monitoring surface measurements to ensure safety. The judgement and interpretation of sensor readings, as well as setting of the desired running speed at different depths is traditionally based on the level of experience and intuition of the operator. The present disclosure describes at least one embodiment of a conveyance control system that automates the control of the conveyance of equipment by controlling the speed of the conveyance efficiently and safely. The conveyance control system may perform one or more of process real-time sensor data, consult physics models of different fidelities, or determine thresholds such as one or more of maximum safe speeds, maximum loading, maximum depth, or other thresholds. One or more of these thresholds may then be utilized to inform the speed of conveyance of the equipment to, for example, automatically control the speed of conveyance efficiently and/or safely.

Additional details will now be provided regarding systems described herein in relation to illustrative figures portraying example implementations. For example, FIG. 1 shows one example of a conveyance system 100 for performing a conveyance operation within a wellbore 102. The conveyance system 100 includes a rig, mast, or derrick 101 used to support a conveyance line 103 (e.g., WL line or CT line) at a surface 106. The conveyance line 103 may be suspended, inserted into, or otherwise positioned within the wellbore 102. For instance, the conveyance line 103 may pass through a wellhead 108. The wellhead 108 may provide a structural, pressure, and/or fluid barrier between the wellbore and the surface 106. For instance, the wellhead 108 may contain wellbore fluids within the wellbore 102. In some embodiments, surface equipment of the conveyance system 100 includes an injector head for conveying the conveyance line 103 within the wellbore. For example, an injector head may include one or more (e.g., hydraulic) drives, chain assemblies, grip assemblies, or other components for providing a tractive effort for running and/or retrieving the conveyance line 103 into and/or from the wellbore 102.

The wellbore 102 may extend through a subsurface and may traverse various formations, layers, strata, or other subterranean features. The wellbore 102 may be a completed (e.g., fully drilled or fully formed) wellbore, or may be a wellbore at any intermediate stage of completion. The wellbore 102 is depicted as extending substantially straight or vertical into the ground, however, the wellbore 102 may be formed in accordance with any trajectory. For example, the wellbore 102 can include one or more bends, doglegs, inclinations, etc., such that the wellbore 102 may exhibit any level of deviation or tortuosity, including in 3-dimensional space.

The conveyance line 103 is connected to a downhole tool 104 for supporting or positioning the downhole tool 104 in the wellbore 102. The downhole tool 104 may be a logging tool, a completion tool, a production tool, or any other tool used for performing any downhole operation, such as for imaging or otherwise measuring characteristics of the wellbore 102 or subsurface, performing a perforation, setting a plug, retrieving lost or stuck equipment, isolating wellbore sections, testing wellbore integrity, sampling fluids, wellbore cleaning, wellbore repair, opening or closing valves, stimulation (e.g., fracking), circulating fluid, downhole communication, or any other tool for performing any other downhole function.

The conveyance line 103 is contained on a spool, reel, or drum 105 which is typically mounted to a truck, trailer, skid, or other equipment. The conveyance line 103 and the downhole tool 104 are advanced into and out of the wellbore 102 from the drum 105 through a series of pulleys, sheaves, motors, and drives. For example, the derrick 101 may include one or more sheaves 107 for directing the conveyance line 103 from the drum into the wellbore 102. The derrick 101 may represent an integration of the conveyance system 100 with an existing drill rig (e.g., used for forming the wellbore) or may be implemented as a separate derrick, mast, rig or other surface equipment constructed for administering the conveyance line 103 into the wellbore.

The conveyance line 103, the downhole tool 104, and other components of the conveyance system 100 may be subject to various forces, loads, and other dynamics. These various components have failure limits and other operational thresholds at which the components may break, yield, or otherwise fail. In many cases, the speed at which the conveyance line 103 is moved within the wellbore 102 may affect the dynamics applied to one or more components of the conveyance system 100. Accordingly, controlling the speed of conveyance of the conveyance line 103 may limit or prevent damage to one or more components. For instance, the conveyance system 100 may include one or more surface sensors for measuring, for example, a surface speed and a surface loading of the conveyance line 103.

The conveyance system 100 may include or may be associated with a client device 112 with a conveyance control system 120 implemented thereon (e.g., or with a client application implemented thereon for accessing the conveyance control system 120 as described herein). The conveyance control system 120 may facilitate identifying working thresholds for conveying the conveyance line 103 within the wellbore 102, as well as operating the conveyance control system 120 within those thresholds.

FIG. 2-1 illustrates an example environment 200 in which a conveyance control system 120 is implemented in accordance with one or more embodiments described herein. As shown in FIG. 2-1, the environment 200 includes a server device 114. The server device 114 may include one or more computing devices (e.g., including processing units, data storage, etc.) organized in an architecture with various network interfaces for connecting to and providing data management and distribution across one or more client systems. As shown in FIG. 2-1, the server device 114 may be connected to and may communicate with (either directly or indirectly) a client device 112 through a network 116. The network 116 may include one or multiple networks and may use one or more communication platforms and/or technologies suitable for transmitting data. The network 116 may refer to any data link that enables transport of electronic data between devices of the environment 200. The network 116 may refer to a hardwired network, a wireless network, or a combination of a hardwired network and a wireless network. In one or more embodiments, the network 116 includes the internet. The network 116 may be configured to facilitate communication between the various computing devices via well-site information transfer standard markup language (WITSML) or similar protocol, or any other protocol or form of communication.

The client device 112 may be representative of one or multiple client devices and may refer to various types of computing devices. For example, the client device 112 may include a mobile device such as a mobile telephone, a smartphone, a personal digital assistant (PDA), a tablet, a laptop, or any other portable device. Additionally, or alternatively, the client device 112 may include one or more non-mobile devices such as a desktop computer, server device, surface or downhole processor or computer (e.g., associated with a sensor, system, or function of the downhole system), or other non-portable devices. In one or more implementations, the client device 112 includes graphical user interfaces (GUI) thereon (e.g., a screen of a mobile device). In addition, or as an alternative, one or more of the client device 112 may be communicatively coupled (e.g., wired or wirelessly) to a display device having a graphical user interface thereon for providing a display of system content. The server device 114 may similarly refer to various types of computing devices. Each of the devices of the environment 200 may include features and/or functionalities described below in connection with FIG. 7.

As shown in FIG. 2-1, the environment 200 may include a conveyance control system 120 implemented on the server device 114. While shown on the server device 114, the conveyance control system 120 may be implemented wholly or in part on the client device 112, across the server device 114 and the client device 112, or on or across one or more additional devices, such that different portions or components of the conveyance control system 120 are implemented on different computing devices in the environment 200. The client device 112 may include a client application 118. The client application 118 may include an application or interface for interacting with and/or receiving the features of the conveyance control system 120 as described herein. In some embodiments, one or more of the functionalities or features of the conveyance control system 120 may be carried out or performed on or by the client application 118. In this way, the environment 200 may be a cloud computing environment, and the conveyance control system 120 may be implemented across one or more devices of the cloud computing environment in order to leverage the processing capabilities, memory capabilities, connectivity, speed, etc., that such cloud computing environments offer in order to facilitate the features and functionalities described herein.

FIG. 2-2 illustrates an example implementation of the conveyance control system 120 as described herein, according to at least one embodiment of the present disclosure. The conveyance control system 120 may include a data manager 122, a threshold engine 124 implementing one or more failure models 128, and a failure manager 126. The conveyance control system 120 may also include a data storage 130 having surface measurements 132 and thresholds 134 stored thereon. While one or more embodiments described herein describe features and functionalities performed by specific components 122–126 of the conveyance control system 120, it will be appreciated that specific features described in connection with one component of the conveyance control system 120 may, in some examples, be performed by one or more of the other components of the conveyance control system 120.

By way of example, one or more of the data receiving, gathering, or storing features of the data manager 122 may be delegated to other components of the conveyance control system 120. As another example, while thresholds may be generated by the threshold engine 124, in some instances, some or all of these features may be performed by the failure manager 126 (or other component of the conveyance control system 120). Indeed, it will be appreciated that some or all of the specific components may be combined into other components and specific functions may be performed by one or across multiple components 122–126 of the conveyance control system 120.

Additionally, while FIG. 1, for example, depicts the conveyance control system 120 implemented on a client device 112 of the downhole system, it should be understood that some or all of the features and functionalities of the conveyance control system 120 may be implemented on or across multiple client devices 112 and/or server devices 114. For example, data may be input and/or received by the data manager 122 on a (e.g., local) client device, and the thresholds may be generated and/or monitored on one or more of a remote, server, or cloud device. Indeed, it will be appreciated that some or all of the specific components 122–126 may be implemented on or across multiple client devices 112 and/or server devices 114, including individual functions of a specific component being performed across multiple devices.

As mentioned above, the conveyance control system 120 includes a data manager 122. The data manager 122 may receive a variety of types of data associated with the conveyance system and may store the data to the data storage 130. The data manager 122 may receive the data from a variety of sources, such as from sensors, surveying tools, downhole tools, other (e.g., client) devices, libraries, databases, user input, etc.

In some embodiments, the data manager 122 receives surface measurements 132 from one or more surface sensors. The surface measurements 132 may include measurements associated with the conveyance line of the conveyance system in the wellbore. For example, the conveyance system 100 may include a speed sensor for measuring a speed at which the line is advanced into or out of the wellbore. The speed sensor may be a surface speed sensor for measuring the speed of the line as observed at or near the surface. In this way, the surface measurements may include surface speed measurements. Such surface speed sensors may include an optical sensor, a rotational rate sensor on one or more pulleys or the drum, any other surface speed sensor, and combinations thereof. In another example, the conveyance system 100 may include a load sensor (or several sensors), for example, for measuring tensile and/or compressive forces exerted on or experienced by the line. The load sensor may measure a weight of the line as observed at the surface, corresponding to the total cumulative weight of all of the line suspended from the rig, including friction, drag, and other dynamics that may act on the line to either contribute to or offset the observed (e.g., some of the) surface weight. The load sensor may be a surface sensor for measuring the loads on the line as observed at or near the surface. In this way, the surface measurements may include surface load measurements. In some embodiments, the conveyance system includes a depth sensor for measuring or tracking a depth of tool of the conveyance system. The depth of tool may correspond to the depth at which a downhole tool is positioned in the wellbore, or otherwise the furthest extent of the line of the conveyance system.

In some embodiments, the data manager 122 receives the surface measurements 132 in real time. For example, the data manager 122 may observe, store to the data storage 130, and update the surface measurements 132 as they are received. This real-time functionality by the data manager 122 may facilitate the real time and/or active monitoring and controlling of the conveyance system as described herein.

In some embodiments, the data manager 122 may identify an operation type of the conveyance system. For example, as described herein, conveyance systems may be implemented with respect to WL applications, CT applications, and other wellbore interventions or evaluations. The data manager 122 may identify and may indicate which type of application the conveyance system is implementing. In some embodiments, the data manager 122 identifies an operational state of the conveyance system. For example, the data manager 122 may identify whether the line is being fed into (e.g., tripped in) the wellbore or being retrieved from (e.g., tripped out of) the wellbore. Identifying the operational stay may facilitate determining the dynamics affecting one or more sections of the line.

In some embodiments, the data manager 122 receives equipment ratings, properties, thresholds, limits, or other characteristics of the various components or equipment of the conveyance system. In some embodiments, the data manager 122 identifies limits for equipment associated with a WL application. For example, the data manager 122 may identify a cable safe working load. The cable safe working load may be a maximum tension that the line can sustain, such as a cable breaking strength. In some cases, the cable safe working load may be a percentage (e.g., 50%) of the cable breaking strength so as to implement a factor of safety. In some embodiments, the data manager 122 identifies a minimum tension for the line. For example, a line in a WL application may have a desirable or recommended minimum tension, below which the line may have a tendency or risk of becoming slack, which can lead to the cable becoming snagged, a downhole tool becoming stuck, etc. Thus, the data manager may identify this minimum tension which the entirety of the line should maintain.

In some embodiments, the data manager 122 identifies limits for equipment associated with a CT application. For example, the data manager 122 may identify a tubing load limit. The tubing load limit may be a maximum loading or tension above which the tubing may collapse or burst. The tubing load limit may be dependent on or associated with a fluid pressure inside and/or outside the CT. The data manager 122 may identify and/or indicate this relationship. In some embodiments, the data manager 122 identifies a maximum compressive loading for a CT line. For example, the maximum compressive loading may be a critical compressive load, above which the tubing may buckle, kink, or lock up. This compressive load may be dependent on or associated with the bending rigidity of the tubing as well as the size or the gap or annulus between the tubing and the casing or wellbore.

In some embodiments, the data manager 122 identifies limits or ratings for other equipment. For example, various components or connections between components may have a weak point rating. The weak point rating may identify a weak point in a component or tool and may identify the amount of loading the component can endure before breaking or failing. In another example, surface equipment such as the drum, the truck, and the rig may have specific operational safety limits associated with loading, speed, etc. The pulleys, motors, sheaves, etc. of the conveyance system may have operational limits within which they are designated to safely operate. The data manager 122 may identify any limit or rating for any of the equipment included in the conveyance system.

The various sensor measurements, limits, ratings, or other operational specifications that the data manager 122 receives, measures, or otherwise identifies in some cases may be designated as a specific value or range of values. In some cases, however, one or more of these metrics are characterized by a certain level of uncertainty. For example, the surface measurements may be measured or interpreted as a given value but may correspond with a certain level of error or uncertainty, for example, due to the limitations in the measurement equipment, signal noise, or other errors. As another example, the operational ratings or limits may be indicated as a given value with an associated level of uncertainty, such as from measurement error in determining the limits, manufacturing tolerances and variance, or other imprecisions. The data manager 122 may identify and indicate the uncertainty associated with any of the values, measurements or metrics it receives. For instance, the data manager 122 may identify a probability distribution or a probability density function for expressing the uncertainty associated with a given metric. As described herein, this uncertainty may be utilized to identify one or more failure thresholds and/or to determine when one or more thresholds are surpassed.

In some embodiments, the data manager 122 receives user input. The data manager 122 may receive the user input, for example, via any of the client devices 112 and/or server devices 114. Any of the data described herein may be input or augmented via the user input. For example, in some instances, some or all of the operational limits or ratings for one or more components of the conveyance system may be received by the data manager 122 as user input. The user input may be received in association with one or more functions or features of the conveyance control system 120, such as part of adjusting and/or controlling the operation of the conveyance system, or any other feature described herein.

As mentioned above, the conveyance control system 120 includes a threshold engine 124. The threshold engine may determine one or more thresholds 134 for informing or directing the operation of the conveyance system. For example, the thresholds 134 may ensure that the conveyance system is operated in a quick and efficient manner, while also ensuring the safety of the equipment, operation, and personnel.

The threshold engine 124 may implement one or more failure models 128 for determining the thresholds 134. The failure models 128 may model or represent physical attributes, properties, behavior, dynamics, etc. of the various components of the conveyance system (e.g., the line, downhole tool, and other components, hereinafter “equipment”). For instance, the failure models 128 may implement physics models, downhole models, and/or other analytical models or simulations for representing the behavior of the equipment and the response of the equipment to the downhole environment, movement within the wellbore, downhole operations, etc. The failure models may include tension models and/or weight models for WL and/or CT applications. The failure models 128 may incorporate the trajectory or geometry of the wellbore as well as subsurface features such as different formations encountered downhole. The failure models 128 may incorporate finite element analysis or other analytical techniques.

In a particular example, the failure models 128 may determine frictional forces acting on the equipment as well as the effects of these friction forces. In another example, the failure models 128 may determine fluid drag experienced by the equipment and its effects. The failure models 128 may account for fluid flowing within and/or outside of a tubing, as well as the size of the gap or annulus between a tubing and the wellbore.

The threshold engine 124 may implement the failure models 128 with respect to one or more inferred parameters. For example, parameters such as friction coefficients, fluid properties, temperature, pressure, material properties, etc. may be parameters that are inferred and/or updated. For example, these values may be inferred based on various measurement values from surface and/or downhole sensors. These parameters may be inferred based on information from surveying operations or from measurements from other wellbores. These inferred values may change and/or may be updated one or more times as new information becomes available or as new inferences are made with higher confidence.

In some embodiments, the threshold engine 124 implements several failure models 128 that each characterize, simulate, or are associated with a specific surface measurement, equipment dynamic (e.g., tension, loading), or failure mode. For instance, the threshold engine 124 may run one or more of these several failure models 128 in parallel. In some embodiments, the threshold engine 124 implements one failure model 128 that incorporates several or all characteristics of the conveyance system.

In some embodiments, the failure models 128 determine the dynamics experienced by the equipment at one or more (or all) locations of the equipment (e.g., at any measurement depth). For instance, the failure models 128 may identify the tension experienced by the line. In some cases, the failure models 128 identify the compression of the line at various locations. The failure models 128 may determine stresses and/or loading on any portion of the equipment, such as stresses and/or loading at the connections between tools or other components. In this way, the failure models 128 may determine the physical response of the equipment to the operation(s) the conveyance system is performing. For example, the failure models 128 may incorporate a depth of tool corresponding to a depth or a length of the line that is extended into the wellbore. The failure models 128 may incorporate a movement of the equipment, such as a speed at which the equipment is being fed into or pulled from the wellbore.

Based on the determined dynamics (e.g., tension and/or compression) on the equipment, the threshold engine 124 may identify one or more failure points. For example, based on the simulation and/or analysis of the equipment and its behavior, the failure models 128 may facilitate determining one or more points in which the equipment may fail or otherwise reach or exceed an operational limit. For instance, the threshold engine 124 may identify one or more failure points at which the line may reach or exceed a cable safe working load. In another example, one or more failure points may correspond to a point where a weak point rating may be reached or exceeded for a given piece of equipment or connection between pieces of equipment and/or the wire or CT. In another example, the threshold engine 124 may determine a failure point for when the loading on the tubing for a CT application may reach or exceed a tubing load limit. In a further example, one or more failure points may correspond with a point in the line having a reduced tension such that the line may become slacked or kinked. In yet another example, the threshold engine 124 may determine a location at which the line may begin to buckle or lock up and may indicate this as a failure point. In this way, the failure models 128 may facilitate determining various failure points for relevant operational limits or ratings of the equipment as described herein.

In some embodiments, the threshold engine 124 determines the thresholds 134 based on the failure points. For example, the threshold engine 124 may translate the failure points to a corresponding surface measurement (e.g., surface loading of the line, surface speed of the line) of a given value at which the failure point may occur. For instance, the threshold engine 124 may determine that the tension in the line will surpass the cable safe working load or the tubing load limit at one or more downhole locations when the surface load of the line reaches a given value. Accordingly, the threshold engine 124 may establish that given value as a maximum surface load threshold for the surface load. In another example, the threshold engine 124 may identify that the tension in the line may drop below a minimum value at one or more downhole locations, indicating that the line may become slack, when the surface load is at or below a specific surface load. Accordingly, the threshold engine 124 may identify that specific surface load as a minimum surface load threshold for the surface load. In another example, the threshold engine 124 may determine that the line (e.g., tubing) at a given location may begin to buckle from excess internal compression when a certain weight of the (e.g., uphole) tubing acts on the line at that given location. Accordingly, the threshold engine 124 may identify a certain minimum surface weight to be maintained at the surface to ensure that the tubing doesn’t experience too much uphole weight at that location and may establish this minimum surface weight as a minimum surface weight threshold for the surface load.

In some embodiments, the threshold engine 124 determines thresholds 134 corresponding to a speed for advancing the line into or out of the wellbore. For example, the threshold engine 124 may determine one or more speed thresholds based on an associated thresholding for the loading of the line (or other components). For instance, the surface loading may be related to and/or influenced by the speed at which the conveyance system is operated. Accordingly, the threshold engine 124 may determine one or more thresholds 134 for conveying the line at a speed that will not cause the conveyance system to surpass the thresholds 134 for loading. As an illustrative example, pulling the line out of the wellbore at a faster speed may tend to subject the equipment to larger loads or larger tensions than when done so at slower speeds, which may reach or exceed safe working loads for the line, equipment, and/or connections. Inserting the line into the wellbore at a faster speed may tend to subject the equipment to lower tensile loads or may even temporarily place the line in a state of compression, which may cause slackline, buckling, kinking, or other low-tensile or compression damage. Accordingly, the threshold engine 124 may determine one or more thresholds related to a speed of conveyance of the line in order to ensure that the equipment is operated within any associated operational limits.

In some embodiments, a given implementation or operation of the conveyance system may be characterized by several failure points. For instance, the tension in the line may be determined to exceed the tubing load limit at several (e.g., different) locations of the line. In another example, the tension in the line may be determined to exceed the cable safe working load, and a weak point rating may also be determined to be surpassed for one or more components or the connection between components. In such instances of multiple failure points, the threshold engine 124 may determine an associated threshold 134 for the surface measurements based on determining which failure point is reached first, which limit is surpassed to a greater degree, which operational rating is more critical, or based on any other criteria. For instance, the threshold engine may determine a threshold for a maximum surface loading based on failure points associated with a cable safe working load and a weak point rating both being reached, and may determine the threshold to be the lowest associated surface loading of either failure point to ensure that neither failure point occurs. In this way, the threshold engine 124 may incorporate many failure points, and may determine associated thresholds for the surface measurements based on each of the failure points and their associated surface measurements to ensure compliance with all operational limits of the equipment.

In this way, the threshold engine 124 may determine failure points or instances at which the equipment may fail (or otherwise surpass an operational limit) and may determine associated thresholds for the surface measurements corresponding with those failure points.

The threshold engine 124 may determine a variety of different thresholds for a variety of different measurements and/or parameters relevant to the safe and efficient operation of the conveyance system. In some embodiments, the threshold engine 124 determines a maximum safe pull threshold. The maximum safe pull threshold may be a maximum surface tension for operating the conveyance system. For instance, the associated surface tension measurement of the maximum safe pull threshold may be a surface tension above which one or more failure points have been identified for the equipment, such as equipment exceeding a cable safe working load, weak point rating, tubing load limit, etc. In some embodiments, the threshold engine 124 determines a maximum pull-out-of-hole (POOH) speed threshold. The maximum POOH speed threshold may be associated with the maximum safe pull threshold. For example, the maximum POOH speed threshold may be a maximum speed with which the conveyance system can be operated without causing the surface load to exceed the maximum safe pull threshold, so as to prevent reaching any cable safe working load, weak point rating, or tubing load limit values.

In some embodiments, the threshold engine 124 determines a minimum surface load threshold. The minimum surface load threshold may be a minimum surface load or weight that must be maintained at the rig of the conveyance system. For instance, the associated surface tension measurement of the minimum surface load threshold may be a surface tension below which a cable may begin to slack, or a tubing may begin to buckle or otherwise fail. In some embodiments, the threshold engine 124 determines a maximum run-in-hole (RIH) speed threshold. The maximum RIH speed threshold may be associated with the minimum surface load threshold. For instance, the maximum RIH speed threshold may be a speed with which the conveyance system can be operated without causing the surface load to drop below the minimum surface load threshold, so as to prevent the line from becoming slack (WL) or from buckling (CT).

In some embodiments, the threshold engine 124 determines a maximum depth threshold. For example, as described herein, the threshold engine may determine the (e.g., tension and compression) loading on the equipment of the conveyance system, and associated failure points. In some embodiments, in addition to determining the threshold levels of surface loading and surface speed associated with the failure points, the threshold engine 124 may determine a maximum depth to which the equipment may be run. For example, the maximum depth threshold may correspond to a depth at which the equipment can no longer be safely pulled out of the wellbore without reaching one or more operational limits or failure points (e.g., cable safe working load, weak point rating, tubing loading limit) and/or without exceeding one or more associated thresholds (e.g., maximum safe pull threshold).

The maximum safe depth threshold may facilitate a safe operation of the conveyance system. For example, in some cases, it may be possible to reach, or even surpass the maximum safe depth threshold without violating one or more other thresholds, such as without exceeding a minimum surface load threshold and/or a maximum RIH speed threshold. However, based on these two metrics alone, it may not be apparent that retrieving the equipment from the wellbore at these depths may result in exceeding other corresponding thresholds, such as a maximum safe pull threshold. The maximum safe depth threshold may inform the operation of the conveyance system such that equipment is not extended to depths beyond that which it can safely be retrieved. In some embodiments, the maximum safe depth threshold may facilitate informing a planning of the wellbore. For example, knowing the maximum depth to which the equipment can be deployed, and comparing this to the total and/or planned depth of the wellbore can inform whether and to what extent a conveyance operation can be performed. Additionally, the conveyance operation may be planned for based on the determined maximum safe depth threshold, such as by selecting and/or implementing equipment that may facilitate a deeper maximum safe depth that may span more (or all of) the wellbore.

In some embodiments, the threshold engine 124 determines a level of uncertainty or error with the thresholds 134. For example, the physics models, tension models, etc. upon which the failure points and associated thresholds 134 are determined may include approximations, estimates and other analytical values that may be associated with a certain level of uncertainty. Additionally, as described above, the operational limits of the various components may also have a certain level of uncertainty. In determining the thresholds 134, the threshold engine 124 may incorporate these various sources of uncertainty and may determine an overall uncertainty for a given threshold 134. For instance, the threshold engine 124 may determine a probabilistic distribution or a probability density function for representing or expressing the thresholds 134 with respect to their associated uncertainty.

The threshold engine 124 may determine one or more thresholds for an operation of the conveyance system in real time. For example, based on the real time surface measurements received by the data manager 122, the threshold engine 124 may determine, in real time, the thresholds 134 applicable to the conveyance operation at a given moment in time. In some embodiments, the threshold engine 124 may update the thresholds 134 one or more times, for example, to adapt to changing circumstances of the conveyance operation. For example, as the equipment is advanced further downhole or uphole, the dynamics exhibited at a given location of the equipment (e.g., line) may change. For instance, as a line encounters a bend or dogleg, the line may initially contact the wellbore wall and a certain amount of friction may be exerted on the line. As the line progresses (e.g., in either direction) the amount of friction may change based on a weight of the line above and/or below the dogleg, wellbore geometry, and/or any number of different factors. Based on changes in the determined forces acting on the line, the threshold engine 124 may update any associated threshold 134. As another example, as described above, the failure models 128 may characterize the dynamics exhibited by the equipment based on one or more inferred parameters. In some cases, these parameters inferences may change based on updated and/or additional information. Accordingly, the threshold engine 124 may update the inferred parameters, which may result in changes and/or updates to the associated thresholds 134. In this way, the threshold engine 124 may maintain the thresholds up to date and may do so in real time to ensure accuracy and precision of the thresholds 134.

As mentioned above, the conveyance control system 120 includes a failure manager 126. The failure manager 126 may facilitate the conveyance system operating within or with respect to the thresholds 134. For example, the failure manager 126 may monitor the surface measurements 132 against the thresholds 134 and may identify when the surface measurements 132 reach or surpass the thresholds 134.

As described herein, in some embodiments, the thresholds 134 may be a specific value for limiting a given surface measurement. For example, the thresholds 134 may be a given surface load or a specific surface speed which may govern the conveyance of the line. The failure manager 126 may determine when a surface measurement reaches or passes an associated value of the thresholds 134.

In some embodiments, as described herein, the thresholds 134, as well as the surface measurements 132, may be represented or expressed with a certain level of uncertainty. The failure manager 126 may monitor the surface measurements 132 and the associated thresholds 134 and may determine, based on and in view of the uncertainty, when the surface measurements 132 are at or past the associated thresholds 134.

FIGS. 3-1 illustrates an example case 300 and FIG. 3-2 illustrates an example case 302 for an example surface measurement expressed with uncertainty as well as an associated threshold expressed with uncertainty, according to embodiments of the present disclosure.

The example case 300 includes a first probability distribution 310 and a second probability distribution 312. The first probability distribution 310 may represent a measured or observed surface measurement and the second probability distribution 312 may represent a surface measurement threshold. Each probability distribution may be associated with a specific measurement type of a surface measurement, such as a surface load or surface speed, and may represent a sample space for the possible values and associated probabilities for a given value (e.g., random sample) of a surface measurement or a surface measurement threshold. For example, the first probability distribution 310 may be expressed by a probability density function (PDF) representing the possible values and likelihood of an actual or true value of a surface measurement. Similarly, the probability distribution 312 may be expressed by a PDF representing the possible values and likelihood of an actual or true value for an associated surface measurement threshold.

In some embodiments, the failure manager 126 identifies when a surface measurement reaches or passes a surface measurement threshold based on an overlap of the probability distributions. For example, an area of overlap 314 between the first probability distribution 310 and the second probability distribution 312 can be characterized by an overlap coefficient (OVL). The OVL may be a number between 0 and 1 representing the percentage of overlap, or total relative common area between the two distributions. For example, an OVL closer to 0 may indicate little to no overlap between the probability distributions, representing a low likelihood or probability that the surface measurement has surpassed the surface measurement threshold. An OVL closer to 1 may indicate a more significant amount of overlap, representing a higher likelihood or probability that the surface measurement has surpassed the surface measurement threshold. Thus, the failure manager 126 may determine that the surface measurement has passed the surface measurement threshold based on an OVL being greater than a threshold value, or greater than an overlap threshold. For example, the overlap threshold may be an OVL of 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, or any value therebetween.

As shown in the example case 300, the OVL between the first probability distribution 310 and the second probability distribution 312 may be relatively small, such as closer to 0. Accordingly, the failure manager 126 may determine the surface measurement has not met or surpassed the surface measurement threshold. The example case 302 includes a third probability distribution 320 in relation to the second probability distribution 312. The third probability distribution may represent the same surface measurement from example case 300, but as measured or observed at a different point in time, under different circumstances, etc. An area of overlap 324 between the third probably distribution 320 and the second probability distribution 312 (the threshold) may be greater than the area of overlap 314. For instance, the area of overlap 324 may be characterized by an OVL that is larger, or closer to 1 than the OVL for the area of overlap 314. Accordingly, the area of overlap 324 may represent a higher likelihood that the surface measurement has surpassed the surface measurement threshold. For example, the area of overlap 324 may have an OVL that is greater than the overlap threshold. Accordingly, the failure manager 126 may determine that the surface measurement has surpassed the associated threshold in example case 302.

The failure manager 126 may, in this way, monitor any measurement against a corresponding threshold to identify when a given threshold is reached. For example, the failure manager may monitor probability distributions for surface load measurements, surface speed measurements, and/or depth of tool measurements and may determine when those measurements surpass associated thresholds, based on an area of overlap as described herein.

In some embodiments, based on identifying that a given threshold has been met or exceeded, the failure manager may indicate this occurrence, for example, by generating an alert or flag. For instance, the failure manager 126 may generate and insert a flag into the associated measurement data. In other cases, the failure manager 126 may generate and present an alert to a user, for instance, to indicate a change to be made to the conveyance system. The failure manager 126 may present the alert by sounding an alarm, presenting the alert via a graphical user interface, or in any other suitable way.

In some embodiments, the failure manager 126 adjusts or implements one or more changes to the conveyance system based on identifying that a threshold has been met or passed. In various embodiments, the failure manager 126 adjusts the conveyance system autonomously, automatically, and without user input. For example, upon identifying that a surface speed has surpassed a surface speed threshold (e.g., maximum RIH speed or maximum POOH speed), the failure manager 126 may automatically adjust the speed of conveyance of the conveyance system to maintain the surface speed measurement within the associated threshold (and/or maintain other measurements within associated thresholds). In this way, the failure manager 126 may prevent damage or failure of the conveyance system equipment by slowing down the conveyance speed as needed.

In some embodiments, the failure manager 126 may identify that the conveyance system is operating at a speed that does not correspond to the surface measurements surpassing any associated thresholds and may adjust the conveyance system to speed up the conveyance. For example, the failure manager 126 may implement a feedback loop to maintain the conveyance speed of the conveyance system such that the surface measurements are at or near the associated thresholds (e.g., or within a given proximity or factor of safety) without surpassing them. Further, the failure manager 126 may control the speed of the conveyance system in this way in real time to continually adjust the conveyance system based on current and changing circumstances of an operation. In this way, the failure manager 126 may automatically control the conveyance speed of the conveyance system to operate as fast as is safely possible.

In some embodiments, the failure manager 126 may stop the conveyance of the conveyance system or may indicate to do so. For example, the failure manger 126 may identify that one or more thresholds have been surpassed and may determine that the speed cannot be adjusted to bring the surface measurements back to safe levels and may accordingly stop or pause the conveyance operation. For instance, the failure manager 126 may attempt to implement a change to the speed to bring the surface measurements back within the thresholds and may identify that the change in speed did not have the expected effect. For instance, the surface measurements may not have returned to safe levels, or the surface measurements may continue to further surpass the thresholds, such as due to the equipment becoming stuck. In such cases, the failure manager may stop the movement of the equipment in order to prevent damage (or further damage) to the equipment. By stopping or pausing the operation in this way, the failure manager 126 may facilitate conveyance operations personnel understanding and/or solving the situation while preventing equipment damage to the furthest extent possible.

In some embodiments, the failure manager 126 may determine that a threshold has been met or passed based on incorporating a response delay. For example, the failure manager 126 may identify a latency or delay between the conveyance control system 120 identifying a surpassed threshold, and the actual change or adjustment to the conveyance system as implemented downhole. Based on the response delay, the failure manager 126 may identify an additional change to the observed surface measurements (e.g., above and/or beyond that which caused the identification of the passed threshold) that occurs during the response delay. This additional change may be based on an operation type, operational status, speed, etc. of the conveyance system.

In some embodiments, the failure manager 126 may determine a response offset for applying to and/or implementing in connection with a given threshold. For example, the response offset may take into account the amount of time it takes to implement a change to the conveyance system, and the associated additional changes to the observed surface measurements that may occur during that delay. The failure manager 126 may accordingly indicate and/or act in response to a passed threshold earlier or sooner based on applying the response to the associated threshold.

As an illustrative example, a maximum surface load threshold may be 100 kilonewtons (kN). Given the response delay in affecting a change in the conveyance system, and given the current conveyance speed of the system, the surface load may increase by an additional 10 kN by the time the conveyance control system 120 can identify and implement a change to the speed. Accordingly, the failure manager 126 may determine and implement a response offset to the maximum surface load threshold in order to determine a surpassed threshold and implement a change earlier and/or sooner. For instance, based on the maximum surface load threshold of 100 kN, the failure manger 126 may determine that the threshold has been reached when the measured surface load is at 90 kN, to accommodate the additional 10 kN change in the measured surface loading during the response delay such that the maximum surface load threshold of 100 kN is not exceeded.

In some cases, a conveyance system may include a downhole conveyance device. For example, a downhole tractor, crawler, or other device may be implemented downhole for engaging the wellbore and for pushing and/or pulling the line (or other downhole tool) in addition to the line being fed or retracted from the surface. In another example, a fluid may be pumped downhole for further pushing the line and other tools downhole, for example, in a CT application.

In some embodiments, the failure manager 126 may incorporate and control these downhole conveyance devices to facilitate a conveyance system operating within (e.g., without surpassing) the associated thresholds. FIG. 4 illustrates an example case 400 of the conveyance control system implementing a downhole conveyance device to operate the conveyance control system within a threshold, according to at least one embodiment of the present disclosure.

In the example case 400, an axial force profile 402 corresponds to the axial force exhibited by the line of a CT application with respect to depth. As shown, near the surface and at higher elevations, the line is initially subjected to tensile forces, based on the weight of the line hanging below (e.g., downhole of) these points. However, in deeper elevations, the forces exhibited by the line are compressive forces. For example, in deviated wells having bends and doglegs, the line may encounter the wellbore wall, and friction forces may cause the weight of uphole sections of the line to compress downhole sections that are positioned in highly deviated portions of the wellbore. For instance, at or around a point 408 the line may experience an increased or maximum compressive force due to wellbore deviations. Accordingly, the critical buckling load of the line may be reached and surpassed, as indicated by the line 406. This may also be represented or expressed as a minimum surface load required to prevent such buckling. Due to the tortuosity of the wellbore, it may not be possible to run the line past highly deviated sections due to the excessive compressive forces.

As just mentioned, conveyance systems may include downhole conveyance devices for facilitating or contributing to the conveyance of the line downhole. The failure manager 126 may identify the capabilities of these conveyance devices and may advantageously implement them to further advance the line while maintaining the conveyance system within the associated thresholds. For example, the failure manager 126 may determine an offset 410 between the loading that the line may experience and an associated threshold and may implement a conveyance device to nullify this offset 410. As an example, an axial force profile 404 corresponds to the axial force exhibited by the line of the CT application with respect to depth, but as implemented with a conveyance device. By implementing the conveyance device downhole to push or pull the line with a magnitude determined by the offset 410, for example, in addition to being fed from the surface by gravity and/or the weight of the line, the amount of compressive force experienced by the line at the point 408 may be reduced such that the critical buckling load is not surpassed. In this way, the failure manager 126 may advantageously implement, automatically and without user input, the capabilities of these additional conveyance devices to ensure that the conveyance system is operated within the designated thresholds. The application of the additional conveyance devices may be utilized in either direction (e.g., downhole or uphole) and with respect to any loading on the equipment (e.g., tension or compression). In this way, the equipment may be operated to further depths without exceeding operational limits of the equipment, such as to avoid the line becoming slack, to avoid excess tension on the line, or any of the failure modes described herein.

FIG. 5 is a flow diagram illustrating an example flow 500 for a functionality of the conveyance control system 120 for controlling an operation of a conveyance system as described herein, according to at least one embodiment of the present disclosure. At 510, the conveyance control system 120 may determine and/or update thresholds as described herein for maintaining the operation of a conveyance system within the operational limits and ratings of the associated equipment. The conveyance control system 120 may update the thresholds in real time as the equipment advances within the wellbore, as new measurements are received, etc. In this way, the conveyance control system 120 may maintain an up to date set of thresholds for ensuring the safety of the operation in a current moment.

Based on the thresholds, the conveyance control system 120 may monitor the surface measurements at 520. The conveyance control system 120 monitors these measurements against the thresholds in order to identify how the conveyance system is behaving or responding to an operation with respect to the thresholds, in order to make changes or adjustments to the operation of the conveyance system. For example, at 530, the conveyance control system 120 determines whether the operation (e.g., speed) of the conveyance system is causing the surface measurements to be within the thresholds. If one or more of the surface measurements are at or in excess of the thresholds, the conveyance control system 120, at 540, may automatically reduce the surface speed. For example, the conveyance control system 120 may determine by how much to reduce the surface speed, may reduce the surface speed by some default interval, and/or may implement a feedback loop for reducing the surface speed. Based on the surface measurements returning to acceptable levels in response to reducing the surface speed, the conveyance control system 120 proceeds back to 510 to update the thresholds and continue monitoring the surface measurements.

At 530, the conveyance control system 120 may determine that the surface measurements are within the thresholds. Based on this determination, the conveyance control system 120 may receive or determine updated thresholds 510 for maintaining the control of the conveyance system current with the changing circumstances of the operation. Alternatively, if the conveyance control system 120 determines that the surface measurements are within the thresholds at 530, the conveyance control system 120 may identify that the conveyance system is being operated at a speed slower than a maximum safe speed. Accordingly, the conveyance control system 120 may increase the surface speed, at 550 (e.g., through a feedback loop), until the surface measurements are at or near (e.g., within a factor of safety) their associated thresholds. In this way, the conveyance control system 120 may control the conveyance speed of the conveyance system such that the equipment is not damaged but may also operate the conveyance speed as fast as can safely be done in order to provide efficiency benefits in addition to safety.

FIG. 6 illustrates a flow diagram for a method 600 or as series of acts for operating a conveyance system implemented in a wellbore as described herein, according to at least one embodiment of the present disclosure. While FIG. 6 illustrates acts according to one embodiment, alternative embodiments may add to, omit, reorder, or modify any of the acts of FIG. 6. The acts of FIG. 6 may be performed as a method, may be performed by a system, or may be implemented as instructions stored in a computer-readable storage medium.

In some embodiments, the method 600 includes an act 610 of receiving surface measurements. For example, the act 610 may include receiving surface measurements including surface load measurements, surface speed measurements, and depth of tool measurements for the conveyance system.

In some embodiments, the method 600 includes an act 620 of, with a failure model, generating a threshold. For example, the act 620 may include with a failure model, generating a threshold associated with at least one of a maximum run-in-hole speed, a maximum pull-out-of-hole speed, a maximum load, a minimum load, or a maximum depth of tool for the conveyance system.

In some embodiments, the failure model adjusts the threshold based on a trajectory of the wellbore, subsurface formation properties, and the depth of tool measurements. In some embodiments, the threshold is updated based on changes in the depth of tool or based on changes to one or more inferred parameters utilized to determine the threshold.

In some embodiments, the thresholds include a threshold probability distribution and the surface measurements include a measurement probability distribution. For example, identifying that the surface measurements surpass the threshold includes determining that an overlap coefficient between the threshold probability distribution and the measurement probability distribution is greater than an overlap threshold.

In some embodiments, the wellbore conveyance system includes a wireline for conveying a wireline tool in the wellbore, and the threshold is generated with respect to conveying the wireline and the wireline tool in the wellbore. In some embodiments, the wellbore conveyance system includes a coiled tubing for conveying a downhole tool in the wellbore, and the thresholds are generated with respect to conveying the coiled tubing and the downhole tool in the wellbore.

In some embodiments, the method 600 includes an act 630 of adjusting the movement of the conveyance system based on identifying that the surface measurements surpass the threshold. For example, the surface speed of the wellbore conveyance system may be adjusted such that the surface measurements are within the threshold. In some embodiments, a push/pull load of a downhole conveyance device of the conveyance system is adjusted such that the surface measurements are within the threshold. For example, the downhole conveyance device may be a tractor for pushing or pulling a downhole portion of the conveyance system. In another example, the downhole conveyance device is a fluid pressure for pushing a downhole portion of the conveyance system. In some embodiments, the movement of the conveyance system may be stopped based on identifying that the surface measurements cannot be maintained within the threshold.

In some embodiments, receiving the surface measurements, generating the threshold, and adjusting the movement of the conveyance system are performed in real time. In some embodiments, adjusting the movement of the conveyance system is performed automatically and without user input.

In some embodiments, the method 600 includes receiving depth of tool measurements, identifying an operational status of the conveyance system, based on the depth of tool measurements and the operational status, generating, with a failure model, a surface load threshold associated with a load on the conveyance system, receiving surface load measurements for the conveyance system, and adjusting a speed of the conveyance system to maintain the surface load measurements within the surface load threshold.

In some embodiments, the operational status is tripping the conveyance system into the wellbore, and the load threshold is a minimum tension for the conveyance system.

In some embodiments, the operational status is tripping the conveyance system into the wellbore, and the load threshold is a maximum compression for the conveyance system.

In some embodiments, the operational status is tripping the conveyance system out of the wellbore, and the load threshold is a maximum tension for the conveyance system.

In some embodiments, the operational status is tripping the conveyance system into the wellbore, and the load threshold is a maximum depth for the conveyance system.

In some embodiments, the method further includes identifying a response delay for adjusting the speed of the conveyance system, and determining a change in load on the conveyance system during the response delay, wherein generating the threshold includes generating a response offset for the threshold, and wherein adjusting the speed includes adjusting the speed based on the response offset to maintain the surface load measurements within the threshold.

Turning now to FIG. 7, this figure illustrates certain components that may be included within a computer system 700. One or more computer systems 700 may be used to implement the various devices, components, and systems described herein.  

The computer system 700 includes a processor 701. The processor 701 may be a general-purpose single- or multi-chip microprocessor (e.g., an Advanced RISC (Reduced Instruction Set Computer) Machine (ARM)), a special purpose microprocessor (e.g., a digital signal processor (DSP)), a microcontroller, a programmable gate array, etc. The processor 701 may be referred to as a central processing unit (CPU). Although just a single processor 701 is shown in the computer system 700 of FIG. 7, in an alternative configuration, a combination of processors (e.g., an ARM and DSP) could be used. 

The computer system 700 also includes memory 703 in electronic communication with the processor 701. The memory 703 may include computer-readable storage media and can be any available media that can be accessed by a general purpose or special purpose computer system. Computer-readable media that store computer-executable instructions are non-transitory computer-readable media (device). Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example and not limitations, embodiment of the present disclosure can comprise at least two distinctly different kinds of computer-readable media: non-transitory computer-readable media (devices) and transmission media.

Both non-transitory computer-readable media (devices) and transmission media may be used temporarily to store or carry software instructions in the form of computer readable program code that allows performance of embodiments of the present disclosure. Non-transitory computer-readable media may further be used to persistently or permanently store such software instructions. Examples of non-transitory computer-readable storage media include physical memory (e.g., RAM, ROM, EPROM, EEPROM, etc.), optical disk storage (e.g., CD, DVD, HDDVD, Blu-ray, etc.), storage devices (e.g., magnetic disk storage, tape storage, diskette, etc.), flash or other solid-state storage or memory, or any other non-transmission medium which can be used to store program code in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer, whether such program code is stored or in software, hardware, firmware, or combinations thereof.

Instructions 705 and data 707 may be stored in the memory 703. The instructions 705 may be executable by the processor 701 to implement some or all of the functionality disclosed herein. Executing the instructions 705 may involve the use of the data 707 that is stored in the memory 703. Any of the various examples of modules and components described herein may be implemented, partially or wholly, as instructions 705 stored in memory 703 and executed by the processor 701. Any of the various examples of data described herein may be among the data 707 that is stored in memory 703 and used during execution of the instructions 705 by the processor 701.

A computer system 700 may also include one or more communication interfaces 709 for communicating with other electronic devices. The communication interface(s) 709 may be based on wired communication technology, wireless communication technology, or both. Some examples of communication interfaces 709 include a Universal Serial Bus (USB), an Ethernet adapter, a wireless adapter that operates in accordance with an Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless communication protocol, a Bluetooth® wireless communication adapter, and an infrared (IR) communication port.

The communication interfaces 709 may connect the computer system 700 to a network. A “network” or “communications network” may generally be defined as one or more data links that enable the transport of electronic data between computer systems and/or modules, engines, or other electronic devices, or combinations thereof. When information is transferred or provided over a communication network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computing device, the computing device properly views the connection as a transmission medium. Transmission media can include a communication network and/or data links, carrier waves, wireless signals, and the like, which can be used to carry desired program or template code means or instructions in the form of computer-executable instruction or data structures and which can be accessed by a general purpose or special purpose computer.

A computer system 700 may also include one or more input devices 711 and one or more output devices 713. Some examples of input devices 711 include a keyboard, mouse, microphone, remote control device, button, joystick, trackball, touchpad, and lightpen. Some examples of output devices 713 include a speaker and a printer. One specific type of output device that is typically included in a computer system 700 is a display device 715. Display devices 715 used with embodiments disclosed herein may utilize any suitable image projection technology, such as liquid crystal display (LCD), light-emitting diode (LED), gas plasma, electroluminescence, or the like. A display controller 717 may also be provided, for converting data 707 stored in the memory 703 into one or more of text, graphics, or moving images (as appropriate) shown on the display device 715.

The various components of the computer system 700 may be coupled together by one or more buses, which may include one or more of a power bus, a control signal bus, a status signal bus, a data bus, other similar components, or combinations thereof. For the sake of clarity, the various buses are illustrated in FIG. 7 as a bus system 719.

The techniques described herein may be implemented in hardware, software, firmware, or any combination thereof, unless specifically described as being implemented in a specific manner. Any features described as modules, components, or the like may also be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, the techniques may be realized at least in part by a non-transitory processor-readable storage medium comprising instructions that, when executed by at least one processor, perform one or more of the methods described herein. The instructions may be organized into routines, programs, objects, components, data structures, etc., which may perform particular tasks and/or implement particular data types, and which may be combined or distributed as desired in various embodiments. 

Further, upon reaching various computer system components, program code in the form of computer-executable instructions or data structures can be transferred automatically or manually from transmission media to non-transitory computer-readable storage media (or vice versa). For example, computer executable instructions or data structures received over a network or data link can be buffered in memory (e.g., RAM) within a network interface module (NIC), and then eventually transferred to computer system RAM and/or to less volatile non-transitory computer-readable storage media at a computer system. Thus, it should be understood that non-transitory computer-readable storage media can be included in computer system components that also (or even primarily) utilize transmission media.

The embodiments of the conveyance control system have been primarily described with reference to wellbore operations; the conveyance control system described herein may be used in applications other than the those of a wellbore. In other embodiments, the conveyance control system according to the present disclosure may be used outside a wellbore or other downhole environment used for the exploration or production of natural resources. For instance, the conveyance control system of the present disclosure may be used in a borehole used for placement of utility lines. Accordingly, the terms “wellbore,” “borehole” and the like should not be interpreted to limit tools, systems, assemblies, or methods of the present disclosure to any particular industry, field, or environment.

One or more specific embodiments of the present disclosure are described herein. These described embodiments are examples of the presently disclosed techniques. Additionally, in an effort to provide a concise description of these embodiments, not all features of an actual embodiment may be described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous embodiment-specific decisions will be made to achieve the developers’ specific goals, such as compliance with system-related and business-related constraints, which may vary from one embodiment to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.

Additionally, it should be understood that references to “one embodiment” or “an embodiment” of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features. For example, any element described in relation to an embodiment herein may be combinable with any element of any other embodiment described herein. Numbers, percentages, ratios, or other values stated herein are intended to include that value, and also other values that are “about” or “approximately” the stated value, as would be appreciated by one of ordinary skill in the art encompassed by embodiments of the present disclosure. A stated value should therefore be interpreted broadly enough to encompass values that are at least close enough to the stated value to perform a desired function or achieve a desired result. The stated values include at least the variation to be expected in a suitable manufacturing or production process, and may include values that are within 5%, within 1%, within 0.1%, or within 0.01% of a stated value.

A person having ordinary skill in the art should realize in view of the present disclosure that equivalent constructions do not depart from the spirit and scope of the present disclosure, and that various changes, substitutions, and alterations may be made to embodiments disclosed herein without departing from the spirit and scope of the present disclosure. Equivalent constructions, including functional “means-plus-function” clauses are intended to cover the structures described herein as performing the recited function, including both structural equivalents that operate in the same manner, and equivalent structures that provide the same function. It is the express intention of the applicant not to invoke means-plus-function or other functional claiming for any claim except for those in which the words ‘means for’ appear together with an associated function. Each addition, deletion, and modification to the embodiments that falls within the meaning and scope of the claims is to be embraced by the claims.

The terms “approximately,” “about,” and “substantially” as used herein represent an amount close to the stated amount that is within standard manufacturing or process tolerances, or which still performs a desired function or achieves a desired result. For example, the terms “approximately,” “about,” and “substantially” may refer to an amount that is within less than 5% of, within less than 1% of, within less than 0.1% of, and within less than 0.01% of a stated amount. Further, it should be understood that any directions or reference frames in the preceding description are merely relative directions or movements. For example, any references to “up” and “down” or “above” or “below” are merely descriptive of the relative position or movement of the related elements. Additionally, as used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.

The present disclosure may be embodied in other specific forms without departing from its spirit or characteristics. The described embodiments are to be considered as illustrative and not restrictive. The scope of the disclosure is, therefore, indicated by the appended claims rather than by the foregoing description. Changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.