Industry solutions
From timetable to deployment — transit planning without a black box
Import the timetable once; Fiatto generates vehicle blocks and duties, proposes the weekly roster with as little overtime as possible, and queues a structural shortage as a purchase request — every step with its reason attached.
The problem
Turning a timetable into deployment is often a black box.
Vehicle blocks and duties by hand
Trips are formed into vehicle blocks and duties by hand, and only the planner knows why a choice was made.
Shortages that show up too late
A duty that stays structurally unstaffed only shows up when hiring is already needed.
No view of plan versus reality
What was planned and what was actually driven sit in different systems.
Example · fictitious data
1 · After the import
Vehicle blocks and duties within the rules
The block generator turns the trips into vehicle blocks with minimal dead time, on a planning board per depot. Duties are split at relief points within driving-time and duty limits; anything that does not fit is flagged, never hidden.
2 · In the weekly roster
A roster with as little extra time as possible
The weekly roster proposal keeps extra hours and overtime as low as possible. Leave and sickness count as unavailable, without showing the reason.
3 · On a shortage
A hiring signal with the request ready
If a duty on an approved roster stays structurally unstaffed, a hiring signal with a prefilled purchase request is ready. Submitting stays human work. Afterwards, plan-versus-reality lays out what was actually driven.
What that looks like in practice
You import 374 trips; the generator turns them into 12 vehicle blocks and 61 duties, all within the driving-time rules. The weekly roster honestly shows which duties remain unstaffed — two weeks in a row, and the purchase request for temporary drivers is already prefilled. Afterwards, plan-versus-reality lays out what was actually driven.
- Block generator with a planning board per depot: minimal dead time, and an interlining what-if that honestly shows what it saves
- Duty cutting within your rules: split at relief points, driving-time and duty limits enforced — anything that does not fit is flagged, never hidden
- Weekly roster proposal with as little extra and overtime as possible; leave and sickness count as 'unavailable' without exposing the reason (GDPR)
- A structural shortage on an approved roster becomes a hiring signal with a prefilled purchase request — submitting stays human work
- Plan versus reality per week: coverage, deviating crews and dead time — linked to the fleet and inspection status
Frequently asked questions
Does Fiatto do the planning itself?
Fiatto proposes vehicle blocks, duties and a weekly roster. A purchase request for hiring is queued, but submitting stays human work.
What if a trip does not fit into a duty?
Then it is flagged. The generator keeps to the driving-time and duty limits and hides nothing.
Does the planner see why someone is unavailable?
No. Leave and sickness count as unavailable, without showing the reason.
See how your timetable moves through the trail?
30 minutes, with your own timetable.
Next: procurement — how a structural shortage becomes a purchase request by itself →Explore the platform