Return to Hub

Documentation Index

Fetch the complete documentation index at: https://docs.mileapp.dev/llms.txt

Use this file to discover all available pages before exploring further.

Return to Hub is a route optimization feature that ensures vehicles return to the hub at the end of every trip. This creates clear route endpoints and helps with operational planning for vehicle dispatch and driver management.

​

What is Return to Hub?

By default, route optimization creates routes that end at the last visit location. With Return to Hub enabled, all routes are extended to include the hub as the final destination, ensuring vehicles complete their trips back at the starting point. Key Characteristics:

• Ensures vehicles return to hub at trip end
• Creates clear route endpoints for operations
• Required for Multi Trip functionality
• Optional sub-configuration for returning after working hours

​

Activate Return to Hub

To activate Return to Hub, follow these steps:

1. Go to the Routing/Configuration menu.
2. Check the “Return to Hub” checkbox.
3. (Optional) Enable “Allow vehicle to return after the end of working time” if needed.

Once enabled, the routing engine will include the hub as the final destination for all vehicle trips.

​

Return to Hub Options

​

Main Configuration: Return to Hub

When enabled, all vehicle routes will end at the hub location, regardless of where the last visit is located.

​

Sub-Configuration: Allow Vehicle to Return After Working Time

This optional setting controls whether vehicles can return to the hub after their working hours end. When enabled:

• Vehicles can complete their return journey even if it extends beyond working hours
• The last visit must still be completed within working hours
• Only the return trip to hub can exceed the time limit

When disabled (default):

• Vehicles must complete the entire route, including return to hub, within working hours
• Routes are planned to ensure hub return happens before working hours end

​

How Return to Hub Works

​

Without Return to Hub (Default Behavior)

Routes end at the last visit location:

1. Route endpoint: Last visit location
2. Total distance: Optimized to minimize travel
3. Use case: When vehicles don’t need to return to base

Example:

• Hub → Visit 1 → Visit 2 → Visit 3 (end)
• Driver finishes at Visit 3 location
• Vehicle remains at Visit 3 until next trip

​

With Return to Hub Enabled

Routes include hub as final destination:

1. Route endpoint: Hub location
2. Total distance: Includes return journey
3. Use case: Standard fleet operations with central dispatch

Example:

• Hub → Visit 1 → Visit 2 → Visit 3 → Hub (end)
• Driver finishes at hub
• Vehicle ready for next dispatch from hub

​

Use Cases

​

Use Case 1: Centralized Fleet Management

Scenario: Logistics company with centralized vehicle maintenance and dispatch operations. Configuration:

• Return to Hub: Enabled
• All vehicles start and end at central hub
• Vehicles available for maintenance and inspection

Result: All vehicles return to base daily for inspection, refueling, and next-day preparation.

​

Use Case 2: Driver Safety and Transportation

Scenario: Company provides transportation for drivers back to central location. Configuration:

• Return to Hub: Enabled
• Drivers can leave personal vehicles at hub
• Company provides safe return location

Result: Drivers start and end shifts at the same location, simplifying commute and parking.

​

Use Case 3: Multi-Trip Operations

Scenario: High-volume delivery requiring multiple trips per vehicle per day. Configuration:

• Return to Hub: Enabled (automatically)
• Multi Trip: Enabled
• Vehicles reload at hub between trips

Result: Vehicles complete multiple delivery rounds with hub returns for reloading.

​

Use Case 4: Inventory and Cash Collection

Scenario: Delivery service requiring end-of-day inventory reconciliation and cash deposit. Configuration:

• Return to Hub: Enabled
• End-of-day procedures at hub
• Secure cash handling location

Result: All drivers return to hub for inventory count and cash deposit procedures.

​

Use Case 5: Flexible Working Hours

Scenario: Peak season operations where return travel might exceed standard hours. Configuration:

• Return to Hub: Enabled
• Allow vehicle to return after the end of working time: Enabled
• Last visit within working hours, return journey flexible

Result: Drivers complete all visits on time, with flexibility for return journey during busy periods.

​

Best Practices

​

When to Use Return to Hub

✓ Use when:

• Vehicles need centralized parking and maintenance
• Drivers require consistent start/end location
• Multi-trip operations are planned
• End-of-day procedures require hub presence
• Security protocols need vehicle return
• Fuel and maintenance facilities are at hub

✗ Avoid when:

• Minimizing distance is critical priority
• Vehicles are stored at distributed locations
• Next-day routes start from previous day’s endpoint
• Additional return distance significantly impacts costs

​

Sub-Configuration: Return After Working Time

Enable when:

• Peak season requires operational flexibility
• Ensuring visit completion is higher priority than strict hour limits
• Return distance from last visit is significant
• Occasional overtime is acceptable for complete service

Disable when:

• Strict working hour compliance is required
• Overtime must be prevented
• Labor regulations restrict extended hours
• Planning needs to account for complete route within hours

​

Combining with Other Features

Works well with:

​

Relationship with Multi Trip

Return to Hub has a special dependency with Multi Trip: This dependency exists because multi-trip operations require vehicles to return to the hub for reloading between trips.

​

Frequently Asked Questions

Q: How much extra distance does Return to Hub add? A: It varies based on the location of the last visit relative to the hub. If the last visit is far from the hub, the return distance can be significant. Q: Can some vehicles return to hub while others don’t? A: No, Return to Hub is a global configuration setting. When enabled, all vehicles in the optimization will return to the hub. You cannot selectively apply it to specific vehicles. Q: What happens if “Allow vehicle to return after working time” is enabled? A: The engine will ensure all visits are completed within working hours, but allows the return journey to the hub to extend beyond the working time limit. This provides flexibility for peak periods while maintaining service quality. Q: Does Return to Hub work with time windows? A: Yes, the engine respects all visit time windows. The return to hub happens after all visits are completed. If working hours are restrictive, some visits may not be assigned to maintain the constraint. Q: If I enable Return to Hub, will it automatically enable Multi Trip? A: No, enabling Return to Hub does not automatically enable Multi Trip. However, the reverse is true: enabling Multi Trip will automatically enable Return to Hub. Q: How does this affect the optimization result? A: Routes will be longer due to the return journey, but operationally simpler. The engine optimizes visit sequence to minimize the return distance impact. Total route time will increase, potentially reducing the number of visits per route.

​

Related Documentation

• Route Optimization Configuration Introduction
• Multi Trip
• Use All Vehicle
• Clustering