Successful Utilisation of Conventional Cement System to Mitigate Shallow Water Flow Risk in Deepwater Block M11, Myanmar
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.
Notice bibliographique
Résumé
Abstract In 2013, PTTEP drilled a deepwater well in the Gulf of Martaban, Myanmar. The water depth was 1003m with riserless drilling over 1000m below seabed. Being exploration well without any reliable offset well, shallow hazards risk was high. Shallow hazards analysis was performed, showing the high risk of shallow water flow. Shallow water flow causes many incidents, including surface casing cement failure. It can happen during cementing, cement phase transitioning, and after the cement has set. Cementing with the shallow water flow presence is, therefore, the critical operation to achieve the well integrity. Using special cement systems, foam or ultra-lightweight, is expensive, logistically challenging, and operationally complicated. After thorough risk analysis and mitigation, conventional class G cement system was selected. Information from 12-1/4″ pilot hole and actual 26″ hole were analysed for cementing plan. Shallow water flow occurred at 1819m in pilot hole. Pump and dump was started from 1760m in 26″ hole to prevent the flow. However, drilling to 2005m encountered another strong flow. So, the critical zone was identified from 2005m downward. For operational success, the critical zone was covered by gas tight tail slurry with API fluid loss control less than 50 mL/30 min, a SGSA transition timer shorter than 30 minutes and a short thickening time to prevent formation fluid migration. Lead slurry was designed for sufficient density and long thickening time to provide enough hydrostatic pressure, preventing fluid migration while tail slurry was setting. Not being ultra-lightweight cement, slurries were pumped with high excess and contain fibrous LCM to mitigate losses risk. Centralisation also contributed to the cementing success. During the cement job, good returns had been observed. No shallow water flow occurred during and after cementing. Operation was continued without subsidence issue. This paper summarises the process of assessing the risks and designing the economical cement operation to mitigate the risks, resulting in safe operation from shallow hazards.
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 enseignantsNi 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.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,001 | 0,000 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,001 | 0,000 |
| Bibliométrie | 0,001 | 0,000 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,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.
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écoule