- Includes Geocoding if coordinates of orders are not provided (extra run-time costs)
- Detailed routing plan can be calculated (extra run-time costs)
- Possible specification of route end points (finding the best route endpoint is part of the optimization)
- Possible specification of delivery deadlines for each order
- Possible specification of order/customer priorities
- Possible specification of load characteristics per order and vehicle
- Different types of transport selectable, e.g. car, bike, walk
- Multiple Vehicles and Depots/Warehouses allowed
- Timing Options to customize for the individual complexity of the problem
- Robust, with many mitigation strategies
Primary use-cases for the Fleetplanner service:
The well-known Traveling Salesman Problem is a special case of the Vehicle Routing Problem: It describes a salesperson who wants to visit a specific set of locations at least once and return to the origin. The order of which the salesperson visits the locations does not matter. The goal is to keep the traveling costs and distance as low as possible. This is a famously difficult problem in computer science since exponentially growing computation time is required to find the optimal route. Popular use cases include “maintenance roundtrips”, “customer on-site visits”, and “planning city tours”.
Multi Traveling Salesperson
In many practical scenarios it makes sense to split up the work to be serviced by “multiple “resources”" instead of one. Since the “resources” can operate in parallel, all customers can be visited earlier. To find optimal routes, the service has to decide which “resource” visits which locations (and in which order). Popular use cases include “maintenance visits”, “customer on-site visits”, and “planning public transportation routes”.
Multiple “resources” can also be used to split up the work sequentially, e.g. a facility manager is in charge of 20 locations and has to visit them once per week - he can use 5 “resources” instead of one to split his viewings up into 5 tours (one per work day).
Vehicle Routing with Customer Deadlines and Priorities
In many scenarios the route is not only determined by its duration but also by “deadlines” that must be met: Customers that have a deadline coming up soon should be prioritised, despite it not being the quickest path. The fleetplanner service will first try to avoid missing deadlines, and then attempt to improve the routing duration. When trade-offs need to be made (e.g. when not all deadlines can be met), then you could assign a “priority” to each customer to ensure that higher priority deadlines are met rather than low priority deadlines (if this trade-off is necessary at all).
That means for the optimization: meet high priority deadline > meet low priority deadline > total duration of routes
Vehicle Routing with Capacity Management
For Vehicle Routing use-cases where freight is picked-up or delivered it is important to not exceed each vehicle’s capacity. The service interface allows you to specify each “order’s load values” (e.g. its weight) as well as each “vehicle’s load constraints” (e.g. its maximum load weight capacity). Popular use cases include “transport” or “delivery companies”.