Environmental Management, Cost Management, and Asset Management for High-Volume Oil Field Waste Injection Projects
Bibliographic record
Abstract
Abstract Ongoing exploration and production activity, combined with increased regulatory requirements, are increasing the volume and costs associated with disposal of oil field wastes, including produced oily sands and tank bottoms, drilling mud and cuttings, crude contaminated surface soils, and naturally occurring radioactive materials (NORM). A cost-effective and environmentally sound disposal option is to re-inject waste material into the subsurface into non-productive and/or depleted zones under controlled fracture conditions. High volume injection projects often involve annual injection exceeding several hundred thousand barrels of waste for several years. The critical engineering management goals for such operations are to: Maintain waste containment in the target formation (environmental management); Sustain long-term injectivity with minimum equipment repairs and well workovers (cost management); and Maximize formation storage capacity and well life (asset management). More than five years experience operating, analyzing, and managing large volume waste injection projects in the US and Canada has enabled Terralog to develop specific design, monitoring, and operating strategies to achieve these goals. Target injection formations must be selected with appropriate overlying barrier and absorption zones. Offset well completions must be carefully examined. The injection well completion should be appropriately designed to take into account high formation stresses and potential movement. Continuous monitoring and analysis must be performed to evaluate varying formation properties, injectivity, stress conditions, and fracture orientation and height growth. Finally, through continuous monitoring and analysis of formation response, injection parameters and properties (such as solids concentration, density, flow rate, shut-in time, etc…) can be adjusted in order to maintain containment, reduce operating costs, and optimize long-term injectivity.
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.002 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.003 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 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".