Dial-a-bus network
Bundling ride requests. Making waiting times visible.
Dispatching is more flexible and predictable for passengers: ride requests are bundled, empty runs are avoided and the waiting time is shown in advance.
- ride requests, waiting time visible to passengers
- Bundled
- ride requests, waiting time visible to passengers
Overview
01 · Problem
Ride requests in rural areas were unevenly distributed.
02 · Approach
Booking, dispatching and notification were connected.
03 · Result
Ride requests could be bundled and the expected waiting time made transparent for passengers.
Before / after
What changed in the business.
Public transport & aviation
Bundling on-demand transport and routes
Starting point
In rural public transport, an on-demand service has to organise rides reliably even though demand and routes fluctuate.
How does digital dispatching improve a dial-a-bus service?
During the project, a platform was built that records ride requests, dispatches suitable tours and informs passengers by message. The portal shows an expected waiting time within the operating logic.
Bundling and tour planning become more practical as a result. Savings in fuel or time are a potential, not a measured result.
At a glance
Levers and services.
- Services
- ConceptImplementationExpansion
- Type of solution
- Processes & workflows
- Industry
- Public transport & aviation
Result
Result and assessment.
- ride requests, waiting time visible to passengers
- Bundled
- ride requests, waiting time visible to passengers
Dispatching is more flexible and predictable for passengers: ride requests are bundled, empty runs are avoided and the waiting time is shown in advance.
What entrepreneurs can take from this
Fluctuating demand can be served better when requests are collected, bundled and answered transparently.
A mechanism, not a promise of results: the effect depends on your starting process.
What this means for you
Building blocks from this case.
This project gave rise to use cases that we now deploy in other companies, adapted to their processes.
Frequently asked questions
Questions about this case.
Your question is not here? In the initial conversation we take 30 minutes for your specific topic.
By message. The portal shows the expected waiting time within the operating logic of the on-demand service.
Dispatching is more flexible and predictable for passengers: ride requests are bundled, empty runs are avoided and the waiting time is shown in advance.
The principle yes, the implementation never one to one. Fluctuating demand can be served better when requests are collected, bundled and answered transparently. In the initial conversation we check which part of it has the greatest leverage for you.
More case studies
Similar cases.
One system
for insights, booking and QR access
Industry & series productionWorkflowsIndustrial 3D printing made transparent: A central event system to run an exhibition centre.
What changed? 3D printing became transparent for guests; the exhibition centre could be organised centrally.
View case
1–2 hrs
instead of several days per calculation
Utilities & suppliersWorkflowsThe core system for more than €3 bn in revenue: Invoicing engine, energy procurement and resource management in one central system.
What changed? One central system supports billing, procurement and resource planning; calculations now take only one to two hours.
View case
1 day
or a few days to a ready workstation
IT system housesWorkflowsEmployee onboarding at the push of a button: A new workstation, a thousand small tasks and orders that can be controlled automatically.
What changed? Workstation and software are ready within a day or a few days.
View case
Do you still plan tours by hand?
In the free initial conversation we look at your process, show a comparable project and assess where the greatest lever lies.
Free · 20 minutes · online
Your next step