The Operational and Economical Impact of CT Spoolable Connectors During the Last Five Years in the Norwegian and Danish Sector of the North Sea: Case Histories
Bibliographic record
Abstract
Abstract Coiled Tubing (CT) equipment in the Norwegian sector of the North Sea has traditionally been heavy, due to CT reels using larger sizes of CT – a trend also observed in other areas. Due to the requirement of performing well interventions in longer wells and larger completion sizes, CT drums weighing 40-60 t have been utilised. Not many platform cranes are capable of lifting such heavy CT drums and during bad weather periods operations are often delayed, even when using significantly lighter CT drums. Using spoolable CT connectors allow for a long and heavy CT string to be lifted on board of a platform on two or more separate drums and joining them together again once onboard. More than 50% weight reduction has been achieved making operational schedules more predictable. In the geographical areas considered, spoolable CT connectors have outperformed traditional methods like boat spooling and butt-welding from a safety, operational and economical point of view. Due to the reduction in weight, larger CT sizes have become available on older platforms as well. New CT applications that were previously considered unfeasible, like selective, high-rate acid fracing through CT, have been performed, extending the capabilities of CT interventions beyond previous logistical and technical limits. Being able to select the correct size of CT, with less dependency on offshore crane limits and weather has a fundamental impact on the usage of CT in the offshore industry. Rather than discussing the spoolable CT connector itself, the primary intention of the paper is to re-view case histories that were performed during the last 5 years. Operational challenges that have been mastered, successes, failures and further developments are presented. A new CT reel configuration to simplify spoolable CT connector installation will be presented. The new applications made possible by this technology and their economic impact on the Norwegian CT market since year 2003 will be reviewed.
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.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.002 | 0.002 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 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 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".