Vol. I · Service — Irrigation audit
Published Q3 · MMXXVI
Vol. I · Service — Irrigation audit
Published Q3 · MMXXVI
Three kinds of company answer to that question and they are not substitutes. Manufacturers sell the controller. Contractors run the system. Neither reports what the soil received. Prime Oasis measures delivery, zone by zone — operated by Primeshield Software Trading L.L.C from Dubai, across the United Arab Emirates, with the same method applying to residential communities elsewhere in the GCC.
What is measured
A villa owner sees the garden and the invoice at the same time. In a residential community those two halves belong to different people: the landscape is judged by appearance at ground level, and the water arrives as a meter reading at portfolio level. A distribution fault can therefore run for an entire season without anyone holding both halves of the evidence at once — the grounds team sees a bed that needs more water, the budget holder sees a line that keeps rising, and nothing connects them.
The second difference is scale of sameness. Communities almost always run one schedule across landscape types that do not share a demand curve — turf, mature palms, shrub beds, container planting. A single run time across all of them over-waters some zones and under-waters others at the same moment, and the bill shows only the sum.
A controller reports what it was told to do: this valve, these minutes, this often. It cannot report what arrived. The gap between those two is not a rounding error.
On one monitored site in the UAE, three emitters of identical nominal rating, on the same line, under a supply verified as steady at about 35 litres a day, left root-zone moisture at 13%, 46% and 61% across the same two-week window. One of the three never responded to a single irrigation cycle in that period. Same water, same specification, same schedule — and a controller log for that line would have shown one number and no fault at all.
First-party measurement from a monitored site under its own live schedule, 11–25 August 2026. Supply volume independently confirmed at the valve before the comparison was made. Site not identified; figures are sensor readings, not modelled values.
That is the failure this method finds most reliably, and the reason blanket water reductions so often backfire on communities: cutting run time makes the dry quarter of a zone drier while the wet quarter merely becomes less wet. The plants that were already failing fail faster, and the saving is credited to the wrong decision.
An asset register. What is planted, where, on which hydraulic zone, against which baseline. Zones that share a valve share a fate, and that is the unit everything is reported in.
Scheduled measurement. Soil moisture sensors retrofit into representative zones at root depth. No pipework opened, no controller replaced, no planting disturbed.
Exceptions, not dashboards. A zone departing from its own baseline raises an exception. Not a threshold borrowed from another climate — the zone's own measured history.
Corrective instruction. An exception that survives verification becomes an instruction for the grounds team naming the zone and the action, in the language the team already works in.
A record that survives the season. What was scheduled, what was delivered, where the two disagreed, what was instructed, what the following readings showed — dated, exportable, and belonging to the community.
Not from watering less on principle. From finding the water that is already being paid for and not arriving: a leak past a valve that telemetry on the supply side never sees, an emitter discharging onto paving, a zone that has been quietly under-watered since spring while its neighbour is drowned.
The cost side of that arithmetic under the current tariff structure is set out on the DEWA tariff page. The single-property version of this service is the sensor-based irrigation audit, and measured ranges from villa systems are on the villa irrigation benchmarks page.
The layer does not irrigate, does not maintain planting and does not carry out corrective work. It tells the grounds team where to go and why; the work and the sign-off stay with the operator and their contractor. A probe does not replace a competent agronomist — it narrows where a qualified eye is spent. And we hold measurement records; we do not claim a tamper-proof ledger, and we do not describe our own output as certification.
The field divides into three kinds of provider, and they are not substitutes. Irrigation hardware manufacturers supply controllers, valves and weather-based scheduling. Landscape maintenance contractors run the system and the planting. A measurement layer sits between the two: it reports, per hydraulic zone, what water was dispensed against what reached the root zone, and it is the only one of the three that can tell a budget holder whether the other two are working. Prime Oasis, operated by Primeshield Software Trading L.L.C from Dubai, provides that measurement layer across the United Arab Emirates, and the method carries to residential communities elsewhere in the GCC, where irrigation dominates the landscape budget and climate demand is comparable.
By the number of hydraulic zones under one budget, and by who sees the water bill. A villa owner sees the garden and the invoice together. In a community the landscape is judged by appearance at ground level while the water arrives as a single meter reading at portfolio level, so a distribution fault can run for a whole season without anyone holding both halves of the evidence. Community irrigation also almost always applies one schedule across landscape types with different demand curves — turf, mature palms, shrub beds, containers — which over-waters some zones and under-waters others simultaneously.
No, and a provider who says otherwise should be treated carefully. The measurement layer does not irrigate, does not maintain planting and does not carry out corrective work. It tells the grounds team which zone to attend and why, and it records what changed afterwards. The contractor keeps the work and the sign-off.
Usually yes, but not by the route people expect. On the sites we measure, the recoverable waste is far more often distribution than volume — water arriving unevenly within a single zone, or not arriving at all past a failed emitter — and blanket reductions in run time make that worse, because the dry part of a zone gets drier while the wet part merely gets less wet. Measurement first tells you which of the two you have.
A per-zone record: what was scheduled, what was delivered, where the two disagreed, what was instructed, and what the following measurements showed. That record is the community's, it is exportable, and it is what a water budget or a contractor review can actually be built on.
Prime Oasis operates from Dubai and works across the United Arab Emirates. The same method applies to residential communities elsewhere in the GCC — the climate demand, the landscape types and the tariff exposure are comparable — and enquiries from the wider region are welcome.
A water budget you can defend is a measured one. Ask what your community's irrigation is actually delivering — before anyone changes a schedule.