# CC-KPI-M-11 Cooling offset by heating (24 h overlap)

> Cooling offset by heating (24 h overlap): expected value (reported; site-wide figure on the combined element). Consumer Connection KPI, Heatweb · reported. Monitoring points, threshold and calculation.

| | |
|---|---|
| Element | Consumer Connection (CC) |
| Standing | Heatweb · reported |
| Monitoring points | CC1 · 30 min · heat meter kWh; cooling meter kWh |
| Threshold | expected value (reported; site-wide figure on the combined element) |
| Calculation | Σ_d min(ΔE_heat,d, ΔE_cool,d) ÷ Σ_d ΔE_cool,d over the period's days |
| Period | Rolling 7 days; month |

Part of the **Meter health** family.

## Discuss this KPI

Is the threshold right? Does the calculation match what you compute on your networks? [Comment on CC-KPI-M-11](https://github.com/heatweb/HNQAP/issues/new?template=kpi-comment.yml&kpi=CC-KPI-M-11&title=CC-KPI-M-11%3A%20), or report how it behaves on your data. Comments are public and are read before every revision.

## Machine-readable

This KPI is a row of [kpi-reference.json](/data/kpi-reference.json) (element `CC`, code `CC-KPI-M-11`). The [notation and rules](/kpis/#how-to-read-the-tables) that apply to every KPI are on the reference page.

## Related KPIs on the consumer connection

- [CC-KPI-M-01 Meter reporting (not silent)](/kpis/cc-kpi-m-01/)
- [CC-KPI-M-02 Meter channel coverage](/kpis/cc-kpi-m-02/)
- [CC-KPI-M-03 Meter reading cadence](/kpis/cc-kpi-m-03/)
- [CC-KPI-M-04 Register integrity](/kpis/cc-kpi-m-04/)
- [CC-KPI-M-05 Plausible temperature difference](/kpis/cc-kpi-m-05/)
- [CC-KPI-M-06 Flow comes to rest (no constant flow)](/kpis/cc-kpi-m-06/)
- [CC-KPI-M-07 No low temperature difference at volume](/kpis/cc-kpi-m-07/)
- [CC-KPI-M-08 No simultaneous heating and cooling](/kpis/cc-kpi-m-08/)