MétaCan
Menu
Retour à la cohorte
Enregistrement W2060608711 · doi:10.2118/2002-138

Bridging the Data Divide;A software solution which eliminates the barriers to data accessibility providing data integration, analysis, and reporting not possible before.

2002· article· en· W2060608711 sur OpenAlexafffundabout
C.H. Faig, Harry Yau, Wharton Christensen, T. Elser

Notice bibliographique

RevueCanadian International Petroleum Conference · 2002
Typearticle
Langueen
DomaineComputer Science
ThématiqueDistributed and Parallel Computing Systems
Établissements canadiensChevron (Canada)
Organismes subventionnairesNatural Resources Canada
Mots-clésBridging (networking)CitationDownloadComputer scienceWorld Wide WebLibrary scienceSoftwareInformation retrievalComputer security

Résumé

récupéré en direct d'OpenAlex

Abstract The oil and gas industry is rich in complex data types. The data for any organization is often distributed and stored in a variety of formats. It is vital, but almost impossible to share this data between and among systems, teams, functions and companies. To overcome these integration challenges, companies dedicate important resources that could be better focused on core business functions. This data exchange issue extends into data availability. Employees cannot retrieve and analyze the data that they need because it exists in other systems that they cannot access, or are not trained to use. The net result of these data sharing barriers is that decisions are often made using incomplete or incorrect information. Even when the desired data is accessible, the time required for gathering and formatting it may limit the amount of analysis that can be performed before a decision must be made. Chevron Texaco Canada Resources, Northrock Resources, Ltd, and Pioneer Natural Resources Canada Inc. have worked with aclaro softworks, inc. to develop a new web-based reporting application which bridges this data divide. The resulting application, petroLook, provides a common interface to multiple systems in the organization, allowing a richer and more complete source of data to be used for decision making. In addition to providing a window into the organization's information, the application has been designed to facilitate analysis of the data, allowing users to mix data from multiple systems, ‘slice and dice’ the available data, perform ranking between data objects, perform variance analysis between data for different time periods or from different systems, and to perform additional calculations as required. This paper will describe how the petroLook application has increased data availability and decision making ability at three case companies. Pioneer integrated economic and production forecasts, reserves, and field data capture data, which resulted in improved business process that were then re-integrated into the overall process. The application has improved the planning and budgeting cycle at Northrock, while Chevron 's implementation extended the functions of the application to calculate and report forward-looking financials. Introduction THE DATA DIVIDE The oil and gas industry is rich in software solutions for almost every phase and component of the business. Geoscientists, Landmen, Engineers, Accountants, Righands, Marketers, and Computer Scientists all have a wide variety of tools at their disposal which make it easier to do their jobs. Each of these tools has been built to meet the specific needs of a target user group. The data generated by these tools is stored in a variety of applications, databases, and formats, and can also be stored in distributed locations. As vendors add more and more features to these tools, they are generating an everincreasing amount of data. While the applications are generally designed around job function, the data they contain and generate is not so restricted. Actual operating costs for a field, which might be stored as a result in an accounting system, is an important input for an engineer who is trying to build an economic evaluation for a project in that field.

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,003
score de la tête « metaresearch » (Gemma)0,009
Version: codex-gemma-dda1882f352aStatut de validation: machine_predicted_unvalidated
Catégories candidatesMétarecherche, Communication savante, Science ouverte
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: aucune
Score de désaccord entre enseignants0,947
Score d'incertitude au seuil0,999

Scores Codex et Gemma par catégorie

CatégorieCodexGemma
Métarecherche0,0030,009
Méta-épidémiologie (sens strict)0,0000,000
Méta-épidémiologie (sens large)0,0000,000
Bibliométrie0,0000,001
Études des sciences et des technologies0,0010,000
Communication savante0,0030,002
Science ouverte0,0120,004
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,103
Tête enseignante GPT0,310
Écart entre enseignants0,207 · 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.

Devis d'étudeSimulation ou modélisation
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

Citations1
Publié2002
Routes d'admission3
Résumé présentoui

Explorer davantage

Même revueCanadian International Petroleum ConferenceMême sujetDistributed and Parallel Computing SystemsTravaux en français237 207