resource allocation.
Assign limited resources, such as people, equipment or budget, to tasks, regions or projects. Get the most done, or spend the least, within capacity.
Two crews dropped out after the storm. How do the remaining crews cover every region with the least travel and no gap in emergency cover?
Resource allocation is modelled as a linear program when resources are divisible and as a mixed-integer program when they are not. For changing conditions kint plans over several periods with a rolling horizon, so each new plan overlaps the last one.
where resource allocation gets hard.
Half a crew or half a crane does not exist. Integer requirements make the problem hard even when the continuous version is easy.
A crew sent north today cannot serve the south tomorrow. Each decision changes the options of the next period.
Fair workload, low cost, full coverage and reserve capacity cannot all be maximised at once.
from the rules to the bound.
kint's decision agent writes the model from the planners' description. In the pilot, kint's forward deployed engineers review it with the experts. Then the solver does this.
choose LP or MIP
Divisible resources go into a linear program, discrete ones into a mixed-integer program. kint selects the formulation from the problem.
plan with a rolling horizon
The plan covers several periods and is re-optimised as conditions change. Windows overlap for smooth handovers.
start from today's plan
The current allocation seeds the next run. The solver starts from a good point and converges faster.
show the binding limits
kint reports which limits bind and where one more crew or one more hour would make the largest difference.
a resource allocation plan, with its reasons.
Below are the parts of a resource allocation result. Planners check them before the plan is released.
the anatomy of an answer- planAn assignment of each crew or asset to a region or task, per period.
- binding limitFor example: specialist skills in one region bind, not the total number of crews.
- sensitivityWhere one more qualified person would improve coverage the most.
- bound and gapBound and gap per planning run, stored with the run.
- recordData version, model version, who reviewed the model and who released the plan.
bring us this decision.
Bring one recurring resource allocation decision with its rules and data. Your planners get a first model they can read.
- Results
- Plan, binding limit, sensitivity, bound and gap, record
- Data centres
- Operated in Germany, or in yours
- all problem types
- routes, schedules, stock and price
- Contact
- hello@kint.pro