An Improved Methodology to Obtain the Arps’ Decline Curve Exponent (b) for Tight/Stacked Gas Reservoirs
Bibliographic record
Abstract
Abstract Production performance forecasting and the estimated ultimate recovery (EUR) evaluation are two of several uncertainties in the study of tight gas reservoirs. Using the Arps’ decline curve analysis to extrapolate the estimated ultimate recovery (EUR), based on the future production forecasting, is still a widely employed engineering tool in the oil and gas industry today. Tight gas reservoirs usually have a long transient/transitional flow period due to its low permeability. Simply by using the best fit "b" value to estimate the best EUR could generate an error as much as 100% from the true EUR. There has been a number of technical papers published dealing with this issue. This paper will present a new improved methodology to determine a more accurate "b" value to be used in the Arps’ decline curve analysis for tight gas reservoirs. This new approach, using a newly developed relationship between Qcum, Qcum, t→∞, qt and t, is more rigorous and much easier to use in comparison with all other existing ones. This new improved methodology will not only make future production forecasting more accurate, but also estimate the original-gas-in-place (OGIP) controlled by the well much easier. In Western Canadian Deep Basin, there are many extremely "tight" gas reservoirs that consist of multiple stacked shorefaces. Permeability in each shoreface varies very significantly, generally with the upper shoreface having a better permeability and the middle and lower ones having a permeability as poor as 0.01 mD. By using a reservoir simulator, a number of simulation runs have been performed by the author to answer the following questions: Could Fetkovich's b-values recommendation (mostly b<= 0.4 ~ 0.5 for single gas layer, b>=0.5 for multi-layer without crossflow) still be applied to the tight gas reservoirs? In a multi-stacked shoreface reservoir, does the lower perm zone contribute to the overall production? Moreover, how and when will it influence the production profile? When using the Arps’ decline curve analysis, what are the reasonable b-values to be used for the tight/stacked gas reservoirs? Both synthetic production decline profiles generated from simulation runs and a field example are presented in this paper to illustrate this new proposed methodology and to answer the above three questions.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".