• Incomplete IMDs by Status

• Incomplete IMDs Trend

• VEE To Dos by Exception Type

• VEE To Dos Trend

• Usage Transaction by Status

• Usage Transaction Trend

• Usage Transaction To Dos by Exception

• Usage Transaction To Dos Trend

• Status: Pending, Error, and so on

• Type: scalar and interval

• Counts, averages and total

• D1-IMDV2 (IMD Monitor - Physical Devices V2): used to process initial measurements related to physical devices.

• D1-IMDD2 (IMD Monitor - Deferred IMDs V2): used to process previously held or deferred IMDs.

• D1-IMDM2 (IMD Monitor - Unattached MCs V2): used to process IMDs for standalone measuring components without a Device Configuration such as weather or price data.

• Ensure consistent records per second processing

• Preserve process during a thread shut down

• Isolate failures to a single IMD

• The D1-IMDV2 batch control invokes monitoring rules associated with the current state of an Initial Measurement Data (IMD). All monitoring rules throughout the IMD's business object's inheritance chain are considered.

• The D1-IMDV2 batch parameters govern whether the processing is further restricted by batch code, business object, status, and so on.

• The D1-IMDV2 batch process is based on the standard monitor process. However, it does not need to be plugged in on a state of the IMD business objects as a "Monitor Process". You do not need to change your IMD business objects to reference this new batch control.

• The D1-IMDV2 batch parameter "runAsBatchCode" can be used to process records where the current status is governed by "Run as Batch Control" when the parameter is not plugged in as a Monitor Process. For example, if there is an IMD in PENDING where the BO status is configured with a "Monitor Process" of D1-IMD then setting the "Run as Batch Control" to D1-IMD will allow this batch control to transition that record.

• The D1-IMDV2 batch control processes all IMDs for a Measurement Component up to and including that limit and each additional IMD will be held if the optional parameter for Measuring Component IMD Limit is configured. For the held IMDs, there are some optional behaviors:

• A To Do entry can be created for each Measurement Component with more than the configured limit of IMDs. Note that only one To Do entry per Measurement Component is created even if there is more than one IMD over the limit.

• The IMDs over the limit can be transitioned to a new status to remove these from the normal processing flow. This ensures these are not picked up on a subsequent run of the D1-IMDV2 batch control and that these must be processed using the D1-IMDD2 batch control.

• Individual Service Points

• Coincident Peaks

• Time-of-Use (TOU) Coincident Peaks

• Service Quantity Identifier

• Time of Use

• Service Type

• Device Id (meter number (customer-facing))

• Specialized IMD Header Initial Extract (D1-SIMDI) - Extracts IMD headers of IMDs whose "To" date/time are later than the Start Date/Time and equal or earlier than the End Date/Time

• Specialized Measurement Initial Extract (D1-SMDIE) - Extracts measurements whose Measurement date/time are later than the Start Date/Time and equal or earlier than the End Date/Time.