<?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>02154nab a2200205   4500</leader>
  <controlfield tag="005">20260520003108.0</controlfield>
  <controlfield tag="008">260224s2015    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">Design and Evaluation of Energy Management using Map-Based ECMS for the PHEV Benchmark</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">ene./feb. 2015</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">15/09/2015 ; 15/09/2015</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">16 p. ; 195-211</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del resumen del autor: Plug-in Hybrid Electric Vehicles (PHEV) provide a promising way of achieving the benefits of the electric vehicle without being limited by the electric range, but they increase the importance of the supervisory control to fully utilize the potential of the powertrain. The winning contribution in the PHEV Benchmark organized by IFP Energies nouvelles is described and evaluated. The control is an adaptive strategy based on a map-based Equivalent Consumption Minimization Strategy (ECMS) approach, developed and implemented in the simulator provided for the PHEV Benchmark. The implemented control strives to be as blended as possible, whilst still ensuring that all electric energy is used in the driving mission. The controller is adaptive to reduce the importance of correct initial values, but since the initial values affect the consumption, a method is developed to estimate the optimal initial value for the controller based on driving cycle information. This works well for most driving cycles with promising consumption results. The controller performs well in the benchmark; however, the driving cycles used show potential for improvement. A robustness built into the controller affects the consumption more than necessary, and in the case of altitude variations the control does not make use of all the energy available. The control is therefore extended to also make use of topography information that could be provided by a GPS which shows a potential further decrease in fuel consumption.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">1</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">Oil and Gas Science and Technology</subfield>
    <subfield code="g">70</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Sivertsson, Martin</subfield>
    <subfield code="9">54882</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Eriksson, Lars</subfield>
    <subfield code="9">54883</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">189205</subfield>
    <subfield code="d">189205</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">257024</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="j">200061437</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200061437</subfield>
    <subfield code="r">2026-03-06 00:19:25</subfield>
    <subfield code="w">2026-03-06</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
