LikeDayAlgorithm ETL task

The LikeDayAlgorithm ETL Task uses the Daily Reading Summary results to identify qualifying like days for various functions that require the averaging of historical readings values. LDA is used for demand response billing determinant calculations. Like days are determined by comparing 24-hour days, not by comparing individual intervals, whether interval data is imported through standard readings import (SRI) or AMI readings import (ARI).

In normal operations, the LDA ETL is scheduled to run on a recurring basis in incremental mode (Full ETL = False). When running in incremental mode, the LDA ETL will process readings since the last time the LDA ETL was run (high-water mark). Some use cases require manual intervention, for example:

  • The LDA task did not complete due to an error.

  • The LDA task was stopped due to outages or other operational issues.

  • One or more service point configurations were changed where the effective dates were prior to the last LDA ETL run.

  • New (historical) readings were imported for one or more service points, where the effective dates were prior to the last LDA ETL run.

The LDA task can be used to recover the following scenarios:

  • (Rare) Build entire ETL for a single service point.

  • (Rare) Build entire ETL for all service points (after a catastrophic event; will be slow).

The following table shows how task parameters are used to recover from different scenarios.

Table 41 Task parameters scenarios

Scenario

Full ETL

Start/End dates

Service point ID

Incrementally build ETL for a service point

False

Not Applicable

Required

Incrementally build ETL for all service points

False

Not Applicable

Blank

Build partial ETL for a service point and date range

True

Both Required

Required

Build partial ETL for all service points and date ranges

True

Both Required

Blank

Build entire ETL for a service point (rare)

True

Both Empty

Required

Build entire ETL for all service points (after a catastrophic event; will be slow)

True

Both Empty

Blank

Notes:  

  • When empty, the Start Date uses the System Settings > ETL > Like Day Algorithm ETL > Like Day Algorithm Baseline Start Date.

  • When empty, the End Date is basically the latest received time from the ReadingGroup table.

  • The LDA ETL high-water mark is associated to the task (not the task template IDs).

  • The LDA ETL high-water mark is updated when (a) building the ENTIRE ETL tables or (b) running incrementally on a recurring schedule.

  • The LDA ETL high-water mark is not updated when (a) processing a single Service Point, or (b) when rebuilding the ETL for a user-defined date range.

Use the following procedure to configure a task template:

  1. Go to System Operations > Task Management > Task Templates.

  2. Use the dropdown menu to select the Task Type and Task Template. (Click Add to create a new task template. For more information, see Adding task templates.)

  3. Configure the Task specific parameters. These parameters are defined after step 5 of this procedure.

  4. Configure the Common task template parameters. For more information, see Task template parameters.

  5. Click Save.

Task specific parameters:

ClosedFull ETL

ClosedStart Date

ClosedEnd Date

Defines the last day from which to include data in the task. To include the full 24 hours of the last day, the task will be scheduled with an adjusted End Date (that is, adding one day to the End Date entered in the task parameter).

ClosedService Point ID

Service Point for which a baseline must be generated. Enter a valid Service Point ID. The LDA ETL task supports only a single Service Point ID per task.