Home / Utility ERP and CIS / Oracle C2M
Oracle C2M staffing and consultants
Oracle Customer to Meter (C2M) combines Customer Care and Billing with Meter Data Management in a single converged product, deployed and operated by the utility. Mako staffs C2M programs with functional, technical and conversion consultants, including utilities migrating from standalone CC&B.
Consultants for converged billing and metering programs, implementation, migration and ongoing upgrade support.
- Submittals within 48 hours
- 80% of submittals hired at a utility client
- AMI Integration Developer
Meter read
AMI head-end into Oracle MDM
- MDM Functional Consultant
Validate
VEE rules in Oracle MDM
- C2M Configuration Lead
Bill determinants
Usage to billing in C2M
- CC&B Rates Analyst
Bill
Rates and bill calculation in CC&B
- Collections Analyst
Pay and collect
Payments, credit and collections
What Oracle C2M is
One utility-managed platform for customer, billing and meter data.
For utilities today on Oracle CC&B with a separate Meter Data Management instance, C2M and CCS collapse two platforms into one. That changes the shape of the team: the billing and metering workstreams design together instead of negotiating across an interface.
Technical work still runs on the Oracle Utilities Application Framework, so extension and batch skills transfer directly (see OUAF developer staffing). For how these roles fit into a broader program plan, see our utility ERP and CIS practice.
If you are evaluating a cloud-delivered deployment instead, the SaaS form of this same converged product is Oracle Customer Cloud Service (CCS), which is where most new utility CIS implementations now start.
One converged product
C2M merges the CC&B and MDM codebases so customer, account and service point data sits alongside measurement and usage data. Cross-system reconciliation between billing and meter data largely disappears, and one upgrade covers both functional domains.
Why utilities move to it
Utilities running CC&B with a separate MDM carry an interface, two upgrade schedules and two support teams. Convergence reduces integration surface, simplifies exception handling between usage and billing, and aligns the platform with Oracle's forward roadmap.
Utility-managed operations
With C2M the utility or its partner owns the environments, patching and upgrade timing. That means more control over when change lands and how far extensions go, in exchange for carrying platform operations and upgrade projects internally.
Extension and customization latitude
C2M permits deeper customization than the cloud service, but heavy custom code still becomes a liability at every upgrade. Successful teams push requirements into supported configuration, business objects, algorithms and scripting, and treat custom Java extensions as a last resort.
Upgrade planning
Because the utility controls timing, C2M upgrades tend to be discrete projects rather than continuous adoption. Regression coverage still matters, but the staffing pattern is periodic upgrade capacity rather than a standing release team.
Coming from standalone MDM
Utilities consolidating an existing MDM instance must migrate VEE rules, measurement history, usage subscriptions and head-end integrations into the converged model, a distinct workstream from the customer and billing conversion.
Roles we place
Contract, contract-to-hire and full-time across functional, technical and program roles on C2M.
- C2M Functional Consultant
- C2M Solution Architect
- Billing & Rates Analyst
- MDM/Metering Analyst
- Conversion Lead
- OUAF Developer
- Integration Developer
- Test Lead
- C2M Project Manager
Where teams need help
The roles C2M programs most often struggle to source.
Migration-experienced functional leads
Consultants who have actually executed a CC&B to C2M move know which configuration carries forward and which must be redesigned, knowledge that is difficult to acquire mid-program.
Converged metering and billing skill
Few consultants are strong on both sides of the converged product. Teams usually pair a billing-heavy functional lead with a metering analyst rather than looking for one person who covers both.
Extension discipline and technical review
A framework-literate technical architect keeps requirements inside supported configuration patterns, which is what keeps future releases from becoming re-implementation projects.
Upgrade and regression testing capacity
Each upgrade needs regression coverage across billing, metering and integrations. Test capacity is often the role utilities plan last and need longest.
How CCS differs from C2M
Same converged functionality, different operating model.
Customer Cloud Service (CCS) delivers the same converged customer and meter data footprint as a service. Oracle provisions and operates the environments and applies releases on a regular cadence, so the utility sheds infrastructure work but adopts Oracle's release schedule and stays inside supported extension boundaries. C2M keeps that control, and the operational responsibility that comes with it, in house.
Most new utility CIS implementations now start on CCS, and it is where many CC&B utilities are heading. We cover the platform, the delivery-team implications and the roles it demands in depth on our dedicated page, and compare the generations side by side in CC&B vs C2M vs CCS.
Oracle C2M staffing questions
What is Oracle C2M?
Oracle Customer to Meter (C2M) is a converged product that combines Customer Care and Billing with Meter Data Management in a single codebase and database. Instead of integrating two separate systems, meter data validation and billing run on one platform, which removes a major interface and aligns upgrade cycles.
What is the difference between C2M and CCS?
C2M is the customer-managed deployment, typically on-premise or on infrastructure the utility controls, so the utility owns environments, patching and upgrade timing. Customer Cloud Service (CCS) is Oracle's SaaS delivery of the same functional footprint, where Oracle manages the environments and applies releases on a regular cadence. The functional configuration work is similar; the operating model, extension boundaries and release discipline differ. Most new implementations now start on CCS.
Do you staff CC&B to C2M migrations?
Yes. We place migration-experienced functional and technical consultants, conversion leads, integration developers, test leads and cutover managers for CC&B to C2M programs, including utilities retiring a standalone MDM instance at the same time. We staff CC&B to CCS moves as well.
What roles are needed on a C2M implementation?
Typically a functional workstream for billing, rates and credit, metering and MDM analysts for VEE and usage configuration, framework developers for extensions and batch, integration engineers for head-end and payment interfaces, test leads, and program roles including a cutover manager. We staff these individually or as a full team.
Hiring a permanent Oracle Utilities employee? MakoHire handles permanent and direct hire (opens in a new tab).
A 30-minute hiring call with our team
We'll talk through the role, the experience your team needs and your timeline. You don't need a finished job description.