Patent Application
20190323337
The present disclosure generally relates to fluid delivery systems and related methods and computer program products and more particularly to fluid delivery systems and related methods and computer program products that comprise at least one sensing device configured to detect at least one aspect of such fluid delivery systems.
The statements in this section merely provide background information related to the present disclosure and may not constitute prior art.
Fluids are used in a variety of applications for various purposes, including engine or system cooling, lubrication, as well as various oilfield operations. In order to be utilized in such various applications, fluid delivery systems are needed to deliver the fluid(s) to appropriate locations at appropriate times and in appropriate configurations (e.g., appropriate flow rates, densities, compositions, volumes, pressures, temperatures, viscosities, etc.). For example, fluid delivery systems are used in many types of oilfield operations that facilitate the extraction of hydrocarbons and natural gas from underground formations. One such oilfield operation is known as hydraulic fracturing. Hydraulic fracturing typically involves pumping fluid(s) down a wellbore at pressures and/or flow rates that are capable of fracturing subterranean formations, thereby inducing the flow of hydrocarbons from those formations.
Generally, hydraulic fracturing is used for unconventional subterranean formations, where the significantly low permeability of the formations causes hydrocarbons to become “trapped” in the rocks, thereby preventing them from flowing freely into a wellbore. Common hydraulic fracturing techniques involve utilizing at least one fluid delivery system to pump one or more fluids down a wellbore at a pressure and/or flow rate that is greater than the fracture gradient of the particular formation that contains the wellbore. Such fluid(s) may comprise one or more additives referred to as “proppant.” Proppant often comprises a sand-like texture due to its particulate properties. The pumping process creates fractures in the rocks of the formation that may be filled by the proppant so that the fractures are not immediately closed again due to the immense subterranean geological pressures they experience. The proppant also provides a highly permeable conduit within the fractures that allows the newly released hydrocarbons to easily flow to the wellbore where they can be recovered.
The process of hydraulic fracturing typically requires at least one fluid delivery system that includes a variety of different components. For example, several trucks and/or trailers are needed to carry fresh water, one or more chemicals or other fluids, proppant or other additives, at least one manifold (also known as a “missile”), and at least one pumping mechanism. The water is mixed with the chemical(s), fluid(s), proppant, and/or other additives by a device known as a blender, thereby forming a mixture typically referred to as “slurry.” This slurry then gets pumped to the manifold, which typically comprises a high-pressure side and a low-pressure side. Slurry is received by the manifold at one or more inlets on the low-pressure side. The slurry is then redirected by the manifold to a pressurizing pumping mechanism, or “frac pump,” configured on a separate truck/trailer adjacent to the manifold. The frac pump significantly increases the pressure of the slurry and then directs it to the high-pressure side of the manifold. The manifold may then distribute the high-pressure slurry to the opening of a wellbore so that it may be used to propagate one or more fractures downhole.
During a hydraulic fracturing process (or any similar fluid delivery process), it is not uncommon for one or more fluid delivery system components to experience one or more problems or issues or to fail entirely. For example, the frac pump(s) generally experience a significant amount of stress and wear that may cause them to breakdown or stop functioning completely. When equipment failure does occur, the entire fracturing process and, if relevant, drilling process must be suspended in order to manually inspect and/or test the manifold, each frac pump, as well as any other relevant fluid delivery system component(s), including any tubes, pipes, hoses, or lines that interconnect the different components of the system, in order to identify the problem and determine a remedy. Depending on how long the inspection and/or testing process takes, a considerable amount of money may be lost due to the suspension of the oilfield operations at the wellbore.
A variety of events may initiate the failure of the various component(s) involved with any fluid delivery system, including those utilized with hydraulic fracturing. For example, head loss, or pressure loss, may occur within one or more sections of tubing or piping due to wear and tear caused by friction; cavitation may occur within one or more system components; flow rates may reach undesirable levels; one or more leaks may develop that may need to be compensated for; and/or the volume of proppant, chemicals, and/or other additives being mixed with water may need to be adjusted. If these events are not identified and addressed in a timely manner, they may cause damage to the affected system component(s) and require them to be repaired and/or replaced, thereby increasing unwanted costs resulting from oilfield operation suspension.
Given the foregoing, fluid delivery systems, methods, and computer program products are needed that allow one or more problems or issues within one or more fluid delivery system components to be identified in a timely manner. Additionally, fluid delivery systems, methods, and computer program products are needed that allow a user to address and/or resolve one or more problems or issues within one or more fluid delivery system components in a timely manner are needed. Fluid delivery systems, methods, and computer program products that facilitate the mitigation and/or prevention of damage to one or more fluid delivery system components are also desired.
This Summary is provided to introduce a selection of concepts. These concepts are further described below in the Detailed Description section. This summary is not intended to identify key features or essential features of this disclosure's subject matter, nor is this Summary intended as an aid in determining the scope of the disclosed subject matter.
Aspects of the present disclosure meet the above-identified needs by providing fluid delivery systems, methods, and computer program products that facilitate the identification of and, if necessary, resolution of one or more problems or issues within one or more fluid delivery system components in a timely manner. Specifically, in an aspect, fluid delivery systems, methods, and computer program products are disclosed that may comprise at least one sensing device that may be configured to detect at least one aspect of a given fluid delivery system, including, for example, at least one flow rate, at least one pressure measurement, at least one density measurement, at least one velocity measurement, at least one temperature measurement, at least one viscosity measurement, at least one composition assessment, and/or at least one volume measurement for at least one fluid passing through at least one portion of at least one component of the system. The sensing device(s) may be configured at any appropriate location(s) within and/or upon one or more portions of one or more components of a particular fluid delivery system where they may be able to make adequate detections and/or measurements, including within and/or upon one or more sections of piping and/or tubing (including high and/or low-pressure piping and/or tubing), within and/or upon one or more pumping mechanisms, within and/or upon one or more portions of at least one manifold apparatus, and/or within and/or upon one or more portions of at least one blending apparatus.
In some aspects, the sensing device(s) used with the fluid delivery systems, methods, and computer program products of the present disclosure may be communicatively coupled to one or more computing devices. Such computing devices may be configured with various computational instructions, or code, in the form of software or one or more software applications that, when executed on at least one computer processor, causes the at least one computer processor to perform certain steps or processes, including interpreting and/or analyzing detected, measured, or sensed data received from one or more sensing devices associated with a given fluid delivery system and/or presenting the detected/measured/sensed data and/or analysis results to at least one user. In some additional aspects, the software or software applications may facilitate the ability of one or more users to instruct the computing device(s), via one or more input devices, to make one or more adjustments to one or more aspects of the fluid delivery systems of the present disclosure, including adjusting one or more flow rates, adjusting at least one internal pressure, adjusting at least one density, adjusting at least one velocity, adjusting at least one temperature, adjusting at least one viscosity, adjusting at least one composition, and adjusting at least one internal volume of one or more fluids passing through at least one portion of at least one component of a given fluid delivery system. In still some additional aspects, the software and/or software applications may cause the computer processor(s) associated with the one or more computing devices to initiate or make any necessary or desired adjustments to at least one fluid delivery process associated with at least one fluid delivery system in an at least semi-autonomous fashion, with only partial or no user input. In such aspects, the software and/or software applications may be programmed to maintain various aspects of the fluid delivery system at certain predetermined levels (e.g., maintain certain flow rates, maintain certain pressures, maintain certain densities, maintain certain velocities, maintain certain temperatures, maintain certain viscosities, maintain certain compositions, and/or maintain certain volumes of one or more fluids passing through at least one portion of at least one component of a given fluid delivery system) by, for example, comparing detected aspects of the fluid delivery system with one or more predetermined standards or values and determining whether the detected aspects are within a tolerable deviation of the predetermined standard(s) or value(s).
Further features and advantages of the present disclosure, as well as the structure and operation of various aspects of the present disclosure, are described in detail below with reference to the accompanying drawings.
The features and advantages of the present disclosure will become more apparent from the Detailed Description set forth below when taken in conjunction with the drawings in which like reference numbers indicate identical or functionally similar elements.
The present disclosure is directed to fluid delivery systems and related methods and computer program products for facilitating the efficient detection of and, if necessary, resolution of one or more problems or issues that may arise during operation of such fluid delivery systems and/or one or more components thereof. Specifically, in an aspect, fluid delivery systems and related methods and computer program products are disclosed that may comprise one or more sensing devices, each of which may be configured to detect at least one aspect of a particular fluid delivery system. The sensing device(s) may be further configured to present detected data and/or other information to one or more users in order to enable the user(s) to determine whether any adjustments need to be made to the operation, functionality, and/or configuration of a particular fluid delivery system. In some aspects, a user may utilize one or more computing devices to view and/or make changes to one or more aspects of a particular fluid delivery system. In some additional aspects, one or more computing devices may be configured to detect one or more aspects of a particular fluid delivery system, determine whether any changes need to be made thereto, and initiate such changes in an at least semi-autonomous manner.
The term “fluid delivery system” and/or the plural form of this term are used throughout herein to refer to any system, machine, apparatus, mechanism, or device that may function, at least partially, either by itself or in conjunction with one or more additional systems or components, to transfer an amount of at least one fluid from at least one fluid source to at least one fluid destination, such as manifolds, pressure pumps, transfer pumps, other pumping mechanisms, gravity fed distribution lines, tanks, vessels, blenders, other blending apparatuses, suction valves, distribution valves, wells, irrigation systems, pipes, tubes, hoses, and the like.
The term “additive” and/or the plural form of this term are used throughout herein to refer to any substance, particle, or element that may be added to one or more fluids to be used during the functioning or operation of at least one fluid delivery system, such as proppant, chemicals, acids, sodium chloride, polyacrylamide, ethylene glycol, borate salts, sodium carbonates, potassium carbonates, glutaraldehyde, guar gum, citric acid, isopropanol, friction reducers, disinfectants, gelling agents, breakers, emulsifiers, stabilizers, surfactants, potassium chloride (KCl), iron control chemicals, oxygen scavengers, scale inhibitors, pH adjusting agents, carboxymethyl hydroxypropyl guar (CMHPG) gels, corrosion inhibitors, biocides, and the like.
The term “fluid” and/or the plural form of this term are used throughout herein to refer to any liquid and/or gaseous substance(s) that may pass through at least one portion of at least one fluid delivery system as defined above, including one or more portions of one or more components thereof, such as water, oil, methanol, slickwater, gasoline, one or more petroleum products, one or more chemicals, one or more gels, one or more crosslinkers, saltwater, brine, one or more acids, produced water, dirty water, liquefied natural gas (LNG), biofuel (or one or more products thereof), pipeline quality natural gas (or any quality natural gas), propane, diesel fuel, fuel oil, and the like.
The term “manifold” and/or the plural form of this term are used throughout herein to refer to any device, mechanism, apparatus, or structure comprised of one or more pipe, tube, and/or hose fittings and having one or more lateral outlets for connecting at least one pipe, tube, and/or hose with one or more additional pipes, tubes, and/or hoses, such as fracturing (or “frac”) manifolds, missiles, missile trailers, exhaust manifolds, zipper manifolds, blender manifolds, transfer pumps, hydration manifolds, water vessel manifolds, and the like.
The term “sensing device” and/or the plural form of this term are used throughout herein to refer to any device, apparatus, element, mechanism, or component that may be capable of sensing and/or detecting at least one physical property, such as flow measuring devices (including flow meters, magnetic flow meters, electromagnetic flow meters, turbine style flow meters, and mass flow (i.e., Coriolis) flow meters); density measuring devices (including densimeters); temperature measuring devices (including thermometers and temperature meters); viscosity measuring devices (including viscometers and rheometers); pressure measuring devices (including pressure transducers and pressure meters); velocity sensing devices (including flow velocity measuring devices and anemometers); volume measuring devices (including volume sensors); hydrometers; composition analyzing devices; and the like.
Referring now to
Cloud-based, Internet-enabled device communication system 100 may include a plurality of users 102 (shown as users 102a-g in
In some embodiments, a user 102 may communicate with a fluid delivery system 106 via computing device 104 in order to detect, view, identify, determine, and/or initiate the resolution of one or more problems or issues associated with one or more aspects of and/or with the operation, functionality, and/or configuration of fluid delivery system 106. In some additional aspects, a user 102h may communicate directly with fluid delivery system 106 using at least one control station 108 and/or one or more input devices that may be associated therewith (such as, for example and not limitation, a mouse, keyboard, touchscreen, joystick, microphone, camera, scanner, chip reader, card reader, magnetic stripe reader, near field communication technology, and the like). By way of example and not limitation, control station 108 may comprise a computer kiosk communicatively coupled (either via wireless media (such as, for example and not limitation, to enable usage from one or more remote locations) or via wired connectivity) to fluid delivery system 106, or any similar computational and/or electronic device(s) as may be apparent to those skilled in the relevant art(s) after reading the description herein, as well as any combination thereof. In still some additional aspects, control station 108 may be used to perform any of the tasks that may be performed by/using computing device 104.
In various aspects, computing device 104 may be configured as: a desktop computer 104a, a laptop computer 104b, a tablet or mobile computer 104c, a smartphone (alternatively referred to as a mobile device) 104d, a Personal Digital Assistant (PDA) 104e, a mobile phone 104f, a handheld scanner 104g, any commercially-available intelligent communications device, or the like.
As shown in
User database 126 may be configured to store information pertaining to one or more users 102. In an aspect, a user 102 may comprise any individual or entity that may be responsible for and/or otherwise concerned with the functionality, operation, and/or configuration of a given fluid delivery system 106. User 102 information that may be stored within user database 126 may include, by way of example and not limitation, a given user's 102 name, type (e.g., whether user 102 is an individual, entity, nonprofit organization, etc.), account or profile information (e.g., account settings, account usage history, background information regarding user 102, etc.), location, infrastructure 101 usage history, login credentials (including, but not limited to, passwords, usernames, passcodes, pin numbers, fingerprint scan data, retinal scan data, voice authentication data, facial recognition information, and the like), and the like.
Fluid delivery system database 128 may be configured to store information pertaining to one or more fluid delivery systems 106. In an aspect, a fluid delivery system 106 may comprise any system, machine, apparatus, or device that may function, at least partially, either by itself or in conjunction with one or more additional systems or components, to transfer an amount of at least one fluid from at least one fluid source 202 (not shown in
Control station database 130 may be configured to store information pertaining to at least one control station 108. In some aspects, by way of example and not limitation, control station 108 may comprise a computer kiosk communicatively coupled (either via wireless media (such as, for example and not limitation, to enable usage from one or more remote locations) or via wired connectivity) to fluid delivery system 106 and configured to identify, detect, present, interpret, compare, determine, and/or analyze one or more aspects of fluid delivery system 106; or, control station 108 may comprise any similar computational or electronic device that may be apparent to those skilled in the relevant art(s) after reading the description herein. Control station 108 information that may be stored within control station database 130 may include, by way of example and not limitation, control station 108 usage history (e.g., which user(s) 102 have used control station 108, how long various user(s) 102 have used control station 108, and the like), control station 108 manufacturer information, control station 108 specifications and/or capabilities, list of problems or issues previously identified using control station 108, list of problems or issues previously resolved using control station 108, list of problems or issues pending under control station 108, control station 108 infrastructure 101 usage history, login credentials required to access and/or utilize fluid control station 108 (including passwords, usernames, passcodes, pin numbers, fingerprint scan data, retinal scan data, voice authentication data, facial recognition information, and the like), and the like.
User database 126, fluid delivery system database 128, and control station database 130 may each be physically separate from one another, logically separate, or physically or logically indistinguishable from some or all other databases.
A system administrator 134 may access infrastructure 101 via the Internet 132 in order to oversee and manage infrastructure 101.
As will be appreciated by those skilled in the relevant art(s) after reading the description herein, an application service provider—an individual person, business, or other entity—may allow access, on a free registration, paid subscriber, and/or pay-per-use basis, to infrastructure 101 via one or more World-Wide Web (WWW) sites on the Internet 132. Thus, system 100 is scalable.
As will also be appreciated by those skilled in the relevant art(s), in an aspect, various screens may be generated by server 122 in response to input from user(s) 102 over Internet 132. As a nonlimiting example, server 122 may comprise a typical web server running a server application at a website which sends out webpages in response to Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secured (HTTPS) requests from remote browsers on various computing devices 104 or control stations 108 being used by various users 102. Thus, server 122 is able to provide a graphical user interface (GUI) to users 102 that utilize system 100 in the form of webpages. These webpages are sent to the user's 102 PC, laptop, mobile device, PDA, or like device 104 or control station 108, and would result in the GUI being displayed.
As will be appreciated by those skilled in the relevant art(s) after reading the description herein, alternate aspects of the present disclosure may include providing a tool for facilitating the detection of, identification of, and/or resolution of one or more problems or issues associated with one or more aspects of and/or with the operation of, functionality of, and/or configuration of fluid delivery system(s) 106 to user(s) 102 via computing device(s) 104 and/or control station(s) 108 as a stand-alone system (e.g., installed on one server PC) or as an enterprise system wherein all the components of system 100 are connected and communicate via an inter-corporate Wide Area Network (WAN) or Local Area Network (LAN). For example, in an aspect where users 102 are all personnel/employees of the same company or are all members of the same group, the present disclosure may be implemented as a stand-alone system, rather than as a web service (i.e., Application Service Provider (ASP) model utilized by various unassociated/unaffiliated users) as shown in
As will also be appreciated by those skilled in the relevant art(s) after reading the description herein, alternate aspects of the present disclosure may include providing the tools for facilitating the detection of, identification of, and/or resolution of one or more problems or issues associated with one or more aspects of and/or with the operation of, functionality of, and/or configuration of fluid delivery system(s) 106 to user(s) 102 via infrastructure 101, computing device(s) 104, and/or control station(s) 108 via a browser or operating system pre-installed with an application or a browser or operating system with a separately downloaded application on such computing device(s) 104 and/or control station(s) 108. That is, as will also be apparent to those skilled in the relevant art(s) after reading the description herein, the application that facilitates the detection of, identification of, and/or resolution of one or more problems or issues associated with one or more aspects of and/or with the operation of, functionality of, and/or configuration of fluid delivery system(s) 106 for user(s) 102 may be part of the “standard” browser or operating system that ships with computing device 104 or control station 108 or may be later added to an existing browser or operating system as part of an “add-on,” “plug-in,” or “app store download.”
Infrastructure 101 may be encrypted to provide for secure communications. A security layer may be included that is configurable using a non-hard-cooled technique selectable by user 102 which may be based on at least one of: user 102, country encryption standards, etc. A type of encryption may include, but is not limited to, protection at least at one communication protocol layer such as the physical hardware layer, communication layer (e.g., radio), data layer, software layer, etc. Encryption may include human interaction and confirmation with built-in and selectable security options, such as, but not limited to, encoding, encrypting, hashing, layering, obscuring, password protecting, obfuscation of data transmission, frequency hopping, and various combinations thereof. As a nonlimiting example, the prevention of spoofing and/or eavesdropping may be accomplished by adding two-prong security communication and confirmation using two or more data communication methods (e.g., light and radio) and protocols (e.g., pattern and freq. hopping). Thus, at least one area of security, as provided above, may be applied to at least provide for communication being encrypted while in the cloud; communication with user 102, communication with fluid delivery system 106, and/or communication with control station 108 that may occur via the Internet 132, a Wi-Fi connection, Bluetooth (a wireless technology standard standardized as IEEE 802.15.1), satellite, or another communication link; communications between computing device(s) 104 and fluid delivery system 106; communications between control station(s) 108 and fluid delivery system 106; communications between computing device(s) 104 and control station(s) 108; communications between Internet of Things devices and fluid delivery system 106 and/or control station(s) 108; and the like.
The Internet of Things, also known as IoT, is a network of physical objects or “things” embedded with electronics, software, sensors, and connectivity to enable objects to exchange data with the manufacturer, operator, and/or other connected devices based on the infrastructure of International Telecommunication Union's Global Standards Initiative. The Internet of Things allows objects to be sensed and controlled remotely across existing network infrastructure, creating opportunities for more direct integration between the physical world and computer-based systems, and resulting in improved efficiency, accuracy, and economic benefit. Each thing is uniquely identifiable through its embedded computing system but is able to interoperate within the existing Internet infrastructure. Communications may comprise use of transport layer security (“TLS”), fast simplex link (“FSL”), data distribution service (“DDS”), hardware boot security, device firewall, application security to harden from malicious attacks, self-healing/patching/firmware upgradability, and the like. Security may be further included by use of at least one of: obfuscation of data transmission, hashing, cryptography, public key infrastructure (PKI), secured boot access, and the like.
Referring now to
In some nonlimiting exemplary embodiments, fluid delivery system 106 may comprise a configuration substantially similar to exemplary fluid delivery system 200 depicted in
Fluid delivery system 200 may be configured to transfer an amount of at least one fluid from fluid source(s) 202 to fluid destination(s) 208 via piping section(s) 204. Piping section(s) 204 may be configured to at least partially contain the amount of fluid(s) to be transferred via fluid delivery system 200. By way of example and not limitation, piping section(s) 204 may comprise high-pressure piping, low-pressure piping, stainless steel piping, carbon steel piping, tubing, hosing, polyvinyl chloride (PVC) piping, any type of fluid line, as well as any similar materials and/or configurations as may be apparent to those skilled in the relevant art(s) after reading the description herein, including any combination thereof. The movement that enables the transferring of the at least one fluid may be at least partially facilitated by gravitational forces. In aspects wherein at least one pumping mechanism 206 may be included with fluid delivery system 200, the movement of the at least one fluid within fluid delivery system 200 may be at least partially facilitated by the functioning of such pumping mechanism(s) 206.
By way of example and not limitation, fluid source(s) 202 may comprise any appropriate location, container, or configuration that is capable of holding an amount of at least one fluid, either manmade or naturally occurring, such as one or more tanks, vessels, reservoirs, trucks, trailers, wells, ponds, rivers, lakes, oceans, and the like. Additionally, by way of further example and not limitation, fluid destination(s) 208 may comprise any location, container, or configuration where an amount of one or more fluids is required or desired to be, including one or more wellbores; one or more machines, pieces of equipment, apparatuses, devices, and/or system components; one or more tanks; one or more vessels; one or more reservoirs; one or more trucks; one or more trailers, one or more ponds; one or more rivers; one or more lakes; one or more oceans; and the like.
In aspects wherein fluid delivery system 200 may comprise one or more pumping mechanisms 206, such pumping mechanisms 206 may comprise any appropriate form as may be apparent to those skilled in the relevant art(s) after reading the description herein, such as pressure pumps (including frac pumps), transfer pumps, and the like. Fluid delivery system 200 may also comprise one or more suction valves, distribution valves, inlet valves, outlet valves, and/or similar fluid flow control mechanisms or structures as may be apparent to those skilled in the relevant art(s) after reading the description herein as needed.
Fluid delivery system 200 may further comprise at least one sensing device 210 (shown as sensing devices 210a-c in
Sensing device(s) 210 that may be associated with fluid delivery system 106 (including the configuration represented by fluid delivery system 200) may be configured at various locations anywhere within and/or upon fluid delivery system 106 from (and including) fluid source(s) 202 to (and including) fluid destination(s) 208 in order to, by way of example and not limitation, measure, sense, and/or detect one or more changes in the density, flow rate, pressure, velocity, temperature, viscosity, composition, and/or volume of the fluid(s) passing through one or more portions or components of fluid delivery system 106 and/or one or more changes regarding the operating condition(s) of one or more components of fluid delivery system 200 (e.g., a change in pressure, temperature, function speed, etc. being experienced by the component(s)). Such changes may be indicative of one or more problems or issues being experienced by fluid delivery system 106 that may need to be addressed or resolved. Some nonlimiting examples of problems or issues that fluid delivery system 106 or one or more components thereof may experience or encounter may include component failure, normal wear and tear, fallout, deadheading, cavitation, sand slugs, iron failure, and/or sanding off. Additionally, in various instances, one or more components or portions of fluid delivery system 106 may experience situations in which there is pressure but no fluid flow, fluid flow but no pressure, and/or one or more blockages. All of these situations may be detected via sensing device(s) 210 and may be addressed or resolved in any appropriate manner. By way of example and not limitation, sensing device(s) 210 may be configured upon/within manifold apparatus 302 (not shown in
Sensing device(s) 210 used within and/or upon various portions or components of fluid delivery system 106 may be affixed using any appropriate means, mechanisms, or devices as may be apparent to those skilled in the relevant art(s) after reading the description herein, including via welding, via adhesion, and via various fastening elements such as nails, nuts, bolts, screws, washers, clips, clamps, clasps, hooks, pins, brackets, and the like, as well as any combination thereof, By way of example and not limitation, sensing device(s) 210 associated with fluid delivery system 106 may be configured inline of piping 204 within the flow of the fluid(s) that may pass therethrough. This may be particularly true in aspects wherein sensing device(s) 210 may comprise one or more flow meters 502 configured to measure the linear, nonlinear, mass, volumetric, or similar flow rate of one or more fluids flowing through one or more portions and/or components of fluid delivery system 106. In such aspects, flow meter(s) 502 may be affixed within one or more sections of piping 204 via one or more flange adapters (such as those available from Victaulie of Easton, Pa.), one or more hammer unions, various clamping or coupling mechanisms, as well as any similar connective, fastening, and/or clamping mechanisms or devices as may be apparent to those skilled in the relevant art(s) after reading the description herein, as well as any combination thereof. In aspects wherein sensing device(s) 210 may comprise one or more pressure transducers 504, such pressure transducer(s) 504 may be affixed upon and/or within one or more portions or components of fluid delivery system 106 via one or more 0.2500 inch National Pipe Thread (NPT) fittings, one or more high-pressure Weco® unions (such as those available from TechnipFMC plc of London, United Kingdom), as well as any similar connective, fastening, and/or clamping mechanisms or devices as may be apparent to those skilled in the relevant art(s) after reading the description herein, as well as any combination thereof.
In aspects wherein sensing device(s) 210 may be included within and/or upon individual component(s) (e.g., by way of limitation, pumping mechanism 206 as represented by sensing device 210b in
In some aspects, it may be important to optimize the performance of each pumping mechanism 206 that may be utilized with a given fluid delivery system 106. Therefore, in some nonlimiting exemplary embodiments, it may be beneficial for fluid delivery system 106 to include at least one sensing device 210 in the form of an inline densimeter in at least one portion of the tubing and/or piping 204 leading to each pumping mechanism 206 in order to, for example and not limitation, detect problems or issues, such as head loss, that may be developing near the entrance to pumping mechanism(s) 206 and/or occurring therein. Additionally, sensing device(s) 210 in the form of one or more flow meters 502 may be positioned within at least one portion of tubing and/or piping 204 coming into and/or going out of each pumping mechanism 206 associated with fluid delivery system 106 and/or within each pumping mechanism 206, in order to detect, identify, prevent, and/or quickly resolve problems or issues that may be occurring therewith and/or therein, such as, by way of example and not limitation, cavitation. These configurations of sensing device(s) 210, along with others, may help increase the efficiency of each pumping mechanism 206 as well as increase the efficiency and/or effectiveness of fluid delivery system 106 as a whole and/or reduce, prevent, or minimize the undesired suspension of the operation of fluid delivery system 106, thereby saving time and money.
Referring now to
In some aspects, by way of example and not limitation, fluid delivery system 106 may take the form of exemplary fluid delivery system 300. Fluid delivery system 300 may comprise at least one fluid source 202 and/or additive source in the form of at least one blending apparatus 304, at least one pumping mechanism 206 (labeled only as pumping mechanism 206a in
In some nonlimiting exemplary embodiments, fluid delivery system 300 may be configured for use with one or more wellbores associated with one or more hydraulic fracturing processes. In such (or similar) embodiments, by way of example and not limitation, pumping mechanism(s) 206 may comprise one or more frac pumps (such as, for example and not limitation, one or more triplex or quintuplex pumps) or mud pumps configured to increase the pressure of a slurry being transported to the wellbore(s) via fluid delivery system 300. Additionally, in such exemplary embodiments, by way of further example and not limitation, blending apparatus 304 may comprise one or more components (such as, by way of example and not limitation, blending tub 306) configured to combine at least one portion of the fluid(s) (e.g., water, oil, methanol, slickwater, gasoline, one or more petroleum products, one or more chemicals, one or more gels, one or more crosslinkers, saltwater, brine, one or more acids, produced water, dirty water, LNG, pipeline quality natural gas, other natural gas, propane, biofuel, and/or the like) from fluid source(s) 202 with one or more additives (e.g., at least one chemical, compound, fluid, proppant, and/or the like) from at least one additive source such as, by way of example and not limitation, hopper 308, in order to form the slurry. Furthermore, in such exemplary embodiments, by way of yet further example and not limitation, fluid destination(s) 208 may comprise one or more wellheads 314 configured to receive an amount of pressurized slurry and deliver the slurry to an internal portion of at least one wellbore. Moreover, in such exemplary embodiments, by way of still further example and not limitation, data center(s) 312 may take the form of one or more data vans configured to house one or more computing devices 104, control stations 108, and/or other computational and/or electronic devices configured to provide at least one user 102 (not shown in
Referring now to
In some aspects, manifold apparatus 302 used with fluid delivery system 106 (such as, for example and not limitation, fluid delivery system 300) may comprise one or more sensing devices 210 configured to measure, sense, and/or detect one or more aspects of one or more fluids passing through manifold apparatus 302 and/or configured to measure, sense, and/or detect one or more aspects of manifold apparatus 302 itself. In some nonlimiting exemplary embodiments, manifold apparatus 302 may comprise a frac manifold or missile with a high-pressure side and a low-pressure side. By way of example and not limitation, in aspects wherein fluid delivery system 106 may be configured for use with one or more wellbores associated with one or more hydraulic fracturing processes, manifold apparatus 302 may comprise one or more sensing devices 210 in the form of one or more magnetic flow meters 402 and/or one or more one high-pressure valve indicators 408. Additionally, manifold apparatus 302 may comprise at least one air actuator 406 for at least one suction valve that may be adjusted manually by user(s) 102 (not shown in
Referring now to
By way of example and not limitation, in some aspects, manifold apparatus 302 may comprise one or more sensing devices 210 in the form of at least one flow meter 502 (shown as flow meters 502a-d in
In some aspects, each flow meter 502 may be configured within and/or upon manifold apparatus 302 so that it may be able to measure the linear, nonlinear, mass, or volumetric flow rate of one or more fluids flowing through one or more portions of manifold apparatus 302, such as, by way of example and not limitation, configured inline of one or more portions of manifold apparatus 302 within the flow of the fluid(s) that may pass therethrough. By monitoring the flow rate of the fluid(s), user(s) 102 (not shown in
In some aspects, each pressure transducer 504 may be configured within and/or upon manifold apparatus 302 in order to detect the pressure of the fluid(s) passing through manifold apparatus 302 at various locations. Knowing when the pressure of the fluid(s) reaches levels that are too low or too high may allow user(s) 102, computing device(s) 104, and/or control station(s) 108 (including control hub(s) 404) to identify problems or issues with one or more components of fluid delivery system 106 (such as, by way of example and not limitation, pumping mechanisms 206 (not shown in
In some aspects, flow meter(s) 502 may be configured along an outer perimeter of manifold apparatus 302 while pressure transducer(s) 504 may be configured at opposing distal ends of manifold apparatus 302. However, as will be appreciated by those skilled in the relevant art(s) after reading the description herein, many different locations may be suitable for flow meter(s) 502 and/or pressure transducer(s) 504.
Referring now to
Process 600, which may at least partially execute within system 100 (not shown in
At step 604, at least one sensing device 210 (not shown in
At step 606, at least one user 102 views sensing device(s) 210 in order to obtain information about one or more aspects of fluid delivery system 106, including but not limited to a flow rate, density, composition, temperature, viscosity, pressure, velocity, and/or volume of the fluid(s) passing through one or more portions of one or more components of fluid delivery system 106; at least one operating condition of one or more components of fluid delivery system 106 (e.g., a pressure, temperature, function speed, etc. being experienced by the component(s)); and/or any similar data or information as may be apparent to those skilled in the relevant art(s) after reading the description herein. By way of example and not limitation, such data or information may be presented upon one or more gauges, meters, display screens, monitors, or similar mechanisms or devices associated with sensing device(s) 210 (either directly or indirectly) as may be apparent to those skilled in the relevant art(s) after reading the description herein.
At step 608, the at least one user 102 determines whether any adjustments need to be made to fluid delivery system 106, including any components thereof. By way of example and not limitation, the determination may be made at least partially based on whether the at least one user 102 thinks that fluid delivery system 106 is operating less efficiently and/or effectively than it could be and/or whether the at least one user 102 thinks that continuing the operation of fluid delivery system 106 may cause damage to one or more components thereof. If the determination is in the affirmative, process 600 proceeds to step 610; if the determination is negative, process 600 proceeds to step 612.
At step 610, the at least one user 102 makes at least one adjustment to at least one aspect of fluid delivery system 106. By way of example and not limitation, the adjustment(s) may be made by user 102 manually adjusting one or more mechanisms or devices associated with fluid delivery system 106, including but not limited to one or more air actuators 406 (not shown in
At step 612 process 600 is terminated and process 600 ends.
Referring now to
Process 700, which may at least partially execute within system 100 (not shown in
At step 704, a user 102 (not shown in
At step 706, at least one sensing device 210 (not shown in
At step 708, computing device(s) 104 and/or control station 108 convert or interpret measured, sensed, and/or detected data from sensing device(s) 210 into information in a form that may be useful to user 102 by performing one or more calculations. By way of example and not limitation, sensing device(s) 210 in the form of one or more densimeters may provide measured/sensed/detected density information to determine a pressure for the fluid(s) within at least one portion of at least one component of fluid delivery system 106, while sensing device(s) 210 in the form of one or more flow meters 502 may provide measured/sensed/detected fluid flow data that may be used with component data to determine an operating efficiency for one or more components of fluid delivery system 106 such as, by way of example and not limitation, pumping mechanism(s) 206 (not shown in
At step 710, at least one user 102 is presented with information regarding at least one aspect of fluid delivery system 106. By way of example and not limitation, such information may be displayed via at least one graphical user interface associated with computing device(s) 104 and/or control station 108 communicatively coupled to sensing device(s) 210, or upon a screen or monitor associated with a given sensing device 210 (either directly or indirectly). Additionally or alternatively, the information may be presented upon one or more gauges, meters, display screens, monitors, or similar mechanisms or devices associated with sensing device(s) 210 (either directly or indirectly) as may be apparent to those skilled in the relevant art(s) after reading the description herein. The displayed information may comprise, by way of example and not limitation, a flow rate, density, composition, temperature, viscosity, pressure, velocity, and/or volume of the fluid(s) passing through one or more portions of one or more components of fluid delivery system 106; an operating efficiency of one or more components of fluid delivery system 106; an operating condition of one or more components of fluid delivery system 106 (e.g., a pressure, temperature, function speed, etc. being experienced by the component(s)); and/or any similar data or information as may be apparent to those skilled in the relevant art(s) after reading the description herein. By way of further example and not limitation, the data or information presented to user(s) 102 may also comprise location and/or component information. For instance, in some nonlimiting exemplary embodiments, the presented information may indicate to user(s) 102 where within fluid delivery system 106 a given flow rate measurement was taken or which component(s) of fluid delivery system 106 are experiencing a particular pressure level.
At step 712, the at least one user 102 determines whether any adjustments need to be made to fluid delivery system 106, including any components thereof. By way of example and not limitation, the determination may be made at least partially based on whether the at least one user 102 thinks that fluid delivery system 106 is operating less efficiently and/or effectively than it could be and/or whether the at least one user 102 thinks that continuing the operation of fluid delivery system 106 may cause damage to one or more components thereof. In some aspects, this determination may be at least partially made with the assistance of mathematical and/or computational analysis performed by one or more computing devices 104 and/or one or more control stations 108 and/or by one or more computing devices 104 and/or one or more control stations 108 comparing the detected/measured aspect(s) of fluid delivery system 106 to one or more predetermined standards or values (e.g., as a nonlimiting example, that may be stored in and retrieved from fluid delivery system database 128) (or a range or predetermined standards or values) and determining whether the detected/measured aspect(s) are outside of a tolerable deviation of the one or more predetermined standards or values (or a range thereof). If the determination is in the affirmative, process 700 proceeds to step 714; if the determination is negative, process 700 proceeds to step 718.
At step 714, user 102 initiates at least one adjustment to at least one aspect of fluid delivery system 106 via at least one input device (such as, for example and not limitation, a mouse, keyboard, touchscreen, joystick, microphone, camera, scanner, chip reader, card reader, magnetic stripe reader, near field communication technology, and the like) associated with computing device(s) 104 and/or control station(s) 108 and uses the input device(s) to identify the desired adjustment(s) via at least one graphical user interface presented via a monitor or display screen associated (either directly or indirectly) with computing device(s) 104 and/or control station(s) 108. By way of example and not limitation, the at least one adjustment to the at least one aspect of fluid delivery system 106 may comprise an adjustment to the flow rate, density, composition, pressure, temperature, viscosity, velocity, and/or volume of the fluid(s) within at least one portion of at least one component of fluid delivery system 106, thereby facilitating the resolution of one or more problems or issues being experienced by fluid delivery system 106 or any component(s) thereof and/or minimizing or avoiding damage thereto. Other types of adjustments may be made to other aspects of fluid delivery system 106 as may be apparent to those skilled in the relevant art(s) after reading the description herein, including adjusting one or more operating parameters of one or more components of fluid delivery system 106 (e.g., a speed of operation, a mode of function, etc.). In order to instigate any adjustment(s) to the aspect(s) of fluid delivery system 106 requested by user 102, computing device(s) 104 and/or control station(s) 108 may control the manipulation of one or more mechanisms or devices associated with fluid delivery system 106, including but not limited to one or more air actuators 406 (not shown in
At step 716, user 102 terminates the open session within system 100. All communication between computing device(s) 104 and/or control station(s) 108 and system 100 may be closed. In some aspects, user 102 may log out of system 100, though this may not be necessary.
In various aspects, steps 704 and 716 of process 700 may be omitted, as user 102 may not be required to log in or log out of system 100.
At step 718 process 700 is terminated and process 700 ends.
Referring now to
Process 800, which may at least partially execute within system 100 (not shown in
At step 804, system 100 detects at least one aspect of fluid delivery system 106 (not shown if
At step 806, computing device(s) 104 (not shown in
At step 808, system 100 presents information regarding at least one aspect of fluid delivery system 106 to at least one user 102 (not shown in
At step 810, system 100 receives at least one input from the at least one user 102 in order to initiate at least one adjustment to at least one aspect of fluid delivery system 106. By way of example and not limitation, the at least one input may be received via at least one input device (such as, for example and not limitation, a mouse, keyboard, touchscreen, joystick, microphone, camera, scanner, chip reader, card reader, magnetic stripe reader, near field communication technology, and the like) associated with computing device(s) 104 and/or control station(s) 108. By way of further example and not limitation, the at least one adjustment to the at least one aspect of fluid delivery system 106 may comprise an adjustment to the flow rate, density, composition, pressure, temperature, viscosity, velocity, and/or volume of the fluid(s) within at least one portion of one component of fluid delivery system 106, thereby resolving one or more problems or issues being experienced by fluid delivery system 106 or any component(s) thereof and/or minimizing or avoiding damage thereto. Other types of adjustments may be made to other aspects of fluid delivery system 106 as may be apparent to those skilled in the relevant art(s) after reading the description herein, including adjusting one or more operating parameters of one or more components of fluid delivery system 106 (e.g., a speed of operation, a mode of function, etc.). In order to instigate any adjustment(s) to the aspect(s) of fluid delivery system 106 requested by user 102, computing device(s) 104 and/or control station(s) 108 may control the manipulation of one or more mechanisms or devices associated with fluid delivery system 106, including but not limited to one or more air actuators 406 (not shown in
At step 812 process 800 is terminated and process 800 ends.
Referring now to
Process 900, which may at least partially execute within system 100 (not shown in
At step 904, system 100 detects at least one aspect of fluid delivery system 106 (not shown in
At step 906, computing device(s) 104 (not shown in
At step 908, system 100 presents information regarding at least one aspect of fluid delivery system 106 to at least one user 102 (not shown in
In some aspects, step 908 may be skipped.
At step 910, system 100 compares at least one aspect of fluid delivery system 106 to at least one predetermined standard or value via computing device(s) 104 and/or control station(s) 108. In some nonlimiting exemplary embodiments, the at least one predetermined standard or value may be stored in and retrieved from, by way of example and not limitation, fluid delivery system database 128. By way of example and not limitation, the at least one predetermined standard or value may comprise a preferred and/or optimal density, composition, temperature, viscosity, flow rate, pressure, velocity, and/or volume of at least one fluid passing through at least one portion of at least one component of fluid delivery system 106 and/or a preferred and/or optimal operating efficiency and/or operating condition(s) of one or more components of fluid delivery system 106 as determined by user(s) 102, computing device(s) 104, control station(s) 108, and/or a manufacturer of fluid delivery system 106 or one or more components thereof; or the at least one predetermined standard or value may comprise a range of preferred and/or optimal densities, compositions, temperatures, viscosities, flow rates, pressures, velocities, and/or volumes of at least one fluid passing through at least one portion of at least one component of fluid delivery system 106 and/or a range of preferred and/or optimal operating efficiencies and/or operating conditions of one or more components of fluid delivery system 106 as determined by user(s) 102, computing device(s) 104, control station(s) 108, and/or a manufacturer of fluid delivery system 106 or one or more components thereof.
In some aspects, the at least one predetermined standard or value may comprise aspect(s) of fluid delivery system 106 that must correspond to other aspect(s) thereof. By way of example and not limitation, in order for a given pumping mechanism 206 to function appropriately, it may require a fluid suction flow rate within a certain range of the discharge rate of fluid(s) from that pumping mechanism 206. If these rates are found to be outside of a predetermined acceptable range, then user 102, computing device(s) 104 and/or control station(s) 108 may alter and/or request one or more changes to the flow of fluid(s) from fluid source(s) 202.
At step 912, system 100 determines whether any changes or adjustments need to be made to any aspect(s) of fluid delivery system 106, including any component(s) thereof via, for example and not limitation, computing device(s) 104 and/or control station(s) 108. By way of example and not limitation, the determination may be made at least partially based on whether system 100 determines, via mathematical and/or computational analysis, that fluid delivery system 106 and/or one or more components thereof is operating less efficiently and/or effectively than it could be and/or that continuing the operation of fluid delivery system 106 may cause damage to one or more components thereof. Additionally, the determination may be at least partially based upon whether at least one aspect of fluid delivery system 106 is not within a tolerable deviation of the at least one predetermined standard or value referenced during the comparison performed at step 910 and therefore requires at least one change or adjustment. If the determination is in the affirmative, process 900 proceeds to step 914; if the determination is negative, process 900 proceeds to step 916.
At step 914, system 100 initiates at least one adjustment to at least one aspect of fluid delivery system 106 via computing device(s) 104 and/or control station(s) 108. By way of example and not limitation, the at least one adjustment to the at least one aspect of fluid delivery system 106 may comprise an adjustment to the flow rate, density, composition, pressure, temperature, viscosity, velocity, and/or volume of the fluid(s) within at least one portion of at least one component fluid delivery system 106, thereby facilitating the resolution of one or more problems or issues being experienced by fluid delivery system 106 or any component(s) thereof and/or minimizing or avoiding damage thereto. Other types of adjustments may be made to other aspects of fluid delivery system 106 as may be apparent to those skilled in the relevant art(s) after reading the description herein, including adjusting one or more operating parameters of one or more components of fluid delivery system 106 (e.g., a speed of operation, a mode of function, etc.). In order to instigate any adjustment(s) to the aspect(s) of fluid delivery system 106 that are determined to be necessary or desirable, computing device(s) 104 and/or control station(s) 108 may control the manipulation of one or more mechanisms or devices associated with fluid delivery system 106, including but not limited to one or more air actuators 406 (not shown in
At step 916 process 900 is terminated and process 900 ends.
Referring now to
Computing functionality 1000 may comprise volatile and non-volatile memory, such as RAM 1002 and ROM 1004, as well as one or more processing devices 1006 (e.g., one or more central processing units (CPUs), one or more graphical processing units (GPUs), and the like). Computing functionality 1000 also optionally comprises various media devices 1008, such as a hard disk module, an optical disk module, and so forth. Computing functionality 1000 may perform various operations identified when the processing device(s) 1006 execute(s) instructions that are maintained by memory (e.g., RAM 1002, ROM 1004, and the like).
More generally, instructions and other information may be stored on any computer readable medium 1010, including, but not limited to, static memory storage devices, magnetic storage devices, and optical storage devices. The term “computer readable medium” also encompasses plural storage devices. In all cases, computer readable medium 1010 represents some form of physical and tangible entity. By way of example and not limitation, computer readable medium 1010 may comprise “computer storage media” and “communications media.”
“Computer storage media” comprises volatile and non-volatile, removable and 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. Computer storage media may be, for example, and not limitation, RAM 1002, ROM 1004, EEPROM, Flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
“Communication media” typically comprise computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier wave or other transport mechanism. Communication media may also comprise any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media comprises wired media such as wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above are also included within the scope of computer readable medium.
Computing functionality 1000 may also comprise an input/output module 1012 for receiving various inputs (via input modules 1014), and for providing various outputs (via one or more output modules). One particular output module mechanism may be a presentation module 1016 and an associated GUI 1018. Computing functionality 1000 may also include one or more network interfaces 1020 for exchanging data with other devices via one or more communication conduits 1022. In some aspects, one or more communication buses 1024 communicatively couple the above-described components together.
Communication conduit(s) 1022 may be implemented in any manner (e.g., by a local area network, a wide area network (e.g., the Internet), and the like, or any combination thereof). Communication conduit(s) 1022 may include any combination of hardwired links, wireless links, routers, gateway functionality, name servers, and the like, governed by any protocol or combination of protocols.
Alternatively, or in addition, any of the functions described herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, illustrative types of hardware logic components that may be used include Field-programmable Gate Arrays (FPGAs), Application-specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
The terms “module” and “component” as used herein generally represent software, firmware, hardware, or any combination thereof. In the case of a software implementation, the module or component represents program code that performs specified tasks when executed on one or more processors. The program code may be stored in one or more computer readable memory devices, as described with reference to
In view of the above, a non-transitory processor readable storage medium is provided. The storage medium comprises an executable computer program product which further comprises a computer software code that, when executed on a processor, causes the processor to perform certain steps or processes. Such steps may include, but are not limited to, causing the processor to detect at least one aspect of at least one fluid delivery system 106, present at least one aspect of the at least one fluid delivery system 106 to at least one user 102, and receive at least one input from the at least one user 102, wherein the at least one input is configured to make at least one adjustment to at least one aspect of the at least one fluid delivery system 106. Such steps may also include, without limitation, causing the processor to present at least one aspect of at least one fluid delivery system 106 to at least one user 102; compare at least one aspect of the at least one fluid delivery system 106 to at least one predetermined standard or value; determine whether at least one aspect of the at least one fluid delivery system 106 is within a tolerable deviation of the at least one predetermined standard or value, and if the at least one aspect of the at least one fluid delivery system 106 is not within a tolerable deviation of the at least one predetermined standard or value, initiate at least one adjustment to the at least one aspect of the at least one fluid delivery system 106.
It is noted that the order of the steps of processes 600-900, including the starting points thereof, may be altered without departing from the scope of the present disclosure, as will be appreciated by those skilled in the relevant art(s) after reading the description herein.
While various aspects of the present disclosure have been described above, it should be understood that they have been presented by way of example and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the spirit and scope of the present disclosure. Thus, the present disclosure should not be limited by any of the above described exemplary aspects, but should be defined only in accordance with the following claims and their equivalents.
In addition, it should be understood that the figures in the attachments, which highlight the structure, methodology, functionality and advantages of the present disclosure, are presented for example purposes only. The present disclosure is sufficiently flexible and configurable, such that it may be implemented in ways other than that shown in the accompanying figures (e.g., utilization with different fluids; utilization of different system components; implementation within computing devices, environments, and methods other than those mentioned herein). As will be appreciated by those skilled in the relevant art(s) after reading the description herein, certain features from different aspects of the systems, methods, and computer program products of the present disclosure may be combined to form yet new aspects of the present disclosure.
Further, the purpose of the foregoing Abstract is to enable the U.S. Patent and Trademark Office and the public generally and especially the scientists, engineers and practitioners in the relevant art(s) who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of this technical disclosure. The Abstract is not intended to be limiting as to the scope of the present disclosure in any way.
