A Case History of Heavy Oil Separation in Northern Alberta: A Singular Challenge of Demulsifier Optimization and Application
Bibliographic record
Abstract
Abstract This case history tracks the continual improvement cycle for the fluid separation process of a heavy oil / oil sands production facility in Northern Alberta over a period of three years. The major challenge posed by the operator of this 13 - 16° API crude oil was to move away from injection of two separate demulsifier formulations to a single product. This was not an easy task due to the very different conditions that existed at the two injection locations. The first location was at a series of injection points upstream of the gathering stations, prior to separation, where temperatures could reach sub-zero conditions and the second was at the battery receiving facility where heating increased temperatures to 100°C. Water cut and shear were also very different and the operator required a very strict 0.2% BS&W on the crude exiting any of the four treater tanks; to further complicate issues crude oil viscosity ranged from 500 - 5000 cP. A unique bottle testing method was developed and used to simulate the field conditions as accurately as possible. Details are given on the chemistry of the individual components of the demulsifier determined to be so crucial to adequate performance and how this was optimized in the field after being identified from the bottle tests. Results show how careful consideration needed to be given to the concentration of the demulsifier bases in the blends and the curious observation that dilution of the final product made a big difference to the final performance in the field. Elaboration is given on potential mechanisms explaining the dilution effect and the paper goes on to conclude how careful design of field testing followed by field implementation can indeed solve complex separation issues and address individual well, battery and field requirements.
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.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.004 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.003 | 0.002 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
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".