MV-RS CS import task
The MV-RS CS Import task allows you to import reading data from MV-RS systems into IEE.
Note: The MV-RS file format does not currently provide a field for Premise information. Only Account is available. If you use MV-RS, create customer configuration against Accounts rather than Premises.
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:
Use EBCDIC Files
Determines whether to use Extended Binary Coded Decimal Interchange Code (EBCDIC) for import or export task templates. EBCDIC is an 8-bit character encoding used on IBM mainframes and AS/400s. Select True to use EBCDIC files. Select False to exclude EBCDIC files.
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.
External System
Defines any external system to which IEE configuration data can be associated. In many places this parameter provides you with the dropdown menu to select from the external systems configured in the External System table.
Backup File
Defines the file path to a directory where IEE creates a backup file of the readings as it imports them to the database. Enter the directory path where IEE writes the backup reading files.
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.
Log File
Defines the file path and filename where IEE creates transaction logs. In task templates, enter the path to the directory where you want the task to place transaction logs.
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.
Custom Field Mapping Group
Defines mapping groups, which are useful if you have multiple Integrator or PremierPlus4 systems. You can create a custom field mapping for each system by creating a new mapping group. Import files have key fields in them, such as AccountNumber, RouteID, PremiseNumber, MeterNumber, and RegisterNumber. In a flat-file import such as PremierPlus4 or Integrator, these fields should appear in a specific place in the import file. Sometimes the IDs are not filled-in or are placed in a different location. IEE supports mapping those fields.
Click Edit to open the dialog box and modify the mappings.
Owner of Import Tasks
Defines the user ID associated with a task. By default, this field populates with the user currently logged into IEE.
Original Task Object ID
The original object ID for the task, if different. You may ignore this field. It is deprecated in IEE.
Create Missing Configuration
Determines whether IEE creates configuration objects and object relationships for the incoming meter data. Select True to create configuration data during the import. Select False to disable this setting. When the meter data file arrives, IEE checks it against the database. If configuration objects do not already exist, or if the configuration objects changed, IEE creates the configuration data during the import. If the configuration data already exists in the database, IEE only imports the meter data. Task templates that include the Create Missing Configuration parameter also include Parameters for Creating Missing Configuration, where you define the configuration data to create.
Trigger Data Driven Schedules
Determines whether the task is eligible for triggering data-driven schedules. Set to False if you do not want import tasks based on this task template to trigger data-driven schedules, even if the data being imported would normally trigger one or more data-driven schedules.
Parameters for Creating Missing Configuration
Defines the configuration parameters if the Create Missing Configuration parameter is set to True. For more information, see Creating missing configuration from import task template.