Merged Maintenance

Merged maintenance allows data in multiple product—specific maintenance objects to be updated via a single maintenance portal.

Administrative Data Merged Maintenance

Merged maintenance is used with several types of administrative data in Customer Care and Billing and Meter Data Management that are used in nearly identical ways in both applications. These include:

  • Service Type

  • SP Type (Service Point Type)

  • Service Quantity Identifier

  • Time of Use

  • Unit of Measure

When a user creates or updates data of these types, the maintenance portal displays a superset of data elements from product-specific business objects based on a “superset” service script (defined in the Joint Maintenance Lookup extendable lookup (see below)). When the data is saved, the corresponding maintenance objects in Customer Care and Billing, Meter Data Management, and Operational Device Management are updated. For example, when a user navigates to the Unit of Measure portal and selects a record to update, the portal displays a combination of data from the X1-UnitOfMeasure and D1-UnitOfMeasure business objects. When the user saves the data, the changes are saved to both the UOM Customer Care and Billing maintenance object and the D1_​UOM Meter Data Management maintenance object.

Note: Service Point Types (asset location types) are also used by Operational Device Management.

Service Point Merged Maintenance

In addition to the above types of administrative data, Customer to Meter service points are also maintained through merged maintenance. Service point merged maintenance does NOT make use of a “superset” service script, but does use product-specific business objects. Oracle Utilities Customer to Meter service points (asset locations in the case of Operational Device Management) are maintained through these product-specific business objects and extendable lookups.

The Customer to Meter base package uses the following service point business objects:

  • Meter Data Management: X1D-ServicePoint

  • Customer Care and Billing: X1-ServicePoint

  • Operational Device Management: W2-ServicePoint

When a Customer to Meter service point is created or updated, the “Maintain CCB Service Point” (X1-CCBSPMNT) and “Maintain ODM Service Point” (X1-ODMSPMNT) Pre-Processing algorithms on the X1D-ServicePoint business object uses the C2M Mapping Field Values (X1–CCBMDM-MDMCCB-Lookup) and ODM-MDM Mapping Field Values (X1-ODMMDM-MDMODM-Lookup) extendable lookups to map lookup values between Customer Care and Billing and Meter Data Management and between Meter Data Management and Operational Device Management, and creates or updates an instance of the X1–ServicePoint and W2-ServicePoint business objects (which are used to update the their corresponding maintenance objects).

Note: Customer to Meter service point types should reference the “Service Point — MDM” (X1D-ServicePoint) business object.

Joint Maintenance Extendable Lookup

The specific business objects and service scripts used by merged maintenance are defined in the Joint Maintenance Lookup (X1-JointMaintenance) extendable lookup. Records in this extendable lookup define the superset script that contains the union of the elements of the objects that exist in Customer Care and Billing and Meter Data Management, as well as the corresponding product-specific business objects.

Merged maintenance lookup values are defined by the following:

  • CCB Maintenance Object: the unique identifier for the joint maintenance lookup value

  • Superset Script: the superset script that contains the union of the elements of the objects that exists in Customer Care and Billing and Meter Data Management. Used for administrative data maintenance only.

  • CCB Business Object: the business object used to update the Customer Care and Billing maintenance object

  • MDM Business Object: the business object used to update the Meter Data Management maintenance object

  • ODM Business Object: the business object used to update the Operational Device Management maintenance object