Optimises routes based on orders, traffic data and SLA requirements.
Developed in Germany · Hosted in the EU or on-premises
Delivered together with
Sovereign hosting in Germany, single-tenant from the first user.
Legal, tax and compliance expertise for legally sound deployment.
Advisory and implementation for the public sector, starting with the AI readiness assessment.
The route is planned in the TMS on Friday, with the orders received by then. Changes come in over the weekend, and early on Monday the telematics system reports the first hold-up. Dispatch then replans on screen, stop by stop, keeping track of the time commitments in their heads.
If the fleet follows the calculated variant rather than the reshuffled one, transport costs per route are 10 to 20% lower.
The 10 to 20% reduction in transport costs is this agent's headline figure. The 41 extra kilometres on the Monday route reflect a typical day in local delivery dispatch; they are not a measured value.
The agent reads the open orders from the TMS along with the agreed time windows. It assigns the weekend's late changes to the route affected.
Route NL-Mo-217, 44 stops after 6 late changes, 9 stops with a fixed time commitmentThe agent simulates several sequences against traffic and telematics data. For each variant, it records which time commitments it keeps and which it breaks.
3 variants calculated, variant B 41 km shorter, stop 29 falls outside the 08:00 to 10:00 windowThe agent puts the variant into the daily plan with kilometres, journey time and the critical stops. Dispatch decides which route goes out.
tourenvorschlag_NL-Mo-217.pdf, 44 stops, 1 stop flagged for a window conflictIt presents the calculated variants with kilometres and window conflicts. Dispatch releases the route and assigns it to the drivers.
It calculates distance, sequence and journey time. Whether the driver can complete the variant within his permitted driving time is something transport management checks before adding a stop.
It plans with the traffic and telematics data from the connected sources. If a driver phones in a diversion, dispatch enters it in the plan by hand.
Connected systems
Operations
A pilot typically runs on your own data within 4 to 6 weeks. The agent connects to your existing systems rather than running as a separate, parallel environment.
EU cloud or private cloud. Processing is GDPR-compliant and models are never trained on your data. Details in the Trust Center.
It is based on experience from comparable projects and process benchmarks, not a commitment. We work out the realistic effect for your organisation during the assessment before the pilot.