<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02767nab a2200193   4500</leader>
  <controlfield tag="005">20260520001939.0</controlfield>
  <controlfield tag="008">260224s2010    xxu                      </controlfield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Zheng, Shiyi</subfield>
    <subfield code="9">42868</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Xu, Wenbin</subfield>
    <subfield code="9">50089</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Calibration of fluid models using multiphase well test data for improved history matching</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">dic. 2010</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">30/05/2011 ; 30/05/2011</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">9 p. ; 168-177</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del resumen del autor: History matching of reservoir performance is difficult due to the uncertainties associated with reservoir properties. These uncertainties include the variety of geological model and fluid model. Usually, reservoir engineer changes geological properties to match history data, but ignore the changes of fluid properties, which may have a big influence on history matching. Considering a mature field entering high water-cut stage, for many infill wells, the well productivity can be obtained by stabilized well testing, but there is a phenomenon for drawdown (DD) test where the bottom-hole pressure (BHP) may increase with time when the water-cut reaches some value. In this situation, many reservoir engineers think this phenomenon was due to the change of production rate, the change of skin factor near wellbore or the interference of multi-wells. This paper excludes the interferences of these reasons, the objective of research focus on multiphase flow and explains the phenomenon from the viewpoint of multiphase flow. It is well known that the change of pressure on late time of well testing is closed to constant in closed system or closed to zero in constant pressure system. But under transient state, steady-state or semi-steady-state conditions, if the bottom-hole pressure goes up, then the DD data may not be used for well test analysis or reservoir engineering analysis. This paper presents study results on wells producing a multiphase reservoir by numerical well test model. According to Darcy's Law, a new theoretical expression was derived in this situation, in which the derivative of bottom-hole flowing pressure is a function of integral of total mobility, which can be approximatively replaced of the average total effective mobility. Using this equation, the reason why well bottom-hole pressure increasing with time may be reasonably explained. According to the results of this study, under multiphase flow condition, the BHP increasing is due to the changing of the fluid total mobility, in this paper, it was further demonstrated that the data of this type can be used to adjust fluid model and improve history matching.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">1-2</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">Journal of Petroleum Science &amp; Engineering</subfield>
    <subfield code="g">75</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">182200</subfield>
    <subfield code="d">182200</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="9">250019</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-05</subfield>
    <subfield code="j">200054240</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200054240</subfield>
    <subfield code="r">2026-03-05 23:52:21</subfield>
    <subfield code="w">2026-03-05</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
