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

This section describes the new and enhanced batch processing features in this release, including:

Calculating consumption for subtractive scalar channels uses a more efficient "look back" algorithm to find a previous read, limiting the number of days searched.

This improves performance when processing scalar meter reads.

No steps are required to enable this feature.

The ILM Crawler - IMD (D1-IMDCL) batch control identifies and runs eligibility evaluation for Initial Measurement Data. In this release, D1-IMDCL extends its function to delete Control table records marked as "eligible for archive" from dropped Initial Measurement Data or Usage Transaction partitions.

This ensures the complete removal of orphaned Control table records from dropped Initial Measurement Data or Usage Transaction partitions.

No steps are required to enable this feature.

The following meter read extracts support file encryption:

This provides additional data security to specialized meter read extracts.

No steps are required to enable this feature.

To encrypt files, run specialized extract batch jobs with the Encryption Key Ring and Signature Key Ring parameters.

The Device Periodic Estimation (D1-DVCPE) batch control replaces the periodic estimation function of the Smart Meter Monitor (D1-SMMTR) batch control, which queries all active devices. D1-DVCPE only queries eligible devices whose measuring components are missing measurements based on the periodic estimation configuration. The records processed by the D1-DVCPE batch job count the the number of estimation Initial Measurement Data (IMDs) generated instead of the number of devices selected, providing an accurate representation of the amount of work performed by the batch job. In addition, periodic estimation algorithms now create estimation IMDs within a new session to break up the large estimation IMDs created for a device with multiple measuring components. The batch job commits IMDs upon completion, which improves processing speed and ensures that all the completed work is not lost when an error occurs in a single estimation instance.

This reduces run times and the required resources to fill gaps in readings.

To enable this feature, complete these steps:

In subsequent releases, the D1-DVCPE batch control will become the default process for periodic estimation. For this release, it is optional and it is recommended that you run a performance test on this tool.

The Clean Up Aggregation Group Runs (D1-AGGRC) batch control allows you to cancel, restart, or revert aggregation group runs. Previously, aggregation group runs were not editable.

The Clean up Aggregation Group (D1-CLAGP) batch control allows you to clear unwanted aggregation results such as measurements, measuring component set data, and aggregation runs at the aggregation group level and individual measuring component set level.

These batch controls include improved logging which allows you to easily identify errors and get better visibility during the aggregation run. For example, the logs include the Measuring Component Set Participant ID, which makes it easy to determine dimensional attributes.

In addition, the Aggregation Group portal now includes the Settlement Batch Run Statistics tab that displays status and key statistics for each batch run.

These updates make it easier to run aggregations, remove unwanted aggregation results, and resolve issues.

No steps are required to enable this feature.

The Aggregation Foundation Set (D1-AggregationFoundationSet) measuring component set business object now includes the following Load Distribution elements:

To enable this feature, complete these steps:

Gas utilities rely on the estimation process for forecasting and backcasting the retailer's aggregate consumption for each "Gas Day".

To enable this feature, specify the Anchor Time (the start and end time for the "Gas Day") on the appropriate aggregator measuring component type.

The start and end times for a "Gas Day" are defined using the Anchor Time field on dynamic aggregation measuring component types, standalone measuring component types, and profile measuring component types. When processing calculations for measuring components whose type specifies an Anchor Time, the Start Time and End Time of the calculation period should match the Anchor Time on the measuring component type.

You can now bill consumption on gas day with the Vector and Service Quantity Math usage rule. The following vector types have been added to process interval consumption for gas days:

The application passes the usage transaction's cutoff time as the anchor time for gas day and the time zone of the usage subscription after calling the Interval Period Helper and/or Axis Conversion from the usage rule.

Additionally, updates to Axis Conversion ensures the correct calculation of intervals when the curve straddles a time shift during conversion. The quantity of the intervals falling on the time shift is considered to be either one hour more or one hour less, where spring forward is 23 hours and fall back is 25 hours.

No steps are required to enable this feature.

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

If you have multiple divisions, you can now see service order operational and health check dashboard data by division code.

The following service order operational/trends and health check dashboards have been enhanced to allow filtering by division code:

To enable this feature, set Restrict Division to Yes in the Control by Division section of the MDM master configuration.

The Meter Health Check Dashboard provides a new set of dashboard zones that enable you to collect and visualize sets of data points relevant to non-final initial measurement data (captured as "IMD Seeder Control" and "IMD Control" records). The application verifies the IMD Seeder log table, extracts message texts, and displays the data points on the dashboards. The data points include the following:

The Meter Health Check Dashboard now provides wider dimensions of the processing and quality of non-final IMDs, whether queued or running in memory.

To enable this feature, create the appropriate Statistics Control records, and run the Statistics Control Monitor (F1-STATS) batch job to populate the user interfaces.

This section describes the new and enhanced device and service point features in this release, including:

The SP Multi-Item Information grid of the Service Portal provides a Duplicate column that allows you to create copies of linked items and assign them a new effective date. Previously, when a set of items linked to a service point changed, you needed to re-enter all the unchanged items and assign a different effective date.

This streamlines the handling of a long items list and minimizes the occurrence of errors.

No steps are required to enable this feature.

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

A new multi-channel setup is enabled on the Coincident Peak and Individual SP Demand, and Rolling Demand usage calculation rules, which provides support for solar and co-generation prosumers. This setup allows the creation of custom formulas to filter results. For example, you could exclude solar generation if it is greater than the consumed usage. In addition, you can exclude certain service points associated with the usage subscription.

This reduces implementation and support costs, and shows supplemental invoice or bill information of customers or accounts with special billing arrangements.

To enable this feature, complete these steps:

This section describes the new and enhanced product usability features in this release, including:

Direct Measurement Processing processes initial measurement data (IMD) in memory and creates final measurements in the Measurement (D1_MSRMT) table instead of creating and updating IMD records. IMD records are now only created in case of an exception. For certain use cases, such as enforcing a processing order for consumption check relationships or processing register reads chronologically, Direct Measurement Processing can optionally create temporary staging records (deleted when processing is completed) in the IMD Control Staging table (D1_IMD_CTRL_STAGE) table. This significantly reduces communication between the application and the database as well as the size of the IMD table.

The IMD Control Staging portal can be used to view details of IMD Control staging records that are not yet processed and, when necessary, advance them through the processing workflow. You can access the portal from either the Initial Measurement Data History zone of the Measuring Component portal or the Initial Measurement Data Search zone in the IMD Query portal.

When the system performs VEE processing based on algorithms defined for the initial measurement's IMD Type, if the initial measurement fails a VEE rule with a Severity of 'Information.', a header record is created in the Initial Measurement Data (D1_INIT_MSRMT_DATA) table that acts as a parent for the VEE exception(s).

A new Measurement Audit table captures any changes made to measurements as part of Direct Measurement Processing. In addition, you can use new zones on the measurement Log tab of the Measurement portal to view the audit data. Additionally, users can view new fields in the Measurement portal to display the additional Pre-VEE values (such as, measurement, condition, reading, reading condition, and more). Direct Measurement Processing uses administrative data called IMD Types to define how initial measurement data are processed using Direct Measurement Processing. IMD Types are defined for specific measuring component types in the "Initial Measurement Creation" processing method (“How to Create MC Related Information”) for each head-end system. There are two main categories of IMD types:

Each IMD Type is responsible for processing and preparing input data through validations, channel identification, and unit mapping, or by applying algorithms for Pre-Processing, Pre-VEE, VEE, and Post-VEE.

Direct Measurement Processing enables filtering of incoming data for 'External Measuring Components' and determines initial measurements for processing based on IMD Type configuration. Direct Measurement Processing is available with Native Implementations only, and only for processing Initial Load measurements. It cannot be used for Manual for Estimation measurements.

To enable this feature, refer to the Configuring Direct Measurement Processing section in the Administrative User Guide for more information.

You can now filter (ignore) unwanted channels of measurements from a head end system as well as route pre-VEE measurements to other systems, such as Oracle Energy and Water Data Intelligence.

Channels that are filtered out or are routed out of the system are defined using "External" measuring components. The Measuring Component Types for these "External" measuring components are marked as "Filtered" or "Pass Through."

"External" measuring components define the channels to be filtered or routed out from the system and the Measuring Component Type for these are "Filtered" or "Pass Through". The measuring component type enables the application to filter at a more granular level than the Unit of Measure (UOM). For example, if all meters are programmed to capture several channels across the entire meter population but only certain channels are actually used for a given set of service points, external measuring components can be created to identify which service points should ignore unnecessary channels. This detailed filtering is compatible with the existing UOM filtering so it is possible to filter out data for UOMs should never be accepted for any meter and use the new more nuanced filtering using external measuring components to identify the particular channels to filter.

For routing of pass through measurements, the application allows you to standardize the data into a common format with a common (non headend specific) set of values before forwarding the data to external recipients with lower costs storage. Data standardization also gives the customer more freedom around the access to the data.

To enable this feature, complete these steps:

This feature is only available with "Direct Measurement Processing".

The Install Event Search portal now displays search results in reverse chronological order, listing the most recent event first. This makes searching data for customers with multiple service point or device histories easier. Additionally, the Install Event On/Off History section now displays the most recent event first. Previously, events were sorted by sequence number.

This provides a more efficient way to view installation events and installation on/off activities.

No steps are required to enable this feature.

This section describes the new and enhanced web services features in this release.

This new REST API Inbound Web Services expose various meter-related entities and data, and provide the capability to create, manage, and view that data:

To enable this feature, refer to the Oracle Utilities REST API for Metering and Customer Information documentation.

Implementations must purchase the appropriate subscriptions or license options to use the Inbound Web Services.

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

The Measurement Reprocessing module recognizes the occurrence of an "office exchange". After performing an office exchange for a meter, the new install event may have a different installation constant (multiplier) than the previous install event (removal). Office exchange occurs when the service point's equipment changes and a new meter multiplier must be used. The application identifies the equipment change and the Measurement Reprocessing module recalculates measurements (historical consumption) based on the office exchange dates. The recalculation of measurements based on the office exchange dates also apply to any new install event that is created where the install event covers a time period where previously processed measurements exist.

This reduces manual recalculation of historical consumption and generates more accurate bills.

No steps are required to enable this feature.

Implementations can turn off measurement reprocessing for an office exchange by setting the Ignore New Install Events parameter to "true" in the Detect Installation Constant Change for Install Event (D1-DETIECHG) algorithm.

You can extend the capabilities of D2-CCBRateScheduleLookup by adding attributes to Rates-specific data areas. D1-ExtLookupRateScheduleCommon now includes the D1-ExtendableLookupCommon data area, enabling you to add attributes to determine the eligibility of rates or to classify rates.

Additionally, you can easily tag Tariff Schedule codes to Rate Schedule codes of Customer to Meter. You can also tag Rate Schedule Types for reporting requirements like net metering related rates, low income rates, rates with disconnect season, rates with profile billing, and direct access rates (meter-to-meter). Additionally, you can store HI-Lo Profiles related to rates, enabling M-side to easily identify the Profile type needed for each rate type.

This enables you to easily tag tariff schedule codes to rate schedule codes and rate schedule type to reporting requirements. This allows you to store Hi-Lo Profiles related to rates.

No steps are required to enable this feature.