<?phpxml version="1.0" encoding="ISO-8859-1"?>
 <collection>
  

 
<record>
 <datafield tag="088" ind1="" ind2="">
  <subfield code="a">GoSwDuycSala09</subfield> 
  </datafield>
<datafield tag="980" ind1="" ind2="">
<subfield code="a">REPORT</subfield>
</datafield>
<datafield tag="909" ind1="C" ind2="0">
<subfield code="p">TRANSP-OR</subfield>
</datafield>
<datafield tag="245" ind1="" ind2="">
<subfield code="a">
Ambush avoidance in Vehicle Routing for valuable delivery</subfield>
</datafield>
<datafield tag="260" ind1="" ind2="">
<subfield code="c">2009</subfield>
</datafield>
 <datafield tag="700" ind1="" ind2="">
  <subfield code="a">Swartz, Peter</subfield> 
  </datafield>
 <datafield tag="700" ind1="" ind2="">
  <subfield code="a">Duyckaerts, Gaetan</subfield> 
  </datafield>
 <datafield tag="700" ind1="" ind2="">
  <subfield code="a">Salani, Matteo</subfield> 
  </datafield>
<datafield tag="520" ind1="" ind2="">
<subfield code="a">
In this work we consider route planning for valuable delivery in an urban environment under the threat of ambushes in which a vehicle, starting from a depot, has to serve a set of predetermined destinations during the day. 
We provide a method to plan for hardly predictable multi-destination routing extending a minmax flow-based model available for single-destination cases. 
We then formulate the process of selecting a visiting order as a game to obtain a mixed routing strategy. We analyse the application of the method to a set of simulation scenarios and compare the mixed routing strategy against the best routing. 
Finally we develop further the methodology introducing a second-level optimization model which reduces the overall risk associated to the proposed mixed routing strategy.</subfield>
</datafield>
<datafield tag="856" ind1="4" ind2="">
<subfield code="z">URL</subfield>
<subfield code="u">https://transp-or.epfl.ch/documents/technicalReports/GoSwDuycSala09.pdf</subfield>
</datafield>
<datafield tag="856" ind1="4" ind2="0">
<subfield code="x">public</subfield>
</datafield>
  </record>



  </collection>
