<?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>01697nab a2200205   4500</leader>
  <controlfield tag="005">20260520002831.0</controlfield>
  <controlfield tag="008">260224s2010    xxu                      </controlfield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Optimal energy management in hybrid electric trucks using route information</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">ene./feb. 2010</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">05/07/2010 ; 05/07/2010</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">12 p. ; 103-114</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del resumen del autor. To benchmark a hybrid vehicle&amp;#x92;s Energy Management Strategy (EMS) usually a given, often certified, velocity trajectory is exploited. In this paper it is reasoned that it is also beneficial to optimize the velocity trajectory. Especially optimizing the vehicle braking trajectories, through maximization of energy recuperation, results in considerable fuel savings on the same traveled distance. Given future route (target velocities as function of traveled distance/location), traffic, and possibly weather information, together with the vehicle&amp;#x92;s road load parameters, the future power request trajectory can be estimated. Dynamic Programming (DP) techniques can then be used to predict the optimal power split trajectory for the upcoming route, such that a desired state-of-charge at the end of the route is reached. The DP solution is re-calculated at a certain rate in order to adapt to changing conditions, e.g., traffic conditions, and used in a lower level real-time EMS to guarantee both battery state-of-charge as well as minimal 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">65</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Van Keulen, T.</subfield>
    <subfield code="9">43449</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">De Jager, B.</subfield>
    <subfield code="9">43450</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Serrarens, A.</subfield>
    <subfield code="9">43451</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">171728</subfield>
    <subfield code="d">171728</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">239547</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-05</subfield>
    <subfield code="j">200046596</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200046596</subfield>
    <subfield code="r">2026-03-05 15:14:08</subfield>
    <subfield code="w">2026-03-05</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
