Choosing a CMMS: 12 questions to ask vendors

Twelve questions separate real CMMS contenders from glossy demos. Bring this list to every vendor call. Anyone who deflects more than two of them is not the right partner for a water or wastewater utility.

The vendor market for water utility CMMS platforms has never been more crowded. There are more than 60 products with a water and wastewater case study on the front page and every one of them is competent enough to demo well. Where they differ is in the last 20 percent of the workflow, the part that only becomes visible once real crews are using the system on real assets. This guide gives you the 12 questions that surface those differences before you sign.

Why these twelve questions

The questions below were curated from the recurring failure modes reported in Water Research Foundation post implementation reviews and the vendor evaluation checklists published by the Association of Metropolitan Water Agencies. They are ordered by how much a wrong answer will cost you over the life of the platform. The first three questions can end a vendor evaluation on the spot; the last three are refinements between finalists.

Question 1: how do you model duty and standby assets?

Water and wastewater utilities are built on duty and standby redundancy. Every pump, blower, generator, chlorinator, and filter has a hot standby waiting. A CMMS designed for a factory floor typically has no concept of this: it treats every asset as an independent object with its own runtime, its own PM schedule, and its own downtime record. On a pumping station, that means the platform cannot answer basic questions like "which pump ran during last night storm" or "when did the standby last exercise for at least 10 minutes".

The right answer includes a duty and standby group concept, runtime accumulation across the group, automatic rotation scheduling, and a report that surfaces standby pumps that have not exercised in the configured window. Anything less and the platform will need custom development to model the reality of a water utility.

Question 2: what happens when a technician loses signal mid work order?

A lot of water utility assets sit in valve chambers, below ground vaults, or at remote lift stations without reliable cellular coverage. The correct behaviour when the technician loses signal is that the mobile app continues to work locally, the technician completes the work order with photos, and everything syncs the next time the tablet reaches wifi or cellular. The failure mode you are testing for is silent sync loss, where the tablet believes the work order is closed but the server never received the update.

Question 3: how do you ingest SCADA data for condition based maintenance?

Condition based maintenance is where CMMS platforms deliver their biggest reliability wins, and it requires the platform to consume real time signals from SCADA. The right integration model is either an OPC UA subscription (industry standard, secure) or an MQTT broker with topic mapping. Simple polling via REST is acceptable for slow signals like runtime hours but fails on fast trending signals like vibration or amperage.

The International Society of Automation maintains the OPC UA standard alongside the OPC Foundation, and it is now the default for industrial device to enterprise system integration. If the vendor cannot name their SCADA integration protocol without pausing, budget for third party middleware.

Question 4: can you generate a regulator ready inspection report?

Every water and wastewater utility spends a nontrivial share of maintenance labour on compliance evidence. The CMMS should be able to produce a PDF report showing all completed inspections for a specific permit condition over a specified period, with technician signature, timestamp, photos, and calibration certificates attached. Vendors that build reporting as an afterthought will demo a summary dashboard instead of an inspection report; that is not the same thing.

Ask for a sample of the report format used by a customer utility to submit evidence to a state EPA or environment agency. If the vendor cannot produce one, budget for the reporting layer to be developed after go live at your cost.

Question 5: itemise the total cost of ownership over 5 years

Vendor quotes typically show the licence line and leave everything else vague. The reality is that year one costs include implementation, data migration, integration, mobile devices, and training, and ongoing costs include subscription, add on modules, integration maintenance, and internal staff time. Get every line in writing before signing.

Question 6: give me three water utility references at my scale

Every vendor has a case study page. What you want is three named contacts at utilities with similar staff count, similar asset count, and similar sector. If the vendor cannot produce three references without a delay, they do not have the water utility depth to be your platform. Reference calls should ask three questions: what would you do differently, what does the vendor bill for that you did not expect, and would you buy the platform again.

Question 7: show me the audit trail on a closed work order

Regulators and auditors will eventually ask who changed what and when. The audit trail on every work order should be immutable, timestamped to the user, and exportable as a report. If a supervisor can quietly change a closed work order without an audit trace, the platform will not survive a serious audit. This is a live demo request, not a marketing question.

Question 8: what security certifications do you hold, and can I see the last penetration test report?

For hosted CMMS, the minimum baseline is SOC 2 Type II or ISO 27001 with a current pen test report available under NDA. The CISA water sector cybersecurity guidance now expects utilities to hold vendor risk assessments on any platform touching operational data. If the vendor cannot share a redacted pen test summary, they are not ready for water sector customers.

Question 9: how do I get my data out?

Every hosted CMMS should allow you to export your complete asset register, work order history, PM schedule library, and inventory in an open format (CSV, JSON) on demand or on schedule. If the answer is "we can do a custom export for a fee", that is a vendor lock in signal. Real platforms provide native export as part of the standard subscription.

Question 10: what does support actually look like at 02:00 on a Saturday?

When a lift station is spilling and the CMMS has locked up, the response time on support determines whether the utility gets back online in 30 minutes or 6 hours. Ask for the support tier definitions, the response time SLAs, the after hours contact path, and the escalation matrix for a severity 1 incident. Then ask for two references who have used the after hours support.

Question 11: describe the ideal implementation, and what typically goes wrong

A confident vendor answers this in five minutes with specifics. The good answer is a phased approach starting with one plant or region, covering the seven modules in a specific order, with clear go live criteria and post go live optimisation cycles. The failure modes they name will tell you where their delivery team has real experience. If the answer is generic ("we work with you closely to configure the system to your needs"), the delivery team is small.

Question 12: what does the exit look like if we choose not to renew?

Nobody enjoys asking this question in year one, but it is a critical test of the vendor character. The correct answer is a data export in an open format, a documented offboarding process, and a courteous handoff to whichever platform the utility chooses next. Vendors that punish exit through data hostage taking or last minute fee increases are common enough that you should ask this in writing.

Common red flags in a vendor demo

Beyond the twelve questions, the following patterns in a demo should raise the level of scrutiny significantly.

• Salesperson insists on running the demo instead of the technical product lead.
• Demo environment cannot show 10,000 assets or 50,000 work orders (real utility scale).
• Refusal to run a live import from a spreadsheet you provided in advance.
• Marketing collateral that mentions AI or predictive maintenance but demo shows no such feature.
• Pricing quoted per user rather than per named user or per asset (usage patterns will surprise you).
• Contract renewal clauses that auto increase 8 percent per year without a cap.
• Data residency answer that cannot name the region or hosting provider.

Scoring vendors against the twelve questions

A repeatable scoring rubric keeps the evaluation defensible. Score each question 0 to 3 (0 no answer, 3 demonstrated live). Weight the top 6 questions double because they represent the highest risk lock in decisions.

Any vendor scoring under 40 out of 63 is not a serious contender. Vendors scoring 45 or higher can be advanced to a paid proof of concept before signing the multi year contract.

The paid proof of concept

The single most valuable step in a serious CMMS evaluation is a paid proof of concept covering one plant or region for 60 days. It is paid because free trials get half hearted attention from both sides. It is 60 days because the fake enthusiasm of week one wears off by week four, and the real assessment happens in the second month.

The proof of concept scope should include: full asset load for the pilot site, PM schedule migration, 5 named users in production use, one working SCADA integration, and one regulator ready inspection report. Success criteria should be documented before starting: user adoption target, work order throughput target, and integration reliability target.

Contract terms that matter more than the price

Once you have chosen a vendor, the contract is where lock in gets baked in. Insist on the following language before signing.

Frequently asked questions

Summary

Vendor selection is the highest leverage decision in a CMMS journey. The twelve questions above cover the failure modes that damage utilities most: shallow asset models, unreliable mobile, integration gaps, thin reporting, hidden costs, and vendor lock in. Score every vendor the same way, weight the foundation questions, and refuse to sign without a paid proof of concept and a contract that protects your data and your ability to leave.

Next reading

• What is a CMMS for water utilities?
• Implementing CMMS in a wastewater plant: a 90 day playbook
• Mobile CMMS: why field crews adopt it or do not
• CMMS vs EAM: which one does a water utility actually need?
• Browse the wastewater plants directory for the kinds of assets your CMMS will manage.