If you’re on an RWA committee evaluating water automation vendors, you’ve probably noticed every pitch sounds roughly the same: “smart,” “AI-powered,” “save water and electricity.” The actual differences that matter for a multi-tower society rarely show up in the marketing copy — they show up when you ask specific questions. This is a practical checklist for a committee doing that evaluation.
1. What exactly is the per-tower or per-node cost, and what does it include?
Get the vendor to break down pricing per node (sensor/controller unit), not just a headline “starting from” number — confirm exactly how many nodes your specific society needs (this depends on your number of tanks and motors, not number of flats). Then ask explicitly what’s included in that price: hardware, installation, firmware updates, repairs and replacements should all be bundled in a subscription model — if any of these are billed separately, that’s effectively a hidden AMC by another name.
2. Is this a subscription (provider owns hardware) or a purchase (you own hardware)?
This matters for your committee’s approval process as much as the total cost. A subscription model typically requires no capital expenditure — it’s an ongoing operating expense, similar to how you already budget for a pump operator’s salary, and usually doesn’t need the same approval threshold as a capital purchase. A one-time hardware purchase requires upfront capital approval and puts the maintenance burden on the society after any warranty period ends.
3. What’s the minimum contract length?
Reasonable vendors offer short initial terms (commonly around 3 months) for standard society deployments — long minimum commitments (a year or more) before you’ve had a chance to evaluate real performance is a red flag, particularly from a vendor who’s confident in their product.
4. Who actually does the installation — your existing electrician, or a specialist visit every time?
A system genuinely designed for scale should be installable by your society’s existing electrician or maintenance staff after a single training session, not require a specialist technician visit for every tower or every future addition. Ask specifically how installation and any future expansion work in practice.
5. How does the system handle multiple towers and shared infrastructure?
This is where genuinely different architectures reveal themselves. Ask directly: does each tank need its own WiFi connection, or does the system use a shared gateway covering the whole site? For a multi-tower society, WiFi-per-tank means WiFi setup and troubleshooting per tank — a real ongoing burden. A gateway-based (commonly LoRa) architecture means one central setup covering the whole property.
6. What happens if the internet or gateway goes down?
Ask specifically whether motor automation continues working locally on each device if connectivity drops, or whether the whole system depends on a live internet connection to function at all. The correct answer is that basic on/off automation should never depend on connectivity — only remote monitoring should.
7. Can staff/committee members have different access levels?
For a society, you likely want maintenance staff to see and act on alerts, while the committee wants overview visibility, without giving everyone the same level of control. Multi-user, role-based access should be a standard feature, not an add-on.
8. Does it provide monthly reports the committee can actually use?
Ask to see a sample monthly report before signing anything — consumption data, savings estimates, and any alerts/incidents over the period. This is what you’ll actually present to residents to justify the expense, so it should be clear and usable, not a raw data dump.
9. What’s the referral/expansion path if this works well?
If your society is part of a larger complex or manages multiple properties, ask how pricing and onboarding work for additional sites — this affects whether a good pilot experience translates into an easy expansion, or requires renegotiating from scratch each time.
10. Can you talk to an existing customer, ideally a similar-sized society?
Any vendor confident in their product should be able to connect you with at least one reference customer of comparable scale. If they can’t or won’t, treat that as meaningful information on its own.
Putting it together — a simple comparison table
For your committee meeting, it’s worth building a simple table across these 10 questions for each vendor you’re seriously considering, rather than comparing headline pricing alone. The vendors that answer all 10 clearly and specifically, without vague marketing language, are usually the ones worth shortlisting.
Frequently asked questions
How long should the evaluation process realistically take?
For a straightforward mid-sized society, gathering answers to these questions from 2-3 vendors and comparing them typically takes 2-4 weeks, including a site visit from each vendor for an accurate quote.
Should the committee insist on a pilot before a full rollout?
Yes, where possible — a pilot on one or two towers before committing to the whole society is a reasonable ask of any vendor confident in their product, and it gives the committee real performance data before a larger decision.
Who should be involved in the evaluation beyond the committee?
Include whoever currently handles day-to-day water/motor management (existing pump operator or maintenance staff) in vendor conversations — they’ll spot practical installation and operational questions the committee might not think to ask.
