
Buying ten smart valves and buying five hundred are not the same purchase.
At ten, almost anything works. Recurring fees are small enough to ignore. You remember which valve is which. If one needs attention, you walk to it. At several hundred, spread across parcels in different locations, every one of those small things turns into a system-level question — and the ones nobody asked about in the pilot are the ones that hurt.
This checklist comes out of a real procurement conversation with a 1,000-hectare vegetable operation in Europe planning a deployment of many hundreds of valves. Over several days they worked through the questions below before placing even a test order. The questions were good ones, and they generalise: any farm scaling past a pilot will eventually hit all six areas.
It is written to be used with any supplier, including us. Where there’s a right answer we’ll say so; where it genuinely depends on your farm, we’ll say that instead.
The six areas to settle before you order:
1. → Connectivity and the real long-term cost
2. → Parcel layout and network coverage
3. → Fitting your existing pumps and electrics
4. → Seasonal removal, storage and reinstallation
1. Connectivity and the Real Long-Term Cost
This is the first question because it’s the one with the largest hidden number attached to it.
Broadly there are two architectures. In a cellular (4G) setup, every valve talks to the mobile network directly — which means every valve carries its own SIM, and its own monthly fee. In a LoRaWAN setup, the valves talk to a gateway, and only the gateway needs an internet connection: either one SIM for the whole site, or an ethernet cable run from a router you already have.
At ten valves the difference is minor. At three hundred valves over a service life of eight to ten years, it is not. The arithmetic is simple and it’s worth doing on paper before you compare any two quotations: monthly fee × number of valves × 12 × service life. Run that number, and then compare it against the one-off cost of a gateway.
Ask your supplier
- Does every valve need its own SIM card, or only the gateway?
- Can the gateway reach the internet by ethernet cable instead of cellular?
- At what valve count does your recommendation switch from cellular to gateway-based?
- Is the software platform free, or is there a subscription or per-device annual fee?
- Does the price differ between the cellular and the gateway version of the same valve?
THE POINT — Hardware price is the visible number. Recurring connectivity and platform fees are the invisible one, and at scale the invisible one can be larger. Ask for total cost of ownership across the full service life, not a unit price.
For a full breakdown of how the two architectures differ in practice, see our detailed comparison: 4G vs LoRaWAN for irrigation.
2. Parcel Layout and Network Coverage
Large farms are rarely one continuous block. More often they’re a scatter of parcels across a wide radius — some clusters of five, some clusters of forty — and that geography, not the hectare count, is what determines your network design.
The critical thing here is to get an honest coverage figure, with both ends of the range. Gateway range is always quoted optimistically, because line-of-sight performance and real performance are different numbers. Ours, for example, is 1 to 4 km: up to 4 km with no significant obstruction, and a minimum of about 1 km in the worst case. Plan with the lower figure, not the higher one — a network designed around best-case range is a network that leaves parcels offline.
Ask your supplier
- What is the gateway’s coverage radius — best case and worst case with obstructions?
- How many devices can a single gateway support?
- Does one gateway serve every device type (valves, sensors, pump controllers), or does each type need its own?
- If a second pump station sits within range of an existing gateway, does it need another gateway?
- Can you help sector a scattered layout into gateway zones before we order?
THE POINT — Your parcel map, not your total area, decides how many gateways you need. Bring the map to the conversation and get the sectoring done before the order, not after the hardware arrives.
3. Fitting Your Existing Pumps and Electrics
This is the area where large farms most often get pushed into something they don’t want, so it deserves the most care.
Many established operations run star-delta starters and have deliberately chosen not to use variable frequency drives — often because of concerns about failure rates in demanding field conditions. It’s a legitimate engineering position. Any remote control proposal that begins with “first, replace your starters” is asking you to take on cost and risk that may be entirely avoidable.
The question to get to the bottom of is this: does the controller sit in the pump’s power circuit, or does it only supply a signal? These are very different things.
A controller that provides a potential-free (dry) contact doesn’t touch the power circuit at all. It simply opens or closes a contact, and that contact acts as the start/stop command wired into whatever control arrangement you already have. Because it never carries the motor current, it isn’t sized to your pump’s power rating — a 22 kW pump and a 75 kW pump take the same signal. Your existing starter, contactors and protection stay exactly where they are.
In practice, on a LoRaWAN system, the wireless side is handled by a DTU — the communication unit that receives the open/close command from the app and converts it into the physical relay action. One gateway serves the DTU alongside the valves and sensors, so a pump station within range of an existing gateway doesn’t need one of its own, though each pump does need its own DTU and relay set.
Two practical wrinkles worth raising early:
- Existing time-clock logic. If your star-delta arrangement is currently started by a timer, a remote command can be defeated by that timer — the controller closes its contact, but the clock hasn’t reached its own start time, so nothing happens. Either the timer logic is removed so the remote controller takes over, or a changeover switch is added so both modes remain available. This is a decision to make with your electrician before hardware arrives.
- Generator-fed pump stations. Once a generator is running, remote pump control behaves exactly as it does on grid power. The generator itself still has to be started, which limits how “unattended” that particular station can be.
Ask your supplier
- Does your controller interfere with the power circuit, or does it only provide a dry contact?
- Do we have to add a VFD or soft starter, or can our existing star-delta arrangement stay as it is?
- Is the controller sized to pump power, or is it power-independent because it only sends a signal?
- Can we keep manual or timer operation as a fallback via a changeover switch?
- What exactly does our electrician need to know before installation day?
THE POINT — A good remote pump solution adapts to your electrics; it doesn’t demand that you rebuild them. If the answer to “do we need a VFD?” is an automatic yes, ask why.
4. Seasonal Removal, Storage and Reinstallation
On a lot of farms — vegetables, cold-winter regions, rented ground — equipment goes out in spring and comes back in before winter, and next season it may not even go on the same field. Many suppliers have simply never thought about this cycle. It’s worth finding out early whether yours has.
The things that matter here are unglamorous but decisive:
- Do the antenna and solar panel detach? They’re the most awkward parts to transport and the easiest to damage. Being able to remove them and store them separately, in bulk, changes the whole logistics of a seasonal teardown.
- Does the energy storage survive a winter of sitting idle? This is a genuine question to ask about any powered field device. On our valves the answer is straightforward — but you should ask it of anything you’re buying: what state the device should be left in over the off-season, and what that does to its expected service life. Get a clear answer rather than an assumption.
- How are device identifiers marked? A printed label that fades in three seasons is a real problem when you’re trying to re-register two hundred units. Ask whether the QR code and serial are printed or laser-engraved — engraved markings survive the field.
- What happens in the software when a valve moves? If a valve goes back on the same spot, reinstallation is trivial. If it moves to a different field, it generally has to be unbound in the app and re-assigned on installation, or you end up with a naming scheme that no longer matches reality. Plan on unbinding units as part of the autumn teardown routine.
- Storage conditions. Normal careful handling and a dry indoor space is usually the whole requirement — but confirm it rather than assume it.
THE POINT — If your equipment comes off the field every autumn, that cycle is part of the product’s job. Ask about detachable parts, off-season storage, marking durability, and the app-side re-assignment procedure before you commit to hundreds of units.
5. Identification and Asset Management at Scale
Ten valves live in your head. Five hundred do not. Somewhere between those numbers, identification stops being a non-issue and becomes the difference between a system you can act on and a dashboard you can’t interpret.
The practical questions are about how a device on a screen maps to a physical location in a field. Most field valves have no GPS, which means the mapping comes from naming discipline, not from the hardware — and naming discipline is something you have to design, not something that arrives in the box.
This becomes concrete the moment something goes wrong. A pressure sensor raising an alarm is only useful if you can tell instantly which block it belongs to; that’s why sensors are generally fitted per valve rather than only at the pump, so a fault localises to a zone instead of to “somewhere on the farm.” Naming valves properly — “Field A, Zone 3” rather than “valve 47” — is what turns an alert into an action.
Ask your supplier
- Does each device carry a unique identifier, and is it visible without opening the unit?
- Can devices be freely named and grouped by field and zone in the platform?
- Is there GPS on the device, or does location come entirely from naming?
- When an alarm fires, what exactly do we see — a device ID, or a location we’ve defined?
- For a large batch, can you supply a list of all device identifiers so we can build an asset register before installation?
PRACTICAL TIP — For any deployment above a few dozen units, build a spreadsheet of device identifiers against intended field positions before installation day, and name devices in the app as you commission them. Doing it retroactively across hundreds of installed units is painful; doing it upfront takes an afternoon.
6. Theft, Damage and Spares
The last area is the one buyers raise late and regret raising late. On a large, distributed site, equipment sits unattended in open fields for months.
On theft, the question is less “can it be stolen” than “is it worth stolen.” Two things reduce the incentive: components that are only compatible with the system they came from have little resale value on their own, and devices bound to an account can’t simply be adopted by someone else — a unique identifier that has already been bound stays bound until it’s released. Ask specifically what happens to a stolen unit that was never unbound.
On damage, expect an honest supplier to tell you something slightly unflattering. In our own field experience, the most common damage isn’t electronic failure at all — it’s solar panels crushed by farm traffic. Actuators and valve bodies are robust; a flat panel in the path of a vehicle is not. That’s a positioning problem and a spares problem, not a quality problem, and it’s much better understood before deployment than after.
Which leads to spares. For a large site, holding a small stock of the most vulnerable parts — panels especially — costs very little and saves a season’s worth of waiting. Ask which parts fail most often in the field, and stock those.
Ask your supplier
- If a device is stolen while still bound to our account, can anyone else use it?
- Do accessories such as solar panels have any value or function outside your system?
- What is the most common cause of field damage you actually see?
- Which spare parts do you recommend we hold, and at what ratio to installed units?
- What is the lead time for replacement parts to our country?
Turning the Checklist Into a Decision
None of these questions has a single correct answer. A farm with one continuous block has a very different network design from one spread over a 30 km radius; a new-build pump station has different constraints from a twenty-year-old star-delta installation; a farm that leaves equipment out year-round has no seasonal teardown problem at all.
What the questions do reveal is something more useful than any spec sheet: whether the supplier has actually deployed at your scale. A supplier who has will answer the awkward ones directly — worst-case coverage, what really breaks in the field, what your electrician needs to do. A supplier who hasn’t will give you best-case numbers and change the subject.
HOW TO USE THIS — Send these questions to every supplier you’re evaluating, ours included. Compare not just the answers but the willingness to answer. On a deployment of several hundred units, the quality of that conversation predicts the quality of the project.
Frequently Asked Questions
What changes when you scale from a few smart valves to hundreds?
Three things stop being trivial: recurring connectivity cost, which multiplies by valve count over the equipment’s whole life; identification and asset management, since you can no longer remember which valve is which; and field logistics such as seasonal removal, storage and spare parts. A pilot of ten valves rarely exposes any of these, which is why they need to be asked about before a large order rather than after.
Should each valve have its own SIM card on a large farm?
It depends on the architecture. With cellular valves, each valve carries its own SIM and its own monthly fee, which multiplies quickly across hundreds of units and across an 8 to 10 year service life. With a LoRaWAN architecture, the valves talk to a gateway and only the gateway needs an internet connection — either a single SIM or an ethernet cable from an existing router. Ask any supplier to quote the recurring connectivity cost over the full service life, not just the hardware price.
Will a smart valve system force me to change my existing pump control?
It shouldn’t have to. Many farms run star-delta starters and deliberately avoid variable frequency drives because of reliability concerns. A remote pump controller that provides a potential-free (dry contact) output does not interfere with the pump’s power circuit at all — it simply closes or opens a contact that acts as the start or stop signal, leaving the existing starter arrangement in place. Ask whether the controller sizes itself to your pump’s power, or whether it only supplies a signal.
Can smart irrigation valves be removed each winter and reinstalled the next season?
Yes, and on farms in cold regions this is routine. The practical points to confirm are whether the antenna and solar panel detach for separate storage, whether the energy storage is damaged by sitting idle through a whole winter, how device identifiers are marked so they remain readable after years in the field, and what has to be done in the app when a valve is moved to a different field the following season.
What actually fails most often on a large smart irrigation deployment?
In field experience, the most common damage is not electronic failure but physical damage caused by farm traffic — solar panels crushed by machinery are far more frequent than actuator or valve body faults. This is worth asking any supplier about directly, because it determines what spare parts you should stock and how you position equipment relative to vehicle routes.
Working through this list for your own farm?
Go deeper on the topics above:
>>> 4G vs LoRaWAN: connectivity and cost · Choosing a remote pump control · The Complete Guide to Smart Irrigation Valves
The equipment referenced:
>>> Ball Valves · Butterfly Valves · Pressure Sensors · LoRaWAN Gateway
Planning a deployment above a hundred units?
>>> Send us your parcel map and pump details, or tap the WhatsApp button in the corner of any page. We’ll work through this list with you — including the parts where the honest answer is “it depends.”
This checklist was compiled from a real procurement conversation with a large European vegetable operation, shared in general terms only. AriValve builds solar-powered, motorized wireless smart irrigation valves deployed across 30+ countries.
