<?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>02155nmc a2200205   4500</leader>
  <controlfield tag="005">20260520010450.0</controlfield>
  <controlfield tag="008">260224s        xxu                      </controlfield>
  <datafield tag="082" ind1=" " ind2=" ">
    <subfield code="a">068.82 553.28 C62 15730</subfield>
  </datafield>
  <datafield tag="210" ind1=" " ind2=" ">
    <subfield code="a">Simposio Campos Maduros</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">CAMBIO DE PARADIGMAS EN CAMPOS MADUROS, CASO UGARTECHE CUENCA CUYANA</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">12/10/2023 ; 12/10/2023</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">22 p. ; 305-326</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">The Ugarteche deposit is located in the Cuyana Basin, a purely continental basin. The productive formations are Barrancas Formation as the main reservoir, and R&#xED;o Blanco Formation as the second important reservoir, both formations of Late Triassic &amp;#x96; Jurassic age. Although the activity began in 1974 and had different stages according to the area, until 2015 there were only 9 wells drilled in the study area of this work. The challenge of resuming the project resided in the environmental conditions due it is an area of vineyards and fruit trees, besides the Mendoza River and Route 40 are located. It should be considered that it was an area with little geological information without 3D seismic, which led to making the static model based on wells and with the help of one or two 2D seismic lines. Throughout time, wells with an accelerated decline and/or completion tests that were not reflected in production. For this reason, possible damage problems were analyzed, mainly for incrustation due to incompatibilities of formation waters, asphaltenes, and movement of fines/clays, this led to the taking of preventive actions such as encapsulation and squeeze during the completion. And execution of chelating agents works, acid stimulation and re-perforate in the case of remediation measures. All these measures worked in almost all cases, being able to recover production in the affected wells.</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="g"></subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">CONGTP</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Palacio, Mar&#xED;a de Bel&#xE9;n</subfield>
    <subfield code="9">61492</subfield>
  </datafield>
  <datafield tag="111" ind1="2" ind2=" ">
    <subfield code="a">Congreso de Exploraci&#xF3;n y Desarrollo de Hidrocarburos (11er : 2022 nov. 8 - 11 : Mendoza)</subfield>
    <subfield code="9">61064</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">196188</subfield>
    <subfield code="d">196188</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">https://biblioteca.iapg.org.ar/ArchivosAdjuntos/Conexplor2022/Simp.CamposMaduros/campos-maduros15.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">263907</subfield>
    <subfield code="a">BVIAPG</subfield>
    <subfield code="b">BVIAPG</subfield>
    <subfield code="c">068.82 553.28 C62 15730</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="j">200068606</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">068.82 553.28 C62 15730</subfield>
    <subfield code="p">200068606</subfield>
    <subfield code="r">2026-03-06 00:41:37</subfield>
    <subfield code="w">2026-03-06</subfield>
    <subfield code="y">ARCHIVO</subfield>
  </datafield>
</record>
