MétaCan
Menu
Back to cohort
Record W1971321814 · doi:10.2118/0115-0078-jpt

Pelican Lake: First Successful Application of Polymer Flooding in a Heavy-Oil Reservoir

2015· article· en· W1971321814 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJournal of Petroleum Technology · 2015
Typearticle
Languageen
FieldEngineering
TopicEnhanced Oil Recovery Techniques
Canadian institutionsnot available
Fundersnot available
KeywordsPelicanOil in placePetroleum engineeringFlooding (psychology)Enhanced oil recoveryOil fieldEnvironmental scienceLight crude oilGeologyPetroleumFishery

Abstract

fetched live from OpenAlex

This article, written by Special Publications Editor Adam Wilson, contains highlights of paper SPE 165234, ’Pelican Lake Field: First Successful Application of Polymer Flooding in a Heavy-Oil Reservoir,’ by Eric Delamaide, SPE, IFP Technologies; and Alain Zaitoun, SPE, Gerard Renard, SPE, and Rene Tabary, SPE, IFP Energies Nouvelles, prepared for the 2013 SPE Enhanced Oil Recovery Conference, Kuala Lumpur, 2-4 July. The paper was peer reviewed and published in the August 2014 SPE Reservoir Evaluation & Engineering journal, p. 340. Initially, polymer flooding had not been considered as a viable enhanced-oil- recover (EOR) technology for Pelican Lake in northern Alberta, Canada, because of the high viscosity of the oil until it was considered in combination with horizontal wells. Polymer flooding generally has been applied in light- or medium-gravity oil, and, even today, standard industry screening criteria limit its use to viscosities up to 150 cp. Pelican Lake is the site of the first successful application of polymer flooding in much-higher-viscosity oil (1,000–2,500 cp). Introduction The Pelican Lake field, approximately 250 km north of Edmonton, Alberta, Canada (Fig. 1), was discovered in 1978 and started producing in 1980. With more than 6 billion bbl of oil originally in place (OOIP) and a primary recovery estimated at less than 7%, it presents a significant target for EOR. But it is also a challenging reservoir with high-viscosity oil in a thin formation. Early History The reservoir-depletion mechanism is solution-gas drive, but initial reservoir pressure was low and there is very little dissolved gas, so there is little energy in the reservoir. Because the oil is also viscous (from 600 to 80,000 cp), primary recovery is low, approximately 5 to 10% of OOIP. In addition, the reservoir is thin (an average thickness of 5 m). As a result, the first wells drilled in 1980–81 were not economic. Horizontal Drilling in Pelican Lake CS Resources drilled its first horizontal wells in the Winter pool in Saskatchewan and then turned to Pelican Lake in 1987. Horizontal drilling is well-adapted to Pelican Lake, provided that the well can be maintained in the pay zone. Because the reservoir is so thin, a horizontal well can increase the reservoir exposure tremendously. The production performances of the horizontal wells were markedly better than those of the vertical wells and seemed to correlate reasonably well with the length of the horizontal drain in the reservoir. In 1991, CS Resources drilled its first openhole lateral arm from a main horizontal drain. Then, in 1993, it went one step further and drilled two multilateral wells with a new tool, the lateral-tieback system. The use of multilaterals would greatly expand in the years to come. Screening of EOR Methods for Pelican Lake Despite the improvement in recovery and overall economics resulting from the use of horizontal and multilateral wells, it was clear that primary recovery would be limited to 5–10% of OOIP, and other options were considered to increase 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.

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.544
Threshold uncertainty score0.597

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.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.009
GPT teacher head0.239
Teacher spread0.230 · 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