<?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>02163nmc a2200205   4500</leader>
  <controlfield tag="005">20260520005610.0</controlfield>
  <controlfield tag="008">260224s2001    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">Probabilistic Model To Develop Multilayer Gas and Oil Prospects</subfield>
    <subfield code="b">SPE 69614</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Dallas, Texas</subfield>
    <subfield code="b">Society of Petroleum Engineers</subfield>
    <subfield code="c">2001</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">12/09/06 ; 17/07/01</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">It is not that uncommon when putting together an exploratory program to find that there are several prospects within a block, and/or several reservoirs within an individual prospect. Given that we could successfully develop each prospect, the total value of the property will be equal to the sum of the individual prospects, i.e. we can add the Net Present Value (NPV) distributions taking into account the probability of success of each prospect to obtain an estimation of the block&amp;#x92;s value. This simple process will be complicated when one or more of the prospects have more than one potential layer. We can solve this problem by introducing simplifications, such as adding all the layers and developing them as one unit. But what if they are at different depths, have different productivity index, gravity or impurities? We can also build a decision tree that takes into consideration the different future scenarios. This is usually tedious, time consuming and we could introduce additional bias when having to assign probabilities to the different branches. This paper shows a simple methodology to build a probabilistic production forecast, capital and operation expenditures for a prospect with several layers, in order to make an economic evaluation of an exploration opportunity.</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">CONGTP</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Faya, Luis C.</subfield>
    <subfield code="9">6527</subfield>
  </datafield>
  <datafield tag="111" ind1="2" ind2=" ">
    <subfield code="a">Latin American and Caribbean Petroleum Engineering Conference (7th : 2001 mar. 25-28 : Buenos Aires, Argentina)</subfield>
    <subfield code="9">5738</subfield>
  </datafield>
  <datafield tag="711" ind1="2" ind2=" ">
    <subfield code="a">Latin American and Caribbean Petroleum Engineering Conference (7th : 2001 mar. 25-28 : Buenos Aires, Argentina)</subfield>
    <subfield code="9">5738</subfield>
  </datafield>
  <datafield tag="800" ind1="1" ind2=" ">
    <subfield code="a">Faya, Luis C.</subfield>
    <subfield code="9">6527</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">131178</subfield>
    <subfield code="d">131178</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">https://biblioteca.iapg.org.ar/ArchivosAdjuntos/LACPEC2001/Spe69614.pdf</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">202100</subfield>
    <subfield code="a">BVIAPG</subfield>
    <subfield code="b">BVIAPG</subfield>
    <subfield code="d">2026-03-03</subfield>
    <subfield code="j">200003256</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200003256</subfield>
    <subfield code="r">2026-03-03 01:41:18</subfield>
    <subfield code="w">2026-03-03</subfield>
    <subfield code="y">ARCHIVO</subfield>
  </datafield>
</record>
