Use case · municipal utilities

every main, every tour.
the budget spent where it counts.

Water, heat, power and waste share one question: which assets to renew, which tours to drive, which crew takes which job. kint answers it within the budget and the rules, with the record for council and regulator.

renewal · this yearone budget, many mains
The situation

one budget. many mains. a choice to defend.

The renewal budget for the year is set. Hundreds of pipe sections, cables and stations compete for it, each with its own age, failure history and impact on residents. Road works should be bundled with other utilities, and the crews are the same ones who answer emergencies. The list that comes out has to hold up in the council meeting.

risk and budget pull apart

The riskiest assets are not always the cheapest to renew. Ranking by age alone spends the budget in the wrong places.

works should be bundled

Opening a road once for water, heat and power saves money and disruption. Planning each network on its own misses it.

crews serve two masters

The same teams do planned work and emergencies. A plan without a reserve fails at the first burst main.

public money needs a record

Council and regulator ask why this section and not that one. The answer has to come with its data and rules.

The decisions

what teams bring to kint.

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.

01 · asset renewalWhich mains, cables and stations do we renew this year within the budget, ranked by failure risk and impact on residents?
Returns

A renewal programme by quarter, with the budget or crew limit that binds.

Works on the same street are bundled across water, heat and power where it saves cost and disruption.

problem type · resource allocation

02 · waste collection toursWhich vehicle empties which containers on which day, within time windows and vehicle limits?
Returns

Tours per vehicle and day with stop order, the binding constraint, and bound and gap.

Changes to collection days or new districts are re-solved across all tours, not patched one by one.

problem type · vehicle routing

03 · field service crewsWhich crew takes which job this week, so planned work gets done and emergency cover holds?
Returns

Assignments per crew with skills matched and a reserve for emergencies.

Working-time rules and on-call duties are hard constraints.

problem type · workforce scheduling

What changes

today, and with kint.

The people stay the same. They work with a plan that states its own quality and its own reasons.

DimensionTodayWith kint
Renewal listRanked by age and experienceSelected within budget by risk and impact
BundlingAgreed in meetingsShared works across networks in the model
CrewsPlanned per departmentOne plan with an emergency reserve kept
RecordSlides for the councilData, model and release stored per plan
How it runs

four steps to the first plan.

Exports from your GIS, asset management 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.

01

connect asset and service data

GIS layers, asset registers, failure history, tours and crew lists, as read-only exports.

02

describe the rules

Budget, risk criteria, bundling rules and working-time limits, stated by the asset and service teams. The agent writes them down for review.

03

solve and compare

The programme next to today's list, with the binding limit and bound and gap stated.

04

release and record

A person releases the plan. The record keeps data, model version and release for council and regulator.

Questions

what teams ask first.

Is there a flagship for municipal utilities?
No packaged flagship covers municipal utilities. The same engine, the same record and the same five stages are set up with your team on the platform.
Can kint use our GIS and asset register?
Yes. Data comes in as read-only exports. Approved plans go back only through an API you control; your systems decide whether to apply them.
Who checks the model?
Asset and service teams review each rule in their own words. In the pilot, kint's FDEs review the model with your experts.
Where does the data run?
kint is hosted in Germany and operates the platform itself. The setup is documented per engagement.

spend the renewal budget on the record.

A conversation with kint's FDEs. Bring the decision and its rules, and get a first model planners can read.

Industry
municipal utilities
Works with
GIS · asset management · ERP
Runs on
the platform
Contact
hello@kint.pro