A practical 90-day rollout plan for CMMS at a wastewater treatment plant - asset register, work order workflow, mobile rollout, and the metrics that prove it worked.
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.
The first fortnight is not a software exercise. It is a scoping exercise. Pick one plant — not a region, not a utility-wide rollout. Define criticality classes with the operators in the room: a typical scheme is A (permit-impacting), B (service-impacting), C (nuisance). List the A and B assets only — usually 80–200 records at a treatment works, plus the lift stations within scope. Class-C assets can be loaded later.
Build the asset hierarchy as Plant → Process Area → Equipment → Component. Resist the urge to go six levels deep on day one; the most successful deployments use 3–4 levels and refine later. Each asset gets a unique tag, manufacturer, model, install date, criticality class, and parent location. That is it for week one. Do not try to capture every nameplate datum — that is a year-two job.
Now the system starts producing work. Map the work-order lifecycle in the CMMS to match how the team actually operates: Request → Approve → Schedule → Assign → In Progress → Closed. Agree which fields are mandatory at close-out — at minimum: actual labour hours, parts used, failure cause, and a free-text note. Skip the temptation to make 15 fields mandatory — technicians will fake them.
Copy in the existing paper PMs. Almost every plant has a binder of recurring tasks; transcribe them into the CMMS at their current frequency, do not redesign them. The redesign happens in month four when you have data. Set frequency by time (weekly, monthly, quarterly), runtime where SCADA feeds it, or condition where you have it.
Parts week is physical. Walk the storeroom with the storekeeper and the maintenance planner. Barcode each bin location — cheap label printer, $200 of supplies. Count what is there. Match counts against issue records from the past 12 months to set min/max levels: min = average monthly consumption x lead-time months + safety stock; max = min x 2 to start.
Link parts to assets. The single highest-value action in the parts module: against each critical asset, list the spares it consumes. When a work order opens against pump P-4201, the technician sees the impeller, mechanical seal, and bearing-set part numbers at the top of the screen. That alone shaves 20 minutes per job.
Do not try to import a 5,000-line parts master in week one. Import the 500 parts that move; the rest follow as they get used.
Mobile is where adoption is won or lost. Hand a phone or rugged tablet to every field tech — not "we will share a couple". Pre-load the CMMS app, log them in, and verify offline mode works before they leave the office (most lift stations have terrible cell signal).
Run paired shifts for the first two weeks: each tech works alongside the implementation lead or planner, doing real work orders on the device. Do not run a classroom training session — it does not stick. Real work, real assets, real problems, with someone qualified at their elbow.
Track three adoption metrics daily during this phase: work orders opened on mobile (target: 70%+ by end of phase), work orders closed within 48 hours (target: 80%+), and proportion of close-outs with parts and labour fields populated (target: 90%+). Anything below these and the rollout is not landing — pause and fix before phase six.
By day 60 there is enough data for the first real reports. Agree what success looks like with the maintenance manager and the plant manager: pick three to five KPIs maximum. A typical wastewater starter set: schedule compliance (PMs completed on time as % of due), backlog hours (open work-order labour estimate), MTBF on critical pumps, emergency callout rate, and PM:CM ratio (preventive vs corrective work-order count).
Build the dashboard once, lock it, and put it on a wall display in the maintenance office. Resist the urge to build 30 reports — nobody reads them. Five charts that the team actually looks at every week beat fifty that get archived.
The final fortnight is about making the system operationally owned. Run a go-live retrospective with the implementation team, the maintenance manager, the planner, two or three field techs, and the plant manager. What landed, what did not, what needs fixing. Document it.
Hand over administration: someone on the utility's payroll needs to own the system. Usually the maintenance planner or a senior technician with the right temperament. They get admin rights, a documented set of routine tasks (user adds, PM tweaks, report changes), and a vendor support contact for anything bigger.
Plan the second site. The first site's lessons compress the second-site rollout to ~60 days. Do not start the second site until the first one is genuinely stable — usually 30 days post-go-live. The temptation to scale fast is the single biggest cause of stalled CMMS programmes.
Five failure patterns kill 90-day rollouts. Over-engineering the asset tree — six-level hierarchies with every component that has its own part number look thorough and become unusable. Importing legacy paper data wholesale — 10 years of paper work-order history transcribed into the new system is 10 years of garbage that pollutes every report. Capture the assets and the PMs; let the work history start fresh. No executive sponsor — without a director or operations manager unblocking budget and political fights, the rollout stalls at the first turf war. No data steward — if no single person owns data quality, the asset register drifts and within six months no two reports agree. Rolling out to the second site too early — covered above; worth repeating.
For the strategic context behind this playbook see the CMMS pillar guide; for the ROI numbers that will get this rollout funded see CMMS effectiveness and ROI at wastewater plants.