Characteristic
Short description
The PTV xTour provides various possibilities to identify orders which remained unscheduled after automatic planning with a PlanToursRequest.
Detailed Consideration
After automatic planning, orders might remain unplanned due to various reasons. There are two different categories of unplanned orders.
Unplanned Orders
During automatic planning, PTV xTour only creates tours without violations.
If scheduling an order resulted in a violation, the order would remain unplanned.
Its id is then added to the field orderIdsNotPlanned in the ToursResponse.
You may need more vehicles
The term vehicle describes what is being routed or planned for. Vehicles are used in route calculation, distance matrix calculation and effectively also in tour planning. In route calculation, vehicle properties like overall size, weight and speed are in focus. In tour planning, it is vehicle properties like capacity and availability.
Commonly a vehicle is motorized, like a truck - including its trailer or a car. However also a bike or even a pedestrian are included in this definition. to plan all the orders in the PlanToursRequest without violations.
Alternatively, you can add the order via a ChangeToursAction to an existing tour. However, this in turn may violate the tour, so it may not be possible to drive this tour in reality. Orders in an input plan may also create violated tours.
Example
A plan with three visits of 2 hours service time each, a single vehicle, and a five hours planning horizon may result in the following response.
Note that only two visits are planned. The third visit remains unplanned because it does not fit into the planning horizon with a single vehicle. Therefore its id is added to the field orderIdsNotPlanned. If there were two identical vehicles instead of only one, the third visit could have been planned.
Unplannable Orders
Unplanned orders may also be unplannable. This means that it is impossible to plan the order without a violation even if there were additional vehicles. Ids of unplannable orders are added to the field orderIdsNotPlannable. Having unplannable orders can be a hint for the user, that there are orders that contain unplausible values, e.g. the order's service time was inadvertently set to 20 hours instead of 2 hours.
Example
A plan with two visits of 2 hours service time each, a visit of 20 hours service time and a five hours planning horizon may result in the following response.
Note that both visits with a two hour service time are planned. The 20 hour service time visit remains unplanned because it does not fit into the planning horizon. Therefore its id is added to the field orderIdsNotPlanned. Even if there were two identical vehicles instead of only one, the unplanned visit could still not be planned, so its id is also added to orderIdsNotPlannable.
Related Topics
| Technical Concept | Orders, Locations, and Stops |
| Integration Sample | Analyzing Unscheduled Orders |