Optimize battery value without bypassing site safety.
Battery dispatch is more than choosing when to charge or discharge. A dependable workflow links forecasts, commercial objectives, equipment constraints, approvals, execution evidence, and settlement.
The five-stage dispatch evidence loop
KUNIES structures battery orchestration as Forecast, Commit, Dispatch, Perform, and Settle. Each stage produces evidence for the next, allowing owners to compare planned value with delivered and settled value.
- Forecast available solar, load, price, and battery capability
- Commit a schedule that respects commercial and operating constraints
- Dispatch only after identity, permission, limit, and approval checks
- Verify acknowledgement and physical asset response
- Reconcile performance with settlement and attributed revenue
Local controllers retain final authority
Cloud analytics can recommend and coordinate a portfolio plan, but the site EMS, PPC, BMS, and protection systems must retain authority over safe equipment operation. If communication, identity, validity, or acknowledgement is uncertain, the control path should fail safely.
Optimization objectives depend on the asset
A battery may support time-of-use management, peak shaving, solar firming, contract compliance, market participation, or several objectives together. The optimization model should expose the objective, constraint set, forecast version, and trade-offs instead of presenting an unexplained command.
Revenue attribution requires settlement evidence
A dispatch recommendation is not proof of value. Owners need the approved schedule, command, acknowledgement, telemetry, baseline, price or tariff logic, and settlement record. This evidence determines whether a claimed improvement is attributable and repeatable.