MétaCan
Menu
Retour à la cohorte
Enregistrement W2095307226 · doi:10.1115/ipc2012-90231

Managing the Threat of SCC in Gas Transmission Pipelines

2012· article· en· W2095307226 sur OpenAlex

Pourquoi ce travail est dans la base

Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.

affAu moins un auteur déclare une institution canadienne dans l'instantané OpenAlex épinglé.

Notice bibliographique

Revuenon disponible
Typearticle
Langueen
DomaineEngineering
ThématiqueStructural Integrity and Reliability Analysis
Établissements canadiensTransCanada (Canada)
Organismes subventionnairesnon disponible
Mots-clésIntegrity managementPipeline transportHydrostatic testEngineeringWork (physics)Pipeline (software)Forensic engineeringRisk analysis (engineering)Petroleum engineeringOperations managementBusinessMechanical engineering

Résumé

récupéré en direct d'OpenAlex

A group of eight gas transmission pipeline operators, responsible collectively for operating over 160,000 miles of pipelines in North America, has participated in a Joint Industry Project (JIP) to examine the current status of Stress Corrosion Cracking (SCC) Threat Management. Many of these operators had previously participated in a JIP addressing the Integrity Management of SCC in High Consequence Areas. Completed in 2006, the JIP developed experience-based guidance for the conduct of hydrostatic testing and excavations, for the assessment of the severity of discovered defects, and for establishing the interval before the next assessment. The outcome was published in ASME STP-PT-011, and formed the basis for proposed revisions to ASME B31.8S. In this second phase of the work, the operational experiences and threat management experiences during the five years since 2006 have been reviewed. From an operational viewpoint, the situation has been very satisfactory; only three in-service failures (ruptures or leaks) due to SCC have been experienced during this period, a considerable reduction compared to the preceding years. However, there is still a legacy of SCC to be managed in older pipelines; for example, 80 near-critical cracks have been removed by hydrostatic testing, and around 100 cracks that would probably have failed a hydrostatic test have been discovered by crack detection ILI. From the threat management viewpoint, a consistent overall framework for addressing SCC is beginning to be established, within which the wide range of operational experience can be addressed using mitigation strategies that are appropriate, proportionate, and timely. Most operators, particularly those with a legacy of SCC in older pipelines, make use of hydrostatic testing. Several now make use of SCC Direct Assessment, following its acceptance as a formal process in around 2005, but mostly for addressing segments with low relative risk of SCC and/or no history of SCC. Many are exploring the application of crack detection ILI; among the JIP members around 45 runs totalling nearly 3000 miles have been completed using EMAT ILI vehicles, and more are scheduled. Almost all the JIP members are using two or more of these approaches in combination as part of their SCC Threat Management strategies. There are areas where the experiences of SCC Threat Management over the last five years point to opportunities for improvement. For SCC Direct Assessment, the use of feedback from excavations to refine the relative rankings for segment prioritisation and dig site selection will become an increasingly important aspect of process improvement. For crack detection ILI, the main issues are the accuracy and reliability of information determining the flaw size and shape for use in predictions of failure pressure and assessments of defect severity. As Threat Management moves from baseline assessment to regular re-assessment, issues that arise include determination of the re-assessment interval, particularly when using SCC Direct Assessment and crack detection ILI. There is also an issue about how best to actively monitor those segments where there is low relative risk and no experience of SCC.

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.

Prédiction distillée sur la base complète

Imitation des enseignants

Ni prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.

score de la tête « metaresearch » (Codex)0,000
score de la tête « metaresearch » (Gemma)0,000
Version: codex-gemma-dda1882f352aStatut de validation: machine_predicted_unvalidated
Catégories candidatesaucune
Catégories consensuellesaucune
DomaineSignal candidat: aucune · Signal consensuel: aucune
Devis d'étudeSignal candidat: Simulation ou modélisation · Signal consensuel: aucune
GenreSignal candidat: Empirique · Signal consensuel: Empirique
Score de désaccord entre enseignants0,608
Score d'incertitude au seuil0,313

Scores Codex et Gemma par catégorie

CatégorieCodexGemma
Métarecherche0,0000,000
Méta-épidémiologie (sens strict)0,0000,000
Méta-épidémiologie (sens large)0,0000,000
Bibliométrie0,0000,000
Études des sciences et des technologies0,0000,000
Communication savante0,0000,000
Science ouverte0,0000,000
Intégrité de la recherche0,0000,000
Charge utile insuffisante (le modèle a refusé de juger)0,0000,000

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.

Tête enseignante Opus0,013
Tête enseignante GPT0,231
Écart entre enseignants0,218 · la distance entre les deux têtes enseignantes sur ce seul travail
Statut de validationscore_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écoule