Method of monitoring service operations of a service vehicle at a well site
Claim Score by NHIP
Abstract
A method monitors servicing operations of a vehicle capable for example of pumping various fluid treatments down into a well being serviced at a well site. The method records the vehicle's engine speed and the values of one or more service-related variables, such as pressure, temperature, flow rate, and pump strokes per minute. These variables are recorded as a function of the time of day in accordance with when they were sensed, and are associated with a well site identifier to form a data record. Global Positioning System data associated with the service vehicle assists in determining the well site identifier or can constitute the well site identifier. In some embodiments, the data record is communicated over a wireless communication link from a remote well site to a central office.

Term
Term ended
Projected expiry passed 9 September 2024, 2 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
22 claims: 2 independent, 20 dependent
- 1A method of monitoring service operations at a well site comprising:determining a well site identifier of the well site;sensing a variable associated with the service operation;storing on an electrical data storage device a first digital value representative of the well site identifier, and a second digital value representative of the variable associated with the fluid, thereby creating a stored data record;and communicating the stored data record to a remote location relative to the well site.
- 11Broadest claimClaim Score 76, broad(NHIP)A method using a service vehicle for monitoring service operations at a well site, wherein the well site is associated with a well site identifier, comprising:determining a first value indicative of the well site identifier;sensing at least one second value associated with the service operation;creating a data record at the vehicle comprising the first value and the at least one second value;and electronically communicating the data record from the vehicle to a location remote to the well site.
Independent claims2
47 paragraphs in 5 sections, as filed
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation-in-part of U.S. patent application Ser. No. 09/945,924, filed Sep. 5, 2001, which is incorporated herein by reference and to which priority is claimed under 35 U.S.C. § 120.
BACKGROUND OF THE INVENTION
[0002] 1. Field of the Invention
[0003] The invention generally pertains to service vehicles used in performing work at a well site, and more specifically to a method of monitoring the vehicle's service operations.
[0004] 2. Description of Related Art
[0005] After a well is set up and operating to draw petroleum, water, or other fluid up from within the ground, various services are periodically performed to maintain the well in good operating condition. Since wells are often miles apart from each other, such services are usually performed by an appropriately equipped service vehicles, including but not be limited to chemical tank trucks or trailers, cement trucks or trailers, hot-oiler tank trucks or trailers, and portable work-over service rigs having hoists to remove and install well components (e.g., sucker rods, tubing, etc.).
[0006] Service vehicles are often owned by independent contractors that well companies (e.g., the well owner or operator) pay to service the wells. Well owners typically have some type of contractual agreement or “master service agreement” with their various contractors. The agreement generally specifies what goods and services are to be provided by the contractor, the corresponding fees, and may even specify other related items such as operating procedures, safety issues, quantity, quality, etc.
[0007] Service operations are usually performed at well sites that are remote to the well owner's main office, perhaps hundreds of miles apart. It therefore can be difficult for a well owner to confirm whether a contractor is fully complying with his part of the agreement. Without a company representative at the well site to witness the services being performed, the well owner may have to rely on whatever report or invoice the contractor supplies. This can lead to misunderstandings, false billings, payment delays, suspicions, and disagreements between the contractor and the well owner. To further complicate matters, in a single day, service contractors may do work at different wells for different well owners. Thus, a contractor could mistakenly bill one well owner for work performed on a well of another owner.
SUMMARY OF THE INVENTION
[0008] A method monitors servicing operations of a vehicle capable for example of pumping various fluid treatments down into a well being serviced at a well site. The method records the vehicle's engine speed and the values of one or more service-related variables, such as pressure, temperature, flow rate, and pump strokes per minute. These variables are recorded as a function of the time of day in accordance with when they were sensed, and are associated with a well site identifier to form a data record. Global Positioning System data associated with the service vehicle assists in determining the well site identifier or can constitute the well site identifier. In some embodiments, the data record is communicated over a wireless communication link from a remote well site to a central office.
BRIEF DESCRIPTION OF THE DRAWINGS
[0009]FIG. 1 is a schematic diagram illustrating a method of monitoring a service vehicle's operations at a first well site according to some embodiments of the invention.
[0010]FIG. 2 is similar to FIG. 1, but showing the service vehicle as a pumping truck pumping fluid at a second well site.
[0011]FIG. 3 is a stored data record of digital values that reflect the pumping operations of a vehicle at multiple well sites.
[0012]FIG. 4 is similar to FIG. 1, but showing another embodiment of a vehicle's pumping operations at a third well site.
[0013]FIG. 5 is similar to FIG. 4, but showing the vehicle pumping fluid at a fourth well site.
[0014]FIG. 6 is a stored data record of digital values that reflect the pumping operations of a vehicle at the well sites of FIGS. 4 and 5.
[0015]FIG. 7 is a schematic diagram showing a vehicle pumping oil from a tank battery.
[0016]FIG. 8 is a schematic diagram showing the vehicle of FIG. 7 pumping hot oil down into a well at a well site.
[0017]FIG. 9 is a schematic diagram showing the vehicle of FIG. 7 circulating hot oil through a tank battery at another well site.
[0018]FIG. 10 is a stored data record of digital values that reflect the pumping operations illustrated in FIGS. 7, 8 and <b>9</b>.
DESCRIPTION OF THE PREFERRED EMBODIMENT
[0019]FIGS. 1 and 2 illustrate one embodiment of the present invention and disclose a service vehicle <b>10</b> for servicing a first well <b>12</b> at a first well site <b>14</b> and a second well <b>16</b> at a second well site <b>18</b>. The two well sites <b>14</b> and <b>18</b> may be quite remote from one another (e.g., miles apart) and may both be miles apart from a main office <b>20</b>. Wells <b>12</b> and <b>16</b> each include a string of tubing <b>22</b> disposed within a string of casing <b>24</b>. Under normal operation, petroleum, water, gas or other ground-source fluid passes through openings in casing <b>24</b> to enter an annulus <b>26</b> between the inner wall of casing <b>24</b> and the outer wall of tubing <b>22</b>. From annulus <b>26</b>, the fluid is then pumped or otherwise forced upward through the interior of tubing <b>22</b>, so the fluid can be extracted at ground level for later use or processing.
[0020] As shown in the present drawings, the service vehicle <b>10</b> is shown as a pump truck used for pumping fluids into the well, and may represent any fluid-pumping vehicle, examples of which include, but are not limited to, a tanker truck, a fluid pumping truck, a kill truck, a chemical truck, a treating truck, and a hot oil truck. However, it should be understood that while the operations of a pump truck are illustrated in detail in this application so as to clarify the nature of the present invention, service vehicle <b>10</b> can be any appropriately equipped service vehicle. Other examples include, but are not limited to, chemical tank trucks or trailers, cement trucks or trailers, hot-oiler tank trucks or trailers, or portable work-over service rigs having hoists to remove and install well components. All of these examples of service vehicles and similar vehicles are generically represented by service vehicle <b>10</b>. The operations of these various service vehicles are well known to those of skill in the art of well servicing operations.
[0021] In one embodiment in which a pump truck is used to facilitate certain operations of servicing a well, an end cap <b>28</b> may be temporarily installed at the upper end of tubing <b>22</b>. With tubing <b>22</b> capped and an annular seal <b>30</b> installed between tubing <b>22</b> and casing <b>24</b>, a servicing fluid can be forced through annulus <b>26</b> and/or tubing <b>22</b>. A pump <b>32</b> on vehicle <b>10</b> can force the servicing fluid into the well via an annulus valve <b>34</b> which communicates with annulus <b>26</b> or a tubing valve <b>36</b> which communicates with tubing <b>22</b>.
[0022] Vehicle <b>10</b> includes at least one tank for holding a fluid and at least one pump for pumping the fluid. Examples of the fluid being pumped include, but are not limited to, water (pure or with some additives), hot oil, fuel to power vehicle <b>10</b> (e.g., gasoline or diesel fuel), a scale inhibitor (e.g., DynoChem 1100 by DynoChem of Midland, Tex.), an emulsion breaker (e.g., DynoChem 5400 by DynoChem), a bactericide (e.g., DynoCide #4 by DynoChem), a paraffin dispersant (e.g., CynoChem 7498 by DynoChem), and an antifoaming agent (e.g., DynoChem 4690 by DynoChem). In some embodiments, vehicle <b>10</b> includes a first tank <b>38</b> for water <b>40</b>, a second tank <b>42</b> for a paraffin dispersant <b>44</b>, a third tank <b>46</b> for a scale inhibitor <b>48</b>, a fourth tank <b>50</b> for a bactericide <b>52</b>, and a fuel tank <b>54</b> for fuel <b>56</b> to power an engine <b>58</b> of vehicle <b>10</b>. Engine <b>58</b> is coupled to power drive wheels <b>60</b> of vehicle <b>10</b> and is further coupled to drive pump <b>32</b>, which is adapted to selectively pump fluids <b>40</b>, <b>44</b>, <b>48</b> and <b>52</b> into a well. Valves <b>39</b>, <b>43</b>, <b>47</b> and <b>51</b> allow pump <b>32</b> to selectively draw fluid from tanks <b>38</b>, <b>42</b>, <b>46</b> and <b>50</b> respectively. A fuel pump <b>61</b> pumps fuel <b>56</b> from tank <b>54</b> to engine <b>58</b>, which allows vehicle <b>10</b> to drive between well sites.
[0023] Vehicle <b>10</b> carries an electrical data storage device, such as a data collector <b>62</b> that receives input signals from various feedback devices for monitoring the operations of vehicle <b>10</b>. Data collector <b>62</b> is schematically illustrated to include any device for collecting, manipulating, converting, transferring and/or storing digital data. Examples of data collector <b>62</b> include, but are not limited to, a personal computer, a desktop computer, a laptop, notebook, a PLC (programmable logic controller), a data logger, etc. The vehicle <b>10</b> further includes various feedback devices for sensing variables associated with the fluid being pumped, including, but not limited to, pressure, temperature and flow rate. Such feedback devices for a pump truck include, but are not limited to, a pump discharge pressure sensor <b>64</b>, a pump discharge flow meter <b>66</b>, an annulus pressure sensor <b>68</b>, a tachometer <b>70</b> (i.e., a device that provides a signal useful in determining a relative speed of engine <b>58</b>), and a counter <b>72</b> to monitor the strokes per minute of a reciprocating pump, such as pump <b>32</b>. Of course, if a different service vehicle is used, the types of feedback devices can be different from the ones listed above. It should be noted that vehicle <b>10</b> could have more or less than the feedback devices mentioned above and still remain within the scope of the invention. For example, counter <b>72</b> and flow meter <b>66</b> both can provide data collector <b>62</b> with an indication of the flow rate of pump <b>32</b>, which may be all that is desirable to monitor. Also, additional feedback devices, such as limit switches, may be used to sense the open/closed position of valves <b>39</b>, <b>43</b>, <b>47</b> and <b>51</b> and provide data collector <b>62</b> with an indication of which fluid pump <b>32</b> is pumping.
[0024] In operation, vehicle <b>10</b> may travel from a contractor's home base to well <b>12</b> to pump water <b>40</b> from tank <b>38</b> down into tubing <b>22</b> and back up through annulus <b>26</b>. Such an operation is often referred to as “killing the well” and is used for preparing the well for further maintenance work and/or for checking the well for leaks or flow blockages. Later in the day, vehicle <b>10</b> may travel to well <b>16</b> to perform a similar killing operation. At the end of the day, vehicle <b>10</b> returns to the contractor's home base. With data collector <b>62</b> collecting data from feedback devices <b>64</b>, <b>66</b>, <b>68</b>, <b>70</b> and <b>72</b> and/or other devices, the vehicle's sequence of operations for the day is recorded as a stored data record <b>74</b>. The stored data record <b>74</b> comprises various digital values representative of the variable associated with the fluid being pumped, the time of day that the fluid is being pumped, the speed of engine <b>58</b>, and a well site identifier that indicates at which well vehicle <b>10</b> was operating.
[0025] The stored data record <b>74</b> can be displayed in various formats such as a tabulation of digital values and/or a corresponding graphical format, as shown in FIG. 3. The graphical format of data record <b>74</b> provides plots of certain key variables as a function of the time of day that the variables were sampled. In FIG. 3, for example, the plotted variables are pump strokes per minutes <b>76</b> as sensed by counter <b>72</b>, tubing pressure <b>78</b> as sensed by pressure sensor <b>64</b>, annulus pressure <b>80</b> as sensed by pressure sensor <b>68</b>, and RPM <b>82</b> (revolutions per minute) of engine <b>58</b> as measured by tachometer <b>70</b>. Variables <b>76</b>, <b>78</b>, <b>80</b> and <b>82</b> are plotted with reference to a common X-axis <b>84</b> representing the time of day. The displayed plots and values of FIG. 3 comprise one example of a stored data record <b>74</b> that is stored by data collector <b>62</b>. All the values of stored data record <b>74</b> are preferably digital for ease of manipulation and storage by data collector <b>62</b>. Although input from feedback devices <b>64</b>, <b>66</b>, <b>68</b>, <b>70</b> and <b>72</b> may originate as analog signals, a conventional A/D converter (in the form of a separate circuit or incorporated into data collector <b>62</b>) converts the signals to digital values readily handled and stored by data collector <b>62</b>.
[0026] It is important that the data record <b>74</b> be associated with a well site identifier. The well site identifier for a specific well may be the well's APIN (American Petroleum Institute Number), or some other textual identifier, such as, for example, “WELL SITE #1,” as shown in FIG. 3. The term “well identifier” as used herein represents any value or feature that can be referenced to distinguish one well from another. The well identifiers may be embodied in bar code labels (as commonly used on retail merchandise), magnetic or electromagnetic strips (similar to a common credit card or some building access security badges), integrated circuit chips (similar to an electromagnetic implant used for animal identification), or in memory such as a hard drive of a computer, a floppy disc, a CD (compact disk), a ZIP drive/cartridge, an electronic chip such as RAM, EPROM, or EEPROM and variations thereof, or magnetic tape. Regardless of the means used to embody the well identifiers, each well will have its well identifier present at the well site, and this well identifier can be input by various means (e.g., manually by keyboard, by scanning the bar code at the well, by uploading information transmitted from the integrated circuit, etc.) to the data collector <b>62</b> so that it can become a part of the data record <b>74</b>.
[0027] Finally, the well site identifier can constitute a global positioning signal (GPS) reading at the website. For instance, the vehicle <b>10</b> can be fitted with a GPS device <b>200</b> to determine the exact location of the vehicle <b>10</b>. Data from the GPS device <b>200</b> can then entered into data collector <b>62</b> so that the vehicle's position becomes part of the data record <b>74</b>. Such data can be taken only when the vehicle <b>10</b> is present at a well site being serviced, or can always be on, such that the location of the vehicle is always known even as it drives from site to site. The GPS device <b>200</b> can communicate with the data collector <b>62</b> by way of a direct connection or automatic uplink, or its data can be manually entered by the vehicle's operator. The term “GPS device” refers to any positioning system that includes a receiver whose general location or global coordinates are determined based on communication between the receiver (e.g., <b>200</b>) and one or more known references, such as satellites, antennas, transmitters, or other predetermined references (not shown). One specific example of a GPS device is a model S-Vee-8 by Trimble Navigation, Ltd. of Sunnyvale, Calif.
[0028] Because each well site occupies a unique position on the face of the earth, the GPS data leaves little doubt as to what well site the vehicle <b>10</b> is servicing. Moreover, the GPS data (plus or minus 50 meters to allow for some variance in the position of the vehicle <b>10</b> at the well site) can be pre-correlated to a well site identifier which is better understood by the well owner or servicing crew. For example, if it is known that XYZ, Inc.'s has three wells with owner well site identifiers “0130,” “0245,” and “3546,” and it is known that these three wells are respectively located at exactly 31° 48′ N/98° 57′ W, 30° 40′ N/96° 33′ W, and 27° 46′ N/97° 30′ W, a look up table in (or in communication with) data collector <b>62</b> can be used to covert the longitude/latitude data from the GPS device <b>200</b> to the owner well site identifiers, with these well site identifiers stored in the data record <b>74</b>. Alternatively, the raw longitude/latitude data from the GPS device <b>200</b> itself can be used as the well site identifier and stored in the data record <b>74</b>, or both the raw GPS data and the looked-up owner well site identifiers can be stored. In short, “well site identifier” can constitute both the raw GPS data and/or better-understood and more traditional well site identifiers.
[0029] For the example shown in FIG. 3, the vehicle's engine was started just before 8:30 am and left idling briefly, as indicated by numeral <b>86</b>. An elevated RPM reading <b>88</b> represents vehicle <b>10</b> traveling from the contractor's home base and arriving at first well <b>12</b> at about 9:10 am. Once at well <b>12</b>, a first well site identifier <b>90</b> that identifies the well by name, description, or location is entered into data collector <b>62</b> by way of a key board <b>92</b> or by some other data input method such as those described above. Numeral <b>94</b> indicates engine <b>58</b> is idle between 9:10 and 9:30 am, during which time workers are apparently setting up to kill well <b>12</b>. Setup may involve connecting a hose <b>96</b> from a pump discharge valve <b>98</b> on vehicle <b>10</b> to tubing valve <b>36</b> on well <b>12</b>. Annulus valve <b>34</b> may be partially opened to relieve fluid pressure building up due to pump <b>32</b> forcing water <b>40</b> into tubing <b>22</b>, which forces fluid upward through annulus <b>26</b>. Discharge <b>100</b> through valve <b>34</b> is preferable directed to a holding tank (not shown).
[0030] At 9:30 am, engine <b>58</b> begins driving pump <b>32</b>, as indicated by the engine RPM <b>82</b>, and eventually pump strokes/min <b>76</b>, tubing pressure <b>78</b>, and annulus pressure <b>80</b> all begin to increase. Numeral <b>102</b> indicates a generally constant flow rate between 10:00 am and 11:30 am. Arrows <b>104</b> of FIG. 1 indicate the general direction of fluid flow through tubing <b>22</b> and annulus <b>26</b> during the kill procedure. The pressure in tubing <b>22</b> peaks shortly after 10:00 am, and the pressure in annulus <b>26</b> peaks just before pump <b>32</b> is turned off at 11:30 am. The pressure of annulus <b>26</b> increases while the pressure in tubing <b>22</b> decreases, which is due to oil originally in tubing <b>22</b> being displaced by the heavier water <b>40</b> from tank <b>38</b>. When the pumping ceases at 11:30 am, tubing pressure <b>78</b> drops off almost immediately; however, annulus pressure <b>80</b> decreases more slowly, because the standing head of water in tubing <b>22</b> continues to apply pressure to fluid in annulus <b>26</b> which now contains a higher percentage of relatively light oil. From 11:30 am to 12:30 am, vehicle <b>10</b> is inactive, which can mean the crew working on well <b>12</b> is taking a lunch break or preparing to leave well site <b>14</b>.
[0031] At 12:30 am, the RPM of engine <b>58</b> increases with no sign of any pumping, which indicates that vehicle <b>10</b> is traveling to another well site. At 1:30 pm, a second well site identifier <b>106</b> is manually or automatically entered into the data collector <b>62</b> to indicate they have arrived at well site <b>18</b>. Equipment setup occurs between 1:30 pm and 2:00 pm, and pumping runs from 2:00 pm to 4:00 pm. Plots <b>76</b>, <b>78</b>, <b>80</b> and <b>82</b> show that the pumping process at well site <b>18</b> is similar to that at well site <b>14</b>. At well site <b>18</b>, however, the pump strokes/min <b>76</b> is higher, while the tubing pressure <b>78</b> and the annulus pressure <b>80</b> is lower than what was experienced at well site <b>14</b>. This could indicate that well <b>12</b> is deeper and/or provides more flow resistance than well <b>16</b>. As the service crew prepares to leave well site <b>18</b>, the plots indicate a period of equipment inactivity between 4:00 pm and 4:30 pm. At 4:30 pm, the engine RPM curve <b>82</b> indicates a short period of engine idling before vehicle <b>10</b> travels about 30 minutes back to the contractor's home base for an arrival time of about 5:00 pm.
[0032] By knowing the displacement of pump <b>32</b>, its strokes/min, and how long pump <b>32</b> was running at each well, the contractor can now determine the quantity of water that was pumped into wells <b>12</b> and <b>16</b> and can charge the well owners accordingly.
[0033] In some embodiments of the invention, data collector <b>62</b> includes communication equipment <b>108</b> (e.g., a modem, cell phone, etc.). Communication equipment <b>108</b> enables the stored data record <b>74</b> to be transmitted via the Internet (or other communication system) over a wireless communication link <b>110</b> (e.g., airwaves, satellite, etc.) to a computer <b>112</b> at a location remote relative to well sites <b>14</b> and <b>18</b>. Computer <b>112</b> may be at the main office of the well owner or at the contractor's home base, so the owner or contractor can monitor operations at the well site even though they may be miles from the site. The term “wireless communication link” refers to data being transmitted over a certain distance through a medium of air and/or space rather than through wires. Wireless communication link <b>110</b> is schematically illustrated to represent a wide variety of systems that are well known to those skilled in the art of wireless communication. For example, if the data collector <b>62</b> is associated with a computer with modem and an antenna <b>114</b>, a similar computer <b>112</b> having a similar modem and antenna <b>116</b> can receive data record <b>74</b>, which as noted can be transferred over the Internet with the assistance of a wireless communication link. Data record <b>74</b> can assume any of a variety of common formats including, but not limited to HTML, e-mail, and various other file formats that may depend on the particular software being used by the respective computers.
[0034] In another embodiment, illustrated in FIGS. <b>4</b>-<b>6</b>, a stored data record <b>74</b>′ comprises a first plot <b>118</b> of annulus pressure, as sensed by pressure sensor <b>68</b>; a second plot <b>120</b> of water flush, as measured in GPM by flow meter <b>66</b> when valve <b>39</b> is open; a third plot <b>122</b> for paraffin dispersant <b>44</b> (CHEM-A), as measured in GPM by flow meter <b>66</b> when valve <b>43</b> is open; a fourth plot <b>124</b> for scale inhibitor <b>48</b> (CHEM-B), as measured in GPM by flow meter <b>66</b> when valve <b>47</b> is open; a fifth plot <b>126</b> for bactericide <b>52</b> (CHEM-C), as measured in GPM by flow meter <b>66</b> when valve <b>51</b> is open; and a sixth plot <b>128</b> for engine RPM. Stored data record <b>74</b>′ indicates that vehicle <b>10</b> departs the contractor's home base at about 8:30 am and arrives at a well site <b>130</b> at about 8:45 am. Upon arrival, a well site identifier <b>132</b> identifying well <b>133</b> at a well site <b>130</b> is entered into data collector <b>62</b>. Equipment setup, which occurs just before 9:00 am, involves connecting hose <b>96</b> from discharge valve <b>98</b> to annulus valve <b>34</b>, as shown in FIG. 4. This allows water and the various chemicals to be selectively and sequentially pumped down into annulus <b>26</b>.
[0035] At 9:00 am, valves <b>43</b>, <b>98</b> and <b>34</b> are opened, valves <b>39</b>, <b>47</b> and <b>51</b> are closed, and the speed of engine <b>58</b> increases to drive pump <b>32</b> to pump CHEM-A from tank <b>42</b> down through annulus <b>26</b>. Pumping continues for about twenty minutes, allowing the total amount of CHEM-A to determined by multiplying the GPM reading of flow meter <b>66</b> by twenty.
[0036] At 9:20 am, valve <b>43</b> closes and valve <b>47</b> opens to pump CHEM-B from tank <b>46</b> down through annulus <b>26</b>, again for about twenty minutes. Similarly, at 9:40 am valve <b>47</b> closes and valve <b>51</b> opens to pump CHEM-C from tank <b>50</b> down through annulus <b>26</b>. A water flushing process is performed from 10:00 am to 11:00 am, wherein valve <b>39</b> is open and valves <b>43</b>, <b>47</b> and <b>51</b> are closed to pump water <b>40</b> from tank <b>38</b> into annulus <b>26</b>. The total amounts of water, CHEM-B, and CHEM-C can be determined in the same way as with CHEM-A. In an alternate embodiment, the total volume of water and chemical being pumped is measured directly, and the results are stored and displayed in gallons rather than gallons/minute.
[0037] At 11:00 am, the pumping stops and hose <b>96</b> is decoupled from annulus valve <b>34</b>. Stored data record <b>74</b>′ indicates that vehicle <b>10</b> is traveling from about 11:30 am to 12:00 am (i.e., from well <b>133</b> to well <b>136</b>), and equipment inactivity from 12:00 am to 1:00 pm indicates a lunch break and/or that equipment is being setup.
[0038] When work resumes, a well site identifier <b>134</b> identifying another well <b>136</b> at another well site <b>138</b> is entered into data collector <b>62</b>. At 1:00 pm, CHEM-B is pumped into well <b>136</b>, and at 1:40 pm, CHEM-C is pumped into well <b>136</b>, as shown in FIG. 5. The two chemicals were each pumped into well <b>136</b> for twice as long as when pumped into well <b>133</b>, and so well <b>136</b> received twice as much of these chemicals. However, plot <b>122</b> indicates that well <b>136</b> did not receive any of CHEM-A. Well <b>136</b> received a water flush from 2:30 pm till about 3:45 pm. It should be noted that the annulus pressure of well <b>136</b> is greater than that of well <b>133</b>, which may indicate that annulus <b>26</b> of well <b>133</b> is partially obstructed.
[0039] Stored data record <b>74</b>′ indicates that vehicle <b>10</b> departs well site <b>138</b> at about 4:30 pm and arrives back at the contractor's home base at 5:00 pm. As with the embodiment of FIGS. <b>1</b>-<b>3</b>, stored data record <b>74</b>′ can be transmitted via wireless communication link <b>110</b> from data collector <b>62</b> to remote computer <b>112</b>.
[0040] In another embodiment of the invention, shown in FIGS. <b>7</b>-<b>10</b>, a vehicle <b>10</b>′ provides a hot oil treatment for a well <b>140</b> at one well site <b>142</b> (FIGS. 7 and 8) and treats a tank battery <b>144</b> at another well site <b>146</b> (FIG. 9). Vehicle <b>10</b>′ comprises a tank <b>148</b> with a heater <b>150</b> for storing and heating oil <b>152</b>. Vehicle <b>10</b>′ also includes a piping system <b>154</b> through which oil is directed by valves <b>156</b>, <b>158</b>, <b>160</b>, <b>162</b> and <b>164</b>. FIG. 10 illustrates a stored data record <b>74</b>″ that captures the activities of vehicle <b>10</b>′ throughout a day. Data record <b>74</b>″ includes a first plot <b>166</b> of pump strokes/min of a pump <b>32</b>′; a second plot <b>168</b> of pump discharge pressure as sensed by pressure sensor <b>64</b>; a third plot <b>170</b> of oil temperature, as sensed by a temperature sensor <b>172</b>; and a fifth plot <b>174</b> of the speed of engine <b>58</b>, as sensed by tachometer <b>70</b>.
[0041] Referring to FIG. 10, vehicle <b>10</b>′ drives to well site <b>142</b> from 8:15 am to 9:00 am, and a well site identifier <b>176</b> is entered into data collector <b>62</b>. At 9:15 am, pump <b>32</b>′ draws oil <b>152</b> from a tank battery <b>178</b> (i.e., any vessel above or below ground for holding oil) through a hose connected to valve <b>162</b>. Valves <b>164</b>, <b>160</b> and <b>156</b> are closed, and valves <b>162</b> and <b>158</b> are open to direct oil in series through hose <b>80</b>, valve <b>162</b>, pump <b>32</b>′, valve <b>158</b> and into tank <b>148</b>.
[0042] From about 9:30 am to 10:00 am, heater <b>150</b> heats oil <b>152</b> to a certain temperature, as sensed by temperature sensor <b>172</b>. In addition, the setup of vehicle <b>10</b>′ is switched over, so hose <b>180</b> connects valve <b>160</b> to annulus valve <b>34</b>, as shown in FIG. 8. By 10:00 am, oil <b>152</b> reaches the proper temperature, and valves <b>156</b>, <b>160</b> and <b>34</b> are opened (valves <b>162</b>, <b>164</b> and <b>158</b> are closed) to allow pump <b>32</b>′ to force the heated oil <b>152</b> down through annulus <b>26</b>. This pumping process runs until 11:30 am. A blockage in annulus <b>26</b> caused the pump discharge pressure to be relatively high at first, as indicated by an initial hump <b>182</b> in plot <b>168</b>, but the pressure fell after the hot oil dissolved the obstruction.
[0043] From 11:30 am to 12:30 am, vehicle <b>10</b>′ is disconnected from well <b>140</b>, and the service crew breaks for lunch. At 12:30 am, vehicle <b>10</b>′ departs well site <b>142</b>, arrives at a well <b>188</b> at well site <b>146</b> at 1:30 pm, and an appropriate well site identifier <b>186</b> is entered into data collector <b>62</b>.
[0044] To provide tank battery <b>144</b> with a hot oil treatment, vehicle <b>10</b>′ is setup at well site <b>146</b>, as shown in FIG. 9. Here, a suction hose <b>190</b> runs between valve <b>162</b> and oil <b>152</b>′ in tank battery <b>144</b>, and a return hose <b>192</b> extends between valve <b>164</b> and tank battery <b>144</b>. Valves <b>160</b> and <b>56</b> are closed, and valves <b>162</b>, <b>164</b> and <b>158</b> are opened to circulate oil in series through suction hose <b>190</b>, valve <b>162</b>, pump <b>32</b>′, valve <b>158</b>, tank <b>148</b>, valve <b>164</b>, and return hose <b>192</b>. As oil <b>152</b>′ passes through tank <b>148</b>, heater <b>150</b> heats oil <b>152</b>′ to a predetermined temperature. This hot oil circulation process runs from 2:00 pm to about 3:50 pm. It should be noted that plot <b>168</b> shows that the pump discharge pressure is significantly lower at 3:00 pm than at 10:30 am, which allows one to conclude that a well was being treated at well site <b>142</b> and that a tank battery was being treated at well site <b>146</b>.
[0045] Stored data record <b>74</b>″ indicates that vehicle <b>10</b>′ departs well site <b>146</b> at about 4:30 pm and arrives back at the contractor's home base at 5:00 pm. Similar to certain other embodiments of the invention, stored data record <b>74</b>″ can be transmitted via wireless communication link <b>110</b> from data collector <b>62</b> to remote computer <b>112</b>.
[0046] While it is preferred to store the acquired data record at the data collector <b>62</b>, this is not strictly necessary. For example, data can come into the data collector <b>62</b> on a continuing basis, and can be transmitted to the remote computer <b>112</b> in almost real time, which allows owner or contractor to monitor the work as it is being accomplished. If this occurs, the data record can be permanently stored at the remote computer <b>112</b> instead of with the data collector <b>62</b>. In this regard, one skilled in the art will understand that the data record need not be completely taken, then stored, and then transmitted, and accordingly this disclosure's concept of a “stored” data record includes data records even only temporarily stored in the data collector <b>62</b> for immediate transmission to the remote computer <b>112</b>.
[0047] Although the invention is described with reference to a preferred embodiment, it should be appreciated by those skilled in the art that various modifications are well within the scope of the invention. For example, the stored data record for pumping fluid into a well or a tank battery could also apply to pump <b>60</b> pumping fuel <b>56</b> from tank <b>54</b> to engine <b>58</b>, whereby fuel consumption of a vehicle can be monitored. Also, since the vehicles are schematically illustrated, the actual configuration of the vehicles' pumps, tanks, valves, piping, etc. can vary widely and still remain well within the scope of the invention. Therefore, the scope of the invention is to be determined by reference to the claims that follow.
Contents5
11 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US11401797B1 | Cited by | United States of America | Applicant |
| US9657538B2 | Cited by | United States of America | Applicant |
| US11448014B1 | Cited by | United States of America | Applicant |
| US2011144809A1 | Cited by | United States of America | Pre-grant |
| US11674365B1 | Cited by | United States of America | Applicant |
| US7760085B2 | Cited by | United States of America | Search report |
| US10815752B2 | Cited by | United States of America | Applicant |
| US8718802B2 | Cited by | United States of America | Applicant |
| WO2016160459A3 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2006047379A1 | Cited by | United States of America | Pre-grant |
| WO2006065627A3 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US11339612B1 | Cited by | United States of America | Search report |
| US9611707B2 | Cited by | United States of America | Applicant |
| WO2006077378A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2008110255A1 | Cited by | United States of America | Pre-grant |
| US2011210142A1 | Cited by | United States of America | Pre-grant |
| WO2006065627A2 | Cited by | World Intellectual Property Organization (WIPO) | Search report |
| US11907029B2 | Cited by | United States of America | Applicant |
| US8045962B2 | Cited by | United States of America | Search report |
| US9324049B2 | Cited by | United States of America | Search report |
| US2013076907A1 | Cited by | United States of America | Pre-grant |
| US8114479B2 | Cited by | United States of America | Applicant |
| US11574372B2 | Cited by | United States of America | Applicant |
| US9605498B2 | Cited by | United States of America | Applicant |
| WO2023132836A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US10745993B2 | Cited by | United States of America | Applicant |
| US11659682B2 | Cited by | United States of America | Applicant |
| US8326538B2 | Cited by | United States of America | Search report |
| US2008177450A1 | Cited by | United States of America | Pre-grant |
| US2010250139A1 | Cited by | United States of America | Pre-grant |
| US2012203507A1 | Cited by | United States of America | Pre-grant |
| US10573159B2 | Cited by | United States of America | Applicant |
| US9253454B2 | Cited by | United States of America | Search report |
| US11448050B1 | Cited by | United States of America | Applicant |
| US11572260B1 | Cited by | United States of America | Search report |
| US8751290B2 | Cited by | United States of America | Applicant |
| US10740730B2 | Cited by | United States of America | Applicant |
| US8386059B2 | Cited by | United States of America | Search report |
| US4700142A | Cites | United States of America | Pre-grant |
| US4765435A | Cites | United States of America | Pre-grant |
| US4884847A | Cites | United States of America | Pre-grant |
| US5218301A | Cites | United States of America | Pre-grant |
| US5298894A | Cites | United States of America | Pre-grant |
| US5438329A | Cites | United States of America | Pre-grant |
| US5617084A | Cites | United States of America | Pre-grant |
| US6006212A | Cites | United States of America | Pre-grant |
| US6021093A | Cites | United States of America | Pre-grant |
| US6087965A | Cites | United States of America | Pre-grant |
| US6253849B1 | Cites | United States of America | Pre-grant |
| US6377189B1 | Cites | United States of America | Pre-grant |
| US6578634B2 | Cites | United States of America | Pre-grant |
| US6826492B2 | Cites | United States of America | Pre-grant |
6 members in 2 offices
Priority claims6
| Document | Office | Kind | Date |
|---|---|---|---|
| 94592401 | United States of America | A | |
| 94592401 | United States of America | A | |
| 44063303 | United States of America | A | |
| 09945924 | – | – | – |
| US20010945924 | – | – | – |
| US20030440633 | – | – | – |
Members6
| Document | Office | Kind | |
|---|---|---|---|
| CA2382630A1 | Canada | A1 | |
| US2003042020A1 | United States of America | A1 | |
| US6578634B2 | United States of America | B2 | |
| US2003196798A1 | United States of America | A1 | |
| CA2382630C | Canada | C | |
| US7064677B2 | United States of America | B2 |
39 transactions on the USPTO file
Allowed after 1 non-final rejection.
- Non-final rejections
- 1
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 12th Year, Large EntityM1553 | M1553 | |
| Post Issue Communication - Certificate of CorrectionN423 | N423 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Terminal Disclaimer FiledDIST | DIST | |
| Terminal Disclaimer FiledDIST | DIST | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Correspondence Address ChangeC.AD | C.AD | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Return from OIPEWROIPE | WROIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Application Return TO OIPEROIPE | ROIPE | |
| Application Return from OIPEWROIPE | WROIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Application Return TO OIPEROIPE | ROIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
22 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Certificate of correctionCC | CC | |
| Information on status: patent grantGrantedSTCF | STCF | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication, DOCDB
- 2003196798
- Publication, EPODOC
- US2003196798
- Application
- 10440633
- Application, DOCDB
- 44063303
- Application, EPODOC
- US20030440633
Titles
- English
- Method of monitoring service operations of a service vehicle at a well site
Patent term adjustment
- A delay
- +479 daysthe office missed an examination deadline
- Net adjustment
- 479 days
Classification
- CPC, 1
- E21B47/008
- IPC, 2
- B67D7 08
- E21B47 00
- USPC, 2
- 166250010
- 166066000