A Pattern-Based Approach to Waterflood Performance Prediction Using Knowledge Management Tools and Classical Reservoir Engineering Forecasting Methods
Bibliographic record
Abstract
Abstract Estimating future performance of waterflooded reservoirs is a challenging reservoir engineering problem in complex reservoirs that are poorly defined. Flow simulation models characterized by limited spatial data of a key heterogeneity do not always represent the reservoir dynamics for water movement. In this paper, an efficient and rapid workflow is presented to estimate the recovery performance of an existing vertical-well, pattern-based waterflood recovery design using knowledge management and reservoir engineering in a collaborative manner. The knowledge management tool is used to gather production data and calculate pattern-based recoveries and injection volumes by defining pattern boundaries and allocating annual well injection/production volumes in a systematic manner. Classical reservoir engineering forecasting methods, namely, a combination of oil cut versus cumulative recovery performance curves, and decline curve analyses are applied to forecast the performance of the waterflood pattern of interest. The methodology is first applied to a synthetic reservoir model, and then to data from a real field developed by an inverted 9-spot recovery design. Extrapolating established trends of oil cut vs. recovery for each pattern for both the synthetic and real cases quantified future performance assessments. Time can also be attached to the performance by introducing liquid rate constraints. Forecasts based on real data highlighted the optimistic nature of the dated full-field simulation history match and provided a more realistic forecast for business planning. Forecasting using both constant and declining liquid rates differentiated the impact of deteriorating reservoir pressure and oil-cut trends on individual pattern oil rate forecasts thus defining current efficiency of each pattern. The methodology as a result turned into a simple yet powerful forecasting workflow that can be used by any asset team. This study is a very good example of how knowledge management tools can be used to increase the capabilities of classical forecasting methods in reservoir engineering.
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.001 | 0.001 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
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".