talk to usSetup times, shift patterns, due dates and dependencies in one model. kint finds the schedule with the least idle time and shows which machine sets the pace.
The week's jobs are on the board. One machine needs a long changeover between product families. Another is down for maintenance on Tuesday afternoon. A priority order that arrived this morning must ship by Friday. Moving one job shifts everything after it. By evening there is a schedule. Whether a better one exists under the same rules, nobody can tell.
Setup time between product families can rival production time. The order of jobs matters more than speed.
A priority order cascades through the schedule. Re-planning by hand costs hours.
Idle machines cost throughput. Without a bound on the best schedule, nobody knows how much.
Crew qualifications, maintenance windows and overtime rules each add a dimension to the puzzle.
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.
In which order do the jobs run on each machine, respecting setups, maintenance and due dates?
A schedule per machine and shift, the bottleneck named, and bound and gap.
Planners see where capacity is tight, where there is room, and why.
Which product batches go to which line, so changeovers stay rare?
An assignment of batches to lines, grouped by setup family.
The solver weighs the full matrix of changeover times between product families, not only neighbouring pairs.
Which crew, with which qualifications, staffs which line in each shift?
A shift plan within working-time rules and works agreements.
Labour law and works agreements are hard constraints. Staff preferences enter as goals.
The people stay the same. They work with a plan that states its own quality and its own reasons.
| Dimension | Today | With kint |
|---|---|---|
| Schedule creation | Hours of manual planning | Solved by the engine, reviewed by planners |
| Quality of the plan | Unknown | Bound and gap, stored with every run |
| Changeovers | Grouped by experience | Minimized across the full setup matrix |
| Rush orders | Re-plan by hand | Re-solve the remaining schedule |
| Planner overrides | The plan is redone on the floor | Built for fewer corrections: the real rules are in the model |
Exports from your MES, ERP or APS 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.
Capabilities, setup times, shift patterns and maintenance windows, from MES or ERP exports.
Due dates, dependencies and overtime limits, stated by the planners and reviewed as written rules.
kint minimizes idle time or makespan under every rule and returns the schedule per machine.
Move a job, change a due date, re-solve. A planner releases the schedule before it reaches the floor.
A conversation with kint's FDEs. Bring the decision and its rules, and get a first model planners can read.