Alaskan Beaufort Sea Pipeline Design, Installation and Operation
Notice bibliographique
Résumé
Abstract The BP Northstar, Pioneer Oooguruk and Eni Nikaitchuq pipeline projects provide a significant experience base for designing, installing and operating future offshore arctic pipelines. Each pipeline is located in the nearshore zone of the Beaufort Sea, offshore the North Slope of Alaska. Maximum pipe diameters range up to 18 inches, water depths to 37 ft and lengths to 6 miles. Unique offshore arctic environmental loading conditions influenced each pipeline design differently for defining the required pipe bundle configuration, thermal insulation and trenching requirements. Similar differences affected the winter construction procedures used for each project and would be expected to impact future pipeline projects in deeper waters. A total of 13 years of pipeline operational experience has been gained and key features such as routine seabed surveys, in-line-inspection pigging and effective leak detection systems are important to the continued safe operations of these pipeline systems. Introduction Development of offshore oil and gas reserves in Arctic and sub-Arctic regions of the world have progressed relatively slowly (INTECSEA, 2011). This slow pace results largely from the remote field locations, unique arctic environmental load conditions and the lack of existing hydrocarbon export facilities. Subsea pipeline systems are often needed to connect offshore fields with onshore pipeline networks, for intrafield flowlines or for export tanker loading lines. Safe and economical design, construction and operational procedures are needed to address the unique conditions encountered for offshore arctic pipelines. Three pipeline systems have been installed in the Beaufort Sea, offshore the North Slope of Alaska for BP's Northstar, Pioneer's Oooguruk and Eni's Nikaitchuq field development projects (Figure 1). The Northstar and Oooguruk projects have been operating for a combined total of over 13 years and the Nikaitchuq project is scheduled to start operations during 2011. Each of these offshore arctic pipeline systems transports oil and gas from gravel island structures to shore. This Beaufort Sea pipeline experience can be applied on future Arctic and sub-Arctic projects having first-year sea ice, multi-year ice or iceberg load conditions. Seasonal sea ice is found at varying latitudes in both marine and inland lake locations, not just north of the Arctic Circle (or surrounding Antarctica). Other potential applications of Beaufort Sea pipeline experience include projects having complex thermal interactions with the local environment and offshore arctic projects requiring conventional marine construction procedures during the short Arctic summer season. Additionally, pipeline operations, maintenance and potential repair procedures form an integral part of an economical, safe and reliable offshore arctic pipeline system. Beaufort Sea Environmental Conditions The nearshore Alaskan Beaufort Sea ice typically breaks up or melts in place starting in June. Summer open water conditions then prevail from late July through mid-October. The summer polar pack ice edge recedes varying distances offshore based on the site location, water depth and year to year variations or long-term climate trends. Even during the open water season, however, ice floes are often present and their movement is influenced by winds and currents. Along much of the Alaskan North Slope coast, low barrier islands prevent multi-year polar pack ice from entering the nearshore lagoon areas. Ice can affect offshore marine operations outside the barrier islands at any time during the summer.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,001 | 0,001 |
| Méta-épidémiologie (sens strict) | 0,001 | 0,001 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,002 | 0,002 |
| Études des sciences et des technologies | 0,002 | 0,001 |
| Communication savante | 0,001 | 0,001 |
| Science ouverte | 0,001 | 0,001 |
| Intégrité de la recherche | 0,001 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,007 | 0,002 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».