AMI contingency read imports
Use the AMI Contingency Read Imports task template to set the parameters for importing contingency reads into IEE.
IEE imports contingency reads immediately upon receiving the request, even if the reads fall within the normal AMI readings import window. IEE does not wait to import the contingency read with other reads.
When multiple register reads that map to the same service point channel are received, IEE saves only the first register read. Any succeeding register reads are ignored. This prevents duplicate reads from causing causing database errors when saving readings for gap fill interrogations and contingency read requests.
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:
Processing Chunk Size
Defines the number of configuration entities processed by sub-tasks. IEE groups the data that was processed by the task into separate batches of the size you designate here. IEE considers the task completed when all child tasks are finished, and each has reported back to the parent tasks.
Chunk size is a parameter common to several task templates. The higher the chunk size value, the greater the portion of the total available work each IEE task runner performs. A smaller value means dividing the work between more concurrent task runners.
Chunk sizes that are too large overburden a few task runners, while other task runners sit idle. In extreme cases, overly large chunk sizes could result in system failure due to lack of available, allocated memory. Chunk sizes that are too small spawn many task runners that perform more initialization and shutdown than actual work. Both large and small extremes will cause delays in export processing.
When fine tuning chunk sizes, consider database resources, hardware requirements, daily processing levels, and processing windows. Adjust values over time, as hardware and networking conditions change.
Import Directory
Defines the folder that IEE monitors for incoming files. IEE automatically schedules files that arrive in this directory for import. You define the paths to default import directories in the IEE System Administration workbench. When configuring the import directory parameter in an import task template, enter the file path to the directory that IEE monitors for import files specific to this task. This parameter supports standard IEE macros. Reference as ($ImportDirectory) when configuring a task.
File Mask
Defines a file extension or a partial file name that IEE uses to monitor import directories and create export files. Enter a file mask such as .xml when configuring an import or export task template. When a file arrives in the import directory, IEE automatically schedules the file for import if it matches the mask. IEE ignores files that do not match the file mask. When creating an export file, IEE appends this mask to the file name.
Owner of Import Tasks
Defines the user ID associated with a task. By default, this field populates with the user currently logged into IEE.