Effect of reservoir and production system integration on field production strategy selection
Bibliographic record
Abstract
In petroleum engineering studies, the integration of reservoir and production system models can improve production forecasts. As the integration increases computation time, it is important to assess when this integration is necessary and how to choose a suitable coupling methodology. This work analyzes the influence of this integration, for a petroleum field in the development phase, evaluating the effects on the production strategy parameters. We tested a benchmark model based on an offshore field in Brazil so we could validate the solution in a reference known model. This work continues the research of Von Hohendorff Filho and Schiozer (2014, 2017) and aims to improve step 11 of the 12-step reservoir development and management methodology by Schiozer et al. (2015). The solution is tested in a reference model. Using the integrated production system and reservoir models from step 11 of the methodology, we re-optimize the production strategy of a standalone production development, while evaluating net present value as the objective function. We adapted an assisted workflow to include the optimization of new variables, such as pipe diameters of the well systems and gathering systems, platform positions, and artificial lift application, and compared these with the production strategy obtained from the same benchmark in a standalone approach. Comparing the integrated standalone and integrated production strategies, we observed important changes that indicate the need to integrate reservoir and production models. The optimized integrated systems resulted in significantly increased net present values, maintaining the same oil recovery factor while requiring lower initial investment. We implemented the best integrated production strategy and the integrated production strategy derived from the standalone case in the reference model which, in this case, represents a real field (emulating a real situation). Integration in the implementation step impacted the production forecast more than the optimization step, demonstrating the benefits of integrating reservoir and production systems to increase project robustness.
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.003 | 0.007 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".