The present disclosure relates generally to a hydraulic fracturing system that includes multiple hydraulic fracturing rigs and multiple power sources, and more particularly, to asymmetric power management of the hydraulic fracturing rigs and the multiple power sources.
Hydraulic fracturing is a means for extracting oil and gas from rock, typically to supplement a horizontal drilling operation. In particular, high pressure fluid is used to fracture the rock, stimulating the flow of oil and gas through the rock to increase the volumes of oil or gas that can be recovered. A hydraulic fracturing rig used to inject high pressure fluid, or fracturing fluid, includes, among other components, an engine, transmission, driveshaft, and pump.
Hydraulic fracturing may involve the use of a hydraulic fracturing system that includes multiple hydraulic fracturing rigs operating at a pressure based on the well head and running at the same or different flow rates to achieve an overall flow rate for the fluid (e.g., measured in barrels per minute). The hydraulic fracturing rigs may include a mix of mechanical and electrical hydraulic fracturing rigs. The hydraulic fracturing rigs may operate according to several different operational parameters and the power sources for the hydraulic fracturing rigs may differ by type of rig (and there may be multiple types of power sources for each type of rig). This can create a complex hydraulic fracturing system of various elements that may be difficult to control for certain objectives. This may result in wasted fuel or power resources, inefficient operation of hydraulic fracturing rigs, and/or the like.
U.S. Pat. No. 10,597,996 B2, granted on Mar. 24, 2020 (“the '996 patent”) describes managing fuel and electrical power on a drilling rig. The number of gensets in use is changed before a change in power consumption is needed. However, the '996 reference does not asymmetrically manage power from various power sources (including multiple types of power sources) and asymmetrically manage load on various hydraulic fracturing rigs (including multiple types of hydraulic fracturing rigs).
The present disclosure may solve one or more of the problems set forth above and/or other problems in the art. The scope of the current disclosure, however, is defined by the attached claims, and not by the ability to solve any specific problem.
In one aspect, a hydraulic fracturing system may include a plurality of electric power source outputs, a plurality of hydraulic fracturing rigs, and a non-transitory computer-readable medium storing instructions. The instructions, when executed by a processor of the hydraulic fracturing system, may cause the hydraulic fracturing system to perform asymmetric power management of the plurality of electric power source outputs and to perform asymmetric load management of the plurality of hydraulic fracturing rigs.
In another aspect, a method may include receiving information related to operation or a configuration of a hydraulic fracturing system. The hydraulic fracturing system may include a plurality of electric power source outputs and a plurality of hydraulic fracturing rigs. The method may further include performing, based on the information, asymmetric power management of the plurality of electric power source outputs. The method may further include performing, based on the information, asymmetric load management of the plurality of hydraulic fracturing rigs.
In yet another aspect, a controller for a hydraulic fracturing system may be configured to receive information related to operation or a configuration of the hydraulic fracturing system. The hydraulic fracturing system may include a plurality of electric power source outputs and a plurality of fracturing rigs. The controller may be further configured to perform, based on the information, asymmetric power management of the plurality of electric power source outputs. The controller may be further configured to perform, based on the information, asymmetric load management of the plurality of hydraulic fracturing rigs.
Other features and aspects of this disclosure will be apparent from the following description and the accompanying drawings.
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various exemplary embodiments and together with the description, serve to explain the principles of the disclosed embodiments.
Both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the features, as claimed. As used herein, the terms “comprises,” “comprising,” “has,” “having,” “includes,” “including,” or other variations thereof, are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements, but may include other elements not expressly listed or inherent to such a process, method, article, or apparatus. In this disclosure, unless stated otherwise, relative terms, such as, for example, “about,” “substantially,” and “approximately” are used to indicate a possible variation of ±10% in the stated value.
A trailer-mounted bleed off tank 16 may be provided to receive bleed off liquid or gas from the fluid lines 10. In addition, nitrogen, which may be beneficial to the hydraulic fracturing process for a variety of reasons, may be stored in tanks 18, with a pumping system 20 used to supply the nitrogen from the tanks 18 to the fluid lines 10 or the well head 12.
The hydraulic fracturing process performed at the site, using the hydraulic fracturing system 2 of the present disclosure, and the equipment used in the process, may be managed and/or monitored from a single location, such as a data monitoring system 22, located at the site or at additional or alternative locations. According to an example, the data monitoring system 22 may be supported on a van, truck or may be otherwise mobile. As will be described below, the data monitoring system 22 may include a user device 24 for displaying or inputting data for monitoring performance and/or controlling operation of the hydraulic fracturing system 2. According to one embodiment, the data gathered by the data monitoring system 22 may be sent off-board or off-site for monitoring performance and/or performing calculations relative to the hydraulic fracturing system 2.
As further illustrated in
Referring to
The controllers 36 may be configured to communicate with one or more sensors (not shown in
The controller 30 and/or the controllers 36 may each include a processor and a memory (not illustrated in
The memory may be a non-transitory computer-readable medium that may include volatile and/or nonvolatile memory, removable and/or non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules, or other data. Such memory includes, but is not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, redundant array of independent disks (RAID) storage systems, or any other medium which can be used to store the desired information and which can be accessed by a computing device (e.g., the user device 24, a server device, etc.). The memory may be implemented as computer-readable storage media (CRSM), which may be any available physical media accessible by the processor to execute instructions stored on the memory. The memory may have an operating system (OS) and/or a variety of suitable applications stored thereon. The OS, when executed by the processor, may enable management of hardware and/or software resources of the controller 30 and/or the controllers 36.
The memory may be capable of storing various computer readable instructions for performing certain operations described herein (e.g., operations of the controller 30 and/or the controllers 36). The instructions, when executed by the processor and/or the hardware logic component, may cause certain operations described herein to be performed.
The controller 30 may store and/or execute an optimization program 32 to perform asymmetric load management and/or power management (e.g., based on data stored in the memory or as otherwise provided to the controller 30, such as via the user device 24, gathered by the controllers 36, or from a database). The controller 30 may store and/or execute a control logic program 34 (e.g., to control the hydraulic fracturing system 2 to operate within safe operating limits). Data used by the controller 30 may include operational priority and/or site configuration-related information, scheduling-related information, cost-related information, power source-related information, power demand-related information, and/or the like. However, various other additional or alternative data may be used.
The micro-grid 48 may include one or more gensets (e.g., each genset may include on or more generators 26), one or more utility grids (e.g., one or more utility grids 28), one or more renewable energy systems, and/or one or more energy storage systems. As illustrated at 44, the micro-grid controller 42 may send, to the micro-grid 48, commands by individual assets. For example, the micro-grid 48 may send a separate set of instructions to each power source (e.g., to each genset, to each utility grid, to each renewable energy system, and to each energy storage system). The commands may control whether the power source is on, off, or idle, an amount of power output from the power source, and/or the like. Because the micro-grid controller 42 may provide separate commands to the power sources of the micro-grid 48, each power source may be controlled independently from the other power sources of the micro-grid 48.
As illustrated at 46, the system controller 30 may send, to a multi-rig controller 50, commands by individual assets. For example, the system controller 30 may send a separate set of instructions to each hydraulic fracturing rig 14 (e.g., to each mechanical fracturing rig 14 and/or to each electric hydraulic fracturing rig 14). The commands may control whether the hydraulic fracturing rig 14 is on, off, or idle, an amount of load on the hydraulic fracturing rig 14, and/or the like. Because the system controller 30 may provide separate commands to the hydraulic fracturing rigs 14, each hydraulic fracturing rig 14 may be controlled independently from the other hydraulic fracturing rigs 14 of the hydraulic fracturing system 2. The multi-rig controller 50 may be one of the controllers 36 described herein.
In some embodiments, just the electric hydraulic fracturing rigs 14 may need power from the micro-grid 48 since the mechanical hydraulic fracturing rigs 14 may have engines on the trailers. In this case, the system controller 30 may separate the load request from the electric hydraulic fracturing rigs 14 and mechanical hydraulic fracturing rigs 14 and may communicate the request of power needed for the electric hydraulic fracturing rigs 14 to the micro-grid 48 in connection with the commands sent at 44.
The input data 52 may include operational priority and/or site configuration-related information 54. For example, the operational priority and/or site configuration-related information 54 may include a priority among multiple hydraulic fracturing rigs 14, an operating mode priority for operation of the hydraulic fracturing rig 14 (e.g., a prioritization of fuel cost reduction over engine emissions reduction, or vice versa), a quantity of hydraulic fracturing rigs 14 at a site, a maximum allowed pressure or flow rate of a hydraulic fracturing rig 14 at the site, quantities and/or types of other equipment located at the site, ages, makes, models, and/or configurations of the equipment at the site, and/or the like. Additionally, or alternatively, the input data 52 may include scheduling-related information 56. For example, the scheduling-related information 56 may include times, dates, durations, locations, etc. for certain operations of the hydraulic fracturing system 2, such as scheduled times and dates for certain pump pressures, scheduled openings or closings of valves, etc.
Additionally, or alternatively, the input data 52 may include cost-related information 58. For example, the cost-related information 58 may include a cost of fuel or power for the hydraulic fracturing rig 14, a total cost of ownership of the hydraulic fracturing rig 14 (e.g., including maintenance costs, costs of fracturing fluid, or personnel costs), a cost of engine emissions (e.g., regulatory costs applied to engine emissions or costs related to reducing engine emissions, such as diesel exhaust fluid (DEF) costs), and/or the like. Additionally, or alternatively, the input data 52 may include power source-related information 60. For example, the power source-related information 60 may include numbers and/or types of power sources available at a site, configured power output ranges for the power sources, a cost of the power output from different types of power sources and/or individual instances of types of power sources, and/or the like. Additionally, or alternatively, the input data 52 may include power demand-related information 62. For example, the power demand-related information 62 may include a power demand for an experienced or expected load on an engine of a hydraulic fracturing rig 14 (e.g., flow, proppant demand, or pressure response), a desired flow rate of fracturing fluid, a desired output pressure of the fracturing fluid, a current gear ratio of a transmission of a hydraulic fracturing rig 14, a current transmission speed of the transmission, a desired pump input speed, and/or the like. The input data 52 may include various other types of data depending on the objective to be optimized by the optimization algorithm 64. For example, the input data 52 may include transmission gear life predictions, pump cavitation predictions, pump life predictions, engine life predictions, and/or the like.
As described in more detail below (e.g., with respect to
The optimization algorithm 64 may be configured to search for a set of optimized operational parameters 68 that achieve an objective. For example, in determining values for optimized operational parameters 68, the controller 30 may minimize or reduce an objective, maximize or increase an objective, and/or balance two or more objectives (e.g., maximize a first objective while keeping a second objective under a threshold value). In this way, “optimized,” “optimization” and similar terms used herein may refer to selection of values (for operational parameters), based on some criteria (an objective), from a set of available values. An objective may be of any suitable type, such as minimizing the cost of fracturing operations of the hydraulic fracturing system 2, minimizing fuel or power consumption of the hydraulic fracturing system 2, minimizing engine emissions from the hydraulic fracturing system 2, maximizing an operational life of equipment of the hydraulic fracturing system 2, minimizing an overall time of the hydraulic fracturing operations, minimizing a cost of ownership of equipment used in the hydraulic fracturing operations, maximizing a maintenance interval of equipment of the hydraulic fracturing system 2, and/or any combinations thereof. As a specific example, the controller 30 may, given minimum operational expectations, maximize fuel or power savings, minimize engine emissions, minimize total cost of operation or ownership of the hydraulic fracturing system 2 considering the costs of various operational parameters, balance maintenance intervals and maintenance costs, and/or the like.
The aspects of the controller 30 of the present disclosure and, in particular, the methods executed by the controller 30 may be used to asymmetrically manage power source outputs and loads. For example, the methods executed by the controller 30 may individually control power outputs from different types of power sources and/or different instances of different types of power sources based on individualized operating characteristics of the power sources. Additionally, or alternatively, the methods executed by the controller 30 may individually control load on different types of hydraulic fracturing rigs 14 and/or different instances of different types of hydraulic fracturing rigs 14 based on individualized operating characteristics of the hydraulic fracturing rigs 14. Thus, certain aspects described herein may provide various advantages to the operation of the hydraulic fracturing rigs 14, such as individual optimization of power sources and hydraulic fracturing rigs 14 while achieving certain objectives, such as minimizing fuel or power consumption, optimizing maintenance intervals, etc. For example, the controller 30 may evaluate a desired mode of operation for the hydraulic fracturing system 2 (e.g., based on input to the controller 30) and may make real-time (or near real-time) decisions to operate individual power sources and hydraulic fracturing rigs on a cost-effective point based on, e.g., utility cost, fuel cost, health of equipment, and/or the like.
At step 202, the method 200 may include identifying a fleet configuration. For example, the controller 30 may identify the types and/or number of hydraulic fracturing rigs 14 at a site (or included in the hydraulic fracturing system 2), a type and/or number of power sources at the site, a capacity of the power sources, and/or the like. At step 204, the method 200 may include determining an optimization mode. For example, the controller 30 may determine whether to optimize operations of the hydraulic fracturing system 2 according to a fuel mode (e.g., that minimizes fuel consumption or fuel costs during operation), a emissions mode (e.g., that minimizes engine emissions or costs of engine emissions during operation), a maintenance mode (e.g., that maximizes or optimizes a maintenance interval based on cost of operation or total cost of operation (TCO)), or a hybrid mode that combines one or more of the previously described modes.
At step 206, the method 200 may include receiving a site target and cost functions for the hydraulic fracturing system 2. For example, the controller 30 may receive information related to a requested pump flow and/or a target pressure for the site target. As another example, the controller 30 may receive a cost function for the operating mode (e.g., a first cost function for a fuel mode, a second cost function for an emission mode, a third cost function for a maintenance mode, or a fourth cost function for a hybrid mode). A cost function may include a mathematical function that maps values for one or more variables to a total score or cost. The optimization algorithm 64 may use the cost function to generate the optimized operational parameters 68, as described herein.
At step 208, the method 200 may include determining a source need to meet the site target. For example, the controller 30 may determine an engine speed and transmission gear for a mechanical hydraulic fracturing rig 14 to meet the site target, may determine an overall bus power for an electric hydraulic fracturing rig 14, and/or the like. After the step 208, the method 200 may include performing various steps 210. As input to the steps 210, the method 200 may include, at step 212, receiving information related to a real-time (or near real-time) utility state. For example, the controller 30 may receive the information at step 212. The real-time utility state may include a cost, health, provider signal, and/or the like related to the utility grid or one or more other power sources. Additionally, or alternatively, the method 200 may include, at step 214, receiving information related to real-time (or near real-time) equipment health and run-time hours. For example, the controller 30 may receive the information at step 214. The real-time equipment health may include an operating status of equipment of the hydraulic fracturing system 2 (e.g., an on/off/idle status), whether the equipment is operating within expected or acceptable operating limits, whether the equipment is operating in a manner likely to produce operating issues within a time period, and/or the like. The run-time hours may identify a quantity of hours that the equipment has been operated, an effective life of the equipment that has elapsed for a given quantity of hours of operation (e.g., operating the equipment in a less than ideal state may consume more of the equipment's life than for the same number of hours in an ideal state), and/or the like.
As part of the steps 210, the method 200 may include, at step 216, determining optimized operational parameters 68 for each hydraulic fracturing rig 14 to meet the site target. For example, the controller 30 may use the optimization algorithm 64 to determine the optimized operational parameters 68 based on an objective associated with an operating mode of the hydraulic fracturing system 2. At step 218, the method 200 may include performing asymmetric power management of power source outputs. For example, the controller 30 may allocate power output by power source type (e.g., micro-grid 48, energy storage, generator 26, etc.), by state of the power source (e.g., on/off/idle), and/or the like. At step 220, the method 200 may include performing asymmetric load management of the hydraulic fracturing rigs 14. For example, the controller 30 may determine, for a mechanical hydraulic fracturing rig 14, an operating state (e.g., on/off/idle), an engine speed for the engine of the hydraulic fracturing rig 14, a gear for the transmission of the hydraulic fracturing rig 14, and/or the like. Note that, in order to simplify the detailed description, the term “load management” is being used herein to refer to management of power usage of mechanical hydraulic fracturing rigs that have direct drive power on-board. As another example, the controller 30 may determine, for an electric hydraulic fracturing rig 14, an operating state, a motor speed of the motor of the hydraulic fracturing rig 14, and/or the like.
At step 222, the method 200 may include managing the power source outputs or the hydraulic fracturing rigs 14 based on a schedule. For example, for the power source outputs, the controller 30 may determine to increase or decrease power output from the power sources (e.g., by changing an operating state of a power source, by ramping operation of the power source up or down, managing utility import or export from the power sources, etc.) based on the job schedule for a site. Continuing with the previous example, the job schedule may indicate stages of hydraulic fracturing operations with increased or decreased activity, and the controller 30 may modify the power source outputs based on whether more or less power is needed during those stages. As another example, for the hydraulic fracturing rigs 14, the controller 30 may determine to increase or decrease load on the hydraulic fracturing rigs 14 (e.g., by changing an operating state of the hydraulic fracturing rigs 14, by ramping operation of the hydraulic fracturing rigs 14 up or down, etc.) based on the job schedule for a site. Continuing with the previous example, the controller 30 may modify the load on the hydraulic fracturing rigs 14 based on stages of increased or decreased hydraulic fracturing, as indicated by the job schedule.
At step 224, the method 200 may include reconfiguring the power source outputs to meet an expected load demand. For example, the controller 30 may determine a sequence of operations of the power sources that may facilitate a stable power source transition and may manage the power source outputs based on this determination. This may help to avoid power instability or power blackouts. At step 226, the method 200 may include reconfiguring the load management based on the optimized operational parameters. For example, the controller 30 may determine a sequence of operations of the hydraulic fracturing rigs 14 that may facilitate stable flow or pressure during hydraulic fracturing.
At step 402, the method 400 may include receiving input data 52 related to a hydraulic fracturing system 2. For example, the controller 30 may receive the input data 52 from the user device 24 (e.g., as input from a user of the user device 24), from a sensor (e.g., associated with an element of the hydraulic fracturing system 2 and/or a component of an element), from a database (e.g., stored by the data monitoring system 22), from a server device (e.g., in a datacenter that is at a hydraulic fracturing site or remote to the hydraulic fracturing site), and/or the like. The controller 30 may receive the input data 52 prior to hydraulic fracturing operations beginning at a site, during the hydraulic fracturing operations, at scheduled intervals, when certain operating thresholds are exceeded or not met, and/or the like. In connection with the receiving at step 402, the controller 30 may further receive a cost function to be used by the optimization algorithm 64.
In connection with the receiving at 402, the controller 30 may further receive operating maps for equipment to be controlled. For example, the controller 30 may receive operating maps for one or more hydraulic fracturing rigs 14 from a database. The operating maps may include engine emissions maps, performance maps, fuel maps, and/or the like associated with the hydraulic fracturing rig 14. A map according to the present disclosure may provide an indication of output parameters of a particular equipment or component thereof as a function of input parameters, such as operating conditions of the hydraulic fracturing rig 14 or a component of the hydraulic fracturing rig 14. For example, an engine emissions map may indicate an amount of engine emissions as a function of engine speed and percentage of peak torque or as a function of power output and engine revolution rate. As another example, a performance map may indicate engine efficiency as a function of engine power output and engine age or may indicate parasitic loss of a pump as a function of flow rate and fluid output pressure. As yet another example, a fuel map (e.g., a brake specific fuel consumption (BSFC) map) may indicate a fuel efficiency of an engine based on the rate of fuel consumption and the power produced by the engine.
At step 404, the method 400 may include determining optimized operational parameters for the hydraulic fracturing system 2. For example, the controller 30 may select values for various operational parameters 68 for a hydraulic fracturing rig 14 and may determine fuel costs and engine emissions costs of the hydraulic fracturing rig 14 based on those values. In determining the values for the various operational parameters 68, the controller 30, via the optimization algorithm 64, may optimize one or more objectives. For example, the objective may be of any suitable type, such as reducing the cost of the fracturing operation, reducing engine emissions from the fracturing operation, reducing idle time during the fracturing operation, reducing wear on fracturing equipment during the fracturing operations, increasing efficiency of the fracturing operation, reducing an overall time of the fracturing operation, reducing the cost of ownership of the equipment used in the fracturing operation, and/or any combinations thereof. As a specific example, the controller 30 may determine optimized operational parameters 68 that minimize fuel costs or engine emissions costs according to certain maximum limits on such costs. As another specific example, if multiple operating points for the hydraulic fracturing rigs 14 provide lower operating costs, the controller 30, via the optimization algorithm 64, may select one of the points based on an objective, such as selecting the point with the lowest engine emissions output.
The determining of the operational parameters 68 may include a determination of an apportionment of power demand to various hydraulic fracturing rigs 14 included in the hydraulic fracturing system 2. To allow for hydraulic fracturing rigs 14 to be operated in a manner that optimizes the engine emissions produced by, and cost of fuel consumed by, multiple hydraulic fracturing rigs 14, the controller 30 may be configured to perform an optimization process that determines an optimized apportionment of the power demand to the individual operating hydraulic fracturing rigs 14 based upon minimizing engine emissions constrained by fuel cost limits. This may result in an equal or unequal apportionment of the power demand between different hydraulic fracturing rigs 14, and some hydraulic fracturing rigs 14 may be turned off. In some implementations, similarly configured hydraulic fracturing rigs 14 may be apportioned a similar or different proportion of the power demand.
Whether the controller 30 apportions the power demand based on total engine emissions and fuel costs may be determined by an operator of the hydraulic fracturing system 2 or it may be automatically determined based signals relating to other hydraulic fracturing system 2 functions. Accordingly, the controller 30 may be configured to receive information indicative of selection of a mode (e.g., an emission mode and/or a fuel mode), which may communicate to the controller 30 whether to enable the engine emission control mode and/or the fuel mode. The mode selection information may be input through the user device 24, for example in the data monitoring system 22, by an operator. Additionally, or alternatively, the mode selection information may also include information that may signal an automatic enablement of the apportionment of the power demand or power supply output such as, for example, information relating to the location of the hydraulic fracturing system 2 (e.g., in an area with certain limitations on engine emissions) and/or information relating to an operating mode of the hydraulic fracturing rigs 14. Additionally, or alternatively, the mode selection information may include information regarding whether the hydraulic fracturing system 2 is in a condition in which enablement of a mode may not be appropriate or a condition in which the mode may be enabled (e.g., enablement of a fuel mode or an emissions mode may not be appropriate unless hydraulic fracturing rigs 14 with a certain configuration are present at a site).
The determining at step 404 may be based on one or more cost functions for an operation mode. For example, the controller 30 may determine optimized operational parameters 68 based on whether values for the parameters cause the cost function to have a score that is equal to or greater than a threshold or that is equal to or less than the threshold.
At step 406, the method 400 may include performing asymmetric power management of electric power source outputs of the hydraulic fracturing system 2. For example, the controller 30 may determine a power source output for each power source individually, by type of power source, and/or the like. In some embodiments, the performing of the asymmetric power management may include causing power to be drawn or output from different electric power sources at different rates. For example, the controller 30 may control one power source to output power at, or to restrict power draw to, a lower level than another power source. In some embodiments, the determining at step 406 may include determining initial power source outputs for the power sources based on the operational parameters 68. For example, the controller 30 may determine power source outputs that satisfy a power demand for the hydraulic fracturing operations in accordance with the optimized operational parameters 68. Additionally, or alternatively, the determining at step 406 may include modifying the power source outputs after starting the hydraulic fracturing operations, e.g., to prevent blackouts or equipment stoppage (e.g., minimizing unplanned downtime), based on modified optimized operational parameters 68, based on an updated score from the cost function, and/or the like.
At step 408, the method 400 may include performing asymmetric load management of the hydraulic fracturing system 2. For example, the controller 30 may determine a load for each hydraulic fracturing rig 14 individually, by type of hydraulic fracturing rig 14, and/or the like. As a specific example, the asymmetric load management of step 408 may include operating a hydraulic fracturing rig 14 at a different operating point from another hydraulic fracturing rig 14. The different operating points may correspond to different output fracturing power levels (output fracturing power for the hydraulic fracturing system may equal discharge pressure times flow rate and power source output power may be kW input to an electric hydraulic fracturing system). The different operating points may be determined based on fuel parameters, engine emissions, or maintenance data. For example, a rig 14 with a higher fuel consumption rate may be operated at a lower output fracturing power level than another rig 14 with a lower fuel consumption rate. In some embodiments, one hydraulic fracturing rig 14 may have a different power output profile from another hydraulic fracturing rig 14 and the performing at step 408 may include distributing different loads to the hydraulic fracturing rigs 14 based on the different power output profiles. A power output profile may include an ideal operating pump torque and speed, an engineering specified pump torque and speed, a maximum operating pump torque and speed, a minimum operating pump torque and speed, and/or the like.
In some embodiments, one hydraulic fracturing rig 14 may have a different maintenance health profile from another hydraulic fracturing rig 14 and the performing at step 408 may include distributing different loads to the hydraulic fracturing rigs 14 based on the different maintenance health profiles. A maintenance health profile may include an expected life of a hydraulic fracturing rig 14 or a component thereof, a length of a time interval between maintenance periods for a hydraulic fracturing rig 14, an operating limit of a component (e.g., an engine, transmission, VFD, motor, or pump) of a hydraulic fracturing rig 14, an operating history of a hydraulic fracturing rig 14, an operating schedule of a hydraulic fracturing rig 14, and/or the like. Additionally, or alternatively, a maintenance health profile may include a score that indicates a current health of the hydraulic fracturing rig 14. For example, the maintenance health profile may indicate whether the hydraulic fracturing rig 14 (or a component thereof) has experienced a health-degrading event, such as exceeding a temperature limit, excessive torsion, abnormal behavior, excessive vibration, cavitation, fluid leakage, failure, etc.
In some embodiments, the performing at step 408 may be based on a prediction of flow capability of a hydraulic fracturing rig 14. For example, the controller 30 may use the optimization algorithm 64 to predict the flow capability based on a suction pressure, predicted cavitation, detected cavitation, valve leakage, areas of reduced torsional vibration, abnormal behavior, and/or the like for the hydraulic fracturing rig 14. In some embodiments, the performing at 408 may be based on characteristics of a discharge pressure and/or flow to the pump for the hydraulic fracturing rig 14. For example, the controller 30 may receive data from sensors regarding the discharge pressure and flow and may input the received data into the optimization algorithm 64 to determine an optimized load on the hydraulic fracturing rig 14. The controller 30 may then adjust blending equipment 8 to optimize the load on the hydraulic fracturing rig 14 (e.g., by sending control signals to the blending equipment 8).
In some embodiments, the performing at step 408 may include determining initial loads for the hydraulic fracturing rigs 14 based on the operational parameters. For example, the controller 30 may determine loads that satisfy a load demand for the hydraulic fracturing operations in accordance with the optimized operational parameters 68.
Additionally, or alternatively, the determining at step 408 may include modifying the load after starting the hydraulic fracturing operations, e.g., to help ensure effective or continued hydraulic fracturing operations (e.g., minimizing unplanned downtime), based on modified optimized operational parameters 68, based on an updated score from the cost function, and/or the like.
Although the method 400 illustrated in
The controller 30 of the present disclosure can provide real-time (or near real-time) power and load management. Thus, aspects of the present disclosure may optimize power output and power consumption for reducing costs or engine emissions of hydraulic fracturing operations. This may improve operation of a hydraulic fracturing rig 14 without the hydraulic fracturing rig 14 experiencing a significant degradation in performance. In addition, aspects of the present disclosure may optimize load on various equipment of the hydraulic fracturing system 2. This may improve operations of the hydraulic fracturing system 2 by reducing engine emissions, reducing fuel consumption, etc. while satisfying a load demand for hydraulic fracturing operations. Other advantages of certain aspects of the present disclosure include providing optimization processes that are compatible with electric hydraulic fracturing rigs 14 and/or mixed fleets, seamless integration of providing power to load demand (e.g., reactive and predictive power output and load management), mixed fleet integration of gas, bi-fuel, dual fuel, and diesel power, optimization of power sources for fuel and carbon footprint reduction, and safe and efficient integration and management of power grids. Further, asymmetric management described herein may reduce or eliminate waste that may occur with evenly shared power assets.
It will be apparent to those skilled in the art that various modifications and variations can be made to the disclosed system without departing from the scope of the disclosure. Other embodiments of the system will be apparent to those skilled in the art from consideration of the specification and practice of the system disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope of the disclosure being indicated by the following claims and their equivalents.
Number | Name | Date | Kind |
---|---|---|---|
8205594 | Fore et al. | Jun 2012 | B2 |
9255531 | Zhang et al. | Feb 2016 | B2 |
9683503 | Zhang et al. | Jun 2017 | B2 |
9889915 | Zhang et al. | Feb 2018 | B2 |
9896982 | Zhang et al. | Feb 2018 | B1 |
10131599 | Olah et al. | Nov 2018 | B2 |
10151192 | Burress et al. | Dec 2018 | B2 |
10415348 | Zhang et al. | Sep 2019 | B2 |
10458352 | Zhang et al. | Oct 2019 | B2 |
10563649 | Zhang et al. | Feb 2020 | B2 |
10597996 | Boone | Mar 2020 | B2 |
10734814 | Converse et al. | Aug 2020 | B2 |
10760996 | Converse et al. | Sep 2020 | B2 |
10815764 | Yeung | Oct 2020 | B1 |
10890061 | Cai et al. | Jan 2021 | B2 |
10914155 | Oehring et al. | Feb 2021 | B2 |
10927774 | Cai et al. | Feb 2021 | B2 |
11408417 | Stephenson | Aug 2022 | B1 |
20130306322 | Sanborn | Nov 2013 | A1 |
20170012439 | Zhang et al. | Jan 2017 | A1 |
20170051598 | Ouenes | Feb 2017 | A1 |
20170130712 | Zhang et al. | May 2017 | A1 |
20200300073 | Hinderliter et al. | Sep 2020 | A1 |
20210131248 | Hinderliter | May 2021 | A1 |
20220003229 | Mu | Jan 2022 | A1 |
20220018234 | Reddy | Jan 2022 | A1 |
20220074297 | Zheng | Mar 2022 | A1 |
20220127944 | Chapman | Apr 2022 | A1 |
20220136489 | Fisher | May 2022 | A1 |
20220154555 | El Tawy | May 2022 | A1 |
20220162931 | Zhong | May 2022 | A1 |
20220345007 | Liu | Oct 2022 | A1 |
Number | Date | Country |
---|---|---|
2020219088 | Oct 2020 | WO |
Entry |
---|
Unpublished U.S. Appl. No. 17/110,415, filed Dec. 3, 2020. |
Number | Date | Country | |
---|---|---|---|
20230235653 A1 | Jul 2023 | US |