Home / Utility ERP and CIS / Utility CIS implementation staffing
Utility CIS implementation staffing
A utility Customer Information System implementation typically needs functional leads for billing and credit, a conversion lead, OUAF or ABAP developers, integration engineers, test leads and a cutover manager. Mako Professionals sources these roles individually or as a full project team for Oracle CC&B, C2M and SAP IS-U programs.
Role-by-role staffing for programs already scoped and moving, or teams still being built.
- 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
How CIS implementation teams are usually structured
Six workstreams, each with distinct accountability, and distinct hiring difficulty.
Functional
Functional consultants own how the system bills and serves customers: rate configuration, billing and invoicing rules, credit and collections treatment, and customer service processes. They translate tariff sheets and regulatory requirements into system configuration and are accountable for design decisions that survive audit. On most programs this is the largest workstream and the first one to be staffed.
Technical
Technical developers build within the platform framework: business objects, algorithms, scripting, extensions and batch processes. They also handle performance tuning of billing and batch jobs, which becomes critical as data volumes grow through testing. Framework-experienced developers are the hardest role to source, so lead time matters.
Conversion
The conversion team extracts legacy customer, account, premise, meter and financial data, maps it to the target model, and runs iterative mock conversions. Their accountability is reconciliation: proving that balances, usage history and service agreements match before cutover. Conversion effort is routinely underestimated and drives more go-live delays than any other workstream.
Integration
Integration engineers connect the CIS to metering and AMI head-ends, payment and remittance processors, GIS, the financial ERP, and outage and work management systems. They own interface design, error handling and reprocessing, and end-to-end testing across system boundaries. Interface count is one of the strongest predictors of overall program effort.
Quality
The quality workstream defines test strategy and executes system integration testing, user acceptance testing and performance testing of billing and batch cycles. Test leads build traceability from requirements through scripts so defects are attributable and regression coverage is real. Under-resourcing this group late in the program is one of the most common causes of a slipped go-live.
Program
Program roles cover project management, cutover planning and change management. The cutover manager owns the sequenced go-live runbook, contingency and rollback plans, while change management prepares customer service and field staff for new processes and screens. These roles hold the workstreams together and keep dependencies visible.
For platform-level detail on the systems these teams implement, see our utility ERP and CIS staffing practice.
Common staffing gaps on CIS programs
Where programs most often run short of the right people at the wrong time.
Conversion capacity underestimated
Conversion is planned as a single pass, then multiple mock conversions and reconciliation cycles reveal far more work. Adding conversion analysts mid-program is slower than staffing the effort realistically up front.
Technical developers scarce with long lead time
OUAF and platform-framework developers are a small talent pool. Waiting until the build phase begins to open these roles typically costs weeks of schedule against a fixed go-live date.
Testing under-resourced late in the program
Test leads and testers are often added only once SIT starts, so test strategy, script coverage and defect triage lag. The result is a compressed UAT window and unresolved defects entering cutover.
Production support not planned before go-live
Implementation consultants roll off quickly after cutover, leaving the utility to stabilize the platform without the people who configured it. A support model staffed before go-live avoids a knowledge cliff.
Engagement models
Contract, contract-to-hire and full-time across every model below.
Individual specialists
A single senior consultant filling a defined gap (a rates analyst, a conversion lead, a framework developer), embedded into your existing team.
Blended teams
A group of consultants supplementing a system integrator or internal team, adding capacity in a specific workstream without changing program ownership.
Full project teams
Functional, technical, conversion, integration and quality roles staffed together, coordinated through a single point of accountability at Mako.
Post go-live support staffing
Production support and stabilization resources who carry configuration knowledge past cutover and clear the post-go-live defect backlog.
Why program leaders work with Mako
Senior consultants, fast turnaround and nationwide reach.
- 48-hour submittal turnaround
- Senior consultants
- Contract, contract-to-hire and full-time
- Coverage nationwide across all 50 states
- Single point of accountability for blended and full teams
- Headquartered in Jupiter, FL
Utility CIS implementation staffing questions
What roles are needed for a utility CIS implementation?
Most programs need a functional workstream (billing, rates, credit and collections, customer service), technical developers for framework configuration and extensions, a conversion team for legacy data, integration engineers for metering, payments and ERP interfaces, a quality workstream for SIT and UAT, and program roles including project management and a cutover manager. Smaller utilities often combine roles, while large programs staff each workstream separately.
How long does a utility CIS implementation take?
It varies widely with utility size, customer count, rate complexity, the number of integrations and whether the program is a conversion or a greenfield build. Multi-year timelines are common for large investor-owned utilities, while municipals and co-ops with simpler rate structures often run shorter programs. We plan staffing around your schedule rather than quoting a fixed duration.
Can you staff an entire CIS project team?
Yes. We place individual specialists into a defined gap, blended teams that supplement an existing systems integrator, or a full project team across functional, technical, conversion, integration and quality workstreams.
Do you provide consultants for CIS conversions specifically?
Yes. We staff conversion leads, data migration analysts, mapping and mock-conversion support, and reconciliation resources who validate balances, usage history and customer records between legacy and target systems.
Do you staff post go-live CIS support?
Yes. We provide production support and stabilization roles, including functional analysts, batch and billing support and technical developers. We recommend planning these roles before go-live rather than after, since implementation consultants typically roll off quickly.
Related
- Oracle CCS staffingThe cloud-delivered platform where most new CIS implementations now start.
- CC&B vs C2M vs CCSHow the Oracle product generations differ and what each demands of a team.
- The hardest utility ERP roles to fillWhere searches stall and why.
- Utility CIS program staffing risksThe six triggers behind mid-program staffing calls.
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.