A 90 day rollout puts a CMMS into productive use at a single wastewater plant. The playbook below is what works in the field, the version that has been beaten down by reality across small utility, mid utility, and contract operator deployments. Skip the steps and you are still onboarding 18 months later.
This is not a marketing timeline. Each phase carries specific deliverables, decision gates, and failure modes. If you are the utility engineer running the CMMS deployment, print this as a plan and hold every stakeholder to it. If you are the vendor or consultant, use it as the accountability structure.
Why 90 days
Shorter than 90 days and the utility side is unable to absorb the change. Longer than 90 days and momentum decays: enthusiastic crews grow sceptical, sponsors lose focus, and the platform drifts into shelfware. The Water Research Foundation post implementation studies consistently show 90 to 120 days as the sweet spot for pilot site go live at wastewater utilities.
The 90 day plan is not a full utility wide rollout. It is a single plant, single work order class, first release. Utility wide expansion follows in months 4 to 12 once the pilot has proven itself.
The three phases
| Phase | Days | Focus |
|---|---|---|
| Phase 1: Foundation | 1 to 30 | Asset load, user setup, PM library, initial training |
| Phase 2: Operations | 31 to 60 | Live work order flow, mobile deployment, compliance evidence |
| Phase 3: Optimisation | 61 to 90 | Reporting cadence, KPI baseline, expansion planning |
Phase 1 (days 1 to 30): Foundation
Week 1: kick off and access
Get the platform provisioned, admin accounts created, and the technical integration path confirmed. Deliverable: the utility team can log in, the vendor implementation lead is identified, the executive sponsor is on the invite list for the weekly review.
Week 2: asset load
Import the asset register from spreadsheet or legacy system. The clean up is where time gets spent. Expect to spend 60 to 100 hours cleaning asset data even if a spreadsheet exists. Missing tags, inconsistent nomenclature, duplicate rows, and dead assets all show up. Deliverable: asset register is loaded to production, hierarchical parent child relationships defined, criticality classifications applied.
Week 3: PM library
Load the top 100 PM templates. Cover the critical assets first. This is the source of the biggest reliability wins in year one and it is where the mistake of loading everything at once destroys momentum. Deliverable: PM library covers 80 percent of scheduled maintenance labour hours.
Week 4: user setup and training
User accounts for every operator, technician, supervisor. Role based permissions. Initial training session for each cohort. Deliverable: every named user can log in and complete a mock work order without help.
Phase 2 (days 31 to 60): Operations
Week 5: first live PMs
Turn on PM scheduling for one asset class (typically pumps). The scheduled work orders start flowing to technicians. Expect glitches: wrong technician assigned, wrong parts listed, wrong instructions. Fix in place; do not roll back. Deliverable: first 20 PMs completed on the platform with evidence captured.
Week 6: mobile go live
Field crews start using the mobile app to close work orders. This is the highest risk moment in the whole deployment. If the mobile experience is faster than paper, adoption sticks. If it is slower, adoption dies quietly. Deliverable: 70 percent of new work orders closed on mobile.
Week 7: compliance evidence
Compliance officer starts using the platform for scheduled inspections. Evidence attachment (photos, forms, sensor screenshots) becomes routine. Deliverable: at least one full compliance obligation cycle completed on the platform end to end.
Week 8: standby and reactive work
Standby pump exercise, corrective maintenance, and reactive work all start flowing through the CMMS. This is where the platform proves it can handle real operational chaos, not just planned work. Deliverable: at least 90 percent of maintenance labour hours are being logged in the CMMS.
Phase 3 (days 61 to 90): Optimisation
Week 9: KPI baseline
The platform now has 30 days of data. Baseline the KPIs (PM compliance, MTBF, MTTR, standby exercise rate, overtime hours). These become the reference point for future optimisation and for the year one ROI report.
Week 10: reporting cadence
Compile the first monthly reports: work order throughput, PM compliance, compliance officer report, plant manager dashboard. Verify the numbers agree with independent sources (payroll, ERP, laboratory information system).
Week 11: process refinements
Every deployment surfaces process gaps by week 10. Fix them: PM templates that were inadequate, user permissions that were too broad or too narrow, integrations that were flaky. This is the last chance before the platform stabilises into a steady state.
Week 12: expansion plan
Document what worked, what did not, and what changes for the next site. Confirm the rollout plan for the remaining plants, pumping stations, or business areas.
Pre work: what to have ready before day 1
Ninety days is tight if the utility arrives at day 1 without preparation. The pre work checklist below gets the deployment off to the fastest start possible. Complete asset inventory from the plant, drawings, and any legacy CMMS export. Named executive sponsor, programme lead, and field lead identified. Vendor contract signed and technical integration path documented. Server or SaaS environment provisioned. User list compiled with roles. Draft PM library from manufacturer manuals and existing SOPs. Mobile device order placed with delivery scheduled for week 4. Weekly review cadence booked on calendars through day 90.
The team structure that works
| Role | Utility side | Vendor side |
|---|---|---|
| Executive sponsor | Ops director or general manager | Vendor account executive |
| Programme lead | Maintenance manager or reliability engineer | Vendor implementation lead |
| Data lead | Senior operator or planner | Vendor data engineer |
| Field lead | Respected crew lead | Vendor customer success |
| Compliance lead | Compliance officer | Vendor SME (as needed) |
| IT lead | Utility IT (integration, security) | Vendor technical support |
Getting the asset load right
The asset load is the make or break deliverable of Phase 1. Do it in a structured way and it takes 60 to 100 hours. Do it under time pressure and it takes 300 hours plus re work.
- Extract the asset list from every source: spreadsheet, legacy CMMS, ERP fixed assets, plant drawings.
- Normalise the tag scheme. Every asset needs a unique tag that operators recognise.
- Assign parent child hierarchy: station, then pump, then motor, then impeller.
- Assign criticality (usually 1 to 5).
- Attach manufacturer, model, install date if available.
- Load to the CMMS as a test import, then production import.
- Field verify at least 10 percent of assets against physical labels.
Loading the PM library efficiently
Instead of loading a PM for every asset, load PM templates that apply to asset classes. A single "submersible pump PM" template can cover 40 identical pumps across the fleet. This is where good CMMS platforms show their value: template inheritance from asset class down to individual asset, with local overrides where needed.
| Asset class | Typical PM templates |
|---|---|
| Submersible pump | Weekly visual, monthly probe clean, quarterly amp check, annual bearing service, 8k hour major |
| Blower | Weekly visual, monthly filter check, quarterly vibration, annual bearing service |
| Clarifier | Daily blanket check, weekly weir check, monthly scraper inspect, annual mechanical |
| UV disinfection | Weekly transmittance check, monthly sleeve wipe, quarterly calibration, annual lamp replace |
| Instrument | Quarterly calibration, semi annual verification, annual reference standard check |
Training that sticks
Vendor training is necessary but not sufficient. The training that actually produces adoption is internal train the trainer, delivered by a respected crew member on the crew equipment, using real work orders on real assets. Vendor training builds the foundation; internal training builds the muscle memory.
Go live criteria
The 90 day playbook only works if the go live gates are clear and non negotiable.
- All named users trained and can log in.
- Asset register loaded and field verified 10 percent.
- PM library covers 80 percent of scheduled labour hours.
- Mobile app functional including offline mode.
- Compliance officer has attached at least one evidence set.
- Integration to ERP or SCADA at least one live data feed.
- Executive sponsor signs off Phase 1 deliverables.
Common failure modes
| Failure mode | Root cause | Preventive action |
|---|---|---|
| Asset load stalls | Asset data worse than expected | 30 percent contingency on load hours |
| Mobile adoption fails | Mobile app slower than paper | Test end to end mobile flow before go live |
| PM compliance stalls | Too many PMs loaded too fast | Load top 100 templates, expand later |
| Parallel paper flow | Supervisors do not enforce closure | Explicit kill of paper in week 6 |
| Compliance evidence missing | Compliance officer not integrated to team | Include in week 1 team from day one |
| Momentum decay | Weekly review skipped | Executive sponsor attendance mandatory |
Days 91 to 365: what happens next
The pilot site becomes the template for utility wide rollout. Typical cadence is one additional site per month, with lessons learned adjustments after each. By month 12, the CMMS is operational across the utility with a 2 to 3 site rollout still in progress at year end.
The other year one focus is data maturity. As the data set accumulates, condition based triggers become viable, predictive analytics become useful, and the ROI story matures. See our companion articles on CMMS ROI and preventive vs predictive maintenance.
Frequently asked questions
Is 90 days actually achievable at a small utility?
Yes, at smaller utilities the timeline can compress to 60 days because asset counts are lower.
What if we do not have a clean asset list?
Do the asset cleanup as part of Phase 1. It is a lot of work but pays back many times over. Delaying it does not help.
Should we start with pumping stations or the treatment plant?
Whichever has the highest failure cost. Usually pumping stations because they are distributed and unmonitored.
How many technicians should be in the pilot?
All of them at the pilot site. Selective adoption creates two classes of workflow and destroys the value.
What if the vendor is slow to respond?
Escalate to the account executive. If unresolved, invoke termination for cause. Vendors that cannot deliver Phase 1 will not deliver Phase 3.
Do we need to migrate historic work order data?
Only recent (12 to 24 months) for MTBF baseline. Older data is rarely useful and slows migration.
Can we do the 90 day playbook remotely?
Partially. The mobile go live and field verification need on site presence.
Should IT own the deployment?
Ops should own it. IT enables it. Reversing that ratio produces platforms optimised for IT convenience rather than operations reality.
What if we blow past 90 days?
Retrospect what went wrong before starting the next site. Do not repeat the same mistakes at scale.
Does the same playbook work for drinking water utilities?
Yes, with different asset classes. The phase structure and gates are identical.
Summary
A 90 day CMMS deployment at a wastewater utility is not a marketing story. It is a well proven playbook with clear phases, deliverables, and gates. Phase 1 loads the foundation. Phase 2 puts the platform into live operations. Phase 3 baselines KPIs and refines the process. Get the gates right and the pilot succeeds, becoming the template for utility wide rollout. Skip the gates and the deployment stalls, taking 18 months to reach the same point at three times the cost.
Next reading
- What is a CMMS for water utilities?
- Choosing a CMMS: 12 questions to ask vendors
- Mobile CMMS: why field crews adopt it or do not
- CMMS ROI at real wastewater plants
- Browse the wastewater plants directory
See the assets in this article
Explore 177,000+ utility infrastructure sites
Locations, capacity, operators, and permits across 24 sectors: the same records our writers pull from.
Start browsingMaintenance guides from the UtilityRadar team.