Irrigation & water management

Why irrigation should be decided with data, not habit

Chile has carried over a decade of water deficit, and in zones like the Valparaíso Region it's water, not land, that caps production. Deciding irrigation by habit —"we always irrigate 3 hours on Mondays"— leaves 15 to 25% of water and energy savings on the table that can be captured with no impact on yield.

The problem isn't a lack of sensors —many farms already have them— but that the data lives scattered: moisture in one app, flow in another, electricity spend only when the bill arrives. Without a single view crossing crop demand, field readings and pump consumption, irrigation stays intuition with a spreadsheet.

The real problem (no marketing)

In most Chilean farms, water and energy are managed blind until something fails or the bill arrives. The breaking points repeat season after season:

The underlying cost is twofold: wasted water and over-paid energy, two line items that weigh on per-block costing and are rarely attributed to the right block. Without measuring water efficiency or electricity use per sector, irrigation is the most expensive black box on the farm.

How this module solves it

The module builds an irrigation schedule per sector from the crop's actual demand —evapotranspiration, or ETc, in millimeters per hectare— and contrasts it with live moisture, pressure and flow readings. ETc is computed from reference evapotranspiration and the crop coefficient:

ETc = ET0 × Kc

On that basis, irrigation stops being a habit and becomes a per-sector decision:

1. 01

   Schedule per sector

   The module proposes mm to apply per sector based on ETc, weather and soil rules, not the clock.

2. 02

   Live sensors

   Moisture, pressure and flow enter the same view with alerts when a sector drops below threshold or a pump runs out of range.

3. 03

   Efficiency and pumps

   It compares applied mm against demand and monitors kWh, hour-meter and BEP of each pump, with a savings diagnostic.

Regulated deficit irrigation stops being theory: you can apply less water in non-critical stages backed by data, and electricity use is allocated to the right block so cost per block reflects the real water and energy spend.

Integration with your current stack

Soil-moisture sensors already exist in many Chilean farms; the module doesn't ask you to replace them, but to bring their data into a single irrigation view. It connects to the platforms you already run:

Irrigation shares block, sector and season as master data with the rest of the platform, so the plant nutrition & health program —especially fertigation— reads from the same source, not a separate spreadsheet.

From data to savings in one season

In water-constrained zones like the Valparaíso Region or Chile's near-north, the 15-25% water and energy savings don't appear at once: they build over the season, tuning sector by sector as the crop's demand shifts. The module makes that curve visible instead of leaving it to intuition.

Early in the season the crop coefficient (Kc) is low and ETc demand is too; irrigating as if at peak production is pure waste. The module adjusts the depth per sector by phenology, so you apply less when the crop asks for less. In non-critical stages, regulated deficit irrigation lets you cut water deliberately, backed by sensors, without hurting yield and even improving quality traits like soluble solids.

The other front is the water nobody measures: leaks, sectors over-irrigating from a miscalibrated valve, inherited schedules nobody revisited. Alerts for moisture below threshold and flow out of range surface those blind spots in hours, not when the block already shows water stress.

At season close, the water and energy footprint isn't an exercise for the audit: it's the record of which sectors captured the savings and which are pending for next time. That season-over-season comparison, allocated to the block, is what turns irrigation from an assumed fixed cost into a margin lever that actually moves.

There's a benefit beyond the electricity bill: in a country where water is a contested resource and usage rights are under pressure, irrigating efficiently is also a license to operate. Export customers ask for sustainability reports, certifications assess resource use, and an operation that can show applied mm per hectare matched to demand arrives at those conversations with evidence, not good intentions. The same data that lowers cost backs the water story in front of the market — and that knowledge stays in the system, not in the head of an irrigator who one day leaves.

Metrics you'll move

The module moves two metrics that hit the margin directly: applied mm per hectare versus ETc demand (water efficiency) and kWh per cubic meter pumped (energy efficiency). On top of them sits the 15-25% water and energy savings the operation can capture without touching yield.

Each indicator enables a decision:

That consumption, allocated per sector, stops being a blurry monthly total and enters as real cost in the right block.