Skip to main content

Time Understanding for Vehicle Route Optimization (VRO)

Description: An overview of how route time metrics are defined, configured, and tracked in VRO — covering duty time components, input tables, solution output tables, and wait-time cost setup.

C
Written by Camila Suarez
Updated over a month ago

In GAINS VRO, every route's total Duty Time is composed of four components: Drive Time (time physically driving between stops), Wait Time (time waiting at a stop due to early arrival or a location not being ready), Rest Time (mandatory breaks such as DOT-required 30-minute rests), and Load/Unload Time (time spent on fixed activities at a stop). Duty Time is the master metric — it governs shift limit enforcement and is the basis for hourly cost calculations. Time constraints are configured in the dbo input tables before the solver runs: dbo.Shipments holds load/unload durations, dbo.HoursOfService defines the HOS ruleset profile linked to each driver (duty limits, drive limits, break requirements, and reset times), and dbo.TimeWindows specifies delivery and pickup windows along with penalty costs for early or late arrivals.

Once VRO builds routes, time results are written to two solution tables. sol.ChosenRoutes stores cumulative time columns per stop — including TotalDutyTimeInMinutes, TotalDriveTimeInMinutes, TotalRestTimeInMinutes, and TotalVariableShiftWaitTimeInMinutes — and you should always use the last stop (MAX Step) to get final route-level values rather than summing across rows. sol.RouteStops provides stop-level detail with per-leg drive time, arrival/departure timestamps, and distance

Did this answer your question?