Industrial Heat Pumps & Electrified Thermal Systems worked example
Thermal Storage Sizing at 17% storage loss and reserve allowance: a worked example
This scenario runs the thermal storage sizing calculation on the strong side: 17% storage loss and reserve allowance, with every other input held at its documented default. Use it when a process engineer or energy manager is sizing hot water tanks, buffer vessels, or thermal batteries for peak shaving, batch heating, or heat recovery smoothing.
The inputs for this scenario
- Average process heat load: 750 kW (unchanged)
- Required storage duration: 4 hr (unchanged)
- Storage loss and reserve allowance: 17 % (raised for this scenario; the documented default is 15)
Working through the calculation
- Applying the documented formula (Base thermal storage energy = average process heat load × required storage duration) to the inputs above produces each figure below.
- At this operating point the engine returns 3,000 kWh for energy used, the number this scenario is built around.
- At this operating point the engine returns 51,000 $ for energy cost.
- At this operating point the engine returns n/a $ / piece for cost per piece.
- At this operating point the engine returns 12,750 $ / hr for hourly cost.
How this compares with the baseline
- Against the tool's baseline example, where storage loss and reserve allowance sits at 15% and the headline result is 3,000 kWh, this scenario lands almost exactly on the baseline at 3,000 kWh.
- Use it when sizing a buffer or thermal store to shift heat pump operation to off-peak hours, bridge defrost or maintenance gaps, or cap peak electrical demand. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.
Results at a glance
- Energy used: 3,000 kWh (headline result)
- Energy cost: 51,000 $
- Cost per piece: n/a $ / piece
- Hourly cost: 12,750 $ / hr
Run it with your numbers
- Every input above is editable in the live Thermal Storage Sizing calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.