- Customers - you cannot specify the customers to consider. By default all customers of a site are considered, unless their inclusion type is set to Exclude in the Customers table.
- Customer's demand - the sum of a customer's demand within a time period for all products. This time period may be less than the specified Experiment duration period because of the value set in the Number of shipments parameter.
- DCs - a DC will not be considered if its inventory policy does not contain the required product.
- Sourcing policy - if a customer is not specified in the sourcing policy, it will be excluded from the experiment.
- Vehicle types - the capacity of the vehicles is considered. Vehicles can be used only on the paths that you define them for.
- Paths - (Only Fixed delivery cost,
Distance based with cost per stop cost, and Cost per drop
calculation formulas are supported) if a customer is specified in the sourcing policy but has no paths leading to and from it,
it will not be serviced, i.e., to properly generate a delivery route, the
Paths table must contain records allowing a vehicle to set off from a DC,
reach the first customer, continue to move from one customer to another one, and finally,
complete the route by returning back to the DC it set off. Make sure that the
Paths table contains the following type of records:
- Site to Customer
- Customer to Customer
- Customer to Site
To run the Capacitated Transportation Optimization experiment
- Click the TO tab located in the top left area of anyLogistix workspace, and select the scenario to work with.
- Navigate to the experiments section and select Capacitated TO experiment.
The GIS map will be substituted with the experiment's parameters.
- Set the experiment parameters:
- Define the Number of shipments.
- Specify the Vehicle types.
- Limit the travel and returning segments if required.
- Change the Min vehicle load ratio for direct shipments if required.
If no errors occur, you will see the experiment progress dialog box, showing data on the currently processed combination of the facility, vehicle type, time period, the reached MIP gap, and the total progress of the experiment.
The progress shows the current iteration and the total number of iterations. The total number is calculated as DCs multiplied by the vehicle types multiplied by the shipments.
When you start the experiment it might face certain errors:
- If Use time windows is enabled, certain customer(s) may be impossible to reach.
In this case the experiment will be aborted and a notification message will pop-up.
e.g. DC open at 10 a.m. and it takes 3 hours to reach the required customer. If the customer is available from 9 a.m. to 12 a.m. the vehicle won't be able to get to the customer on time.
A direct shipment to a customer requires the vehicle to go directly to that customer from the positioning site, which means that there must be a properly defined path between these two objects. If the direct path is not available for some reason (e.g. the required vehicle type is not available on this path), an error message will pop-up, allowing you to skip this specific input combination (site + customer + vehicle type) and go on with the rest of the data (including other combinations with these elements, since they won't result in an error).
The skipped combination will not be available in the results, since the experiment does not consider the skipped data.
e.g. (see image below) Normally a vehicle from London can reach the Brighton customer through the Canterbury customer, but in case of a direct shipment it must have a direct route to the Brighton customer. If this vehicle type is not defined for the direct path, all combinations involving this vehicle type on this path will be skipped.
How can we improve this article?