Farm Land and Pivot Management
The Land and Pivot Map is the starting point for a farm review. It shows planted and resting pivots alongside orchard blocks, with views for crop, water and cost. Use it to locate an exception before opening the parcel behind it.
The example contains 200 pivots across 20 areas and 500 orchard blocks. A pivot represents an irrigated field circle; an orchard block represents a perennial planting area.
Before you begin
Agree the season and measure being reviewed: cultivated hectares, total hectares, water volume or allocated cost. Treat fallow land as a rotation decision unless the parcel record indicates otherwise.
Navigation: Top-right screen dropdown → Land & Pivot Map.
Procedure
- Review the planted and resting split. The example has 100 planted pivots and 100 resting pivots.
- Compare the 4,415 cultivated hectares with the separately reported 4,750 fallow hectares.
- Change the view selector to the crop, water or cost perspective needed for the review. Check the selected measure before interpreting the map.
- Select a pivot and confirm its hectares, crop, supplying well and current logical land.
- In the orchard view, select a crop to inspect its blocks. Compare bearing blocks separately from blocks still growing.
Responsibilities and follow-up
Pass the parcel or block reference to the team responsible for the exception. Use Parcel History for rotation and seasonal performance, Water Management for abstraction, and Cost Drill-Down for an unexplained charge.
Questions the map answers
| Question | Next screen |
|---|---|
| Why did this field cost more? | Parcel Record, then Cost Drill-Down |
| Why is this field resting? | Parcel history and rotation verdict |
| Which crops compete for water? | Water, Licence & Crop Mix |
| Which orchard blocks are declining? | Orchard Block Health & Replant |
Important notes
Zero water cost on idle land does not mean zero total cost. Area-based engine costs can remain in work in progress. The demo classifies blocks under four years old as growing; confirm the bearing-age rules for each crop in your implementation.
