Blowout preventer testing system and method

[0001] This Patent Application is related to a pending U.S. patent application filed on Dec. 22, 2004 under Ser. No. 11/025,415 and published as 2005/0269079 on Dec. 8, 2005. The teachings therein are incorporated herein by reference. This patent application claims the priority of a USA Provisional Patent Application filed on Feb. 1, 2007 under Ser. No. 60/887,739 and entitled “Improved Blowout Preventer System.”

[0002] This invention relates to the general subject of production of oil and gas and, in particular, to methods and apparatuses for testing fluid systems.

[0003] Current subsea Blow Out Preventer (BOP) testing practice (in U.S. “Oil and Gas Drilling Operation,” Subpart D, 30 C.F.R. Chapter II, current Edition; and generally worldwide) is to view shut-in test pressures on circular chart recorders and wait until a 5-minute period of reasonably stable pressures is obtained (see FIG. 1). Reasonably stable pressures must be greater than or equal to the required test pressure and allow for temperature-related pressure declines. Tests are initiated well in excess of required pressures. A 5-minute period of reasonably stable pressures is required as proof of non-leaking tests since, absent additional analysis, the periods of overtly declining shut-in pressures could be indicative of leaks in the systems. The basic chart recorder used on a majority of drilling rigs today was patented over one hundred years ago (Wittmer, G. X.: “Recording Apparatus for Fluid Meters,” U.S. Pat. No. 716,973).

[0004] In the United States under current regulations, subsea BOP tests, recorded on 4-hour 15,000 psi circular charts, are typically ended when pressure decline rates are in the range −4 to −3 psi/min. This is because the pressure trace begins to appear steady once pressure decline rates diminish to the range −4 to −3 psi/min, making this the as-practiced limit of circular chart resolution. Given the subjective nature of visual chart interpretation, tests are sometimes stopped at pressure decline rates as high as −5 psi/min and as low as −2 psi/min. A decline rate of −3 psi/min is representative of a high standard of current testing practice. The pressure at which this occurs is defined as P_s or the “pressure at stabilization.”

[0005] Industry trends toward deeper water, synthetic oil-based fluids, and subsurface conditions requiring increasingly higher test pressures all contribute to lengthy delays while waiting for pressures to stabilize during subsea BOP testing. Also, subsea BOP stacks with redundancy of components and use of multiple-diameter drill strings leads to greater numbers of tests that must be conducted.

[0006] An investigation of the phenomenon of lengthy subsea BOP testing times (see Franklin, C. M., Vargo, R. F., Sathuvalli, U. B. and Payne, M. L.: “Advanced Analysis Identifies Greater Efficiency for Testing BOPs in Deep Water,” SPEDC [December 2005] 242-250) conclusively attributed the prolonged decay of pressure with time to heating of the test fluids during pressurization followed by cooling of the fluids during shut-in test periods. They proposed that real time digital analysis of the pressure decay could yield large time and cost savings with safety benefits gained through reduced exposure time of personnel to pressurized lines.

[0007] FIG. 2 depicts an example of the basic components involved in testing a subsea BOP stack 8. A drill string tool or test plug 9 is lowered into the interior or throughbore of the BOP and it seats at the lower end of the BOP to seal off the well components further down the wellbore. The system is a pressure vessel comprised of the test line 10 from the Cementing Unit (CU) 12 and the drillpipe 14 from the surface 13 of the rig 16 down to the BOP stack 8 at the mudline 20. In this work, the capacity of the BOP pressure vessel is referred to as the “test volume” (i.e. an isolated portion of the throughbore of the BOP). A choke line 24 and a kill line 26 connect the throughbore at the interior of the BOP to the CU 12. The valves (e.g., annular preventers, pipe rams, shear rams, etc.) 22 in the BOP stack are tested in sequence by closing each valve and then pumping fluid from the CU into the test volume until a “target pressure” is reached (i.e. the “pumping phase”). At the target pressure, pumping stops and the pressure in the test volume is monitored until the test is deemed valid (i.e. the “shut-in phase”). In deepwater wells, the duration of the shut-in phase can be as long as 60 minutes when Synthetic Based Muds (SBM's) are used. Pressure testing a BOP with SBM leads to lengthy testing times as a result of pressure/volume/temperature (PVT) influences associated with the fluid properties of SBM. These influences are especially pronounced in deepwater and high-pressure test environments.

[0008] In the example of FIG. 3, eight pipe ram tests averaged 53.5 minutes each, four annular preventer tests averaged 16.8 minutes each, and the total shut-in time was 8.25 hours. In the U.S., the ideal combined shut-in time would be one hour given the U.S. Minerals Management Service (MMS) requirement that each of the 12 tests must hold the required pressure for 5 minutes. In this example, an excess of 7.25 hours was expended waiting for pressures to stabilize.

[0009] Pressure declines of non-leaking tests may be attributed to cooling of the fluids in the pressurized system:

• • [0010] Surface-temperature fluids are pumped from the CU into the kill and/or choke line(s) to apply elevated pressure to the subsea BOP components being tested (i.e., these fluids are warmer than their surroundings).
  • [0011] Fluids in the kill and/or choke line(s) compress as additional fluids are pumped in (i.e., these fluids are displaced deeper to cooler surroundings).
  • [0012] Fluids in the kill and/or choke line(s) undergo an internal energy rise when they are compressed; this heat of compression causes a slight elevation of fluid temperatures throughout the system.
  • [0013] The pressurized fluids in the kill and/or choke line(s) cool as they lose heat to their surroundings.
  • [0014] Shut-in test pressures decline as the testing fluids cool; the rate of pressure decline is fastest initially when the temperature differences (ΔT) between fluids and surroundings are greatest, and slows as ΔT becomes less.

[0015] Subsea BOP tests tend to take longer with synthetic base muds (SBM) than with water base fluids (see FIG. 4) because:

• • [0016] SBM is more compressible than water, hence more SBM (and heat) is pumped-in to attain a given test pressure.
  • [0017] SBM has greater heat of compression (temperature rise) than water.
  • [0018] SBM has lower heat capacity than water so loses heat more slowly and takes longer to cool.

[0019] The problem of BOP testing has existed for some time. Considerable time and effort is expended each year to perform BOP tests. In spite of this, and with the exception of the earlier work by Franklin, et al., BOP testing schemes have not progressed in a long time. Actually, the problem has become aggravated with the passage of time because each year more and more testing is conducted at higher pressures using the current time consuming processes.

[0020] In accordance with one embodiment of the present invention, a method is provided for testing a blowout preventer (BOP) having a throughbore between its upper and lower ends, means for isolating a portion of the throughbore and means for providing a signal that is representative of the actual pressure within the isolated portion of the throughbore. The method uses a pressurization unit for applying pressurized fluid to the isolated portion of the throughbore of the BOP, and comprises the steps of: (a) using the signal that is representative of the actual pressure in the isolated portion of the throughbore over successive time points, using a predetermined regression model, having a plurality of constant but un-determined coefficients, to express the pressure in the isolated portion of the throughbore as a function of time, and to solve for the value of the coefficients; (b) using the evaluated coefficients and the regression model to forecast the time when the rate of pressure change in the isolated portion of the throughbore approximates a predetermined rate of pressure change; (c) using the evaluated coefficients, the regression model, and the time of step (b) to forecast the pressure in the isolated portion of the throughbore; (d) repeating the previous steps until successive forecasts of the pressure in the isolated portion of the throughbore stabilize relative to a predetermined convergence test; and (e) producing a visual indication when successive forecasts stabilize.

[0021] In one embodiment of the invention, a safety factor is applied by having step (e) further conditioned on Pt/Pf being less than or equal to a predetermined fraction that is derived from testing a representatively large sample of satisfactorily performing BOPs, where “Pt” is the pressure applied to the BOP when monitoring begins, and “Pf” is the current stabilized pressure from step (d).

[0022] In another embodiment a further degree of safety is introduced by the added steps of (f): using the evaluated coefficients and the regression model to predict/forecast the time when the pressure in the isolated portion of the throughbore will stabilize relative to a second pre-determined pressure decline rate that is less than the first pre-determined pressure decline rate, and to predict/forecast the pressure “Pz” at such time; and (g) producing a visual indication if (Pf−Pz) is not greater than the product of Pf and “ε” where “ε” is less than one.

[0023] In accordance with yet another aspect of the present invention, an apparatus is provided for testing a blowout preventer. In particular, the apparatus comprises a digital computer that receives a signal that is representative of current pressure within the isolated portion of the throughbore and that is programmed to: (1) regress the signal to

[0024] $A+\frac{b}{c+t^m}$
where A, b, c, and m are coefficients and “t” is time; (2) compute successive sets of coefficients {A_i+1, b_i+1, c_i+1, m_i+1} from successive signals representative of current pressure within the isolated portion of the throughbore over time; (3) predict the pressure in the isolated portion of the throughbore as a function of time; (4) successively compute the pressure decline rate, the time when a first pre-determined pressure decline rate is achieved, and the pressure in the isolated portion of the throughbore at such time; and (5) signal when successive predicted pressures becomes stable.

[0025] The digital BOP testing algorithm has been thoroughly evaluated through retrospective analysis of hundreds of digitally recorded subsea BOP tests conducted in the U.S. Gulf of Mexico. Digital BOP testing software has been run in real time at every opportunity via remote live acquisition of subsea BOP testing data.

[0026] Digital BOP testing software performed successfully in trials conducted onboard a deepwater drilling rig in the Gulf of Mexico. Digital analysis was employed concurrent to the chart recorder method of test interpretation which remained the deciding factor. Field trials accomplished the non-trivial challenge to acquire sufficiently high quality data flows and interface to existing signal processing infrastructure onboard floating drilling operations.

[0027] The U.S. Minerals Management Service (MMS) was notified of status and results throughout development and trials of digital BOP testing. A proposal was submitted to commence in 2007, a subset of subsea BOP tests to be interpreted using digital analysis in lieu of the chart recorder method. Approval is pending.

[0028] Some of the advantages of the invention include simplicity and speed. Recent advances in digital technology and the relative ease of data processing with inexpensive personal computer (PC) technology lead to a clear opportunity for improvement in the recording, analysis, and validation of BOP tests. Numerous other advantages and features of the present invention will become readily apparent from the following detailed description of the invention, the embodiments described therein, from the claims and from the accompanying drawings.

[0043] While this invention is a susceptible embodiment in many different forms, there is shown in the drawings, and will herein be described in detail, one specific embodiment of the invention. It should be understood, however, that the present disclosure is to be considered an exemplification of the principles of the invention and is not intended to limit the invention to any specific embodiment so described.

Digital BOP Testing Algorithm

[0044] To enable real time interpretation of subsea blowout preventer tests, a digital BOP testing algorithm was developed. Many specific approaches may be taken; preferably, the algorithm should obtain accurate pressure forecasts and have good predictive capability. The algorithm is used to fit observed or actual pressure data, and a pressure trend is extrapolated. Finally, a test criteria is applied to check for confidence in the pressure forecast.

[0045] Pump rate, volume pumped and pump pressure data are received in approximately 1-second intervals by the computer 50 shown in FIG. 2 after analog to digital conversion 52. These measurements may be made from CUs by cementing services providers. Those skilled in the art know that other pressure measurement sources exist. The end of pumping and beginning of shut-in test periods are detected.

[0046] One specific algorithm and process will be described. During shut-in periods, the coefficients of a function of the form:

[0047] $\begin{array}{cc}P\left(t\right)=A+\frac{b}{c+t^m}& \left(1\right)\end{array}$
are created in a regression of the current population of data {time, pressure} in such a way as to minimize the difference (in a least-squares sense) between the actual data and a computation of Eq. (1) at the same times as the actual data sets regressed to the entire time, and pressure data is set whenever fresh data are received. The values of A, b, c and m that provide the best fit of the function to the data are then computed.

[0048] Given that Eq. (1) expresses shut-in test pressure as a function of time, the pressure decline rate is the first derivative of Eq. (1):

[0049] $\begin{array}{cc}{P}^{\prime }\left(t\right)=\frac{-{\mathrm{bmt}}^{m-1}}{{\left(c+t^m\right)}^2}& \left(2\right)\end{array}$
and, for a particular value of the derivative, such as P′_T, (i.e., the pressure decline rate at time T), the time at which that value occurs is stated by Eq. (3):

[0050] $\begin{array}{cc}T={\left[\frac{-{P_T^{\prime }\left(c+T^m\right)}^2}{\mathrm{bm}}\right]}^{\frac{1}{m-1}}& \left(3\right)\end{array}$

[0051] Using the computed values of “b”, “c” and “m”, an iterative technique can be used to solve Eq. (3) for the time at which a certain value of P′_T occurs, and Eq. (1) can then be used to predict the associated pressure.

[0052] Within each computation cycle, the time at stabilization t_s (e.g., when P′(t_s)=−3 psi/min) is computed from Eq. (3), using the coefficients from the current best fit of Eq. (1). The pressure at stabilization P_s is computed from Eq. (1) using the computed values of “A”, “b”, “c”, “m” and t_s. This is compared with previous P_s forecasts and a test for convergence to a stable solution is applied. “Stable solution” here means the forecast or predicted pressure does not change appreciably as more data is added, whereupon the user/operator is confident that the solution correctly represents the pressure trend and can be used to interpret the current BOP test.

[0053] Various “tests for convergence to a ‘stable solution’” may be used. In one embodiment, the convergence test requires a minimum of 60 consecutive P_s predictions to be within 3 psi of one another. In one working situation, additional data was obtained about once every second of time. There are many possible tests with attendant trade-offs of solution time (i.e., elapsed shut-in time to obtain the first stable solution) and pressure forecasting accuracy. A range of tests was investigated, and the combination of sixty samples and 3 psi was found to be an appropriate criterion: the “(60, 3) criteria.”

[0054] When a stable solution is obtained, the predicted value of P_s is compared to the required test pressure P_req. In the simplest situation, if P_s is greater than or equal to P_req, the test is declared “successful” (positive) and, given confidence in the interpretation, the test can be ended in order to proceed to the next test. If P_s is less than P_req, the test is declared “unsuccessful” (negative) and, given confidence in the interpretation, the test can be “pumped up” or repeated. After stability is achieved, one or more additional tasks may be performed: a graphical display is created that depicts the modeled forecast pressure computations ahead of actual or measured pressure readings; a report is generated that logs testing times, forecast pressures, actual pressure, predicted final pressure, and required test pressure; etc. Other possibilities are readily suggested to those of ordinary skill in the art.

[0055] Digital BOP testing interpretations have been, and will for some time, continue to be compared with chart recorder results (see FIG. 1) where the chart method is presumed correct and the digital method may or may not concur. It may therefore be desirable to calibrate the digital method to the chart method to facilitate comparisons. The digital algorithm is therefore focused on predicting the pressure P_s at which a test performed by the chart method is likely to be ended and interpreted (e.g., the shut-in pressure at which the pressure decline rate is −3 psi/min.).

Digital Algorithm Performance Study

[0056] The P_s prediction accuracy of the digital BOP testing algorithm was quantified by applying it to a study group of 98 high pressure subsea BOP tests obtained from 17 fortnightly test suites, all conducted on the same floating drilling rig in the U.S. Gulf of Mexico. This group is significant in that all tests were held shut-in to pressure decline rates of −3 psi/min or less, thus enabling direct comparison of P_s predicted and P_s actual.

[0057] There is a positive relation between t_s (elapsed shut-in time at which the pressure decline rate is predicted to be −3 psi/min) and digital BOP testing algorithm solution times (see FIG. 5). The average solution time in the 98-test study group was 07:37 minutes with a maximum of 20:29 and a minimum of 01:14.

[0058] The potential time savings via digital BOP testing for a given test series are a linear function of the total shut-in time required to complete the series by chart recorder method. Digital BOP testing should consistently reduce the required shut-in time of the chart recorder method by approximately 68% (see FIG. 6).

[0059] FIG. 7 shows the cumulative distribution of P_s prediction errors in the study group. The error range is −0.53% to 0.81% with a mean of 0.11% and standard deviation of 0.24%. Hence, if a chart recorder test starts at 8,850 psi and the actual P_s value is 8,020 psi, it is reasonable to conclude that the digital BOP testing forecast will be within the range 8,010 psi to 8,048 psi with the most likely value being 8,029 psi.

[0060] FIG. 8 shows the data of FIG. 7 in histogram format with a “bell curve” superimposed. This indicates an approximately normal distribution of error values. The digital BOP testing algorithm produces an approximately normal distribution of P_s forecasting errors. Assuming the rules of normal distributions apply to these data, statistically significant conclusions can be drawn from an error analysis:

• • [0061] The mean P_s prediction error of a subset (the study group of 98 high-pressure sub-sea BOP tests held shut-in to pressure decline rates of −3 psi/min or less) of the total population (all subsea BOP tests of which the study group is representative) falls within the range 0.11%±0.05%, 95% of the time (or 19 times out of 20).
  • [0062] The error term falls within the range −0.62% to 0.75% 99.5% of the time with 95% confidence.
  • [0063] The upper bound error will be less than 0.69%, 199 times out of 200 (99.5% of the time).

[0064] The practical result of this error analysis is that:

• • [0065] The digital BOP testing algorithm is highly accurate, on par with or better than measurement accuracies of the electronic pressure transducers and mechanical chart recorders typically in use on CUs where subsea BOP tests are interpreted.
  • [0066] The condition for a test to be deemed “positive” (i.e., stated previously as P_{s predicted}≧P_req) can incorporate the 99.5% upper bound error, by implementing it in the digital BOP testing software as P_s(1−δ_{upper 95.5})≧P_req where δ_{upper 95.5}=0.0069. Those skilled in the art understand that the value 0.0069 can be adjusted to reflect additional knowledge of algorithms, performance and the desired safety factor(s).
    Digital BOP Testing Software

[0067] Digital BOP testing is most conveniently implemented by software loaded on a laptop computer 50 with the intent of supporting the current workflow of subsea BOP testing. Although the software is therefore designed to be seen and used at CUs 12 by CU operators, those skilled in the art realize that the software may be used by other personnel at the drilling rig, and by personnel remotely located from the rig.

[0068] FIGS. 9A and 9B depict the displays seen during initiation of high pressure subsea BOP tests. Digital BOP testing software displays a pressure vs. volume graph during pressurization (FIG. 9A), and then the initial shut-in pressure test data are displayed while being analyzed (FIG. 9B). In FIG. 9B, the yellow line is actually a series of successive discrete pressure measurements, which because of the scale of the time axis, appears as a continuous line,

[0069] A pump-in graph obtained during pressurization shows the linear relation of pressure vs. volume, computed in this example to be 1,792 psi/bbl. Once pumping ends, a graph of shut-in pressure vs. time is updated with each new pressure measurement taken by the PC. A distinctively colored light (here yellow for “noncommittal”) is displayed on the PC while digital BOP testing software analyzes the data and seeks a stable pressure forecast.

[0070] A pressure forecast, shown in purple, is displayed after the first stable solution is obtained (see FIGS. 10A and 10B) and the test is interpreted as either positive or negative. The test is positive in this example so a distinct colored light (here green for “safe” or “positive”) is displayed. The light would be red in the event of a negative test interpretation. The required test pressure is shown in red at the bottom of the graph. Pending regulatory approval of digital BOP testing, the intent is for a test to end after receipt of a conclusive interpretation. The test in this example was shut-in for 51 minutes additional time because it was interpreted by chart recorder method. This depicts how well the observed data overlay the pressure forecast. In addition, a graphical display (See FIG. 14 of published USA patent application 2005/0269079) may be presented to the user.

[0071] In particular, the familiar red, green, and yellow “traffic light” scheme was implemented to clearly identify the results of testing:

• • [0072] A “green” light was assigned to a test when:
    • [0073] 1. P_s predictions satisfy the (60,3) criterion, and
    • [0074] 2. P_s(1−δ)≧P_req where δ=0.0069, and
    • [0075] 3. (P_s−P_z)/P_s≦0.125.

[0076] The digital algorithm can obtain stable solutions during analysis of subsea BOP tests in less than 5 minutes of shut-in time. Preferably, digital BOP testing software should not display a green light until at least 5 minutes of shut-in time have elapsed. This is necessary to comply with the current MMS requirement of “must hold the required pressure for 5 minutes.”

• • [0077] A “red” light was assigned to a test when:
    • [0078] 1. P_s predictions satisfy the (60,3) criterion and
    • [0079] 2. P_s(1−δ)<P_req where δ=0.0069, or
    • [0080] 3. (P_s−P_z)/P_s≧0.125.
      If shut-in pressure P_s falls below P_req before a test is ended, a red light is lit.
  • [0081] The green light criteria was (P_s−P_z)/P_s≦0.125 where:
    • [0082] 1. P_s is the “stable” pressure associated with prediction of the time t_s when P′_T=−3 psi/min, and
    • [0083] 2. P_z is the pressure associated with prediction of the time t_z when P′_T=−1 psi/min.

[0084] The purpose of examining the pressure forecast at times t_s and t_z was to discern if the modeled pressure decline trend extrapolated to a relatively high pressure (indicative of no leak), or a relatively low (possibly zero) pressure which would be indicative of a leak. The conditional value of 0.125 was empirically determined from a study of 145 high pressure subsea BOP tests to discern the range of normal vs. anomalous values of the quantity (P_s−P_z)/P_s. The (P_s−P_z)/P_s≦0.125 criteria addresses improbable, but possible, instances of tests with very small leaks initiated at sufficiently high pressures to satisfy the P_s(1−δ)≧P_req requirement. This use of the digital BOP testing pressure forecast is meant to provide an appropriate safeguard, in addition to those already described, to assure digital BOP testing meets or exceeds the capability of the current chart recorder method to correctly interpret subsea BOP tests. Other safeguards may be employed for similar purposes. Once a reliable model of the pressure trend is obtained, numerous digital analyses may be performed to evaluate the information in greater detail.

[0085] FIGS. 10A and 10B show digital BOP testing software results. A pressure forecast is displayed and the test data are interpreted once a stable solution is obtained (FIG. 10A). A stable solution was obtained 15.9 min post shut-in, and P_{s predicted} was 9,629 psi occurring at clock time 23:19:38. The test continued to a pressure decline rate of −3 psi/min from which P_{s actual} was 9,661 psi occurring at 23:13:12. The −32 psi difference between P_{s predicted} and P_{s actual} is a forecasting error of −0.33%. Digital BOP testing software correctly interpreted the test as positive, but did so 51 minutes ahead of the chart recorder result. In FIG. 10B the test remained shut-in following the initial pressure forecast, and additional pressure data is displayed to show the accuracy of the forecast. The Eq. (1) values of the pressure forecast are: A=8,906.5; b=2.887E+5; c=2.246E+2; and m=0.623.

[0086] FIGS. 11A through 11D show a similar result from the subsea BOP test conducted subsequent to the example of FIGS. 10A and 10B. The test was held shut-in for 65 minutes to a pressure decline rate of −3 psi/min. Digital BOP testing software obtained a stable solution 17.2 minutes post shut-in, and P_s was predicted as 9,577 psi occurring at 00:48:22 hours. P_{s actual} was recorded as 9,608 psi occurring at 00:42:01. P_{s predicted} was 31 psi less than P_{s actual} representing a −0.32% forecasting error. Digital BOP testing correctly interpreted the test as “positive” but did so 48 minutes in advance of the chart recorder result. P_s was predicted with 99.7% accuracy 48 minutes ahead of the chart recorder result. The Eq. (1) values of the pressure forecast are: A=8,802.3; b=3.689E+5; c=2.804E+2; and m=0.635.

[0087] Table 1 displays results from a series of ten surface manifold tests held shut-in to pressure decline rates of −3 psi/min or less thus enabling quantification of P_s prediction accuracies and potential time savings obtainable through use of digital BOP testing software. The average solution time was 6.9 minutes with a mean error of −0.08%±0.04% yielding a potential 50% reduction of the total shut-in time required by the chart recorder method of interpreting surface manifold tests.

[0088]

TABLE 1
DWH_2006-05-11 SURFACE MANIFOLD TESTS
Ps (3, 60) Algorithm Forecast
			solution	time
Ps[psi]	error [psi]	error %	time	savings
7,702	−1	−0.01%	0:04:52	0:01:19
7,656	−6	−0.08%	0:07:11	0:04:56
7,631	−3	−0.04%	0:06:54	0:06:14
5,142	−6	−0.11%	0:05:32	0:08:09
5,157	−7	−0.13%	0:05:42	0:06:52
5,195	−5	−0.09%	0:05:26	0:08:41
5,179	−6	−0.12%	0:06:09	0:07:36
7,553	−6	−0.09%	0:15:13	0:14:24
6,542	−6	−0.10%	0:06:45	0:08:45
7,702	−2	−0.03%	0:04:56	0:02:13
avg	−5	−0.08%	0:06:52	0:06:55
max	−1	−0.01%	0:15:13	0:14:24
min	−7	−0.13%	0:04:52	0:01:19
std dev	2.10	0.04%	0:03:03	0:03:41
	total shut-in time		2:17:49
	total time savings		1:09:09

[0089] FIG. 12 describes the operation of digital BOP testing software. The software code was initially written in C++ version 6.0 with the Microsoft Foundation Class Library (MFC) and in Visual Basic 6.0. Subsequent releases were written in C#. There are several ancillary programs in other languages (e.g. Mat Lab). Two programs implement the algorithm: Anatomize and Clouseau. Both rely on external dll files that only become memory resident during execution. Software development was initially performed on a Gateway Power Spec desktop computer. A Dell desktop PC was used during field testing (using an Intel dual-processor running at 3.2 G Hz). The operating system was Microsoft Windows XP. Data was sent to the PC after analog to digital conversion via an Ethernet connection.

[0090] FIG. 14 illustrates a BOP test and a set of “labeled tags” utilized in the automation of FIG. 12. The tags are defined in Table 2.

[0091]

	TABLE 2
	Tag	Description
	To	Earliest time of test
	I1	Pumping start for test
	I2	Pumping stops for test
	I3	End of test
	Te	Latest time of test

[0092] These labeled tags assume a perfect test sequence like the one shown in FIG. 14. There will be instances where it may be impossible to identify some of the tags and there may be instances where the same tag occurs more than once. But the goal is to have a common language associated with a test sequence including metrics that can have values.

[0093] There can be any number of low or high-pressure event tag sets (i.e., sets of {I1, I2, I3}). Determination of the various tags is accomplished using a Non-Deterministic Finite-State Automaton (NFA) visualized in FIG. 13. NFA forms the basis of the event recognition approach. Although it may mature with time, this NFA has performed quite adequately for testing described herein. This NFA can also be used for real-time acquisition (such as occurs in Anatomize software).

[0094] Referring to FIG. 13, P_noise is a pressure that is assumed to be just at the noise level (e.g., 100 psi). Pressures below this value are presumed to be zero; all pressure reports below P_noise are assumed to represent an un-pressurized cavity. This is intended to accommodate inherent noise in acquired pressure data. “nLow” is a count of the number of samples that fall below the presumed noise level P_noise (i.e., the isolated portion of the throughbore of the BOP is assumed to be un-pressured). This accommodates noise in the pressure data where a few pressure reports might be unrealistically low.

[0095] In FIG. 13 there are four boxes: two cycle boxes 60 and 61 and two event boxes 62 and 63. In all four occurrences, there are exactly two lines of text:

[0096] “Make” is always on the first line, and either

[0097] “Cycle” (boxes 60 and 61), or “Event” (boxes 62 and 63) on the second line. In the diagram, “Make” implies the programmatic creation of an instance of the specified object. In C# (and other object-oriented languages), objects are blocks of memory that contain unique variable storage and references to actions (methods) that the object can perform. Thus, “Make Event” implies that a new Event object is created in memory and made accessible for data storage and actions (invocation of the objects methods). Objects can (and in this case do) persist for the life of the program.

[0098] Cycle and Event are concepts in the real world and objects in code. An Event is pictorially represented as of one of the “towers” appearing in FIG. 13; a numeric annotation indicating the Event number appears above the towers that have significant time duration. Events are an ordered set: {1, 2, 3 . . . }. Conceptually, an Event is when something is being pressure tested; regardless of the outcome of the test. Generally (but not always) an Event consists of a low-pressure test followed by a high-pressure test (See FIG. 14). The high-pressure test portion immediately follows the low-pressure portion with no return to zero pressure.

[0099] Programmatically, an Event is implemented as a class (and thus an object). An Event object is created when no Event is active and the pressure rises above threshold value. An Event terminates when the logic described in FIG. 13 reaches box 64 with “Te” inside. Each object Event contains the Event number, Test number, starting and ending index (i.e., To and Te) in the general data pool, the highest pressure reached during the Event, and a handle on the general data pool where To and Te apply. An Event includes an ordered collection of Cycle objects. Event objects: know how to save and harvest themselves to and from a storage file, can describe themselves in three formats, and can deliver the best known high-pressure, low-pressure and pumping cycle. Each of the three formats is an expression intended for List boxes. Two of the formats are for information-only purposes; that is, a self-description designed for human consumption. The third format is designed to allow the List in which they are presented to act as selection List; for example, Events could present themselves by name, start and end times with the expectation that a user will subsequently select them. This is similar to the list of recent files presented by commonly used Microsoft Word software under the File toolbar. An ordered collection of Events exists at the highest level of Anatomize.

[0100] Any number of Cycles can exist as “children” of an Event. A Cycle encompasses consecutive data reports within an Event that are pumping followed by not-pumping reports. In the simplest case, an Event could consist of a single Cycle where pressure was being built during pumping followed by reports where pumping had stopped and the decline portion of the test was conducted.

[0101] In most real-world cases, several Cycle objects are created as alternating pumping and decline operations occur. A simple two-step pressure test (depicted in FIG. 14) consists of an initial pumping phase to achieve a low-pressure test level followed by a non-pumping decline portion (Cycle 1). After an assurance that the low-pressure test was successful, another pumping phase is used to raise the pressure to the level of a high-pressure test followed by the high-pressure decline phase (Cycle 2). Real-world operations may see the creation of a dozen or more Cycles as the pump operator alternates between pumping and decline phases.

[0102] A Cycle is implemented as a class and contains a variety of data including the test pressure deemed appropriate to the Cycle (i.e., determined at run time), the highest pressure achieved during the Cycle, a variety of algorithm-specific parameters (e.g. dP/dt for First Stability), initial light parameters and vectors containing data analysis performed during the Cycle including formula parameters (i.e., A, b, c and m in Equation 1).

[0103] A Cycle object knows how to save and harvest itself to and from a storage file. It can deliver information about the analyses performed (e.g., the time when the first derivative of the analysis was equal to a particular value). A Cycle can describe itself in several formats. It can determine if its data is a bounded set (used here to mean if all data subsequent to First Light is bounded by a Validity Algorithm, for example). Cycle objects are also used in separate threads to create the data analysis, that is, the regression of a collection of contiguous data reports contained in the general data pool and a determination of the significance of the regression: the Yellow, Red and Green indicator lights.

[0104] In the drawing, boxes 70 through 78 denote the most significant program memory of a state change. For example, leaving State 2 Pumping always results in “I2” being set (which is recorded in a Cycle) and #low 78 being reset (set to zero) which is done outside of either an Event or a Cycle. A box 74 and 75 with “To” indicates that the new Event just created is tagged with the index into the general data pool where the Event begins. A box 64 with “Te” indicates that an Event ended and was tagged with the last index into the general data pool where the last applicable data report occurred for that Event.

[0105] In FIG. 13, the large circles 80, 81, 82, and 83 represent “States” (i.e., the situation the program finds itself in). For example, the first state 80 “1 Waiting for any Event” is where the program assumes no Event is current. and it is looking at each new data report with the expectation that an Event will start (or be noticed). The FSA diagram shows that this State can only be “exited” when pumping starts, and can be “entered” either initially (from “0 Start” if the pressure is low), or after an Event has been closed (i.e., box 64).

Processing Discussion: Practical Considerations

[0106] In theory there should be no need to perform data smoothing. It is only due to induced electronic noise (usually resulting from a lack of shielding) and low precision sensors that data smoothing becomes necessary. Under the right circumstances data smoothing will not be required. Others are working to create just such an environment in the real world.

[0107] Also, when the initial analog-to-digital conversion is made, there is a possibility that spurious electrical signals are introduced into the converter through radiation (e.g., sparking motors, transmitting radios, portable phones, etc.) and through hard connections (variations/noise in the power supply and inherent component noise).

[0108] In addition, noise may be introduced in the analog signal from the BOP and CU pressure sensors. Most pressure transducers 52 have a precision of only a few psi or perhaps tens of psi. Thus, under perfect conditions, the pressure transducer will have some characteristic noise (it is usually published in the transducer specifications). It is possible to get very precise transducers, but they are expensive. Historically there has not been a need for the kind of precision currently sought, and the field is replete with the less expensive transducers.

[0109] “Predictive wag” may result in a failure of the overall algorithm to report a prediction to the end user. Internally, the algorithm (with very few exceptions) makes a prediction with every new data point, but the predictions must be self-consistent before a prediction is reported to the end user. Part of the overall methodology is that the predictive wag is small before the automation is considered sufficiently steady to report a prediction to the end user. This criterion is based on the assumption that if each consecutive prediction is being made on a single population created from a representative data set, the predictions must all result in the same value.

[0110] For example, assume that, for given values of {A, b, c, m},

[0111] $P\left(t\right)=A+\frac{b}{c+t^m}$
is created for integer values of 3<t<N (where N is some very large number). A perfect regression of the generated dataset for any number of data points (say k, where k≧4) (i.e., {A_k, b_k, c_k, m_k}) should reproduce the original set of coefficients. If the thus created coefficient sets {A_k, b_k, c_k, m_k} vary, there is some inherent problem. Experiments performing regressions to artificial datasets have demonstrated the basic algorithmic approach: the same set of coefficients {A, b, c, m} are created for any number of data points (within numerical accuracy). A set of created coefficients {A_k, b_k, c_k, m_k} is essentially the same as a prediction. A prediction is just

[0112] $A+\frac{b}{c+T^m}$
where T is the time of the prediction. There are two major reasons the predictions would not be consistent (i.e., predictive wag is intolerably high):

• • [0113] 1. If the real-world population is not being developed from a physical process that can be described with the assumed form, then each addition to the population will result in a new predicted value. One interesting example of this is a linear decline with time P(t)=α+βt. This form closely resembles a leak in the system. That is, there will be predictive wag in the case of a leak, and the internally-generated predictions will not be steady; they are “wagging” (in this case, monotonically, but the effect is the same: a non-steady prediction).
  • [0114] 2. If there is a large amount of noise in the incoming data, particularly at early times, the internally-generated predictions will have a greater swing. The predictive wag will simply be a reflection of the noise in the data. This indication of noise could be sufficiently large for the overall algorithm to fail in providing a prediction to the end user; the noise would be large to mask the underlying data negating a legitimate prediction.

[0115] 1. Individual subsea BOP tests can require upwards of an hour for pressures to stabilize acceptably when interpreted by chart recorder method.

[0116] 2. In a 98-test study, digital analysis correctly interpreted all tests in an average solution time of 07:37 with a maximum of 20:29 and a minimum of 01:14 minutes.

[0117] 3. In the same 98-test study, the digital pressure prediction error range was −0.53% to 0.81% with a mean of 0.11% and standard deviation of 0.24%.

[0118] 4. Digital subsea BOP test interpretation can consistently reduce the required shut-in time of the as-practiced chart recorder method by approximately 68%.

[0119] 5. Digital BOP testing software will perform similarly well when applied to high pressure surface manifold tests.

[0120] From the foregoing description, it will be observed that numerous variations, alternatives and modifications will be apparent to those skilled in the art. Accordingly, this description is to be construed as illustrative only and is for the purpose of teaching those skilled in the art the manner of carrying out the invention. Various changes may be made in the shape and arrangement of components.

[0121] For example, during development, a number of alternative algorithm forms were tried with mixed results:
A+De^Bt
A+Be^nt+Ce^mt
A+(D/(B+Ct^m))
A+(D/(B+Ce^tm))
A+Be^nt+C exp (mt+lt²)
A+(De^nt/(B+Ct^m))
A+De^nt+G/(B+Ct^m)
where “e” or “exp” is approximately 2.71828183 and is the base of the natural logarithm, A, B, C, D, E, G, l, m and n are constants; and t is time.

[0122] Of all the forms tested,

[0123] $A+\frac{b}{c+t^m}$
seemed to be the best. It is a good form and has proven effective in all known cases. Desirable features of a predictive algorithm are a reasonably good fit to the data, and a generally accurate depiction of the pressure change over time due to heat transfer. Undesirable characteristics are an algorithm that over-predicts pressure, has negative pressure predictions, and/or has increasing pressure predictions. Preferably the algorithm is not more computationally complex than is necessary to achieve the desired accuracy.

[0124] While this methodology is most applicable for synthetic and oil-based mud systems, it is applicable for all fluid systems. Moreover, equivalent elements may be substituted for those illustrated and described. For example, a specialized hand held computer (e.g., pocket PC, PDA or smart cell phone) may be used instead of a general purpose PC or laptop. Also, certain features of the invention may be used independently of other features of the invention. For example, the concept of the invention may not be limited to submerged BOPs or deep water drilling; shelf and land-based BOPs testing might also be affected. Since digital high pressure surface manifold testing and surface manifold testing are often required along with subsea BOP testing, there is a safety benefit to reduced personnel exposure to pressurized lines, a work benefit to completing tasks more efficiently and, a reliability benefit to objectively interpreting each test. Those skilled in the art should also understand that while the BOP Illustrated herein is representative of the general situation, there are other configurations. Most commonly, the drill pipe forms part of the pressure vessel to the extent that pressure is applied from the Cementing Unit via the kill and/or choke lines to its exterior over an isolated length inside the BOP stack, but pressure inside the drill pipe remains strictly hydrostatic. A less common configuration (but one used on one drillship from which field data is cited herein) dispenses with the test plug and instead uses a “test ram” a/k/a “Subsea Stack Test Valve (SSTV)” (see Judge, Robert “Minimizing the Cost of Required BOP Testing A Case Study”, IADC European Well Control Conference, 4-5 Apr. 2006, Amsterdam). The test ram or SSTV is basically a lowermost pipe ram in the BOP stack with sealing elements inverted to hold pressure from above rather than below. The test ram forms the lower barrier of the test cavity in lieu of the test plug otherwise seated in the wellhead.

[0125] Thus, it will be appreciated that various modifications, alternatives, variations and changes may be made without departing from the spirit and scope of the invention as defined in the appended claims. It is, of course, intended to cover by the appended claims all such modifications involved within the scope of the claims.