Operating workflow

From the field to a decision you can act on

How drone scans, field nodes, and irrigation sensors become a map and a record, with alerts planned — end to end.

Complete workflow

How data moves through IrrigTech

Every source in the field feeds the same pipeline, so a drone scan and a soil reading end up on the same map.

01

Field

Drone scans, field nodes, and irrigation sensors all cover the same physical field.

02

Data collection

Imagery and soil readings are captured and geotagged; flow and pressure data are planned inputs.

03

Transfer

LoRa, WiFi, or cellular carries data back — with store-and-forward sync where signal is limited.

04

IrrigTech Cloud

Readings and imagery are organized against the correct field and timestamp.

05

AI-assisted analysis

In development

Models flag anomalies and patterns worth a closer look — decision support, not a diagnosis.

06

Field map / dashboard

Results are laid over the field boundary so you can see where, not just what.

07

Alerts

Planned: thresholds you set per crop and zone will decide what's worth a notification.

08

Field record

Every scan and reading is attached to that field's permanent history.

09

Your action

You or your agronomist decide what happens next — inspect, irrigate, or treat.

Field Scanner Drone Prototype

Automatic scanning workflow

Once a field boundary is defined, repeat scans are planned to run on a schedule without a pilot in the field, once the workflow is validated.

01

Schedule

You set how often a field should be scanned.

02

Generate mission

A flight path would be generated from the stored field boundary.

03

Autonomous scan

The drone is designed to fly the mission and return when finished.

04

Data collection

RGB, and where equipped, multispectral or thermal imagery is captured and geotagged.

05

Sync

Imagery uploads to IrrigTech Cloud once connectivity is available.

06

AI-assisted analysis

Imagery is processed for anomalies, stress indicators, and change over time.

07

Field map

A geotagged map highlights areas that may be worth a closer look.

08

Alert

Significant changes since the last scan can trigger a notification.

09

Historical comparison

Each scan is stored against the field record, so trends build over time.

This workflow describes the Field Scanner Drone's design target. Autonomous mission generation and AI-assisted analysis are in development — ground verification is recommended before acting on any flagged area. See Hardware for current status.
Sensor monitoring Prototype

Nitrogen, tracked across the week

SAMPLE · FIELD 02 · NITROGEN (ppm)TARGET 30–45
41Mon
37Tue
34Wed
29Thu
24Fri
32Sat
38Sun

Illustrative sample only: a Friday dip below target would trigger an alert, and a top-up would bring nitrogen back into range by Saturday.

Chat on WhatsApp