Better Route API - Data Flow & Basic Use Cases

Data Flow

The Better Route API requires you to set up a basic connector set up upfront - allowing job information to reach Bettermile, so it can be used in then the route optimizations over the day.

The Basics - Setting up a tour and generating sequences

Once the job data for a tour has reached Bettermile in the connector, you can go ahead and create a tour. With this being done you can go ahead and a sequence generation. The sequence generation is recommend for any mode to be requested in at least 10 min intervals - if you have updates in the meanwhile (e.g. a job status update), of course more often is beneficial. The modes allow you to define if the route is follow a custom order of waypoints or if to optimize freely based on current location, the defined destination and start time on the sequence request or if to keep a previously defined order mainly intact. The most used optimization mode is FIXED_OPTIMIZATION as it instructs that ETAs of waypoints to be re-calculated, while the order of the waypoints is mostly kept intact (waypoint may only be moved in certain special cases, like when the timeframe changes for a waypoint).

Talk to us if you want to learn more on the basics. Happy to have a chat!

Cater to specific drivers needs (and habits)

We are aware every delivery tour is a bit different while still following basic delivery standards. Drivers have habits (and this is totally ok). Bettermile is there to support these needs.

Selecting the first waypoint

The driver preferring to start their daily tour either in one particular street or in a specific area is something completely normal. This can be reflected with allowing to select the first waypoint when doing the sequence request - you can do this of course also throughout the day if needed.

Setting a custom timeframe on a waypoint

While you can also are able to transfer timeframe information on jobs via the connector - there are cases where it may make sense to allow the driver to also set on the waypoint a specific timeframe (e.g. them knowning that this road being not accessible for vehicles after 10:30 am)

Adding (& removing) custom jobs

While we expect most jobs (aka tasks) for the drivers' tour are transmitted via the connector, there may be situations - such as the driver needing to charge vehicle - where he wants this reflected as separate custom jobs. This means the charging spot is reflected and placed in sequences as well as allowing the surrounding waypoints to update accordingly in ETAs. (for the use case of vehicle charging: best to be combined with custom timeframes on waypoints as well as custom stop time)

Defining a custom destination

The common use case is, the driver in the end of the day returning back to the depot. As this is not the case for all drivers on all days, we allow to also define a custom destination, that we then take into account when calculating the

Defining custom waypoints

In cases where your driver is in need for a mega stop - so a stop where he then delivers to multiple addresses by foot from one parking spot - define a custom waypoint. It is up to your driver then to define the jobs to do here as well as the address where this should happen.

Setting custom stop times

All waypoints get calculated stop times - reflecting the waypoint itself as well as the jobs to be done here. Some waypoints with e.g. security checks to handle, we can not reflect unless the driver let's us know. For this we allow custom stop time to be set (recommended are 15 min intervals to not overwelm the driver in decision)

Checking for recalculation gain

While on the road the day happens, and once in a while there may be faster options to reach destination. Especially if your driver choose to drive in a fully custom order sequence - in order to make a possible ETA gain visible to him, you can request in intervals recalculation gain potential - so a time the driver could save to destination, if he would request a FULL_OPTIMIZATION mode sequence (later please ofc change then to a FIXED_OPTIMZATION mode one , in order to keep the rest of sequence for the driver intakt).