Integrator billing export
The Integrator Billing Export task allows you to request data from IEE for export to an Integrator-compatible external system, using the Integrator format.
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
Export Parameters
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.
Export Directory
Defines the directory where IEE places the file containing exported data. Accept the IEE default file path or click Search to browse to a directory. This parameter supports the standard IEE macros. Reference as ($ExportDirectory) when configuring a task. Exported data is generated by an export task template or an export API.
Export File Name
Defines the export file name. You can enter a unique file name or accept the default. This parameter supports the standard IEE macros.
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.
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.
Mapping
Estimated can't read code
Enter the code to use in the export file for estimated can't read values.
Failed can't read code
Defines the read code to use in the export file for failed can't read values.
No Match on External System Code
Defines the reading source for an export if the reading source is not set, or if the read did not enter IEE through the WorkCollection tables.
Force Complete Defaults
When IEE can't find a reading and it's time to bill, it uses the Force Complete parameters to determine the values to export.
Force Complete Can't Read Code
Defines the value that indicates why a meter couldn't be read. In an export task template, this setting defines the default value for IEE to use for meters that could not be read. IEE stores can't read codes in a code table, which you can update in the System Administration workbench. In IEE, this term is sometimes referred to as read code.
Force Complete Meter Reader ID
Enter the meter reader ID to use. Defines the ID code of a particular meter reader. In an export task template, enter a default value for IEE to use for the meter reader.
Force Complete Operator ID
Enter the operator ID value to use. Defines the operator ID. Enter a default value to use for the operator in the exported file.
Force Complete Save Reads
Defines the value that indicates why a meter couldn't be read. In an export task template, this setting defines the default value for IEE to use for meters that could not be read. IEE stores can't read codes in a code table, which you can update in the System Administration workbench. In IEE, this term is sometimes referred to as read code.
Force Complete Reading Value
Enter the reading value to use. Defines the actual meter reading. In an export task template, enter the value IEE uses as the reading value in an export for any meter for which IEE can't find a reading. Typically, this value is set to 0 (zero).
Generic bad can't read code
Enter the read code for IEE to use for invalid readings in the export file.
Generic good can't read code
Enter the read code used for valid readings in the export file.
Force Complete Routes
Defines the route to use. Enter the value or click Edit to use the Using the search utility dialog. A route or route element is a collection of service points that is read by mobile, handheld or fixed network collection systems on a specific schedule.
Force Complete Accounts
Enter the value or click Edit to use the Using the search utility dialog. The contractual relationship between a customer and one or more quantities delivered at one or more service points. An account is referred to by its account number or ID. Most billing systems use account numbers as the primary mechanism to track loads and revenues.
Tip: Click Edit to launch the Using the search utility dialog and find the specific route or account you want to use.
Valid Collection System for Must Read
A Find Best Read parameter for exports that specifies the collection system from which a read must originate in order to be considered a best read.
Create AMR Request for Contingency Reads
Determines whether the billing export creates contingency reading requests when writing a file, if no readings are detected and force complete conditions have not been met.
Find Best Read
Determines the read IEE retrieves when there are more than one best read. IEE follows the rules in the task template to determine which read to retrieve.
A billing system typically expects a particular set of can't read codes. When readings are collected by different systems, such as AMR and handhelds, the Can't Read codes don't always correspond. If the Can't Read code does not match the expected set, the export file uses the read codes specified in the task template.
Best Read Allow Edited or Estimated
Defines whether to allow edited or estimated readings. Use as a Find Best Read parameter for exports. In an export task template, select True to include readings that resulted from editing or estimating rather than actual meter reads. Select False to exclude these values.
Best Reading 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.
Best Read Status Required
Select Good to permit only valid reads in the export file. Select Any if the export can include invalid reads as well. Reading Status Required is a Find Best Read parameter for exports.
Best Reading Search Order
Select Earliest to instruct IEE to search for the best read starting with the earliest read and work forward to the most recent read. Select Latest to instruct IEE to start the search with the most-recent reading and work back to earlier readings. Reading Search Order is also referred to as a Find Best Read parameter for exports.
Best Read Earliest Time Allowed on First Day
Determines the time IEE starts looking for readings. IEE ignores any readings that arrived prior to this time on the Start Date of the batch that are included in this export.
Best Read Latest Time Allowed on Last Day
Enter the time that IEE should stop looking for readings. IEE ignores any readings that arrived after this time, on the end-date of the batch included in this export. The end-date is the critical read date for these readings.
Find Second-Best Read
Same as the Find best read section, but with the values adjusted for the next-best read. If IEE can't find a best read that meets all of the requirements specified in the task template, it looks for the next-best read.
Restrict Second-Best Rules to Critical Date
An export parameter that IEE to run "second-best" rules prior to the critical date. Best read rules can be applied to generate readings if IEE receives no readings from collection systems.