A battery model with boundaries
Configure power, energy capacity, SoC window, efficiency, C-rate and directional power limits.
Invalid combinations are rejected at input.
Battery storage and BESS ROI
Connect battery power, capacity and dispatch with client data, grid limits, tariffs and financial assumptions.
Battery model, energy flows and financial assumptions connected
The problem
Dispatch, usable SoC window, losses, degradation and replacement together determine what the battery actually does.
The solution
Configure the BESS, simulate energy flows and connect investment, maintenance and replacement assumptions to the outcome.
From data sheet to business case
Configure the BESS, simulate energy flows and connect investment, maintenance and replacement assumptions to the outcome.
Configure power, energy capacity, SoC window, efficiency, C-rate and directional power limits.
Invalid combinations are rejected at input.Track charging, discharging, conversion loss, standby loss and stored energy on the project timeline.
The energy balance remains traceable by interval and year.Test multiple kW and kWh configurations and assess the resulting energy and peak outcomes.
A sizing result can only be applied to its unchanged source configuration.Include CAPEX, OPEX, lifetime, degradation and replacement assumptions in the financial view.
NPV and payback follow from project inputs and are not guaranteed.Every conclusion remains attached to the resolution, limits and inputs that determine it.
Power in kW and energy capacity in kWh.
Initial, minimum and maximum state of charge.
Battery flows follow the canonical interval timeline.
How it works
Import load and generation and configure the connection, contract and tariffs.
Enter kW, kWh, SoC, efficiency and financial assumptions.
Assess dispatch, peak demand, cash flows, NPV and payback per variant.
Illustrative decision case
An adviser evaluates battery storage for self-consumption and a lower import peak for a fictional client with PV.
In the scenario
What becomes visible
Additional energy capacity only creates value when the profile and power window can actually use it.
Decision direction
Compare smaller and larger variants using equal dispatch and financial assumptions before selecting a preferred configuration.
This is a fictional example, not a customer result, quote or return guarantee. Actual outcomes depend on data, tariffs and assumptions.Read next
A practical guide connected to this decision.
Explore the knowledge baseFAQ
kW is charging and discharging power. kWh is the amount of energy the battery can store. Both constrain dispatch and must be configured separately.
No. PeakPilot can compare configurations and sizing rules, but the preferred variant depends on the objective, source data, technical limits and financial assumptions.
The battery model supports charging and discharging efficiency, standby loss and annual degradation. Use project-specific values from technical documentation.
You can review the relevant energy and peak outcomes side by side. Keep the dispatch objective and scenario assumptions explicit so the comparison remains traceable.
Define lifetime and replacement cost per kWh in the financial assumptions. PeakPilot can derive replacement events within the project lifetime.
No. It is a model estimate based on entered costs, tariffs, performance and lifetime. Always verify investment and contract terms.
Compare battery variants using the same client data and financial assumptions.
Start a free simulation