A truck route plan is only usable if it respects what the vehicle, the road and the law impose. Travia builds rounds from those constraints and compares the result with your real day.
Payload, number of axles and body type decide which vehicle can take which order, and in which order it is loaded.
Each order is assigned to a vehicle whose capacity and equipment fit. Incompatibilities are excluded before the calculation, not corrected afterwards.
Night and Sunday driving bans, roads closed to 40-tonne trucks, local restrictions: a route that is valid on a map is not always allowed for a truck.
Closed roads and time windows are stored as network constraints. The engine avoids them and reports when an order cannot be served the same day.
Driving time and mandatory breaks belong in the plan. A round that ignores them ends late or out of compliance.
Driving, break and service times are planning parameters. The plan shows the expected time of every stop.
Several depots, loading on the way, empty runs to be limited: the stop order has to take the whole network into account.
Several depots, intermediate loads and returns are weighed at the level of the whole day, not round by round.
No. Travia works upstream of round building and can take orders from your ERP or TMS. Existing telematics data can feed the tracking. The exact scope is set during the design phase.
They are stored during configuration as network and time-window constraints, based on your real rules. Testing a real day is precisely how the compliance of the generated plan is checked.
The engine does not force an unrealistic plan: the order is reported as unplaced, with the constraint that blocks it, for dispatch to decide.
Send us your current rounds. We reproduce your constraints and compare the results with your current organisation.
No software change required first