SYSTEMS AND METHODS FOR ENHANCED PROCESS CONTROL OF AMINE CIRCULATION PUMPS

Description

FIELD OF THE DISCLOSURE

The present disclosure relates generally to natural gas processing technology and, more particularly, to methods and systems for controlling the operability of amine gas pumps in a sour gas processing train.

BACKGROUND OF THE DISCLOSURE

“Sour gas” processing is a procedure common to petroleum refining, natural gas production, and petrochemical operations. Sour gas refers to natural gas that contains significant amounts of hydrogen sulfide (H₂S) and sometimes carbon dioxide (CO₂). These impurities may be harmful to processing equipment, to operating users, and to surrounding ecology. To address this potential harm, sour gas is typically “sweetened” to remove H₂S and CO₂ from the natural gas stream. One technique to sweeten natural gas utilizes amines (e.g., nitrogen (N) based compounds having a lone pair) to selectively absorb H₂S and CO₂, stripping the natural gas from harmful impurities. Often, sour gas processing utilizes complex sour gas processing trains. Control systems for sour gas processing trains may be configured to achieve efficient and effective gas sweetening.

Although current techniques for sour gas processing, and for controlling gas processing trains in particular, are based on technological advancements made over many years, current processing techniques may still be ineffective to achieve ideal sweetening results. For example, control systems for sour gas processing trains may be unreliable and inefficient. Accordingly, there is an impetus to improve sour gas processing technology to overcome current technological challenges by implementing improvements including, for example: enhancing the control systems within a sour gas processing train, reducing inefficiencies associated with amine-based gas processing systems, increasing the throughput of amine-based gas processing systems, reducing errors associated with current control systems, decreasing the cost of amine-based sour gas processing, and the like.

Consequently, there exists a need for further improvements in sour gas processing technology to overcome the aforementioned technical challenges and other challenges not mentioned.

SUMMARY OF THE DISCLOSURE

Various details of the present disclosure are hereinafter summarized to provide a basic understanding. This summary is not an exhaustive overview of the disclosure and is neither intended to identify certain elements of the disclosure, nor to delineate the scope thereof. Rather, the primary purpose of this summary is to present some concepts of the disclosure in a simplified form prior to the more detailed description that is presented hereinafter.

According to an embodiment consistent with the present disclosure, an override control component may be described herein. The override control component may include a first memory and first set of one or more processors. The first set of one or more processors may be configured to cause the override control component to receive, from an auto-start logic component, one or more initial control signals generated in response to at least one parameter exiting a threshold range, wherein the at least one parameter exiting the threshold range is caused by an active/standby mode change at one or more amine pumps, to generate one or more control signals based on the one or more initial control signals, and to output the one or more control signals, the one or more control signals configured to cause an adjustment at a flow control valve.

In another embodiment, a control loop may be described. The control loop may include a flow indicator (FI). The control loop may include a flow control valve (FCV). The control loop may include a flow indicator controller (FIC) coupled to the FI and the override control component, the FIC having an auto-start logic component. The control loop may include an override control component coupled to the FCV and comprising a first memory and first set of one or more processors, the first set of one or more processors configured to cause the override control component to receive one or more initial control signals generated in response to at least one parameter exiting a threshold range, wherein the at least one parameter exiting the threshold range is caused by an active/standby mode change at one or more amine pumps, to generate one or more control signals based on the one or more initial control signals, and to output the one or more control signals, the one or more control signals configured to adjust the FCV.

In another embodiment, a method for controlling an amine gas pump system may be described. The method may include receiving, at an override control component, one or more initial control signals generated in response to at least one parameter exiting a threshold range, wherein the at least one parameter exiting the threshold range is caused by an active/standby mode change at one or more amine pumps. The method may include generating one or more control signals based on the one or more initial control signals. The method may include outputting the one or more control signals, the one or more control signals configured to adjust at least one flow control valve.

Other embodiments of the present disclosure provide: an apparatus operable, configured, or otherwise adapted to perform the aforementioned methods as well as those described elsewhere herein; a non-transitory, computer-readable media including computer-executable instructions that, when executed by a processor of an apparatus, cause the apparatus to perform the aforementioned methods as well as those described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the aforementioned methods as well as those described elsewhere herein; and an apparatus including means for performing the aforementioned methods as well as those described elsewhere herein. By way of example, an apparatus may include a processing system, or processing systems cooperating over one or more message passing interfaces.

Any combinations of the various embodiments and implementations disclosed herein can be used in a further embodiment, consistent with the disclosure. These and other aspects and features can be appreciated from the following description of certain embodiments presented herein in accordance with the disclosure and the accompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the disclosure, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only example embodiments and are therefore not to be considered limiting of its scope, and may admit to other equally effective embodiments.

FIG. 1 is a schematic diagram of an example sour gas processing system having amine circulation pumps operating in a parallel duty/standby mode of operation.

FIG. 2 is a schematic diagram of an example flow intake control loop having a flow indicator controller (FIC) configured to control amine circulation pumps operating in a parallel duty/standby mode of operation.

FIG. 3 is a schematic diagram of an example flow intake control loop having an override control component, according to one or more embodiments of the present disclosure.

FIG. 4 is a block diagram of an example FIC and an example override control component, according to one or more embodiments of the present disclosure.

FIG. 5 an example flow diagram for an override control scheme in a sour gas processing system, according to at least one embodiment of the present disclosure.

FIG. 6 is a block diagram of a computing platform that may be used to implement one or more of the systems or methods described herein in accordance with certain embodiments.

FIG. 7 is a block diagram of a computer system that may be used to implement one or more of the systems or methods described herein in accordance with certain embodiments.

DETAILED DESCRIPTION

Embodiments of the present disclosure will now be described in detail with reference to the accompanying drawing figures. Like elements in the various figures may be denoted by like reference numerals. Further, in the following detailed description, specific details are set forth in order to provide a more thorough understanding of the claimed subject matter. However, it will be apparent to one of ordinary skill in the art that the embodiments disclosed herein may be practiced without these specific details, or with details that are not described herein in the interest of clarity. Thus, in some instances, well-known features have not been described in detail to avoid unnecessarily complicating the description. Additionally, it will be apparent to one of ordinary skill in the art that the scale of the elements presented in the accompanying drawing figures may vary without departing from the scope of the present disclosure.

Sour gas processing trains may be configured to sweeten natural gas using amines, which selectively absorb harmful acidic components such as H₂S and CO₂. Sour gas processing systems may utilize complex sour gas processing trains to achieve amine-based sweetening. Processing trains may include (1) a set of pumps and (2) a control system configured to operate the pumps in an active/standby mode. The active/standby mode of operation allows pumps arranged in parallel to operate one-at-a-time (independently) to achieve optimal flow and pressure results within the processing train. In other words, while one pump actively pumps gas through the processing train, the other pump does not pump gas through the processing train. The control system may toggle which pump is active based on the needs of the processing train.

In some cases, when a control system switches the pumps from active to standby mode, or vice versa, the standby pump may immediately commence full operation as the active pump enters standby mode. This may cause a fail-start or a safety trip where the system briefly operates the standby pump at full capacity. Full capacity operation may create inadequate flow, low suction, and the like. Repeated fail-starts and a safety trips may cause energy waste, may inconvenience operating users, and may reduce overall throughput of sweetened natural gas.

Embodiments of the present disclosure provide an override control system (e.g., an override control scheme and override control component) configured to enhance current processing train control systems. This enhancement may be achieved, for example, by modifying control signals from the control system to precisely actuate one or more flow control valves (FCVs). Controlling the FCVs allows the control system to maintain appropriate flow rate and pressure throughout the processing train, avoiding wasteful and inefficient processing interruptions.

Example Sour Gas Processing System

FIG. 1 illustrates an example sour gas processing system 100 that may incorporate one or more principles of the present disclosure. In at least one embodiment, the sour gas processing system 100 may be considered and otherwise referred to as a sour gas processing “train”. As illustrated, the sour gas processing system 100 includes a gas processing section or unit 101 and an acid gas handling section or unit 103.

The gas processing unit 101 (hereafter “the unit 101”) includes an amine contactor 102, a plurality of flow paths 104a-d that feed the amine contactor 102, and a flow controller 106 including a flow control valve (FCV) 108 communicably coupled to a flow indicator transmitter (FIT) 110 via control line 112. The unit 101 further includes a flow indicator (FI) 114 and a pressure indicator transmitter (PIT) 116. The unit further includes an amine trim cooler 118, a pressure indicator (PI) 120, and a PI 122. The unit further includes FCV 124, FCV 126, a first amine pump 128, a second amine pump 130, an FIT 132, an FIT 134, an FCV 136, an FCV 138, a reflow path 140a-c, a FCV 142, and a FCV 144. The foregoing components will be discussed in further detail below.

The acid gas handling unit 103 (hereafter “the unit 103”) includes a stripper component 146, an output 148 from the stripper component 146, a plurality of flow paths 150a-d, a first acid pump 152, a second acid pump 154, an FIT 156, an FIT 158, a reflow path 160a-b, a FCV 162, and an FCV 164. The unit 103 further includes a PIT 166, an FI 168, and a flow path 170. As depicted, the flow path 170 may fluidly couple the unit 103 to the unit 101. The foregoing components will be discussed in further detail below.

In at least one embodiment, the unit 103 may facilitate the circulation of an acidic gas to the unit 101 via flow path 170. The acidic gas exits the stripper component 146 via flow path 150a, which directs the acidic gas to the first and second acid pumps 152, 154. In at least one embodiment, the acid pumps 152, 154 may operate in a duty/standby mode of operation, where one of the acid pumps 152, 154 is actively pumping the acidic gas, while the other is on standby to save energy. After exiting either of the acid pumps 152, 154, the acidic gas is conveyed within flow paths 150b, 150c, respectively. The acidic gas encounters FIT 156 along flow path 150b and encounters FIT 158 along flow path 150c, then proceeds either to flow path 150d or to flow path 160 to be recycled. The FITs 156, 158 may be configured to monitor and report flow rates of the acidic gas in the flow paths 150b, 150c, respectively.

In some applications, a portion of the acidic gas may be recycled back to the stripper component 146 via flow paths 160a, 160b from flow paths 150b, 150c, respectively. The flow of the acidic gas through the flow paths 160a, 160b may be controlled via FCVs 162, 164, respectively. The acidic gas may be conveyed from flow paths 160a, 160b to flow path 160c, which conveys the acidic gas back to the stripper component 146. In at least one embodiment, the stripper component 146 may direct the acidic gas to a different system (not shown, e.g., an acid gas enrichment system, a sulfur production plant) via the output 148. In at least one embodiment, flow path 160c may fluidly communicate with flow path 170, which transfers the acidic gas into the unit 101.

The unit 101 may facilitate the flow of the acidic gas to the amine contactor 102, which may be configured to strip acidic components (e.g., H₂S) from the acidic gas, thereby “sweetening” the gas for further processing. In at least one embodiment, the unit 101 may circulate an amine component (e.g., an amine aqueous solution). As illustrated in FIG. 1, the acidic gas enters unit 101 along flow path 170 and enters the amine trim cooler 118, which may be configured to facilitate cooling of amines introduced into the acidic gas as it enters the 101.

After being discharged from the amine trim cooler 118, the acidic gas proceeds via flow path 104a and the PIs 120, 122 monitor and measure pressure within the flow path 104a. From flow path 104a, the acidic gas may be conveyed into one or both of flow paths 104b, 104c, and FCVs 124, 126 operate to regulate flow into the flow paths 104b, 104c, respectively. In flow path 104b, the acidic gas is conveyed to the first amine pump 128, and in flow path 104c, the acidic gas is conveyed to the second amine pump 130. In at least one embodiment, PI 120 may have a function distinct from PI 122.

In at least one embodiment, the first and second amine pumps 128, 130 may operate in a duty/standby mode of operation, where one of the amine pumps 128, 130 is actively pumping the acidic gas, while the other remains on standby. In one example, when the first amine pump 128 is active, FCVs 124 and 136 are open, and FCVs 126 and 138 are closed while the second amine pump 130 is in standby mode. In another example, when the second amine pump 130 is active, the FCVs 126 and 138 are open, and FCVs 124 and 138 is closed, while the first amine pump 128 is in standby mode. In at least one embodiment, when the acidic gas exits the first amine pump 128, it proceeds along flow path 104b and FIT 132 monitors the flow rate to FCV 136. Similarly, when the acidic gas exits the second amine pump 130, it proceeds along flow path 104c and FIT 134 monitors the flow rate to FCV 138.

In at least one embodiment, a portion of the acidic gas discharged from the amine pumps 128, 130 may be recycled back to the amine trim cooler 118 via flow paths 140a-c. As illustrated, the flow path 140a may extend from flow path 104b at a location downstream from FIT 132 and upstream from FCV 136. Moreover, the flow path 140b may extend from flow path 104c at a location downstream from FIT 134 and upstream from FCV 138. In at least one embodiment, recycling of acidic gas travelling along flow path 140a is facilitated by at least the opening of FCV 142, and may be further enabled by the closing of FCV 136. Similarly, recycling of acidic gas travelling along flow path 140b is facilitated by at least the opening of FCV 144, and may be further enabled by the closing of FCV 138. The acidic gas may travel along flow paths 140a and 140b to flow path 140c, where it returns to the amine trim cooler 118 for further processing.

In at least one embodiment, acidic gas that is not recycled to the amine trim cooler 118 is directed to flow path 140c. The pressure and flow rate of the acidic gas within flow path 140c may be monitored with the PIT 116 and the FI 114, respectively. The flow controller 106 may be configured to control the flow of acidic gas to the amine contactor 102 by transmitting acidic gas flow measurements from FIT 110 to FCV 108 via control line 112. More specifically, the flow controller 106 may be able to control (e.g., throttle) the rate of flow and pressure within unit 101 using at least one FCV of the system 100 (e.g., FCV 108). The control line 112 may be a wireless connection, a wired connection, or both, though other types of connection are contemplated. In at least one embodiment, the acidic gas exits the flow controller 106 and travels along flow path 104d to enter the amine contactor 102 where the acidic gas is stripped of its acidic component.

In one non-limiting example, the stripper component 146 is upstream from the acid pumps 152, 154, the FITs 156, 158, the PIT 166, the FI 168, and each of the components of unit 101. Moreover, the stripper component 146 is located downstream from FCV 162 and FCV 146. The first acid pump 152 operates in parallel with the second acid pump 154. FIT 156, PIT 166, FI 168, and each of the components of unit 101 are downstream from pump 152. FIT 158, PIT 166, FI 168, and each of the components of unit 101 are downstream from pump 154. FCV 162 is downstream from FIT 156 and upstream from the stripper component 146. FCV 164 is downstream from FIT 158 and upstream from the stripper component 146.

In one non-limiting example, the amine trim component 118 is upstream from PI 120, PI 122, FCV 124, FCV 126, pump 128, pump 130, FIT 130, FIT 134, FCV 136, FCV 138, PIT 116, RI 114, FIT 110, FCV 108, and amine contactor 102. The amine trim cooler is downstream from FCV 142 and FCV 144. Pump 128 operates parallel to pump 130. FIT 132, FV 136, PIT 116, FI 114, each of the components of flow controller 106, and amine contactor 102 are downstream from pump 128. FCV 124 is upstream from pump 124. FIT 134, FCV 138, PIT 116, FI 114, each of the components of flow controller 106, and amine contactor 102 are downstream from pump 128. FCV 126 is upstream from pump 130. FCV 142 is downstream from FIT 132 and upstream from the amine trim cooler 118. FCV 144 is downstream from FIT 134 and upstream from the amine trim cooler 118. Amine contactor 102 is downstream from each of the other components of unit 101 and each of the components of unit 103.

In at least one embodiment, the first and second amine pumps 128, 130 (and optionally the acid pumps 152, 154) are capable of supporting an auto-start logic scheme (i.e., method). The auto-start logic may be stored in a non-transitory computer-readable medium on a computer system in communication with the amine pumps 128 and 130 (e.g., the computer system 700 of FIG. 7). In some cases, the auto-start logic scheme may be stored at one or more flow controller (FICs) (e.g., the FIC 402 of FIG. 4) associated with the computer system. The FIC(s) may have at least a memory and one or more processors having computer readable instructions stored thereon, which are capable of implementing the auto-start logic scheme. The one or more processor(s) may be central processing units (CPUs). Where there is more than one FIC, each FIC may operate independent from one another or as part of the same network of controllers. Where multiple FICs are part of the same network of controllers, they may operate in sequence with one another, in parallel with one another, as physical components of a shared virtual machine, or as components of server-less network capable of processing decomposed flow data. One example of an FIC implemented in system 100 is further illustrated in FIG. 2.

FIG. 2 illustrates an example control loop 200 as applied in the unit 101 of FIG. 1. As illustrated, the control loop 200 includes an FIC 202, a FCV 204, a FI 206, communication lines 208 and 210, and a flow path 212. The FCV 204 may be considered similar to FCV 136 and/or FCV 138. The FI 206 may be considered similar to FI 132 and/or 134. The flow path 212 may be considered similar to flow path 104b and/or flow path 104c. Acidic gas may be conveyed within the flow path 212, past the FI 206, and towards the FCV 204. The FIC 202 may receive information (e.g., flow rate data, etc.) from the FI 206 via the communication line 210, and based on the data received from the FI 206, the FIC 202 may be configured to communicate with and control the FCV 204 via the communication line 208. The communication lines 208, 210 may comprise wireless connections, wired connections, or both, though other types of connection (communication) are contemplated. In at least one embodiment, the FIC 202 may include multiple FICs. In at least one embodiment, the FIC 202 may be connected to (in communication with) other FICs within system 100 of FIG. 1 via a master controller (not shown).

The FIC(s) (e.g., FIC 202 of FIG. 2) may be capable of communicating with each of the components of the system 100 (FIG. 1) discussed herein (e.g., any of FCVs 108, 124, 126, 136, 138, 142, 144, 162, and 164). The auto-start logic scheme at the FIC(s) is a control scheme that may be capable of facilitating active/standby mode at each of the pumps. In one non-limiting example, the auto-start logic scheme may maintain the first amine pump 128 in an active state, while maintaining the second amine pump 130 in an idle state. Based on a trigger or signal, the auto-start logic scheme may reverse the state of pumps 128 and 130, placing the second amine pump 130 in an active state and the first amine pump 128 in an idle state. Based on another trigger or signal, the auto-start logic scheme may again reverse the state of the amine pumps 130 and 128, placing the first amine pump 128 in an active state and the second amine pump 130 in an idle state. In another non-limiting example, the auto-start logic scheme may maintain the second amine pump 130 in an active state, while maintaining the first amine pump 128 in an idle state.

In at least one embodiment, the auto-start logic scheme may operate autonomously. In other embodiments, however, the auto-start logic scheme may be operated according to user input. In at least one embodiment, the auto-start logic scheme may be active any time a system (e.g., system 100 of FIG. 1) is operational, or may be active only according to need of the user.

The auto-start logic scheme may be capable of ceasing operation of an active pump based on certain threshold values, switching full operation instead to the standby pump. The threshold values may include a pump capacity percentage value, a low flow threshold value for a common discharge header flow, a suction value, a pump capacity value, and the like. The active pump may fail to meet a threshold defined at the FIC(s) pumps when, for example, a common discharge header value drops below the setpoint of about 45% or more to about 55% or less pump capacity (e.g., for example 50% pump capacity, though other values are contemplated). The active pump may fail to meet a threshold defined at the FIC(s) when, for example, the flow at the common discharge header drops below a threshold of about 600 gallons per minute (GPM) or more to about 660 GPM or less, (e.g., for example 630 GPM, though other values are contemplated).

In some cases, to reverse the active and standby modes of a set of pumps, the FIC(s) may be operable to open an adjacent FCV (e.g., FCV 124, FCV 126) to allow more gas flow to the standby pump. In some cases, the FIC(s) may cause the pump in standby mode to start automatically at full capacity. Full capacity flow may be between 1000 GPM or more to about 1400 GPM or less, (e.g., for example 1200 GPM, though other values are contemplated). This may cause an issue where both the active pump and the standby pump temporarily maintain full operational capacity. This may double the flow rate at unit 101, creating undesirable conditions at unit 101 (e.g., low suction pressure upstream from each of the pumps, shut down (S/D) conditions, emergency shut down (ESD) conditions, low-low suction pressure conditions). In turn, this may cause both pumps to trip or fail as a safety instrumented function (SIF) that protects the pumps against low suction pressure or system vacuums. As a result, the standby pump may fail to start smoothly, wasting energy supplied to system 100 and reducing the efficiency of the sweetening procedure of system 100. Where the trip of the active and standby pumps are maintained with no autonomous restart, this may cause the entire system 100 to cease operation altogether, creating difficult externalities for system operators.

Aspects Related to Controlling the Operability of Amine Gas Pumps

Embodiments in accordance with the present disclosure generally relate to natural gas processing technology and, more particularly, to methods and systems for controlling the operability of amine gas pumps in a sour gas processing train. Aspects described herein may enhance the auto-logic control scheme described above by providing an override controller and override control scheme (i.e., method) in communication with each of the one or more FIC(s) (e.g., FIC 204 of FIGS. 2 and 3). The override control scheme is capable of overriding and/or supplementing control signals from the auto-start logic scheme, resulting in enhanced control of the pressure and flow of system 100 of FIG. 1. By implementing systems and methods discussed according to aspects provided herein, unnecessary pump trips and system stalls may be avoided. This may facilitate more steady and reliable operation for sour gas processing trains.

In at least one embodiment of the present disclosure, a control loop may be implemented in a gas processing system to mitigate the trip effect of the auto-start logic scheme, as described above. FIG. 3 illustrates an example control loop 300. The control loop 300 has an FIC 302 capable of implementing an auto-start logic scheme configured to communicate with an override control component 304 having an override control scheme. The control loop 300 includes an FIC 302, an override control component 304, a FCV 204, a FI 206, a communication line 306, a communication line 308, a communication line 310, and a flow path 212. The FCV 204 may be considered similar to FCV 136 and/or FCV 138. The FI 206 may be considered similar to FI 132 and/or 134. The flow path 212 may be considered similar to flow path 104b and/or flow path 104c. Acidic gas may flow along the flow path 212, past the FI 206, and towards the FCV 204. The FIC 302 may receive flow rate information from the FI 206 via communication line 310, and the FIC 302 may be configured to control the FCV 204 based on the data obtained by the FI 206 via communication lines 306 and 308.

In at least one embodiment, the override control component 304 may generate one or more signals to send to the FCV 204 via communication line 308 and based on one or more initial signals received from the FIC 302 via communication line 306. The override control component 304 may validate or modify the signals received from the FIC 302 based on flow values and pressure values detected within the system 100. In other embodiments, the override control component 304 may cancel signals from the FIC 302 based on flow values and pressure values detected within the system 100 (e.g., via FI(s) and/or PIT(s)). The communication lines 306, 308, 310 may comprise wireless or wired communication lines, or both, though other types of communication line are contemplated.

In at least one embodiment, the FIC 302 may include multiple FICs. In at least one embodiment, the FIC 302 may be connected to other FICs within system 100 of FIG. 1 via a master controller (not shown). In at least one embodiment, the override control component 304 may include multiple override control components. In at least one embodiment, the override control component 304 may be connected to other override control components within system 100 of FIG. 1 via a master controller (not shown). In at least one embodiment, the override control scheme is located at the override control component 304 and operates in sequence with the auto-start logic scheme at the FIC 302.

According to aspects of the present disclosure, the override control component 304 has dedicated resources (e.g., processing resources, memory resources, hardware resources, and/or software resources) which may allow it to effectively process override control scheme commands in order to optimize, for example, the common discharge header value of a system, a suction value of a system, a pump capacity value of a system, and the like. The override control component may achieve this by actuating FCV 204 to a precise actuation position via one or more signals sent from the override control component 304. Precise actuation may include opening the control value to a minimum flow capacity position, and intermediate flow capacity position, or a maximum flow capacity position. An intermediate flow capacity position may fall between a minimum flow capacity position and a maximum flow capacity position. The flow capacity position may be determined based on flow values and pressure values detected within the system 100 (e.g., via FI(s) and/or PIT(s)). This capability, which may be implemented to override any FIC (e.g., FIC 302) within a gas processing system (e.g., system 100), may mitigate the trip effect or fail-start that occurs when an active pump enters standby mode and a standby pump enters active mode. In this manner, the override control scheme may enhance the control system to maintain system stasis and to avoid processing interruptions.

FIG. 4 illustrates a schematic diagram of an example controller 400, which includes an FIC 402. Controller 400 may be implemented as part of control loop 300 of FIG. 3 and as part of the gas processing unit 101 of FIG. 1. Within gas processing unit 101, controller 400 may be implemented at a single location or at multiple locations and may be a master controller or may be in communication with a master controller by way of a communication line. In at least one embodiment, the communication line may be a wireless communication line, a wired communication line, or both, though other types of communication line are contemplated.

The FIC 402 may be similar to the FIC 302 of FIG. 3. The FIC 402 may be capable of communicating with each of the components of the system 100 discussed herein. Where there are more than one FIC 402, each of the FICs 402 may operate independent from one another or as part of the same network of controllers. Where multiple FICs 402 are part of the same network of controllers, they may operate in sequence with one another, in parallel with one another, as physical components of a shared virtual machine, or as components of server-less network capable of processing decomposed flow data.

The auto-start logic component 404 at the FIC 402 is a control component that may be capable of facilitating active/standby mode at each of the pumps, as described above with respect to FIG. 1. The auto-start logic component 404 may perform operations with the auto-start logic scheme described above with respect to FIG. 3.

Controller 400 also includes an override control component 406, which may be similar to the override control component 304 of FIG. 3. The override control component 406 may be capable of communicating with each of the components of the system 100 discussed herein. Where there are more than one override control component 406, each of the override control components 406 may operate independent from one another or as part of the same network of controllers. Where multiple override control components 406 are part of the same network of controllers, they may operate in sequence with one another, in parallel with one another, as physical components of a shared virtual machine, or as components of server-less network capable of processing decomposed flow data.

The override control component 406 is a control component that may be capable of relaying, modifying, or cancelling exchange control action signals from the auto-start logic component 404 to adjust an actuator component (e.g., FCV 204 of FIG. 3) to control downstream pressure, reduce suction, and thus reduce fail-starts and system trips. The override control component 406 may perform operations with the override control scheme described above with respect to FIG. 3. In at least one embodiment, the override control component 406 may operate autonomously, but may alternatively be operated according to user input. In at least one embodiment, the override control component 406 may be active any time a system (e.g., system 100 of FIG. 1) is operational, or may be active only according to need of the user.

In at least one embodiment, the auto-start logic component 404 receives flow information from an FI (e.g., FI 206 of FIG. 3), and detects one or more parameters. If one of the parameters exits (exceeds or falls below) a threshold range assigned to that parameter, the auto-start logic 404 outputs one or more exchange control action signals to a target FCV (e.g., FCV 204) to bring the parameters back within the threshold range, or otherwise implements an SIF function. In at least one embodiment, exiting a threshold range includes failing to meet a threshold value. In one example, the system (as indicated by an FI) may fail to meet a threshold when a common discharge header value drops below the setpoint of about 45% or more to about 55% or less pump capacity (e.g., for example 50% pump capacity, though other values are contemplated). In one example, the system (as indicated by an FI) may fail to meet a threshold when the flow at the common discharge header drops below a threshold of about 600 GPM or more to about 660 GPM or less, (e.g., for example 630 GPM, though other values are contemplated). In one example, the system (as indicated by an FI) may fail to meet a threshold when a suction pressure value drops below the setpoint. In at least one embodiment, the pressure value setpoint may be about 65 pounds per square inch/gauge (PSIG) or more to about 80 PSIG or less (e.g., 73 PSIG), though other values are contemplated. In one example, the system may exit a threshold range when the maximum capacity of a system component (e.g., a pump) is reached.

In at least one embodiment, the override control component 406 may receive the one or more exchange control action signals directed to the target FCV and may process the signals according to the needs of the system. In some cases, the override control component 406 may generate one or more new signals based on the received exchange control action signals. In at least one embodiment, the override control system 406 generates the one or more new signals by adjusting the signals to optimally control the target FCV, thus controlling the flow and pressure of the system to mitigate potential interruption. In at least one embodiment, the override control system 406 generates the one or more new signals by first validating the efficacy of the signals received from the auto-start logic component 404, and then reproducing the received signals to effectively relay them to the target FCV. In at least one embodiment, the override control system 406 generates the one or more new signals by cancelling the received signals and either transmitting a null signal to the target FCV or ending the signal flow (transmission).

The override control component 406 may operate across multiple controllers 400. In one example, an active pump may be controlled by a controller 400, and a standby pump may be controlled by a different controller 400. Each of the controllers 400 may communicate common information to optimize system performance, as discussed herein. Controller 400 may communicate, for example, via communication component 410.

In at least one embodiment, override control component 406 may be linked to an anti-wind up reset component (not shown) in order to provide feedback signals to a master controller. The anti-wind reset component may facilitate a pumpless control scheme. An anti-windup mechanism may prevent integral windup, which occurs when a controller's integral term accumulates error even when the actuator (e.g., an FCV) is saturated. This can lead to poor performance of the system.

The auto-start logic component 404 may include a CPU processing system, which may be configured to control the operability of amine gas pumps in a sour gas processing train as performed by controller 400. The CPU processing system of the auto-start logic component 404 may include one or more processors 414 coupled to a computer readable medium/memory 412 via a bus. The one or more processors 414 and the computer readable medium/memory 412 may communicate via a message passing interface (MPI) 408. In certain aspects the computer readable medium/memory 412 is configured to store instruction (e.g., computer executable code) that when executed by the one or more processors 414, cause the one or more processors to perform the method 500 described with respect to FIG. 5, or any aspect related to it. Reference to a processor performing a function of controller 400 may include one or more processors performing that function of controller 400.

In the depicted example, computer-readable medium/memory 414 stores code (e.g., executable instructions) for receiving 420, code for generating 422, and code for outputting 424. Processing of code 420-424 may cause the controller 400 to perform the method 500 described with respect to FIG. 5, or any aspect related to it.

The one or more processors 414 include circuitry configured to implement (e.g., execute) the code stored in the computer-readable medium/memory 412, including circuitry for receiving 426, circuitry for generating 428, and circuitry for outputting 430. Processing with circuitry 426-430 may cause the controller 400 to perform the method 500 described with respect to FIG. 5, or any aspect related to it.

The override control component 406 may include a CPU processing system. The CPU processing system may be configured to control the operability of amine gas pumps in a sour gas processing train as performed by controller 400. The CPU processing system of the override control component 406 may include one or more processors 418. The one or more processors 418 are coupled to a computer readable medium/memory 416 via a bus. The one or more processors 418 and the computer readable medium/memory 416 may communicate via an MPI 409. In certain aspects the computer readable medium/memory 416 is configured to store instruction (e.g., computer executable code) that when executed by the one or more processors 418, cause the one or more processors to perform the method 500 described with respect to FIG. 5, or any aspect related to it. Reference to a processor performing a function of controller 400 may include one or more processors performing that function of controller 400.

In the depicted example, computer-readable medium/memory 418 stores code (e.g., executable instructions) for receiving 432, code for generating 434, code for outputting 436, code for relaying 438, code for modifying 440, and code for cancelling 442. Processing of code 432-442 may cause the controller 400 to perform the method 500 described with respect to FIG. 5, or any aspect related to it.

The one or more processors 418 include circuitry configured to implement (e.g., execute) the code stored in the computer-readable medium/memory 416, including circuitry for receiving 444, circuitry for generating 446, circuitry for outputting 448, circuitry for relaying 450, circuitry for modifying 452, and circuitry for cancelling 454. Processing with circuitry 444-454 may cause the controller 400 to perform the method 500 described with respect to FIG. 5, or any aspect related to it.

Various components of the controller 400 may provide means for performing the method 500 described with respect to FIG. 5, or any aspect related to it.

The auto-start logic component 404 may communicate with the override control component 406 to perform the method 500 described with respect to FIG. 5, or any aspect related to it. In one example, the auto-start logic component 404 may be coupled to the override control component 406 via bus. The auto-start logic component 404 and the override control component 406 may communicate via an MPI 409, a land area network (LAN), a fiber optic connection, or another type of wired communication. In one example, the auto-start logic component 404 may be coupled to the override control component 406 wirelessly. The auto-start logic component 404 and the override control component 406 may communicate via a wireless LAN, a Bluetooth spectrum connection, a cellular network, a satellite network, a near field connection (NFC), or another type of wireless network.

The controller may include a communication component 410. In the depicted example, the communication component 410 is an antenna capable of communicating with controllers similar to controller 400 to perform the method 500 described with respect to FIG. 5, or any aspect related to it. In additional examples, the communication component 410 may be a bus or a wired connection.

Example Methods

FIG. 5 is a schematic flowchart of an example method 500 for controlling an amine gas pump system by one or more processors, such as the processors of controller 400 of FIG. 4.

Method 500 begins at operation 502 with one or more processors receiving, from an auto-start logic component, one or more initial control signals generated in response to at least one parameter exiting a threshold range. In at least one example, the at least one parameter includes at least one of: a common discharge header setpoint value, a pump capacity setpoint value, a max capacity limit, and a suction pressure value. In at least one example, exiting a threshold range includes measuring the common discharge header setpoint value to be below 630 gallons per minute, measuring the pump capacity setpoint value to be below 50% pump capacity, detecting the max capacity limit for a pump, or measuring the suction pressure value to be below a setpoint value. In at least one embodiment, the suction pressure value setpoint may be about 65 pounds per square inch/gauge (PSIG) or more to about 80 PSIG or less (e.g., 73 PSIG), though other values are contemplated. In at least one example, the one or more initial control signals are exchange control action signals configured to actuate the at least one flow control valve to a maximum actuation position.

Method 500 continues to operation 504 with one or more processors generating one or more control signals based on the one or more initial control signals. In at least one example, the one or more control signals are configured to control a first flow from an active pump, a second flow from a standby pump, or both the first flow and the second flow.

Method 500 continues to operation 506 with one or more processors outputting the one or more control signals, the one or more control signals configured to adjust a flow control valve.

In at least one embodiment, the method 500 may include an operation by one or more processors to receive flow information from a flow indicator, the flow indicator detecting the at least one parameter, and output the one or more initial control signals, the one or more initial control signals generated based on the detecting.

In at least one embodiment, the method 500 may include an operation by one or more processors to validate the one or more initial control signals, and relay the one or more initial control signals to the flow control valve.

In at least one embodiment, the method 500 may include an operation by one or more processors to modify the one or more initial control signals to construct the one or more control signals, the one or more control signals being configured to actuate the flow control valve to an intermediate position. In at least one example, the one or more control signals are configured to adjust the flow control valve to maintain a flow value of a system and a pressure value of the system.

In at least one embodiment, the method 500 may include an operation by one or more processors to cancel the one or more initial control signals.

In one aspect, method 500, or any aspect related to it, may be performed by an apparatus, such as controller 400 of FIG. 4, which includes various components operable, configured to, or adapted to perform the method 500. Controller 400 is described above in further detail.

FIG. 5 is just one example of a method, and other methods including fewer, additional, or alternative operations are contemplated consistent with the disclosure.

Example Computer System

FIG. 6 is an example of a block diagram of a system 600. The system 600 can be implemented using one or more modules, shown in block form in at least FIGS. 3-5. The one or more modules can be in software or hardware form, or a combination thereof. In some examples, the system 600 can be implemented as machine readable instructions for execution on one or more computing platforms 602 (referred to as a computing platform herein), as shown in FIG. 6. The computing platform 602 can include one or more computing devices selected from, for example, a desktop computer, a server, a controller, a blade, a mobile phone, a tablet, a laptop, a personal digital assistant (PDA), and the like.

The computing platform 604 can include a processor 604 and a memory 606. By way of example, the memory 606 can be implemented, for example, as a non-transitory computer storage medium, such as volatile memory (e.g., random access memory), non-volatile memory (e.g., a hard disk drive, a solid-state drive, a flash memory, or the like), or a combination thereof. The processor 604 can be implemented, for example, as one or more processor cores. The memory 606 can store machine-readable instructions that can be retrieved and executed by the processor 604 to implement the system 600. Each of the processor 604 and the memory 606 can be implemented on a similar or a different computing platform. The computing platform 602 can be implemented in a cloud computing environment (for example, as disclosed herein) and thus on a cloud infrastructure. In such a situation, features of the computing platform 602 can be representative of a single instance of hardware or multiple instances of hardware executing across the multiple of instances (e.g., distributed) of hardware (e.g., computers, routers, memory, processors, or a combination thereof). Alternatively, the computing platform 602 can be implemented on a single dedicated server or workstation. In view of the structural and functional features described above, example methods will be better appreciated with reference to FIG. 5.

In view of the foregoing structural and functional description, those skilled in the art will appreciate that portions of the embodiments may be embodied as a method, data processing system, or computer program product. Accordingly, these portions of the present embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware, such as shown and described with respect to the computer system of FIG. 7. Furthermore, portions of the embodiments may be a computer program product on a computer-readable storage medium having computer readable program code on the medium. Any non-transitory, tangible storage media possessing structure may be utilized including, but not limited to, static and dynamic storage devices, volatile and non-volatile memories, hard disks, optical storage devices, and magnetic storage devices, but excludes any medium that is not eligible for patent protection under 35 U.S.C. § 101 (such as a propagating electrical or electromagnetic signals per se). As an example and not by way of limitation, computer-readable storage media may include a semiconductor-based circuit or device or other IC (such, as for example, a field-programmable gate array (FPGA) or an ASIC), a hard disk, an HDD, a hybrid hard drive (HHD), an optical disc, an optical disc drive (ODD), a magneto-optical disc, a magneto-optical drive, a floppy disk, a floppy disk drive (FDD), magnetic tape, a holographic storage medium, a solid-state drive (SSD), a RAM-drive, a SECURE DIGITAL card, a SECURE DIGITAL drive, or another suitable computer-readable storage medium or a combination of two or more of these, where appropriate. A computer-readable non-transitory storage medium may be volatile, nonvolatile, or a combination of volatile and non-volatile, as appropriate.

Certain embodiments have also been described herein with reference to block illustrations of methods, systems, and computer program products. It will be understood that blocks and/or combinations of blocks in the illustrations, as well as methods or steps or acts or processes described herein, can be implemented by a computer program comprising a routine of set instructions stored in a machine-readable storage medium as described herein. These instructions may be provided to one or more processors of a general purpose computer, special purpose computer, or other programmable data processing apparatus (or a combination of devices and circuits) to produce a machine, such that the instructions of the machine, when executed by the processor, implement the functions specified in the block or blocks, or in the acts, steps, methods and processes described herein.

These processor-executable instructions may also be stored in computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture including instructions which implement the function specified. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to realize a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in flowchart blocks that may be described herein.

In this regard, FIG. 7 illustrates one example of a computer system 700 that can be employed to execute one or more embodiments of the present disclosure. Computer system 700 can be implemented on one or more general purpose networked computer systems, embedded computer systems, routers, switches, server devices, client devices, various intermediate devices/nodes or standalone computer systems. Additionally, computer system 700 can be implemented on various mobile clients such as, for example, a personal digital assistant (PDA), laptop computer, pager, and the like, provided it includes sufficient processing capabilities.

Computer system 700 includes processing unit 702, system memory 704, and system bus 706 that couples various system components, including the system memory 704, to processing unit 702. System memory 704 can include volatile (e.g. RAM, DRAM, SDRAM, Double Data Rate (DDR) RAM, etc.) and non-volatile (e.g. Flash, NAND, etc.) memory. Dual microprocessors and other multi-processor architectures also can be used as processing unit 702. System bus 706 may be any of several types of bus structure including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. System memory 704 includes read only memory (ROM) 710 and random access memory (RAM) 712. A basic input/output system (BIOS) 714 can reside in ROM 710 containing the basic routines that help to transfer information among elements within computer system 700.

Computer system 700 can include a hard disk drive 716, magnetic disk drive 718, e.g., to read from or write to removable disk 720, and an optical disk drive 722, e.g., for reading CD-ROM disk 724 or to read from or write to other optical media. Hard disk drive 716, magnetic disk drive 718, and optical disk drive 722 are connected to system bus 706 by a hard disk drive interface 726, a magnetic disk drive interface 728, and an optical drive interface 730, respectively. The drives and associated computer-readable media provide nonvolatile storage of data, data structures, and computer-executable instructions for computer system 700. Although the description of computer-readable media above refers to a hard disk, a removable magnetic disk and a CD, other types of media that are readable by a computer, such as magnetic cassettes, flash memory cards, digital video disks and the like, in a variety of forms, may also be used in the operating environment; further, any such media may contain computer-executable instructions for implementing one or more parts of embodiments shown and described herein.

A number of program modules may be stored in drives and RAM 710, including operating system 732, one or more application programs 734, other program modules 736, and program data 738. In some examples, the application programs 734 can include the auto-start logic scheme and/or the override control scheme, and the program data 738 can include signals obtained and output from an override control component. The application programs 734 and program data 738 can include functions and methods programmed to controlling an amine gas pump system by one or more processors, such as controlling the actuation of a FCV, such as shown and described herein.

A user may enter commands and information into computer system 700 through one or more input devices 740, such as a pointing device (e.g., a mouse, touch screen), keyboard, microphone, joystick, game pad, scanner, and the like. For instance, the user can employ input device 740 to edit or modify initial control signals received from an auto-start logic component, as described herein. These and other input devices 740 are often connected to processing unit 702 through a corresponding port interface 742 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, serial port, or universal serial bus (USB). One or more output devices 744 (e.g., display, a monitor, printer, projector, or other type of displaying device) is also connected to system bus 706 via interface 746, such as a video adapter.

Computer system 700 may operate in a networked environment using logical connections to one or more remote computers, such as remote computer 748. Remote computer 748 may be a workstation, computer system, router, peer device, or other common network node, and typically includes many or all the elements described relative to computer system 700. The logical connections, schematically indicated at 750, can include a local area network (LAN) and/or a wide area network (WAN), or a combination of these, and can be in a cloud-type architecture, for example configured as private clouds, public clouds, hybrid clouds, and multi-clouds. When used in a LAN networking environment, computer system 700 can be connected to the local network through a network interface or adapter 752. When used in a WAN networking environment, computer system 700 can include a modem, or can be connected to a communications server on the LAN. The modem, which may be internal or external, can be connected to system bus 706 via an appropriate port interface. In a networked environment, application programs 734 or program data 738 depicted relative to computer system 700, or portions thereof, may be stored in a remote memory storage device 754.

Although this disclosure includes a detailed description on a computing platform and/or computer, implementation of the teachings recited herein are not limited to only such computing platforms. Rather, embodiments of the present disclosure are capable of being implemented in conjunction with any other type of computing environment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models (e.g., software as a service (SaaS, platform as a service (PaaS), and/or infrastructure as a service (IaaS)) and at least four deployment models (e.g., private cloud, community cloud, public cloud, and/or hybrid cloud). A cloud computing environment can be service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability.

The present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention. The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, for example, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “contains”, “containing”, “includes”, “including,” “comprises”, and/or “comprising,” and variations thereof, when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Terms of orientation used herein are merely for purposes of convention and referencing and are not to be construed as limiting. However, it is recognized these terms could be used with reference to an operator or user. Accordingly, no limitations are implied or to be inferred. In addition, the use of ordinal numbers (e.g., first, second, third, etc.) is for distinction and not counting. For example, the use of “third” does not imply there must be a corresponding “first” or “second.” Also, if used herein, the terms “coupled” or “coupled to” or “connected” or “connected to” or “attached” or “attached to” may indicate establishing either a direct or indirect connection, and is not limited to either unless expressly referenced as such. Furthermore, to the extent that the terms “includes,” “has,” “possesses,” and the like are used in the detailed description, claims, appendices and drawings such terms are intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim. The term “based on” means “based at least in part on.” The terms “about” and “approximately” can be used to include any numerical value that can vary without changing the basic function of that value. When used with a range, “about” and “approximately” also disclose the range defined by the absolute values of the two endpoints, e.g. “about 2 to about 4” also discloses the range “from 2 to 4.” Generally, the terms “about” and “approximately” may refer to plus or minus 5-10% of the indicated number.

While the disclosure has described several exemplary embodiments, it will be understood by those skilled in the art that various changes can be made, and equivalents can be substituted for elements thereof, without departing from the spirit and scope of the invention. In addition, many modifications will be appreciated by those skilled in the art to adapt a particular instrument, situation, or material to embodiments of the disclosure without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiments disclosed, or to the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims. Moreover, reference in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, or component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative.