MétaCan
Menu
Back to cohort
Record W4249663406 · doi:10.4043/17894-ms

Flow-Assurance Modeling: Reality Check and Aspects of Transient Operations of Gas/Condensate Pipelines

2006· article· en· W4249663406 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueOffshore Technology Conference · 2006
Typearticle
Languageen
FieldEngineering
TopicOffshore Engineering and Technologies
Canadian institutionsnot available
Fundersnot available
KeywordsTransient (computer programming)Pipeline transportFlow assuranceTransient flowComputer scienceTransient analysisFlow (mathematics)Petroleum engineeringEngineeringEnvironmental scienceMarine engineeringSystems engineeringMechanical engineeringTransient responseElectrical engineeringMechanicsPhysicsOperating systemChemistry

Abstract

fetched live from OpenAlex

Abstract Statoil operates a number of gas condensate pipelines in the North Sea. This paper focuses on experience gained from operation and simulation, up to and including tail end, of the 150 km long 22' Huldra to Heimdal pipeline. During initial production at Huldra the liquid accumulation was higher than predicted by modeling. Additionally liquid surge waves not found in simulations were observed at the receiving facility. These findings were challenging due to very low liquid surge capacity in the receiving facility, and the minimum flow rate was increased. Investigations were carried out in order to explain the observations, and it was determined that condensate carry over in the Huldra scrubber significantly influenced the condensate content in pipeline. The pipeline has now entered the tail end production phase. Due to high liquid content at low production rates, water/MEG no longer reaches the receiving facility on a regular basis, causing local hydrate problems at Heimdal and a lack of MEG for re-injection. Simulations show that cyclic operation of the receiving facility will transport water/MEG out of the pipeline on a more regular basis. This change in operating philosophy may be implemented in 2006. Introduction The traditional gas condensate development had a processfacility close to the field, and the fluids would be exported through a single phase gas line and a single phase liquid line. This involved expensive process facilities at remote locations, often off-shore, and multiple pipelines. From the 1970's significant research efforts was put into multiphase transport. As the ability to design two phase (gas and hydrocarbon liquid) pipelines advanced it was sufficient to dehydrate the fluid close to the field, and the hydrocarbons were transported in a multiphase pipeline. This gave significant saving due to a simpler and smaller process facility and a single pipeline (MLNG [1] in Malaysia, BLNG in Brunei, Sable Island in Canada and Nam Con Son in Vietnam). The last step in the development has been the ability to design three phase pipelines (gas, hydrocarbon liquid and water), which was achieved in the early 1990's. This completely removes the need for the process facility, which are replaced by simple wellhead platforms (Huldra [2,3] and Troll [4] in Norway, South Pars in Iran, Ras Laffan and Qatar Gas in Qatar and Goldeneye in the UK) or complete sub-sea developments (Mensa [5] and Canyon Express [6,7] in the US, Scarab/Saffron [8] in Egypt, TOGI [9], Snøhvit and Ormen Lange [10] in Norway). Table 1 and Figure 1 summarizes the development of gas condensate pipelines by some of their key parameters, such as pipeline diameter, length, two phase versus three phase and development by wellhead platform versus subsea development. The present trend is that almost all pipelines are three phase, and most are subsea developments unless the water is shallow. handling relates to slug catcher size and plant liquid processing capacity.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.143
Threshold uncertainty score0.884

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.015
GPT teacher head0.213
Teacher spread0.199 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it