talk to usPlans for the decisions grid operators face, for example redispatch, maintenance outages and field crews. kint states which limit binds. Flexibility portfolios bid across markets on the same engine.
It is early afternoon. Cloud cover cuts solar infeed, wind picks up in the north, demand rises in the south. Storage, generation, grid limits and market positions all interact, and the plan has to change now. Every storage decision also changes what is possible in the hours after it.
Solar and wind change faster than a manual plan can follow. Forecast errors become imbalance.
Day-ahead, intraday, FCR and aFRR draw on the same battery. Solving one market at a time leaves capacity on the table.
Charging now limits what is possible later. Each storage decision affects the hours that follow.
Grid codes, emission caps and reserve requirements enter the model as constraints, so no plan breaks them.
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 redispatch measures relieve a congested line at the lowest cost, while supply stays secure?
Measures per asset and hour, the binding grid limit, and bound and gap.
All lines are checked at once, so relieving one congestion does not create the next.
When does each line, transformer or plant go offline for maintenance with the least impact on supply?
Outage windows per asset, matched to crews, spare parts and seasonal demand.
Lead times for spare parts and crew availability are part of the model, not a note beside it.
How do batteries and flexible loads split their capacity across day-ahead, intraday, FCR and aFRR?
A bid schedule per market and hour within state of charge and cycle limits, with a record per bid.
When the forecast changes, kint re-solves from the current state of charge and the commitments already made.
Which crew takes which job across the service regions?
Assignments per crew with routes, matched skills and an emergency reserve.
Travel time is minimized across all crews together, not one crew at a time.
The people stay the same. They work with a plan that states its own quality and its own reasons.
| Dimension | Today | With kint |
|---|---|---|
| Day-ahead plan | Hours by hand | Re-solved when a new forecast arrives |
| Markets | One at a time | Day-ahead, intraday, FCR and aFRR in one model |
| Compliance | Checked afterwards | Hard constraints in the model |
| Maintenance | By calendar | Placed where it costs the least supply |
| Reasoning | In the operator's head | Binding limit and a record per bid and measure |
Exports from your SCADA, EMS or VPP 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.
Assets, storage, forecasts, prices and weather, as read-only exports or via API.
Cost, emission targets, reserve requirements and grid rules, written down and reviewed.
kint returns the schedule and re-solves when forecasts or states change.
Operators see the plan and the reasoning and can override any decision. Overrides are recorded.
A conversation with kint's FDEs. Bring the decision and its rules, and get a first model planners can read.