MétaCan
Menu
Retour à la cohorte
Enregistrement W2583844069 · doi:10.2118/1016-0073-jpt

Technology Focus: Sand Management and Sand Control

2016· article· en· W2583844069 sur OpenAlexaboutno aff
R. J. Wetzel

Notice bibliographique

RevueJournal of Petroleum Technology · 2016
Typearticle
Langueen
DomaineEngineering
ThématiqueOil and Gas Production Techniques
Établissements canadiensnon disponible
Organismes subventionnairesnon disponible
Mots-clésSuspectSoftware deploymentSet (abstract data type)Term (time)Risk analysis (engineering)Control (management)Quality (philosophy)Computer sciencesortOperations researchWork (physics)Focus (optics)Operations managementBusinessEngineeringPolitical scienceLawArtificial intelligence

Résumé

récupéré en direct d'OpenAlex

Technology Focus I suppose that many of us are taking a deep breath just now. Many of us could be revisiting how we have been completing wells and what we might be able to improve. These improvement areas often involve some sort of trade-off between well deliverability and well/completion costs (in terms of equipment and rig time to deploy these various alternatives). I suspect that we all have been involved with completions where these two areas are debated. In my experience, it seems that much of our discussion revolves around what the various participants “feel” is the best approach. Much of the decision eventually hinges on what we will do in the short term (deployment) rather than in the long term (deliverability). The reason is, in my opinion, that we are fairly sure about the near-term items (related to cost) but often very uncertain about the longer-term items (deliverability as a result of how well we deployed the lower completion). Why is it that many of our completion quality decisions are focused on cost and not deliverability? I can think of two primary reasons: (a) We lack the metrics to support our decisions and (b) we do not have consistent practices (e.g., laboratory and design work, deployment processes) across our wells to allow us to compare our results. I suspect that you can think of others. Both of these areas offer improvement opportunities. For those of us who have a robust set of metrics to evaluate our overall sand-control planning and deployment process, if the preparation work (e.g., core testing, compatibility testing, equipment selection) is not carried out in a consistent fashion, the variation in results as depicted in our metrics would not lead us to a specific course for improvement because the variation from well to well might simply be explained away by the differences in planning and execution. Given the preceding idea, could the development of consistent practices be a critical first step on our journey toward achieving improvements in completion quality? The list of those practices that we should carry out in a consistent manner is quite long. For sand-control applications, we could start with those activities that occur early in the design process. After reviewing the many high-quality technical papers written over the past year, I have found a few that I think offer a good place for you to start your journey toward consistency. The three summarized papers are all related to the selection of proppant and screens in your sand-control completions. I am not promoting any one of these papers over the others. However, I am suggesting that whatever your organization does in this area, your organization should do it consistently. You may find your organization’s new, preferred approach to proppant and screen selection in one or more of the presented articles. JPT Recommended additional reading at OnePetro: www.onepetro.org. SPE 178966 Sand-Retention Testing: Reservoir Sand or Simulated Sand—Does It Matter? by Tracey Ballard, Weatherford, et al. SPE 179036 Sand-Screen Design and Optimization for Horizontal Wells Using Reservoir Grain-Size-Distribution Mapping by Mahdi Mahmoudi, University of Alberta, et al.

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 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: Autre devis · Signal consensuel: aucune
GenreSignal candidat: Empirique · Signal consensuel: Empirique
Score de désaccord entre enseignants0,906
Score d'incertitude au seuil0,436

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,0010,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,003
Tête enseignante GPT0,192
Écart entre enseignants0,189 · 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

Classification

machine, non validée

Prédiction automatique; un appel candidat d’une seule tête enseignante, pas un consensus.

Les modèles n’ont appliqué aucune catégorie : rien dans la taxonomie ne correspondait à ce travail.
Devis d'étudeAutre devis
Domainenon disponible
GenreEmpirique

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

En bref

Citations2
Publié2016
Routes d'admission1
Résumé présentoui

Explorer davantage

Même revueJournal of Petroleum TechnologyMême sujetOil and Gas Production TechniquesTravaux en français237 207