Assets

Internal Table Name: VRPOutputAssets

The Assets table provides information about sequence of routes that are assigned to an asset during the planning horizon by Transportation Optimization.

Scenario

Table: VRPOutputAssets

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

The scenario for which the output data was generated.

Asset ID

Table: VRPOutputAssets

Internal Name: AssetID

The identifier of the asset.

Asset Name

Table: VRPOutputAssets

Internal Name: AssetName

The asset type that the asset represents.

Location

Table: VRPOutputAssets

Internal Name: Location

The Site Name to which the asset is assigned from the Asset Availability table.

Start Date Time

Table: VRPOutputAssets

Internal Name: StartDateTime

The date and time at which the asset started its first route.

End Date Time

Table: VRPOutputAssets

Internal Name: EndDateTime

The date and time at which the asset ended its last route.

Total Asset Route Cost

Table: VRPOutputAssets

Internal Name: TotalCost

The total cost calculated for the asset. This includes both route costs and asset fixed costs.

Horizon Fixed Asset Cost

Table: VRPOutputAssets

Internal Name: EquipmentFixedCost

The total asset-based fixed cost of the asset for the model horizon.

Total Route Cost

Table: VRPOutputAssets

Internal Name: TotalRouteCost

The total cost of the routes assigned to the asset.

Total Distance

Table: VRPOutputAssets

Internal Name: TotalDistance

The total distance traveled by the asset.

Reposition Distance

Table: VRPOutputAssets

Internal Name: RepositionDistance

The total distance the asset travels to return to its starting location for the round trip routes assigned to the asset. The asset is usually empty for this distance.

Total Stops

Table: VRPOutputAssets

Internal Name: TotalStops

The total number of stops for the routes assigned to the asset. These stops include the in-transit stops, plus the initial and final stops at the pool site. It also includes stops at a domicile, if the asset is located at a site other than the pool site.

In Transit Stops

Table: VRPOutputAssets

Internal Name: InTransitStops

The total number of in-transit stops for the routes assigned to the asset. This count includes any stop with a pickup or delivery. For example, this would include a pickup stop at the pool site origin of an outbound route.

Total Weight

Table: VRPOutputAssets

Internal Name: TotalWeight

The total weight carried on the asset.

Total Cubic

Table: VRPOutputAssets

Internal Name: TotalCubic

The total cubic volume carried on the asset.

Total Qty

Table: VRPOutputAssets

Internal Name: TotalQty

The total quantity carried on the asset.

Total Time

Table: VRPOutputAssets

Internal Name: TotalTime

The total time in minutes spent from the start of the first route to the end of the last route assigned to the asset.

Total Time = End Date Time - Start Date Time

Duty Time

Table: VRPOutputAssets

Internal Name: DutyTime

The total duty time (in minutes) for the asset.

Duty Time = Drive Time (driving time) + Service Time (loading/unloading time) + Break Time (short breaks) + Wait Time

Drive Time

Table: VRPOutputAssets

Internal Name: OperatingTime

The total driving time expressed in minutes.

Reposition Time

Table: VRPOutputAssets

Internal Name: RepositionTime

The total operating time, in minutes, with an empty load. This is the time the asset travels to return to its starting location for the round trip routes assigned to the asset.

Service Time

Table: VRPOutputAssets

Internal Name: ServiceTime

The time incurred in activities such as loading and unloading shipments. You can define Fixed Service Time and Variable Service Time on the Transportation Assets table, Fixed Service Time and Variable Service Time on the Sites table, and Service Time (service time at the non-pool site location) on the Shipment itself.

Wait Time

Table: VRPOutputAssets

Internal Name: WaitTime

The total wait time, in minutes, incurred at locations. For example, wait time can be incurred when the asset arrives before opening time at a location.

Break Time

Table: VRPOutputAssets

Internal Name: ShortBreakTime

The total break time, in minutes, from short breaks within a shift. You must define Break Time and Max Drive Time Before Break in the Transportation Asset table to incur short breaks within a shift.

Overnight Time

Table: VRPOutputAssets

Internal Name: LongBreakTime

The time incurred due to Rest Time, which is defined in Transportation Assets. The shift is defined based on the Max Duty Time Before Rest Time in Transportation Assets.

Total Gap Time Between Routes

Table: VRPOutputAssets

Internal Name: TotalGapTimeBetweenRoutes

The total time accumulated through gaps between the end and start of all the routes assigned to an asset, in minutes.

Start Date Time Local

Table: VRPOutputAssets

Internal Name: StartDateTimeLocal

The local time of the first location at the start of the first route assigned to the asset.

End Date Time Local

Table: VRPOutputAssets

Internal Name: EndDateTimeLocal

The local time of the last location at the end of the last route assigned to the asset.

Time Utilization

Table: VRPOutputAssets

Internal Name: TimeUtilization

This utilization applies for tours only; that is, when the Optimize Fleet Size option is selected. It is calculated, for each asset, as:

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

Route Utilization

Table: VRPOutputAssets

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: VRPOutputAssets

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.

Number of Routes in Asset

Table: VRPOutputAssets

Internal Name: NumberOfRoutes

The number of routes that are assigned to the asset.

Decomposition ID

Table: VRPOutputAssets

Internal Name: DecompositionID

Displays the decomposition value based on the selected Shipments Decomposition Field in Transportation Optimization Options. For example, if you have selected Shipment Destination Country as the Shipments Decomposition Field, shipments with destinations in Spain are not routed with shipments to France.

Scenario ID

Table: VRPOutputAssets

Internal Name: ScenarioID

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

Sub-Scenario ID

Table: VRPOutputAssets

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?