• In
Oracle Utilities Customer to Meter (C2M) solution, CC&B and MDM systems are
installed together. The C2M system comprises of CC&B, MDM, SGG, SOM and ODM
in a single instance
• The
primary aim of C2M is to provide an integration free single Oracle utilities system
with:
–
Single database
–
Single framework & application
– Single unified User Interface
• At
the high level, the features are supported by different C2M subsystems are as
below:
– CC&B: Sales and marketing, Program
management, Customer account management, Rating, Billing, Budget plans, Deposits,
Loans, Payment processing, Credit and collection
– MDM: Measurement Data management, VEE, Usage
Subscription, Usage calculations
– ODM: Smart Device management including life
cycle, Tracking firmware versions on smart devices
– SGG: Usage and Event data loading, two-way
smart command management
– SOM: Service order management, smart
command orchestration
Application
Module
|
Supported
Subsystem
|
Customer
account
|
CC&B
|
Rate and
Billing
|
CC&B
|
Payments
|
CC&B
|
Credit and
Collection
|
CC&B
|
Devices and
Items
|
MDM
|
Measurement
Data
|
MDM
|
Usage
calculation
|
MDM
|
Service Order
|
SOM
|
Command orchestration
|
SOM
|
Device Inventory
|
ODM
|
Device Testing
|
ODM
|
Firmware upgrade
|
ODM
|
• Integration free Internal Interaction within
subsystems:
– C2M
application components have internal integration for admin and master data
between different subsystems. New
X1 layer OUAF components used to achieve Customer to Meter specific data synchronization
functionality.
– “Customer to Meter Master
Configuration” provides a summary of master and administration data integration
free internal interaction configuration. This contains configuration about consolidated
maintenance objects, extendable lookup mapping of admin data between CC&B
and MDM and master data synchronization between different subsystems.
– “Seeder
Sync Request Master Configuration” encapsulates the master data synchronization
mapping of Customer to Meter for below entities.
• CC&B Person –> MDM Contact
• CC&B Service Agreement –> MDM
Usage Subscription
• CC&B Bill Cycle –> MDM Bill
Cycle
• CC&B Contract Option –> MDM
Dynamic Option
• CC&B Contract Option Event –>
MDM Dynamic Option Event
– “Master
Data Synchronization Configuration” master configuration is used to retrieve a specific
identifier type that is used to convert from the CCB identifier to the
identifier of corresponding MDM object.
Excellent information / update Senthil. Thanks for sharing.
ReplyDeleteThis is helpful
ReplyDeleteThanks for Sharing this. This is really helpful in understanding the overview of C2M.
ReplyDeleteAwesome information.
ReplyDeleteWellcome back. Thanks for sharing.
ReplyDeleteHi Senthil, This is very useful. Could you also explain what are the risks/ challenges of using C2M over CCB & MDM standalone. OR in which cases should a business have these systems implemented standalone instead of C2M
ReplyDeleteThis is great Senthil. Appreciate you generous help.
ReplyDeleteHi Senthil, this was a great post! Do you know if any Utilities have gone live with Oracle's C2M implementation yet? I know a few were implementing it (Hydro Ottawa, Nashville Electric) but have not heard of anyone being live...
ReplyDeleteHi Senthil...Information shared here is highly appreciated. Your article has inspired many of us to learn this. You have shared your immense knowledge on Oracle C2M .Recently i came to know MaxMunus offers the best Oracle C2M training across the globe. If you come across anyone looking for training, you can ask him to contact them directly. They are reachable at:-
ReplyDeleteOracle C2M training