AMI monitor ETL task
The AMI Monitor ETL Task populates staging tables that build baseline reading import data and process new reading data after each execution. ARI administrators can check the status of the ETL to monitor ARI performance.
Run this task on a daily recurring schedule, after the ARI process completes. For more information, see Recurring schedules overview.
Use the following procedure to configure a task template:
-
Go to System Operations > Task Management > Task Templates.
-
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.)
-
Configure the Task specific parameters. These parameters are defined after step 5 of this procedure.
-
Configure the Common task template parameters. For more information, see Task template parameters.
-
Click Save.
Task specific parameters:
Full ETL
Defines whether the ETL task runs in full (True) or incremental (False) mode.
Caution: Do not set Full ETL to True except during initial system configuration or to perform a complete rebuild of the ETL tables. When set to True, define the Start Date parameter to prevent the ETL from re-running for readings already within the system.
Set to False for any task template that runs on a recurring basis. False indicates that the ETL runs in incremental mode. The ETL queries the ConfigChange table to identify service points that have changed since the last time the ETL ran. Only the readings created since the last execution of the task are added to the ETL tables (such as DailyReadingSummary and LikeDayAlgorithm).
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).