FRINK Linked Data Fragments server

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

• W2023017651 abstract "Abstract In the report the analysis of the basic difficulties of prediction cases hydrodynamic modeling is executed. It is offered to describe prediction cases not in terms of simulator key words, but in terms of events and patterns of actions. It will raise the quality of prediction cases and will reduce time necessary for its designing. Also it will free the reservoir management engineer of necessity of detailed studying numerous simulator key words. Introduction According to requirements of Russian regulating documents [1, 2] the digital filtration model should be constructed as a part of reservoir management documentation. It serves for revealing zones of oil-in-place and predicting results of the further reservoir management. With use of digital filtration model some reservoir management prediction cases are calculated, and then the most effective case gets out. Thus quality of the accepted decision is influenced with quality of the initial data incorporated in model, quality of model history matching, and also the used way of the prediction case description. This report is devoted to the last of these factors. Classic way of the prediction case description Let's consider the basic difficulties of prediction case description.Designing a prediction case, reservoir management engineer operates with concepts perforation, well repair work, start of production, transition well to another object after some water cut», etc. To perform calculations he should to describe a prediction case in language of a simulator key words and cells of a hydrodynamic grid. The detailed knowledge of simulator key words and understanding of interference of these words is necessary.It is not possible to achieve ideal model history matching. As a rule, even in models with qualitatively executed history matching, the model values of productivity for some wells can considerably differ from actual values. In such situation it is important to correctly choose a well control method in prediction case. Traditionally, one of the next two ways is used.Control by bore hole pressure (BHP). In a case when model productivity of well is differs from actual, it leads to significant difference predicted oil and liquid rates from the actual.Control by last liquid production rate. Thus predicted oil and liquid production rates will not differs from actual, but modeling of perforations and squeezes becomes impossible (as it will not be reflected on oil and liquid production rates). It will be more correct to control production wells by last depression with restrictions on bore hole pressure. Such way would remove lacks of the previous two methods. Unfortunately, this method is not realized in existed simulators. However this method is inapplicable, when it is planned to restore reservoir pressure (with the help of injection). In this case depression after restoration reservoir pressure should be greater then at the start of prediction. Also it is inapplicable, when is planned to optimize work of the wells. Therefore it is desirable to have also an opportunity to change depression depending on a condition of reservoir management." @default.
• W2023017651 created "2016-06-24" @default.
• W2023017651 creator A5020499634 @default.
• W2023017651 creator A5050021603 @default.
• W2023017651 date "2008-10-28" @default.
• W2023017651 modified "2023-09-24" @default.
• W2023017651 title "Hydrodynamic Simulation Of Predicted Options Of Field Development" @default.
• W2023017651 doi "https://doi.org/10.2118/117408-ms" @default.
• W2023017651 hasPublicationYear "2008" @default.
• W2023017651 type Work @default.
• W2023017651 sameAs 2023017651 @default.
• W2023017651 citedByCount "1" @default.
• W2023017651 countsByYear W20230176512020 @default.
• W2023017651 crossrefType "proceedings-article" @default.
• W2023017651 hasAuthorship W2023017651A5020499634 @default.
• W2023017651 hasAuthorship W2023017651A5050021603 @default.
• W2023017651 hasConcept C202444582 @default.
• W2023017651 hasConcept C33923547 @default.
• W2023017651 hasConcept C39432304 @default.
• W2023017651 hasConcept C41008148 @default.
• W2023017651 hasConcept C9652623 @default.
• W2023017651 hasConceptScore W2023017651C202444582 @default.
• W2023017651 hasConceptScore W2023017651C33923547 @default.
• W2023017651 hasConceptScore W2023017651C39432304 @default.
• W2023017651 hasConceptScore W2023017651C41008148 @default.
• W2023017651 hasConceptScore W2023017651C9652623 @default.
• W2023017651 hasLocation W20230176511 @default.
• W2023017651 hasOpenAccess W2023017651 @default.
• W2023017651 hasPrimaryLocation W20230176511 @default.
• W2023017651 hasRelatedWork W1997866474 @default.
• W2023017651 hasRelatedWork W2042305627 @default.
• W2023017651 hasRelatedWork W2287557217 @default.
• W2023017651 hasRelatedWork W2368533078 @default.
• W2023017651 hasRelatedWork W2387835245 @default.
• W2023017651 hasRelatedWork W2610977553 @default.
• W2023017651 hasRelatedWork W2731053458 @default.
• W2023017651 hasRelatedWork W2735099109 @default.
• W2023017651 hasRelatedWork W2741631988 @default.
• W2023017651 hasRelatedWork W2800336875 @default.
• W2023017651 hasRelatedWork W2892419114 @default.
• W2023017651 hasRelatedWork W2893581190 @default.
• W2023017651 hasRelatedWork W2901744307 @default.
• W2023017651 hasRelatedWork W2908013461 @default.
• W2023017651 hasRelatedWork W2982669660 @default.
• W2023017651 hasRelatedWork W2989765678 @default.
• W2023017651 hasRelatedWork W3098005741 @default.
• W2023017651 hasRelatedWork W3105383601 @default.
• W2023017651 hasRelatedWork W3120854013 @default.
• W2023017651 hasRelatedWork W2572681612 @default.
• W2023017651 isParatext "false" @default.
• W2023017651 isRetracted "false" @default.
• W2023017651 magId "2023017651" @default.
• W2023017651 workType "article" @default.