Meter Data Management and Service Order Management Related Enhancements

This section outlines meter data management, service order management, and smart grid gateway related enhancements introduced in this release of Oracle Utilities Customer to Meter, including:

• User Experience Enhancements

• Usage Calculation and Measurement Processing Enhancements

• Integration and Data Extract Enhancements

• Smart Grid Gateway Enhancements

User Experience Enhancements

This section describes the new and enhanced user experience features in this release, including:

• Operational Dashboard Filter

• Meter Health Check

Operational Dashboard Filter

In this release, the following zones on the Meter Operational Dashboard allow you to filter data by Division Code:

• 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

The new filter helps reduce clutter and irrelevant data in the dashboards.

Steps to Enable

To enable this feature, turn on Division Security in Master Configuration and set up the users' default divisions.

Meter Health Check

You can check the health of the system or monitor the state of the environment through accessing the different dimensions of meter data, such as the count of Initial Measurement Data records by:

• Status: Pending, Error, and so on

• Type: scalar and interval

• Counts, averages and total

You can collect a set of data points over time to track the health of environment regularly and take appropriate actions. The tool also enables you to export data or results in Microsoft Excel or in printed formatted.

Steps to Enable

To enable this feature, refer to the Configuring the Meter Health Check Dashboard section of the Oracle Utilities Customer to Meter Administrative User Guide for more information.

Usage Calculation and Measurement Processing Enhancements

This section describes the new and enhanced usage calculation and measurement processing features in this release, including:

• Initial Measurement Data Monitor Batch Controls

• Usage Calculation Rule - Demand at Service Point Level

• Usage Calculation Rule - Rolling Demand

• Updated Initiation for Measurement Reprocessing

• Non-final Initial Measurement Data Self-service Removal Tool

Initial Measurement Data Monitor Batch Controls

The following Initial Measurement Data (IMD) Monitor batch controls minimize performance issues when adding large numbers of historical or backlog readings. These use the IMD as the processing work unit instead of the Device Configuration. This prevents situations in which an error on an IMD rolls back processing for all of the IMDS for a given device configuration. These include:

• 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.

In addition, these batch controls provide more frequent commits that:

• Ensure consistent records per second processing

• Preserve process during a thread shut down

• Isolate failures to a single IMD

Steps to Enable

No steps are required to enable this feature.

Tips and Considerations

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.

Usage Calculation Rule - Demand at Service Point Level

The "Coincident Peak and Individual SP Demand" usage calculation rule enables you to determine demand at the service point level based on:

• Individual Service Points

• Coincident Peaks

• Time-of-Use (TOU) Coincident Peaks

Previously, demand was only calculated at the subscription level.

Steps to Enable

To enable this feature, refer to the Usage Calculation Rules section of the Oracle Utilities Customer to Meter Administrative User Guide for more information.

Usage Calculation Rule - Rolling Demand

The Rolling Demand usage calculation rule allows you to support meters that record intervals at one interval length (for example, a 15 minute interval) and tariffs that require demand values to be calculated at higher interval lengths (for example, 30 minute intervals). This allows you to bill rolling demand in a standardized way across various interval rates.

Steps to Enable

No steps are required to enable this feature.

Updated Initiation for Measurement Reprocessing

Measurement Reprocessing is initiated when install event dates change. Previously, measurement reprocessing was only initiated when the installation constant was changed. When the installation and removal dates expand to cover a longer time, this process checks for existing measurements that require a change in multiplier and reprocessing.

Steps to Enable

No steps are required to enable this feature.

Non-final Initial Measurement Data Self-service Removal Tool

You can identify and remove unnecessary Initial Measurement Data (IMDs) in "non-final" status with a self-service tool that enables you to filter IMDs by date range, business object, business object status, and device configuration. This allows you to perform quick data cleanup and reduces manual record deletion.

Steps to Enable

No steps are required to enable this feature.

Integration and Data Extract Enhancements

This section describes the new and enhanced integration and data extract features in this release, including:

• DataConnect Interval AMI Extract - Additional Data

• Measurement and Initial Measurement Data Header Extract-related Batch Processes

DataConnect Interval AMI Extract - Additional Data

The "Interval AMI" DataConnect data extracts now include the following data:

• Service Quantity Identifier

• Time of Use

• Service Type

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

These extracts can be used for Opower integration or as integration to other energy management systems. These provide more detailed interval data extracts. It also reduces project cost and configuration time.

Steps to Enable

To enable this feature, refer to the Defining DataConnect Options section of the Oracle Utilities Customer to Meter Administrative User Guide for more information.

Measurement and Initial Measurement Data Header Extract-related Batch Processes

These batch controls streamline the initial export of Measurement data and Initial Measurement Data (IMD) header data:

• 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

Additionally, you can extend the default SQL Timeout value (900 seconds) of the Specialized IMD Header Extract Current (D1-SIMDC) or Specialized Measurement Extract Current (D1-SMDECS) batch control with the "Override SQL Timeout" parameter.

Steps to Enable

No steps are required to enable this feature.

Smart Grid Gateway Enhancements

This section describes the new and enhanced smart grid gateway features in this release, including:

• Generic Common Information Model (CIM) Adapter

• Unit of Measure Filtering for On-Demand Reads

• Generic CIM AMI Adapter - On-Demand Read and Device Status Check Commands

Generic Common Information Model (CIM) Adapter

The Adapter Development Kit provides you with Common Information Model (CIM) IEC 61968-9, Edition 2.0 interfaces for file-based processing of usage and events, and a real time interface for events.

This provides productized CIM file-based processing of usage and events, and a real-time interface for events. It also reduces project time and costs when working with CIM head-end systems.

Steps To Enable

To enable this feature, complete these steps:

1. Add the ADK - Master Configuration and enter the details to support the real-time event interface.

2. Add a Usage and Events entries for the SGG Payload Processing Configuration extendable lookup to leverage the com.splwg.d1.domain.sgg.dg.processing.PayloadHandlerViaUserExits payload handler class.

3. Add two batch controls using D1-PLPRM (Payload Processing Monitor Template) and associate these with the appropriate SGG Paylaod Processing Configuration extendable lookup values.

4. Update the ADK - UOM Code to Standard UOM mapping extendable lookup with the mapping for the ReadingType values. These should map to UOM, TOU, and SQI where applicable.

5. Update the ADK - Device Event Mapping extendable lookup with configuration for the event types that will be processed.

6. Add an entry to the File Storage Configuration extendable lookup indicating where the real-time event processing will store and receive files.

7. Create a head end system with the appropriate processing roles to process initial measurement data and events.

Unit of Measure Filtering for On-Demand Reads

The application provides Unit of Measure (UOM) filtering for on-demand read commands for the following Smart Grid Gateway adapters:

• Landis+Gyr

• Itron AMM (formerly Silver Springs Networks)

• Adapter Development Kit

These UOM filters minimize IMD Seeder errors on devices where UOMs are not configured as measuring components.

Steps to Enable

No steps are required to enable this feature.

Generic CIM AMI Adapter - On-Demand Read and Device Status Check Commands

In this release, the Adapter Development Kit includes on-demand read and device status check commands based on the Common Information Model (CIM) IEC 61968-9, Edition 2.0 standard. This provides support for the CIM standard and a framework for other commands. It also reduces project time and costs when working with CIM head-end systems.

Steps To Enable

To enable this feature, refer to the Adapter Development Kit - Common Information Model Commands section of the Oracle Utilities Smart Grid Gateway Administrative Guide for more information.