Oracle MDM Applications

Oracle Utilities - Meter Data Management System:

The primary challenge of implementing smart metering technology is that it results in a flow of large volume of meter data that is much greater than traditional manual metering systems where the meter data is collected on a bi-monthly, monthly or quarterly basis. This increased data volume will flow into the utility which manages the distribution system and also be passed to and from third-party retailers for processing under new market transactions.

Utilities implementing Smart Metering programs face the challenge of managing the huge volume of meter data and transform them into business requirements.

To meet these challenges Oracle MDM system provides utilities with a business critical solution for storing, validating, aggregating and processing large volumes of meter data and preparing them for billing, settlements, analysis and other reporting needs. Oracle MDM system is built with it state of art software and hardware platforms to handle such a huge volume of flooding data in a more efficient way.

S&H Inc has strong expertise in implementation and support of following core features of Oracle Utilities MDM system.

Master Data Synchronization:

Meter data management repository does not own meter, service point, premise and customer contact master data. But these data is mandatory and to be made available to MDM to become operational. A set of data synchronization processes brings these data from the respective data owner systems into Oracle MDM. For example, a utility using Oracle CC&B, the customer and meter information would be synchronized into MDM through the synchronization process. Similarly, any information captured from the field using head end systems will need to be synchronized back to the respective CIS systems.

Initial Synchronization process would typically be carried out during the production migration time of the smart metering implementations. Once the system goes live, the new master data and the filed updates are synchronized using On-going Synchronization process.

Validation, Editing and Estimation (VEE):

One of the most important features of Oracle Utilities Meter Data Management System is the data cleansing process. This is commonly referred as Validation, Editing and Estimation (VEE) process. Oracle Utilities Meter Data Management System contains a wide range of pre configured VEE rules to process the consumption data received from data collection systems on bi-monthly, monthly or quarterly basis as well as the interval data received from modern AMI systems.

Oracle MDM supports a number of widely used industry standard VEE rules out of the box and also provides users with the ability to easily create any custom validation and estimation rules for a variety of purposes. It requires minimal configuration or programming and scripting to create such special rules with very less cost and time associated with system deployment and operations. Oracle MDM allows the user to create different VEE rules for different types of meter registers and based on what the meter measures. The below is the list of pre configured VEE rules supported by Oracle MDM.

  • Interval Adjustment From Scalar
  • Interval Interpolation Estimation
  • Scalar Estimation
  • Interval Size Validation
  • Sum Check Validation
  • High/Low Check
  • Negative Consumption Check
  • Channel / Register Multiplier Check
  • Scalar Replacement Rule
  • Interval Averaging Estimation
  • Interval Profile Estimation
  • Scalar Profile Estimation
  • Interval Spike Check Validation
  • Unit Of Measure Check
  • Zero Consumption Check
  • Interval Missing Quantity Check
  • Scalar Calculation From Interval
  • Interval Replacement Rule

VEE rules are often driven by the regulatory bodies in different geography and by the utilities specific business processes. There may be more complex VEE requirements imposed in a deregulated market area where data need to be delivered to multiple market participants. Oracle MDM uses more complex VEE rules to process the interval data than the scalar data received from the manual collection systems. It can support different VEE work flows for different jurisdictions, geography, service type or customer type based on specific criteria as well.

Measurement and Billable Usage

In the past, utilities were collecting the measurements on monthly or quarterly basis. With the advent of Smart Grid applications utilities are collecting interval data on a possible smallest interval (15-min, 30-min) periods.

Multiple AMI systems would send the data via their respective head end systems to Oracle SGG (smart Grid Gateway), where the data is unified and queued to be processed by Oracle MDM system. Once the measurements are received, Oracle MDM will run the VEE processes to create a clean bill ready measurement data. This process will also fill any gaps (for the missing data) based on the VEE configurations. Downstream utility systems such as Billing Systems, Data Warehouse Systems and Outage Management Systems can subscribe their data from the Oracle MDM for their specific purposes.

For example, Oracle Customer Care & Billing system can obtain billable usage data for interval and scalar meters from Oracle MDM without worrying about which AMI system collected the measurement data from the customers. This service oriented architecture creates a virtual plug and play capability and ensures the flexibility during system upgrades or change of any sub systems with minimal cost, disruption and effort.

Smart Meter Events

The Smart meters are capable of detecting and producing various events to alert a utility that something significant has happened to it, such as an attempt to tamper with the device, a loss of power, or that the device has a low battery indicator. While loading a device event, the Oracle MDM first determines from which Head End System the event is received and then finds out which device produced it. Based on the Head End System that sent it, the system finds the standard event type that corresponds to the event sent. Oracle MDM then determines if any additional processing is needed for the event. For example, some events might arrive in pairs (power outage and power restoration) are handled differently than singular events. External applications can subscribe to receive events of certain categories. After events have been analyzed and stored, they are sent to the subscribing application using the business process defined for the subscriber.

Smart Grid Gateway (SGG) – Two Way Communication and Process Automation

S&H has strong experience implementing and customizing a range of Smart Grid gateway (SGG) adapters to integrate multiple AMI systems that use different technologies, protocol and data formats to share meter data with other systems. This feature effectively decouples downstream applications from Advanced Metering Infrastructure. It also allows the integration of new technologies as they emerge, and the decommissioning of old technologies, without being restricted to a single vendor or AMI implementation. This means consumers can use Oracle MDM as a single consistent interface across the various AMI systems with data presented in a centralized repository.

Oracle MDM feature enables bi-directional smart metering infrastructure networks to communicate with other systems. It provides routing and management components for implementing the required two-way processes. Oracle MDM is capable of handling the following smart metering commands with Oracle SGG:

  • Remote Connect - Initiates power flow from the source through the meter. This does not mean that the device is being installed. Once command is being sent, it is assumed that the device has already been installed. The Head End Systems typically require more than one communication to facilitate this process. Utilities may also want to retrieve a start read for scalar subtractive meters during this command.
  • Remote Disconnect - Stops power flow through the meter. This does not mean that the device is being removed. Like connect command, disconnect typically involves more than one communication to the Head End System. Utilities may want to retrieve an end read for scalar subtractive meters during this command.
  • Device Commissioning - Drives the registration or discovery of the device by the Head End System. This process does not always require an explicit communication. Utilities won’t always receive an explicit response to a commission request. Sometimes receiving measurements could be an indication of a successful commissioning.
  • Device Decommissioning - Notifies the Head End System that no further data will be arriving from the device
  • On Demand Read (Interval) - Accommodates near real time requests for readings.
  • Device Status Check (Meter Ping) - Returns the working condition of a device, and this might involve more than one communication.

In addition to standard commands, any meter vendor specific two-way communication commands can be built using the MSM extension features. The Smart metering commands can be enabled by end to end process automations. For example, an utility using Oracle CC&B and MDM systems could include the integration of “turn-on/turn-off” business process by combining both manual collection method and smart meters with an integrated remote connect disconnect command. In this case, once CC&B system determines that customer power is to be turned off, Oracle MDM system can be implemented to determine, depending on the meter type, whether the turn-on/turn-off requires a field service order, or can be executed directly through the smart metering infrastructure systems using the SGG smart metering commands. Oracle SGG benefits the customer by reducing costs to implement and operate smart grid processes and programs, minimizes data duplication and improves system performance, provides a common set of commands to foster application interoperability and improves the security and better audit of smart grid processes.

Back to Top