Entity: clientCalorificValue

Superseded by calorificValue. The client tier is no longer a table of its own: a calorific value has the same shape wherever it is stated, and the scope is a column rather than a separate entity. A row with no gauge set is what this page used to describe.

Two things changed with the consolidation, both required by the consumption calculation:

• Validity dates. This entity had none, so a corrected client value silently repriced every historical figure derived from it. Every scope is now dated, and a change recomputes the affected period instead.
• One resolver. Gauge, client and platform scopes now carry identical columns, so resolution is one rule — the most specific scope holding a value valid on the date being computed.

Emission factors keep their own entity, clientEmissionFactor; they are the same mechanism over different data, and consolidating them is not in this analysis's scope.

This page is kept so that older references resolve. See Calorific Value Management.