Coupling a Thermal Reservoir Simulator with a Dynamic, Multiphase Wellbore Flow Simulator to Rigorously Model Complex SAGD Well Geometries and Completions
Bibliographic record
Abstract
Abstract In this paper, we propose a methodology to iteratively couple a wellbore simulator and a reservoir simulator in order to model the complex flow regimes that exist in a producing SAGD well while still taking into consideration the fluid movement and distribution within the reservoir. The process was successfully tested and implemented in two SAGD pads and the results were compared with those obtained using a commercial, fully-coupled reservoir-wellbore model. This method addresses the modeling limitations encountered in typical thermal reservoir simulators that use source/sink or discretized formulations to describe wellbore flow. SAGD producers exhibit overly complex flow regimes caused by the presence of a steam phase that can condense within the wellbore and promote significant variations in temperatures and pressures along the tubulars. Therefore, standalone wellbore simulators are necessary to predict performance as accurately as possible; however, using a wellbore simulator alone will neglect the effects caused by varying inflow conditions from the reservoir. With these variations occurring both in time and in space (along the wellbore), it is necessary to include the dynamic input of a reservoir simulator, hence the rationale for coupling both models. The algorithm devised to integrate the wellbore and reservoir simulators was coded into a standalone GUI-driven computer program called a coupler. The coupler was used to evaluate the performance of new SAGD pairs and new infill producers featuring flow devices and slanted trajectories. In this work, we will present the results of field case studies with the proposed coupling approach to evaluate the effect on ultimate recovery of drilling new SAGD pairs and SAGD infills using toe-up or toe-down trajectories as well as fitting these wells with inflow control devices. When applying the coupling workflow to the case studies, we determined that despite challenging conditions, it is possible to have inclined SAGD wells properly transition from preheating to production as well as allowing access to previously untapped parts of the reservoir resources, which increased ultimate recovery.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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 teacher head, 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".