MétaCan
Menu
Back to cohort
Record W1999576297 · doi:10.2118/08-02-22-cs

Improving the Performance of Classic SAGD with Offsetting Vertical Producers

2008· article· en· W1999576297 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueJournal of Canadian Petroleum Technology · 2008
Typearticle
Languageen
FieldEngineering
TopicReservoir Engineering and Simulation Methods
Canadian institutionsHusky Energy (Canada)
Fundersnot available
KeywordsInjectorPetroleum engineeringSteam injectionDirectional drillingDrillingOil fieldPerpendicularGeologyProcess (computing)Field (mathematics)EngineeringMechanical engineeringComputer scienceGeometryMathematics

Abstract

fetched live from OpenAlex

Abstract Both theoretical knowledge and field use of 'classic' SAGD (defined in this paper as two horizontal wells of the same length separated by a relatively short vertical distance, typically 5 to 7 m, with the injector on the top and the producer on the bottom) have greatly expanded over the last 15 years. During that period only a few modifications of classic SAGD have been proposed. The most successful was the use of vertical injectors at Sceptre (now CNRL) North Tangleflags and Strike (now Husky) Bolney. Laterally staggered injectors and producers and perpendicular injectors and producers have been proposed, but have not been successfully field tested. This paper discusses field observations and numerical simulation studies indicating that properly placed vertical production wells can capture a significant amount of oil that is not produced by classic SAGD development. These vertical wells could also first be used for steam injection high in the pay, CSS low in the pay or temperature observation purposes, adding further enhancement to the performance of nearby classic SAGD pairs. Horizontal wells could also be placed to access oil that is missed because it is below and beneath classic SAGD pairs, but practical aspects involving drilling, completing and producing horizontal wells in a non-uniformly heated and depleted environment suggest vertical wells are a better choice. Recent History of SAGD Usage Classic SAGD Classic SAGD is currently the most discussed and most proposed steam-based exploitation process in Canada. An excellent summary was published in 2001 by the inventor of the process, Dr. Roger Butler(1). Other recent publications have discussed a variety of topics about classic SAGD, including: reservoir screening criteria(2, 3), steam chest containment(4), co-injection of solvents(5, 6), optimum pressure regime(7), producer inflow problems(8), effect of solution gas(9) and late life strategies(10). Prior Proposed Spatial Alterations From Classic SAGD The literature also contains descriptions of processes for several well orientations altered from the classic SAGD configuration. The most advanced alteration is the use of vertical injectors and horizontal producers(11–15). The most successful field project to date using this configuration has been Sceptre's (now CNRL) North Tangle flags(16). Another spatial variation from classic SAGD is the addition of horizontal CSS wells(17). This configuration contains a horizontal CSS well at the same depth as the SAGD producers, and located in the middle of a typical SAGD pair-to-pair spacing, about 50 m away from each of the off setting pairs. Placement of the infill horizontal wells at the same depth as the SAGD producers likely leaves unswept oil below that depth, and possibly creates another opportunity for the addition of vertical producers. To date, only numerical simulation and physical modelling have been conducted, but those results suggest improved energy efficiency and productivity compared to classic SAGD. A third variation of well orientation is cross-SAGD or XSAGD(18). For XSAGD, the injectors are placed above the producers, but perpendicular to them.

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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.069
Threshold uncertainty score0.275

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
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.008
GPT teacher head0.195
Teacher spread0.187 · 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