Force Derivation of Interval Data

Derivation algorithms base their calculations on data from other profiles, classic TOU maps, registers, bill factors, contract options and so on. These may be referred to as the algorithms' source data.

Ideally, derivation algorithms should be able to detect changes made to their source data since the last derivation and re-derive values for the relevant periods if any changes are detected. Refer to Using the Latest Updates to Source Data for more information.

As long as the source data has means of recording changes (e.g. an update date/time stamped on the new records), the algorithm can detect the changes and trigger re-derivation. However, not all objects in the system have this recording mechanism, making automatic detection of changes for re-derivation impossible.

Consider the sample derivation algorithm in Preventing Gaps in Data. This algorithm used a bill factor to apply a constant to the source curve to arrive at a derived curve. Imagine that the users discover that the bill factor value was incorrect and that once this value is fixed, the data needs to be re-derived. The algorithms have no way of knowing that this bill factor has changed. In such cases, the user may run derivation and specify a period for which to force derivation, so that re-derivation with new values may take place. Refer to the background processes Process IB-SPDB - SA Interval Profile Data Creation and Process IB-STDB - SA TOU Data Creation for information about running derivation through batch. Refer to Service Agreement - Interval Info for information about running derivation online.