Predicting Brine Mixing Deep Within the Reservoir, and the Impact on Scale Control in Marginal and Deepwater Developments
Bibliographic record
Abstract
Abstract Sulphate scale deposition is a common problem in hydrocarbon reservoirs where injection seawater, rich in sulphate, mixes with formation brines, rich in barium, strontium and calcium. The deposition of these scales can cause significant production impairment if it occurs within zones near the production wellbores. To control scale deposition within the near wellbore region of a reservoir, scale squeeze treatments are commonly deployed. In cases where the scale severity is very high, removal of sulphate ions from the injection water is an alternative scale control strategy. Both these methods of mitigation have associated CAPEX (e.g. desulphation plant) and OPEX (e.g. scale squeeze treatments) costs. Typically, to assess the severity of the problem in new fields, thermodynamic calculations are performed to calculate the mass of scale that will form. Until present there has been little work carried out to identify the location of scale formation within the reservoir. In this paper, field data and flow simulations from three North Sea fields are presented to show that the formation of scale can in fact occur deep within the reservoir, and have negligible negative impact on oil production within the near wellbore region. Evidence is presented from these North Sea fields that shows the evolution of the brine chemistry as seawater breakthrough occurs and squeeze treatments were applied. The evidence from the produced brine chemistry is linked to flow calculations for these fields to show that in some systems scale is depositing deep within the reservoir, reducing the potential for damage in the near production wellbore region. The extent and impact of the deposition varies throughout the reservoir and can be quantified. The ability to model brine mixing and stripping of the scaling ions before the fluids reach the production wellbore has a very significant impact on the economic assessment of marginal fields and deepwater developments. In such fields, the technical challenge and cost (CAPEX/OPEX) of scale control might make development un-economic. This paper outlines the data requirements and methodology used to allow such an assessment to be made.
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 distilled prediction
Teacher imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 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.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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 teacher head, 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".