Today
Dispatchers plan collection and delivery routes from experience, and something changes every day: an urgent job, a vehicle out of service, a full container. The data for it is spread across the ERP, spreadsheets and phone notes. Empty runs and missed time windows cost money and customer trust.
An example
On Monday, Wertora Recycling has 212 container exchanges to run, including 38 roll-off containers of 15 m³ and 20 m³. With the cleaned-up data the route planner needs 14 routes instead of 16. At 9:40 two urgent pickups come in, and after re-planning both fit into existing routes without breaking a time window.
Your data, wherever it lives
Today orders and customer time windows sit in the ERP, containers and shifts in spreadsheets, fill levels come from sensors or from customers on the phone, vehicles and positions from telematics and urgent jobs by e-mail. demi reads, understands and links them into one planning record per day, with your rights. The AI hands your route planner complete data every morning, explains every change from the day before and triggers re-planning within minutes for an urgent job, and dispatchers approve the routes.
Where the data lives today
- ERP
- Office files
- Machines & sensors
- Phone & voice
- Telematics
- E-mails
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
The case needs data from the ERP, TMS and spreadsheets. demi replaces nothing and joins orders, customer time windows, containers and their fill levels, vehicles with capacity, and drivers and shifts into one planning record per day. demi writes back only after approval.
- 2 · PermitPermission Layer
Dispatchers approve routes, and drivers see only their own route. Every change after approval is recorded with its reason.
- 3 · ActIntelligence Layer
Routes are computed by your route planner or a connected routing solver from the recorded constraints, not by the language model. The agent feeds it complete data, explains the changes from the previous day and triggers re-planning for urgent jobs.
How it runs
- 1
The day before, demi gathers orders, time windows, containers and available vehicles.
- 2
The agent checks the data for gaps, such as missing time windows or container types.
- 3
The route planner computes the routes, and the agent explains what changed from the day before.
- 4
Dispatch releases the plan and every driver gets their route.
- 5
When an urgent job comes in, routes are re-planned and the change goes up for release.
What changes
Fewer empty runs
Time windows kept
Faster daily planning
What does it bring you?
Check it with your own numbers
Every starting value is an assumption you can change. The calculation sits right below, step by step.
Your numbers
Result
+119 hfreed per year
Assumptions and calculation
demi brings orders, containers and vehicles into planning and fits in rush jobs; you release the routes.
90 min → 63 min per case
How we calculate
22 route plans × 90 min × 30% × 1.0 (manual) × 12 months = 7,128 min = 119 h
Value per year, before demi costs
Freed per year+119 h
Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.
= Value per year, before demi costs
+€7,735
gained per year
119 h ÷ 1,760 h per role = 0.1 full-time roles
An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.
Combine with more cases and get the packageQuestions about this use case
Does demi replace our route planning software?
No. Your route planner stays and computes the routes. demi makes sure it gets complete, clean data and explains the result. If you have none, a routing solver is connected.
Can demi handle urgent jobs?
Yes. An urgent job from an e-mail or phone note is captured as an order and triggers re-planning. Dispatch sees which route changes and which time windows are affected, and releases it.
Does demi use fill levels?
If your containers have fill-level sensors or drivers report fill levels, they are used. Full containers are pulled forward and half-empty ones pushed back, by your rules. Without fill levels, demi plans from orders and fixed intervals.
What do drivers see?
Each driver sees only their own route with sequence, addresses, time windows and container type. Changes during the day reach them only after dispatch has released them.
