- 04 Dec 2024
- 8 Minutes to read
- Print
- DarkLight
Edit Default Optimization Settings
- Updated on 04 Dec 2024
- 8 Minutes to read
- Print
- DarkLight
You can edit Bringg's default route optimization (RO) settings for planned routes to suit your business priorities and ensure the best possible service for your customers. Adjust and refine preferences that activate when you or your dispatchers optimize routes in Dispatch or Planning to accommodate evolving business priorities.
For example, your default RO settings may initially define the max. route distance allowed for any route as 100 miles. But you may decide to limit it to 80 instead, managing any orders outside that limit by exception. Or, you may need to increase the default clustering level if you want each of your drivers to stay focused in their own geographic areas.
Once you adjust the default optimization settings, you can create override settings for specific teams or use cases. For example, set a wider max. order radius for teams working in more expansive rural areas. Learn more.
Before You Begin
- Confirm you have a user account of type Admin.
- Verify your list of requirements like distance, capacity, or timing limitations for optimization.
- Contact your Bringg customer service representative to configure your initial optimization settings. Learn more.
- Define the shifts and allocation of resources, by creating delivery blocks. Learn more.
- Set up your delivery options with delivery slots. Learn more.
- (Optional) Add vehicle profiles and assign them to your specific vehicles. Learn more.
Update Default Optimization Settings
Step 1: Access the configuration settings page by selecting your username > Settings > Optimization Settings
This page displays any optimization policies you have created.
Step 2: Open the Optimization Default settings by selecting Edit.
Step 3:Adjust the default parameters of your route optimization.
These settings determine the primary rules Bringg's RO engine follows in assigning drivers and vehicles to routes. Tailor the optimization outputs to fit your most common routing needs.
For example, to save unforeseen costs, you can set your optimization to avoid toll roads.
Step 5: Adjust the settings as needed.
For example, to save unforeseen costs, you can set your optimization to avoid toll roads.
Field | Description |
---|---|
Maintain consistency | When enabled, the optimization preserves a consistent solution each time using the same priorities. Otherwise, it may offer you alternative optimal solutions, prioritizing different elements, to help you find the one that best suits your priorities. |
Driver fairness | If enabled, this setting ensures equitable distribution among drivers with respect to the duration of each route (including ETOS). In this case, the optimization selects the route with the lowest standard deviation among drivers for the total route time, but does not consider whether the number or orders assigned to each one is distributed equitably. |
Use all drivers | If enabled, the optimization will prioritize assigning orders to all the drivers who are on shift and available instead of creating fewer routes with fewer drivers. |
Limit absolute orders on route | When enabled, the optimization engine understands the maximum number of orders allowed on a route as the total number allowed, not just the maximum allowed at any point along the route. For example, when a driver is contracted based on a maximum number of orders they can deliver on a route or shift. |
Consider capacity limitations | When enabled, the optimization considers the maximum handling units and weight capacity that the vehicle can transport at a time. |
Max. order radius | The aerial distance limit (km) of any route from the driver start location. The optimization excludes any order outside this radius. |
Force earliest departure | When enabled, the optimization requires drivers to begin routes at the earliest time they are available, whether or not this will cause waiting time later on. Note This setting may override Willingness to wait for the first stop on a route. |
Force delivery within the time window | Selecting this option means the ETA and estimated time on site (TOS) of an order's fulfillment cannot extend beyond the order's time window. For example, if an order that requires assembly has an ETOS of 30 minutes, RO will exclude it from a route if it will arrive within a half hour of the end of the time window. |
Max. route distance | The maximum distance (km) that the optimization can assign to a route. |
Initial loading/unloading time (minutes) | The standard time (minutes) the optimization adds to the start or end of a delivery block to account for either loading or unloading the vehicle. |
Squash time (minutes) | The time (minutes) added for every order after the first one, which is delivered to the same address and customer as the first. For example, if you are sending two orders to Customer X, each with an independent estimated time on site (ETOS) of 15 minutes, and a squash time of 5 minutes, the total ETOS for both orders together is now 20 minutes instead of 30. This setting does not consider differences in order type, such as time required for pick up time as opposed to drop off. Note This setting does not consider differences in order type, such as time required for pick up time as opposed to drop off. |
Exclude ferries | When enabled, the optimization will exclude routes requiring transport via ferry. Use to avoid delays due to congestion at docks. |
Exclude alleys | When enabled, the optimization will not propose routes requiring travel through alleys. Recommended if you use larger vehicles. |
Avoid toll roads | (Outside USA only) Indicate whether or not you want the optimization to avoid toll roads and thereby save costs. In the USA, this setting is automatically required. |
When rerunning optimization: Preserve sequence or Reshuffle | Select which method to use when adding new orders to an already optimized route:
|
Willingness to wait | For stops along a route, indicate using the slider scale to what extent it is an issue for a driver to arrive ahead of schedule and need to wait before fulfilling the order. This setting is not considered by the optimization on the first stop, especially when Force earliest departure is enabled. Note Apply this setting only when all orders in the route have the same time window. For example, if they all must be delivered on Tuesday between 8:00-17:00. |
Default clustering level | The default rank you set for the route clustering process. A higher rank means less often that drivers will crisscross with one another during a shift. |
Default start/end location | Select which option from the dropdown menu to set as the default start or end location of your routes. |
Traffic variable | (Default traffic) The percent of added time to the route due to anticipated traffic. For example, set a +50% anticipated traffic delay in the morning and evening throughout the week and a +125% delay on the day of a major town event that involves road closures. Note Not applicable when using advanced traffic integration, or when traffic variables are applied to specific service areas. Learn more. |
Allow flexible reloading | Selecting this option gives drivers permission to complete multiple routes in one day by returning to the fulfillment center to pick up more orders. Reloads depend on capacity limitations. If preset reload times are already defined in delivery blocks, this setting allows for additional reloads. |
Step 4: Preserve or erase your changes to the default configuration by selecting Save or Discard.
Step 5: (Optional) Create override settings for particular circumstances or teams.
For example, you can set optimization parameters to factor in more time for traffic when heading out of a city before weekends or holidays. Learn more.