Stale data detection process

The Stale Data Detection Process task template is not an export task in itself. Use this task template to define how IEE identifies stale data.

Note: This task takes time to run. Run it no more than once or twice a day.

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:

• Filter by Entity

  Entity Type

  Defines the entity that IEE builds the export file or report around. Entity type supports all main configuration entities. The valid values are as follows.

  • service point

  • account

  • meter

  • data routing program

  • monitoring data program

  In a task template, select the entity type from the dropdown menu and click Search to find the specific ID. Click the appropriate row in the search results and click OK to add the ID to the task template.

  Service 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.

• Filter by Date Range

  Time Period

  Defines the time span of the data to include in the task for exports, reports, and other tasks. Some common time periods include: Today, Yesterday, Month, Month to Date, Week, Week to Date, Year, and Year to Date.

  Start Date

  Defines the first day from which to include data in the task.

  Tip: Defines the date to start the baseline calculation. Use this parameter to indicate how far back your baseline is needed. Typically, this is the first day of operation or recovery period. If this value is not properly set, it may default to the beginning of time, and Like Days may calculate as far back as historic data is available. This will overwhelm the LikeDayAlgorithmDate table and lead to slower processing.

  End 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).

• Filter by

  Billing System Cycle ID

  Defines the unique identifier of the billing system cycle associated with the entity type. Billing cycles enable prioritization by billing due dates. The valid values are as follows. Allow Overrides, Valid ScheduleID Only, and Override Default.

  Schedule ID

  Defines the unique schedule ID. When you Schedules, you assign a unique ID. Schedules start all tasks simultaneously, not sequentially. Tasks that don't require data can start right away; other tasks might first interrogate the database, discover a lack of required data, and wait until that data arrives before running.

  Readings Source

  Determines which read to include in the export file if IEE finds reads from two different collection systems for the same meter. Reading Source is a Find Best Read parameter for exports.

  Task Template

  Defines the task template. Every IEE task is based on a task template that defines the parameters required to run the task. The task templates are based on task types. You can create several templates with task-specific parameters for each task type. You cannot change the task types.

  Start Offset (Days)

  Defines a time-period of data to include in this task occurrence. Enter the number of days of which to offset the data from the last occurrence using whole numbers. For example, to run the task against data starting five days after the last occurrence until today, enter 5.

  Any data that IEE received prior to this offset window is not considered stale.