MétaCan
Menu
Back to cohort
Record W2080454216 · doi:10.2118/08-09-12-cs

Design of the Steam and Solvent Injection Strategy in Expanding Solvent Steam-Assisted Gravity Drainage

2008· article· en· W2080454216 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
fundA Canadian funder is recorded on the work.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueJournal of Canadian Petroleum Technology · 2008
Typearticle
Languageen
FieldEngineering
TopicEnhanced Oil Recovery Techniques
Canadian institutionsUniversity of Calgary
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsSteam-assisted gravity drainagePetroleum engineeringSteam injectionSolventWaste managementProcess (computing)Environmental scienceOil sandsChemistryAsphaltEngineeringMaterials scienceOrganic chemistry

Abstract

fetched live from OpenAlex

Abstract Steam-Assisted Gravity Drainage (SAGD) is a commercial in situ recovery technology that is effective at recovering heavy oil and bitumen. However, generation of steam by combusting natural gas adversely impacts the economics of the process, especially when the natural gas price is high, as has been the case lately. It has been shown that solvent additives can improve oil production rates, or at least maintain similar oil production rates with reduced steam injection. This is the basis of the Expanding Solvent Steam-Assisted Gravity Drainage (ES-SAGD) process. The key idea is that steam plus solvent is better than steam alone to mobilize heavy oil in the reservoir. This implies that ES-SAGD can potentially use less water and require smaller water handling and treatment facilities than those in SAGD. One key capability of ES-SAGD is that the recovered solvent can be recycled and re-injected into the reservoir. However, if too much solvent is injected and too little is recovered, the process can be uneconomic because the solvent is often more valuable than the produced heavy oil. In this research, the solvent injection strategy is designed for a single wellpair ES-SAGD operation by optimizing the net energy injected to oil ratio in a detailed and realistic three-dimensional heavy oil reservoir. The process parameters for design include the operating pressure and relative amounts of steam and solvent in the injected stream. The results show that the operating pressure and injection strategy must be carefully controlled to ensure high energy efficiency and solvent recovery. Introduction At in situ native conditions, the viscosity of Athabasca bitumen is typically greater than one million centipoise; often ranging between two and six million centipoise. The key barrier to be overcome for producing bitumen from Athabasca reservoirs is to mobilize it in the reservoir, that is, lower its viscosity sufficiently so that it readily flows in the reservoir to a production wellbore. There are several means to do this: first, heat the bitumen to a sufficiently high temperature; second, dissolve solvent in the bitumen and dilute it; and third, induce a compositional change of the oil that leads to a mobile oil phase, e.g., asphaltene precipitation or in situ upgrading. The effect of temperature on the viscosity of Athabasca bitumen is plotted in Figure 1(1) and is taken advantage of in the Steam-Assisted Gravity Drainage (SAGD) process(2). SAGD is now considered a commercial technology to produce Athabasca and Cold Lake bitumen reservoirs of Alberta(2–6). Typically, the original temperature of Athabasca reservoirs ranges from 7 to 11 ºC. The correlation displayed in Figure 1 shows that the viscosity falls by four orders of magnitude after the bitumen is heated by 100 ºC. Figure 1 reveals that the viscosity of Athabasca bitumen drops to less than 10 cP after its temperature exceeds about 196 ºC. This paper will consider this as the target oil phase viscosity to enable sufficient production from SAGD. At steam saturation conditions, this corresponds to a steam pressure equal to about 1,472 kPa.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.203
Threshold uncertainty score0.984

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.015
GPT teacher head0.217
Teacher spread0.202 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it