Automated Process Control System for Steam-Injection Processes
Bibliographic record
Abstract
Two types of models have been used when it comes to scaling steam-based injection processes from the laboratory to the field: low pressure and high pressure models. The latter, which uses similar fluids and operating conditions as the field reservoirs, is more suited for the steam injection process.Conducting high pressure and high temperature model experiments is very difficult as many variables, such as steam quality, injection rate and pressure need to be controlled all at once and in real time.An advanced automated process control system has been commissioned to overcome this operating complexity in steam injection wells. Steam quality is calculated using a neural network. This network uses an intermediate temperature in the heater and its control signal to assess the steam quality leaving the heater. The production cooling system controls the temperature of the produced fluids at 60oC in order to achieve a significant difference in density between the process fluids, water and heavy oil. As the water and oil densities are known at the controlled temperature, the water cut is determined by measuring the combined density of the produced fluids with a coriolis flow meter.This study has shown that an automated process control system is capable of controlling and optimizing steam injection processes like the steam-assisted gravity drainage process.
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.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.007 | 0.002 |
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".