For planning teams without an OR department

your planners know the rules.
we write the math.

Some planning is too complex for a spreadsheet, and the company too lean for an operations research group. Planners explain the decision in their own words. kint's decision agent and forward deployed engineers (FDEs), engineers who work directly with the planners, turn it into a model. The team keeps deciding.

how a rule becomes math

“an order never goes on two trucks.”

  1. saidby your plannerIn the words the team already uses.
  2. written∀o: Σt xo,t = 1As a constraint in the model, which the planner can read back.
What changes

same team. better options.

Your planners stay the experts. The difference is what they work with.

Today
With kint
A spreadsheet that only one person understands
A model the whole team can read and review
One plan, built by hand on Friday afternoon
The best plan the solver finds within your rules, with its gap
“What if?” means a second weekend
Scenarios compared on the same model
Nobody can say why the plan looks like this
The limit that binds the plan, in plain language
Who builds the model

three parties. one model.

Your planners

know the operation

They explain the goal, the rules and the exceptions, the way they would explain them to a new colleague. They check every model before it runs.

  • describe the decision
  • review the rules the agent wrote down
  • release or reject each plan
The agent

writes the model

It turns plain language into rule cards, then into an optimization model. It asks when something is unclear, and a person on your team releases each plan.

  • rule cards for review
  • a generated, versioned model
  • scenarios on request
kint's FDEs

checks the math

In the pilot, a team of FDEs builds the one decision with the planners and reviews the model with them. They make sure the model is right and the results hold, so the checking is covered without an in-house OR group. In production, FDEs build the first workflows and join again for each new decision.

  • model review in the pilot
  • solver choice and tuning
  • a direct line to kint's FDEs
Typical decisions

the plans your team makes every week.

the plans your team makes every week.
DecisionThe question kint answersProblem type
shifts and machinesRosters with rest periods and qualifications. Jobs with setup times and due dates.Which order of jobs meets every due date with the fewest changeovers?production scheduling
tours and service callsVehicles, time windows, capacity limits, drivers with their own rules.Which tours cover all stops in their time windows with the fewest kilometres?vehicle routing
material and budgetLimited resources, many demands: raw material across lines, budget across projects.Which split of material across lines produces the most with the least waste?resource allocation
Getting started

one decision first.

A pilot on one decision, with your data, measured against how you plan today. If kint cannot improve on it, you will hear that from us first. The pilot runs through the five stages a kint decision goes through.

  1. connect data
    An export from the ERP or the spreadsheet you plan with today. Read-only, versioned.
  2. describe the decision
    Planners explain goal, rules and exceptions in their own words. The agent writes them down as rule cards for review.
  3. build the model
    The agent turns the reviewed rules into a model. kint's FDEs check it with your experts.
  4. compare scenarios
    kint's plans next to yours, on the same weeks. You see the difference and the reasons.
  5. decide with a record
    Each plan comes with its binding limit, bound and gap. You choose whether the workflow goes into daily use.

which plan costs your team the most time?

Tell us about it. A short call with kint's FDEs gives an honest answer on whether optimization helps.

You need
One decision and an export of the data behind it
kint brings
The agent, the solvers and engineers who review the model
Pricing
how engagements are structured
Contact
hello@kint.pro