When to water, how much, and where.
One irrigation number per plot, per day, from your weather, your moisture readings and the stage the crop is in. The weekly build becomes a review.
Most irrigation programmes are built by hand once a week: depth and duration per variety, coefficients applied plot by plot, evapotranspiration averaged from last week. The crop’s water need changes every day. Your programme should too.
That build costs the irrigation manager hours every week, most of them on arithmetic. ORTH does the arithmetic daily and drafts the table. The manager reviews, corrects and sends.
The irrigation arithmetic, done every day on every plot.
Six things ORTH works out before the irrigation manager opens the table.
Evapotranspiration, every day
Reference evapotranspiration is taken from your nearest station or the hyperlocal feed each day. A hot, windy day and a cool, overcast one get different numbers. Last week’s average is gone.
The coefficient for the stage the plot is in
ORTH multiplies evapotranspiration by the crop coefficient for your crop at its current stage: bud break, flowering, fruit set, veraison or full canopy. Every plot moves at its own pace, and its coefficient moves with it.
The water already in the ground
Moisture readings at the depths you have them, root-zone depletion and the holding capacity from your soil analysis set how much of today’s demand the ground already covers. ORTH replaces what the crop has used.
Depth and duration per plot
The number comes back as millimetres, then as minutes on your system: drip, micro-sprinkler or pivot, at your emitter flow and spacing. The pump crew gets a duration per plot, per shift.
Water chemistry and salinity
Your water analysis feeds the plan: EC, pH, sodium and chlorides. On saline water ORTH adds the leaching fraction to the schedule and flags the blocks where salts are building in the root zone.
Plan versus applied, all season
Applied volumes logged by the crew sit against the plan per plot and per farm. Over-watering and under-watering show up in the week they happen, in cubic metres per hectare next to the plan.
One irrigation number per plot, from the weather station to the pump.
Five steps, run every day on your plots. The irrigation manager makes the final call.
Set the plots up once
Enter each plot with its crop, variety, planting date, irrigation system and soil. Reference evapotranspiration comes from your nearest station or the hyperlocal feed. Moisture readings come in at the depths you have them, surface and root zone, logged from the field or uploaded from your sensors.
ORTH counts the water need daily
ORTH takes evapotranspiration, the crop coefficient for the plot’s current stage and the water already in the ground, and returns a depth and a duration per plot, per day. An almond block at full canopy and one in dormancy get different numbers; so do a citrus orchard in fruit set and a table-grape block at veraison.
Review, correct, send
The programme arrives as a draft table. The irrigation manager checks it against the field, corrects a plot, and sends it to the pump crew as assigned actions with a name and a time on each.
Log what was applied
The pump crew logs applied volumes against the plan as the work happens. Plan versus applied is visible per plot and per farm all season, with no file to assemble afterwards.
Get an alert when a plot drifts
A plot losing more than the plan puts back, a dry spell coming, a reading out of range: ORTH alerts the right person in the morning, in time to act that day.
Less water, and the hours back.
Less water, fewer hours on the programme, and plan versus applied visible all season.
Less water, from counting evapotranspiration every day against your moisture readings instead of averaging it once a week.
The weekly irrigation build arrives as a draft table. The irrigation manager corrects and signs in minutes, and the hours go back to the field.
Of surveyed growers use ORTH for water and irrigation. On olive it is the first thing they bring, ahead of crop protection.
The weekly irrigation build became a sign-off.
Every week the irrigation manager built the programme by hand: depth and duration per variety, per shift, coefficients applied plot by plot, half an hour on evapotranspiration averaging alone. ORTH now counts it daily and drafts the table. He reviews, corrects and sends. The operation reports more than 15% water saved.
The forecast turns on Wednesday. The table turns with it.
A heatwave is forecast from midweek on a table-grape block at veraison. ORTH raises the plot’s daily depth from Wednesday, shows the root-zone readings that justify it, and flags the two plots already at field capacity where no extra water goes on. The irrigation manager approves the revised table on Tuesday evening. The pump crew gets the new durations in Wednesday’s brief.
What growers ask ORTH about water.
Typed or spoken from the row, in your language. Answered from your plots, your weather, your analyses and your protocol, with the working shown.
Request a demoRun it as a team, or as a group.
Pick the plan that matches how you farm.
-58.png){kind=icon}
For a farm or a grower organisation.
Everyone on the operation works from the same plot record.
- The irrigation table drafted every day. The pump crew logs what was applied.
- Team chats with ORTH on every plot.
- Actions assigned with an owner and a date. Field notes from the row.
- Packs from $5,000 a year. Live in days.
For a group, a network and its growers.
A private instance running your protocols on every farm.
- One irrigation programme across every farm, with plan versus applied on one dashboard.
- Your protocols behind every answer, on every farm.
- A private instance. Your data, exportable at any time.
- Validated by your own agronomists before rollout.