Improved Recovery Potential in Mature Heavy Oil Fields by Alkali-Surfactant Flooding
Bibliographic record
Abstract
Abstract Many reservoirs in Canada are too small or thin for energy-intensive thermal EOR operations. The reservoirs may also be disturbed during primary production, generating low-resistance flow-pathways between injectors and producers, thus injected fluids will follow these pathways and not contact additional oil. In these conditions, alkali-surfactant injection has considerable potential as a technique for additional non-thermal recovery of heavy oil. During unstable displacement of heavy oil by water, water breakthrough occurs early, and subsequent water injection will channel mostly through the water fingers and bypass significant volumes of continuous oil. It has been shown in other works that alkali and/or surfactant injection can lead to improved heavy oil recovery compared to waterflooding, but researchers have proposed different reasons for this response. This work summarizes the mechanisms that are responsible for improved heavy oil recovery and presents the results of 30 laboratory core floods investigating alkali-surfactant injection into sand-packs containing heavy oil (viscosity 11,500 mPa⋅s at 23°C). By injecting less than 1% of alkali-surfactant (AS) solution with water, a combination of oil-in-water (O/W) and water-in-oil (W/O) emulsions will form in the water channels, effectively blocking them off. Further injected solution will therefore contact fresh regions of the core. It is shown that this design of AS injection in heavy oil leads to improved sweep efficiency of the flood. This corresponds to lower apparent relative permeability values to the aqueous phase, and a discussion is provided regarding how AS floods can be controlled and optimized. In any heavy oil reservoir that is considered a viable candidate for waterflooding, AS flooding can also potentially be applied. The significance of this work is that it describes the mechanisms responsible for the improved oil recovery, which allows for optimized design of chemical flooding conditions. This study demonstrates how a small amount of chemical injected along with water can lead to dramatic improvements in the recovery from previously flooded heavy oil fields.
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.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 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.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".