<?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>02178nab a2200217   4500</leader>
  <controlfield tag="005">20260520003102.0</controlfield>
  <controlfield tag="008">260224s2012    xxu                 ing  </controlfield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">Ingl&#xE9;s</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Simultaneous Inversion of Production Data and Seismic Attributes: Application to a Synthetic SAGD Produced Field Case</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">mar./abr. 2012</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">27/05/2013 ; 27/05/2013</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">12 p. ; 289-301</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Traducci&#xF3;n del res&#xFA;men del autor: The joint use of production data and time-lapse seismic attributes can help to understand fluid flows within geological formations and to build reliable numerical models for representing these formations. This concern recently motivated the development of dedicated inversion or matching techniques for identifying models consistent with all collected data. The methodology presented in this paper makes it possible to map petrophysical properties such as facies, porosity and permeability into reservoirs from production data and seismic attributes. It is successfully applied to a synthetic case describing a heavy oil field produced from steam assisted gravity drainage. This case study generated from a real case shows how to design the inversion methodology to match the entire set of available data. A few key points are highlighted since they drive the success of the proposed matching methodology. First, parameterization is essential. It must allow for locally varying petrophysical properties from a reduced number of parameters. Second, this study stresses the need for alternative formulations for quantifying the mismatch between reference seismic attributes and simulated seismic attributes. Last, two methods are compared for integrating reference seismic attributes either in time or in depth (after a time-to-depth conversion). In the case studied, it is shown that the two approaches are equivalent since time-to depth-conversion error is quite small.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">2</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">Oil and Gas Science and Technology</subfield>
    <subfield code="g">67</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Tillier, E.</subfield>
    <subfield code="9">53208</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Le Ravalec, M.</subfield>
    <subfield code="9">53127</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Da Veiga, S.</subfield>
    <subfield code="9">53209</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">187708</subfield>
    <subfield code="d">187708</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">255527</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="j">200059851</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200059851</subfield>
    <subfield code="r">2026-03-06 00:17:42</subfield>
    <subfield code="w">2026-03-06</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
