Oracle Utilities Customer To Meter (C2M) - Why is it called “Integration Free Single Instance System”?

•    This post describes the difference between separate instances of CCB + MDM and single instance C2M and explains how the internal integration is done in C2M without having SOA middleware layer.

•    Prior to the advent of C2M, the CC&B and MDM systems are installed separately (Database and Application Server) and Oracle SOA middleware is used for integrating these systems. There exists a CCB - MDM integration pack to glue these systems.

•    When a CCB objects is created or updated, underlying MO audit algorithm is used to create corresponding outbound sync request. This will be sent to MDM via SOA middleware.  CCB - MDM productized integration pack carries out the integration / synchronization of following entities between these two systems using SOA middleware infrastructure and BEPL process orchestration.

From CCB	To MDM
CCB Person	MDM Contact
CCB Service Agreement	MDM Usage Subscription
CCB Service Point	MDM Service Point
CCB Meter Information	MDM Device
CCB Meter Configuration	MDM Device Configuration
CCB SP Meter History	MDM Installation Event
CCB Bill Cycle	MDM Measurement Cycle
CCB Billable Usage request/response	MDM Bill Determinant request/response

The below diagram depicts SOA middleware layer used between CCB and MDM systems for such integrations. 

•    As Oracle Utilities C2M being a single instance system, it reduces complexity and does NOT use SOA middleware and productized CCB - MDM integration pack for master data synchronization and integration.

•    C2M system uses X1 OUAF layer entities (BO, Algorithms, Extendable Lookups, Master configurations) for data interaction.  The X1 layer acts as internal middleware between CCB (C1) and MDM (D1) for data synchronization. This new X1 is purely a logical layer and does not have any MOs in it.   

•    In C2M, data synchronization between CCB and MDM related entities are preformed using the following approaches. 

•       Internal Data Synchronization

•       Joint Maintenance Synchronization

•       Joint Maintenance Superset Script Synchronization 

The below diagram depicts C2M integration free data synchronization between CCB and MDM entities. 

 1. Internal data synchronization approach: Audit algorithms on CCB entities are used for data synchronization. MO audit algorithms creates specific outbound sync requests which is similar to what is practiced in CCB - MDM separate instances integration. The following entities are synchronized using this approach.

 

From CCB	To MDM
C1 Person	D1 Contact
C1 Service Agreement	D1 Usage Subscription
C1 Bill Cycle	D1 Bill Cycle
C1 Contract Option	D1 Dynamic Option
C1 Contract Option Event	D1 Dynamic Option Event

 2. Joint Maintenance Synchronization Approach: This approach is used to synchronize entities having single user interface but have different MOs in CCB(C1) and MDM(D1).

From	To
D1 Service Point	C1 Service Point
D1 Service Point	C1 Bill Cycle
C1 Premise	D1 Service Point
D1 TOU Group	C1 TOU Group
D1 TOU Map	C1 TOU Map
D1 TOU Map Template	C1 TOU Map Template
D1 TOU Map Type	C1 TOU MAP Type
D1 Device Type	C1 Meter Type

 








       

• Service Point: Pre-Processing algorithm on MDM Service Point BO used to add, update or delete CCB Service Point.  MDM Service Point BO audit algorithm is used to update CCB Bill Cycle due to MDM SP measurement cycle change 

• Premise: Audit algorithm on CCB Premise MO is used to update MDM Service Point details as and when required

•  MDM Admin Entities: If CCB holds subset of MDM data, audit algorithms on MDM BOs with be used to add, update or delete corresponding CCB entities. TOU Group, TOU Map, TOU Map Template, TOU Map Type, Device Type are synchronized from MDM(D1) to CCB(C1) using this approach.

  3. Joint Maintenance Superset Script Synchronization Approach:  This approach is used to maintain similar entities having different data in CCB and MDM.                             X1-JointMaintenance extendable lookup holds details about superset script, CCB BO and MDM BO for data maintenance. BPA scripts are used for maintaining following administration entities in this approach.

CCB	MDM	Superset BPA Script
C1 Unit of Measure	D1 Unit of Measure	X1-UOMMnB
C1 Time of Use	D1 Time of Use	X1-TOUMnB
C1 Service Quantity Identifier	D1 Service Quantity Identifier	X1-SQIMnB
C1 Service Type	D1 Service Type	X1-SvcTyMnB
C1 Service Point Type	D1 Service Point Type	X1-SPTypMnB

Note: Device, Device Configuration and Measuring component data are specific to MDM (D1) so these entities are not synchronized with CCB.