FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W4234971028> ?p ?o ?g. }

• W4234971028 abstract "Managing Operational Data Throughout the Life Cycle of an Asset Mike Feechan Mike Feechan Halliburton Energy Services Search for other works by this author on: This Site Google Scholar Paper presented at the SPE Petroleum Computer Conference, Dallas, Texas, June 1997. Paper Number: SPE-38115-MS https://doi.org/10.2118/38115-MS Published: June 08 1997 Cite View This Citation Add to Citation Manager Share Icon Share Twitter LinkedIn Get Permissions Search Site Citation Feechan, Mike. Managing Operational Data Throughout the Life Cycle of an Asset. Paper presented at the SPE Petroleum Computer Conference, Dallas, Texas, June 1997. doi: https://doi.org/10.2118/38115-MS Download citation file: Ris (Zotero) Reference Manager EasyBib Bookends Mendeley Papers EndNote RefWorks BibTex Search Dropdown Menu nav search search input Search input auto suggest search filter All ContentAll ProceedingsSociety of Petroleum Engineers (SPE)SPE Petroleum Computer Conference Search Advanced Search AbstractTraditionally within the energy industry, much emphasis has been placed upon the gathering and management of geoscientific data for easy access, analysis, and decision-making purposes. Typically, however, much less emphasis has been placed on the management of operational data and its integration with geoscientific, economic, and public-domain data sets. As a result, much of the data is never captured or stored, and attempting to access these data is time-consuming and sometimes unsuccessful.In 1995, Halliburton Energy Services launched a major project to design and implement an environment for managing operational and technical data with integrated applications to access, retrieve, and analyze the data. The foundation of this project was Halliburton's technical data model (HTDM), which has been under development since 1991. While the initial goal was to provide operational and technical data to Halliburton's internal users, it quickly became apparent that efficient management of wellsite data from the point of acquisition presents a major opportunity to the industry for more effective and efficient operations. Informed, timely, optimized decision making is enabled by easy access to these data and by the analysis of these data with integrated application software. Halliburton's plan includes development of a globally distributed relational database with application and communications methods that allow acquisition, access, and analysis of data from any location.This paper also presents examples of successful implementation of the system to lower costs and improve efficiency by effective data mangement.IntroductionFor years, the energy industry has gathered and managed geoscientific data for easy access, detailed analysis, and critical decision-making. Such data have included those derived from seismic, geologic, petrophysical, and well-test surveys. Typically, however, the industry has placed much less emphasis on managing operational data and integrating that data with geoscientific, economic, and public-domain data sets. Although much operational data has been captured, they are usually found over disconnected and frequently incompatible computer databases. Just as often, operational data are found in hardcopy files in widely separated locations. Thus, the difficulty in gathering operational data from these disjointed sources have made attempts at comprehensive analysis of such data expensive, time consuming and often impractical.Today, operators and service companies concentrate on overall reservoir management and seek the most cost-effective methods to achieve and maintain optimal reservoir performance. A high-quality, well-populated, easily accessible operational database can be analyzed to help minimize operational costs and determine the most successful operational procedures.In 1995, Halliburton Energy Services launched a major project to design and implement an environment for managing operational and technical data with integrated applications to access and analyze the data. This project was named TIMS (Technical Information Management Systems). To implement the operational aspects of the TIMS project, project goals were clarified and workflow processes were reviewed. Then, a comprehensive relational data model and an associated workflow scheme were developed, and software and hardware were selected to implement the database and workflow scheme. The database and workflow are currently being phased into field operations.Project GoalsThe database and workflow scheme that were to be developed through the TIMS project would:–support and improve mainstay workflow processes across all the company's product-service lines (PSLs)–capture and manage job experience to support decision functions Keywords: Drillstem Testing, information management, drillstem/well testing, Upstream Oil & Gas, operational data, life cycle Subjects: Formation Evaluation & Management, Information Management and Systems, Drillstem/well testing This content is only available via PDF. 1997. Society of Petroleum Engineers You can access this article if you purchase or spend a download." @default.
• W4234971028 created "2022-05-12" @default.
• W4234971028 creator A5086442254 @default.
• W4234971028 date "1997-06-01" @default.
• W4234971028 modified "2023-09-25" @default.
• W4234971028 title "Managing Operational Data Throughout the Life Cycle of an Asset " @default.
• W4234971028 doi "https://doi.org/10.2523/38115-ms" @default.
• W4234971028 hasPublicationYear "1997" @default.
• W4234971028 type Work @default.
• W4234971028 citedByCount "0" @default.
• W4234971028 crossrefType "proceedings-article" @default.
• W4234971028 hasAuthorship W4234971028A5086442254 @default.
• W4234971028 hasConcept C10138342 @default.
• W4234971028 hasConcept C127413603 @default.
• W4234971028 hasConcept C136764020 @default.
• W4234971028 hasConcept C144133560 @default.
• W4234971028 hasConcept C171730128 @default.
• W4234971028 hasConcept C2776517139 @default.
• W4234971028 hasConcept C2778805511 @default.
• W4234971028 hasConcept C2780154274 @default.
• W4234971028 hasConcept C38652104 @default.
• W4234971028 hasConcept C41008148 @default.
• W4234971028 hasConcept C42475967 @default.
• W4234971028 hasConcept C76178495 @default.
• W4234971028 hasConcept C77088390 @default.
• W4234971028 hasConceptScore W4234971028C10138342 @default.
• W4234971028 hasConceptScore W4234971028C127413603 @default.
• W4234971028 hasConceptScore W4234971028C136764020 @default.
• W4234971028 hasConceptScore W4234971028C144133560 @default.
• W4234971028 hasConceptScore W4234971028C171730128 @default.
• W4234971028 hasConceptScore W4234971028C2776517139 @default.
• W4234971028 hasConceptScore W4234971028C2778805511 @default.
• W4234971028 hasConceptScore W4234971028C2780154274 @default.
• W4234971028 hasConceptScore W4234971028C38652104 @default.
• W4234971028 hasConceptScore W4234971028C41008148 @default.
• W4234971028 hasConceptScore W4234971028C42475967 @default.
• W4234971028 hasConceptScore W4234971028C76178495 @default.
• W4234971028 hasConceptScore W4234971028C77088390 @default.
• W4234971028 hasLocation W42349710281 @default.
• W4234971028 hasOpenAccess W4234971028 @default.
• W4234971028 hasPrimaryLocation W42349710281 @default.
• W4234971028 hasRelatedWork W2017614413 @default.
• W4234971028 hasRelatedWork W2024347112 @default.
• W4234971028 hasRelatedWork W2171420994 @default.
• W4234971028 hasRelatedWork W2226589689 @default.
• W4234971028 hasRelatedWork W2317981192 @default.
• W4234971028 hasRelatedWork W2374348909 @default.
• W4234971028 hasRelatedWork W2376987262 @default.
• W4234971028 hasRelatedWork W2393813166 @default.
• W4234971028 hasRelatedWork W2949483020 @default.
• W4234971028 hasRelatedWork W4255905854 @default.
• W4234971028 isParatext "false" @default.
• W4234971028 isRetracted "false" @default.
• W4234971028 workType "article" @default.