Unique Cement Design to Mitigate Trapped Annular Pressure TAP Between Two Casing Strings in Steam Injection Wells
Bibliographic record
Abstract
Abstract Shell has experienced production casing deformation on several infill wells in an existing thermal development project in Canada. A full investigation identified trapped annular pressure (TAP) caused by unreacted water fraction in set cement between casing strings as a potential casing failure mode. A novel and innovative application of an existing technology (a cement blend incorporating hollow-glass microspheres) was developed, tested and implemented as an effective means to provide pressure relief in the cemented casing-casing annulus on steam injection wells. Thermal cement blends from two suppliers were used in the testing program. The test slurries were cured in a test cylinder until compressive strength development tapered off, and then heated in increments to 320°C while pressure was recorded. Typical thermal blends containing a range of concentrations of hollow-glass microspheres were tested in this manner to establish a slurry design that would prevent the pressure build up from surpassing the temperature de-rated collapse resistance of the casing. The tests using typical thermal cement blends with no glass bead additive resulted in rapid increase in pressure as the test cell was heated, and exceeded the temperature de-rated collapse value of the production casing string at temperatures much lower than typical steam injection temperatures. Tests performed on blends containing the glass spheres showed consistency and repeatability in results, and pressures were well below the de-rated collapse pressure of the production casing string at the maximum steam injection temperature. Based on preliminary results, this investigation has concluded that the cement blend containing 10% BWOC hollow-glass microspheres is a viable alternative to conventional thermal blends, capable of providing hydraulic isolation to meet regulatory requirements and industry best practices, with the added benefit of providing a mechanism to mitigate TAP on steam injection wells.
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.001 | 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".