Irrigation & Site Control
How to Choose a Commercial Irrigation Controller
A practical buyer's guide to controller capacity, offline operation, flow safety, sensors, serviceability, remote management, and lifecycle support.
A commercial irrigation controller should be selected around the property, hydraulic system, operating team, and consequence of failure—not only the number of stations printed on the enclosure. The right evaluation starts with what must keep working locally, what staff must be able to diagnose, and how the system will be supported years after installation.
Key takeaways
- ✓Document zones, pumps, master valves, sensors, water sources, operating windows, and future expansion before comparing products.
- ✓Confirm exactly what continues during an internet outage and how queued activity reconciles afterward.
- ✓Treat flow measurement, maximum runtimes, interlocks, and technician diagnostics as operational requirements rather than accessories.
- ✓Evaluate installation, training, replacement parts, software support, exports, and ownership of site data across the expected lifecycle.
Start with the property and hydraulic design
Count more than valve stations. Record water sources, point-of-connection capacity, pumps, master valves, pressure zones, wire paths, simultaneous-flow limits, soil and plant differences, weather exposure, and the people who operate or service the property. A campus with 40 stations and one shared pump has different control risks than four independent 10-station properties.
Expansion belongs in the initial design. Include spare outputs, field-input capacity, enclosure space, communication range, and a documented method for adding controllers or remote devices without rebuilding the operating model.
- Identify outputs that must never run together.
- Define maximum station and program runtimes.
- List critical alerts and who should receive them.
- Record seasonal, event-day, maintenance, and emergency operating needs.
Separate local control from remote convenience
Ask vendors to demonstrate what happens when internet service fails before, during, and after a scheduled run. Essential schedules, safety limits, manual control, and field interlocks should have a clearly documented local behavior. A mobile application is useful, but it should not be the only way a technician can stop water or diagnose an output at the property.
Remote management should add fleet visibility, reports, configuration workflows, notifications, and support access with appropriate permissions. Confirm how changes are authenticated, audited, queued, and reconciled so an old cloud command cannot create a surprise after connectivity returns.
Evaluate flow safety and field evidence
A flow meter becomes operationally useful when the controller can associate readings with the active hydraulic state. Expected flow ranges should allow learning, review, and adjustment rather than relying on one universal threshold. The response to abnormal flow may differ for a small deviation, a broken lateral, or unexpected flow when every station is supposed to be off.
Technicians also need evidence: commanded output, measured flow, pressure when available, current or wire-test results, sensor state, communication health, and a time-aligned event history. Clear evidence shortens troubleshooting and helps distinguish a valve problem from wiring, supply, sensor, or communication failure.
Compare lifecycle cost and support
Purchase price is only one part of cost. Include installation labor, communication subscriptions, replacement modules, training, seasonal programming, truck rolls, water loss, exports, cybersecurity maintenance, and expected support life. Confirm who owns the configuration and history and what happens if a subscription ends.
Before a portfolio rollout, run a field trial on a representative property. Test ordinary schedules, manual service, loss of internet, power recovery, sensor faults, abnormal flow, user permissions, exports, and controller replacement. Record acceptance criteria before the trial begins.
Frequently Asked Questions
Direct answers
How many irrigation stations should a commercial controller support?
Choose capacity from the documented property design plus reasonable expansion. Station count alone does not address pumps, master valves, sensors, simultaneous-flow rules, or multiple properties.
Should a commercial irrigation controller work without the cloud?
Essential schedules, safety rules, and local service functions should have documented outage behavior. Remote services can add visibility and coordination without being the sole control path.
What should be tested before a large rollout?
Test scheduling, manual control, flow exceptions, power and network loss, recovery, permissions, audit history, exports, technician workflows, and replacement procedures on a representative site.