Simulator
From the meter file to the payback, one checked step at a time.
The Simulator reads the site's own year of meter data, rebuilds the bill under a versioned tariff, tries battery sizes against it and prices the result. Every saving it reports is computed by its own bill engine.
Data check
Interval length, units and time zone read from the fileGaps, duplicates and daylight-saving shifts found and listedkW mixed up with kWh, and spikes, flaggedAn exception report: fill, keep or leave out, your choice
Bill reconstruction
Tariffs are versioned, each with its source and the date it was readThe bill is rebuilt from the meter data, component by componentSet against the real bill, so a mismatch shows before the study goes on
Solar
Solar already on the site shows in the meter data: its surplus charges the batteryA modelled solar year for the site's location and system (PVGIS), for planned panels
Battery dispatch
Rule-based dispatch, the way a site controller runsOptimal dispatch (linear programming) as the upper bound, and how much of it the rule-based case capturesConnection-limit mode: the smallest battery that keeps the site under a fixed kW limit after a new load, such as EV chargers or a heat pump
Financials
Capex, opex and degradationNPV, IRR and simple paybackAgeing re-billed at 80 % and 60 % capacity, with a replacement at end of life
Where the battery case comes from
It differs by country, so the default scenario follows the site's country.
- Germany
- Peak-charge savings and solar self-consumption.
- Netherlands
- Growing within a grid connection that can't be enlarged: EV chargers, heat pumps, more production. Savings come second.
- Romania
- Solar self-consumption, price spreads and grants.
- Elsewhere
- Peak shaving and self-consumption, with the site's own tariff.
Feasibility estimates, not bankable guarantees or investment advice. Zorowatt does not control batteries. Disclaimer