<?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>02378nab a2200217   4500</leader>
  <controlfield tag="005">20260520004420.0</controlfield>
  <controlfield tag="008">260224s2013    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">Geology and geohistory contribute to flow assurance</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">mayo 2013</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">10/07/2013 ; 10/07/2013</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">5 p. ; 129-134</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del resumen del autor: This paper presents information regarding past traditional flow-assurance analyses at an example field, along with an example using a new multidisciplinary method that integrates geological information into the analyses, resulting in a detailed asphaltene matrix risk profile for this reservoir. During the past asphaltene flow-assurance risk assessment, the traditional analyses have revealed some anomalous results such as asphaltene onset pressure (AOP) being detected from some fluid samples while not being detected from others. The apparently inconsistent AOP results are critical to understanding how to guide flow-assurance measures. Therefore, all available asphaltene data were re-assessed in all aspects to attempt to clarify asphaltene risk. Asphaltene issues have often been discussed by multidisciplinary teams consisting of petrophysicists and engineers with well, production, reservoir, chemical, or pipeline backgrounds because such multidisciplinary approaches can deliver fresh eyes to redefine problems. This paper, as a new approach, demonstrates the worth of uniting a further discipline, geoscience, with flow assurance. A synergy between reservoir engineering and geoscience (geology and geohistory) has been developed to explain AOP results for this complex fluid. The results should help flow-assurance specialists to better define the asphaltene operating envelope, which will be used for reservoir and production operations optimization. In addition, these results should be useful for optimizing data surveillance, flow assurance, and for defining new sample acquisition plans. These findings may also be helpful in minimizing future sampling and fluids analysis while achieving reliable flow assurance.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">2</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">SPE Production &amp; Operations</subfield>
    <subfield code="g">28</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Yonebayashi, Hideharu</subfield>
    <subfield code="9">53354</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Tosic, Slavko</subfield>
    <subfield code="9">53355</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">O'Brien, Dennis R</subfield>
    <subfield code="9">53356</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">187795</subfield>
    <subfield code="d">187795</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">255614</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="j">200059945</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200059945</subfield>
    <subfield code="r">2026-03-06 00:17:50</subfield>
    <subfield code="w">2026-03-06</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
