Configuring miscellaneous system settings

  1. Go to System Administration > System Admin > System Settings.

  2. From the Section dropdown menu, select Miscellaneous.

  3. Configure the following parameters:

  4. Click Save.

Aggregation

Net Aggregation Chunk Size

Defines the number of channels to process as one batch during net aggregation. Select zero to disable chunking. This setting splits the channels associated with a net formula into manageable chunks. Setting the value too high can result in database timeouts or lag.

The IEE installer populates many of these parameters with default values. The default value might not be the recommended or optimal setting for your specific IEE implementation. You must tune these values to achieve optimal system performance.

Days to Search for Historical Reads

Defines the number of days from the current time stamp to look back to find historical readings. This value limits the search to readings with end times within the last n days. IEE ignores reads older than the entered value. To disable this setting and search for all historical reads enter a value of zero.

Australian Market

Australian Market Inactive Meter Rule

Determines whether IEE uses the special assignment of reading status codes based on the meter’s status code, effective for each meter version. The default value is False. Select True to enable this parameter.

Enhanced Reading XML Import Enhanced Reading XML Processing Size

Defines the chunking size of the interaction with the database. This controls the size of the interaction with the database. The default chunk size is 100 and the maximum chunk size is 500.

You must tune this value to achieve optimal system performance. For example, depending on your implementation, automatically selecting the maximum size without testing your system may cause your system to run the process out of memory or overtax your database.

Use this setting in conjunction with the Enhanced Reading XML Threads parameter. Together, these settings affect the Reading Import XML Enhanced task type.

Enhanced Reading XML Threads

Defines the number of threads the import process can use. The default thread count is 7 and the maximum thread count is 50.

Tune this value to achieve optimal system performance. For example, depending on your implementation, automatically selecting the maximum size without testing your system can cause your system to run the process out of memory or overtax the database.

Use this setting together with the Enhanced Reading XML Processing Size parameter. Together, these settings affect the Reading Import XML Enhanced task type.

Import Fail Queue

Create Import Fail Queue Items

Determines whether to create Import Fail Queue items while importing readings. The import fail queue items are typically created when the channels specified in the import file are not found in IEE. The Import Fail Queue is primarily a diagnostic tool to help you identify problems arising when importing readings. Setting the value to True can reduce performance and increase the growth of the database tables that populate the user interface. If you are not using this tool, set the value to False.

Provisioning

Provisioning Maximum Retry Threads

Defines the maximum number for the Saturne Provisioning Service to use to concurrently send retry messages to an external system. Increasing the number of threads increases memory usage, which reduces the time spent sending messages. The capability of the external system receiving the message can limit the number of threads that you can use.

Provisioning Retry Frequency in Minutes

Defines the number of minutes to wait before the Saturne Provisioning Retry Service attempts to send updates to an external system when the attempt to send the initial message failed. IEE waits this amount of minutes before attempting to resend the initial message. You can increase this setting to accommodate prolonged or systemic network performance problems.

Provisioning Retry Timeout in Minutes

Defines the number of minutes that the Saturne Provisioning Retry Service spends attempting to send updates to an external system when the attempt to send the initial message failed. Use this setting to control when the Saturne Provisioning Retry Service stops attempting to send updates to an external system. You can increase this setting to accommodate prolonged or systemic network performance problems.

Reading Purge by Partition

Reading Purge By Partition Batch Size

Defines the number of reading group service point channel rows that are processed in each iteration of the reading purge by partition operation.

Reading Purge By Partition Days To Keep

Defines the number of days after which readings are considered historic by the reading purge by partition operation. Readings older than this number of days are eligible for removal.

Reading Purge By Partition Time To Run (in minutes)

Defines the length of time the reading purge by partition operation runs. Use this setting to limit the operation to a particular window of time.

Reading Purge by Partition History

Enables users to purge historical readings prior to the retention settings date (MinRGSPCDatePurged).

Important! To hold the historical reading on the partitioned tables, there must be at least one empty truncated partition (without dropping it) below the MinRGSPCDatePurged date.

Reading_PurgeByPartition_Hist performs the following actions:

  • Checks to see if the min (EndTime) for RegisterReading and ReadingGroupSPC is v_MinInterimDate.

  • Cross-checks to see if the v_MinInterimDate with MinRGSPCDatePurged (v_PurgeDate) has already been purged.

    • Historical readings will not be available to purge if the v_MinInterimDate is greater than the high-water mark of the oldest partition for RegisterReading or ReadingGroupSPC.

    • Historical readings will be available to purge if the v_MinInterimDate is less than the high-water mark of the oldest partition for RegisterReading or ReadingGroupSPC.

    • v_PurgeDate is used as the purge date to truncate the partitions and delete the dependent tables.

      • Truncation of a partition only occurs when the v_PurgeDate is greater than the high_value of the partition.

      • On schedule <> 1, truncation of a partition will not occur, but the records from the main table and all dependent tables are deleted based on the purge date (v_PurgeDate).

  • Truncates the following tables when the high_value is less than the Purge Date (v_PurgeDate):

    • Truncate Reading Table

    • Truncate RegisterReading Table

    • Truncate ReadingGroupSPC Table

  • Deletes the records from the following tables for the purge period (up to the purge date, v_PurgeDate):

    • ValidationLogDetail

    • ValidationQueueUpdateTodo

    • ValidationLog

    • ReadingCreationEditLog

    • ReadingEditLog

    • ExportFileHistory

    • ExportHistory

    • ReadingPeriodWithStatusID

    • EstimationLogdetail

    • SettlementHistory

    • ReadingGroup

Note: Data in the ReadingGroup table is deleted after the data is deleted in the other child tables: ReadingGroupSPC, RegisterReading, ExportHistory, and SettlementHistory.

Use the following query to run Reading_PurgeByPartition_Hist for Oracle:

DECLARE

BATCHSIZE NUMBER;

TASKID NUMBER;

SCHEDULED NUMBER;

BEGIN

BATCHSIZE := 1;

TASKID := NULL;

SCHEDULED := 1;

READING_PURGEBYPARTITION_HIST

(

BATCHSIZE => BATCHSIZE,

TASKID => TASKID,

SCHEDULED => SCHEDULED

);

END;

Use the following query to run Reading_PurgeByPartition_Hist for SQL Server:

USE [ItronEE]

GO

DECLARE @return_value int

EXEC @return_value = [dbo].[Reading_PurgeByPartition_Hist]

@BatchSize = 1,

@TaskId = NULL,

@Scheduled = 1

SELECT 'Return Value' = @return_value

GO