Transportation Summary

Internal Table Name: VehicleRouteOptimizationSummary

Scenario

Table: VehicleRouteOptimizationSummary

Internal Name: Not Applicable (Scenario column not in table)

The scenario for which the output data was generated.

Solve Start Time

Table: VehicleRouteOptimizationSummary

Internal Name: ModelRunTime

The date and time when the Transportation Optimization run started.

Solve Duration

Table: VehicleRouteOptimizationSummary

Internal Name: SolveTime

The time it took for the Transportation Optimization to complete.

Total Transportation System Cost

Table: VehicleRouteOptimizationSummary

Internal Name: TotalTransportationSystemCost

The total cost of the complete transportation optimization solution. This value is

Total Route Cost +Total Fixed Asset Cost + Unrouted Shipment Direct Shipping Cost

Total Route Cost

Table: VehicleRouteOptimizationSummary

Internal Name: TotalRouteCost

The total cost of the generated routes.

Total Direct Shipping Cost

Table: VehicleRouteOptimizationSummary

Internal Name: TotalLTLCost

The total cost incurred in the solution based on the Direct Shipping Cost from the Shipments table. This is the sum of all direct shipping costs where shipments were assigned to Direct routing rather than on routes generated by Transportation Optimization.

Total Fixed Asset Cost

Table: VehicleRouteOptimizationSummary

Internal Name: TotalFixedAssetCost

The total fixed asset cost incurred in the solution. This is based on the Unit Fixed Cost as defined in the Transportation Asset table. The Total Fixed Asset Cost is only incurred when using Optimize Fleet Size.

Total Inventory Holding Cost

Table: VehicleRouteOptimizationSummary

Internal Name: TotalInventoryHoldingCost

When running Periodic Optimization, this column displays the cost incurred holding inventory. The Inventory Holding Cost in the Periodic Schedule table is applied to the quantity, weight or volume of Transportation Daily Orders as determined by the Periodic Schedule Inventory Holding Cost Basis.

Total Routes

Table: VehicleRouteOptimizationSummary

Internal Name: TotalRoutes

The total number of generated routes.

Total Assets

Table: VehicleRouteOptimizationSummary

Internal Name: TotalAssets

The total number of unique transportation assets used.

Total Stops

Table: VehicleRouteOptimizationSummary

Internal Name: TotalStops

The total number of stops on the generated routes.

Total In-Transit Stops

Table: VehicleRouteOptimizationSummary

Internal Name: TotalInTransitStops

The number of in-transit stops on the generated routes. This count does not include the initial stop at the pool site nor the final stop at the pool site for round trip routes. It also does not include stops at a domicile, in the case where the asset is located at a site other than the pool site.

Total Distance

Table: VehicleRouteOptimizationSummary

Internal Name: TotalDistance

The total distance traveled on the generated routes.

Total Reposition Distance

Table: VehicleRouteOptimizationSummary

Internal Name: TotalRepositionDistance

The total distance the assets traveled to return to their starting locations in round trip routes. The asset is typically empty for this distance.

Total Time

Table: VehicleRouteOptimizationSummary

Internal Name: TotalTime

The total time in minutes spent on the generated routes. This is defined as End Date Time - Start Date Time per route.

Total Input Quantity

Table: VehicleRouteOptimizationSummary

Internal Name: TotalInputQuantity

The total of all shipment quantities considered for Transportation Optimization.

Total Output Quantity

Table: VehicleRouteOptimizationSummary

Internal Name: TotalOutputQuantity

The total of all shipment quantities carried on the generated routes.

Total Input Weight

Table: VehicleRouteOptimizationSummary

Internal Name: TotalInputWeight

The total of all shipment weight considered for Transportation Optimization.

Total Output Weight

Table: VehicleRouteOptimizationSummary

Internal Name: TotalOutputWeight

The total of all shipment weight carried on the generated routes.

Total Input Cubic

Table: VehicleRouteOptimizationSummary

Internal Name: TotalInputCubic

The total of all shipment cubic volume considered for Transportation Optimization.

Total Output Cubic

Table: VehicleRouteOptimizationSummary

Internal Name: TotalOutputCubic

The total of all shipment cubic volume carried on the generated routes.

Total Segments

Table: VehicleRouteOptimizationSummary

Internal Name: TotalSegments

The total number of segments on all generated routes. Segments are the lanes between pairs of stops.

Total Deliveries

Table: VehicleRouteOptimizationSummary

Internal Name: TotalDeliveries

The total number of delivered shipments on all generated routes.

Total Unrouted Shipments

Table: VehicleRouteOptimizationSummary

Internal Name: TotalUnroutableShipments

The total number of unrouted shipments. Unrouted shipments are those shipments that are not routed by Transportation Optimization. Shipments are typically unrouted when they violate a constraint such as asset capacity or business hours at a location. Shipments can also be unrouted if the Direct Shipment Cost is less than the cost to route a shipment. The Direct Shipment Cost is often the cost to deliver the shipment using LTL or parcel shipping.

Total Invalid Shipments

Table: VehicleRouteOptimizationSummary

Internal Name: TotalInvalidShipments

The total number of invalid shipments. Invalid shipments are those shipments that cannot be considered for routing by Transportation Optimization. In many cases, the Origin or Destination in the Shipment record does not have a corresponding Site Name in the Sites table. This results in an invalid shipment. Conflicting constraints can also cause a shipment to be considered invalid, such as when there are conflicting Relationship Constraints defined for the same shipment.

Optimization Type

Table: VehicleRouteOptimizationSummary

Internal Name: OptimizationType

The selected algorithm run on the data. One of the following:

  • Standard Optimization
  • Backhaul Optimization
  • Periodic Optimization
  • Interleaved Optimization

Asset Time Utilization

Table: VehicleRouteOptimizationSummary

Internal Name: AssetTimeUtilization

This utilization applies for tours only; that is, when the Optimize Fleet Size option is selected. It is calculated, across all assets in the scenario, as:

Where Length of Tour is the duration in time of the tour.

Route Utilization

Table: VehicleRouteOptimizationSummary

Internal Name: RouteUtilization

This is the percentage of total/maximum for the unit of measure most utilized on the route, calculated per route:

For example, if a vehicle has a total weight capacity of 40,000 lbs and picks up 30,000 lbs. from the distribution center for a milk run delivery route, its route utilization will be 30,000/40,000 = 75%. The unit of measure considered for this calculation is the unit of measure most utilized on the route (one of Quantity, Weight or Cubic).

This calculation is useful for assessing routes when using standard optimization (pooled inbound or outbound networks). It may not be appropriate for interleaved (continuous moves) networks where routes have several pickups and several deliveries. Please refer to the Segment Utilization formula for this type of route.

Segment Utilization

Table: VehicleRouteOptimizationSummary

Internal Name: SegmentUtilization

This is the average vehicle utilization across each segment on the route, weighted by the distance of each segment:

Consider the example of a route for a vehicle with a maximum weight capacity of 40,000 lbs:

Segment [A,B]: load = 20,000 lbs., distance = 100 miles

Segment [B,C]: load = 10,000 lbs., distance = 200 miles

Segment [C,A]: load = 0 lbs., distance = 200 miles

The segment utilization is calculated as (100 * 20,000 + 200 * 10,000 + 200 * 0) / (500 * 40,000) = 20%

The unit of measure considered for this calculation is the unit of measure most utilized on the route (one of Quantity, Weight or Cubic).

This calculation is useful for assessing routes when using interleaved optimization (continuous moves). It may not be best for standard optimization (pooled inbound or outbound) networks since the vehicle gets progressively empty (outbound) or full (inbound) throughout the route. Please refer to the Route Utilization formula for this type of route.

Total Sourcing Cost

Table: VehicleRouteOptimizationSummary

Internal Name: TotalSourcingCost

Displays the total cost incurred for shipments that have been dynamically sourced. Shipments that do not have a source defined can be assigned a source site and will incur a unit production cost based on the selected source. Additionally, a single fixed startup cost can be incurred if a site dynamically assigned as a source to one or more shipments. This cost is the Total Fixed Startup Cost + Total Variable Production Cost.

Total Sortie Cost

Table: VehicleRouteOptimizationSummary

Internal Name: TotalSortieCost

Displays the total cost incurred for sorties that are carried out by drones.

Total Sorties

Table: VehicleRouteOptimizationSummary

Internal Name: TotalSorties

Displays the total number of sorties that are carried out by drones.

Total Drones

Table: VehicleRouteOptimizationSummary

Internal Name: TotalDrones

Displays the total number of drones that are used to carry out sorties.

Total Sortie Stops

Table: VehicleRouteOptimizationSummary

Internal Name: TotalSortieStops

Displays the total number of stops that drones carry out on sorties.

Sortie Utilization

Table: VehicleRouteOptimizationSummary

Internal Name: SortieUtilization

Displays the average of the Sortie Utilization from the Sortie Summary for the individual sorties in the solution.

Solver Setting

Table: VehicleRouteOptimizationSummary

Internal Name: SolverSetting

The value set in the Solver Setting option in Transportation Optimization options at the time the scenario was solved. This will be one of Fastest, Fast, Balanced, Expanded or Detailed.

Scenario ID

Table: VehicleRouteOptimizationSummary

Internal Name: ScenarioID

The identifier of the scenario for which the output data was generated.

Sub-Scenario ID

Table: VehicleRouteOptimizationSummary

Internal Name: StepNumber

The identifier of the sub-scenario, if applicable, for which the output data was generated.

Last modified: Wednesday May 15, 2024

Is this useful?