Oracle Customer Care and Billing (CC&B) is one of the two enterprise standards for utility customer information and billing. The hard part is rarely the software, it is the implementation. This guide covers what an Oracle Utilities implementation involves and where programs go wrong.
What the program actually includes
A CC&B implementation is more than installing the billing engine:
- Rating and billing configuration. Encoding every rate, rider, and tax the utility charges.
- Data migration. Moving accounts, meters, and billing history off the legacy CIS cleanly.
- Integration. Wiring CC&B to meter data management (Oracle MDM), outage management (Oracle Network Management), payment processors, and the general ledger.
- Testing. Running real billing scenarios, including estimated reads, prorated bills, and deregulated-market cases, before go-live.
Common pitfalls
- Underestimating rate complexity. Time-of-use, tiered, and seasonal rates multiply test cases. Scope them early.
- Dirty legacy data. Bad meter and account data in the old CIS surfaces as billing errors after cutover. Cleanse before you migrate, not after.
- Big-bang cutovers. Phasing by service type or region reduces risk on high-volume billing.
- Thin reconciliation. Plan parallel billing runs so you can prove the new system bills the same as the old one before you switch off the legacy system.
Where this fits
If you are still selecting between platforms rather than implementing, start with the Oracle vs SAP for utilities comparison. For utilities weighing a lighter-weight option, the Cayenta CIS review covers the mid-market alternative.