talk to usVehicle rotations, crew duties, depot slots and maintenance intervals in one model. kint covers the timetable at the lowest cost under labour rules and vehicle limits, and shows which rule binds.
Three vehicles are out tomorrow, one for an unplanned repair and two for scheduled maintenance. The timetable stays the same. Which vehicles take which rotations, which drivers take which duties, and which trips change depot? Every swap touches rest times, qualifications and the next maintenance interval.
A vehicle swap changes the duties of every driver on it. Solving vehicles first and crews second leaves the cheaper combined plan unseen.
Rest times, shift lengths, breaks and route knowledge each restrict who can drive what.
Kilometres and hours since the last inspection decide which vehicle may run which rotation.
When a vehicle fails, the plan for the rest of the day has to change from its current state.
Each decision comes back as a plan, the rule that binds it, and the gap to the best possible plan. A person releases it before it is used.
Which vehicle runs which rotation, so every trip is covered and every maintenance interval holds?
Rotations per vehicle with depot moves, the binding interval, and bound and gap.
Empty runs between depots are part of the cost, so the plan keeps them short.
Which driver takes which duty, within rest times, qualifications and route knowledge?
Duties per driver within labour law and works agreements, with the rule that binds.
Preferences enter as goals. Labour law and works agreements stay hard constraints.
A vehicle fails at noon. Which swaps cover the rest of the day with the least change for passengers and crews?
A re-planned afternoon from the current state, with every change listed.
The operations team sees what moved and releases the new plan.
The people stay the same. They work with a plan that states its own quality and its own reasons.
| Dimension | Today | With kint |
|---|---|---|
| Rotations and duties | Planned one after the other | Solved together in one model |
| Quality of the plan | Unknown | Bound and gap, stored with every run |
| Labour rules | Checked after planning | Hard constraints in the model |
| Disruption | Re-plan by hand | Re-solve from the current state |
Exports from your scheduling system, depot system or ERP are enough to start. kint's decision agent drafts the model from the planners' description. In the pilot, kint's forward deployed engineers (FDEs), who work directly with the customer's team, review it with the experts.
Timetable, vehicle list, maintenance intervals and duty rules, as read-only exports.
Planners state labour rules, depot limits and priorities in their own words. The agent writes them down for review.
Rotations and duties next to today's plan, with bound and gap stated.
A person releases the plan. It goes back only through an API you control.
A conversation with kint's FDEs. Bring the decision and its rules, and get a first model planners can read.