Agro-Tech Execution
From scheduled field task through IoT-driven monitoring, harvest scheduling, yield capture, and resource metering — the operational execution pipeline of a growing season.
What this group does
The Agro-Tech Execution group is the field-to-harvest operational pipeline for Agriculture & Agro-Tech Operations. It carries a production cycle from a scheduled field task through IoT-driven monitoring, season and harvest scheduling, yield capture, and resource metering — each screen writing real data forward to the next.
Field/Greenhouse Orders
→
Season & Harvest Scheduling
→
IoT Climate & Soil Monitor
→
Crop Yield Dashboard
→
Resource Counters
All five screens share the same underlying data store, so most cross-screen hooks below are real updates against sibling records rather than simulated hand-offs. A few reach into Harvest & Supply Inventory and Quality & Crop Health Operations for staging, consumption, WIP, and pre-harvest audit data.
1. Field/Greenhouse Orders
Purpose: Schedule and execute the four core field tasks — plowing, fertigation, pesticide spraying, and pruning — against a specific field or greenhouse, and log what actually happened once the crew is done.
Key features
- Task types — Plowing, Fertigation, Pesticide Spraying, or Pruning, each order (ID format
FOD-2026-XXXX) targeting a field/greenhouse code. - Order lifecycle — Draft → Scheduled → In Progress → Completed → QA On Hold, tracked via a status badge.
- Execution log — actual start/end times, fuel/energy consumed, operator observations, materials used (planned vs. actual rate per material), hours worked, and a crop-health-anomaly flag the field crew can raise directly from the execution form.
- Assignment — links the order to an assigned workforce member and, optionally, an assigned equipment asset.
Integration triggers
| Action | What it does |
|---|---|
| Sync order materials to consumption | On save when status transitions to Completed with materials logged: deducts the matching SKU's on-hand quantity in Agro-Input Staging and writes a consumption record into Agro-Material Consumption for each material used — see Harvest & Supply Inventory. |
| Update asset operating hours | Intended to roll logged hours worked into the assigned asset's cumulative operating hours to trigger Preventive Maintenance scheduling. Currently inactive — no maintenance screen exists yet in this add-on to receive the update (see Agro-Equipment Maintenance). |
| Flag crop-health anomaly | Intended to open an alert directly in Pest & Disease Alerts when the crew reports a crop-health anomaly during execution. Currently inactive, pending the alert store being wired up on the Quality & Crop Health side. |
2. Season & Harvest Scheduling
Purpose: Plan a crop's full season — planting through harvest window — against a target harvest and a target field/greenhouse, track milestones, and reserve downstream storage capacity.
Key features
- Schedule codes — ID format
HSC-2026-XXXX, each linked to a target harvest and a field/greenhouse. - Status lifecycle — Planned → Maturing → Ready for Harvest → Active Harvesting → Completed.
- Milestones — a checklist of dated milestones (label, target date, completed flag) tracked per schedule.
- Harvest Readiness Score — computed from accumulated Growing Degree Days (GDD) against a maturity target, blended 70/30 with soil moisture health.
- Silo reservation — a target silo and expected volume can be set on the schedule; reserving capacity calls into the Silo & Storage Management registry.
- Pre-harvest clearance gate — pre-harvest clearance and harvest lockout flags block harvest authorization until a Crop Health Checklist pre-harvest audit passes and any active PHI (Pre-Harvest Interval) window from Agro-Chemical Analytics has cleared.
Integration triggers
| Action | What it does |
|---|---|
| Sync schedule to WIP | When a schedule is locked in, instantiates an active crop-cycle batch (Germination stage) in Growing Crop Tracking WIP — see Harvest & Supply Inventory. |
| Reserve storage capacity | Adds the schedule's expected harvest volume to the target silo's reserved tonnage in the Silo & Storage Management registry — see the implementation note in Harvest & Supply Inventory. |
| Schedule pre-harvest quality audit | Dispatches a mandatory pre-harvest-audit inspection request into Crop Health Checklist, status Requires Attention, linked back to this schedule — see Quality & Crop Health Operations. |
3. IoT Climate & Soil Monitor
Purpose: Monitor live telemetry from field/greenhouse sensor nodes — temperature, humidity, soil moisture, EC, pH, VPD — and automatically respond when readings cross configured thresholds.
Key features
- Node codes — ID format
IOT-2026-XXXX, each targeting a field/greenhouse and optionally an agronomic SOP. - Sensor status — Optimal, Warning (Dry Soil), Critical (High Temp), or Sensor Offline.
- Telemetry fields — ambient temp (°C), relative humidity (%), soil moisture (%), soil EC, soil pH, VPD (kPa), battery (%), signal strength (%), last ping timestamp.
- Microclimate Health Score — comparing ambient temp/humidity/pH against the crop recipe's target growth-stage parameters.
- Configurable thresholds — per-node min/max bounds for temp, humidity, and soil moisture drive the automated triggers below.
Integration triggers
| Action | What it does |
|---|---|
| Trigger automated field order | When soil moisture drops below the node's configured threshold, generates an emergency Fertigation field order (status Scheduled) directly into Field/Greenhouse Orders' ledger — both screens share the same underlying data store. |
| Create maintenance work order | When a node pings offline or reports corrupt values, dispatches a hardware maintenance work order using the same shared maintenance-request mechanism already used elsewhere in TotalApp. |
4. Crop Yield Dashboard
Purpose: Capture the actual harvest outcome per batch — yield per hectare, quality grade, weighbridge reading, defects — and compare it against the target baseline.
Key features
- Yield records — ID format
YLD-2026-XXXX, linked to a harvest batch code, an optional harvest schedule, and a target harvest. - Quality grades — Grade A Premium, Grade B Industrial, or Grade C Waste.
- Yield variance — compares the actual yield per hectare against the target yield baseline; positive means the harvest outperformed baseline.
- Defect tracking — a list of defect entries (reason, percent of loss) plus an overall percent loss/waste figure.
- Weighbridge reading & silo receipt — actual tonnage from the weighbridge and a silo receipt certificate URL for the batch.
Integration triggers
| Action | What it does |
|---|---|
| Publish yield to traceability | Once a yield record is validated, generates a serialized lot (ID format LOT-2026-XXXX) directly in the Farm-to-Fork Traceability store, carrying origin field, harvest batch code, and a link back to this yield record — see Quality & Crop Health Operations. |
| Sync yield variance to target harvests | Folds the actual yield into Target Harvests' running machine-learning baseline average for that crop product. |
| Log inbound storage batch | Creates an unverified intake lot directly in the Silo & Storage Management registry when a harvest batch is reconciled — see Harvest & Supply Inventory. |
5. Resource Counters
Purpose: Meter utility consumption — irrigation water, electricity, diesel, natural gas — per field/greenhouse zone against a daily quota, and post the observed cost downstream.
Key features
- Counter codes — ID format
CTR-2026-XXXX, resource types Irrigation Water (m³), Electricity (kWh), Diesel (Liters), or Natural Gas (m³). - Counter status — Normal, Threshold Exceeded, Possible Leak/Overuse, or Uncalibrated.
- Net usage & quota — the previous-vs-current reading is clamped to a non-negative delta (so a meter rollover never reports negative usage); a percent-of-daily-limit figure shows how much of the allowance has been consumed.
- Leak/surge flags — a leak-flagged and a power-surge-flagged indicator, plus a photo-proof URL and last calibration date per counter.
- SOP cost attribution — each counter can be linked to an agronomic SOP so its usage cost rolls into that SOP's running cost basis.
Integration triggers
| Action | What it does |
|---|---|
| Post resource to material consumption | Posts the counter's net usage and total cost into Agro-Material Consumption's ledger, mapped to the matching source category (water/utilities, power/electricity, or fuel) — see Harvest & Supply Inventory. |
| Flag equipment/pipe leak | Dispatches an emergency maintenance work order ("Abnormal Utility Surge / Leak") using the same shared maintenance-request mechanism used by IoT Climate & Soil Monitor. |
| Recalculate SOP cost basis | Folds the counter's observed utility cost into the linked SOP's running cost-basis average. |
End-to-end data flow
| Source screen / action | Writes | Target screen / record |
|---|---|---|
| Field/Greenhouse Orders — Sync order materials to consumption | Deducts staging stock; new consumption record | Agro-Input Staging + Agro-Material Consumption |
| Season & Harvest Scheduling — Sync schedule to WIP | New crop-cycle batch (Germination stage) | Growing Crop Tracking WIP |
| Season & Harvest Scheduling — Reserve storage capacity | Increments reserved tonnage on target silo | Silo & Storage Management registry |
| Season & Harvest Scheduling — Schedule pre-harvest quality audit | New pre-harvest-audit checklist | Crop Health Checklist |
| IoT Climate & Soil Monitor — Trigger automated field order | New Fertigation field order | Field/Greenhouse Orders |
| IoT Climate & Soil Monitor — Create maintenance work order | New maintenance work order | Shared maintenance-request mechanism |
| Crop Yield Dashboard — Publish yield to traceability | New serialized lot (ID format LOT-2026-XXXX) | Farm-to-Fork Traceability |
| Crop Yield Dashboard — Sync yield variance to target harvests | Updates ML baseline yield average | Target Harvests |
| Crop Yield Dashboard — Log inbound storage batch | New unverified intake lot | Silo & Storage Management registry |
| Resource Counters — Post resource to material consumption | New consumption record (utility category) | Agro-Material Consumption |
| Resource Counters — Flag equipment/pipe leak | New maintenance work order | Shared maintenance-request mechanism |
| Resource Counters — Recalculate SOP cost basis | Updates SOP running cost basis | Agronomic SOPs |
Pages in this section
Frequently Asked Questions
Why does an emergency field order created by IoT Climate & Soil Monitor have no assigned workforce?
It's created with the workforce field left empty — a scheduling placeholder that still needs a human to assign a crew from Field/Greenhouse Orders before it can move past Scheduled.
Why doesn't logging a crop-health anomaly during field execution create an alert yet?
That escalation path is currently inactive — the anomaly flag is saved on the order's execution log, but the automatic alert into Pest & Disease Alerts is not yet wired up.
What is the Harvest Readiness Score based on?
A weighted blend: 70% from accumulated Growing Degree Days versus the crop's target GDD, and 30% from how close soil moisture sits to a 50% midpoint. It's computed live whenever the schedule's telemetry-fed fields change.
Can a harvest schedule be moved to Active Harvesting while a PHI window is still active?
No — the harvest lockout flag is set by Agro-Chemical Analytics whenever a Pre-Harvest Interval is still counting down on that field, and it blocks harvest authorization until the interval clears. See Quality & Crop Health Operations for the PHI mechanics.
Why does a resource counter reading never go negative even after a meter reset?
The previous-vs-current delta is clamped at zero, so a counter rollover or hardware reset is reported as zero usage for that reading rather than a nonsensical negative number.
Where does the material consumption cost logged from a field order actually get priced?
The consumption record is written with cost fields at zero — pricing is applied afterward in Agro-Material Consumption itself, which owns the ledger. See Harvest & Supply Inventory.