Design Considerations for Mitigating the Impact of Contaminants in Rich MEG on Monoethylene Glycol Recovery Unit MRU Performance
Bibliographic record
Abstract
Abstract Supplying monoethylene glycol (MEG) to the wellhead is critical to gas production since interruption of MEG injection can lead to loss of well production due to the risk of hydrate plug formation in the subsea production infrastructure. Maintaining a high reliability of MEG supply is heavily dependent on good MEG Recovery Unit (MRU) performance. This paper is applicable to subsea gas-condensate wells using MEG for hydrate inhibition and outlines a holistic approach towards diminishing the impact of contaminants in Rich MEG on MRU operating performance. An overview of the impact of various contaminants on MRU operation and how to deal with them will be discussed. Conceptual design considerations and practical applications as per vendor experience will be presented, as well as, examples of the impact of Rich MEG contaminants on MRU operation. During the life of the gas reservoir, both short term events (e.g., completions fluid clean up, well start up, flow rate increases) and long term events (e.g., hydrocarbons entrainment, clay, silt, corrosion products, corrosion inhibitors, scale inhibitors, demulsifiers, formation water breakthrough) introduce contaminants into the Rich MEG that need to be considered in terms of impact on operational reliability of the MRU. If the effects of the contaminants result in reducing the reliability of the MRU to less than the desired design target, then they need to be removed or at least reduced in quantity to a level that permits the reliability target to be achieved. Key groups that need to be involved in conjunction with the Client to ensure successful MRU design are Flow Assurance (wellhead chemistry and pipeline flow), Testing/Simulation facility and/or Vendor facility (study work, bench tests, and/or separation equipment piloting), Hydrocarbons Process Engineering (topsides or onshore processing facilities/MEG Regenerator and MEG Reclaimer design), and the MRU package vendor. Effective communication and collaboration between all parties in the early phases of the project is essential for managing these contaminants and maximizing MRU availability.
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.001 |
| Meta-epidemiology (narrow) | 0.001 | 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.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 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".