Agro-Tech Execution

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.

All five screens share one service file, src/services/agroTechExecutionService.ts, so most cross-screen hooks below are real read-modify-write calls against sibling records in the same file rather than simulated hand-offs. A few reach out to harvestSupplyInventoryService.ts and qualityCropHealthService.ts 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, pruning, each order (FOD-2026-XXXX) targeting a ProductionAreaItem field/greenhouse code.
• Order lifecycle — draft → scheduled → in_progress → completed → qa_on_hold, tracked via FieldOrderStatus badges.
• 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 (Employee.uid) and, optionally, an assigned equipment asset.

Integration triggers

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 — HSC-2026-XXXX, each linked to a TargetHarvestItem and a ProductionAreaItem.
• 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 by computeHarvestReadinessScore() 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 — preHarvestClearanceApproved and harvestLockoutActive 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

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 — IOT-2026-XXXX, each targeting a ProductionAreaItem and optionally an AgronomicSopItem.
• Sensor status — optimal, warning_dry_soil, critical_high_temp, 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 — computed by computeMicroclimateHealthScore(), 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 (IoTThresholdConfig) drive the automated triggers below.

Integration triggers

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 — YLD-2026-XXXX, linked to a harvest batch code, an optional harvest schedule, and a TargetHarvestItem.
• Quality grades — grade_a_premium, grade_b_industrial, grade_c_waste.
• Yield variance — computeYieldVariancePercent() compares actualYieldPerHa against targetYieldBaselinePerHa; 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

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 — CTR-2026-XXXX, resource types irrigation_water_m3, electricity_kwh, diesel_liters, natural_gas_m3.
• Counter status — normal, threshold_exceeded, possible_leak_overuse, uncalibrated.
• Net usage & quota — computeNetUsage() clamps previous-vs-current reading to a non-negative delta (so a meter rollover never reports negative usage); computeDailyQuotaPercent() shows percent of the daily limit allowance consumed.
• Leak/surge flags — leakFlagged and powerSurgeFlagged booleans, plus a photo-proof URL and last calibration date per counter.
• SOP cost attribution — each counter can be linked to an AgronomicSopItem so its usage cost rolls into that SOP's running cost basis.

Integration triggers

End-to-end data flow

Pages in this section

• Overview
• Operational Setup & Master Data
• Domain Roles & Capabilities
• Screen Workflows
• Quality & Crop Health Operations
• Agro-Equipment Maintenance
• Harvest & Supply Inventory

Frequently Asked Questions