Automated Turf Irrigation Scheduling

Status: Research complete | ClickUp: 868hp9uzb

Overview

Automated scheduling engine that computes per-zone irrigation runtimes using QWEL formula chains (ETo → plant factors → distribution uniformity → runtime minutes), species-specific turf factors, and smart controller API integration.

Strategic Fit

Transforms the irrigation capability from static design to dynamic, ongoing management — the bridge from "design it" to "run it." Enables smart controller integration (Rachio, Hydrawise) for real-time schedule delivery.

TODO: Product Manager to expand with user stories and acceptance criteria.

Automated Turf Irrigation Scheduling from Design-Time Intelligence

ID: SS-RR-2026-002 | Date: 2026-03-01 | Status: complete ClickUp: Automated Turf Irrigation Scheduling from Design-Time Intelligence Plan: SS-RP-2026-002 Domain: Irrigation Management / Automated Scheduling

TL;DR

SimplyScapes already computes Distribution Uniformity (DU) and Precipitation Rate (PR) per zone from irrigation design geometry — values that normally require a $500–$2,000 catch can field audit. This research confirms that no product, patent, or academic paper anywhere connects design-computed DU to irrigation scheduling formulas. The gap is confirmed across 15 vertical competitors, 17 adjacent markets, 20 patents, and 37 academic references. Phase 1 implementation is straightforward: feed existing design-computed DU and PR through the standard QWEL formula chain (ETo × PF ÷ DU → runtime) with species-specific growing season thresholds, then push the resulting schedule to Rachio via its public API. All SmartRain patents require physical hardware; SimplyScapes' software-only approach has clear freedom to operate. Defensive disclosure covering 13 alternative embodiments should be filed promptly to protect this whitespace before competitors file on design-derived scheduling.

---

Part I: The Idea

1. What We're Exploring

SimplyScapes already computes two of the most expensive-to-obtain values in irrigation management: Distribution Uniformity (DU) and Precipitation Rate (PR) per zone, directly from the irrigation design geometry. Today those values sit idle after design time — displayed in the UI but disconnected from scheduling. The core idea is to close the loop: feed DU, PR, reference evapotranspiration (ETo), and plant factors (PF) through the standard QWEL formula chain to generate zone-by-zone irrigation schedules automatically.

The formula chain is straightforward:

ETo × PF = ETc (crop evapotranspiration)
ETc − Effective Precipitation = IWR (irrigation water requirement)
IWR / (PR × DU) = Gross Runtime
Gross Runtime / Time-to-Runoff = Cycle-Soak Splits
Monthly Runtime / Irrigation Days = Per-Event Runtime

What makes this novel is the DU input. Every existing scheduling tool — from Rachio's Flex Daily to HydroPoint's WeatherTRAK to a QWEL auditor's spreadsheet — assumes DU comes from a physical catch can test. A professional irrigator places 12–24 catch cans in a zone, runs the system for a measured interval, collects the water, and calculates the lower-quarter distribution uniformity (DULQ). This field audit is the single most expensive step in professional irrigation management, often costing $500–$2,000 per property.

SimplyScapes can skip the catch can entirely. The platform's irrigation design engine already knows exactly where every head is placed, its arc, radius, GPM, and manufacturer performance data. From this geometry, it computes DU — currently shown in the UI as values like 80% and 71% per zone. It also computes PR per head from manufacturer catalog data (e.g., 0.61"/hr for a Rain Bird R-VAN24). These design-computed values can feed directly into the QWEL formula chain.

The platform already has the other pieces in place:

• A Schedule tab showing Rachio controller integration with per-zone day and runtime settings
• A Water Budget tab computing MAWA vs. ETWU using EPA WaterSense 2.0 methodology
• Water district restriction alerts (Weber Basin Water Conservancy District rules displayed)
• Leak detection capabilities in the Manage tab
• A plant library with 2,500+ species, genus/species taxonomy, and water use classifications

The gap is the connection between design intelligence and scheduling. DU and PR are computed but don't flow into schedule calculation. The Water Budget (ETWU) is computed independently of the actual schedule. Bridging this gap with the QWEL formula chain turns SimplyScapes from a design tool into a design-to-operations platform.

Phase 1 implementation is deliberately simple: ETo-based formula chain using existing design-computed DU and manufacturer PR, standard plant factors from WUCOLS, and publicly available ETo data. No hardware sensors required. Works with the data SimplyScapes already has.

The research also explores advanced techniques — soil sensors, satellite ET, machine learning, predictive scheduling — for a comprehensive defensive disclosure that protects the full innovation space before competitors file patents in adjacent areas.

2. Why It Matters

The irrigation audit bottleneck is real. Professional irrigation auditing requires trained technicians, physical equipment, and on-site visits. A QWEL-certified auditor (the user is one) runs a catch can test, manually calculates DU and PR, then plugs those into a spreadsheet to derive schedules. The result is excellent — but the process doesn't scale. Most residential and small commercial properties never get audited. Eliminating the catch can through design-computed DU makes professional-grade scheduling accessible to every property with a SimplyScapes irrigation design.

Water conservation regulations are tightening. California's MWELO, Utah's statewide programs, and EPA WaterSense are driving demand for quantified water budgets. MWELO requires a Maximum Applied Water Allowance (MAWA) calculation for new landscapes — SimplyScapes already computes this. But MWELO compliance is backward-looking: "did you stay within budget?" Automated scheduling is forward-looking: "here's exactly how many minutes to run each zone this month to hit the target." The combination of compliance + scheduling is the full picture that water districts need.

Smart controllers are dumb about design. Rachio, Hunter Hydrawise, Rain Bird, and Orbit B-hyve all adjust watering for weather — but they operate in a vacuum. They don't know what heads are installed, what the coverage pattern looks like, or what the actual DU of the system is. A Rachio Flex Daily schedule uses default assumptions (DU typically 0.70 unless the user manually overrides it). A design-aware schedule uses the actual DU computed from the specific heads and layout. The difference in water accuracy can be 15–30% — enough to mean the difference between a healthy lawn and either drowning it or browning it.

Species-specific scheduling is unaddressed. EPA WaterSense 2.0 uses a universal 50°F Growing Degree Day threshold to determine the irrigation season. But cool-season turf (Kentucky bluegrass, tall fescue, perennial ryegrass) actively grows below 50°F — it thrives in 60–75°F air temperatures and continues growing as low as 40°F. Warm-season turf (bermudagrass, zoysiagrass, St. Augustine) goes dormant at soil temperatures around 55–65°F, well above the 50°F threshold. A universal threshold either waters dormant warm-season turf too long or starts too late for cool-season turf. Species-specific growing season determination has both practical and patentable value.

SmartRain is filing aggressively. Six patents or applications from a single inventor (Rudy Lars Larsen) cover irrigation management, landscaper integration, AI prediction, sensor grids, and map integration. All claims require physical hardware — controllers with flow meters, soil moisture sensors, GPS devices. SimplyScapes' design-time software approach appears outside their claim scope, but the patent velocity signals an active competitor who may expand claims. A comprehensive defensive disclosure before they file on design-derived scheduling protects this innovation space.

Nobody bridges design → schedule. The competitive landscape divides cleanly into three camps: controllers (Rachio, Hunter, Rain Bird, Orbit), management platforms (WeatherTRAK, Weathermatic, Calsense, ETwater), and design tools (Land F/X, IrriCad, SimplyScapes). The controllers schedule but don't know the design. The management platforms optimize but require expensive hardware. The design tools design but don't schedule. SimplyScapes is uniquely positioned to close this gap — it has the design data, the controller integration, and the water budget math already in place.

---

Part II: Research Findings

3. QWEL Formula Chain -- ETo to Runtime

The standard ET-based irrigation scheduling formula chain has six sequential steps, consistent across QWEL, MWELO, and the Irrigation Association's recommended practices. The chain converts atmospheric water demand into zone-specific runtime minutes with cycle-soak splitting.

3.1 The Six-Step Chain

Step 1: ETo                              (reference evapotranspiration, inches/month)
Step 2: ETo × PF = ETc                   (crop/landscape evapotranspiration)
Step 3: ETc − Pe = IWR                   (irrigation water requirement)
Step 4: IWR × SM = Gross Irrigation      (adjusted for distribution uniformity)
Step 5: Gross / PR × 60 = Total Runtime  (convert inches to minutes)
Step 6: Runtime / Cycles = Per-Cycle RT  (cycle-soak splitting)

Step 1 — Reference Evapotranspiration (ETo): The atmospheric demand for water, calculated using the ASCE Standardized Penman-Monteith equation from solar radiation, temperature, wind speed, and humidity. For SimplyScapes Phase 1, Open-Meteo is the recommended ETo source — it provides global coverage, free access with no API key, FAO-56 PM method, and both forecast and historical data. CIMIS (California only) remains the gold standard where available; gridMET covers CONUS at 4km resolution but has 12–31% overestimation bias vs. station data.

Step 2 — Crop Evapotranspiration (ETc): ETc = ETo × PF. Plant factors from SLIDE/WUCOLS: cool-season turf = 0.80, warm-season = 0.60. Monthly Kc values vary significantly — cool-season peaks at 1.04 in April, warm-season peaks at 0.79 in May. The MWELO alternative uses a composite landscape coefficient (KL = Ks × Kd × Kmc), primarily for compliance budgets rather than operational scheduling.

Step 3 — Irrigation Water Requirement (IWR): IWR = ETc − Pe. Effective precipitation (Pe) methods include: SLIDE 50% rule (Pe = P × 0.50), USDA SCS method, WaterSense monthly data, or Pe = 0 for arid climates. IWR cannot be negative.

Step 4 — Gross Irrigation: Gross = IWR × SM where SM = 1/DU (QWEL standard) or SM = 1/(0.4 + 0.6 × DU) (IA revised, caps over-application at low DU). At DU = 0.70, Method A yields SM = 1.43 while Method B yields 1.22. For SimplyScapes' design-computed DU range (0.65–0.85), the difference between methods is modest.

Step 5 — Total Runtime: Runtime = (Gross / PR) × 60. Precipitation rates vary by head type: conventional spray 1.3–2.0 in/hr, rotary nozzles 0.4–0.8 in/hr (R-VAN = 0.61 in/hr), gear-drive rotors 0.4–1.0 in/hr. PR is computed per-head from manufacturer catalog data using: PR = (GPM × 96.3) / Area.

Step 6 — Cycle-Soak Splitting: When PR exceeds the soil infiltration rate, runtime is split into cycles separated by soak periods. Time-to-Runoff = (Infiltration Rate / PR) × 60. For clay loam at 0.3 in/hr with R-VAN at 0.61 in/hr, time-to-runoff = 29.5 minutes — matching the user's observed 20-minute threshold for their system (calculated: 19.7 min when accounting for slope).

3.2 Worked Example: Orem, UT — July

For Kentucky bluegrass with R-VAN24 heads on clay loam, watering 3 days/week:

ETo = 8.50 in/month → ETc = 8.50 × 0.80 = 6.80 in/month
Pe = 0.50 × 0.50 = 0.25 in → IWR = 6.80 − 0.25 = 6.55 in/month
SM = 1/0.70 = 1.43 → Gross = 6.55 × 1.43 = 9.37 in/month
Events = 3 × 4.43 = 13.3/month → Gross/event = 0.70 in
Runtime = (0.70 / 0.61) × 60 = 69 min
Time-to-runoff = (0.30 / 0.61) × 60 = 29 min → 3 cycles × 23 min, 30-min soak

Schedule output: 3 cycles × 23 minutes at 4:00 AM, 4:53 AM, 5:46 AM, three days per week.

3.3 QWEL vs. WaterSense 2.0 vs. MWELO

The three methodologies serve different purposes: QWEL produces operational schedules (minutes per zone), WaterSense produces compliance budgets (annual gallons), and MWELO produces regulatory budgets (MAWA vs. ETWU). Only QWEL outputs actionable runtime values. SimplyScapes can bridge the gap by computing both the compliance budget (already implemented) and the operational schedule (the proposed feature), then reconciling them — showing whether the schedule stays within the MAWA budget.

3.4 Edge Cases

Nine edge cases require handling: zero-precipitation months (arid regions, Pe = 0), precipitation exceeding ETc (skip irrigation), very low DU (cap SM to prevent >3× over-application), mixed-species zones (use highest PF), extreme heat events (increase irrigation frequency), frost/dormancy transitions (ramp PF per species algorithm), wind effects on real-world DU, new turf establishment (2× PF for first 4–6 weeks), and water restriction compliance (cap days/week, increase per-event runtime).

Full reference: supporting/qwel-formula-chain.md — 33 sources, complete formula definitions, ETo source comparison matrix, Python cycle-soak algorithm, and detailed infiltration rate tables.

---

4. Design-Computed DU -- The Novel Mechanism

This is the core innovation. The research confirms that no prior art exists for the specific integration of design-computed DU into irrigation scheduling formulas. While both halves of the problem are well-established independently — DU simulation from design geometry (Domain A) and DU-based scheduling formulas (Domain B) — no existing system connects them.

4.1 How Field-Measured DU Works Today

The catch can test (ASABE S436.1, IA Audit Guidelines, QWEL Protocol) requires placing 24+ catch cans in a grid across each irrigation zone, running the system for 5–20 minutes, and computing DU_LQ as the ratio of the lowest-quarter average to the overall average. This costs $200–500 per residential property and requires wind below 5 mph, trained technicians, and a full day for 6–8 zones. Results vary by 5–10 percentage points across tests of the same system on different days.

Field-measured DU is consistently poor. Baum et al. (2005) found an average residential DU_LQ of only 0.45 in Central Florida — fixed spray heads at 0.41, rotary sprinklers at 0.49. The gap between design DU (0.65–0.85) and field reality (0.40–0.60) is the fundamental problem: design-computed DU represents an ideal-condition upper bound.

4.2 How SimplyScapes Computes DU

SimplyScapes uses the direct superposition approach: manufacturer radial distribution profiles (per ASABE S398.1) are overlaid at design-specified head positions, accounting for arc limits and radius. At each virtual grid point, precipitation contributions from all overlapping heads are summed. DU_LQ is calculated from the resulting grid using the standard lower-quarter formula. The computation runs at design time, immediately after head placement, with no field work required.

This approach is the same method used by WinSIPP (Senninger/Hunter), IrriCad (Lincoln Agritech), and IrriPro (Irriworks) for design evaluation. Academic validation shows simulation accuracy within 2–7% of field measurements under controlled conditions (Playan et al. 2006: R² = 97%, SE = 3.09%; Zapata et al. 2025: R² = 97%, SE = 1.1%).

4.3 The Design-to-Reality Gap

Design DU is an upper bound. Real installations degrade DU through five factors:

| Factor | Impact on DU | Mitigation | |--------|-------------|------------| | Wind (most significant) | 5–20% reduction at 2–10 mph | Apply Design-to-Field Adjustment Factor (DFAF) | | Pressure variation | 3–5% from pipe friction losses | Addressable via hydraulic analysis (future) | | Installation errors | 5–15% from head position/arc deviation | Quality control at install | | Head wear/degradation | Progressive, 3–5 year timeline | Age-based DFAF degradation | | Obstructions (trees, structures) | Varies, can be severe | Design updates over time |

Recommended Design-to-Field Adjustment Factor (DFAF): 0.90 for new professional installations, 0.80 for established systems (1–3 years), 0.70 for aging systems (5+ years). This accounts for the systematic overestimate of design DU while still being far more accurate than the default DU = 0.70 that smart controllers assume.

4.4 The Prior Art Gap

Every existing system that uses DU in scheduling assumes DU comes from a field measurement or manual input:

• Patent US7596429B2: DU is a user input — manually entered during setup.
• Patent US8948921B2: Lists DU as a parameter but does not specify how it's obtained.
• Rachio Flex Daily: Uses efficiency parameter (default 0.70) — user must override.
• Irrigation F/X: Computes DU from layout AND computes PR from layout — but does NOT feed DU into its scheduling calculation. Runtime = Target Depth / PR, with no DU adjustment.
• WinSIPP, IrriCad, IrriPro: Compute DU for design evaluation. None generate schedules.

The gap is clear and confirmed across patents, products, and academic literature. Nobody connects Domain A (design-computed DU) to Domain B (DU-adjusted scheduling) to produce zone-by-zone irrigation runtimes from design geometry alone. This represents genuine novel territory.

Full reference: supporting/design-computed-du.md — 40 sources, detailed simulation methodology, accuracy assessment tables, complete prior art search results, and DFAF recommendations.

---

5. Species-Specific Irrigation Season and Plant Factors

The EPA WaterSense Water Budget Tool uses a universal 50°F Growing Degree Day base temperature to determine the irrigation season, applied identically to all plant types. This approach has five specific deficiencies that species-specific scheduling can address, representing both practical value and defensive disclosure territory.

5.1 Why the Universal 50°F Threshold Fails

For cool-season turf: Root growth continues at soil temperatures as low as 33°F (Penn State Extension). The UC ANR monthly Kc for cool-season turf in November is 0.75 — far above zero. In Denver (average March temp: 43°F), WaterSense excludes March from the irrigation season, but cool-season turf is actively growing.

For warm-season turf: Bermudagrass requires soil temperature above 55–65°F at 4-inch depth for meaningful growth (Texas A&M AgriLife). In Nashville (average March temp: 52°F), WaterSense includes March in the irrigation season, but bermudagrass soil temperature is 45–50°F — the turf is dormant and brown.

Magnitude of error: The universal threshold causes 1–3 months per year of incorrect scheduling, 10–30% annual water waste in shoulder months, and no summer dormancy modeling for cool-season turf in the transition zone.

5.2 Species-Level Plant Factors

Research identified meaningful species-level variation within the standard cool/warm categories:

| Species | Annual PF | Relative Water Use | Key Distinction | |---------|----------|-------------------|-----------------| | Buffalograss | 0.30–0.50 | Very Low | Only native N. American turf; ~50% of bermuda water use | | Bermudagrass | 0.60 | Low-Moderate | Standard warm-season benchmark | | Zoysiagrass | 0.60 | Low | Similar to bermuda; slower green-up | | Centipedegrass | 0.50–0.60 | Low | Lacks deep dormancy; susceptible to freeze-thaw | | St. Augustinegrass | 0.60–0.70 | Moderate-High | Approaches cool-season water use in humid climates | | Fine fescue | 0.60–0.80 | Low-Moderate | Significantly less water than KBG at equivalent quality | | Tall fescue | 0.80 | Moderate-High | Most drought-tolerant high-quality cool-season (deep roots) | | Kentucky bluegrass | 0.80 | High | Peak ET of 8.5–10 mm/day | | Creeping bentgrass | 0.80–0.85 | High | Golf-course mowing heights increase water demand |

The water use ranking from lowest to highest: Buffalograss < Bermudagrass ≈ Zoysiagrass < Centipedegrass < Bahiagrass < St. Augustinegrass < Tall Fescue < Fine Fescue < Perennial Ryegrass ≈ Kentucky Bluegrass < Creeping Bentgrass.

5.3 Dormancy Thresholds

Cool-season: shoot growth ceases at air temp < 40°F; root growth ceases at soil temp < 33°F; root growth optimal at soil temp 50–65°F. Summer dormancy triggers above sustained air temp of 85–90°F.

Warm-season: all species share approximately soil temp < 55°F for dormancy entry. Green-up varies — bermudagrass needs soil at 65°F at 4-inch depth; zoysiagrass begins at 55–60°F. Cold hardiness ranges from -10°F (buffalograss) to 20–25°F (St. Augustine).

5.4 Proposed Algorithm

A rolling-average soil temperature threshold with linear ramp replaces the binary GDD approach:

def monthly_pf(T_soil, base_temp, active_temp, pf_active, pf_dormant):
    if T_soil <= base_temp:
        return pf_dormant
    elif T_soil >= active_temp:
        return pf_active
    else:
        fraction = (T_soil - base_temp) / (active_temp - base_temp)
        return pf_dormant + fraction * (pf_active - pf_dormant)

MVP database columns (3 columns): plant_factor, base_temp_f, active_temp_f. These enable species-specific scheduling with SimplyScapes' existing 2,500+ species plant library. Example: Kentucky bluegrass → PF=0.80, base=33°F, active=55°F. Bermudagrass → PF=0.60, base=55°F, active=65°F.

Full reference: supporting/species-specific-turf-factors.md — 12 species documented, monthly Kc tables, complete dormancy threshold data, GDD base temperatures, and the full algorithm specification with 13 proposed database columns.

---

6. Smart Controller API Integration

SimplyScapes needs to push computed schedules to smart controllers. Research mapped the API landscape for 8 controllers and identified three viable integration targets.

6.1 Controller Capability Matrix

| Controller | Schedule Push | API Access | Integration Viability | |-----------|--------------|-----------|----------------------| | Rachio 3 | Partial (adjust/run, not create) | Public REST, bearer token | Priority 1 — best documented, 1,700 calls/day | | OpenSprinkler | Full CRUD | Local HTTP, MD5 auth | Priority 2 — deepest control, open source | | RainMachine | Full CRUD | Local REST, token auth | Priority 3 — strong local API (but business uncertain) | | Hunter Hydrawise | Unknown (v2 GraphQL gated) | Requires commercial auth | Future — needs Hunter partnership | | Rain Bird IQ4 | Read-focused | Paid subscription | Future — commercial only | | Rain Bird LNK2 | No create/modify | Reverse-engineered SIP | Not viable | | Orbit B-hyve | Unknown | Reverse-engineered | Not viable | | Weathermatic SmartLink | Yes | REST with API key/secret | Possible — commercial landscape focus |

6.2 Rachio Integration Workflow

Rachio's API does not support programmatic schedule creation — schedules must be pre-created in the app. The recommended hybrid workflow:

1. One-time setup: User creates a Fixed schedule in the Rachio app (template)
2. Sync zone properties: SimplyScapes writes vegetation type, soil, nozzle PR, shade, root depth, and efficiency from the design → PUT /public/zone
3. Push runtime adjustments: Compute QWEL-based runtimes, translate to seasonal adjustment → PUT /public/schedulerule/seasonal_adjustment
4. Alternative — direct zone runs: Bypass the schedule entirely → PUT /public/zone/start_multiple with exact durations (loses Weather Intelligence)
5. Alternative — moisture override: Tell Rachio's Flex Daily the current soil moisture → PUT /public/zone/setMoisturePercent (most elegant but requires soil moisture modeling)
6. Monitor execution: Register webhooks for zone completion events with flowVolumeG feedback

Key insight — the "nozzle PR trick": Setting customNozzle.inchesPerHour to the design-computed PR × DU product causes Rachio's own scheduling logic to automatically compensate for the zone's actual uniformity. This is the simplest integration path — one API call per zone that makes Rachio's existing algorithms design-aware.

6.3 SimplyScapes vs. Rachio Flex Daily

The critical difference: Rachio uses efficiency (default 0.70) as a static guess. SimplyScapes uses design-computed DU per zone. A zone with DU = 0.55 needs 82% more runtime than one with DU = 1.0 — a correction Rachio cannot make without design data. The recommended approach is to enhance Rachio's inputs rather than replace its algorithm entirely, getting the best of both worlds (design precision + weather intelligence).

Full reference: supporting/smart-controller-apis.md — 39 sources, complete endpoint documentation for all 8 controllers, JSON data models, webhook payload examples, and a TypeScript IrrigationControllerAdapter interface specification.

---

7. SmartRain Freedom-to-Operate Analysis

SmartRain (Smart Rain Systems LLC) has filed aggressively with 6+ patents from a single inventor (Rudy Lars Larsen). The FTO analysis examined every independent claim in the portfolio. Overall risk assessment: LOW. All SmartRain patents require physical hardware that SimplyScapes does not use.

7.1 Patent Portfolio Summary

| Patent | Title | Filed | Key Hardware Required | Risk | |--------|-------|-------|----------------------|------| | US9,307,706B2 | Irrigation Management | 2014 | Controller + flow sensor | NONE | | US10,660,279B2 | Irrigation Management (continuation) | 2018 | Flow sensor + moisture sensor | NONE | | US11,185,024B2 | Map Integration | 2019 | GPS + satellite imagery + sensors | NONE | | US11,684,029B2 | Landscaper Integration | 2020 | Two remote devices + physical controller | LOW | | US11,839,184B2 | AI Irrigation System | 2020 | Weather/flow data + historical models | LOW (current), MODERATE (future AI) | | US20210176931A1 | Soil Sensor Grid | 2021 | Physical moisture sensor grid + relay | NONE |

7.2 Three Risk Areas Analyzed

Risk Area 1 — Cost Savings (US10,660,279B2): The patent ties cost savings to physical sensor data (flow meter or moisture sensor) and a fee-based service model. SimplyScapes estimates water usage from design parameters (PR × time × area) — categorically different from metered flow. Risk: LOW.

Risk Area 2 — Landscape Event Adjustment (US11,684,029B2): The patent covers real-time operational interruptions (e.g., "sod was just installed") with predetermined durations that auto-revert. SimplyScapes' design-driven recomputation regenerates the entire schedule from first principles when design parameters change — no temporary override, no auto-revert. Risk: LOW.

Risk Area 3 — AI-Predicted Soil Moisture (US11,839,184B2): This is the most nuanced area. The patent requires correlating current precipitation events against stored historical triggering event models to predict soil moisture. SimplyScapes' deterministic ETo-based formula chain is clearly outside scope. However, if SimplyScapes later builds historical model correlation for soil moisture prediction, it could implicate Claim 11. Risk: LOW for current approach, MODERATE for advanced predictive features.

Design-around strategies: (1) Frame all weather adjustments as ET-adjusted water budgeting, not soil moisture prediction; (2) Use deterministic threshold checks for rain skip, not historical event correlation; (3) Label water usage estimates as "estimated from design parameters"; (4) Derive establishment watering from plant database data, not predetermined event durations.

7.3 Broader Patent Landscape

14 additional competitor patents were analyzed. All require physical hardware. The closest prior art is Husqvarna/ETwater's US10,028,454B2 (cloud + plant database + ET scheduling) — but it requires physical site survey data and does not compute DU from design geometry. The expired HydroPoint patent US7,337,042 (2004) establishes that ET-based scheduling is in the public domain.

Key finding: No identified patent anywhere in the landscape covers computing DU from irrigation design geometry and using that computed DU to generate schedules. This is genuine whitespace. TDCommons and IP.com searches returned no relevant defensive publications — SimplyScapes would be the first to publish in this domain.

Full reference: supporting/patent-landscape-fto.md — 57KB, full independent claims extracted for all 6 SmartRain patents, 14 additional patents analyzed, 5 design-around strategies, and 4 defensive disclosure topic recommendations.

---

8. Advanced Scheduling Intelligence

Beyond the Phase 1 ETo-based approach, the research surveyed seven technology domains for comprehensive defensive disclosure coverage. The goal: establish prior art across the full innovation space before competitors file on approaches combining design-time intelligence with advanced techniques.

8.1 Key Finding

No existing system combines design-computed DU with any advanced scheduling technique. Every advanced scheduling system — from satellite ET to soil sensors to machine learning — assumes DU comes from a field measurement or uses a default. The combination of SimplyScapes' design-time DU/PR with any of these technologies represents unoccupied territory.

8.2 Technology Landscape

| Technology | Accuracy | Cost/Zone | Integration Complexity | TRL | |-----------|---------|-----------|----------------------|-----| | Soil moisture sensors (capacitance) | ±3–5% VWC | $80–200 | Moderate | 7 | | Soil moisture sensors (TDR) | ±1% VWC | $300–2,000 | High | 9 | | Flow meters | ±2% of reading | $150–400 | Low-Moderate | 8 | | OpenET (satellite) | 15.8 mm/month MAE | Free (API) | Low | 6 | | Weather forecast skip | N/A | Free | Low | 8 | | ML-enhanced ET | Varies | Compute cost | High | 4–5 | | Digital twin | Conceptual | R&D | Very High | 2–3 |

OpenET deserves special attention: 30m × 30m spatial resolution, daily products for CONUS, ensemble of 6 satellite models, free API access. At field scale it could provide site-specific ET that outperforms regional weather station interpolation. The 17% average error is acceptable for residential irrigation scheduling.

8.3 Thirteen Alternative Embodiments for Defensive Disclosure

1. Satellite ET Fusion: Design-computed DU + OpenET site-specific ET → zone runtimes
2. Probabilistic Weather Integration: Multi-model ensemble forecast → skip probability → schedule adjustment
3. Flow Meter Feedback Loop: Predicted vs. actual flow → DU calibration → DFAF update
4. Soil Moisture Sensor Calibration: Sensor VWC → model calibration → schedule refinement
5. ML-Enhanced ET Prediction: Design features + weather → neural network ET → schedule
6. Digital Twin Irrigation Model: Full soil-plant-atmosphere simulation per zone
7. Reinforcement Learning Schedule Optimization: RL agent learns optimal watering from turf health feedback
8. Fleet Learning Across Properties: Aggregate anonymized data across SimplyScapes designs → improve DFAF estimates
9. Utility Meter Reconciliation: Municipal water meter data → validate total property water use → detect system-wide efficiency loss
10. NDVI Vegetation Feedback: Satellite or drone NDVI → turf health index → PF adjustment
11. Adaptive Cycle-Soak Optimization: Flow meter during irrigation → real-time infiltration rate detection → dynamic cycle timing
12. Multi-Controller Coordination: Coordinate schedules across multiple controllers on one property → respect flow constraints
13. Water District Compliance Automation: MAWA budget + schedule → automatic compliance reporting to districts

8.4 Eight Whitespace Areas

The research identified 8 areas where no product or patent exists:

1. Design-computed DU → schedule (SimplyScapes' core innovation)
2. Species-specific growing season determination from temperature data
3. Design-to-field adjustment factor (DFAF) with age-based degradation
4. Satellite ET fusion with design-computed DU
5. TypeScript/JavaScript ET computation library (none exists on npm)
6. Fleet learning for DU accuracy improvement
7. Automatic compliance reconciliation (MAWA budget vs. actual schedule)
8. Multi-controller coordination for hydraulic flow constraints

Full reference: supporting/advanced-scheduling-intelligence.md — 86 sources, 13 alternative embodiments detailed, technology readiness matrix for 17 technologies, and complete whitespace analysis.

---

Part III: Market Landscape

9. Market Overview

How the market currently handles turf irrigation scheduling:

The irrigation scheduling market splits cleanly into three camps that do not communicate. Design tools (Land F/X, IrriCad, SimplyScapes) compute DU, PR, and coverage from head placement geometry — then generate a static document and stop. Smart controllers (Rachio, Hunter Hydrawise, Rain Bird, Orbit B-hyve) schedule watering from weather data and manual zone configuration — but they don't know what heads are installed or what the actual DU is. Commercial management platforms (WeatherTRAK, Weathermatic, Calsense, ETwater/Jain) add ET-based scheduling and portfolio dashboards — but still require field-measured inputs and hardware subscriptions costing $1,500–$3,000+ per controller.

Every serious scheduling product uses some form of evapotranspiration calculation. The differentiation is in data sources (local weather station vs. satellite vs. proprietary network), update frequency (daily vs. hourly), and methodology (simple ET replacement vs. soil moisture depletion tracking). What every product shares — without exception from $70 B-hyve to $2,500 WeatherTRAK — is zone-level scheduling with broad plant-type categories (4–8 types) and no design awareness.

The design-to-schedule gap is the central market finding: nobody bridges design intelligence into operational scheduling. Design tools know DU, PR, species, and head geometry. Controllers know weather and soil type. The data that would make scheduling dramatically more accurate (design-computed DU and manufacturer PR) sits unused in the design tool while the controller guesses at default values.

Market maturity: Growing — ET-based scheduling is established in commercial markets but still gaining adoption in residential. The commercial segment is shifting from hardware sales to platform subscriptions (Weathermatic SmartLink Connect, Calsense IMaaS). The residential segment is commoditizing on hardware while differentiating on software intelligence.

Customer satisfaction: Underserved — Rachio community forums are dominated by users struggling with default efficiency and precipitation rate assumptions that don't match their actual systems. Commercial customers accept manual calibration because no alternative exists. No customer segment has access to design-aware scheduling.

10. Vertical Market Analysis

15 companies were analyzed across four tiers: consumer smart controllers (4), commercial management platforms (4), design tools (3), and discovery additions (4). Full details in supporting/vertical-competitor-analysis.md.

Consumer Smart Controllers

Rachio (Flex Daily / Flex Monthly) — The most technically sophisticated consumer scheduling system. Maintains a virtual soil moisture balance per zone using ET. Uses an efficiency parameter per zone (default ~70%) analogous to DU but not labeled as such. Public REST API with 1,700 calls/day is the best-documented controller API available. Primary integration target — the setMoisturePercent endpoint allows SimplyScapes to function as an intelligence overlay, and the "nozzle PR trick" (setting customNozzle.inchesPerHour to PR × DU) makes Rachio's own algorithms design-aware with one API call per zone. Key gap: Community forums are dominated by users struggling because default efficiency and PR assumptions don't match their actual systems.

Hunter (Hydrawise / Pro-HC) — Three watering modes per zone with a proprietary Virtual Weather Station aggregating satellite, aircraft, and mobile phone barometric data. Flow monitoring hardware provides ground-truth water delivery data. Secondary integration target — GraphQL v2 API has potential but requires commercial partnership. More restrictive rate limits than Rachio. Key gap: No DU or efficiency input; coarse plant type categories; WiFi reliability issues.

Rain Bird (ARC8 / IQ4) — Uses weather-adjusted percentage scaling rather than true ET-based soil moisture tracking. Consumer scheduling is the weakest among major competitors. No official API for consumer controllers. Not viable for integration — SimplyScapes would compete against Rain Bird rather than integrate with it. However, the massive installed base means many users will have Rain Bird hardware; the unofficial pyrainbird local protocol could enable community-driven integration.

Orbit B-hyve — Full ET-based soil moisture depletion model at the lowest price point ($70–$120). Notable for including a built-in catch-cup test feature — one of the few consumer controllers that acknowledges uniformity matters, but puts the measurement burden on the user. No official API (reverse-engineered WebSocket only). Not viable for official integration.

Commercial Management Platforms

Weathermatic (SmartLink) — ET-based scheduling with per-zone custom precipitation rate input and a ±75% fine-tuning adjustment. SmartLink Connect (launching summer 2026) retrofits non-Weathermatic controllers (Hunter 2-wire, Rain Bird) into the SmartLink cloud. Has a published developer API (SmartLink Network v2). Partnership opportunity — Weathermatic is becoming a scheduling intelligence layer over competitor hardware, architecturally similar to what SimplyScapes proposes but from the operations side. Their fine-tuning adjustment is the closest market proxy for DU, but it's a manual guess, not a computed value. 38% average water savings documented across 500,000+ units.

HydroPoint (WeatherTRAK) — Most scientifically rigorous commercial methodology using FAO Penman-Monteith ET with proprietary ET Everywhere weather service and soil moisture depletion tracking. Compliance tools (Budget Manager, Water Window, Drought Manager) are selling points for institutional buyers. Not viable for integration — closed platform, no public API. The gap between their six categorical zone-level questions and SimplyScapes' design-computed DU/PR with species-level plant factors is the core opportunity.

ETwater / Jain Unity — Most aggressive AI/ML claims with hourly schedule adjustments, predictive scheduling, and patented big-data processing. The most important lesson in this analysis: you can have ML, predictive analytics, and a billion data points, and still operate at the zone level with categorical plant types. Their parent company (Jain/Rivulis) manufactures drip emitters but has not connected the emitter catalog to the scheduling intelligence — the exact gap SimplyScapes fills. HermitCrab retrofit adapter is a useful precedent for hardware-agnostic scheduling.

Calsense — Targets municipal/institutional market with predictive water budgets and FlowStation concurrent valve optimization. IMaaS (Irrigation Management as a Service) model — 10-year fixed annual fee covering hardware, software, monitoring, training — validates the subscription model for irrigation intelligence. Published AI roadmap (Smart Irrigation 2.0) but focus is operational efficiency, not plant science.

Design Tools

Land F/X — Closest conceptual competitor to SimplyScapes' design-side capabilities. 4,000+ plants with WUCOLS water use data. Computes precipitation rate per schematic area and generates runtime schedules as static documents. Critical distinction: Land F/X stops at the design document. The static schedule is a PDF, not a controller configuration. DU is implicit (head placement enables assessment) but not explicitly computed as a numeric value. No API, no controller integration, no weather adjustment.

IrriCad — Global leader in irrigation design software (90+ countries). Deep hydraulic analysis (pressure, flow, pipe sizing) with manufacturer sprinkler databases. Can model sprinkler overlap patterns relevant to DU calculation. Validates that design-side DU computation is technically feasible, but uses it for hydraulic design optimization, not scheduling. No scheduling, no controller integration, no API.

Discovery Additions

SmartRain — Predictive ET for 4-day forward scheduling with integrated flow monitoring, soil sensing, and SmartLandscape (adjusts schedules for landscape service events — subject of patent US11,684,029B2). Hardware-centric: all features require SmartRain controllers + flow sensors + soil sensors. No public API. Most aggressive IP filer in this space — see Section 7 for FTO analysis.

OpenSprinkler — Open-source controller with the most complete local REST API available. Full program management (create, edit, delete), MQTT support, flow sensor integration. Ideal secondary integration target for local-first, cloud-independent scheduling pipeline. SimplyScapes could contribute a design-computed DU scheduling module directly to the OpenSprinkler firmware.

RainMachine — Cloud-independent controller with open-source Penman-Monteith implementation and multi-source weather aggregation. Effectively discontinued — all hardware appears unavailable, company status unclear. A cautionary tale about hardware-dependent business models in smart irrigation, reinforcing SimplyScapes' software-only approach.

Toro (Tempus) — Timer-based scheduling with seasonal percentage adjustment. Least sophisticated smart scheduling among major manufacturers. Late entrant (Tempus launched 2022). Not a competitive threat on scheduling intelligence, but significant market presence.

Vertical Market Patterns

Six patterns emerge across all 15 companies:

1. ET-based scheduling is table stakes. The differentiation is in data quality and methodology, not in whether ET is used.
2. Zone-level scheduling is universal. No product goes below zone granularity.
3. Broad plant type categories are standard. 4–8 categories. No species-level selection anywhere.
4. Catch-cup testing is the assumed DU source. Every product that uses DU/efficiency assumes field measurement.
5. Cloud dependency is the norm. Only OpenSprinkler offers fully local scheduling intelligence.
6. Subscription models are growing. Commercial market moving from hardware sales to platform revenue.

Vertical Market Gaps

1. Design-to-schedule bridge — No product connects design data to operational scheduling
2. Design-computed DU — No product computes DU from geometry for scheduling
3. Species-specific scheduling — No product differentiates scheduling by turfgrass species
4. Growing season intelligence — No product uses species-specific dormancy thresholds
5. Establishment scheduling — No landscape controller adjusts for newly planted turf
6. Compliance-to-schedule connection — No product guarantees the schedule stays within the MWELO water budget

Full reference: supporting/vertical-competitor-analysis.md — 15 companies analyzed, API capability matrix, controller integration priority ranking, and complete design-awareness gap analysis.

---

11. Adjacent Market Patterns

17 adjacent market products and industries were analyzed. Full details in supporting/adjacent-market-academic.md. The ten most transferable insights not yet applied to landscape irrigation:

1. Design-Computed Performance Prediction (from Solar Energy: Enphase/SolarEdge/Aurora Solar) Solar installation software predicts kWh output from panel geometry, then monitors actual vs. predicted performance to detect degradation. No irrigation product uses design geometry to predict system performance. SimplyScapes' design-computed DU is the irrigation equivalent of solar panel layout performance prediction — the core novelty.

2. Variable Crop Coefficients by Growth Stage (from AgTech: Netafim GrowSphere + USGA Research) Agricultural platforms have used growth-stage-adjusted water demand for decades. A 2025 USGA study proves GDD-adjusted Kc reduces turfgrass irrigation 10–15% vs. fixed Kc. No residential controller uses variable Kc values. SimplyScapes could be first to implement GDD-normalized Kc for residential turf scheduling.

3. Demand Response Framework for Water Restrictions (from Energy: Nest/Ecobee analogy) The electric grid's demand response model (graduated levels, pre-event buffering, portfolio coordination) was proposed for irrigation by Lunstad & Sowby (2024 ASCE JWRPM) but never implemented in any product. SimplyScapes already displays water restriction alerts in the UI; this could formalize into a multi-stage response framework (normal → conservation → mandatory → survival → ban).

4. Ensemble Model Approach (from Satellite ET: OpenET) OpenET's finding that no single ET model dominates and weighted ensembles perform best suggests aggregating multiple weather/ET data sources rather than relying on a single API. The ensemble approach could extend to soil moisture estimation.

5. Degradation Detection from Design Baseline (from Solar + Digital Twins: Willow/Autodesk Tandem) Solar monitoring detects degradation by comparing actual vs. predicted output. Building digital twins detect drift from sensor data. No irrigation product compares actual water use against a design-predicted baseline to detect system degradation. SimplyScapes' design data provides this baseline.

6. Portfolio-Level Water Intelligence (from Commercial Water: Banyan Water + Dropcountr/KUBRA) Banyan Water provides portfolio dashboards for commercial properties; Dropcountr provides utility-side analytics with peer comparison driving 6% average water savings. No product provides portfolio-level water intelligence for residential irrigation contractors. SimplyScapes' design data enables this without smart meters.

7. Sensor + Model Fusion Progression (from AgTech: CropX / Phytech / Hortau / Sentek) These companies represent a progression from pure sensing to sensor + AI fusion. CropX validates that ET-only scheduling is a viable starting point — they started with sensors and added ET models, while SimplyScapes starts with ET models and can add sensors later. The key insight: design-computed DU serves as a substitute for physical uniformity measurements.

8. Soil Redistribution Compensates for Surface Non-Uniformity (from Academic Research) A 2023 Journal of Hydrology study found that soil water movement partially compensates for sprinkler non-uniformity. Design-computed DU (measuring surface uniformity) is conservative — actual root-zone uniformity is higher. This provides scientific basis for trusting design-computed DU without large safety factors.

9. Open Source ET is a Commodity (from pyETo/pyfao56/RainMachine/OpenSprinkler) The Penman-Monteith ET calculation is well-implemented in multiple open-source packages. The ET calculation itself is not the innovation. The innovation is what inputs you feed into it (design-computed DU and PR) and how you apply the output (per-zone schedules pushed to controllers).

10. Water My Yard Validates the Market (Texas A&M AgriLife) Water My Yard delivers ET-based residential irrigation recommendations to 30% of Texas single-family homes, saving an estimated 2.7 billion gallons/year (~$230/household/year). SimplyScapes' design-computed approach is strictly more precise because it incorporates system-specific DU and PR rather than generic assumptions.

Full reference: supporting/adjacent-market-academic.md — 17 adjacents analyzed, 10 cross-industry insights, and 37 academic references.

---

12. Patent & IP Findings

Overall patent risk: Low Freedom to operate: Clear (for Phase 1 design-computed DU scheduling); Caution (for future AI/ML predictive features)

SmartRain Patent Portfolio

Six patents from a single inventor (Rudy Lars Larsen). All claims require physical hardware that SimplyScapes does not use:

| # | Patent | Title | Filed | Key Hardware Required | Risk | |---|--------|-------|-------|----------------------|------| | 1 | US9,307,706B2 | Irrigation Management | 2014 | Controller + flow sensor | NONE | | 2 | US10,660,279B2 | Irrigation Management (cont.) | 2018 | Flow sensor + moisture sensor | NONE | | 3 | US11,185,024B2 | Map Integration | 2019 | GPS + satellite imagery + sensors | NONE | | 4 | US11,684,029B2 | Landscaper Integration | 2020 | Two remote devices + physical controller | LOW | | 5 | US11,839,184B2 | AI Irrigation System | 2020 | Weather/flow + historical models | LOW (current); MODERATE (future AI) | | 6 | US20210176931A1 | Soil Sensor Grid | 2021 | Physical moisture sensor grid + relay | NONE |

Design-around strategies: (1) Frame weather adjustments as ET-adjusted water budgeting, not soil moisture prediction; (2) Use deterministic threshold checks for rain skip, not historical event correlation; (3) Label water usage estimates as "estimated from design parameters"; (4) Derive establishment watering from plant database data, not predetermined event durations.

Broader Patent Landscape

14 additional competitor patents analyzed. All require physical hardware. Key findings:

• US10,028,454B2 (Husqvarna/ETwater) — Closest prior art (cloud + plant database + ET scheduling) but requires physical site survey data. Does not compute DU from design geometry.
• US7,337,042 (HydroPoint, 2004) — Expired. Establishes that ET-based scheduling is in the public domain.
• US7,596,429B2 (WeatherTRAK) — DU is a user input, manually entered during setup.

Critical finding: No identified patent anywhere in the landscape covers computing DU from irrigation design geometry and using that computed DU to generate schedules. TDCommons and IP.com searches returned no relevant defensive publications. This is genuine whitespace.

FTO Summary Matrix

| Approach | FTO Status | Notes | |----------|-----------|-------| | Design-computed DU → schedule generation | CLEAR | No prior art found | | ET formula chain (QWEL/Penman-Monteith) | CLEAR | Public domain methodology | | Species-specific growing season thresholds | CLEAR | Extension of public data | | Weather forecast rain skip | CAUTION | Multiple patents; use ET budget framing | | AI/ML predictive soil moisture | CAUTION | SmartRain US11,839,184B2 claims | | Flow meter feedback for DU calibration | CLEAR | Standard measurement practice | | Establishment lifecycle scheduling | CLEAR | No patents found |

Full reference: supporting/patent-landscape-fto.md — 20 patents analyzed with full independent claims extracted, 5 design-around strategies, and 4 defensive disclosure topic recommendations.

---

13. Academic & Open Source

37 academic references were identified and categorized across seven domains. Full consolidated reference table in supporting/adjacent-market-academic.md.

Key Academic Findings

Turfgrass water requirements vary 2.3× by species. Qian & Engelke found minimum annual irrigation ranges from 244 mm (bermudagrass) to 552 mm (Kentucky bluegrass). This validates species-specific scheduling over one-size-fits-all approaches.

GDD-adjusted Kc reduces irrigation 10–15%. The 2025 USGA Green Section Record published the first GDD-normalized Kc models for turfgrass, showing fixed Kc values overwater in spring/fall and occasionally underwater in peak summer. This is the first study to develop GDD-adjusted Kc models specifically for turfgrass.

Mowing height significantly affects water requirements. Oregon State research found tall fescue and perennial ryegrass at standard mowing height require only 26–36% ETref replacement, while fine fescues at 5/8-inch height require 95–98% — a scheduling factor not captured by species-level PF alone.

Cultivar-level differences matter. Texas A&M AgriLife found Cobalt St. Augustine maintained acceptable quality for 70 days at 50% ET replacement — 14 days longer than TifTuf bermuda and 27 days longer than Palisades zoysia. Cultivar-specific scheduling can significantly impact water conservation.

ML can predict DU from system parameters. A 2023 Scientific Reports study used Random Forest and XGBoost to predict sprinkler water distribution uniformity from operating pressure, height, discharge, nozzle diameter, wind, humidity, and temperature — validating that DU can be predicted from parameters rather than measured in the field.

Soil redistribution improves root-zone uniformity. A 2023 Journal of Hydrology study found soil water movement partially compensates for sprinkler non-uniformity, meaning design-computed surface DU is conservative relative to actual root-zone uniformity.

Smart controllers save 15–40%. Lunstad & Sowby's 2024 meta-analysis of 80 studies found smart controllers reduce water demand by 15% for average users and 40%+ for heavy users. Weather-based (ET) and soil moisture controllers achieve similar savings.

Open Source Tools

| Tool | Type | Relevance | |------|------|-----------| | Open-Meteo | Free API | Primary ETo source for Phase 1 — global, no API key, FAO-56 PM | | pyfao56 | Python library | Most comprehensive open-source ET + water balance (USDA-ARS, peer-reviewed) | | pyETo / pyet | Python libraries | Lightweight ET calculation libraries | | OpenET | Satellite platform | 30m ET validation data, ensemble of 6 models, free API | | WUCOLS V | Plant database | 4,100+ taxa water use classifications, public domain | | CIMIS | Weather network | California ETo gold standard, 150+ stations | | gridMET | Gridded dataset | 4km daily ETo for CONUS (12–31% overestimation bias vs. station data) | | NTEP | Turfgrass database | Cultivar-level performance data for water requirements | | OpenSprinkler | Controller firmware | Open-source REST API, reference implementation |

Notable gap: No TypeScript/JavaScript ET computation library exists on npm. SimplyScapes would need to implement Penman-Monteith natively or port from Python (pyfao56/pyETo).

---

Part IV: Synthesis

Opportunity Map

Validated Patterns (safe to build on — table stakes)

These approaches are used by multiple products with no patent barriers:

1. ET-based scheduling from weather data. Every smart controller does this. The QWEL/Penman-Monteith formula chain is public domain and standardized (ANSI/ASABE S623.1). No IP barriers.
2. Zone-level scheduling. Universal approach. SLIDE Rules validate zone as the correct management unit.
3. Cycle-soak splitting. Standard practice from soil infiltration rates. Implemented by Rachio, B-hyve, Weathermatic, WeatherTRAK.
4. Weather forecast integration (rain/freeze skip). Available in all smart controllers. Multiple implementation approaches exist. Use ET budget framing to avoid patent concerns.
5. Controller API integration. Rachio, OpenSprinkler, and Weathermatic all offer APIs for schedule management.

Differentiation Opportunities (where to innovate)

1. Design-Computed DU → Schedule Generation

   • Market gap: No product connects design-side DU computation to scheduling formulas
   • Inspiration: Solar energy's design-time performance prediction → operational monitoring
   • Patent risk: None — confirmed genuine whitespace across patents, products, and academic literature
   • Why it's different: Every existing system assumes DU comes from a physical catch can test. SimplyScapes computes it from design geometry, eliminating the $500–$2,000 field audit

2. Species-Specific Growing Season Determination

   • Market gap: EPA WaterSense universal 50°F threshold causes 1–3 months/year incorrect scheduling
   • Inspiration: Netafim's growth-stage scheduling + 2025 USGA GDD-adjusted Kc research
   • Patent risk: None — extension of public domain data from UC ANR, Texas A&M, USU
   • Why it's different: First system to use species-specific soil temperature thresholds with a linear ramp function instead of binary on/off

3. Design-to-Field Adjustment Factor (DFAF) with Age-Based Degradation

   • Market gap: No product accounts for the systematic gap between design DU and field DU
   • Inspiration: Solar energy's degradation detection from design baseline
   • Patent risk: None — novel application of well-established engineering principles
   • Why it's different: Provides a principled way to trust design-computed DU while acknowledging it's an upper bound (0.90 new → 0.80 established → 0.70 aging)

4. Compliance-to-Schedule Reconciliation

   • Market gap: MWELO water budgets (MAWA/ETWU) computed independently of operational schedules
   • Inspiration: Banyan Water's portfolio-level compliance dashboards
   • Patent risk: None — connecting two existing public-domain calculations
   • Why it's different: First system that generates schedules mathematically guaranteed to stay within the MWELO water budget

5. Nozzle PR Trick for Rachio Integration

   • Market gap: Rachio users struggle with default efficiency assumptions
   • Patent risk: None — using published API as intended
   • Why it's different: One API call per zone (setting customNozzle.inchesPerHour to PR × DU) makes Rachio's own Flex Daily algorithm design-aware

6. Fleet Learning Across Properties

   • Market gap: No product aggregates anonymized data across designs to improve accuracy
   • Inspiration: CropX's 20,000+ user data network; Nest's learning from user adjustments
   • Patent risk: Low — standard ML aggregation patterns
   • Why it's different: Design-to-field accuracy can improve as SimplyScapes sees more installations

7. Portfolio Water Intelligence for Contractors

   • Market gap: No product provides portfolio-level water intelligence for residential contractors
   • Inspiration: Banyan Water (commercial) + Dropcountr (utility-side peer comparison)
   • Patent risk: None
   • Why it's different: Design-computed water budgets per property aggregated across a contractor's portfolio without requiring smart meters

Caution Zones (promising but constrained)

1. AI/ML Predictive Soil Moisture — Promising for advanced scheduling, but SmartRain US11,839,184B2 covers correlating weather events against stored historical models to predict soil moisture. Design-around: use deterministic ET-budget-based soil moisture tracking (within QWEL framework) rather than pattern-matching against historical event databases.

2. Weather Forecast Schedule Adjustment — Multiple patents cover proactive schedule modification from forecasts. Design-around: frame adjustments as ET budget recalculation from forecast ETo data, not as direct schedule modification from precipitation predictions. SmartRain's 4-day predictive ET is prior art establishing this general approach.

3. Landscape Event Schedule Modification — SmartRain US11,684,029B2 covers adjusting schedules based on landscape service events with predetermined durations and auto-revert. Design-around: SimplyScapes' approach regenerates the entire schedule from first principles when design parameters change, with no temporary overrides or auto-revert mechanisms.

The Technical Landscape

Phase 1 Architecture (Minimal Viable Product):

Open-Meteo API → ETo (daily/monthly)
                      ↓
SimplyScapes Design Engine
  ├── DU per zone (already computed)
  ├── PR per head (from manufacturer catalog)
  ├── Soil type per zone
  ├── Turf species per zone (from 2,500+ plant library)
  └── WUCOLS PF per species
                      ↓
QWEL Formula Chain
  ETo × PF = ETc → ETc − Pe = IWR → IWR × (1/DU) / PR × 60 = Runtime
  Runtime / Time-to-Runoff = Cycle-Soak Splits
                      ↓
Schedule Output
  ├── Per-zone runtime minutes per event
  ├── Cycle-soak configuration
  ├── Days-per-week recommendation
  └── Monthly schedule calendar
                      ↓
Controller Push (Rachio Priority 1)
  ├── Zone properties (PR, efficiency, soil, vegetation)
  ├── Seasonal adjustment percentages
  └── OR nozzle PR trick (PR × DU → customNozzle)

Key Data Sources:

• ETo: Open-Meteo (free, global, FAO-56 PM, forecast + historical)
• Plant Factors: WUCOLS/SLIDE (public domain, already in plant library)
• DU: Design engine (already computed and displayed in UI)
• PR: Manufacturer catalogs (already in design database)
• Soil infiltration: USDA Web Soil Survey (standard lookup tables)
• Dormancy thresholds: UC ANR, Texas A&M, USU Extension data

Database additions (MVP — 3 columns):

• plant_factor — species-specific annual PF (e.g., KBG = 0.80, bermuda = 0.60)
• base_temp_f — soil temperature below which PF = 0 (e.g., KBG = 33°F, bermuda = 55°F)
• active_temp_f — soil temperature above which PF = full value (e.g., KBG = 55°F, bermuda = 65°F)

Implementation complexity: Low-moderate. All formula components are established. The novel connection (design-computed DU → QWEL formula chain) requires no new algorithms — only wiring existing values into a standard calculation. The Rachio API integration is well-documented with a clear endpoint strategy.

What doesn't exist yet: No TypeScript/JavaScript ET library on npm. SimplyScapes would need to implement Penman-Monteith natively or port from Python (pyfao56 is the most comprehensive reference implementation). This is a one-time engineering investment (~2–4 weeks) that could also be published as an open-source npm package — community goodwill + defensive publication.

Open Questions

• [ ] What is the actual accuracy of SimplyScapes' design-computed DU vs. field-measured DU? A validation study on 5–10 installed systems would quantify the DFAF recommendations and strengthen the defensive publication.
• [ ] How should mixed-species turf zones be handled? SLIDE says "use the highest PF species." Should SimplyScapes require mono-species zones or allow mixed-species with automatic PF selection?
• [ ] Should the Phase 1 product expose the full QWEL formula chain to users, or abstract it behind a "recommended schedule" output? Transparency builds trust with QWEL-trained professionals; abstraction serves homeowners.
• [ ] What is the right ETo update frequency? Monthly is standard for water budgets but daily or weekly better captures shoulder-season variability. Open-Meteo provides daily data.
• [ ] How should the system handle the Rachio "no create schedule" API limitation? The hybrid workflow (user creates Fixed schedule template, SimplyScapes modifies via seasonal adjustment) has UX friction. The start_multiple bypass loses Weather Intelligence. The setMoisturePercent approach is the most elegant but requires soil moisture modeling.
• [ ] Should SimplyScapes build its own ET computation or rely on Open-Meteo's pre-computed ETo? Building own calculation provides more control and enables the open-source npm package strategy, but adds engineering complexity.
• [ ] What is the monetization model? Scheduling-as-a-feature (included in existing subscription) or scheduling-as-a-product (separate tier)? Calsense's IMaaS and Weathermatic's $18–50/month provide commercial precedent.
• [ ] How should the DFAF degrade over time? The recommended 0.90 → 0.80 → 0.70 progression needs a timeline. Is it linear degradation? Step functions at 1, 3, and 5 years? Should it be configurable per system?
• [ ] Can SimplyScapes leverage the UC Davis LAWR spreadsheet tool as a validation benchmark? Their annual irrigation calendar from ETo + DU + soil type + wetting depth is the same calculation, just manual.
• [ ] Should the defensive disclosure cover the full 13 alternative embodiments, or focus on the 3–4 most likely to be pursued by competitors?

Opportunity Assessment

Novelty: High. Design-computed DU → schedule generation has no prior art in patents, products, or academic literature. The specific integration of design-time intelligence into operational scheduling is confirmed genuine whitespace. Species-specific growing season determination adds a secondary layer of novelty.

Feasibility: High. Every component exists independently: DU is already computed in the UI, PR is already in the design database, the QWEL formula chain is standardized, Rachio's API is well-documented, and plant factor data is public domain. The innovation is the connection, not any individual component. Phase 1 requires no new algorithms, no hardware, no sensors — only wiring existing values into established formulas.

Impact: High. Eliminates the $500–$2,000 catch can audit for every property with a SimplyScapes design. Water My Yard validates residential savings of ~$230/household/year. A 15–30% improvement in schedule accuracy (from actual DU vs. default 0.70) translates to meaningful water conservation. For SimplyScapes commercially, this transforms the platform from a design tool into a design-to-operations platform — a category expansion with significant revenue implications.

Timeline: Phase 1 (core ETo-based scheduling with design-computed DU) is an estimated 4–8 week engineering effort. Species-specific dormancy thresholds add ~1–2 weeks. Rachio integration adds ~2–3 weeks. Total Phase 1 MVP: approximately one quarter.

---

Recommended Next Steps

1. Run /ss-legal disclosure for defensive disclosure — Cover the core innovation (design-computed DU → schedule) plus the 13 alternative embodiments. Priority: establish prior art before SmartRain or others file on design-derived scheduling approaches.
2. Run /ss-product spec for Phase 1 technical specification — Define the data flow from design engine through QWEL formula chain to Rachio API, including the species-specific dormancy algorithm and DFAF recommendations.
3. Flag SmartRain US11,839,184B2 for counsel review — The AI/ML predictive soil moisture patent is the only moderate-risk item. Need legal opinion on whether SimplyScapes' future advanced features could implicate Claim 11's historical event correlation pattern.
4. Conduct DU validation study — Measure field DU on 5–10 installed SimplyScapes-designed systems and compare against design-computed values. This quantifies DFAF recommendations and strengthens both the product and the defensive publication.
5. Publish open-source TypeScript ET library on npm — First ET computation library in the JavaScript ecosystem. Community goodwill, defensive publication value, and demonstrates technical credibility.
6. Explore Weathermatic SmartLink Connect partnership — Their hardware-agnostic platform strategy aligns with SimplyScapes' design-intelligence approach. Complementary, not competitive.

Sources

| # | Type | Reference | URL | |---|------|-----------|-----| | 1 | Standard | QWEL — Qualified Water Efficient Landscaper certification | https://qwel.net/ | | 2 | Standard | ANSI/ASABE S623.1 (R2022) — Determining Landscape Plant Water Demands | https://webstore.ansi.org/standards/asabe/ansiasabes623jan2017r2022 | | 3 | Standard | EPA WaterSense Water Budget Tool v2.0 | https://www.epa.gov/watersense | | 4 | Standard | California MWELO — Model Water Efficient Landscape Ordinance | https://water.ca.gov/Programs/Water-Use-And-Efficiency/Urban-Water-Use-Efficiency/Model-Water-Efficient-Landscape-Ordinance | | 5 | Database | WUCOLS V — Water Use Classification of Landscape Species, UC Davis | https://wucols.ucdavis.edu/ | | 6 | Database | USU CWEL SLIDE Rules | https://extension.usu.edu/cwel/slide-rules | | 7 | API | Open-Meteo — Free Weather & ETo API | https://open-meteo.com/ | | 8 | API | Rachio Public API v2.0 | https://rachio.readme.io/ | | 9 | Platform | OpenET — Satellite-Derived Evapotranspiration | https://etdata.org/ | | 10 | API | CIMIS — California Irrigation Management Information System | https://cimis.water.ca.gov/ | | 11 | Software | pyfao56 v1.4.0 — USDA-ARS FAO-56 implementation | https://github.com/kthorp/pyfao56 | | 12 | Software | pyETo — FAO-56 Penman-Monteith ETo in Python | https://github.com/woodcrafty/PyETo | | 13 | Paper | Baum et al. (2005) — Residential irrigation DU study, Central Florida | — | | 14 | Paper | Playan et al. (2006) — Sprinkler simulation accuracy, R² = 97% | — | | 15 | Paper | Zapata et al. (2025) — Simulation accuracy SE = 1.1% | — | | 16 | Paper | Lunstad & Sowby (2024) — Smart Irrigation Controllers meta-analysis, ASCE JWRPM | https://ascelibrary.org/doi/10.1061/JWRMD5.WRENG-5871 | | 17 | Paper | Velpuri et al. (2023) — OpenET accuracy assessment, Nature Water | https://www.nature.com/articles/s44221-023-00181-7 | | 18 | Paper | Reitz et al. (2025) — OpenET model weighting, Water Resources Research | https://agupubs.onlinelibrary.wiley.com/doi/10.1029/2024WR038899 | | 19 | Paper | Qian & Engelke — Minimum Water Requirements of Four Turfgrasses, HortScience | — | | 20 | Paper | Blankenship (2020) — Water requirements by species and mowing height | https://acsess.onlinelibrary.wiley.com/doi/full/10.1002/cft2.20020 | | 21 | Paper | Scientific Reports (2023) — ML-based DU prediction from system parameters | https://www.nature.com/articles/s41598-023-47688-3 | | 22 | Paper | Journal of Hydrology (2023) — Soil redistribution under sprinkler irrigation | https://www.sciencedirect.com/science/article/abs/pii/S0022169423012982 | | 23 | Paper | Saikai et al. (2023) — Deep RL for irrigation scheduling, PLOS Water | https://journals.plos.org/water/article?id=10.1371/journal.pwat.0000169 | | 24 | USGA | Dynamic Water Use Models for Turfgrass (2025) — Green Section Record 63(17) | https://www.usga.org/content/usga/home-page/course-care/green-section-record/63/issue-17/dynamic-water-use-models-for-improved-irrigation-scheduling.html | | 25 | Extension | UC ANR Turfgrass Crop Coefficients | https://ucanr.edu/sites/UrbanHort/Water_Use_of_Turfgrass_and_Landscape_Plant_Materials/Turfgrass_Crop_Coefficients_Kc | | 26 | Extension | Texas A&M AgriLife Turfgrass Program | https://aggieturf.tamu.edu/ | | 27 | Extension | Purdue Turf GDD Applications | https://turf.purdue.edu/use-growing-degree-days-to-better-time-your-applications/ | | 28 | App | Water My Yard — Texas A&M AgriLife Extension | https://watermyyard.org/ | | 29 | Patent | US9,307,706B2 — SmartRain Irrigation Management (2014) | https://patents.google.com/patent/US9307706B2 | | 30 | Patent | US10,660,279B2 — SmartRain Irrigation Management (2018) | https://patents.google.com/patent/US10660279B2 | | 31 | Patent | US11,185,024B2 — SmartRain Map Integration (2019) | https://patents.google.com/patent/US11185024B2 | | 32 | Patent | US11,684,029B2 — SmartRain Landscaper Integration (2020) | https://patents.google.com/patent/US11684029B2 | | 33 | Patent | US11,839,184B2 — SmartRain AI Irrigation (2020) | https://patents.google.com/patent/US11839184B2 | | 34 | Patent | US20210176931A1 — SmartRain Soil Sensor Grid (2021) | https://patents.google.com/patent/US20210176931A1 | | 35 | Patent | US10,028,454B2 — Husqvarna/ETwater (closest prior art) | https://patents.google.com/patent/US10028454B2 | | 36 | Patent | US7,337,042 — HydroPoint (expired, ET scheduling public domain) | https://patents.google.com/patent/US7337042 | | 37 | Patent | US7,596,429B2 — WeatherTRAK (DU as user input) | https://patents.google.com/patent/US7596429B2 | | 38 | Product | Rachio Flex Daily FAQ | https://support.rachio.com/en_us/flex-daily-schedules-faq-BJ2YPIJKw | | 39 | Product | Hunter Hydrawise API | https://www.hunterirrigation.com/support/hydrawise-api-information | | 40 | Product | Weathermatic SmartLink | https://www.weathermatic.com/products/smartlink/ | | 41 | Product | HydroPoint WeatherTRAK | https://www.hydropoint.com/weathertrak/ | | 42 | Product | ETwater / Jain Unity | https://www.jainunity.com/ | | 43 | Product | Calsense CS3000 / IMaaS | https://calsense.com/ | | 44 | Product | Land F/X Irrigation Module | https://www.landfx.com/ | | 45 | Product | IrriCad Design Software | https://www.irricad.com/ | | 46 | Product | SmartRain Systems | https://smartrainsystems.com/ | | 47 | Product | OpenSprinkler | https://opensprinkler.com/ | | 48 | Product | RainMachine (discontinued) | https://www.rainmachine.com/ | | 49 | Product | Orbit B-hyve | https://bhyve.orbitonline.com/ | | 50 | Product | Rain Bird ARC8 / IQ4 | https://www.rainbird.com/ | | 51 | Product | Toro Tempus | https://www.toro.com/ | | 52 | Product | Netafim GrowSphere | https://www.netafim.com/en/digital-farming/ | | 53 | Product | CropX Digital Agronomy | https://cropx.com/ | | 54 | Product | Banyan Water | https://banyanwater.com/ | | 55 | Product | Dropcountr (KUBRA) | https://www.dropcountr.com/ | | 56 | Product | Phytech | https://www.phytech.com/ | | 57 | Product | DTN / ClearAg | https://docs.clearag.com/ | | 58 | Data | gridMET — Daily Surface Meteorological Data | https://www.climatologylab.org/gridmet.html | | 59 | Data | NTEP — National Turfgrass Evaluation Program | https://www.ntep.org/ | | 60 | Conference | AGU Fall Meeting H11P-0899 (2024) — OpenET urban turfgrass validation | — | | 61 | Paper | J. Cleaner Production (2023) — Digital twin for smart farming irrigation | https://www.sciencedirect.com/science/article/abs/pii/S0959652623000781 | | 62 | Supporting | QWEL Formula Chain Analysis | supporting/qwel-formula-chain.md | | 63 | Supporting | Design-Computed DU Research | supporting/design-computed-du.md | | 64 | Supporting | Species-Specific Turf Factors | supporting/species-specific-turf-factors.md | | 65 | Supporting | Smart Controller APIs | supporting/smart-controller-apis.md | | 66 | Supporting | Patent Landscape & FTO Analysis | supporting/patent-landscape-fto.md | | 67 | Supporting | Advanced Scheduling Intelligence | supporting/advanced-scheduling-intelligence.md | | 68 | Supporting | Vertical Competitor Analysis | supporting/vertical-competitor-analysis.md | | 69 | Supporting | Adjacent Market & Academic Scan | supporting/adjacent-market-academic.md |

QWEL Formula Chain: ETo to Per-Zone Runtime Minutes

Parent: SS-RP-2026-002 | Date: 2026-03-01 ClickUp: Automated Turf Irrigation Scheduling Type: Supporting Research -- Formula Chain Reference

---

1. Complete Formula Chain

This section documents the full formula chain used in ET-based landscape irrigation scheduling, from raw reference evapotranspiration to per-zone runtime minutes with cycle-soak splits. The chain is consistent across QWEL, MWELO, and the Irrigation Association's recommended practices, though each methodology uses slightly different variable names and default values.

1.1 Overview

The formula chain has six sequential steps:

Step 1: ETo                              (reference evapotranspiration, inches/month)
Step 2: ETo x PF = ETc                   (crop/landscape evapotranspiration)
Step 3: ETc - Pe = IWR                   (irrigation water requirement)
Step 4: IWR x SM = Gross Irrigation      (adjusted for distribution uniformity)
Step 5: Gross / PR = Total Runtime        (convert inches to minutes)
Step 6: Runtime / Cycles = Per-Cycle RT   (cycle-soak splitting)

1.2 Step 1 -- Reference Evapotranspiration (ETo)

Definition: ETo is the evapotranspiration rate of a well-watered, 4-7 inch tall, cool-season grass reference surface. It represents the atmospheric demand for water independent of crop type.

Calculation method: The industry standard is the ASCE Standardized Reference Evapotranspiration Equation, based on the FAO-56 Penman-Monteith equation. The equation uses four weather parameters:

• Solar radiation (Rs)
• Air temperature (T)
• Wind speed (u2)
• Relative humidity / vapor pressure deficit (ea, es)

The ASCE standardized form for a short reference crop (ETo) uses numerator constant Cn = 900 and denominator constant Cd = 0.34 for daily time steps.

Units: inches/day, inches/month, or mm/day (1 mm = 0.03937 in)

Data sources: See Section 2 for a detailed comparison of ETo data providers (CIMIS, USU Climate Center, Open-Meteo, gridMET).

1.3 Step 2 -- Crop/Landscape Evapotranspiration (ETc or ETL)

Formula:

ETc = ETo x PF

Or equivalently in MWELO notation:

ETL = ETo x KL

Where:

| Variable | Name | Definition | Units | |----------|------|------------|-------| | ETo | Reference Evapotranspiration | Atmospheric water demand for reference grass | inches/period | | PF | Plant Factor | Ratio of plant water use to ETo (SLIDE/QWEL terminology) | dimensionless | | KL | Landscape Coefficient | Equivalent to PF in MWELO terminology | dimensionless | | ETc | Crop Evapotranspiration | Actual water demand of the planted landscape | inches/period | | ETL | Landscape Evapotranspiration | MWELO terminology for ETc | inches/period |

Plant Factor (PF) vs. Landscape Coefficient (KL):

The terms are used interchangeably in practice, but they originate from different methodologies:

• PF (Plant Factor): Used by QWEL, SLIDE, and ANSI/ASABE S623.1. A single value per plant type category. Simple and direct.
• KL (Landscape Coefficient): Used by MWELO. A composite of three sub-factors: KL = Ks x Kd x Kmc (species factor x density factor x microclimate factor).

Standard PF values for turf (SLIDE / ANSI/ASABE S623.1):

| Plant Type | PF | Source | |------------|-----|--------| | Cool-season turfgrass (Kentucky bluegrass, tall fescue, ryegrass, bentgrass) | 0.80 | SLIDE / WUCOLS | | Warm-season turfgrass (bermudagrass, zoysiagrass, St. Augustinegrass) | 0.60 | SLIDE / WUCOLS | | Trees, shrubs, vines, groundcovers | 0.50 | SLIDE | | Desert-adapted plants | 0.30 | SLIDE | | Herbaceous perennials | 0.50 | SLIDE | | Annual flowers & bedding plants | 0.80 | SLIDE |

Monthly crop coefficients (Kc) for turfgrass (UC Davis research):

Cool-season turfgrass (annual average Kc = 0.80):

| Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | |-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| | 0.60 | 0.60 | 0.80 | 1.04 | 1.00 | 0.96 | 0.96 | 0.96 | 0.80 | 0.80 | 0.80 | 0.60 |

Warm-season turfgrass (annual average Kc = 0.60):

| Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | |-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| | 0.56 | 0.54 | 0.56 | 0.67 | 0.79 | 0.75 | 0.75 | 0.75 | 0.67 | 0.54 | 0.56 | 0.56 |

Note on UC Davis Kc data: Warm-season species require approximately 20% less water than cool-season species during the growing season. For minimal acceptable quality, cool-season turf can survive at approximately 60% of ETo, while warm-season turf can survive at approximately 40% of ETo. The PF values of 0.80 and 0.60 represent the target for good quality appearance, not mere survival.

MWELO Landscape Coefficient (KL) sub-factors:

KL = Ks x Kd x Kmc

| Sub-factor | Name | Low | Medium | High | |------------|------|-----|--------|------| | Ks | Species Factor | 0.2 | 0.5 | 0.9 | | Kd | Density Factor | 0.5 | 1.0 | 1.3 | | Kmc | Microclimate Factor | 0.5 | 1.0 | 1.4 |

For a typical turf zone (medium density, average microclimate):

• Cool-season: KL = 0.9 x 1.0 x 1.0 = 0.90 (MWELO uses higher Ks than SLIDE PF)
• Warm-season: KL = 0.6 x 1.0 x 1.0 = 0.60

Implementation note for SimplyScapes: Use the SLIDE plant factor values (PF = 0.80 / 0.60) for operational scheduling. These are simpler, scientifically grounded, and align with the QWEL certification training. The MWELO KL approach with Ks/Kd/Kmc is primarily for compliance water budget (MAWA/ETWU) calculation, not runtime scheduling.

1.4 Step 3 -- Irrigation Water Requirement (IWR)

Formula:

IWR = ETc - Pe

Where:

| Variable | Name | Definition | Units | |----------|------|------------|-------| | IWR | Irrigation Water Requirement | Net water that must be supplied by irrigation | inches/period | | ETc | Crop Evapotranspiration | Plant water demand (from Step 2) | inches/period | | Pe | Effective Precipitation | Portion of rainfall usable by plants | inches/period |

Effective Precipitation (Pe) calculation:

Multiple methods exist for estimating effective precipitation. The landscape irrigation industry typically uses simplified approaches:

1. SLIDE / ANSI/ASABE S623.1 method: Pe = 50% of actual precipitation

   Pe = P x 0.50
   

   This is the standard for landscape irrigation demand estimation. The 50% factor accounts for runoff, deep percolation below the root zone, and evaporation from the soil surface.

2. USDA SCS method (simplified): Pe = (P - 0.25") x 0.80

   Pe = (P - 0.25) x 0.80    (where P > 0.25"; otherwise Pe = 0)
   

   This method deducts the first 0.25 inches as interception loss, then applies an 80% effectiveness factor.

3. WaterSense approach: Uses monthly effective precipitation directly from the Water Budget Data Finder tool. Only months where ETo exceeds effective precipitation are included in the irrigation season.

4. Conservative approach (arid climates): Pe = 0 In arid regions (e.g., most of Utah, inland California), effective precipitation during the irrigation season is often negligible. Setting Pe = 0 is conservative and simplifies calculation.

Constraint: IWR cannot be negative. If Pe >= ETc for a given month, set IWR = 0 (no irrigation required that month).

1.5 Step 4 -- Gross Irrigation Requirement (Adjusted for DU)

Formula using Scheduling Multiplier:

Gross Irrigation = IWR x SM

Or equivalently:

Gross Irrigation = IWR / IE

Where:

| Variable | Name | Definition | Units | |----------|------|------------|-------| | SM | Scheduling Multiplier | Factor to compensate for non-uniform application | dimensionless | | IE | Irrigation Efficiency | Fraction of applied water beneficially used | dimensionless |

Scheduling Multiplier (SM) formulas:

There are two common formulas for the scheduling multiplier. The choice between them has significant implications for systems with poor uniformity:

Method A -- Simple Inverse (QWEL / IA standard):

SM = 1 / DUlq

This method ensures the average of the lowest quarter of the irrigated area receives the target application depth. It means 87.5% of the area receives at least the target amount.

Example: DUlq = 0.70 --> SM = 1 / 0.70 = 1.43

Method B -- Capped Scheduling Multiplier (IA revised):

SM = 1 / (0.4 + (0.6 x DUlq))

This formula was proposed in an IA technical paper ("Revisiting the Scheduling Coefficient," 2009) to prevent excessive water application on systems with very poor uniformity. It incorporates the relationship between DUlq and DUlh (Distribution Uniformity of the lowest head).

Example: DUlq = 0.70 --> SM = 1 / (0.4 + (0.6 x 0.70)) = 1 / 0.82 = 1.22

Comparison of SM methods at various DU values:

| DUlq | SM (Method A: 1/DU) | SM (Method B: 1/(0.4+0.6*DU)) | |------|---------------------|-------------------------------| | 0.90 | 1.11 | 1.09 | | 0.80 | 1.25 | 1.14 | | 0.70 | 1.43 | 1.22 | | 0.60 | 1.67 | 1.32 | | 0.50 | 2.00 | 1.43 | | 0.40 | 2.50 | 1.56 | | 0.39 | 2.56 | 1.58 |

Critical note on user's DUlq = 0.39: The user's QWEL audit spreadsheet shows a measured DUlq of 0.39 for the test zone. Using Method A (1/DU), this yields SM = 2.56 -- meaning the system must apply 2.56x the target depth to ensure the driest quarter gets enough water. This is extremely poor uniformity. Method B would give SM = 1.58, which caps the over-application. For SimplyScapes, design-computed DU will typically range from 0.65-0.85, making the difference between methods less significant.

MWELO Irrigation Efficiency (IE) values:

MWELO uses a fixed IE instead of a DU-based scheduling multiplier:

| Irrigation Type | IE Value | |-----------------|----------| | Overhead spray devices | 0.75 | | Drip / micro-irrigation | 0.81 |

The MWELO IE is used for compliance water budget calculation (ETWU), not for operational scheduling. The relationship between IE and DU is: IE approximately equals DU for well-managed systems (IE includes application losses beyond non-uniformity).

1.6 Step 5 -- Total Runtime (Converting Inches to Minutes)

Formula:

Total Runtime (minutes) = (Gross Irrigation (inches) / PR (inches/hour)) x 60

Or equivalently:

Total Runtime (hours) = Gross Irrigation (inches) / PR (inches/hour)

Where:

| Variable | Name | Definition | Units | |----------|------|------------|-------| | PR | Precipitation Rate | Rate at which the sprinkler system applies water | inches/hour | | Gross Irrigation | Adjusted IWR | Water depth to apply per irrigation event | inches | | Total Runtime | Run time | How long the zone must run per irrigation event | minutes |

Typical Precipitation Rates by sprinkler type:

| Sprinkler Type | PR Range (in/hr) | Common Default | |----------------|-------------------|----------------| | Conventional spray heads | 1.3 -- 2.0 | 1.5 | | Gear-drive rotors | 0.4 -- 1.0 | 0.5 -- 0.6 | | Rotary nozzles (MP Rotator) | 0.4 -- 0.8 | 0.4 | | MP800 (short throw rotary) | 0.8 | 0.8 | | Rain Bird R-VAN | 0.4 -- 0.8 | 0.61 (user data) | | Drip irrigation | varies by emitter | measured in GPH |

Precipitation Rate formula (from manufacturer data or catch can test):

PR (in/hr) = (GPM x 96.3) / Area (sq ft)

Where 96.3 is a conversion constant (gallons per minute to inches per hour over one square foot). Some references use 96.25.

Splitting monthly runtime into individual irrigation events:

Runtime per event = Monthly Total Runtime / Events per month
Events per month = Irrigation days per week x (days in month / 7)

Example:

• Monthly Gross Irrigation = 4.5 inches
• PR = 0.61 in/hr
• Total monthly runtime = (4.5 / 0.61) x 60 = 443 minutes
• Watering 3 days/week = 3 x 4.3 = 12.9 events/month
• Runtime per event = 443 / 12.9 = 34.3 minutes --> round up to 35 minutes

1.7 Step 6 -- Cycle-Soak Splitting

Purpose: When the sprinkler precipitation rate exceeds the soil's infiltration rate, water pools on the surface and runs off. Cycle-soak splitting breaks a single long runtime into multiple shorter cycles separated by soak periods, allowing water to infiltrate between cycles.

Formula:

Number of Cycles = CEILING(Runtime per event / Time-to-Runoff)
Runtime per Cycle = Runtime per event / Number of Cycles

Or rounded up:

Runtime per Cycle = CEILING(Runtime per event / Number of Cycles)

Time-to-Runoff calculation:

Time-to-Runoff (minutes) = (Soil Infiltration Rate (in/hr) / PR (in/hr)) x 60

This assumes a flat surface. For slopes, the effective infiltration rate decreases.

Soak time: The minimum soak period between cycles is typically the same as the cycle duration, or at least 30 minutes for clay soils. Controllers like RainMachine recommend soak time equal to or greater than watering duration.

See Section 4 for detailed soil infiltration rates and cycle-soak tables by soil type and slope.

1.8 Complete Worked Example

Given:

• Location: Orem, UT (zip 84057)
• Month: July
• ETo = 8.5 inches/month (from USU Climate Center)
• Plant: Cool-season turfgrass (Kentucky bluegrass)
• PF = 0.80
• Monthly precipitation = 0.5 inches
• DUlq = 0.70 (design-computed)
• PR = 0.61 in/hr (Rain Bird R-VAN24)
• Soil: Clay loam (infiltration rate = 0.3 in/hr)
• Slope: 0-3% (flat)
• Watering days: 3 per week

Calculation:

Step 1: ETo = 8.50 in/month

Step 2: ETc = ETo x PF
       ETc = 8.50 x 0.80 = 6.80 in/month

Step 3: Pe = P x 0.50 = 0.50 x 0.50 = 0.25 in/month
       IWR = ETc - Pe = 6.80 - 0.25 = 6.55 in/month

Step 4: SM = 1 / DUlq = 1 / 0.70 = 1.43
       Gross = IWR x SM = 6.55 x 1.43 = 9.37 in/month

Step 5: Events/month = 3 days/week x (31/7) = 13.3
       Gross per event = 9.37 / 13.3 = 0.70 in/event
       Runtime per event = (0.70 / 0.61) x 60 = 68.9 min --> 69 min

Step 6: Time-to-runoff = (0.30 / 0.61) x 60 = 29.5 min --> 29 min
       Cycles = CEILING(69 / 29) = 3
       Runtime per cycle = CEILING(69 / 3) = 23 min
       Soak time = 30 min (minimum for clay loam)

SCHEDULE: 3 cycles x 23 minutes, with 30-minute soak between cycles
         Run at 4:00 AM, 4:53 AM, 5:46 AM
         Repeat 3 days per week (e.g., Mon/Wed/Fri)

---

2. ETo Data Sources Comparison

All ET-based scheduling requires a reliable source of reference evapotranspiration data. The choice of ETo data source affects accuracy, geographic coverage, cost, and API integration complexity.

2.1 CIMIS (California Irrigation Management Information System)

| Attribute | Detail | |-----------|--------| | Provider | California Department of Water Resources | | URL | https://cimis.water.ca.gov/ | | API Endpoint | https://et.water.ca.gov/api/data | | Coverage | California only (150+ weather stations; statewide Spatial CIMIS at 2km grid) | | Resolution | Station-level (point) or 2km grid (Spatial CIMIS) | | Temporal | Daily and hourly (hourly only from weather stations, not spatial) | | ETo Variable | day-asce-eto (ASCE Penman-Monteith) | | Method | ASCE Standardized PM (Cn=900, Cd=0.34) | | Data Range | June 7, 1982 -- present | | Cost | Free (requires API key registration) | | Auth | Application key (appKey parameter) | | Target Types | Station number, zip code, lat/lng, street address | | Response Format | JSON or XML | | Limitations | California only; hourly data only from WSN (not spatial); zip code queries limited to CA census zip codes | | Quality | Gold standard for California; station data includes quality control codes |

Example API call:

https://et.water.ca.gov/api/data?appKey=YOUR_KEY&targets=84057&startDate=2025-07-01&endDate=2025-07-31&dataItems=day-asce-eto,day-precip

Note: CIMIS is California-only. Not usable for Utah (zip 84057) or most other states.

2.2 USU Climate Center (Utah Climate Center)

| Attribute | Detail | |-----------|--------| | Provider | Utah State University | | URL | https://climate.usu.edu/ | | Coverage | Utah (69 locations with 20-year averages; 54 AGWX stations; 19 AgriMet stations; 16 UCRN stations) | | Resolution | Station-level (point); MapServer for spatial interpolation | | Temporal | Daily (real-time from stations); monthly/annual averages compiled | | ETo Calculation | ASCE Standardized PM (Penman-Monteith) for both short (ETo) and tall (ETr) crops | | Data Range | 2000-2022 averages; real-time from active stations | | Cost | Free | | API | MapServer interface at https://climate.usu.edu/mapServer/mapGUI/index.php | | Limitations | Utah only; no formal REST API with zip code lookup; averages may not reflect current year conditions | | Quality | High quality for Utah; 20-year averaging smooths anomalies |

Annual ETo range in Utah:

• Lowest: Alta, UT = 29.84 in/year
• Highest: St. George, UT = 59.68 in/year
• Logan area: ~43 in/year
• Moab: ~56 in/year

Note: The user's QWEL spreadsheet uses USU Climate Center data for zip 84057 (Orem, UT). The monthly ETo values from this source are pre-computed long-term averages, suitable for fixed monthly scheduling but not for real-time weather-responsive schedules.

2.3 Open-Meteo

| Attribute | Detail | |-----------|--------| | Provider | Open-Meteo (open source, Swiss-based) | | URL | https://open-meteo.com/ | | Forecast API | https://api.open-meteo.com/v1/forecast | | Historical API | https://archive-api.open-meteo.com/v1/archive | | Coverage | Global | | Resolution | 1-11 km (varies by weather model; up to 2 km in some regions) | | Temporal | Hourly and daily | | ETo Variable | et0_fao_evapotranspiration (daily sum, in mm) | | Method | FAO-56 Penman-Monteith (calculated from temperature, wind speed, humidity, solar radiation) | | Forecast Range | Up to 16 days | | Historical Range | 1940 -- present (via ERA5 reanalysis) | | Cost | Free for non-commercial / open source; commercial plans available | | Auth | No API key required for free tier | | Response Format | JSON | | Limitations | Resolution varies by region; reanalysis data may overestimate ETo compared to station data; mm units require conversion for US applications | | Quality | Good for global coverage; ETo derived from weather model output, not direct station measurement |

Example API call (forecast):

GET https://api.open-meteo.com/v1/forecast?latitude=40.29&longitude=-111.69&daily=et0_fao_evapotranspiration,precipitation_sum&timezone=America/Denver

Example API call (historical):

GET https://archive-api.open-meteo.com/v1/archive?latitude=40.29&longitude=-111.69&start_date=2025-07-01&end_date=2025-07-31&daily=et0_fao_evapotranspiration,precipitation_sum&timezone=America/Denver

Recommended for SimplyScapes Phase 1: Open-Meteo is the strongest candidate for SimplyScapes because it provides: (a) global coverage (not limited to one state), (b) no API key requirement, (c) both forecast and historical ETo, (d) free for commercial use with attribution, (e) coordinates-based lookup that works with any address. The SS-TD-2026-001 defensive disclosure already references Open-Meteo.

2.4 gridMET

| Attribute | Detail | |-----------|--------| | Provider | University of Idaho Climatology Lab | | URL | https://www.climatologylab.org/gridmet.html | | Access | THREDDS OPeNDAP, NetCDF direct download, PyGridMET (Python), Climate Engine | | Download URL | http://www.northwestknowledge.net/metdata/data/ | | Coverage | Contiguous US (CONUS) only | | Resolution | ~4 km (1/24th degree) | | Temporal | Daily | | ETo Variables | pet (grass reference ETo, mm), etr (alfalfa reference ETr, mm) | | Method | ASCE Standardized PM; derived from PRISM + NLDAS-2 blending | | Data Range | 1979 -- present (updated daily) | | Cost | Free | | Auth | None for direct download; Google Earth Engine access available | | Response Format | NetCDF | | Limitations | CONUS only; 12-31% median overestimation bias vs. station data (air temp, radiation overestimated, humidity underestimated); NetCDF format requires specialized processing | | Quality | Good spatial coverage; known systematic bias should be accounted for |

File naming convention:

etr_2025.nc    (alfalfa reference ET)
pet_2025.nc    (grass reference ETo)

Bias warning: Research has found gridMET overestimates reference ET by 12-31% compared to weather station data, primarily due to overstatement of air temperature, shortwave radiation, and wind speed, and understatement of humidity. Any use of gridMET data for scheduling should apply a bias correction factor.

2.5 ETo Data Sources Comparison Summary

| Feature | CIMIS | USU Climate | Open-Meteo | gridMET | |---------|-------|-------------|------------|---------| | Coverage | CA only | UT only | Global | CONUS | | Resolution | 2km / station | Station | 1-11 km | 4 km | | Real-time | Yes | Yes | Yes | Yes (1-day delay) | | Forecast | No | No | Yes (16-day) | No | | Historical | 1982+ | 2000+ | 1940+ | 1979+ | | API type | REST (JSON/XML) | Web/MapServer | REST (JSON) | OPeNDAP/NetCDF | | API key | Required | N/A | Not required | N/A | | ETo method | ASCE PM | ASCE PM | FAO-56 PM | ASCE PM | | Cost | Free | Free | Free (non-commercial) | Free | | Bias | Reference (station) | Low (station) | Model-derived | 12-31% high | | Best for | CA projects | UT projects | National/global SaaS | Bulk analysis |

---

3. Methodology Comparison: QWEL vs. WaterSense 2.0 vs. MWELO

3.1 Purpose and Scope

| Aspect | QWEL | WaterSense 2.0 | MWELO | |--------|------|----------------|-------| | Full Name | Qualified Water Efficient Landscaper | EPA WaterSense Homes Specification v2.0 | Model Water Efficient Landscape Ordinance | | Authority | EPA WaterSense (professional certification) | EPA WaterSense (homes certification) | California Department of Water Resources | | Purpose | Train professionals in irrigation auditing and scheduling | Certify water-efficient new homes | Regulate landscape water use in new construction | | Output | Per-zone irrigation schedule (runtime minutes) | Compliance water budget (pass/fail) | Compliance water budget (MAWA >= ETWU) | | Scope | Existing landscapes (retrofit/audit) | New home construction | New landscapes > 500 sq ft (CA) | | Produces schedule? | Yes | No (budget only) | No (budget only) |

3.2 Formula Comparison

Step-by-step comparison of each methodology's approach:

| Step | QWEL / IA | WaterSense 2.0 | MWELO | |------|-----------|----------------|-------| | ETo source | Local weather station or data service | Water Budget Data Finder (by zip code) | Local ETo from Appendix A or DWR | | Plant water use | PF (Plant Factor) from SLIDE or WUCOLS | Species factor from embedded database | KL = Ks x Kd x Kmc (landscape coefficient) | | Effective precip | Pe = P x 0.50 (SLIDE standard) | Built into tool (peak month analysis) | Not explicitly subtracted in MAWA formula | | Irrigation efficiency | DU-based (SM = 1/DUlq from catch can or design) | Default 58% application rate | IE = 0.75 (spray) or 0.81 (drip) | | Area calculation | Per-zone (actual zone sq ft) | Total landscape area | Per-hydrozone (LA) + special (SLA) | | Budget formula | Not a budget -- produces runtime | Water use <= budget threshold | ETWU <= MAWA | | Cycle-soak | Yes (based on soil type and PR) | Not addressed | Not addressed | | Output | Minutes per zone per day | Gallons per year (compliance) | Gallons per year (compliance) |

3.3 QWEL Scheduling Methodology (Operational)

QWEL uses the formula chain documented in Section 1 to produce actionable irrigation schedules. The QWEL certification training teaches professionals to:

1. Conduct a catch can test (24+ containers) to measure DUlq
2. Calculate PR from catch can data
3. Obtain ETo for the location from local data
4. Apply plant factors per zone
5. Calculate per-zone runtime using SM = 1/DUlq
6. Apply cycle-soak splitting based on soil type
7. Program the controller with the resulting schedule

The key differentiator: QWEL is the only methodology of the three that produces a per-zone irrigation schedule. WaterSense and MWELO produce compliance budgets only.

3.4 WaterSense 2.0 Water Budget Methodology (Compliance)

WaterSense 2.0 is a homes certification program, not a scheduling tool. Its water budget approach:

1. Irrigation season determination: Uses Growing Degree Days (GRDD) with a base temperature of 50 degrees F. A month is in the growing season if at least 50% of days have GRDD > 0 (i.e., average daily temperature exceeds 50 degrees F).

2. Peak watering month: The month where (ETo - effective precipitation) is greatest. All calculations are benchmarked against this peak month.

3. Landscape water allowance: Calculated as a maximum total water use for the landscape, using species-specific coefficients from an embedded database and a default irrigation application rate of 58%.

4. Pass/fail: The designed landscape either meets the water budget or does not. No schedule is produced.

Critique (from planning phase): The universal 50 degrees F GRDD threshold is problematic. Cool-season turfgrass (Kentucky bluegrass, tall fescue) actively grows below 50 degrees F -- it begins growth when soil temperatures reach 40-45 degrees F. Warm-season turfgrass (bermudagrass) goes dormant at higher soil temperatures (55-65 degrees F). A species-specific growing season determination would be more accurate. This is an identified whitespace for SimplyScapes.

3.5 MWELO Water Budget Methodology (Compliance)

MWELO is a California regulation that limits landscape water use through a water budget framework:

Maximum Applied Water Allowance (MAWA):

For residential areas:

MAWA = (ETo) x (0.62) x [(ETAF x LA) + ((1 - ETAF) x SLA)]

Where ETAF (ET Adjustment Factor) varies by use:

• Residential: ETAF = 0.55
• Non-residential (post-2025): ETAF = 0.45
• Special Landscape Area: ETAF = 1.0

The 0.62 conversion factor converts acre-inches/acre to gallons/sq ft (1 inch of water over 1 sq ft = 0.623 gallons).

Estimated Total Water Use (ETWU):

ETWU = sum of all hydrozones: (ETo x 0.62 x (PF / IE) x LA)

Where for each hydrozone:

• PF = Plant Factor from WUCOLS (or KL = Ks x Kd x Kmc)
• IE = 0.75 (overhead spray) or 0.81 (drip)
• LA = landscape area of the hydrozone (sq ft)

Compliance test: ETWU <= MAWA

Key relationship to operational scheduling: MWELO compliance does not produce a schedule. SimplyScapes already calculates ETWU and MAWA on the Water Budget tab. The formula chain in Section 1 produces the actual schedule. These two systems can be connected: the total water applied by the operational schedule (sum of all zone runtimes x PR x zone area) should not exceed MAWA.

3.6 Methodology Cross-Reference Matrix

| Variable | QWEL Name | WaterSense Name | MWELO Name | SLIDE Name | |----------|-----------|-----------------|------------|------------| | Reference ET | ETo | ETo | ETo | ETo | | Plant water use factor | PF | Species coefficient | KL (or PF/ETAF) | PF | | Irrigation efficiency | DUlq (via SM) | 58% application rate | IE (0.75/0.81) | DU | | Effective precipitation | Pe (50% of P) | Built-in | Not in MAWA formula | P x 0.50 | | Output | Runtime (min/zone) | Budget (gal/year) | Budget (gal/year) | Demand (gal) | | Schedule produced? | Yes | No | No | No (demand only) | | Cycle-soak? | Yes | No | No | No |

---

4. Cycle-Soak Splitting

4.1 Why Cycle-Soak is Necessary

When the sprinkler precipitation rate (PR) exceeds the soil's infiltration rate, water accumulates on the surface faster than it can absorb. On flat ground, this causes pooling. On slopes, it causes runoff. Cycle-soak splitting prevents this by breaking a single long irrigation event into multiple shorter cycles, with soak periods between them to allow infiltration.

4.2 Soil Infiltration Rates

The steady-state infiltration rate depends on soil texture. These are widely published values from USDA, NRCS, and university extension sources:

| Soil Texture | USDA Classification | Infiltration Rate (in/hr) | Notes | |-------------|---------------------|--------------------------|-------| | Coarse sand | Sand | > 2.0 | Rarely needs cycle-soak | | Sand | Sand | 0.8 -- 2.0 | Rarely needs cycle-soak | | Sandy loam | Sandy loam | 0.4 -- 0.8 | May need cycle-soak with spray heads | | Loam | Loam | 0.2 -- 0.4 | Needs cycle-soak with spray heads | | Silt loam | Silt loam | 0.2 -- 0.4 | Needs cycle-soak with spray heads | | Clay loam | Clay loam | 0.1 -- 0.3 | Needs cycle-soak with most sprinklers | | Silty clay | Silty clay | 0.1 -- 0.15 | Needs cycle-soak with all sprinklers | | Clay | Clay | 0.04 -- 0.2 | Always needs cycle-soak |

Note on flat-ground clay: Clay soil on flat ground has an infiltration rate of approximately 0.13 in/hr. All sprinkler types (spray heads at 1.5 in/hr, rotors at 0.5 in/hr, and rotary nozzles at 0.4 in/hr) exceed this rate.

4.3 Slope Effects on Infiltration

Slope reduces the effective infiltration rate because gravity pulls water downhill before it can infiltrate. The steeper the slope, the shorter the time to runoff.

Approximate slope reduction factors:

| Slope Grade | Slope Angle | Reduction Factor | Example: Clay (0.13 in/hr base) | |-------------|-------------|------------------|---------------------------------| | 0-3% | 0-2 deg | 1.00 (no reduction) | 0.13 in/hr | | 4-6% | 2-3 deg | 0.75 | 0.10 in/hr | | 7-12% | 4-7 deg | 0.50 | 0.065 in/hr | | 13-20% | 7-11 deg | 0.30 | 0.039 in/hr | | >20% | >11 deg | 0.20 | 0.026 in/hr |

Note: These are approximate reduction factors synthesized from multiple sources. Actual runoff behavior depends on soil compaction, organic matter, root density, thatch thickness, and antecedent moisture. Field observation remains the gold standard.

4.4 Maximum Runtime Before Runoff (by Soil Type and Sprinkler Type)

The maximum runtime before runoff is calculated as:

Max Runtime (min) = (Soil Infiltration Rate / Precipitation Rate) x 60

Calculated maximum runtimes (minutes) -- flat ground, no slope:

| Soil Type | Infil. Rate | Spray (1.5 in/hr) | Rotor (0.5 in/hr) | Rotary (0.4 in/hr) | |-----------|-------------|--------------------|--------------------|---------------------| | Sand | 1.0 | 40 | 120 | 150 | | Sandy loam | 0.6 | 24 | 72 | 90 | | Loam | 0.3 | 12 | 36 | 45 | | Clay loam | 0.2 | 8 | 24 | 30 | | Clay | 0.13 | 5 | 16 | 20 |

Maximum runtimes with slope -- clay loam (0.2 in/hr base), rotor (0.5 in/hr):

| Slope | Effective Infil. | Max Runtime | |-------|-----------------|-------------| | 0-3% | 0.20 in/hr | 24 min | | 4-6% | 0.15 in/hr | 18 min | | 7-12% | 0.10 in/hr | 12 min | | 13-20% | 0.06 in/hr | 7 min |

4.5 Weathermatic SmartLink Reference Values

Weathermatic (SmartLink controllers) provides specific cycle-soak parameters in their documentation:

Spray heads on flat ground (0% slope):

| Soil Type | Max Cycle Time | Min Soak Time | |-----------|---------------|---------------| | Sand | 24 min | 18 min | | Loam | 12 min | 15 min | | Clay | 8 min | 11 min |

Soak time guidance:

• Minimum soak = at least equal to cycle duration
• For clay soils: minimum 30 minutes recommended
• RainMachine (EPA WaterSense algorithm): soak >= zone watering duration, never less than 30 minutes

4.6 Cycle-Soak Algorithm for SimplyScapes

Inputs:

• runtime_per_event (minutes) -- from Step 5 of formula chain
• soil_type -- from property data or user input
• slope_percent -- from zone data or user input
• PR -- precipitation rate for the zone (from design)

Algorithm:

def calculate_cycle_soak(runtime_per_event, soil_infiltration_rate,
                          slope_percent, precipitation_rate):
    # Apply slope reduction factor
    if slope_percent <= 3:
        slope_factor = 1.00
    elif slope_percent <= 6:
        slope_factor = 0.75
    elif slope_percent <= 12:
        slope_factor = 0.50
    elif slope_percent <= 20:
        slope_factor = 0.30
    else:
        slope_factor = 0.20

    effective_infiltration = soil_infiltration_rate * slope_factor

    # Calculate maximum runtime before runoff
    if precipitation_rate <= effective_infiltration:
        # No cycle-soak needed -- soil absorbs faster than applied
        return {
            'cycles': 1,
            'runtime_per_cycle': math.ceil(runtime_per_event),
            'soak_minutes': 0
        }

    max_runtime = (effective_infiltration / precipitation_rate) * 60
    max_runtime = max(max_runtime, 2)  # minimum 2-minute cycle

    # Calculate number of cycles
    num_cycles = math.ceil(runtime_per_event / max_runtime)
    runtime_per_cycle = math.ceil(runtime_per_event / num_cycles)

    # Soak time: max of cycle duration or 30 minutes for heavy soils
    soak_minutes = max(runtime_per_cycle, 30 if effective_infiltration < 0.2 else 15)

    return {
        'cycles': num_cycles,
        'runtime_per_cycle': runtime_per_cycle,
        'soak_minutes': soak_minutes
    }

4.7 User's Data Point: Time-to-Runoff = 20 Minutes

The user's QWEL audit spreadsheet records a time-to-runoff of 20 minutes for the test zone. This is consistent with:

• Clay loam soil (infiltration ~0.2 in/hr)
• Rotary nozzle (R-VAN at 0.61 in/hr)
• Flat or near-flat slope
• Calculated: (0.2 / 0.61) x 60 = 19.7 minutes -- matches the user's observed 20 minutes almost exactly

---

5. Edge Cases and Limitations

5.1 Zero-Precipitation Months (Arid Climates)

In arid regions (most of Utah, inland California, Arizona, Nevada), summer months have negligible rainfall. The formula chain handles this correctly: Pe = 0, so IWR = ETc. No special handling needed.

5.2 Months Where Precipitation Exceeds ETc

When Pe >= ETc, IWR = 0 (clamped, cannot go negative). No irrigation is needed. This typically occurs in winter months or during the shoulder season in wetter climates. The schedule should show zero runtime for these months.

5.3 Very Low DU (Below 0.50)

Systems with DUlq below 0.50 are severely non-uniform. The 1/DU scheduling multiplier produces values above 2.0, meaning more than half the applied water is wasted on over-irrigated areas. In practice:

• DUlq < 0.50: System should be repaired/redesigned before scheduling.
• DUlq 0.50-0.60: Poor system; schedule will work but waste significant water. Flag for user attention.
• DUlq 0.60-0.70: Below average; workable with cycle-soak.
• DUlq 0.70-0.85: Typical range for well-designed systems.
• DUlq > 0.85: Excellent; minor scheduling multiplier impact.

For design-computed DU, SimplyScapes should flag zones with DU < 0.60 as needing design adjustment before generating schedules.

5.4 Mixed Species in a Zone

The SLIDE rules state that when plant types are mixed in a hydrozone, the water demand is governed by the plant type with the highest PF. For turf, this means if a zone has both cool-season (PF = 0.80) and warm-season (PF = 0.60) turf, use PF = 0.80 for the zone.

In SimplyScapes, each zone should have a single plant type assignment. The irrigation design already associates zones with specific head types and areas. The plant type (and therefore PF) should be a zone property.

5.5 Extreme Heat Events

During extreme heat (ETo >> historical average), the formula chain automatically increases irrigation because the schedule is driven by ETo. If using real-time ETo from Open-Meteo, the schedule will self-adjust. If using historical monthly averages (USU Climate Center), extreme heat will not be captured, potentially causing drought stress.

Recommendation: Use forecast ETo for real-time scheduling (Open-Meteo daily forecast) and historical averages only for baseline schedule planning.

5.6 Frost and Dormancy

When air temperatures drop below freezing, irrigation should be suspended regardless of ETo calculations. The formula chain does not account for frost. A separate frost guard should:

1. Suspend irrigation when forecast low temperature < 35 degrees F
2. Resume when temperatures recover and growing season conditions return

For cool-season turf, irrigation may still be needed in early spring and late fall when temperatures are above freezing but below 50 degrees F. For warm-season turf, irrigation should stop when the grass enters dormancy (typically when soil temperatures drop below 55 degrees F).

5.7 Wind Effects on DU

Design-computed DU assumes calm conditions. Wind degrades uniformity significantly. The IA recommends applying a wind derating factor to DU:

• Wind < 5 mph: No adjustment
• Wind 5-10 mph: Reduce DU by 10-15%
• Wind > 10 mph: Reduce DU by 15-25%

SimplyScapes should consider either applying a default wind derating or allowing the user to specify expected wind conditions.

5.8 New Turf Establishment

Newly planted turf (sod or seed) requires significantly more water during establishment than the formula chain produces. Establishment watering follows a different schedule:

• Sod (weeks 1-2): Multiple short cycles per day (3-4x/day, 5-10 minutes each) to keep surface moist
• Seed (weeks 1-4): Light, frequent watering (4-6x/day, 3-5 minutes) to prevent seed desiccation
• Tapering (weeks 2-6 for sod, weeks 4-8 for seed): Gradually reduce frequency, increase depth

The formula chain should only be applied once turf is established (typically 6-8 weeks after planting for sod, 8-12 weeks for seed).

5.9 Water Restrictions

Many water districts impose watering day and time restrictions (e.g., no watering on certain days, no watering between 10 AM and 6 PM). The formula chain produces total water need; the schedule must then be constrained to fit within allowed windows. If the required runtime exceeds the allowed window, the system is under-irrigating and should alert the user.

SimplyScapes already displays water district alerts (Weber Basin Water Conservancy District).

---

6. Relationship Between Compliance Budget and Operational Schedule

6.1 Two Parallel Systems

SimplyScapes maintains two parallel water accounting systems:

1. Compliance budget (MWELO/WaterSense): ETWU <= MAWA

   • Calculated annually
   • Uses fixed IE values (0.75 spray, 0.81 drip)
   • Produces gallons/year
   • Already implemented on the Water Budget tab

2. Operational schedule (QWEL formula chain): Per-zone runtime

   • Calculated monthly (or more frequently with real-time ETo)
   • Uses actual DU from design
   • Produces minutes/zone/event
   • Target of this research

6.2 The Connection

The total water applied by the operational schedule should not exceed the compliance budget. This creates a feedback loop:

Operational Water Use = SUM over all zones:
    (Runtime per event x Events per month x PR x Zone Area x 0.623) / 12

MAWA = (ETo) x (0.62) x [(ETAF x LA) + ((1 - ETAF) x SLA)]

Compliance check: Annual Operational Water Use <= MAWA

Key insight: If the operational schedule uses the same PF and a DU-based efficiency that is worse than MWELO's assumed IE (0.75), the operational schedule may exceed MAWA. This would happen when:

1 / DUlq > 1 / 0.75    -->    DUlq < 0.75

For zones with DUlq < 0.75, the operational schedule will use more water than MWELO's compliance budget assumes. This is a real-world problem: the MWELO budget is optimistic about irrigation efficiency.

6.3 Reconciliation Strategy

SimplyScapes can bridge the gap between compliance and operations by:

1. Computing both independently: Run the ETWU/MAWA calculation (already done) and the formula chain schedule (new).

2. Comparing the results: Show the user whether their operational schedule will exceed, meet, or under-run the MWELO budget.

3. Flagging problem zones: If a zone's DU is so low that its scheduled water use pushes total ETWU above MAWA, alert the user that the irrigation design needs improvement.

4. Adjusting PF for conservation: The user can reduce PF below the standard values (e.g., from 0.80 to 0.70 for cool-season turf) to stay within budget at the cost of slightly reduced turf quality.

6.4 From Budget to Schedule (the Missing Link)

No existing product closes the loop from compliance budget to operational schedule. This is SimplyScapes' opportunity:

| System | MWELO Budget | QWEL Schedule | |--------|-------------|---------------| | Input: ETo | Yes (annual/monthly) | Yes (monthly/daily) | | Input: Plant Factor | Yes (per hydrozone) | Yes (per zone) | | Input: Area | Yes (per hydrozone) | Yes (per zone) | | Input: IE / DU | IE = 0.75/0.81 (fixed) | DU = design-computed | | Input: PR | No | Yes (from design) | | Input: Soil / Slope | No | Yes (for cycle-soak) | | Output | Gallons/year (budget) | Minutes/zone/event (schedule) | | Cycle-soak | No | Yes | | Controller-ready | No | Yes |

The formula chain documented in this paper is the bridge.

---

7. Sources

| # | Type | Reference | URL | |---|------|-----------|-----| | 1 | Standard | ANSI/ASABE S623.1 JAN2017 (R2022) -- Determining Landscape Plant Water Demands (SLIDE) | https://webstore.ansi.org/standards/asabe/ansiasabes623jan2017r2022 | | 2 | Standard | QWEL Certification Program -- Irrigation Audit Form | https://www.qwel.net/files/QWEL_Irrigation_Audit.pdf | | 3 | Regulation | MWELO -- Model Water Efficient Landscape Ordinance (CA DWR, 2025 update) | https://water.ca.gov/-/media/DWR-Website/Web-Pages/Programs/Water-Use-And-Efficiency/MWELO-Rulemaking/Final-MWELO-Text-and-Appendices_20250103.pdf | | 4 | Specification | EPA WaterSense Specification for Homes, Version 2.0 (Feb 2021) | https://www.epa.gov/sites/default/files/2021-02/documents/watersense_final_homes_specification_v2.0.pdf | | 5 | Guidance | EPA WaterSense Water Budget Approach | https://www.epa.gov/sites/default/files/2017-01/documents/ws-homes-water-budget-approach.pdf | | 6 | Tool | EPA WaterSense Water Budget Tool v2.0 (Excel) | https://www.epa.gov/watersense/water-budget-tool | | 7 | Research | UC Davis CCUH -- Turfgrass Crop Coefficients (Kc) | https://ucanr.edu/sites/UrbanHort/Water_Use_of_Turfgrass_and_Landscape_Plant_Materials/Turfgrass_Crop_Coefficients_Kc/ | | 8 | Research | UC Davis CCUH -- Using ANSI/ASABE S623 & SLIDE to Estimate Landscape Water Requirements | https://ucanr.edu/site/center-landscape-urban-horticulture/using-ansi/asabe-s623-slide-estimate-landscape-water | | 9 | Technical Paper | IA -- Revisiting the Scheduling Coefficient (2009) | https://www.irrigation.org/IA/FileUploads/IA/Resources/TechnicalPapers/2009/RevisitingTheSchedulingCoefficient.pdf | | 10 | API Docs | CIMIS Web API REST Services | https://et.water.ca.gov/Rest/Index | | 11 | Data | USU Climate Center -- Evapotranspiration and Precipitation Data for Utah | https://extension.usu.edu/irrigation/research/evapotranspiration-and-precipitation-data | | 12 | API Docs | Open-Meteo Weather Forecast API | https://open-meteo.com/en/docs | | 13 | API Docs | Open-Meteo Historical Weather API | https://open-meteo.com/en/docs/historical-weather-api | | 14 | Blog | Open-Meteo -- Reference Evapotranspiration for Irrigation | https://openmeteo.substack.com/p/reference-evapotranspiration-for | | 15 | Data | gridMET -- Climatology Lab, University of Idaho | https://www.climatologylab.org/gridmet.html | | 16 | Standard | FAO-56 Penman-Monteith Reference Evapotranspiration (FAO Irrigation and Drainage Paper 56) | https://www.fao.org/4/x0490e/x0490e00.htm | | 17 | Guide | RCAC -- Estimating Landscape Irrigation Requirements | https://www.rcac.org/wp-content/uploads/2015/08/Estimating-Landscape-Irrigation-Requirements.pdf | | 18 | Guidance | UC Sonoma County Extension -- How to Calculate DU and Adjust Irrigation Requirements | https://ucanr.edu/county/ucce-sonoma-county/how-calculate-distribution-uniformity-and-adjust-irrigation-requirements | | 19 | Data | WUCOLS IV -- Water Use Classification of Landscape Species (UC Davis) | https://wucols.ucdavis.edu/ | | 20 | Guidance | Rain Bird -- Irrigation Scheduling: Use ET to Save Water | https://www.rainbird.com/professionals/irrigation-scheduling-use-et-save-water | | 21 | Guidance | Colorado State Extension GardenNotes #265 -- Methods to Schedule Home Lawn Irrigation | https://cmg.extension.colostate.edu/Gardennotes/265.pdf | | 22 | Guidance | Smart Irrigation -- Watering Times & Schedule Methodology | https://smartirrigation.com/sprinkler-watering-times-schedule/ | | 23 | Guidance | Weathermatic Support -- Soil Type and Slope (cycle-soak parameters) | https://support.weathermatic.com/hc/en-us/articles/360056448073 | | 24 | Data | NRCS/USDA -- Soil Infiltration Technical Reference | https://www.nrcs.usda.gov/sites/default/files/2022-10/Infiltration.pdf | | 25 | Guidance | Texas A&M AgriLife -- Preventing Runoff with Cycle and Soak Irrigation | https://www.dcmga.com/wp-content/uploads/docs/agrilife/water/al-preventing-runoff-cycle-soak-irrigation.pdf | | 26 | Data | FAO -- Effective Rainfall in Irrigated Agriculture (USDA SCS method) | https://www.fao.org/4/x5560e/x5560e03.htm | | 27 | Guidance | MWELO Guidebook -- Landscape, Irrigation, Water Budget Overview | https://water.ca.gov/-/media/DWR-Website/Web-Pages/Programs/Water-Use-And-Efficiency/Urban-Water-Use-Efficiency/MWELO-Files/MWELO-Guidebook/C--Landscape-Irrigation-Water-Budget-Overview.pdf | | 28 | Research | BSEACD -- Methodology for Estimating Landscape Irrigation Demand | https://bseacd.org/uploads/BSEACD_Irr_Demand_Meth_Rprt_2014_Final_140424.pdf | | 29 | Academic | UF/IFAS -- Evapotranspiration-Based Irrigation Scheduling for Agriculture (AE457) | https://edis.ifas.ufl.edu/publication/AE457 | | 30 | Guide | Lawn Sense Texas -- Soil Infiltration Rate Chart | https://lawnsensetexas.com/soil-infiltration-rate-chart/ | | 31 | User Data | QWEL Irrigation Audit Spreadsheet (DUlq=0.39, PF, ETo from USU) | https://docs.google.com/spreadsheets/d/1-1Qr35TjWsB1PtdTT4SFNt6eKB7tu-596PlT8QBpXV4/ | | 32 | Crossover | SS-RR-2026-001 -- Plant-Specific Drip Irrigation Intelligence (main report) | docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/plant-specific-drip-irrigation-intelligence/research/report-v2-2026-03-01.md | | 33 | Crossover | SS-TD-2026-001 -- Defensive Disclosure (Open-Meteo ETo reference) | docs/simplyscapes/legal/disclosures/submitted/SS-TD-2026-001-plant-specific-drip-irrigation-intelligence.md |

Species-Specific Irrigation Season Determination and Plant Factors for Turfgrass

Supporting Paper for: SS-RP-2026-002 Automated Turf Irrigation Scheduling ClickUp: Automated Turf Irrigation Scheduling Date: 2026-03-01 | Status: draft

Executive Summary

The EPA WaterSense Water Budget Tool uses a universal Growing Degree Day (GDD) base temperature of 50 deg F and treats the irrigation season as any month where 50% or more of days have positive growing degree days. This approach applies identical logic to all plant types. In practice, cool-season turfgrasses (Kentucky bluegrass, tall fescue) actively grow with soil temperatures as low as 40 deg F and continue root growth down to 33 deg F, while warm-season turfgrasses (bermudagrass, zoysiagrass) enter dormancy when soil temperatures drop below 55 deg F and do not resume significant growth until soil temperatures reach 60-65 deg F. The universal 50 deg F threshold therefore over-irrigates warm-season turf in shoulder months and under-irrigates cool-season turf during active cool-weather growth periods.

Similarly, the commonly used plant factor (PF) values of 0.80 for cool-season and 0.60 for warm-season turf -- while adequate as category averages -- mask meaningful species-level differences. Buffalograss needs roughly 50% of the water that Kentucky bluegrass requires; creeping bentgrass demands more water than any other cool-season species; bahiagrass has measurably higher crop coefficients than bermudagrass during spring green-up.

This paper compiles species-level plant factors, dormancy thresholds, growing season patterns, and base temperature data from peer-reviewed research and university extension services to support species-specific irrigation scheduling in the SimplyScapes platform.

---

1. Turf Species Plant Factors

1.1 Background: What Is a Plant Factor?

A plant factor (PF), also called a crop coefficient (Kc) or species coefficient, adjusts reference evapotranspiration (ETo) to estimate actual crop water demand:

ETc = ETo x PF

The ANSI/ASABE S623.1 standard (SLIDE methodology) and WUCOLS IV both define PF values for landscape plants. For turfgrass, WUCOLS notes that warm-season and cool-season grasses were not reviewed by the WUCOLS IV regional committees; their PF values derive from external turfgrass research (Pittenger et al.).

The UC ANR Center for Landscape and Urban Horticulture publishes monthly Kc values that refine the annual averages, showing how water demand shifts across the growing season.

1.2 Category-Level Plant Factors (WUCOLS / SLIDE / WaterSense)

| Source | Cool-Season PF | Warm-Season PF | |--------|---------------|----------------| | WUCOLS IV (UC Davis) | 0.80 | 0.60 | | ANSI/ASABE S623.1 (SLIDE) | 0.80 | 0.60 | | EPA WaterSense Water Budget | 0.80 | 0.60 |

These values represent the minimum water needed to maintain acceptable lawn quality -- not optimal quality. At 0.60 ETo, bermudagrass provides acceptable appearance. Cool-season grasses receiving only 0.60 ETo will show considerable thinning and browning.

1.3 Monthly Kc Values (UC ANR)

The UC ANR Center for Landscape and Urban Horticulture publishes monthly Kc that reveal seasonal demand variation:

Cool-Season Turfgrass Monthly Kc:

| Month | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | |-------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| | Kc | 0.60| 0.65| 0.85| 1.04| 1.00| 0.95| 0.85| 0.80| 0.85| 0.85| 0.75| 0.60|

Warm-Season Turfgrass Monthly Kc:

| Month | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | |-------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| | Kc | 0.55| 0.54| 0.60| 0.70| 0.79| 0.75| 0.70| 0.68| 0.70| 0.54| 0.55| 0.55|

Annual average for cool-season: 0.80. Annual average for warm-season: 0.60. Source: UC ANR Center for Landscape and Urban Horticulture.

Key insight: During peak growth (April-May), cool-season Kc reaches 1.00-1.04 (i.e., water demand exceeds reference ETo), while warm-season peaks at 0.79. During winter months, cool-season Kc drops to 0.60 but remains above zero, whereas warm-season drops to 0.54-0.55 because dormant turf still loses some moisture through the soil surface.

1.4 Species-Level Plant Factor / Kc Table

The following table synthesizes data from multiple research sources. Note that most published research reports Kc at the category level (cool-season vs. warm-season) rather than at the individual species level. Where species-specific data exists, it is noted.

Cool-Season Species

| Species | Annual Avg Kc/PF | Kc Range (Monthly) | Relative ET Rate | Key Source | |---------|-----------------|---------------------|-----------------|------------| | Kentucky bluegrass (Poa pratensis) | 0.80 | 0.60 - 1.05 | High (8.5-10 mm/day peak) | Huang 2006 (USGA); UC ANR | | Tall fescue (Festuca arundinacea) | 0.80 | 0.55 - 1.05 | Moderate-High (6-8 mm/day peak) | Blankenship et al. 2020; UC ANR | | Perennial ryegrass (Lolium perenne) | 0.80 | 0.60 - 1.05 | High | UC ANR | | Fine fescue (Festuca spp.) | 0.60 - 0.80 | 0.40 - 0.90 | Low-Moderate | Braun et al. 2022 | | Creeping bentgrass (Agrostis stolonifera) | 0.80 - 0.85 | 0.60 - 1.10 | High (golf-course mow: higher) | Virginia Tech; UC ANR |

Notes on cool-season species:

• Fine fescue is the outlier in this group. Research at Oregon State University showed fine fescues required only 58-96% ET replacement for high quality, compared to 26-43% for tall fescue (at acceptable quality). Fine fescue uses significantly less water than KBG at equivalent quality levels. A PF of 0.60 is defensible for fine fescue lawns.
• Creeping bentgrass at golf-course mowing heights (0.125-0.5 in) has higher water requirements. The Kc of 0.85 for fairway bentgrass vs 0.80 for home lawn is documented in Oregon State irrigation rate research. At putting green heights, daily water demand can reach 0.3 inches in peak summer.
• Tall fescue is the most drought-tolerant of the high-quality cool-season species due to its deep root system (2-3 ft vs 6-12 in for KBG). K-State studies showed tall fescue required less supplemental irrigation than KBG to maintain acceptable quality.

Warm-Season Species

| Species | Annual Avg Kc/PF | Kc Range (Monthly) | Relative ET Rate | Key Source | |---------|-----------------|---------------------|-----------------|------------| | Common bermudagrass (Cynodon dactylon) | 0.60 | 0.30 - 0.80 | Low-Moderate | Kruse et al. 2015; UC ANR | | Hybrid bermudagrass (C. dactylon x C. transvaalensis) | 0.60 | 0.30 - 0.80 | Low-Moderate | Kruse et al. 2015 | | Zoysiagrass (Zoysia japonica / Z. matrella) | 0.60 | 0.30 - 0.80 | Low | Kruse et al. 2015 | | St. Augustinegrass (Stenotaphrum secundatum) | 0.60 - 0.70 | 0.30 - 0.80 | Moderate-High | Kruse et al. 2015; Huang 2006 | | Buffalograss (Bouteloua dactyloides) | 0.30 - 0.50 | 0.20 - 0.60 | Very Low (<6 mm/day) | Colorado State Ext.; Huang 2006 | | Centipedegrass (Eremochloa ophiuroides) | 0.50 - 0.60 | 0.25 - 0.70 | Low | UF/IFAS; Clemson Ext. | | Bahiagrass (Paspalum notatum) | 0.60 - 0.70 | 0.35 - 0.90 | Moderate | Jia et al. 2009; Kruse et al. 2015 |

Notes on warm-season species:

• Kruse et al. (2015) measured Kc for Tifway bermudagrass, Empire zoysiagrass, Floratam St. Augustinegrass, and Argentine bahiagrass using weighing lysimeters in Gainesville, FL. Key finding: Kc peaked at approx. 0.80 during active growth (high VPD, high solar radiation) and declined to approx. 0.30 in late fall/winter. On 24 of 30 measurement periods, zoysiagrass, bermudagrass, and St. Augustinegrass Kc did not differ from one another. Bahiagrass showed elevated Kc in years 2-3, particularly during early spring. This demonstrates that the universal 0.60 PF under-predicts water demand during active growth and over-predicts during dormancy.
• Buffalograss is the only turfgrass native to North America. Its water demand is substantially lower than other warm-season species (approx. 50% of bermudagrass). Colorado State Extension recommends 1-2 inches of water every 2-4 weeks during summer. A PF of 0.30-0.50 is appropriate, placing it in the WUCOLS "Low" category alongside many xeric shrubs.
• St. Augustinegrass has higher water use than bermudagrass and zoysiagrass, approaching the lower range of cool-season grasses in humid climates.

1.5 Relative Water Use Ranking

From lowest to highest ET rate (synthesized from Huang 2006, Kruse et al. 2015, and UC ANR data):

Buffalograss < Bermudagrass = Zoysiagrass < Centipedegrass < Bahiagrass
< St. Augustinegrass < Tall Fescue < Fine Fescue < Perennial Ryegrass
= Kentucky Bluegrass < Creeping Bentgrass

Note: Fine fescue is paradoxical -- it has low water requirements but its ET rate in well-watered conditions can be moderate because of its dense canopy. The ranking above reflects supplemental irrigation need, not peak ET rate.

---

2. Dormancy Thresholds by Species

2.1 Soil Temperature vs. Air Temperature

Dormancy transitions are more accurately predicted by soil temperature than air temperature because:

1. Soil temperature at 2-4 inch depth buffers diurnal air temperature swings
2. Root-zone temperature directly controls root growth initiation/cessation
3. Air temperature can spike above growth thresholds during winter without triggering real growth if soil remains cold

For algorithmic scheduling, soil temperature at 4-inch depth is the preferred metric. Where soil temperature data is unavailable, 7-day rolling average air temperature serves as a practical proxy (soil temperature at 4 in. lags air temperature by approximately 3-7 days depending on moisture content and soil type).

2.2 Cool-Season Turfgrass Dormancy Thresholds

| Parameter | Temperature | Source | |-----------|------------|--------| | Shoot growth ceases | Air temp < 40 deg F (4 deg C) | Penn State Extension | | Root growth ceases | Soil temp < 33 deg F (1 deg C) | Penn State Extension | | Root growth slow/minimal | Soil temp 33-45 deg F (1-7 deg C) | Penn State Extension | | Root growth optimal | Soil temp 50-65 deg F (10-18 deg C) | Penn State Extension | | Root growth declines | Soil temp > 70 deg F (21 deg C) | Penn State Extension | | Root growth nearly stops | Soil temp > 90 deg F (32 deg C) | Penn State Extension | | Leaf growth optimal | Air temp 60-75 deg F (16-24 deg C) | Penn State Extension | | Summer dormancy begins | Air temp sustained > 85-90 deg F | Various | | Winter dormancy begins | After 2+ hard frosts | Texas A&M |

Key points:

• Cool-season grasses maintain some metabolic activity and water demand even when shoot growth has stopped, because root growth continues at much lower temperatures (down to 33 deg F).
• Summer dormancy is a separate phenomenon: during sustained heat above 85 deg F, cool-season grasses enter a protective summer dormancy. This is critical in the transition zone (USDA zones 6-7) where summer irrigation scheduling for cool-season turf must account for reduced growth efficiency.
• Kentucky bluegrass root growth peaks at soil temp of 60 deg F and declines sharply above 70 deg F; leaf growth pretty much ceases after two hard frosts.
• Perennial ryegrass goes dormant after 10+ consecutive days below 50 deg F air temperature, and enters summer dormancy when air temperatures reach 87 deg F.

2.3 Warm-Season Turfgrass Dormancy Thresholds

| Species | Dormancy Entry (Soil Temp) | Green-Up Begins (Soil Temp) | Active Growth (Soil Temp) | Cold Hardiness Limit | |---------|---------------------------|----------------------------|--------------------------|---------------------| | Bermudagrass (common) | < 55 deg F (13 deg C) | > 55 deg F, full at 65 deg F | > 65 deg F (18 deg C) | 10 deg F (-12 deg C) | | Bermudagrass (hybrid) | < 55 deg F (13 deg C) | > 60-65 deg F | > 65 deg F (18 deg C) | 20 deg F (-7 deg C) | | Zoysiagrass | < 55 deg F (13 deg C) | 55-60 deg F (several consecutive days) | > 60 deg F (16 deg C) | 0 deg F (-18 deg C) | | St. Augustinegrass | < 55 deg F (13 deg C) | > 60 deg F | > 65 deg F (18 deg C) | 20-25 deg F (-4 to -7 deg C) | | Buffalograss | < 55-60 deg F | > 55-60 deg F | > 65 deg F (18 deg C) | -10 deg F (-23 deg C) | | Centipedegrass | < 55 deg F (13 deg C) | > 60 deg F | > 65 deg F (18 deg C) | 10 deg F (-12 deg C) | | Bahiagrass | < 55 deg F (13 deg C) | > 60 deg F | > 65 deg F (18 deg C) | 15 deg F (-9 deg C) |

Sources: Texas A&M AgriLife Extension, University of Georgia Extension (Walter Reeves), Clemson Extension, University of Florida IFAS, Missouri Extension, Penn State Extension.

Key points:

• All warm-season species share approximately the same dormancy entry threshold (soil temp < 55 deg F), but green-up requirements vary. Bermudagrass needs nighttime air temperatures consistently above 60 deg F AND soil temperature at 65 deg F at 4-inch depth for significant spring growth. Zoysiagrass begins green-up at a slightly lower threshold (55-60 deg F) but greens up more slowly than bermudagrass.
• Centipedegrass lacks a true deep dormancy period and is therefore especially susceptible to winter injury from freeze-thaw cycles (Clemson Extension).
• Buffalograss has the widest temperature tolerance range of any warm-season species, surviving to -10 deg F and going dormant during both cold and extended drought.

2.4 Base Temperatures for GDD Models

| Species Category | Traditional Base Temp | Research-Recommended Base Temp | Source | |-----------------|----------------------|-------------------------------|--------| | Cool-season turf (general) | 32 deg F (0 deg C) | 32 deg F (0 deg C) | Michigan State; Syngenta GreenCast | | Warm-season turf (general) | 50 deg F (10 deg C) | 50 deg F (10 deg C) | Syngenta GreenCast | | Bermudagrass (emergence) | 41 deg F (5 deg C) | 59 deg F (15 deg C) | Agronomy Journal (2021) | | Bermudagrass (PGR timing) | 50 deg F (10 deg C) | 50 deg F (10 deg C) | Reasor et al. 2018 | | Zoysiagrass (seedhead) | 50 deg F (10 deg C) | 50 deg F (10 deg C) | McCullough et al. 2017 | | EPA WaterSense (universal) | 50 deg F (10 deg C) | N/A (see critique below) | EPA |

The base temperature for GDD models is defined as the temperature below which no meaningful growth occurs. For cool-season turfgrasses, a base of 32 deg F is appropriate because root growth continues down to 33 deg F. For warm-season turfgrasses, a base of 50 deg F is appropriate because growth ceases below that threshold. The EPA WaterSense tool applies the warm-season base (50 deg F) to all plants, which systematically excludes cool-season growing days in the 33-50 deg F range.

---

3. Growing Season Patterns: Cool-Season vs. Warm-Season

3.1 Cool-Season Growth Pattern

Cool-season grasses exhibit a bimodal growth pattern with two peaks per year:

       Relative Growth Rate
  High |       **                  **
       |      *  *                *  *
       |     *    *              *    *
  Med  |    *      *            *      *
       |   *        *          *        *
  Low  |  *          **      **          *
       | *             ******             *
  None |*                                  *
       +----+----+----+----+----+----+----+----+----+----+----+----+
        Jan  Feb  Mar  Apr  May  Jun  Jul  Aug  Sep  Oct  Nov  Dec

• Spring peak: March through June (shoot growth driven by 60-75 deg F air temp)
• Summer depression: July through August (growth slows or stops above 85 deg F)
• Fall peak: September through November (second growth surge as temps cool)
• Winter minimal: December through February (root growth only at 33-50 deg F)

Water demand follows growth rate but does not go to zero in winter because:

1. Root growth continues at soil temps above 33 deg F
2. Evaporative demand from the soil surface persists
3. The UC ANR monthly Kc of 0.60 in December/January reflects this residual demand

3.2 Warm-Season Growth Pattern

Warm-season grasses exhibit a single-peaked (unimodal) growth pattern:

       Relative Growth Rate
  High |                   ****
       |                  *    *
       |                 *      *
  Med  |                *        *
       |               *          *
  Low  |              *            *
       |             *              *
  None |*************                **************
       +----+----+----+----+----+----+----+----+----+----+----+----+
        Jan  Feb  Mar  Apr  May  Jun  Jul  Aug  Sep  Oct  Nov  Dec

• Dormancy: November through March (varies by species and latitude)
• Green-up: March through April (when soil temp at 4 in. reaches 55-65 deg F)
• Peak growth: June through August (optimum air temp 80-95 deg F)
• Dormancy onset: October through November (after first sustained cold period)

During dormancy, warm-season turf is brown and requires no irrigation in most climates. The Kc values of 0.30-0.55 reported for dormant months largely represent soil surface evaporation, not plant transpiration.

3.3 Seasonal Water Demand Comparison

Approximate monthly ETc as fraction of peak-month ETc, normalized to 1.0:

| Month | Cool-Season | Warm-Season | |-------|-------------|-------------| | Jan | 0.15 | 0.00 (dormant) | | Feb | 0.20 | 0.00 (dormant) | | Mar | 0.55 | 0.10 (green-up beginning) | | Apr | 0.85 | 0.40 | | May | 1.00 | 0.80 | | Jun | 0.80 | 1.00 | | Jul | 0.60 (summer stress) | 1.00 | | Aug | 0.55 (summer stress) | 0.95 | | Sep | 0.75 | 0.70 | | Oct | 0.65 | 0.30 | | Nov | 0.35 | 0.05 (dormancy onset) | | Dec | 0.15 | 0.00 (dormant) |

These values are illustrative for a mid-latitude location (approx. 37 deg N, transition zone). The actual shape shifts significantly with latitude, altitude, and local climate.

---

4. Critique of EPA WaterSense 50 deg F Universal Threshold

4.1 How the WaterSense Growing Season Works

The EPA WaterSense Water Budget Tool determines the irrigation season using Growing Degree Reference Days (GRDD) with a base temperature of 50 deg F (10 deg C). A month is included in the irrigation season if 50% or more of its days have a positive GRDD value (i.e., average daily temperature exceeds 50 deg F). This approach is applied identically regardless of plant type.

4.2 Where It Fails for Cool-Season Turf

Problem 1: Excludes active cool-season growth periods.

Cool-season turfgrass root growth continues at soil temperatures as low as 33 deg F and shoot growth at air temperatures as low as 40 deg F (Penn State Extension). In many locations, March and November have average temperatures near or below 50 deg F but support active cool-season turf growth and meaningful water demand. The UC ANR monthly Kc for cool-season turf in these months is 0.75-0.85 -- far above zero.

Example: Denver, CO (USDA Zone 5b)

• Average March temperature: 43 deg F
• GRDD at base 50 deg F: Most March days are negative
• WaterSense: March is likely excluded from irrigation season
• Reality: Cool-season turf is actively growing (roots at soil temp 40-50 deg F); Kc = 0.85; supplemental irrigation may be needed if March is dry

Example: Philadelphia, PA (USDA Zone 7a)

• Average November temperature: 46 deg F
• GRDD at base 50 deg F: Majority of November days are negative
• WaterSense: November is excluded from irrigation season
• Reality: Cool-season turf still has active root growth and moderate water demand; fall is a critical growth/recovery period

Problem 2: Treats cool-season and warm-season identically.

By using the same 50 deg F base for all plants, the tool does not distinguish between Kentucky bluegrass (which is actively growing at 45 deg F air temp) and bermudagrass (which is fully dormant at 50 deg F soil temp). A landscape with cool-season turf in Denver gets the same growing season calculation as one with bermudagrass in Atlanta.

4.3 Where It Fails for Warm-Season Turf

Problem 3: Includes months where warm-season turf is dormant.

Bermudagrass does not begin meaningful green-up until soil temperature reaches 55-65 deg F at 4-inch depth (Texas A&M AgriLife Extension). In the transition zone, air temperatures may average above 50 deg F in late March/early April while soil temperature at depth remains below 55 deg F. The WaterSense tool would include this month in the irrigation season and allocate water to dormant bermudagrass.

Example: Nashville, TN (USDA Zone 7a)

• Average March temperature: 52 deg F (so GRDD > 0 on most days)
• WaterSense: March is in the irrigation season
• Reality: Bermudagrass soil temperature at 4 in. is 45-50 deg F; turf is still dormant and brown; irrigation is wasted

Problem 4: Does not account for the dormancy-to-growth transition lag.

Even when air temperature exceeds 50 deg F, warm-season turf requires several consecutive days of soil temperature above 55 deg F (and nighttime air temps above 60 deg F for bermudagrass) before initiating green-up. A single warm week in early spring does not trigger growth. The binary GRDD threshold cannot model this hysteresis.

4.4 Summary of Deficiencies

| Deficiency | Impact | Magnitude | |------------|--------|-----------| | Single base temp for all species | Wrong season start/end for both cool and warm | 1-3 months per year | | No species-specific dormancy thresholds | Water allocated to dormant turf | 10-30% annual waste in shoulder months | | No soil temperature consideration | Air temp proxies miss thermal lag | 2-4 weeks of incorrect scheduling | | Binary threshold (50% of days) | No transition modeling | Abrupt on/off vs. gradual ramp | | No summer dormancy for cool-season | Over-irrigates heat-stressed KBG | 10-20% summer waste in transition zone |

---

5. Proposed Algorithm for Species-Specific Growing Season

5.1 Design Goals

1. Determine irrigation season start/end per turf species, not per location
2. Use temperature data that is readily available (weather station or gridded)
3. Model gradual transition (ramp-up/ramp-down) rather than binary on/off
4. Support mixed-species landscapes (cool + warm zones in same project)
5. Degrade gracefully when only zip-code-level data is available

5.2 Recommended Approach: Species-Specific Temperature Threshold with Ramp

Rather than GDD accumulation (which is sensitive to base temperature selection and averaging method), we recommend a rolling-average soil temperature threshold approach with a linear ramp:

Step 1: Assign Species Parameters

For each turf species in the design, look up:

• base_temp: Temperature below which irrigation demand is zero
• active_temp: Temperature above which full PF applies
• pf_active: Plant factor during active growth
• pf_dormant: Plant factor during dormancy (0.0 for warm-season, 0.10-0.15 for cool-season)

Step 2: Compute Monthly Soil Temperature Proxy

Use 30-year normal monthly average air temperature from the nearest weather station (available via PRISM, Open-Meteo Climate API, or NOAA normals). Apply a soil temperature offset:

T_soil_proxy = T_air_monthly_avg - offset

Where offset is typically 2-5 deg F (soil at 4 in. depth lags and buffers air temperature). In practice, using air temperature directly (offset = 0) is conservative and acceptable for a water budget tool.

Step 3: Compute Monthly PF with Ramp

def monthly_pf(T_soil, base_temp, active_temp, pf_active, pf_dormant):
    if T_soil <= base_temp:
        return pf_dormant
    elif T_soil >= active_temp:
        return pf_active
    else:
        # Linear ramp between dormancy and active growth
        fraction = (T_soil - base_temp) / (active_temp - base_temp)
        return pf_dormant + fraction * (pf_active - pf_dormant)

This produces a smooth transition rather than a binary on/off, reflecting the biological reality that growth (and water demand) increases gradually as temperatures rise.

Step 4: Compute Monthly ETc

ETc_month = ETo_month x monthly_pf(T_soil_month, ...)

Where ETo_month comes from the same climate data source (PRISM, gridMET, Open-Meteo, CIMIS, or WaterSense Data Finder).

5.3 Species Parameter Table for Algorithm

| Species | Base Temp (deg F) | Active Temp (deg F) | PF Active | PF Dormant | GDD Base (deg F) | |---------|------------------|--------------------:|----------:|-----------:|------------------:| | Kentucky bluegrass | 33 | 55 | 0.80 | 0.10 | 32 | | Tall fescue | 33 | 55 | 0.80 | 0.10 | 32 | | Perennial ryegrass | 33 | 55 | 0.80 | 0.10 | 32 | | Fine fescue | 33 | 50 | 0.60 | 0.10 | 32 | | Creeping bentgrass | 33 | 55 | 0.85 | 0.10 | 32 | | Bermudagrass (common) | 55 | 70 | 0.60 | 0.00 | 50 | | Bermudagrass (hybrid) | 55 | 70 | 0.60 | 0.00 | 50 | | Zoysiagrass | 55 | 65 | 0.60 | 0.00 | 50 | | St. Augustinegrass | 55 | 70 | 0.65 | 0.00 | 50 | | Buffalograss | 55 | 70 | 0.40 | 0.00 | 50 | | Centipedegrass | 55 | 70 | 0.55 | 0.00 | 50 | | Bahiagrass | 55 | 70 | 0.65 | 0.00 | 50 |

Rationale for key values:

• Cool-season base temp of 33 deg F: Root growth continues to 33 deg F (Penn State); some water demand persists even in near-freezing soil
• Cool-season active temp of 55 deg F: Full growth rate achieved when soil temp reaches optimal root growth range (50-65 deg F)
• Warm-season base temp of 55 deg F: All warm-season species go dormant below this soil temperature
• Warm-season active temp of 65-70 deg F: Significant growth and full water demand requires soil temperatures in this range; bermudagrass specifically needs soil temp of 65 deg F at 4 in. depth for rhizome/stolon growth

5.4 Comparison with Alternative Approaches

| Approach | Pros | Cons | |----------|------|------| | GDD accumulation (EPA WaterSense) | Simple; well-understood | Wrong base temp for cool-season; binary season; no species differentiation | | Calendar-based (fixed dates) | Simplest to implement | Ignores climate variation; wrong for unusual years | | Soil temperature threshold (proposed) | Species-specific; models transitions; uses available data | Requires monthly temperature normals; proxy needed where soil temp data is unavailable | | Real-time soil sensor | Most accurate | Requires hardware; not available at design time |

The proposed approach occupies the optimal position: it is more accurate than GDD or calendar methods, uses readily available climate data, and can be implemented at design time without requiring sensors. When real-time soil temperature data is available (via smart controller integration), the algorithm can switch from proxy to actual values.

5.5 Cool-Season Summer Stress Adjustment

An additional refinement for cool-season turf in the transition zone:

def summer_stress_factor(T_air_max, species):
    if species.type != 'cool_season':
        return 1.0
    if T_air_max < 85:
        return 1.0
    elif T_air_max > 95:
        return 0.50  # Summer dormancy; reduced water uptake efficiency
    else:
        return 1.0 - 0.05 * (T_air_max - 85)  # Linear reduction

During sustained heat above 85 deg F, cool-season turf growth slows and water use efficiency drops. However, irrigation should not be eliminated entirely because some irrigation prevents crown death. The summer stress factor reduces the effective PF but maintains a floor of 0.50 PF to keep turf alive.

---

6. Plant Database Schema Additions

6.1 Current SimplyScapes Plant Table Schema

The existing plant table includes: water, zone_min, zone_max, sun, soil, height, width, growth_rate.

6.2 Required Additions for Species-Specific Scheduling

The following columns should be added to support the algorithm described in Section 5:

| Column Name | Data Type | Unit | Description | Example (KBG) | Example (Bermuda) | |-------------|-----------|------|-------------|---------------|-------------------| | plant_factor | DECIMAL(3,2) | dimensionless | WUCOLS/SLIDE plant factor for active growth | 0.80 | 0.60 | | plant_factor_dormant | DECIMAL(3,2) | dimensionless | Plant factor during dormancy | 0.10 | 0.00 | | season_type | ENUM | -- | 'cool_season', 'warm_season', 'evergreen', 'deciduous' | cool_season | warm_season | | base_temp_f | SMALLINT | deg F | Soil temp below which growth ceases (irrigation demand = dormant PF) | 33 | 55 | | active_temp_f | SMALLINT | deg F | Soil temp above which full PF applies | 55 | 70 | | optimal_temp_low_f | SMALLINT | deg F | Low end of optimal air temp range for shoot growth | 60 | 80 | | optimal_temp_high_f | SMALLINT | deg F | High end of optimal air temp range for shoot growth | 75 | 95 | | summer_stress_temp_f | SMALLINT | deg F | Air temp above which summer stress begins (cool-season only) | 85 | NULL | | cold_hardiness_f | SMALLINT | deg F | Minimum survival temperature | -30 | 10 | | gdd_base_f | SMALLINT | deg F | Base temperature for GDD calculations | 32 | 50 | | establishment_weeks | SMALLINT | weeks | Weeks of elevated irrigation after planting | 6 | 4 | | establishment_pf | DECIMAL(3,2) | dimensionless | Plant factor during establishment period | 1.00 | 0.80 | | root_depth_in | SMALLINT | inches | Typical mature root depth for MAD calculations | 8 | 12 |

6.3 Data Population Priority

For the initial implementation, only three columns are essential:

1. plant_factor -- enables species-specific ETc calculation
2. base_temp_f -- enables species-specific season start/end
3. active_temp_f -- enables the ramp function

The remaining columns enhance accuracy and enable advanced features (establishment scheduling, management allowable depletion, summer stress adjustments).

6.4 Seeding the Data

The species parameter table in Section 5.3 provides values for all 12 major turfgrass species. For non-turf landscape plants, WUCOLS IV provides plant factor data for over 3,500 species across six California climate regions. The base_temp_f and active_temp_f for non-turf species can initially default to the EPA WaterSense values (50 deg F base) and be refined over time.

---

7. Transition Zone Complications (USDA Zones 6-7)

7.1 The Transition Zone Problem

The turfgrass transition zone spans roughly USDA Hardiness Zones 6 through 7 (approximately 35-40 deg N latitude), including major metro areas like Washington DC, Nashville, St. Louis, Kansas City, Denver, and Raleigh. In this zone, summers are too hot for cool-season grasses to thrive year-round, and winters are too cold for warm-season grasses to stay green year-round.

7.2 Common Scenarios

Scenario A: Cool-season turf in the transition zone (e.g., tall fescue in Nashville)

• Active growth: March-June, September-November (bimodal)
• Summer stress: July-August (Kc drops to 0.50-0.60 due to heat stress)
• Irrigation needed most critically in summer to prevent crown death, even though growth efficiency is low
• Risk: Over-irrigating in summer promotes disease; under-irrigating kills turf

Scenario B: Warm-season turf in the transition zone (e.g., bermudagrass in Kansas City)

• Active growth: May-September (5-month window)
• Dormancy: November-March (5 months of brown turf)
• Green-up delayed vs. southern locations (mid-April to May vs. March)
• Risk: Winter kill in severe winters; shortened growing season reduces recovery capacity

Scenario C: Mixed warm/cool landscape (e.g., bermudagrass lawn with tall fescue shade areas)

• Two different irrigation schedules required on the same property
• Warm-season zones: no irrigation November-March
• Cool-season zones: reduced but non-zero irrigation November-March
• Spring scheduling: cool-season zones ramp up in March while warm-season zones remain dormant until May

7.3 Algorithm Implications

The proposed species-specific algorithm (Section 5) handles transition zone complexity naturally because:

1. Each zone in the irrigation design is tagged with its turf species
2. The species parameters determine the zone-specific growing season
3. Different zones on the same property can have different irrigation start/end dates and PF values
4. The ramp function handles the gradual transitions that characterize transition zone seasons

However, the following refinements are needed for transition zone accuracy:

Overseeding consideration: In the transition zone, bermudagrass lawns are often overseeded with perennial ryegrass in fall for winter color. During the overseeded period (October-April), the lawn behaves as cool-season turf (PF 0.80, base temp 33 deg F) even though the permanent turf is warm-season. The scheduling algorithm should support an "overseeded" flag that switches PF and temperature parameters during the overseeded period.

Microclimate variation: Within a single property in the transition zone, south-facing slopes may be warm enough for bermudagrass to thrive while north-facing areas need cool-season turf. The SimplyScapes design already captures sun exposure per zone, which could be used to apply microclimate adjustments (e.g., +5 deg F for full south exposure, -5 deg F for full north exposure).

7.4 Decision Framework for Transition Zone Species Selection

For the SimplyScapes plant recommendation engine:

| Factor | Favors Cool-Season | Favors Warm-Season | |--------|-------------------|-------------------| | USDA zone | 6a-6b | 7a-7b | | Shade present | Yes | No (bermuda needs full sun) | | Year-round green desired | Yes | No (accepts winter brown) | | Water conservation priority | No (KBG needs more water) | Yes (bermuda uses 25% less) | | Summer durability priority | No (heat stress risk) | Yes (thrives in heat) | | Traffic tolerance | Moderate (KBG); Good (tall fescue) | Excellent (bermuda) |

---

8. Sources

Peer-Reviewed Research

| Citation | Key Data Used | |----------|--------------| | Kruse, J.K., M.C. Dukes, et al. (2015). Consumptive water use and crop coefficients for warm-season turfgrass species in the Southeastern United States. Agricultural Water Management, 156:10-18. | Warm-season Kc values by species (bermuda, zoysia, St. Aug, bahia); seasonal Kc fluctuation 0.30-0.80 | | Romero, C.C. and M.D. Dukes. (2016). Review of Turfgrass Evapotranspiration and Crop Coefficients. Applied Engineering in Agriculture, 32(1). | Comprehensive Kc range: cool 0.05-1.05, warm 0.28-0.99; ET rates by species | | Jia, X., et al. (2009). Bahiagrass crop coefficients from eddy correlation measurements in central Florida. Irrigation Science, 28:5-15. | Bahiagrass Kc 0.35-0.90; seasonal variation in FL | | Huang, B. (2006). Turfgrass Water Requirements and Factors Affecting Water Usage. Chapter 11 in Water Quality and Quantity Issues for Turfgrasses in Urban Landscapes. USGA. | Relative ET rankings for 24 species; water use rates 3-8 mm/day cool, 2-5 mm/day warm | | Braun, R.C., et al. (2022). Review of cool-season turfgrass water use and requirements: II. Responses to drought stress. Crop Science, 62:2215-2234. | Fine fescue drought tolerance; cool-season ET replacement percentages | | Blankenship, T.M., et al. (2020). Water requirements influenced by turfgrass species and mowing height in western Oregon. Crop, Forage & Turfgrass Management, 6(1). | Tall fescue Kc 0.55-0.70; species-specific Kc at different mowing heights | | McCullough, P.E., et al. (2017). Seedhead Development of Three Warm-Season Turfgrasses as Influenced by Growing Degree Days, Photoperiod, and Maintenance Regimens. Intl. Turfgrass Soc. Research J., 13. | GDD base 10 deg C for zoysiagrass; seedhead emergence at 167-196 GDD | | Reasor, E.H., et al. (2018). Growing Degree Day Models for Plant Growth Regulator Applications on Ultradwarf Hybrid Bermudagrass Putting Greens. Crop Science, 58:1-11. | Bermuda GDD models; base temp 10 deg C for PGR timing | | Agronomy Journal (2021). Base temperatures affect accuracy of growing degree day model to predict emergence of bermudagrasses. | TBASE 5 deg C vs 15 deg C comparison; 15 deg C recommended for emergence prediction |

University Extension Services

| Source | Key Data Used | |--------|--------------| | Penn State Extension. The Cool-Season Turfgrasses: Basic Structures, Growth and Development. | Root growth 33-65 deg F; shoot growth 60-75 deg F; growth cessation temps | | Texas A&M AgriLife Extension. Spring Transition in Bermudagrass; Bermudagrass Home Lawn Management Calendar. | Bermuda green-up: soil 65 deg F at 4 in., nighttime air > 60 deg F | | Clemson Extension (HGIC). Centipedegrass Yearly Maintenance Program; St. Augustinegrass Maintenance Calendar. | Centipedegrass winter injury susceptibility; warm-season maintenance timing | | University of Florida IFAS. St. Augustinegrass for Florida Lawns (ENH5/LH010). | St. Aug cold tolerance; dormancy characteristics | | Missouri Extension. Establishment and Care of Buffalograss Lawns (G6730). | Buffalograss dormancy thresholds; water requirements | | Colorado State Extension. Buffalograss Lawns (GardenNotes #565). | Buffalograss PF 0.30-0.50; low water requirements | | Oregon State Extension. Irrigation rates and frequencies for Western and Eastern Oregon turfgrass (EM-9311). | Cool-season Kc by species and mowing height | | K-State Research and Extension. Water needs of tall fescue, Kentucky bluegrass (2020). | Comparative irrigation requirements KBG vs tall fescue | | NC State Extension (TurfFiles). Creeping Bentgrass. | Bentgrass water requirements and management | | Purdue University Turfgrass Science. Use Growing Degree Days to Better Time Your Applications. | GDD calculation methods; base temp selection |

Standards and Tools

| Source | Key Data Used | |--------|--------------| | ANSI/ASABE S623.1 JAN2017 (R2022). Determining Landscape Plant Water Demands. | PF 0.80 cool-season, 0.60 warm-season; SLIDE methodology | | WUCOLS IV (UC Davis, 2014). Water Use Classification of Landscape Species. | Plant factor framework; turfgrass PF values | | UC ANR Center for Landscape & Urban Horticulture. Turfgrass Crop Coefficients (Kc). | Monthly Kc tables: cool 0.60-1.04, warm 0.54-0.79 | | EPA WaterSense. Water Budget Approach (2017); Water Budget Tool v1.04 (2020). | GRDD methodology; universal 50 deg F base; growing season determination | | Syngenta GreenCast. About Growing Degree Days. | GDD base temp: 0 deg C cool-season, 10 deg C warm-season | | NTEP (National Turfgrass Evaluation Program). National Cool-Season Water Use-Drought Tolerance Test. | Cultivar-level drought tolerance data; 50% ETo threshold for some entries |

---

Appendix A: Quick Reference -- SimplyScapes Implementation Priorities

Minimum Viable Implementation (Phase 1)

1. Add plant_factor, base_temp_f, active_temp_f columns to plant table
2. Populate for the 12 turf species in Section 5.3
3. Implement the monthly PF ramp function (Section 5.2, Step 3)
4. Source monthly ETo and temperature normals from Open-Meteo Climate API
5. Replace EPA WaterSense binary growing season with species-specific ramp

Enhanced Implementation (Phase 2)

6. Add season_type, summer_stress_temp_f, establishment_weeks, establishment_pf, root_depth_in columns
7. Implement summer stress factor for cool-season turf (Section 5.5)
8. Support overseeding flag for transition zone bermudagrass
9. Use soil temperature data from smart controller integration where available

Advanced Implementation (Phase 3)

10. Monthly Kc curves per species (not just ramp) using the UC ANR data
11. Microclimate adjustments based on zone sun exposure and slope
12. NTEP cultivar-level Kc refinements (e.g., 'Midnight' KBG vs. 'Park' KBG)
13. Real-time soil temperature from connected sensors replacing proxy values

Design-Computed Distribution Uniformity (DU) as a Novel Mechanism for Irrigation Scheduling

Parent: SS-RR-2026-002 ClickUp: Automated Turf Irrigation Scheduling Type: Supporting Research Paper Date: 2026-03-01 Status: draft

Abstract

This paper investigates whether Distribution Uniformity (DU) computed from irrigation design geometry can replace field-measured DU (from catch can tests) as an input to standard irrigation scheduling formulas such as the QWEL formula chain. We examine traditional field measurement methodology, simulation approaches for computing DU from design parameters, the accuracy gap between design-computed and field-measured DU, and -- critically -- whether any prior art exists for using design-derived DU directly in schedule generation. Our finding is that no prior art exists for this specific integration: while DU simulation from design geometry is well-established in academia, and DU-based scheduling formulas are well-established in practice, no existing system connects the two by feeding design-computed DU into scheduling formulas to produce zone-by-zone irrigation runtimes without a physical field audit. This represents a genuine novel mechanism.

---

1. Field-Measured DU: Methodology and Limitations

1.1 The Catch Can Test

The catch can test is the industry-standard method for measuring Distribution Uniformity in the field. The procedure is codified in several standards and guidelines:

• ASABE S436.1 (Test Procedure for Determining the Uniformity of Water Distribution): Specifies collector spacing of 9.8 ft (3 m) for spray devices and 16.4 ft (5 m) for impact sprinklers, with a minimum irrigation depth of 0.6 inches during testing.
• ASABE/ICC 802 (Landscape Irrigation Sprinkler and Emitter Standard): Establishes minimum design and performance requirements and uniform test methods for sprinkler products.
• ASABE S398.1 (Procedure for Sprinkler Testing and Performance Reporting): Defines the single-head radial distribution profile test that underpins all overlap simulations.
• Irrigation Association Audit Guidelines: Recommend a minimum of 24 catch cans per zone, placed in a grid pattern at 5-8 ft spacing for spray heads or 10-20 ft spacing for rotors.
• QWEL Irrigation Audit Protocol: Requires wind speed at or below 5 mph, spray head runtime of 5-10 minutes, and rotor runtime of 10-20 minutes (at least five full rotations for large rotors).

Procedure summary:

1. Place a minimum of 24 catch cans in a uniform grid across the irrigation zone.
2. Run the zone for a measured duration (5-20 minutes depending on head type).
3. Measure the volume or depth of water in each can.
4. Sort measurements from lowest to highest.
5. Calculate DU_LQ (Distribution Uniformity of the Lower Quarter).

1.2 DU_LQ Calculation

The standard DU calculation used in landscape irrigation is the Lower Quarter formulation:

DU_LQ = (Average of lowest 25% of measurements) / (Average of all measurements) x 100%

For a 24-can test, this means averaging the 6 lowest catches and dividing by the overall average. This is the formulation specified by the Irrigation Association and used in QWEL, MWELO, and EPA WaterSense methodologies.

1.3 Alternative Uniformity Measures

Several alternative uniformity coefficients exist, each with different applications:

Christiansen Uniformity Coefficient (CU): Developed in 1942, this is the oldest and most widely cited measure:

CU = 100% x (1 - (Sum of |d_i - d_mean|) / (n x d_mean))

Where d_i is each individual measurement and d_mean is the overall average. CU weights all deviations equally, whereas DU_LQ focuses on the driest quarter. CU values are typically 5-10 percentage points higher than DU_LQ for the same system. A CU of 84% is generally considered the minimum acceptable value.

Heermann-Hein Uniformity Coefficient (CU_H): A modified version that weights each measurement by its distance from the center, designed for center pivot systems where outer sprinklers cover more area. Calculated as:

CU_H = 100 x (1 - Sum(S_i x |V_i - V_p|) / Sum(V_i x S_i))

Where S_i is the distance of the i-th collector from the pivot point and V_p is the area-weighted average volume.

Scheduling Coefficient (SC): Developed specifically for turfgrass irrigation by Mecham and von Bernuth. Unlike DU_LQ (which uses the lowest 25% of point samples), SC uses a contiguous area (typically the driest 1%, 5%, or 10% of the irrigated area). SC is always higher than DU_LQ because contiguous dry areas average out point-to-point variation. SC indicates how much additional water the driest contiguous area needs relative to the average.

1.4 Typical Field-Measured DU Values

Field measurements consistently show that installed landscape irrigation systems perform well below their design potential:

| System Type | Typical Field DU_LQ | Well-Maintained DU_LQ | Design Target DU_LQ | |-------------|--------------------|-----------------------|---------------------| | Fixed spray heads | 0.41 - 0.55 | 0.55 - 0.65 | 0.65 - 0.75 | | Rotary nozzles (e.g., MP Rotator, R-VAN) | 0.55 - 0.70 | 0.70 - 0.85 | 0.75 - 0.85 | | Gear-driven rotors | 0.49 - 0.60 | 0.60 - 0.75 | 0.70 - 0.80 | | Drip irrigation | 0.70 - 0.90 | 0.85 - 0.95 | 0.85 - 0.95 |

Key findings from published studies:

• Baum et al. (2005) found the average DU_LQ for residential irrigation systems in Central Florida was only 0.45, with rotary sprinklers at 0.49 and fixed spray heads at 0.41.
• The standard Mobile Irrigation Laboratory (MIL) procedure may overestimate uniformity for residential systems because it uses fewer catch cans and may not capture the full spatial variability.
• Multiple agencies (e.g., Tucson Unified School District) require a minimum DU of 65% measured in the field on new installations.
• The Irrigation Association considers 80%+ as above average, 60-80% as needing improvement, and below 60% as poor.

1.5 Cost and Practical Limitations of Catch Can Tests

The catch can test is the most expensive and time-consuming step in a professional irrigation audit:

• Time per zone: 30-60 minutes including setup, runtime, measurement, and cleanup. A typical residential property with 6-8 zones requires a full day.
• Equipment: 24+ uniform catch cans, measuring cylinders or graduated containers, stopwatch, wind gauge.
• Environmental constraints: Must be conducted with wind speed at or below 5 mph. Test precision decreases measurably above 2.2 mph. Above 11 mph, tests are considered invalid.
• Professional cost: A certified QWEL or CLIA irrigation audit typically costs $200-500 for a residential property, with the catch can test representing the majority of field time.
• Repeatability: Results vary significantly with wind conditions, water pressure fluctuations, time of day, and technician technique. Two audits of the same system on different days can produce DU values that differ by 5-10 percentage points.
• Single-point-in-time measurement: A catch can test captures system performance at one moment. It does not account for pressure variation throughout the day, seasonal pressure changes, or progressive degradation.

---

2. Design-Computed DU: Simulation Approaches

2.1 The Fundamental Approach

Design-computed DU uses the same mathematical framework as field-measured DU but replaces physical water collection with a computational simulation. The process is:

1. Obtain the radial distribution profile for each sprinkler head from manufacturer test data (per ASABE S398.1). This profile shows water application depth as a function of distance from the head, tested in zero-wind, controlled-pressure conditions.

2. Place the heads in their design positions with the specified arc, radius, and spacing from the irrigation design geometry.

3. Create a virtual catch can grid across the irrigated area at a specified resolution (typically 1 ft or 0.5 m grid points).

4. Superimpose the precipitation contributions from all overlapping heads at each grid point, accounting for arc limits and radius.

5. Calculate DU_LQ from the simulated grid using the same lower-quarter formula as the field method.

2.2 Mathematical Models

Three principal simulation approaches are used in the literature:

2.2.1 Direct Superposition of Radial Profiles

The simplest and most widely used approach. Each sprinkler's radial profile (from manufacturer data per ASABE S398.1) is treated as a radially symmetric precipitation pattern. At each grid point, the distance to each head is calculated, the corresponding precipitation depth is read from the profile, and contributions from all heads within range are summed.

This is the approach used by:

• WinSIPP (Senninger/Hunter) for agricultural sprinkler layout evaluation
• IrriCad for hydraulic and uniformity analysis
• SimplyScapes irrigation engine for coverage scoring

Advantages: Simple, fast, deterministic, directly uses manufacturer data. Limitations: Assumes radial symmetry (valid for full-circle heads, requires adjustment for part-circle arcs), does not account for wind.

2.2.2 Ballistic Trajectory Modeling

Models individual water droplets as ballistic projectiles, solving the equations of motion for drops of different sizes and initial velocities leaving the sprinkler nozzle. This approach:

• Accounts for droplet size distribution from the nozzle
• Models air resistance and gravitational forces
• Can incorporate wind speed and direction
• Produces a full spatial precipitation map

Key research: Playan, Zapata, and colleagues at the CSIC (Spain) developed and validated a ballistic simulation model calibrated against field data in the Ebro Valley. Their calibration achieved a standard error of CU estimation of 3.09%, with a coefficient of determination of 97% between estimated and measured CU values. The model generated 1,440 discrete uniformity estimates from just 12 isolated sprinkler evaluations and 43 solid-set evaluations (Playan et al., 2006, Agricultural Water Management).

Advantages: High accuracy, wind effects, physically-based. Limitations: Computationally intensive, requires detailed nozzle characterization data, calibration needed per sprinkler model.

2.2.3 Machine Learning Approaches

Recent research has applied machine learning algorithms to predict DU from operating parameters without full physical simulation:

• Li et al. (2023) in Nature Scientific Reports used Random Forest (RF), Extreme Gradient Boosting (XGB), and hybrid RF-XGB models to predict water distribution uniformity based on operating pressure, sprinkler height, discharge, nozzle diameter, wind speed, humidity, and temperature.

• Zapata et al. (2025) in Irrigation Science used regression modeling to estimate whole-field uniformity with a coefficient of determination of 97% and standard error of just 1.1%.

These approaches are computationally efficient but require training data from physical tests and may not generalize well across different sprinkler types.

2.3 Software Implementations

Several commercial and research software systems compute sprinkler uniformity from design parameters, but none currently connect this computation to irrigation scheduling:

WinSIPP3 (Senninger/Hunter Industries)

• Calculates precipitation rate and uniformity for various sprinkler models, operating pressures, nozzle sizes, and sprinkler heights.
• Compares different spacing configurations to determine optimal layout.
• Produces densograms (visual uniformity maps of overlapping coverage).
• Outputs: CU, DU_LQ, and Scheduling Coefficient.
• Data source: Distribution profiles from ASABE S398.1 testing of Senninger products.
• Purpose: Design optimization only. Does not generate irrigation schedules.

IrriCad (Lincoln Agritech)

• Industry-leading irrigation design software.
• Performs hydraulic analysis including pressure variation effects on sprinkler performance.
• Calculates uniformity from head placement geometry.
• Purpose: Design and hydraulic analysis. Does not generate watering schedules from uniformity data.

IrriPro (Irriworks)

• Calculates all hydraulic parameters including uniformity of distribution at every point in the network.
• Automatic design and pipe sizing.
• 3D visualization of head losses and uniformity.
• Purpose: Design optimization. No evidence of schedule generation from DU.

Irrigation F/X (Land F/X)

• Uniformity tool examines the layout of each head, determines overlap coverage, and color-codes areas by coverage count.
• Watering Schedule determines the precipitation rate from actual head layout (not just theoretical values) and calculates application time.
• Runtime Schedule mimics smart controller grouping.
• Critical finding: The Watering Schedule uses precipitation rate (PR) from head layout but does NOT use design-computed DU in the schedule calculation. DU is handled as a separate visual analysis tool. The scheduling tools compute runtime from PR alone: Runtime = Target depth / PR. There is no DU-adjusted scheduling.

Pro Contractor Studio (Software Republic)

• Performs distribution analysis and water scheduling.
• Generates irrigation schedule tables.
• No evidence that distribution analysis feeds into schedule calculations.

GIS-Based Approaches

• Zapata et al. used QGIS + EPANET (both free) to simulate water application from all emitters in an irrigation installation, obtaining geospatial representation of applied water and DU. Overlapping areas are summed and rasterized.
• Purpose: Research analysis. Not connected to scheduling.

2.4 How SimplyScapes Computes DU

Based on the research plan and platform description, SimplyScapes computes DU per zone using:

• Inputs: Head positions (x,y coordinates on the design plan), arc (degrees of coverage), radius (throw distance in feet), GPM (gallons per minute from manufacturer catalog data for the selected nozzle).
• Method: Overlapping precipitation pattern analysis from manufacturer radial profiles, similar to the direct superposition approach described in Section 2.2.1.
• Outputs: Per-zone DU percentage (e.g., 80%, 71% as shown in UI screenshots) and per-head Precipitation Rate (e.g., 0.61"/hr for Rain Bird R-VAN24).

This computation happens at design time as part of the automated irrigation design engine's coverage scoring. The DU and PR values are available immediately after head placement without any field work.

---

3. Accuracy Assessment: Design vs. Field DU

3.1 Published Accuracy Comparisons

The academic literature provides strong evidence that simulation-computed uniformity closely matches field-measured uniformity under controlled conditions:

| Study | Method | CU/DU Error vs. Field | Conditions | |-------|--------|----------------------|------------| | Playan et al. (2006) | Ballistic simulation | CU standard error: 3.09% | Calibrated model, Ebro Valley, Spain | | Li et al. (2023) | Machine learning (RF-XGB hybrid) | CU error < 7% | Multiple sprinkler types, varied conditions | | Zapata et al. (2025) | Regression-based estimation | Standard error: 1.1%, R-squared: 97% | Whole-field solid-set systems | | Chen et al. (2023) | Modified ballistic + FEM | Average relative error: 2.46% | Indoor and field validation | | SSIWDTH model (2024) | Ballistic + terrain | Consistency coefficient: 0.96 | Undulating terrain scenarios |

Key finding: Under zero-wind, controlled-pressure conditions (which are the same conditions under which manufacturer data is collected), simulation accuracy is consistently within 2-7% of field measurements.

3.2 The Design-to-Reality Gap

However, design-computed DU represents an ideal-condition upper bound. Real installations introduce several degradation factors that cause field-measured DU to fall below design DU:

3.2.1 Wind Effects (Most Significant Factor)

Wind is the single largest source of DU degradation in landscape sprinkler systems:

• Distribution uniformity of most sprinklers is significantly negatively correlated with wind speed.
• At wind speeds above 2.2 mph (1 m/s), measurable degradation begins.
• At 5 mph (2.2 m/s), the QWEL/IA threshold for valid audit data, DU can be 5-15% lower than zero-wind values.
• Wind shifts the distribution pattern approximately 5 feet downwind for typical spray heads.
• Rotor sprinkler heads show more visible wind distortion than spray heads.
• Very small droplets from high-pressure operation are especially susceptible to wind drift.
• At wind speeds above 11 mph, catch can tests are considered invalid because the distortion is so severe.

Quantitative impact estimates:

• 0-2 mph wind: Negligible impact (< 2% DU reduction)
• 2-5 mph wind: Moderate impact (5-10% DU reduction)
• 5-10 mph wind: Significant impact (10-20% DU reduction)
• 10+ mph wind: Severe impact (20%+ DU reduction, test invalid)

3.2.2 Pressure Variation

Pipe friction losses cause pressure to decrease along lateral lines, resulting in reduced flow and radius from downstream heads:

• A 10% pressure variation from design typically causes 3-5% DU reduction.
• Residential systems with undersized supply lines or long lateral runs are especially susceptible.
• Low-pressure conditions cause spray patterns to not reach adjacent heads, creating brown spots.
• Pressure fluctuation throughout the day (peak municipal demand periods) can cause temporary DU reduction of 5-15%.

3.2.3 Installation Errors

The design assumes heads are installed exactly at their specified positions. Real-world installation introduces deviations:

• Head spacing errors of 6-12 inches from design are common.
• Incorrect arc settings (e.g., 180 degrees set to 170 degrees) create coverage gaps.
• Heads not set to grade (tilted, too high, or too low) distort the pattern.
• Incorrect nozzle selection (wrong GPM for the zone's design pressure).
• Type or brand of equipment has the least impact on DU compared to proper design, installation, and maintenance.

3.2.4 Head Wear and Degradation

Sprinkler components degrade over time:

• Nozzle wear increases the discharge area, raising flow rate at a given pressure and altering the distribution pattern.
• Gear-drive mechanisms wear, causing inconsistent rotation speed.
• Seals and springs degrade, affecting pop-up height and retraction.
• Sprinkler heads typically need replacement every 3-5 years.
• A typical residential system lifespan is 10-20 years depending on maintenance.

3.2.5 Obstructions and Vegetation Growth

• Trees, shrubs, and structures that grow or are added after installation intercept spray patterns.
• Turf growth around spray heads can block low-angle spray patterns.
• Fences, play equipment, and garden beds create shadow zones.

3.3 Quantifying the Design-to-Field Gap

Combining the evidence, we can estimate the typical gap between design-computed DU and field-measured DU:

| Scenario | Design DU | Expected Field DU | Gap | |----------|-----------|-------------------|-----| | New installation, calm conditions, professional install | 80% | 70-75% | 5-10% | | New installation, moderate wind (3-5 mph) | 80% | 60-70% | 10-20% | | 3-year-old system, average maintenance | 80% | 55-65% | 15-25% | | 5+ year system, minimal maintenance | 80% | 40-55% | 25-40% |

The research by Baum et al. (2005) finding an average residential DU of only 45% -- compared to typical design targets of 65-80% -- illustrates the magnitude of this gap in real-world conditions.

---

4. Prior Art Search Results

This section documents the critical search for any system that uses design-derived DU (computed from sprinkler geometry) to generate irrigation schedules. This is the most important finding for the patent/disclosure strategy.

4.1 The Two Halves of the Problem

The innovation connects two well-established technical domains:

Domain A: DU Simulation from Design Geometry (well-established)

• Academic literature on ballistic and superposition models dates to the 1980s.
• Commercial software (WinSIPP, IrriCad, IrriPro, Irrigation F/X) computes DU from head layout geometry as a design evaluation tool.
• SimplyScapes already does this per zone.

Domain B: DU-Adjusted Irrigation Scheduling (well-established)

• QWEL formula: RTM = 1 / (0.4 + 0.6 x DU_LQ) uses DU to compute runtime.
• UC Davis CCUH scheduling worksheets use DU to calculate the Scheduling Multiplier.
• EPA WaterSense, MWELO, and IA methodologies all incorporate DU into efficiency calculations.
• Smart controllers (Rachio, Hydrawise) accept DU as an input parameter.

The Gap: Nobody connects Domain A to Domain B.

4.2 Patent Search Results

US7596429B2 / WO2004052560A2 (Irrigation system)

• Uses DU in the irrigation requirement calculation.
• DU is treated as a user input (manually entered during system setup).
• Does not compute DU from design geometry.
• Does not describe any automated DU derivation method.

US8948921B2 / US20120303168A1 (Smart irrigation)

• Lists DU as one of many landscape information parameters.
• Does not specify how DU is obtained (field test, user input, or computed).
• No methodology for DU computation from design geometry.
• The patent treats DU as a static input, not a computed value.

US7899580B2 (Irrigation system)

• Lists DU among user-provided landscape parameters per irrigation station.
• DU is a manual input alongside plant type, soil type, and precipitation rate.
• No design-based DU computation.

US6895987B2 (Irrigation controller modifier)

• Receives DU as information from the user.
• No automated DU derivation.

US10028454B2 (Husqvarna/ETwater cloud irrigation)

• The closest prior art to cloud-based irrigation scheduling.
• Claims are tied to hardware retrofit system.
• Does not describe DU computation from design geometry.

SmartRain portfolio (US9307706B2, US10660279B2, US11684029B2, US11839184B2, US20210176931A1)

• All claims require physical hardware (controllers, flow meters, soil sensors, GPS).
• None describe computing DU from design parameters.
• None bridge the design-to-schedule gap.

4.3 Software Product Search Results

Rachio smart controller:

• Accepts DU as an "Efficiency" setting in Advanced Zone Settings.
• Default value: 70% (a generic assumption, not computed from any design).
• Users are told "the only true way to measure efficiency is to do a catch cup test."
• No mechanism to receive DU from a design tool or compute it from head layout.

Hydrawise (Hunter):

• Accepts zone-level parameters but does not accept DU as a direct input in the consumer product.
• No design-to-schedule pipeline.

Orbit B-hyve:

• Users can enter catch cup test results into the app.
• No design-derived DU capability.

WeatherTRAK / HydroPoint:

• Uses ET-based scheduling with DU from field audits.
• Requires SWAT-certified auditor to provide field-measured DU.
• No design-derived DU option.

Weathermatic SmartLink:

• ET-based scheduling for professional landscape management.
• DU from field measurement only.

Land F/X / Irrigation F/X:

• Computes uniformity visually from head layout (coverage color map).
• Generates watering schedules from precipitation rate (PR).
• Does NOT use computed DU in the watering schedule calculation. The runtime formula uses PR alone: Runtime = Target depth / PR. DU is a separate design evaluation tool, not connected to scheduling.

IrriCad / IrriPro / WinSIPP:

• Compute uniformity from design geometry for design evaluation purposes.
• None generate irrigation schedules (watering runtimes) from computed DU.

Pro Contractor Studio:

• Performs distribution analysis and generates schedule tables.
• No evidence that distribution analysis feeds into schedule calculations.

4.4 Academic Literature Search Results

Extensive searches across Google Scholar, ASCE Journal of Irrigation and Drainage Engineering, Irrigation Science (Springer), Agricultural Water Management (Elsevier), and Transactions of the ASABE found:

• Dozens of papers on computing/simulating DU from design parameters.
• Dozens of papers on using DU in irrigation scheduling formulas.
• Zero papers that connect simulated/design-computed DU directly to irrigation schedule generation without a field measurement step.

The closest related work:

• Keller and Bliesner (1990) in "Sprinkle and Trickle Irrigation" established the theoretical framework for using DU in irrigation efficiency calculations, but assumed field-measured DU.
• Playan et al. (2006) demonstrated that simulated DU is highly accurate (3% standard error), but used the simulation for design optimization, not schedule generation.
• Li et al. (2023) predicted DU using machine learning, but the purpose was performance evaluation, not scheduling.

4.5 Defensive Publication and IP Database Search

Based on searches described in the research plan:

• TDCommons: No defensive publications found for design-DU-to-schedule.
• IP.com: No prior art disclosures found for this specific integration.

4.6 Prior Art Summary

| What Exists | What Does NOT Exist | |-------------|---------------------| | Computing DU from design geometry (simulation) | Using design-computed DU to generate irrigation schedules | | Using DU in scheduling formulas (QWEL, etc.) | Connecting design software DU output to scheduling engines | | Smart controllers accepting DU as user input | Smart controllers deriving DU from design data | | Design tools computing PR from head layout | Design tools feeding both PR and DU into runtime calculation | | Catch can tests providing DU for scheduling | Any system that eliminates the catch can test from the scheduling pipeline |

Conclusion: The specific integration of design-computed DU into the QWEL formula chain (or any scheduling formula) to generate per-zone irrigation runtimes represents a novel mechanism with no identified prior art.

---

5. Recommended Safety Factors

Since design-computed DU represents an ideal-condition upper bound, safety factors must be applied to account for real-world degradation when using it for scheduling purposes.

5.1 The QWEL Run Time Multiplier

The QWEL formula already incorporates DU through the Run Time Multiplier:

RTM = 1 / (0.4 + 0.6 x DU_LQ)

This means a DU_LQ of 0.80 yields RTM = 1.136, while a DU_LQ of 0.60 yields RTM = 1.316. The formula already adds a buffer -- it does not assume 100% efficiency even at high DU values due to the 0.4 constant term.

5.2 Recommended Design-DU Adjustment Factor

To convert design-computed DU to a conservative scheduling-ready value, we recommend a Design-to-Field Adjustment Factor (DFAF) based on the degradation analysis in Section 3.3:

Tier 1 -- New Installation (0-2 years), professional install:

DU_scheduling = DU_design x 0.90

Rationale: 5-10% degradation from minor installation deviations, normal pressure variation, and average wind exposure during irrigation events.

Tier 2 -- Established System (2-5 years), typical maintenance:

DU_scheduling = DU_design x 0.80

Rationale: 15-25% degradation from head wear, vegetation interference, minor pressure degradation, and accumulated installation drift.

Tier 3 -- Aging System (5+ years), unknown maintenance:

DU_scheduling = DU_design x 0.70

Rationale: Significant degradation likely from wear, clogging, and deferred maintenance.

5.3 Wind Adjustment

For sites with known wind exposure, an additional wind derating factor should be applied:

| Wind Exposure Category | Wind Derating Factor | |----------------------|---------------------| | Sheltered (enclosed courtyard, lee side of building) | 1.00 (no adjustment) | | Normal (typical residential, partial exposure) | 0.95 | | Exposed (open field, hilltop, coastal) | 0.85 |

Combined formula:

DU_scheduling = DU_design x DFAF x Wind_factor

Example: A SimplyScapes zone showing DU_design = 80% for a 1-year-old residential system with normal wind exposure:

DU_scheduling = 0.80 x 0.90 x 0.95 = 0.684 (68.4%)
RTM = 1 / (0.4 + 0.6 x 0.684) = 1 / 0.810 = 1.234

This means the schedule would apply 23.4% more water than the theoretical minimum to compensate for real-world non-uniformity. Compare to using the unadjusted design DU of 80%:

RTM = 1 / (0.4 + 0.6 x 0.80) = 1 / 0.88 = 1.136

The safety-factored approach adds approximately 10% more water than the design-only calculation, providing a conservative buffer without the cost of a field audit.

5.4 Comparison to Current Practice

It is worth noting that the current alternative for systems without a field audit is far worse:

• Rachio default: Uses a generic 70% efficiency for all zones regardless of design quality. This is neither calibrated to the design nor to field conditions.
• No-audit scenario: Most homeowners and even many landscape professionals set schedules based on intuition, watering until the grass "looks right," or using municipal guidelines (e.g., "water 3 times per week for 15 minutes"). These approaches have no DU adjustment at all.
• Design-computed DU with safety factors provides a site-specific, zone-specific DU value that is grounded in the actual head layout and manufacturer performance data, even if it requires conservative adjustment. This is categorically better than a generic default or no DU at all.

5.5 Feedback Loop for Refinement

Design-computed DU with safety factors should be treated as a starting point that can be refined through:

1. Optional catch can validation: Users who perform a catch can test can replace the design-computed DU with field-measured DU, providing maximum accuracy.
2. Water usage feedback: If actual water consumption (from controller data or utility bills) exceeds or falls below predictions, the safety factors can be adjusted.
3. Turf condition monitoring: Brown spots or soggy areas indicate the DU adjustment is too aggressive or too conservative.
4. System age tracking: As the system ages, the DFAF tier can be automatically adjusted.

---

6. Novelty Assessment

6.1 Is This Genuinely New?

Yes. Based on exhaustive search across patents, commercial software, academic literature, and industry publications, we found no prior art for the specific mechanism of:

Computing DU from irrigation design geometry (head placement, arc, radius, spacing, nozzle performance data) and feeding that DU value into the QWEL formula chain (or any equivalent scheduling formula) to automatically generate per-zone irrigation runtimes without a physical catch can test.

6.2 Why Hasn't This Been Done Before?

The gap exists because of a historical divide between two distinct professional roles and tool categories:

1. Irrigation designers use CAD tools (Land F/X, IrriCad, IrriPro) to design systems. They compute DU to evaluate design quality (will this layout provide adequate uniformity?). Their work product is a set of construction documents. They do not typically generate operational schedules.

2. Irrigation auditors (QWEL, CLIA certified) evaluate installed systems. They measure DU with catch cans and use it to calculate scheduling adjustments. Their work product is a set of schedule recommendations. They do not have access to design geometry.

3. Smart controller companies (Rachio, Hunter, Rain Bird) build scheduling engines that accept DU as a user input but have no connection to design tools. Their DU input is either a generic default (70%) or requires the user to perform a catch can test.

4. Irrigation design software companies (Land F/X, IrriCad) compute DU from design geometry but do not have scheduling engines. Their DU output is used to improve the design, not to generate schedules.

SimplyScapes is unique in that it operates across all four roles: it is a design tool (head placement), a simulation engine (DU computation), a scheduling engine (QWEL formula chain), and a controller integration platform (Rachio API). No other system spans this full pipeline.

6.3 Elements of Novelty

The novel mechanism has several distinct elements, each strengthening the overall novelty claim:

1. Design-geometry-derived DU as a scheduling input: Using the output of a sprinkler overlap simulation (computed from head positions, arcs, radii, and manufacturer performance data) as the DU input to an irrigation scheduling formula.

2. Elimination of the catch can test from the scheduling pipeline: For the first time, a complete ETo-to-runtime schedule can be generated from a new irrigation design without any field measurement.

3. Zone-specific DU from design: Each zone gets its own DU value based on its specific head layout, rather than a generic default. This is more accurate than a generic 70% default even with safety factor derating.

4. Integrated design-to-schedule pipeline: The same platform that places heads and computes DU also generates the schedule and pushes it to a controller. No data transfer, no manual entry, no separate tools.

5. Safety-factor framework for design DU: The tiered adjustment approach (DFAF + wind factor) to convert ideal-condition design DU to a conservative scheduling-ready value.

6.4 Defensive Disclosure Implications

For the defensive disclosure (SS-TD-2026-002), the following alternative embodiments should be claimed to protect the full innovation space:

• Design-DU-to-schedule using any scheduling formula (QWEL, IA, MWELO, custom)
• Design-DU with safety factors based on system age, wind exposure, or installation quality
• Design-DU refined by optional field measurement (catch can override)
• Design-DU adjusted using water usage feedback from controllers
• Design-DU adjusted using weather data (wind speed at time of irrigation)
• Design-DU used to calculate cycle-soak splits (via time-to-runoff from soil infiltration rate and slope)
• Design-DU used for MWELO compliance budgets (connecting design evaluation to regulatory compliance)
• Design-DU combined with satellite ET data for schedule generation
• Design-DU combined with soil moisture sensor feedback for adaptive scheduling
• Machine-learning-predicted DU from design parameters used in scheduling

---

7. Sources

| # | Type | Reference | URL / Location | |---|------|-----------|---------------| | 1 | Standard | ASABE S436.1 -- Test Procedure for Uniformity of Water Distribution | https://www.canr.msu.edu/uploads/235/67987/ASAE_S436.1.pdf | | 2 | Standard | ASABE/ICC 802 -- Landscape Irrigation Sprinkler and Emitter Standard | https://elibrary.asabe.org/abstract.asp?aid=45690 | | 3 | Standard | ASABE S398.1 -- Sprinkler Testing and Performance Reporting | ASABE Library | | 4 | Guideline | Irrigation Association Audit Guidelines (CLIA/CGIA) | https://www.irrigation.org/IA/FileUploads/IA/Certification/CLIA-CGIA_AuditGuidelines.pdf | | 5 | Guideline | QWEL Irrigation Audit Protocol | https://www.qwel.net/files/QWEL_Irrigation_Audit.pdf | | 6 | Guideline | QWEL Exam Formula Sheet v2.0 | https://www.qwel.net/files/QWEL_Exam_Formula.pdf | | 7 | Paper | Baum et al. (2005). Analysis of Residential Irrigation Distribution Uniformity. J. Irrigation and Drainage Engineering, ASCE, 131(4). | https://ascelibrary.org/doi/10.1061/(ASCE)0733-9437(2005)131:4(336) | | 8 | Paper | Playan, Zapata et al. (2006). Assessing sprinkler irrigation uniformity using a ballistic simulation model. Agricultural Water Management, 84(1-2), 89-100. | https://www.sciencedirect.com/science/article/abs/pii/S0378377406000266 | | 9 | Paper | Li et al. (2023). Prediction of water distribution uniformity of sprinkler irrigation system based on machine learning algorithms. Nature Scientific Reports. | https://www.nature.com/articles/s41598-023-47688-3 | | 10 | Paper | Zapata et al. (2025). Estimating whole-field solid-set sprinkler irrigation uniformity. Irrigation Science, Springer. | https://link.springer.com/article/10.1007/s00271-025-01036-7 | | 11 | Paper | Chen et al. (2023/2024). Evaluation of water distribution and uniformity of sprinkler irrigation based on harmonic analysis and FEM. Biosystems Engineering. | https://www.sciencedirect.com/science/article/abs/pii/S1537511024002514 | | 12 | Paper | SSIWDTH model (2024). Accurate model for sprinkler water distribution on undulating terrain. Computers and Electronics in Agriculture. | https://www.sciencedirect.com/science/article/abs/pii/S0168169924005878 | | 13 | Paper | Sprinkler irrigation uniformity assessment: Relational analysis of CU and DU. Xue (2023). Irrigation and Drainage, Wiley. | https://onlinelibrary.wiley.com/doi/10.1002/ird.2837 | | 14 | Paper | Extended Assessment of Sprinkler Irrigation Uniformity Using GIS and Hydraulic Modeling (2022). Sustainability, MDPI. | https://www.mdpi.com/2071-1050/14/15/9723 | | 15 | Paper | von Bernuth & Mecham (2009). Revisiting the Scheduling Coefficient. IA Technical Paper. | https://www.irrigation.org/IA/FileUploads/IA/Resources/TechnicalPapers/2009/RevisitingTheSchedulingCoefficient.pdf | | 16 | Paper | Sprinkler Head Maintenance Effects on Water Application Uniformity (2000). J. Irrigation and Drainage Engineering, ASCE, 126(3). | https://ascelibrary.org/doi/10.1061/(ASCE)0733-9437(2000)126:3(142) | | 17 | IA Paper | Using Distribution Uniformity to Evaluate the Quality of a Sprinkler System (2004). Irrigation Association Technical Papers. | https://www.irrigation.org/IA/FileUploads/IA/Resources/TechnicalPapers/2004/UsingDistributionUniformityToEvaluateTheQualityOfASprinklerSystem.pdf | | 18 | IA Paper | Maximizing Irrigation Distribution Uniformity with Catch-Can Performance Data (2008). Irrigation Association Technical Papers. | https://www.irrigation.org/IA/FileUploads/IA/Resources/TechnicalPapers/2008/MaximizingIrrigationDistributionUniformityWithCatch-CanPerformanceData.pdf | | 19 | Extension | Oklahoma State University: Effects of Wind Speed and Water Pressure on Home Sprinkler Systems. | https://extension.okstate.edu/fact-sheets/the-effects-of-wind-speed-and-water-pressure-on-home-sprinkler-systems.html | | 20 | Extension | Utah State University: Maintaining and Improving Irrigation Application Uniformity. | https://extension.usu.edu/irrigation/research/maintaining-and-improving-irrigation-application-uniformity-in-sprinkler-and-drip-systems | | 21 | Extension | NC State: Landscape Irrigation Auditing Made Simple. | https://content.ces.ncsu.edu/landscape-irrigation-auditing-made-simple | | 22 | Extension | Alabama Cooperative Extension: Maintaining Water Application Uniformity. | https://www.aces.edu/blog/topics/crop-production/maintaining-water-application-uniformity-in-irrigation-systems/ | | 23 | Extension | UC Davis CCUH: Measuring DU and Calculating Run Time. | https://ccuh.ucdavis.edu/measuring-DU-run-time | | 24 | Extension | UF/IFAS: Irrigation Efficiency and Distribution Uniformity. | https://blogs.ifas.ufl.edu/columbiaco/2024/12/04/irrigation-efficiency-and-distribution-uniformity/ | | 25 | Software | WinSIPP3 -- Senninger/Hunter Sprinkler Simulation | https://agriculture.hunterirrigation.com/irrigation-product/winsipptm3 | | 26 | Software | IrriCad -- Lincoln Agritech Irrigation Design | https://www.irricad.com/ | | 27 | Software | IrriPro -- Irriworks Irrigation Design | https://irriworks.com/irripro/ | | 28 | Software | Irrigation F/X -- Land F/X CAD Plugin | https://www.landfx.com/irrigationfx | | 29 | Software | Pro Contractor Studio -- Software Republic | https://www.softwarerepublic.com/ | | 30 | Patent | US7596429B2 -- Irrigation system (DU as user input) | https://patents.google.com/patent/US7596429 | | 31 | Patent | US8948921B2 -- Smart irrigation (DU in landscape info) | https://patents.google.com/patent/US8948921B2 | | 32 | Patent | US7899580B2 -- Irrigation system (DU as user input) | https://patents.google.com/patent/US7899580 | | 33 | Patent | US6895987B2 -- Irrigation controller modifier | https://patents.google.com/patent/US6895987 | | 34 | Product | Rachio Advanced Zone Settings (Efficiency = DU, default 70%) | https://support.rachio.com/what-are-advanced-zone-settings-Byh9v81Fv | | 35 | Product | Rain Bird Nozzle Performance Data (VAN Series, MPR) | https://www.rainbird.com/sites/default/files/media/documents/2020-09/van-series-spray-nozzles-performance-charts.pdf | | 36 | Reference | Wikipedia: Distribution Uniformity | https://en.wikipedia.org/wiki/Distribution_uniformity | | 37 | Reference | QWEL Reference Manual (California) | https://www.qwel.net/files/QWEL_Reference_Manual_CA_INTERACTIVE.pdf | | 38 | Reference | Hunter Irrigation Technical Manual (DU, Friction, PR) | https://www.hunterirrigation.com/sites/default/files/BR_IrrigationTechManual_dom.pdf | | 39 | Cross-ref | SS-RR-2026-001 (Plant-Specific Drip Irrigation Intelligence) | docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/plant-specific-drip-irrigation-intelligence/research/report-v2-2026-03-01.md | | 40 | Cross-ref | SS-RR-2026-001 Patent Landscape (competitive findings) | docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/plant-specific-drip-irrigation-intelligence/research/supporting/patent-landscape.md |

Smart Irrigation Controller APIs for Schedule Integration

ID: SS-RR-2026-003 | Date: 2026-03-01 | Status: complete Domain: Irrigation Management / Smart Controller APIs Parent: Automated Turf Irrigation Scheduling (SS-RP-2026-002) Crossover: Controller Integration Feasibility (SS-RR-2026-002)

TL;DR

SimplyScapes needs to push ETo-derived irrigation schedules -- zone-by-zone runtimes, days of week, and start times -- computed from design-time DU and PR data directly to smart controllers. This paper maps the API landscape in depth. Rachio remains the priority target: its public REST API (v2) exposes 25+ endpoints with bearer-token auth at 1,700 calls/day, including zone-level runtime control via start_multiple, seasonal adjustment via schedulerule/seasonal_adjustment, moisture-level overrides via setMoisturePercent, and real-time feedback via webhooks with flowVolumeG data from connected flow meters. However, the API does not support programmatic schedule creation -- schedules must be pre-created in the Rachio app, then controlled via API. OpenSprinkler provides the deepest control: full CRUD for programs via its /cp endpoint, including per-station durations, days-of-week bitmasks, multiple start times, and weather adjustment flags. RainMachine is a strong third option with a documented local REST API supporting program creation, zone property management, flow sensor data, and ET-based scheduling built into the firmware. Hunter Hydrawise has a capable GraphQL API (v2) gated behind commercial authorization. Rain Bird has no public API for residential controllers; the IQ4 commercial platform requires a paid subscription and focuses on data retrieval rather than schedule push. Orbit B-hyve has no official API; community libraries are reverse-engineered and commercially unviable. Weathermatic SmartLink has a documented REST API with API key/secret authentication, oriented toward commercial landscape management.

---

1. Controller API Capability Matrix

| Controller | API Type | Auth Model | Schedule Push | Usage Readback | Rate Limits | Cost | Commercial Use | |-----------|----------|-----------|---------------|----------------|-------------|------|----------------| | Rachio 3 / 3e | REST (cloud) | OAuth2 bearer token (user-generated) | Partial: start/stop/adjust existing schedules; no create | Yes: webhooks with flowVolumeG, event history via GET | 1,700 calls/day; reset midnight UTC | Free | Yes (public API) | | OpenSprinkler 3.x | HTTP (local) | MD5 password hash per request | Full CRUD: create/modify/delete programs, per-station durations, days, start times | Yes: /jl log with flow pulse counts per station run | None (local) | Free | Yes (open source, GPL) | | RainMachine Pro/Touch | REST (local + cloud) | Password -> access_token (local); email/password (remote) | Full CRUD: create/modify programs, set zone properties, duration + frequency | Yes: /watering/details with flowclicks, /dailystats | None documented (local) | Free | Yes (documented developer API) | | Hunter Hydrawise (v1.5) | REST (cloud) | API key (query param) | No: read status + manual start/stop only | Limited: next-run times, current status | Rate-limited; nextpoll field controls interval | Free | No (personal use only) | | Hunter Hydrawise (v2) | GraphQL (cloud) | OAuth2 with scopes | Unknown: likely more capable than v1.5 | Reporting scope available | Rate-limited (429 errors reported) | Free (gated) | Requires written authorization | | Rain Bird IQ4 | REST (cloud) | API subscription + owner role | Read-focused: retrieves schedules, flow data, alarms | Yes: flow data per site, alarm history | Unknown | Paid subscription | Yes (commercial platform) | | Rain Bird LNK2 (residential) | SIP binary protocol (local) | Password | No: read schedules + manual run only; no create/modify | No | N/A (local, 1 connection) | N/A | No (reverse-engineered) | | Orbit B-hyve | REST + WebSocket (cloud) | Email/password -> JWT | Unknown (undocumented) | Unknown | Unknown | N/A | No (unofficial, reverse-engineered) | | Weathermatic SmartLink | REST (cloud) | API key + secret token | Yes (commercial API via Apiary docs) | Yes (commercial landscape reporting) | Unknown | Requires developer registration | Yes (commercial) |

---

2. Rachio API Deep Dive

2.1 API Architecture

Base URL: https://api.rach.io/1

Protocol: RESTful HTTP with JSON payloads.

Authentication: OAuth2 bearer token.

• Token is generated by the user in the Rachio mobile app: Profile > API key > Copy.
• Passed in the Authorization header: Authorization: Bearer <token>.
• There is no delegated OAuth flow for third-party apps. Each user must manually copy their API key. Rachio community forums have discussed adding webhook OAuth authorization, but this has not been implemented as of March 2026.
• The token is a static, long-lived string (UUID format, e.g., 8e600a4c-0027-4a9a-9bda-dc8d5c90350d).

Rate Limits:

• 1,700 API calls per day (~1.18 calls/minute average).
• Reset at midnight UTC.
• Response headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset.
• Rachio is willing to discuss exceptions for specific use cases.
• Webhooks do not count against rate limits and should be used for status monitoring.

2.2 Complete Endpoint Reference

Person / User:

| Endpoint | Method | Purpose | |----------|--------|---------| | /public/person/info | GET | Get authenticated user info; returns person ID | | /public/person/:id | GET | Get user details including device IDs |

Device / Controller:

| Endpoint | Method | Purpose | |----------|--------|---------| | /public/device/:id | GET | Full controller details: zones, scheduleRules, flexScheduleRules, status, location | | /public/device/:id/current_schedule | GET | Currently running schedule and zone | | /public/device/:id/event?startTime=&endTime= | GET | Historical watering events (timestamps in epoch ms) | | /public/device/:id/forecast?units= | GET | Weather forecast data (ETo, precip, temp, wind, humidity) | | /public/device/on | PUT | Power device on | | /public/device/off | PUT | Power device off (standby mode) | | /public/device/stop_water | PUT | Stop all active watering | | /public/device/rain_delay | PUT | Set rain delay (duration in seconds) | | /public/device/pause_zone_run | PUT | Pause current zone run | | /public/device/resume_zone_run | PUT | Resume paused zone run |

Zone Control:

| Endpoint | Method | Purpose | |----------|--------|---------| | /public/zone/:id | GET | Zone config: vegetation, soil, nozzle, shade, rootZoneDepth, efficiency, MAD | | /public/zone/start | PUT | Start a single zone with duration (body: {"id": "...", "duration": 900}) | | /public/zone/start_multiple | PUT | Start multiple zones sequentially with per-zone durations | | /public/zone/setMoistureLevel | PUT | Set soil moisture in mm | | /public/zone/setMoisturePercent | PUT | Set soil moisture as percentage (0.0 - 1.0) | | /public/zone/enable | PUT | Enable a zone | | /public/zone/disable | PUT | Disable a zone |

Schedule Rules:

| Endpoint | Method | Purpose | |----------|--------|---------| | /public/schedulerule/:id | GET | Get schedule details: zones with durations, days, type, cycle/soak | | /public/schedulerule/start | PUT | Trigger a pre-created schedule immediately | | /public/schedulerule/skip | PUT | Skip the next scheduled run | | /public/schedulerule/seasonal_adjustment | PUT | Adjust all zone durations by percentage (-1.0 to 1.0) | | /public/schedulerule/skip_forward_zone_run | PUT | Skip to the next zone in a running schedule | | /public/flexschedulerule/:id | GET | Get Flex schedule details |

Webhooks:

| Endpoint | Method | Purpose | |----------|--------|---------| | /public/notification/webhook | POST | Register a new webhook | | /public/notification/webhook | PUT | Update an existing webhook | | /public/notification/webhook/:id | GET | Get webhook details | | /public/notification/webhook/:id | DELETE | Delete a webhook | | /public/notification/:deviceId/webhook | GET | List all webhooks for a device | | /public/notification/webhook_event_type | GET | List all available event types |

2.3 Zone Data Model

The Rachio zone object contains properties that map directly to irrigation science parameters:

{
  "id": "zone-uuid",
  "zoneNumber": 1,
  "name": "Front Lawn",
  "enabled": true,
  "customCrop": { "name": "Cool Season Grass", "coefficient": 0.8 },
  "customSoil": { "name": "LOAM" },
  "customNozzle": { "name": "FIXED_SPRAY_HEAD", "inchesPerHour": 1.5 },
  "customShade": { "name": "LOTS_OF_SUN" },
  "rootZoneDepth": 6.0,
  "yardAreaSquareFeet": 2500,
  "efficiency": 0.7,
  "managementAllowedDepletion": 0.5,
  "depthOfWater": 0.41,
  "availableWater": 0.17,
  "saturatedDepthOfWater": 0.83,
  "slope": "FLAT"
}

These properties are writable via PUT to /public/zone, meaning SimplyScapes can synchronize zone configuration (vegetation type, soil type, nozzle precipitation rate, shade exposure, root depth, efficiency) from the irrigation design directly to Rachio. This alignment ensures Rachio's own scheduling intelligence operates on accurate design data.

2.4 ScheduleRule Data Model

{
  "id": "schedule-uuid",
  "name": "Morning Watering",
  "enabled": true,
  "zones": [
    { "zoneId": "zone-1-uuid", "duration": 900, "sortOrder": 0 },
    { "zoneId": "zone-2-uuid", "duration": 600, "sortOrder": 1 },
    { "zoneId": "zone-3-uuid", "duration": 1200, "sortOrder": 2 }
  ],
  "scheduleJobTypes": ["DAY_OF_WEEK_1", "DAY_OF_WEEK_3", "DAY_OF_WEEK_5"],
  "startDate": 1709251200000,
  "totalDuration": 2700,
  "cycleSoak": true,
  "cycleSoakStatus": "ON",
  "rainDelay": true,
  "weatherIntelligenceSensitivity": 0.5,
  "seasonalAdjustment": 0.0,
  "type": "FIXED"
}

Key fields for schedule integration:

• zones[].duration: Per-zone runtime in seconds.
• scheduleJobTypes: Encodes watering days. Values include DAY_OF_WEEK_0 through DAY_OF_WEEK_6 (Sunday=0), ODD, EVEN, INTERVAL_N, and ANY.
• seasonalAdjustment: Percentage modifier from -1.0 (skip) to 1.0 (double).
• cycleSoak: Enables cycle/soak to prevent runoff on slopes or clay soils.
• weatherIntelligenceSensitivity: Controls how aggressively Weather Intelligence skips runs (0.0 = never skip, 1.0 = aggressive skip).

2.5 Schedule Push Workflow for SimplyScapes

Because the Rachio API does not expose a schedule creation endpoint, the push workflow must use a hybrid approach:

Step 1: One-time setup (user action in Rachio app). User creates a Fixed schedule in the Rachio app with the zones in the correct order. This serves as the "template" schedule that SimplyScapes will control.

Step 2: Sync zone properties (API). SimplyScapes writes zone configuration (vegetation type, soil, nozzle PR, shade, root depth, efficiency) from the irrigation design to Rachio via PUT /public/zone. This ensures Rachio's own weather intelligence operates on accurate data.

Step 3: Push runtime adjustments (API). SimplyScapes computes ETo-based runtimes using the QWEL formula chain and translates them to a seasonal adjustment percentage relative to the base schedule durations. Apply via PUT /public/schedulerule/seasonal_adjustment.

Step 4: Alternative -- direct zone runs (API). For more precise control, SimplyScapes can bypass the schedule entirely and use PUT /public/zone/start_multiple to run zones in sequence with exact durations calculated from the QWEL formula. This gives per-zone, per-day control but loses Rachio Weather Intelligence skip logic.

Step 5: Set moisture levels (API). SimplyScapes can use PUT /public/zone/setMoisturePercent to tell Rachio's Flex Daily algorithm what the current soil moisture level is, letting Flex Daily's built-in scheduling logic determine when to water. This is the most elegant integration but requires SimplyScapes to compute soil moisture depletion.

Step 6: Monitor execution (Webhooks). Register webhooks for ZONE_STARTED, ZONE_COMPLETED, SCHEDULE_COMPLETED, and WEATHER_INTELLIGENCE_SKIP events. Zone completion events include flowVolumeG (gallons from flow meter) and durationSeconds (actual runtime).

Tradeoffs:

| Approach | Pros | Cons | |----------|------|------| | Seasonal adjustment | Simple; preserves Weather Intelligence | Uniform % across all zones in schedule | | start_multiple (run-once) | Per-zone precision; exact durations | Loses Weather Intelligence; must handle scheduling ourselves | | setMoisturePercent | Leverages Flex Daily's sophisticated algorithm | Requires accurate soil moisture modeling; indirect control |

2.6 Webhook Event Payloads

Zone completion events provide execution feedback:

{
  "id": "webhook-delivery-uuid",
  "type": "ZONE_STATUS",
  "subType": "ZONE_COMPLETED",
  "deviceId": "device-uuid",
  "zoneId": "zone-uuid",
  "zoneNumber": 3,
  "zoneName": "Back Lawn",
  "duration": 900,
  "durationInMinutes": 15,
  "flowVolume": 125.3,
  "zoneRunStatus": {
    "state": "COMPLETED",
    "startTime": "2026-03-01T06:00:00Z",
    "endTime": "2026-03-01T06:15:00Z",
    "scheduleType": "FIXED"
  },
  "timestamp": "2026-03-01T06:15:02Z"
}

The flowVolume field (reported as flowVolumeG in gallons) is available when a Rachio-compatible flow meter is connected. This enables the feedback loop: compare predicted vs actual water application.

Webhook deliveries include an x-signature header computed via HMAC-SHA256 using the API token as the shared secret, allowing verification that events originate from Rachio servers.

2.7 Rachio Flex Daily vs. QWEL ETo Comparison

Rachio Flex Daily algorithm:

• Built on the Penman-Monteith equation for reference evapotranspiration (ETo).
• Uses real-time weather data: temperature, humidity, wind speed, solar radiation.
• Applies crop coefficients to convert ETo to crop ET (ETc = ETo x Kc).
• Tracks soil moisture depletion daily: depletion = prior depletion + ETc - precipitation.
• Waters when depletion reaches the Management Allowed Depletion (MAD) threshold.
• Dynamically adjusts both frequency and duration based on weather forecasts.
• Introduced "Dynamic Crop Coefficient" feature that varies Kc by season and growth stage.

QWEL formula chain (SimplyScapes approach):

• Uses reference ETo from local weather stations (typically CIMIS, CoAgMet, or NWS data).
• Applies Plant Factor (PF) analogous to crop coefficient: ETc = ETo x PF.
• Accounts for Distribution Uniformity (DU) from design data: adjusted runtime = (ETc / PR) / DU.
• Uses design-time Precipitation Rate (PR) rather than manufacturer-specified nozzle rate.
• Incorporates MWELO landscape coefficient (KL = Ks x Kd x Kmc) for mixed plantings.
• Results in weekly or monthly watering budgets in inches, converted to zone runtimes.

Key differences:

| Aspect | Rachio Flex Daily | QWEL (SimplyScapes) | |--------|------------------|---------------------| | ETo source | Weather Underground / NWS (cloud) | CIMIS, CoAgMet, NWS (configurable) | | ETo method | Penman-Monteith | Penman-Monteith (via station data) | | Crop coefficient | Per-zone (user-configured or dynamic) | Per-zone from plant database (PF) | | DU factor | Not used (assumes uniform application) | From design geometry (key differentiator) | | PR source | User-configured nozzle type | Design-computed from head layout | | Scheduling | Daily dynamic (water when MAD reached) | Weekly/monthly budget allocation | | Soil moisture | Modeled depletion tracking | Optional sensor integration | | Slope handling | Cycle/soak from zone config | Cycle/soak calculated from design |

The SimplyScapes advantage is that DU and PR come from actual design geometry rather than generic manufacturer specs or user configuration. A spray zone with poor head-to-head coverage (DU = 0.55) receives 82% more runtime than one with excellent uniformity (DU = 1.0) -- a correction that Rachio's algorithm cannot make because it does not know the DU.

Integration implication: Rather than replacing Flex Daily entirely, SimplyScapes can enhance it by writing accurate zone properties (vegetation, soil, nozzle, shade) and adjusting moisture levels via setMoisturePercent to feed Flex Daily better inputs. Alternatively, SimplyScapes can bypass Flex Daily and push exact runtimes via start_multiple, applying its own DU-corrected calculations.

---

3. Hunter Hydrawise API

3.1 API v1.5 (REST) -- Personal Use

Base URL: https://api.hydrawise.com/api/v1/

Authentication: API key passed as a query parameter (api_key=<key>). Generated from the Hydrawise account: Menu > Account Details > Account Settings > Generate API Key.

Endpoints:

| Endpoint | Method | Purpose | |----------|--------|---------| | statusschedule.php | GET | Current schedule status, upcoming runs, zone states | | customerdetails.php | GET | Account info, controllers, zone configuration | | setzone.php | GET | Zone control: start (action=run), stop (action=stop), suspend |

Parameters for setzone.php:

• action: run, stop, suspend, suspendall, runall, stopall
• relay_id: Zone identifier (Hydrawise calls zones "relays")
• period_id: Schedule reference
• custom: Duration in seconds for manual run

Capabilities:

• Read controller names, zone names and numbers.
• Read time until next scheduled run, run duration, currently running zone.
• Manual start/stop zones with custom duration.
• Run all stations.
• Suspend individual zones or all zones.

Cannot do:

• Create or modify schedules.
• Set zone properties (vegetation, soil, nozzle).
• Access water usage or flow data.

Rate limiting: The statusschedule.php response includes a nextpoll field indicating the minimum interval before the next API call should be made. Exceeding this rate results in HTTP 429 errors. Home Assistant integrations have encountered frequent rate limiting issues, suggesting the limit is relatively aggressive.

Commercial restriction: The API Terms of Use explicitly state this API is for personal use only. Commercial use requires prior written authorization from Hunter Industries.

3.2 API v2 (GraphQL/OAuth2) -- Commercial Path

Endpoint: https://app.hydrawise.com/api/v2/graph Explorer: https://app.hydrawise.com/api/v2/graph/explore

Authentication: OAuth2 with the following scopes:

• manualoperation -- Manual zone start/stop
• zone_remote_control -- Zone configuration and control
• reporting -- Usage and performance data
• alerts -- Alarm and notification access
• contractor_controllers -- Multi-site management for landscape contractors

Architecture: Hydrawise migrated their entire web application to GraphQL in a 12-month refactoring effort, giving the v2 API significantly more capability than v1.5. The pydrawise Python library (used by Home Assistant) provides:

• get_controllers() -- List controllers
• get_zones(controller) -- List zones with configuration
• start_zone(zone) -- Manual zone start
• suspend_zone(zone, until) -- Suspend zone until date

Access model: Hydrawise "generally does not give open access to the GraphQL API." Commercial API access requires contacting support@hydrawise.com with a written request describing the intended use case. Hunter reserves the right to charge for API access in the future.

Water usage: The reporting scope suggests water usage data is available via GraphQL, but detailed query/mutation documentation is not publicly available. Home Assistant community members have requested flow sensor data exposure but it is not yet confirmed in the GraphQL schema.

Schedule push feasibility: Unknown. The v2 API likely supports schedule management given that the entire Hydrawise web app runs on it, but this capability is not publicly documented and would need to be confirmed during a commercial partnership discussion with Hunter.

---

4. Other Controller APIs

4.1 OpenSprinkler (Open Source)

Market position: Leading open-source irrigation controller. Available as hardware (OpenSprinkler 3.x, ~$150) and Raspberry Pi HAT (OSPi). Supports 8 zones standard, expandable to 200 zones with expansion boards.

API type: HTTP GET requests with JSON responses. All operations use GET (including writes), with parameters passed as query strings.

Base URL: http://<device-ip>/

Authentication: MD5 hash of device password, passed as pw parameter on every request. No tokens, no sessions, no OAuth.

Key endpoints for schedule integration:

| Endpoint | Purpose | Details | |----------|---------|---------| | /ja | Get all data | Combined response: controller vars, options, stations, status, programs | | /jp | Get programs | All program definitions with flags, days, start times, durations | | /js | Station status | Array of on/off states for all stations | | /jn | Station names | Names, master valve bits, sensor flags, groups | | /jl?start=&end=&type= | Logs | Records as [pid, sid, duration, end_time, flow] | | /cp?pw=&pid=&v=&name= | Create/modify program | Full CRUD: flags, days, start times, per-station durations | | /dp?pw=&pid= | Delete program | Delete by ID or all (pid=-1) | | /cm?pw=&sid=&en=&t= | Manual station run | Open/close station with duration in seconds | | /cr?pw=&t=[...] | Run-once program | Per-station durations array for immediate execution | | /mp?pw=&pid=&uwt=&qo= | Start program | Run existing program with weather adjust and queue options |

Program data structure: The /cp endpoint accepts a program body encoded as a JSON array:

v=[flags, days0, days1, [start_time_0, start_time_1, start_time_2, start_time_3], [dur_0, dur_1, ..., dur_n]]

• flags: Bitmask for enabled, weather adjustment, odd/even/interval mode.
• days0: Weekly bitmask where bits 0-6 = Monday through Sunday (e.g., days0=127 = daily; days0=21 = Mon/Wed/Fri).
• days1: Used for interval scheduling (interval count and starting day).
• start_times: Up to 4 start times per program, encoded as minutes from midnight (e.g., 360 = 6:00 AM). Use -1 for disabled slots.
• durations: Array of per-station durations in seconds. Index corresponds to station number. Set to 0 for stations not in this program.

Run-once programs: The /cr endpoint accepts a comma-separated array of durations for all stations and executes immediately:

/cr?pw=xxx&t=[600,900,0,1200,0,0,0,0]

This is ideal for SimplyScapes: compute per-zone runtimes from the QWEL formula and push them as a run-once program.

Queue options: Multiple programs can be queued:

• qo=0: Append to end of queue
• qo=1: Insert at front of queue
• qo=2: Replace current queue

Flow sensor support:

• Configured in Options > Weather and Sensors.
• Flow pulses counted during each station run and logged in /jl.
• Per-station flow is tracked when stations run sequentially (parallel station runs aggregate flow, making per-station attribution impossible).
• Flow rate = (pulse_count x pulse_volume) / duration.
• All API values returned in SI units regardless of display settings.

Weather adjustment:

• Zimmerman method: adjusts runtime % based on temperature, humidity, precipitation.
• Can be enabled/disabled per-program.
• Per-program, not per-station -- all stations in a program get the same adjustment.
• Recent firmware (2.3.3/174) added Multi-Day Average Watering Levels for interval-based programs.

SimplyScapes integration path: OpenSprinkler is the ideal target for full schedule control. The API supports everything needed: create programs with per-station durations and specific days, modify programs as conditions change, push run-once schedules for immediate execution. The local-only nature means SimplyScapes must either run an on-premise agent or the user must configure port forwarding / VPN access.

4.2 RainMachine

Market position: Mid-market smart controller with strong ET-based scheduling built into the firmware. Available as RainMachine Touch HD-12/16 and RainMachine Pro. Uses local weather data to compute ETo on-device. Smaller market share than Rachio but technically sophisticated.

API type: REST API with JSON payloads. Available on both local network and via RainMachine cloud remote access service.

Local base URL: https://<device-ip>:8080/api/4/ (HTTPS) or http://<device-ip>:8081/api/4/ (HTTP)

Remote base URL: https://my.rainmachine.com/ (cloud relay)

Authentication:

Local access:

POST /api/4/auth/login
Body: {"pwd": "device-password", "remember": true}
Response: {"access_token": "...", "expires_in": ...}

All subsequent requests append ?access_token=<token>.

Remote access:

POST https://my.rainmachine.com/login/auth
Body: {"user": {"email": "...", "pwd": "..."}}

Key endpoints:

| Endpoint | Method | Purpose | |----------|--------|---------| | /api/4/zone | GET | List all zones with properties | | /api/4/zone/:id | GET | Single zone details | | /api/4/zone/:id/start/:seconds | POST | Start zone for N seconds | | /api/4/zone/:id/stop | POST | Stop zone | | /api/4/zone/properties | GET | Advanced zone properties | | /api/4/zone/properties | POST | Set zone properties | | /api/4/program | GET | List all programs | | /api/4/program/:id | GET | Single program details | | /api/4/program | POST | Create new program | | /api/4/program/:id | POST | Modify existing program | | /api/4/program/:id/start | POST | Start program | | /api/4/program/:id/stop | POST | Stop program | | /api/4/watering/queue | GET | Current watering queue | | /api/4/watering/past/:date/:ndays | GET | Past watering history | | /api/4/watering/details | GET | Detailed watering data with flow | | /api/4/dailystats | GET | Daily water usage statistics | | /api/4/restrictions/hourly | GET/POST | Hourly watering restrictions | | /api/4/restrictions/global | GET/POST | Global restrictions (e.g., odd/even day) | | /api/4/parser | GET | Weather data parser info (ETo sources) | | /api/4/mixer/:date/:ndays | GET | Mixed weather data used for scheduling |

Program creation: Programs include:

• Zone assignments with per-zone durations in minutes.
• Frequency: daily, specific days of week, interval.
• Start time.
• Weather adjustment mode: "Auto" (ET-adjusted) or "Fixed" (user-specified durations).
• Active state.

Watering restrictions:

POST /api/4/restrictions/hourly
Body: {"uid": 1, "dayStartMin": 0, "minDuration": 480, "weekDays": "1111111"}

Weekdays encoded as 7-character string (MTWTFSS), where 1 = enabled.

Flow sensor data:

• flowclicks field in watering log records.
• system.flowSensorWateringClicks tracks total clicks during active watering.
• Flow data available per-zone when zones run sequentially.

ET data: RainMachine computes ETo on-device using its weather parser system, which can ingest data from Weather Underground, NOAA, Davis Vantage, and other local weather sources. The /api/4/parser endpoint exposes which weather services are active and their data. Users can even push local weather data to the device via the API for hyper-local ETo computation.

SimplyScapes integration assessment: RainMachine is a strong candidate because its API supports full schedule CRUD, zone property management, and flow sensor readback. The device-local ETo computation means it can function independently with accurate scheduling even without SimplyScapes. The integration model would be to push DU-corrected runtimes as program modifications while letting RainMachine handle weather-based adjustments in "Auto" mode.

4.3 Rain Bird (Residential + Commercial)

Residential (LNK2 WiFi module): No public API. The pyrainbird community library reverse-engineers the proprietary Serial Interface Protocol (SIP), a binary protocol communicated over HTTP directly to the LNK2 module on the local network. Limited to one concurrent connection, no schedule creation capability, and likely to break with firmware updates. Not viable for production use.

Commercial (IQ4 Central Control):

IQ4 is Rain Bird's cloud-based central control platform for commercial irrigation management. It supports API integration with Building Management Systems (BMS).

Architecture:

• Web interface: https://iq4.rainbird.com
• API server: https://iq4server.rainbird.com
• IQ4 syncs irrigation programs daily to field controllers.
• Log retrieval from controllers occurs one or more times daily.

API capabilities (data retrieval focused):

• Flow data by site over configurable time periods.
• Alarm data (pipe breaks, stuck valves, flow anomalies).
• Schedule and programming data.
• Controller status.

Access requirements:

• API subscription must be purchased from Rain Bird's subscriptions page.
• API users must have the Owner role in the IQ4 account.
• Companies must authorize third-party API access.
• Oriented toward landscape management companies integrating with their own business systems for work orders, reports, and compliance.

Schedule push capability: The IQ4 API documentation emphasizes data retrieval ("BMS or other third-party systems request specific data from IQ4 via API calls"). There is no clear evidence that the API supports pushing or creating schedules programmatically. IQ4 itself manages scheduling; the API appears to be read-only for schedule data.

4.4 Orbit B-hyve (Unofficial)

API architecture: Hybrid REST + WebSocket.

• REST API (https://api.orbitbhyve.com) for authentication and data retrieval.
• WebSocket (wss://api.orbitbhyve.com/v1/events) for real-time bidirectional communication with devices.

Authentication: Email/password credentials exchanged for a JWT token.

Community libraries:

• pybhyve (Python, asyncio): https://github.com/sebr/pybhyve
• bhyve-api (Node.js): https://github.com/billchurch/bhyve-api
• bhyve-mqtt (MQTT gateway): https://github.com/billchurch/bhyve-mqtt

Capabilities (reverse-engineered):

• Device discovery and configuration.
• Manual zone start/stop (via WebSocket commands).
• Smart watering soil moisture adjustment.
• Rain delay enable/disable.
• Program start.
• WebSocket for real-time status updates.

Limitations:

• Entirely reverse-engineered via man-in-the-middle traffic analysis of the B-hyve app.
• No official documentation, no developer program, no partnership path.
• Can break at any time when Orbit updates their app or backend.
• Not viable for production commercial use.

4.5 Weathermatic SmartLink

API type: REST API documented at Apiary (http://docs.smartlinknetworkv2.apiary.io/).

Authentication: API key + secret token issued upon developer registration with Weathermatic. Credentials set as environment variables: SLN_API_KEY and SLN_API_SECRET_KEY.

Target market: Commercial landscape management. SmartLink is Weathermatic's cloud-based irrigation management platform for professional landscapers managing multiple properties.

Capabilities:

• Remote monitoring and control of irrigation systems.
• Integration with business and accounting systems.
• Multi-site management.
• Flow monitoring.

Developer resources:

• Apiary documentation: http://docs.smartlinknetworkv2.apiary.io/
• Ruby gem: https://github.com/tgmerritt/smartlinknetwork

Limitations: Specific endpoint documentation is gated behind the Apiary docs and developer registration. The API appears oriented toward commercial landscape management workflows rather than individual controller schedule management.

---

5. Schedule Data Model

To abstract across controller APIs, SimplyScapes needs a universal schedule data model that can be projected onto each controller's API format.

5.1 Universal Schedule Representation

interface IrrigationSchedule {
  id: string;                          // SimplyScapes internal ID
  name: string;                        // Human-readable name
  controllerId: string;                // External controller reference
  controllerType: ControllerType;      // RACHIO | OPENSPRINKLER | RAINMACHINE | ...

  // Timing
  startTime: string;                   // HH:MM (24h format)
  startTimes?: string[];               // Multiple start times (OpenSprinkler supports up to 4)
  daysOfWeek: number[];                // 0=Sun, 1=Mon, ..., 6=Sat (Rachio convention)
  intervalDays?: number;               // Alternative: run every N days
  oddEven?: 'ODD' | 'EVEN';           // Alternative: odd/even day scheduling

  // Zone runtimes
  zones: ZoneRuntime[];
  totalDurationSeconds: number;        // Sum of all zone runtimes

  // Behavior
  cycleSoak: boolean;                  // Enable cycle/soak for runoff prevention
  cycleSoakMinutes?: number;           // Soak duration between cycles
  weatherAdjust: boolean;              // Allow weather-based skip/adjustment
  weatherSensitivity?: number;         // 0.0 (never skip) to 1.0 (aggressive skip)
  seasonalAdjustment: number;          // -1.0 to 1.0 (percentage adjustment)

  // Restrictions
  startDate?: string;                  // ISO date: schedule active from
  endDate?: string;                    // ISO date: schedule active until
  restrictedHours?: RestrictedHour[];  // Municipal watering restriction windows

  // Metadata
  source: 'DESIGN' | 'MANUAL';        // How was this schedule computed?
  computedFrom?: {
    eto: number;                       // Reference ETo used (in/day)
    du: number;                        // Design DU applied
    pr: number;                        // Design PR applied (in/hr)
    pf: number;                        // Plant factor used
  };
}

interface ZoneRuntime {
  zoneId: string;                      // External zone reference on controller
  zoneNumber: number;                  // Physical zone number
  durationSeconds: number;             // Computed runtime
  sortOrder: number;                   // Execution order

  // Optional per-zone metadata
  plantFactor?: number;                // PF used for this zone's calculation
  distributionUniformity?: number;     // DU from design
  precipitationRate?: number;          // PR from design (in/hr)
}

interface RestrictedHour {
  startMinuteOfDay: number;            // Minutes from midnight
  durationMinutes: number;             // Length of restriction window
  daysOfWeek: boolean[];               // Which days restriction applies
}

5.2 Controller Projection Map

| Field | Rachio | OpenSprinkler | RainMachine | |-------|--------|---------------|-------------| | startTime | In app (not settable via API) | start_times[] (minutes from midnight) | Program start time | | daysOfWeek | scheduleJobTypes: ["DAY_OF_WEEK_N"] | days0 bitmask (bits 0-6 = Mon-Sun) | Weekday string "1010100" | | zone duration | zones[].duration (seconds) | durations[] (seconds, indexed by station) | Per-zone minutes in program | | cycleSoak | cycleSoak: true | Not natively supported | Supported in program settings | | weatherAdjust | weatherIntelligenceSensitivity | /uwt flag per program | Auto vs Fixed mode | | seasonalAdjust | seasonalAdjustment (-1 to 1) | Weather adjustment method (Zimmerman) | Auto adjustment percentage | | restrictions | Rain delay (seconds) | Rain delay (hours) | /restrictions/hourly and /restrictions/global | | oddEven | scheduleJobTypes: ["ODD"/"EVEN"] | Flag in days0/days1 | Global restriction |

5.3 Day Encoding Conventions

Each controller uses a different convention for day-of-week encoding:

| Controller | Encoding | Monday Example | Mon/Wed/Fri | |-----------|----------|----------------|-------------| | Rachio | Array of strings | ["DAY_OF_WEEK_1"] | ["DAY_OF_WEEK_1","DAY_OF_WEEK_3","DAY_OF_WEEK_5"] | | OpenSprinkler | Bitmask (Mon=bit0) | days0=1 | days0=21 (binary: 0010101) | | RainMachine | 7-char string (MTWTFSS) | "1000000" | "1010100" |

SimplyScapes should store days as a boolean array [false, true, false, true, false, true, false] (Sun through Sat) and transform to each controller's encoding at push time.

---

6. Push vs Pull: Tradeoffs

6.1 Full Push (SimplyScapes computes and pushes schedules)

How it works: SimplyScapes runs the QWEL formula chain, computes per-zone runtimes, and pushes them to the controller as either modified schedules or run-once programs. The controller executes what it is told.

Advantages:

• SimplyScapes controls the irrigation science (DU, PR from design).
• Consistent scheduling logic across all controller brands.
• Can incorporate design-specific data that no controller has (head layout, zone geometry, plant mix).
• Enables unified reporting: what was scheduled vs. what ran.

Disadvantages:

• SimplyScapes must handle all weather intelligence (rain skip, freeze skip, wind delay, forecast integration) that controllers normally provide.
• If SimplyScapes backend has an outage, schedules stop updating.
• 3-hour max duration limit on Rachio zone runs.
• Real-time weather changes (unexpected rain) cannot be acted on instantly.
• User sees "manual" runs in controller app, not a recognizable schedule.

6.2 Full Pull (Controller manages its own scheduling)

How it works: SimplyScapes writes accurate zone properties (vegetation, soil, nozzle, shade, root depth, efficiency, MAD) to the controller and lets the controller's built-in algorithm (Flex Daily, SmartWatering, etc.) compute schedules.

Advantages:

• Controller handles weather intelligence, rain skip, freeze protection natively.
• No dependency on SimplyScapes backend availability for daily scheduling.
• Users see familiar schedules in their controller app.
• Leverages years of controller manufacturer algorithm tuning.

Disadvantages:

• Controllers do not know DU from the design -- they assume uniform application.
• Controllers use generic nozzle PR from type selection, not design-computed PR.
• No control over the specific scheduling algorithm.
• Inconsistent behavior across controller brands.

6.3 Hybrid Approach (Recommended)

How it works: SimplyScapes writes accurate zone properties AND applies runtime corrections, but lets the controller handle weather intelligence.

Implementation for Rachio:

1. Write zone properties (vegetation, soil, nozzle PR, shade, root depth) via PUT /public/zone -- this gives Flex Daily accurate inputs.
2. Compute the DU correction factor per zone: correction = 1/DU - 1. A zone with DU=0.65 gets correction = 0.538 (53.8% more water).
3. Apply the DU correction as a seasonal adjustment or by modifying the zone's inchesPerHour (nozzle PR) to reflect the design-computed effective PR (= design PR x DU) rather than the manufacturer's rated PR.
4. Let Flex Daily handle day-to-day weather adjustments.
5. Monitor via webhooks; re-sync if user overrides.

The nozzle PR trick: Instead of pushing runtime adjustments, SimplyScapes can set the zone's customNozzle.inchesPerHour to the design-computed effective PR (which already accounts for DU). Rachio's algorithm will then naturally compute longer runtimes for zones with lower DU because it sees a lower precipitation rate. This is the most elegant integration because it works within Rachio's existing algorithm rather than fighting it.

Implementation for OpenSprinkler:

1. Create a program via /cp with per-station durations computed from the full QWEL formula (ETo x PF / PR / DU).
2. Enable weather adjustment (uwt=1) for temperature/humidity/precip correction on top of the QWEL base calculation.
3. Update program durations periodically as ETo changes seasonally.
4. Use /cr for ad-hoc adjustments when conditions warrant.

Implementation for RainMachine:

1. Set zone properties via POST /api/4/zone/properties.
2. Create program in "Auto" mode for ET-based weather adjustment.
3. Set per-zone durations with DU correction baked in.
4. RainMachine applies its own ET-based daily adjustments on top.

---

7. Feedback Loop Potential

7.1 Data Available by Controller

| Data Type | Rachio | OpenSprinkler | RainMachine | Hydrawise | Rain Bird IQ4 | |-----------|--------|---------------|-------------|-----------|---------------| | Runtime (actual vs scheduled) | Yes (webhook + events API) | Yes (/jl logs) | Yes (/watering/past) | Yes (status API) | Yes (log retrieval) | | Flow volume (gallons/liters) | Yes (flowVolumeG in webhooks, requires flow meter) | Yes (pulse count in logs, requires flow sensor) | Yes (flowclicks in watering details, requires flow sensor) | No (flow sensor not exposed via API) | Yes (flow data per site) | | Weather data used | Yes (forecast API with ETo) | Yes (weather adjustment %) | Yes (/mixer endpoint with detailed weather) | No | No | | Skip/delay events | Yes (WEATHER_INTELLIGENCE_SKIP webhook) | Yes (log shows skipped programs) | Yes (restriction events in log) | Partial (status shows suspends) | Yes (alarm data) | | Error/fault detection | Yes (BROWNOUT_VALVE, flow anomaly webhooks) | Yes (current draw monitoring, flow anomaly) | Yes (flow sensor anomaly detection) | Yes (alerts scope in v2) | Yes (alarms: pipe break, stuck valve) |

7.2 Feedback Loop Architecture

SimplyScapes Design Engine
    |
    v
QWEL Formula Chain (ETo x PF / PR / DU)
    |
    v
Computed Schedule (per-zone runtimes)
    |
    +-- Push to Controller (API) ---------> Controller Executes
    |                                           |
    |                                           v
    |                                     Webhook / Poll
    |                                           |
    |                                           v
    +<-- Actual Execution Data <---------- Feedback Ingestion
    |    (runtime, flow volume,
    |     skip events, faults)
    |
    v
Variance Analysis
    |
    +-- Runtime variance > threshold? --> Alert user / adjust schedule
    +-- Flow variance > threshold?    --> Possible leak / clog / head issue
    +-- Consistent over-application?  --> Reduce PF or adjust DU model
    +-- Consistent under-application? --> Increase PF or check design

7.3 Specific Feedback Metrics

Predicted vs. Actual Runtime: Compare the scheduled duration (pushed by SimplyScapes) against actual execution duration (reported via webhook/API). Variance indicates controller modifications (cycle/soak splits, weather adjustments, manual overrides).

Predicted vs. Actual Volume (requires flow meter): If a zone is predicted to apply 125 gallons (based on PR x duration x area) but the flow meter reports 95 gallons, this indicates either:

• Lower actual PR than design spec (possible nozzle degradation).
• Valve not fully opening.
• Pressure issue reducing flow.

If actual volume exceeds prediction, possible leak or broken head.

Flow Rate Consistency: Track flow rate (volume / time) per zone over time. Declining flow rate suggests nozzle clogging or pressure drop. Increasing flow rate suggests broken head or lateral leak.

Skip Rate Analysis: If Weather Intelligence skips >50% of scheduled runs over a period, the base schedule may be too aggressive. SimplyScapes can auto-reduce the PF or increase the watering interval.

7.4 Flow Meter Requirements

Feedback loops with volumetric data require a flow meter on the irrigation mainline:

| Controller | Compatible Flow Meters | Cost | |-----------|----------------------|------| | Rachio | EveryDrop Wired/Wireless (WM-1000), third-party pulse meters | $75-120 | | OpenSprinkler | Any pulse-output flow meter (3/4" or 1") | $30-80 | | RainMachine | Pulse-output flow sensors via sensor input | $30-80 | | Hydrawise | Hunter HC Flow Meter (built into HC controllers) | Included in Pro-HC | | Rain Bird | Rain Bird FS series (for IQ4-connected controllers) | $100-200 |

---

8. Integration Priority Recommendation

8.1 Priority Ranking

| Priority | Controller | Rationale | |----------|-----------|-----------| | 1 | Rachio | Largest consumer smart controller market share. Public REST API. Already in SimplyScapes UI. Zone properties writable (vegetation, soil, nozzle, shade). Webhooks for feedback. Flow meter data available. 1,700 calls/day sufficient for residential. Main limitation (no schedule creation) workable via the "nozzle PR trick" + seasonal adjustment. | | 2 | OpenSprinkler | Full CRUD for programs. Open source (no vendor lock-in). Per-station duration control. Run-once programs for ad-hoc scheduling. Flow sensor support. Best API for precise schedule push. Smaller market but highly technical users = strong early adopters. | | 3 | RainMachine | Full CRUD for programs. Documented REST API with local and remote access. ET-based scheduling built in (complementary to QWEL). Flow sensor data. Zone properties writable. Good for users who want on-device intelligence plus design-derived DU corrections. | | 4 | Hunter Hydrawise | Strong professional market overlap. GraphQL API (v2) likely capable but gated behind commercial agreement. Business development task, not a technical one. Pursue partnership with Hunter Industries. | | 5 | Weathermatic SmartLink | Commercial landscape market. Documented REST API with developer registration. Low priority due to smaller addressable market for SimplyScapes residential focus. Higher priority if SimplyScapes expands to commercial landscape management. | | 6 | Rain Bird IQ4 | Only viable for commercial landscape market. Paid subscription. Data retrieval focused (not schedule push). Partner if commercial market becomes strategic. | | -- | Orbit B-hyve | Not recommended. No official API. Reverse-engineered and commercially unviable. | | -- | Rain Bird (residential) | Not recommended. No public API. Reverse-engineered SIP protocol is fragile and local-only. |

8.2 Implementation Phases

Phase 1: MVP (Rachio, Q2 2026)

• Implement Rachio API client with bearer-token auth.
• Sync zone properties from irrigation design to Rachio zones.
• Apply the "nozzle PR trick": set customNozzle.inchesPerHour to design-computed effective PR (PR x DU) so Flex Daily naturally compensates for non-uniform distribution.
• Register webhooks for zone completion events.
• Display scheduled vs. actual runtime in SimplyScapes UI.
• If flow meter present, display predicted vs. actual volume.
• Provide seasonal adjustment control: let user choose how aggressively SimplyScapes adjusts Rachio schedules based on QWEL calculations.

Phase 2: Full Schedule Control (OpenSprinkler + RainMachine, Q3 2026)

• Implement OpenSprinkler API client (local HTTP, MD5 auth).
• Full program creation from QWEL formula output.
• Implement RainMachine API client (local REST, token auth).
• Program creation with DU-corrected durations in "Auto" mode.
• For both: periodic schedule updates as ETo changes seasonally.
• Flow sensor integration for feedback loops.

Phase 3: Professional Market (Hydrawise, Q4 2026+)

• Contact Hunter Industries for commercial GraphQL API access.
• If approved, implement OAuth2 + GraphQL client.
• Target professional landscapers managing multiple Hydrawise sites.

Phase 4: Commercial Expansion (Weathermatic, Rain Bird IQ4, 2027+)

• Evaluate based on commercial market traction.
• Weathermatic SmartLink API integration for commercial properties.
• Rain Bird IQ4 API subscription for data integration (not schedule push).

8.3 Technical Architecture

The controller abstraction layer should implement a common interface:

interface IrrigationControllerAdapter {
  // Authentication
  connect(credentials: ControllerCredentials): Promise<void>;
  disconnect(): Promise<void>;

  // Zone management
  getZones(): Promise<Zone[]>;
  setZoneProperties(zoneId: string, props: ZoneProperties): Promise<void>;

  // Schedule management
  getSchedules(): Promise<Schedule[]>;
  createSchedule?(schedule: ScheduleInput): Promise<string>;  // Optional: not all support
  updateSchedule?(scheduleId: string, updates: ScheduleUpdates): Promise<void>;
  adjustRuntime(scheduleId: string, adjustmentPct: number): Promise<void>;

  // Execution
  runZones(runs: ZoneRun[]): Promise<void>;
  runSchedule(scheduleId: string): Promise<void>;
  stopAll(): Promise<void>;

  // Monitoring
  getStatus(): Promise<ControllerStatus>;
  getWateringHistory(start: Date, end: Date): Promise<WateringEvent[]>;
  registerWebhook?(url: string, events: string[]): Promise<void>;

  // Capabilities
  capabilities: {
    canCreateSchedules: boolean;
    canModifySchedules: boolean;
    canSetZoneProperties: boolean;
    hasFlowMeter: boolean;
    hasWebhooks: boolean;
    isCloudBased: boolean;
    maxZones: number;
    rateLimit?: { callsPerDay: number };
  };
}

Implementations:

• RachioAdapter -- Cloud REST, bearer token, webhook-driven
• OpenSprinklerAdapter -- Local HTTP, MD5 auth, polling
• RainMachineAdapter -- Local/cloud REST, token auth, polling
• HydrawiseAdapter -- Cloud GraphQL, OAuth2 (future)

---

9. Sources

| Source | URL | Accessed | |--------|-----|----------| | Rachio API Documentation | https://rachio.readme.io/ | 2026-03-01 | | Rachio Authentication | https://rachio.readme.io/reference/authentication | 2026-03-01 | | Rachio Data Objects | https://rachio.readme.io/reference/data-objects | 2026-03-01 | | Rachio Webhook Types | https://rachio.readme.io/reference/sample-webhook-json | 2026-03-01 | | Rachio Postman Collection | https://www.postman.com/rachio/rachio-public-workspace/documentation/y85j8lw/rachio-public-api-v2-0 | 2026-03-01 | | Rachio Support: Public API | https://support.rachio.com/en_us/public-api-documentation-S1UydL1Fv | 2026-03-01 | | Rachio Support: Flex Daily FAQ | https://support.rachio.com/en_us/flex-daily-schedules-faq-BJ2YPIJKw | 2026-03-01 | | Rachio Community: ET Calculations | https://community.rachio.com/t/evapotranspiration-et-calculations/36670 | 2026-03-01 | | Rachio Community: API Schedule Use | https://community.rachio.com/t/use-api-to-customize-the-start-and-end-of-watering/39060 | 2026-03-01 | | Rachio Home Assistant Integration | https://www.home-assistant.io/integrations/rachio/ | 2026-03-01 | | Hydrawise API Info (Hunter) | https://www.hunterirrigation.com/support/hydrawise-api-information | 2026-03-01 | | Hydrawise REST API v1.5 (PDF) | https://www.hunterirrigation.com/sites/default/files/2024-03/Hydrawise%20REST%20API.pdf | 2026-03-01 | | Hydrawise GraphQL Explorer | https://app.hydrawise.com/api/v2/graph/explore | 2026-03-01 | | pydrawise (Python GraphQL client) | https://github.com/dknowles2/pydrawise | 2026-03-01 | | Hydrawise Rate Limiting (Hunter) | https://www.hunterirrigation.com/en-metric/support/hydrawise-rate-limiting-too-many-requests | 2026-03-01 | | Hydrawise Home Assistant Integration | https://www.home-assistant.io/integrations/hydrawise/ | 2026-03-01 | | Rain Bird IQ4 BMS Integration | https://www.rainbird.com/professionals/iq4-product-development-update-new-bms-Integration | 2026-03-01 | | Rain Bird IQ4 API Brochure (PDF) | https://www.rainbird.com/sites/default/files/media/documents/2023-10/iq4_api_brochure.pdf | 2026-03-01 | | pyrainbird (Rain Bird Python) | https://github.com/allenporter/pyrainbird | 2026-03-01 | | Rain Bird Home Assistant Integration | https://www.home-assistant.io/integrations/rainbird/ | 2026-03-01 | | Orbit B-hyve Home Assistant | https://github.com/sebr/bhyve-home-assistant | 2026-03-01 | | pybhyve (Python B-hyve client) | https://github.com/sebr/pybhyve | 2026-03-01 | | bhyve-api (Node.js B-hyve client) | https://github.com/billchurch/bhyve-api | 2026-03-01 | | OpenSprinkler API Reference | https://opensprinkler.github.io/OpenSprinkler-Firmware/2.2.1/221_4_api/ | 2026-03-01 | | OpenSprinkler Firmware (GitHub) | https://github.com/OpenSprinkler/OpenSprinkler-Firmware | 2026-03-01 | | OpenSprinkler Forums: Flow Sensor | https://opensprinkler.com/forums/topic/flow-meter-monitoringlogging/ | 2026-03-01 | | RainMachine REST API Guide | https://support.rainmachine.com/hc/en-us/articles/228022248 | 2026-03-01 | | RainMachine API Documentation (Apiary) | https://rainmachine.docs.apiary.io/ | 2026-03-01 | | RainMachine Developer Resources (GitHub) | https://github.com/sprinkler/rainmachine-developer-resources | 2026-03-01 | | RainMachine Flow Sensor API | https://support.rainmachine.com/hc/en-us/community/posts/360015731414 | 2026-03-01 | | RainMachine Watering Log Format | https://support.rainmachine.com/hc/en-us/articles/228620787 | 2026-03-01 | | RainMachine Home Assistant Integration | https://www.home-assistant.io/integrations/rainmachine/ | 2026-03-01 | | Weathermatic SmartLink API (Apiary) | http://docs.smartlinknetworkv2.apiary.io/ | 2026-03-01 | | Weathermatic SmartLink Ruby Gem | https://github.com/tgmerritt/smartlinknetwork | 2026-03-01 | | HAsmartirrigation (HA ET Calculator) | https://github.com/jeroenterheerdt/HAsmartirrigation | 2026-03-01 | | FAO-56 Penman-Monteith Reference | https://www.fao.org/4/x0490e/x0490e08.htm | 2026-03-01 | | SS-RR-2026-002 Controller Integration | ../../../plant-specific-drip-irrigation-intelligence/supporting/controller-integration.md | 2026-03-01 |

Patent Landscape & Freedom-to-Operate Analysis: Automated Irrigation Scheduling

Parent Research: SS-RP-2026-002 Automated Turf Irrigation Scheduling from Design-Time Intelligence ClickUp: Automated Turf Irrigation Scheduling Date: 2026-03-01 Status: Draft -- Supporting Paper Disclaimer: This analysis is NOT legal advice. It is a preliminary technical assessment intended to identify areas for further review by qualified patent counsel.

---

Executive Summary

This freedom-to-operate (FTO) analysis evaluates the patent landscape surrounding SimplyScapes' planned feature: automated turf irrigation scheduling using design-computed Distribution Uniformity (DU) and Precipitation Rate (PR). The core innovation is that DU and PR are derived from the irrigation design geometry itself (head placement, arc, radius, spacing) rather than from physical field tests, eliminating the most expensive step in professional irrigation auditing.

Key Finding: SimplyScapes' design-time intelligence approach operates in a fundamentally different architectural space from the existing patent landscape. Every SmartRain patent requires physical hardware (controllers, flow sensors, moisture sensors) as mandatory claim elements. SimplyScapes' pure software approach -- computing schedules from design geometry without physical sensors or controllers -- does not infringe any SmartRain independent claim as currently written. However, three risk areas warrant monitoring and specific design-around strategies as the platform evolves.

Overall Risk Assessment: LOW (with caution areas noted)

---

1. SmartRain Patent Portfolio Analysis

Smart Rain Systems LLC (inventor Rudy Lars Larsen, Salt Lake City, UT) holds the following granted patents and pending applications. For each, we extract the independent claims, identify mandatory hardware elements, and assess overlap with the SimplyScapes design-time intelligence approach.

1.1 US9,307,706B2 -- Irrigation Management

| Field | Value | |-------|-------| | Filed | May 21, 2013 (priority: May 21, 2012) | | Granted | April 12, 2016 | | Expires | ~May 22, 2034 | | Assignee | Smart Rain Systems LLC | | CPC | A01G25/16, A01G25/165, G05B19/04, G05B19/048 |

Independent Claim 1 requires ALL of the following elements:

• Visiting a property and identifying characteristics affecting water usage
• Developing an irrigation management plan using those characteristics
• Determining value via a guaranteed rate and cost savings calculation (business method)
• Communicatively connecting a controller controlling water application with a central computer at a remote location
• The central computer connected to a plurality of second controllers at a plurality of second properties
• Implementing the plan from the central computer
• Continually monitoring water usage using water usage data communicated to the central computer from the controller
• Diagnosing a fault using the water usage data
• Dispatching a technician to repair the fault

Independent Claim 13 requires:

• A plurality of controllers, each controlling water application by an irrigation system
• A central computer remote from and in communication with each controller
• Central computer configured to implement individualized plans based on on-site visit characteristics
• Guaranteed ROI within a predefined period
• Detecting faults using water usage data from controllers
• Running user-defined tests to diagnose faults
• Notifying and dispatching technicians
• Disabling/enabling stations in response to faults
• Fee determination based on water cost savings allocation

Hardware Requirements: Physical controllers, central computer, flow-based monitoring, physical site visits, technician dispatch infrastructure.

Overlap Assessment: NONE. SimplyScapes does not operate physical controllers, does not monitor real-time water usage via flow sensors, does not perform fault detection, and does not dispatch technicians. The business-method claim elements (guaranteed ROI, cost savings allocation) are also absent. SimplyScapes generates schedules from design data, not from physical monitoring.

---

1.2 US10,660,279B2 -- Irrigation Management (Continuation)

| Field | Value | |-------|-------| | Filed | October 26, 2015 (priority: May 21, 2012) | | Granted | May 26, 2020 | | Expires | ~2034 (based on priority) | | Assignee | Smart Rain Systems LLC | | CPC | A01G25/16, A01G25/165, G05B19/04, G05B19/048 |

Independent Claim 1 requires ALL of the following:

• Managing an irrigation system comprising a master valve, at least one flow sensor, and at least one moisture sensor
• Installing the master valve between main water line and property
• Installing the flow sensor at the master valve, in wired/wireless communication with controller
• Installing the moisture sensor, in wired/wireless communication with controller
• Communicatively connecting a controller with a central computer at remote location
• Communicatively connecting at least one mobile device with the central computer
• Monitoring effectiveness using water usage data from either the flow sensor or the moisture sensor
• Determining a fault based on water usage data
• Assigning a time frame for fault response based on weather forecast
• Calculating water cost savings and charging based on those savings
• Tracking adjusted plans vs. original plans for cost effect

Independent Claim 8 additionally requires:

• Flow sensor and moisture sensor (same hardware)
• Comparing property water usage data against water authority data
• Calibrating the flow sensor when data differs by threshold

Hardware Requirements: Master valve, flow sensor(s), moisture sensor(s), controller, central computer, mobile device. Physical installation required.

Overlap Assessment: NONE for current design-time intelligence. The claims are deeply coupled to physical sensor hardware (flow sensors, moisture sensors, master valves) that must be physically installed. SimplyScapes computes schedules from design geometry without any of these physical components.

RISK AREA 1 (see Section 2.1): The "cost savings calculations" element requires further analysis if SimplyScapes estimates water usage savings from schedule optimization.

---

1.3 US11,185,024B2 -- Irrigation System Map Integration

| Field | Value | |-------|-------| | Filed | April 26, 2019 | | Granted | November 30, 2021 | | Expires | ~2039 | | Assignee | Smart Rain Systems LLC | | CPC | G05D7/0664, A01G25/165, A01G25/167 |

Independent Claim 1 requires:

• An irrigation system comprising flow sensors, moisture sensors, and a plurality of valves
• An irrigation management server (IMS) configured to:
  • Receive irrigation system information including location of flow sensors and location of moisture sensors
  • Retrieve GPS location of a user seeking access
  • Retrieve a third party map of the GPS location
  • Overlay irrigation system information onto the third party map
  • Display location of flow sensors and moisture sensors over the map
  • Display perimeter lines of zones and interactive secondary menus with selectable commands (soil evaporation rate, moisture content, watering times)

Independent Claims 11 and 20 have substantially similar requirements, all requiring GPS user location retrieval, flow sensors, moisture sensors, and map overlay of physical sensor locations.

Hardware Requirements: Flow sensors, moisture sensors, valves, GPS positioning of user, third-party map integration displaying physical sensor locations.

Overlap Assessment: NONE. User has previously confirmed this patent is not a concern because SimplyScapes does not use GPS positioning of users or display physical sensor locations on maps. SimplyScapes' design view shows head placement geometry from the design, not real-time sensor data overlaid via GPS.

---

1.4 US11,684,029B2 -- Landscaper Integration (Schedule Adjustment for Landscape Events)

| Field | Value | |-------|-------| | Filed | February 7, 2022 (priority: January 3, 2018) | | Granted | June 13, 2023 | | Expires | ~2038 | | Assignee | Smart Rain Systems LLC | | CPC | A01G25/165, G05B2219/2625, Y02A40/22 |

Independent Claim 1 (full text extracted) requires ALL of:

• An irrigation manager interface on a first remote device with a task menu for inputting customized landscape tasks (type of event + zones affected)
• A user interface on a second remote device with selections including:
  • Predetermined landscape events: lawn mowing service, fertilization application, sod installation, shrub installation, tree installation, flower installation
  • Customized landscape tasks
  • Date of the landscape event
• A processor programmed with the predetermined landscape events, each comprising a predetermined duration to water or not water based on type
• The processor configured to:
  • Receive signals from the first remote device for event type and date
  • Process the event with the predetermined duration
  • Signal a controller to alter a watering schedule
  • Receive a signal of completion after the predetermined duration
  • Signal the controller that the event is completed
• A controller connected to the processor that controls application of water for a specified location

Independent Claims 14 and 20 have substantially similar structure, all requiring:

• First remote device (irrigation manager interface)
• Second remote device (user interface)
• Processor programmed with landscape events
• At least one controller connected to the processor that controls water application

Hardware Requirements: Two remote devices (irrigation manager + user), processor, physical irrigation controller(s) that receive signals and control water application.

Overlap Assessment: LOW-MODERATE -- see Risk Area 2 (Section 2.2) for detailed analysis. The claim requires a physical controller that receives signals and controls water application. SimplyScapes generates schedule recommendations from design data but does not directly control physical controllers (though Rachio integration exists in the UI). The "landscape event" concept in this patent is specifically about real-time interruptions to an active watering schedule (mow today, hold watering for 2 days), not about adjusting design parameters that regenerate a schedule.

---

1.5 US11,839,184B2 -- Artificially Intelligent Irrigation System

| Field | Value | |-------|-------| | Filed | September 1, 2022 (priority: June 10, 2019) | | Granted | December 12, 2023 | | Expires | ~2040 | | Assignee | Smart Rain Systems LLC | | CPC | A01G25/167, G01N33/246, G01W1/10, G01W1/14, G06Q50/02 |

Independent Claim 1 (full text extracted from freepatentsonline.com):

A system for predicting soil moisture at a first property based on a triggering event, and managing an irrigation system at the first property in response to the triggering event the system comprising: a processor in communication with a prediction system and a database; and a storage medium storing instructions that, when executed, configure the processor to: establish a baseline watering schedule comprising one or more baseline watering events; receive at least one of weather data and water flow data; filter the at least one of weather data and water flow data to determine if a potential triggering event has occurred; where the potential triggering event has occurred, comparing at least one feature of the potential triggering event to at least one model feature of stored historical triggering event models to determine a correlation value between the potential triggering event and stored historical triggering events, the at least one model feature including at least one of type, location, date, time, and amount; where the correlation value is above a predetermined threshold, making a soil moisture prediction for the first property based on the at least one stored historical triggering event model; and where soil moisture prediction for the first property will increase within a predetermined amount of time of a baseline watering event, delaying the baseline watering event.

Independent Claim 11:

A system for predicting soil moisture at a first property based on a precipitation event at a location remote from the first property, and managing an irrigation system at the first property in response to the precipitation event at the location remote from the first property, the system comprising: a processor in communication with a prediction system and a database; and a storage medium storing instructions that, when executed, configure the processor to: establish a baseline watering schedule comprising one or more baseline watering events; receive weather data for the location remote from the first property; filter the weather data for the location remote from the first property to determine if the precipitation event has occurred; where the precipitation event has occurred, generating a predictive soil moisture model based on at least one stored historical precipitation event model, the at least one stored historical precipitation event model comprising model features; and modifying the baseline watering schedule in response to the predictive soil moisture model.

Independent Claim 15:

A system for predicting soil moisture at a first property based on a triggering event, and managing an irrigation system at the first property in response to the triggering event the system comprising: a processor in communication with a prediction system and a database; and a storage medium storing instructions that, when executed, configure the processor to: receive at least one of weather data, rain data, and water flow data; filter the at least one of the weather data, the rain data, and the water flow data to determine if a potential triggering event has occurred; where the potential triggering event has occurred, comparing at least one feature of the potential triggering event to at least one model feature of stored historical triggering event models to determine a correlation value between the potential triggering event and stored historical triggering events, the at least one model feature including at least one of type, location, date, time, and amount; where the correlation value is above a predetermined threshold, making a soil moisture prediction for the first property based on the at least one stored historical triggering event model; and where soil moisture prediction for the first property will increase within a predetermined amount of time of a baseline watering event, delaying a baseline watering event of a predetermined baseline watering schedule.

Hardware Requirements Analysis -- CRITICAL:

Unlike the other SmartRain patents, the independent claims of US11,839,184 do NOT explicitly require physical sensors (flow sensors, moisture sensors) as mandatory claim elements. The claims recite:

• A processor in communication with a prediction system and a database
• A storage medium storing instructions
• Receiving "weather data" and/or "water flow data" and/or "rain data"
• Comparing triggering events to historical models
• Making soil moisture predictions
• Modifying/delaying baseline watering schedules

However, the claims are specifically directed at:

1. Predicting soil moisture (not computing irrigation need from ET)
2. Event-driven triggering (precipitation events, flow data events)
3. Historical model correlation (comparing current events to stored historical event models)
4. Delaying baseline watering events based on predicted moisture increase

Overlap Assessment: LOW-MODERATE -- see Risk Area 3 (Section 2.3) for detailed analysis. SimplyScapes' design-time approach computes runtime from ET formulas (ETo x PF / (PR x DU)), which is a deterministic calculation, not a predictive soil moisture model based on historical event correlation. However, if SimplyScapes adds weather forecast integration to predictively delay scheduled irrigations, the architecture could potentially implicate Claims 11 and 15.

---

1.6 US20210176931A1 -- Soil Sensor Grid (Pending Application)

| Field | Value | |-------|-------| | Filed | February 25, 2021 (priority: September 23, 2016) | | Status | Published application (pending) | | Assignee | Smart Rain Systems LLC | | CPC | A01G25/167, G05B19/042 |

Independent Claim 1 requires:

• An irrigation system comprising at least one first sprinkler
• At least one first moisture sensor and at least one second moisture sensor in communication with each other
• A moisture sensor grid comprising the moisture sensors providing data to a relay device
• At least one controller in communication with the relay device
• A cloud-based platform in communication with the controller
• Map overlay with satellite image showing sensor grid, sprinkler locations, and moisture data
• Interactive secondary menus with selectable commands

Independent Claims 6 and 11 similarly require physical moisture sensor grids, controllers, cloud platforms, and map overlays.

Hardware Requirements: Physical moisture sensor grid, sprinklers, controllers, relay devices, cloud platform.

Overlap Assessment: NONE. SimplyScapes does not use physical moisture sensor grids or relay devices. This patent is entirely about in-ground sensor hardware and visualization.

---

1.7 Additional SmartRain Patents (from smartrain.net/patent/)

| Patent | Title | Risk | |--------|-------|------| | US10,932,424 | Smart Rain Interactive Maps | Same family as US11,185,024; same GPS/sensor overlay approach. No overlap. | | US11,240,976 | Remote Irrigation Control System | Remote control of physical controllers. Requires controller hardware. No overlap. | | USD942,957 | Irrigation Controller Housing | Design patent for physical hardware appearance. No overlap. |

---

2. Risk Area Deep Dives

2.1 Risk Area 1: Cost Savings Calculations (US10,660,279B2)

Question: Do "cost savings calculations" require actual metered flow data, or could estimated water usage derived from schedules overlap?

Claim Analysis:

US10,660,279B2 Claim 1 recites cost savings in a very specific context:

• "calculating a water cost savings of irrigation water costs"
• "charging a cost of the irrigation management services based on the water cost savings"
• "tracking an adjusted irrigation management plan against an original developed irrigation management plan"
• The savings are calculated from "water usage data from either the at least one flow sensor or the at least one moisture sensor"

Key Distinction: The cost savings in this claim are:

1. Derived from actual measured data (flow sensor or moisture sensor data)
2. Used to charge fees for an irrigation management service
3. Part of a tracking system that compares adjusted vs. original plans with cost effect analysis
4. Specifically track "client-directed watering" as a separate cost item

SimplyScapes' Approach:

• SimplyScapes estimates water usage from schedule calculations (PR x runtime x area), not from metered flow data
• SimplyScapes does not charge based on water savings
• SimplyScapes may show estimated water budget vs. actual schedule for MWELO compliance

Risk Assessment: LOW. The claim requires physical flow/moisture sensors as the data source and ties cost savings to a service fee structure. Estimating theoretical water usage from design parameters (PR, area, runtime) to show compliance or efficiency metrics is categorically different from measuring actual flow data to calculate and charge for savings. The claim cannot be infringed without the physical sensor hardware.

Design-Around Strategy:

• Label any water usage estimates as "estimated from design parameters" not "measured savings"
• Do not tie water usage estimates to a fee or billing calculation
• Source all usage calculations from design geometry (PR x time x area), never from metered flow
• If future metered integration is added, ensure it is a separate feature path clearly distinct from the fee-based savings model in the patent

---

2.2 Risk Area 2: Landscape Event Schedule Adjustment (US11,684,029B2)

Question: Does "schedule adjustment for landscape events" overlap with SimplyScapes adjusting schedules based on design changes?

Claim Analysis:

US11,684,029B2 Claim 1 covers a very specific workflow:

1. An irrigation manager inputs customized landscape tasks via a first remote device
2. A user selects from predetermined landscape events (mowing, fertilization, sod install, shrub install, tree install, flower install) via a second remote device
3. Each event has a predetermined duration to water or not water
4. The processor receives the event signal, processes it, and signals a controller to alter the schedule
5. After the predetermined duration expires, the processor signals the controller that the event is completed (auto-revert)

Critical Distinctions:

The patent covers real-time operational interruptions to an active watering schedule:

• "A landscape event has occurred" (past tense -- something happened on site)
• The system temporarily suspends or modifies watering in response
• After a predetermined duration, the system automatically reverts

SimplyScapes' design change workflow is fundamentally different:

• A designer modifies the irrigation design (adds heads, changes spacing, adjusts plant types)
• The system recomputes DU and PR from the new geometry
• The schedule is regenerated from the updated design parameters
• There is no "event duration" or "auto-revert" -- the new design IS the new baseline

Additional Claim Limitations Not Present in SimplyScapes:

• Two separate remote devices (manager interface + user interface)
• Physical controller that receives signals and controls water application
• Signal of completion after predetermined duration
• Predetermined duration per event type

Risk Assessment: LOW. SimplyScapes' design-time recomputation is architecturally distinct from SmartRain's operational event-driven schedule interruption. SimplyScapes recomputes the entire schedule from first principles when design parameters change. SmartRain temporarily overrides an existing schedule for a fixed duration and then reverts.

Design-Around Strategy:

• Frame all schedule changes as "design-driven recomputation" not "event-driven adjustment"
• When a user changes plant types or adds landscaping in the design, recompute the entire schedule from design parameters (DU, PR, ETo, PF) rather than applying a temporary overlay
• Do not implement predetermined durations for "landscape events" that auto-revert
• If implementing a "new sod" or "new planting" establishment mode, derive the modified schedule from the plant database establishment watering requirements (agronomic data), not from a predetermined duration per event type
• Ensure the schedule change is permanent until the next design change, not a temporary override

Caution: If SimplyScapes ever adds an "event" system where a user can say "I just laid sod" and the system temporarily increases watering for a preset period then auto-reverts, that would move closer to the claim scope. The recommended approach is to let the user update the design (change the zone to "establishment mode" in the plant database), which regenerates the schedule from first principles -- no predetermined duration, no auto-revert, and no event-driven override.

---

2.3 Risk Area 3: AI-Predicted Soil Moisture (US11,839,184B2)

Question: Does "AI-predicted soil moisture" overlap if SimplyScapes later adds predictive scheduling using weather forecasts?

Claim Analysis:

This is the most nuanced risk area because the independent claims do NOT explicitly require physical sensors. However, the claims are narrowly directed at a specific technical approach:

What the claims require:

1. A system for predicting soil moisture (not computing irrigation need)
2. Based on a triggering event (precipitation event or flow data event)
3. Receiving weather data and/or water flow data (Claim 1 says "at least one of weather data and water flow data"; Claim 15 adds "rain data")
4. Filtering the data to determine if a triggering event occurred
5. Comparing the triggering event to stored historical triggering event models
6. Determining a correlation value between current and historical events
7. Where correlation exceeds threshold, making a soil moisture prediction from historical models
8. Delaying a baseline watering event when predicted moisture will increase

What SimplyScapes does (current):

• Computes irrigation need deterministically: ETo x PF / (PR x DU) = runtime
• Uses published ETo data (historical averages or current reference ET)
• No soil moisture prediction
• No event-based triggering
• No historical model correlation

What SimplyScapes might do (future weather forecast integration):

• Receive weather forecast data
• If rain is forecast, skip or delay the next irrigation event
• This is a simple threshold check, not a historical model correlation

Infringement Analysis for Future Weather Integration:

Even with weather forecast integration, SimplyScapes would likely NOT meet all claim limitations because:

1. No soil moisture prediction: SimplyScapes would skip watering when rain is forecast, not predict what soil moisture will be. The output is a binary decision (water/skip), not a moisture prediction model.

2. No historical triggering event models: SimplyScapes would compare forecast rainfall amount against a threshold (e.g., "if forecast rain > 0.25 inches, skip"), not correlate the current event against stored historical precipitation event models to find similar past events and predict outcomes.

3. No correlation value computation: The claims require computing a correlation value between the current triggering event and historical events, using model features (type, location, date, time, amount). A simple "rain forecast > threshold" check does not involve correlation with historical events.

4. Different data flow: SimplyScapes uses forecast (future-looking) data to make proactive scheduling decisions. The patent uses observed or detected events (past/current) to predict future soil moisture effects by correlating with historical event outcomes.

However, Claim 11 is broader -- it requires:

• Receiving weather data for a remote location
• Filtering for a precipitation event
• Generating a predictive soil moisture model from stored historical precipitation event models
• Modifying the baseline schedule in response

If SimplyScapes builds a system that (a) monitors weather data, (b) detects precipitation events, (c) uses historical models to predict how that precipitation will affect soil moisture, and (d) modifies schedules accordingly -- that could implicate Claim 11.

Risk Assessment: LOW for current approach, MODERATE for advanced predictive features.

Design-Around Strategy:

• For weather-based schedule adjustment, use a deterministic threshold approach: "If forecast rainfall exceeds X inches in the next Y hours, reduce/skip the next irrigation by Z minutes." This is a simple conditional, not a historical model correlation.
• Do NOT build a system that stores historical precipitation event models and correlates current events against them to predict soil moisture outcomes.
• Use ET-based water balance as the schedule adjustment mechanism, not soil moisture prediction. The QWEL formula chain (ETo - effective precipitation = irrigation water requirement) is a well-established agronomic calculation, not a predictive AI model.
• If implementing machine learning, focus on plant stress detection or ET refinement rather than soil moisture prediction from event correlation.
• Frame any weather-responsive scheduling as "ET-adjusted water budgeting" (standard practice) rather than "predictive soil moisture modeling" (SmartRain's claimed approach).
• Consider establishing prior art through a defensive disclosure covering weather-forecast-adjusted ET scheduling for design-computed irrigation systems (see Section 8).

---

3. Other Relevant Patents Found

3.1 Comprehensive Patent Table

| Patent # | Title | Assignee | Filed | Expires | Risk to SimplyScapes | Notes | |-----------|-------|----------|-------|---------|---------------------|-------| | US10,028,454B2 | Environmental Services Platform | Husqvarna AB (orig. ET Water Systems) | Aug 24, 2015 | ~2035 | LOW-MODERATE | Cloud + plant database + ET scheduling. Closest prior art to SimplyScapes approach. Claims require site survey data correlation with external data sources. | | US20250048979A1 | Irrigation System, Sensor and Smart Scheduling | Waterworks Inc (Daniel Zhao) | Aug 11, 2024 | Pending | NEGLIGIBLE | Claims are deeply hardware-specific (moisture sensor wand, dome, pointed end, physical controller housing). Pure hardware patent for IoT sensor devices. No software scheduling overlap. | | US9,504,213B2 | Smart Sprinkler System with Variable Scheduling | Sustainable Savings LLC (orig. Rachio) | Aug 14, 2013 | ~2033 | NEGLIGIBLE | Claims require radar-based rainfall information and variable repeating schedule with non-sprinkling days. SimplyScapes uses ET-based computation, not radar rain delay. | | US7,337,042B2 | ET-Based Irrigation Control | HydroPoint Data Systems | Oct 29, 2004 | EXPIRED (~2024) | NONE | Pioneer ET scheduling patent. Claims required 4-D grid computation of weather parameters. Now expired -- establishes strong prior art that ET-based irrigation scheduling is in the public domain. | | US8,401,705B2 | Temperature Budgeting | Hunter Industries | Filed ~2011 | ~2031 | NEGLIGIBLE | Temperature-based water budgeting for controllers. Requires physical irrigation controller hardware. | | US7,962,244B2 | Landscape Irrigation Time of Use | Hunter Industries | Filed ~2009 | ~2029 | NEGLIGIBLE | Time-of-use watering restriction compliance. Controller-based, not relevant to design-time scheduling. | | US8,620,480B2 | Automated Water Budgeting | Hunter Industries | Filed ~2012 | ~2032 | NEGLIGIBLE | Automated seasonal adjustment and water budgeting in physical controllers. | | US8,649,907B2 | Irrigation Control Method | Rain Bird | Filed ~2012 | ~2032 | NEGLIGIBLE | Server-based scheduling with weather forecast rain delay. Requires controller hardware communication. | | US9,241,451B2 | Irrigation Control Methods | Rain Bird | Filed ~2013 | ~2033 | NEGLIGIBLE | Similar server-based irrigation with forecast integration. Controller hardware required. | | US10,362,739B2 | Wireless Irrigation Monitoring | Rain Bird | Filed ~2016 | ~2036 | NEGLIGIBLE | Wireless nodes for environmental monitoring and irrigation control. Hardware sensor network. | | US8,948,921B2 | Smart Irrigation System | Orbit Irrigation Products | Filed ~2012 | ~2032 | NEGLIGIBLE | Smart irrigation with calibration data and flow rate calculation. Controller hardware required. | | US9,192,110B2 | Central Irrigation Control | The Toro Company | Filed ~2012 | ~2032 | NEGLIGIBLE | Central control with ET interface, pump control, precipitation management. Large commercial system. | | US9,202,252B1 | Water Conservation and Land Use Optimization | Jain Agriculture Services | Filed ~2013 | ~2033 | LOW | System for water conservation. Classified under G06Q50/02. Agriculture-focused, not turf landscape. | | US8,712,592B2 | Resource Demand System | HydroPoint Data Systems | Mar 29, 2011 | ~2031 | LOW | Controlling resource demand systems. May cover aspects of cloud-based scheduling but requires specific demand management hardware. |

3.2 Closest Prior Art Patent: US10,028,454B2 (Husqvarna/ETwater)

This patent deserves special attention because it describes a cloud-based platform combining:

• Site survey data
• Plant databases
• Weather data
• Evapotranspiration calculations
• Optimized irrigation scheduling

The patent was originally assigned to ET Water Systems Inc (now Husqvarna AB). It represents the closest prior art to the general concept of cloud-based, data-driven irrigation scheduling. However, the key differences from SimplyScapes are:

1. ETwater requires physical site survey data as input -- SimplyScapes derives equivalent data from the design
2. ETwater's scheduling engine operates on already-installed systems -- SimplyScapes generates schedules at design time before installation
3. ETwater does not compute DU from design geometry -- this is SimplyScapes' core innovation

The existence of this patent as prior art is actually beneficial to SimplyScapes: it establishes that cloud-based ET scheduling with plant databases is a known concept (filed 2015), which narrows the scope of any future SmartRain claims in this space.

---

4. Competitor IP Activity

4.1 Active Patent Filers in Irrigation Scheduling

| Company | Patent Activity | Focus Areas | Threat Level | |---------|----------------|-------------|--------------| | Smart Rain Systems LLC | 6+ granted patents, active filer | Remote management, sensors, AI prediction, landscaper integration | MODERATE -- most active and closest competitor | | Rain Bird Corporation | Large portfolio (10+ relevant patents) | Controller-based scheduling, weather integration, wireless monitoring | LOW -- focused on hardware controllers | | Hunter Industries | Moderate portfolio (5+ relevant) | Temperature budgeting, water conservation, time-of-use compliance | LOW -- focused on embedded controller intelligence | | The Toro Company | Large portfolio | Central control systems, ET interfaces, commercial irrigation | LOW -- focused on commercial/golf market | | Rachio / Sustainable Savings LLC | Several patents | Radar rain delay, variable scheduling, smart controllers | LOW -- consumer WiFi controller focus | | Orbit Irrigation Products | Several patents | Smart irrigation, WiFi controllers, flow calibration | LOW -- consumer hardware focus | | HydroPoint Data Systems | Key ET patents (some expired) | ET computation, 4-D weather grid, demand management | LOW -- pioneer patents aging out | | Husqvarna AB / ET Water | US10,028,454 + others | Cloud platform, plant databases, site surveys, ET scheduling | LOW-MODERATE -- closest architectural parallel | | Waterworks Inc | US20250048979A1 (pending) | Physical sensor hardware for smart scheduling | NEGLIGIBLE -- pure hardware claims | | Jain Irrigation / Jain Agriculture | Several patents | Agricultural drip irrigation, water conservation | NEGLIGIBLE -- agriculture-focused, not turf |

4.2 Key Observations About Competitor IP

1. Universal Hardware Coupling: Every competitor's patents are built around physical hardware -- controllers, sensors, valves. No identified patent claims pure software-based schedule generation from design geometry.

2. ET Scheduling is Well-Established Prior Art: HydroPoint's US7,337,042 (expired ~2024) and the broader body of ET-based scheduling patents establish that computing irrigation schedules from evapotranspiration data is in the public domain. This is foundational prior art for SimplyScapes.

3. Design-Time Intelligence is Whitespace: No identified patent covers the concept of computing DU from irrigation design geometry (head placement, arc, radius, spacing) and using that computed DU to generate schedules. This appears to be genuine whitespace in the patent landscape.

4. Cloud + Plant DB + ET is Known: Husqvarna's US10,028,454 establishes that combining cloud platforms, plant databases, and ET data for scheduling is prior art (filed 2015). SimplyScapes' innovation is the SOURCE of the DU data (design vs. field test), not the formula chain itself.

---

5. Defensive Publications Found

5.1 TDCommons Search Results

A search of the Technical Disclosure Commons (tdcommons.org) for terms including "irrigation scheduling," "evapotranspiration," "distribution uniformity," and "precipitation rate" returned no directly relevant defensive publications in the irrigation scheduling space. The TDCommons repository is primarily populated by technology companies (Google, Samsung, etc.) and the irrigation industry has not historically used this platform for defensive publishing.

Implication: This represents an opportunity for SimplyScapes. Publishing a defensive disclosure on TDCommons would establish prior art in a searchable database that patent examiners consult, and the absence of existing disclosures means SimplyScapes' disclosure would be the first in this specific domain.

5.2 IP.com Search Results

A search of publicly available prior art databases for irrigation scheduling software with evapotranspiration did not identify specific IP.com disclosures covering design-time DU computation for schedule generation. The available prior art consists primarily of:

• Academic publications on ET-based scheduling methods
• USDA/ARS research papers on irrigation scheduling software
• Extension service publications (UC Davis, University of Minnesota, University of Florida)

5.3 Relevant Academic Prior Art

The following academic and institutional publications establish prior art for ET-based irrigation scheduling:

| Source | Relevance | |--------|-----------| | QWEL certification curriculum (qwel.net) | Documents the DU-based formula chain: ETo x PF / (PR x DU) | | EPA WaterSense Water Budget Tool 2.0 | Establishes methodology for water budget computation with species coefficients | | MWELO Appendix D | California regulatory framework for landscape water budget calculation | | ANSI/ASABE S623.1 (SLIDE Rules) | Industry standard for landscape irrigation design evaluation | | UC Davis CCUH publications | Academic prior art for DU measurement and scheduling computation | | IA (Irrigation Association) technical standards | Industry standards for audit-based scheduling |

Critical Gap in Prior Art: While DU-based scheduling is well-documented, ALL existing publications assume DU is obtained from a physical catch-can field test. No identified prior art computes DU from the irrigation design geometry itself. This is SimplyScapes' core innovation and the primary candidate for defensive disclosure.

---

6. Freedom to Operate Summary

6.1 Overall Risk Assessment Matrix

| Area | Risk Level | Rationale | |------|-----------|-----------| | Design-computed DU/PR schedule generation | CLEAR | No identified patent covers computing DU from design geometry. All existing scheduling patents assume physical measurement or sensor input. | | ET-based formula chain (ETo x PF / (PR x DU)) | CLEAR | Standard agronomic practice documented in QWEL, EPA WaterSense, MWELO. HydroPoint ET patents largely expired. The formula chain itself is not patentable. | | Plant database with species-specific factors | CLEAR | Husqvarna's US10,028,454 established plant database + ET as prior art (2015). Species coefficients are published agronomic data. | | Cloud-based schedule delivery | CLEAR | Broadly established prior art across Rain Bird, HydroPoint, Husqvarna, and others. | | Rachio controller integration | CLEAR | Using a public API to send schedules to a third-party controller is not covered by SmartRain's patents (which require the patentee's own controllers). | | Water usage estimation from design parameters | CLEAR (with caution) | Estimating theoretical usage from PR x time x area is engineering calculation, not metered flow. Do not tie to fee-based savings calculation (see Risk Area 1). | | Landscape change-driven schedule recomputation | CLEAR (with caution) | Design-driven recomputation from first principles is distinct from SmartRain's event-driven temporary override (see Risk Area 2). | | Weather forecast-based schedule skip/delay | CAUTION | Simple threshold-based rain skip is likely clear (extensive prior art in Rain Bird, Rachio patents). Historical model correlation for soil moisture prediction may implicate SmartRain US11,839,184 (see Risk Area 3). | | AI/ML predictive scheduling | CAUTION | If future AI features predict soil moisture from historical event correlation, may implicate SmartRain US11,839,184. Use ET-based water balance approach instead. | | Physical sensor integration | CAUTION | If SimplyScapes adds physical flow sensors or moisture sensors, multiple SmartRain claims could become relevant. Currently not planned. |

6.2 Summary Statement

SimplyScapes' core approach -- computing irrigation schedules from design-time DU and PR using standard ET formulas -- operates in clear whitespace relative to the identified patent landscape. The fundamental architectural distinction is that SimplyScapes derives scheduling inputs from design geometry (a software computation) rather than from physical sensors and controllers (hardware infrastructure). This distinction puts SimplyScapes outside the scope of every identified SmartRain independent claim, as all require hardware elements (controllers, sensors, or both) that SimplyScapes does not use.

The primary risk areas involve feature expansion: (1) tying estimated water savings to billing/fees, (2) implementing event-driven temporary schedule overrides with auto-revert, and (3) building predictive soil moisture models from historical event correlation. All three can be addressed through specific design-around strategies documented in Section 7.

---

7. Design-Around Recommendations

7.1 Strategy D1: Pure Design-Time Architecture

Principle: All scheduling inputs should be derived from the irrigation design, not from physical sensors or real-time operational data.

Implementation:

• DU computed from head placement, spacing, arc, radius, nozzle performance data
• PR derived from manufacturer specifications and design geometry
• ETo sourced from published reference data (CIMIS, USU Climate Center, gridMET)
• Plant factors (PF) from an agronomic plant database
• Soil infiltration rates from USDA soil surveys (Web Soil Survey) by location
• Slope factors from digital elevation data

Why this works: SmartRain's patents universally claim systems that operate on data from physical sensors installed at a property. SimplyScapes operates on data from the design that creates the property's irrigation system. These are categorically different data sources.

7.2 Strategy D2: Deterministic Formulas, Not Predictive Models

Principle: Use established agronomic formulas (QWEL, Penman-Monteith, EPA WaterSense) for schedule computation, not predictive machine learning models for soil moisture.

Implementation:

• Schedule computation: ETo x PF / (PR x DU) = gross runtime
• Cycle-soak splitting: runtime / soil infiltration capacity = number of cycles
• Seasonal adjustment: monthly ETo variation from reference data
• No soil moisture prediction models
• No historical event correlation databases
• No triggering event detection and comparison systems

Why this works: SmartRain US11,839,184 specifically claims predictive soil moisture modeling from historical event correlation. Deterministic ET-based formulas are standard agronomic practice with extensive prior art and are not covered by these claims.

7.3 Strategy D3: Weather Adjustment via ET Deficit, Not Moisture Prediction

Principle: If adding weather responsiveness, adjust the ET calculation (water balance method), not predict soil moisture.

Implementation:

• Receive forecast precipitation data
• Compute effective precipitation using USDA SCS method or similar
• Subtract effective precipitation from the irrigation water requirement: IWR = ETc - Pe
• If IWR <= 0, skip/reduce the irrigation event
• Frame as "adjusted water budget" not "predicted soil moisture"

Why this works: This is the standard water balance method documented in QWEL, EPA WaterSense 2.0, and MWELO. It computes irrigation NEED from ET deficit, not soil moisture from event correlation. It is well-established prior art that predates SmartRain's AI patent by decades.

7.4 Strategy D4: Design Recomputation, Not Event Override

Principle: When the landscape or design changes, recompute the entire schedule from design parameters rather than applying a temporary event-driven override.

Implementation:

• User changes plant type in a zone -> recompute PF -> recompute entire schedule
• User adds sod installation -> update zone to "establishment" mode in plant database -> recompute schedule from establishment PF and watering frequency
• No predetermined durations per event type
• No auto-revert after a fixed period
• Schedule changes are permanent until the next design modification

Why this works: SmartRain US11,684,029 specifically claims predetermined landscape events with fixed durations that signal a controller to temporarily alter and then auto-revert a schedule. Design-driven recomputation generates a new baseline schedule from first principles -- there is no "event" to revert from.

7.5 Strategy D5: Estimated Usage, Not Metered Savings

Principle: Present water usage data as engineering estimates from design parameters, never as metered savings tied to billing.

Implementation:

• Calculate estimated water usage: PR x runtime x area x frequency
• Display as "estimated monthly water usage" or "design water budget"
• Compare against MWELO/WaterSense compliance thresholds (MAWA/ETWU)
• Never display as "water cost savings" or "savings vs. previous"
• Never tie water usage calculations to a service fee or billing model

Why this works: SmartRain US10,660,279 specifically claims calculating water cost savings from metered flow/sensor data and charging service fees based on those savings. Design-based estimates for compliance purposes are engineering calculations, not service billing metrics.

---

8. Defensive Disclosure Recommendations

Based on the whitespace identified in this FTO analysis, SimplyScapes should file a defensive disclosure covering the following innovations to establish prior art and prevent competitors from patenting these concepts:

8.1 Core Disclosure: Design-Computed DU for Automated Schedule Generation

Title: "Method for Generating Irrigation Schedules from Design-Computed Distribution Uniformity and Precipitation Rate"

Key claims to disclose:

1. Computing Distribution Uniformity (DU) from irrigation design geometry (head placement coordinates, arc, radius, nozzle type, spacing pattern) without physical catch-can testing
2. Deriving zone-specific Precipitation Rate (PR) from manufacturer nozzle performance data and the design's head layout geometry
3. Feeding design-computed DU and PR through standard ET formulas (ETo x PF / (PR x DU)) to generate per-zone irrigation runtimes
4. Automatically computing cycle-soak splits from design-computed PR, soil infiltration rate (from USDA soil survey data), and slope factor (from digital elevation data)
5. Generating a complete irrigation schedule (runtimes, start times, cycle-soak splits, frequency) entirely from design-time data without physical sensors, field tests, or installed controllers
6. Dynamically recomputing schedules when design parameters change (head repositioned, nozzle changed, zone boundaries modified, plant type updated)

8.2 Extended Disclosures

8.2.1 Species-Specific Season Logic:

• Using plant-database-driven base temperatures and dormancy thresholds to determine irrigation season start/stop dates per zone (rather than EPA WaterSense 2.0's universal 50F GDD threshold)
• Computing variable plant factors across the growing season from species-specific crop coefficient curves

8.2.2 Weather-Adjusted Design Schedules:

• Adjusting design-computed schedules using forecast precipitation data via ET water balance method (not soil moisture prediction)
• Computing effective precipitation from forecast data and subtracting from irrigation water requirement (IWR = ETc - Pe)
• Applying seasonal ET variation from reference data to dynamically adjust design-computed runtimes

8.2.3 Multi-Controller Schedule Distribution:

• Generating schedules from design parameters and distributing to multiple controller platforms (Rachio, Hunter Hydrawise, Rain Bird, etc.) via their respective APIs
• Translating design-computed schedules into controller-specific formats while maintaining design integrity

8.2.4 Design-Audit Comparison:

• Comparing design-computed DU against field-measured DU (from catch-can audit) to quantify installation quality
• Identifying zones where installed performance deviates from design intent and recommending adjustments

8.3 Publication Strategy

Recommended platforms:

1. TDCommons (tdcommons.org): Primary platform. Indexed by Google Patents and searched by patent examiners. Free to publish. No existing irrigation scheduling disclosures found (first mover advantage).
2. IP.com: Secondary platform for broader prior art coverage.
3. ArXiv or institutional repository: For the academic credibility component.

Timing: File defensive disclosures BEFORE any public product launch or marketing of the scheduling feature. The disclosure date establishes the prior art date. SmartRain is an aggressive filer and could attempt to patent variations of the design-computed approach if they observe it in the market.

---

9. Sources

9.1 SmartRain Patents (Primary Analysis)

| Patent | Source | Access Date | |--------|--------|-------------| | US9,307,706B2 | Google Patents | 2026-03-01 | | US10,660,279B2 | Google Patents | 2026-03-01 | | US11,185,024B2 | Google Patents | 2026-03-01 | | US11,684,029B2 | Google Patents | 2026-03-01 | | US11,839,184B2 | Google Patents, FreePatentsOnline | 2026-03-01 | | US20210176931A1 | Google Patents | 2026-03-01 | | SmartRain Patent Page | smartrain.net/patent | 2026-03-01 |

9.2 Competitor Patents

| Patent | Assignee | Source | |--------|----------|--------| | US10,028,454B2 | Husqvarna AB / ET Water Systems | Google Patents | | US20250048979A1 | Waterworks Inc | Google Patents | | US9,504,213B2 | Sustainable Savings (Rachio) | Google Patents | | US7,337,042B2 | HydroPoint Data Systems | Google Patents | | US8,401,705B2 | Hunter Industries | Google Patents | | US7,962,244B2 | Hunter Industries | Google Patents | | US8,620,480B2 | Hunter Industries | Google Patents | | US8,649,907B2 | Rain Bird | Google Patents | | US9,241,451B2 | Rain Bird | Google Patents | | US10,362,739B2 | Rain Bird | Google Patents | | US8,948,921B2 | Orbit Irrigation Products | Google Patents | | US9,192,110B2 | The Toro Company | Google Patents | | US9,202,252B1 | Jain Agriculture Services | Google Patents | | US8,712,592B2 | HydroPoint Data Systems | Google Patents |

9.3 Assignee Portfolio Searches

| Search | Source | |--------|--------| | Smart Rain Systems LLC patents | Justia Patents | | Rachio Inc patents | Rachio Patents Page | | Hunter Industries patents | Justia Patents | | Orbit Irrigation Products patents | Justia Patents | | Toro Company patents | Justia Patents |

9.4 CPC Code Searches

| CPC Code | Description | Relevant Results | |----------|-------------|-----------------| | A01G25/16 | Control of watering | SmartRain, Hunter, Rain Bird, Orbit patents | | A01G25/167 | Control by soil/atmosphere humidity sensors | SmartRain AI patent, sensor-based systems | | G06Q50/02 | Agriculture/Forestry/Mining IT systems | Jain Agriculture, SmartRain AI patent | | G05D22/00 | Control of fluid flow (superseded) | Limited relevant results |

9.5 Defensive Publication Searches

| Database | Search Terms | Results | |----------|-------------|---------| | TDCommons (tdcommons.org) | irrigation scheduling, evapotranspiration, distribution uniformity | No relevant defensive publications found | | IP.com (via web search) | irrigation scheduling, evapotranspiration, automated software | No specific IP.com disclosures found in irrigation scheduling | | Academic databases | ET-based scheduling software, DU computation | USDA/ARS, UC Davis, UMN Extension publications found (prior art for ET methods) |

9.6 Industry Standards and Reference Documents

| Document | Relevance | |----------|-----------| | QWEL Certification Curriculum | Documents DU-based formula chain (ETo x PF / (PR x DU)) | | EPA WaterSense Water Budget Tool 2.0 | Methodology for water budget computation with species coefficients | | MWELO Appendix D | California regulatory framework for landscape water budgets | | ANSI/ASABE S623.1 (SLIDE Rules) | Industry standard for landscape irrigation design evaluation |

---

Appendix A: SmartRain Claim Element Matrix

This matrix maps each SmartRain independent claim element against SimplyScapes' design-time intelligence approach. An "X" indicates the claim element is present; a blank indicates absence.

| Claim Element | SmartRain Claims | SimplyScapes | |---------------|:----------------:|:------------:| | Physical irrigation controller | X | | | Flow sensor(s) | X (706, 279, 024, 931) | | | Moisture sensor(s) | X (279, 024, 931, 184*) | | | Master valve | X (279) | | | Central computer / IMS | X | X (cloud) | | On-site visit / site survey | X (706) | | | Remote device(s) / mobile | X (279, 029) | X (web app) | | GPS user positioning | X (024) | | | Water usage data monitoring | X (706, 279) | | | Fault detection / diagnosis | X (706, 279) | | | Technician dispatch | X (706) | | | Cost savings calculation from metered data | X (706, 279) | | | Fee/billing based on savings | X (706, 279) | | | Predetermined landscape events | X (029) | | | Auto-revert after event duration | X (029) | | | Historical event model correlation | X (184) | | | Soil moisture prediction | X (184) | | | Triggering event detection | X (184) | | | Design-computed DU | | X | | Design-computed PR | | X | | ET formula chain computation | | X | | Plant database factors | | X |

Note: US11,839,184 claims reference weather data and water flow data as inputs but do not explicitly require physical sensor hardware in independent claims. However, the claims are directed at soil moisture prediction from historical event correlation, which is architecturally distinct from ET-based schedule computation from design parameters.

---

Appendix B: Patent Expiration Timeline

| Year | Patent Expiring | Impact | |------|----------------|--------| | ~2024 | US7,337,042 (HydroPoint ET) | ET-based irrigation scheduling fully in public domain | | ~2029 | US7,962,244 (Hunter TOU) | Time-of-use scheduling compliance in public domain | | ~2031 | US8,401,705 (Hunter temp budgeting) | Temperature-based water budgeting in public domain | | ~2032 | US8,649,907 (Rain Bird control) | Server-based weather-adjusted scheduling in public domain | | ~2032 | US8,948,921 (Orbit smart irrigation) | Smart irrigation with calibration in public domain | | ~2033 | US9,504,213 (Rachio radar) | Radar-based rain skip scheduling in public domain | | ~2034 | US9,307,706 (SmartRain mgmt) | SmartRain remote management in public domain | | ~2034 | US10,660,279 (SmartRain cont.) | SmartRain sensor-based management in public domain | | ~2035 | US10,028,454 (Husqvarna/ETwater) | Cloud + plant DB + ET scheduling in public domain | | ~2038 | US11,684,029 (SmartRain landscaper) | Landscape event scheduling in public domain | | ~2039 | US11,185,024 (SmartRain maps) | Map integration with sensor overlay in public domain | | ~2040 | US11,839,184 (SmartRain AI) | AI soil moisture prediction in public domain |

---

This analysis was prepared as a supporting document for the SimplyScapes innovation pipeline. All patent findings represent a technical assessment and are NOT legal advice. Identified risk areas should be reviewed by qualified patent counsel before product decisions are made.

Advanced Irrigation Scheduling Intelligence: State of the Art and Whitespace Analysis

ID: SS-RR-2026-002-S1 | Date: 2026-03-01 | Status: complete ClickUp: Automated Turf Irrigation Scheduling from Design-Time Intelligence Parent plan: SS-RP-2026-002 Domain: Irrigation Management / Advanced Scheduling Intelligence Purpose: Supporting research for defensive disclosure -- comprehensive coverage of sensors, AI, satellite ET, predictive scheduling, feedback loops, digital twins, and open-source tools

---

Executive Summary

This paper surveys the full landscape of advanced irrigation scheduling intelligence beyond the simple ETo-based approach that SimplyScapes Phase 1 will implement. The goal is to establish comprehensive prior art for a defensive disclosure that protects the innovation space before competitors (particularly SmartRain, Rachio, and emerging AI irrigation startups) file patents on approaches that combine design-time intelligence with advanced scheduling techniques.

The research covers seven technology domains: (1) sensor-augmented scheduling, (2) satellite and remote sensing ET, (3) machine learning approaches, (4) weather forecast integration, (5) feedback loops and adaptive scheduling, (6) novel data sources, and (7) digital twin concepts. For each domain, we assess the current state of the art, accuracy metrics, cost structures, integration complexity, and the whitespace available for defensive disclosure.

Key finding: No existing system combines design-computed Distribution Uniformity (DU) with any of these advanced techniques. Every advanced scheduling system assumes DU comes from a field measurement or uses a default value. The combination of SimplyScapes' design-time DU/PR computation with satellite ET, sensor feedback, ML prediction, or digital twin modeling represents unoccupied territory across the entire patent landscape.

---

1. Sensor-Augmented Scheduling

1.1 Soil Moisture Sensors

Soil moisture sensors provide volumetric water content (VWC) measurements that directly indicate plant-available water in the root zone. Three primary measurement technologies dominate the market:

Time Domain Reflectometry (TDR)

• Measurement accuracy: +/- 1% VWC (highest accuracy class)
• Cost: $300-$2,000+ per sensor unit
• Principle: Measures the travel time of an electromagnetic pulse along a waveguide embedded in soil; travel time is proportional to the dielectric constant, which correlates with water content
• Strengths: Gold-standard accuracy, low sensitivity to soil salinity and temperature
• Limitations: High cost prohibits deployment at residential scale; requires careful installation and calibration

Frequency Domain Reflectometry (FDR)

• Measurement accuracy: +/- 2-3% VWC after soil-specific calibration
• Cost: $100-$500 per sensor unit
• Principle: Measures the frequency response of an oscillating electromagnetic field in the soil; frequency shifts with changing dielectric constant
• Strengths: Good accuracy at moderate cost; simpler electronics than TDR
• Limitations: Sensitive to soil salinity and temperature; requires calibration for different soil types

Capacitance Sensors (Low-Cost)

• Measurement accuracy: +/- 3-5% VWC (lower than 5% error rates demonstrated in calibrated deployments)
• Cost: $10-$100 per sensor unit; full IoT station costs approximately $80-$163
• Principle: Measures the capacitance between two electrodes embedded in soil, which varies with the dielectric constant of the surrounding medium
• Strengths: Low cost enables dense deployment; suitable for IoT integration; adequate accuracy for irrigation scheduling decisions
• Limitations: Highly sensitive to soil salinity (EC) and temperature; requires careful calibration; soil-specific behavior varies significantly

Multi-Depth Measurement (CropX Approach)

CropX sensors collect moisture, temperature, and electrical conductivity at multiple depths (8" and 18" standard, installable at 3 depths). The sensor mechanism uses amplitude domain reflectometry at 100MHz, estimating soil moisture based on impedance differentials between electrodes and soil. Measurements occur every 150ms, are averaged over 30-minute intervals, and transmitted to the cloud every 12 hours. Accuracy is specified at +/- 2% VWC.

CropX applies proprietary crop-specific agronomic models combined with satellite data, weather station feeds, and farm machinery telemetry to generate irrigation recommendations. The platform serves 20,000+ users across 70+ countries and 100+ crop types.

Residential Landscape Context:

For residential landscapes, soil moisture sensors face economic and practical barriers. A typical residential property with 4-8 irrigation zones would require 4-16 sensors (one per zone minimum, two per zone for redundancy) at $80-$200 each for IoT-connected sensors. Total hardware cost: $320-$3,200 before installation. This cost is prohibitive for most residential applications but feasible for commercial properties and high-value landscapes.

The WaterSense program estimates that installing a soil moisture sensor can save an average home with an automatic landscape irrigation system more than 15,000 gallons of water annually, providing economic justification at utility rates above $8-10/1,000 gallons.

1.2 Flow Meters and Flow Sensors

Flow meters measure the volume and rate of water flowing through irrigation pipes, enabling three key capabilities:

Leak Detection:

• Hunter HC Flow Meter: Industry-leading accuracy of +/- 2% of reading
• Bluebot: Learns normal water use patterns and alerts on anomalies (installed on accessible irrigation pipe or valve box)
• Flume 2: Uses patented magnetic field reading from the water meter itself; detects usage to 1/100th of a gallon; uses machine learning for leak detection; cost ~$199 consumer device
• Phyn Plus: Ultrasonic flow sensor built by Badger Meter; scans flow 50 times/second; detects flows as low as 0.026 GPM
• Moen Flo: Reported 96% decrease in water damage claim events; 60% of homeowners notified of unknown leak within 30 days

Actual vs. Expected Water Use: Flow meters enable reconciliation between the predicted water delivery (from the schedule calculation: runtime x precipitation rate x area) and actual water delivered. This creates a feedback loop that can detect:

• Degraded sprinkler performance (clogged nozzles, worn seals)
• Pressure problems (too high = misting, too low = poor coverage)
• Changed DU from real-world conditions vs. design assumptions
• Broken heads or pipe leaks

Zone-Level Water Metering: Commercial platforms (WeatherTRAK, SmartRain) use flow data at the zone level to track per-zone water consumption and compare it against the scheduled amount. This enables zone-by-zone performance tracking and identifies zones that consistently over- or under-deliver water.

1.3 Pressure Sensors

Pressure sensors monitor system pressure at various points in the irrigation network:

• Recommended operating ranges: Fixed spray heads 20-30 PSI, rotor sprinklers 30-50 PSI, drip irrigation 10-30 PSI
• Diagnostic value: Pressure variation indicates pump problems, nozzle plugging, line breaks, or insufficient capacity
• IoT-enabled sensors: Battery-operated pressure sensors using NB-IoT technology enable near real-time data transmission for remote monitoring
• Integration with scheduling: Pressure data can be used to adjust scheduling parameters -- low pressure reduces effective DU and PR, requiring longer runtimes to deliver the same water volume

1.4 On-Site Weather Stations

On-site weather stations provide the most accurate microclimate data for ET calculation but are expensive and require maintenance:

• Full weather station (Davis Vantage Pro2 equivalent): $400-$1,500; measures temperature, humidity, wind speed/direction, solar radiation, rainfall -- all inputs for Penman-Monteith ET calculation
• Simplified sensors (Weathermatic, Hunter Solar Sync): $100-$300; measure temperature and solar radiation only; estimate ET using simplified models (Hargreaves method)
• ET accuracy: On-site Penman-Monteith calculation is the gold standard (basis of FAO-56). Simplified temperature-radiation methods introduce 5-15% error compared to full Penman-Monteith but outperform regional weather station data in areas with strong microclimatic variation

Integration Complexity:

The WeatherTRAK ET Everywhere service represents the state of the art in commercial ET data delivery. HydroPoint monitors local weather stations nationwide and uses radio transmissions to notify controllers of weather changes. The controller adjusts programs using the Penman-Monteith equation, optimizing by plant type, soil type, sprinkler type, sun exposure, and slope. The scheduling engine walks through six landscape questions and then automatically calculates and adjusts daily runtimes.

---

2. Satellite and Remote Sensing ET

2.1 OpenET

OpenET is the most significant recent development in satellite-based ET data for water management in the United States.

Technical Specifications:

• Spatial resolution: 30m x 30m (approximately 1/4 acre -- field scale)
• Temporal resolution: Daily, monthly, and annual products
• Geographic coverage: Contiguous United States (CONUS)
• Satellite source: Primarily Landsat (NASA/USGS partnership)
• Models: Ensemble of six remote sensing models (DisALEXI, eeMETRIC, geeSEBAL, PT-JPL, SIMS, SSEBop)
• Availability: 1999-present (monthly); 2016-present (daily)

Accuracy Assessment (Nature Water, 2023):

• Cropland sites: Mean absolute error = 15.8 mm/month (17% of mean observed ET), mean bias error = -5.3 mm/month (6%), R-squared = 0.90
• Annual crops (wheat, corn, soy, rice): ~10-20% average error rate
• Best performance: Arid regions (California, Southwest US)
• Weaker performance: Shrublands and forested sites (higher inter-model variability)

API Access:

• Base URL: https://openet.gitbook.io/docs/
• Endpoints: raster/timeseries/point (point queries), geodatabase (pre-computed field data)
• Response format: JSON (timeseries), CSV/GeoJSON (polygon queries)
• Quota: 100 queries/month (free tier); increased quota with Earth Engine account linkage
• Maximum query size: 50,000 acres per request, 50 polygons per custom shapefile query
• Cost: Free (subject to usage quotas)
• Authentication: API key registration required

Limitations for Residential Landscapes:

• 30m resolution is adequate for large commercial properties but coarse for typical residential lots (most residential properties are 1-4 pixels)
• Temporal gap: Landsat revisit is 8-16 days; cloud cover further reduces usable observations; not suitable for daily scheduling decisions
• Urban heterogeneity: Residential landscapes mix impervious surfaces (roofs, driveways), turf, trees, and ornamental beds within a single 30m pixel, making per-pixel ET values unreliable for zone-level scheduling
• Calibration: The accuracy assessment focused on agricultural land; urban/ suburban landscape accuracy is not well characterized

2.2 NASA ECOSTRESS

ECOSTRESS (ECOsystem Spaceborne Thermal Radiometer Experiment on Space Station) provides higher-resolution thermal imagery from the International Space Station.

Technical Specifications:

• Spatial resolution: 38m x 69m at nadir (approximately 70m effective)
• Revisit cycle: Average 4 days (variable due to ISS orbit)
• Spectral bands: 5 thermal infrared bands (8-12 micrometers)
• Coverage: Global between 52 degrees N and 52 degrees S latitude
• ET products: ECO3ETALEXI (DisALEXI-JPL) at 70m for CONUS

Accuracy:

• Relative to eddy flux data, ECOSTRESS ET improved correlation by 85% (0.76 to 0.89) and normalized RMSE by 62% (13% to 8%) compared to coarser-resolution products
• Particularly useful for mapping diurnal variations of surface urban heat island effects at sub-district scale

Urban Landscape Applications: ECOSTRESS has demonstrated utility for examining urban heat island characteristics at different times of day, which is relevant to understanding microclimate effects on landscape irrigation demand. The diurnal temperature variation data could inform time-of-day scheduling optimization.

2.3 Sentinel-2

Sentinel-2 provides the highest freely-available spatial resolution for vegetation monitoring:

Technical Specifications:

• Spatial resolution: 10m (visible and NIR bands), 20m (red edge and SWIR)
• Revisit time: 5 days (with two satellites, Sentinel-2A and 2B)
• Spectral bands: 13 bands from visible to SWIR

ET Estimation Capability: Research has demonstrated estimation of urban evapotranspiration at 10m resolution using Sentinel-2 NDVI data combined with leaf area index (LAI) estimation and carbon-water coupling models. A machine learning approach combining Sentinel-2 time series with meteorological data has been applied to map ET at 10m spatial and hourly temporal resolution for urban areas.

NDVI for Irrigation Monitoring: Both NDVI and NDMI (Normalized Difference Moisture Index) from Sentinel-2 are highly sensitive to moisture, making them effective for determining irrigation timing and identifying water-stressed areas. The 5-day revisit and 10m resolution make Sentinel-2 more suitable than Landsat for monitoring individual residential properties.

2.4 Data Fusion Approaches

To overcome the temporal limitations of Landsat (8-16 day revisit), data fusion methods combine:

• Landsat (30m, 8-16 day) for spatial detail
• MODIS (250-500m, daily) for temporal frequency
• ECOSTRESS (70m, 4-day) for thermal/ET diurnal variation
• Sentinel-2 (10m, 5-day) for vegetation index detail

These fusion approaches can produce daily 30m ET estimates but require significant computational resources and are currently limited to research applications. OpenET partially addresses this through its ensemble approach.

2.5 Relevance to SimplyScapes

Satellite ET data is most valuable as a validation and calibration source rather than a primary scheduling input for residential landscapes:

1. Validate design-computed ET estimates against satellite observations over time
2. Detect microclimate anomalies that cause actual ET to deviate from regional weather station data (south-facing slopes, urban heat islands, wind corridors)
3. Seasonal adjustment of plant factors based on observed vegetation health (NDVI) vs. expected health for the applied water volume
4. Portfolio-level monitoring for landscape management companies: satellite NDVI can flag properties where irrigation appears inadequate or excessive without on-site visits

---

3. Machine Learning Approaches

3.1 Published Research Landscape

Recent systematic reviews (2024-2025) identify a significant rise in ML applications for irrigation scheduling, with peak publication activity between 2020 and 2024. Meta-analyses show consistent water savings of 30-50% and yield improvements of 20-30% across ML-augmented irrigation systems compared to conventional scheduling.

Common ML Models Applied:

• Random Forest (RF): Used for soil moisture prediction and ET estimation; robust to overfitting; handles mixed input types well
• Support Vector Machines (SVM): Applied to classification tasks (irrigate vs. don't irrigate) and regression (predict soil moisture)
• Convolutional Neural Networks (CNN): Applied to spatial data (satellite imagery, soil property maps) for ET estimation
• Long Short-Term Memory (LSTM): Used for time-series prediction of soil moisture, ET, and irrigation demand; captures temporal dependencies
• XGBoost: Gradient boosting for tabular feature sets (weather, soil, plant data); high accuracy with interpretable feature importance
• GRU-Transformer: Emerging architecture combining GRU temporal modeling with transformer attention mechanisms for multi-layer soil moisture prediction
• CNN-LSTM Hybrid: Combines spatial feature extraction (CNN) with temporal sequence modeling (LSTM) for integrated soil-weather prediction

Typical Input Features:

• Weather data: temperature, humidity, wind speed, solar radiation, rainfall
• Soil properties: texture, field capacity, wilting point, hydraulic conductivity
• Vegetation indices: NDVI, LAI, crop coefficient
• Historical irrigation and soil moisture data
• Geographic/topographic features: elevation, slope, aspect

Typical Output Variables:

• Predicted soil moisture at various depths and time horizons
• Estimated or predicted ET (actual or reference)
• Irrigation recommendation (amount and timing)
• Crop/plant water stress indicators

3.2 Deep Reinforcement Learning for Irrigation

Reinforcement learning (RL) is emerging as a particularly promising approach because irrigation scheduling is inherently a sequential decision-making problem that can be formulated as a Markov Decision Process (MDP).

Framework:

• State: Current soil moisture, weather conditions, crop stage, season
• Action: Irrigation amount (or no irrigation) for the current time step
• Reward: Function of water use efficiency, plant health, and water cost
• Environment: Typically a crop simulation model (DSSAT, AquaCrop, SWAP) that simulates soil-plant-atmosphere interactions

Key Research Results:

Deep Q-Network (DQN) Studies:

• Wheat production: DRL decision rules uniformly improved on conventional heuristics for all testing years, with the largest improvement reaching 17% (2023, PLOS Water)
• Cotton production: 39% improvement in water use efficiency (8.4% yield increase with 22.1% reduction in water consumption) compared to fixed-schedule strategies (2025, MDPI Agriculture)
• Tomato production (Portugal): DQN trained with dual LSTM environment models for soil moisture prediction

Performance Characteristics:

• DRL outperforms conventional heuristics most significantly under water scarcity constraints and zero-rainfall conditions
• In high-rainfall variability conditions, DRL does not consistently outperform optimized heuristic approaches
• Training requires a simulation environment (not feasible with real-world trial-and-error alone)

Relevance to Landscape Irrigation: RL for landscape irrigation has not been published (all existing research focuses on agricultural crops). Landscape irrigation presents unique challenges:

• Multi-species zones (mixed plant water needs within a single irrigation zone)
• Aesthetic objectives (not yield maximization)
• Longer time horizons (perennial plants, not annual crop cycles)
• Less tolerance for error (plant death is irreversible)

3.3 ML for ET Estimation

Machine learning models are increasingly used to estimate reference ET (ETo) from limited input data:

• Full Penman-Monteith requires temperature, humidity, wind speed, solar radiation (often unavailable at the required spatial resolution)
• ML models can estimate ETo from temperature alone (or temperature + elevation) with accuracy approaching the full Penman-Monteith calculation when trained on regional data
• Accuracy claims: ANN models predict ETo with R-squared > 0.95 using only max/min temperature and extraterrestrial radiation as inputs (compared to full Penman-Monteith)
• Implication for SimplyScapes: ML-estimated ETo could provide hyperlocal ET data calibrated to specific microclimates, improving on regional weather station data without requiring on-site sensors

3.4 AI-Driven Commercial Systems

ETwater/Jain Logic: Claims proprietary ML models with predictive analytics for hourly schedule adjustment. Their HermitCrab retrofit device enables cloud AI scheduling on conventional controllers. Acquired by Jain Irrigation Systems (world's largest drip manufacturer).

SmartRain US11839184B2: Patent claims AI-predicted soil moisture from sensor + weather + historical data with training datasets. Claims are tied to physical sensor infrastructure.

Waterworks Inc US20250048979A1: Patent application for AI scheduling system -- another competitor claim in the space. Analysis in the patent landscape paper (SS-RR-2026-001).

---

4. Weather Forecast Integration

4.1 Beyond Historical ETo

Traditional ET-based scheduling uses historical average ETo (monthly normals) to set seasonal schedules. Advanced approaches use weather forecast data for predictive scheduling:

Predictive ET Calculation: Rather than using yesterday's weather to determine today's irrigation need, predictive scheduling uses forecast weather data to calculate expected ET for the coming 1-7 days. This enables:

• Pre-emptive schedule adjustment (increase irrigation before a heat wave, reduce before a cool period)
• Rain avoidance (skip irrigation when rain is forecast with sufficient probability)
• Optimal irrigation timing (water during the coolest period before a hot day, not after the stress has occurred)

Research Findings:

• Probabilistic weather forecasts can save 0-100mm of irrigation water compared to conventional scheduling by combining forecasted probabilities of rain intensity over 3-day horizons (Springer, Irrigation Science)
• Real-time irrigation scheduling based on weather forecasts, field observations, and human-machine interactions demonstrated improved efficiency using the SWAP soil-water-atmosphere-plant model (AGU Water Resources Research, 2023)
• Ensemble weather forecast approaches show 20-48% water savings and up to 20% profit gains across diverse agricultural settings

4.2 Probabilistic Rain Skip

Current smart controllers implement deterministic rain skip (if rain sensor detects rain, skip irrigation). Advanced approaches use probabilistic forecasts:

Deterministic Rain Skip (Current State):

• Rain sensor activates at a threshold (e.g., 1/8" rainfall)
• Controller skips the current scheduled irrigation
• Limitation: No look-ahead; does not adjust future schedules based on expected cumulative rainfall

Probabilistic Rain Skip (Advanced):

• Fetch forecast rainfall probabilities for the next 3-7 days
• Calculate expected effective rainfall (probability x amount) for each day
• Reduce scheduled irrigation by the expected effective rainfall contribution
• Account for soil infiltration capacity (heavy rain on saturated soil produces runoff, not infiltration)
• Adjust confidence thresholds based on forecast lead time (more conservative for longer-range forecasts)

Implementation Example: Rachio's Flex Daily algorithm incorporates forecast data: when soil moisture is below the Maximum Allowed Depletion (MAD) threshold, the system checks forecast rainfall before scheduling irrigation. However, the exact probabilistic model is not publicly documented.

4.3 Freeze Protection

Advanced controllers incorporate freeze protection logic:

• Temperature threshold: Suspend irrigation when ambient temperature approaches freezing (typically 35-37F threshold)
• Wind chill factor: Account for wind cooling effects on exposed sprinkler systems
• Duration prediction: Use forecast data to determine how long the freeze period will last and adjust the subsequent schedule to compensate for missed irrigation
• Pipe protection: In some systems, run a brief flush cycle to prevent standing water from freezing in exposed pipes

4.4 Weather Data Sources and APIs

Open-Meteo:

• Endpoint: https://api.open-meteo.com/v1/forecast
• ETo parameter: et0_fao_evapotranspiration (daily and hourly)
• Forecast range: Up to 16 days (&forecast_days=16)
• Historical data: /v1/archive endpoint (full historical archive)
• Historical forecast: Access to 2-5 years of archived forecast data
• Cost: Free for non-commercial use (up to 10,000 API calls/day)
• ETo method: FAO-56 Penman-Monteith
• Global coverage with 1km resolution weather models (ERA5, ECMWF IFS)

FrogCast (Agriculture-Specific):

• Field-level precision with probabilistic forecasts
• Agriculture-focused weather variables including growing degree days, evapotranspiration, and frost risk
• Probabilistic rainfall forecasts with confidence intervals

gridMET:

• Spatial resolution: ~4km (1/24th degree)
• Coverage: Contiguous US, 1979-present
• Variables: Reference alfalfa ET (Penman-Monteith), vapor pressure deficit, and full meteorological suite
• Access: Direct NetCDF download, NCSS (NetCDF Subset Service), Google Earth Engine
• Python access: PyGridMET library (docs.hyriver.io/readme/pygridmet.html)
• File naming: variable_abbreviation_year.nc
• Base URL: http://www.northwestknowledge.net/metdata/data/
• Cost: Free (public domain, University of Idaho)

PRISM:

• Spatial resolution: 800m (highest resolution gridded climate dataset for US)
• Coverage: Contiguous US, 1895-present
• Variables: Temperature, precipitation, dew point, vapor pressure deficit (not directly ET, but inputs for ET calculation)
• Integration: PRISM provides the spatial interpolation grid that gridMET uses as its foundation

USU Climate Center:

• Provides monthly ETo by zip code for the western US
• API endpoint already used by SimplyScapes Water Budget calculation
• Based on ASCE standardized reference ET methodology

---

5. Feedback Loops and Adaptive Scheduling

5.1 Actual vs. Predicted Reconciliation

The most valuable feedback loop for irrigation scheduling is comparing predicted water delivery against actual outcomes:

Water Delivery Reconciliation:

Predicted Delivery = Runtime (min) x PR (in/hr) x (1/60) = inches applied
Actual Delivery = Flow meter reading / Zone area = inches applied
Discrepancy = Actual - Predicted

Sources of discrepancy:

• Pressure variation: Municipal water pressure fluctuates 10-30% daily; affects actual PR from every sprinkler head
• Nozzle degradation: Wear increases flow rate; clogging decreases it
• DU degradation: Wind, settling, obstruction, head damage all reduce DU from design values over time
• Soil infiltration changes: Compaction, thatch buildup, and organic matter decomposition change actual infiltration rate vs. assumed rate

Plant Health Reconciliation:

Expected Plant Health = f(species, applied water, ET, season)
Observed Plant Health = Visual inspection, NDVI, customer feedback
Discrepancy = Observed - Expected

If the applied water matches the calculated need but plant health is poor, the model inputs are wrong (incorrect PF, incorrect ET, soil issues). If the applied water deviates from the calculated need and plant health is good, the model may be over- or under-estimating.

5.2 Learning from Controller Data

Smart controllers accumulate operational data that can improve scheduling over time:

Rachio Flex Daily Data:

• Tracks daily soil moisture depletion estimates per zone
• Records actual watering events (time, duration, manual adjustments)
• Logs weather data (temperature, precipitation, wind) from nearby stations
• Stores user-adjusted zone parameters (soil type, slope, shade, nozzle type)
• API provides access to historical watering and moisture data via developer.rachio.com

Fleet-Level Learning (Commercial): Landscape management companies operating hundreds of controllers can aggregate data across properties to identify:

• Regional ET model biases (consistent over- or under-watering across a geographic area)
• Soil type misclassification patterns (clay soils labeled as loam, causing incorrect infiltration assumptions)
• Species-specific plant factor corrections (observed water needs vs. WUCOLS/SLIDE published values)
• Seasonal pattern anomalies (El Nino/La Nina effects on regional ET)

5.3 Continuous Improvement Architecture

A production-grade feedback loop architecture would include:

1. Prediction layer: Generate daily irrigation schedule using ETo, design-computed DU/PR, plant factors, and soil properties
2. Execution layer: Push schedule to controller; record actual runtimes and flow meter readings
3. Observation layer: Collect actual weather data (post-hoc), flow data, and optionally soil moisture or NDVI data
4. Reconciliation layer: Compare predicted vs. actual water delivery and predicted vs. observed plant outcomes
5. Calibration layer: Adjust model parameters (DU correction factor, PR correction factor, PF adjustment, soil infiltration rate) based on accumulated discrepancy data
6. Confidence layer: Track model accuracy over time; flag zones where the model consistently fails (indicating a fundamental assumption error requiring human inspection)

---

6. Novel Data Sources

6.1 Utility Smart Meter Data

Advanced metering infrastructure (AMI) is increasingly deployed by water utilities, creating new data sources for irrigation optimization:

Disaggregated Water Use:

• AMI smart meters capture detailed and frequent (hourly or sub-hourly) water consumption data
• Disaggregation algorithms separate indoor use (showers, laundry, dishwashers) from outdoor use (irrigation, pools, hose bibs)
• Platforms like Dropcountr and WaterSmart provide customer-facing portals with outdoor use analytics
• Dropcountr PLUS combines AMI data with user profile surveys about appliances and irrigation systems to generate per-use-category breakdowns

Integration Opportunities:

• Irrigation runtime verification: Utility meter data can verify that the irrigation controller actually ran the scheduled program (detects controller failures, power outages, or override events)
• Leak detection: Continuous flow during non-irrigation periods indicates leaks; Flume API (flumewater.com/api) enables programmatic access to real-time flow data
• Water budget compliance: Actual outdoor water use from utility data can be compared against the MWELO water budget (ETWU) in real time
• Neighborhood benchmarking: Utility data enables property-to-property comparisons of outdoor water use normalized by landscape area, plant palette, and ET zone

API Access:

• Flume: Personal API access with Client ID/Client Secret; integrates with Home Assistant, Alexa, Google Home, Orbit
• Dropcountr: Utility-deployed; customer access via utility portal
• Phyn: API access for integration partners
• Home Assistant integrations available for Flume, Phyn, Moen Flo

6.2 NDVI and Plant Health Imagery

NDVI (Normalized Difference Vegetation Index) provides a remote measure of plant health that can serve as a feedback signal for irrigation scheduling:

Drone-Based NDVI:

• Resolution: Centimeter-scale (1-5 cm per pixel)
• Frequency: On-demand (typically monthly for landscape management)
• Cost: $50-$300 per property per flight (decreasing rapidly)
• Advantage: Captures plant-level detail invisible in satellite imagery; can detect individual stressed plants within a zone
• Use case: High-value commercial landscapes, resort/hotel grounds, theme parks, golf courses

Satellite-Based NDVI:

• Sentinel-2: 10m resolution, 5-day revisit (free)
• Landsat: 30m resolution, 8-16 day revisit (free via OpenET)
• Commercial: Planet Labs (3m daily), Maxar (sub-meter)
• Use case: Portfolio-level monitoring for landscape management companies; flag properties needing attention without site visits

Integration with Irrigation Scheduling: NDVI trends over time can indicate whether the current irrigation schedule is adequate:

• Declining NDVI during growing season = potential under-irrigation (or disease/pest issues)
• Stable or increasing NDVI = irrigation appears adequate
• Very high NDVI in water-stressed regions = potential over-irrigation (encouraging excessive growth)

6.3 Runoff Detection

Runoff is the primary failure mode for irrigation scheduling -- applying water faster than the soil can absorb it wastes water, causes erosion, and pollutes stormwater:

Current Approaches:

• Cycle-soak calculations based on soil infiltration rate and slope (implemented in QWEL formula chain)
• Rain sensors that interrupt irrigation during active rainfall
• Soil moisture sensors at saturation threshold

Emerging Approaches:

• Visual runoff detection: Camera-based systems (not yet commercial for residential) that detect water flowing off landscape areas
• Downstream flow monitoring: Sensors in storm drains that detect irrigation-sourced flow (municipal water conservation programs)
• Soil infiltration feedback: Combining soil moisture rate-of-change data with irrigation runtime data to calculate actual vs. assumed infiltration rate and adjust cycle-soak parameters accordingly

6.4 Neighborhood and Fleet Aggregation

Social Comparison Effect: Research demonstrates that social comparison has a greater effect when related to the behavior of a geographically closer community. Neighborhood-level water use comparisons can drive 5-15% water savings through behavioral nudges.

Fleet Aggregation for Landscape Companies: A landscape management company with 200+ residential clients in the same climate zone can aggregate data to:

• Identify optimal regional watering schedules by comparing plant health outcomes across clients
• Detect properties that deviate significantly from the fleet average (potential system issues)
• Calibrate plant factors and ET models using the fleet as a natural experiment
• Benchmark new properties against the fleet to suggest initial schedules before site-specific data accumulates

---

7. Digital Twin Concepts

7.1 Current State of Digital Twins in Irrigation

Digital twin technology for irrigation is emerging but has yet to achieve broad adoption. Publication trends show 1 paper in 2021, 2 in 2022, and 4 each in 2023 and 2024, indicating early-stage but accelerating interest.

Definition for Landscape Irrigation: A digital twin of a landscape irrigation system is a virtual representation that mirrors the physical system's components (pipes, valves, heads, soil, plants) and dynamically simulates water flow, soil moisture dynamics, plant water uptake, and evapotranspiration in response to weather, scheduling inputs, and system state changes.

7.2 Soil Water Balance Modeling

The foundation of an irrigation digital twin is a soil water balance model:

HYDRUS-1D/2D/3D:

• Numerically solves Richards' equation for variably-saturated water flow
• Simulates heat and solute transport
• Calibration accuracy: RMSE < 0.05 cm3/cm3 for water content, RMSE < 0.1 mg/cm3 for salinity
• Recent research: Modeling root water uptake of landscape groundcovers with HYDRUS-1D (2025 publication in Agricultural Water Management)
• Open source (public domain, USDA-ARS)

SWAP Model (Soil-Water-Atmosphere-Plant):

• Simulates soil water, heat, and solute dynamics coupled with plant growth
• Calibrated and validated using field experiment data
• Used in reinforcement learning research as the simulation environment for training irrigation policies
• Can simulate and optimize irrigation schedules after calibration

FAO-56 Soil Water Budget (Simplified):

• Single or dual crop coefficient approach
• Daily soil water balance tracking (inputs: ET, rainfall, irrigation; outputs: soil moisture, drainage, runoff)
• Implemented in pyfao56 Python package (USDA-ARS)
• Lower computational cost than HYDRUS/SWAP; suitable for real-time scheduling applications

7.3 Landscape Digital Twin Architecture

A digital twin for landscape irrigation would combine:

1. Design model: Head positions, arcs, radii, GPM, pipe layout, valve zones (already computed in SimplyScapes irrigation design engine)
2. Soil model: Layer-specific properties (texture, field capacity, wilting point, infiltration rate, bulk density) for each zone
3. Plant model: Species, root depth, plant factor, canopy coverage, growth stage, dormancy thresholds
4. Weather driver: Real-time and forecast weather data (ETo, rainfall, temperature, wind)
5. Hydraulic model: Pipe network, pressure distribution, flow rates, head performance curves
6. Water balance simulation: Daily or sub-daily simulation of soil moisture at root zone depth for each zone
7. Feedback integration: Sensor data (if available) used to calibrate and correct model state

Key Differentiator for SimplyScapes: SimplyScapes already has components (1), (3), and partially (5) from the irrigation design engine. The design-computed DU and PR provide the hydraulic model inputs. Adding a soil water balance model (component 6) using FAO-56 methods would create a basic digital twin without requiring any sensor hardware -- calibrated entirely from design data, manufacturer specs, and public weather data.

7.4 Scenario Simulation

A digital twin enables "what-if" scenario analysis:

• "What happens to water use if I change from Kentucky bluegrass to tall fescue?" (change PF, recalculate seasonal schedule)
• "What if I add a rain sensor vs. upgrading to a weather-based controller?" (simulate rain-skip events from historical weather data)
• "How much water would I save by improving DU from 71% to 85%?" (change DU parameter, recalculate runtimes)
• "What is the optimal cycle-soak split for my clay soil on a 10% slope?" (simulate infiltration and runoff at different cycle lengths)

7.5 Calibration and Validation

Digital twin accuracy depends on calibration against real-world observations:

• Zero-sensor calibration: Use design parameters + regional soil survey data (USDA Web Soil Survey) + public weather data. Accuracy: estimated +/- 20-30% of actual water needs (adequate for initial scheduling)
• Flow-sensor calibration: Add flow meter data to reconcile predicted vs. actual water delivery. Accuracy improvement: +/- 10-15%
• Soil-sensor calibration: Add soil moisture sensor data to calibrate soil hydraulic parameters. Accuracy improvement: +/- 5-10%
• Satellite calibration: Use NDVI/ET data to validate plant health outcomes over seasonal timescales

---

8. Open Source and API Ecosystem

8.1 ET Calculation Libraries

| Library | Language | Method | Maintained | Package Manager | Notes | |---------|----------|--------|------------|-----------------|-------| | pyfao56 | Python | FAO-56 (single & dual crop coeff) | Active (v1.4.0, 2025) | PyPI, conda-forge | USDA-ARS developed; includes soil water balance; crop coefficient tables | | PyETo | Python | FAO-56 PM, Hargreaves, Thornthwaite | Inactive | Source only | Not installable via pip; must incorporate source | | aquacrop-eto | Python | FAO-56 PM, Hargreaves, Thornthwaite | Active | PyPI | Fork of PyETo; pip-installable | | PyEt | Python | 20 PET methods | Active | PyPI | Supports time series and gridded datasets | | penmon | Python | FAO-56 PM | Active | PyPI | Weather station class abstraction | | AquaCrop | Python | FAO AquaCrop model | Active | PyPI | Full crop-water productivity model |

No JavaScript/TypeScript ET libraries exist on npm. This represents both a gap and an opportunity: SimplyScapes could implement FAO-56 Penman-Monteith in TypeScript for server-side ET calculation, eliminating the need for a Python microservice.

8.2 Weather Data APIs

| Service | ETo Available | Resolution | Coverage | Cost | Rate Limit | Forecast Range | |---------|---------------|------------|----------|------|------------|----------------| | Open-Meteo | Yes (et0_fao_evapotranspiration) | 1km | Global | Free (<10K calls/day) | 10,000/day | 16 days | | gridMET | Yes (alfalfa ET) | 4km | CONUS | Free | Unlimited download | Historical only | | PRISM | No (inputs only) | 800m | CONUS | Free | Unlimited | Historical only | | USU Climate Center | Yes (monthly ETo) | Zip code | Western US | Free | Unknown | Historical normals | | CIMIS | Yes (daily ETo) | Station-based | California | Free | Registration | Historical + 7-day | | OpenWeatherMap | No (compute from inputs) | Point-based | Global | Free tier available | 1,000/day (free) | 8 days | | Visual Crossing | Yes (computed) | Point-based | Global | Free tier (1K/day) | 1,000/day | 15 days | | FrogCast | Yes | Field-level | Regional | Paid | API key | Probabilistic |

8.3 Satellite Data APIs

| Service | Data Product | Resolution | Temporal | Coverage | Cost | API Type | |---------|-------------|------------|----------|----------|------|----------| | OpenET | Field-scale ET | 30m | Daily/Monthly | CONUS | Free (100 queries/mo) | REST | | Google Earth Engine | Landsat, Sentinel, MODIS | 10-500m | Variable | Global | Free (research) | Python/JS | | Sentinel Hub | Sentinel-2 NDVI | 10m | 5-day | Global | Free tier (30K units/mo) | REST | | Planet Labs | Daily NDVI | 3m | Daily | Global | Paid ($) | REST | | USGS EarthExplorer | Landsat | 30m | 8-16 day | Global | Free | Bulk download |

8.4 Soil Data Services

| Service | Data | Resolution | Coverage | API | |---------|------|------------|----------|-----| | USDA Web Soil Survey | Soil properties, texture, infiltration | Polygon-based | US | SOAP/REST (SDA) | | SSURGO | Detailed soil survey | 1:12,000 - 1:63,360 | US | Download/SDA | | SoilGrids | Global soil properties | 250m | Global | REST/WCS | | ISRIC | Soil hydraulic parameters | 250m | Global | REST |

8.5 Controller APIs

| Controller | API Type | Schedule Push | Usage Read | Rate Limit | Auth Model | |------------|----------|---------------|------------|------------|------------| | Rachio | REST v2 | Yes | Yes | 1,700/day | OAuth 2.0 | | Hydrawise (Hunter) | REST v1.5 / GraphQL v2 | Yes (v2) | Yes | Rate-limited | API key / OAuth | | OpenSprinkler | REST | Yes | Yes | None (local) | Password | | Rain Bird (IQ4) | Proprietary | Limited | Limited | N/A | Dealer access | | Orbit B-hyve | Unofficial REST | Yes (reverse-engineered) | Yes | Unknown | OAuth | | Weathermatic SmartLink | Proprietary | Via cloud | Yes | N/A | Dealer/partner |

8.6 Open-Source Irrigation Controllers

OpenSprinkler:

• Fully open-source firmware (GitHub: OpenSprinkler/OpenSprinkler-Firmware)
• REST API for all operations (schedule, zone control, sensor data)
• Weather adjustment methods: Apple (default), AccuWeather, PirateWeather, OpenWeatherMap, Open-Meteo, DWD, WUnderground
• ETo adjustment method supported across all weather providers
• Node.js-based weather service (OpenSprinkler/OpenSprinkler-Weather)
• Hardware: AC, DC, and Latch models; integrates with standard solenoid valves
• Community: Active user base, Home Assistant integration
• Cost: ~$150-$180 for controller hardware

RainMachine:

• Linux-based smart controller with local processing
• Open API for third-party integration
• Supports custom weather parsers (Python)
• Community-developed integrations

8.7 Simulation and Modeling Tools

| Tool | Purpose | Language | License | Notes | |------|---------|----------|---------|-------| | HYDRUS-1D | Soil water flow simulation | Fortran/C | Free (public domain) | USDA-ARS; Richards equation solver | | SWAP | Soil-water-atmosphere-plant | Fortran | Free | Wageningen University | | AquaCrop | Crop water productivity | Python (pyAquaCrop) | Free | FAO model | | DSSAT | Crop simulation | Fortran | Free (registration) | Decision support for crop management | | geeSEBAL | Satellite ET (SEBAL model) | JavaScript/Python | Open source | Google Earth Engine implementation | | eeMETRIC | Satellite ET (METRIC model) | JavaScript | Open source | Google Earth Engine; part of OpenET |

---

9. Technology Readiness Map

| Technology | TRL | Cost (Residential) | Accuracy | Integration Complexity | Time to Value | |------------|-----|--------------------|---------|-----------------------|---------------| | ETo-based scheduling (design DU) | 7 | $0 (software only) | +/- 20-30% | Low (API + math) | Weeks | | Weather forecast rain skip | 8 | $0 (API data) | Variable (forecast dependent) | Low | Weeks | | Freeze protection (temp threshold) | 9 | $0 (API data) | High (simple threshold) | Very Low | Days | | Flow meter leak detection | 8 | $100-$300/zone | +/- 2% flow | Medium (hardware + API) | Months | | Soil moisture sensor (capacitance) | 7 | $80-$200/zone | +/- 3-5% VWC | Medium (hardware + calibration) | Months | | Soil moisture sensor (TDR) | 9 | $300-$2,000/zone | +/- 1% VWC | Medium (hardware + calibration) | Months | | On-site weather station | 8 | $400-$1,500 | Best (on-site PM) | Medium (hardware + mounting) | Weeks | | OpenET satellite ET | 6 | $0 (free API) | +/- 17% monthly (cropland) | Medium (API + interpretation) | Months | | ECOSTRESS ET | 5 | $0 (free data) | Varies (70m resolution) | High (data processing) | Months | | Sentinel-2 NDVI monitoring | 6 | $0 (free data) | N/A (relative metric) | High (image processing) | Months | | Drone NDVI assessment | 7 | $50-$300/flight | High (cm resolution) | High (operational) | Per-flight | | ML soil moisture prediction | 4 | $0 (software) | Varies (+/- 5-15%) | High (training data) | Months-Years | | Deep RL scheduling | 3 | $0 (software) | Potentially best | Very High (sim environment) | Years | | Digital twin (basic FAO-56) | 4 | $0 (software) | +/- 20-30% (uncalibrated) | Medium-High | Months | | Digital twin (sensor-calibrated) | 3 | $500-$5,000/property | +/- 5-10% | Very High | Months-Years | | Utility smart meter integration | 5 | $0 (utility data) | +/- 1% (meter accuracy) | High (utility API access) | Months | | Neighborhood aggregation | 3 | $0 (fleet data) | N/A (comparative) | Medium (data pipeline) | Years |

TRL Scale: 1=Basic principles, 3=Proof of concept, 5=Technology validation, 7=System prototype, 9=Commercial deployment

---

10. Alternative Embodiments for Defensive Disclosure

The following concrete approaches should be covered in the defensive disclosure to establish prior art. Each builds on SimplyScapes' novel design-time DU/PR computation combined with one or more advanced techniques:

10.1 Design-DU + Satellite ET Validation

A system that computes irrigation schedules from design-time DU and PR, using satellite-derived ET (OpenET, ECOSTRESS, or Sentinel-2) to validate and calibrate the schedule over time. The satellite data provides a ground-truth comparison: if satellite ET estimates for the property consistently exceed or fall below the design-based ET calculation, the system adjusts the regional ETo correction factor for that specific property.

10.2 Design-DU + Probabilistic Weather Integration

A system that generates base schedules from design-time DU/PR and ETo, then adjusts daily based on probabilistic weather forecasts. The system fetches 3-7 day forecast data from Open-Meteo or equivalent, calculates expected rainfall probability-weighted amounts, and reduces scheduled irrigation by the expected effective precipitation. The system also implements predictive ET (using forecast temperature, humidity, wind, and solar radiation) rather than historical ET for proactive schedule adjustment.

10.3 Design-DU + Flow Meter Feedback Loop

A system that computes initial schedules from design parameters and then uses flow meter data (from Flume, Phyn, Bluebot, or controller-integrated flow sensors) to continuously calibrate the actual precipitation rate of each zone. Over time, the system learns the actual PR (which may differ from design PR due to pressure variation, nozzle wear, or installation deviations) and adjusts runtimes accordingly. The system also detects DU degradation by comparing flow consistency across cycles.

10.4 Design-DU + Soil Moisture Sensor Calibration

A system that uses design-computed DU/PR for initial schedule generation and then uses soil moisture sensor data to calibrate the soil water balance model. The sensor data provides ground-truth soil moisture measurements that allow the system to adjust soil hydraulic parameters (field capacity, wilting point, infiltration rate) for each zone, improving schedule accuracy over time without requiring the sensor data for ongoing operation (calibrate-then-remove approach).

10.5 Design-DU + ML-Enhanced ET Prediction

A system that trains a machine learning model (LSTM, XGBoost, or similar) to predict hyperlocal ET from limited inputs (temperature, elevation, season, latitude) using the design-based schedule outcomes (plant health observations, flow data, soil moisture readings) as training targets. The model learns site-specific microclimate effects (south-facing exposure, wind corridors, urban heat island) that regional ETo data misses.

10.6 Design-DU + Digital Twin Simulation

A system that creates a digital twin of the landscape irrigation system by combining the design model (head positions, DU, PR), soil survey data (USDA Web Soil Survey), plant database (WUCOLS plant factors, root depths), and weather data into a daily soil water balance simulation (FAO-56 dual crop coefficient method). The digital twin simulates soil moisture at root-zone depth for each zone and generates irrigation schedules that maintain moisture between field capacity and the management allowable depletion threshold. No physical sensors are required; the model is calibrated entirely from design data and public datasets.

10.7 Design-DU + Reinforcement Learning Optimization

A system that uses the digital twin (10.6) as a simulation environment for training a reinforcement learning agent to optimize irrigation schedules. The RL agent's state space includes simulated soil moisture, weather conditions, plant growth stage, and season. The action space is the daily irrigation amount per zone. The reward function balances water conservation, plant health maintenance, and regulatory compliance (MWELO water budget). The trained policy can be deployed on the controller for real-time scheduling decisions.

10.8 Design-DU + Fleet Learning Across Properties

A system that aggregates scheduling data, weather data, plant health outcomes, and controller usage patterns across a fleet of properties managed by a landscape company. The fleet data is used to train a collaborative model that improves scheduling accuracy for all properties in the fleet, particularly benefiting new properties with no historical data. The system identifies properties that are outliers (consistently higher or lower water use than fleet average for similar landscapes) and flags them for inspection.

10.9 Design-DU + Utility Meter Reconciliation

A system that uses utility smart meter data (via Flume API, Dropcountr, or utility AMI portal) to reconcile designed water budgets against actual consumption. The system compares the scheduled water delivery (computed from design DU/PR and ETo) against metered outdoor water use (disaggregated from total meter data). Persistent discrepancies trigger alerts: over-use may indicate leaks, manual overrides, or degraded system performance; under-use may indicate controller failures or skipped schedules.

10.10 Design-DU + NDVI Plant Health Feedback

A system that uses satellite (Sentinel-2, 10m) or drone NDVI data to assess plant health outcomes of the irrigation schedule over time. The system correlates NDVI trends with applied water volumes (from the design-based schedule) and adjusts plant factors (PF) for specific zones where the observed vegetation health does not match the expected response. Zones with declining NDVI despite adequate calculated irrigation may indicate incorrect plant factors, soil issues, or disease/pest problems.

10.11 Design-DU + Cycle-Soak Optimization from Soil Data

A system that uses USDA Web Soil Survey data (soil texture, infiltration rate class, slope from design topography) to compute optimal cycle-soak splits for each zone, then refines these splits based on observed runoff indicators (soil moisture rate-of-change patterns, flow meter data showing continued flow after valve close indicates pooled water draining back). The system adapts cycle-soak parameters seasonally as soil conditions change (compaction in summer, freeze-thaw loosening in spring).

10.12 Design-DU + Multi-Controller Coordination

A system that coordinates irrigation schedules across multiple controllers on the same property (or adjacent properties sharing a water supply) to optimize water pressure and flow distribution. Using the design's hydraulic model (pipe sizes, distances, head flow rates), the system ensures that simultaneous zone activations across controllers do not create pressure drops that would degrade DU below acceptable thresholds.

10.13 Design-DU + Water District Restriction Compliance

A system that automatically adjusts irrigation schedules to comply with water district restrictions (watering day limitations, time-of-day windows, seasonal budgets) while maintaining the design-computed water delivery target. The system redistributes the weekly water budget across allowed watering days and time windows, adjusting cycle-soak splits as needed to deliver the full calculated water volume within the permitted schedule.

---

11. Whitespace Analysis

11.1 Approaches Nobody is Patenting

Based on the patent landscape analysis (see SS-RR-2026-001 patent landscape paper and SmartRain FTO analysis), the following areas represent significant whitespace where no patents or patent applications were found:

1. Design-Time DU as a Scheduling Input No patent, publication, or product uses irrigation design geometry (head placement, arc, radius, spacing) to derive DU for scheduling purposes. Every existing system assumes DU comes from a field measurement (catch can test) or uses a default value. This is SimplyScapes' core novelty and the single most important claim to protect.

2. Software-Only Scheduling Without Hardware Dependencies All identified patents (SmartRain, ETwater/Husqvarna, Waterworks Inc) require physical hardware in the loop (controllers, sensors, flow meters). A pure software system that generates schedules from design data, manufacturer specifications, and public weather data has no patent coverage.

3. Design-Computed PR as a Scheduling Input Similar to DU, no system uses design-computed precipitation rate (derived from manufacturer nozzle specifications and head spacing geometry) as a direct scheduling input. Existing systems require the user to manually input PR or select from a dropdown of generic values.

4. Digital Twin from Design Data (No Sensors) Digital twin approaches in published research all assume sensor data for calibration. A digital twin calibrated entirely from design data (head positions, pipe layout, soil survey, plant database, weather API) with no sensor hardware is not described in any patent or publication.

5. Fleet-Level Plant Factor Calibration No system uses fleet data (outcomes across multiple properties) to calibrate species-specific plant factors. WUCOLS and SLIDE provide static, regionally-averaged values. A system that learns improved PF values from observed outcomes across a managed portfolio is novel.

6. Satellite Validation of Design-Based Schedules Using satellite ET or NDVI data to validate (not generate) irrigation schedules computed from design parameters is not described in any identified patent or product. All satellite ET applications focus on directly computing irrigation needs, not on validating a model that was built from design data.

7. Cross-Property Hydraulic Coordination No patent covers coordinating irrigation schedules across multiple properties that share water infrastructure (common in townhome communities, planned developments) using design hydraulic models.

8. MWELO Compliance Automation from Design Data No patent or product automatically generates MWELO-compliant irrigation schedules from the same design data used for the water budget compliance calculation. Current practice requires separate calculation of the water budget (MAWA/ETWU) and the operational schedule with no linkage.

11.2 Biggest Opportunities for Prior Art Establishment

Priority 1 (Critical -- include in defensive disclosure):

• Design-DU + any advanced technique (sensors, satellite, ML, digital twin)
• Software-only scheduling from design geometry
• Digital twin calibrated from design data alone
• Fleet learning for plant factor calibration

Priority 2 (Important -- include for comprehensive coverage):

• Probabilistic rain skip with design-based water budget reconciliation
• Utility meter reconciliation against design water budgets
• Satellite NDVI validation of design-based irrigation outcomes
• Multi-controller hydraulic coordination from design models

Priority 3 (Defensive -- include to prevent future blocking):

• RL-trained scheduling policies using design-based digital twin as environment
• Drone NDVI feedback loops for design parameter calibration
• Neighborhood aggregation for regional ET model correction
• Water district restriction optimization with design-computed constraints

---

12. Sources

| # | Type | Reference | URL / Location | |---|------|-----------|----------------| | 1 | Journal | AI-Driven Smart Irrigation and Resource Optimization (JSIAR, 2025) | https://jsiar.com/2025-May/JSIAR-M-25-05444.pdf | | 2 | Journal | Machine learning and digital twins in smart irrigation (Taylor & Francis, 2025) | https://www.tandfonline.com/doi/full/10.1080/27525783.2025.2562418 | | 3 | Journal | Comparative Analysis of Soil Moisture- and Weather-Based Irrigation Scheduling (PMC, 2024) | https://pmc.ncbi.nlm.nih.gov/articles/PMC11902337/ | | 4 | Journal | Low-Cost Soil Moisture Sensor for Real-Time Irrigation Scheduling (Wiley, 2026) | https://onlinelibrary.wiley.com/doi/full/10.1002/ird.70026 | | 5 | Journal | Calibration of Low-Cost Capacitive Soil Moisture Sensors (PMC, 2025) | https://pmc.ncbi.nlm.nih.gov/articles/PMC11768944/ | | 6 | Journal | Automated Low-Cost Soil Moisture Sensors: Trade-Off (MDPI Sensors, 2023) | https://www.mdpi.com/1424-8220/23/5/2451 | | 7 | Journal | Assessment of Low-Cost and Higher-End Soil Moisture Sensors (PMC, 2024) | https://pmc.ncbi.nlm.nih.gov/articles/PMC11435841/ | | 8 | Journal | Assessing the accuracy of OpenET satellite-based ET data (Nature Water, 2023) | https://www.nature.com/articles/s44221-023-00181-7 | | 9 | Website | OpenET Platform and Documentation | https://etdata.org/ | | 10 | Website | OpenET API Documentation | https://openet.gitbook.io/docs/ | | 11 | Website | OpenET FAQ | https://etdata.org/faq/ | | 12 | Report | USGS EROS Helps Assess OpenET Accuracy | https://www.usgs.gov/centers/eros/news/usgs-eros-helps-assess-openet-accuracy | | 13 | Journal | ECOSTRESS: NASA's Next Generation Mission (Water Resources Research, 2020) | https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2019WR026058 | | 14 | Data | ECOSTRESS Evapotranspiration DisALEXI 70m (NASA Earthdata) | https://www.earthdata.nasa.gov/data/catalog/lpcloud-eco3etalexi-001 | | 15 | Data | ECOSTRESS DisALEXI USDA 30m Global (NASA Earthdata) | https://www.earthdata.nasa.gov/data/catalog/lpcloud-eco3etalexiu-001 | | 16 | Journal | Evaluation of ECOSTRESS ET over heterogeneous landscapes (ScienceDirect, 2022) | https://www.sciencedirect.com/science/article/abs/pii/S002216942201040X | | 17 | Journal | Estimating Urban ET at 10m Resolution Using Sentinel-2 (MDPI Remote Sensing, 2021) | https://www.mdpi.com/2072-4292/13/11/2048 | | 18 | Journal | City-wide high-resolution mapping of ET (ScienceDirect, 2023) | https://www.sciencedirect.com/science/article/pii/S003442572300038X | | 19 | Journal | Sentinel-2 MSI data to monitor crop irrigation (ScienceDirect, 2020) | https://www.sciencedirect.com/science/article/pii/S0303243420302531 | | 20 | Journal | Deep reinforcement learning for irrigation scheduling (PLOS Water, 2023) | https://journals.plos.org/water/article?id=10.1371/journal.pwat.0000169 | | 21 | Journal | Irrigation optimization with deep RL -- Portugal (ScienceDirect, 2022) | https://www.sciencedirect.com/science/article/pii/S0378377422000270 | | 22 | Journal | Smart Irrigation Scheduling Using Crop Model and Improved Deep RL (MDPI Agriculture, 2025) | https://www.mdpi.com/2077-0472/15/24/2569 | | 23 | Journal | Assessing the value of deep RL for irrigation scheduling (ScienceDirect, 2024) | https://www.sciencedirect.com/science/article/pii/S277237552400008X | | 24 | Journal | Real-Time Irrigation Scheduling Based on Weather Forecasts (AGU WRR, 2023) | https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2023WR035810 | | 25 | Journal | Analysis framework for irrigation decisions using ensemble weather forecasts (Springer, 2022) | https://link.springer.com/article/10.1007/s00271-022-00807-w | | 26 | Journal | Enhancing irrigation water productivity using ensemble weather forecasts (ScienceDirect, 2024) | https://www.sciencedirect.com/science/article/abs/pii/S0022169424010060 | | 27 | Website | Rain Bird Weather Based Irrigation | https://www.rainbird.com/weatherbasedirrigation | | 28 | Website | FrogCast Agriculture Weather API | https://frogcast.com/agriculture/ | | 29 | Journal | Development of a Digital Twin for smart farming (J. Cleaner Production, 2023) | https://www.sciencedirect.com/science/article/abs/pii/S0959652623000781 | | 30 | Journal | IoT-digital twin-inspired smart irrigation (ScienceDirect, 2023) | https://www.sciencedirect.com/science/article/abs/pii/S2210537923001026 | | 31 | Journal | Harnessing Digital Twins for Sustainable Agricultural Water Management (MDPI Applied Sciences, 2025) | https://www.mdpi.com/2076-3417/15/8/4228 | | 32 | Journal | Digital Twin Applications in the Water Sector (MDPI Water, 2025) | https://www.mdpi.com/2073-4441/17/20/2957 | | 33 | Article | Digital twins transforming water management (WEF, 2024) | https://www.weforum.org/stories/2024/11/why-digital-twins-might-transform-the-world-of-water-management/ | | 34 | Software | pyfao56: FAO-56 evapotranspiration in Python (v1.4.0) | https://pypi.org/project/pyfao56/ | | 35 | Journal | pyfao56 paper (SoftwareX, 2022) | https://www.sciencedirect.com/science/article/pii/S2352711022001261 | | 36 | Software | PyETo: Python ETo calculation library | https://github.com/woodcrafty/PyETo | | 37 | Software | aquacrop-eto (fork of PyETo) | https://github.com/aquacropos/aquacrop-eto | | 38 | Software | penmon: FAO-56 weather station class | https://github.com/sherzodr/penmon | | 39 | Website | Open-Meteo Weather API | https://open-meteo.com/ | | 40 | Website | Open-Meteo Historical Weather API | https://open-meteo.com/en/docs/historical-weather-api | | 41 | Website | gridMET -- Climatology Lab | https://www.climatologylab.org/gridmet.html | | 42 | Software | PyGridMET: Daily climate data through GridMET | https://docs.hyriver.io/readme/pygridmet.html | | 43 | Data | gridMET on Google Earth Engine | https://developers.google.com/earth-engine/datasets/catalog/IDAHO_EPSCOR_GRIDMET | | 44 | Website | HydroPoint WeatherTRAK ET Pro3 | https://www.hydropoint.com/weathertrak/products/weathertrak-et-pro3/ | | 45 | Website | WeatherTRAK Central Cloud-Based Irrigation Control | https://www.hydropoint.com/weathertrak/products/weathertrak-central/ | | 46 | Website | CropX Agronomic Farm Management System | https://cropx.com/ | | 47 | Website | CropX Soil Moisture Sensor and Telemetry Hardware | https://cropx.com/cropx-system/hardware/ | | 48 | Website | CropX Irrigation Planning | https://cropx.com/cropx-system/irrigation-planning/ | | 49 | Website | Rachio Flex Daily Moisture Levels | https://support.rachio.com/en_us/what-are-moisture-levels-(flexible-daily-schedules)-SJ19DUJYw | | 50 | Website | Flume Smart Water Monitor | https://flumewater.com/ | | 51 | Website | Phyn Plus Smart Water Assistant | https://phyn.com/products/phyn-plus-smart-water-assistant-shutoff-v2 | | 52 | Website | Bluebot Smart Water Meter | https://www.bluebot.com/ | | 53 | Website | Moen Flo Smart Water Monitor | https://shop.moen.com/pages/flo-smart-water-monitor | | 54 | Website | Hunter HC Flow Meter | https://www.hunterirrigation.com/irrigation-product/sensors/hc-flow-meter | | 55 | Website | OpenSprinkler Open-Source Controller | https://opensprinkler.com/product/opensprinkler/ | | 56 | Software | OpenSprinkler Firmware (GitHub) | https://github.com/opensprinkler/OpenSprinkler-Firmware | | 57 | Software | OpenSprinkler Weather Service (GitHub) | https://github.com/OpenSprinkler/OpenSprinkler-Weather | | 58 | Software | geeSEBAL: Open-source SEBAL on Google Earth Engine | https://github.com/gee-hydro/geeSEBAL | | 59 | Software | eeMETRIC on Google Earth Engine (OpenET) | https://developers.google.com/earth-engine/datasets/catalog/OpenET_EEMETRIC_CONUS_GRIDMET_MONTHLY_v2_0 | | 60 | Website | USGS Landsat Collection 2 Provisional Actual ET | https://www.usgs.gov/landsat-missions/landsat-collection-2-provisional-actual-evapotranspiration-science-product | | 61 | Journal | Influence of Landsat Revisit Frequency on ET for Agricultural Water Management (ResearchGate, 2019) | https://www.researchgate.net/publication/330948303 | | 62 | Journal | Improving spatiotemporal resolution of ET via data fusion (Springer Irrigation Science, 2022) | https://link.springer.com/article/10.1007/s00271-022-00799-7 | | 63 | Website | Dropcountr Smart Utilities (AMI) | https://www.dropcountr.com/smart-utilities/ | | 64 | Journal | Smart Water Meters: A Comprehensive Review (MDPI Water, 2024) | https://www.mdpi.com/2073-4441/16/1/113 | | 65 | Journal | Neighborhood social comparison and water use efficiency (Frontiers in Water, 2022) | https://www.frontiersin.org/journals/water/articles/10.3389/frwa.2022.821896/full | | 66 | Data | California Efficient Outdoor Water Uses Data | https://data.ca.gov/dataset/data-for-calculating-efficient-outdoor-water-uses | | 67 | Journal | Insights into Efficient Irrigation of Urban Landscapes (MDPI Sustainability, 2022) | https://mdpi.com/2071-1050/14/3/1427/htm | | 68 | Website | EPA WaterSense Soil Moisture-Based Controllers | https://www.epa.gov/watersense/soil-moisture-based-irrigation-controllers | | 69 | Website | Ellenex Pressure Monitoring in Irrigation Systems | https://www.ellenex.com/solutions/pressure-monitoring-in-irrigation-systems | | 70 | Website | METER Group PS-1 Pressure Sensor | https://metergroup.com/products/ps-1/ | | 71 | Journal | HYDRUS-1D Software Package (USDA-ARS) | https://www.ars.usda.gov/arsuserfiles/20360500/pdf_pubs/P2119.pdf | | 72 | Journal | Modeling root water uptake of landscape groundcovers with HYDRUS-1D (Agric Water Mgmt, 2025) | https://www.sciencedirect.com/science/article/pii/S0378377425006869 | | 73 | Journal | Application of ML approaches in irrigation decision making -- review (Agric Water Mgmt, 2024) | https://www.sciencedirect.com/science/article/pii/S0378377424000453 | | 74 | Journal | AI-driven irrigation systems: systematic review (ScienceDirect, 2025) | https://www.sciencedirect.com/science/article/pii/S2772375525002151 | | 75 | Journal | ML for agricultural water management -- review (J Hydroinformatics, 2025) | https://iwaponline.com/jh/article/27/3/474/107443/ | | 76 | Website | Flume Home Assistant Integration | https://www.home-assistant.io/integrations/flume/ | | 77 | Patent | US9307706B2 -- SmartRain Irrigation Management | https://patents.google.com/patent/US9307706B2 | | 78 | Patent | US11839184B2 -- SmartRain AI Irrigation System | https://patents.google.com/patent/US11839184B2 | | 79 | Patent App | US20250048979A1 -- Waterworks Inc AI Scheduling | https://patents.google.com/patent/US20250048979A1 | | 80 | Patent | US10028454B2 -- Husqvarna/ETwater Cloud Irrigation | https://patents.google.com/patent/US10028454B2 | | 81 | Research | SS-RR-2026-001 Patent Landscape | docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/plant-specific-drip-irrigation-intelligence/research/supporting/patent-landscape.md | | 82 | Research | SS-RR-2026-001 Adjacent Market Scan | docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/plant-specific-drip-irrigation-intelligence/research/supporting/adjacent-market-scan.md | | 83 | Research | SS-RR-2026-001 Competitive Analysis (Commercial) | docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/plant-specific-drip-irrigation-intelligence/research/supporting/competitive-analysis-commercial.md | | 84 | Research | SS-RR-2026-001 Controller Integration | docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/plant-specific-drip-irrigation-intelligence/research/supporting/controller-integration.md | | 85 | Journal | Soil moisture sensors for irrigation scheduling (UMN Extension) | https://extension.umn.edu/irrigation/soil-moisture-sensors-irrigation-scheduling | | 86 | Website | DOE Water-Efficient Technology: Advanced Irrigation Controls | https://www.energy.gov/femp/water-efficient-technology-opportunity-advanced-irrigation-controls |

---

This supporting paper was produced as part of SS-RP-2026-002 research. It is intended to inform the defensive disclosure (SS-TD-2026-002) with comprehensive prior art coverage of advanced irrigation scheduling techniques beyond the Phase 1 ETo-based implementation.

Vertical Competitor Analysis: Automated Turf Irrigation Scheduling

Date: 2026-03-01 | Status: complete Related plan: docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/automated-turf-irrigation-scheduling/research/plan.md ClickUp: Automated Turf Irrigation Scheduling from Design-Time Intelligence Scope: 15 companies analyzed -- 11 named competitors + 4 discovery-phase additions Cross-references: SS-RR-2026-001 competitive analyses (residential + commercial)

---

Executive Summary

This analysis examines how 15 companies approach irrigation scheduling -- specifically, how they compute watering schedules, whether they accept Distribution Uniformity (DU) as an input, how they handle per-species plant factors, what APIs exist for schedule integration, and where gaps remain.

The findings reinforce and extend SS-RR-2026-001's core conclusion: every product operates at the zone level, and none bridge the gap between irrigation design and irrigation scheduling. More specifically for turf scheduling:

1. No product accepts design-computed DU as a scheduling input. Consumer controllers (Rachio, Orbit) use default efficiency assumptions or require manual catch-can testing. Commercial platforms (WeatherTRAK, Weathermatic) accept user-entered DU but require field measurement. Design tools (Land F/X, IrriCad) compute DU but do not generate operational schedules.

2. No product uses species-specific turf plant factors for scheduling. All controllers use broad plant-type categories (e.g., "cool season turf," "warm season turf") with preset crop coefficients. None integrate WUCOLS species-level data or differentiate between Kentucky bluegrass (Kc=0.80) and bermudagrass (Kc=0.60) at the scheduling level.

3. The Rachio API is the most viable integration target for pushing design-derived schedules. It supports schedule rule creation, zone-level moisture control (setMoisturePercent), manual zone start/stop, and seasonal adjustment -- all via a public REST API with 1,700 calls/day.

4. The design-to-schedule gap is the core whitespace. Design tools know DU and PR but don't schedule. Controllers schedule but don't know DU or PR (except via manual input). SimplyScapes is uniquely positioned to close this gap by flowing design-computed DU and PR directly into the QWEL formula chain.

---

Cross-Reference: Validated Findings from SS-RR-2026-001

The following findings were established in the plant-specific drip irrigation research (SS-RR-2026-001 competitive analyses, residential + commercial) and are treated as validated context. They are not re-researched here but are cross-referenced where they inform turf scheduling analysis.

| Finding | Source | Scheduling Relevance | |---------|--------|---------------------| | All controllers operate at zone level only | SS-RR-2026-001 residential, all 5 companies | Turf scheduling inherits same limitation -- mixed cool/warm season zones get one schedule | | Rachio API v2 supports setMoisturePercent per zone, 1,700 calls/day | SS-RR-2026-001 residential, Rachio section | Primary integration endpoint for pushing design-computed schedules | | Hydrawise has v1.5 REST + v2 GraphQL (commercial, oAuth2) APIs | SS-RR-2026-001 residential, Hunter section | Secondary integration target; rate limits more restrictive than Rachio | | No competitor derives DU from design geometry | SS-RR-2026-001 residential + commercial, cross-cutting | Core novelty of SimplyScapes approach remains uncontested | | Consumer controllers don't accept DU as input | SS-RR-2026-001 residential, all companies | Only commercial systems accept user-entered DU; none compute it | | WUCOLS is public domain; MWELO formula is government regulation | SS-RR-2026-001 commercial, WaterWonk section | Plant factor data and compliance math are freely usable | | Netafim GrowSphere is the closest analog to lifecycle-aware scheduling | SS-RR-2026-001 residential, Netafim section | Pattern for growth-stage adjustments applicable to turf establishment | | Weathermatic SmartLink Connect manages competitor controllers | SS-RR-2026-001 commercial, Weathermatic section | Platform play; signals market moving beyond hardware lock-in | | ETwater/Jain claims AI/ML but operates at zone level | SS-RR-2026-001 commercial, ETwater section | Despite ML branding, plant type remains a zone-level categorical input | | Calsense IMaaS is a validated business model for irrigation-as-a-service | SS-RR-2026-001 commercial, Calsense section | Subscription model precedent for SimplyScapes scheduling service |

---

Competitor Analysis

1. Rachio (Flex Daily / Flex Monthly)

How they approach scheduling

Rachio's Flex Daily algorithm is the most technically sophisticated consumer scheduling system. It maintains a virtual soil moisture balance per zone using the following logic:

Soil Moisture = Previous Balance - ETc + Precipitation + Irrigation
ETc = ET0 x Kc (crop coefficient per zone)
Irrigation triggers when moisture drops below MAD threshold

Zone-level inputs: Soil type, slope, sun/shade exposure, vegetation type (lawn, shrubs, trees, annuals, perennials), root depth, crop coefficient (Kc), available water capacity (AWC), allowed depletion percentage (MAD), nozzle precipitation rate, and irrigation efficiency.

Three schedule modes:

• Flex Daily: Fully dynamic daily decisions per zone -- the most advanced mode. Determines both when and how long to water.
• Flex Monthly: Monthly adjustment of a baseline schedule -- less dynamic but more predictable for users.
• Fixed: Static schedule with weather skip overlays (rain, wind, freeze, saturation skips).

DU/Efficiency handling: Rachio uses an "efficiency" parameter per zone (default ~70%) which is analogous to DU but is not labeled as such. The formula incorporates it as: Watering Time = 60 x Irrigation Amount / (sqrt(efficiency) x nozzle PR). The default nozzle PR is 1.0 in/hr. Rachio's community forums are filled with users struggling because the default efficiency and PR assumptions don't match their actual systems. Rachio explicitly recommends catch-cup tests to determine actual PR and efficiency -- they do not compute these from design data.

Species handling: Vegetation type is a broad category (e.g., "Cool Season Grass," "Warm Season Grass"). The corresponding crop coefficient (Kc) is preset for each category. Users can manually adjust Kc via a "Crop Coefficient" slider, but there is no species-level plant database. A zone with Kentucky bluegrass and a zone with tall fescue both select "Cool Season Grass" and receive the same Kc.

Strengths

• Most advanced consumer ET-based scheduling algorithm with transparent soil moisture tracking
• Excellent public REST API (see API section below)
• No subscription fees -- all smart features included with hardware ($200-230)
• Strong Home Assistant integration and smart home ecosystem
• Weather Intelligence Plus: automatic rain, wind, freeze, saturation skips
• Cycle & Soak to prevent runoff on slopes and clay soils
• Large enthusiast community with detailed technical discussions

Gaps / Limitations

• No DU input from design: Efficiency is a manual percentage; not derived from actual sprinkler placement geometry
• Default assumptions cause errors: Default nozzle PR of 1.0 in/hr and efficiency of ~70% are often wrong. Community forums are filled with over/under-watering complaints traced to incorrect defaults
• No species-level plant factors: Kc is tied to broad vegetation categories, not specific turfgrass species
• No growing season intelligence: No concept of species-specific dormancy thresholds; relies on weather skips rather than proactive season determination
• Cloud-dependent: All smart scheduling requires Rachio's cloud servers; no local API
• No plant database: Users must manually determine Kc, root depth, and other parameters

API / Integration

Rachio Public API v2.0 (api.rach.io/1/public) -- Bearer token auth, 1,700 calls/day:

| Endpoint | Method | Scheduling Relevance | |----------|--------|---------------------| | /public/zone/setMoisturePercent | PUT | Set zone soil moisture 0-1; triggers/suppresses Flex Daily watering | | /public/zone/setMoistureLevel | PUT | Set soil moisture in mm; more precise than percent | | /public/zone/start | PUT | Start a single zone with specific duration (seconds) | | /public/zone/start_multiple | PUT | Start multiple zones with individual durations and sort order | | /public/schedulerule/:id | GET | Read existing schedule rules (zones, durations, days) | | /public/schedulerule/skip | PUT | Skip next scheduled run | | /public/schedulerule/start | PUT | Start a schedule rule immediately | | /public/schedulerule/seasonal_adjustment | PUT | Adjust seasonal watering percentage | | /public/device/:id/current_schedule | GET | Check active schedule status | | /public/device/:id/forecast | GET | Read weather forecast data | | /public/device/:id/event | GET | Query device events by time range | | /public/device/rain_delay | PUT | Set rain delay with duration | | /public/device/stop_water | PUT | Stop all watering |

Key limitation: The API does not expose a createScheduleRule endpoint. You can read, start, skip, and seasonally adjust existing schedule rules, but creating new schedules programmatically requires using zone/start_multiple for ad-hoc runs or manipulating moisture levels to influence Flex Daily behavior. This means SimplyScapes would most likely: (a) set zone parameters (PR, efficiency) to match design-computed values, then let Flex Daily optimize; or (b) use start_multiple to execute pre-calculated runtimes on a timer basis from the SimplyScapes backend.

Webhook support: Rachio supports webhooks for zone/schedule/device events, enabling real-time feedback on watering activity.

Key takeaway for SimplyScapes

Rachio remains the primary integration target. The setMoisturePercent endpoint allows SimplyScapes to function as an "intelligence overlay" -- the design engine computes what moisture level each zone should be at, and Rachio handles the physical execution. The critical gap is that Rachio's Flex Daily uses a default efficiency/DU that is almost certainly wrong for most systems. SimplyScapes can close this gap by pushing the actual design-computed DU and PR into the zone configuration, making Flex Daily dramatically more accurate without requiring a catch-cup test.

---

2. Hunter (Hydrawise / Pro-HC / Centralus)

How they approach scheduling

Hunter offers three distinct platforms with different scheduling approaches:

Hydrawise (cloud platform for Pro-HC, HCC controllers):

• Three watering modes per zone: Time-Based (fixed durations with weather triggers), Smart ET (ET-based replacement), Virtual Solar Sync (seasonal solar radiation adjustment)
• Virtual Weather Station: Proprietary multi-source weather aggregation combining satellite data, real weather stations, atmospheric data from aircraft, and mobile phone barometric pressure
• Plant Type setting determines the fraction of reference ET required; Sun/Shade accounts for microclimate
• Plant type categories are coarse-grained (broad groups, not species)

Centralus (cloud platform for Pro-C, ICC2, ACC2 controllers):

• Separate platform from Hydrawise for different controller families
• Centralized management for commercial installations
• Weather-based scheduling adjustments

Pro-HC hardware features:

• HC Flow Meter enables real-time flow monitoring and leak detection
• Two-wire decoder system (EZ-DM module) supports up to 54 stations
• Up to 6 programs with limited per-zone program flexibility

Strengths

• Flow monitoring hardware provides ground-truth water delivery data
• Two-wire decoder system scales to large commercial installations
• Virtual Weather Station's multi-source aggregation may improve accuracy
• Professional contractor plan ecosystem for portfolio management
• Predictive Watering adjusts based on Weather Company data

Gaps / Limitations

• No DU input: Neither Hydrawise nor Centralus accepts DU as a scheduling parameter; efficiency is not user-configurable
• Coarse plant type categories: Plant types are broad groups (lawn, shrubs, trees), not species-specific
• No design awareness: System has no concept of head placement, spacing, or spray pattern geometry
• WiFi reliability issues: Multiple user reports of flaky connectivity requiring nightly controller reboots
• Weather override bugs: Inaccurate Virtual Weather Station data causes erroneous irrigation skips that cannot be overridden
• Subscription-gated features: Accurate weather station selection requires Enthusiast plan ($60/yr)
• API rate limits more restrictive than Rachio: 3 zone start/stop per 30 seconds; 30 total API calls per 5 minutes

API / Integration

Two APIs available:

| API | Auth | Use Case | Rate Limit | |-----|------|----------|-----------| | REST API v1.5 | API key per account | Homeowner/non-commercial | 30 calls / 5 min | | GraphQL API v2 | oAuth2 | Commercial, home automation, government | Rate limited (specific limits via agreement) |

REST v1.5 capabilities: Controller info, zone names/numbers, schedule status, manual zone start/stop/suspend. No zone moisture level control (unlike Rachio). No schedule creation endpoints.

GraphQL v2 capabilities: More comprehensive but requires commercial authorization via support@hydrawise.com. GDPR/CCPA compliant. Specific endpoint capabilities not publicly documented.

Home Assistant integration: Cloud-dependent; no local API available. No MQTT support. Integration relies on polling Hydrawise cloud servers.

Key takeaway for SimplyScapes

Hunter's flow monitoring hardware is uniquely valuable for validating design-computed DU against actual water delivery. If SimplyScapes integrates with Hunter, it could offer a "design DU vs. measured DU" comparison that quantifies installation quality. However, the API is more limited than Rachio's (no moisture control, more restrictive rate limits), making it a secondary integration target. The GraphQL v2 API could open more possibilities but requires commercial partnership.

---

3. Rain Bird (IQ4 / ESP-TM2 / ARC8)

How they approach scheduling

Rain Bird takes a weather-adjusted percentage scaling approach rather than true ET-based soil moisture tracking:

Consumer controllers (ARC8, ST8):

• Three independent programs (A, B, C) with four start times each
• Automatic Seasonal Adjust: Scales daily watering duration based on postal code weather data (historical averages + yesterday's weather + tomorrow's forecast). Claims up to 30% water savings.
• Zone configuration: plant type, plant density, soil type, slope, sun/shade
• Users set maximum run times for peak season; controller scales down from that baseline
• Not ET-based: Does not maintain a soil moisture balance model; adjusts time percentages rather than calculating water replacement needs

Professional platforms (IQ4 Central Control):

• Cloud-based (IQ4-Cloud) or desktop (IQ4-Desktop) central management
• Supports ET-based adjustments for commercial installations
• Batch editing across hundreds of stations; map-based visualization
• BMS (Building Management System) integration API
• Available for ESP-LXIVM, ESP-ME3, and other commercial controllers

Rain Bird 2.0 App (2025):

• Unified mobile app combining residential and IQ4 central control
• Real-time schedule changes from mobile
• Still uses percentage-scaling approach for consumer controllers

Strengths

• Largest irrigation manufacturer globally; massive contractor network
• Deepest hardware ecosystem (4-zone residential to 200+ station commercial)
• IQ4 is true enterprise-grade irrigation management with BMS API
• CirrusPRO golf platform uses volume-based "watering by rotations" -- conceptually adjacent to per-plant volume delivery
• ARC8 at ~$140 is competitively priced for entry-level smart scheduling
• No subscription required for consumer controllers

Gaps / Limitations

• Consumer scheduling is weakest of major competitors: Percentage scaling is less sophisticated than Rachio's or B-hyve's soil moisture depletion models. Reviewers consistently describe it as "dumbed down"
• No DU or efficiency input on consumer controllers
• No ET-based scheduling in consumer products; only weather-adjusted percentages
• No species-level plant factors: Broad categories only
• WiFi module issues: LNK2 WiFi module has limited range, requires separate purchase (~$70-100), and frequent resets
• Fragmented product line: Different apps and platforms for different controller families; no unified ecosystem
• Limited public API: No official REST API for consumer controllers

API / Integration

| Platform | API | Notes | |----------|-----|-------| | Consumer (ARC8, ST8) | None official | Community reverse-engineered: pyrainbird (Python), rainbird-api (Node.js) via local network protocol | | ESP-TM2 / ESP-ME3 | Via LNK2 module | Same local protocol as consumer; no cloud API | | IQ4 Central Control | BMS Integration API | Subscription required; enterprise only | | CirrusPRO | Proprietary | Golf course only |

Home Assistant: pyrainbird community integration via local network; works without cloud but is unofficial and unsupported.

Key takeaway for SimplyScapes

Rain Bird's consumer scheduling is the weakest competitive threat -- their percentage-scaling approach is demonstrably inferior to a proper ETo/DU formula chain. SimplyScapes would compete against Rain Bird rather than integrate with it (no usable API). However, Rain Bird's massive installed base means many SimplyScapes users will have Rain Bird hardware; the pyrainbird local API could enable a community-driven integration path. The IQ4 BMS API is relevant if SimplyScapes expands to commercial property management.

---

4. Orbit (B-hyve)

How they approach scheduling

B-hyve uses a WeatherSense algorithm that is technically similar to Rachio's Flex Daily but less configurable and less transparent:

ET calculation:

ETc = ET0 x Kp (plant factor) x Kmc (microclimate factor)

Soil moisture tracking:

• Field Capacity (FC), Permanent Wilting Point (PWP), Basic Infiltration Rate (BIR), Management Allowed Depletion (MAD, default 50%)
• Effective root depth (typically 50% of maximum root depth)
• Waters when depletion exceeds MAD threshold

Zone inputs: Soil type, plant type, sun/shade, slope, sprinkler type (spray, rotor, drip). System recognizes drip at 95% efficiency vs. 75% for spray/rotors.

Smart Watering vs. WeatherSense Weather Delays:

• Smart Watering: Autonomous scheduling decisions including when and how long to water, with daily ET-based adjustments
• WeatherSense Weather Delays: Simpler mode that only delays existing fixed schedules based on weather conditions (rain, freeze, wind)

Catch-cup test feature: B-hyve includes a built-in test mode that helps users measure actual precipitation rate and uniformity -- one of the few consumer controllers that even mentions uniformity to users.

Strengths

• Lowest price point in the smart controller market ($70-$120 range)
• No subscription fees; all WeatherSense features included
• Full ET-based soil moisture depletion model despite budget pricing
• Drip-specific efficiency setting (95% vs. 75%) shows basic drip awareness
• Built-in catch-cup test feature for precipitation rate measurement
• WaterSense and SWAT certified; may qualify for utility rebates
• B-hyve Pro for contractors: unlimited controllers, free

Gaps / Limitations

• No DU input: Efficiency is preset by sprinkler type, not configurable per zone from design data
• No species-level plant factors: Broad categories only
• No public API: Third-party integrations rely on reverse-engineered WebSocket connections to Orbit's servers; fragile and unsupported
• Less transparency: Smart watering calculations are opaque compared to Rachio's moisture graphs
• App stability issues: Crashes on interval scheduling; smart watering sometimes violates local water restrictions
• Corporate ownership uncertainty: Now owned by Husqvarna Water (formerly Hydro-Rain); direction unclear

API / Integration

No official public API. Unofficial endpoints discovered via reverse engineering:

| Endpoint Type | Notes | |--------------|-------| | Devices | Device listing and status | | Timelines | Scheduling data | | Landscapes | Zone configuration | | History | Watering history | | WebSocket | Real-time status (25-second reconnect intervals) |

Bearer token auth. Community implementations exist in Python, Node.js, and Hubitat. Integration is fragile and may break with firmware updates.

Home Assistant: Unofficial integration via reverse-engineered API; cloud-dependent.

Key takeaway for SimplyScapes

B-hyve proves ET-based scheduling can be delivered at sub-$100 pricing, setting the market expectation floor. Its built-in catch-cup test feature is notable -- it acknowledges that PR and uniformity matter, but puts the burden on the user to measure them physically. SimplyScapes eliminates this burden entirely through design computation. The lack of a public API makes B-hyve a poor integration target; SimplyScapes would more likely position as a replacement intelligence layer that outputs schedules users can manually configure in B-hyve.

---

5. Weathermatic (SmartLink)

How they approach scheduling

Weathermatic uses ET-based "Smart Watering Mode" with per-zone landscape inputs:

Per-zone inputs:

• Plant type: Turf (cool/warm season), shrubs, trees, flowers, mixed -- categorical, not species-specific
• Soil type: Clay, sand, loam (for cycle-soak calculation)
• Slope: 0-25 degrees (runoff prevention)
• Sprinkler type: Rotor, spray, drip (with preset or custom precip rate)
• Fine-tuning: Per-zone adjustment from -50% to +25% for shade, wind, sprinkler inefficiency

Scheduling algorithm:

• ET calculation using on-site weather sensor data + geographic location
• Likely Penman-Monteith or simplified ET model (not explicitly documented)
• Zone runtime = f(ET, plant type Kc, soil type, slope, sprinkler PR, fine-tuning adjustment)
• Cycle-soak automatically calculated from soil/slope inputs
• Adjusts daily based on weather sensor readings

SmartLink cloud platform: Remote monitoring, portfolio management (manage all sites from one dashboard), global commands, flow monitoring, leak detection, and water use reporting.

SmartLink Connect (launching summer 2026): Retrofits non-Weathermatic controllers (Hunter 2-wire, Rain Bird) into the SmartLink cloud platform. Does not replace the controller -- adds a SmartLink Connect adapter that bridges the existing controller to Weathermatic's cloud intelligence.

Strengths

• Portfolio management at scale for landscape maintenance companies
• SmartLink Connect enables managing competitor hardware (strategic moat)
• Subscription model with hardware included ($18-50/month) eliminates capex
• Water savings reporting generates client-facing value demonstration
• 38% average water savings documented across 500,000+ installed units
• Custom precipitation rate input per zone (unlike consumer controllers)
• Has a developer API (SmartLink Network API v2)

Gaps / Limitations

• DU is not a scheduling input: While custom PR is accepted, DU is not. The fine-tuning adjustment (-50% to +25%) is the closest proxy, but it's a manual guess, not a computed value
• No species-level plant factors: Plant type is a 4-5 category dropdown
• No design awareness: System programs schedules from operational data (what's installed), not design data (what was intended)
• No MWELO-specific compliance tools: Water reporting exists but not structured for MWELO water budget documentation
• No establishment awareness: No lifecycle stage tracking
• App stability concerns: Users report app redesigns removing functionality

API / Integration

SmartLink Network API v2 -- Developer key required:

• Hosted at Apiary: docs.smartlinknetworkv2.apiary.io
• Ruby gem available: gem install weathermatic
• Weathermatic was the first commercial irrigation system with a published developer API framework
• Capabilities: Controller management, zone control, schedule management, water usage reporting
• Rate limits: Not publicly documented

Key takeaway for SimplyScapes

Weathermatic's SmartLink Connect strategy reveals that the commercial irrigation market is consolidating around platforms, not hardware. Weathermatic is becoming a scheduling intelligence layer that manages other companies' controllers -- which is architecturally similar to what SimplyScapes proposes, but from the operations side rather than the design side. The key differentiation: Weathermatic starts from "what's already installed and how's the weather"; SimplyScapes starts from "what was designed, what's the DU, what species are planted." These are complementary, not competitive -- a partnership opportunity exists.

---

6. HydroPoint (WeatherTRAK)

How they approach scheduling

WeatherTRAK uses the most scientifically rigorous scheduling methodology in the commercial market:

ET Everywhere proprietary weather service:

• Location-specific ET data delivered daily to each controller
• Uses FAO Penman-Monteith equation (the international standard)
• Analyzes solar radiation, temperature, wind, relative humidity
• Claims higher resolution than nearest-weather-station approaches
• Data delivered via cellular connection

Scheduling engine ("Auto Mode"): Six zone-level questions determine scheduling:

1. Vegetation type (turf, shrubs, trees, mixed, groundcover)
2. Soil type
3. Sprinkler type and precipitation rate
4. Slope
5. Sun exposure
6. Root depth

The controller then independently calculates water days, run times, and cycle-soak periods per zone. A soil moisture depletion tracking model determines when the root zone needs refilling -- similar to Rachio's Flex Daily but with proprietary weather data.

Compliance tools:

• Budget Manager: Dashboard comparing consumption vs. user-defined budgets
• Water Window Compliance: Reveals non-compliant settings across sites
• Drought Manager: Proactive setup of drought restriction stages
• Learned Flow: Learns normal flow patterns per zone for leak detection

Strengths

• Highest SWAT score (perfect) and EPA WaterSense certification
• Claims 95% of maximum conservation potential vs. 60-70% for competitors
• FAO Penman-Monteith ET (explicitly documented methodology)
• Depletion tracking model goes beyond simple ET replacement
• Compliance tools (Water Window, Drought Manager) are selling points
• 28,000+ controllers installed in commercial/municipal landscapes
• 10-year all-inclusive packages available

Gaps / Limitations

• No DU input from design: Accepts user-entered PR per zone but DU is embedded in the scheduling engine's assumptions, not user-configurable
• Vegetation type is categorical: 5-6 broad categories, not species
• No design awareness: Does not know what heads are installed or how they're spaced
• No establishment lifecycle: Newly planted turf gets same schedule as established turf
• Mobile app quality issues: Crashes when stopping manual watering, alerts fail to clear, slow loading -- reported to persist for years
• Struggles with strict restrictions: Does not work well on sites limited to one-day-per-week watering
• Pricing opacity: Requires sales contact; estimated $1,500-2,500 per controller plus annual subscription
• No public API documented for third-party integration

API / Integration

No public developer API. WeatherTRAK Central is a closed cloud platform. Integration with third-party systems requires direct partnership with HydroPoint. No Home Assistant integration exists.

The BMS Integration API (via Baseline, which HydroPoint acquired in 2016) may provide some integration capability for commercial installations, but documentation is not publicly available.

Key takeaway for SimplyScapes

HydroPoint's depletion tracking model and FAO Penman-Monteith ET represent the scientific gold standard in commercial scheduling. However, their approach remains anchored in operational data -- the six zone-level questions are essentially the same inputs every competitor asks for. The gap between their six categorical questions and SimplyScapes' design-computed DU/PR with species-level plant factors is the core opportunity. Their mobile app quality problems also demonstrate that established commercial players are vulnerable to better-designed software.

---

7. ETwater / Jain Unity

How they approach scheduling

ETwater (acquired by Jain Irrigation in 2018, rebranded Jain Unity) makes the most aggressive AI/ML claims in the market:

Scheduling methodology:

• Proprietary ML models process weather, soil moisture response, plant factors, soil type, slope, and environmental conditions
• Predictive scheduling: Incorporates weather forecast data to skip irrigation proactively (before rain occurs, not just after)
• Hourly adjustments: Schedules adjust hourly based on live ET calculations -- more frequent than competitors' daily adjustments
• Processes over a billion data points hourly on soil moisture response across all installed sites
• Patent on centrally processing big data for predictive watering schedules

Product lineup:

• SmartBox: New installation controller (8-48 stations, EPA WaterSense)
• HermitCrab Pro: Retrofit adapter converting conventional controllers to 4G LTE smart controllers; powered by Jain Unity
• Jain Unity platform: Cloud dashboard showing plant moisture levels, weekly ET loss/replenishment, forecast data

Cost-of-water tracking: Unique feature tracking actual water cost in dollars, not just gallons -- speaks to budget-conscious institutional buyers.

Strengths

• Most technologically ambitious competitor with patented ML approach
• Predictive scheduling using weather forecasts (proactive, not reactive)
• Hourly adjustment frequency exceeds all competitors
• HermitCrab retrofit model enables adoption without controller replacement
• Cost-of-water tracking in dollars is a unique value proposition
• Parent company (Jain/Rivulis) is one of world's largest drip manufacturers
• 50% water reduction claims in marketing materials

Gaps / Limitations

• Zone-level despite AI branding: Plant type remains a zone-level categorical input; ML operates on zone aggregates, not per-plant
• No DU input: System does not accept or compute distribution uniformity
• No species-level plant factors: Despite sophisticated ML, plant type input is the same broad categories as every other competitor
• Opaque technology: Actual algorithm, data inputs, and model architecture are not publicly documented; difficult to assess sophistication vs. marketing
• Limited recent updates: Most available information dates 2018-2023; limited evidence of 2024-2026 feature releases
• No public API: No documented developer API for third-party integration
• Post-acquisition direction unclear: Jain/Rivulis focus appears split between landscape and agricultural markets
• Despite Jain being a drip manufacturer, no emitter-to-schedule connection exists -- the drip product catalog is not connected to the scheduling intelligence

API / Integration

No public API. Jain Unity is a closed cloud platform. No Home Assistant integration. No documented third-party integration path. Integration would require direct partnership with Jain/Rivulis.

Key takeaway for SimplyScapes

ETwater/Jain represents the most important lesson in this analysis: you can have ML, predictive analytics, and a billion data points, and still operate at the zone level with categorical plant types. Their AI investment goes toward better weather prediction and soil moisture modeling -- which is valuable -- but they never connected the dots to design-time data. The fact that their parent company manufactures drip emitters but has not connected the emitter catalog to the scheduling intelligence is the exact gap SimplyScapes would fill. The HermitCrab retrofit model is a useful precedent for hardware-agnostic scheduling intelligence.

---

8. Calsense

How they approach scheduling

Calsense targets the municipal and institutional market with a predictive water budget approach:

CS3000 scheduling:

• Weather-based irrigation using daily ET to calculate station run times
• Per-"Group" programming: groups of like stations share plant type, head type, soil type, and slope settings
• Predictive water budget maximizes savings during drought conditions
• FlowStation product optimizes concurrent valve operation based on available water supply
• Controllers communicate with each other and are accessible remotely
• Daily weather data shared automatically via WeatherSense, tipping rain buckets, and/or external weather sensors

Cloud management (Calsense Command Center Online):

• Cloud-based control for all CS3000 controllers
• Real-time alerts for flow and electrical issues
• Reports: water usage vs. budget, gallons saved, events log
• Controllers auto-adjust run times based on real-time weather data

IMaaS (Irrigation Management as a Service):

• 10-year fixed annual fee covers hardware, software, monitoring, training, support -- no capital expenditure
• Won Irrigation Association's New Product Award (2022)
• Eliminates capex barrier for municipalities and institutions

AI roadmap (Smart Irrigation 2.0):

• Published seven-stage roadmap culminating in predictive analytics
• "Cal" AI assistant (2023) handles general irrigation Q&A
• Signals AI/ML investment but focus is operational efficiency and predictive maintenance, not plant science

Strengths

• Deep municipal/institutional customer relationships
• Flow management excellence with auto-isolation of faulty zones
• FlowStation concurrent valve optimization is unique
• IMaaS model eliminates capex for public-sector customers
• Soil moisture sensor support (up to 20 sensors per controller for Baseline products)
• Reclaimed water compliance support
• AI roadmap signals forward-looking technology investment
• Solar-powered controller option available

Gaps / Limitations

• Group-level scheduling: Plant type, head type, soil type programmed per "Group" of like stations, not per individual zone or plant
• No DU input: System does not accept distribution uniformity; relies on ET + landscape inputs
• No species-level plant factors: Broad categories only
• No design awareness: Manages operational schedules, does not know design intent
• No establishment lifecycle: No awareness of plant age or growth stage
• Hardware cost: BaseStation 1000 ~$2,900-3,300 before subscriptions (solved by IMaaS for Calsense but not Baseline)
• AI roadmap is early-stage: "Cal" assistant is general Q&A, not plant-specific scheduling intelligence
• Limited consumer/small contractor market: Products and pricing designed for institutional customers

API / Integration

No public developer API documented. Calsense Command Center Online is a closed cloud platform. Baseline (acquired by HydroPoint in 2016) offers BaseManager Plus cloud service, but API details are not publicly available.

No Home Assistant integration exists.

Key takeaway for SimplyScapes

Calsense's IMaaS model validates that municipalities will pay for irrigation intelligence as a service. Their AI roadmap is worth monitoring -- if Calsense moves toward plant-level intelligence, they have the municipal relationships to deploy it. However, their approach starts from hardware and operations, not from design and plant science. SimplyScapes' design-time intelligence sits upstream of Calsense's operational domain, making complementary partnership more likely than direct competition.

---

9. Land F/X

How they approach scheduling

Land F/X is an AutoCAD plugin for landscape design, not a scheduling controller. It is the closest thing to what SimplyScapes does on the design side:

Irrigation module capabilities:

• Schematic irrigation design with head placement
• Precipitation rate assignment per schematic area
• Hydrozone designation (High, Medium, Low water use)
• Watering Schedule: Calculates precipitation per week of watering
• Runtime Schedule: Calculates precipitation per day; groups valves together to determine efficient runtime representing mainline capability
• Water budget calculation (MAWA/ETWU per MWELO methodology)
• Bill of materials generation

Plant database:

• 4,000+ plants with WUCOLS water use classifications
• Plant factor data integrated into water budget calculations
• Species-level data exists but is used for compliance documentation, not operational scheduling

Critical distinction: Land F/X generates design-time schedules -- a static document showing recommended runtimes per zone. It does not connect to any physical controller, does not adjust for weather, and does not provide ongoing scheduling intelligence. The output is a PDF or spreadsheet, not a controller configuration.

Strengths

• 4,000+ plants with WUCOLS water use data -- the largest integrated plant database in the irrigation design space
• Head placement and coverage analysis for DU assessment
• MWELO-compliant water budget calculations
• Industry standard for landscape architecture firms
• Runtime Schedule feature mimics smart controller grouping logic

Gaps / Limitations

• Design tool only -- no operational scheduling: Runtime schedules are static documents, not dynamic schedules that adjust for weather
• No controller integration: Cannot push schedules to Rachio, Hunter, Rain Bird, or any smart controller
• No API: Desktop CAD plugin with no cloud platform or developer API
• No ongoing intelligence: Schedule is calculated once at design time and never updated
• DU is implicit, not explicit: Head placement enables DU assessment but Land F/X does not explicitly compute or display DU as a numeric value in the way SimplyScapes does
• Desktop-only: Requires AutoCAD license; no web or mobile platform
• No weather integration: Static schedules do not account for actual weather conditions

API / Integration

None. Land F/X is a desktop AutoCAD plugin. No API, no cloud platform, no controller integration. Output is drawings, schedules (PDF/spreadsheet), and bills of materials.

Key takeaway for SimplyScapes

Land F/X is the closest conceptual competitor to SimplyScapes' design-side capabilities. The critical difference: Land F/X stops at the design document. SimplyScapes proposes to continue from design into operations -- computing DU and PR from the design, feeding them through the QWEL formula chain, and pushing the resulting schedule to a smart controller. Land F/X's 4,000+ plant database with WUCOLS data validates the market demand for species-level plant intelligence in irrigation design. Any Land F/X user who also uses a smart controller is a potential SimplyScapes customer -- they currently create a static schedule in Land F/X and then manually configure their controller separately, losing the design intelligence in the process.

---

10. IrriCad

How they approach scheduling

IrriCad is irrigation design software focused on hydraulic analysis, not scheduling:

Core capabilities:

• CAD-based irrigation system design (standalone or AutoCAD/BricsCAD plugin)
• Hydraulic pipe sizing and network analysis for branched or looped systems
• Sprinkler performance modeling from manufacturer databases
• Pressure distribution analysis across the system
• Automatic pipe fitting selection and bill of materials
• Velocity limits, elevation data, pipe costs, energy cost optimization
• Available in 90+ countries, established in 1988

DU handling: IrriCad can model sprinkler performance including overlap patterns and pressure distribution, which are the inputs needed to compute DU. However, IrriCad's focus is on hydraulic design optimization (pipe sizing, pressure management) rather than on scheduling or operational intelligence. The DU analysis capability exists within the design workflow but is not connected to any schedule generation.

Key distinction from SimplyScapes: IrriCad optimizes the physical irrigation infrastructure (pipes, fittings, pressure); SimplyScapes optimizes what happens after the infrastructure is built (scheduling, water budgets, controller integration).

Strengths

• Global leader in irrigation design software (90+ countries)
• Deep hydraulic analysis capabilities (pressure, flow, pipe sizing)
• Manufacturer sprinkler databases with performance data
• Can model sprinkler overlap patterns relevant to DU calculation
• Handles both landscape and agricultural irrigation design
• Available as standalone or CAD plugin

Gaps / Limitations

• Design tool only -- no scheduling capability: Does not generate operational watering schedules
• No controller integration: Cannot connect to any smart controller
• No weather integration: Static design tool without real-time data
• No API for third-party integration
• DU is a design metric, not a scheduling input: Even though IrriCad can model uniformity, it does not use DU to compute watering runtimes
• No plant database for water use: Focused on hydraulics, not plant water requirements
• No MWELO/water budget capabilities
• Desktop-only: Requires local installation

API / Integration

None. IrriCad is a desktop design application. No API, no cloud platform, no controller integration.

Key takeaway for SimplyScapes

IrriCad validates that design software can model sprinkler performance and uniformity. It is the closest existing tool to computing DU from design geometry. However, IrriCad uses this capability for hydraulic design optimization, not for scheduling. SimplyScapes' innovation is taking the design-computed DU/PR values and flowing them into the QWEL formula chain for schedule generation -- something IrriCad does not do and shows no indication of pursuing. IrriCad is not a competitive threat to the scheduling innovation; it is a validation that design-side DU computation is technically feasible.

---

11. SmartRain

How they approach scheduling

SmartRain (Smart Rain Systems LLC) is both a product competitor and a patent threat (see separate FTO analysis). Their scheduling approach:

SmartController product line:

• SmartController Original Gen3: Cloud-based controller
• SmartController Lite: Entry-level
• SmartController 2-Wire: Commercial/large residential

Scheduling methodology:

• SmartWeather: Proprietary ET formula with 20+ years of field testing that calculates exact water needs per day
• Predictive ET: Uses predictive evapotranspiration to determine water schedule for the next four days (forward-looking, not just reactive)
• VirtualWeatherStation: Cloud-based software accessing 1 million+ virtual weather stations across North America
• Advanced zone scheduling with adjustments for: landscape, microclimate, plant type, precipitation rate, root depth, slope, soil, spacing, sprinkler type
• Selectable watering days and custom start/stop dates

Unique features:

• IrrigationStacking: Waters all selected zones simultaneously while auto-adjusting for available flow rates (via cloud computing)
• SmartIrrigation Flow: Real-time flow monitoring per zone; immediately reports flow rate changes
• SmartSoil: Real-time soil readings and volumetric water measurements
• SmartLandscape: Integrates landscape service appointments (mowing, fertilization, sod/tree install) into controller schedule adjustments (this is the subject of patent US11684029B2)
• SmartMapping: Map-based system visualization

Strengths

• Predictive ET for 4-day forward scheduling
• Integrated flow monitoring per zone
• Real-time soil moisture sensing capability
• SmartLandscape integration of maintenance events into scheduling
• IrrigationStacking for concurrent zone operation with flow optimization
• Up to 30% water waste reduction claims

Gaps / Limitations

• No DU input from design: Accepts precipitation rate and spacing as inputs but does not compute DU from design geometry
• No species-level plant factors: Plant type is categorical
• No design awareness: Controller does not know what heads are installed or how they were designed; zone parameters are manually entered
• Hardware-centric: All patents and products require SmartRain's physical controllers, flow sensors, and/or soil sensors
• No public API documented: No developer API for third-party integration
• Pricing not public: Requires sales contact
• Limited consumer review data: Primarily targets commercial/HOA market; minimal presence on G2/Capterra/consumer review sites

API / Integration

No public API documented. SmartRain's SmartApp is available on iOS, Android, and desktop. No Home Assistant integration. No documented third-party integration path.

Key takeaway for SimplyScapes

SmartRain's SmartLandscape feature -- adjusting schedules based on landscape service events -- is the most direct overlap with SimplyScapes' concept of design-aware scheduling. However, SmartRain's implementation requires physical hardware (their controller + flow sensors + soil sensors) for all functionality. SimplyScapes' pure-software, design-computed approach is architecturally different and likely outside SmartRain's patent claims (see separate FTO analysis). The 4-day predictive ET capability is notable and should be considered for SimplyScapes' advanced scheduling features. Watch SmartRain's patent filings carefully -- they are the most aggressive IP filer in this space.

---

12. OpenSprinkler (Discovery)

How they approach scheduling

OpenSprinkler is an open-source smart irrigation controller that provides full transparency into its scheduling algorithms:

Scheduling methodology:

• Weather-based watering adjustment using Zimmerman method or ET-based method
• Zimmerman: Adjusts watering time based on temperature, humidity, and precipitation (simpler than ET)
• ET adjustment: Uses reference ET to calculate watering level as percentage of baseline
• Programs with flexible scheduling (daily, interval, weekday selection)
• Multi-day average watering levels (2025 firmware update) for fixed-interval programs

Open-source features:

• Firmware source code on GitHub (OpenSprinkler/OpenSprinkler-Firmware)
• REST API for full programmatic control
• MQTT support for home automation integration
• HTTP(S) zone support for remote stations
• Multiple sensor inputs including flow sensor
• Active development with 2025 firmware updates (v2.2.1 and v2.3.3)

Strengths

• Fully open source: Firmware, algorithms, and API are all transparent and modifiable
• Local processing: No cloud dependency; runs entirely on-device
• REST API: Full local API for programmatic schedule control, zone management, and sensor reading
• MQTT support: Native integration with Home Assistant and other automation platforms
• Active development: Regular firmware updates (most recent 2025)
• Low cost: ~$150-200 for hardware; no subscription
• Customizable: Users can modify scheduling algorithms directly

Gaps / Limitations

• No DU input: Scheduling is percentage-based adjustment, not DU-aware
• No species-level plant factors: Manual zone configuration with broad categories
• Zimmerman method is simplistic: Not a true soil moisture depletion model; adjusts time percentages based on weather
• DIY audience: Requires technical comfort; not mainstream consumer
• Limited weather sources: Depends on configured weather service
• No design awareness: Does not know system design or head placement

API / Integration

Full local REST API with comprehensive endpoints:

• Program management (create, edit, delete schedules)
• Zone control (start, stop, enable, disable)
• System settings (weather adjustment, sensor config)
• Status and logging
• MQTT publishing for real-time state updates

Home Assistant: Direct integration via local API; no cloud required. Most complete local API of any irrigation controller.

Key takeaway for SimplyScapes

OpenSprinkler's REST API is the most complete and well-documented local controller API available. If SimplyScapes wants to demonstrate a fully local, cloud-independent scheduling pipeline (design -> QWEL formula -> controller), OpenSprinkler is the ideal target. Its open-source nature also means SimplyScapes could contribute a "design-computed DU" scheduling module directly to the OpenSprinkler firmware -- a powerful community goodwill play that would demonstrate the value of design-aware scheduling.

---

13. RainMachine (Discovery)

How they approach scheduling

RainMachine was notable for its local-first, open-API approach to smart irrigation, but the company appears to be winding down operations as of 2025:

Scheduling methodology:

• Penman-Monteith ET formula with open-source implementation
• Local computation of weather science and water schedules (no cloud required)
• Seven-day weather forecast integration from multiple sources (NOAA, Weather Underground, NetAtmo, FAWN, CIMIS, Mesonet, Davis, and others)
• All scheduling runs on-device; cloud-independent by design

Open API:

• Fully documented open-source API
• Open-source SDKs
• ET formula source code publicly available
• Active developer community (while hardware was available)

Current status (as of 2025):

• All hardware models appear discontinued
• Company status unclear; support forum posts ask "are you still in business?" with no definitive answer
• Existing devices continue to work without cloud services
• No new products or firmware updates announced

Strengths

• Cloud-independent local processing (all intelligence on-device)
• Open-source ET implementation (Penman-Monteith)
• Open API with full local control
• Multi-source weather data aggregation
• Existing devices continue to work indefinitely without company support

Gaps / Limitations

• Effectively discontinued: No hardware available for purchase
• Company viability uncertain: Signs of business failure
• No DU input: Standard zone-level scheduling
• No species-level plant factors
• No design awareness
• Diminishing ecosystem: Developer community shrinking as company fades

API / Integration

Open local REST API -- fully documented, no cloud required. Home Assistant integration available. However, relevance is diminishing as hardware becomes unavailable.

Key takeaway for SimplyScapes

RainMachine's open-source ET implementation validates that Penman-Monteith scheduling can run locally without cloud infrastructure. Their apparent business failure is a cautionary tale about hardware-dependent business models in smart irrigation -- the hardware margins are thin and the market is dominated by incumbents (Rachio, Hunter, Rain Bird). This reinforces SimplyScapes' software-only approach: provide the intelligence layer without the hardware dependency.

---

14. Toro (Tempus / Evolution) (Discovery)

How they approach scheduling

Toro -- the parent company of Irritrol -- offers the Tempus controller line for landscape irrigation:

Tempus controller features:

• Multiple scheduling modes: daily, weekly, odd/even days, 1-31 day intervals
• Water Budget (Seasonal Adjust): Adjusts run times from 0% to 200% in 10% increments per month
• Flow monitoring for leak detection and valve diagnostics
• Run times from 1 minute to 8 hours in 1-minute increments
• IoT/WiFi module for remote monitoring via smartphone app
• Bluetooth connectivity for local programming

Evolution Series:

• More advanced commercial controller
• Supports flow management and weather-based adjustments
• Compatible with Toro's sensor ecosystem

Eagle Plus Series (announced September 2025):

• Newest controller with expanded connectivity options
• Additional feature details not yet widely available

Scheduling approach: Toro uses traditional timer-based scheduling with seasonal percentage adjustment -- similar to Rain Bird's approach and less sophisticated than Rachio's or B-hyve's ET-based soil moisture depletion models.

Strengths

• Toro is a major, well-capitalized irrigation manufacturer
• Broad product portfolio (residential through golf course)
• Flow monitoring integrated into Tempus line
• 0-200% seasonal adjustment provides some weather adaptation
• Long run time support (up to 8 hours) suits drip applications

Gaps / Limitations

• Timer-based, not ET-based: Water Budget is percentage scaling, not soil moisture depletion tracking
• No DU input: System does not accept distribution uniformity
• No species-level plant factors
• No design awareness
• No public API documented: No developer API for third-party integration
• Limited smart scheduling: Less sophisticated than Rachio, Hunter, or even B-hyve
• Late to smart irrigation: Tempus launched in 2022; competitors have years of algorithmic refinement

API / Integration

No public API documented. Toro App provides mobile control but no developer access. No Home Assistant integration confirmed. No documented third-party integration path.

Key takeaway for SimplyScapes

Toro is a significant market presence but a weak smart scheduling competitor. Their percentage-scaling approach is the least sophisticated among major manufacturers. Toro's strength is in hardware distribution and brand recognition, not scheduling intelligence. SimplyScapes would easily outperform Toro's scheduling on technical merit. Watch the Eagle Plus Series for any scheduling improvements.

---

15. Galcon (Discovery)

How they approach scheduling

Galcon is an Israeli manufacturer focusing on agricultural and greenhouse irrigation:

Product lines:

• GSI PRO: Web-based irrigation controller with 8 irrigation programs, unlimited start times, fertigation control, EC/pH management
• Galileo Cloud: Advanced cloud system for multi-site greenhouse management including climate control (temperature, humidity, CO2, light)
• DC battery controllers for remote/field applications

Scheduling approach: Program-based timer scheduling with cloud-based remote management. Focused on agricultural applications (greenhouses, field crops) rather than landscape turf irrigation. Supports quantitative and proportional fertigation control.

Strengths

• Strong in agricultural/greenhouse market
• Cloud-based management with interactive farm mapping
• Fertigation integration (fertilizer + irrigation combined)
• Global distribution (strong in Middle East, Asia, Australia)

Gaps / Limitations

• Agricultural focus, not landscape: Products designed for greenhouse and field crop irrigation, not residential or commercial turf
• Timer-based scheduling: No ET-based intelligence for landscape
• No DU input: Not relevant to their agricultural use case
• No landscape plant database
• No API for third-party landscape integration
• No US residential/commercial market presence

API / Integration

GSI web-based interface provides remote control but no documented developer API for third-party integration.

Key takeaway for SimplyScapes

Galcon is not a direct competitor in the landscape turf scheduling space. Their agricultural focus and fertigation capabilities are more relevant to Netafim/GrowSphere comparisons. Not a competitive threat for turf irrigation scheduling.

---

Additional Discovery: Companies Investigated but Not Profiled

The following companies were investigated during the discovery phase but do not warrant full profiles:

| Company | Finding | Status | |---------|---------|--------| | Skydrop | Acquired by Scotts Miracle-Gro; appears effectively defunct. Limited ET-based scheduling via WiFi. No API. No competitive relevance. | Defunct | | Banyan Water | Commercial water management platform. IoT devices + weather tracking + satellite imagery + plant databases for irrigation scheduling. Targets large commercial real estate portfolios. Patented leak detection. No public API. Relevant as an adjacent market competitor for commercial, but not direct vertical competitor for turf scheduling. | Adjacent market | | WaterSign | Could not find a product matching this name in municipal water analytics for irrigation scheduling. May be a regional or very early-stage company. No competitive data available. | Not found | | Droplet | No substantive product information found for an "AI irrigation startup" under this name. May be pre-product or defunct. | Not found |

---

Synthesis

Market Patterns: What Most Products Converge On

1. ET-based scheduling is the baseline. Every serious smart controller uses some form of evapotranspiration calculation. The differentiation is in data sources (local weather station vs. satellite vs. proprietary network), frequency (daily vs. hourly), and methodology (simple ET replacement vs. soil moisture depletion tracking).

2. Zone-level is universal. Without exception, every product -- from $70 B-hyve to $2,500 WeatherTRAK -- schedules at the zone (valve) level. A zone gets one schedule regardless of what's planted in it.

3. Broad plant type categories are standard. Every product offers 4-8 plant type categories (cool season turf, warm season turf, shrubs, trees, annuals, groundcover). None offer species-level selection.

4. Cloud dependency is the norm. Only OpenSprinkler and the (likely defunct) RainMachine offer fully local scheduling intelligence. Every other product requires cloud connectivity for smart features.

5. Subscription models are growing. Weathermatic ($18-50/mo with hardware included), Calsense IMaaS (10-year fixed fee), and HydroPoint (annual subscription) show the commercial market moving toward recurring revenue. Consumer products (Rachio, B-hyve) remain one-time purchase.

6. Catch-cup testing is the assumed DU source. Every product that uses DU or efficiency in its calculations assumes the value comes from a physical field measurement. Rachio's community forums are dominated by users struggling with default efficiency assumptions.

Market Gaps: What Is NOT Being Solved

1. Design-to-schedule bridge. No product connects irrigation design data (head placement, spacing, arc, radius, manufacturer performance specs) to operational scheduling. Design tools (Land F/X, IrriCad) stop at the design document. Controllers start from scratch with manual zone configuration.

2. Design-computed DU. No product computes DU from design geometry for use in scheduling. Consumer controllers use fixed defaults (typically 70%). Commercial systems require field measurement. Design tools compute DU-related metrics but don't use them for scheduling.

3. Species-specific scheduling. No product differentiates scheduling based on turfgrass species. A zone of Kentucky bluegrass (Kc=0.80) and a zone of bermudagrass (Kc=0.60) both select "turf" and may receive the same scheduling treatment unless the user manually adjusts crop coefficients.

4. Growing season intelligence. No product determines irrigation start/end dates based on species-specific dormancy thresholds. EPA WaterSense 2.0's universal 50F GRDD threshold is the most advanced publicly available approach, and it is too crude (does not differentiate cool-season vs. warm-season turf).

5. Establishment scheduling. No landscape controller adjusts scheduling for newly planted turf (sod or seed). The 90-day establishment period with tapering water requirements is handled entirely by manual user intervention or professional judgment.

6. Compliance-to-schedule connection. MWELO water budgets (MAWA/ETWU) are calculated independently of operational schedules. No product generates a schedule that is mathematically guaranteed to stay within the MWELO water budget.

The Design-Awareness Gap

This is the central finding: nobody bridges design to schedule.

DESIGN TOOLS                    CONTROLLERS
Land F/X    ----gap---->        Rachio
IrriCad     ----gap---->        Hunter/Hydrawise
SimplyScapes----gap---->        Rain Bird
                                B-hyve
                                Weathermatic
                                WeatherTRAK
                                SmartRain

Design tools know:              Controllers know:
- Head placement                - Zone configuration (manual input)
- Spacing geometry              - Weather/ET data
- Manufacturer specs            - Soil type (manual input)
- DU (computed)                 - Plant type (broad category)
- PR (from catalog)             - Slope (manual input)
- Plant species (database)      - Efficiency (default or manual)
- WUCOLS plant factors

Design tools DON'T:             Controllers DON'T:
- Generate schedules            - Know actual DU
- Connect to controllers        - Know PR from specs
- Adjust for weather            - Know what heads are installed
- Track soil moisture           - Know species-level plant factors
                                - Know design intent

SimplyScapes is the only platform positioned on both sides of this gap. It has the design data (head placement, DU, PR, manufacturer specs, plant species) AND the controller integration (Rachio already in the UI). The QWEL formula chain is the mathematical bridge: design-computed DU and PR feed into the formula alongside public ETo data and WUCOLS plant factors to produce zone-by-zone runtimes that can be pushed to the controller.

Where SimplyScapes Differentiates

| Capability | SimplyScapes | Best Competitor | Gap | |------------|-------------|-----------------|-----| | DU from design geometry | Yes (already computed) | IrriCad (design only, not for scheduling) | No competitor uses design DU for scheduling | | PR from manufacturer catalog | Yes (already computed) | Land F/X (for design documentation only) | No competitor flows catalog PR into schedule | | Species-level plant factors | Yes (2,500+ plant library with WUCOLS) | Land F/X (4,000+ for design docs, not scheduling) | No competitor uses species Kc in live scheduling | | QWEL formula chain for scheduling | Proposed (this research) | None | Nobody automates ETo -> runtime via QWEL with design DU | | Controller integration | Yes (Rachio in UI) | Weathermatic SmartLink Connect (operational only) | No competitor pushes design-derived schedules to controllers | | MWELO compliance + schedule | Yes (Water Budget tab exists) | WeatherTRAK Budget Manager (operational budget only) | No competitor guarantees schedule stays within MWELO budget | | Species-specific growing season | Proposed (this research) | EPA WaterSense 2.0 (universal 50F threshold) | Nobody uses species-specific dormancy thresholds | | Establishment scheduling | Proposed (from SS-RR-2026-001) | None in landscape | Only Netafim does this for ag crops |

API Integration Priority Matrix

| Controller | API Quality | Schedule Push | DU/Efficiency Input | Moisture Control | Priority | |-----------|------------|---------------|--------------------|--------------------|----------| | Rachio | Excellent (public REST, 1,700/day) | Via zone/start_multiple or moisture override | Efficiency field (manual) | setMoisturePercent, setMoistureLevel | PRIMARY | | OpenSprinkler | Excellent (local REST, open source) | Full program management | Manual | Via API | SECONDARY (for local-first users) | | Hunter Hydrawise | Moderate (REST v1.5, GraphQL v2) | Zone start/stop only | Not configurable | Not available | TERTIARY (requires commercial partnership for v2) | | Weathermatic | Available (Apiary-hosted, developer key) | Schedule management | Custom PR per zone | Not documented | MONITOR (commercial partnership potential) | | Rain Bird | Poor (reverse-engineered only) | Via pyrainbird (unofficial) | Not available | Not available | LOW (community integration only) | | B-hyve (Orbit) | Poor (reverse-engineered only) | Via unofficial WebSocket | Not available | Not available | LOW | | SmartRain | None | N/A | N/A | N/A | NOT VIABLE | | HydroPoint | None | N/A | N/A | N/A | NOT VIABLE | | Toro | None | N/A | N/A | N/A | NOT VIABLE | | Calsense | None | N/A | N/A | N/A | NOT VIABLE |

---

Sources

| # | Source | URL | |---|--------|-----| | 1 | Rachio Flex Daily FAQ | https://support.rachio.com/en_us/flex-daily-schedules-faq-BJ2YPIJKw | | 2 | Rachio API Documentation | https://rachio.readme.io/ | | 3 | Rachio API setMoisturePercent | https://rachio.readme.io/reference/publiczonesetmoisturepercent | | 4 | Rachio Public API v2.0 (Postman) | https://www.postman.com/rachio/rachio-public-workspace/documentation/y85j8lw/rachio-public-api-v2-0 | | 5 | Rachio Community: Precipitation Rate / Catch Cup Test | https://community.rachio.com/t/precipitation-rate-catch-cup-test/25644 | | 6 | Rachio Community: Flex Daily Overwatering | https://community.rachio.com/t/rachio-watering-schedule-much-more-aggressive-than-needed/9248 | | 7 | Rachio Community: Nozzle Type as Flow/Precip Rate | https://community.rachio.com/t/nozzle-type-is-a-clumsy-way-of-specifying-flow-precipitation-rate/10131 | | 8 | Rachio Home Assistant Integration | https://www.home-assistant.io/integrations/rachio/ | | 9 | Hunter Hydrawise API Information | https://www.hunterirrigation.com/support/hydrawise-api-information | | 10 | Hydrawise REST API v1.5 PDF | https://www.hunterirrigation.com/sites/default/files/2024-03/Hydrawise%20REST%20API.pdf | | 11 | Hydrawise GraphQL API Explorer | https://app.hydrawise.com/api/v2/graph/explore | | 12 | Hydrawise Integration Support | https://www.hunterirrigation.com/support/hydrawise-integration-support | | 13 | Hydrawise Home Assistant Integration | https://www.home-assistant.io/integrations/hydrawise/ | | 14 | Rain Bird IQ4 Product Page | https://www.rainbird.com/products/iq4 | | 15 | Rain Bird IQ4 Tech Spec PDF | https://www.rainbird.com/sites/default/files/media/documents/2020-01/D41773-0120_IQ4-TechSpec_FIN.pdf | | 16 | Rain Bird 2.0 App and IQ4 Central Control | https://www.rainbird.com/homeowners/rain-bird-2.0app | | 17 | Orbit B-hyve Smart Controller Guide | https://sprinklersystemcalculator.com/HowTo/orbitBhyve.html | | 18 | B-hyve Smart Watering vs WeatherSense Delays | https://support.orbitonline.com/en/b-hyve-smart-indoor-outdoor-irrigation-controller/Smart-Watering-VS-WeatherSense-Weather-Delays-6f6 | | 19 | Weathermatic SmartLink Product Page | https://www.weathermatic.com/products/smartlink/ | | 20 | Weathermatic Developer APIs Announcement | https://www.prlog.org/12358909-weathermatic-releases-smartlink-developer-apis.html | | 21 | Weathermatic SmartLink Connect | https://www.weathermatic.com/2025/02/19/weathermatic-unveils-smartlink-connect-to-enable-remote-management-of-2-wire-and-other-irrigation-controllers/ | | 22 | SmartLink Network Ruby Gem (GitHub) | https://github.com/tgmerritt/smartlinknetwork | | 23 | HydroPoint WeatherTRAK Evapotranspiration | https://www.hydropoint.com/weathertrak/evapotranspiration/ | | 24 | WeatherTRAK ET Pro3 Product Page | https://www.hydropoint.com/weathertrak/products/weathertrak-et-pro3/ | | 25 | WeatherTRAK Central Platform | https://www.hydropoint.com/weathertrak/products/weathertrak-central/ | | 26 | WeatherTRAK Auto Mode Programming | https://hydropoint.helpjuice.com/972748-programming-in-auto-mode | | 27 | ETwater / Jain Unity Platform | https://jainsusa.com/etwater/unity/ | | 28 | Jain Unity HermitCrab Pro | https://jainsusa.com/etwater/controller/hermit-crab-2-with-flow-monitoring/ | | 29 | Jain AI-Powered Irrigation Launch | https://www.landscapemanagement.net/jain-irrigation-launches-ai-powered-irrigation-solution/ | | 30 | Calsense CS3000 Controller | https://calsense.com/smart-solutions/controllers/cs3000-controller-conventional/ | | 31 | Calsense Designers Guide 2025 PDF | https://www.calsense.com/wp-content/uploads/2021/08/Designers-Guide-2025.pdf | | 32 | Calsense Smart Irrigation 2.0 Roadmap | https://www.calsense.com/smart-irrigation-2-0/ | | 33 | Land F/X Watering Schedule | https://www.landfx.com/docs/irrigation/schedules-and-reports/1545-watering-schedule.html | | 34 | Land F/X Runtime Schedule | https://www.landfx.com/index.php/docs/irrigation/schedules-and-reports/item/196-irrigation-schedules-and-reports.html | | 35 | Land F/X Hydrozone and PR Attributes | https://www.landfx.com/community/hydrozone-and-precipitation-rate-attributes-for-irrigation-valve-callouts/oldest.html | | 36 | IrriCad Product Page | https://www.irricad.com/ | | 37 | IrriCad (Nelson Irrigation) | https://nelsonirrigation.com/products/software/irricad/ | | 38 | SmartRain Key Features | https://smartrain.net/smart-irrigation/key-features/ | | 39 | SmartRain Technology Page | https://smartrain.net/technology/ | | 40 | SmartRain SmartController Gen3 | https://smartrain.net/products/smartcontroller-original-gen3/ | | 41 | OpenSprinkler Product Page | https://opensprinkler.com/product/opensprinkler/ | | 42 | OpenSprinkler Firmware GitHub | https://github.com/OpenSprinkler/OpenSprinkler-Firmware | | 43 | OpenSprinkler User Manual (2025) | https://raysfiles.com/os_compiled_firmware/docs/2.2.1/OSUserManual221_3.pdf | | 44 | RainMachine Product Page | https://www.rainmachine.com/ | | 45 | RainMachine Business Status Discussion | https://support.rainmachine.com/hc/en-us/community/posts/6625420556055-Are-you-all-still-in-business-Asking-again | | 46 | Toro Tempus Series | https://sites.toro.com/tempus/ | | 47 | Toro Eagle Plus Series Announcement | https://newsroom.toro.com/en/news/2025-us/09-29-25-introducing-eagle-plus-series-irrigation-control | | 48 | Galcon GSI Controllers | https://www.galconc.com/ | | 49 | Banyan Water Irrigation Insight | https://banyanwater.com/solutions/irrigation-insight/ | | 50 | Home Assistant 2025 Smart Irrigation Controller Discussion | https://community.home-assistant.io/t/2025-smart-irrigation-controller/864755 | | 51 | Smart Irrigation Systems G2 Reviews | https://www.g2.com/categories/smart-irrigation-systems | | 52 | WUCOLS V (UC Davis) | https://wucols.ucdavis.edu/ | | 53 | DU Best Practices (IA Technical Paper) | https://www.irrigation.org/IA/FileUploads/IA/Resources/TechnicalPapers/2004/UsingDistributionUniformityToEvaluateTheQualityOfASprinklerSystem.pdf | | 54 | ML-Based DU Prediction (Nature Scientific Reports) | https://www.nature.com/articles/s41598-023-47688-3 | | 55 | SS-RR-2026-001 Competitive Analysis (Residential) | docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/plant-specific-drip-irrigation-intelligence/research/supporting/competitive-analysis-residential.md | | 56 | SS-RR-2026-001 Competitive Analysis (Commercial) | docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/plant-specific-drip-irrigation-intelligence/research/supporting/competitive-analysis-commercial.md |

Adjacent Market Analysis & Academic/Open Source Scan

ID: SS-RR-2026-002-B | Date: 2026-03-01 | Status: complete ClickUp: Automated Turf Irrigation Scheduling Parent plan: SS-RP-2026-002 Domain: Irrigation Management / Automated Turf Scheduling Cross-reference: SS-RR-2026-001 (Plant-Specific Drip Irrigation Intelligence)

---

PART 1: Adjacent Market Pattern Analysis

This section examines products and industries that solve analogous problems to automated turf irrigation scheduling from design-time intelligence. For each adjacent, we identify the transferable pattern, the SimplyScapes adaptation, and the limits of the analogy. Findings from SS-RR-2026-001 are cross-referenced and extended where applicable.

---

1. Netafim GrowSphere / Crop Advisor -- Growth-Stage-Aware Scheduling

Cross-reference: SS-RR-2026-001-B Section 1 validated the lifecycle-aware scheduling pattern for drip irrigation. This section extends it to turf.

Their solution: GrowSphere's Crop Advisor runs crop model algorithms built on 50+ years of Netafim agronomic knowledge. The system fuses three data sources -- sensors (soil moisture, weather), hydraulic data (flow, pressure), and crop growth-stage models -- to produce daily irrigation recommendations recalculated every midnight. In 2025, Netafim expanded fertigation models for corn, with more crops under development. Crop Advisor tailors water and nutrient delivery to specific lifecycle phases (germination, vegetative, flowering, fruit set, maturation).

Transferable pattern: Growth-stage-aware scheduling with three-source data fusion. The insight that water demand varies dramatically by growth stage applies directly to turfgrass: newly seeded/sodded turf needs daily shallow watering; established turf during active growth needs deep infrequent watering tied to ET; dormant turf needs zero irrigation. The midnight recalculation cadence is a good model for schedule update frequency.

SimplyScapes adaptation: Turf has fewer growth stages than row crops, but the pattern transfers as a simplified lifecycle model:

• Establishment phase (post-seeding/sodding): Daily shallow irrigation for 2-4 weeks, gradually tapering (validated by SS-RR-2026-001 establishment lifecycle research showing the 3-phase tapering model).
• Active growth phase: ET-based scheduling using the QWEL formula chain (ETo x PF / DU = runtime).
• Dormancy phase: Zero or minimal irrigation, triggered by species-specific GDD thresholds (cool-season turf: base temp 0C; warm-season turf: base temp 10C).
• Transition phases: Spring green-up (ramp-up) and fall wind-down (taper-off), where water demand changes rapidly.

For data fusion, SimplyScapes replaces Netafim's sensor layer with design-computed data (DU and PR from head placement geometry), weather data (ETo from public APIs), and plant models (species-specific PF and dormancy thresholds from WUCOLS/extension data).

What doesn't transfer: Netafim's sensor feedback loop (real-time soil moisture as ground truth) is absent in Phase 1. Turf has simpler growth stages than crops but more species variability within a single zone (cool-season blends). Netafim's fertigation component is out of scope for turf scheduling.

---

2. CropX -- Sensor + Model Fusion, ET Validation

Cross-reference: SS-RR-2026-001-B Section 1 covered CropX's sensor platform. This section extends with 2024-2025 developments.

Their solution: CropX is a digital farm management system used by 20,000+ users across 70+ countries. Multi-depth soil sensors (SV line) measure moisture, temperature, conductivity, and salinity. In late 2024, CropX fully integrated the Tule Evapotranspiration sensor (measuring actual ET from canopy-level measurements) and launched "CropX Actual ET" -- a first-of-its-kind above-canopy sensor for monitoring real-time plant water use. In 2025, CropX integrated with Reinke Manufacturing's ReinCloud 3 platform, providing soil, weather, and agronomic data alongside pivot control systems. Users report up to 50% irrigation water reduction.

Transferable pattern: CropX validates that ET-only models can be improved by ground-truth soil moisture data, but also demonstrates that ET-only scheduling is a viable starting point. Their actual ET sensor provides a pathway from estimated ET (model-based) to measured ET (sensor-based), which is the same progression SimplyScapes would follow from Phase 1 (ET-only) to advanced (sensor-augmented). The key insight is that CropX started with sensor data and added ET models, while SimplyScapes starts with ET models and can add sensor data later.

SimplyScapes adaptation: Phase 1 uses ET-only scheduling (ETo from weather APIs, adjusted by PF and DU). Future phases could add soil moisture sensors as optional ground-truth validation, following the CropX pattern of sensor + model fusion. The design-computed DU serves as a substitute for physical uniformity measurements, analogous to how CropX's sensors substitute for manual soil sampling.

What doesn't transfer: CropX's hardware installation model (physical sensors in the ground) is a barrier for residential. Their multi-depth sensing (surface to 60cm+) is overkill for turf with shallow root zones (4-8 inches). Their per-field management unit maps to per-zone in landscape irrigation, but residential zones are much smaller.

---

3. OpenET -- Satellite-Derived ET for Landscape-Scale Validation

Cross-reference: SS-RR-2026-001-B identified OpenET as a potential data source. This section deepens the analysis with urban turfgrass validation data.

Their solution: OpenET uses an ensemble of six satellite-driven models (ALEXI/DisALEXI, eeMETRIC, geeSEBAL, PT-JPL, SIMS, SSEBop) to calculate ET from Landsat imagery at ~30m resolution. A 2024 AGU presentation specifically addressed validating OpenET for urban turfgrass to support urban water management. A rigorous 2023 Nature Water assessment found monthly error rates of 10-20% for agricultural crops, with annual errors consistently below 10% in Mediterranean climates. OpenET expanded to 48 states in 2024 and now serves as a free, public data resource.

Transferable pattern: OpenET demonstrates that satellite-derived ET can serve as an independent validation source for weather-station-based ETo calculations. The 30m resolution is too coarse for individual residential zones but could validate ETo data at the neighborhood or project scale. The ensemble approach (averaging six models) is a pattern worth emulating -- multiple data sources averaged together produce more robust estimates than any single source.

SimplyScapes adaptation: OpenET could serve three roles:

1. ETo validation: Cross-check weather-station ETo (from USU Climate Center, CIMIS, or Open-Meteo) against satellite-derived ET for the same location.
2. Actual vs. predicted comparison: Compare predicted water demand (from the QWEL formula chain) against satellite-observed actual ET for scheduled landscapes.
3. Water audit tool: For landscape contractors, compare actual landscape water use (from OpenET) against designed water budget (from SimplyScapes MWELO calculation) to identify over/under-watering.

What doesn't transfer: 30m pixel resolution means a single pixel covers most residential properties. Temporal resolution (Landsat revisit every 16 days) is too slow for daily scheduling. Urban heat island effects and mixed land cover within pixels reduce accuracy for residential parcels. The validation for urban turfgrass is still emerging (2024 AGU presentation, not yet in peer-reviewed literature for urban landscapes specifically).

---

4. Climate FieldView (Bayer) -- Design-to-Operations Data Pipeline

Cross-reference: SS-RR-2026-001-B Section 3 covered the general pattern. This section adds 2024 platform updates.

Their solution: Climate FieldView is Bayer's digital farming platform, now deployed on 250+ million subscribed acres across 23 countries. In 2024, FieldView launched "Your Farm at a Glance" (summary dashboards), FieldView Premium (advanced analytics tier), and FieldView Drive 2.0 (improved hardware for data collection during planting, spraying, and harvest). The platform creates prescription maps -- acre-by-acre recommendations that can be transferred directly to equipment. Key pattern: design-time data (planting plans, soil maps, seed selection) flows through analytics into operational recommendations.

Transferable pattern: The design-to-operations pipeline is the closest analogy to SimplyScapes' core innovation. FieldView's flow is: field boundaries + soil data + seed selection + weather -> prescription maps -> equipment execution. SimplyScapes' equivalent is: zone boundaries + soil type + plant selection + head placement + weather -> irrigation schedule -> controller execution. The 2024 "Your Farm at a Glance" feature demonstrates the value of aggregating operational data into an intuitive summary view -- a pattern for SimplyScapes' Schedule tab.

SimplyScapes adaptation: The prescription map paradigm maps directly to per-zone irrigation schedules. Just as FieldView generates variable-rate seeding prescriptions from field data, SimplyScapes generates variable-runtime irrigation schedules from design data. The key differentiator: FieldView requires in-field data collection (via Drive hardware), while SimplyScapes generates prescriptions from design geometry alone. The tiered subscription model (FieldView Plus vs. Premium) is also worth studying for monetization strategy.

What doesn't transfer: Agricultural fields have uniform crops within management zones; landscape zones have mixed species. FieldView's data pipeline requires proprietary hardware (Drive); SimplyScapes needs no hardware beyond the existing controller. FieldView's scale (thousands of acres per farm) vs. SimplyScapes (fractions of an acre per residential property) requires different UX patterns.

---

5. Building HVAC (Nest / Ecobee) -- Learning Schedules from Usage Patterns

Their solution: The Nest Learning Thermostat uses machine learning to learn temperature preferences and schedule patterns from user behavior over the first few weeks. It uses occupancy sensors and phone location to detect away-from-home status and shift to energy-saving mode. Seasonal Savings makes gradual adjustments (up to 2F) over 3-week periods to optimize efficiency without sacrificing comfort. The system uses different algorithms depending on the specific HVAC setup (forced air, radiant, heat pump).

Transferable pattern: Four key patterns transfer:

1. Learning from user adjustments: When a homeowner manually adjusts their irrigation schedule (skipping a day, adding extra watering), the system could learn and adjust future recommendations.
2. Seasonal auto-adjustment: Nest's Seasonal Savings makes small, gradual changes over 3-week periods. Turf irrigation needs similar gradual seasonal transitions rather than abrupt monthly schedule changes.
3. Setup-specific algorithms: Nest uses different algorithms for different HVAC types. SimplyScapes should use different scheduling algorithms for different head types (rotary vs. spray vs. bubbler), soil types, and turf species.
4. Away mode: Nest detects empty homes and reduces HVAC. Irrigation equivalent: vacation mode that maintains minimum watering to prevent turf death while conserving water.

SimplyScapes adaptation: The "learn from user adjustments" pattern is most directly applicable. If a homeowner consistently reduces watering below the recommended schedule and their turf remains healthy, the system could learn that the original schedule was over-prescribing and adjust the PF or DU assumptions. The seasonal transition pattern maps to the growing-season determination algorithm -- gradual ramp-up in spring and taper-down in fall rather than binary on/off.

What doesn't transfer: HVAC operates on minute-to-minute feedback (thermostat reads current temperature). Irrigation has no equivalent real-time feedback in Phase 1 (no soil moisture sensor). HVAC has immediate consequence of wrong decision (discomfort); irrigation consequences are delayed (turf stress appears days later). Occupancy-based optimization is less relevant -- lawns need water regardless of whether anyone is home.

---

6. Solar Energy (Enphase / SolarEdge) -- Design-Time Performance Prediction

Their solution: Solar installation software (Aurora Solar, Helioscope) uses design geometry (panel placement, orientation, tilt, shading analysis) to predict system performance before installation. Post-installation, Enphase and SolarEdge monitoring platforms track actual vs. predicted performance at the panel level. SolarEdge provides degradation tracking to identify long-term performance decline. Both platforms provide weather-adjusted performance comparisons and automated alerts for anomalies.

Transferable pattern: The core analogy is design-time prediction validated by operational monitoring. Solar designers predict kWh output from system geometry (panel count, orientation, shading); irrigation designers can predict water delivery from system geometry (head count, arc, spacing, DU). Solar monitoring tracks actual vs. predicted output and flags degradation; irrigation monitoring could track actual vs. predicted water use and flag system degradation (clogged nozzles, pressure loss).

SimplyScapes adaptation: The design-time-to-operations pipeline is the most transferable pattern:

1. Design-time prediction: Just as solar software predicts annual kWh from panel geometry, SimplyScapes predicts annual water use from head geometry (DU, PR) and weather (ETo).
2. Performance gap monitoring: Solar tracks predicted vs. actual kWh. SimplyScapes could track predicted vs. actual water use (from controller runtime data or utility meter).
3. Degradation detection: Solar identifies panel degradation from declining output ratios. SimplyScapes could identify nozzle wear, pressure loss, or coverage gaps from increasing water use relative to predictions.
4. Automated alerts: Solar sends alerts when panels underperform. SimplyScapes could alert when zones use significantly more water than predicted (possible leak or DU degradation).

What doesn't transfer: Solar output is continuously measurable (inverter reports kWh in real-time). Irrigation outcome (turf health) is not directly measurable without sensors or visual assessment. Solar degradation is gradual and predictable; irrigation system degradation can be sudden (broken head, clogged nozzle). Solar has a single performance metric (kWh); irrigation has multiple (uniformity, volume, frequency, turf quality).

---

7. Digital Twins (Willow / Autodesk Tandem) -- BIM-to-Operations Pipeline

Their solution: Willow's digital twin platform connects BIM (Building Information Modeling) data to operational systems, creating a unified Knowledge Graph with over 75+ system integrations and 10+ million telemetry points processed in real-time. The platform enables predictive maintenance by monitoring building component conditions and anticipating maintenance needs. A 2023 Journal of Cleaner Production study demonstrated 15-20% crop yield increases and 30-40% water use reductions using digital twins for smart farming irrigation. However, as of 2025, digital twin technology has yet to achieve widespread adoption in agricultural water management (only 4 publications per year in 2023-2024).

Transferable pattern: The BIM-to-operations pipeline is conceptually identical to SimplyScapes' design-to-schedule pipeline. In building management, the BIM model (design-time data) feeds into operational analytics (runtime predictions, maintenance scheduling). In irrigation, the design model (head placement, zone layout, pipe sizing) feeds into operational scheduling (runtimes, cycle-soak splits) and could feed into maintenance predictions (when to replace nozzles based on hours of operation).

SimplyScapes adaptation: SimplyScapes already has the "BIM" equivalent -- the irrigation design with head positions, zone boundaries, pipe layouts, and coverage analysis. The opportunity is to extend this design model into an operational digital twin:

1. Design model as operational baseline: Zone DU, PR, and coverage maps serve as the as-designed baseline.
2. Operational drift detection: Compare actual water use (from controller data) against design predictions to detect system drift.
3. Maintenance prediction: Estimate nozzle replacement timing based on hours of operation and water quality.
4. What-if simulation: Model the impact of adding/removing heads, changing nozzles, or modifying zones before making physical changes.

What doesn't transfer: Building digital twins have dense sensor networks (BMS, CMMS, IoT). Residential irrigation has minimal sensing (at most a flow sensor). Building lifecycles are decades with slow degradation; irrigation systems can change rapidly (seasonal adjustments, damage from mowers/vehicles). The BIM data model is standardized (IFC); irrigation design data models are proprietary.

---

8. WUCOLS / UC Davis -- Plant Factor Data Infrastructure

Cross-reference: SS-RR-2026-001-B Section 5 validated WUCOLS as public domain and foundational for plant-specific scheduling.

Their solution: WUCOLS V contains water use classifications for 4,100+ taxa across 6 California climate zones. The landscape coefficient (KL) is computed as KL = Ks x Kd x Kmc (species factor x density factor x microclimate factor). A 2023 study comparing WUCOLS against irrigation records found it produced the most accurate estimates among three factor-based approaches tested. UC Davis also operates the UC Landscape Plant Irrigation Trials (UCLPIT), which provides empirical data on landscape plant water use under controlled conditions. Additionally, UC Davis LAWR has developed spreadsheet tools that generate annual irrigation calendars from ETo, DU, soil type, and desired wetting depth.

Transferable pattern: WUCOLS provides the species factor (Ks) that is foundational for calculating landscape water demand. The 2023 validation study confirms WUCOLS as the most reliable method for estimating landscape plant water requirements. For turfgrass specifically, the pattern is simpler than for mixed landscapes: cool-season turf Ks = 0.80, warm-season turf Ks = 0.60 (from WUCOLS). The UCLPIT research provides empirical validation data.

SimplyScapes adaptation: WUCOLS plant factors are already used in the SimplyScapes water budget (MWELO) calculation. For turf scheduling, the species factor feeds directly into the QWEL formula chain: ETc = ETo x PF, where PF = Ks x Kd x Kmc. UC Davis' spreadsheet tool (ETo + DU + soil type -> calendar) is essentially the same calculation SimplyScapes would automate from design data.

What doesn't transfer: WUCOLS is California-centric (6 CA climate zones). National coverage requires supplementation with USU CWEL/SLIDE data. WUCOLS provides static classifications (Low/Medium/High), not dynamic crop coefficients that vary by growth stage or season. The 4,100+ taxa coverage is comprehensive for ornamentals but the turfgrass entries are coarse (grouped by cool-season vs. warm-season, not by specific cultivar).

---

9. USU CWEL / SLIDE Rules -- National Plant Factor Methodology

Their solution: The SLIDE Rules (Simplified Landscape Irrigation Demand Estimation), developed at Utah State University's Center for Water-Efficient Landscaping, provide a research-based methodology for estimating landscape water demand. SLIDE is the basis for ANSI/ASABE S623.1, the national standard for determining landscape plant water demands (reaffirmed 2022). The methodology defines four key rules, including: (1) a landscape zone controlled by one valve is the smallest water management unit; (2) when plant types are mixed in a zone, water demand is governed by the type with the highest PF; (3) dense plant cover (>=80% canopy coverage) is treated as a single "big leaf." USU Extension also provides a Landscape Irrigation Calculator for Utah (updated 2024).

Transferable pattern: SLIDE's zone-based management unit maps directly to irrigation controller zones. The "highest PF governs" rule is critical for turf scheduling: if a zone contains both cool-season turf (PF 0.80) and warm-season turf (PF 0.60), the schedule must be set for the cool-season turf. The "big leaf" simplification for dense turf (which is always >=80% canopy coverage) means the calculation treats the entire zone as a single surface -- simplifying the math considerably compared to mixed-species landscape beds.

SimplyScapes adaptation: The SLIDE methodology validates the QWEL formula chain approach. SimplyScapes' design engine already defines zones as the management unit and computes DU per zone. The SLIDE rules confirm that:

1. Per-zone scheduling is the correct granularity (not per-head or per-plant for turf).
2. Dense turf can be treated as a "big leaf" with a single PF.
3. Mixed species within a zone should use the highest water-demand species PF.
4. The calculation chain is standardized (ANSI standard) and defensible.

What doesn't transfer: SLIDE provides plant factor categories (6-9 plant types) rather than species-specific factors. The methodology assumes field-measured DU; design-computed DU is SimplyScapes' novel contribution. SLIDE's Utah-centric calculator needs adaptation for other climates.

---

10. Urban Water Analytics (WaterSmart / Dropcountr) -- Utility-Side Water Intelligence

Their solution: Dropcountr (now operated by KUBRA after acquisition) translates smart meter data into actionable information for both utilities and customers. The platform provides residential customers with real-time water use dashboards, leak alerts, usage threshold notifications, irrigation analysis, and peer comparison (how your usage compares to similar households). A 2025 study found the app reduced average household water use by 6%, with greater savings among heavy users. WaterSmart provides similar capabilities focused on utility-side analytics, customer engagement, and water efficiency program management.

Transferable pattern: Three key patterns:

1. Peer comparison: Dropcountr shows how your water use compares to similar households. SimplyScapes could show how your irrigation schedule compares to the calculated optimum -- are you watering 20% more than the QWEL formula recommends?
2. Usage threshold alerts: Dropcountr alerts when usage nears costly rate tiers. SimplyScapes could alert when cumulative irrigation exceeds the MWELO water budget (MAWA).
3. Irrigation analysis from meter data: Dropcountr can estimate irrigation water use from whole-house meter data. SimplyScapes has more precise data -- it knows exactly how much water should be applied per zone from the design calculations.

SimplyScapes adaptation: The utility-side analytics pattern suggests a contractor-facing dashboard that aggregates water use across all managed properties, showing which properties are over/under their water budgets. The peer comparison model could extend to comparing actual water use against design-predicted water use, providing a "water efficiency score" per property.

What doesn't transfer: Dropcountr requires smart meter data from the utility. SimplyScapes estimates water use from controller runtimes and design-computed PR. Dropcountr operates at whole-household granularity; SimplyScapes operates at per-zone granularity. The utility partnership model is a different business channel than SimplyScapes' contractor-focused approach.

---

11. AgTech Irrigation Startups (Phytech / Hortau / Sentek) -- Sensor-Model Fusion

Their solution:

• Phytech measures changes in stem/trunk diameter to detect plant stress before visible symptoms appear. In 2024-2025, Phytech launched AI Advisor (the first AI-powered irrigation advisor trained on real in-field IoT data), integrated with Manna's satellite remote sensing, and partnered with Netafim GrowSphere. Coverage: 45 million trees across 18,000 sites globally.
• Hortau uses soil tension probes (measuring how hard plants must work to extract water) rather than volumetric moisture, arguing tension is the only method that directly measures water availability to plants. Each advisor, aided by AI, creates weekly irrigation schedules. Studies show 20% water reduction in California almonds.
• Sentek provides multi-depth soil sensing (EnviroSCAN to 40m depth, TriSCAN for moisture + salinity separation) with IrriMAX software for visualization. Reports 30-50% water savings.

Transferable pattern: These three companies represent a progression from pure sensing to sensor + AI fusion:

1. Phytech's plant-based sensing: Measuring the plant's actual response (stress) rather than environmental proxies (soil moisture, weather). For turf, the equivalent would be detecting stress through visual assessment, NDVI, or thermal imaging.
2. Hortau's soil tension approach: Measuring water availability rather than water content. This is more meaningful for scheduling because the same volumetric moisture means different things in different soils.
3. Sentek's multi-depth profiling: Understanding where roots are actually extracting water. For turf, this reveals whether roots are shallow (frequent watering needed) or deep (infrequent deep watering effective).

SimplyScapes adaptation: These sensor platforms demonstrate the progression path from Phase 1 (ET-only) to advanced:

• Phase 1: ETo + PF + DU (no sensors)
• Phase 2: Add weather forecast integration (7-day Penman-Monteith from Open-Meteo)
• Phase 3: Add optional soil moisture sensor integration (validate ET-based predictions)
• Phase 4: Add plant health monitoring (thermal/NDVI from smartphone camera or satellite)

What doesn't transfer: All three require physical sensors installed in the field -- prohibitive cost for residential turf. Phytech's per-plant monitoring is irrelevant for turf (a grass is not a tree). Hortau's advisory service model requires human agronomists. Sentek's multi-depth sensing is overkill for shallow-rooted turf.

---

12. Weather Data Providers with ET Products (DTN/ClearAg)

Their solution: DTN acquired Iteris' ClearAg platform in 2020, gaining an Irrigation Decision Support API that provides localized, predictive irrigation analytics without requiring hardware. ClearAg's EvapoSmart service delivers crop-specific ET data using crop coefficients, with hourly data available for any global location from January 1 of the previous year through 9 days into the future. The service was designed for the water budget calculation use case and includes reference ET, crop coefficients, crop potential ET, and precipitation data.

Transferable pattern: ClearAg demonstrates that ET-based irrigation intelligence can be delivered as a cloud API service without requiring on-site hardware. The 9-day forecast capability enables predictive scheduling (adjusting this week's irrigation based on expected rainfall next week). The crop coefficient approach (adjusting reference ET for specific crops) is exactly the QWEL formula chain's species factor.

SimplyScapes adaptation: ClearAg-style ET APIs (or equivalently, Open-Meteo's free ET API) provide the weather data layer for the QWEL formula chain. The 9-day forecast integration enables proactive schedule adjustment -- skip today's irrigation if rain is forecast for tomorrow. This is a quick win for Phase 1 that every smart controller does (rain skip), but SimplyScapes can do it more precisely because it knows the exact water deficit from the design-computed schedule.

What doesn't transfer: ClearAg's crop coefficients are for agricultural crops, not landscape turfgrass. Their pricing model is per-API-call, which may not align with a consumer product. Their global coverage is broader than needed for a US-focused residential platform.

---

13. Energy Management / Demand Response -- Water Restriction Response

Their solution: Electric utilities use demand response programs to shift peak electricity consumption to off-peak hours. Smart thermostats (Nest, Ecobee) participate by pre-cooling homes before peak periods and reducing cooling during demand events. A 2023 ASCE paper (Lunstad & Sowby) specifically proposed applying the electric grid's demand response concept to residential irrigation, showing that smart irrigation controllers could coordinate thousands of customers to spread water usage across time slots, reducing peak flows, managing storage/pressure, and lowering pumping energy costs.

Transferable pattern: The demand response analogy is powerful for water restriction compliance:

1. Restriction-aware scheduling: Just as Nest shifts HVAC load away from peak electricity hours, irrigation controllers should shift watering away from restricted days/times. SimplyScapes already displays water district restrictions (Weber Basin) in the UI.
2. Graduated response: Demand response has stages (voluntary conservation, mandatory curtailment, rolling blackouts). Water restrictions follow the same pattern (voluntary targets, mandatory odd/even days, total outdoor watering bans). The scheduling algorithm should support multiple restriction levels.
3. Pre-restriction buffering: Nest pre-cools before a demand event. Irrigation could pre-water before a restriction period begins, applying a deeper watering to build soil moisture reserve.
4. Portfolio coordination: Utilities coordinate across thousands of buildings. A landscape contractor managing dozens of properties could coordinate irrigation schedules to comply with community-wide restrictions while minimizing turf stress.

SimplyScapes adaptation: The restriction-response framework maps directly:

• Normal mode: Schedule from QWEL formula chain
• Stage 1 (voluntary conservation): Reduce PF by 10-20%, extend cycle intervals
• Stage 2 (mandatory restrictions): Comply with odd/even days, permitted time windows, reduced days-per-week
• Stage 3 (severe restrictions): Survival watering only -- minimum water to prevent turf death
• Emergency (ban): Zero irrigation, provide drought recovery guidance

What doesn't transfer: Electricity demand response operates in real-time (minutes). Water restriction response operates on days/weeks. The financial incentive structure is different (electricity: time-of-use pricing; water: tiered rate structures). Pre-restriction buffering works for electricity (thermal mass stores cooling) but is limited for irrigation (soil can only store so much water before it drains).

---

14. Banyan Water -- Portfolio-Scale Commercial Water Management

Their solution: Founded in 2011, Banyan Water provides commercial water management with real-time leak detection and automated irrigation solutions. In 2023 alone, their patented leak detection identified 242 irrigation leaks, saving 138 million gallons. Total savings: 5.8 billion gallons verified through utility data. The platform installs IoT devices and weather-tracking technology on existing irrigation systems, creating schedules based on property needs, weather patterns, and landscape updates. Portfolio-wide dashboards empower businesses to save 40-60% on water costs.

Transferable pattern: Banyan demonstrates the commercial-scale version of what SimplyScapes targets for residential: design-informed, weather-adjusted irrigation scheduling with leak detection. Their portfolio management dashboard (aggregating water data across multiple properties) is the model for SimplyScapes' contractor-facing features. Their patented leak detection (comparing expected vs. actual flow) validates the value of having a design-predicted baseline to compare against operational data.

SimplyScapes adaptation: The portfolio management pattern directly applies to landscape contractors managing multiple residential properties. The leak detection approach (expected flow from design vs. actual flow from meter/controller) is enabled by SimplyScapes' design-computed data. A contractor dashboard showing water budget compliance across all managed properties would be a high-value feature.

What doesn't transfer: Banyan's IoT hardware installation model is cost-prohibitive for residential. Their subscription model ($X/property/month) targets commercial real estate portfolios, not individual homeowners. Their water savings verification through utility data requires utility partnerships.

---

15. Turfgrass Research Tools -- Water My Yard (Texas A&M AgriLife)

Their solution: Water My Yard is a free app from Texas A&M AgriLife Extension that provides weekly customized irrigation recommendations based on local ET data from 57 specialized weather stations. The app tells homeowners when and how many minutes to run their irrigation systems. Coverage: 30% of Texas single-family homes. Impact: estimated 2.7 billion gallons/year saved statewide, approximately $230/household/year in water cost savings.

Transferable pattern: Water My Yard is the closest existing product to SimplyScapes' Phase 1 turf scheduling concept -- ET-based recommendations delivered to homeowners. Key differences that reveal SimplyScapes' advantage:

1. Water My Yard uses generic assumptions for DU and PR (it doesn't know the user's actual irrigation system). SimplyScapes knows the exact DU and PR from the design.
2. Water My Yard provides one recommendation for the user's lawn type. SimplyScapes can provide per-zone recommendations with zone-specific DU, PR, and turf type.
3. Water My Yard requires a nearby weather station. SimplyScapes can use gridded weather data (Open-Meteo) for any location.

SimplyScapes adaptation: Water My Yard validates the market for ET-based residential irrigation recommendations and demonstrates the water savings potential ($230/household/year). SimplyScapes' design-computed approach is strictly more precise because it incorporates system-specific DU and PR rather than generic assumptions.

What doesn't transfer: Water My Yard's success depends on a network of 57 physical weather stations in Texas. SimplyScapes should not require physical infrastructure. Water My Yard is a free public service funded by water utilities; SimplyScapes needs a commercial business model.

---

16. RainMachine -- Open Source ET-Based Controller

Their solution: RainMachine is a cloud-independent smart irrigation controller that performs all weather processing locally. The device uses open-source Penman-Monteith ET calculations with data from 12+ weather sources (NOAA, CIMIS, NetAtmo, Davis, Open Weather Map, etc.). The ET formula source code and API are published and verifiable. RainMachine uses 7-day forecasts to adjust watering schedules.

Transferable pattern: RainMachine demonstrates that open-source, locally-computed ET scheduling is viable and can work without a cloud dependency. Their multi-source weather data aggregation (pulling from 12+ sources) is a pattern for robustness -- if one weather source is unavailable or inaccurate, others compensate. The cloud-independent architecture is relevant for privacy-conscious users and offline reliability.

SimplyScapes adaptation: RainMachine validates the Penman-Monteith approach for residential irrigation but has the same limitation as all controllers -- it doesn't know the system's DU or PR. SimplyScapes' contribution is adding the design-computed DU and PR as additional inputs to the same ET calculation, converting a generic recommendation into a system-specific schedule. RainMachine's open-source ET code could be referenced to validate SimplyScapes' own ET calculations.

What doesn't transfer: RainMachine is a hardware product (controller). SimplyScapes is a software platform that pushes schedules to existing controllers. RainMachine's local processing model means no server-side intelligence; SimplyScapes benefits from cloud processing for design analysis.

---

17. OpenSprinkler -- Open Source Controller + Community

Their solution: OpenSprinkler is an open-source web-based irrigation controller supporting up to 72 zones (with expanders). It features a weather-based algorithm that adjusts watering based on local weather data, MQTT support, flow sensor integration, HTTP(S) API, and email notifications. The hardware is available as a DIY kit or pre-assembled unit. The software, firmware, and API are fully open source on GitHub.

Transferable pattern: OpenSprinkler demonstrates the open-source/DIY community's approach to irrigation scheduling. Their REST API provides a model for how SimplyScapes could push schedules to controllers. The weather-adjustment algorithm (adjusting run times based on rain, temperature, and humidity) is a simpler version of ET-based scheduling. The flow sensor integration enables actual vs. predicted water use comparison.

SimplyScapes adaptation: OpenSprinkler's REST API is well-documented and could be a controller integration target alongside Rachio. The open-source community has effectively reverse-engineered irrigation scheduling, validating the approach. SimplyScapes could position itself as the "design intelligence layer" that feeds into OpenSprinkler (and other controllers) with more precise scheduling data than the controller can compute on its own.

What doesn't transfer: OpenSprinkler is a niche product for hobbyists/makers, not a mainstream consumer product. Its scheduling algorithm is simpler than full ET-based scheduling (weather adjustment percentages rather than Penman-Monteith ET calculations). The DIY installation model doesn't align with SimplyScapes' professional contractor focus.

---

PART 2: Academic & Open Source Scan

This section surveys academic research, university programs, and open-source tools relevant to automated turf irrigation scheduling from design-time intelligence.

Academic Literature Findings

A. Turfgrass Water Requirements and Crop Coefficients

Turfgrass Crop Coefficients (UC Davis Center for Landscape & Urban Horticulture) UC ANR has published species-specific turfgrass Kc values based on controlled research. Annual average Kc values are most commonly used, but monthly values more precisely capture seasonal variation. Key finding: cool-season grasses (tall fescue, Kentucky bluegrass, perennial ryegrass) have Kc values around 0.80, while warm-season grasses (bermudagrass, buffalograss, zoysiagrass) have Kc values around 0.60. The difference in water requirements between species is approximately 20-40%.

Dynamic Water Use Models (USGA / NMSU, 2025) Research at New Mexico State University developed variable crop coefficient (Kc) models normalized by Growing Degree Days (GDD) or week-of-year (WOY). Key findings:

• Switching from fixed Kc to variable GDD-based Kc reduced annual irrigation by ~10% for cool-season grasses and ~15% for warm-season grasses.
• Fixed Kc values overwater in spring and fall and occasionally underwater in peak summer.
• Peak water use: cool-season grasses 0.21-0.26 in/day; warm-season grasses 0.18-0.20 in/day.
• This is the first study to develop GDD-adjusted Kc models specifically for turfgrass.
• The models emphasize minimum water for acceptable quality rather than optimal conditions.

Minimum Water Requirements in the Transition Zone (Qian & Engelke, HortScience) Study of four turfgrasses in the transition zone found minimum annual irrigation ranging from 244 mm (bermudagrass) to 552 mm (Kentucky bluegrass), a 2.3x difference. This validates species-specific scheduling over one-size-fits-all approaches.

Texas A&M AgriLife Turfgrass Research (2024) The AggieTurf program evaluated five cultivars (Cobalt and Raleigh St. Augustine, Palisades zoysia, Tifway and TifTuf bermuda) at 80%, 60%, 50%, and 40% ET replacement. Key finding: Cobalt St. Augustine maintained acceptable quality for 70 days at 50% ET replacement -- 14 days longer than TifTuf bermuda and 27 days longer than Palisades zoysia. This demonstrates that cultivar-specific (not just species-level) scheduling can significantly impact water conservation.

Oregon State Water Requirements Study (Blankenship, 2020) Evaluated water requirements of tall fescue, perennial ryegrass, creeping bentgrass, and Kentucky bluegrass in western Oregon. Key finding: tall fescue and perennial ryegrass required only 26-36% ETref replacement, while fine fescues at 5/8-inch mowing height required 95-98% ETref. Mowing height significantly affects water requirements -- a scheduling factor not captured by species-level PF alone.

B. Species-Specific Dormancy and Growing Season

Growing Degree Days for Turfgrass Management (Purdue, Syngenta GreenCast) GDD base temperatures for turfgrass:

• Cool-season grasses: base temperature 0C (32F)
• Warm-season grasses: base temperature 10C (50F)
• EPA WaterSense 2.0 uses a universal 50F base, which is incorrect for cool-season turf (overestimates dormancy duration, cutting irrigation season short) and approximately correct for warm-season turf.

Cool-Season Growth Thresholds:

• Active growth: daytime air 60-75F, nighttime mid-50s
• Minimal growth below 50F air/soil temperature
• Dormancy triggered by sustained temperatures above 90F (summer dormancy in heat-stressed regions)

Warm-Season Growth Thresholds:

• Break dormancy when nighttime soil temperatures consistently above 60F
• Active growth: daytime 80-95F, nighttime around 72F
• Dormancy triggered by first frost or sustained nighttime temperatures below 55-60F

C. Distribution Uniformity Simulation and Modeling

ML-Based DU Prediction (Scientific Reports, 2023) Random Forest, XGB, and XGB-RF algorithms predicted sprinkler water distribution uniformity based on operating pressure, sprinkler height, discharge, nozzle diameter, wind speed, humidity, and temperature. This validates that DU can be predicted from system parameters rather than measured in the field -- the same principle behind SimplyScapes' design-computed DU.

GIS-Based DU Simulation (Sustainability, 2022) QGIS + EPANET simulation strategy for geospatial representation of applied water and DU assessment across entire installations. This approach models water distribution from individual emitter performance data overlaid on spatial layouts -- conceptually similar to SimplyScapes' coverage scoring from head placement.

Harmonic Analysis DU Model (Computers and Electronics in Agriculture, 2024) Analytical model for single sprinkler uniformity and combined sprinkler combinations using harmonic analysis. The finite element method approach provides a mathematical framework for predicting DU from sprinkler geometry.

COMSOL Soil Moisture Uniformity (Journal of Hydrology, 2023) Numerical simulation of soil water movement under sprinkler irrigation, finding that soil redistribution partially compensates for sprinkler non-uniformity. Key implication: actual root-zone uniformity is higher than surface DU -- design-computed DU may be conservative, which is a desirable property for scheduling.

D. Smart Irrigation and Machine Learning

Smart Irrigation Controllers in Residential Applications (ASCE JWRPM, 2024) Lunstad & Sowby reviewed 80 studies across US, Canada, and Australia. Key findings:

• Smart controllers reduce water demand by 15% for average users, 40%+ for heavy users.
• Weather-based (ET) controllers and soil moisture controllers achieve similar savings.
• Proposed applying electric grid demand response concepts to irrigation.
• First comprehensive meta-analysis of residential smart irrigation performance.

Deep Reinforcement Learning for Irrigation Scheduling (PLOS Water, 2023) Saikai, Peake, and Chenu demonstrated deep RL for irrigation using high-dimensional sensor feedback. The approach learns optimal irrigation policies from simulated crop growth models, adjusting water application based on state (soil moisture, crop stage, weather forecast).

Machine Learning and Digital Twins in Smart Irrigation (Taylor & Francis, 2025) Comprehensive review categorizing ML approaches for irrigation: LSTMs for ET/soil moisture forecasting, reinforcement learning for adaptive scheduling, and digital twins for simulation-based optimization. Key finding: LSTMs outperform traditional time-series models for ET forecasting.

Application of ML in Irrigation Decision Making (Agricultural Water Management, 2024) Review of ML approaches including ANNs, SVMs, Random Forests, and deep learning for irrigation scheduling. Notes that ML models require large training datasets and remain "black box" -- a limitation for regulatory compliance where QWEL/MWELO formulas provide transparent, auditable calculations.

E. Satellite and Remote Sensing ET

OpenET Accuracy Assessment (Nature Water, 2023) Velpuri et al. assessed OpenET against 152 ground-based measurement sites. For annual crops in Mediterranean climates, monthly error rates were consistently below 10% during peak growing season. The ensemble of 6 models produces more accurate results than any individual model.

OpenET Urban Turfgrass Validation (AGU Fall Meeting, 2024) First study specifically validating OpenET satellite-based ET for urban turfgrass. Preliminary results show OpenET can estimate temporal and spatial variability of daily actual ET for both irrigated and non-irrigated turfgrass. This is early-stage research but highly relevant for landscape water management.

OpenET Model Weighting (Water Resources Research, 2025) Reitz et al. developed performance-weighted ensemble approach showing no single model dominates across all metrics and landscapes. Recommends application-specific model selection or weighted ensembles.

ECOSTRESS High-Resolution Urban ET (NASA/JPL, ongoing) ECOSTRESS provides 70m resolution thermal data from ISS, with urban heat island and landscape water use applications. Collection 2 (released January 2024) improved calibration and ET models. As of January 2025, over 500,000 scenes acquired. The 70m resolution is finer than Landsat (30m for visible, ~100m for thermal) but still too coarse for individual residential zones.

USU Extension Satellite-Based Urban ET (USU CWEL) Utah State University's Center for Water-Efficient Landscaping is developing satellite-based urban ET estimation methods. This represents the bridge between agricultural satellite ET (well-validated) and landscape irrigation applications (emerging).

F. WUCOLS and Landscape Coefficient Methodology

WUCOLS Validation Study (ResearchGate, 2022) Evaluation of the WUCOLS method for estimating water requirements of landscape plants found it produces the most precise, complete, and practical estimates compared to alternative approaches and had the closest agreement with irrigation records.

Water Requirements Comparison of Three Factor-Based Approaches (Landscape and Urban Planning, 2013) Compared WUCOLS, UC Davis LIMP, and Colorado Water Conservation Board methods. Found significant variation between approaches, with WUCOLS providing the most comprehensive species coverage and best validation against field data.

WUCOLS Application in Arid Environments (Ecological Informatics, 2023) Applied WUCOLS method to Iran's National Botanical Garden, demonstrating applicability outside California. Results showed WUCOLS was effective for estimating irrigation demand in arid climates when local ETo data was available.

G. Digital Twin for Irrigation

Digital Twin for Smart Farming Irrigation (J. Cleaner Production, 2023) Developed a FIWARE-based IoT platform + discrete event simulation model for irrigation. Results: 15-20% yield increase, 30-40% water use reduction. The digital twin allows evaluating different irrigation strategies before field implementation.

Harnessing Digital Twins for Sustainable Agricultural Water Management (Applied Sciences, 2025) Systematic review finding gradual growth (1 publication in 2021 to 4 each in 2023-2024). Technology has not yet achieved widespread adoption. Key challenge: integrating heterogeneous data sources (sensors, weather, soil maps, crop models) into a coherent simulation.

---

Open Source Tools and Data Sources

| Tool/Resource | Type | Description | License | Relevance | |---------------|------|-------------|---------|-----------| | pyETo | Python library | FAO-56 Penman-Monteith ETo calculation. Functions for unit conversion and missing data estimation. | BSD 3-Clause | Core ET calculation. Source-level integration required (no pip install). | | pyet | Python library | Alternative ET library supporting 1D (pandas) and 3D (xarray) data. Multiple ET methods. | Open source | More modern alternative to pyETo with better installation support. | | pyfao56 | Python library | USDA-ARS implementation of FAO-56 dual crop coefficient + daily soil water balance. Version 1.4.0 (2024) adds single Kc, weather-adjusted Kc, and FAO-56 tables. | Open source | Most comprehensive ET + water balance implementation. Peer-reviewed (SoftwareX). | | OpenET | Web platform + API | Satellite-derived ET at 30m resolution. Ensemble of 6 models. Free public access. 48-state coverage. | Public data | Validation source for weather-station ETo. Field-scale actual ET. | | WUCOLS V | Database | 4,100+ taxa water use classifications across 6 CA climate zones. | Public domain | Species factor (Ks) data for landscape coefficient calculation. | | CIMIS | API + weather network | California Irrigation Management Information System. 150+ stations. Daily/hourly ETo. | Public data | Reference ETo data for California. Model for state-level ET networks. | | Open-Meteo | Free API | Global weather + ETo data. Historical, current, and 16-day forecast. No API key required. | Open source | Primary weather/ETo data source for Phase 1. Already used in SS-TD-2026-001. | | USU Climate Center | API | ETo by zip code for western US states. Monthly averages. | Public data | Already identified as ETo source in plan. US-focused coverage. | | OpenSprinkler | Controller + firmware | Open source irrigation controller with REST API. GitHub-hosted firmware. | GPL | Reference implementation for controller integration. REST API documentation. | | RainMachine | Controller + SDK | Open source ET scheduling algorithm. Open API for third-party integration. | Open source | Reference implementation for Penman-Monteith irrigation scheduling. | | NTEP Data | Database | National Turfgrass Evaluation Program trial data for species/cultivar performance. | Public data | Cultivar-level performance data for water requirements. 2024 cool-season water use reports. | | UC Davis LAWR Spreadsheet | Spreadsheet tool | Annual irrigation calendar from ETo + DU + soil type + wetting depth. | Public data | Reference implementation of the same calculation SimplyScapes automates. | | Water My Yard | Web app | ET-based residential irrigation recommendations for Texas. 57 weather stations. | Public service | Validation dataset for ET-based residential scheduling approach. | | gridMET | Gridded dataset | Daily surface meteorological data (4km resolution) including ETo for CONUS. | Public data | Alternative ETo source with complete US coverage. |

---

Consolidated Reference Table

| # | Type | Reference | Date | Relevance to SS-RR-2026-002 | |---|------|-----------|------|------------------------------| | 1 | Journal | Lunstad & Sowby. "Smart Irrigation Controllers in Residential Applications." ASCE JWRPM 150(1). | 2024 | Meta-analysis: 80 studies, 15-40% water savings. Demand response analogy. | | 2 | Journal | Velpuri et al. "Assessing the accuracy of OpenET satellite-based ET data." Nature Water. | 2023 | OpenET validation: <10% monthly error in Mediterranean climates. | | 3 | Journal | Reitz et al. "Performance Mapping and Weighting for OpenET Ensemble." Water Resources Research. | 2025 | No single ET model dominates; weighted ensembles recommended. | | 4 | Conference | AGU Fall Meeting H11P-0899. "Validating OpenET for urban turfgrass." | 2024 | First urban turfgrass OpenET validation study. | | 5 | Journal | Saikai et al. "Deep RL for irrigation scheduling using high-dimensional sensor feedback." PLOS Water. | 2023 | RL-based irrigation scheduling proof of concept. | | 6 | Journal | "Machine learning and digital twins in smart irrigation." Taylor & Francis. | 2025 | Comprehensive review: LSTM, RL, digital twin approaches. | | 7 | Journal | "Application of ML in irrigation decision making." Agricultural Water Management. | 2024 | ML review: datasets, black-box limitations, regulatory concerns. | | 8 | Journal | "Prediction of DU based on machine learning." Scientific Reports. | 2023 | ML-predicted DU from system parameters (validates design-computed DU concept). | | 9 | Journal | "Extended Assessment of Sprinkler Uniformity Using GIS." Sustainability. | 2022 | QGIS + EPANET simulation for geospatial DU assessment. | | 10 | Journal | "DU evaluation using harmonic analysis and FEM." Computers & Electronics in Agriculture. | 2024 | Analytical DU model from sprinkler geometry. | | 11 | Journal | "Soil water content uniformity under sprinkler irrigation." Journal of Hydrology. | 2023 | Soil redistribution compensates for surface non-uniformity. | | 12 | Journal | "Digital Twin for smart farming irrigation." J. Cleaner Production. | 2023 | 30-40% water reduction using digital twin irrigation management. | | 13 | Review | "Harnessing Digital Twins for Agricultural Water Management." Applied Sciences. | 2025 | Systematic review: technology still early-stage (4 papers/year). | | 14 | USGA | "Dynamic Water Use Models for Improved Irrigation Scheduling." Green Section Record 63(17). | 2025 | GDD-adjusted Kc reduces irrigation 10-15% vs. fixed Kc for turfgrass. | | 15 | USGA | Huang. "Turfgrass Water Requirements and Factors Affecting Water Usage." | 2006 | Foundational reference: species-specific water use data. | | 16 | Journal | Blankenship. "Water requirements influenced by species and mowing height." Crop, Forage & Turfgrass Mgmt. | 2020 | Tall fescue/ryegrass: 26-36% ETref; fine fescues: 95-98% ETref. | | 17 | Journal | Qian & Engelke. "Minimum Water Requirements of Four Turfgrasses." HortScience. | 2015 | Bermuda 244mm vs. bluegrass 552mm annual irrigation. | | 18 | UC ANR | Turfgrass Crop Coefficients (Kc). Center for Landscape & Urban Horticulture. | ongoing | Species-specific Kc values: cool-season ~0.80, warm-season ~0.60. | | 19 | UC Davis | WUCOLS V. Water Use Classification of Landscape Species. | 2014 | 4,100+ taxa. Public domain. Foundation for landscape Ks. | | 20 | ANSI | ANSI/ASABE S623.1 (R2022). Determining Landscape Plant Water Demands. | 2022 | National standard based on SLIDE rules. Zone-level management. | | 21 | USU | SLIDE Rules. Simplified Landscape Irrigation Demand Estimation. | ongoing | Four rules for landscape water demand. Basis for S623.1. | | 22 | Journal | "Evaluation of WUCOLS Method for Estimating Water Requirements." ResearchGate. | 2022 | WUCOLS validated as most accurate landscape water estimation method. | | 23 | Journal | "Water requirements: comparison of three factor-based approaches." Landscape & Urban Planning. | 2013 | WUCOLS vs. LIMP vs. CWCB comparison. | | 24 | Software | pyfao56 v1.4.0. USDA-ARS. FAO-56 dual crop coefficient + soil water balance. | 2024 | Peer-reviewed Python ET implementation. | | 25 | Software | pyETo. FAO-56 Penman-Monteith ETo in Python. | ongoing | Lightweight ET calculation library. | | 26 | Software | pyet. Python ET package for 1D/3D data. | ongoing | Modern alternative to pyETo. | | 27 | Platform | OpenET (etdata.org). Satellite ET at 30m for 48 states. | 2024 | Free ET validation data. Ensemble of 6 models. | | 28 | Platform | ECOSTRESS. NASA/JPL. 70m thermal/ET from ISS. | 2024 | Higher resolution than Landsat for urban ET. Collection 2 released. | | 29 | App | Water My Yard. Texas A&M AgriLife. ET-based lawn watering recommendations. | ongoing | Validates ET-based residential scheduling market. $230/household/year savings. | | 30 | Data | NTEP 2024 Cool-Season Water Use Reports. | 2024 | Cultivar-level turfgrass water performance data. | | 31 | UC Davis | SmartLawn Project. CCUH. 2023 water use data by turf type. | 2023 | Empirical turf water use under controlled conditions. | | 32 | Extension | Syngenta GreenCast GDD. GDD base temperatures for turf management. | ongoing | Cool-season base 0C, warm-season base 10C. | | 33 | Extension | Purdue Turf. "Use GDD to Better Time Your Applications." | ongoing | GDD methodology for turfgrass management timing. | | 34 | UF/IFAS | AE446. Smart Irrigation Controllers: ET-Based Controllers. | ongoing | Extension guide for ET controller operation and configuration. | | 35 | Journal | Pierrat et al. "Evaluation of ECOSTRESS Collection 2 ET Products." Water Resources Research. | 2025 | ECOSTRESS validation: strengths and uncertainties for ET modeling. | | 36 | Standard | QWEL certification program. Qualified Water Efficient Landscaper. | ongoing | Formula chain: ETo x PF / DU = runtime. Industry training standard. | | 37 | Standard | EPA WaterSense Water Budget Tool v2.0. | ongoing | GRDD-based growing season with universal 50F threshold. |

---

PART 3: Cross-Industry Insights

Big Ideas from Adjacent Markets Not Yet Applied to Landscape Irrigation

1. Design-Computed Performance Prediction (from Solar) Solar energy's design-to-monitoring pipeline is well-established: predict performance from geometry, then validate with operational data. No landscape irrigation product uses design geometry to predict system performance. SimplyScapes' design-computed DU is the irrigation equivalent of solar panel layout performance prediction. This is the core novelty.

2. Variable Crop Coefficients by Growth Stage (from AgTech + USGA Research) Agricultural platforms (Netafim, CropX) have used growth-stage-adjusted water demand for decades. The 2025 USGA study proves this works for turfgrass too (10-15% water savings from GDD-adjusted Kc). No residential irrigation controller or scheduling platform uses variable Kc values -- they all use fixed species factors year-round. SimplyScapes could be first to implement GDD-normalized Kc for residential turf scheduling.

3. Demand Response Framework for Water Restrictions (from Energy) The electric grid's demand response model (graduated response levels, pre-event buffering, portfolio coordination) has been proposed for irrigation (Lunstad & Sowby, 2024 ASCE) but not implemented in any product. SimplyScapes' restriction-aware scheduling (already showing Weber Basin alerts in the UI) could formalize this into a multi-stage response framework.

4. Ensemble Model Approach (from OpenET) OpenET's finding that no single ET model dominates and weighted ensembles perform best suggests SimplyScapes should aggregate multiple weather/ET data sources rather than relying on a single API. The ensemble approach could extend to soil moisture estimation (combining multiple models rather than trusting one).

5. Degradation Detection from Design Baseline (from Solar + Digital Twins) Solar monitoring detects panel degradation by comparing actual vs. predicted output. Building digital twins detect HVAC degradation from sensor drift. No irrigation product compares actual water use against a design-predicted baseline to detect system degradation (clogged nozzles, pressure loss, coverage gaps). SimplyScapes' design data provides this baseline.

6. Portfolio-Level Water Intelligence (from Banyan Water + Dropcountr) Commercial water management (Banyan) and utility analytics (Dropcountr) provide portfolio-level dashboards, but only for commercial properties with smart meters. No product provides portfolio-level water intelligence for residential irrigation contractors managing dozens of properties. SimplyScapes' design data enables this without smart meters -- predicted water use per property can be aggregated across a contractor's entire portfolio.

7. Peer Comparison and Behavioral Nudges (from Dropcountr) Dropcountr's peer comparison (your water use vs. similar households) drives 6% average water savings. The irrigation equivalent would be comparing your actual irrigation (from controller data) against the QWEL-computed optimum, or comparing your property's water use against similar properties with similar landscapes. No irrigation product does this.

8. Plant-Based Stress Detection Before Symptoms (from Phytech) Phytech's trunk diameter sensors detect tree stress 24-48 hours before visible symptoms. For turf, the equivalent would be thermal or NDVI imaging (from smartphone cameras or satellites) to detect turf stress before it becomes visible wilting. This is a Phase 3+ opportunity that no residential product has implemented.

9. Soil Redistribution Compensates for Surface Non-Uniformity (from Academic Research) The 2023 Journal of Hydrology study showing that soil water movement partially compensates for sprinkler non-uniformity is highly relevant. It means design-computed DU (which measures surface uniformity) is conservative -- actual root-zone uniformity is higher than surface DU. This provides a scientific basis for trusting design-computed DU without applying large safety factors.

10. Open Source ET Calculation is a Commodity (from pyETo/pyfao56/RainMachine) The Penman-Monteith ET calculation is well-implemented in multiple open-source packages (pyETo, pyet, pyfao56) and controllers (RainMachine, OpenSprinkler). The ET calculation itself is not the innovation -- it's a commodity. The innovation is what inputs you feed into it (design-computed DU and PR) and how you apply the output (per-zone schedules pushed to controllers).

Cross-Reference Summary: SS-RR-2026-001 Validated Findings Applied to Turf Scheduling

The following findings from the drip irrigation research (SS-RR-2026-001) are directly applicable and should be treated as validated context for SS-RR-2026-002:

| Finding | SS-RR-2026-001 Source | Application to Turf Scheduling | |---------|----------------------|-------------------------------| | All controllers operate at zone level, not per-plant | Competitive analysis (residential) | Turf scheduling is inherently zone-level, validating the QWEL per-zone approach | | No competitor derives DU from design geometry | Competitive analysis (residential + commercial) | Confirmed novelty of design-computed DU for turf scheduling | | Rachio API v2 supports schedule push (1,700 calls/day) | Controller integration | Same API for pushing turf schedules to Rachio controllers | | WUCOLS is public domain | Adjacent market scan | Turf PF values from WUCOLS are freely usable | | MWELO formula is government regulation | Adjacent market scan | QWEL formula chain is based on the same methodology | | Netafim GrowSphere is closest analog for lifecycle-aware scheduling | Adjacent market scan | Applied to turf establishment (post-seeding/sodding) lifecycle | | Competitive landscape divides into controllers vs. platforms vs. design tools | Competitive analysis | SimplyScapes bridges design tools -> scheduling, a gap nobody fills | | US10028454B2 (Husqvarna/ETwater) has hardware-tied claims | Patent landscape | Software-only approach has favorable FTO for turf scheduling too | | 3-phase establishment tapering model | Establishment lifecycle | Applicable to turf establishment after sodding/overseeding |

---

Source Bibliography

1. Netafim. "GrowSphere Crop Advisor." https://www.netafim.com/en/digital-farming/crop-advisor/
2. CropX. "Digital Agronomy Platform." https://cropx.com/
3. OpenET. "Open-Source Transparent Water Management Data." https://etdata.org/
4. Climate FieldView (Bayer). https://www.cropscience.bayer.us/tools/fieldview
5. Google Nest. "How Nest thermostats learn." https://support.google.com/googlenest/answer/9247510
6. SolarEdge / Enphase monitoring platforms. https://www.a-rsolar.com/blog/solaredge-monitoring-vs-enphase-monitoring/
7. Willow Digital Twin. https://willowinc.com/willow-digital-twin
8. WUCOLS V. UC Davis. https://wucols.ucdavis.edu/
9. USU CWEL SLIDE Rules. https://extension.usu.edu/cwel/slide-rules
10. ANSI/ASABE S623.1 (R2022). https://webstore.ansi.org/standards/asabe/ansiasabes623jan2017r2022
11. Dropcountr (KUBRA). https://www.dropcountr.com/
12. Phytech. https://www.phytech.com/
13. Hortau. https://hortau.com/
14. Sentek Technologies. https://sentektechnologies.com/
15. DTN / ClearAg. https://docs.clearag.com/
16. Banyan Water. https://banyanwater.com/
17. RainMachine. https://www.rainmachine.com/
18. OpenSprinkler. https://opensprinkler.com/
19. Water My Yard (Texas A&M AgriLife). https://watermyyard.org/
20. Lunstad & Sowby. "Smart Irrigation Controllers in Residential Applications." ASCE JWRPM 150(1), 2024. https://ascelibrary.org/doi/10.1061/JWRMD5.WRENG-5871
21. Velpuri et al. "Assessing the accuracy of OpenET." Nature Water, 2023. https://www.nature.com/articles/s44221-023-00181-7
22. Reitz et al. "Performance Mapping for OpenET Ensemble." WRR, 2025. https://agupubs.onlinelibrary.wiley.com/doi/10.1029/2024WR038899
23. Saikai et al. "Deep RL for irrigation scheduling." PLOS Water, 2023. https://journals.plos.org/water/article?id=10.1371/journal.pwat.0000169
24. "Prediction of DU based on ML algorithms." Scientific Reports, 2023. https://www.nature.com/articles/s41598-023-47688-3
25. "Extended Assessment of Sprinkler Uniformity Using GIS." Sustainability, 2022. https://www.mdpi.com/2071-1050/14/15/9723
26. "Soil water content uniformity under sprinkler irrigation." J. Hydrology, 2023. https://www.sciencedirect.com/science/article/abs/pii/S0022169423012982
27. "Digital Twin for smart farming: Irrigation management." J. Cleaner Production, 2023. https://www.sciencedirect.com/science/article/abs/pii/S0959652623000781
28. USGA. "Dynamic Water Use Models for Improved Irrigation Scheduling." Green Section Record 63(17), 2025. https://www.usga.org/content/usga/home-page/course-care/green-section-record/63/issue-17/dynamic-water-use-models-for-improved-irrigation-scheduling.html
29. Huang. "Turfgrass Water Requirements." USGA. https://www.usga.org/content/dam/usga/pdf/Water%20Resource%20Center/turfgrass-water-requirements.pdf
30. Blankenship. "Water requirements influenced by species and mowing height." 2020. https://acsess.onlinelibrary.wiley.com/doi/full/10.1002/cft2.20020
31. UC ANR. Turfgrass Crop Coefficients. https://ucanr.edu/sites/UrbanHort/Water_Use_of_Turfgrass_and_Landscape_Plant_Materials/Turfgrass_Crop_Coefficients_Kc
32. pyETo. GitHub. https://github.com/woodcrafty/PyETo
33. pyet. GitHub. https://github.com/pyet-org/pyet
34. pyfao56. USDA-ARS. GitHub. https://github.com/kthorp/pyfao56
35. ECOSTRESS. NASA/JPL. https://ecostress.jpl.nasa.gov/
36. NTEP. National Turfgrass Evaluation Program. https://www.ntep.org/
37. UC Davis SmartLawn. https://ccuh.ucdavis.edu/resources/projects/smartlandscape-at-uc-davis/smartlawn
38. UC Davis LAWR. Water Balance Irrigation Scheduling. https://lawr.ucdavis.edu/cooperative-extension/irrigation/drought-tips/water-balance-irrigation-scheduling-using-cimis-eto
39. Texas A&M AgriLife Turfgrass Program. https://aggieturf.tamu.edu/
40. Purdue Turf. GDD Applications. https://turf.purdue.edu/use-growing-degree-days-to-better-time-your-applications/
41. Syngenta GreenCast GDD. https://www.greencastonline.com/growing-degree-days/learn-more
42. UF/IFAS AE446. ET-Based Smart Irrigation Controllers. https://edis.ifas.ufl.edu/publication/AE446
43. Pierrat et al. "Evaluation of ECOSTRESS Collection 2 ET Products." WRR, 2025. https://agupubs.onlinelibrary.wiley.com/doi/10.1029/2024WR039404
44. USU Extension. Satellite-Based Urban ET Estimation. https://extension.usu.edu/cwel/urban-et
45. "Harnessing Digital Twins for Agricultural Water Management." Applied Sciences, 2025. https://www.mdpi.com/2076-3417/15/8/4228
46. "ML and digital twins in smart irrigation." Taylor & Francis, 2025. https://www.tandfonline.com/doi/full/10.1080/27525783.2025.2562418
47. "Application of ML in irrigation decision making." Agricultural Water Management, 2024. https://www.sciencedirect.com/science/article/pii/S0378377424000453
48. SS-RR-2026-001. Plant-Specific Drip Irrigation Intelligence. Adjacent Market Scan. docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/plant-specific-drip-irrigation-intelligence/research/supporting/adjacent-market-scan.md
49. SS-RR-2026-001. Plant-Specific Drip Irrigation Intelligence. Establishment Lifecycle. docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/plant-specific-drip-irrigation-intelligence/research/supporting/establishment-lifecycle.md