<?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>02274nmc a2200205   4500</leader>
  <controlfield tag="005">20260520165302.0</controlfield>
  <controlfield tag="008">260224s2022                             </controlfield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Chang, David M.</subfield>
    <subfield code="9">60672</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Brown, Robert S.</subfield>
    <subfield code="9">60673</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Yaconis, Santiago J.</subfield>
    <subfield code="9">60674</subfield>
  </datafield>
  <datafield tag="111" ind1="2" ind2=" ">
    <subfield code="a">Congreso Latinoamericano y del Caribe de Refinaci&#xF3;n (6to. : 2022 jun. 1-3 : Buenos Aires)</subfield>
    <subfield code="9">60649</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">CLOSING THE GAP BETWEEN OPTIMIZATION AND OPERABILITY WITH RESILIENT ADVANCED PROCESS CONTROL</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Buenos Aires</subfield>
    <subfield code="b">Instituto Argentino del Petr&#xF3;leo y del Gas, IAPG</subfield>
    <subfield code="c">2022</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">21/06/2022 ; 21/06/2022</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">16 p.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Advanced Process Controls (APC) are designed to yield a certain benefit but are demanding to sustain in the long term. Several factors such as wrong strategy philosophy, instrumentation maintenance and human factors may attempt against APC performance and endurance to dynamic situations. Even artificial intelligence analysis may not be enough against a wrong strategy. APCs are well known for pushing unit limits to its constraints and therefore delivering additional margins. Nevertheless, they have been around the industry for a long time and some consider them as "old" or well-known techniques which do not have much more to exploit. This study shows the roadmap applied on a Fluid Catalytic Cracking APC, with decreasing uptime year to year, in order to make Operations embrace the technology again. Advanced measurement calibration techniques and model structuring were used to gain overall robustness which led to higher uptime. Additionally, a thorough analysis in the process and comprehension of the human factor involved was held. Results showed that uptime was improved, and feed throughput increased by an additional 5% during the harshest season conditions. Additionally, process variance and product sent to flare system was minimized. This confirms that understanding the human factor role and harnessing specific techniques to ensure a resilient APC capable to withstand the disturbances of a continuously changing operation is the key to success.</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">https://biblioteca.iapg.org.ar/ArchivosAdjuntos/CongresoRefinacion2022/043.pdf</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">CONGTP</subfield>
    <subfield code="2">ddc</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">194905</subfield>
    <subfield code="d">194905</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">262624</subfield>
    <subfield code="a">CBAAB</subfield>
    <subfield code="b">CBAAB</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="j">200067292</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200067292</subfield>
    <subfield code="r">2026-03-06 00:39:49</subfield>
    <subfield code="w">2026-03-06</subfield>
    <subfield code="y">ARCHIVO</subfield>
  </datafield>
</record>
