A utility CIS implementation is defined as the structured process of deploying a customer information system, covering configuration, data migration, integration, and staff training, to replace a legacy billing or customer management platform. For a small water utility, a complete CIS implementation typically takes 12–24 weeks and does not require a large internal IT team.
When utility directors hear 'CIS implementation,' most assume a multi-year project requiring a dedicated IT department and a capital budget sized for a large municipal system. That assumption comes from years of exposure to enterprise utility software, platforms built for 500,000-meter systems and priced accordingly.
A customer information system (CIS) implementation at a small-to-mid water utility looks different. It involves five distinct phases: pre-implementation data preparation, system configuration and integration, data migration execution, staff training and process changeover, and go-live stabilization. Each phase has a defined scope, a realistic timeline, and clear handover criteria.
This guide walks through each phase in sequence: what it involves, what the utility's team needs to bring to it, and what goes wrong when it is skipped or rushed.
Before a single line of CIS configuration is written, the utility's data needs to be understood. This is the phase most small utilities underestimate, and the one most responsible for implementation delays.
A pre-implementation data audit covers four categories:
1. Customer account records - Are account numbers consistent? Are there duplicate accounts for the same service address? Are closed accounts clearly distinguished from active ones?
2. Meter inventory - Is every meter linked to an active account and a valid service address? Are there unregistered meters producing reads that go unmatched to a customer?
3. Billing history - How many years of history need to migrate? What is the data quality — gaps, anomalies, unresolved disputes?
4. Rate structures and fee schedules - Are current rates fully documented? Are exceptions (lifeline rates, agricultural rates, fire protection charges) recorded in a format the new CIS can ingest?
Alongside the data audit, stakeholder alignment must happen in the same window. The utility's Finance Director, Billing Manager, Field Operations lead, and IT contact all need to be available for the configuration decisions that follow in Phase 2. Decisions made without Finance's input — rate structure mapping, billing cycle timing, payment application rules, are the decisions that require expensive rework three months later.
A realistic data audit and stakeholder alignment phase runs three weeks for a utility of 10,000–30,000 meters with reasonably clean billing data. Utilities with legacy systems that have not been audited in years should budget four to five weeks.
1. Customer account records de-duplicated and active/inactive status verified across all service addresses
2. Meter inventory reconciled - every meter linked to an active account with a confirmed service address
3. Billing history completeness assessed - gaps flagged for archiving vs. migration before Phase 3 begins
4. Rate structures and fee schedules fully documented, including all grandfathered rates and negotiated exceptions
5. Stakeholder sign-off confirmed from Finance, Billing, and Field Operations before Phase 2 configuration begins
With clean data and aligned stakeholders, Phase 2 converts the utility's operational rules into the new CIS. The system is configured to reflect how this specific utility runs — not a generic template.
System configuration covers five areas:
Rate structure mapping translates the utility's existing rate schedules: tiered residential rates, commercial flat rates, agricultural exceptions, fire protection fees — into the CIS billing engine. This is the most consequential configuration work in the implementation. A mis-mapped rate structure does not announce itself until the first billing run produces incorrect charges for hundreds of accounts.
Service territory and account setup establishes the geographic and organizational structure of the utility in the CIS: service zones, meter routes, district assignments, and billing cycle calendars.
Workflow and routing rules define how service requests, work orders, and payment exceptions move through the system, who receives an alert when a high-usage anomaly is detected, which field technician is assigned to a given service zone, what the escalation path is for an unresolved billing dispute.
Payment gateway integration connects the CIS to the utility's payment processing provider, enabling online payments, IVR phone payments, and in-person cashiering from a single system record. SMART360 carries 25+ pre-built integrations with AMI systems, payment gateways, GIS platforms, and ERP systems — meaning integration work at this phase is configuration, not custom development. For a full list of supported integrations, see the customer information system software page.
AMI and meter data integration links the CIS to the utility's advanced metering infrastructure, enabling interval reads, tamper alerts, and consumption anomalies to flow directly into customer accounts and trigger automated service workflows.
Phase 2 runs four to five weeks for a standard implementation. Utilities with complex rate structures or multiple legacy integration points should budget an additional week for configuration review before moving to Phase 3.
Data migration overlaps with the tail end of Phase 2 — configuration and migration run in parallel to compress the overall timeline without sacrificing quality.
• Active customer accounts — full record including account number, service address, contact details, and account status
• Open service orders and active field work items
• 24 months of billing history for active accounts — the standard reference period for customer dispute resolution
• Meter inventory and device assignments
• Payment history for the current billing year
• Billing history beyond 24 months (archived to a read-only reporting environment, accessible but not in the active CIS)
• Closed accounts (archived with final bill records preserved for the utility's statutory retention period under applicable state PUC regulations)
• Historical work orders for completed jobs (archived, not migrated to the active service management queue)
• Legacy rate structures no longer in active use
During the migration window, a parallel-run period is critical — the legacy system and the new CIS run simultaneously for one to two billing cycles, with output compared at the account level to catch discrepancies before the legacy system is decommissioned. Utilities that skip the parallel run and cut over in a single billing cycle take on significant billing accuracy risk in their first post-go-live month.
Training is the phase small utilities most frequently under plan. The assumption is that if the system is configured correctly, staff will figure it out. This assumption produces the most common post-go-live failure mode: a billing manager who has not completed a full billing cycle in the new system before cutover.
Three staff groups require distinct training tracks:
Billing team training covers the full billing cycle from meter read import through exception management to bill generation and payment application. Training is not complete until the billing team has run a billing cycle end-to-end in a test environment — with real account data, producing output that can be reconciled against a known-good reference period. This typically takes two to three weeks of structured training plus one full test billing cycle.
Customer service representative training covers account lookup, service request creation, payment processing, and common exception workflows — disputed bills, returned payments, final bills. Standard duration is one week of structured training.
Field technician training covers work order receipt on mobile devices, field completion workflows, and meter data entry. For utilities using SMART360's AMI integrations, a significant portion of this workflow is automated — field technicians receive pre-populated work orders and submit completion data from a mobile interface. Training is typically two days.
The utility's go-live date should be set only after the billing team has completed their test billing cycle and signed off on output accuracy. Go-live pressure from an internal deadline or a vendor pushing to close a reporting period is the second most common source of implementation problems — after inadequate data preparation.
Go-live is not the end of the implementation. It is the beginning of the stabilization window — the period during which the system runs on live data while the implementation team actively monitors for issues.
Four metrics to track in the first 30 days:
Billing run accuracy — the percentage of accounts generating a bill within expected parameters on the first post-go-live billing cycle. A well-implemented CIS with clean migrated data should achieve high first-cycle accuracy. Exceptions should be monitored daily and resolved before the second cycle runs.
Customer call volume — inbound calls typically spike in the first two weeks post-go-live as customers encounter the new self-service portal and billing statement format. A spike of 15–25% above baseline is normal and should resolve by week four as portal adoption increases. A sustained spike beyond week four indicates a communication or portal usability problem.
Integration feed stability — AMI reads, payment gateway transactions, and any ERP data feeds should be monitored daily in the first 30 days to catch mapping errors before they compound across billing cycles.
Exception queue volume — the number of billing exceptions requiring manual review before a bill issues should decline week-over-week through the first month as rate structure configurations are confirmed. A stable or growing exception queue after week two indicates a configuration issue that requires immediate attention.
Utilities that complete the full five-phase implementation and stabilization period consistently report approximately 50% reduction in operational expenditure compared to their legacy system baseline, once automated workflows replace the manual processes that characterized their previous CIS.
A water utility CIS implementation takes 12 to 24 weeks from contract signature to a stable, fully operational go-live. That is the realistic range for a small-to-mid utility (3,000–100,000 meters) with reasonable data quality and a vendor that provides dedicated implementation support.
The factors that determine where a utility lands within that range:
Enterprise utility software vendors — the platforms built for large metropolitan systems — typically quote 12 to 18 months for a CIS implementation. That timeline reflects the complexity of their systems, the size of their typical customer, and the volume of custom development their implementations require. Small and mid-sized utilities that have received those quotes and shelved modernization plans are measuring against the wrong benchmark.
SMART360 completed the Island Water Authority's CIS implementation in 12 weeks — including data migration, integration setup, staff training, and go-live. The authority subsequently achieved a 47% reduction in operational costs in the 12 months following go-live. That implementation is documented in the
The pay-per-meter pricing model means a small utility pays for the meters it operates — not an enterprise license sized for a system ten times larger. For a 15,000-meter water utility, the pricing difference between a pay-per-meter CIS and an enterprise-license platform can be the difference between a modernization that gets funded this budget cycle and one that stays on the capital improvement wish list for another five years.
1. Starting Phase 2 before the data audit is complete. Configuration decisions — rate structure mapping, meter route assignments, billing cycle calendars — are built on the utility's data. If that data has not been audited and cleaned, the configuration is built on assumptions that may not survive first contact with a real billing run.
2. Going live before the billing team completes a test billing cycle. The only way to confirm a billing configuration is correct is to run a full cycle end-to-end in a test environment and reconcile the output against a known-good reference period. Utilities that skip this step consistently encounter preventable billing exceptions in their first live cycle.
3. Not involving Finance in rate structure mapping. Rate exceptions — lifeline rates, negotiated commercial agreements, agricultural concessions — live in Finance's contract files, not in the legacy CIS. If the Finance Director is not in the room during Phase 2, exceptions do not get configured, and the first billing run charges those customers on incorrect rates.
4. Treating data migration as an IT responsibility rather than a Finance and Billing responsibility. The staff who know whether a customer account record is accurate are the billing team who work with those records daily. IT manages the technical mechanics of migration. Finance and Billing must own the data quality decisions.
5. Choosing a vendor without a dedicated implementation team. A CIS configured by the utility's own staff against a documentation library is not a supported implementation — it is a self-service deployment. Small utilities without large IT departments need a vendor that assigns a named implementation manager, owns the project timeline, and takes accountability for go-live. SMART360's
6. The CIS implementation support model includes a dedicated implementation manager for every deployment — a standard inclusion, not an add-on charge. A pay-per-meter pricing structure that includes dedicated implementation support is the difference between a 12-week go-live and an 18-month ordeal.
A small-to-mid water utility (3,000–100,000 meters) can expect a CIS implementation to take between 12 and 24 weeks from contract signature to stable go-live. The primary variables are data quality, rate structure complexity, and integration requirements. Utilities with clean data and standard rate structures consistently reach go-live at the shorter end of that range.
The four categories requiring pre-implementation preparation are: active customer account records (de-duplicated and status-verified), meter inventory (reconciled to active accounts and service addresses), billing history (assessed for completeness and migration scope), and rate structures and fee schedules (fully documented including all grandfathered exceptions). This preparation is completed in Phase 1 — before system configuration begins in Phase 2.
Yes. Cloud-native CIS platforms are built for utilities without large internal IT departments. The utility's primary responsibility during implementation is data preparation and staff training — both led by Finance, Billing, and Operations staff. The vendor's implementation team handles system configuration, integration setup, data migration mechanics, and go-live coordination. The utility's IT contact is involved for network access and security approvals, not system build work.
Poor data quality is the leading implementation risk. A customer account database with duplicate records, unlinked meters, and undocumented rate exceptions will produce billing errors and customer complaints in the first post-go-live billing cycle. The solution is a structured data audit completed before Phase 2 begins — not a data cleanup effort run concurrently with go-live.
