The strongest candidates combine a costly peak-demand constraint with storage or operating flexibility and a field system capable of validation.

Water scarcity alone does not tell whether a farm can benefit from lower peak hydraulic demand.

That distinction matters because irrigation decisions cross several boundaries: a water record becomes a physical delivery, a delivery becomes a hydraulic condition, and that condition becomes a root-zone response. A number at one boundary cannot automatically prove performance at the next.

The mechanisms to keep visible.

01

High lift or demand charges can increase the value of peak reduction.

02

A constrained delivery window can make buffering valuable.

03

Poor field condition, uncertain supply, or missing operator capacity can overwhelm the proposed benefit.

Turn the pain point into a defined operating question.

Screen for the constraint, adoption capacity, measurability, and economic consequence—not scarcity alone.

Start with the decision the analysis must support. Then identify the smallest set of inputs capable of changing that decision. Keep source facts, calculations, model outputs, estimates, and operator observations distinct throughout the workflow.

Make the result reviewable.

Combine regional layers with a site interview and field verification before assigning priority.

Define the boundaryName every input and unitPreserve source and timestampExpose assumptionsClassify the evidenceRecord missing information

What this analysis cannot establish by itself.

Opportunity scores rank questions for follow-up; they do not promise savings or adoption.

SIM treats an honest limitation as part of the result. Where evidence is incomplete, the correct status is inconclusive or unverified—not a more confident sentence.