Upgrades and support for Oracle Utilities billing and outage systems.
We upgrade and support Oracle Utilities Customer Care and Billing, Customer to Meter and Network Management System, and we build on the Oracle Utilities Application Framework. We also staff the configuration and integration roles utilities find hard to hire for.
Cohash upgrades and supports Oracle Utilities Customer Care and Billing (CC&B), Customer to Meter (C2M) and Network Management System (NMS).
We plan moves from 2.x releases to the 25.x line and rework algorithms and batch on the Oracle Utilities Application Framework (OUAF). We also build integrations to meters, ERP and CRM. Certified engineers are available onsite in the US or from nearshore and offshore teams, on contract, contract-to-hire or permanent terms.
you probably need this if
CC&B runs on a 2.x release and nobody has read the 25.4 upgrade notes yet.
Bill cycles spill past the batch window every summer and winter peak.
A patch to the framework breaks custom algorithms that nobody documented.
09 Sep 2025CC&B 25.4 Release notes list tested one-step upgrades to 25.4 from 2.9.0.1.1, 2.9.0.0.0, 2.8.0.0.0, 2.7.0.3.0 and 2.6.0.1.0. Ships with OUAF 25.4. source ↗
09 Sep 2025Customer to Meter 25.4 Adds Operational Device Management to Customer to Meter. Follows 2.9.0.2.0 on Oracle's release list. source ↗
09 Sep 2025OUAF 25.4 Adds UI masking for numbers through the new F1-MASKNBR algorithm type, among other framework changes. source ↗
06 Feb 2026NMS 25.12.0.0 Follows 2.6.0.2. Enhancements cover DERMS, Flex Operations, FLISR, power flow, SCADA, the Operations Mobile Application and outage management. source ↗
today · Oct 22, 2026
the story · oracle utilities cc&b, c2m & nms estate
From the first call to a setup your own team can run.
Here's what usually prompts a call about your Oracle Utilities CC&B, C2M & NMS estate, what we do about it and in which order, and where you end up.
01 · where it hurts02 · what we change03 · how it runs04 · where you end up
incident board · oracle utilities cc&b, c2m & nms…3 open
openCC&B runs on a 2.x release and nobody has read the 25.4 upgrade notes yet.
recurringBill cycles spill past the batch window every summer and winter peak.
blockedA patch to the framework breaks custom algorithms that nobody documented.
exposure
CC&B and C2M upgrades to 25.xOUAF configuration and extensionsNMS upgrades and outage operationsIntegrationsBatch and performance tuningStaffing for Oracle Utilities
CC&BERP
startrehearsehandover
Inventory and fit
Technical upgrade on a copy
Parallel bill cycles
Cut-over and support
we are here
ready to hand over
The utility upgrades on a tested path with fewer custom objects than before, and future…
The control room enters storm season on the current release, with operators already…
Custom code inventory: algorithms, business objects, scripts, zones and batch controls
Upgrade path decision with the tested one-step route to 25.4
chapter 01 · where it hurts
Why teams reach out
CC&B runs on a 2.x release and nobody has read the 25.4 upgrade notes yet.
Bill cycles spill past the batch window every summer and winter peak.
A patch to the framework breaks custom algorithms that nobody documented.
chapter 02 · what we change
How we solve it
CC&B and C2M upgrades to 25.x
OUAF configuration and extensions
NMS upgrades and outage operations
Integrations
Batch and performance tuning
Staffing for Oracle Utilities
chapter 03 · how it runs
Our approach
Inventory and fit
Technical upgrade on a copy
Parallel bill cycles
Cut-over and support
chapter 04 · where you end up
What changes
The utility upgrades on a tested path with fewer custom objects than before, and future framework patches touch less code.
The control room enters storm season on the current release, with operators already trained on the new screens and a rollback plan they have seen work.
Custom code inventory: algorithms, business objects, scripts, zones and batch controls
Upgrade path decision with the tested one-step route to 25.4
what we do
Our Oracle Utilities CC&B, C2M & NMS work
6 kinds of Oracle Utilities CC&B, C2M & NMS work, each run by engineers who have done it on live tenants.
Upgrade planning from 2.6, 2.7, 2.8 or 2.9 to 25.4, using the one-step paths Oracle tested. Custom algorithms, business objects and batch controls are inventoried and retested first.
Algorithms, business objects, scripts, zones and batch controls built in the framework's own tools, kept in Content Migration Assistant bundles so they move between environments cleanly.
NMS upgrades from 2.5 or 2.6 to 25.12, with model build, SCADA and AMI interfaces, and storm-mode testing before the change goes near the control room.
Meter data from AMI head-ends, GL extracts to ERP, account and bill APIs for CRM and portals, and outage feeds from NMS to customer channels.
Thread counts, commit intervals and run schedules reviewed against the actual bill cycle volumes, so billing finishes inside its window.
CC&B and C2M functional consultants, OUAF developers, NMS engineers and integration developers, onsite, nearshore or offshore.
capability 01 / 06in production
CC&BERP
CC&B and C2M upgrades to 25.x
Upgrade planning from 2.6, 2.7, 2.8 or 2.9 to 25.4, using the one-step paths Oracle tested. Custom algorithms, business objects and batch controls are inventoried and retested first.
Algorithms, business objects, scripts, zones and batch controls built in the framework's own tools, kept in Content Migration Assistant bundles so they move between environments cleanly.
NMS upgrades from 2.5 or 2.6 to 25.12, with model build, SCADA and AMI interfaces, and storm-mode testing before the change goes near the control room.
Oracle Utilities CC&B, C2M & NMS situations we walk into
We pieced these together from Oracle Utilities CC&B, C2M & NMS situations that come up a lot. They're patterns. You won't find a specific client in them.
case file 01
CC&B 2.7.0.1 with ten years of custom algorithms
composite · not a client story
Beforethe situation
A water and wastewater utility runs CC&B 2.7.0.1 with several hundred custom algorithms and a dozen batch controls cloned from base. The 25.4 release notes don't list 2.7.0.1 as a tested starting point.
What we dothe work
We map the route through 2.7.0.3.0, then inventory every algorithm and cloned batch control against base 25.4. Clones that base now covers are retired. A production copy is upgraded twice, once for timing and once for full regression, before parallel bill cycles start.
Afterwhere you end up
The utility upgrades on a tested path with fewer custom objects than before, and future framework patches touch less code.
case file 02
NMS 2.5 and a storm season eight months out
composite · not a client story
Beforethe situation
An electric distribution utility runs NMS 2.5 with SCADA and AMI interfaces. The control room won't accept changes from late spring, and the vendor's newer FLISR features are only in recent releases.
What we dothe work
We build the 25.12 environment from the current network model, replay recorded storm traffic against it and run operator walk-throughs. Interfaces are retested with SCADA and AMI owners, and cut-over is set for the quiet months.
Afterwhere you end up
The control room enters storm season on the current release, with operators already trained on the new screens and a rollback plan they have seen work.
How a Oracle Utilities CC&B, C2M & NMS engagement runs
We don't start a step until the last one has produced something you can check.
step 01
Inventory and fit
We go through each custom algorithm, business object, script, zone, batch control and interface and check it against the 25.x release notes and OUAF deprecation notices.
step 02
Technical upgrade on a copy
We take a copy of production through the tested one-step path to 25.4 or 25.12, time each conversion run and fix whatever fails to compile or load.
step 03
Parallel bill cycles
We run selected bill cycles on both versions at once. Before sign-off, bills, financial transactions and GL extracts are compared line by line.
step 04
Cut-over and support
We time the production upgrade to fall between bill cycles, stay through the first full month of billing and hand your support team a runbook.
ai on oracle utilities cc&b, c2m & nms
Where AI fits on Oracle Utilities CC&B, C2M & NMS, and where it needs guardrails.
We don't name vendor AI features for on-premises CC&B, C2M or NMS here, because the 25.x release notes we track focus on billing, meter, outage and framework changes. AI is still useful around these systems: documenting custom OUAF code, building bill-cycle regression tests and triaging batch failures.
AI agentasks for data or an action
Scoped identityonly the access it needs
MCP serverthe one door into the platform
Logged, approveda person signs off on writes
CC&BOracle Utilities CC&B, C2M & NMSdoes the work
Oracle doesn't currently publish an official MCP server for CC&B, C2M or NMS, so agents go through the framework's web service APIs, or else read-only reporting copies. Give them a dedicated application user with minimal roles and log their calls. Account, bill and outage record changes wait for a human to approve them.
Documenting custom OUAF code
Custom algorithms, business objects and scripts pile up over the years, often with no documentation. AI can draft a description of each from the code, and OUAF developers check it. Then the 25.4 upgrade inventory starts from facts.
Bill-cycle regression tests
We use production bill cycles to build comparison scripts and test cases, with AI helping. AI then groups the variances between old and new versions by likely cause. Billing analysts sign off each one.
Batch and interface triage
Batch thread logs plus AMI, ERP and CRM interface errors go into one daily list, summarized by AI with probable causes. During peak bill cycles, that lets support staff fix the right thing first.
Upgrade mapping to 25.x
AI can check each custom object against base 25.4 or NMS 25.12 functions and flag it if base now covers it. Engineers decide what to retire.
Where CC&B, C2M and NMS sit between the grid and the business
Meter reads flow from the AMI head-end into Customer to Meter for validation, usage and billing. NMS takes SCADA telemetry and customer calls to manage outages, while billing results move on to ERP, CRM and the data warehouse.
01 · Field and grid
AMI head-endinterval reads · meter events → C2M 25.4 · interval reads
SCADAbreaker status · telemetry → NMS 25.12 · telemetry
What a Oracle Utilities CC&B, C2M & NMS engagement leaves behind
These are working documents, written against your configuration, so your team can run them without us.
inventory01
Custom code inventory: algorithms, business objects, scripts, zones and batch controls
yours to keep
tests02
Upgrade path decision with the tested one-step route to 25.4
yours to keep
document03
Conversion run timings from a technical upgrade of a production copy
yours to keep
report04
Parallel bill cycle comparison report with every variance explained
yours to keep
inventory05
Interface catalog covering AMI, ERP, CRM and NMS feeds with owners
yours to keep
runbook06
Cut-over runbook timed between bill cycles
yours to keep
talent and delivery · oracle utilities cc&b, c2m & nms
Certified engineers, wherever you need them.
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
Onsite
Engineers at your sites in the US
Nearshore
Overlapping hours with US teams
Offshore
Overnight progress on your backlog
All time zones
Coverage handed over across time zones
24-hour coverage · US Central time
OnsiteUS business hours
Nearshoreoverlapping US hours
Offshoreovernight progress
Combinedhandover, not hand-off
00:0006:0012:0018:0000:00
roles we staff
CC&B functional consultant (billing and rates)
OUAF developer (algorithms, business objects, scripts)
C2M meter data management consultant
NMS engineer (model build, SCADA, FLISR)
Oracle Utilities integration developer
Oracle Utilities DBA and batch performance engineer
due diligence · oracle utilities cc&b, c2m & nms
Questions to ask any partner, including us.
Put these to anyone bidding on your Oracle Utilities CC&B, C2M & NMS work. The ones who've done it answer differently from the ones who've read about it.
Q1
Which tested one-step path to 25.4 applies to our exact CC&B release?
Oracle tested specific starting releases. A plan that assumes a path not on that list adds an extra upgrade hop that nobody budgeted for.
Q2
How will you find cloned base objects before the upgrade?
Cloned batch controls and algorithms miss base fixes. Finding and retiring them is often the biggest cost driver in a CC&B upgrade.
Q3
How many full bill cycles will you compare in parallel, and how?
Billing defects show up in totals, rounding and edge-case rates. A line-by-line comparison of bills and financial transactions catches what spot checks miss.
Q4
How do you test an NMS upgrade under storm load?
Testing on a normal day hides the problems you care about. If you want to know how outage prediction and crew dispatch will hold up, replay recorded storm traffic.
Q5
Who keeps our CMA bundles and environment migrations in order?
OUAF configuration moves between environments through Content Migration Assistant. If the team is sloppy about it, test and production drift apart.
01What changed with the jump from 2.9 to 25.4?
Oracle switched the on-premises line from 2.x numbering to year-based releases. CC&B and C2M jumped from 2.9.0.2.0 to 25.4, and NMS from 2.6.0.2 to 25.12.0.0. Don't let the new numbers fool you. It's still an upgrade with database and framework changes, and it needs the same inventory, conversion and regression work.
02Can we upgrade straight from CC&B 2.7 to 25.4?
The 25.4 release notes list a tested one-step path from 2.7.0.3.0, and also from 2.6.0.1.0, 2.8.0.0.0 and the 2.9 releases. If you're on a different 2.7 level, move to a tested starting point first. Other paths are in the Database Administrator's Guide.
03How long does a CC&B or C2M upgrade take?
It depends on the amount of custom code, the number of interfaces and how many full bill cycles you want to compare in parallel. We size it after an inventory of algorithms, business objects, batch controls and interfaces, and after a first technical upgrade of a copy of production.
04Do you work on Customer Cloud Service as well as on-premises?
Yes, on configuration, integration and data migration. The upgrade work on this page applies to on-premises installs. Cloud service customers get releases from Oracle on its own schedule, so the work shifts to regression testing and keeping extensions compatible.
05Can you provide Oracle Utilities people without a project?
Yes. We place CC&B and C2M functional consultants, OUAF developers, NMS engineers and integration developers. They work onsite in the US, nearshore or offshore, on contract, contract-to-hire or permanent terms.
services
Related services
Projects on Oracle Utilities CC&B, C2M & NMS usually end up touching one of these, so they're worth a look.
Reviewed by the Cohash teamOracle Utilities CC&B, C2M & NMS is a trademark of its owner, used here to identify the platform.how we handle facts and data →
next step
Tell us what you're running. We'll tell you what we'd do first.
A 30-minute working session with a senior engineer. No slides.
