Well lockout and automation systems and methods

Abstract

Techniques for adaptively performing an operation in a well system that include determining, using a control sub-system, an operation schedule that indicates control action steps in the operation; instructing, using the control sub-system, the well system to initiate a first control action step of the operation that transitions a first fluid valve from a first current valve state to a first target valve state; determining, using the control sub-system, whether an expedited performance parameter associated with the operation is set in the operation schedule; and in response to determining that the expedited performance parameter associated with the operation is set, instructing, using the control sub-system, the well system to initiate a second control action step of the operation that transitions a second fluid valve from a second current valve state to a second target valve state before the first fluid valve achieves the first target valve state.

Description

CROSS-REFERENCE

[0001] The present disclosure is a continuation-in-part of U.S. Non-Provisional application Ser. No. 18 / 793,067, entitled “WELL LOCKOUT AND AUTOMATION SYSTEMS AND METHODS” and filed Aug. 2, 2024, which is a continuation of U.S. Non-Provisional application Ser. No. 18 / 603,738, entitled “WELL LOCKOUT AND AUTOMATION SYSTEMS AND METHODS,” filed Mar. 13, 2024, and now U.S. Pat. No. 12,104,477, which claims priority to and benefit of U.S. Provisional Application No. 63 / 451,865, entitled “REMOTE LOCKOUT SYSTEM FOR FRAC VALVE OPERATIONS” and filed Mar. 13, 2023, which are each incorporated herein by reference in its entirety for all purposes.BACKGROUND

[0002] The present disclosure generally relates to well systems and, more particularly, to techniques for properly and efficiently coordinating operations in a well system, for example, to facilitate improving operational efficiency (e.g., production time) of the well system.

[0003] Often, to produce fluid, such as oil and / or gas, from a well in a well system, multiple different groups of operators may need to perform operations around the well system. For example, a wireline operator may be responsible for performing a perforation operation in a wellbore while a pressure pumper may be responsible for performing a hydraulic fracturing operation in the wellbore. As another example, a service technician may be responsible for controlling operation of fluid valves in a valve tree disposed on a wellbore to perform a valve tree operation that enables performance of other well operations, such as a perforation operation and / or a hydraulic fracturing operation.

[0004] In other words, at least in some instances, performance of a well operation assigned to one operator group may be dependent on performance of a well operation assigned to a different operator group and, in fact, different well operations may result in the same equipment being operated in different manners. For example, to enable a wireline tool to be inserted into a wellbore and, thus, performance of a perforation operation, a wireline operator may need a service technician operator to perform a valve tree operation that transitions a fluid valve at the top of a corresponding valve tree to its open state. On the other hand, to block fracturing fluid from leaking to the surrounding environment during performance of a hydraulic fracturing operation, a pressure pumper may need the service technician to perform a valve tree operation that transitions the fluid valve at the top of the valve tree to its closed state. Additionally, to enable fracturing fluid to fracture surrounding formations, the perforation operation may need to be performed before the hydraulic fracturing operation. Accordingly, coordination between different operator groups around a well system potentially creates a bottleneck that limits operational efficiency of the well system.SUMMARY

[0005] This summary is provided to introduce a selection of concepts that are further described below 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.

[0006] In one embodiment, a method of adaptively performing an operation in a well system includes determining, using a control sub-system of the well system, an operation schedule that indicates control action steps in the operation; instructing, using the control sub-system, the well system to initiate a first control action step of the operation from the operation schedule that transitions a first fluid valve from a first current valve state to a first target valve state; determining, using the control sub-system, whether an expedited performance parameter associated with the operation is set in the operation schedule; and in response to determining that the expedited performance parameter associated with the operation is set in the operation schedule, instructing, using the control sub-system, the well system to initiate a second control action step of the operation from the operation schedule that transitions a second fluid valve from a second current valve state to a second target valve state before the first fluid valve achieves the first target valve state.

[0007] In another embodiment, a well system includes first well system equipment; second well system equipment; a power sub-system coupled to the first well system equipment and the second well system equipment; and a control sub-system communicatively coupled to the power sub-system. The control sub-system instructs the power sub-system to supply power to the first well system equipment to perform a first control action step of an operation that transitions the first well system equipment from a first current equipment state to a first target equipment state in accordance with an operation schedule; and when a sequential performance parameter associated with the operation is not set in the operation schedule, instruct the power sub-system to concurrently supply power to the first well system equipment and the second well system equipment to perform, concurrent with the first control action step of the operation, a second control action step of the operation that transitions the second well system equipment from a second current equipment state to a second target equipment state.

[0008] In a further embodiment, a tangible, non-transitory, computer-readable media stores instructions executable by processing circuitry in a well system. The instructions include instructions to determine, using the processing circuitry, an operation schedule that indicates control action steps of an operation to be performed in the well system; instruct, using the processing circuitry, the well system to initiate a first control action step of the operation from the operation schedule that transitions first well system equipment from a first current equipment state to a first target equipment state; determine, using the processing circuitry, whether a sequential performance parameter associated with the operation is set in the operation schedule; and when the sequential performance parameter associated with the operation is not set in the operation schedule, instruct, using the processing circuitry, the well system to initiate a second control action step of the operation from the operation schedule that transitions second well system equipment from a second current equipment state to a second target equipment state before the first well system equipment achieves the first target equipment state.BRIEF DESCRIPTION OF DRAWINGS

[0009] FIG. 1 is a block diagram of an example of a well system, in accordance with an embodiment of the present disclosure.

[0010] FIG. 2 is a side view of an example of a fluid-powered fluid valve that may be included in the well system of FIG. 1, in accordance with an embodiment of the present disclosure.

[0011] FIG. 3 is a block diagram of an example of a distributed control sub-system that may be included in the well system of FIG. 1, in accordance with an embodiment of the present disclosure.

[0012] FIG. 4 is a flow diagram describing an example of a process for coordinating operations performed by different operator groups around a well system, in accordance with an embodiment of the present disclosure.

[0013] FIG. 5 is a flow diagram describing an example of a process for automating performance of an operation in a well system, in accordance with an embodiment of the present disclosure.

[0014] FIG. 6 is a flow diagram describing an example of a process for secondarily confirming achievement of a target valve state, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION

[0015] One or more specific embodiments of the present disclosure will be described below with reference to the figures. Wherever possible, like or identical reference numerals are used in the figures to identify common or the same features. The figures are not necessarily to scale. In particular, certain features and / or certain views of the figures may be shown exaggerated in scale for purposes of clarification. As used herein, the term “coupled” or “coupled to” may indicate establishing either a direct or indirect connection and, thus, is not limited to either unless expressly referenced as such.

[0016] The present disclosure generally relates to a well system that operates to produce fluid, such as oil and / or gas, from a well. Due to its complexity, the overall process of producing fluid from a well often involves multiple different parties and, thus, corresponding operator groups that have different responsibilities. For example, a wireline (e.g., tool) operator may be responsible for performing a perforation operation in a wellbore and, thus, controlling the operation of a wireline (e.g., perforation) tool that is disposed within the wellbore. As another example, a pressure pumper (e.g., fracturing operator) may be responsible for performing a hydraulic fracturing operation in a wellbore and, thus, controlling the operation of a fracturing fluid pump that supplies fracturing fluid to the wellbore. As a further example, a service technician (e.g., operator) may be responsible for performing a valve tree operation to control operation of a fluid valve in a corresponding valve tree and, thus, access to a corresponding wellbore.

[0017] In fact, although different operations may be serially performed on a well, to facilitate improving operational efficiency, different operator groups may nevertheless operate at least partially in parallel. For example, although a hydraulic fracturing operation may be performed on a well after a perforation operation, a pressure pumper may begin preparing (e.g., mixing and / or blending) fracturing fluid while a wireline operator is still in the process of perforating the casing and the surrounding formation.

[0018] Moreover, to accomplish their responsibilities, at least in some instances, different operator groups may need the same equipment to be operated in different manners. For example, to enable a wireline tool to be disposed within a corresponding wellbore during a perforation operation, a wireline operator may need a fluid valve at the top of a valve tree to be in its open state. On the other hand, to prevent fracturing fluid from inadvertently leaking to the surrounding environment during a hydraulic fracturing operation, a pressure pumper may need the fluid valve at the top of the valve tree to be in its closed state. Accordingly, to enable performance of the perforation operation, a service technician may need to perform a first valve tree operation to transition the valve tree to a perforation valve configuration in which the fluid valve at the top of the valve tree is in its open state and, to enable performance of the hydraulic fracturing operation, the service technician may need to perform a second valve tree operation to transition the valve tree to a fracturing valve configuration in which the fluid valve at the top of the valve tree is in its closed state.

[0019] However, closing a fluid valve of a valve tree while a wireline tool is still disposed within a corresponding wellbore may result in the fluid valve inadvertently trapping or even cutting a conveyance line that connects the wireline tool to the surface, thereby necessitating corrective operations, such as fishing the wireline tool out of the wellbore, before normal operation can resume. In other words, at least in some instances, inappropriate coordination between different operator groups around a well system may potentially limit operational efficiency (e.g., production time) of the well system.

[0020] Accordingly, to facilitate improving operational efficiency, the present disclosure provides techniques for properly and efficiently coordinating different operator groups around a well system, for example, to enable different operator groups to operate at least partially in parallel while reducing the likelihood of their operations inadvertently disrupting one another. To facilitate controlling and, thus, coordinating operations, a well system generally includes a control sub-system. In particular, the control sub-system may be communicatively coupled to well system equipment, such as one or more fluid valves and / or one or more fluid pumps, to enable the control sub-system to instruct the well system equipment to execute control actions, for example, in addition to one or more sensors to enable the control sub-system to determine operational parameters of the well system. Merely as an illustrative non-limiting example, a control sub-system may instruct a valve actuator to transition a fluid valve from its current valve state (e.g., fully open state, fully closed state, or intermediate valve state) to a target (e.g., different) valve state, for example, in addition to receiving sensor feedback indicative of whether the fluid valve has achieved its target valve state.

[0021] Additionally, to facilitate coordinating different operator groups around a well system, a control sub-system may be distributed between multiple operator devices, which are each assigned to and associated with a different operator group, and a central controller, which is communicatively coupled to the operator devices. Merely as an illustrative non-limiting example, to facilitate coordinating hydraulic fracturing operations and perforation operations, a central controller may be communicatively coupled to a first operator device, which is assigned to and associated with a representative wireline operator, as well as a second operator device, which is assigned to and associated with a representative pressure pumper, for example, in addition to a third operator device, which is assigned to and associated with a representative service technician, and / or a fourth operator device, which is assigned to and associated with a representative well owner's operator.

[0022] Generally, an operator device that is assigned to and associated with an operator may include an electronic display, which enables the control sub-system to present information to the operator, and a user input device (e.g., buttons and / or touch sensors), which enables the operator to provide user inputs to the control sub-system. For example, the electronic display of an operator device may present a current valve state of a fluid valve and / or a prompt for response. Additionally or alternatively, the user input device of an operator device may enable an operator to request that the fluid valve change to a different valve state and / or to respond to the prompt. Accordingly, to facilitate coordinating performance of a subsequent (e.g., next) operation with performance of a preceding operation by a first operator, in some embodiments, a second operator may request performance of the subsequent operation via their operator device and, in response, the control sub-system may request approval from the first operator for performance of the subsequent operation and, until approval from the first operator is received, maintain a lockout to block the second operator or any other operator from performing the subsequent operation via their operator device.

[0023] However, at least in some instances, different operator groups that work on the same well may only have a contractual relationship with the owner of the well. For example, the owner of a well may have a contractual relationship with a wireline operator, a pressure pumper, and a service technician, but the wireline operator, the pressure pumper, and the service technician may not have a contractual relationship with one another. In other words, in such instances, different operator groups working on the same well may be independent third parties relative to one another and, thus, do not have the authority to approve or authorize the performance of an operation by another operator group.

[0024] Accordingly, to facilitate coordinating performance of a subsequent (e.g., next) operation with performance of a preceding operation by a first operator, in other embodiments, a control sub-system may, in response to a request by a second operator to perform the subsequent operation, maintain a lockout to block the second operator or any other operator from performing the subsequent operation via their operator device until completion confirmation is received from the first operator, for example, and the second operator finalizes or reconfirms their request to perform the subsequent operation (e.g., to provide the second operator an opportunity to cancel their request before actual performance). In particular, in some such embodiments, the control sub-system may simply wait for the first operator to input their completion confirmation via their operator device. However, to facilitate expediting the transition between different operations, in other such embodiments, the control sub-system may present the first operator with a prompt on their operator device to confirm completion of their preceding operation, for example, in response to receiving the request from the second operator to perform the subsequent operation and / or in accordance with an operation schedule.

[0025] Nevertheless, to facilitate further reducing the likelihood of issues arising when transitioning between operations and / or improving operator accountability, in some embodiments, a control sub-system may inform a first operator of a subsequent operation that is to be performed by a second operator after the first operator confirms completion of their preceding operation, for example, to enable the first operator to block performance of the subsequent operation even though the first operator has in fact completed performance of their preceding operation (e.g., if the first operator foresees a potential issue with performing the subsequent operation despite having completed their preceding operation). In particular, in some such embodiments, the control sub-system may merely indicate a subsequent operation that will be performed next when prompting an operator to confirm completion of their preceding operation. However, before permitting performance of a subsequent operation, in other such embodiments, the control sub-system may prompt the operator to explicitly acknowledge the specific subsequent operation that will be performed next. In other words, in such embodiments, the control sub-system may maintain a lockout to block a second operator from performing a subsequent operation via their operator device until completion confirmation of a preceding operation as well as acknowledgement of the subsequent operation are received from the first operator.

[0026] In any case, for traceability purposes, in some embodiments, a control sub-system may log or otherwise track received completion confirmations and / or acknowledgements relative to performance of subsequent operations via an operations log, for example, in addition to request finalizations or re-confirmations. Merely as an illustrative non-limiting example, a control sub-system may log that a wireline operator confirmed completion of a perforation operation at a first time and that a service technician began performing a valve tree operation to transition a valve tree from a perforation valve configuration to a different (e.g., fracturing or shut-in) valve configuration at a second time after the first time, for example, and that a requesting operator, such as the service technician or a well owner's operator, requested performance of the valve tree operation at a third time before the first time, that the wireline operator acknowledged that the valve tree operation will be performed next at a fourth time around (e.g., slightly before, slightly after, or concurrent with) the first time, and / or that that the requesting operator finalized or re-confirmed their request to perform the valve tree operation at a fifth time between the first time and the second time. Accordingly, if a fluid valve of a corresponding valve tree were to inadvertently close on a conveyance line of a wireline tool during the valve tree operation, the operation log can be referenced to show that the wireline tool should have been out of a corresponding wellbore and, thus, that the conveyance line should have been removed from the valve tree by the time the valve tree operation was initiated.

[0027] In any case, after receiving a completion confirmation from a first operator associated with a preceding operation, a control sub-system may permit performance of a second operator's subsequent (e.g., next) operation, for example, after also receiving an acknowledgement from the first operator that the subsequent operation will be performed next and / or receiving finalization or re-confirmation of the request to perform the subsequent operation. In particular, while an operator is permitted to perform an operation, in some embodiments, a control sub-system may remove a lockout from the operator to enable the operator to control individual equipment from their operator device to perform a control action step in the operation. Merely as an illustrative non-limiting example, when permitted to perform a valve tree operation, a control sub-system may enable a service technician to instruct a valve actuator to transition a corresponding fluid valve from its current valve state to a target valve state from their operator device.

[0028] However, at least in some instances, an operation in a well system may include multiple (e.g., sequential) control action steps. For example, to perform a valve tree operation that transitions a valve tree to a fracturing valve configuration, a swab (e.g., top and / or crown) valve of the valve tree may to be transitioned to its closed state before an injection wing valve of the valve tree is transitioned to its open state. In fact, in some instances, opening the injection wing valve while the swab valve is still open may result in hydraulic fluid inadvertently leaking to the surrounding environment instead of fracturing the formation surrounding a corresponding wellbore, thereby necessitating corrective operations, such as environmental cleanup, before normal operation can resume. In other words, at least in some instances, inappropriate coordination between different control action steps in an operation, which may occur even if performed by the same operator, may potentially limit operational efficiency (e.g., production time) of a well system.

[0029] Accordingly, to facilitate improving well system operational efficiency, in other embodiments, a control sub-system may at least partially automate performance of one or more control action steps in an operation in accordance with an operation schedule (e.g., recipe and / or sequence). In particular, to facilitate reducing the potential for operator error, in some such embodiments, while performance of a corresponding operation is permitted, a control sub-system may nevertheless maintain a lockout on an operator to block the operator from controlling individual equipment from their operator device and, instead, automatically instruct well system equipment to perform control action steps of the operation in accordance with the operation schedule.

[0030] To facilitate automating performance of an operation, a corresponding operation schedule may generally specify the control action steps in the operation as well as a target equipment state to be achieved in each control action step. For example, an operation schedule associated with a valve tree operation that transitions a valve tree to a fracturing valve configuration may indicate that a swab (e.g., top and / or crown) valve on the valve tree is to be transitioned to its closed state in a first (e.g., initial) control action step and that an injection wing valve on the valve tree is to be transitioned to its open state in a second (e.g., subsequent) control action step.

[0031] Accordingly, to facilitate coordinating control action steps and / or operations, in some embodiments, a control sub-system may be communicatively coupled to equipment sensors that feedback operational parameters of corresponding equipment. For example, a valve sensor may feedback an indication of the current valve state of a corresponding fluid valve to enable the control sub-system to determine whether the fluid valve is currently in a fully open state, a fully closed state, or an intermediate valve state between the fully open state and the fully closed state and, thus, whether the fluid valve is currently in its target valve state.

[0032] However, at least in some instances, a faulty equipment sensor may feedback improper operational parameters or cease providing operational parameter feedback altogether. For example, a faulty valve sensor may indicate that a corresponding fluid valve has not achieved its target valve state when the fluid valve has in fact achieved its target valve state.

[0033] Accordingly, to facilitate reducing the likelihood of inadvertently holding up sequential performance of control action steps in an operation simply due to a faulty equipment sensor, in some embodiments, a control sub-system may utilize a sensor timeout for an equipment sensor. In particular, a sensor timeout associated with an equipment sensor may be set based on the amount of time corresponding equipment is expected to take to reach a target equipment state. For example, a sensor timeout associated with a valve sensor may be set based on (e.g., to match or slightly longer than) the expected time (e.g., duration) for changing a corresponding fluid valve from its current valve state to a target valve state. As such, when a sensor timeout associated with an equipment sensor has been reached but the equipment sensor indicates that corresponding equipment has not yet reached its target equipment state, in some embodiments, a control sub-system may presume that the equipment has reached its target equipment state and begin performance of a next control action step, for example, in addition identifying that the equipment sensor is potentially faulty once achievement of the target state is secondarily confirmed by an operator and / or via analysis of fluid parameter sensor feedback.

[0034] Nevertheless, to facilitate improving execution speed, in other embodiments, a control sub-system may initiate sequential control action steps of an operation in rapid succession (e.g., substantially simultaneously), for example, instead of waiting for a preceding control action step to be completed before initiating a subsequent control action step. As an illustrative non-limiting example, a control sub-system may initiate a first control action step to transition a swab (e.g., top and / or crown) valve to its closed state and, before the swab valve achieves its closed state, initiate a second control action step to transition a corresponding injection wing valve to its open state.

[0035] In fact, in some embodiments, a control sub-system may adaptively switch between automatically performing operations in an expedited (e.g., simultaneous) mode in which sequential control action steps are initiated in rapid succession and a sequential mode in which a subsequent control action step is initiated after completion of a preceding control action step, for example, based at least in part on whether a sequential performance parameter or an expedited performance parameter is set in a corresponding operation schedule. In this manner, as will be described in more detail below, the present disclosure provides techniques for improving automated coordination and performance of control action steps in an operation and, thus, well system operational efficiency (e.g., production time), for example, by enabling the operation to be completed faster and / or with fewer improper work stoppages. Additionally, as will be described in more detail below, the present disclosure provides techniques for improving coordination between different operator groups around a well system that have differing responsibilities, which, at least in some instances, may facilitate improving well system efficiency, for example, by enabling faster switching between well operations performed by different operator groups and / or reducing the need for corrective action while accounting for the actual relationship between the different operator groups.

[0036] To help illustrate, an example of a well system 10 is shown in FIG. 1. As in the depicted example, to facilitate forming (e.g., drilling) a wellbore 12 of a well 14 in a surrounding formation 16, a well system 10 may generally include a wellhead 18 secured over the wellbore 12. In particular, in the depicted example, the well system 10 includes a first wellhead 18A secured over a first wellbore 12A of a first well 14A and a second wellhead 18B secured over a second wellbore 12B of a second well 14B.

[0037] However, it should be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, a well system 10 may include a single well 14 and, thus, a single wellhead 18. Alternatively, in other embodiments, a well system 10 may include more than two (e.g., three, four, or more) wells 14 and, thus, more than two (e.g., three, four, or more) wellheads 18.

[0038] In any case, as depicted, a wellhead 18 on a well 14 may generally support and suspend a casing 20 within a corresponding wellbore 12 to facilitate fluidly isolating the wellbore 12 from surrounding formations 16 as well as structurally supporting the wellbore 12. As in the depicted example, to facilitate improving fluid isolation and / or structural support provided by a casing 20, in some embodiments, cement 22 may be disposed in an annulus surrounding the casing 20, for example, between the casing 20 and the surrounding formation 16 and / or between the casing 20 and an outer casing 20. In addition to a casing 20, as in the depicted example, in some embodiments, a wellhead 18 may be secured to and / or or rest on a conductor pipe 21, for example, which is driven into the formation 16 before drilling of a corresponding wellbore 12.

[0039] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, a well 14 may not include a conductor pipe 21. Additionally or alternatively, in other embodiments, a well 14 may include multiple casings 20 concentrically secured to and suspended from a wellhead 18, for example, to enable the corresponding wellbore 12 to be cyclically drilled deeper.

[0040] In any case, as in the depicted example, to facilitate controlling access to a wellbore 12, a well system 10 may include a valve tree 26, which includes multiple fluid valves 28, secured on and fluidly connected to a corresponding wellhead 18. In particular, in the depicted example, the well system 10 includes a first valve tree 26 secured on the first wellhead 18A such that a bore of the first valve tree 26A is fluidly connected to a bore of the first wellhead 18A and, thus, the first wellbore 12A. Additionally, the well system 10 includes a second valve tree 26B secured on the second wellhead 18B such that a bore of the second valve tree 26B is fluidly connected to a bore of the second wellhead 18B and, thus, the second wellbore 12B.

[0041] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, a wellhead 18 may include one or more of its own fluid valves 28. Additionally, in other embodiments, a well system 10 may include more than two (e.g., three, four, or more) valve trees 26, for example, when the well system 10 includes more than two wells 14. Alternatively, in other embodiments, a well system 10 may include a single valve tree 26, for example, when the well system 10 includes a single well 14 or when the same valve tree 26 is to be used with multiple different wells 14.

[0042] In any case, to provide master control over fluid flow into and / or out of a corresponding wellbore 12, as in the depicted example, the fluid valves 28 on a valve tree 26 generally include one or more master (e.g., working) valves 30. In particular, in the depicted example, the valve trees 26 each includes an upper master (e.g., working) valve 30A and a lower master (e.g., working) valve 30B. Additionally, to provide external access to a corresponding wellbore 12, as in the depicted example, the fluid valves 28 on a valve tree 26 generally include a swab (e.g., top, crown, and / or working) valve 32 at the top of the valve tree 26.

[0043] Furthermore, to facilitate producing fluid from and / or injecting fluid into a corresponding wellbore 12, as in the depicted example, the fluid valves 28 on a valve tree 26 generally include one or more wing valves 34. In particular, in the depicted example, the valve trees 26 each includes a first wing valve 34A and a second wing valve 34B connected in series on a wing valve branch 36 that extends out (e.g., horizontally) from a vertical extent of the valve tree 26. Additionally, to facilitate storing produced fluid for transportation and / or processing, as in the depicted example, a wing valve branch 36 of a valve tree 26 may be fluidly connected to a production fluid storage (e.g., tank) 38 via one or more fluid valves 28 and one or more fluid conduits 40, such as piping, tubing, or a hose.

[0044] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, a valve tree 26 may be fluidly connected directly to a produced fluid storage 38 without any other fluid valves 28 connected therebetween. Furthermore, in other embodiments, a valve tree 26 may include multiple wing valve branches 36, for example, which extend out in different (e.g., opposite) directions. Additionally or alternatively, in other embodiments, a wing valve branch 36 on a valve tree 26 may include a single wing valve 34 or more than two (e.g., three, four, or more) wing valves 34.

[0045] In any case, as described above, a casing 20 disposed within a wellbore 12 may facilitate fluidly isolating the wellbore 12 from the surrounding formation 16. Accordingly, to enable fluid to flow from a surrounding formation 16 through a corresponding casing 20 into a wellbore 12 and, thus, from the wellbore 12 through a valve tree 26 to a produced fluid storage 38, a perforation operation may need to be performed to perforate the casing 20, for example, in addition to the surrounding formation 16 and / or cement 22 formed between the casing 20 and the surrounding formation 16. In particular, as in the depicted example, a perforation operation may be performed in a well 14 using a wireline (e.g., downhole) tool 42, which is disposed within its wellbore 12 and suspended from the surface via a conveyance line 44, such as a wireline, a slickline, or coiled tubing.

[0046] Accordingly, to perform a perforation operation in a corresponding wellbore 12, as in the depicted example, the conveyance line 44 of a wireline tool 42 may extend through a valve tree 26, for example, after the wireline tool 42 has been inserted through the valve tree 26 into the wellbore 12 and before the wireline tool 42 is withdrawn from the wellbore 12 through the valve tree 26. In other words, to perform a perforation operation in a corresponding well 14, each working (e.g., swab, crown, and / or master) valve 28 of a valve tree 26 may need to be in its open state. In fact, inadvertently closing a working valve 28 of a valve tree 26 while a wireline tool 42 is still disposed within a corresponding wellbore 12 may result in the working valve 28 inadvertently trapping or even cutting the conveyance line 44 of the wireline tool 42, which potentially limits operational efficiency (e.g., production time) of the well system 10, for example, due to corrective action, such as fishing the wireline tool 42 out of the wellbore 12, being needed before normal operation can resume.

[0047] In any case, as in the depicted example, to facilitate performing a hydraulic fracturing operation and, thus, improving production of a well 14, a well system 10 may supply fracturing fluid from a fracturing fluid source 46 to a corresponding valve tree 26. In particular, to facilitate supplying fracturing fluid to a valve tree 26, as in the depicted example, a fracturing fluid source 46 generally includes a fluid pump 50—namely a fracturing fluid pump 50A.

[0048] Additionally, in some embodiments, fracturing fluid may include a base fluid, such as water or methanol, mixed with proppant (e.g., particles), such as sand and / or ceramic beads, and one or more chemical additives, such as scale inhibitors (e.g., ethylene glycol), clay stabilizers (e.g., potassium chloride), corrosion inhibitors (e.g., propargyl alcohol), gelling agents (e.g., guar gum), pH adjustors (e.g., sodium carbonate), foaming agents (e.g., nitrogen gas), or any combination thereof. In some such embodiments, fracturing fluid may be pre-mixed before being transported to a well system 10.

[0049] However, in other embodiments, fracturing fluid may be mixed onsite in a well system 10, for example, to facilitate better accounting for (e.g., adaptively adjusting formulation of fracturing fluid for) potential well and / or formation variations. To facilitate mixing fracturing fluid on-site, a fracturing fluid source 46 may include a mixer (e.g., blender) 48 as well as a base fluid source (e.g., tank and / or pump) 52, a proppant source (e.g., tank or hopper) 54, and a chemical additive source (e.g., tank) 56, which are each fluidly connected to the mixer 48 via one or more corresponding fluid conduits 40 and one or more corresponding fluid valves 28. Accordingly, in such embodiments, supply of the base fluid, the proppant, and the chemical additives to the mixer 48 and, thus, the formulation (e.g., composition) of fracturing fluid may be controlled by controlling actuation (e.g., opening and / or closing) of corresponding fluid valves 28.

[0050] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, a fracturing fluid source 46 in a well system 10 may not include a base fluid source 52, a proppant source 54, and / or a chemical additive source 56, for example, when fracturing fluid to be used in the well system 10 is at least partially mixed offsite.

[0051] In any case, as in the depicted example, to facilitate distributing fracturing fluid from a fracturing fluid source 46 between multiple different wells 14, in some embodiments, a well system 10 may include a header apparatus 58 fluidly connected between the fracturing fluid source 46 and corresponding valve trees 26. In particular, as in the depicted example, to facilitate controlling supply of fracturing fluid from a fracturing fluid source 46 to a header apparatus 58, in some embodiments, a well system 10 may include one or more fluid valves 28 and one or more fluid conduits 40 fluidly connected between the fracturing fluid source 46 and the header apparatus 58.

[0052] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, a header apparatus 58 may be fluidly connected directly to a fracturing fluid source 46 without any other fluid valves 28 connected therebetween.

[0053] In any case, as in the depicted example, to facilitate selectively distributing fracturing fluid from a fracturing fluid source 46 to multiple wells 14, in some embodiments, a header apparatus 58 may generally include a header trunk 60 and multiple header branches 62, which each fluidly connects the header trunk 60 to a corresponding valve tree 26 and includes a fluid valve 28—namely a branch isolating (e.g., isolation) valve 64. In particular, in the depicted example, the header apparatus 58 includes a first header branch 62A, which fluidly connects the header trunk 60 to the first valve tree 26A and includes a first branch isolating (e.g., isolation) valve 64A disposed therebetween, and a second header branch 62B, which fluidly connects the header trunk 60 to the second valve tree 26B and includes a second branch isolating (e.g., isolation) valve 64B disposed therebetween.

[0054] Additionally, as in the depicted example, in some embodiments, a header trunk 60 of a header apparatus 58 may include one or more trunk isolating (e.g., isolation) valves 66, for example, to facilitate supplying appropriately pressurized fracturing fluid to an upstream valve tree 26 with improved efficiency. As an illustrative non-limiting example, to enable fracturing fluid to be supplied to the second valve tree 26B, the trunk isolating valve 66 may be in its open state to enable fracturing fluid to flow to the second header branch 62B. However, when fracturing fluid is to be supplied to the first valve tree 26A, the trunk isolating valve 66 may be in its closed state to block the fracturing fluid from flowing to the second header branch 62B to reduce the volume the fracturing fluid needs to fill and, thus, the time it takes to supply appropriately pressured fracturing fluid to the first valve tree 26A, for example, as compared to merely closing the second branch isolating valve 64B on the second header branch 62B while leaving the header trunk 60 unimpeded (e.g., trunk isolating valve 66 in its open state). In other words, in such embodiments, a header trunk 60 of a header apparatus 58 may include N−1 trunk isolating valves 66 where N is the number of header branches 62 in the header apparatus 58.

[0055] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, a header trunk 60 of a header apparatus 58 may not include a trunk isolating valve 66, for example, when header branches 62 of the header apparatus 58 are sufficiently close together. Additionally, in other embodiments, a header branch 62 of header apparatus 58 may not include a branch isolating valve 64, for example, when the header branch 62 is fluidly connected to a wing valve branch 36 of a corresponding valve tree 26 and, thus, a wing valve 34 can be used as a branch isolating valve 64. Alternatively, in other embodiments, a well system 10 may not include a header apparatus 58, for example, when the well system 10 includes a single well 14 or instead includes a zipper apparatus.

[0056] In any case, as in the depicted example, to facilitate automating operation thereof, a fluid valve 28 in a well system 10 generally includes an automated valve actuator 68, for example, in addition to a manual valve actuator 70 (e.g., handle or wheel) that enables an operator to manually control (e.g., override) operation of the fluid valve 28. In particular, in some embodiments, an automated valve actuator 68 of a fluid valve 28 may be an electromechanical actuator (e.g., motor) and, thus, adjusts the valve state of the fluid valve 28 based on electrical power is supplied thereto. However, in other embodiments, an automated valve actuator 68 of a fluid valve 28 may be a fluid-powered (e.g., hydraulic or pneumatic) actuator and, thus, adjusts the valve state of the fluid valve 28 based on pressurized actuation fluid supplied thereto.

[0057] To help illustrate, an example of a fluid valve 28A, which may be included in a well system 10 and includes a fluid-powered (e.g., hydraulic or pneumatic) valve actuator 68A, is shown in FIG. 2. As in the depicted example, a fluid valve 28 generally includes a valve body 72 that defines a fluid bore 74 through the fluid valve 28. In particular, in the depicted example, the valve body 72 of the fluid valve 28 includes a central spool 76 with side caps 78 secured (e.g., bolted) thereto.

[0058] However, it should be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, a fluid valve 28 in a well system 10 may have a different valve body 72. For example, in other embodiments, the valve body 72 of a fluid valve 28 may be a single integrated component and, thus, not include a central spool 76 and separate side caps 78.

[0059] In any case, as depicted, the fluid-powered valve actuator 68A is secured to the valve body 72. In particular, although obfuscated from view, the fluid-powered valve actuator 68A extends into the valve body 72 such that the fluid-powered actuator is coupled to a flow control component, such as a gate or a ball, disposed within the fluid bore 74 of the fluid valve 28A. Accordingly, actuating the fluid-powered valve actuator 68A may move the flow control component within the fluid bore 74 to transition the fluid valve 28A between an open state and a closed state in an automated manner.

[0060] Nevertheless, as in the depicted example, to enable manual control by an operator, in some embodiments, a fluid valve 28 in a well system 10 may include a manual valve actuator 70, such as a handle or a wheel. In particular, although somewhat obfuscated from view in the depicted example, the manual valve actuator 70 extends through the fluid-powered valve actuator 68A and the valve body 72 such that the manual valve actuator 70 is also coupled to the flow control component of the fluid valve 28A. Accordingly, actuating the manual valve actuator 70 may also move the flow control component within the fluid bore 74 to transition the fluid valve 28A between its open state and its closed state, for example, to enable an operator to manually override automated operation by the fluid-power valve actuator 68A.

[0061] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, a fluid valve 28 in a well system 10 may not include a manual valve actuator 70. In fact, in some embodiments, a subset of fluid valves 28 (e.g., upper master valve 30A) may include a manual valve actuator 70 while a different subset of fluid valves 28 (e.g., lower master valve 30B, wing valve 34, and / or swab valve 32) do not include a manual valve actuator 70.

[0062] In any case, as in the depicted example, to facilitate controlling actuation direction thereof and, thus, the transitioning of a corresponding fluid valve 28 between its open state and its closed state, in some embodiments, a fluid-powered valve actuator 68A may include multiple fluid ports 71—namely an open fluid port 71A and a close fluid port 71B. In particular, when actuation (e.g., pressurized) fluid is supplied to the open fluid port 71A in the depicted example, the fluid-powered valve actuator 68A may actuate the flow control component in a first direction such that the fluid valve 28A transitions away from its closed state toward its open state. On the other hand, when actuation fluid is supplied to the close fluid port 71B in the depicted example, the fluid-powered valve actuator 68B may actuate the flow control component in a second (e.g., opposite) direction such that the fluid valve transition away from its open state toward its closed state.

[0063] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, a fluid-powered valve actuator 68A of a fluid valve 28 may include a single fluid port 71. In such embodiments, the fluid valve 28 may be transitioned away from its open state toward its closed state by supplying actuation fluid to the fluid port 71 and transitioned away from its closed state toward its open state by extracting actuation fluid from the fluid port 71 or vice versa. Additionally or alternatively, as mentioned above, in other embodiments, an automated valve actuator 68 of a fluid valve 28 may be an electromechanical valve actuator 68.

[0064] In any case, as in the example depicted in FIG. 1, to facilitate powering operation of equipment, such as a fluid valve 28 and / or a fluid pump 50, therein, a well system 10 generally includes a power sub-system 80. As depicted, a power sub-system 80 generally includes a power source 82. In particular, in some embodiments, a power source 82 in a power sub-system 80 may be a mechanical power source 82, such as an internal combustion engine. However, in other embodiments, a power source 82 in a power sub-system 80 may be an electrical power source 82, such as an electrical grid and / or an electrical generator.

[0065] In fact, in some embodiments when a power source 82 in its power sub-system 80 is an electrical power source 82, equipment in a well system 10 may nevertheless be mechanically powered. In particular, as in the depicted example, to facilitate mechanically powering equipment using an electrical power source 82, a power sub-system 80 may include a fluid power assembly 84.

[0066] To facilitate pressurizing actuation fluid and, thus, mechanically powering operation of well system equipment, as in the depicted example, a fluid power assembly 84 in a power sub-system 80 may generally include an actuation fluid reservoir (e.g., tank) 86 and a fluid pump 50—namely an actuation fluid pump 50B, which is fluidly coupled between the actuation fluid reservoir 86 and the equipment. Additionally, as in the depicted example, to enable selectively powering operation of different equipment, in some embodiments, a fluid power assembly 84 may include a fluid manifold 88 fluidly coupled between the actuation fluid pump 50B and the equipment as well as one or more fluid valves 28 and one or more fluid conduits 40 fluidly coupled between the fluid manifold 88 and the equipment. In particular, as in the depicted example, a set of one or more fluid valves 28 may be fluidly coupled between the fluid manifold 88 and a corresponding fluid port 90, which is fluidly coupled to a fluid port 71 on a fluid-powered valve actuator 68A of a fluid valve 28 via one or more fluid conduits 40. For example, a first fluid port 90A of the fluid power assembly 84 may be fluidly coupled to an open fluid port 71A on a fluid-powered valve actuator 68A of a fluid valve 28, such as a working (e.g., swab or master) valve in a valve tree 26, while a second fluid port 90B of the fluid power assembly 84 may be fluidly coupled to a close fluid port 71B on the fluid-powered valve actuator 68A of the fluid valve 28.

[0067] Accordingly, in the depicted example, the actuation fluid pump 50B and the fluid valves 28 in the fluid power assembly 84 may operate to selectively supply actuation fluid to a fluid-powered valve actuator 68A of a fluid valve 28 to mechanically power operation of the fluid valve 28. Additionally, in the depicted example, operation of the actuation fluid pump 50B and the fluid valves 28 in the fluid power assembly 84 may be electrically powered by the power source 82. Accordingly, as in the depicted example, in some embodiments, one or more electrical conduits (e.g., wires and / or cables) 92 may be coupled between a power source 82 in a power sub-system 80 and an actuation fluid pump 50B and fluid valves 28 in a fluid power assembly 84 of the power sub-system 80.

[0068] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, the operation (e.g., pumping rate) of equipment, such as a fluid pump 50 and / or a fluid valve 28, in a fluid power assembly 84 may alternatively be controlled using pressurized actuation fluid. Additionally, in other embodiments, equipment, such as a fluid valve 28 and / or a fluid pump 50, in a well system 10 may be electrically powered and, thus, its power sub-system 80 may not include a fluid power assembly 84 and one or more electrical conduits 92 may be coupled between an electrical power source 82 in the power sub-system 80 and the well system equipment. Furthermore, in other embodiments, a power source 82 in a power sub-system 80 that powers well system equipment, such as a fluid valve 28 and / or a fluid pump 50, may be a mechanical power source 82 and, thus, mechanically coupled to the well system equipment, for example, via shafts and / or gears.

[0069] In any case, as in the depicted example, to facilitate controlling operation of well system equipment, in some embodiments, a power sub-system 80 may additionally include a power converter 94 coupled between the power source 82 and the well system equipment. For example, when the power source 82 is an electrical power source, the power converter 94 may be an electrical power converter 94, which operates to adjust voltage, current, magnitude, amplitude, phase, frequency, polarity, and / or the like of electrical power received from the electrical power source 82 before supply to the well system equipment. Alternatively, when the power source 82 is a mechanical power source, the power converter 94 may be a mechanical power converter 94, such as a transmission or gearbox, which operates to adjust velocity, torque, direction, and / or the like of mechanical power received from the mechanical power source 82 before supply to the well system equipment.

[0070] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, a power sub-system 80 in a well system 10 may not include a power converter 94, for example, when operation of its power source 82 is directly controlled to control its output power and, thus, the power supplied to well system equipment.

[0071] In any case, as in the depicted example, to facilitate selectively powering operation of different well system equipment using the same power source 82, in some embodiments, a power sub-system 80 may additionally include a switching assembly 96 coupled between the power source 82 and the well system equipment. For example, when the power source 82 is an electrical power source 82, the switching assembly 96 may be a switchgear assembly, which operates to selectively connect input electrical power to a subset of electrical conduits 92 that each connects to different well system equipment. Alternatively, when the power source 82 is a mechanical power source, the switching assembly 96 may be a gear change assembly, which operates to selectively connect an input gear driven by input mechanical power to a subset of output gears that are each mechanically coupled to different well system equipment.

[0072] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, a switching assembly 96 in a power sub-system 80 may be coupled between a power source 82 and a power converter 94. Alternatively, in other embodiments, a power sub-system 80 in a well system 10 may not include a switching assembly 96, for example, when the power sub-system 80 has a power source 82 dedicated to each piece of well system equipment.

[0073] In any case, as in the depicted example, to facilitate controlling and, thus, at least partially automating operation of equipment therein, a well system 10 generally includes a control sub-system 98. To facilitate communication therewith, as depicted, a control sub-system 98 in a well system 10 generally includes more input / output (I / O) devices 104.

[0074] In particular, in some embodiments, I / O devices 104 of a control sub-system 98 may include one or more input / output (I / O) ports (e.g., terminals), which enable the control sub-system 98 to be communicatively coupled to well system equipment, for example, in addition to one or more sensors 106 via a wired or wireless communication network. Accordingly, as in the depicted example, the I / O devices 104 of a control sub-system 98 may enable the control sub-system 98 to communicate (e.g., output) control signals 108 that instruct well system equipment to perform corresponding control actions. For example, the control sub-system 98 may communicate a control signal 108 that instructs an automated valve actuator 68 to transition a fluid valve 28 from its current open state to a target closed state or vice versa. As another example, the control sub-system 98 may communicate a control signal 108 that instructs a pump actuator (e.g., motor) to transition a fluid pump 50 from a current lower pumping rate (e.g., off) state to a target higher pumping rate (e.g., on) state or vice versa.

[0075] Furthermore, as in the depicted example, in some embodiments, the I / O devices 104 of a control sub-system 98 in a well system 10 may enable the control sub-system 98 to receive sensor signals 110, which are indicative of a current state of the well system 10. In particular, in some such embodiments, a control sub-system 98 may be communicatively coupled to one or more equipment sensors 106A, which operate to return sensor signals 110 indicative of an equipment state of corresponding well system equipment. For example, an equipment sensor 106A associated with a fluid valve 28 may return sensor signals 110 indicative of a current valve state of the fluid valve 28 (e.g., whether fully open state, fully closed state, or intermediate state between fully open state and fully closed state). As another example, an equipment sensor 106A associated with a fluid pump 50 may return sensor signals 110 indicative of a current pumping rate state of the fluid pump 50.

[0076] Additionally or alternatively, in some such embodiments, a control sub-system 98 in a well system 10 may be communicatively coupled to one or more fluid parameter sensors 106B, which operate to return sensor signals 110 indicates of fluid parameters, such as fluid pressure, fluid composition, fluid temperature, and / or the like, within the well system 10. For example, a first (e.g., upstream) fluid parameter sensor 106B, which is coupled immediately upstream from a fluid valve 28 such that no other fluid valves 28 are disposed therebetween, may return sensor signals 110 indicative of fluid parameters flowing into the fluid valve 28 while a second (e.g., downstream) fluid parameter sensor 106B, which is coupled immediately downstream from the fluid valve 28 such that that no fluid valves 28 are disposed therebetween, may return sensor signals 110 indicative of fluid parameters flowing out from the fluid valve 28. As another example, a fluid parameter sensor 106B coupled at an outlet of a fluid pump 50 may return sensor signals 110 indicative of fluid parameters being flowed out of the fluid pump 50.

[0077] Furthermore, in some such embodiments, a control sub-system 98 in a well system 10 may be communicatively coupled to one or more optical sensors 106C, such as a camera, which operate to return sensor signals 110 indicative of a visual representation (e.g., image or video) of a targeted area in the well system 10. For example, an optical sensor 106C focused on (e.g., targeted at) a fluid valve 28 may return sensor signals 110 indicative of a visual representation of the fluid valve 28 to enable an operator to confirm a current valve state of the fluid valve 28 and, thus, whether the fluid valve 28 has achieved its target valve state.

[0078] In fact, as in the depicted example, to facilitate improving visual recognition of its current valve state, in some embodiments, a fluid valve 28 may additionally include a visual indicator 112, such as a flag or arm. In particular, as in the depicted example, a visual indicator 112 may be secured to a (e.g., automated or manual) valve actuator of a fluid valve 28, for example, such that the visual indicator 112 extends radially outward. Accordingly, when the valve actuator actuates (e.g., rotates) to move a corresponding flow control component of the fluid valve 28, the visual indicator 112 may move in a corresponding manner to provide an exaggerated visual indication of the current position of the flow control component and, thus, the current valve state of the fluid valve 28. For example, to provide an exaggerated visual indication of the valve state of a corresponding fluid valve 28, a visual indicator 112 may be in a first (e.g., vertical) orientation while the fluid valve 28 is in its fully open state, a second (e.g., horizontal) orientation while the fluid valve 28 is in its fully closed state, and a third (e.g., slanted) orientation between the first orientation and the second orientation while the fluid valve 28 is in an intermediate valve state.

[0079] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, a fluid valve 28 may not include a visual indicator 112 or utilize a different type of visual indicator, such as a light-emitting diode that emits light while the fluid valve 28 is in a first (e.g., closed) valve state and does not emit light while the fluid valve is in a second (e.g., open and / or different) valve state. Additionally, in some embodiments, a valve tree 26 may include a data acquisition module that gathers sensor signals 110 associated with fluid valves 28 on the valve tree 26, for example, before relaying the sensor signals 110 to a central controller in a control sub-system 98.

[0080] In any case, as in the depicted example, to facilitate analyzing sensor signals 110 and / or generating control signals 108 and, thus, controlling operation of a well system 10, a control sub-system 98 therein generally includes one or more processors 114 and memory 116. In particular, memory 116 in a control sub-system 98 generally includes one or more tangible, non-transitory, computer-readable media that are implemented and / or operated to store data and / or executable instructions. For example, as will be described in more detail below, the memory 116 may store an operation schedule and / or an operation log for a corresponding well system 10. As another example, the memory 116 may store sensor data, such as equipment states, fluid parameters, and / or image data, based on one or more sensor signals 110. Accordingly, in some embodiments, the memory 116 may include volatile memory, such as random-access memory (RAM), and / or non-volatile memory, such as read-only memory (ROM), flash memory, one or more solid-state drives (SSDs), one or more hard disk drives (HDDs), or any combination thereof.

[0081] Additionally, a processor 114 in a control sub-system 98 may generally include processing circuitry that is implemented and / or operated to process data and / or execute instructions stored in memory 116. For example, the processor 114 may process operational parameters associated with well system equipment to determine a current equipment state of the well system equipment and, as will be described in more detail below, may process fluid parameters stored in memory 116 to secondarily confirm the current equipment state of the well system equipment. As another example, to automate operation of well system equipment, the processor 114 may process a current equipment state of the well system equipment relative to an operation schedule stored in memory 116 to generate control signals 108 that instruct performance of a control action step that adjusts the well system equipment from its current equipment state to a target (e.g., different) equipment state. Accordingly, in some embodiments, a processor 114 in a control sub-system 98 may include one or more general purpose microprocessors, one or more application specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs), or any combination thereof.

[0082] In any case, in addition to I / O ports, to enable communication with an operator (e.g., user), I / O devices 104 of a control sub-system 98 may include one or more user output devices and one or more user input devices. In particular, in some embodiments, a user output device of a control sub-system 98 may include an electronic display, for example, which is implemented and / or operated to display a graphical user interface (GUI) that provides a visual representation of an equipment state, a visual representation of a fluid parameter, a prompt for response, and / or an image of well system equipment. Additionally, in some embodiments, a user input device of a control sub-system 98 may include one or more hard buttons, one or more soft buttons (e.g., touch sensor), one or more microphones, one or more keyboards, one or more cameras, and / or one or more mice, for example, which enable an operator to respond to a prompt and / or to request a change to an equipment state.

[0083] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, as mentioned above, to produce fluid from a well 14 in a well system 10, multiple different parties and, thus, corresponding operator groups may need to perform operations in the well system 10. Additionally, as mentioned above, at least in some instances, improper coordination between different operations in a well system 10 may potentially limit operational efficiency (e.g., production time) of the well system 10, for example, due to corrective actions needing to be performed before normal operation can resume. Accordingly, although depicted as a single block in FIG. 1, the control sub-system 98 of a well system 10 may in fact be distributed between multiple operators and, thus, multiple operator devices.

[0084] To help illustrate, an example of a distributed control sub-system 98A that may be included in a well system 10 is shown in FIG. 3. As depicted, the distributed control sub-system 98A generally includes multiple operator devices 120. In particular, in the depicted example, a first operator device 120A and an Nth operator device 120N are each a mobile device, such as a mobile phone, a tablet computer, a laptop computer, or the like. On the other hand, in the depicted example, a second operator device 120B is a human-machine interface (HMI) mounted on a skid 123.

[0085] Additionally, to facilitate properly and efficiently coordinating operations of multiple different parties and, thus, corresponding operator groups, in some embodiments, an operator device 120 may be assigned to and associated with a representative operator of an operator group. For example, in the depicted example, the first operator device 120A may be assigned to and associated with a representative wireline operator, the second operator device 120B may be assigned to and associated with a representative service technician, and the Nth operator device 120N may be assigned to and associated with a representative well owner's operator.

[0086] However, it should be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, an operator device 120 assigned to and associated with a service technician may be a mobile device. Additionally or alternatively, in other embodiments, an operator device 120 assigned to and associated with a wireline operator or a well owner's operator may be a human-machine interface (HMI) mounted on a skid 123. Furthermore, in other embodiments, a control sub-system 98A may only include two operator devices 120, for example, when only two operator groups are expected to operate in a well system 10. Alternatively, in other embodiments, a control sub-system 98A may include more than three (e.g., four, five, or more) operator devices 120, for example, when more than three operator groups are expected to operate in a well system 10 (e.g., with a third operator device 120 assigned to and associated with a pressure pumper).

[0087] In any case, as in the depicted example, to facilitate properly and efficiently coordinating requests received from and / or performance of operations associated with different operators, a distributed control sub-system 98A generally includes a central controller 118, which is communicatively coupled to each of the operator devices 120 via a (e.g., wired and / or wireless) communication network 122. In particular, a central controller 118 in a distributed control sub-system 98A may generally coordinate operations in a well system 10 in accordance with an operation schedule (e.g., recipe) 124, for example, which is stored in memory 116.

[0088] Generally, an operation schedule 124 for a well system 10 may indicate a target order and / or a target duration of operations to be performed in the well system 10. For example, the operation schedule 124 may indicate that a first valve tree operation, which transitions a valve tree 26 to a perforation valve configuration, is to be performed before a perforation operation and that a second valve tree operation, which transitions the valve tree 26 to a fracturing valve configuration is to be performed before a hydraulic fracturing operation. As another example, the operation schedule 124 may indicate that a third valve tree operation, which transitions the valve tree 26 to a shut-in valve configuration, is to be performed between the perforation operation and the second valve tree operation.

[0089] Additionally, to facilitate automating performance of an operation that includes multiple control action steps, in some embodiments, an operation schedule 124 for a well system 10 may indicate a target order of the control action steps, a target duration of each control action step, and / or a target equipment state to be achieved in each control action step. For example, to facilitate automating performance of a valve tree operation that transitions a valve tree 26 to a perforation valve configuration, the operation schedule 124 may indicate that a first working (e.g., swab or master) valve 28 is to be transitioned to its open state in a first (e.g., initial) control action step and a second working (e.g., swab or master) valve 28 is to be transitioned to its open state in a second (e.g., subsequent) control action step.

[0090] As another example, to facilitate automating performance of a valve tree operation that transitions a valve tree 26 to a fracturing valve configuration, the operation schedule 124 may indicate that a swab (e.g., top) valve 32 on the valve tree 26 is to be transitioned to its closed state in a first (e.g., initial) control step, a corresponding isolating valve (e.g., branch isolating valve 64 on corresponding header branch 62 and / or fluid valve 28 fluidly coupled between a fracturing fluid source 46 and the valve tree 26) is to be transitioned to its open state in a second (e.g., subsequent) control action step, and a master valve 30 on the valve tree 26 is to be transitioned to its open state in a third (e.g., further subsequent) control action step. As a further example, to facilitate automating performance of a valve tree operation that transitions a valve tree 26 to a shut-in valve configuration, the operation schedule 124 may indicate that a first working (e.g., swab or master) valve 28 is to be transitioned to its closed state in a first (e.g., initial) control action step and a second working (e.g., swab or master) valve 28 is to be transitioned to its closed state in a second (e.g., subsequent) control action step.

[0091] Additionally, to facilitate adaptively adjusting automated performance of an operation, in some embodiments, an operation schedule 124 may include a sequential performance (e.g., execution) parameter associated with the operation. In particular, when the sequential performance parameter associated with an operation is set, the control sub-system 98 may perform control action steps of the operation in a sequential mode such that a subsequent control action step is initiated after a preceding control action step is completed. On the other hand, when the sequential performance parameter is not set (e.g., default), the control sub-system 98 may perform control action steps of the operation in an expedited mode by initiating the control action steps in rapid succession (e.g., substantially simultaneously) such that a subsequent control action step is initiated before a preceding control action step is completed.

[0092] Alternatively, to facilitate adaptively adjusting performance of an operation, in other embodiments, an operation schedule 124 may include an expedited performance (e.g., execution) parameter associated with the operation. In particular, when the expedited performance parameter associated with an operation is set, the control sub-system 98 may perform control action steps of the operation in an expedited mode by initiating the control action steps in rapid succession (e.g., substantially simultaneously) such that a subsequent control action step is initiated before a preceding control action step is completed. On the other hand, when the expedited performance parameter is not set (e.g., default), the control sub-system 98 may perform control action steps of the operation in a sequential mode such that a subsequent control action step is initiated after a preceding control action step is completed.

[0093] Furthermore, in some embodiments, an operation schedule 124 may indicate a type parameter associated with an operation, for example, to facilitate operator selection and / or association with unique rules (e.g., criteria). As an illustrative non-limiting example, a type parameter associated with an operation in an operation schedule 124 may indicate whether the operation is a hydraulic fracturing operation, whether the operation is a perforation (e.g., wireline) operation, and / or whether the operation is another type of operation, such as a production operation or a valve tree operation.

[0094] In any case, as in the depicted example, to facilitate communication with an operator, the I / O devices 104 of each operator device 120 generally include a user output device 104—namely an electronic display 104A—and a user input device 104B, such as one or more hard buttons, one or more soft buttons (e.g., touch sensor), one or more microphones, one or more cameras, one or more keyboards, and / or one or more mice. In particular, an electronic display 104A of an operator device 120 may generally display a graphical user interface (GUI) that provides an operator with a visual representation of information relevant to a corresponding well system 10. For example, an electronic display 104A of an operator device 120 may indicate a (e.g., current or target) equipment state and / or a (e.g., current or target) fluid parameter in the well system 10. As another example, in some embodiments, an electronic display 104A of an operator device 120 may display a prompt that requests a corresponding operator to approve performance of a next operation associated with a different operator group.

[0095] However, at least in some instances, different operator groups that operate on the same well 14 may not have a contractual relationship with one another and, thus, may be independent third parties. For example, a wireline operator, a service technician, and a pressure pumper may each have a contractual relationship with a well owner, but not with one another. In other words, at least in some instances, a first (e.g., wireline) operator may not have the authority to control or approve operations associated with a second operator (e.g., service technician or pressure pumper). Accordingly, in other embodiments, an electronic display 104A of an operator device 120 may display a prompt that requests a corresponding operator to confirm completion of their preceding operation. As another example, in some embodiments, an electronic display 104A of an operator device 120 may inform an operator of a subsequent operation that will be performed next after the operator confirms completion of their preceding operation, for example, as a prompt that requests that the operator explicitly acknowledge that the subsequent operation (e.g., in addition to the specific control actions included therein) will be performed next (e.g., to provide an additional check that further facilitates reducing the likelihood of issues arising when transitioning between operations). As a further example, in some embodiments, an electronic display 104A of an operator device 120 may display a prompt that requests that a corresponding operator finalize or re-confirm their request to perform an operation, for example, after a different operator has confirmed completion of their preceding operation to enable the operator to cancel their request (e.g., in view of changes to well system and / or environmental conditions).

[0096] In any case, a user input device 104B of an operator device 120 may generally enable an operator to interact with a corresponding well system 10. For example, in some embodiments, a user input device 104B of an operator device 120 may enable an operator to request that well system equipment change from a current equipment state to a target (e.g., different) equipment state to perform a control action step in an operation. However, as will be described in more detail below, to facilitate reducing the likelihood of operator (e.g., human and / or user) error, in other embodiments, a central controller 118 may merely enable an operator to request that a well system 10 perform the operation as a whole and the well system 10 may automatically execute control action steps of the operation when appropriate, for example, instead of enabling the operator to control individual well system equipment from their operator device 120.

[0097] As another example, to facilitate appropriately coordinating operations of different operators, in some embodiments, a user input device 104B of an operator device 120 may enable a first operator to approve performance of a next operation associated with a second operator, for example, in response to a prompt on the electronic display 104A of their operator device 120. In such embodiments, a central controller 118 may lockout performance of the second operator's next operation via their operator device 120 until approval is received from the first operator.

[0098] However, as discussed above, at least in some instances, different operators that operate on the same well 14 may be independent third parties and, thus, an operator may not have the authority to control or approve operations performed by a different operator group. Accordingly, to facilitate appropriately coordinating operations of different operators, in other embodiments, a user input device 104B of an operator device 120 may enable a first operator to confirm completion of their preceding operation, for example, in response to a prompt on the electronic display 104A of their operator device 120. In particular, in some such embodiments, a central controller 118 may lockout performance of a second operator's next operation via their operator device 120 until completion confirmation of a preceding operation is received from the first operator, for example, and the first operator acknowledges that the next operation will be performed after their preceding operation and a requesting (e.g., second or well owner's) operator, subsequently, finalizes or re-confirms their request to perform the next operation.

[0099] To facilitate traceability, in some embodiments, a central controller 118 may keep an operation log 126, for example, in memory 116. In particular, in some such embodiments, an operation log 126 may track when an operator approved performance of a next operation of another operator and when the other operator actually performed their next operation, for example, in addition to when performance of the next operation was requested. However, in other such embodiments, an operation log 126 may track when an operator confirmed completion of their preceding operation and when another operator performed their subsequent operation, for example, in addition to when the operator acknowledged that the subsequent operation will be performed next, when a requesting (e.g., other or well owner's) operator requested performance of the subsequent operation, and / or when the requesting operator subsequently finalized or re-confirmed their request to perform the subsequent operation.

[0100] Accordingly, in such embodiments, if an issue that requires corrective action occurs in a well system 10, a corresponding operation log 126 may be referenced to identify a potential coordination breakdown that caused the issue, for example, to help avoid the issue in the future and / or to assign responsibility. In fact, to facilitate avoiding an issue that occurred during a previous cycle of an operation schedule 124, in some embodiments, a central controller 118 may adaptively adjust the operation schedule 124 before using the operation schedule 124 during a subsequent cycle. For example, when a pervious cycle of the operation schedule 124 resulted in a first operation, which was performed before or concurrently with a second operation, inadvertently disrupting performance of the second operation, the central controller 118 may adaptively adjust the operation schedule 124 to require that the first operation be performed after completion of the second operation during a subsequent cycle of the operation schedule 124.

[0101] In any case, once a lockout is removed from an operator of a well system 10, a central controller 118 may permit performance of the operator's next operation in the well system 10 from their operator device 120. In particular, in some embodiments, the central controller 118 may remove a lockout from an operator to enable the operator to perform their next operation by controlling the operation of individual well system equipment from their operator device 120. For example, when performance of a valve tree operation that transitions a valve tree 26 to a fracturing valve configuration is permitted, the central controller 118 may remove a lockout from a service technician to permit the service technician to instruct, via their operator device 120, a swab (e.g., top or crown) valve 32 on the valve tree 26 to transition to its closed state, instruct a corresponding isolating valve (e.g., branch isolating valve 64 on a corresponding header branch 62 and / or fluid valve 28 fluidly coupled between a fracturing fluid source 46 and the valve tree 26) to transition to its open state, and instruct a master (e.g., working) valve 30 on the valve tree 26 to transition to its open state.

[0102] However, since an operation may include multiple control action steps, in other embodiments, to facilitate reducing the likelihood of operator error and, thus, improving well system operational efficiency, a central controller 118 may keep an operator locked out from controlling operation of individual well system equipment even after performance of the operator's next operation is permitted. Instead, in some such embodiments, a central controller 118 may merely enable an operator to instruct performance of their next permitted operation as a whole and the central controller 118 may automatically control operation of well system equipment to perform control action steps of the operation. For example, the central controller 118 may merely enable a service technician to request performance of a valve tree operation as a whole from their operator device 120 and, when performance is permitted, automatically instruct a swab valve 32 on a valve tree 26 to transition to its closed state, automatically instruct a corresponding isolating valve (e.g., branch isolating valve 64 on corresponding header branch 62 and / or fluid valve 28 fluidly coupled between a fracturing fluid source 46 and the valve tree 26) to transition to its open state, and automatically instruct a master (e.g., working) valve 30 on the valve tree 26 to transition to its open state.

[0103] In fact, to facilitate improving changeover between different operations and, thus, further improving well system operational efficiency, in some embodiments, a central controller 118 may automatically initiate performance of an operation when appropriate, for example, instead of waiting for an operator to explicitly request or instruct performance. In particular, in some such embodiments, a central controller 118 may automatically begin determining when performance of an operator's next operation is appropriate upon receiving the operator's completion confirmation for their preceding operation. For example, upon receiving confirmation from a pressure pumper that a fluid preparation (e.g., blending and / or mixing) operation is complete, the central controller 118 may automatically begin determining whether performance of a hydraulic fracturing operation is appropriate.

[0104] In any case, as in the depicted example, in some embodiments, well system equipment may include its own equipment controller 128. Accordingly, to perform an operation in such embodiments, a central controller 118 may relay instructions to an equipment controller 128 and the equipment controller 128 may then control the operation of corresponding well system equipment accordingly.

[0105] However, it should again be appreciated that the depicted example is merely intended to be illustrative and not limiting. In particular, in other embodiments, well system equipment may not have its own equipment controller 128 and, thus, a central controller 118 may directly control operation of the well system equipment. In any case, in this manner, a distributed control sub-system 98A in a well system 10 may facilitate properly and efficiently coordinating operations of different operators in the well system 10, which, at least in some instances, may facilitate improving operational efficiency (e.g., production time) of the well system 10, for example, by enabling different operators to work at least partially in parallel while accounting for the actual relationship between different operators and reducing corrective actions needed due to improper coordination between the different operators.

[0106] To help further illustrate, an example of a process 130 for coordinating performance of operations in a well system 10 is described in FIG. 4. Generally, the process 130 includes locking out operators (process block 131), permitting performance of a first operation (process block 132), receiving a request to perform a next operation of an operator (process block 134), and determining whether a different operator has confirmed completion of a preceding operation (decision block 136). Additionally, when the different operator has not confirmed completion of the preceding operation, the process 130 generally includes maintaining the operator locked out to block performance of the next operation from an operator device (process block 137) and indicating that performance of the next operation is not yet permitted (process block 138). On the other hand, when the different operator has confirmed completion of the preceding operation, the process 130 generally includes indicating that the next operation is permitted for performance (process block 140), determining whether any operations remain (decision block 142), and locking out the operators when no operations remain (process block 144).

[0107] However, it should be appreciated that the example process 130 is merely intended to be illustrative and not limiting. In particular, in other embodiments, a process 130 for coordinating operations in a well system 10 may omit one of the or more depicted process blocks or decision blocks. Additionally or alternatively, in some embodiments, a process 130 for coordinating performance of operations in a well system 10 may include one or more additional process blocks and / or one or more additional decision blocks. For example, in some embodiments, the process 130 may additionally include automatically performing the first operation (process block 145) and / or requesting that the different operator confirm completion of the preceding operation (process block 146). As another example, in some embodiments, the process 130 may additionally include requesting that the different operator acknowledge the next operation (process block 147) and determining whether the different operator has acknowledged the next operation (decision block 149). As a further example, in some embodiments, the process 130 may additional include requesting that a requesting operator reconfirm the request to perform the next operation (process block 151) and determining whether the requesting operator has reconfirmed the request to perform the next operation (decision block 153). As another example, the process 130 may additionally include determining whether a request timeout has been reached when the different operator has not confirmed completion of the preceding operation (decision block 150) and / or automatically performing the next operation when the different operator has confirmed completion of the preceding operation (process block 152).

[0108] Additionally, in some embodiments, a process 130 for coordinating performance of operations in a well system 10 may be performed at least in part by executing instructions stored in one or more tangible, non-transitory, computer-readable media, such as control sub-system memory 116, using processing circuitry, such as one or more control sub-system processors 114. In other words, in some embodiments, the process 130 may be performed at least in part by a control sub-system 98, such as a distributed control sub-system 98A (e.g., central controller 118 and multiple operator devices 120), of a well system 10.

[0109] Accordingly, to coordinate performance of operations by different operators in a well system 10, a control sub-system 98 may initially place a lockout on all operators (process block 131). In particular, the control sub-system 98 may place a lockout on an operator to block the operator from controlling the operation of equipment, such as a fluid valve 28 or a fluid pump 50, in the well system 10 from their operator device 120.

[0110] The control sub-system 98 may then permit performance of a first operation in the well system 10, for example, in accordance with an operation schedule 124 (process block 132). In particular, in some embodiments, the control sub-system 98 may remove a lockout from a corresponding operator to enable the operator to perform the first operation by controlling operation of individual well system equipment from their operator device 120 (process block 154). For example, to perform a valve tree operation that transitions a valve tree 26 to a perforation valve configuration, the control sub-system 98 may remove a lockout from a service technician to enable the service technician to instruct, via their operator device 120, that each working (e.g., swab or master) valve 28 on a corresponding valve tree 26 transition to its open state. As another example, to perform a valve tree operation that transitions the valve tree 26 to a fracturing valve configuration, the control sub-system 98 may remove a lockout from the service technician to enable the service technician to instruct, via their operator device 120, that a swab (e.g., top or crown) valve 32 on the valve tree 26 transition to its closed state and that each master valve 30 on the valve tree 26 transition to its open state. As a further example, to perform a valve tree operation that transitions the valve tree 26 to a shut-in valve configuration (e.g., between perforation valve configuration and fracturing valve configuration), the control sub-system 98 may remove a lockout from the service technician to enable the service technician to instruct, via their operator device 120, that each working (e.g., swab or master) valve 28 on the valve tree 26 transition to its closed state.

[0111] However, to facilitate reducing operator error and, thus, improving well system operational efficiency, in other embodiments, the control sub-system 98 may automatically perform the first operation in the manner described in more detail below without removing the lockout from the corresponding operator (process block 145). In other words, in such embodiments, the control sub-system 98 may keep an operator locked out even while a corresponding operation is permitted for performance in the well system 10.

[0112] Moreover, although some operations may need to be sequentially performed on a well 14, in some embodiments, to facilitate improving well system operational efficiency, multiple different operators may nevertheless work at least partially in parallel. In other words, in such embodiments, multiple different operators may concurrently perform their first operations. For example, although a hydraulic fracturing operation is generally performed on a well 14 after a perforation operation, a pressure pumper may perform a fluid preparation operation while a wireline operator is performing the perforation operation.

[0113] In any case, the control sub-system 98 may then receive a request to perform a next operation of an operator (process block 134), for example, from the operator or a well owner's operator. In particular, in some embodiments, an operator may explicitly request an adjustment to an equipment state of individual well system equipment from their operator device 120. For example, to perform a valve tree operation, an operator may explicitly request that a fluid valve 28 on a valve tree 26 transition from its current valve state to a target (e.g., different) valve state via their operator device. Accordingly, in such embodiments, a central controller 118 of the control sub-system 98 may receive an explicit request from an operator to change an equipment state of individual well system equipment, such as fluid valve 28 or a fluid pump 50, from a corresponding operator device 120, for example, via a communication network 122 (process block 156).

[0114] However, as described above, to perform an operation, at least in some instances, multiple different pieces of well system equipment may need to be controlled. In fact, at least in some such instances, multiple pieces of well system equipment may need to be controlled to perform sequential control action steps in an operation. For example, to perform a valve tree operation that transitions a valve tree 26 to a fracturing valve configuration, a swab (e.g., top or crown) valve 32 on the valve tree 26 may be transitioned to its closed state in a first control step, a corresponding isolating valve (e.g., branch isolating valve 64 on corresponding header branch 62 and / or fluid valve 28 fluidly coupled between a fracturing fluid source 46 and the valve tree 26) may be transitioned to its open state in a second (e.g., subsequent) control action step, and a master valve 30 on the valve tree 26 may be transitioned to its open state in a third (e.g., further subsequent) control action step. Accordingly, in some embodiments, to perform the valve tree operation, a service technician may explicitly request, via their operator device 120, that the swab valve 32 be transitioned to its closed state to perform the first control action step before explicitly requesting that the isolating valve be transitioned to its open state to perform the second control step and explicitly requesting that the master valve 30 be transitioned to its open state to perform the third control action step.

[0115] However, despite being performed by the same operator, in some instances, improper coordination between control action steps in an operation may nevertheless occur and potentially cause issues in a well system 10 that require corrective action before normal operation can resume, thereby potentially limiting operational efficiency (e.g., production time) of the well system 10. For example, transitioning a fracturing fluid pump 50A to an on (e.g., pumping) state before a fluid valve 28 coupled between the fracturing fluid pump 50A and a valve tree 26 has achieved its open state may inadvertently deadhead the fracturing fluid pump 50A, which, at least in some instances, may reduce the lifespan of the fracturing fluid pump 50A and, thus, increase the frequency of corrective actions (e.g., swapping out fracturing fluid pumps 50). As another example, transitioning the fracturing fluid pump 50A to its on state when the fluid valve 28 has achieved its open state but a swab (e.g., top or crown) valve 32 on the valve tree 26 has not achieved its closed state may result in fracturing fluid inadvertently leaking to the surrounding environment and, thus, potentially necessitate corrective actions (e.g., environmental cleanup) before normal operation can resume.

[0116] Accordingly, to facilitate reducing operator error and, thus, improving well system operational efficiency, in other embodiments, a central controller 118 may instead merely permit an operator to request performance of an operation as a whole from their operator device 120 and, thus, receive a request to perform the next operation as a whole from the operator's operator device 120, for example, via a communication network 122 (process block 158). As an illustrative non-limiting example, the control sub-system 98 may permit an operator to request performance of a valve tree operation as a whole from their operator device 120, but not permit the operator to request that an individual fluid valve 28 change to a different valve state. As will be described in more detail below, in such embodiments, once an operation is permitted for performance, the control sub-system 98 may automatically perform the operation while keeping a corresponding operator locked out, which, at least in some instances, may facilitate reducing the likelihood of operator error resulting in improper coordination between control action steps in the operation and, thus, improving well system operational efficiency.

[0117] In fact, to facilitate expediting change over between different operations and, thus, further improving well system operational efficiency, in some embodiments, the control sub-system 98 may preemptively (e.g., automatically) request performance of an operator's next operation when the operator confirms completion of their preceding operation, for example, instead of waiting for an explicit request to perform the operator's next operation (process block 160). As an illustrative non-limiting example, the control sub-system 98 may preemptively request performance of a hydraulic fracturing operation once a pressure pumper confirms completion of a fluid preparation operation.

[0118] In any case, before permitting performance of an operator's next operation, the control sub-system 98 may determine whether a different operator has confirmed completion of their preceding operation, for example, in accordance with an operation schedule 124 (decision block 136). In particular, to facilitate proper coordination, the control sub-system 98 may determine whether completion confirmation has been received from each operator that performs a preceding operation that may be inadvertently affected by performance of the operator's next operation and, thus, potentially multiple different operators. For example, before permitting performance of a valve tree operation that transitions a valve tree 26 away from a wireline valve configuration (e.g., to a shut-in configuration), the control sub-system 98 may determine whether a wireline operator has confirmed completion of a perforation operation. As another example, before permitting performance of a valve tree operation that transitions a valve tree 26 away from a fracturing valve configuration, the control sub-system 98 may determine whether a fracturing operator has confirmed completion of a hydraulic fracturing operation.

[0119] That is, at least in some embodiments, the control sub-system 98 may receive and / or request completion confirmations from different operators for different next operations in the well system 10. In other words, in such embodiments, completion confirmations requested and / or received for a next operation may depend on and, thus, vary with the configuration of equipment, such as fluid valves 28 and / or fluid pumps 50, in the well system 10. In some embodiments, equipment configuration of the well system 10 may be manually input (e.g., set up) into the control sub-system 98 by an operator. However, to facilitate easing setup, in other embodiments, the control sub-system 98 may automatically determine and set up equipment configuration based on a (e.g., schematic) drawing of the well system 10.

[0120] To facilitate expediting completion confirmation and, thus, change over from the different operator's preceding operation to the operator's next operation, in some embodiments, the control sub-system 98 may explicitly request that the different operator confirm completion of their preceding operation, for example, in response to a request to perform the operator's next operation (process block 146). In particular, in some such embodiments, the control sub-system 98 may display a prompt on an electronic display 104A of the different operator's operator device 120 that requests that the different operator confirm completion of their preceding operation (process block 161). For example, the control sub-system 98 may display a prompt on the operator device 120 of a wireline operator requesting that the wireline operator confirm completion of a perforation operation.

[0121] To facilitate further reducing the likelihood of issues arising when switching to a subsequent operation associated an operator from a preceding operation associated with a different operator and / or improving operator accountability, in some embodiments, before permitting performance of the next operation, the control sub-system 98 may additionally determine whether the different operator has acknowledged that the subsequent operation will be performed next (decision block 149). In particular, in some such embodiments, the control sub-system 98 may merely inform the different operator of the subsequent operation that is to be performed next when the different operator is requested or prompted to confirm completion of their preceding operation. Accordingly, in such embodiments, the control sub-system 98 enables the different operator to block performance of the subsequent operation by not confirming completion of their preceding operation when the preceding operation is in fact complete, for example, when the different operator foresees an issue with performing the subsequent operation despite their preceding operation being complete.

[0122] However, to facilitate providing an accurate operational status of a well system 10, in other such embodiments, the control sub-system 98 may separately request that the different operator associated with the preceding operation explicitly acknowledge that the specific subsequent operation will be performed next, for example, in addition to the specific control actions included in the subsequent operation (process block 147). In particular, in such embodiments, the control sub-system 98 may display a prompt on an electronic display 104A of the different operator's operator device 120 that requests that the different operator acknowledge that a specific subsequent operation will be performed next (process block 163). For example, the control sub-system 98 may display a prompt on the operator device 120 of a wireline operator requesting that the wireline operator acknowledge that a valve tree operation, which transitions a valve tree 26 away from a wireline valve configuration, will be performed next.

[0123] To facilitate better accounting for potential well condition changes, in some embodiments, before permitting performance of the next operation, the control sub-system 98 may additionally determine whether a requesting operator has reconfirmed or finalized their request to perform the next operation (decision block 153). In particular, in such embodiments, after the different operator has confirmed completion of their preceding operation, the control sub-system 98 may request that the requesting operator finalize or reconfirm their request to perform the next operation (process block 151), for example, by displaying a prompt on their operator device 120 that requests reconfirmation or finalization of the request to perform the next operation (process block 165), and cancel the request if the requesting operator does not finalize or reconfirm their request. In other words, in such embodiments, after completion confirmation of the preceding operation, the control sub-system 98 may provide the requesting operator an opportunity to cancel their request, for example, in view of well condition changes between when the next operation was requested and when completion confirmation of the preceding operation was received.

[0124] In any case, when the different operator has not yet confirmed completion of their preceding operation, the control sub-system 98 may maintain the lockout on an operator to block the operator from performing their next operation from their operator device 120 (process block 137). In other words, the control sub-system 98 may maintain the lockout on the operator to block the operator from controlling well system equipment from their operator device 120, for example, by greying out an option on their operator device 120 to instruct the well system equipment to transition to a different equipment state (process block 162).

[0125] Additionally, when the different operator has not yet confirmed completion of their preceding operation, the control sub-system 98 may indicate that performance of the operator's next operation is not yet permitted (process block 138). In particular, in some embodiments, the control sub-system 98 may notify a requesting operator that performance of a next operation is not yet permitted by displaying a message on their operator device 120 (process block 164) so that the requesting operator can re-request performance of the next operation at a later time (arrow 166).

[0126] However, to facilitate reducing the number of times performance of a next operation needs to be re-requested, in some embodiments, the control sub-system 98 may utilize a request timeout (e.g., time threshold). In other words, in such embodiments, instead of immediately indicating that an operator's next operation is not yet permitted, the control sub-system 98 may determine whether a request timeout has been reached (e.g., elapsed) (decision block 150), continue checking for the different operator's completion confirmation until the request timeout is reached (arrow 166), and only indicate that the operator's next operation is not yet permitted once the request timeout has been reached but the different operator has not yet confirmed completion of their preceding operation.

[0127] In any case, after the different operator has confirmed completion of their preceding operation, the control sub-system 98 may indicate that performance of the operator's next operation is now permitted, for example, by displaying a message on the operator's operator device 120 and / or in addition to placing a lockout back on the different operator (process block 140). In particular, in some embodiments, the control sub-system 98 may remove a lockout from the operator to enable the operator to perform their next operation by controlling individual well system equipment from their operator device 120, for example, by enabling selection of (e.g., un-greying) an option that instructs the well system equipment to transition to a different equipment state (process block 168). Nevertheless, before removing a lockout on an operator to enable the operator to perform an operation, in some such embodiments, the control sub-system 98 may request that a requesting operator finalize or re-confirm their request to perform the operation (e.g., by displaying a prompt on the requesting operator's operator device 120) and cancel the request if the requesting operator does not finalize or reconfirm their request. In other words, in such embodiments, after completion confirmation of the preceding operation, the control sub-system 98 may provide the requesting operator an opportunity to cancel their request, for example, in view of well condition changes between when the next operation was requested and when completion confirmation of the preceding operation was received.

[0128] In any case, to facilitate improving well system operational efficiency, in other embodiments, the control sub-system 98 may automatically perform the operator's next operation once the different operator has confirmed completion of their preceding operation, for example, and the requesting operator has finalized or re-confirmed their request to perform the next operation (process block 152). In particular, in some such embodiments, while their next operation is permitted for performance, the control sub-system 98 may nevertheless keep the operator locked out (process block 170). In other words, in such embodiments, even while their next operation is permitted for performance, the control sub-system 98 may block the operator from controlling individual well system equipment from their operator device 120, which, at least in some instances, may facilitate further reducing the likelihood of operator error and, thus, further improving well system operation efficiency.

[0129] To help illustrate, an example of a process 172 for automatically performing an operation in a well system 10 is described in FIG. 5. Generally, the process 172 includes instructing performance of a control action step in an operation (process block 174) and determining whether a sequential performance parameter is set (decision block 173). Additionally, when the sequential performance parameter is set, the process 172 generally includes determining whether an equipment sensor indicates that a target equipment state has been achieved (decision block 176), determining whether a sensor timeout has been reached (decision block 178), determining whether a control action step remains in the operation (decision block 180), and indicating completion of the operation when no control action step remains (process block 182).

[0130] On the other hand, when the sequential performance parameter is not set, the process 172 generally includes determining whether a control action step remains in the operation (decision block 175), instructing performance of a remaining control action step (arrow 177), and, when no control action step remains in the operation, determining whether sensors indicate that each target equipment state has been achieved (decision block 179), determining whether a target equipment state is secondarily confirmed (decision block 181), ceasing performance of the operation when achievement of each target equipment state is not confirmed by the sensors and is not secondarily confirmed (process block 186), and indicating completion of the operation when achievement of each target equipment state is confirmed by the sensors or secondarily confirmed (process block 182).

[0131] However, it should be appreciated that the example process 172 is merely intended to be illustrative and not limiting. In particular, in other embodiments, a process 172 for automatically performing an operation in a well system 10 may include one or more additional process blocks and / or one or more additional decision blocks. For example, when the sequential performance parameter is set, in some embodiments, the process 172 may additionally include determining whether the target equipment state is secondarily confirmed when the equipment sensor does not indicate that the target equipment state has been achieved and the sensor timeout has been reached (decision block 184), ceasing performance of the operation when the target equipment state is not secondarily confirmed (process block 186), and indicating that the sensor is potentially faulty when the sensor timeout is reached and the target equipment state is secondarily confirmed (process block 188). As another example, when the sequential performance parameter is not set, in some embodiments, the process 172 may additionally include determining whether an operation timeout has been reached (decision block 183) and indicating that a sensor is potentially faulty when the operation timeout is reach and a corresponding target state is secondarily confirmed (process block 185).

[0132] Additionally, in some embodiments, a process 172 for automatically performing an operation in a well system 10 may be performed at least in part by executing instructions stored in one or more tangible, non-transitory, computer-readable media, such as control sub-system memory 116, using processing circuitry, such as one or more control sub-system processors 114. In other words, in some embodiments, the process 172 may be performed at least in part by a control sub-system 98, such as a distributed control sub-system 98A (e.g., central controller 118 and multiple operator devices 120), of a well system 10.

[0133] Accordingly, to automatically perform an operation in a well system 10, a control sub-system 98 may instruct performance of a control action step in the operation that changes well system equipment, such as a fluid valve 28 or a fluid pump 50, from its current equipment state to a target equipment state in accordance with an operation schedule 124, for example, which is stored in memory 116 (process block 174). In particular, in some embodiments, the control sub-system 98 may simply instruct the well system equipment to execute a control action step via one or more control signals 108, for example, when the well system equipment includes its own equipment controller 128 (process block 187).

[0134] However, in other embodiments, to control well system equipment, the control sub-system 98 may control the power a power sub-system 80 of the well system 10 supplies to the well system equipment, for example, via one or more control signals 108. In particular, in some such embodiments, the control sub-system 98 may instruct the power sub-system 80 to adjust electrical power supplied from an electrical power source 82 to the well system equipment, for example, via an electrical power converter 94 and / or an electrical switching assembly 96 (e.g., switchgear) (process block 189). Merely as an illustrative, non-limiting example, the control sub-system 98 may instruct the power sub-system 80 to supply electrical power with a first (e.g., positive) polarity to a fluid valve 28 to transition the fluid valve 28 toward its closed state and electrical power with a second (e.g., negative and / or different) polarity to transition the fluid valve 28 toward its open state. As another example, the control sub-system 98 may instruct the power sub-system 80 to supply electrical power with a lower magnitude to a fluid pump 50 to transition the fluid pump 50 to a lower (e.g., slower) pumping rate state, to supply electrical power with a higher magnitude to transition the fluid pump 50 to a higher (e.g., faster) pumping rate state, and to cease supplying electrical power to the fluid pump 50 to transition the fluid pump 50 to a non-pumping (e.g., off) state.

[0135] In other such embodiments, the control sub-system 98 may control the power sub-system 80 to adjust mechanical power supplied to the well system equipment. In particular, in some such embodiments, the control sub-system 98 may instruct the power sub-system 80 to adjust mechanical power supplied from a mechanical power source 82 (e.g., internal combustion engine) to the well system equipment, for example, via a mechanical power converter 94 (e.g., transmission or gearbox) and / or a mechanical switching assembly 96 (e.g., gear change assembly) (process block 190). As an illustrative non-limiting example, the control sub-system 98 may instruct the power sub-system 80 to actuate (e.g., rotate and / or translate) an output shaft connected to a fluid valve 28 in a first (e.g., clockwise) direction to transition the fluid valve 28 toward its closed state and to actuate the output shaft in a second (e.g., counterclockwise and / or different) direction to transition the fluid valve 28 toward its open state. As another example, the control sub-system 98 may instruct the power sub-system 80 to actuate an output shaft connected to a fluid pump 50 with a lower velocity and / or torque to transition the fluid pump 50 to a lower pumping rate state, to actuate the output shaft with a higher velocity and / or torque to transition the fluid pump 50 to a higher pumping rate state, and to cease actuating the output shaft to transition the fluid pump 50 to a non-pumping state.

[0136] However, as described above, to facilitate controlling operation of well system equipment, in other embodiments, the power sub-system 80 may adjust mechanical power supplied to the well system equipment as pressurized actuation fluid. Accordingly, in such embodiments, the control sub-system 98 may instruct the power sub-system 80 to adjust the supply of pressurized actuation fluid from the fluid power assembly 84 to the well system equipment (process block 191). For example, the control sub-system 98 may instruct the power sub-system 80 to supply pressurized actuation fluid to an open fluid port 71A on a fluid valve 28 to transition the fluid valve 28 toward its open state and to supply pressurized actuation fluid to a close fluid port 71B on the fluid valve 28 to transition the fluid valve 28 toward its closed state. As another example, the control sub-system 98 may instruct the power sub-system 80 to supply actuation fluid with a lower fluid pressure to a fluid pump 50 to transition the fluid pump 50 toward a lower pumping rate state, to supply actuation fluid with a higher fluid pressure to transition the fluid pump 50 toward a higher pumping rate state, and to cease supplying pressurized actuation fluid to the fluid pump 50 to transition the fluid pump 50 to a non-pumping state.

[0137] In any case, the control sub-system 98 may then determine whether a sequential performance parameter associated with the operation is set in the operation schedule 124 (decision block 173). As described above, when a sequential performance parameter associated with an operation is set, control action steps in the operation may be sequentially performed such that a subsequent control action step is initiated after a preceding control action step is completed.

[0138] Accordingly, when the sequential performance parameter is set, the control sub-system 98 may determine whether a corresponding equipment sensor 106A indicates that the well system equipment has achieved its target equipment state in the control action step (decision block 176). In particular, as described above, the control sub-system 98 may receive feedback from an equipment sensor 106A that is indicative of a current equipment state of corresponding well system equipment via one or more sensor signals 110. Accordingly, to determine whether a target equipment state has been achieved, the control sub-system 98 may determine whether a current equipment state of the well system equipment indicated by a corresponding equipment sensor 106A matches its target equipment state in the control action step.

[0139] Since well system equipment often does not change equipment state instantaneously, the control sub-system 98 may utilize a sensor timeout (e.g., time threshold). In particular, in some embodiments, a sensor timeout associated with an equipment sensor 106A may be set based on (e.g., to match or slightly longer than) the time (e.g., duration) expected to transition corresponding well system equipment from its current equipment state to its target equipment state in the control action step. However, to facilitate more conservatively accounting for equipment and / or environmental variations, in other embodiments, a sensor timeout associated with an equipment sensor 106A may be set based on the time expected to transition corresponding well system equipment from a first extreme equipment state to a second (e.g., opposite) equipment state. For example, a sensor timeout associated with an equipment sensor 106A that corresponds with a fluid valve 28 may be set based on the time expected to transition the fluid valve 28 from its fully open state to its fully closed state, or vice versa. As another example, a sensor timeout associated with an equipment sensor 106A that corresponds with a fluid pump 50 may be set based on the time expected to transition the fluid pump 50 from its non-pumping (e.g., off) state to its maximum pumping rate (e.g., on) state, or vice versa.

[0140] In any case, the control sub-system 98 may determine whether a corresponding sensor timeout has been reached (decision block 178) and continue checking whether the equipment sensor 106A indicates that the well system equipment has achieved its target equipment state until the sensor timeout is reached (arrow 171). In particular, to reduce the likelihood of producing further issues in the well system 10, in some embodiments, the control sub-system 98 may presume that the well system equipment is not able to achieve its target equipment state when the equipment sensor 106A does not indicate that the target equipment state has been achieved before the sensor timeout is reached and, thus, cease performance of the operation.

[0141] However, as discussed above, a faulty equipment sensor 106A may feedback an improper equipment state. In other words, in some instances, feedback from an equipment sensor 106A may indicate that corresponding well system equipment has not been achieved its target equipment state when the well system equipment has in fact achieved its target equipment state due to the equipment sensor 106A being faulty.

[0142] Accordingly, in other embodiments, the control sub-system 98 may presume that the equipment sensor 106A associated with the well system equipment is faulty when a corresponding sensor timeout is reached and corresponding sensor feedback indicates that the well system equipment has not achieved its target equipment state. In other words, in such embodiments, the control sub-system 98 may presume that the well system equipment has achieved its target equipment state once the sensor timeout is reached (e.g., elapses) and continue accordingly. That is, in such embodiments, the control sub-system 98 may determine that the well system equipment has achieved its target equipment state at the earlier of sensor feedback from a corresponding equipment sensor 106A indicating that the well system equipment has achieved its target equipment state and the sensor timeout being reached (e.g., elapsing).

[0143] However, to better distinguish between a faulty equipment sensor 106A and faulty well system equipment and, thus, reducing unnecessary work stoppages and likelihood of a subsequent control action step producing further issues in the well system 10, the control sub-system 98 may determine whether the target equipment state of the well system equipment is secondarily confirmed (decision block 184) and cease performance of the operation only if the target equipment state is not secondarily confirmed (process block 186). In particular, in some such embodiments, the control sub-system 98 may secondarily confirm whether the target equipment state has been achieved based on feedback from fluid parameter sensors 106B in the well system 10 and / or operator feedback.

[0144] To help illustrate, an example of a process 192 for secondarily confirming whether a fluid valve 28 has achieved its target valve state is described in FIG. 6. Generally, the process 192 includes determining a fluid parameter immediately downstream of a fluid valve (process block 194), determining an expected value of the downstream fluid parameter (process block 196), determining whether the determined fluid parameter value is within a variation threshold from the expected value (decision block 198), and determining whether a confirmation from an operator that the fluid valve has achieved its target valve state has been received (decision block 200). Additionally, when the determined fluid parameter value is within the variation threshold and / or operator confirmation is received, the process 192 generally includes indicating that the target valve state has been secondarily confirmed (process block 202). Furthermore, when the determined fluid parameter is not within the variation threshold and operator confirmation is not received, the process 192 generally includes indicating that the target valve state is not secondarily confirmed (process block 204).

[0145] However, it should be appreciated that the example process 192 is merely intended to be illustrative and not limiting. In particular, in other embodiments, depicted process blocks may be performed in a different order. For example, in other embodiments, the expected value of the downstream fluid parameter may be determined before the fluid parameter immediately downstream of the fluid valve is determined.

[0146] Additionally, in other embodiments, a process 192 for secondarily confirming whether a fluid valve 28 has achieved it target valve state may omit one or more of the depicted process blocks and / or one or more depicted decision blocks. For example, in other embodiments, the process 192 may only secondarily confirm whether the target valve state has been achieved based on operator confirmation and, thus, not include determining the fluid parameter immediately downstream of the fluid valve, determining the expected value of the downstream fluid parameter, or determining whether the determined fluid parameter value is within the variation threshold from the expected value. Alternatively, in other embodiments, the process 192 may only secondarily confirm whether the target valve state has been achieved based on feedback from fluid parameter sensors and, thus, not include determining whether operator confirmation is received.

[0147] Furthermore, in some embodiments, a process 192 for secondarily confirming whether a fluid valve 28 has achieved it target valve state may include one or more additional process blocks and / or one or more additional decision blocks. For example, in some embodiments, the process 192 may additionally include requesting operator confirmation of a current valve state of the fluid valve (process block 206). As another example, when operator confirmation has not yet been received, in some embodiments, the process 192 may additionally include determining whether a confirmation timeout has been reached (decision block 208).

[0148] Moreover, in some embodiments, a process 192 for secondarily confirming whether a fluid valve 28 has achieved it target valve state may be performed at least in part by executing instructions stored in one or more tangible, non-transitory, computer-readable media, such as control sub-system memory 116, using processing circuitry, such as one or more control sub-system processors 114. In other words, in some embodiments, the process 192 may be performed at least in part by a control sub-system 98, such as a distributed control sub-system 98A (e.g., central controller 118 and multiple operator devices 120), of a well system 10.

[0149] Accordingly, to secondarily confirm whether a fluid valve 28 in a well system 10 has achieved its target valve state, a control sub-system 98 may determine a fluid parameter immediately downstream from the fluid valve 28 based on sensor feedback (e.g., one or more sensor signals 110) received from one or more fluid parameter sensors 106B disposed immediately downstream of the fluid valve 28 (e.g., with no other fluid valves 28 therebetween) (process block 194). In particular, in some embodiments, the control sub-system 98 may determine a fluid pressure immediately downstream of the fluid valve 28 (process block 210), a fluid temperature immediately downstream of the fluid valve 28 (process block 212), and / or a fluid composition immediately downstream of the fluid valve (process block 214).

[0150] In any case, the control sub-system 98 may additionally determine an expected value of the fluid parameter immediately downstream of the fluid valve (process block 196) and determine whether the determined fluid parameter value is within a variation threshold form the expected value (decision block 198). In particular, in some embodiments, an expected value of an immediately downstream fluid parameter may be predetermined, for example, and stored in control sub-system memory 116.

[0151] However, in other embodiments, the control sub-system 98 may adaptively determine the expected value of a fluid parameter immediately downstream of the fluid valve 28. In particular, in some such embodiments, the control sub-system 98 may determine environmental conditions and determine the expected value of an immediately downstream fluid parameter accordingly (process block 216). For example, when the target valve state is a closed state, the control sub-system 98 may determine the expected fluid temperature immediately downstream of the fluid valve 28 based at least in part on environmental temperature.

[0152] Additionally, in some such embodiments, the control sub-system 98 may determine previous operation of the well system 10 and determine the expected value of a fluid parameter immediately downstream of the fluid valve 28 accordingly (process block 218). For example, when the target valve state is a closed state, the control sub-system 98 may determine the expected fluid pressure immediately downstream of the fluid valve 28 based at least in part on the fluid pressure of fluid flowed through the fluid valve 28 during a previous operation. As another example, when the target valve state is a closed state, the control sub-system 98 may determine the expected fluid composition immediately downstream of the fluid valve 28 based at least in part on the fluid composition of fluid flowed through the fluid valve 28 during a previous operation. As a further example, when the target valve state is a closed state, the control sub-system 98 may determine the expected fluid temperature immediately downstream of the fluid valve 28 based at least in part on the fluid temperature of fluid flowed through the fluid valve 28 during a previous operation.

[0153] Furthermore, in some such embodiments, the control sub-system 98 may determine a fluid parameter immediately upstream from the fluid valve 28 and determine the expected value of the immediately downstream fluid parameter accordingly (process block 220). In other words, in such embodiments, the control sub-system 98 may determine the expected value of an immediately downstream fluid parameter based at least in part on sensor feedback (e.g., one or more sensor signals 110) received from one or more fluid parameter sensors 106B disposed immediately upstream of the fluid valve 28 (e.g., with no other fluid valves 28 therebetween). For example, when the target valve state is an open state, the control sub-system 98 may determine the expected value of fluid pressure immediately downstream from the fluid valve 28 based at least in part on fluid pressure immediately upstream from the fluid valve 28. As another example, when the target valve state is an open state, the control sub-system 98 may determine the expected value of fluid temperature immediately downstream from the fluid valve 28 based at least in part on fluid temperature immediately upstream from the fluid valve 28. As a further example, when the target valve state is an open state, the control sub-system 98 may determine the expected value of fluid composition immediately downstream of the fluid valve 28 based at least in part on the fluid composition immediately upstream of the fluid valve 28.

[0154] In any case, although a determined value of an immediately downstream fluid parameter should be relatively close to a corresponding expected value when the fluid valve 28 has achieved its target state, the variation threshold may be set to account for process, equipment, and / or environmental variations. For example, when the target valve state is an open state, a variation threshold associated with an immediately downstream fluid pressure may be set to account for pressure change that may occur as fluid flows through the fluid valve 28. As another example, a variation threshold associated with an immediately downstream fluid composition may account for materials that may be inadvertently introduced as fluid flows through the fluid valve 28, for example, due to corrosion or erosion of the fluid valve 28. As a further example, a variation threshold associated with an immediately downstream fluid temperature may be set to account for the effect environmental temperature may have on the temperature of fluid within the well system 10. Nevertheless, in more conservative embodiments, a variation threshold may be set to force the determined value of the immediately downstream fluid parameter to match the expected value, for example, when the expected value is already determined to account for process, equipment, and / or environmental variations.

[0155] In any case, the control sub-system 98 may additionally determine whether operator confirmation that the fluid valve 28 has achieved its target valve state has been received (decision block 200). In particular, in some embodiments, an operator may confirm a current valve state of the fluid valve 28 from their operator device 120 and, thus, the control sub-system 98 may determine whether the fluid valve 28 has achieved its target valve state based on whether the operator confirmed valve state matches the target valve state. As described above, to facilitate operator confirmation of its current valve state, in some embodiments, a fluid valve 28 may have a visual indicator 112, such as a flag, attached to a valve actuator such that the visual indicator 112 changes positions (e.g., orientation) as the fluid valve 28 changes to different valve states. Additionally, as described above, to facilitate remote visual confirmation, in some embodiments, an optical sensor 106C may capture an image or video of the fluid valve 28, which the control sub-system 98 can then display, for example, on an operator device 120.

[0156] Accordingly, to facilitate expediting operator confirmation and, thus, well system operational efficiency, in some embodiments, the control sub-system 98 may explicitly request that an operator confirm (e.g., return) the current valve state of the fluid valve 28 (process block 206). In particular, in some such embodiments, the control sub-system 98 may display a prompt on the operator's operator device 120 that requests that the operator confirm the current valve state.

[0157] In any case, when the value of the determined immediately downstream fluid parameter is not within the variation threshold and operator confirmation of achievement of the target valve state has not been received, the control sub-system 98 may indicate that the target valve state has not been secondarily confirmed (process block 204). Accordingly, returning to the process 172 of FIG. 5, when achievement of the target equipment state has not been secondarily confirmed and the sensor timeout has elapsed, in some embodiments, the control sub-system 98 may cease performance of the operation (process block 186).

[0158] However, returning to the process 192 of FIG. 6, to provide an operator a reasonable time to respond, in some embodiments, the control sub-system 98 may utilize a confirmation timeout (e.g., time threshold) and only indicate that the target valve state has not been secondarily confirmed once the confirmation timeout has been reached (e.g., elapsed). In other words, in such embodiments, the control sub-system 98 may determine whether a confirmation timeout has been reached (decision block 208) and continue waiting for operator confirmation until the confirmation timeout is reached (arrow 224).

[0159] In fact, to facilitate balancing the amount of time provided for operator confirmation against efficient performance, in some such embodiments, the duration of the confirmation timeout may match the duration of a sensor timeout that is associated with an equipment sensor 106A that corresponds with the fluid valve 28, and the control sub-system 98 may concurrently run the confirmation timeout and the sensor timeout. In other words, in such embodiments, the control sub-system 98 may begin attempting to secondarily confirm achievement of the target valve state while waiting for the equipment sensor 106A to confirm achievement of the target valve state. Nevertheless, in other embodiments, the control sub-system 98 may only start the confirmation timeout after the sensor timeout has been reached and, thus, only attempt to secondarily confirm achievement of the target valve state after an equipment sensor 106A is unable to confirm achievement of the target valve state.

[0160] In any case, when the value of the determined immediately downstream fluid parameter is within the variation threshold and / or the operator has confirmed achievement of the target valve state, the control sub-system 98 may indicate that the target valve state has been secondarily confirmed (process block 202). Accordingly, returning to the process 172 of FIG. 5, when the sensor timeout has elapsed but achievement of the target equipment state has been secondarily confirmed, in some embodiments, the control sub-system 98 may indicate that the equipment sensor 106A corresponding with the well system equipment is potentially faulty (process block 188). For example, the control sub-system 98 may notify an operator of a potentially faulty equipment sensor 106A by displaying a message on their operator device 120 (process block 226).

[0161] In any case, once achievement of the target equipment state of the control action step is confirmed, the control sub-system 98 may determine whether any control action steps remain in the operation in accordance with the operation schedule 124 (decision block 180) and, if so, automatically perform a next control action step in the same manner (arrow 228). Once there are no control action steps remaining, the control sub-system 98 may indicate that performance of the operation is complete (process block 182). Nevertheless, to facilitate proper and efficient coordination between operations performed by different operators in the manner described above, in some embodiments, the control sub-system 98 may request that a corresponding operator explicitly confirm completion of the operation, for example, via a prompt on their operator device 120 (process block 230).

[0162] However, it should again be appreciated that example process 172 is merely intended to be illustrative and not limiting. For example, to default to sequential performance, in other embodiments, control action steps in an operation may be sequentially performed in the manner described above when an expedited performance parameter associated with the operation is not set in the operation schedule 124. In any case, in this manner, a control sub-system 98 may automatically control well system equipment to sequentially perform control action steps of an operation in a well system 10, for example, with no or minimal operator input or guidance, which, at least in some instances, may facilitate reducing operator error and, thus, improving operational efficiency (e.g., production time) of the well system 10.

[0163] However, as described above, when a sequential performance parameter associated with an operation is not set, control action steps in the operation may be initiated in rapid succession such that a subsequent control action step is initiated before a preceding control action step is completed. In other words, in some embodiments, control action steps in an operation may default to expedited performance.

[0164] In any case, when the sequential performance parameter associated with the operation is not set, the control sub-system 98 may determine whether any control action steps remain in the operation in accordance with the operation schedule 124 (decision block 175) and, if so, automatically initiate performance of a next control action step in the same manner (arrow 177). Once there are no control action steps remaining to be initiated, the control sub-system 98 may determine whether equipment sensors 106A indicate that each piece of well system equipment has achieved its target equipment state in the control action steps of the operation (decision block 179). In other words, when the sequential performance parameter is not set, the control sub-system 98 may initiate each control action step in the operation before confirming whether corresponding target equipment states have been achieved.

[0165] As described above, the control sub-system 98 may receive feedback from an equipment sensor 106A that is indicative of a current equipment state of corresponding well system equipment via one or more sensor signals 110. Accordingly, to determine whether a target equipment state has been achieved, the control sub-system 98 may determine whether a current equipment state of the well system equipment indicated by a corresponding equipment sensor 106A matches its target equipment state in a corresponding control action step.

[0166] Additionally, as described above, well system equipment often does not change equipment state instantaneously. In fact, when multiple control action steps are initiated in rapid succession and, thus, multiple pieces of well system equipment are concurrently operated, in some embodiments, the control sub-system 98 may instruct the power sub-system 80 to concurrently supply power to the different pieces of well system equipment. In other words, in such embodiments, the power supplied by the power sub-system 80 may be split between the different pieces of well system equipment, thereby potentially slowing the transition of a specific piece of equipment to its target equipment state as compared to sequential performance, for example, while nevertheless enabling each piece of equipment to achieve its target equipment state in a shorter total duration as compared to sequential performance.

[0167] To facilitate accounting for non-instantaneous equipment state changes that are initiated in rapid succession, in some embodiments, the control sub-system 98 may utilize an operation timeout (e.g., time threshold). In particular, an operation timeout associated with an operation may be set to based on (e.g., to match or slightly longer than) the total time (e.g., duration) expected to transition each pieces of well system equipment from its current equipment state to its target equipment state in a corresponding control action step when the transitions are initiated in rapid succession. In other words, in some embodiments, an operation timeout associated with an operation may be set based on (e.g., to match or slightly shorter than) a sum of the sensor timeouts of the equipment sensors 106A associated with the well system equipment operated (e.g., transitioned) during the operation.

[0168] Accordingly, the control sub-system 98 may determine whether a corresponding operation timeout has been reached (decision block 183) and continue checking whether the equipment sensors 106A indicate that each piece of well system equipment operated during the operation has achieved its target equipment state until the operation timeout is reached (arrow 231). However, as discussed above, a faulty equipment sensor 106A may feedback an improper equipment state. In other words, in some instances, feedback from an equipment sensor 106A may indicate that corresponding well system equipment has not been achieved its target equipment state when the well system equipment has in fact achieved its target equipment state due to the equipment sensor 106A being faulty.

[0169] To better distinguishing between faulty equipment sensors 106A and faulty well system equipment and, thus, reducing unnecessary work stoppages and / or likelihood of subsequent operations production further issues in the well system 10, the control sub-system 98 may determine whether each target equipment state that is not confirmed by a corresponding equipment sensor 106A is secondarily confirmed (decision block 181) and cease performance of the operation and block performance of subsequent operations when each of those target equipment states is not secondarily confirmed (process block 186). In particular, in some embodiments, the control sub-system 98 may secondarily confirm whether a target equipment state has been achieved in the manner described above.

[0170] Additionally, when ceasing performance of an operation, in some embodiments, the control sub-system 98 may automatically instruct reversal of one or more (e.g., most recent) control action steps initiated during the operation, for example, to facilitate minimizing corrective actions in the well system 10. As an illustrative non-limiting example, when performance of a valve tree operation that transitions a fluid valve 28 from its open state to its closed state is ceased, the control sub-system 98 may automatically instruct the well system 10 to transition the fluid valve 28 back to its open state, for example, to facilitate reducing the likelihood of the fluid valve 28 fully severing a conveyance line 44 extending therethrough.

[0171] In addition to automatically ceasing performance when appropriate, in some embodiments, the control sub-system 98 may enable an operator to manually cease (e.g., abort) performance of an operation from their operator device 120, for example, due to the operator perceiving a potential issue with continuing before the control sub-system 98. To facilitate reducing the likelihood of a manually ceased operation inadvertently being restarted (e.g., by a different operator), in some embodiments, the control sub-system 98 may permit resumption of the operation only if requested and / or approved by the same operator. Additionally, to encourage fully analyzing the condition of relevant well system equipment and, thus, appropriate resumption, in some embodiments, the control sub-system 98 may require that an operator request and / or approve resumption of a ceased operation from within a threshold proximity, for example, at a skid-mounted HM I operator device 120 instead of a mobile operator device 120.

[0172] In any case, when the operation timeout has elapsed but achievement of a target equipment state has been secondarily confirmed, in some embodiments, the control sub-system 98 may indicate that a corresponding equipment sensor 106A is potentially faulty (process block 185). For example, the control sub-system 98 may notify an operator of a potentially faulty equipment sensor 106A by displaying a message on their operator device 120 (process block 233)

[0173] Once achievement of each target equipment state in the operation is confirmed, the control sub-system 98 may indicate that performance of the operation is complete (process block 182). Nevertheless, to facilitate proper and efficient coordination between operations performed by different operators in the manner described above, in some embodiments, the control sub-system 98 may request that a corresponding operator explicitly confirm completion of the operation, for example, via a prompt on their operator device 120 (process block 230).

[0174] However, it should again be appreciated that example process 172 is merely intended to be illustrative and not limiting. For example, to default to sequential performance, in other embodiments, control action steps in an operation may be initiated in rapid succession in the manner described above when an expedited performance parameter associated with the operation is set in the operation schedule 124. In any case, in this manner, a control sub-system 98 may automatically control well system equipment to initiate, in rapid succession, multiple control action steps of an operation in a well system 10, for example, with no or minimal operator input or guidance, which, at least in some instances, may facilitate reducing operator error and, thus, improving operational efficiency (e.g., production time) of the well system 10.

[0175] Returning to the process 130 of FIG. 4, once an operation is completed, the control sub-system 98 may determine whether any more operations are to be performed in the well system 10 (e.g., in accordance with an operation schedule 124) and, if so, wait for a request to perform an operation before proceeding in the same manner (arrow 232). Once there are no more operations to be performed in the well system 10, the control sub-system 98 may place a lockout on all the operators to block the operators from subsequently and, thus, improperly controlling operation of well system equipment from their operator devices 120 (process block 144).

[0176] Moreover, as described above, since multiple different operator groups may perform operations around a well system 10, in some embodiments, a control sub-system 98 may keep an operation log 126, for example, in memory 116. In other words, in such embodiments, the control sub-system 98 may maintain an operation log 126 during the process 130 of coordinating operations in the well system 10. In particular, the control sub-system 98 may use the operation log 126 to track when performance of the operator's next operation was requested, when the different operator confirmed completion of their preceding operation, and when performance of the operator's next operation started. Merely as an illustrative, non-limiting example, the operation log 126 may track when an operator (e.g., service technician and / or well owner's operator) requested performance of a valve tree operation, when a wireline operator confirmed completion of a perforation operation, and when the service technician began performance of the valve tree operation, for example, in addition to when the requesting operator finalized or re-confirmed their request.

[0177] Accordingly, in such embodiments, if an issue that requires corrective action occurs in the well system 10, the corresponding operation log 126 may be referenced to identify a potential coordination breakdown that caused the issue, for example, to help avoid the issue in the future and / or to assign responsibility. As an illustrative non-limiting example, if a working (e.g., swab or master) valve is inadvertently closed on a conveyance line 44 during a valve tree operation, the operation log 126 may be consulted to confirm whether performance of the valve tree operation started after a wireline operator confirmed completion of a corresponding perforation operation and, if so, that the issue resulted due to the wireline operator improperly confirming completion of the perforation operation. In this manner, the techniques described in the present disclosure facilitate properly and efficiently coordinating operations of different operator groups around a well system, which, at least in some instances, may facilitate improving operational efficiency (e.g., production time) of the well system, for example, at least in part by minimizing operator error while accounting for the actual relationship between the different operator groups.

[0178] While the present disclosure has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this disclosure, will appreciate that other embodiments may be devised which do not depart from the scope of the disclosure as described herein. Accordingly, the scope of the disclosure should be limited only by the attached claims.

[0179] In particular, although useful for coordinating multiple different operator groups that perform operations on the same well 14 and, thus, described in that manner, the techniques of the present disclosure may nevertheless be used with a single operator group or even a single operator. For example, in some such embodiments, a control sub-system 98 in a well system 10 may simply enable an operator to request performance of an operation and immediately request that the operator finalize or re-confirm their request before permitting performance of the operation. Additionally, in some such embodiments, a control sub-system 98 in a well system 10 may use an operation log 126 to track when an operator requested performance of their next operation as well as when the operator finalized or re-confirmed their request to perform their next operation, for example, in addition to when the operator confirmed completion of their preceding operation and / or when the operator actually began performing their next operation.

Claims

1. A method of adaptively performing an operation in a well system, comprising:determining, using a control sub-system of the well system, an operation schedule that indicates control action steps in the operation;instructing, using the control sub-system, the well system to initiate a first control action step of the operation from the operation schedule that transitions a first fluid valve from a first current valve state to a first target valve state;determining, using the control sub-system, whether an expedited performance parameter associated with the operation is set in the operation schedule; andin response to determining that the expedited performance parameter associated with the operation is set in the operation schedule, instructing, using the control sub-system, the well system to initiate a second control action step of the operation from the operation schedule that transitions a second fluid valve from a second current valve state to a second target valve state before the first fluid valve achieves the first target valve state.

2. The method of claim 1, comprising, in response to determining that the expedited performance parameter associated with the operation is not set in the operation schedule:determining, using the control sub-system, whether the first fluid valve has achieved the first target valve state based on sensor feedback received from an equipment sensor associated with the first fluid valve before a sensor timeout elapses; andinstructing, using the control sub-system, the well system to perform the second control action step of the operation to transition the second fluid valve from the second current valve state to the second target valve state at an earlier of the sensor feedback indicating that the first fluid valve has achieved the first target valve state and the sensor timeout elapsing.

3. The method of claim 2, comprising indicating, using the control sub-system, that the equipment sensor associated with the first fluid valve is potentially faulty in response to determining that the sensor timeout elapsed.

4. The method of claim 1, comprising, in response to determining that the expedited performance parameter associated with the operation is set in the operation schedule, instructing, using the control sub-system, the well system to initiate a third control action step of the operation from the operation schedule that transitions a third fluid valve from a third current valve state to a third target valve state before the second fluid valve achieves the second target valve state.

5. The method of claim 1, comprising:receiving, using the control sub-system, a request from a first operator to perform the operation in the well system;in response to receiving the request to perform the operation, determining, using the control sub-system, whether a second operator associated with a preceding operation has confirmed completion of the preceding operation; andblocking performance of the first control action step of the operation in response to determining that the second operator has not confirmed completion of the preceding operation.

6. The method of claim 5, comprising:in response to determining that the second operator has confirmed completion of the preceding operation, determining, using the control sub-system, whether the first operator has re-confirmed the request to perform the operation in the well system; andblocking performance of the first control action step of the operation in response to determining that the first operator has not re-confirmed the request to perform the operation in the well system, wherein instructing the well system to initiate the first control action step of the operation comprises instructing the well system to initiate the first control action step of the operation in response to determining that the second operator has confirmed completion of the preceding operation in the well system and the first operator has re-confirmed the request to perform the operation in the well system.

7. The method of claim 1, wherein instructing the well system to initiate the first control action step of the operation comprises instructing a power sub-system of the well system to supply pressurized actuation fluid to the first fluid valve.

8. The method of claim 1, wherein, in response to determining that the expedited performance parameter associated with the operation is set in the operation schedule, instructing the well system to initiate the second control action step of the operation from the operation schedule comprises instructing a power sub-system of the well system to concurrently supply power to the first fluid valve and the second fluid valve.

9. A well system, comprising:first well system equipment;second well system equipment;a power sub-system coupled to the first well system equipment and the second well system equipment; anda control sub-system communicatively coupled to the power sub-system, wherein the control sub-system is configured to:instruct the power sub-system to supply power to the first well system equipment to perform a first control action step of an operation that transitions the first well system equipment from a first current equipment state to a first target equipment state in accordance with an operation schedule; andwhen a sequential performance parameter associated with the operation is not set in the operation schedule, instruct the power sub-system to concurrently supply power to the first well system equipment and the second well system equipment to perform, concurrent with the first control action step of the operation, a second control action step of the operation that transitions the second well system equipment from a second current equipment state to a second target equipment state.

10. The well system of claim 9, wherein:the first well system equipment comprises a first fluid valve; andthe second well system equipment comprises a second fluid valve.

11. The well system of claim 9, comprising an equipment sensor associated with the first well system equipment and communicatively coupled to the control sub-system, wherein the control sub-system is configured to:determine whether the first well system equipment has achieved the first target equipment state based at least in part on sensor feedback received from the equipment sensor; andwhen the sequential performance parameter associated with the operation is set in the operation schedule, at an earlier of the sensor feedback indicating that the first well system equipment has achieved the first target equipment state and a sensor timeout elapsing:instruct the power sub-system to cease supplying power to the first well system equipment to complete the first control action step of the operation; andsubsequently instruct the power sub-system to supply power to the second well system equipment to perform the second control action step of the operation that transitions the second well system equipment from the second current equipment state to the second target equipment state after completion of the first control action step of the operation.

12. The well system of claim 9, comprising third well system equipment, wherein:the power sub-system is coupled to the third well system equipment; andwhen the sequential performance parameter associated with the operation is not set in the operation schedule, the control sub-system is configured to instruct the power sub-system to concurrently supply power to the first well system equipment, the second well system equipment, and the third well system equipment to perform, concurrent with the first control action step and the second control action step of the operation, a third control action step of the operation that transitions the third well system equipment from a third current equipment state to a third target equipment state.

13. The well system of claim 9, wherein the power sub-system is configured to supply power as pressurized actuation fluid.

14. The well system of claim 9, wherein the control sub-system comprises:a first operator device configured to enable a first operator to input a request to perform the operation in the well system;a second operator device configured to enable a second operator to confirm completion of a preceding operation in the well system; anda central controller communicatively coupled to the first operator device and the second operator device, wherein the central controller is configured to block performance of the operation when the second operator has not confirmed completion of the preceding operation.

15. The well system of claim 14, wherein:the first operator device is configured to enable the first operator to finalize the request to perform the operation in the well system after the second operator has confirmed completion of the preceding operation in the well system; andthe central controller is configured to:block performance of the operation when the second operator has not finalized the request to perform the operation in the well system; andinstruct the power sub-system to supply power to the first well system equipment to perform the first control action step of the operation after the second operator has confirmed completion of the preceding operation in the well system and the first operator has finalized the request to perform the operation in the well system.

16. A tangible, non-transitory, computer-readable media storing instructions executable by processing circuitry in a well system, wherein the instructions comprise instructions to:determine, using the processing circuitry, an operation schedule that indicates control action steps of an operation to be performed in the well system;instruct, using the processing circuitry, the well system to initiate a first control action step of the operation from the operation schedule that transitions first well system equipment from a first current equipment state to a first target equipment state;determine, using the processing circuitry, whether a sequential performance parameter associated with the operation is set in the operation schedule; andwhen the sequential performance parameter associated with the operation is not set in the operation schedule, instruct, using the processing circuitry, the well system to initiate a second control action step of the operation from the operation schedule that transitions second well system equipment from a second current equipment state to a second target equipment state before the first well system equipment achieves the first target equipment state.

17. The tangible, non-transitory, computer-readable media of claim 16, wherein, when the sequential performance parameter associated with the operation is not set in the operation schedule, the instructions to instruct the well system to initiate the second control action step of the operation from the operation schedule comprise instructions to instruct a power sub-system of the well system to concurrently supply power to the first well system equipment and the second well system equipment.

18. The tangible, non-transitory, computer-readable media of claim 16, wherein the instructions comprise instructions to, when the sequential performance parameter associated with the operation is set in the operation schedule:determine, using the processing circuitry, whether sensor feedback received from an equipment sensor associated with the first well system equipment indicates that the first well system equipment has achieved the first target equipment state before a sensor timeout elapses; andinstruct, using the processing circuitry, the well system to initiate the second control action step of the operation from the operation schedule that transitions the second well system equipment from the second current equipment state to the second target equipment state at an earlier of the sensor feedback indicating that the first well system equipment has achieved the first target equipment state and the sensor timeout elapsing.

19. The tangible, non-transitory, computer-readable media of claim 16, wherein the instructions comprise instruction to, when the sequential performance parameter associated with the operation is not set in the operation schedule, instruct, using the processing circuitry, the well system to initiate a third control action step of the operation from the operation schedule that transitions third well system equipment from a third current equipment state to a third target equipment state before the second well system equipment achieves the second target equipment state.

20. The tangible, non-transitory, computer-readable media of claim 16, wherein the instructions to instruct the well system to initiate the first control action step of the operation comprise instructions to instruct a power sub-system of the well system to supply pressurized actuation fluid to the first well system equipment.

Images