Tradeteam – Drinks Distributor – Transport Review

Posted by Jason Tindley on 06-Sep-2023 14:57:11

DHL Tradeteam – Wholesaler Fleet Review.png


To assist or enable all elements of the study a base case model was built using historical delivery data of two average and two peak weeks.  The model was built with all routes exactly as planned down to the route content, drop order and vehicle size using the same software Distributer use for daily planning.

Missed OTIFs

The bulk of the missed OTIFs were in Central London where nearly half of customers have AM delivery restrictions.  Reaching East London from Reading for an AM delivery is a challenge in its own right.  To identify less obvious reasons for declining service standards, a sample of routes were compared as planned vs. as in the model vs. as driven on the day according to TMS data.  This revealed that on average, speeds and unloading times were comparable between the original plans, the base case model and the actual operation according to the TMS data.  However, it was the exceptions that were causing the missed service levels:

  • Most of the actual unloading times broadly matched the planned unloading times, but there were some unloading times that were much higher than planned and these had a knock on effect for the rest of the route.
  • Broadly, most of the inter drop driving times approached the planned inter drop driving times but there were a number of exceptions, probably due to traffic jams, where the inter drop driving time was much higher than planned leading to missed OTIFs later in the trip.
  • There were instances of risky planning where a delivery was planned to arrive ten minutes before the delivery window closed or an AM delivery was placed on the latter half of a trip, leading to a negative outcome
  • The default digitised road network lacked detail at the urban road level leading to nearly adjacent deliveries having other drops placed in between them on the plan.
  • Drivers chose to change the delivery order of their routes in over a third of cases.  One contributing factor to this behaviour is likely to be the lack of digital road network detail at urban level.

Given the findings, these were the recommendations put forth:

  • In order to mitigate unexpected delays, introduce defensive planning such as:
  • Changing AM customers’ delivery windows to close 30 minutes earlier in the customer master file.
  • Avoiding the planning of AM deliveries in the second half of a route.
  • Investigate instances where delivery took a lot longer than planned.  If this is due to one or more customers’ consistent behaviour, then amend their record in the customer master file accordingly with longer delivery times.
  • Replace the default digitised road map with a fully detailed one such as the ones used by satnavs to get a more rational drop order that drivers do not feel the need to alter.
  • Set up a feedback loop between drivers and planners to introduce to and maintain in the planning software slow down factors for specific times of day and at known traffic black spots.

Replacement Fleet Size and Profile

Building a detailed base case model is essential to any transport modelling study.  Not only does it prove or not that the data and parameters used are correct and representative, but if it is built exactly as planned as it was in this instance, the base case model immediately highlights what is thought to be but is not.

What was learned from the exact base case model was that many customers were restricted to vans in the master file not because they physically were but because they had habitually been planned to be served by vans.  This became obvious when routes known to have been run with a 7.5T or 18T rigid were peppered with drops allegedly restricted to vans.  Had this not been brought to light then fleet size and profile proposed would not have been correct.

After the issues highlighted by the base case were dealt with the four representative weeks’ data were rescheduled in order to determine the appropriate fleet size and profile to move forward with.  Given the findings of the investigation into missed OTIFs, two solutions were put forth: one assuming no changes to operations and a second one assuming more defensive planning in order to meet OTIF targets.

Review of Distribution Network

The main distribution network opportunity revolved around supporting the Reading stockholding site.  Reaching East London from Reading is a challenge so a suitable Distributer site in East London was tested as a satellite.  What came to light was that the benefits of adding such a location to the network were limited because the predominance of AM deliveries in its catchment area meant that driver average shift times were too short at the East London site and therefore the number of vehicles higher than should be given normal average drivers’ hours.

Whilst for this scenario there were savings to be had on radial delivery, the aggregated vehicle count between the two sites would have decrease and the utilisation of the Reading fleet would have increased, these savings were cancelled by the trunking requirement to feed the East London satellite, so the only benefit of this arrangement was in terms of increased customer service and reduced risk of missed OTIFs.


New Call-to-action

Topics: Transport Planning

Subscribe here!

Recent Posts

New Call-to-action