Logistics

Route Planning Agent

The evening before, the route is set. By morning, it no longer works.

Optimises routes based on orders, traffic data and SLA requirements.

Optimises routes based on orders, traffic data and SLA requirements.

Open agent

Enlarge demo

Public administration

Four processes that take up the most time today

Developed in Germany · Hosted in the EU

Developed in Germany · Hosted in the EU or on-premises

Delivered together with

Sovereign hosting in Germany, single-tenant from the first user.

Sovereign hosting in Germany, single-tenant from the first user.

Legal, tax and compliance expertise for legally sound deployment.

Legal, tax and compliance expertise for legally sound deployment.

Advisory and implementation for the public sector, starting with the AI readiness assessment.

Advisory and implementation for the public sector, starting with the AI readiness assessment.

Dispatch reshuffles the stops by hand twice on Monday morning, and in the afternoon the driver ends up driving the detour.

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.

38

stops

Monday's route is set in the TMS on Friday evening with 38 stops.

6

late changes

Six order changes come in over the weekend, two of them with a fixed time commitment.

2

manual replans

Dispatch reshuffles the sequence twice, once first thing and once at ten.

41 km

extra distance

In the evening, telematics shows 41 kilometres more than the calculated sequence would have needed.

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.

Three steps through the process.

The agent calculates route variants and shows where a time commitment breaks; the route that goes out is the one dispatch releases.

1.

1.

Combine orders and time windows

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.

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 commitment

2.

2.

Calculate route variants against the commitments

The agent simulates several sequences against traffic and telematics data. For each variant, it records which time commitments it keeps and which it breaks.

The 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 window

3.

3.

Put the route proposal into the daily plan

The agent puts the variant into the daily plan with kilometres, journey time and the critical stops. Dispatch decides which route goes out.

The 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 conflict

What the agent does not do.

It does not release any route.

It does not release any route.

It presents the calculated variants with kilometres and window conflicts. Dispatch releases the route and assigns it to the drivers.

It does not factor in driving and rest times.

It does not factor in driving and rest times.

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.

A road closure the driver only reports over the radio does not appear in the calculation.

A road closure the driver only reports over the radio does not appear in the calculation.

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

TMS transport management

fleet telematics

ERP

Operations

Deployment model

EU cloud or private cloud

EU cloud or private cloud

Data processing

GDPR-compliant, no model training on your data

GDPR-compliant, no model training on your data

Responsible teams

Dispatch, transport management

Dispatch, transport management

The questions that come up before the first meeting.

How quickly is the Route Planning Agent ready to use?

Where is the data processed?

Where does the figure “10 to 20% lower transport costs” come from?

Related agents.

All agents

Platform

Industries

Services

Resources

Company

Pricing

From AI strategy to a running platform: we show you the way.

Talk to us

Log in

DE

EN

English

Platform

Industries

Services

Resources

Company

Pricing

From AI strategy to a running platform: we show you the way.

Talk to us

Log in

DE

EN

English
neuland.ai

The AI management and orchestration platform from Cologne.

Developed in Cologne. Operated in the EU or in your data center.

Certifications and compliance: ISO 27001, ISO 9001, GDPR, EU AI Act, DORA, StBerG, and BRAO
WirtschaftsWoche Best of Technology 2026 seal, 2nd place in the Process Management category for neuland.ai

© 2026 neuland AI AG