Plant-Specific Drip Irrigation Intelligence

Status: Research complete | ClickUp: 868hp3w89

Overview

Intelligent drip irrigation system that uses plant-specific water requirements (WUCOLS plant factors, ET adjustment, establishment lifecycle) to automatically size emitters and calculate per-plant watering schedules.

Strategic Fit

Extends the existing irrigation capability from sprinkler-only to drip systems, addressing the growing demand for water-efficient precision irrigation in residential and commercial landscapes.

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

Plant-Specific Drip Irrigation Intelligence (v2)

ID: SS-RR-2026-001 | Date: 2026-03-01 | Status: draft ClickUp: Plant-Specific Drip Irrigation Intelligence Plan: SS-RP-2026-001 Prior version: v1 (2026-02-28) — superseded, content merged into this report Domain: Irrigation Management / Precision Watering

TL;DR

Plant-specific drip irrigation intelligence — a system that automatically selects emitters and generates per-plant watering schedules based on species data, weather, and soil — is a genuine whitespace opportunity. No product, patent, or academic publication combines WUCOLS species-level plant factors with real-time ET adjustment, emitter product databases, and establishment lifecycle management. All 10 vertical competitors operate at the zone level; none reach individual plants. The science is published (WUCOLS V covers 4,100+ taxa, MWELO provides the regulatory math, Gilman/Costello provide establishment models), the data sources are free and accessible (Open-Meteo ET₀, SSURGO soils, WUCOLS GitHub export), and SimplyScapes already has the structural advantages to build it — a 2,500+ species plant library, an irrigation design engine with manufacturer catalogs, and the exact customer base that needs this. Patent risk is favorable: the one patent requiring counsel review (US10028454B2, Husqvarna/ET Water) targets hardware-integrated systems, not software-only recommendation engines. Five differentiation opportunities identified, all in patent-free zones. MVP (design-time emitter auto-placement + water budget) is achievable in 2–3 months.

---

Part I: The Idea

1. What We're Exploring

Most people — homeowners and many landscape professionals — have no idea how much water their individual plants actually need. They set a sprinkler timer, guess at minutes, and hope for the best. Overwatering wastes water and money. Underwatering kills plants. Both are endemic.

The core idea is a system that does two things:

At design time: When a user places non-turf plants in a SimplyScapes irrigation design, the system automatically selects and places the right type, size, and quantity of drip emitters next to each plant — based on the species' water requirements, the plant's size at planting, the soil type, and the user's preferred manufacturer.

Ongoing management: After installation, the system generates a week-by-week watering schedule that evolves over years. It accounts for the plant's establishment phase (frequent watering early on, tapering as roots develop), adjusts for weather using local ET data, and recommends hardware changes as plants grow (adding emitters, repositioning them toward the dripline, or transitioning from point-source drip to bubblers for large trees).

This transforms SimplyScapes from a tool that helps you design irrigation into a tool that helps you manage it — for the life of the landscape.

Platform context: SimplyScapes already has the critical building blocks. The plant table has ~100+ columns including water (requirement classification), zone_min/zone_max (USDA zones), sun, soil, height, width, and growth_rate. The irrigation engine (src/lib/irrigation/) already handles sprinkler head placement with manufacturer catalogs (Hunter, Rain Bird) and water allowance budgeting (PR #148, merged Feb 2026). What's missing: WUCOLS plant factor data, ET adjustment factors, establishment period data, and drip emitter associations in the schema.

2. Why It Matters

Water conservation is a regulatory and market force. Western US drought regulations (MWELO in California, Utah statewide programs) are driving demand for tools that quantify landscape water use. Water districts — already SimplyScapes customers — need residents to use water efficiently. A system that calculates per-plant water budgets and tracks actual use against MWELO allowances directly serves this institutional demand.

The gap between science and practice is enormous. WUCOLS tells you a Ceanothus is "Low" water use and a Hydrangea is "High." The MWELO formula can calculate exactly how many gallons each needs. University extension services have published establishment tapering schedules. But none of this reaches the average user. It's buried in PDFs and academic spreadsheets.

Smart controllers don't solve this. Rachio, Hunter Hydrawise, and Rain Bird smart controllers adjust watering for weather — but only at the zone level. If a low-water Ceanothus and a high-water Hydrangea share a zone, the controller can't differentiate. The species-level intelligence doesn't exist in any product today.

SimplyScapes has a structural advantage. The platform already knows what plants are in the design (2,500+ species library with genus/species taxonomy), already has an irrigation design tool with manufacturer catalogs, and already serves the exact audience that needs this.

Lifecycle management is completely unaddressed. Every existing system treats irrigation as static. But plants change dramatically over their first 1-3 years. No product manages the establishment-to-mature transition.

---

Part II: Research Findings

Topic 1: Plant Data Pipeline — WUCOLS Mapping & Coverage Gaps

1.1 WUCOLS V Data Structure and Coverage

Source: WUCOLS V — UC Davis | Plant Search Database | GitHub Repository | DWR Collaboration Announcement

Species coverage:

• WUCOLS IV: 3,546 taxa evaluated
• WUCOLS V: 4,100+ taxa (live as of March 25, 2025)
• The V update added approximately 1,200 new taxa reviewed by volunteers from horticulture, academia, government agencies, and NGOs
• UC Davis states that the great majority of taxa available from wholesale nurseries in California are now included

Data structure -- columns per plant record:

| Column | Description | |--------|-------------| | Plant Type | Abbreviation codes: T (Tree), S (Shrub), V (Vine), Gc (Groundcover), P (Perennial), G (Grass), Su (Succulent), Pm (Palm/Cycad), B (Bamboo), Bu (Bulb), N (unknown/other) | | Botanical Name | Scientific genus and species | | Common Name | English common name | | Water Use (Region 1) | Rating for North-Central Coast | | Water Use (Region 2) | Rating for Central Valley | | Water Use (Region 3) | Rating for South Coast | | Water Use (Region 4) | Rating for South Inland | | Water Use (Region 5) | Rating for High Desert | | Water Use (Region 6) | Rating for Low Desert |

Six California climate regions:

1. North-Central Coast (Region 1)
2. Central Valley (Region 2)
3. South Coast (Region 3)
4. South Inland (Region 4)
5. High Desert (Region 5)
6. Low Desert (Region 6)

A single species may have different water use ratings in different regions (e.g., a plant rated "Low" on the coast may be rated "Moderate" inland where it is hotter).

Water use classification scheme -- four categories with numerical Plant Factor (PF) ranges:

| WUCOLS Category | Plant Factor Range | Interpretation | |-----------------|-------------------|----------------| | Very Low (VL) | < 0.1 | Needs < 10% of turf water | | Low (L) | 0.1 - 0.3 | Needs 10-30% of turf water | | Moderate (M) | 0.4 - 0.6 | Needs 40-60% of turf water | | High (H) | 0.7 - 1.0 | Needs 70-100% of turf water |

Source: Water News Network -- Plant Factors | WUCOLS 2000 PDF

MWELO convention for midpoint values: If you know the category but not a precise PF, use the midpoint: VL = 0.1, L = 0.2, M = 0.5, H = 0.8. Source: Lodi MWELO calculation example

Data availability and export:

• Freely accessible online at wucols.ucdavis.edu/plant-search-database
• Exportable to .xlsx (Excel) via "Export to Excel" button on the results page
• Can be converted to .csv for programmatic use
• Source code available on GitHub (React/TypeScript frontend)
• No documented REST API for direct programmatic access -- web scraping or xlsx export + parse is the integration path
• Multiple third-party tools have already ingested the data (WaterWonk, Alluvial Soil Lab, Land F/X)

Key limitation for SimplyScapes: WUCOLS is California-specific. The six climate regions cover California only. For SimplyScapes users in Arizona, Texas, Utah, Florida, or other states, the WUCOLS water use ratings may not directly apply -- though the species coverage itself (botanical names) is relevant nationally.

---

1.2 Beyond WUCOLS -- Other Plant Water Databases

ANSI/ASABE S623.1 -- SLIDE Rules

Source: USU CWEL -- SLIDE Rules | UC ANR -- Using SLIDE | ASABE Standard

SLIDE (Simplified Landscape Irrigation Demand Estimation) is an ANSI standard (S623.1, originally Jan 2017, reaffirmed 2022) developed by Roger Kjelgren at Utah State University. Unlike WUCOLS, SLIDE assigns plant factors by plant type category, not by individual species.

SLIDE Plant Factor table:

| Plant Type Category | Plant Factor | |---------------------|-------------| | Cool-season turfgrass (tall fescue, bluegrass, rye, bent) | 0.8 | | Warm-season turfgrass (bermuda, zoysia, St. Augustine, buffalo) | 0.6 | | Annual flowers and bedding plants | 0.8 | | Woody plants & herbaceous perennials (humid climates) | 0.7 | | Woody plants & herbaceous perennials (arid climates) | 0.5 | | Desert-adapted plants | 0.3 | | Deciduous fruit crops | 0.8 | | Evergreen fruit crops | 1.0 | | Vegetable crops | 1.0 |

Core formula: Landscape Water Demand (gallons) = ETo x Plant Factor x Landscape Area x 0.623

Four SLIDE Rules:

1. Oasis ETo -- Reference ET from large turf areas is prescriptive for turf but not for diverse plantings
2. Plant Factor -- PFs alone adjust ETo; they are assigned by type category, not species
3. Plant Density -- Dense cover (>=80%) acts as a single "big leaf" governed by the highest-PF species; sparse cover (<80%) depends on individual plant leaf area
4. Hydrozones -- Water demand of a mixed-species zone is governed by the plant type with the highest PF

SLIDE vs. WUCOLS -- key differences:

| Dimension | WUCOLS | SLIDE | |-----------|--------|-------| | Granularity | Per-species (4,100+ taxa) | Per-plant-type (6-9 categories) | | Geographic scope | California (6 regions) | National (climate-adjusted) | | Precision | Categorical ranges (VL/L/M/H) | Single value per type | | Scientific basis | Expert consensus (horticultural practitioners) | Research-based (peer-reviewed) | | Density/microclimate | Handled by separate Kd, Kmc factors | Built into rules (Rule #3, #4) |

Relevance for SimplyScapes: SLIDE is the appropriate fallback for plants not in WUCOLS. If a species has no WUCOLS entry, assign the SLIDE PF based on its plant type (tree/shrub/groundcover/etc.) and climate zone (arid vs. humid). SLIDE is also the basis for MWELO water budget calculations nationally.

PlantFile (Australia)

Source: PlantFile | CAD International -- PlantFile

PlantFile is an Australian landscape plant database containing:

• 3,586 species and 5,271 cultivars (8,857 total entries)
• 42 categories of information per plant including water usage
• Searchable by growth type, water usage, mature height, aspect, and more
• Used throughout Australian TAFE colleges and professional landscape design

PlantFile includes water use ratings per species but uses an Australian climate framework, not WUCOLS categories. Data is proprietary (licensed software, not open data).

Relevance for SimplyScapes: PlantFile could serve as a supplementary data source for species not in WUCOLS, particularly for Australian/South Pacific species. However, the water use ratings would need calibration to US climate zones.

AusTraits (Australia -- Open Data)

Source: AusTraits | Nature -- AusTraits publication

AusTraits is an open-source, curated plant trait database for the Australian flora:

• 448 traits across 28,640+ taxa
• Includes physiological water-related traits (water-use efficiency, gas exchange)
• Includes morphological traits that correlate with water use (leaf area, height)
• Supported by the Australian Research Data Commons (ARDC)
• Freely downloadable

Relevance for SimplyScapes: AusTraits contains species-level physiological water-use data that could help refine PF estimates for species shared between Australian and US landscapes (many ornamental genera overlap -- Eucalyptus, Acacia, Callistemon, Grevillea, etc.). The trait-based approach could also inform a genus-level inference model.

South Africa -- Hydrozone Plant Database

Source: Horticulture Research paper | UNISA thesis -- ALWUMSA model

South Africa developed a landscape plant database linked to hydrozones and plant factors, created through collaboration between the South African Green Industries Council, South African Nursery Association, South African Landscapers Institute, Turf Grass Managers Association, and Rand Water's Water Wise team.

Key characteristics:

• Plants classified into four hydrozones (high, medium, low, very low water requirements)
• Each plant linked to a plant factor coefficient
• Methodology mirrors WUCOLS but for South African climate conditions
• Resulted in the ALWUMSA model (Amenity Landscape Water Use Model South Africa)

Relevance for SimplyScapes: The South African framework validates the WUCOLS approach internationally and provides plant factor data for African-origin species commonly used in US landscapes (Agapanthus, Strelitzia, Protea, etc.).

Israel -- Volcani Center Research

Source: Volcani Center -- Environmental Physics and Irrigation | Institute of Soil, Water and Environmental Sciences

Israel's Agricultural Research Organization (Volcani Center) conducts extensive irrigation research through the Institute of Soil, Water and Environmental Sciences, covering precision irrigation optimization, subsurface hydrology, remote sensing, and agrometeorology. However, Israeli research is primarily focused on agricultural crops rather than ornamental landscape species. No equivalent landscape plant water use database like WUCOLS was found in public Israeli sources.

Relevance for SimplyScapes: Limited direct applicability. Israeli drip irrigation technology (Netafim originated in Israel) and precision irrigation algorithms may inform the engineering approach, but their plant coefficient databases focus on agricultural crops, not landscape ornamentals.

Regional US Extension Resources

Source: USU CWEL -- Water-Wise Plants | USU -- Landscape Irrigation Calculator | TexasET Network

Utah State University (CWEL):

• Maintains water-wise plant lists organized by trees, shrubs, perennials, groundcovers, grasses
• Provides a Landscape Irrigation Calculator for Utah
• Developed the SLIDE methodology that became ANSI/ASABE S623
• Plant lists have qualitative water-use ratings but not species-level PF coefficients

Texas A&M AgriLife:

• Operates the TexasET Network (reference ET data across Texas)
• Crop coefficients developed for Texas High Plains agriculture
• Limited landscape-specific ornamental plant coefficient data

Colorado State University:

• Conducted a Shrub Water Use Study at the CSU arboretum measuring actual water use of four common shrub species (Cornus sericea, Hydrangea arborescens, Physocarpus opulifolius, Salix purpurea) at varying irrigation levels
• Found that some shrubs (Cornus, Physocarpus, Salix) appeared acceptable for landscape use even at 0% supplemental irrigation
• Hydrangea required >100% ETo for optimal performance

Key finding: No state outside California maintains a comprehensive WUCOLS-equivalent database with per-species water use classifications. Extension services provide qualitative guidance and plant lists, but not the structured, per-species PF data needed for per-plant irrigation calculations. WUCOLS remains the only comprehensive source for species-level data at scale.

---

1.3 Refining Plant Factor Ranges

WUCOLS assigns categorical ranges (e.g., "Moderate" = 0.4-0.6), which creates meaningful uncertainty in per-plant calculations. A plant at PF 0.4 uses 33% less water than one at PF 0.6. Several approaches exist for narrowing these ranges:

UC Landscape Plant Irrigation Trials (UCLPIT)

Source: UCLPIT | UC ANR UCLPIT | UCLPIT History

UC Davis runs a field trial program that evaluates landscape plants under deficit irrigation:

• Plants are established in Year 1 with regular irrigation (~8.3 gal/event weekly)
• In Year 2, deficit irrigation at three reduced levels (percentage of ETo) begins
• Data collected: growth measurements and quality ratings at each irrigation level
• Trials at Davis (USDA Zone 9b, full sun, silty clay-loam) and since 2017, at UC ANR South Coast REC in Irvine
• Results published as plant-specific irrigation recommendations
• Program has been running since 2004-2005 with ~10 species in the original trial

This is the most promising source for refining WUCOLS categories. UCLPIT generates actual performance data at specific irrigation percentages, which can pin a species to a narrower PF range than WUCOLS provides.

Lysimeter Studies -- Species-Level PF Measurements

Source: Magnolia and Viburnum PF study (MDPI Water 2021) | CSU Shrub Water Use Study

Targeted lysimeter research has produced species-specific PF values:

| Species | Measured PF | Season/Condition | Source | |---------|-------------|------------------|--------| | Magnolia grandiflora | 0.7 | Late spring vigorous growth | MDPI Water 2021 | | Magnolia grandiflora | 0.5-0.6 | Rest of year | MDPI Water 2021 | | Viburnum odoratissimum | 0.5-0.6 | Spring dry season (monsoonal climate) | MDPI Water 2021 |

These studies use weighing lysimeters for individual plants, calculating PF as the ratio of actual ET (normalized by projected crown area) to reference ET. The methodology is rigorous but has only been applied to a handful of species.

Key insight from the Magnolia study: PF values vary by season, not just by species. Magnolia shifts from 0.7 during active growth to 0.5-0.6 during dormant periods. This suggests that a single static PF per species is an oversimplification -- seasonal adjustment could improve accuracy.

Phylogenetic Trait Imputation

Source: Nature -- Phylogenetic signal in water-related traits (2023) | Nature Scientific Data -- Global tree hydraulic traits (2024)

Recent research demonstrates that plant water-use traits have strong phylogenetic signals -- closely related species share similar water-use characteristics. This enables trait imputation for unstudied species:

• Researchers have imputed hydraulic and structural traits for 55,779 tree species using random forest models trained on TRY plant trait database observations and phylogenetic eigenvector maps
• Traits imputed include water-use efficiency (WUE), xylem pressure, rooting depth
• The approach works because water-conducting and nutrient-use traits show phylogenetic niche conservatism with correlated evolution

Relevance for SimplyScapes: This validates a genus-level inference strategy. If Quercus agrifolia is rated "Low" in WUCOLS, and Quercus virginiana is not in WUCOLS, the genus-level average (or the phylogenetically nearest rated species) provides a scientifically defensible estimate.

The Landscape Coefficient Method (Costello et al. 2000)

Source: WUCOLS 2000 Guide (PDF) | MWELO calculation examples

The Landscape Coefficient Method (LCM) from Costello, Matheny, and Clark provides a framework for adjusting PF ranges by incorporating site-specific factors:

KL = Ks x Kd x Kmc

Where:

• Ks (species factor): 0.2 (low), 0.5 (moderate), 0.9 (high) -- matches WUCOLS midpoints
• Kd (density factor): 0.5-0.9 (sparse plantings), 1.0 (average), 1.1-1.3 (tiered/dense plantings)
• Kmc (microclimate factor): 0.5-0.9 (shaded/protected), 1.0 (average), 1.1-1.4 (exposed/paved surroundings)

ETL = KL x ETo

This means the effective PF for a specific installation is the product of species, density, and microclimate factors. A "Moderate" species (Ks = 0.5) in a shaded location (Kmc = 0.7) with sparse planting (Kd = 0.7) would have an effective KL = 0.5 x 0.7 x 0.7 = 0.245 -- effectively "Low" water use.

Implication for SimplyScapes: Rather than trying to pin every species to a single precise PF, SimplyScapes could use the WUCOLS midpoint as Ks and let users adjust Kd and Kmc based on their site conditions. The system already knows plant type (from the plant table) and could infer density from the design layout. Microclimate could be user-input or derived from sun/shade data in the design.

---

1.4 WUCOLS-to-SimplyScapes Mapping Feasibility

Coverage Estimation

SimplyScapes has approximately 2,500+ species in its plant library. WUCOLS V has 4,100+ taxa. At first glance this looks like WUCOLS should cover most of the SimplyScapes library, but the reality is more nuanced:

Favorable factors:

• WUCOLS was built from nursery grower catalogs -- it covers the commercially available landscape plant palette
• WUCOLS V specifically added ~1,200 taxa identified as missing from nursery submissions
• UC Davis states the great majority of wholesale nursery taxa in California are now included
• SimplyScapes' library was built from commercial nursery data, creating significant overlap

Unfavorable factors:

• SimplyScapes serves users nationally, not just California -- regional cultivars (e.g., Southeastern native plants, Midwest prairie species) may not be in WUCOLS
• WUCOLS focuses on California landscape plants -- species primarily used in the Northeast, Southeast, or Pacific Northwest may be absent
• Cultivar coverage is inconsistent -- WUCOLS may list a genus or species but not specific cultivars (e.g., Ceanothus spp. is listed, but individual cultivar water needs may differ)
• Some species have WUCOLS entries for some regions but not others (listed as "--" in regions where they are not commonly grown)

Estimated coverage: Without running an actual match, a reasonable estimate based on the data structure is:

• 60-75% of SimplyScapes species will have a direct WUCOLS match (same botanical name)
• An additional 10-15% can be matched at the genus level (species not listed, but genus has entries with a consistent water-use pattern)
• 10-25% will have no WUCOLS match and will need a fallback strategy

Gap-Filling Strategy (Tiered Approach)

Based on the research, the following tiered strategy handles unmapped species:

Tier 1: Direct WUCOLS match (estimated 60-75% of library)

• Match by exact botanical name (genus + species)
• Use region-appropriate water use rating
• Convert to PF using MWELO midpoint convention

Tier 2: Genus-level inference (estimated 10-15% of library)

• If species not found, check if other species in the same genus have WUCOLS entries
• If genus entries are consistent (all "Low"), assign that rating
• If genus entries vary, use the most conservative (highest water use) rating
• Scientific basis: phylogenetic signal in water-use traits is strong (see Section 1.3)
• WUCOLS itself supports this approach -- it lists some entries by genus only (e.g., "Ceanothus spp.") explicitly indicating all species/cultivars in that genus share the rating

Tier 3: SLIDE plant type fallback (estimated 10-20% of library)

• For species with no WUCOLS genus-level data, fall back to the SLIDE PF for their plant type
• Trees/shrubs in arid climates: PF = 0.5
• Trees/shrubs in humid climates: PF = 0.7
• Desert plants: PF = 0.3
• SimplyScapes already has plant type data in its schema (tree, shrub, groundcover, etc.)

Tier 4: User override / manual assignment (last resort)

• Allow users to manually set or adjust water use category for any plant
• Display a flag indicating "estimated -- no WUCOLS data" so users can calibrate

How Other Tools Handle This

Land F/X (landscape CAD software):

• Includes WUCOLS water use data across all location categories in their plant database
• Users can manually update plant data to reflect WUCOLS values for their chosen region
• Database manager cross-checks user edits using additional resources
• Source: Land F/X Data Vetting

Netro Smart Sprinkler:

• Maintains an internal database of 1,000+ common plant species with species-specific watering characteristics
• Uses a multi-factor algorithm combining plant type, soil properties, weather, and temperature
• For unknown plants, users can assign plant type categories (lawn, garden, shrub, tree)
• Source: Netro Smart Sprinkler

Rachio Smart Controller:

• Configures watering by vegetation type at the zone level, not species level
• Categories: Cool Season Grass, Warm Season Grass, Trees, Shrubs, Perennials, Annuals, Ground Cover, Xeriscape, Desert
• No species-level database -- purely type-based PF assignment
• Source: Rachio Vegetation Types

WaterWonk:

• Mobile-optimized WUCOLS lookup tool
• Provides region-specific water use ratings directly from WUCOLS data
• No gap-filling strategy for missing species
• Source: WaterWonk

---

1.5 Key Findings and Recommendations for SimplyScapes

Finding 1: WUCOLS V is the definitive foundation. At 4,100+ taxa with per-region water use classifications, freely downloadable as Excel, WUCOLS is the only comprehensive species-level landscape plant water use database in the world. No other country has an equivalent at this scale.

Finding 2: SLIDE provides the national fallback. Where WUCOLS does not cover a species (or when operating outside California), SLIDE's plant-type-based PF values provide a scientifically defensible default. SLIDE was developed explicitly as a simplified national alternative.

Finding 3: The gap is manageable. The tiered approach (WUCOLS direct match -> genus inference -> SLIDE type fallback -> user override) should cover 100% of SimplyScapes' plant library with varying levels of precision. The critical next step is running an actual match analysis between the SimplyScapes plant table and WUCOLS V data.

Finding 4: WUCOLS gives ranges, not point values. "Moderate" spans 0.4-0.6, a 50% variation. For MVP, using MWELO midpoints (VL=0.1, L=0.2, M=0.5, H=0.8) is standard practice and defensible. Refinement via UCLPIT data, lysimeter studies, or seasonal adjustment is a future enhancement.

Finding 5: International databases are supplementary, not primary. PlantFile (Australia, 8,857 entries), AusTraits (28,640 taxa with water traits), and the South African hydrozone database provide useful cross-referencing for specific genera but are not structured as drop-in WUCOLS supplements.

Finding 6: The Landscape Coefficient Method handles site variation. The Costello formula (KL = Ks x Kd x Kmc) lets SimplyScapes adjust WUCOLS-based species factors for plant density and microclimate, which the design tool could calculate automatically from the layout.

Finding 7: Phylogenetic inference is scientifically valid. Recent research confirms strong phylogenetic signals in plant water-use traits, supporting genus-level fallback as a defensible methodology (not just a heuristic).

---

Topic 1 Sources

| # | Type | Reference | URL | |---|------|-----------|-----| | 1 | Database | WUCOLS V -- Plant Search Database (UC Davis) | https://wucols.ucdavis.edu/plant-search-database | | 2 | Repository | WUCOLS Plant Search Database -- GitHub | https://github.com/ucdavis/WUCOLS-plant-search-database | | 3 | Government | DWR + UC Davis WUCOLS Collaboration Announcement | https://water.ca.gov/News/Blog/2023/Sep-23/DWR-Collaborates-With-UC-Davis-to-Expand-Plant-Database-for-Landscape-Community | | 4 | Standard | ANSI/ASABE S623.1 -- SLIDE Rules | https://webstore.ansi.org/standards/asabe/ansiasabes623jan2017r2022 | | 5 | Extension | USU CWEL -- SLIDE Rules | https://extension.usu.edu/cwel/slide-rules | | 6 | Extension | UC ANR -- Using ANSI/ASABE S623 & SLIDE | https://ucanr.edu/site/center-landscape-urban-horticulture/using-ansi/asabe-s623-slide-estimate-landscape-water | | 7 | Reference | WUCOLS 2000 -- Landscape Coefficient Method (PDF) | https://cimis.water.ca.gov/Content/PDF/wucols00.pdf | | 8 | Article | Water News Network -- Plant Factor Values | https://www.waternewsnetwork.com/knowing-your-plants-water-needs-plant-factors/ | | 9 | Software | PlantFile -- Australian Plant Database | https://plantfile.com.au/products | | 10 | Database | AusTraits -- Australian Plant Trait Database | https://austraits.org/ | | 11 | Paper | AusTraits publication (Nature Scientific Data, 2021) | https://www.nature.com/articles/s41597-021-01006-6 | | 12 | Paper | South Africa Hydrozone Plant Database (Horticulture Research) | https://horticultureresearch.net/jah/2021_23_1_28_36.pdf | | 13 | Thesis | ALWUMSA -- Amenity Landscape Water Use Model South Africa | https://uir.unisa.ac.za/handle/10500/25607 | | 14 | Research | Volcani Center -- Environmental Physics and Irrigation | https://www.agri.gov.il/en/research-center/department/environmental-physics-and-irrigation | | 15 | Research | UCLPIT -- UC Landscape Plant Irrigation Trials | https://uclpit.ucdavis.edu/ | | 16 | Paper | Magnolia and Viburnum Plant Factors (MDPI Water, 2021) | https://www.mdpi.com/2073-4441/13/13/1744 | | 17 | Paper | Phylogenetic signal in plant water-related traits (New Phytologist, 2023) | https://nph.onlinelibrary.wiley.com/doi/10.1111/nph.18565 | | 18 | Paper | Global tree hydraulic traits -- phylogenetic imputation (Nature Scientific Data, 2024) | https://www.nature.com/articles/s41597-024-04254-4 | | 19 | Paper | Nouri et al. -- Water requirements of urban landscape plants (Ecological Engineering, 2013) | https://www.sciencedirect.com/science/article/abs/pii/S0925857413001432 | | 20 | Paper | WUCOLS method applied in Iran (Ecological Informatics, 2023) | https://www.sciencedirect.com/science/article/abs/pii/S1574954123004193 | | 21 | Extension | USU CWEL -- Water-Wise Plants for Utah | https://extension.usu.edu/cwel/water-wise-plants | | 22 | Extension | USU CWEL -- Landscape Irrigation Calculator | https://extension.usu.edu/cwel/landscape-irrigation-calculator | | 23 | Research | CSU -- Shrub Water Use Study | https://agsci.colostate.edu/landscapeplants/arboretum/shrub-water-use-study/ | | 24 | Extension | UC ANR -- Plant Factor vs. Crop Coefficient | https://ucanr.edu/site/center-landscape-urban-horticulture/plant-factor-or-crop-coefficient-whats-difference | | 25 | Product | Rachio -- Vegetation Type Configuration | https://support.rachio.com/en_us/what-type-of-vegetation-do-i-have-By_5DIyYv | | 26 | Product | Netro Smart Sprinkler -- Plant Database | https://www.netrohome.com/en/shop/products/sprite | | 27 | Product | Land F/X -- Plant Data Vetting Resources | https://www.landfx.com/docs/planting/planting-getting-started/6213-data-vetting-resources.html | | 28 | Tool | WaterWonk -- Mobile WUCOLS Lookup | https://waterwonk.us/ | | 29 | Regulation | MWELO -- Inyo County Prescriptive Application | https://www.inyocounty.us/sites/default/files/2024-11/MWELO%20Prescriptive%20Application%20(Appendix%20D)%20with%20Ordinance.pdf | | 30 | Paper | Water Demand Determination Using WUCOLS and LIMP (MDPI Water, 2025) | https://www.mdpi.com/2073-4441/17/10/1429 |

---

Topic 6: Soil-Plant-Water Interaction Modeling

6.1 SSURGO / Web Soil Survey — Programmatic Soil Data Access

What SSURGO provides:

The Soil Survey Geographic Database (SSURGO) is the most detailed soil survey product from USDA-NRCS, containing information collected by the National Cooperative Soil Survey over more than a century. It covers most of the United States and provides the soil data needed to inform emitter selection and irrigation runtime calculations.

Key soil properties available from SSURGO for irrigation:

| Property | Table.Column | Units | Relevance to Irrigation | |----------|-------------|-------|------------------------| | Soil texture class | chorizon.texcl | Class name (e.g., "sandy loam") | Emitter flow rate selection, runtime calculation | | Sand % | chorizon.sandtotal_r | Percent | Infiltration estimation | | Silt % | chorizon.silttotal_r | Percent | Infiltration estimation | | Clay % | chorizon.claytotal_r | Percent | Infiltration estimation | | Available water capacity | chorizon.awc_r | in/in (inches water per inch soil) | Water storage, irrigation frequency | | Saturated hydraulic conductivity (Ksat) | chorizon.ksat_r | micrometers/sec | Maximum infiltration rate | | Hydrologic soil group | component.hydgrp | A, B, C, D | Drainage classification | | Drainage class | component.drainagecl | Class name | Overall drainage behavior |

AWC (available water capacity) values are pre-adjusted for coarse fragments in the SSURGO database. The _r suffix denotes "representative" (typical) values; _l and _h variants provide low and high estimates.

Spatial resolution:

• Vector polygons: SSURGO's native format is map unit polygons digitized at scales ranging from 1:12,000 to 1:63,360. At the most common scale (1:12,000), the minimum delineation is approximately 1-3 acres, though this varies by survey area.
• Gridded (gSSURGO): State-level databases are available at 10-meter resolution; the CONUS (continental US) database at 30-meter resolution. This is sufficient for residential property-level lookups.
• Coverage: Available for most areas in the United States. Some tribal lands and recent urban development areas may have gaps.

API access — Soil Data Access (SDA):

The primary programmatic interface is the Soil Data Access (SDA) web service:

• REST endpoint: https://SDMDataAccess.sc.egov.usda.gov/Tabular/post.rest
• Method: POST only (cannot be invoked via browser GET)
• Response formats: XML, JSON, JSON+COLUMNNAME, JSON+COLUMNNAME+METADATA
• Query language: T-SQL against the Soil Data Mart database
• Coordinate system: WGS84 (standard GPS coordinates)
• Limits: 100,000 records and 32MB JSON serialization per query

Point-location query — how to look up soil by GPS coordinates:

The key function is SDA_Get_Mukey_from_intersection_with_WktWgs84(), which accepts WKT (Well-Known Text) geometry in WGS84 coordinates and returns the map unit key (mukey) for that location.

Example SQL for point lookup:

SELECT mukey, muname
FROM mapunit
WHERE mukey IN (
  SELECT * FROM SDA_Get_Mukey_from_intersection_with_WktWgs84(
    'point(-121.77100 37.368402)'
  )
)

Once you have the mukey, you can join to component and chorizon tables to get soil properties:

SELECT
  m.mukey, m.muname,
  c.compname, c.comppct_r, c.hydgrp, c.drainagecl,
  ch.hzname, ch.hzdept_r, ch.hzdepb_r,
  ch.sandtotal_r, ch.silttotal_r, ch.claytotal_r,
  ch.awc_r, ch.ksat_r, ch.texcl
FROM mapunit m
  JOIN component c ON c.mukey = m.mukey
  JOIN chorizon ch ON ch.cokey = c.cokey
WHERE m.mukey IN (
  SELECT * FROM SDA_Get_Mukey_from_intersection_with_WktWgs84(
    'point(-121.77100 37.368402)'
  )
)
AND c.comppct_r >= 20
AND ch.hzdept_r = 0
ORDER BY c.comppct_r DESC

This query: (1) finds the map unit at a lat/lon, (2) gets dominant components (>=20% of map unit), (3) retrieves the surface horizon (top layer) soil properties.

SoilWeb API — simpler alternative:

UC Davis California Soil Resource Lab operates SoilWeb, which provides a simpler (though unofficial) REST endpoint:

https://casoilresource.lawr.ucdavis.edu/soil_web/reflector_api/soils.php
  ?what=mapunit&lon=-122&lat=37

This returns JSON with the mukey for a point location. From there you still need SDA for detailed soil properties. SoilWeb is not an official USDA service and may have availability limitations, but it's a convenient shortcut for mukey lookups.

SoilGrids — global alternative:

For locations outside the US (or as a supplementary data source), the ISRIC SoilGrids 2.0 API provides modeled soil properties globally at 250m resolution:

https://rest.isric.org/soilgrids/v2.0/properties/query
  ?lon=-122&lat=37
  &property=clay&property=sand
  &depth=0-5cm&value=mean

Returns JSON with predicted soil properties. Lower accuracy than SSURGO for US locations but provides coverage where SSURGO has gaps.

JavaScript / Node.js access:

No npm packages exist specifically for SSURGO/SDA access. The recommended approach is direct HTTP POST using fetch():

async function getSoilByCoordinates(lat, lon) {
  const sql = `
    SELECT m.mukey, m.muname, c.compname, c.comppct_r,
           c.hydgrp, ch.texcl, ch.sandtotal_r,
           ch.silttotal_r, ch.claytotal_r,
           ch.awc_r, ch.ksat_r
    FROM mapunit m
    JOIN component c ON c.mukey = m.mukey
    JOIN chorizon ch ON ch.cokey = c.cokey
    WHERE m.mukey IN (
      SELECT * FROM SDA_Get_Mukey_from_intersection_with_WktWgs84(
        'point(${lon} ${lat})'
      )
    )
    AND c.comppct_r >= 20 AND ch.hzdept_r = 0
    ORDER BY c.comppct_r DESC
  `;

  const response = await fetch(
    'https://SDMDataAccess.sc.egov.usda.gov/Tabular/post.rest',
    {
      method: 'POST',
      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
      body: `query=${encodeURIComponent(sql)}&format=JSON+COLUMNNAME`
    }
  );
  return response.json();
}

Recommendation for SimplyScapes: Implement a soil lookup service that calls SDA on project creation, caches the result per project location, and exposes soil type as a project-level setting (with manual override). The 10-30m resolution is more than adequate for residential properties. Cache results aggressively -- soil data is static; it never changes for a given location.

6.2 Soil Type Effects on Emitter Selection & Runtime

Soil type directly affects two irrigation design decisions: what emitter flow rate to use and how long to run the system.

Infiltration rates by soil texture:

| Soil Texture | Infiltration Rate (in/hr) | Emitter Recommendation | Runtime Guidance | |-------------|--------------------------|----------------------|-----------------| | Coarse sand | 0.75 - 1.0+ | Higher flow (2-4 GPH); closer spacing | Short, frequent cycles; 2-3x per week | | Sandy loam | 0.5 - 0.75 | Medium flow (1-2 GPH) | Moderate frequency; 2x per week | | Loam | 0.3 - 0.5 | Medium flow (1-2 GPH) | 1-2x per week at ~0.5" per cycle | | Silt loam | 0.3 - 0.5 | Low-medium flow (0.5-1 GPH) | 1x per week at ~1.0" per cycle | | Clay loam | 0.10 - 0.15 | Low flow (0.5 GPH) | 1x per week; risk of ponding at higher rates | | Clay | 0.08 - 0.15 | Low flow (0.5 GPH) | 1x per week; slow application to prevent runoff |

Water holding capacity by soil type:

| Soil Type | Available Water Capacity (in/in) | Practical Implication | |-----------|--------------------------------|---------------------| | Coarse sand | 0.05 | Drains fast; water passes through root zone quickly; needs frequent short irrigations | | Sandy loam | 0.10 - 0.12 | Moderate retention; good for drip irrigation | | Loam | 0.15 - 0.18 | Ideal; holds water well without waterlogging | | Clay loam | 0.14 - 0.17 | Good retention but slow infiltration; ponding risk | | Clay | 0.15 - 0.17 | High retention but very slow infiltration; runoff risk |

Key design principle: Sandy soils need higher emitter flow rates with closer spacing (because water moves straight down, not laterally) but shorter runtimes (because it drains past the root zone quickly). Clay soils need lower flow rates (to avoid ponding/runoff) with wider spacing (because water spreads laterally) but can run longer per cycle.

MWELO irrigation efficiency by system type:

| System Type | MWELO IE | Notes | |------------|---------|-------| | Drip emitters | 0.81 | Point source and inline dripline | | Bubblers | 0.81 | Same efficiency class as drip | | Spray heads (fixed) | 0.75 | Pop-up spray, shrub heads | | Rotors | 0.75 | Gear-driven rotors, impact sprinklers |

These efficiency values are used in the ETAF calculation: ETAF = Plant Factor / Irrigation Efficiency. For drip, with IE = 0.81, a moderate-water plant (PF = 0.5) yields ETAF = 0.5 / 0.81 = 0.617.

6.3 MWELO Density Factor (Kd) — Comprehensive Reference

The density factor accounts for the water demand differences caused by planting density and canopy layering. Denser plantings with multiple canopy tiers (groundcover + shrubs + trees) lose more water to transpiration than sparse, single-tier plantings.

Kd lookup table by vegetation type:

| Vegetation Type | Low Kd | Average Kd | High Kd | |----------------|--------|------------|---------| | Trees (single-tier) | 0.50 | 1.00 | 1.30 | | Shrubs (single-tier) | 0.50 | 1.00 | 1.10 | | Groundcover (single-tier) | 0.50 | 1.00 | 1.10 | | Mixed / tiered planting | 0.60 | 1.10 | 1.30 | | Turfgrass | 0.60 | 1.00 | 1.00 |

Source: Costello, Matheny, Clark & Jones (2000), "A Guide to Estimating Irrigation Water Needs of Landscape Plantings in California" and subsequent MWELO guidance documents.

When to apply each level:

• Low (0.5-0.6): Sparse, widely spaced plantings. Individual plants with significant bare soil or mulch between them. Immature plantings before canopy closure. New landscape installations in the first 1-2 years before fill-in. Solo specimens.
• Average (1.0): Typical landscape density. Groundcover that fully covers the soil. Shrubs at standard nursery spacing that will fill in within 2-3 years. Single canopy layer at full maturity. This is the default and should be used when density is unknown.
• High (1.1-1.3): Multi-tiered plantings with overlapping canopies. Trees over shrubs over groundcover in the same bed. Dense mass plantings. Mature layered landscapes. The maximum 1.3 applies specifically to dense tree canopy over other vegetation layers.

How Kd affects calculations in practice:

The density factor is a multiplier in the landscape coefficient formula. For a planting with Ks=0.5 (moderate water plant), Kmc=1.0 (average microclimate):

• Low density (Kd=0.5): KL = 0.5 x 0.5 x 1.0 = 0.25
• Average density (Kd=1.0): KL = 0.5 x 1.0 x 1.0 = 0.50
• High density, tiered (Kd=1.3): KL = 0.5 x 1.3 x 1.0 = 0.65

This represents a 2.6x range from lowest to highest density. The impact is substantial but the extreme ends are uncommon in typical residential landscapes.

Recommendation for SimplyScapes:

For per-plant calculations (not bed-level), the density factor needs special treatment. When calculating water for an individual plant, Kd should reflect the plant's planting context:

| SimplyScapes Scenario | Recommended Default Kd | |----------------------|----------------------| | Individual plant in mulched bed, no neighboring plants within 2x canopy width | 0.6 (low) | | Plant in a group/mass planting of same type, single canopy layer | 1.0 (average) | | Plant in a mixed bed with other plants, but single canopy tier | 1.0 (average) | | Plant in a layered bed (e.g., tree over shrubs over groundcover) | 1.2 (high) | | Dense screen or hedge planting | 1.1 (high) |

The system could potentially infer Kd from the design itself -- if a plant is placed near other plants of different heights, it's a tiered planting (Kd=1.2). If isolated, it's low density (Kd=0.6). For MVP, a project-level default of 1.0 with per-hydrozone override is simplest.

6.4 MWELO Microclimate Factor (Kmc) — Comprehensive Reference

The microclimate factor adjusts for site-specific conditions (sun exposure, wind, reflected heat from hardscapes) that cause a planting to use more or less water than it would under reference ET conditions.

Kmc lookup table by vegetation type:

| Vegetation Type | Low Kmc | Average Kmc | High Kmc | |----------------|---------|-------------|----------| | Trees | 0.50 | 1.00 | 1.40 | | Shrubs | 0.50 | 1.00 | 1.30 | | Groundcover | 0.50 | 1.00 | 1.20 | | Mixed | 0.50 | 1.00 | 1.40 | | Turfgrass | 0.80 | 1.00 | 1.20 |

Source: Costello et al. (2000) and MWELO guidance.

When to apply each level:

• Low (0.5-0.8): Protected from wind. North-facing exposure or shaded by buildings/structures for most of the day. Enclosed courtyards with minimal air movement. Under mature tree canopy (understory plants). Research shows shaded lawns mostly stay within recommended irrigation ranges without adjustment.
• Average (1.0): Equivalent to reference ET conditions -- open, moderately exposed. Partial sun (4-6 hours direct sun). Moderate wind. Standard suburban landscape. This is the default for unspecified conditions.
• High (1.2-1.4): Full sun exposure (8+ hours). South or west-facing exposure adjacent to reflective surfaces. Near large paved areas, concrete, or buildings that radiate heat. Regular or significant wind exposure. Medians and parking lot islands. Rooftop or elevated planters. Research found that unshaded lawns used 40% more water than recommended, demonstrating the significant real-world impact of full sun exposure.

Quantified microclimate impact:

Published research provides context on how much microclimate matters in practice:

• Unshaded lawns vs. shaded lawns: 40% higher water consumption in unshaded conditions (peer-reviewed field study)
• The microclimate factor is considered the most uncertain factor in determining urban landscape ET. It is harder to assign objectively than the species factor or density factor because it depends on multiple interacting variables (sun angle, wind exposure, proximity to heat-absorbing surfaces, building shadows)
• In high-microclimate conditions (hot, exposed, windy), actual water demand can significantly exceed what the species factor alone would predict

Recommendation for SimplyScapes:

| SimplyScapes Scenario | Recommended Default Kmc | |----------------------|------------------------| | Shaded bed (north side of building, under large tree canopy) | 0.8 | | Standard residential bed (mixed sun, some afternoon shade) | 1.0 | | Full sun bed (south or west exposure, no shade) | 1.1 | | Planting adjacent to hardscape (driveway, patio, parking) | 1.2 | | Parking lot island, median strip, or exposed rooftop | 1.3-1.4 |

For MVP, default to 1.0 and offer a simple dropdown per hydrozone: "Shaded / Normal / Full Sun / Near Hardscape". Advanced users or professionals can input a specific value. The system could potentially auto-suggest based on property orientation and proximity to structures if that data is captured in the design.

6.5 Mulch Effects on Landscape Water Demand

Mulch significantly reduces irrigation water demand by suppressing soil surface evaporation, moderating soil temperature, and improving water infiltration.

Quantified water savings from mulch:

| Study/Source | Finding | Mulch Type | Depth | |-------------|---------|-----------|-------| | University of Florida (Gilman lab) | 33% reduction in soil water loss to evaporation | Pine bark | Not specified in study | | Frontiers in Agronomy (2024 meta-review) | 28-58.8% reduction in evaporation; up to 22% enhancement in moisture retention | Various organic and inorganic | Variable | | Irrigation Science (2024 review) | Early season: 40% reduction; mid-season: 35%; late season: 33% | Various mulch types | Variable | | University of Nebraska Extension | 8-13 deg F reduction in summer soil temperature | Coarse organic (wood chips, shredded wood) | 3-4 inches | | Agricultural field studies | 14-29% reduction in irrigation water for pepper; up to 70% for onion | Various | Variable |

Recommended mulch depths:

• Organic mulch (wood chips, shredded bark): 3-4 inches. Most effective for moisture conservation. Coarse-textured organic mulch on bare soil works best.
• Inorganic mulch (gravel, decomposed granite): 2-3 inches.
• Minimum effective depth: 2 inches. Below this, weed suppression and moisture retention drop significantly.
• Avoid: Fine-textured organic mulch (sawdust) and materials with waxy surfaces -- these can become hydrophobic (water-repellent). Avoid rubber mulch -- increases soil temperature, leaches chemicals, and poses fire risk.

Should the system account for mulch?

Yes, but conservatively. The research supports a meaningful reduction in water demand from proper mulching, but the exact percentage varies widely depending on mulch type, depth, climate, and maintenance.

Recommended approach for SimplyScapes:

| Mulch Status | Water Demand Adjustment | |-------------|----------------------| | No mulch (bare soil) | 1.0 (no adjustment -- baseline) | | Standard mulch (3-4" organic) | 0.80 - 0.85 (15-20% reduction) | | Heavy mulch (4"+ or inorganic) | 0.75 - 0.80 (20-25% reduction) |

These are conservative compared to the research findings (which show up to 33-58% reductions) because: (1) mulch degrades over time and may not be maintained at optimal depth, (2) the research often measures evaporation reduction specifically, while total plant water demand also includes transpiration which mulch does not reduce, and (3) the system should err toward slight overwatering rather than underwatering for plant health.

For MVP, a simple boolean "mulched (yes/no)" with a default 15% reduction for "yes" is the simplest implementation. A value of 0.85 as the mulch adjustment factor is a defensible conservative default.

Important note: MWELO does not currently include a mulch adjustment factor in the water budget formula. The 3-inch mulch requirement in MWELO (Section 492.13) is treated as a prescriptive requirement rather than a quantitative adjustment to the water allowance. Any mulch adjustment SimplyScapes applies would be an enhancement beyond MWELO for runtime scheduling purposes, not for compliance calculation.

6.6 Sensitivity Analysis: Which Factors Matter Most

Understanding which factors in the MWELO formula have the greatest impact on the final gallons-per-plant number determines where SimplyScapes should invest in precision versus where defaults are adequate.

The complete per-plant water calculation chain:

Gallons/year = ETo x Ks x Kd x Kmc x Plant_Area x 0.62 / IE

Where:

• ETo = Reference evapotranspiration (inches/year) -- location-dependent
• Ks = Species factor from WUCOLS (0.1 to 1.0)
• Kd = Density factor (0.5 to 1.3)
• Kmc = Microclimate factor (0.5 to 1.4)
• Plant_Area = Canopy area or allocated landscape area (sq ft)
• 0.62 = Conversion factor (inches to gallons per sq ft)
• IE = Irrigation efficiency (0.81 for drip)

Factor ranges and impact:

| Factor | Range | Ratio (max/min) | Impact Assessment | |--------|-------|-----------------|-------------------| | Ks (species factor) | 0.1 - 1.0 | 10.0x | Highest impact. A high-water Hydrangea (Ks=0.8) needs 8x the water of a very-low-water Ceanothus (Ks=0.1). This is the single most important factor and the one where SimplyScapes has the best data (WUCOLS mapping). | | Kmc (microclimate) | 0.5 - 1.4 | 2.8x | Second highest. A plant in full sun near hot pavement (1.4) needs nearly 3x the water of the same plant in deep shade (0.5). Also the most uncertain factor -- hardest to measure or assign objectively. | | Kd (density) | 0.5 - 1.3 | 2.6x | Third highest. Dense tiered planting (1.3) uses 2.6x vs. sparse planting (0.5). But the practical range is narrower -- most residential landscapes fall between 0.8 and 1.2 (a 1.5x range). | | IE (irrigation efficiency) | 0.75 - 0.81 | 1.08x | Low impact (for system type selection). Switching from spray to drip changes the denominator only ~8%. But IE determines how much water is wasted, which affects total consumption significantly. | | ETo (reference ET) | ~20 - 80 in/year (US range) | 4.0x | High impact but location-fixed. Cannot be controlled -- it's determined by where the project is located. Phoenix (80 in/yr) vs. Seattle (20 in/yr) creates a 4x difference. Already captured by the ET data source. | | Plant_Area | Variable | Variable | High impact, plant-specific. A mature shade tree with a 30-ft canopy (700 sq ft) needs orders of magnitude more water than a 2-ft shrub (3 sq ft). This is driven by plant species and maturity. |

Sensitivity ranking for SimplyScapes development priority:

1. Ks (species factor) -- GET THIS RIGHT. 10x range and the area where SimplyScapes has the most control and competitive advantage. Accurate WUCOLS mapping to the plant library is the single most impactful thing the system can do. Precision within the WUCOLS ranges (e.g., using 0.5 vs. 0.6 for "Moderate") has meaningful impact.

2. Plant area / canopy size -- GET THIS RIGHT. Directly multiplies the result. The system needs accurate canopy estimates at planting and at maturity. The existing width field in the plant table provides this.

3. Kmc (microclimate) -- OFFER SIMPLE CHOICES, DEFAULT CONSERVATIVELY. High impact but highly uncertain. A 3-level dropdown (Shaded/Normal/Exposed) covering Kmc = 0.8/1.0/1.2 captures the most practical range without false precision. Don't try to compute this automatically unless the system has access to property orientation and satellite imagery.

4. Kd (density) -- DEFAULT TO 1.0, ALLOW OVERRIDE. The practical range in residential landscapes is narrow (0.8-1.2). Defaulting to 1.0 and allowing per-hydrozone override is appropriate for MVP. The system could auto-detect tiered plantings from the design (multiple plant heights in the same bed) in a future version.

5. ETo -- ALREADY HANDLED. Location-based lookup from Open-Meteo or CIMIS. No user input needed.

6. IE -- ALREADY HANDLED. Fixed at 0.81 for drip systems. No user input needed for the drip-focused MVP.

Worked example -- sensitivity demonstration:

Scenario: A medium-water shrub (e.g., Pittosporum tobira) in Sacramento, CA.

Base case: ETo = 51.1 in/yr, Ks = 0.5, Kd = 1.0, Kmc = 1.0, canopy area = 16 sq ft (4' wide), IE = 0.81

Base gallons/year = 51.1 x 0.5 x 1.0 x 1.0 x 16 x 0.62 / 0.81
                  = 313 gallons/year
                  = 26 gallons/month (growing season average)

Now varying each factor individually:

| Variation | Change | New Gallons/Year | % Change from Base | |-----------|--------|-----------------|-------------------| | Ks = 0.3 (low water) | Species factor down | 188 | -40% | | Ks = 0.8 (high water) | Species factor up | 502 | +60% | | Kmc = 0.8 (shaded) | Microclimate down | 251 | -20% | | Kmc = 1.2 (full sun, hardscape) | Microclimate up | 376 | +20% | | Kd = 0.6 (sparse) | Density down | 188 | -40% | | Kd = 1.2 (tiered) | Density up | 376 | +20% | | Canopy = 9 sq ft (3' wide) | Smaller plant | 176 | -44% | | Canopy = 25 sq ft (5' wide) | Larger plant | 490 | +57% |

Key takeaway: Species factor and plant size dominate the calculation. Getting Ks and canopy area right matters far more than precision on Kd or Kmc. A Kmc error of 0.2 (e.g., using 1.0 when reality is 1.2) changes the result by 20%. A Ks error of 0.3 (e.g., using 0.5 when reality is 0.8) changes it by 60%.

6.7 Practical MWELO Calculation Examples

Formula summary:

The MWELO framework uses two parallel calculations:

1. MAWA (Maximum Applied Water Allowance) -- the cap:

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

2. ETWU (Estimated Total Water Use) -- the actual design demand:

ETWU = sum over all hydrozones of:
  (ETo x KL x Area x 0.62) / IE

Where KL = Ks x Kd x Kmc is calculated per hydrozone.

Compliance requirement: ETWU must be less than or equal to MAWA.

ETAF caps (2024 amendments):

• Residential projects: ETAF <= 0.55
• Non-residential projects: ETAF <= 0.45
• Special Landscape Areas (edible gardens, recreational turf): ETAF up to 1.0

Worked example -- residential landscape in Sacramento, CA:

Project: 2,000 sq ft total landscape area, no special landscape areas.

ETo (Sacramento, from MWELO Appendix): 51.1 inches/year

Step 1: Calculate MAWA

MAWA = (51.1)(0.62)[(0.55 x 2,000) + ((1 - 0.55) x 0)]
     = (51.1)(0.62)(1,100)
     = 34,851 gallons/year

Step 2: Design hydrozones and calculate ETWU

| Hydrozone | Area (sq ft) | Plant Type | Ks | Kd | Kmc | KL | IE | |-----------|-------------|------------|-----|-----|------|-----|-----| | HZ-1: Low water shrubs | 800 | Native shrubs | 0.3 | 1.0 | 1.0 | 0.30 | 0.81 | | HZ-2: Medium water perennials | 600 | Mixed perennials | 0.5 | 1.0 | 1.0 | 0.50 | 0.81 | | HZ-3: Shade garden | 400 | Ferns, hostas | 0.5 | 1.0 | 0.8 | 0.40 | 0.81 | | HZ-4: Entry planting (hot, near concrete) | 200 | Medium shrubs | 0.5 | 1.2 | 1.2 | 0.72 | 0.81 |

ETWU calculation per hydrozone:

HZ-1: (51.1 x 0.30 x 800 x 0.62) / 0.81 = 9,392 gal/yr
HZ-2: (51.1 x 0.50 x 600 x 0.62) / 0.81 = 11,740 gal/yr
HZ-3: (51.1 x 0.40 x 400 x 0.62) / 0.81 = 6,261 gal/yr
HZ-4: (51.1 x 0.72 x 200 x 0.62) / 0.81 = 5,633 gal/yr

Total ETWU = 9,392 + 11,740 + 6,261 + 5,633 = 33,026 gal/yr

Compliance check: 33,026 <= 34,851. PASS.

Notice how HZ-4 (the entry planting near concrete) uses almost as much water as HZ-1 (which is 4x larger) because the high Kd and Kmc amplify the demand. This is exactly the kind of insight the system should surface to designers.

Converting ETWU to per-plant gallons:

For SimplyScapes' per-plant calculations, the MWELO formula is applied at the individual plant level:

Example: One Pittosporum tobira 'Wheeler's Dwarf' in HZ-2 (medium water, average conditions):

Canopy at planting: 2' wide = 3.14 sq ft (circular canopy estimate)
Per-plant gallons/year = (51.1 x 0.50 x 1.0 x 1.0 x 3.14 x 0.62) / 0.81
                       = 61 gallons/year
                       = ~1.2 gallons/week during peak season

At maturity (4' wide = 12.6 sq ft):

Per-plant gallons/year = (51.1 x 0.50 x 1.0 x 1.0 x 12.6 x 0.62) / 0.81
                       = 243 gallons/year
                       = ~4.7 gallons/week during peak season

This 4x increase from planting to maturity (driven purely by canopy area growth) demonstrates why lifecycle management matters -- the system needs to adjust emitter quantity and runtime as plants grow.

6.8 Sources

| # | Type | Reference | URL | |---|------|-----------|-----| | S1 | API | USDA Soil Data Access (SDA) REST Web Service | https://sdmdataaccess.nrcs.usda.gov/WebServiceHelp.aspx | | S2 | Database | SSURGO - Soil Survey Geographic Database (NRCS) | https://www.nrcs.usda.gov/resources/data-and-reports/soil-survey-geographic-database-ssurgo | | S3 | Tool | SoilWeb -- Online Soil Survey Browser (UC Davis) | https://casoilresource.lawr.ucdavis.edu/gmap/ | | S4 | API | SoilGrids 2.0 REST API (ISRIC) | https://rest.isric.org/soilgrids/v2.0/ | | S5 | Database | gSSURGO - Gridded Soil Survey Geographic Database | https://www.nrcs.usda.gov/resources/data-and-reports/gridded-soil-survey-geographic-gssurgo-database | | S6 | Guide | SDA Advanced Queries Documentation | https://sdmdataaccess.sc.egov.usda.gov/documents/AdvancedQueries.html | | S7 | Research | Costello, Matheny, Clark & Jones (2000) - Landscape Coefficient Method and WUCOLS III | https://cimis.water.ca.gov/Content/PDF/wucols00.pdf | | S8 | Standard | MWELO Final Text and Appendices (CA DWR, Jan 2025) | https://water.ca.gov/-/media/DWR-Website/Web-Pages/Programs/Water-Use-And-Efficiency/MWELO-Rulemaking/Final-MWELO-Text-and-Appendices_20250103.pdf | | S9 | Guide | MWELO Guidebook - Landscape Irrigation Water Budget Overview (CA DWR) | 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 | | S10 | Guide | EPA WaterSense Water Budget Approach | https://www.epa.gov/sites/default/files/2017-01/documents/ws-homes-water-budget-approach.pdf | | S11 | Reference | Atomic Irrigation - Evapotranspiration Kd and Kmc Tables | https://atomicirrigation.com/evapotranspiration-et/ | | S12 | Research | Methodology for Estimating Landscape Irrigation Demand (BSEACD, 2014) | https://bseacd.org/uploads/BSEACD_Irr_Demand_Meth_Rprt_2014_Final_140424.pdf | | S13 | Extension | University of Nebraska - Landscape Mulch for Water Conservation | https://water.unl.edu/article/lawns-gardens-landscapes/landscape-mulch-water-conservation/ | | S14 | Research | University of Florida - Mulch Reduces Soil Water Loss to Evaporation by 33% | https://gardenprofessors.com/university-of-florida-study-mulch-reduces-soil-water-loss-to-evaporation-by-33/ | | S15 | Journal | Frontiers in Agronomy (2024) - Mulching Practices in Dryland Agriculture | https://www.frontiersin.org/journals/agronomy/articles/10.3389/fagro.2024.1361697/full | | S16 | Journal | Irrigation Science (2024) - Mulching Effects on Soil Evaporation and Crop Coefficients | https://link.springer.com/article/10.1007/s00271-024-00924-8 | | S17 | Extension | Clemson HGIC - Soil Type and Irrigation Frequency | https://hgic.clemson.edu/factsheet/landscape-irrigation-management-part-6-soil-type-irrigation-frequency/ | | S18 | Guide | Hunter Industries - Emitter Flow Rate Selection by Soil Type | https://www.hunterirrigation.com/en-metric/support/how-do-i-choose-right-emitter-flow-rate-correct-emitter-spacing-and-appropriate-row-spacing | | S19 | Extension | Utah State University - Water-Wise Landscaping: Mulch | https://extension.usu.edu/cwel/research/water-wise-landscaping-mulch | | S20 | Guide | City of Fresno - Micro/Drip Irrigation by Soil Type | https://www.fresno.gov/wp-content/uploads/2024/05/2024-04-30-Final-Info-Sheet-Micro-Drip-Irrigation-by-Soil-Type.pdf | | S21 | Database | WUCOLS V - Water Use Classification of Landscape Species | https://wucols.ucdavis.edu/ | | S22 | Journal | HortScience - Landscape Coefficients for Single- and Mixed-species Landscapes | https://journals.ashs.org/hortsci/view/journals/hortsci/45/10/article-p1529.xml | | S23 | Tool | CA Open Data - Water Budget Calculators | https://lab.data.ca.gov/dataset/water-budget-calculators | | S24 | Guide | SSURGO Metadata - Table Column Descriptions | https://www.nrcs.usda.gov/sites/default/files/2022-08/SSURGO-Metadata-Table-Column-Descriptions-Report.pdf | | S25 | Guide | CA Soil Resource Lab - SSURGO Analysis Common Queries | https://casoilresource.lawr.ucdavis.edu/software/postgis-spatially-enabled-relational-database-sytem/analysis-ssurgo-data-postgis-overview/logistics-getting-connected-and-executing-queries/learning-example-common-queries |

---

Topic 3: Emitter Product Landscape & Database Design

3.1 Minimum Viable Emitter Database

The residential drip irrigation market is dominated by five manufacturers. A minimum viable product database covering ~80% of residential drip applications requires four emitter categories from each: point-source drip emitters, inline dripline, micro-bubblers, and micro-sprays.

Hunter Industries (hunterirrigation.com)

| Category | Product Family | Flow Rates | Key Specs | |----------|---------------|------------|-----------| | Point-source emitters | HE series | 0.5, 1.0, 2.0, 4.0, 6.0 GPH | Self-piercing barb, 10/32 threaded, 1/2" FPT. Pressure-compensating. Made in USA | | Multi-port emitters | MPE series | 0.5 GPH per port (6 ports) | Pressure-compensating, for plant groupings | | Inline dripline | HDL (3 variants) | 0.4, 0.6, 0.9 GPH | HDL-PC (standard), HDL-CV (check valve for slopes/subsurface), HDL-R (reclaimed water). Spacing: 12", 18", 24". OD 0.660". Operating range 10-60 PSI. 120 mesh filtration. Coils: 100', 250', 500' | | Micro-bubblers | MSBN series | 0.5, 1.0 GPM | Full, half, quarter circle. Pressure-compensating. Mount on Pro-Spray pop-ups | | Micro-sprays | MSN series (Solo-Drip, Halo-Spray, Trio-Spray) | Variable | Short-radius, controlled coverage for small spaces | | Specialty | Eco-Mat, Eco-Wrap, RZWS (Root Zone Watering System) | Various | Subsurface and root-zone applications |

Hunter offers approximately 21 micro irrigation product families total.

Rain Bird (rainbird.com)

| Category | Product Family | Flow Rates | Key Specs | |----------|---------------|------------|-----------| | Point-source emitters | XB / Xeri-Bug series | 0.5, 1.0, 2.0 GPH | Pressure-compensating (15-50 PSI range). Self-piercing barb, 10/32 threaded, 1/2" FPT inlet. Self-flushing. 150-200 mesh filtration | | Multi-outlet | XBD-80 | Configurable per port (10 flow options per port) | 8 ports, integral 200-mesh filter, accepts Xeri-Bug or PC modules | | Inline dripline | XFD / XFDe series | 0.9 GPH typical | Pressure-compensating (8.5-60 PSI). 12" spacing standard. Coils: 100', 250' | | Micro-bubblers | MB series (MBF, MBH) | Up to 24 GPH | Full-circle (8 streams), half-circle (5 streams). Pressure-compensating. Stake-mounted | | Micro-sprays | MS series | 0-29 GPH adjustable | 0-10' spray distance. Fingertip flow control with shut-off. Quarter, half, full circle. Adjustable height staked risers |

Rain Bird also sells complete drip kits (54-piece, 108-piece) for residential DIY.

Netafim (netafimusa.com)

| Category | Product Family | Flow Rates | Key Specs | |----------|---------------|------------|-----------| | Point-source emitters | Woodpecker Jr. (PCJ) / Woodpecker PC | 0.5, 1.0, 2.0, 4.0, 6.0 GPH | Pressure-compensating. Built-in CNL check valve. Self-piercing barb. Industry-leading installed base globally | | Inline dripline | TechLine CV (17mm) | 0.26, 0.4, 0.6, 0.9 GPH | PC range 14.5-58 PSI. 2 PSI check valve (4.6' elevation hold). Spacing: 12", 18", 24". OD 0.66". UV-resistant, post-consumer recycled PE. 7" bending radius | | Inline dripline | TechLine EZ (12mm) | 0.42 GPH | 6" spacing. On-surface looped systems. Self-flushing anti-siphon emitter | | Inline dripline | TechLine CV XR | Various | Copper oxide root intrusion protection for subsurface |

Netafim is the global leader in drip irrigation (invented the technology in Israel). Their landscape/turf division catalog covers driplines, drippers, and accessories. They do NOT manufacture micro-bubblers or micro-sprays for landscape -- they focus on dripline and point-source emitters.

Toro / DML (toro.com)

| Category | Product Family | Flow Rates | Key Specs | |----------|---------------|------------|-----------| | Inline dripline | DL2000 series | 0.5, 1.0 GPH | Pressure-compensating. ROOTGUARD technology (Treflan-impregnated, root intrusion resistant). Spacing: 12", 18". Subsurface or at-grade installation. 4"-8" burial depth. 120 mesh filtration. Black and red coils: 100', 500', 1000' | | Drip tape (ag) | Aqua-Traxx / Aqua-Traxx Azul | Various | PBX design. Primarily agricultural. 4-24" spacing options. Low-pressure (4 PSI minimum) | | Micro-spray/bubbler | Blue Stripe accessories | Various | Consumer-grade. Available at Home Depot/Walmart |

Toro's landscape drip line is focused on the professional market (DL2000 for subsurface). Their Blue Stripe brand serves residential retail. Aqua-Traxx is agricultural and NOT relevant for residential landscape.

Jain Irrigation (jains.com / shop.jains.com)

| Category | Product Family | Flow Rates | Key Specs | |----------|---------------|------------|-----------| | Point-source emitters | Jain Emitter | 0.5, 1.0, 2.0, 3.5 GPH (2, 4, 8, 14 LPH) | Nominal operating pressure 1 kg/cm2. For orchards, vineyards, greenhouses, nurseries, landscape | | Inline dripline | Various | Various | Available through DripWorks and specialty suppliers | | Micro-sprinklers | J-Mini | Various | For landscape, flower beds, shrubs, nurseries |

Jain has limited US residential landscape market presence. Products are primarily sold through specialty agricultural suppliers and their own webstore. Jain acquired ETwater (now Jain Logic) for smart ET-based controllers, which is strategically interesting but separate from emitter hardware.

DIG Corporation (digcorp.com) -- notable mention outside the big five:

DIG offers budget-friendly drip emitters in four operating types (pressure-compensating, turbulent flow, vortex, adjustable flow) and is widely available at Home Depot. They are a significant player in the DIY/residential segment despite not being one of the "big five" professional manufacturers.

3.2 Recommended MVP Product Set

For 80% residential coverage, the minimum viable database needs:

| Emitter Type | Recommended Brands | Why | |-------------|-------------------|-----| | Point-source PC emitters | Hunter HE, Rain Bird XB, Netafim Woodpecker | These three dominate professional and residential installations. 0.5-6.0 GPH range covers all individual plant scenarios | | Inline dripline | Hunter HDL, Rain Bird XFD, Netafim TechLine CV, Toro DL2000 | All four are specified regularly. Toro DL2000 is the subsurface leader. Netafim TechLine is the most specified dripline overall | | Micro-bubblers | Hunter MSBN, Rain Bird MB series | Only Hunter and Rain Bird offer full micro-bubbler lines for landscape. Needed for large trees and shrubs | | Micro-sprays | Hunter MSN, Rain Bird MS series | Same two manufacturers dominate. Critical for mass plantings and ground cover |

Estimated SKU count for MVP: Approximately 80-120 SKUs total (5 flow rates x 3 connection types x 3 brands for point-source = ~45; 3-4 flow/spacing combos x 4 brands for dripline = ~48; plus ~20 micro-bubbler/spray variants). This is manageable for initial manual data entry.

3.3 Structured Product Data Availability

| Source | Format | Access | Quality | Notes | |--------|--------|--------|---------|-------| | Hunter PIM | XLSX, CSV, web-based | Login required; fill survey form to request access | High | Centralized product data management system. Designed for distributor ERP/WMS/CMS integration. Best structured data source of any manufacturer. URL: hunterirrigation.com/distributor-resources/hunter-pim | | Rain Bird | PDF specs, IQ4 API (controller data only) | PDFs public; API requires subscription | Medium | Product specs are PDF catalogs, not structured data. The IQ4 API is for controller telemetry, NOT product catalog data. Technical specs downloadable from rainbird.com/agency/technical-specifications-agency | | Netafim | PDF catalogs | Public download | Medium | Landscape & Turf catalog (2023 edition) covers all products. PDF only -- no structured data feed. Download hub: netafimusa.com/download-resources | | Toro | PDF spec catalog | Public download | Medium | Specification catalog available at specifier.toro.com. 2025 price list published. No API or structured data feed | | Jain | Web store listings, PDF | Basic | Low | Limited structured data. Primarily consumer web store | | Distributor APIs | None found | N/A | N/A | Neither Ewing Irrigation nor SiteOne Landscape Supply offers public product data APIs or feeds. SiteOne has an online catalog but no developer access | | Open-source databases | None found | N/A | N/A | No open-source irrigation product database exists. MIT GEAR Lab has low-pressure emitter research but no product catalog. IrrigationGlobal.com has basic technical data links |

Key finding: Hunter's PIM system is the only structured, machine-readable product data source in the industry. All other manufacturers distribute specifications as PDF catalogs only. For an MVP, the practical approach is:

1. Request Hunter PIM access (XLSX/CSV export)
2. Manually extract data from Rain Bird, Netafim, and Toro PDF catalogs
3. Structure into a normalized database table with columns: manufacturer, product_family, model, emitter_type, flow_rate_gph, connection_type, pressure_compensating (bool), min_pressure_psi, max_pressure_psi, check_valve (bool), spacing_options, filtration_mesh

3.4 Product Line Stability & Maintenance Burden

Update frequency: Emitter product lines are notably stable compared to electronics or software. Based on the research:

• Core emitter families persist for 5-10+ years. Hunter's point-source emitters and Rain Bird's Xeri-Bug have been on the market for well over a decade with incremental improvements but no radical redesigns. Netafim's Woodpecker has been the global standard for decades.
• Dripline products evolve more frequently (3-5 year cycles) as manufacturers add variants (check valves, root barriers, new flow rates). Hunter's HDL replaced their older PLD line. Netafim added TechLine CV XR (copper oxide) as a variant.
• New products are additive, not replacements. Manufacturers rarely discontinue emitter SKUs -- they add new options. Hunter recently launched redesigned point-source emitters but kept the same flow rate and connection options.
• Price lists update annually (Toro publishes yearly; current list is 2025).

Estimated maintenance burden: A well-structured emitter database would need review approximately once per year at the manufacturer trade show cycle (Irrigation Show, typically November/December). Updates would typically involve adding new SKUs rather than modifying existing ones. This is a very manageable maintenance load -- likely 4-8 hours per year to check for new products and add them.

Risk: acquisitions. Toro acquired DML (the Drip Mist Landscape division). Jain acquired ETwater. Industry consolidation could change product lines, but historically acquiring companies maintain existing product families.

---

Topic 4: ET Data Sources & Accuracy for Compliance

4.1 Open-Meteo ET0 Accuracy

What Open-Meteo provides:

• FAO-56 Penman-Monteith ET0 calculation using temperature, wind speed, humidity, and solar radiation
• Hourly and daily resolution
• Global coverage at up to 2 km spatial resolution (varies by weather model)
• Free for non-commercial use; no API key required for basic access
• Available parameter: et0_fao_evapotranspiration (in mm/hour for hourly, mm/day for daily)
• API endpoint: open-meteo.com/en/docs

Underlying weather models and their resolutions: | Model | Resolution | Forecast Range | Best For | |-------|-----------|----------------|----------| | ECMWF IFS | 9 km | 10 days | Global, highest accuracy globally | | ICON (DWD) | 2 km (Europe), variable elsewhere | 7 days | Europe (temperature, cloud, wind gusts) | | GFS (NOAA) | 25 km (forecast), 50 km (extended) | 16-35 days | US, long-range | | HRRR (NOAA) | 3 km | ~18 hours | US, very high resolution short-term | | ERA5 (ECMWF) | 25 km (0.25 degrees) | Historical reanalysis | Historical data, gap-filling |

Accuracy assessment:

• No published validation study was found comparing Open-Meteo ET0 specifically to CIMIS ground-station data or any other reference network. This is a significant gap.
• Open-Meteo states their weather model time series is "nearly as accurate as direct measurements" due to high update frequencies (1, 3, or 6 hours) and initialization from weather stations, satellites, radar, airplanes, and soundings.
• The underlying weather models are well-validated (ECMWF is considered the most accurate global model), but the ET0 calculation adds another layer where errors in any input variable (especially wind speed and humidity, which have the poorest spatial resolution) compound.
• For the US specifically: The HRRR model at 3 km resolution provides the best input data, but only for short-term forecasts. GFS at 25 km provides longer-range data but with coarser inputs.
• Important distinction: Open-Meteo provides both an et0_fao_evapotranspiration (reference ET for well-watered grass) and a separate evapotranspiration variable that accounts for actual vegetation and soil moisture. For MWELO calculations, the ET0 reference value is what's needed.

Bottom line: Open-Meteo ET0 is likely within 10-20% of ground-station measurements for most US locations based on the quality of the underlying weather models, but this has NOT been formally validated. For compliance-critical applications, this uncertainty may be problematic.

4.2 MWELO Compliance Requirements

What the regulation requires:

The Maximum Applied Water Allowance (MAWA) formula:

MAWA = ETo x ETAF x LA x 0.62

Where:

• ETo = Reference evapotranspiration (from MWELO Appendix A/C, based on CIMIS zones)
• ETAF = Evapotranspiration Adjustment Factor = Plant Factor / Irrigation Efficiency
• LA = Landscape Area (sq ft)
• 0.62 = Conversion factor (inches to gallons per sq ft)

ETAF caps (2024 amendments):

• Residential: ETAF cannot exceed 0.55
• Non-residential: ETAF cannot exceed 0.45
• Special Landscape Areas (edible gardens, recreational turf): ETAF up to 1.0

Plant factors (from WUCOLS):

• Very Low: 0.0-0.1
• Low: 0.1-0.3
• Moderate: 0.4-0.6
• High: 0.7-1.0

ET data sources accepted:

• MWELO Appendix A/C provides annual and monthly ETo values by city/county across California, derived from CIMIS reference evapotranspiration zones (1999 base map)
• For locations not in Appendix A/C: use data from nearby cities in the same CIMIS reference evapotranspiration zone
• For irrigation scheduling (distinct from water budget): "current reference evapotranspiration data, such as from CIMIS, other equivalent data, or soil moisture sensor data"

Key finding: MWELO does NOT mandate CIMIS as the only acceptable ET source. The regulation says "such as from CIMIS" -- using language of example, not requirement. However, the water budget calculation itself uses fixed annual ETo values from Appendix A/C (which ARE derived from CIMIS). The dynamic ET data (for scheduling, not budgeting) allows "other equivalent data."

Compliance is at zone level, not per-plant. MWELO compliance is calculated at the landscape project level -- the total MAWA for the entire landscape area. Hydrozones must be defined (grouping plants by water use), but the compliance calculation aggregates to the whole project. Per-plant granularity exceeds what's required -- it's an enhancement, not a necessity for compliance.

2024 MWELO Amendments:

• Approved October 2024 by California Water Commission
• Clarified that "annual reference" ETo is used for MAWA calculation
• Appendix C (renumbered) provides both annual and monthly ETo values
• Monthly values are for irrigation scheduling and auditing
• Annual values are for water budget compliance
• Updated online February 2025

District-specific requirements:

| District | ET Data Source | Reporting | Notes | |----------|--------------|-----------|-------| | EBMUD (East Bay) | CIMIS | GIS + aerial image landscape area measurement at water service application | Water Efficiency Review at tap application. Compliance enforced at landscape plan review stage | | LADWP (Los Angeles) | CIMIS / Spatial CIMIS | Annual reporting | LA region well-covered by CIMIS stations | | Denver Water | CoAgMet / local ET | Irrigation & Landscape Plan review for taps serving 1+ acre irrigated area | Water budget required. Benchmark: 12 gal/sq ft/year. Must show hydrozone-based irrigation plan |

Annual reporting requirement (statewide): All California cities and counties must report MWELO implementation to DWR by January 31 each year via the WUEdata Portal.

4.3 OpenET Platform Capabilities

What it is: OpenET (etdata.org) is a NASA/USGS-supported online platform that maps actual evapotranspiration at field scale (30m x 30m) using satellite data. It runs an ensemble of six Landsat-driven ET models: DisALEXI, eeMETRIC, geeSEBAL, PT-JPL, SIMS, and SSEBop.

Data products:

• Daily, monthly, and annual satellite-based ET data
• 30m x 30m spatial resolution (individual field/parcel scale)
• Historical data from 2000 to present (monthly), 2016 to present (daily)
• Also provides gridded precipitation and vegetation condition data

API access:

• REST API at openet-api.org (documentation: openet.gitbook.io/docs)
• Supports custom field boundary queries
• Free tier: 100 queries/month, max 50,000 acres per query
• Account registration required, API key from Account Dashboard
• Support: support@openetdata.org

Coverage expansion (2025):

• Originally launched 2021 with 17 western states
• Expanded to 23 states in 2023
• As of late 2025: expanded to 48 states (eastern US coverage added)

Accuracy:

• Validated against 152 in-situ flux tower stations across the contiguous US
• Cropland: Mean absolute error 15.8 mm/month (17% of mean observed ET), mean bias -5.3 mm/month (6%), r-squared 0.90
• Shrublands/forests: Higher inter-model variability and lower accuracy compared to croplands
• Urban turfgrass: DisALEXI model performed best with RMSE 0.6 mm/day and r-squared 0.8 (AGU 2024 presentation -- preliminary results)

Critical distinction for SimplyScapes: OpenET measures ACTUAL ET, not REFERENCE ET (ET0).

For MWELO compliance, you need reference ET0 (the ET of a hypothetical well-watered grass surface), then apply plant factors and irrigation efficiency to calculate allowable water. OpenET gives you what the landscape actually used -- which is useful for auditing and verification, but is a different data product than what's needed for design-time water budgeting.

Potential use case for SimplyScapes: OpenET could serve as a verification/auditing tool -- comparing the design-time water budget against satellite-measured actual water use post-installation. This is a powerful differentiator for water district customers but is a secondary use case.

4.4 Regional ET Networks Outside California

| Network | State | Stations | ET Method | Data Access | API/Format | |---------|-------|----------|-----------|-------------|------------| | CIMIS | California | 145+ active | ASCE Penman-Monteith | Free, API key required | REST API (JSON/XML). Query by station, zip code, coordinates, street address. et.water.ca.gov | | Spatial CIMIS | California (statewide) | Satellite + station hybrid | ASCE-PM with GOES satellite solar data | Free, account required | 2 km grid, ASCII files. Daily ETo and solar radiation maps. cimis.water.ca.gov/SpatialData.aspx | | TexasET | Texas | 56 stations | Penman-Monteith | Free | texaset.tamu.edu. Cell phone/IP data transfer | | FAWN | Florida | 42 stations | Penman-Monteith | Free | CSV, JSON, XHTML formats. 15-minute data intervals. fawn.ifas.ufl.edu/data | | CoAgMet | Colorado | 90+ stations | Penman-Monteith | Free | coagmet.colostate.edu. Research-grade weather stations | | AZMET | Arizona | ~28 stations | Penman-Monteith | Free | azmet.arizona.edu. Hourly and daily data |

Coverage assessment:

• Well-covered states: California (CIMIS is gold standard, 145+ stations + satellite), Arizona (AZMET), Florida (FAWN), Colorado (CoAgMet), Texas (TexasET)
• Partially covered: Most agricultural states have some network through Extension services
• Significant gaps: Northeast US, Pacific Northwest (limited dedicated ET networks -- rely on NWS data and weather model estimates), Upper Midwest

Important finding: Outside the western US, dedicated ET weather station networks are sparse. States without agricultural ET networks (much of the Northeast, Midwest, Southeast beyond Florida) would need to rely on either: (a) Open-Meteo modeled ET0, (b) National Weather Service data calculated into ET0, or (c) OpenET satellite-based actual ET (now available in 48 states). This makes Open-Meteo (or equivalent weather-model-based ET0) effectively the only option for national coverage.

4.5 Emerging ET Data Sources

ECOSTRESS (NASA/JPL) -- Collection 2 (launched January 2024)

• 70m resolution thermal-infrared data from the ISS
• ~4-day revisit interval
• Collection 2 improvements: updated calibration, better geolocation, improved cloud mask, new ET models (PT-JPL-SM with soil moisture constraint)
• Data fusion product (ECO_L2T_STARS) combining VIIRS (500m-1km) and Harmonized Landsat Sentinel-2 (30m) for daily 30m ET
• Useful for research but NOT operationally integrated into irrigation scheduling tools yet

OpenET nationwide expansion (2025)

• Expanded from 23 to 48 states, covering most of the contiguous US
• This is the most significant development for SimplyScapes' national ambitions -- satellite-based ET data is now available almost everywhere
• Still measures actual ET (not reference ET0), but the expansion signals growing institutional acceptance

Landsat + Sentinel-2 data fusion

• Research combining Landsat thermal (30m) with Sentinel-2 optical (10m) data
• Enables daily ET estimates at 30m resolution (vs. Landsat-only 16-day cycle)
• OpenET already incorporates this approach

ERA5-Land (ECMWF)

• Historical reanalysis at 9 km resolution (improved from ERA5's 25 km)
• Available through Open-Meteo for historical ET0 calculations
• Useful for establishing baseline ET patterns at a location

4.6 Recommended ET Data Strategy for SimplyScapes

| Use Case | Primary Source | Fallback | Notes | |----------|---------------|----------|-------| | Design-time water budgeting (national) | Open-Meteo ET0 | CIMIS Appendix A/C values (California only) | Open-Meteo is the only free, no-API-key, global-coverage ET0 source with sufficient resolution. Use CIMIS values for CA compliance specifically | | California MWELO compliance | CIMIS (Appendix A/C annual values for budget; Spatial CIMIS for scheduling) | Open-Meteo ET0 as supplement | CIMIS is the accepted standard. Water budgets must use Appendix A/C values. Open-Meteo can supplement for scheduling | | Runtime irrigation scheduling | Open-Meteo ET0 (daily/hourly) | State ET networks where available (FAWN, AZMET, CoAgMet, TexasET) | Real-time ET0 adjustments need high-frequency data. Open-Meteo provides this nationally | | Post-installation auditing | OpenET (actual ET at 30m) | Water meter data from utility | Compare actual ET (what the landscape consumed) against designed water budget. Powerful for water district reporting | | Historical baseline analysis | Open-Meteo (ERA5-based historical ET0) | CIMIS historical records (California) | Establish typical ET patterns for a location to inform scheduling defaults |

Key recommendations:

1. Build on Open-Meteo first for national coverage and ease of integration (free, no API key, REST API)
2. Integrate CIMIS data for California to ensure regulatory acceptance
3. Add OpenET as a premium auditing feature for water district customers
4. Plan for, but don't block on, validation -- Commission or conduct a comparison study of Open-Meteo ET0 vs. CIMIS station data for key California locations to quantify accuracy. This would be a publishable finding that benefits the industry
5. Store ETo at the project location level -- cache daily ET0 values per project so scheduling calculations don't require real-time API calls

---

Topic 2: Establishment & Growth Lifecycle Science

2.1 Establishment Periods by Climate Region

The most comprehensive establishment data comes from Dr. Edward Gilman's research at UF/IFAS. The establishment period -- defined as the time until roots have grown approximately 3x the distance from trunk to branch tips and growth rates stabilize year-to-year -- varies dramatically by USDA hardiness zone:

Tree Establishment Period (months per inch trunk caliper):

| USDA Hardiness Zone | Months per Inch Caliper | Example: 2" Caliper Tree | Example: 4" Caliper Tree | |---------------------|------------------------|-------------------------|-------------------------| | Zones 9-11 (warmest) | 3 months | 6 months | 12 months | | Zones 7-8 | 6 months | 12 months | 24 months | | Zones 2-6 (coolest) | 12 months | 24 months | 48 months | | Desert climates | Extended beyond zone guidelines | Variable | Variable |

Source: UF/IFAS -- Tree Establishment Period (Gilman) | Virginia Tech -- Planting Trees (426-702)

Regional confirmation from extension services:

• Colorado (Zone 5-6): CSU Extension confirms one year per inch of trunk diameter minimum, with 3-5 years for full establishment. Winter watering required. Source: CSU GardenNotes #635
• Virginia (Zone 6-8): Virginia Extension documents 6 months per inch in zones 7-8, one year per inch in zones 6 and below, consistent with Gilman data. Source: Virginia Cooperative Extension
• Arizona (Zone 9-10): AMWUA provides week-by-week desert schedules showing establishment in weeks (not months per caliper), reflecting the faster warm-climate timeline but also the need for more intensive irrigation in arid conditions. Source: AMWUA Watering Schedules
• Minnesota (Zone 3-4): UMN Extension recommends weekly watering for at least 12 weeks, then continued monitoring through the first full growing season. Source: UMN Extension -- Watering Newly Planted Trees and Shrubs
• Pacific Northwest (Zone 7-9): PNW ISA recommends 2-3 years of supplemental irrigation during dry summers, even for rain-adapted species. Source: PNW ISA -- Providing Water & Nutrients

Shrub and perennial establishment periods:

| Plant Type | Typical Establishment Period | Notes | |-----------|----------------------------|-------| | Trees (deciduous) | Gilman formula: months/inch × caliper | Longest establishment; most data available | | Trees (evergreen) | Same formula, plus fall watering in cold zones | Need winter watering before ground freezes (MD, CO, MN) | | Shrubs | 6-12 months (smaller), 12-24 months (larger) | Less studied than trees; generally follow tree patterns scaled down | | Perennials | 4-12 months depending on season planted | Spring plantings: monitor through following summer. Fall plantings: established by second summer | | Groundcovers | 3-6 months, then irrigation system can handle | Fastest to establish; most tolerant of automated irrigation |

Source: Weston Nurseries -- New Plant Watering Guidelines | Backbone Valley Nursery -- Watering Guidelines | PSU Extension -- Care and Maintenance of Perennials

---

2.2 Three-Phase Tapering Schedule (Gilman Model)

The UF/IFAS three-phase tapering schedule is the most widely cited and regionally adaptable model. It provides specific frequency and volume guidance by tree size:

Irrigation Frequency by Tree Size:

| Phase | Trees < 2" Caliper | Trees 2-4" Caliper | Trees > 4" Caliper | |-------|-------------------|--------------------|--------------------| | Phase 1: High frequency | Daily for 2 weeks | Daily for 1 month | Daily for 6 weeks | | Phase 2: Tapering | Every other day for 2 months | Every other day for 3 months | Every other day for 5 months | | Phase 3: Maintenance | Weekly until established | Weekly until established | Weekly until established |

Volume per irrigation event:

| Climate | Gallons per Inch Trunk Caliper | |---------|-------------------------------| | Cool climates (zones 2-6) | 1-2 gallons | | Warm climates (zones 7-11) | 2-3 gallons |

Source: UF/IFAS -- Tree Irrigation Schedule (Gilman)

Example calculation: A 3" caliper live oak (Quercus virginiana) planted in Sacramento (Zone 9b):

• Phase 1: Daily, 6-9 gallons per event, for 1 month
• Phase 2: Every other day, 6-9 gallons per event, for 3 months
• Phase 3: Weekly, 6-9 gallons per event, until established (~9 months total)
• Total establishment period: ~9 months (3 months/inch × 3 inches)

Desert region schedule (AMWUA):

The Arizona Municipal Water Users Association provides a separate weekly tapering schedule for desert-adapted plants:

| Weeks | Frequency | |-------|-----------| | Weeks 1-2 | Every 1-2 days | | Weeks 3-4 | Every 3-4 days | | Weeks 5-8 | Every 4-7 days | | Weeks 8+ | Every 7-14 days | | Year 2+ | Every 10-14 days (transitioning to seasonal deep watering) |

Source: AMWUA -- Watering Schedules

Colorado/Mountain West schedule (CSU):

| Period | Frequency | Notes | |--------|-----------|-------| | First growing season | Every other day | Adjust for rainfall | | Winter (year 1) | Once per week to twice per month | When temps above freezing, no snow cover | | Year 2 growing season | 2x per week | Tapering from establishment | | Years 3-5 | 2x per month (summer), 1x per month (winter) | Monitoring for stress signs | | Year 5+ | Established; water during drought only | Some species become fully drought-tolerant |

Source: CSU GardenNotes #635 | CSU Extension -- Fall and Winter Watering

Key insight for SimplyScapes: The three-phase Gilman model (daily → every other day → weekly) is simple, widely validated, and parameterizable by just two inputs: tree caliper at planting and USDA hardiness zone. Desert and mountain regions need additional winter watering logic. This is directly encodable into software.

---

2.3 Planting Method Effects on Establishment

How a plant was grown in the nursery significantly affects its irrigation needs during establishment:

Container-grown vs. field-grown (B&B) vs. bare root:

| Factor | Container-Grown | B&B (Field-Grown) | Bare Root | |--------|----------------|-------------------|-----------| | Root system at planting | Circling roots in soilless media; confined to pot volume | Roots severed during harvest; soil intact around root ball | No soil; dormant roots exposed | | Initial water sensitivity | Most sensitive -- root ball dries faster than surrounding soil due to soilless media | Moderate -- soil-to-soil interface can impede water movement | Low sensitivity initially (dormant); needs moisture as roots activate | | Establishment speed | Slower -- roots must grow out of container media into landscape soil | Moderate -- roots regenerate quickly if "hardened off" | Often fastest for small plants -- no media interface issues | | Irrigation frequency needed | Highest -- must keep root ball moist; container media dries faster than native soil | Moderate -- soil types may differ between root ball and site | Lower once active; 4-6 weeks dormancy before visible growth | | Risk of failure if underwatered | Highest -- desiccation and death if root ball dries | Moderate -- freshly dug trees also susceptible | Low (if dormant); moderate once leafing out |

Source: UF/IFAS -- Container vs. Field-Grown Comparisons (Gilman) | UF/IFAS Extension -- Differences Between Container, B&B, and Bare Root Trees | RootMaker -- Establishment of Container Grown Plants

Gilman's key finding: Despite container plants taking longer to establish, shoot and trunk growth appear similar to field-grown trees provided irrigation is supplied until establishment is complete. The critical variable is irrigation management during the first year, not the production method itself.

Recommendation for SimplyScapes: For MVP, the system should ask planting method (container, B&B, bare root) and adjust Phase 1 duration:

• Container: Extend Phase 1 by 50% (more frequent watering needed to keep soilless media moist)
• B&B: Use standard Gilman schedule
• Bare root: Shorter Phase 1 (less initial volume needed) but add a 4-6 week dormancy period before the schedule begins

---

2.4 Ornamental Plant Growth Rate Data

Understanding how fast landscape plants grow is essential for predicting when emitter adjustments are needed (adding emitters, moving them outward, upsizing to bubblers).

Industry Growth Rate Classifications

The landscape industry uses a three-tier growth rate classification:

| Category | Growth Rate | Typical Species Examples | |----------|------------|------------------------| | Slow | ≤ 12 inches/year | Boxwood, Japanese maple, Southern magnolia | | Medium (Moderate) | 13-24 inches/year | Red maple, Crape myrtle, Holly | | Fast | ≥ 25 inches/year | River birch, Willow oak, Leyland cypress |

Source: Melinda Myers -- Tree and Shrub Growth Rates | Davey Tree -- Tree Growth Rates 101

These classifications apply to height growth. Canopy spread growth is less standardized but generally follows a similar proportional pattern based on the species' mature height-to-width ratio.

Virginia Tech Tree Canopy Spread Database

The most directly applicable database for SimplyScapes is the Virginia Tech/VNLA Tree Canopy Spread Coverage database:

Database overview:

• 336 tree species (234 deciduous, 102 evergreen)
• Provides 10-year and 20-year canopy spread projections
• Assumes standard nursery stock starting size (1"-2" caliper or 5'-7' height)
• Values are estimates for Mid-Atlantic urban landscapes
• Sortable by botanical name or tree size
• Downloadable as Excel spreadsheet
• Each species hyperlinked to UF/USFS fact sheet

Projection examples (from standard nursery stock):

| Species | 10-Year Spread (ft) | 10-Year Area (sq ft) | 20-Year Spread (ft) | 20-Year Area (sq ft) | |---------|--------------------|--------------------|--------------------|--------------------| | Small (e.g., Taxodium imbricarium) | 5-6 | 21-26 | ~8-10 | ~50-80 | | Large (e.g., Ulmus americana) | 15-18 | 175-250 | 20-25 | 314-491 |

Source: VNLA/Virginia Tech -- Tree Canopy Spread Coverage | Virginia Tech Urban Forestry -- Canopy Spread Database

Relevance for SimplyScapes: This database provides the canopy growth projections needed to predict when emitter placement adjustments are needed. If a species grows from 4' spread to 12' spread in 10 years, the system can schedule emitter repositioning alerts at year 3-4 (when the dripline has moved significantly) and hardware upgrade recommendations at year 8-10 (when the tree may need bubblers instead of point-source emitters).

Growth Rate Data in SimplyScapes' Existing Plant Table

SimplyScapes already stores growth_rate in its plant table, along with height (mature) and width (mature). Combined with the planting size (which the user specifies at design time or the system defaults from ANSI Z60.1 nursery standards), the system can interpolate growth over time:

Simple linear interpolation model:

Year N canopy width = Planting width + (Mature width - Planting width) × (N / Years to maturity)

Where "Years to maturity" can be estimated from the growth rate category:

• Slow: 20-30 years to mature width
• Medium: 10-20 years
• Fast: 5-10 years

This is deliberately oversimplified -- growth is not linear (it's more sigmoid-shaped, with slow initial growth, rapid middle growth, and asymptotic approach to mature size). But for the purpose of scheduling emitter adjustments every 3-5 years, a linear approximation is adequate. The system prompts users to update actual plant size periodically anyway.

ANSI Z60.1 Nursery Stock Standards

ANSI Z60.1 (American Standard for Nursery Stock) defines standard relationships between caliper, height, and root ball size at the time of sale:

Shade tree caliper-to-height relationship (typical):

| Caliper (inches) | Typical Height (ft) | Typical Root Ball Diameter (in) | |-------------------|--------------------|---------------------------------| | 1.0 | 6-8 | 18 | | 1.5 | 8-10 | 20 | | 2.0 | 10-12 | 24 | | 2.5 | 12-14 | 28 | | 3.0 | 14-16 | 32 | | 4.0 | 16-18 | 42 |

Source: ANSI Z60.1-2014 -- American Standard for Nursery Stock

Relevance for SimplyScapes: When a user specifies a tree by caliper size at planting, ANSI Z60.1 provides the expected height and root ball diameter. This feeds the initial emitter placement (emitters at 6-12" from trunk, based on root ball diameter) and the initial canopy area estimate (for water budget calculations).

---

2.5 Phase Transition Triggers

The plan asked: what should trigger transitions between establishment phases -- time-based, growth-based, or user-confirmed?

Recommendation: Time-based with user confirmation at milestones.

| Trigger Type | Pros | Cons | Verdict | |-------------|------|------|---------| | Time-based (automatic) | Simple, predictable, no user input needed after planting date | Doesn't account for actual plant health or microclimate | Primary trigger -- reliable default | | Growth-based (measured) | Most accurate | Requires user to measure/report plant size; few will do this regularly | Enhancement -- offer but don't require | | User-confirmed (manual) | Puts the user in control | Creates notification fatigue; users forget | Milestone check -- prompt at key transitions |

Recommended hybrid approach for SimplyScapes:

1. Automatic time-based transitions using the Gilman schedule (parameterized by caliper, zone, and planting method)
2. Milestone notifications at phase transitions: "Your Red Maple was planted 3 months ago. The system is moving from daily to every-other-day watering. Does this look right based on how the tree is doing?"
3. Annual growth check prompt: "It's been one year since planting. How does your tree look?" with options: "Thriving" (proceed to next phase), "Stressed" (extend current phase), "I've lost this plant" (remove from schedule)
4. Emitter adjustment alerts based on projected canopy growth: "Your tree's canopy is estimated at 8 feet now. Consider adding 2 emitters and moving them outward to the dripline."

This approach works without sensors, respects user attention, and degrades gracefully if the user ignores prompts (the time-based schedule continues regardless).

---

2.6 Key Findings and Recommendations

Finding 1: The Gilman establishment model is the gold standard. The months-per-inch-per-zone formula is the most widely cited, regionally validated, and computationally simple model. It's the right foundation for SimplyScapes' establishment engine.

Finding 2: Four US climate patterns need distinct schedules. The research supports four establishment schedule archetypes:

1. Warm humid (zones 9-11, Southeast/Gulf): Fastest establishment, moderate irrigation intensity
2. Temperate (zones 6-8, Mid-Atlantic/Upper South): Moderate establishment, seasonal irrigation
3. Cold (zones 2-5, Midwest/Northeast): Slowest establishment, winter watering critical
4. Arid/Desert (zones 7-10, Southwest/Mountain West): Fast establishment timeline but highest irrigation intensity, year-round watering including winter

Finding 3: Planting method matters for Phase 1 intensity. Container-grown plants need more frequent irrigation in Phase 1 than B&B or bare root. This is a meaningful adjustment the system should make.

Finding 4: The Virginia Tech canopy database is directly applicable. 336 species with 10- and 20-year canopy projections, downloadable as Excel. Combined with SimplyScapes' existing growth_rate and width fields, this provides the data needed for growth-based emitter adjustment alerts.

Finding 5: Shrub and perennial establishment data is less formalized. Tree establishment is well-studied (Gilman, extension services). Shrub and perennial data is largely derived from tree research with shorter timelines. The system should apply scaled-down versions of tree schedules (e.g., shrubs = 50-75% of tree establishment duration for same zone).

Finding 6: Phase transitions should be time-based with user checkpoints. Automatic scheduling with milestone notifications and annual growth prompts balances accuracy with user experience. Sensor-free operation is preserved.

Finding 7: Growth modeling is adequate at the 3-5 year resolution needed. The system doesn't need to predict exact canopy size at month 18. It needs to know approximately when to alert the user to add emitters or reposition them. Linear interpolation from planting size to mature size, grouped into 3-5 year milestones, is sufficient for this purpose.

Topic 2 Sources

| # | Type | Reference | URL | |---|------|-----------|-----| | 1 | Research | UF/IFAS -- Tree Establishment Period (Gilman) | https://hort.ifas.ufl.edu/woody/establishment-period.shtml | | 2 | Research | UF/IFAS -- Tree Irrigation Schedule (Gilman) | https://hort.ifas.ufl.edu/woody/irrigation2.shtml | | 3 | Research | UF/IFAS -- Container vs. Field-Grown Comparisons | https://hort.ifas.ufl.edu/woody/more-comparisons.shtml | | 4 | Extension | UMN Extension -- Watering Newly Planted Trees and Shrubs | https://extension.umn.edu/planting-and-growing-guides/watering-newly-planted-trees-and-shrubs | | 5 | Extension | CSU GardenNotes #635 -- Care of Recently Planted Trees | https://cmg.extension.colostate.edu/Gardennotes/635.pdf | | 6 | Extension | CSU Extension -- Fall and Winter Watering | https://extension.colostate.edu/resource/fall-and-winter-watering-of-plants-and-trees/ | | 7 | Extension | Virginia Cooperative Extension -- Planting Trees (426-702) | https://www.pubs.ext.vt.edu/content/dam/pubs_ext_vt_edu/426/426-702/426-702.pdf | | 8 | Extension | University of Maryland Extension -- Watering Trees and Shrubs | https://extension.umd.edu/resource/watering-trees-and-shrubs | | 9 | Extension | PSU Extension -- Care and Maintenance of Perennials | https://extension.psu.edu/care-and-maintenance-of-perennials | | 10 | Guide | AMWUA -- Arizona Watering Schedules | https://www.amwua.org/landscaping-with-style/maintain/watering-schedules | | 11 | Guide | PNW ISA -- Providing Water & Nutrients | https://pnwisa.org/page/providing-water-nutrients | | 12 | Database | VNLA/Virginia Tech -- Tree Canopy Spread Coverage in Urban Landscapes | https://vnla.org/tree-canopy-spread-coverage-in-urban-landscapes/ | | 13 | Database | Virginia Tech -- Tree Canopy Spread Predictions | http://dendro.cnre.vt.edu/predictions/about.htm | | 14 | Standard | ANSI Z60.1-2014 -- American Standard for Nursery Stock | https://cdn.ymaws.com/americanhort.site-ym.com/resource/collection/38ED7535-9C88-45E2-AF44-01C26838AD0C/ANSI_Nursery_Stock_Standards_AmericanHort_2014.pdf | | 15 | Extension | UF/IFAS Extension -- Container, B&B, Bare Root Differences | https://blogs.ifas.ufl.edu/lakeco/2021/12/20/differences-between-container-bb-and-bare-root-trees/ | | 16 | Research | RootMaker -- Establishment of Container Grown Plants | https://rootmaker.com/wp-content/uploads/2024/11/establishment.pdf | | 17 | Reference | Melinda Myers -- Tree and Shrub Growth Rates | https://www.melindamyers.com/audio-video/melindas-garden-moment-audio-tips/trees-shrubs-roses/tree-and-shrub-growth-rates | | 18 | Reference | Davey Tree -- Tree Growth Rates 101 | https://blog.davey.com/tree-growth-rates-101-what-you-should-know/ |

---

Topic 5: Controller Integration Feasibility

5.1 API Capability Matrix

The plan asked whether SimplyScapes can push schedule changes to consumer irrigation controllers. After reviewing available documentation, the answer is nuanced: most controllers expose APIs, but none support full third-party schedule creation.

Controller API Capabilities:

| Capability | Rachio | Hunter Hydrawise | Rain Bird (LNK2) | B-hyve (Orbit) | OpenSprinkler | |-----------|--------|-----------------|-------------------|-----------------|---------------| | Public API | Yes (documented) | Yes (REST, documented) | No (reverse-engineered) | No (reverse-engineered) | Yes (open source) | | Authentication | Bearer token (API key) | API key per account | Local LAN discovery | Cloud WebSocket | Local HTTP / cloud | | Read zone config | Yes | Yes | Limited | Yes (unofficial) | Yes | | Read schedules | Yes | Yes (next run, duration) | Limited | Yes (unofficial) | Yes | | Start/stop zones manually | Yes (up to 3 hrs) | Yes | Yes | Yes (unofficial) | Yes | | Push new schedule | No -- can only skip/start existing | No -- run/suspend/stop only | No | No | Yes -- full schedule push | | Modify schedule parameters | Seasonal adjustment only (-100% to +100%) | No | No | No | Yes -- full control | | Set soil moisture | Yes (mm or %) | No | No | No | No | | Webhooks/events | Yes | No | No | No | MQTT, IFTTT, email | | Rate limits | 1,700 calls/day | Unknown | N/A (local) | Unknown | No limit (local) | | Commercial use allowed | Not specified | No (personal use only) | N/A | N/A | Yes (open source) | | Partner program | Not found | Not found | Not found | Not found | N/A |

Sources: Rachio API Docs | Rachio API Support | Hydrawise REST API v1.5 (PDF) | Hydrawise API Info | Rain Bird Home Assistant Integration | B-hyve Unofficial API (GitHub) | OpenSprinkler GitHub

5.2 Key Finding: No Major Controller Supports Third-Party Schedule Push

The most significant finding: none of the major consumer controllers (Rachio, Hydrawise, Rain Bird, B-hyve) allow third parties to create or modify watering schedules via API. The APIs are designed for monitoring and manual zone activation, not for external scheduling systems.

What Rachio's API does support (closest to useful):

• Read complete zone configurations (soil type, crop type, nozzle, slope, shade)
• Read existing schedule rules and their zone-duration pairs
• Adjust seasonal adjustment factor (-100% to +100%) -- this is the most promising write capability
• Set soil moisture levels per zone (mm or %)
• Start/stop zones manually with custom duration
• Skip upcoming scheduled runs
• Receive webhook notifications for run events

What it does NOT support:

• Creating new schedule rules
• Modifying zone runtime durations within existing schedules
• Changing zone configuration parameters (soil type, crop type, etc.)
• Setting water budgets or allowances

Rachio's seasonal adjustment is the key lever. If SimplyScapes calculates that a zone needs 20% more water this week (based on ET data and plant factors), the API's seasonal adjustment endpoint could increase the existing schedule's output by that percentage. This is a coarse adjustment (applies to all zones uniformly or per-zone if the API supports it) but it's a viable integration path.

5.3 OpenSprinkler: The Open-Source Path

OpenSprinkler stands out as the only controller with full programmatic schedule control:

• Full schedule push capability: Third parties can create, modify, and delete programs and schedules
• Open-source firmware: ESP8266-based, hackable, community-supported
• REST API: Documented, no rate limits for local access
• Integration ecosystem: Home Assistant, MQTT, IFTTT
• Hardware: ~$180 for 8-zone AC model, expandable to 48+ zones
• Market position: Niche (enthusiast/maker market), not mainstream consumer

Relevance for SimplyScapes: OpenSprinkler could serve as a reference integration to prove the concept (full schedule push) while the major controller manufacturers remain closed. It demonstrates the technical feasibility of the integration pattern even if the addressable market is small.

Source: OpenSprinkler Product Page | OpenSprinkler Firmware GitHub

5.4 Home Assistant as an Integration Bridge

Home Assistant is a popular open-source home automation platform with native irrigation controller integrations and a concept directly relevant to SimplyScapes:

HAsmartirrigation (Smart Irrigation custom component):

• Open-source Home Assistant component that calculates daily irrigation needs based on ET data
• Uses weather data to compute reference ET and adjusts watering schedules
• Supports precipitation and soil moisture input
• Can control any Home Assistant-integrated controller (Rachio, Hydrawise, Rain Bird, OpenSprinkler)

Irrigation Unlimited:

• More complex scheduling component supporting multi-zone, time-based, sun-event-based schedules
• Supports sequential and concurrent zone operation
• Daily, weekly, monthly, or interval-based schedules

Pattern for SimplyScapes: Home Assistant demonstrates that the middleware pattern works -- a scheduling brain (HA) sits between the intelligence layer (weather/ET) and the hardware layer (controller). SimplyScapes would occupy the same position but with deeper plant-specific intelligence. Users who already run Home Assistant could be an early-adopter audience.

Source: HAsmartirrigation GitHub | Irrigation Unlimited GitHub

5.5 Controller Manufacturer Incentive Analysis

Would controller manufacturers be motivated to partner with SimplyScapes or open their APIs further?

| Factor | Pro-Partnership | Anti-Partnership | |--------|----------------|-----------------| | Market expansion | SimplyScapes brings design-time users who haven't bought controllers yet | SimplyScapes could steer users to any brand | | Data value | Plant-level data enhances their weather-based scheduling | SimplyScapes' intelligence layer could make their scheduling obsolete | | Customer retention | Deeper integration = stickier customers | Depends on SimplyScapes, creating dependency | | Competitive dynamics | First controller to integrate gets a referral channel | Others may see it as threat to differentiation | | MWELO compliance | SimplyScapes solves a problem controllers can't (per-plant budgeting) | May not prioritize compliance tools for consumer products |

Assessment: Rachio is the most likely partner -- their API is the most open, they serve a tech-forward audience, and their Flex Daily algorithm already uses ET-based calculations that would benefit from plant-level intelligence. The integration path (seasonal adjustment API + webhook events) exists today without requiring a formal partnership.

Hunter/Hydrawise is less likely due to the "personal use only" API restriction, but their professional market focus aligns with SimplyScapes' landscaper audience.

5.6 Recommended Integration Strategy

Phase 1 (MVP): Recommendation-only (no controller integration)

• System generates per-plant watering schedules as recommendations
• User sees: "Run Zone 3 for 45 minutes, 3x/week" and manually programs their controller
• Generates printable schedule cards or calendar exports (.ics)
• Value: works with ANY controller (including non-smart timers)
• Timeline: Ships with MVP

Phase 2: Read-only integration (Rachio first)

• Connect to user's Rachio via API key
• Read zone configuration to auto-map SimplyScapes hydrozones to controller zones
• Display actual run data alongside recommended schedules ("Your controller ran 30 min; we recommend 45 min")
• Use webhooks to track actual watering events
• Timeline: 1-2 months after MVP

Phase 3: Seasonal adjustment push (Rachio)

• Calculate optimal seasonal adjustment percentage based on ET data and plant factors
• Push seasonal adjustment to Rachio via API (the one write operation supported)
• User approves the adjustment: "SimplyScapes recommends increasing your watering by 15% this week based on the heat wave. Apply?"
• Timeline: Quarter after Phase 2

Phase 4: Full schedule push (OpenSprinkler first, then partnerships)

• For OpenSprinkler users: full schedule generation and push
• For major brands: pursue API partnerships based on Phase 2-3 traction data
• Alternative: explore IFTTT/Zapier as indirect write paths
• Timeline: 6-12 months post-MVP

Key principle: Don't let controller integration block the MVP. The system is valuable as a recommendation engine even without pushing schedules. Controller integration is an enhancement that deepens the value proposition over time.

Topic 5 Sources

| # | Type | Reference | URL | |---|------|-----------|-----| | 1 | API | Rachio Public API Documentation | https://rachio.readme.io/ | | 2 | API | Rachio API Data Objects Reference | https://rachio.readme.io/reference/data-objects | | 3 | Support | Rachio Public API Documentation (Support) | https://support.rachio.com/en_us/public-api-documentation-S1UydL1Fv | | 4 | API | Hydrawise REST API v1.5 (PDF) | https://www.hunterirrigation.com/sites/default/files/2024-03/Hydrawise%20REST%20API.pdf | | 5 | Support | Hydrawise API Information (Hunter) | https://www.hunterirrigation.com/en-metric/support/hydrawise-api-information | | 6 | Integration | Rain Bird -- Home Assistant Integration | https://www.home-assistant.io/integrations/rainbird/ | | 7 | Code | B-hyve Unofficial API (Node.js) | https://github.com/billchurch/bhyve-api | | 8 | Code | B-hyve Home Assistant Integration | https://github.com/sebr/bhyve-home-assistant | | 9 | Product | OpenSprinkler -- Open Source Irrigation Controller | https://opensprinkler.com/product/opensprinkler/ | | 10 | Code | OpenSprinkler Firmware (GitHub) | https://github.com/OpenSprinkler | | 11 | Code | HAsmartirrigation -- Smart Irrigation for Home Assistant | https://github.com/jeroenterheerdt/HAsmartirrigation | | 12 | Code | Irrigation Unlimited -- HA Irrigation Controller | https://github.com/rgc99/irrigation_unlimited | | 13 | Integration | Rachio -- Home Assistant Integration | https://www.home-assistant.io/integrations/rachio/ | | 14 | Integration | Hydrawise -- Home Assistant Integration | https://www.home-assistant.io/integrations/hydrawise/ | | 15 | API | Rachio Public API v2.0 (Postman) | https://www.postman.com/rachio/rachio-public-workspace/documentation/y85j8lw/rachio-public-api-v2-0 |

---

Part III: Market Landscape

Detailed sub-reports: The full competitive analyses, patent landscape, and adjacent market research are in companion files. This section synthesizes key findings.

• Vertical Competitors 1-5 — Rachio, Hydrawise, Rain Bird, B-hyve, Netafim GrowSphere
• Vertical Competitors 6-10 — Weathermatic, WeatherTRAK, Baseline/Calsense, ETwater/Jain, WaterWonk
• Patent Landscape & FTO — 20 patents, 5 competitor portfolios, FTO assessment
• Adjacent Markets & Academic Scan — 6 adjacent industries, 14 academic papers, 15 open-source tools

7. Market Overview

How the market currently handles plant-specific irrigation: it doesn't.

Every irrigation product on the market today — consumer, professional, commercial, and agricultural — operates at the zone level. A zone is a set of plants controlled by a single valve. All plants in a zone get the same watering schedule regardless of species, size, maturity, or water requirements. The only product that approaches lifecycle-stage awareness is Netafim GrowSphere's Crop Advisor, which adapts irrigation to a crop's growth stage — but only for agricultural monocultures (coffee, cotton, potatoes), at enterprise pricing ($2,000+ hardware + annual subscription), with no landscape plant models.

The gap between zone-level scheduling and per-plant intelligence is the defining whitespace in this market.

Scheduling approaches across the landscape:

| Approach | Products | How It Works | |----------|----------|-------------| | ET-based soil moisture depletion | Rachio Flex Daily, B-hyve WeatherSense, Hydrawise Smart Mode | Tracks a virtual soil moisture balance per zone. Waters when depletion exceeds a threshold (MAD). The most scientifically rigorous consumer approach | | ET-based runtime adjustment | WeatherTRAK, Weathermatic, ETwater | Calculates daily ET and adjusts runtime proportionally. May or may not maintain a soil balance model | | Weather-adjusted duration scaling | Rain Bird ARC/ST series | User sets peak-season max runtime; controller scales down based on weather. Not a true ET model | | Crop model + sensor fusion | Netafim GrowSphere Crop Advisor | Daily model refresh using soil sensor data + weather + growth-stage-aware crop parameters. Agricultural only | | Static lookup | WaterWonk | WUCOLS plant factor lookup tool for professionals. Returns a category (VL/L/M/H), not a schedule |

Market maturity: Growing — ET-based scheduling is established in consumer smart controllers, but intelligence depth is shallow. The concept of per-plant scheduling is discussed in forums and reviews but doesn't exist in any product.

Customer satisfaction: Underserved — Users across all platforms consistently complain about the zone-level constraint, opaque algorithms, and inability to handle mixed-species plantings. Professional landscapers want species-level data in the field but have no tools beyond the now-outdated WaterWonk.

8. Vertical Market Analysis

Ten competitors were analyzed across consumer, professional, commercial, and agricultural segments. The full teardown for each product is in the companion reports. Key findings by product:

Consumer Smart Controllers

Rachio — The most technically sophisticated consumer platform. Flex Daily uses FAO-56 ET with configurable Kc, root depth, AWC, and MAD per zone. Public REST API (1,700 calls/day) with zone moisture control makes Rachio the strongest integration target. No subscription, ~$200 hardware. Key gap: No per-plant awareness, no lifecycle modeling, drip zones treated identically to spray zones.

B-hyve (Orbit) — Proves ET-based scheduling can ship at sub-$100 with zero subscription. Genuine soil moisture depletion model with configurable Kc, MAD, FC, PWP. Recognizes drip at 95% efficiency. Key gap: No public API (reverse-engineered WebSocket only), app stability issues, no per-plant intelligence.

Rain Bird — Largest global installed base but weakest consumer smart scheduling. ARC8/ST8 use weather-adjusted duration scaling (not true ET). CirrusPRO's volume-based "watering by rotations" concept (golf only) is conceptually interesting. Key gap: Algorithm described as "dumbed down" by reviewers, no public API, WiFi module range issues.

Hunter Hydrawise — Differentiates with flow monitoring hardware (HC Flow Meter) and professional-grade two-wire decoder systems scaling to 54 stations. Three watering modes. Key gap: Subscription-gated features, more restrictive API than Rachio (30 calls/5 min), coarse plant categories.

Commercial/Professional Platforms

Weathermatic SmartLink — Making a smart horizontal play with SmartLink Connect (managing other brands' controllers). Subscription model ($18-50/mo) includes hardware, lifetime warranty, and upgrades. 38% average water savings across 500,000+ units. Key gap: Zone-level only, no WUCOLS integration, no establishment awareness.

HydroPoint WeatherTRAK — Most scientifically rigorous ET approach (Penman-Monteith, proprietary ET Everywhere data, soil depletion tracking). Perfect SWAT score. Key gap: Compliance tools stop at water window restrictions — no MWELO water budgets. Mobile app quality complaints.

Baseline/Calsense — Deepest municipal and water district relationships. Calsense's IMaaS model (no capex, fixed annual fee for 10 years) is the most relevant business model insight for institutional sales. Announced seven-stage AI roadmap. Key gap: Zone-level only, no plant database, AI roadmap is early.

ETwater/Jain Logic — Most aggressive AI/ML claims (predictive scheduling, hourly adjustments, "billions of data points"). Parent company Jain is a major drip manufacturer but has NOT connected their emitter catalog to their scheduling intelligence. Key gap: Technology is opaque, recent public updates sparse, no emitter-schedule integration.

Specialized Tools

WaterWonk — Validates demand signal: professionals need species-level WUCOLS data in the field. But explicitly marked as outdated (January 2025), effectively unmaintained, provides raw data lookup only. Key gap: The entire gap between "look up a plant factor" and "generate a complete per-plant irrigation plan" is the SimplyScapes opportunity.

Netafim GrowSphere — Conceptual North Star. Crop Advisor's three-source data fusion (sensor + hydraulic + crop model), lifecycle-stage-aware scheduling, and field-validated models demonstrate the architecture needed. Key gap: Agricultural only, enterprise pricing, closed ecosystem, no landscape plant models.

Competitive Matrix Summary

| Capability | Rachio | Hydrawise | Rain Bird | B-hyve | Weathermatic | WeatherTRAK | Baseline | ETwater | WaterWonk | GrowSphere | |------------|--------|-----------|-----------|--------|-------------|-------------|----------|---------|-----------|------------| | ET-based scheduling | ✅ | ✅ | ❌ (consumer) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | | Per-plant intelligence | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ (per-crop block) | | Species-level plant data | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ (lookup only) | ❌ | | Lifecycle awareness | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ (ag crops) | | Drip-specific intelligence | ❌ | ❌ | ❌ | ⚠️ (efficiency only) | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | | Emitter auto-selection | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | | MWELO compliance | ❌ | ❌ | ❌ | ❌ | ❌ | ⚠️ (water windows) | ⚠️ (reporting) | ⚠️ | ❌ | ❌ | | Public API | ✅ (best) | ✅ (limited) | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | N/A | ❌ |

Vertical market patterns:

1. ET-based scheduling is table stakes for professional and consumer smart controllers, but implementation depth varies dramatically (Rachio's full soil moisture model vs. Rain Bird's duration scaling)
2. Every platform uses broad plant type categories (turf, shrubs, trees, flowers) — none use botanical species identification or WUCOLS plant factors
3. Controller manufacturers think hardware-first — they optimize scheduling around what their hardware can deliver, not what plants actually need
4. Subscription models are split — consumer platforms are moving to no-subscription (Rachio, B-hyve), while commercial platforms charge monthly (Weathermatic, WeatherTRAK)
5. No product connects irrigation design to ongoing management — the design tools (IRRICAD, SimplyScapes) and the controllers live in separate worlds

Vertical market gaps (every product is missing these):

1. Species-level plant water knowledge embedded in the scheduling engine
2. Establishment-to-mature lifecycle management
3. Drip emitter auto-selection based on plant water requirements
4. Per-plant water budget calculation for MWELO compliance
5. Design-time irrigation intelligence (before installation, not after)

9. Adjacent Market Patterns

Six adjacent markets were analyzed for transferable patterns. Full analysis in the companion report.

Netafim GrowSphere / CropX — Agricultural Per-Crop Lifecycle Irrigation

Transferable pattern: Lifecycle-stage-aware irrigation scheduling built on decades of agronomic knowledge. GrowSphere's Crop Advisor runs nightly recalculations using weather + soil + growth-stage parameters. Landscape adaptation: WUCOLS plant factors + university extension establishment schedules serve as the landscape equivalent of Netafim's crop knowledge base. Doesn't transfer: Monoculture assumption, sensor dependency, precise growth-stage definitions.

Smart Building HVAC — Per-Zone Optimization with Individual Load Profiles

Transferable pattern: Managing individual thermal load profiles (different rooms, different heat needs) through shared HVAC infrastructure is structurally identical to managing individual plant water needs through shared irrigation zones. Model Predictive Control (MPC) — using weather forecasts to pre-optimize schedules — translates directly. Doesn't transfer: Real-time feedback loops (no thermostat equivalent per plant), reversibility of errors.

Precision Viticulture — Per-Vine Monitoring and Stress-Target Management

Transferable pattern: Fruition Sciences' block-to-vine data hierarchy maps to property > zone > plant. The stress-target management concept — targeting specific water stress levels rather than maximum water delivery — is a paradigm shift worth adopting. 65% water savings demonstrated. Doesn't transfer: Economics of per-plant sensor hardware, monoculture simplification.

AeroGarden / GrowAI — Sensor-Free Growth-Stage Adaptive Delivery

Transferable pattern: GrowAI validates that water/nutrient delivery can adapt to growth stage using time-based models rather than root-zone sensors. Pre-programmed per-species knowledge base (seed pod parameters) is directly analogous to WUCOLS plant factors. Doesn't transfer: Controlled indoor environment, hydroponic medium uniformity.

John Deere Operations Center / Climate FieldView — Landscape Digital Twins

Transferable pattern: Multi-layer data overlay (satellite + soil + weather + historical yield) maps to a landscape overlay of species data + ET + soil type + irrigation history. Variable-rate prescriptions (different treatment per management zone) map to per-plant watering prescriptions. Doesn't transfer: ISOBUS equipment integration, satellite resolution for individual plants.

Robin Autopilot — Per-Property Digital Modeling for Service Companies

Transferable pattern: Validates per-property digital modeling for residential landscapes and the RaaS/SaaS business model. Fleet Console architecture (monitoring, alerts, crew routing across hundreds of properties) is the exact operational model needed for multi-property irrigation management. Doesn't transfer: Physical robot presence for mapping, binary success metric.

Cross-industry insight: No adjacent market has solved the problem of managing diverse, heterogeneous organisms in an uncontrolled outdoor environment without sensors. Agriculture assumes monoculture; HVAC has thermostats in every room; viticulture manages one species; indoor growing is a controlled environment. Per-plant irrigation intelligence for diverse outdoor landscapes is genuinely novel.

10. Patent & IP Findings

Full patent landscape analysis in the companion report. 20 patents analyzed across 8 search term combinations, 5 competitor portfolios reviewed.

Overall patent risk: Low Freedom to operate: Favorable for software-only recommendation system

Key Patents

| # | Patent | Title | Assignee | Filed | FTO Risk | Notes | |---|--------|-------|----------|-------|----------|-------| | 1 | US10028454B2 | Environmental Services Platform | Husqvarna (ET Water) | 2015 | MODERATE | Cloud platform using plant databases + ET for scheduling. Closest prior art. Claims appear tied to complete system with hardware integration. Requires patent counsel review | | 2 | US8948921B2 | Smart irrigation system | Husqvarna (ET Water) | 2011 | Low | Data model includes per-plant parameters. Claims require hardware "smart controller converter" device | | 3 | US20200037520A1 | Dynamically increasing plant root depth | Rachio | 2019 | Low-Moderate | Overlaps with establishment/tapering concept. Claims require physical controller + sensors | | 4 | US8209061B2 | Computer-operated landscape irrigation | Toro | 2006 | Low | Software-based scheduling with ET. Expires August 2026 | | 5 | US11160220B2 | Smart drip irrigation emitter | Rain Bird | 2019 | None | Purely hardware (embedded electronics in emitters) |

Competitor IP Summary

| Company | Patent Focus | Risk Level | |---------|-------------|------------| | Rachio | Controller hardware + software (closed-loop) | Low | | Hunter | Controller hardware, water budgeting (temp-based, NOT ET) | None | | Toro | Integrated irrigation/lighting software (key patent expires Aug 2026) | Low | | Rain Bird | Smart emitter hardware, IoT sensor networks | None | | Netafim | Drip hardware (emitters, dripline, pressure compensation) | None | | Husqvarna/ET Water | Cloud-based irrigation platforms | Moderate |

FTO Advantages (Software-Only Architecture)

1. No hardware = no infringement on the vast majority of irrigation patent claims
2. All data sources are public domain (WUCOLS from UC Davis, Open-Meteo free API, manufacturer catalogs public, MWELO formula is state regulation)
3. Extensive prior art for the plant factors × ET approach (documented since at least 2000)
4. Establishment tapering is published university science (UF/IFAS, AMWUA)
5. Abandoned US20020014539A1 (filed 2000) explicitly describes plant factors of 0.3/0.5/0.8 × ET for per-species scheduling, establishing this approach as prior art

Whitespace (Unpatented Opportunities)

1. WUCOLS-based automated scheduling — No patent references WUCOLS as a data source
2. Emitter product database for automated selection — All emitter patents are hardware designs
3. Design-time irrigation intelligence — No patent covers generating per-plant specs at design phase
4. Lifecycle-aware sensor-free recommendations — No patent covers sensor-free multi-year lifecycle management
5. MWELO compliance report generation — No patent covers automated MWELO water budget documentation
6. Landscape irrigation digital twin — All digital twin patents are industrial; no landscape-specific patents exist

Defensive publications found: None on TDCommons related to irrigation scheduling. This is an opportunity to file a defensive publication.

Recommendation: Engage patent counsel to review US10028454B2 independent claims against the SimplyScapes architecture. Consider filing a defensive publication on TDCommons and a provisional patent application covering the whitespace areas.

11. Academic & Open Source

Full scan in the companion report. 14 academic papers, 7 USDA NIFA projects, and 15 open-source tools identified.

Key Academic Findings

| Paper | Key Finding | Relevance | |-------|-------------|-----------| | Litvak et al. (2017), Water Resources Research | Turfgrass = 70% of urban vegetation ET; 54% of residential water goes to irrigation | Validates the scale of the water use problem | | Three-layer urban ET model (2024), Urban Forestry & Urban Greening | Proposed overstory/understory/ground cover ET model for mixed plantings | Directly supports per-plant approach over zone averages | | Ornamental deficit irrigation (2019), Agricultural Water Management | Different ornamental species respond differently to deficit irrigation | Validates per-species water factors | | Factor-based water demand comparison (2014), Ecological Engineering | Significant variation between WUCOLS, MWELO landscape coefficient, and UC methods | SimplyScapes should use full MWELO KL (Ks × Kd × Kmc), not raw WUCOLS alone | | ASCE irrigation scheduling review (2020) | ET/water balance is one of four valid methods; integrated approaches perform best | Confirms ET approach validity; combining methods adds value |

Key Academic Gaps (Innovation Opportunity)

1. No published per-plant scheduling model for diverse landscapes (agricultural per-crop exists, landscape per-plant doesn't)
2. Limited ornamental growth rate databases — ANSI Z60.1 and VT canopy database exist but are fragmented
3. WUCOLS is California-centric — no equivalent national database (SLIDE Rules provide fallback but with less species specificity)
4. Urban microclimate effects (Kmc) poorly quantified — limited empirical backing for defaults
5. Establishment science fragmented by region — no unified national resource

Key Open Source Tools

| Tool | What It Does | Relevance | |------|-------------|-----------| | HAsmartirrigation | Home Assistant ET-based irrigation scheduling per zone | Closest OSS implementation to zone-level ET scheduling | | RefET (WSWUP) | Python ASCE reference ET calculations | Reference implementation for ET backend | | OpenET | Satellite-based ET at 30m resolution, 48 states | ET data source complement to Open-Meteo | | EPA WaterSense Water Budget Tool | Excel-based landscape water budget calculator | Reference for compliance-grade output format |

---

Part IV: Synthesis

Opportunity Map

Validated Patterns (safe to build on)

1. ET-based water balance scheduling — Used by Rachio, Hydrawise, B-hyve, WeatherTRAK, Weathermatic, ETwater. Well-established science (FAO-56). No IP barriers. This is table stakes.

2. WUCOLS plant factors as species-level water coefficients — Published public-domain data from UC Davis. 4,100+ taxa. Referenced in MWELO regulations. No patent mentions WUCOLS by name.

3. MWELO landscape coefficient formula (ETL = ETo × Ks × Kd × Kmc) — California state regulation. Government-published formula. Used by water districts statewide. Cannot be patented.

4. Establishment tapering schedules — Published by UF/IFAS, AMWUA, and multiple state extension services. The Gilman model (months/inch caliper × USDA zone) provides a parameterized framework. Cited in abandoned US20020014539A1 (2000).

5. Emitter sizing by plant water demand — Published in manufacturer design guides (Netafim Techline, Hunter selection guide, Toro dripline guide) and extension publications. Standard irrigation design practice.

Differentiation Opportunities (where to innovate)

1. Per-plant scheduling engine combining WUCOLS + ET + emitter database

   • Market gap: No product combines species-level plant data with weather-adjusted ET and emitter-specific delivery calculations
   • Inspiration: Netafim Crop Advisor's three-source data fusion (plant model + weather + system data)
   • Patent risk: Low — WUCOLS is public data, ET formulas are published science, emitter specs are public
   • Why it's different: Operates at the individual plant level, not zone level; design-time, not post-installation

2. Lifecycle-aware irrigation management without sensors

   • Market gap: Only GrowSphere has lifecycle awareness, and it requires hardware sensors + agricultural crops
   • Inspiration: AeroGarden GrowAI (sensor-free growth-stage adaptation using time-based models)
   • Patent risk: Low — Establishment schedules are published science; time-based phase transitions don't require sensors
   • Why it's different: First sensor-free lifecycle management for landscape plants, covering establishment → growth → maturity

3. Design-to-management bridge

   • Market gap: Design tools (IRRICAD, SimplyScapes) and management tools (Rachio, Hydrawise) live in separate worlds
   • Inspiration: Climate FieldView's prescription-to-execution pipeline (design → variable-rate application)
   • Patent risk: Low — No patent covers generating irrigation specs at design time
   • Why it's different: Irrigation intelligence begins when the user places a plant in the design, not after installation

4. MWELO compliance documentation generator

   • Market gap: No product auto-generates the Landscape Documentation Package (water budget, hydrozone map, irrigation schedule) from a per-plant design
   • Inspiration: Baseline/Calsense's municipal reporting and WeatherTRAK's compliance features
   • Patent risk: None — MWELO is government regulation; compliance reporting can't be patented
   • Why it's different: Compliance becomes a byproduct of good design, not a separate manual exercise

5. Landscape digital twin

   • Market gap: No landscape-specific digital twin exists; all digital twin patents are industrial
   • Inspiration: FieldView's field-level digital twins with multi-layer data overlay
   • Patent risk: Low — Novel application of digital twin concept to landscape irrigation
   • Why it's different: A living model of the landscape that evolves with plant growth, weather, and usage data

Caution Zones (promising but constrained)

1. Direct controller schedule push — Rachio's API allows zone moisture control and seasonal adjustment, but no controller supports true per-plant schedule push. The 4-phase integration strategy (recommend → read → adjust → push) manages this constraint progressively. Alternative: OpenSprinkler for full schedule control.

2. Cloud-based plant database + ET scheduling platform — US10028454B2 (Husqvarna/ET Water) claims are potentially relevant but appear tied to the complete ET Water system architecture. Engage patent counsel before building a cloud-based scheduling product that directly controls hardware. MVP as recommendation-only (no controller integration) largely sidesteps this risk.

3. Growth rate prediction for ornamental plants — Limited data exists. VT canopy database covers 336 species with 10/20-year projections; ANSI Z60.1 provides nursery sizing standards. But comprehensive ornamental growth modeling doesn't exist in literature. This will require building incrementally from available data.

The Technical Landscape

The MVP can be built entirely from public-domain data and published science:

| Component | Data Source | Status | |-----------|-----------|--------| | Plant water requirements | WUCOLS V (4,100+ taxa, UC Davis) | Available, exportable to CSV | | National fallback plant factors | SLIDE Rules (ANSI/ASABE S623.1) | Published standard | | Reference ET | Open-Meteo API (free, global, no key) | Available, FAO-56 PM | | Compliance ET (CA) | CIMIS API (free registration) | Available, ground-station data | | Soil data | SSURGO via SDA REST API (USDA) | Available, national coverage | | Emitter product catalog | Manufacturer spec sheets (Hunter, Rain Bird, Netafim, Toro, Jain) | Public, requires periodic updates | | Establishment schedules | UF/IFAS, AMWUA, state extension services | Published, region-specific | | MWELO formula | CA DWR official regulation (Jan 2025 update) | Published government formula | | Growth rate data | VT canopy database (336 species), ANSI Z60.1 | Partial — largest gap |

Key technical challenges:

1. WUCOLS-to-SimplyScapes mapping — WUCOLS has 4,100+ taxa; SimplyScapes has 2,500+ species. Mapping botanical names (with synonym handling) is the critical data engineering task.

2. Plant factor precision — WUCOLS provides categories (VL/L/M/H) with ranges, not point estimates. Using midpoints (0.1/0.2/0.5/0.8) per MWELO convention is adequate for v1 but could be refined with local observation data over time.

3. National coverage — WUCOLS covers 6 California regions. For national coverage, the SLIDE Rules provide plant-type-level factors (trees, shrubs, groundcovers, mixed) that can serve as fallback outside California.

4. Emitter database maintenance — Manufacturer product lines change. An MVP set of ~20 core emitter SKUs covers 80% of residential drip scenarios. Full catalog is a maintenance commitment.

5. Controller integration constraints — No major controller supports per-plant schedule push. The recommended 4-phase integration strategy starts with recommendation-only and progressively deepens integration.

Open Questions

• [ ] How many of SimplyScapes' 2,500+ species can be matched to WUCOLS V entries? What's the actual coverage gap after synonym resolution?
• [ ] What's the accuracy of Open-Meteo ET0 vs. CIMIS ground-station data for MWELO compliance purposes? Has any water district explicitly rejected non-CIMIS ET sources?
• [ ] How much ornamental growth rate data can be extracted from the VT canopy database (336 species) and ANSI Z60.1? Is this sufficient for a v1 growth model?
• [ ] What are the independent claims of US10028454B2 (Husqvarna/ET Water) and do they cover a recommendation-only platform without controller hardware integration?
• [ ] Would Rachio be interested in a partnership where SimplyScapes provides per-plant intelligence that feeds into their API? What's the right business development approach?
• [ ] How do water districts outside California handle landscape water budget requirements? Are there emerging equivalents to MWELO in other states?
• [ ] Can the establishment tapering model (Gilman formula + regional schedules) be validated against actual field outcomes? What feedback loops would improve accuracy over time?
• [ ] Is there a path to build ornamental plant growth models incrementally from user-reported observations (crowdsourced plant growth data)?

Opportunity Assessment

Novelty: Very High — No product, patent, or academic publication describes a system that combines WUCOLS species-level plant factors + weather API ET + emitter product database + establishment lifecycle management to generate per-plant irrigation recommendations at design time. Each component exists individually; the combination and application to landscape (not agriculture) is genuinely new.

Feasibility: High — All data sources are public and accessible. The core algorithms (MWELO landscape coefficient, ET-based water balance, emitter sizing) are published science. The main engineering challenge is data mapping (WUCOLS → SimplyScapes plant library) and product UX, not algorithmic invention. SimplyScapes' existing plant library, irrigation engine, and manufacturer catalogs provide a substantial head start.

Impact: High — Addresses a $2B+ residential irrigation market where 54% of household water goes to landscapes, most of it wasted. Serves all four SimplyScapes customer segments: professionals (design-time efficiency), homeowners (easy setup), water districts (MWELO compliance), and educators (learning tool). Creates a lifecycle relationship (design → install → manage → maintain) that transforms SimplyScapes from a design tool into a management platform.

Timeline:

• MVP (design-time emitter auto-placement + water budget): 2-3 months — WUCOLS mapping + emitter database + per-plant calculation in the design tool
• V2 (establishment schedules + ongoing recommendations): 3-6 months — Add lifecycle management and week-by-week schedules
• V3 (controller integration): 6-12 months — Rachio API integration for read/adjust, OpenSprinkler for full push
• V4 (compliance reporting + digital twin): 12-18 months — MWELO documentation generation, landscape digital twin with growth tracking

---

Recommended Next Steps

1. Run /ss-product spec to define the technical specification — Focus on MVP scope: WUCOLS mapping, emitter auto-selection, per-plant water budget calculation
2. Engage patent counsel to review US10028454B2 — The one patent that needs professional FTO analysis
3. Run /ss-legal disclosure for defensive publication — File on TDCommons covering the WUCOLS + ET + emitter + lifecycle combination
4. Begin WUCOLS data mapping — Download WUCOLS V export, map to SimplyScapes plant library, quantify the coverage gap
5. Build MVP emitter product database — Core ~20 SKUs across Hunter, Rain Bird, Netafim covering the 4 residential drip scenarios (point source, multi-outlet, inline dripline, bubbler)
6. Contact Rachio developer relations — Explore partnership potential for per-plant intelligence feeding into their API

---

Sources

<!-- Comprehensive source table covering all sections. Sources from Part II topics are in their respective topic-level source tables above. These are Part III/IV sources. -->

| # | Type | Reference | URL | |---|------|-----------|-----| | 1 | Product | Rachio Flex Daily / Public API | https://rachio.readme.io/ | | 2 | Product | Hunter Hydrawise REST API | https://www.hunterirrigation.com/sites/default/files/2024-03/Hydrawise%20REST%20API.pdf | | 3 | Product | Rain Bird ARC Series | https://www.rainbird.com/products/arc-series-smart-irrigation-controllers | | 4 | Product | B-hyve Smart Watering Advanced Settings | https://support.orbitonline.com/en/b-hyve-smart-indoor-outdoor-irrigation-controller/Smart-Watering-Advanced-Settings-6df2 | | 5 | Product | Netafim GrowSphere Crop Advisor | https://www.netafim.com/en/digital-farming/crop-advisor/ | | 6 | Product | Weathermatic SmartLink | https://www.weathermatic.com/smartlink | | 7 | Product | HydroPoint WeatherTRAK | https://www.hydropoint.com/ | | 8 | Product | Baseline (Calsense) | https://www.calsense.com/ | | 9 | Product | ETwater / Jain Logic | https://etwater.com/ | | 10 | Tool | WaterWonk | https://waterwonk.us/ | | 11 | Patent | US10028454B2 — Environmental Services Platform | https://patents.google.com/patent/US10028454B2/en | | 12 | Patent | US8948921B2 — Smart irrigation system | https://patents.google.com/patent/US8948921B2/en | | 13 | Patent | US20200037520A1 — Root depth training | https://patents.google.com/patent/US20200037520A1/en | | 14 | Patent | US8209061B2 — Computer-operated landscape irrigation (Toro) | https://patents.google.com/patent/US8209061B2/en | | 15 | Patent | US20020014539A1 — Per-species irrigation (abandoned, prior art) | https://patents.google.com/patent/US20020014539A1/en | | 16 | Journal | Litvak et al. (2017) — Urban landscape ET in LA | https://agupubs.onlinelibrary.wiley.com/doi/abs/10.1002/2016WR020254 | | 17 | Journal | ASCE Irrigation Scheduling Review (2020) | https://ascelibrary.org/doi/abs/10.1061/(ASCE)IR.1943-4774.0001464 | | 18 | Journal | Three-layer urban ET model (2024) | https://www.sciencedirect.com/science/article/abs/pii/S1618866724001870 | | 19 | Journal | Water demand comparison methods (2014) | https://www.sciencedirect.com/science/article/abs/pii/S0925857413001432 | | 20 | Journal | OpenET accuracy assessment (Nature Water, 2023) | https://www.nature.com/articles/s44221-023-00181-7 | | 21 | Open Source | HAsmartirrigation (Home Assistant) | https://github.com/jeroenterheerdt/HAsmartirrigation | | 22 | Open Source | RefET — Python ASCE Reference ET | https://github.com/WSWUP/RefET | | 23 | Open Source | OpenSprinkler | https://opensprinkler.com/ | | 24 | Tool | EPA WaterSense Water Budget Tool | https://www.epa.gov/watersense/water-budget-tool | | 25 | NIFA | USU Landscape Water Consumption Study | https://portal.nifa.usda.gov/web/crisprojectpages/0158215 | | 26 | Search | TDCommons Defensive Publications | https://www.tdcommons.org/dpubs_series/ | | 27 | Software | IRRICAD Irrigation Design | https://www.irricad.com/ | | 28 | Software | Toro AquaFlow Drip Design | https://driptips.toro.com/aquaflow-drip-irrigation-design-software/ |

Irrigation Technology Competitive Analysis

Date: 2026-03-01 Purpose: Competitive landscape analysis for per-plant drip irrigation intelligence system Companies analyzed: Rachio, Hunter Hydrawise, Rain Bird, B-hyve (Orbit), Netafim GrowSphere

---

Executive Summary

All five companies operate at the zone level for scheduling intelligence. None offer true per-plant irrigation optimization for residential or commercial landscape contexts. The closest analog is Netafim GrowSphere's Crop Advisor, which delivers lifecycle-stage-aware recommendations -- but only for agricultural row crops, not landscape plants. This represents a significant whitespace opportunity for a per-plant drip irrigation intelligence system.

| Company | Scheduling Granularity | Per-Plant Capability | Lifecycle Awareness | Open API | Pricing Model | |---------|----------------------|---------------------|---------------------|----------|---------------| | Rachio | Zone-level ET/soil moisture balance | None | None | Yes (REST, 1700 calls/day) | One-time hardware ($150-$230), no subscription | | Hunter Hydrawise | Zone-level ET or time-based | None | None | Yes (REST, rate-limited) | Hardware ($200-$2000+) + tiered subscriptions ($0-$60+/yr) | | Rain Bird | Zone-level seasonal adjustment | None | None | Limited/proprietary | Hardware ($100-$400+), IQ4 requires subscription | | B-hyve (Orbit) | Zone-level ET | None | None | Unofficial (reverse-engineered) | One-time hardware ($90-$120), no subscription | | Netafim GrowSphere | Field-block-level crop models | Crop-block, not per-plant | Yes (crop lifecycle stages) | Proprietary/closed | Enterprise: hardware ($2000+) + annual subscription |

---

1. Rachio

How They Approach Plant-Specific / Zone-Level Scheduling

Rachio's Flex Daily algorithm is the most technically sophisticated consumer-grade scheduling system. It uses a soil moisture depletion model that tracks a virtual soil moisture balance per zone:

• Inputs per zone: 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, irrigation efficiency
• Weather data: Real-time ET (evapotranspiration) from local weather stations, forecasted precipitation, wind, temperature, humidity
• Algorithm: Daily water balance: Soil Moisture = Previous Balance - ETc + Precipitation + Irrigation. Waters when moisture drops below the MAD threshold. ETc = ET0 x Kc (crop coefficient).

The system operates exclusively at the zone level. A zone containing mixed plantings (e.g., roses and trees on the same valve) receives a single schedule based on averaged or dominant parameters. There is no mechanism to specify individual plants within a zone.

Flex Daily modes:

• Flex Daily: Fully dynamic daily decisions per zone
• Flex Monthly: Monthly adjustment of baseline schedule
• Fixed: Static schedule with weather skip overlays

Drip irrigation support: Rachio can control drip zones, but treats them identically to spray zones in scheduling logic. Users must manually calculate precipitation rates for drip emitters (GPH converted to in/hr). No emitter-level awareness.

Strengths

• Most advanced consumer ET-based scheduling algorithm on the market
• Excellent public REST API (v2.0) with 1,700 calls/day, webhooks, zone moisture control, and third-party libraries (Python, Go, Node.js)
• API allows direct soil moisture percentage adjustment per zone (0-1 range), enabling external intelligence systems to override or augment Rachio's built-in logic
• Robust Home Assistant integration and smart home ecosystem support (Alexa, Google Assistant, IFTTT)
• No subscription fees -- all smart features included with hardware purchase
• Weather Intelligence Plus: automatic rain skip, wind skip, freeze skip, saturation skip
• Cycle & Soak to prevent runoff on slopes and clay soils
• Strong community and forum with detailed technical discussions
• Pro Series controllers for landscape contractors with multi-site management

Limitations / Gaps

• No per-plant intelligence: Scheduling operates at zone level only. Mixed-planting zones get a single averaged schedule.
• No plant lifecycle awareness: No concept of establishment period, growth stage, dormancy, or seasonal plant-specific needs beyond static crop coefficients.
• No drip-specific intelligence: Drip zones use the same scheduling model as spray zones. No awareness of emitter count, individual emitter flow rates, or plant-to-emitter mapping.
• Weather station dependency: Accuracy degrades significantly if no weather station is nearby. No on-site sensor integration (no soil moisture sensor input).
• Cloud dependency: Controller requires Rachio cloud servers to function with smart features. If Rachio shuts down, controllers lose intelligence.
• No plant database: Users must manually determine and input crop coefficients, root depths, and other parameters per zone. No built-in botanical knowledge.
• Server-side only: The only way to reach the controller is via Rachio servers; no local API.
• App ads: Users report increasing in-app product promotion.

Technical Approach

• API: Public REST API v2.0 at api.rach.io/1. Bearer token auth. Endpoints for devices, zones, schedules, weather, notifications. Zone moisture can be set programmatically. Webhook support for zone/schedule/device events.
• Algorithm: FAO-56 Penman-Monteith ET0 reference, modified by zone-specific Kc, adjusted daily using weather station data.
• Data sources: Weather Underground, National Weather Service, Davis weather stations, local airport stations. No satellite imagery or remote sensing.
• Hardware: 8/16-zone controllers. WiFi 2.4 GHz. 24VAC valve output.

Pricing Model

• Hardware: Rachio 3 8-zone: ~$200 MSRP. 16-zone: ~$230. Pro Series 6-zone: ~$180.
• Software: No subscription. All features (Flex Daily, Weather Intelligence Plus, API access) included.
• Pro program: Buy 10 Pro controllers, get 1 free.

Key Takeaway for Per-Plant Drip System

Rachio's open API and zone-level moisture control make it the most viable integration target. An external per-plant intelligence layer could use the Rachio API to: (1) read zone weather/ET data, (2) calculate per-plant needs using its own models, (3) set zone moisture levels or trigger zone runs programmatically. However, the per-plant system would still be constrained by Rachio's zone-level valve actuation -- true per-plant control would require sub-zone valve hardware that Rachio does not support. The API's 1,700 calls/day limit is sufficient for residential use but may constrain commercial deployments.

---

2. Hunter Hydrawise

How They Approach Plant-Specific / Zone-Level Scheduling

Hydrawise offers three watering modes per zone:

1. Time-Based Watering: Fixed durations with weather-trigger adjustments (temperature, rainfall, wind, predicted rainfall). Recommended for shallow-rooted plants, flowers, and vegetable gardens.
2. Smart (ET) Watering: Uses evapotranspiration data to calculate zone water needs. Determines how much water has been lost through evaporation and transpiration, then schedules irrigation to replace it. Recommended for deep-rooted plants, established lawns, shrubs, and trees.
3. Virtual Solar Sync: Mimics a solar sync sensor using weather data. Adjusts run times based on seasonal solar radiation patterns. Recommended for large root systems.

Zone configuration parameters: Zone name, zone number, watering type (time/ET/solar sync), run time, cycle & soak settings, master valve assignment.

Plant type awareness: Plant Type setting determines the fraction of reference ET required. Sun/Shade setting accounts for microclimate. However, plant type selection is coarse-grained (broad categories, not specific species).

Weather data: Uses a "Virtual Weather Station" that combines satellite data, real weather stations, atmospheric data from aircraft, and barometric pressure from mobile phones to generate localized forecasts.

Strengths

• Flow monitoring: Optional HC Flow Meter enables real-time leak detection, pipe break alerts, and zone flow verification. This is a differentiating hardware capability that most competitors lack at the consumer/prosumer level.
• Professional-grade hardware: HCC controller supports up to 54 stations via two-wire decoder (EZ-DM module), mixing conventional, decoder, and wireless outputs. Designed for commercial, municipal, and large residential sites.
• Two-wire decoder system: EZ-1 decoders support up to 3,000 ft wire runs; EZ-LR up to 6,000 ft. Simplifies large-scale installations by requiring only two wires instead of individual wire runs per valve.
• Virtual Weather Station: Proprietary multi-source weather aggregation may improve accuracy vs. single-station-dependent systems.
• Multi-platform control: Full graphical touchscreen on HCC controller + cloud app + API access.
• Professional plan ecosystem: Contractor plans for managing hundreds of controllers across client sites.

Limitations / Gaps

• Zone-level only: Like all competitors, scheduling intelligence stops at the zone boundary. No per-plant or per-emitter capability.
• No plant lifecycle modeling: No concept of establishment, growth stages, dormancy, or seasonal transitions.
• Coarse plant type categories: Plant types are broad (e.g., "lawn," "shrubs") rather than species-specific. No botanical database.
• WiFi reliability issues: Multiple user reports of flaky WiFi connectivity, requiring nightly controller reboots as a workaround.
• Weather override bugs: Users report irrigation being erroneously skipped due to inaccurate Virtual Weather Station data that cannot be disabled.
• Program limitations: Limited to 6 programs; users wanting per-zone program control (e.g., 24 programs for 24 zones) are constrained.
• Subscription-gated features: Accurate weather station selection requires the Enthusiast plan ($60/yr). Free tier uses only Hydrawise's virtual weather, which users find less reliable.
• API rate limits: 3 zone start/stop commands per 30 seconds; 30 total API calls per 5 minutes. More restrictive than Rachio.

Technical Approach

• API: REST API v1.5 over HTTPS. API key authentication per account. Endpoints for controller info, zone names/numbers, schedule status, manual zone start/stop/suspend. No zone moisture level control (unlike Rachio).
• Algorithm: ET-based for Smart watering mode. ET0 from Virtual Weather Station, modified by plant type Kc and sun/shade factors. Time-based mode uses trigger conditions rather than soil moisture balance.
• Data sources: Proprietary Virtual Weather Station (satellite, airport, personal weather stations, aircraft atmospheric, mobile barometric). Optional local sensor inputs (rain, flow).
• Hardware: HC (6-station), Pro-HC (up to 24-station), HPC (up to 48-station conventional), HCC (up to 54-station with decoder). All Hydrawise-ready.

Pricing Model

• Hardware: Pro-HC 6-station: ~$200. Pro-HC 24-station: ~$400. HCC commercial: ~$800-$2,000+.
• Home Plan (Free): Up to 3 controllers, 30-day history, basic weather.
• Enthusiast Plan ($60/yr): 5 controllers, 365-day history, 100k+ weather station access, SMS alerts, 5 user accounts.
• Contractor Plans: Tiered pricing for 75, 250, or more controllers. Pricing not publicly listed; requires sales contact.

Key Takeaway for Per-Plant Drip System

Hydrawise's flow monitoring capability is uniquely relevant -- flow data at the zone level could validate per-plant irrigation models by confirming actual water delivery. The two-wire decoder system demonstrates scalability for large installations. However, the API is more limited than Rachio's (no moisture level control, more restrictive rate limits), and the subscription model adds ongoing cost. The tight API rate limits would make real-time per-plant control via the Hydrawise API impractical without negotiating custom rate limits with Hunter.

---

3. Rain Bird

How They Approach Plant-Specific / Zone-Level Scheduling

Rain Bird takes a more traditional, program-centric approach to scheduling. Their consumer controllers (ARC series, ST8) offer:

• Three independent programs (A, B, C): Each program controls watering days, start times, and per-zone durations. Four start times per program = 12 total start times across three programs.
• Automatic Seasonal Adjust: Adjusts daily watering duration based on local postal code historical weather averages, yesterday's known weather, and tomorrow's forecast. Claims up to 30% water savings.
• Zone configuration: Plant type selection, plant density (foliage amount/spacing), soil type, slope, sun/shade.

Key distinction: Rain Bird's consumer smart controllers (ARC8, ST8) do not use ET-based scheduling like Rachio or Hydrawise. They adjust run time duration based on weather patterns rather than maintaining a soil moisture balance model. Users set maximum run times for peak season, and the controller scales down from that baseline.

Professional platforms:

• IQ4 Central Control: Cloud-based or desktop platform for commercial irrigation management. Supports batch editing across hundreds of stations, map-based system visualization, automated alarms, and runtime reports. Available as IQ4-Cloud (web-based) or IQ4-Desktop (local installation with 5-satellite base capacity).
• CirrusPRO: Golf course-specific cloud platform with precision irrigation by rotations, real-time monitoring, hybrid field control (IC, satellite, decoder systems). Not applicable to residential/commercial landscape.

Strengths

• Massive installed base: Rain Bird is the largest irrigation manufacturer globally. Enormous contractor familiarity and distribution network.
• Hardware ecosystem depth: Controllers from 4-zone residential to 200+ station commercial. Broad sensor compatibility (rain, rain/freeze, soil moisture, flow, wind).
• IQ4 commercial platform: True enterprise-grade irrigation management with BMS (Building Management System) API integration, multi-user permissions, and fleet management.
• CirrusPRO precision: Patented watering-by-rotations for golf courses eliminates precipitation rate calculations -- a concept that could inspire per-plant volume-based scheduling.
• Proven reliability: Long track record in professional irrigation. Hardware is considered robust and field-proven.
• ARC8 pricing: Entry-level smart controller at ~$140 is competitively priced.
• No subscription for consumer: ARC8 and ST8 include all smart features with hardware purchase.

Limitations / Gaps

• No true ET-based scheduling in consumer controllers: The ARC8 and ST8 use weather-adjusted durations, not soil moisture depletion models. Users report the system reducing watering inappropriately during heat waves.
• Weak smart scheduling algorithm: Reviewers consistently note Rain Bird's consumer smart features are less sophisticated than Rachio and Hydrawise. The seasonal adjustment is described as "dumbed down."
• No per-plant or species-specific intelligence: Zone-level only. Plant type selection is broad categories.
• No plant lifecycle awareness: No establishment, growth stage, or dormancy modeling.
• WiFi connectivity problems: LNK2 WiFi module has limited range. Users report needing dedicated WiFi extenders and frequent resets. The module is a separate purchase (~$70-100) for ESP-TM2 series.
• App quality issues: Users report buggy app, slow connectivity, communication errors with multiple controllers, and forced location tracking.
• Fragmented product line: Different apps and platforms for different controller families. No unified ecosystem.
• Limited public API: No official public REST API for consumer controllers. IQ4 has a BMS integration API but requires a subscription. Third-party libraries (pyrainbird) exist via reverse engineering.
• CirrusPRO is golf-only: The most advanced platform is restricted to golf course applications.

Technical Approach

• API: No official public API for consumer controllers. IQ4 BMS Integration API available with subscription for commercial installations. pyrainbird (Python) and rainbird-api (Node.js) are community reverse-engineered libraries using the controller's local network protocol.
• Algorithm: Weather-adjusted percentage scaling of user-defined max run times. Not ET-based for consumer products. IQ4 supports ET-based adjustments for commercial.
• Data sources: Local postal code weather data (historical averages + forecast). No proprietary weather aggregation.
• Hardware: ARC6/ARC8 (consumer, built-in WiFi). ESP-TM2 (professional, WiFi via LNK2 module). ESP-ME3 (expandable, up to 22 stations). ESP-LXIVM (commercial decoder). IQ4 central control.

Pricing Model

• Consumer hardware: ARC8: ~$140. ARC6: ~$110. ST8: ~$170-200.
• Professional hardware: ESP-TM2 8-station: ~$120 (controller only, WiFi module sold separately at ~$80). ESP-ME3: ~$170+.
• WiFi module: LNK2: ~$70-100 (required add-on for ESP-TM2 and ESP-ME3 series).
• IQ4: IQ4-Cloud requires subscription (pricing via sales contact). IQ4-Desktop: ~$500+ base with per-satellite expansion.
• Consumer software: No subscription for ARC and ST series.

Key Takeaway for Per-Plant Drip System

Rain Bird's massive market presence and contractor network represent both a competitive moat and a partnership opportunity. Their CirrusPRO watering-by-rotations concept (volume-based rather than time-based irrigation) is conceptually adjacent to per-plant volume delivery. However, Rain Bird's consumer smart scheduling is the weakest of the five competitors analyzed, and their lack of a public API makes integration difficult. A per-plant system would more likely compete against Rain Bird's consumer line rather than integrate with it.

---

4. B-hyve (Orbit)

How They Approach Plant-Specific / Zone-Level Scheduling

B-hyve uses a WeatherSense algorithm that combines ET-based calculations with zone-level configuration:

• Zone inputs: Soil type, plant type, sun/shade exposure, slope, sprinkler type (spray, rotor, drip)
• ET calculation: Application Rate (AR), Efficiency (E), Plant Factor (Kp/Kc -- fraction of reference ET), Microclimate Factor (Kmc)
• Soil parameters: Field Capacity (FC), Permanent Wilting Point (PWP), Basic Infiltration Rate (BIR), Management Allowed Depletion (MAD, default 50%)
• Root zone: Effective root depth (typically 50% of maximum root depth)
• Smart Watering: Automatically creates and adjusts run times based on real weather data, adjusted daily for temperature, humidity, wind, and calculated plant water needs

The algorithm is technically similar to Rachio's Flex Daily (both use ET-based soil moisture balance), but B-hyve's implementation is less configurable and less transparent to the user.

Strengths

• Lowest price point: 6-zone controller at ~$90, 12-zone at ~$105-120. Significantly undercuts Rachio and Hydrawise.
• No subscription fees: All WeatherSense smart features included with hardware purchase.
• Full ET-based scheduling: Despite the low price, B-hyve implements a genuine soil moisture depletion model with configurable parameters (Kc, MAD, FC, PWP, root depth).
• Drip irrigation efficiency setting: System recognizes drip at 95% efficiency vs. 75% for spray/rotors, indicating basic awareness of drip irrigation characteristics.
• B-hyve Pro for contractors: Separate app and dashboard for managing unlimited controllers across client sites. Includes proximity-based client lookup and remote troubleshooting.
• WaterSense and SWAT certified: May qualify for utility rebates.
• Bluetooth + WiFi: Dual connectivity means basic control works even without WiFi (via Bluetooth when physically near the controller).
• Build-your-own bundle pricing: Bundle discounts for controller + accessories.

Limitations / Gaps

• No per-plant intelligence: Zone-level only, identical to all competitors.
• No plant lifecycle awareness: Static crop coefficients; no establishment, growth, or dormancy modeling.
• No public API: No official developer API. Third-party integrations (Home Assistant) use reverse-engineered WebSocket connections to Orbit's backend servers. This makes integration fragile and unsupported.
• App stability issues: Users report crashes when setting interval watering, and smart watering sometimes overrides county water-use restrictions by running zones multiple times per day.
• Less transparency: Smart watering calculations are less visible to users than Rachio's moisture graphs and ET breakdowns.
• Limited plant type granularity: Plant types are broad categories, not species-specific.
• WebSocket-only status updates: Real-time data relies on WebSocket connection to Orbit servers, with 25-second reconnection intervals if connection drops.
• Owned by Husqvarna Water (formerly Hydro-Rain): Corporate ownership changes add uncertainty about long-term API/platform direction.

Technical Approach

• API: No official public API. Unofficial endpoints discovered through reverse engineering: Devices, Timelines, Landscapes, History. WebSocket connection for real-time status. Bearer token auth. Community implementations in Python, Node.js, and Hubitat.
• Algorithm: ET-based soil moisture balance. ETc = ET0 x Kp x Kmc. Soil moisture tracked using FC, PWP, MAD, and root zone depth. Scheduling triggers when depletion exceeds MAD threshold.
• Data sources: Weather data from Orbit's backend (sources not publicly documented). Local weather adjustments for rainfall, wind, cloud cover, freezing temperatures.
• Hardware: 4/6/8/12/16-zone controllers. WiFi 2.4 GHz + Bluetooth. Indoor/outdoor models. B-hyve XR (dual-band WiFi, color LED display).

Pricing Model

• Hardware: 4-zone indoor: ~$70. 6-zone: ~$90. 8-zone: ~$100. 12-zone indoor/outdoor: ~$105-120. B-hyve XR 8/16-zone: ~$130-150.
• Hose timers: B-hyve XD single: ~$35. Two-hose: ~$50. Four-hose: ~$80.
• Software: No subscription for any features.
• Pro: B-hyve Pro app and dashboard free for contractors; no per-controller fees.

Key Takeaway for Per-Plant Drip System

B-hyve proves that ET-based scheduling can be delivered at a sub-$100 price point with no subscription, setting a price expectation floor for consumer smart irrigation. Their drip-specific efficiency setting (95% vs. 75%) shows awareness of drip as a distinct modality, but no deeper drip-specific intelligence exists. The lack of a public API is a significant barrier to integration -- any per-plant system would need to either replace B-hyve entirely or use fragile reverse-engineered endpoints. B-hyve's market position as the budget option means a per-plant system should differentiate on intelligence depth, not compete on price.

---

5. Netafim GrowSphere

How They Approach Plant-Specific / Zone-Level Scheduling

GrowSphere is fundamentally different from the other four competitors. It is an agricultural precision irrigation operating system designed for commercial farming, not residential or commercial landscape irrigation.

Crop Advisor module is the most relevant component:

• Lifecycle-stage-aware irrigation: Crop models modify recommendations based on the crop's current growth stage. The system understands that a plant's water needs change as it moves from seedling to vegetative growth to flowering to fruit set to harvest.
• Three data source fusion: Combines (1) real-time sensor data (soil moisture, weather), (2) hydraulic system data (valve status, lateral pressure, submain flow), and (3) crop models (growth stage, crop-specific parameters).
• Crop model inputs: Climate data, soil texture, crop development stage and associated parameters, irrigation strategy, hydraulic limitations, field analysis (soil/tissue/water testing), actual irrigation amounts applied.
• Daily model updates: Models refresh at midnight, adjusting recommendations based on changing climate conditions and feedback from the field.
• Field-validated: Over 30 field trials across coffee, cotton, potatoes, onions, and other crops. Results showed higher yields with less water and nitrogen.

GrowSphere platform capabilities:

• Monitoring: Real-time soil moisture (multi-depth), weather station data, pressure sensors, hydraulic performance feedback.
• Control: Remote valve operation, automated irrigation scheduling, fertigation management (fertilizer injection into irrigation lines).
• Visualization: Interactive field maps, real-time system status, historical data and reporting.

Strengths

• Only competitor with lifecycle-stage awareness: Crop Advisor is the only system among the five that adjusts irrigation based on where a plant is in its growth cycle. This is the closest existing analog to per-plant intelligence.
• Agronomic depth: Built on 50+ years of Netafim irrigation science, developed with universities and research institutes. Crop models are field-tested, not just theoretical.
• Multi-depth soil moisture sensing: Hardware-integrated soil moisture sensors at multiple depths provide real ground-truth data, not just modeled estimates.
• Hydraulic awareness: Unique integration of hydraulic system data (pressure, flow, valve status) into irrigation decisions. Accounts for real-world system constraints.
• Fertigation integration: Combined irrigation + fertilization management is a dimension no residential competitor addresses.
• Sensor fusion architecture: The three-source data fusion (sensor + hydraulic + agronomic models) is an architectural pattern directly applicable to per-plant drip intelligence.
• Field-scale precision: Manages irrigation at the field block level with sensor-driven feedback loops.
• Future roadmap includes AI/ML: Netafim has announced plans for AI and machine learning to enhance location-specific crop modeling.

Limitations / Gaps

• Not designed for landscape plants: Crop models are built for agricultural crops (coffee, cotton, potatoes, onions, etc.), not ornamental landscape plants, turf, trees, or mixed plantings.
• No per-plant granularity: Operates at the field-block level (multiple rows of the same crop), not individual plants.
• Enterprise-only pricing: Hardware starts at $2,000+ for controllers. Annual subscription required. Not accessible to residential or small commercial landscape customers.
• Closed ecosystem: No public API documented. Proprietary controllers, sensors, and software platform. Cannot integrate with third-party irrigation hardware.
• Agricultural focus: The platform assumes monoculture or near-monoculture plantings, not the mixed-species gardens typical of residential landscapes.
• Complex setup: Requires professional installation, sensor deployment, and agronomic configuration. Not self-serve.
• Limited crop model library: While growing, the number of validated crop models is still limited to major commercial crops.
• No independent reviews: Virtually no third-party reviews, G2/Capterra/TrustRadius presence, or user community discussions found. The platform is too niche and enterprise-focused for consumer review sites.
• Connectivity requirements: Designed for agricultural field conditions, which may not align with suburban/urban landscape infrastructure.

Technical Approach

• API: No documented public API. Proprietary cloud platform (GrowSphere cloud). Flutter-based cross-platform mobile app. Integration appears limited to Netafim's own hardware ecosystem.
• Algorithm: Proprietary crop models developed by Netafim agronomists. FAO-based ET calculations modified by crop-specific growth stage parameters. Daily model refresh. Field trial validated.
• Data sources: On-site multi-depth soil moisture sensors, on-site weather stations (integrated into GrowSphere), pressure/flow sensors on irrigation infrastructure, weather forecast services, historical soil/tissue/water analysis data.
• Hardware: GrowSphere MAX controller (touchscreen, 6 expansion slots, PLC-based). GrowSphere MINI for smaller operations. Proprietary soil moisture sensors, weather stations, and pressure sensors. All hardware is Netafim-manufactured.

Pricing Model

• Hardware: GrowSphere MAX controller: estimated $2,000-5,000+ (includes touchscreen, CPU module, enclosure). Sensors: $200-1,000+ each depending on type. Weather station: $500-2,000+.
• Software: Annual subscription (pricing not publicly listed, varies by deployment size). Non-refundable, no proration for partial-year use.
• Installation: Professional installation required. Cost varies by system complexity.
• Smallholder version: Netafim announced a lower-cost version targeting smallholder farmers in Asia for Q2 2026, using phone/tablet control with reduced sensor requirements.

Key Takeaway for Per-Plant Drip System

GrowSphere's Crop Advisor is the conceptual North Star for a per-plant system. Its three-source data fusion (sensor + hydraulic + agronomic model), lifecycle-stage-aware scheduling, and field-validated crop models demonstrate the architecture needed for per-plant intelligence. The key opportunity is to bring this agricultural-grade approach down to landscape irrigation: (1) build plant models for ornamental species, not just crops, (2) operate at per-plant granularity instead of field-block, (3) price for residential/commercial landscape rather than enterprise agriculture, and (4) integrate with existing consumer controllers (Rachio) rather than requiring proprietary hardware. Netafim's announced AI/ML roadmap signals that even agriculture is moving toward more adaptive, data-driven models -- a per-plant landscape system should plan for this from the start.

---

Cross-Cutting User Pain Points (from G2, Capterra, forums, review sites)

Universal Complaints Across All Platforms

1. WiFi connectivity problems -- Every single platform has significant user complaints about WiFi reliability. This is a hardware/infrastructure problem, not software.
2. Weather data inaccuracy -- Users across Rachio, Hydrawise, and B-hyve report smart scheduling making poor decisions due to incorrect local weather data. The gap between weather station location and actual site conditions causes over- or under-watering.
3. One-size-fits-all zone model -- Users repeatedly describe frustration with mixed-planting zones. A zone containing both drought-tolerant shrubs and thirsty annuals gets a single schedule that is wrong for both.
4. No plant knowledge -- Users are expected to know crop coefficients, root depths, and soil characteristics. Most homeowners do not have this knowledge and rely on defaults that may be incorrect.
5. Cloud dependency -- All four consumer platforms require their respective cloud services to operate. No local-only fallback for smart scheduling.
6. Opaque algorithms -- Users (especially on Rachio and Hydrawise forums) express frustration that they cannot understand why the system made specific watering decisions.

Platform-Specific Pain Points

| Platform | Top User Complaint | |----------|-------------------| | Rachio | Server dependency; flowmeter compatibility issues; weather station proximity requirement | | Hydrawise | WiFi flakiness; weather data overrides canceling irrigation inappropriately; subscription-gated weather station access | | Rain Bird | Weak smart scheduling ("dumbed down"); WiFi module range; buggy app with communication errors | | B-hyve | App crashes on interval scheduling; smart watering overriding local water restrictions; unclear algorithm behavior | | GrowSphere | Enterprise-only pricing; no landscape plant models; closed ecosystem |

---

Strategic Implications for a Per-Plant Drip Irrigation Intelligence System

Whitespace Identified

1. Per-plant scheduling intelligence does not exist in any consumer or prosumer irrigation product. All five competitors operate at zone level.
2. Plant lifecycle awareness exists only in agricultural contexts (Netafim) and is not available for landscape plants.
3. Drip-specific intelligence is absent across all platforms. Drip zones are treated as spray zones with different efficiency percentages.
4. No product includes a plant knowledge base that could recommend watering parameters based on species identification.
5. No product bridges the gap between agricultural-grade crop modeling (Netafim) and consumer-grade ease of use (Rachio/B-hyve).

Integration Strategy Recommendation

• Primary integration target: Rachio -- Best public API, largest enthusiast user base, zone moisture control enables external intelligence overlay, no subscription barrier for users.
• Secondary hardware partner: Hunter -- Flow monitoring data is uniquely valuable for validating per-plant models. Professional HCC decoder system scales to large installations.
• Conceptual model: Netafim Crop Advisor -- Three-source data fusion (sensor + hydraulic + plant model) and lifecycle-stage awareness should be adapted from agricultural to landscape context.
• Competitive positioning: Against Rain Bird and B-hyve -- Both have weak smart scheduling that leaves room for a demonstrably superior per-plant approach.

Pricing Opportunity

The market shows a clear gap between consumer controllers ($90-$230, no subscription) and agricultural precision systems ($5,000+, annual subscription). A per-plant drip intelligence system priced in the $200-$500 range with a modest subscription ($5-15/mo) for cloud intelligence could occupy a completely uncontested price band while delivering capabilities that currently require agricultural-grade investment.

Competitive Analysis: Commercial Irrigation Intelligence Platforms

Date: 2026-03-01 | Status: complete Related plan: docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/plant-specific-drip-irrigation-intelligence/research/plan.md ClickUp: Plant-Specific Drip Irrigation Intelligence Scope: 5 companies — Weathermatic SmartLink, HydroPoint WeatherTRAK, Baseline/Calsense, ETwater/Jain Logic, WaterWonk

---

Executive Summary

All five companies analyzed operate at the zone level — none offer per-plant intelligence. They group plants by irrigation zone (valve) and apply a single water calculation per zone based on the dominant plant type, soil, and slope. MWELO compliance features exist but are limited to water budget reporting and drought restriction management rather than plant-level water budget documentation. The gap between what these platforms do (zone-level ET scheduling) and what SimplyScapes is proposing (per-plant species-specific drip intelligence from design through establishment) remains wide and unoccupied.

---

1. Weathermatic SmartLink

How They Approach Irrigation Scheduling / Water Management

Weathermatic uses ET-based "Smart Watering Mode" that combines local weather data with per-zone landscape inputs. The SmartLine controller calculates daily evapotranspiration loss and schedules irrigation to replace exactly what was lost. Scheduling adjusts automatically 365 days/year based on weather sensor readings.

Per-zone inputs required:

• Plant type: Turf (cool/warm season), shrubs, trees, flowers, mixed — categorical selection, not species-specific
• Soil type: Clay, sand, loam — used to calculate run/soak cycles
• Slope: 0-25 degrees — factors into cycle-soak to prevent runoff
• 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

The system also supports a weather station (on-site sensor) that feeds real-time conditions into the ET calculation.

SmartLink cloud layer adds remote monitoring, portfolio management (manage all sites from one dashboard), global commands, flow monitoring, leak detection, and water use reporting across all managed controllers.

SmartLink Connect (2025-2026): New product that retrofits non-Weathermatic controllers (Hunter 2-wire, Rain Bird) into the SmartLink cloud platform. This is a significant strategic move to grow their managed portfolio without requiring controller replacement. Available summer 2026.

Strengths

• Portfolio management at scale: Designed for landscape maintenance companies managing hundreds of sites. One dashboard, global commands, inspections tool across entire portfolio
• Cross-brand compatibility: SmartLink Connect lets them manage Hunter and Rain Bird controllers, removing a major adoption barrier
• Subscription model with hardware included: $18-50/month depending on tier includes controller hardware, lifetime warranty, and upgrades — eliminates capex for landscape companies
• Water savings reporting: Generates client-facing reports showing exactly how much water (and money) was saved — strong value prop for selling the service
• 38% average water savings documented across the installed base (500,000+ units in 85 countries)
• Leak detection and flow monitoring built into the platform

Limitations / Gaps

• Zone-level only: Plant type selection is categorical (turf/shrubs/trees/ flowers), not species-specific. If a zone has mixed plant types, the user must pick the dominant type and accept the compromise
• No per-plant intelligence: No awareness of individual plant species, water needs, establishment status, or growth lifecycle
• No MWELO-specific compliance tools: Water reporting exists but is not structured for MWELO water budget documentation (MAWA vs. ETWU calculations)
• No WUCOLS integration: Plant factor comes from broad categories, not from WUCOLS species-level data
• No drip emitter sizing: System accepts drip as a sprinkler type but does not recommend or size emitters per plant
• No establishment awareness: No concept of newly planted vs. established plants, no tapering schedules
• App stability concerns: User reports of app redesigns removing functionality, limited manual watering options

Technical Approach

• ET calculation using on-site weather sensor data + geographic location
• Penman-Monteith or simplified ET model (not explicitly documented which)
• Zone-level run time = f(ET, plant type coefficient, soil type, slope, sprinkler precip rate, fine-tuning adjustment)
• Cycle-soak automatically calculated from soil/slope inputs
• Cloud connectivity via LTE aircard (cellular)
• Flow sensors optional for leak detection and water metering

Pricing Model

| Tier | Monthly Cost | Includes | |------|-------------|----------| | Basic connectivity | $18/month | SmartLink cloud access, remote monitoring | | Landscape Pro (Premier Partner) | $39-50/month | Controller hardware, weather station, aircard, consulting, training, support, lifetime warranty | | SmartLink Connect | TBD (launching 2026) | Retrofit adapter for non-Weathermatic controllers |

No long-term contracts required. Cancel anytime. Hardware included in subscription — returns if service cancelled.

Key Takeaway for SimplyScapes

Weathermatic proves the market values portfolio-level water management reporting and subscription pricing. Their "water saved = money saved" client reports are a model for how SimplyScapes could present per-plant intelligence value. However, Weathermatic's plant type input is a dropdown with 4-5 categories — the gap between that and species-level WUCOLS data is enormous. Their SmartLink Connect strategy (managing other brands' controllers) shows the market is moving toward platform plays rather than hardware lock-in. SimplyScapes' design-time intelligence sits upstream of all of this — none of these controllers know what plants are actually in the landscape.

---

2. HydroPoint WeatherTRAK

How They Approach Irrigation Scheduling / Water Management

WeatherTRAK uses a proprietary weather data service called "ET Everywhere" that delivers high-resolution, location-specific ET data to each controller daily. The system uses the FAO Penman-Monteith equation — the international standard for ET estimation — analyzing solar radiation, temperature, wind, and relative humidity.

Per-zone scheduling in Auto Mode works through six questions:

1. What vegetation type? (turf, shrubs, trees, mixed, groundcover)
2. What soil type?
3. What sprinkler type and precipitation rate?
4. What is the slope?
5. What is the sun exposure?
6. What is the root depth?

The controller then automatically calculates water days, run times, and cycle-soak periods independently for each zone. A soil moisture depletion tracking model determines when the root zone needs refilling rather than watering on a fixed timer.

WeatherTRAK Central is the cloud management layer providing portfolio-wide visibility, water budget tracking, and compliance management.

Strengths

• Highest documented precision: Achieved a perfect score on the Irrigation Association's SWAT protocol and EPA WaterSense certification. Claims 95% of maximum conservation potential vs. 60-70% for competitors
• ET Everywhere proprietary weather data: Location-specific (not nearest weather station), updated daily, presumably interpolated from multiple sources for higher accuracy
• Depletion tracking model: Goes beyond simple ET replacement to track soil moisture depletion state — waters when the root zone actually needs it
• Compliance tools: Water Window Compliance checker reveals non-compliant settings across sites. Drought Manager allows proactive setup of drought restriction stages
• Budget Manager: Dashboard comparing water consumption vs. user-defined budgets, with daily measured and estimated usage
• Scale: 28,000+ controllers installed, focused on commercial/municipal landscapes
• 10-year all-inclusive packages available locking in hardware, warranty, cellular, and central service at current pricing

Limitations / Gaps

• Zone-level only: Same as Weathermatic — vegetation type is categorical (turf/shrubs/trees/mixed), not species-specific
• No per-plant intelligence: No concept of individual plant species, WUCOLS plant factors, or species-specific water needs
• No MWELO water budget calculation: Compliance tools focus on water window restrictions and drought stages, not MWELO's MAWA/ETWU plant-level water budget methodology
• No establishment awareness: No lifecycle stage tracking — newly planted trees get the same schedule as 10-year-old established trees
• No emitter sizing or design-time assistance: System manages schedules for existing irrigation hardware, does not help specify or size drip emitters
• Mobile app quality issues: Documented bugs — app crashes when stopping manual watering, alerts fail to clear, slow loading times. Users report these bugs persisting for years
• Struggles with strict watering restrictions: Reported to not work well on sites limited to one-day-per-week watering
• Pricing opacity: Specific per-controller pricing not publicly listed, requires sales contact

Technical Approach

• FAO Penman-Monteith ET calculation (explicitly documented)
• Proprietary "ET Everywhere" weather data — high-resolution, location-specific, daily updates via cellular
• Soil moisture depletion tracking model (proprietary)
• Per-zone independent scheduling with auto-calculated water days, run times, cycle-soak
• Flow monitoring with "Learned Flow" for leak detection (learns normal flow patterns per zone)
• Cloud-based central management (WeatherTRAK Central) via annual subscription

Pricing Model

| Component | Pricing | |-----------|---------| | ET Pro3 controller | Hardware purchase (price via distributor, ~$1,500-2,500 estimated) | | WeatherTRAK Central | Annual subscription (price not public) | | All-inclusive 10-year package | Bundles hardware + warranty + cellular + central service | | Flow sensors | Additional hardware cost |

Pricing is deliberately opaque — positioned as enterprise sales with custom quoting rather than self-serve purchasing.

Key Takeaway for SimplyScapes

HydroPoint's depletion tracking model and ET Everywhere data service represent the most scientifically rigorous approach in this competitive set. Their compliance tools (Water Window Compliance, Drought Manager) show that compliance is a selling point for commercial customers, but their compliance stops at "are we watering within allowed windows" — it does not extend to "here is a plant-by-plant MWELO water budget." The gap between their six categorical questions per zone and SimplyScapes' vision of species-level plant factor coefficients is the core opportunity. Their mobile app quality problems also suggest that established players are vulnerable to better-designed software.

---

3. Baseline (Calsense)

Note: HydroPoint acquired Baseline in 2016. Baseline continues as an independent product line under HydroPoint but serves a different market segment. Calsense is a separate company focused on municipal and institutional markets. The user's question groups them together, which reflects their overlapping customer base (water districts, municipalities) rather than corporate structure.

How They Approach Irrigation Scheduling / Water Management

Baseline (BaseStation 1000/3200): Operates in either standard timer mode or "WeatherAccess" mode (requires BaseManager Plus subscription). In WeatherAccess mode, scheduling is ET-based using web weather data and optional on-site weather sensors. Supports up to 100 zones with flow monitoring, soil moisture sensors (up to 20), and three points of connection (master valve, flow sensor, pump).

Calsense (CS3000): Uses a predictive water budget feature that determines irrigation schedules based on weather, soil, topography, and plant type — programmed at the "Group" level (groups of like stations/zones). Controllers communicate with each other and are accessible remotely. A unique feature is the FlowStation product that maximizes concurrent valve operation based on available water supply.

Calsense IMaaS (Irrigation Management as a Service): A full-service model where Calsense provides hardware, software, monitoring, training, and support as a 10-year fixed annual fee. No capital expenditure required. Won the Irrigation Association's New Product award (2022).

Strengths

• Water district and municipal relationships: Deep roots in the municipal, school district, university, and HOA markets. Case studies include City of Carson (25% water reduction), City of Vista
• Flow management excellence: Baseline's flow monitoring and management software reacts to high/low flow situations, isolates faulty zones, and protects sites from unexpected flow problems. FlowStation optimizes concurrent operation
• Soil moisture sensor integration: Baseline supports up to 20 soil moisture sensors per controller — uniquely positioned for data-driven irrigation compared to ET-only competitors
• IMaaS model eliminates capex: Municipalities and institutions avoid capital budget hurdles with Calsense's all-inclusive annual service model
• AI roadmap (Calsense): Published seven-stage Smart Irrigation 2.0 roadmap culminating in predictive analytics. Introduced "Cal" AI assistant (2023) for general irrigation Q&A. Publicly signaling AI/ML investment
• 2-wire and hybrid controller support: Handles complex large-site installations that smaller controllers cannot
• Reclaimed water support: Calsense systems designed for reclaimed water irrigation compliance — important for municipal customers
• EPA WaterSense certified (BaseStation 1000 in WeatherAccess mode)

Limitations / Gaps

• Zone/group-level scheduling: Calsense programs plant type, head type, and soil type per "Group" of like stations, not per individual plant
• No per-plant intelligence: No species-level data, no WUCOLS integration, no individual plant water budgets
• No establishment lifecycle management: No awareness of plant age, establishment status, or growth stage
• No drip emitter design tools: System manages schedules, does not participate in irrigation design or emitter selection
• MWELO compliance is operational, not documentation-based: Helps comply with watering restrictions and water budgets but does not generate MWELO-specific submittal documentation (MAWA/ETWU calculations per hydrozone)
• Hardware cost: BaseStation 1000 lists at ~$2,900-3,300 before subscription fees. High capex barrier (solved by IMaaS for Calsense customers but not Baseline customers)
• AI roadmap is early: "Cal" assistant handles general Q&A, not plant-specific scheduling intelligence. Predictive analytics on the roadmap but not yet delivered
• Limited consumer/small contractor market: Products and pricing designed for institutional and large commercial customers

Technical Approach

• Baseline: ET-based scheduling via BaseManager Plus cloud service, optional soil moisture sensor integration (patented technology), flow monitoring with auto-isolation, 2-wire decoder support for large sites
• Calsense: Predictive water budget algorithm using weather + soil + topography + plant type inputs. Web-based remote management (Calsense Connect). Controllers can share data with each other on a site. Solar-powered controller option available
• Both use cellular/WiFi connectivity for cloud management

Pricing Model

| Component | Pricing | |-----------|---------| | Baseline BaseStation 1000 (24-zone) | ~$2,900-3,300 hardware | | BaseManager Plus subscription | Required for WeatherAccess mode (price not public) | | Calsense CS3000 | Hardware purchase (price via distributor) | | Calsense IMaaS | Fixed annual fee for 10 years — hardware, software, monitoring, support included. No capex | | Soil moisture sensors (Baseline) | Additional per-sensor cost |

Key Takeaway for SimplyScapes

Calsense's IMaaS model is the most relevant business model insight: water districts and municipalities will pay for irrigation intelligence as a service rather than buying hardware. Their AI roadmap signals are worth watching — if Calsense moves toward plant-level intelligence in their seven-stage roadmap, they have the municipal customer relationships to deploy it. However, their approach starts from the controller/hardware side, not the design/plant knowledge side. SimplyScapes has the opposite advantage: deep plant data and design context that no controller company possesses. The soil moisture sensor integration (Baseline) is also notable — it provides ground-truth data that could validate or improve SimplyScapes' model-based approach if a sensor integration path is ever pursued.

---

4. ETwater (now Jain Logic / Jain Unity)

How They Approach Irrigation Scheduling / Water Management

ETwater was acquired by Jain Irrigation in 2018 and rebranded as Jain Unity. The platform claims to be the first landscape irrigation system "fully powered by artificial intelligence and predictive analytics."

The system processes environmental data from multiple sources — including landscape-specific information such as plant types, soil, and slope conditions — to generate automated, scientifically calculated watering schedules that adjust as weather changes. Jain Unity processes over a billion data points hourly on how soil moisture responds to rain or irrigation events.

Key differentiation: ETwater's scheduling is predictive, not reactive. It incorporates weather forecast data to skip irrigation when rain is coming rather than only responding after rain has occurred. Schedules adjust hourly based on live ET calculations.

Product lineup:

• SmartBox: New installation controller, 8-48 stations in 8-station increments, EPA WaterSense certified
• HermitCrab: Retrofit adapter that connects conventional "clock" controllers to the internet for smart scheduling — no controller replacement needed
• Jain Unity platform: Cloud dashboard showing plant moisture levels, weekly ET loss/replenishment notifications, historical and forecast weather data

Strengths

• Most advanced AI/ML claims in the competitive set: Patented technology integrating data science, machine learning, and predictive analytics for site-specific scheduling
• Predictive scheduling: Knows what weather is coming and adjusts proactively rather than reactively — skips irrigation when rain is forecast
• Hourly adjustments: Not just daily ET updates — schedules adjust hourly based on live conditions
• Billion-data-point processing: Cloud-based system processes soil moisture response data across all installed sites to improve models
• Cost of water tracking: Unique feature that tracks actual water cost in dollars, not just gallons — speaks directly to budget-conscious institutional customers
• Retrofit model (HermitCrab): Allows smart scheduling without replacing existing controllers — low-friction adoption path
• Parent company synergy: Jain Irrigation is one of the world's largest drip irrigation manufacturers. Potential for integrated hardware + software solutions
• 50% water reduction claims documented in marketing materials

Limitations / Gaps

• Zone/station-level scheduling: Despite the AI branding, scheduling operates per-zone/station — plant type is a zone-level input, not a per-plant input
• No per-plant intelligence: Plant types, soil, and slope are zone-level inputs. No evidence of species-level WUCOLS data integration or individual plant water budgets
• No establishment lifecycle: No concept of newly planted vs. established plants or tapering schedules
• No drip emitter design intelligence: Despite parent company being a drip irrigation manufacturer, the platform does not recommend or size emitters
• Opaque technology: "AI and predictive analytics" is marketed heavily but the actual algorithm, data inputs, and model architecture are not publicly documented. Difficult to assess actual sophistication vs. marketing
• Limited recent public updates: Most available information dates from 2018-2023. Limited evidence of 2024-2025 feature releases or roadmap announcements
• Pricing not public: Subscription-based but specific pricing requires sales contact
• Market positioning unclear post-acquisition: Jain Unity's focus appears split between landscape and agricultural markets. Product development direction is not publicly clear
• No MWELO-specific compliance documentation: Water budget tracking exists but not structured for MWELO submittal requirements

Technical Approach

• Proprietary ML models processing weather, soil moisture response, plant factors, soil type, slope, and environmental conditions
• Predictive analytics incorporating weather forecasts (not just historical/ real-time data)
• Cloud-based central processing (not on-controller)
• ET calculation from multiple weather sources (dew point, wind, cloud cover, humidity, temperature)
• Patent on centrally processing big data for predictive watering schedules based on plant types, soil, slope, and environmental factors
• 4G wireless connectivity

Pricing Model

| Component | Pricing | |-----------|---------| | SmartBox controller | Hardware + monthly subscription (price not public) | | HermitCrab retrofit | Lower cost entry — retrofit + subscription | | Jain Unity cloud platform | Included with subscription | | 30-day free trial | Available |

Subscription-based model. Contact sales at (888) 685-5505 or info@etwater.com for pricing.

Key Takeaway for SimplyScapes

ETwater/Jain represents the most technologically ambitious competitor but also the most opaque. Their AI/ML claims are difficult to validate without seeing the actual system. The critical insight is that despite having a parent company that manufactures drip emitters and a cloud platform that processes plant type data, they still have not connected the emitter product catalog to the scheduling intelligence. This is exactly the gap SimplyScapes would fill: not just "what schedule should this zone run" but "which specific emitter should be placed at this specific plant, and here is the schedule that changes as the plant establishes and grows." The HermitCrab retrofit model is a good precedent for how SimplyScapes could integrate with existing controllers without requiring hardware replacement.

---

5. WaterWonk

How They Approach Irrigation Scheduling / Water Management

WaterWonk is fundamentally different from the other four companies. It is not an irrigation controller or scheduling platform. It is a set of free web-based tools for looking up plant water use data and calculating irrigation run times, built on top of the WUCOLS (Water Use Classifications of Landscape Species) database.

Two core tools:

1. WUCOLS Plant Search (waterwonk.us / m.waterwonk.us): Searchable interface to the WUCOLS database. Users enter a city name to set their climate region, then search for plants by name. Returns the WUCOLS water use classification (Very Low, Low, Moderate, High) for that plant in that region.

2. IrrCalc (waterwonk.us/irrcalc/): Irrigation zone run time calculator. Inputs: weekly ETo, plant factor, precipitation rate, distribution uniformity, month. Calculates weekly run time in minutes using the formula: Runtime = (ETo x Plant Factor / Precipitation Rate / D.U.) x 60

WaterWonk was created in 2009 specifically to help landscape professionals comply with MWELO by making WUCOLS data accessible on mobile devices.

Strengths

• Direct WUCOLS access: The most user-friendly interface for looking up species-level plant water use classifications in California
• Free and no login required: Zero friction for quick lookups
• Mobile-optimized: Designed specifically for field use on phones
• IrrCalc simplicity: Quick zone-level run time calculation without needing a full irrigation management platform
• My Plant List feature: Users can save plants for reference (requires account)
• Created by a domain expert: Built by Rebecca Miller-Cripps (Puddle Stompers), a respected figure in California landscape water efficiency
• MWELO compliance origin: Purpose-built to help professionals comply with California's landscape water efficiency ordinance

Limitations / Gaps

• Outdated data as of January 2025: The WaterWonk site explicitly states "As of January, 2025 this list is not up to date" and directs users to the official UC Davis WUCOLS search instead. The mobile app has WUCOLS IV water use values but was not updated to include all WUCOLS IV plants due to the expanded plant types making the mobile format difficult to maintain
• No scheduling automation: IrrCalc calculates a run time number — it does not create a schedule, adjust for weather, or connect to any controller
• No per-plant intelligence: Despite having species-level WUCOLS data, the IrrCalc tool operates at the zone level (one plant factor per calculation)
• No establishment or lifecycle awareness: Static calculations only — no concept of plant age, establishment stage, or growth trajectory
• No emitter sizing: Does not recommend emitter types, GPH, or quantities
• No weather integration: Users must manually input ETo — the tool does not pull weather data or ET from any source
• California-only: WUCOLS covers 6 California climate regions. No coverage for other states (though plant factor concepts apply nationally)
• No MWELO water budget documentation: Despite being created for MWELO compliance, does not generate the actual MWELO documentation package (Landscape Documentation Package with MAWA/ETWU calculations per hydrozone)
• Maintenance abandoned: The explicit "not up to date" notice and redirection to UC Davis suggests the tool is no longer actively maintained
• Single-developer project: Appears to be a solo project by Rebecca Miller-Cripps rather than a commercially supported product

Technical Approach

• Static database lookup against WUCOLS dataset
• Simple arithmetic calculation for IrrCalc (no modeling, no ML, no weather integration)
• Web-based with mobile-optimized version
• No cloud infrastructure, no controller integration, no data pipeline

Pricing Model

Free. No subscription, no paid tier. WaterWonk appears to be a community contribution tool rather than a commercial product.

Key Takeaway for SimplyScapes

WaterWonk validates the core demand signal: landscape professionals need species-level plant water data in the field, and the WUCOLS database is the foundation they rely on. The fact that WaterWonk exists (and was used enough to justify a mobile app) proves professionals want per-plant water intelligence. But WaterWonk stopped at the lookup step. The massive gap is everything that comes after the lookup: translating WUCOLS plant factor into gallons per plant per day, selecting the right emitter, calculating run times, generating a schedule that adapts to weather and plant establishment stage, and producing MWELO-compliant documentation. WaterWonk is essentially a dictionary where SimplyScapes would be the whole sentence — and the paragraph, and the essay. The fact that WaterWonk is now outdated and pointing users to UC Davis creates a clear opportunity to become the modern, maintained, integrated alternative.

---

Cross-Cutting Analysis

The Universal Gap: Zone vs. Plant

Every controller platform in this analysis operates at the zone level — a zone being a group of plants connected to a single irrigation valve. The per-zone inputs are essentially the same across all platforms:

| Input | Weathermatic | WeatherTRAK | Baseline/Calsense | ETwater | |-------|-------------|-------------|-------------------|---------| | Plant type | Category (4-5 types) | Category (5-6 types) | Category (by group) | Category (zone-level) | | Soil type | Yes | Yes | Yes | Yes | | Slope | Yes | Yes | Yes | Yes | | Sprinkler/emitter type | Yes | Yes | Yes | Yes | | Sun exposure | Fine-tune % | Yes (explicit) | Limited | Implied in AI | | Root depth | No | Yes | Via soil sensors | Implied in AI | | Species-level plant factor | No | No | No | No | | Individual plant water budget | No | No | No | No | | Establishment stage | No | No | No | No | | Growth lifecycle | No | No | No | No | | Emitter sizing per plant | No | No | No | No | | MWELO hydrozone documentation | No | No | No | No |

The bottom six rows represent SimplyScapes' proposed differentiation. No competitor addresses any of them.

Pricing Model Comparison

| Company | Model | Approximate Cost | Capex Required? | |---------|-------|-----------------|----------------| | Weathermatic | Monthly subscription (hardware included) | $18-50/month per controller | No | | WeatherTRAK | Hardware purchase + annual subscription | $1,500-2,500 hardware + subscription | Yes (unless all-inclusive package) | | Baseline | Hardware purchase + subscription | ~$2,900-3,300 hardware + subscription | Yes | | Calsense IMaaS | Fixed annual fee (10-year term) | Not public — all-inclusive | No | | ETwater | Monthly subscription | Not public | Depends on product | | WaterWonk | Free | $0 | N/A |

The industry is clearly moving toward subscription/service models (Weathermatic's hardware-included subscription, Calsense IMaaS). This aligns well with SimplyScapes' SaaS model — the intelligence layer does not require hardware and can be priced as a subscription.

MWELO Compliance Capabilities

| Feature | Weathermatic | WeatherTRAK | Baseline/Calsense | ETwater | WaterWonk | |---------|-------------|-------------|-------------------|---------|-----------| | Water use reporting | Yes | Yes | Yes | Yes | No | | Water budget vs. actual | Limited | Yes (Budget Manager) | Yes | Yes | No | | Water window compliance | No | Yes | Limited | Limited | No | | Drought restriction management | Limited | Yes (Drought Manager) | Yes (predictive budget) | Yes | No | | MWELO MAWA/ETWU calculation | No | No | No | No | No | | Per-hydrozone water budget | No | No | No | No | No | | Landscape Documentation Package | No | No | No | No | No |

No platform generates the actual MWELO Landscape Documentation Package that water districts require for new landscape installations and major renovations. This documentation requires per-hydrozone calculations with specific plant factor coefficients from WUCOLS — exactly the kind of plant-level intelligence SimplyScapes would provide.

Roadmap Signals

• Weathermatic: Expanding horizontally (SmartLink Connect for other brands' controllers) rather than deepening plant intelligence. No signals toward per-plant features
• HydroPoint/WeatherTRAK: Investing in mobile app improvements and flow monitoring. No signals toward plant-level intelligence
• Calsense: Most active in signaling AI/ML ambitions (seven-stage roadmap, Cal AI assistant). Could potentially move toward plant-specific intelligence but current focus is on predictive maintenance and operational efficiency, not plant science
• ETwater/Jain: Quiet since 2023. AI/ML claims exist but limited evidence of recent advancement. Parent company (Jain/Rivulis) focus appears to be on agricultural markets
• WaterWonk: Effectively unmaintained as of January 2025

Where SimplyScapes Fits

SimplyScapes occupies a position that none of these competitors can easily reach because it sits upstream of all of them — at the design stage. By the time a landscape reaches any of these controllers, the critical per-plant decisions have already been made (or more commonly, never made at all).

The competitive moat is:

1. Plant library with species-level data (2,500+ species) mapped to WUCOLS
2. Design context — the system knows what plants are where
3. Emitter selection intelligence — connecting plant water needs to specific hardware
4. Lifecycle awareness — establishment through maturity
5. MWELO documentation generation — the compliance output that no controller produces

None of the five analyzed companies are positioned to build this. Controller companies work backwards from hardware; SimplyScapes works forward from design knowledge.

---

Sources

| # | Source | URL | |---|--------|-----| | 1 | Weathermatic SmartLink product page | https://www.weathermatic.com/products/smartlink/ | | 2 | Weathermatic SmartLink Connect announcement | https://www.weathermatic.com/2025/02/19/weathermatic-unveils-smartlink-connect-to-enable-remote-management-of-2-wire-and-other-irrigation-controllers/ | | 3 | Weathermatic Smart Watering Mode programming | https://support.weathermatic.com/hc/en-us/articles/360056415633-4-0-Programming-for-Smart-Watering-Mode | | 4 | SmartLink Network pricing | https://smartlinknetwork.com/pricing/ | | 5 | HydroPoint WeatherTRAK product page | https://www.hydropoint.com/weathertrak/ | | 6 | WeatherTRAK ET Pro3 | https://www.hydropoint.com/weathertrak/products/weathertrak-et-pro3/ | | 7 | WeatherTRAK Central | https://www.hydropoint.com/weathertrak/products/weathertrak-central/ | | 8 | WeatherTRAK Auto Mode programming | https://hydropoint.helpjuice.com/972748-programming-in-auto-mode | | 9 | HydroPoint evapotranspiration approach | https://www.hydropoint.com/weathertrak/evapotranspiration/ | | 10 | WeatherTRAK G2 Reviews | https://www.g2.com/products/hydropoint-weathertrak/reviews | | 11 | HydroPoint acquires Baseline | https://www.hydropoint.com/newsroom/hydropoint-acquires-smart-irrigation-provider-baseline-2/ | | 12 | Baseline BaseStation 1000 | https://www.hydropoint.com/baseline/products/basestation-1000/ | | 13 | Baseline flow sensors | https://www.hydropoint.com/baseline/products/flow-sensor/ | | 14 | Calsense home page | https://www.calsense.com/ | | 15 | Calsense CS3000 controller | https://calsense.com/smart-solutions/controllers/cs3000-controller-conventional/ | | 16 | Calsense IMaaS launch | https://www.prnewswire.com/news-releases/calsense-launches-irrigation-management-as-a-service-301491065.html | | 17 | Calsense Smart Irrigation 2.0 roadmap | https://www.calsense.com/smart-irrigation-2-0/ | | 18 | Calsense AI assistant Cal announcement | https://www.calsense.com/2023/11/28/irrigation-show-2023-calsense-introduces-irrigation-assistan/ | | 19 | Calsense City of Carson case study | https://calsense.com/project-gallery/collection/city-of-carson-smart-irrigation-case-study/ | | 20 | ETwater / Jain acquisition | https://www.jains.com/Company/news/JainIrrigationIncAcquiresSmartIrrigationPioneerETwater.htm | | 21 | Jain Unity launch | https://www.prweb.com/releases/jain-irrigation-announces-launch-of-jain-unity-r-for-water-management-805306685.html | | 22 | ETwater SmartBox controller | https://www.landscapemanagement.net/jain-irrigation-inc-etwater-smartbox-controller/ | | 23 | ETwater HermitCrab retrofit | https://www.landscapemanagement.net/etwater-by-jain-the-hermitcrab-retrofit/ | | 24 | ETwater subscription model | https://www.landscapemanagement.net/etwater-available-via-subscription/ | | 25 | Jain Irrigation AI solution launch | https://www.landscapemanagement.net/jain-irrigation-launches-ai-powered-irrigation-solution/ | | 26 | WaterWonk WUCOLS search | https://waterwonk.us/ | | 27 | WaterWonk mobile | https://m.waterwonk.us/ | | 28 | WaterWonk IrrCalc | https://waterwonk.us/irrcalc/ | | 29 | WUCOLS V (UC Davis) | https://wucols.ucdavis.edu/ | | 30 | WUCOLS plant search database | https://wucols.ucdavis.edu/plant-search-database | | 31 | MWELO official page (CA DWR) | https://water.ca.gov/Programs/Water-Use-And-Efficiency/Urban-Water-Use-Efficiency/Model-Water-Efficient-Landscape-Ordinance | | 32 | Weathermatic water savings case study | https://www.pacscape.com/files/Weathermatic-SmartLink-Saves-Water-and-Money.pdf | | 33 | WeatherTRAK all-inclusive packages | https://www.hydropoint.com/weathertrak/services/all-inclusive-package/ | | 34 | Calsense IMaaS award | https://www.prnewswire.com/news-releases/calsense-wins-irrigation-associations-new-product-award-for-irrigation-management-as-a-service-innovation-301700811.html | | 35 | Jain cost of water tracking | https://www.prweb.com/releases/Jain_Introduces_Cost_Of_Water_Tracking_Into_Smart_Irrigation/prweb19044020.htm | | 36 | Puddle Stompers / WaterWonk apps | https://puddle-stompers.com/apps.php |

Patent Landscape: Plant-Specific Drip Irrigation Intelligence

Date: 2026-03-01 | Type: Patent Landscape & FTO Assessment ClickUp: Plant-Specific Drip Irrigation Intelligence Related plan: docs/simplyscapes/product/catalog/takeoff-tool/irrigation/ideas/plant-specific-drip-irrigation-intelligence/research/plan.md

Executive Summary

This patent landscape search examined 20+ patents across Google Patents, reviewed competitor IP portfolios (Rachio, Hunter, Toro, Rain Bird, Netafim), and searched TDCommons for defensive publications. The analysis focuses on freedom-to-operate (FTO) for a software-only system that uses published plant data (WUCOLS) + weather APIs + emitter databases to recommend per-plant irrigation schedules.

Key findings:

1. No patent claims the specific combination of WUCOLS plant factor lookup + weather API ET + emitter database selection + per-plant schedule generation as a purely software service. This is a clear whitespace.

2. Most irrigation patents are hardware-dependent -- requiring physical sensors, controllers, valves, or emitter hardware. A software-only recommendation system that generates schedules from published data largely sidesteps these claims.

3. US10028454B2 (ET Water / Husqvarna) is the closest prior art -- a cloud-based environmental services platform using plant databases, ET calculations, and weather APIs for irrigation scheduling. However, its claims are tied to a specific system architecture with smart controller hardware integration and retrofit converter devices.

4. US20200037520A1 (Rachio) covers dynamically increasing plant root depth through watering schedule adjustment, which overlaps with the establishment tapering concept. However, its claims require a physical irrigation controller and soil/weather sensors.

5. No patent was found covering WUCOLS specifically as a data source for automated irrigation scheduling. WUCOLS is public-domain data published by the University of California.

6. No defensive publications related to irrigation scheduling were found on TDCommons.

7. Overall FTO assessment: FAVORABLE for a software-only, recommendation-based system. The primary risk areas are narrow and can be designed around.

---

Patent Table

Priority 1: Known Patents (Deep Analysis)

| # | Patent | Title | Assignee | Filed | Status | Key Claims | Relevance to Per-Plant Drip Intelligence | FTO Risk (Software-Only) | |---|--------|-------|----------|-------|--------|------------|------------------------------------------|--------------------------| | 1 | US8948921B2 | System and method for smart irrigation | Husqvarna AB (orig. ET Water Systems) | 2011-11-21 | Active | System with "smart controller converter" hardware device receiving schedules from central server; claims hardware signal interface, data receiver (GPRS/WiFi/SMS), processor | Claims landscape info including "plant type, age of plant, plant coefficient, number of emitters per plant, flow rate of emitter" -- highly relevant data model. However, all independent claims require a physical "smart controller converter" device | LOW. Claims are tied to hardware retrofit device. A software-only recommendation engine that outputs a schedule PDF/printout does not practice the claimed hardware elements | | 2 | US6947810B2 | System for automated monitoring and maintenance of crops | Skinner/Davena Family Trust; Vineyard Investigations | 2003-03-31 | Active (expires ~2023, likely expired) | Per-plant sensors and emitters on multi-channel conduits; DNA-based insect detection; physical valve mechanisms | Per-plant concept is relevant, but claims require physical sensors attached to conduits at each plant position and hardware valve mechanisms | NONE. Entirely hardware-dependent (sensors, conduits, valves). No software overlap | | 3 | US20190313590A1 | Smart Drip Irrigation Emitter | Rain Bird Corporation | 2019-04-04 | Application (granted as US11160220B2) | Drip emitter with embedded electronics, wireless transceiver, solenoid valve, microprocessor, sensors; mesh network of smart emitters | Hardware innovation -- embedding electronics within individual drip emitters for per-plant wireless control | NONE. Purely hardware claims (physical emitter design, PCB layout, wireless power receivers). No software scheduling claims | | 4 | US20080276534A1 | Devices and Methods for Growing Plants by Measuring Liquid Consumption | AeroGrow International | 2007-12-17 | Application (status unclear) | Hydroponic/aeroponic apparatus with liquid level measurement; adjusts light/nutrients based on consumption rate | Growth-stage adaptive concept is relevant as analogy, but claims are specific to indoor hydroponic/aeroponic systems with enclosed vessels | NONE. Indoor hydroponic only, not outdoor landscape irrigation. Different domain entirely | | 5 | US20250048979A1 | Irrigation system, irrigation sensor and smart scheduling | Waterworks Inc | 2024-08-11 | Application (pending) | Moisture sensors with physical wands for soil insertion; controller with zone connections; ML-based scheduling rules | Uses machine learning for schedule optimization, which is conceptually relevant. But claims require physical moisture sensor hardware with "pointed wands" | LOW. Claims require physical sensor hardware. Software-only ML scheduling without proprietary sensors does not infringe. Monitor if granted with broader software claims |

Priority 2: Closest Software-Relevant Patents

| # | Patent | Title | Assignee | Filed | Status | Key Claims | Relevance | FTO Risk | |---|--------|-------|----------|-------|--------|------------|-----------|----------| | 6 | US10028454B2 | Environmental Services Platform | Husqvarna AB (orig. ET Water Systems) | 2015-08-24 | Active (expires 2036-05-15) | Cloud-based platform correlating site survey data with plant databases (1M+ species), weather APIs, soil data; generates "plant-specific hyper-local evapotranspiration"; real-time schedule recalculation | CLOSEST PRIOR ART. Cloud platform using plant databases + weather data + ET calculation for irrigation scheduling. Very similar concept | MODERATE. Claims cover cloud-based irrigation schedule generation using plant data + ET. However, claims appear tied to the complete ET Water/Husqvarna system architecture including smart controller hardware integration. A purely recommendation-based system (no controller integration) may not practice the full claimed system. Requires detailed claim-by-claim analysis by patent counsel | | 7 | US20200037520A1 | Method for Dynamically Increasing Plant Root Depth | Rachio Inc | 2019-07-31 | Application (likely granted) | Server estimates root depth based on historical watering data, grass type, soil characteristics; generates training watering plan to increase root depth over time; uses crop coefficients | Overlaps with establishment/tapering concept -- gradually adjusting watering to train deeper roots | LOW-MODERATE. Claims require physical irrigation controller + sensors (soil moisture, weather, cameras). The concept of adjusting watering over time to train root depth is claimed, but in context of a closed-loop physical system. A schedule recommendation from published data is different | | 8 | US8209061B2 (filed as US20100030389A1) | Computer-Operated Landscape Irrigation and Lighting System | The Toro Company | 2006-07-31 | Active (expires 2026-08-04) | PC-based landscape control software; FAO-56 ET calculation; scheduling advisor using PAW, allowable depletion, soil infiltration rates; zone-by-zone management | Software-based scheduling with ET and soil data. Close conceptual overlap | LOW. Claims tied to a combined irrigation+lighting control system operating hardware. Scheduling Advisor is a feature within a hardware control system, not a standalone recommendation engine. Expires August 2026 | | 9 | US10743484B2 | Precipitation sensing to vary irrigation schedules | Rachio Inc | 2018-04-17 | Active | Software-based precipitation analysis; central controller analyzes rain sensor signals with ET rates and meteorological data to adjust schedules | Software-based schedule adjustment using weather data | LOW. Claims require physical rain sensor hardware and irrigation controller. Schedule adjustment algorithm is claimed only in context of sensor signal processing | | 10 | US8649907B2 | Method and system for irrigation control | Rain Bird Corporation | 2010-08-03 | Active | Wireless IoT nodes; distributed sensor network; server uses daily ET + crop type + soil + growth period for scheduling; remote web/mobile management | Server-side scheduling using ET, crop type, and growth period -- relevant data model | LOW. Claims require physical wireless sensor nodes, solenoid valve controllers. The server-side scheduling is claimed only as part of the hardware+software system |

Priority 3: Water Budget & ET-Based Scheduling Patents

| # | Patent | Title | Assignee | Filed | Status | Key Claims | Relevance | FTO Risk | |---|--------|-------|----------|-------|--------|------------|-----------|----------| | 11 | US8620480B2 | Irrigation water conservation with automated water budgeting and time of use technology | Hunter Industries | 2010-11-29 | Active | Automated seasonal water budget using temperature budgeting (explicitly NOT ET-based); pre-calculated bell curves for seasonal needs; can be add-on module or standalone | Water budget automation concept. Notably avoids ET and plant factors -- uses temperature-only approach | NONE. Claims are hardware controller-based and explicitly do NOT use ET, plant factors, or crop coefficients. Different approach entirely | | 12 | US8565904B2 | Irrigation controller integrating no-watering restrictions and ET local characteristic curve | Individual inventor | 2011-04-05 | Active | "FROG" controller using empirically-derived local ET curves; learns existing controller schedules; avoids crop coefficients (explicitly criticizes them as "suited to agriculture, not homeowners") | Uses localized ET data for scheduling. Explicitly avoids plant-specific coefficients | NONE. Claims require physical "FROG" controller device. Uses ET curves but explicitly avoids per-plant/per-species approach | | 13 | US7337042B2 | Method and system for controlling irrigation using computed evapotranspiration values | HydroPoint Data Systems | 2004-10-29 | EXPIRED (2024-10-29) | Remote ET calculation from non-local weather data using mesoscale modeling; 4D grid weather interpolation; transmits ET to irrigation systems | Foundational patent on cloud-based ET calculation for remote irrigation control. Now expired | NONE. Expired October 2024. Now public domain | | 14 | US20020014539A1 | Irrigation system for controlling irrigation in response to changing environmental conditions | Individual inventor | 2000-12-19 | ABANDONED (2002) | Method using plant factors (0.3/0.5/0.8 for low/moderate/high water plants) multiplied by ET to determine per-species water needs; automatic schedule adjustment | Most directly relevant to per-plant scheduling using plant factors x ET. However, abandoned in 2002 | NONE. Abandoned application. Never granted. Now prior art that helps establish this approach as unpatentable (obvious) | | 15 | US9173354B2 | Irrigation system and method | IBM | 2013-08-15 | Active | Dripline zones with replaceable emitters; controllable valves at zone borders; sequential valve actuation for zone-by-zone delivery | Zone-level drip control hardware | NONE. Hardware-only (solenoid coils, magnetic stoppers, physical valves). No scheduling algorithm claims |

Priority 4: Additional Competitor Patents

| # | Patent | Title | Assignee | Filed | Status | Key Claims | Relevance | FTO Risk | |---|--------|-------|----------|-------|--------|------------|-----------|----------| | 16 | US7962244B2 | Landscape irrigation time of use scheduling | Hunter Industries | ~2007 | Active | Time-of-use scheduling compliance with local watering restrictions | Regulatory compliance scheduling | NONE. Hardware controller feature for time-of-use compliance. No per-plant or ET claims | | 17 | US7245991B1 | Distributed architecture irrigation controller | Hunter Industries | ~2004 | Active | Distributed processing across controller modules | Controller architecture | NONE. Hardware architecture only | | 18 | US7584023B1 / US20110049260A1 | Electronic irrigation system software | The Toro Company | 2007-02-12 | Active | Irrigation control software on PC; graphical UI for schedule creation; sensor monitoring integration | Software-based scheduling and monitoring with GUI | LOW. Claims tied to integrated hardware control system. UI for controlling physical irrigation equipment, not standalone recommendations | | 19 | US9202252B1 | System for conserving water and optimizing land and water use | Swiim Systems / USDA / Jain | 2013-03-15 | Active | Software platform for agricultural water conservation; crop selection/rotation optimization; water rights market facilitation | Agricultural water optimization software | NONE. Agricultural domain, not landscape irrigation. Water rights market focus | | 20 | US11160220B2 (from US20190313590A1) | Smart drip irrigation emitter | Rain Bird Corporation | 2019-04-04 | Active | Smart drip emitter hardware with embedded electronics and mesh networking | Per-plant hardware control | NONE. Purely hardware claims |

---

Competitor IP Summary

Rachio Inc.

• Portfolio focus: Smart irrigation controllers with software-based scheduling, precipitation sensing, root depth management
• Key patents: US10743484B2 (precipitation sensing), US20200037520A1 (root depth training), design patents (D935,904)
• FTO assessment: Rachio's patents consistently require physical controller hardware and sensors. Their software innovations are claimed only in context of their hardware ecosystem. A standalone software recommendation system does not practice their claims. The root depth/establishment tapering concept is the closest overlap, but Rachio claims it with physical controllers and sensors
• Risk level: LOW

Hunter Industries

• Portfolio focus: Controller hardware, water budgeting, ET-based scheduling, time-of-use compliance, sensor integration
• Key patents: US8620480B2 (water budgeting), US7962244B2 (time-of-use), US8793024B1 (soil moisture adjustment)
• FTO assessment: Hunter's patents are heavily hardware-focused -- controllers, modules, sensor interfaces. Their water budget approach explicitly avoids ET and plant factors (uses temperature budgeting instead). No claims on software-only recommendation systems or per-plant scheduling
• Risk level: NONE

The Toro Company

• Portfolio focus: Irrigation control software, landscape lighting integration, sensor-based systems
• Key patents: US8209061B2 (PC-based landscape irrigation/lighting), US7584023B1 (electronic irrigation software)
• FTO assessment: Toro has the most software-focused patents among hardware competitors, but claims are tied to integrated hardware control systems. US8209061B2 expires August 2026. No claims on plant-database-driven recommendation engines
• Risk level: LOW (and diminishing as key patents expire)

Rain Bird Corporation

• Portfolio focus: Smart emitter hardware, IoT sensor networks, wireless irrigation control, drip emitter physical design
• Key patents: US11160220B2 (smart drip emitter), US8649907B2 (IoT irrigation control), 450+ total patents
• FTO assessment: Rain Bird's extensive portfolio is overwhelmingly hardware-focused -- emitter designs, valve mechanisms, sensor networks. Their software claims are embedded within IoT hardware system claims. No standalone software recommendation patents identified
• Risk level: NONE

Netafim Ltd.

• Portfolio focus: Drip irrigation hardware (emitters, dripline, pressure compensation), agricultural digital farming (NetBeat/GrowSphere)
• Key patents: ~250 patents, primarily drip hardware. US7048010B2 (low-pressure drip system)
• FTO assessment: Netafim's patents are almost entirely physical drip irrigation hardware. Their digital farming platform (GrowSphere/NetBeat) is agricultural-focused, not landscape. No landscape irrigation software patents identified
• Risk level: NONE

Husqvarna AB (via ET Water Systems acquisition)

• Portfolio focus: Cloud-based irrigation platforms, smart controller retrofit systems
• Key patents: US8948921B2 (smart irrigation system), US10028454B2 (environmental services platform)
• FTO assessment: Highest risk competitor. US10028454B2 describes a cloud platform using plant databases (1M+ species), weather APIs, and ET calculations for irrigation scheduling -- conceptually very close to the proposed SimplyScapes system. However, claims appear tied to the complete ET Water system architecture including hardware controller integration. The system is now owned by Husqvarna and appears to be the basis of their smart irrigation products
• Risk level: MODERATE -- requires detailed claim analysis by patent counsel

---

Freedom-to-Operate Assessment

Proposed SimplyScapes System Architecture

For FTO purposes, the system under evaluation is:

• Software-only -- no proprietary hardware, no sensors, no controllers manufactured
• Data inputs: WUCOLS plant database (public domain, UC Davis), weather APIs (Open-Meteo, public), emitter manufacturer catalogs (public product data)
• Processing: Per-plant water calculation using MWELO formula (ETL = ETo x Ks x Kd x Kmc), emitter selection from product database, establishment tapering from published extension service schedules
• Output: Irrigation schedule recommendations (digital display, PDF, printable), emitter specifications, water budget reports
• No direct controller integration in MVP (recommendation-only)

Risk Matrix

| Risk Level | Patent(s) | Concern | Mitigation | |------------|-----------|---------|------------| | MODERATE | US10028454B2 (Husqvarna/ET Water) | Cloud platform using plant databases + ET + weather for irrigation scheduling | 1. Analyze independent claims vs. SimplyScapes architecture -- key difference is recommendation-only vs. controller-integrated system. 2. SimplyScapes uses WUCOLS specifically (public data), not a proprietary plant database. 3. No hardware retrofit device. 4. Consider design-around if claims are broad. Recommend patent counsel review | | LOW-MODERATE | US20200037520A1 (Rachio) | Dynamically adjusting watering schedule to increase root depth over time | 1. Rachio claims require physical controller + sensors. 2. SimplyScapes uses published extension service establishment schedules (prior art from UF/IFAS, AMWUA), not a proprietary algorithm. 3. No closed-loop sensor feedback. 4. Establishment tapering is well-documented in horticultural science | | LOW | US8948921B2 (Husqvarna/ET Water) | Data model includes per-plant parameters (plant type, age, coefficient, emitters per plant, flow rate) | Claims require hardware "smart controller converter" device. Software-only system does not practice hardware claims. Monitor for continuation applications with broader software claims | | LOW | US8209061B2 (Toro) | Software-based scheduling with ET and soil data | Expires August 2026. Claims tied to integrated hardware control system | | LOW | US20250048979A1 (Waterworks) | ML-based irrigation scheduling | Pending application. Claims require physical sensor hardware. Monitor for grant with claim amendments | | NONE | All other patents reviewed | Hardware-only claims (sensors, controllers, valves, emitters) | Software-only system does not practice hardware claims |

Key FTO Advantages for Software-Only Approach

1. No hardware = no infringement on hardware claims. The overwhelming majority of irrigation patents claim physical devices (controllers, sensors, emitters, valves). A software recommendation system that outputs schedules without controlling hardware avoids these claims entirely.

2. Public data sources eliminate trade secret concerns. WUCOLS is published by UC Davis as a public resource. ET data is available via free APIs (Open-Meteo). Emitter specifications are published by manufacturers. The MWELO formula is published California state regulation. No proprietary data is needed.

3. Well-established prior art. The concept of using plant factors x ET to calculate irrigation needs is documented in horticultural literature going back decades. The abandoned US20020014539A1 (filed 2000) explicitly describes plant factors of 0.3/0.5/0.8 multiplied by ET for per-species scheduling. This establishes the fundamental approach as prior art.

4. Establishment tapering is public science. UF/IFAS, AMWUA, and multiple university extension services have published detailed establishment watering schedules. Using published schedules is not patentable.

5. MWELO formula is government regulation. The landscape coefficient formula (ETL = ETo x Ks x Kd x Kmc) is California state regulation, published in official government documents. It cannot be patented.

Residual Risks

1. US10028454B2 claim scope uncertainty. Without a line-by-line claim analysis, it is unclear whether the independent claims of this patent are broad enough to cover a recommendation-only platform that does not integrate with physical controllers. The specification describes a comprehensive system, but independent claims may be narrower. This is the single most important patent for counsel to review.

2. Continuation applications. Companies like Husqvarna, Rachio, and Rain Bird may file continuation applications with claims targeting software-only implementations. Monitor new applications from these assignees.

3. International patents. This search focused on US patents. International filings (EP, WO, AU, IL) from the same assignees should be checked, particularly for landscape irrigation in water-scarce markets.

4. Future patent applications. The specific combination of WUCOLS + per-plant emitter selection + lifecycle management appears to be unpatented whitespace. Filing a defensive publication or patent application would provide protection.

---

TDCommons Defensive Publications Search

A search of TDCommons (tdcommons.org) for defensive publications related to irrigation scheduling, plant watering, landscape water management, and related terms returned no relevant results. The platform contains technical disclosures primarily in software, AI, automotive, and medical device fields, with no identified publications addressing landscape irrigation intelligence.

Implication: There is an opportunity to file a defensive publication on TDCommons covering the specific method of combining WUCOLS plant factor data + weather API ET + emitter product databases + establishment lifecycle schedules to generate per-plant irrigation recommendations. This would create prior art preventing future broad patent claims in this space.

---

Search Terms & Coverage

| Search Term | Results Found | Relevant Patents | |-------------|---------------|------------------| | "per-plant irrigation scheduling" | No exact matches | US8948921B2, US6947810B2 (tangential) | | "species-specific irrigation" / "plant-specific watering" | No exact matches | None with exact terminology | | "drip emitter automatic selection" / "emitter sizing system" | No exact matches | Hardware emitter patents only (Rain Bird, Netafim) | | "plant establishment irrigation" / "irrigation tapering schedule" | No exact matches | US20200037520A1 (root depth training) | | "landscape water budget calculation" / "MWELO compliance software" | Multiple results | US8620480B2, US8538592B2, US8565904B2 | | "irrigation lifecycle management" / "plant growth irrigation adjustment" | No exact matches | US20080276534A1 (indoor only) | | "digital twin landscape irrigation" | No landscape irrigation results | Digital twin patents in wind/industrial only | | "plant factor coefficient" + "irrigation" | Multiple results | US20020014539A1 (abandoned), US8948921B2, US8649907B2 | | "crop coefficient" / "plant factor" + irrigation schedule software | Multiple results | US10028454B2, US20020014539A1, US8649907B2 | | "landscape coefficient" / "species factor" + irrigation | Multiple results | US8948921B2, US8209061B2 | | WUCOLS + irrigation scheduling | No patent matches | WUCOLS not referenced in any patent | | "emitter database" / "emitter catalog" | No software matches | Hardware emitter design patents only | | Rachio assignee patents | Multiple results | US10743484B2, US20200037520A1, D935,904 |

---

Whitespace Identified

The following areas appear to be unpatented and represent potential IP opportunities:

1. WUCOLS-based automated irrigation scheduling -- No patent references WUCOLS as a data source for automated schedule generation. The combination of WUCOLS plant factors + weather API ET + automated per-plant scheduling is novel in patent literature.

2. Emitter product database for automated selection -- No patent covers a software system that maintains an emitter product database and automatically recommends emitter type/flow rate based on plant water requirements. All emitter patents are hardware designs.

3. Design-time irrigation intelligence -- No patent covers generating per-plant irrigation specifications (emitter type, GPH, runtime, frequency) at the landscape design phase, before installation. Existing patents assume an installed system.

4. Lifecycle-aware irrigation recommendations without sensors -- No patent covers a sensor-free system that adjusts irrigation recommendations over a multi-year lifecycle (establishment, growth, maturity, decline) using published horticultural data rather than sensor feedback.

5. MWELO compliance report generation -- No patent covers automated generation of MWELO water budget compliance documentation from a per-plant design database.

6. Digital twin for landscape irrigation -- No landscape-specific digital twin patent exists. All digital twin patents are industrial (wind farms, manufacturing, oil rigs). A landscape digital twin tracking plant growth and water needs over time is entirely novel.

---

Recommendations

1. Engage patent counsel to review US10028454B2 (Husqvarna/ET Water) independent claims in detail. This is the one patent that could potentially pose FTO concerns for a cloud-based plant-data-driven irrigation scheduling platform.

2. File a defensive publication on TDCommons covering the specific SimplyScapes method: WUCOLS plant factor lookup + Open-Meteo ET API + emitter product database + establishment lifecycle schedule = per-plant drip irrigation recommendation. This creates prior art immediately.

3. Consider a provisional patent application covering the whitespace areas identified above, particularly design-time irrigation intelligence, lifecycle-aware sensor-free recommendations, and the emitter auto-selection method.

4. Monitor continuation applications from Husqvarna (ET Water patents), Rachio, and Waterworks Inc. Set up Google Patents alerts for these assignees.

5. Proceed with development confidence. The software-only, recommendation-based architecture has a favorable FTO position. The key differentiator -- using published WUCOLS data + public weather APIs + manufacturer product catalogs to generate per-plant recommendations at design time -- has no direct patent coverage.

---

Sources

| # | Type | Reference | URL | |---|------|-----------|-----| | 1 | Patent | US8948921B2 -- System and method for smart irrigation | https://patents.google.com/patent/US8948921B2/en | | 2 | Patent | US6947810B2 -- Per-plant sensor and emitter control | https://patents.google.com/patent/US6947810B2/en | | 3 | Patent | US20190313590A1 / US11160220B2 -- Smart drip irrigation emitter | https://patents.google.com/patent/US20190313590A1/en | | 4 | Patent | US20080276534A1 -- Growth-stage adaptive irrigation (AeroGarden) | https://patents.google.com/patent/US20080276534A1/en | | 5 | Patent | US20250048979A1 -- Smart scheduling with ML | https://patents.google.com/patent/US20250048979A1/en | | 6 | Patent | US10028454B2 -- Environmental Services Platform | https://patents.google.com/patent/US10028454B2/en | | 7 | Patent | US20200037520A1 -- Method for dynamically increasing plant root depth | https://patents.google.com/patent/US20200037520A1/en | | 8 | Patent | US8209061B2 -- Computer-operated landscape irrigation and lighting | https://patents.google.com/patent/US20100030389A1/en | | 9 | Patent | US10743484B2 -- Precipitation sensing to vary irrigation schedules | https://patents.google.com/patent/US10743484B2/en | | 10 | Patent | US8649907B2 -- Method and system for irrigation control | https://patents.google.com/patent/US8649907B2/en | | 11 | Patent | US8620480B2 -- Automated water budgeting | https://patents.google.com/patent/US8620480B2/en | | 12 | Patent | US8565904B2 -- ET local characteristic curve irrigation controller | https://patents.google.com/patent/US8565904B2/en | | 13 | Patent | US7337042B2 -- Controlling irrigation using computed ET values (EXPIRED) | https://patents.google.com/patent/US7337042B2/en | | 14 | Patent | US20020014539A1 -- Irrigation in response to changing conditions (ABANDONED) | https://patents.google.com/patent/US20020014539A1/en | | 15 | Patent | US9173354B2 -- Irrigation system and method (IBM) | https://patents.google.com/patent/US9173354B2/en | | 16 | Patent | US7962244B2 -- Landscape irrigation time of use scheduling | https://patents.google.com/patent/US7962244B2/en | | 17 | Patent | US7245991B1 -- Distributed architecture irrigation controller | https://patents.google.com/patent/US7245991B1/en | | 18 | Patent | US7584023B1 -- Electronic irrigation system software | https://patents.google.com/patent/US7584023B1/en | | 19 | Patent | US9202252B1 -- Water conservation and land/water use optimization | https://patents.google.com/patent/US9202252B1/en | | 20 | Patent | US20070089365A1 -- Plant watering system (ABANDONED) | https://patents.google.com/patent/US20070089365A1/en | | 21 | Search | Rachio patent portfolio | https://patents.justia.com/assignee/rachio-inc | | 22 | Search | Rain Bird patent portfolio | https://patents.justia.com/assignee/rain-bird-corporation | | 23 | Search | Hunter Industries patent portfolio (via Google Patents searches) | https://patents.google.com/ | | 24 | Search | Toro Company patent portfolio | https://patents.justia.com/assignee/toro-company | | 25 | Search | Netafim patent portfolio | https://patents.justia.com/assignee/netafim-ltd | | 26 | Search | TDCommons defensive publication search | https://www.tdcommons.org/dpubs_series/ | | 27 | Search | Justia Patents -- Class 700/284 (Irrigation) | https://patents.justia.com/patents-by-us-classification/700/284 |

Adjacent Market Pattern Analysis & Academic/Open Source Scan

ID: SS-RR-2026-001-B | Date: 2026-03-01 | Status: complete ClickUp: Plant-Specific Drip Irrigation Intelligence Parent plan: SS-RP-2026-001 Domain: Irrigation Management / Precision Watering

---

PART 1: Adjacent Market Pattern Analysis

This section examines six products and industries that solve analogous problems to plant-specific landscape irrigation intelligence. For each, we identify the transferable pattern and its limits.

---

1. Netafim GrowSphere / CropX

What they are: GrowSphere is Netafim's cloud-based operating system for precision irrigation and fertigation, integrating hydraulic control, operational management, and agronomic intelligence. CropX is a complementary soil-sensing platform used by 20,000+ users across 70+ countries and 100+ crop types.

Their solution to the analogous problem:

Agricultural crops go through defined growth stages (germination, vegetative, flowering, fruit set, maturation) with dramatically different water needs at each phase. GrowSphere's Crop Advisor module solves this by running crop model algorithms built on 50 years of Netafim agronomic knowledge. The system takes as inputs: climate data, soil texture, crop development stage parameters, irrigation strategy, hydraulic constraints, and field sensor feedback. Every midnight, the model recalculates irrigation recommendations based on updated climate conditions and field data.

CropX approaches the same problem from the soil side -- sensors at multiple depths measure moisture, temperature, electrical conductivity, and salinity. Combined with satellite data, weather stations, and farm machinery telemetry, CropX applies crop-specific agronomic models to determine when and how much to irrigate.

Transferable pattern:

• Lifecycle-stage-aware irrigation models. The concept that water delivery must change as the organism matures is directly applicable. Landscape plants have analogous phases: establishment (high-frequency watering), root development (tapering), and mature maintenance (weather-adjusted only).
• Midnight recalculation loop. The nightly batch recalculation pattern using weather forecasts and sensor feedback is a clean architectural model for landscape irrigation. SimplyScapes could run a similar daily or weekly recalculation using ET data from Open-Meteo.
• Multi-source data fusion. GrowSphere combines sensor data, weather data, crop models, and hydraulic constraints into a single recommendation. This layered approach (rather than relying on any single data source) is the right architecture for landscape irrigation.
• 50+ years of empirical crop data encoded as algorithms. WUCOLS + university extension establishment schedules are the landscape equivalent of Netafim's crop knowledge base.

What does NOT transfer:

• Crop uniformity assumption. Agricultural fields contain rows of identical plants. Landscape beds contain diverse species with different water needs planted adjacent to each other. The per-crop model must become a per-plant model.
• Sensor dependency. GrowSphere and CropX rely on in-ground soil sensors. Residential landscape irrigation cannot depend on per-plant sensor hardware -- the system must be data-driven and sensor-free.
• Monoculture economics. Agricultural irrigation ROI is calculated per-acre yield. Landscape irrigation value is measured in plant survival, aesthetic quality, and water savings -- fundamentally different metrics.
• Growth stage precision. Crop growth stages (V1-VT-R6 in corn) are precisely defined and predictable. Ornamental plant growth stages are fuzzier and more variable by species.
• Q2 2026 smallholder product. Netafim's upcoming low-cost version (fewer sensors, phone-operated) is interesting but still assumes agricultural crop context.

Key sources:

• Netafim GrowSphere Digital Farming
• GrowSphere Crop Advisor
• CropX Agronomic Platform
• CropX Irrigation Planning

---

2. Smart Building HVAC (Nest, ecobee commercial)

What they are: Smart thermostat and building management systems that optimize heating/cooling across multiple zones in commercial and residential buildings. Ecobee SmartBuildings extends this to multi-unit commercial and multifamily properties.

Their solution to the analogous problem:

Buildings have multiple thermal zones, each with different characteristics (sun exposure, occupancy patterns, insulation quality, equipment heat load). Smart HVAC systems create individual zone profiles and optimize each zone independently while managing shared infrastructure (a single HVAC system serving multiple zones). Key techniques include:

• Model Predictive Control (MPC): Using thermal models of each zone to predict future conditions and pre-condition spaces proactively. Research shows this approach saves 24% energy in heating and 9% in cooling versus rule-based control.
• Per-zone load profiles: Each zone learns its own thermal response characteristics over time, accounting for solar gain, occupancy patterns, and thermal mass.
• Time-of-use optimization: Ecobee's systems precool/preheat during off-peak electricity periods, saving up to 23% on cooling costs -- scheduling optimization beyond simple on/off.
• Machine learning algorithms: RF, XGBoost, and neural networks achieve 96%+ accuracy in predicting zone-level thermal comfort needs.

Transferable pattern:

• Per-zone becomes per-plant. The conceptual leap from "every room has different thermal needs" to "every plant has different water needs" is the core analogy. HVAC solved this with zone profiles; irrigation needs plant profiles.
• Shared infrastructure, independent demands. A single HVAC unit serves multiple zones just as a single irrigation valve serves multiple plants. The optimization problem (how to satisfy diverse needs through shared infrastructure) is structurally identical.
• Predictive scheduling. MPC-based HVAC doesn't wait for a room to get hot -- it preconditions. Similarly, irrigation should predict water needs based on upcoming weather, not just react to current conditions.
• Learning from operational data. Smart thermostats learn individual building behavior over time. An irrigation system could learn site-specific microclimate effects (south-facing beds dry faster, shaded areas retain moisture).
• Fleet management model. Ecobee SmartBuildings manages thousands of thermostats across properties via a single API/portal. This maps to a landscape company managing irrigation schedules across hundreds of client properties.

What does NOT transfer:

• Real-time feedback loops. HVAC has immediate temperature feedback (thermometer in every room). Landscape irrigation has no equivalent real-time plant-moisture sensor in the consumer/prosumer market.
• Reversibility. HVAC errors are immediately recoverable (turn on AC if too hot). Irrigation errors can kill plants and may take months to manifest.
• Zone granularity vs. cost. Adding a temperature sensor to a room costs $20. Adding a soil moisture sensor per plant is economically unviable for residential landscapes.
• Indoor controlled environment. HVAC operates in enclosed spaces with predictable physics. Landscape irrigation faces open-system variables (rain, wind, runoff, soil heterogeneity).

Key sources:

• ecobee SmartBuildings
• ML Predictive Model for Smart Buildings (ScienceDirect)
• RL for HVAC Control (Springer)
• Multi-Zone Building Energy Management (ScienceDirect)

---

3. Precision Viticulture (Fruition Sciences, Tule Technologies)

What they are: Precision viticulture companies that provide per-vine and per-block monitoring to optimize wine grape irrigation for quality and yield. Fruition Sciences uses sap flow sensors; Tule Technologies uses surface renewal ET measurement.

Their solution to the analogous problem:

Wine grapes require carefully managed water stress -- too much water reduces grape quality, too little kills vines. Fruition Sciences installs sap flow sensor collars directly on vine trunks that measure water movement through the plant in real time. Temperature differentials before and after heat application reveal transpiration rates. Data transmits via solar-powered loggers to a cloud platform that compares blocks, vintages, and stress levels.

Tule Technologies places miniature weather-station-like sensors throughout vineyards to measure actual ET at the canopy level, feeding data into an AI system that calculates precise irrigation volumes. Their sensors measure environmental variables that traditional weather stations miss at the microclimate level.

Wineries like Wente Family Estates combine both systems -- Fruition for plant-level physiological data, Tule for atmospheric demand -- achieving 65% water savings on average.

Transferable pattern:

• Plant-as-sensor concept. Fruition's sap flow approach treats the plant itself as the sensor rather than measuring the soil. While we cannot install sap flow sensors on landscape plants, the concept of inferring plant water status from observable characteristics (growth rate, leaf appearance) could inform user-facing guidance.
• Block-to-vine data hierarchy. Vineyards are organized as estate > block > vine, with irrigation managed at the block level but monitored at the vine level. Landscape irrigation maps similarly: property > zone > individual plant. The data model is directly transferable.
• Stress-target management. Viticulture doesn't aim for maximum water -- it targets specific stress levels for quality. Similarly, many landscape plants perform better with moderate stress (deeper root development, more compact growth, better flowering). The concept of "target water stress" rather than "maximum water delivery" is a paradigm shift worth studying.
• Multi-vintage historical comparison. Fruition compares performance across growing seasons. Landscape systems could compare year-over-year water use and plant performance to optimize schedules.

What does NOT transfer:

• Economic justification for per-plant sensors. Wine grapes at $3,000-$10,000/ton justify $500+ sensor installations per block. Landscape plants at $20-$200 each cannot support this cost structure.
• Monoculture simplification. A vineyard block contains one rootstock/scion combination. A landscape bed may contain 10+ species.
• Expert interpretation. Fruition's data requires viticulturist interpretation. Landscape irrigation intelligence must be fully automated and require zero agronomic expertise.
• Quality vs. survival metric. Vineyard irrigation optimizes for flavor compounds and brix levels. Landscape irrigation optimizes for survival, health, and aesthetic appearance -- different objective functions.

Key sources:

• Fruition Sciences Sap Flow Sensors
• Fruition Sciences White Papers
• Tule Technologies
• Precision Viticulture Water -- Napa Valley Wine Academy

---

4. AeroGarden / Indoor Growing (GrowAI)

What they are: Consumer indoor hydroponic growing systems by Scotts Miracle-Gro. The AeroGarden product line grows herbs and small plants in nutrient-solution-based countertop units. The GrowAI system adds computer vision and machine learning.

Their solution to the analogous problem:

AeroGarden's traditional systems used pre-programmed schedules: add water when the indicator light comes on, add nutrients every two weeks, run lights on a fixed timer. GrowAI fundamentally changes this by using computer vision and machine learning to monitor plants 24/7 and adapt growing conditions in real time. The system detects plant growth stage, identifies problems before they become visible to humans (98% accuracy vs. 89% for competitors), and automatically adjusts:

• LED light spectrum and intensity (35% more PAR, 35% less electricity)
• Nutrient concentration
• Watering timing
• Air circulation intensity

The key innovation is that GrowAI learns from each growing cycle and adapts to the specific environment (ambient light, temperature, humidity of the room) rather than following static schedules.

Transferable pattern:

• Growth-stage adaptive delivery without sensors in the root zone. AeroGarden proves that you can adjust water and nutrient delivery based on growth stage without per-plant soil sensors. The growth stage is inferred from time-based models and visual observation (or in GrowAI's case, computer vision). This validates the sensor-free approach for landscape irrigation.
• Pre-programmed knowledge base per species. Each AeroGarden seed pod comes with species-specific growing parameters. This is directly analogous to WUCOLS plant factors -- a knowledge base that encodes per-species water needs.
• Simplified user interface. AeroGarden hides all complexity behind simple indicators (add water now, add nutrients now). Landscape irrigation intelligence should similarly compress complex calculations into actionable recommendations.
• Closed-loop learning. GrowAI improves recommendations based on observed outcomes. While landscape irrigation cannot easily close the loop (no camera on every plant), user feedback (plant died, plant thriving) could serve as a coarse feedback signal.

What does NOT transfer:

• Controlled environment. AeroGarden operates indoors with controlled light, temperature, and zero precipitation variability. Landscape irrigation must account for weather, soil drainage, sun/shade exposure, and seasonal change.
• Hydroponic medium. AeroGarden uses soilless growing medium with uniform water-holding characteristics. Landscape plants grow in heterogeneous soil with variable drainage, clay content, and organic matter.
• Scale. AeroGarden manages 6-12 plants in a 2-square-foot unit. Landscape irrigation manages dozens to hundreds of plants across thousands of square feet.
• Computer vision feasibility. GrowAI's camera-based monitoring works because plants are 12 inches from a fixed camera. Landscape-scale computer vision for individual plant health monitoring is not currently practical for residential use.

Key sources:

• AeroGarden How It Works
• AeroGarden GrowAI Analysis
• AeroGarden by Scotts Miracle-Gro

---

5. John Deere Operations Center / Climate FieldView

What they are: Cloud-based digital agriculture platforms that create field-level digital twins for crop management. John Deere Operations Center (by Deere & Co.) manages equipment, field data, and prescriptions. Climate FieldView (by Bayer Crop Science) provides satellite imagery, management zone creation, and variable-rate prescriptions.

Their solution to the analogous problem:

Agricultural fields are heterogeneous -- soil type, drainage, organic matter, compaction, and yield potential vary across a single field. These platforms create digital twins of each field by layering multiple data sources:

• Boundary mapping: GPS-traced field boundaries define the management unit.
• Satellite imagery: Regular captures reveal crop health variability (NDVI, chlorophyll content).
• Historical yield data: Combine harvester yield monitors record per-pass productivity.
• Soil sampling: Lab results tied to GPS coordinates reveal nutrient and texture variability.
• As-applied maps: Track exactly what was planted and applied where.
• Management zones: Algorithms cluster areas with similar characteristics and auto-generate variable-rate prescriptions (different seed populations or fertilizer rates for different zones).

John Deere's Operations Center extends this to a unified platform where farm managers set up the digital twin of their farm and plan work ahead of time, monitoring activity in real time and analyzing performance.

Transferable pattern:

• Landscape digital twin concept. SimplyScapes already has the foundation -- a digital representation of a landscape design with plant locations, species, and irrigation zones. Extending this to a living digital twin that evolves with the landscape (plants grow, some die, new ones are added) is the direct analog of FieldView's field digital twin.
• Multi-layer data overlay. FieldView layers satellite imagery, soil data, weather, and historical performance. A landscape digital twin could layer: plant species data (WUCOLS), site-specific weather (ET from Open-Meteo), soil type (SSURGO/Web Soil Survey), establishment stage, and irrigation history.
• Variable-rate prescription model. FieldView's variable-rate seeding prescriptions (different rates for different management zones) map directly to per-plant watering prescriptions (different GPH for different species in the same irrigation zone).
• Boundary-to-prescription workflow. The FieldView flow of (1) define boundaries, (2) analyze data layers, (3) generate prescription, (4) execute via equipment is structurally identical to (1) define landscape plan, (2) lookup plant water needs, (3) generate irrigation schedule, (4) push to controller or print schedule.
• Temporal data accumulation. FieldView stores multi-year yield data that improves future decisions. Landscape irrigation could accumulate multi-year performance data per property.

What does NOT transfer:

• Equipment integration. FieldView talks to combine yield monitors and planter controllers via ISOBUS. Landscape irrigation controllers have no equivalent standardized machine-to-cloud protocol.
• Satellite resolution. Agricultural satellite imagery at 3-10m resolution works for 100-acre fields. It cannot distinguish individual plants in a 500-sq-ft landscape bed.
• Harvest feedback. Agricultural digital twins close the loop via yield data at harvest. Landscape irrigation has no equivalent quantitative outcome measurement.
• Scale economics. These platforms serve farms of hundreds to thousands of acres. The per-acre economics of data collection, processing, and storage don't translate to 0.1-acre residential lots without dramatic cost reduction.

Key sources:

• John Deere Precision Ag Technology
• Climate FieldView
• FieldView Field-Level Data Analysis
• FieldView Prescription Building
• Digital Twins in Agriculture (PMC)

---

6. Lawnbot / Robin Autopilot

What they are: Robotic mowing companies that deploy autonomous mowers on residential and commercial properties. Robin Autopilot operates a Robotics-as-a-Service (RaaS) model with fleet management software. The broader category includes Husqvarna CEORA, Scythe Robotics (commercial), and Segway Navimow.

Their solution to the analogous problem:

Each property has unique geometry, obstacles, terrain, and grass areas. Robotic mowers solve this by creating per-property digital maps:

• Initial property mapping: During first deployment, the robot traverses the entire property and creates a digital boundary map. Modern systems use RTK-GPS (1-3cm accuracy) combined with vision AI and inertial sensors, eliminating the need for physical boundary wires.
• Multi-zone management: Properties divided by driveways, paths, or structures are mapped as separate zones, each with independent mowing schedules.
• Robin Fleet Console: A multi-manufacturer fleet management platform that lets landscapers monitor status, track maintenance, send commands, and route service crews across thousands of robots. The platform integrates with CRM systems and Google Maps for routing.
• RaaS business model: Robin provides software, CRM, training, and proprietary hardware (patented robotic door for fence navigation) as a subscription service, with landscapers deploying robots across their customer base.

Transferable pattern:

• Per-property digital model. Robotic mowers have validated that residential landscapes can be digitally modeled at high fidelity. The boundary mapping, zone definition, and scheduling infrastructure these companies have built is conceptually identical to what's needed for per-plant irrigation management.
• Fleet/portfolio management for service companies. Robin's Fleet Console -- managing thousands of units across hundreds of properties -- is the exact operational model a landscape company would need for managing irrigation schedules across their client portfolio. The SaaS platform architecture (monitoring, alerts, maintenance tracking, crew routing) translates directly.
• RaaS as distribution model. Robin proved that landscape professionals will adopt a SaaS subscription model for landscape technology. This validates SimplyScapes' approach of offering irrigation intelligence as a platform service rather than a hardware product.
• Multi-manufacturer integration. Robin's platform works with mowers from Husqvarna, Graze, Greenzie, and Scythe. A landscape irrigation intelligence platform should similarly be controller-agnostic (Rachio, Hunter, Rain Bird).

What does NOT transfer:

• Physical robot presence. Mowing robots physically traverse the property, enabling detailed mapping. Irrigation intelligence must infer property characteristics from design data, satellite imagery, and user input -- no physical agent visits the site.
• Mowing is uniform. Every square foot of turf gets the same treatment (cut to the same height). Irrigation requires heterogeneous treatment (different water volumes for different plants). The per-zone approach of mowing is insufficient for per-plant irrigation.
• Binary success metric. Mowing either happened or it didn't. Irrigation quality is a spectrum that's hard to measure without direct observation.
• Limited data model depth. Robotic mower property data is primarily geometric (boundaries, obstacles, slopes). Irrigation intelligence requires biological data (species, growth stage, root depth) layered on top of geometry.

Key sources:

• Robin Autopilot Fleet Console Launch
• Robin Autopilot RaaS Model (NALP)
• RTK-GPS Robot Mower Navigation (Yarbo)
• Robin Autopilot Subscriber Platform

---

Cross-Market Pattern Synthesis

| Pattern | Source Industries | Landscape Irrigation Application | |---------|------------------|----------------------------------| | Lifecycle-stage-aware models | Agriculture (GrowSphere), Indoor growing (AeroGarden) | Establishment-to-mature irrigation tapering based on time-since-planting and species-specific growth rates | | Per-entity optimization through shared infrastructure | HVAC (per-zone), Viticulture (per-vine) | Per-plant water calculation delivered through shared irrigation zones | | Digital twin with multi-layer data | Ag platforms (FieldView, Operations Center) | Landscape digital twin layering species data, weather/ET, soil, and irrigation history | | Predictive scheduling using weather models | HVAC (MPC), Agriculture (Crop Advisor nightly recalculation) | Daily/weekly irrigation recalculation using ET forecast data | | Fleet management for service companies | Landscape robotics (Robin Fleet Console) | Multi-property irrigation schedule management for landscape companies | | Sensor-free growth-stage inference | Indoor growing (AeroGarden GrowAI) | Time-based + species-parameter growth stage transitions without per-plant sensors | | Knowledge base per organism | Agriculture (50yr crop models), Viticulture (varietal databases) | WUCOLS + extension establishment schedules as encoded plant knowledge |

Key gap no adjacent market has solved: None of these adjacent markets manage diverse, heterogeneous organisms in an uncontrolled outdoor environment without sensors. Agriculture assumes monoculture; HVAC has thermostats in every room; viticulture manages one species; indoor growing is a controlled environment. Landscape irrigation with per-plant intelligence for diverse outdoor plantings is genuinely novel.

---

PART 2: Academic & Open Source Scan

Search Terms and Venues Covered

| Search Term | Venues Searched | |-------------|-----------------| | "landscape irrigation scheduling model" | Google Scholar, ScienceDirect, ASCE Library, Extension services | | "ornamental plant water requirements" | Google Scholar, ResearchGate, HortScience, HortTechnology | | "plant factor coefficient" NOT "crop coefficient" | Google Scholar, WUCOLS literature, MWELO documentation | | "drip irrigation design automation" | Google Scholar, software vendor sites, GitHub | | "landscape water budget software" | EPA WaterSense, state tools, MWELO calculators | | "urban landscape evapotranspiration" | Water Resources Research, Remote Sensing, MDPI journals | | "establishment irrigation ornamental" | University extension services, ASHS journals, NIFA projects | | GitHub repos tagged "irrigation" + "landscape" | GitHub Topics, HACS, community projects | | ASCE Journal of Irrigation and Drainage Engineering | ASCE Library (2020-2025) | | HortScience / HortTechnology (ASHS) | ASHS journals (2023-2025) | | USDA NIFA funded projects | NIFA CRIS database |

---

Academic Literature Findings

| # | Type | Reference | Date | Key Finding | Relevance to SimplyScapes | |---|------|-----------|------|-------------|--------------------------| | 1 | Journal Article | Litvak et al., "Evapotranspiration of urban landscapes in Los Angeles, California at the municipal scale," Water Resources Research | 2017 | Modeled urban landscape ET as a two-component system (turfgrass + trees). Found turfgrass is responsible for 70% of vegetation ET; 54% of residential water goes to irrigation. Annual ET from vegetated landscapes was 1,110 mm/yr. | Validates the two-component (turf + non-turf) approach to landscape water budgeting. Confirms the scale of the water use problem. | | 2 | Journal Article | "Irrigation Scheduling Approaches and Applications: A Review," ASCE J. Irrigation and Drainage Engineering, Vol 146 No 6 | 2020 | Compares four operational methods: ET/water balance, soil moisture status, plant water status, and models. Concludes that combining approaches yields best results. | Confirms that the MWELO ET-based water budget approach (used by WUCOLS/SimplyScapes) is one of four valid methods; sensor-free ET approach is well-established in literature. | | 3 | Journal Article | "Effects of various irrigation regimes on water use efficiency and visual quality of some ornamental herbaceous plants," Agricultural Water Management | 2019 | Tested 4 ornamental species at 25%, 50%, 75%, and 100% ET0 irrigation levels. Found species-specific thresholds where visual quality degrades. | Provides empirical evidence that different ornamental species respond differently to deficit irrigation -- supports per-species water factors rather than uniform watering. | | 4 | Journal Article | "Regulated deficit irrigation in different phenological stages of potted geranium plants," Acta Physiologiae Plantarum | 2013 | Deficit irrigation outside flowering phase brought flowering forward, increased root/shoot ratio, improved plant form, and saved 20% water. | Validates growth-stage-specific irrigation adjustment: establishment/vegetative phase can tolerate less water without harming flowering. Directly supports lifecycle-aware scheduling. | | 5 | Journal Article | "Water requirements of urban landscape plants: A comparison of three factor-based approaches," Ecological Engineering | 2014 | Compared WUCOLS, landscape coefficient method (MWELO), and UC landscape water demand approach. Found significant variation between methods for same plants. | Highlights that WUCOLS plant factors are approximate and that method choice matters. SimplyScapes should use MWELO's landscape coefficient (Ks x Kd x Kmc) rather than raw WUCOLS categories alone. | | 6 | Journal Article | "Estimation of Urban Evapotranspiration at High Spatiotemporal Resolution," Remote Sensing | 2023 | Developed PT-Urban model for urban ET that accounts for urban canopy heat storage. Found that ignoring canopy heat storage significantly degrades half-hourly ET estimation in urban areas. | Relevant for accuracy of ET-based irrigation in urban settings. Urban heat island effects mean standard reference ET may underestimate actual plant water demand in cities. | | 7 | Journal Article | "A three-layer evapotranspiration model considering vertical structure of urban green spaces," Urban Forestry & Urban Greening | 2024 | Proposed a three-layer model (overstory trees, understory shrubs, ground cover) for urban green space ET, capturing vertical structure effects on water demand. | Directly relevant to landscape irrigation: a planting bed with a tree, shrubs, and groundcover has layered water demand. Supports the per-plant approach over zone-level averages. | | 8 | Journal Article | "Irrigation rates and turfgrass evapotranspiration in cities with contrasting water availability," JAWRA | 2025 | Compared urban turfgrass irrigation rates and actual ET across multiple cities with different water policies and climate. Found large variation in irrigation efficiency. | Demonstrates that water policy context (the user's water district) significantly affects actual irrigation behavior. Supports building MWELO compliance into the system. | | 9 | Journal Article | "Effects of Reduced Substrate Volumetric Water Contents on Three Landscape Shrubs," HortScience Vol 60 No 2 | 2025 | Tested Knock Out rose, rosemary, and chaste tree at 0.40 vs. 0.20 m3/m3 substrate water content for 50 days. Found species-specific responses to reduced water. | Recent data confirming species-specific drought responses in common landscape shrubs. Can inform plant factor refinements beyond WUCOLS categories. | | 10 | Journal Article | "Landscape irrigation scheduling efficiency and adequacy by various control technologies," Agricultural Water Management | 2011 | Measured irrigation adequacy and efficiency using soil water balance models for ET-based controllers, soil moisture sensor controllers, and rain sensors. | Quantifies that ET-based controllers (the approach SimplyScapes would use) achieve good scheduling adequacy when properly calibrated. | | 11 | Database | WUCOLS V -- Water Use Classification of Landscape Species (UC Davis) | 2025 | Live database of 4,100+ taxa with plant water use ratings across 6 California climate regions. WUCOLS V update completed March 2025 with ~1,200 new entries. | Primary plant factor data source. The V update expanding to 4,100+ species significantly improves coverage for SimplyScapes' 2,500+ species library. | | 12 | Journal Article | "Water Demand Determination for Landscape Using WUCOLS and LIMP Mathematical Models," Water (MDPI) | 2025 | Compared WUCOLS-based water demand calculation with LIMP (Landscape Irrigation Management Program) mathematical model for landscape water budgeting. | Directly relevant methodology paper comparing approaches to landscape water budget calculation. | | 13 | Journal Article | "Assessing the accuracy of OpenET satellite-based evapotranspiration data," Nature Water | 2023 | Evaluated OpenET's ensemble of six remote sensing models against ground-truth data. Found field-scale accuracy suitable for water management applications. | Validates OpenET as a credible ET data source for landscape irrigation, complementing Open-Meteo's reference ET0 data. | | 14 | Research Report | "Quantifying microclimatic conditions: An attempt to more accurately estimate urban landscape water requirements," Landscape & Urban Planning | 2021 | Attempted to quantify microclimate effects (the Kmc factor in MWELO) on actual urban landscape water needs. Found significant microclimate variation within single properties. | Supports the MWELO microclimate factor (Kmc) as important for accuracy, but also shows defaults may be insufficient for high accuracy. |

---

USDA NIFA Funded Projects

| # | Project Title | Institution | Key Focus | Relevance | |---|---------------|-------------|-----------|-----------| | 1 | Water Management and Quality for Ornamental Crop Production and Health | Rutgers University | Alternative water sources (reclaimed, stormwater, graywater) for ornamental irrigation; water quality effects on plant health | Tangentially relevant -- confirms institutional research investment in ornamental irrigation optimization | | 2 | Water Management and Quality for Ornamental Crop Production and Health | Clemson University | Water management practices for nursery production; runoff reduction | Nursery production focus, but methodology for measuring ornamental water use is transferable | | 3 | Water Management and Quality for Ornamental Crop Production and Health | Purdue University | Irrigation efficiency for container-grown ornamentals | Container production focus; data on ornamental water uptake rates potentially useful | | 4 | Investigating Landscape Water Consumption and Minimum Tree Water Requirements | Utah State University | Evaluates smart controller effectiveness; determines minimum tree water requirements for urban landscape conservation | Highly relevant. Directly researches the landscape irrigation scheduling problem and minimum water needs for established landscape trees. Part of the CWEL (Center for Water-Efficient Landscaping) program. | | 5 | Optimizing Irrigation Efficiency for Ornamental Plants | University of Georgia | Developing irrigation controllers that apply correct water amounts only when plants need it | Relevant technology development for sensor-based ornamental irrigation controllers | | 6 | Quantifying and Qualifying Water Use in Ornamental Plant Production | University of Florida | Measuring water use in ornamental plant production systems | Source data for ornamental plant water uptake rates | | 7 | NC_old1186: Water Management and Quality for Specialty Crop Production | Multi-institutional (NIMSS) | Collaborative project across multiple states studying water management for specialty and ornamental crops | Ongoing multi-state collaboration that may produce new ornamental water use data |

---

Open Source Projects & Software Tools

| # | Type | Name / Reference | URL | Description | Relevance | |---|------|-----------------|-----|-------------|-----------| | 1 | HA Integration | HAsmartirrigation | GitHub | Home Assistant component that calculates irrigation runtime based on ET, precipitation, and soil moisture. Supports multiple zones with individual configuration. Uses daily ET calculation from temperature/humidity. | High relevance. Closest open-source implementation to per-zone ET-based irrigation scheduling. Zone configuration model could inform SimplyScapes' per-plant approach. | | 2 | HA Integration | Smart Sprinklers (Irrigation Unlimited fork) | GitHub | Home Assistant integration with weather-aware scheduling, cycle-and-soak methodology, moisture-based control, and adaptive learning across multiple zones. | Weather-adaptive scheduling algorithms and cycle/soak logic are directly relevant. | | 3 | HA Integration | Irrigation Unlimited | GitHub | Full-featured irrigation controller for Home Assistant with advanced scheduling, sequence management, and zone control. | Controller integration architecture reference. | | 4 | Hardware + Software | OpenSprinkler | Website | Open-source web-based sprinkler controller. Drop-in replacement for conventional controllers. Scales from a few zones to 48 zones. | Demonstrates open-source controller ecosystem. Could be an integration target for SimplyScapes. | | 5 | Hardware + Software | Hydrosys4 | Website | Raspberry Pi-based irrigation and greenhouse automation with up to 70+ irrigation lines, soil moisture feedback, weather adjustment, and conditional irrigation. | Demonstrates sensor-based conditional irrigation logic. More complex than needed for landscape use but architecture is instructive. | | 6 | ML Model | Irrigation Scheduler (RL) | GitHub | Reinforcement Learning model for irrigation scheduling in smart agriculture. | Academic prototype demonstrating ML-based irrigation optimization. Could inform future SimplyScapes ML features. | | 7 | Python Library | RefET (WSWUP) | GitHub | Python implementation of ASCE standardized reference evapotranspiration calculations. | Useful reference implementation for ET calculations in SimplyScapes' backend. | | 8 | Satellite Platform | OpenET | Website / GitHub | Satellite-based ET data at 30m resolution using an ensemble of 6 models. Expanded to 48 states in 2025. Open-source model implementations available. | High relevance. Primary ET data source alternative/supplement to Open-Meteo. Open-source model code available for reference. | | 9 | Web App | EPA WaterSense Water Budget Tool | EPA | Excel-based tool for calculating landscape water budgets using local climate data, plant factors, and irrigation system efficiency. WaterSense specification compliant. | High relevance. Reference implementation of the water budget calculation that SimplyScapes would automate. Shows what compliance-grade output looks like. | | 10 | Web App | USU Landscape Irrigation Calculator | USU Extension | Online calculator for annual and monthly landscape water budgets by region. | Simple reference implementation of landscape water budgeting. | | 11 | Web App | TGWCA Water Budget Calculator | TGWCA | MWELO-compliant water budget calculator with customizable controls for irrigation rate, frequency, and green cover. Free to use. | MWELO compliance reference tool. | | 12 | Design Software | IRRICAD | Website | Commercial irrigation design software for all pressurized systems (drip, sprinkler, residential, commercial). Global leader. | Competitive reference for irrigation design automation. Not open source but defines the feature standard. | | 13 | Design Software | AquaFlow (Toro) | Toro | Free drip irrigation design software from Toro for configuring drip systems for optimum hydraulic performance. Available as iOS/Android app. | Reference for drip-specific design automation. Free and manufacturer-provided. | | 14 | Design Software | IrriPro (IrriWorks) | Website | Advanced irrigation design software for landscape, urban, gardening, sports fields, and parks. | Commercial landscape irrigation design tool. Competitor/reference. | | 15 | Design Software | Pro Contractor Studio | Website | Stand-alone irrigation design program for residential and medium commercial projects. No CAD dependency. | Competitor/reference for residential irrigation design. |

---

ASCE Journal of Irrigation and Drainage Engineering -- Recent Relevant Publications

| Year | Article | Key Finding | |------|---------|-------------| | 2020 | "Irrigation Scheduling Approaches and Applications: A Review" | Comprehensive review comparing ET/water balance, soil moisture, plant water status, and model-based scheduling methods. Concluded that integrated approaches combining methods perform best. | | 2022 | "Soil Moisture or ET-Based Smart Irrigation Scheduling: A Comparison for Sweet Corn with Sap Flow" | Compared soil-moisture-based vs. ET-based scheduling using sap flow as ground truth. Found both approaches viable with proper calibration. | | 2025 | "Hydraulic and Hydrologic Invariance: Effectiveness of Green Roofs and Permeable Pavements" | Tangentially relevant -- demonstrates stormwater management modeling approaches that could inform runoff-aware irrigation scheduling. |

---

HortScience / HortTechnology -- Recent Relevant Publications

| Year | Journal | Article | Key Finding | |------|---------|---------|-------------| | 2025 | HortScience | "Effects of Reduced Substrate VWC on Three Landscape Shrubs" | Species-specific responses to reduced water: rose, rosemary, and chaste tree showed different tolerance thresholds after 50 days at 0.20 vs. 0.40 m3/m3. | | 2024 | HortTechnology | NC_old1186 multi-state water management project publications | Ongoing research on water-conserving irrigation practices in production and landscape settings across multiple states. | | 2023 | Various | Ornamental nursery irrigation efficiency studies | Overhead irrigation shown as most common but least efficient for ornamentals; microirrigation systems (drip) more efficient but higher installation/maintenance cost. |

---

Key Academic Gaps Identified

1. No published per-plant irrigation scheduling model for diverse landscapes. Agricultural models exist for per-crop scheduling, but nothing analogous exists for mixed-species landscape beds. This is the core innovation opportunity.

2. Limited ornamental growth rate databases. While ANSI Z60.1 provides nursery sizing standards and urban forestry literature has tree growth data, there is no comprehensive database mapping ornamental plant growth rates (canopy width, height, root zone expansion) over time. This is a data gap SimplyScapes would need to fill incrementally.

3. WUCOLS is California-centric. While plant water use categories are somewhat transferable to other semi-arid climates, the 6-region framework does not cover the entire US. The SLIDE Rules (ANSI/ASABE S623.1) provide a more generalized framework but with less species specificity.

4. Urban microclimate effects on landscape ET are poorly quantified. The MWELO microclimate factor (Kmc) has limited empirical backing. Research shows significant within-property variation but does not provide actionable lookup tables.

5. Establishment irrigation science is fragmented by region. UF/IFAS, AMWUA, and a few state extensions have published schedules, but there is no unified national resource. Many regions have no published establishment tapering data.

---

Source Summary Table

| # | Type | Reference | URL | |---|------|-----------|-----| | S1 | Platform | Netafim GrowSphere Digital Farming | https://www.netafim.com/en/digital-farming/ | | S2 | Platform | GrowSphere Crop Advisor | https://www.netafim.com/en/digital-farming/crop-advisor/ | | S3 | Platform | CropX Agronomic Platform | https://cropx.com/ | | S4 | Platform | CropX Irrigation Planning | https://cropx.com/cropx-system/irrigation-planning/ | | S5 | Platform | ecobee SmartBuildings | https://ecobee.com/smartbuildings | | S6 | Journal | ML Predictive Model Smart Buildings | https://www.sciencedirect.com/science/article/pii/S259012302400402X | | S7 | Journal | RL for HVAC Control (Springer) | https://link.springer.com/article/10.1007/s10791-025-09544-y | | S8 | Journal | Multi-Zone Building Energy Mgmt | https://www.sciencedirect.com/science/article/abs/pii/S0360544220315188 | | S9 | Platform | Fruition Sciences Sap Flow | https://fruitionsciences.com/en/sap-flow-irrigation-sensors | | S10 | Research | Fruition Sciences White Papers | https://fruitionsciences.com/en/sciences-white-papers | | S11 | Platform | Tule Technologies | https://tule.ag/ | | S12 | Article | Precision Viticulture Water (NVWA) | https://napavalleywineacademy.com/precision-viticulture-water/ | | S13 | Platform | AeroGarden How It Works | https://aerogarden.com/how-it-works.html | | S14 | Analysis | AeroGarden GrowAI | https://justoborn.com/aerogarden-growa/ | | S15 | Platform | John Deere Precision Ag | https://www.deere.com/en/technology-products/precision-ag-technology/ | | S16 | Platform | Climate FieldView | https://climate.com/en-us.html | | S17 | Platform | FieldView Data Analysis | https://climate.com/en-us/solutions/analyze-data.html | | S18 | Platform | FieldView Prescription Building | https://climate.com/en-us/solutions/build-prescriptions.html | | S19 | Journal | Digital Twins in Agriculture (PMC) | https://pmc.ncbi.nlm.nih.gov/articles/PMC11100011/ | | S20 | Article | Robin Autopilot Fleet Console | https://www.landscapemanagement.net/robin-autopilots-launches-new-fleet-management-platform/ | | S21 | Article | Robin RaaS Model (NALP) | https://blog.landscapeprofessionals.org/the-future-is-robotics-as-a-service/ | | S22 | Article | RTK-GPS Mower Navigation (Yarbo) | https://www.yarbo.com/blog/rtk-gps-technology | | S23 | Journal | Litvak et al., Urban Landscape ET in LA (WRR) | https://agupubs.onlinelibrary.wiley.com/doi/abs/10.1002/2016WR020254 | | S24 | Journal | ASCE Irrigation Scheduling Review | https://ascelibrary.org/doi/abs/10.1061/(ASCE)IR.1943-4774.0001464 | | S25 | Journal | Ornamental Irrigation Regimes (Ag Water Mgmt) | https://www.sciencedirect.com/science/article/abs/pii/S0378377418312137 | | S26 | Journal | Deficit Irrigation Geranium (Springer) | https://link.springer.com/article/10.1007/s11738-012-1165-x | | S27 | Journal | Urban Landscape Water Requirements Comparison | https://www.sciencedirect.com/science/article/abs/pii/S0925857413001432 | | S28 | Journal | Urban ET High Spatiotemporal Resolution | https://www.mdpi.com/2072-4292/15/5/1327 | | S29 | Journal | Three-Layer Urban Green Space ET Model | https://www.sciencedirect.com/science/article/abs/pii/S1618866724001870 | | S30 | Journal | Turfgrass Irrigation Rates Cities (JAWRA 2025) | https://onlinelibrary.wiley.com/doi/10.1111/1752-1688.13236 | | S31 | Journal | Landscape Shrub Water Responses (HortScience 2025) | https://journals.ashs.org/hortsci/view/journals/hortsci/60/2/article-p208.xml | | S32 | Database | WUCOLS V (UC Davis) | https://wucols.ucdavis.edu/ | | S33 | Journal | WUCOLS + LIMP Water Demand Models (MDPI 2025) | https://www.mdpi.com/2073-4441/17/10/1429 | | S34 | Journal | OpenET Accuracy Assessment (Nature Water 2023) | https://www.nature.com/articles/s44221-023-00181-7 | | S35 | Journal | Urban Microclimate Landscape Water (L&UP 2021) | https://www.sciencedirect.com/science/article/abs/pii/S1618866720305847 | | S36 | NIFA Project | USU Landscape Water Consumption & Tree Water Req. | https://portal.nifa.usda.gov/web/crisprojectpages/0158215-investigating-landscape-water-consumption-and-minimum-tree-water-requirements-to-improve-irrigation-scheduling-for-urban-landscape-water-conservation.html | | S37 | NIFA Project | Rutgers Ornamental Water Mgmt | https://portal.nifa.usda.gov/web/crisprojectpages/1008077-water-management-and-quality-for-ornamental-crop-production-and-health.html | | S38 | NIFA Project | UGA Irrigation Efficiency Ornamentals | https://portal.nifa.usda.gov/web/crisprojectpages/0203661-optimizing-irrigation-efficiency-for-ornamental-plants.html | | S39 | NIFA Project | UF Quantifying Ornamental Water Use | https://portal.nifa.usda.gov/web/crisprojectpages/0205044-quantifying-and-qualifying-water-use-in-ornamental-plant-production.html | | S40 | Open Source | HAsmartirrigation (Home Assistant) | https://github.com/jeroenterheerdt/HAsmartirrigation | | S41 | Open Source | Smart Sprinklers (Home Assistant) | https://github.com/ljbotero/smart_sprinklers | | S42 | Open Source | Irrigation Unlimited (Home Assistant) | https://github.com/rgc99/irrigation_unlimited | | S43 | Open Source | OpenSprinkler | https://rayshobby.net/wordpress/opensprinkler/ | | S44 | Open Source | Hydrosys4 | https://hydrosysblog.wordpress.com/ | | S45 | Open Source | Irrigation Scheduler (RL Model) | https://github.com/savude/irrigation_scheduler | | S46 | Open Source | RefET Python Library | https://github.com/WSWUP/RefET | | S47 | Platform | OpenET | https://etdata.org/ | | S48 | Open Source | OpenET GitHub | https://github.com/Open-ET | | S49 | Tool | EPA WaterSense Water Budget Tool | https://www.epa.gov/watersense/water-budget-tool | | S50 | Tool | USU Landscape Irrigation Calculator | https://extension.usu.edu/cwel/landscape-irrigation-calculator | | S51 | Tool | TGWCA Water Budget Calculator | https://www.tgwca.org/waterbudget.html | | S52 | Software | IRRICAD | https://www.irricad.com/ | | S53 | Software | AquaFlow (Toro) | https://driptips.toro.com/aquaflow-drip-irrigation-design-software/ | | S54 | Software | IrriPro (IrriWorks) | https://irriworks.com/irripro/ | | S55 | Software | Pro Contractor Studio | https://www.softwarerepublic.com/ | | S56 | Extension | UC Davis Landscape Irrigation Scheduling | https://ccuh.ucdavis.edu/landscape-irrigation-scheduling | | S57 | Extension | UF/IFAS Irrigation Research | https://hort.ifas.ufl.edu/woody/irrigation-research.shtml | | S58 | Extension | USU Efficient Irrigation Trees/Shrubs | https://extension.usu.edu/cwel/research/efficient-irrigation-of-trees-and-shrubs | | S59 | Extension | Clemson Landscape Irrigation Mgmt | https://hgic.clemson.edu/factsheet/landscape-irrigation-management-3/ | | S60 | Regulation | CA MWELO | https://water.ca.gov/Programs/Water-Use-And-Efficiency/Urban-Water-Use-Efficiency/Model-Water-Efficient-Landscape-Ordinance |

Controller Integration Feasibility

ID: SS-RR-2026-002 | Date: 2026-03-01 | Status: complete Domain: Irrigation Management / Smart Controller Integration Related: Plant-Specific Drip Irrigation Intelligence (SS-RR-2026-001)

TL;DR

SimplyScapes can push per-plant irrigation schedules to smart controllers, but the path varies dramatically by manufacturer. Rachio is the clear first integration target: a well-documented public REST API with bearer-token auth, full zone read/write (including vegetation type, soil type, nozzle, shade), schedule start/skip/adjust, and webhook support -- all free at 1,700 calls/day. OpenSprinkler is the best open-source option with a fully open HTTP API covering programs, stations, and weather adjustments. Hunter Hydrawise has two APIs: a personal-use REST API (v1.5) for basic zone control, and a GraphQL/OAuth2 API (v2) for commercial use that requires written authorization. Rain Bird has no public API -- integration requires the reverse-engineered SIP protocol via the pyrainbird library, limited to one concurrent connection. B-hyve (Orbit) has no official API; community libraries use reverse-engineered REST+WebSocket endpoints that could break at any time. The recommended strategy: start with Rachio (official API), add OpenSprinkler (open-source, full control), pursue Hydrawise commercial API access, and use Rain Bird IQ4's commercial API subscription for the professional landscaper market.

---

1. Controller-by-Controller Analysis

1.1 Rachio (Rachio Inc.)

Market position: Leading consumer smart irrigation controller. Rachio 3 is the most popular WiFi sprinkler controller in the US residential market.

API availability: Official public REST API, well-documented at rachio.readme.io.

API documentation: Rachio Public API v2.0 | Postman collection | Support article

Authentication

• Model: OAuth2 bearer token
• Token acquisition: Users generate personal API tokens from the Rachio mobile app (Profile > API key > Copy)
• Header format: Authorization: Bearer <token>
• Third-party OAuth flow: Not currently available. There is no delegated OAuth flow for third-party apps to authenticate on behalf of users. Each user must manually copy their API key and paste it into the third-party app. This is a significant limitation for a consumer-facing integration.
• Rachio has discussed OAuth webhook authorization in community forums but has not implemented it as of March 2026.

Endpoints and Capabilities

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

| Category | Endpoint | Method | Capability | |----------|----------|--------|------------| | Person | /public/person/info | GET | Get authenticated user info | | | /public/person/:id | GET | Get user details | | Device | /public/device/:id | GET | Get controller details, zones, schedules | | | /public/device/:id/current_schedule | GET | Get currently running schedule | | | /public/device/:id/event | GET | Query historical watering events | | | /public/device/:id/forecast | GET | Weather forecast data | | | /public/device/on | PUT | Power device on | | | /public/device/off | PUT | Power device off | | | /public/device/stop_water | PUT | Stop all watering | | | /public/device/rain_delay | PUT | Set rain delay (duration param) | | | /public/device/pause_zone_run | PUT | Pause current zone run | | | /public/device/resume_zone_run | PUT | Resume paused zone run | | Zone | /public/zone/:id | GET | Get zone config (vegetation, soil, nozzle, shade) | | | /public/zone/start | PUT | Start zone watering (with duration) | | | /public/zone/start_multiple | PUT | Run multiple zones in sequence | | | /public/zone/setMoistureLevel | PUT | Set soil moisture (mm) | | | /public/zone/setMoisturePercent | PUT | Set soil moisture (0-1 pct) | | | /public/zone/enable | PUT | Enable zone | | | /public/zone/disable | PUT | Disable zone | | Schedule | /public/schedulerule/:id | GET | Get schedule rule details | | | /public/schedulerule/start | PUT | Start a schedule | | | /public/schedulerule/skip | PUT | Skip next scheduled run | | | /public/schedulerule/seasonal_adjustment | PUT | Adjust duration by pct (-1 to 1) | | | /public/schedulerule/skip_forward_zone_run | PUT | Advance to next zone | | Webhooks | /public/notification/webhook | POST | Create webhook | | | /public/notification/webhook | PUT | Update webhook | | | /public/notification/webhook/:id | DELETE | Delete webhook | | | /public/notification/:deviceId/webhook | GET | List device webhooks | | | /public/notification/webhook_event_type | GET | List event types |

Zone Data Model (Key Properties)

Rachio zones expose rich configuration data that aligns directly with SimplyScapes' per-plant irrigation model:

• customCrop - Vegetation type with name and coefficient (e.g., "Cool Season Grass", coeff 0.8)
• customSoil - Soil type (e.g., "LOAM", "CLAY", "SAND")
• customNozzle - Nozzle type with precipitation rate (e.g., "FIXED_SPRAY_HEAD", 1.5 in/hr)
• customShade - Sun exposure (e.g., "LOTS_OF_SUN", "SOME_SHADE")
• rootZoneDepth - Root depth in inches
• yardAreaSquareFeet - Zone area
• depthOfWater, availableWater, saturatedDepthOfWater - Water metrics
• managementAllowedDepletion - MAD value for scheduling
• slope - Terrain slope data

The zone PUT endpoint at /public/zone supports modifying these properties. This means SimplyScapes could set zone vegetation type, soil, nozzle, and shade to match the design data.

Schedule Data Model

Schedule rules include:

• Zone array with per-zone durations and sort order
• Schedule type (Fixed, Flex Daily, Flex Monthly)
• Weather intelligence sensitivity
• Cycle/soak settings
• Water budget percentage
• Rain delay settings
• Seasonal adjustment

Key limitation: The public API can start, skip, and seasonally adjust existing schedules, but creating new schedules via the API is not clearly documented. The API appears to be primarily read + control (start/stop/adjust) rather than full CRUD for schedule creation. Schedule creation may need to happen through the Rachio app, with the API used to adjust runtimes and trigger runs.

Rate Limits

• 1,700 API calls per day (~1.2 calls/minute)
• Rachio is willing to discuss exceptions for specific use cases
• Webhooks provide a non-polling alternative for status updates

Partner Ecosystem

• Alarm.com is the largest integration partner (requires monitoring company to enable Irrigation Service Package)
• URC Total Control added Rachio integration for professional home automation
• 3 formal partners: 2 technology partners, 1 channel partner
• IFTTT integration with triggers (watering start/stop, any event) and actions (rain delay, skip, stop all, start zone)
• Home Assistant integration using the same public API
• No formal developer partner program or app marketplace

SimplyScapes Feasibility Assessment

| Capability | Feasible? | Notes | |-----------|-----------|-------| | Read zone configuration | Yes | Full zone details including vegetation, soil, nozzle | | Modify zone properties | Yes | PUT /public/zone supports property updates | | Start/stop individual zones | Yes | With duration control | | Adjust schedule runtimes | Yes | Seasonal adjustment (-100% to +100%) | | Create new schedules | Unclear | Not clearly documented in public API | | Push per-plant runtimes | Partial | Can set moisture levels and run zones for specific durations; cannot create per-plant sub-zone schedules | | Real-time status | Yes | Via webhooks (non-polling) | | User onboarding | Manual | User must copy API key from Rachio app |

Verdict: Rachio is the strongest integration candidate. The API provides the right level of zone-level control for SimplyScapes to adjust watering based on plant data. The main gaps are: (1) no OAuth flow for seamless user auth, and (2) schedule creation may be limited. However, the ability to modify zone properties (vegetation, soil, nozzle) and adjust runtimes via seasonal adjustment is sufficient for an MVP integration.

---

1.2 Hunter Hydrawise (Hunter Industries)

Market position: Strong in the professional landscaping market. Hunter Industries is one of the largest irrigation equipment manufacturers globally. Hydrawise is their smart controller platform.

API availability: Two distinct APIs exist:

API v1.5 (REST) -- Personal Use

Documentation: Hydrawise REST API v1.5 PDF | API Info page

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

| Endpoint | Method | Capability | |----------|--------|------------| | statusschedule.php | GET | Current irrigation status and upcoming schedule | | customerdetails.php | GET | Account info and device data | | setzone.php | GET | Start/stop/suspend zones (action, relay_id, duration) |

Authentication: Simple API key passed as query parameter. Generated from Hydrawise account settings.

Critical restriction: "This API is not suitable for commercial applications and is for personal use only." The API Terms of Use explicitly state: "Any commercial use of the APIs must be submitted for prior and written authorization of Hunter Industries."

Capabilities:

• Read controller names, zone names/numbers
• Read time until next run, currently running zones, run time length
• Manual start/stop zones
• Run all stations
• Suspend individual zones or all zones
• Cannot create or modify schedules -- "No provisions exist for managing schedules through third-party integrations"

Local API: Also available for firmware versions below 3.0.0. Provides direct HTTP access on the local network with faster response (no 5-15 second cloud delay) but limited to basic zone control.

API v2 (GraphQL/OAuth2) -- Commercial Path

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

Authentication: OAuth2 with scopes for manual operation, zone remote control, reporting, alerts, and contractor controllers.

Key facts:

• Hydrawise migrated their web app to GraphQL, making it technically more capable
• Designed to handle commercial use cases (irrigation contractors with thousands of devices)
• Access is gated -- Hydrawise "generally does not give open access to the GraphQL API"
• Commercial inquiries should be directed to support@hydrawise.com
• The pydrawise Python library interfaces with this GraphQL API and provides: get_controllers(), get_zones(), start_zone(), and likely more undocumented methods

Terms of use key points:

• Commercial use requires prior written authorization from Hunter Industries
• Cannot use APIs in products competing with Hunter's offerings without written auth
• API key must remain confidential
• Hunter reserves the right to charge for API access in the future
• Hunter reserves the right to restrict call frequency

SimplyScapes Feasibility Assessment

| Capability | Feasible? | Notes | |-----------|-----------|-------| | Read zone configuration | Yes (v1) | Zone names, numbers, next run times | | Modify zone properties | No (v1) | Not available in personal API | | Start/stop zones | Yes (v1) | With duration parameter | | Modify schedules | No (v1) | Explicitly not supported | | Create schedules | No (v1) | Explicitly not supported | | Commercial use | Requires approval | Must contact support@hydrawise.com | | GraphQL full access | Unknown | Gated behind commercial agreement |

Verdict: Hydrawise integration is feasible but requires a formal business relationship with Hunter Industries. The personal REST API is too limited (no schedule modification, personal use only). The GraphQL API is more capable but access requires written commercial authorization. SimplyScapes should pursue a commercial API partnership with Hunter -- the professional landscaper market overlap is strong. This is a business development task, not a technical one.

---

1.3 Rain Bird (Rain Bird Corporation)

Market position: One of the largest irrigation manufacturers globally. Dominant in professional and commercial irrigation. The LNK2 WiFi module upgrades existing Rain Bird controllers (ESP-TM2, ESP-ME3, ESP-RZXe, ESP-LXME2, ESP-LXIVM) for smart connectivity.

API availability: No public developer API for residential controllers. Two paths exist:

Residential: Reverse-Engineered SIP Protocol (pyrainbird)

Library: pyrainbird -- Python library used by Home Assistant

Protocol: Rain Bird Serial Interface Protocol (SIP) -- a proprietary binary protocol communicated over HTTP directly to the LNK2 WiFi module's IP address on the local network.

Authentication: Password-based (LNK2 module password).

Available SIP commands (from sipcommands.yaml):

| Command Code | Operation | |-------------|-----------| | 02 | Get model/version | | 03 | Get available stations | | 05 | Get serial number | | 10/11 | Get/Set current time | | 12/13 | Get/Set current date | | 20 | Retrieve schedule | | 30 | Water budget configuration | | 32 | Seasonal adjustment factors | | 36/37 | Get/Set rain delay | | 38 | Run program manually | | 39 | Run station manually | | 3E | Rain sensor state | | 3F | Get active stations | | 40 | Stop irrigation | | 42 | Advance station | | 48 | Get current irrigation state | | 4B | Stack manual station run |

Critical limitations:

• Local network only -- must be on the same network as the LNK2 module (no cloud API)
• One concurrent connection -- the module can only handle one client at a time; cannot be used simultaneously with the Rain Bird app
• Reverse-engineered -- not sanctioned by Rain Bird; could break with firmware updates
• Limited device testing -- only ESP-TM2 confirmed compatible
• No schedule creation/modification -- can read schedules and run programs, but cannot create or modify watering programs

Commercial: Rain Bird IQ4 Central Control API

Platform: IQ4 -- Rain Bird's commercial central control platform for managing multiple controllers across properties.

API capabilities:

• BMS (Building Management System) integration via REST API
• Retrieves irrigation data from the IQ4 database on demand
• Flow data by site over time periods
• Data can be used for work orders, customer reports, compliance

Access model: Requires an API subscription purchased from Rain Bird's subscriptions page.

Target market: Commercial landscape management, facilities management, not residential.

Recent developments (2026): Rain Bird expanded CirrusPRO (their golf course platform) with Spectrum Technologies and Watertronics integrations for soil data and pump monitoring.

SimplyScapes Feasibility Assessment

| Capability | Feasible? | Notes | |-----------|-----------|-------| | Read zones | Partial | Via pyrainbird (local only, reverse-engineered) | | Modify schedules | No | SIP protocol supports read + manual run only | | Start/stop zones | Yes | Via pyrainbird (local only) | | Cloud API | No | No public cloud API for residential | | Commercial API | Yes (IQ4) | Requires subscription; data retrieval focus | | Push schedules | No | No mechanism to create/modify programs |

Verdict: Rain Bird is the hardest integration target. There is no sanctioned developer API for residential controllers. The reverse-engineered SIP protocol is local-only and fragile. The IQ4 commercial API is data-retrieval focused, not for pushing schedules. SimplyScapes should monitor Rain Bird's API strategy but not prioritize integration unless a commercial partnership can be established. For professional landscapers using Rain Bird controllers, the IQ4 subscription API could provide data integration (reading flow data, generating reports) even if schedule pushing is not feasible.

---

1.4 Orbit B-hyve (Orbit Irrigation)

Market position: Budget-friendly smart controller. B-hyve is popular for price-conscious homeowners.

API availability: No official public API. All integration libraries are reverse-engineered.

Unofficial API Libraries

Node.js: bhyve-api -- bare-bones REST + WebSocket interface Python: pybhyve -- asyncio library for REST and WebSocket APIs MQTT Bridge: bhyve-mqtt -- MQTT gateway to B-hyve API

Architecture: Hybrid REST + WebSocket

• REST API for authentication (email/password -> JWT token) and data retrieval
• WebSocket (WSS) for real-time bidirectional communication with devices
• Many commands require the WebSocket channel; program retrieval is one that does not

Authentication: Email/password credentials -> JWT token

Data available (reverse-engineered):

• Devices (controller info)
• Timelines (programs/schedules)
• Landscapes (smart irrigation data)
• History (watering events)

Critical limitations:

• Entirely reverse-engineered -- "not officially supported or endorsed by Orbit Irrigation Products, LLC"
• No documentation -- API structure discovered via man-in-the-middle traffic analysis
• Can break at any time -- Orbit can change their API without notice
• No developer program -- no path to official support

SimplyScapes Feasibility Assessment

| Capability | Feasible? | Notes | |-----------|-----------|-------| | Read zones/devices | Yes (unofficial) | Via reverse-engineered REST endpoints | | Modify schedules | Unclear | WebSocket commands may support it | | Start/stop zones | Likely | Via WebSocket commands | | Authentication | Fragile | User credentials, JWT -- could change | | Commercial viability | No | No official API, no partnership path |

Verdict: B-hyve integration is technically possible but commercially unviable. Building a product feature on a reverse-engineered, unsanctioned API is too risky. SimplyScapes should not invest here unless Orbit releases an official API or partner program.

---

1.5 OpenSprinkler (Open Source)

Market position: Leading open-source irrigation controller. Available as hardware (OpenSprinkler 3.x) and Raspberry Pi add-on (OSPi). Niche but loyal user base among tech-savvy homeowners and hobbyists.

API availability: Fully open HTTP API documented at opensprinkler.github.io.

Hardware: 8 zones standard, expandable to 200 zones with expansion boards. Supports 24VAC solenoids. OSPi uses Raspberry Pi GPIO pins with shift registers.

API Details

Protocol: HTTP GET requests with JSON responses (not true REST -- uses GET for all operations including writes).

Authentication: MD5 hash of device password passed as pw parameter on every request.

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

| Endpoint | Purpose | Read/Write | |----------|---------|------------| | /jc | Controller variables (time, sensors, status) | Read | | /jo | System options and settings | Read | | /jn | Station names and attributes | Read | | /js | Station status | Read | | /jp | Program data | Read | | /jl | Log data | Read | | /ja | Combined: all of the above in one call | Read | | /db | Diagnostics (no auth required) | Read | | /cv | Modify controller variables (reboot, enable/disable, rain delay) | Write | | /co | Change system options | Write | | /cs | Change station names and attributes | Write | | /cm | Manual station run (open/close zones) | Write | | /cp | Create/modify program | Write | | /dp | Delete program(s) | Write | | /cr | Run-once program | Write | | /mp | Start program manually | Write | | /up | Reorder programs | Write |

Program Creation via API

Programs can be fully created via the /cp endpoint:

/cp?pw=xxx&pid=-1&v=[flags,days,start_times,durations]&name=ProgramName

Program parameters include:

• Flags (weather adjustment enabled/disabled)
• Days of week / interval scheduling
• Multiple start times per program
• Per-station durations
• Date range restrictions (from/to dates)

Weather adjustment: Each program can individually enable/disable automatic weather adjustment. The Zimmerman method calculates watering percentage based on temperature, humidity, and precipitation. However, weather adjustment is per-program, not per-zone.

Station types supported:

• Standard (shift register / GPIO)
• HTTP stations (trigger external HTTP GET commands)
• Remote stations (control zones on other OpenSprinkler units via IP)

SimplyScapes Feasibility Assessment

| Capability | Feasible? | Notes | |-----------|-----------|-------| | Read zones/stations | Yes | Full station names, attributes, status | | Create programs | Yes | Full CRUD via /cp and /dp | | Modify programs | Yes | Update durations, days, start times | | Manual zone control | Yes | /cm with duration | | Weather adjustment | Yes | Per-program (not per-zone) | | Run-once programs | Yes | /cr for ad-hoc schedules | | Authentication | Simple | MD5 password hash | | Stability | Excellent | Open-source, no vendor lock-in risk |

Verdict: OpenSprinkler is the ideal integration target for full schedule control. The API supports everything SimplyScapes needs: read zones, create programs with per-station durations, modify programs, run ad-hoc schedules, and adjust for weather. The user base is smaller but highly technical and likely to be early adopters. The open-source nature eliminates vendor risk. The HTTP station type even enables OpenSprinkler to trigger external APIs, creating bidirectional integration possibilities.

---

1.6 Other Notable Controllers

Yardian Pro

• Apple HomeKit, Alexa, Google Assistant integration
• Home Assistant compatible
• No known public developer API

RainMachine

• Local API available (used by Home Assistant)
• ET-based scheduling built in
• Smaller market share

Netro

• IFTTT integration
• No known public developer API

---

2. Integration Bridges

2.1 IFTTT

Rachio integration is the most developed:

• Triggers: Watering start, watering stop, any device event
• Actions: Rain delay, skip watering, stop all, start zone
• Polling: Every 5 minutes (Pro/Pro+) or hourly (Free)

Limitations: IFTTT is too coarse for per-plant scheduling. It can trigger individual zone starts but cannot set durations or create complex schedules. Useful for simple automations (e.g., "if soil moisture sensor below threshold, start zone 3") but not for pushing calculated irrigation schedules.

Other controllers on IFTTT: Netro has an integration. Hydrawise and Rain Bird do not. B-hyve does not.

Zapier: No direct irrigation controller integrations found. Zapier's ecosystem is focused on business SaaS tools, not IoT/hardware.

2.2 Home Assistant

Home Assistant serves as the most comprehensive integration hub for irrigation controllers. Every major controller has a Home Assistant integration:

| Controller | HA Integration | Protocol Used | Local/Cloud | |-----------|---------------|---------------|-------------| | Rachio | Official | REST API (bearer token) | Cloud | | Hydrawise | Official | GraphQL/OAuth2 (v2 API) | Cloud | | Rain Bird | Official | pyrainbird / SIP protocol | Local | | OpenSprinkler | Community | REST API (HTTP) | Local | | B-hyve | Community (HACS) | REST + WebSocket | Cloud |

Smart Irrigation components:

• HAsmartirrigation -- Calculates watering time based on evapotranspiration (ET), precipitation, and moisture loss. Outputs calculated durations as sensor values that automations can use to control any irrigation integration.
• irrigation_unlimited -- Full irrigation controller component for Home Assistant with zone sequencing, adjustment, and scheduling.

Relevance to SimplyScapes: Home Assistant demonstrates that the technical integration patterns work. However, SimplyScapes should integrate directly with controller APIs rather than requiring users to run Home Assistant as middleware. The HA ecosystem is valuable as a reference implementation and for understanding each controller's protocol quirks.

2.3 Summary of Bridge Options

| Bridge | Per-Plant Scheduling | Schedule Creation | Practical? | |--------|---------------------|-------------------|-----------| | IFTTT | No | No (zone start only) | No | | Zapier | No | No integrations | No | | Home Assistant | Possible (via automations) | Yes (complex setup) | Not for consumers | | Direct API | Yes (controller-dependent) | Yes (Rachio, OpenSprinkler) | Best path |

---

3. Manufacturer Partnership Analysis

3.1 Would Manufacturers Partner?

Rachio -- Likely receptive:

• Already has a public API explicitly for third-party integrations
• Active community forum discussing API usage
• Existing partnerships (Alarm.com, URC, IFTTT)
• API documentation encourages building "mashups" with "infinite flexibility"
• Willing to discuss rate limit exceptions
• Gap: No formal developer partner program or app marketplace yet
• Risk: Rachio could view SimplyScapes' plant intelligence layer as additive to their product rather than competitive

Hunter Hydrawise -- Possible but gated:

• Commercial API access requires written authorization
• Terms explicitly prohibit competitive use without permission
• Strong professional landscaper customer base overlaps with SimplyScapes
• Hunter is a hardware company; software intelligence partnerships could be attractive
• Approach: Position SimplyScapes as driving demand for Hydrawise hardware, not competing with it

Rain Bird -- Difficult for residential, possible for commercial:

• No public API for residential controllers
• IQ4 commercial platform has an API subscription ($)
• Recently expanding integrations (Spectrum, Watertronics for CirrusPRO)
• Very large, traditional company -- slower to open up
• Approach: Target the IQ4/commercial market where API access exists; pursue enterprise partnership

Orbit B-hyve -- Not viable:

• No public API, no developer program, no partnership path
• Budget market positioning suggests limited interest in premium integrations

3.2 Successful Third-Party Integration Examples

| Integration | Controller | What It Does | |------------|-----------|--------------| | Alarm.com + Rachio | Rachio | View sprinkler status, start zones, run schedules from security app | | Alarm.com + Hydrawise | Hydrawise | Similar zone control within Alarm.com platform | | URC Total Control + Rachio | Rachio | Professional home automation control of irrigation | | Dew for Hydrawise | Hydrawise | Third-party app built on GraphQL API (Anomaly software) | | HAsmartirrigation | Multiple | ET-based calculated watering times pushing to any HA-connected controller |

These examples demonstrate that controller manufacturers (especially Rachio and Hunter) are receptive to third-party integrations that add value to their hardware ecosystem.

---

4. Capability Matrix

| Capability | Rachio | Hydrawise (v1) | Hydrawise (v2) | Rain Bird | B-hyve | OpenSprinkler | |-----------|--------|----------------|-----------------|-----------|--------|---------------| | Read zones | Yes | Yes | Yes | Partial (local) | Yes (unofficial) | Yes | | Read schedules | Yes | Yes | Yes | Partial (local) | Yes (unofficial) | Yes | | Modify zone properties | Yes | No | Unknown | No | Unknown | Yes (names/attrs) | | Create schedules | Unclear | No | Unknown | No | Unknown | Yes | | Modify schedule runtimes | Yes (seasonal adj) | No | Unknown | No (water budget only) | Unknown | Yes | | Start/stop zones | Yes | Yes | Yes | Yes (local) | Likely | Yes | | Run-once programs | Yes (multi-zone) | No | Unknown | Yes (local) | Unknown | Yes | | Push per-zone durations | Yes (start_multiple) | No | Unknown | No | Unknown | Yes | | Real-time status | Yes (webhooks) | Yes | Yes | Partial (local) | Yes (WebSocket) | Yes (polling) | | Weather data | Yes (forecast API) | No | Unknown | No | No | Yes (Zimmerman) | | Auth model | Bearer token | API key (query) | OAuth2 | Password (local) | JWT (email/pwd) | MD5 hash | | Commercial use | Yes (public API) | No (personal only) | Requires approval | No public API | No official API | Yes (open source) | | API stability | High (official) | Medium (official) | Medium (gated) | Low (reverse-eng) | Low (reverse-eng) | High (open source) | | Rate limit | 1,700/day | Unknown | Unknown | N/A (local) | Unknown | None (local) | | Cloud/Local | Cloud | Cloud | Cloud | Local only | Cloud | Local (+ cloud opt.) |

---

5. Recommended Integration Strategy

Phase 1: MVP (Rachio + OpenSprinkler)

Rachio integration (3-4 weeks):

1. User provides their Rachio API key (manual copy from app)
2. SimplyScapes reads zone configuration via GET /public/device/:id
3. Map SimplyScapes plant/zone data to Rachio zone properties (vegetation type, soil, nozzle, shade)
4. Push zone property updates via PUT /public/zone to align Rachio's scheduling intelligence with actual plant data
5. Use seasonal_adjustment to dynamically modify runtimes based on SimplyScapes' ET calculations
6. Use start_multiple to push calculated per-zone runtimes as run-once events
7. Register webhooks for watering event notifications

OpenSprinkler integration (2-3 weeks):

1. User provides OpenSprinkler IP address and password
2. Read all station data via /ja
3. Create programs via /cp with per-station durations calculated by SimplyScapes
4. Modify programs dynamically as plants establish and seasons change
5. Use /cr for ad-hoc run-once programs when conditions require

Phase 2: Commercial Expansion

Hydrawise commercial partnership (business development, 2-6 months):

1. Contact support@hydrawise.com for commercial API authorization
2. Position integration as driving Hydrawise hardware adoption by landscape professionals
3. If approved, build GraphQL integration with OAuth2 user authentication
4. Target professional landscapers managing multiple properties

Rain Bird IQ4 data integration (conditional on partnership):

1. Evaluate IQ4 API subscription for commercial landscape market
2. Focus on data retrieval (flow data, compliance reporting) rather than schedule pushing
3. Explore enterprise partnership for deeper integration

Phase 3: Scale

• Build OAuth2 flow with Rachio (if they add support for third-party auth)
• Evaluate new controllers entering the market
• Consider building a SimplyScapes-branded OpenSprinkler integration kit

---

6. Technical Architecture Recommendations

API Abstraction Layer

SimplyScapes should build a controller abstraction layer that normalizes the different API patterns:

IrrigationController (interface)
  ├── getZones() -> Zone[]
  ├── getSchedules() -> Schedule[]
  ├── setZoneProperties(zoneId, props) -> void
  ├── pushSchedule(schedule) -> void
  ├── runZone(zoneId, durationMinutes) -> void
  ├── runMultipleZones(zoneRuns[]) -> void
  ├── adjustRuntime(scheduleId, adjustmentPct) -> void
  ├── getStatus() -> ControllerStatus
  └── registerWebhook(url, events) -> void

Each controller integration implements this interface with controller-specific API calls. This insulates the core scheduling logic from controller-specific details.

Authentication Storage

• Rachio: Store bearer token (encrypted at rest)
• OpenSprinkler: Store IP address + password hash (encrypted at rest)
• Hydrawise: OAuth2 tokens with refresh (if commercial access granted)
• Never store user credentials in plaintext

Sync Strategy

• Push model: Calculate schedules server-side, push to controllers when conditions change
• Webhook-driven updates: Use Rachio webhooks to confirm execution and detect manual overrides
• Polling fallback: For controllers without webhooks (OpenSprinkler), poll status at reasonable intervals
• Conflict resolution: If user manually adjusts schedule on controller, detect via status polling and notify user of divergence

---

7. Key Documentation URLs

| Resource | URL | |----------|-----| | Rachio API docs | https://rachio.readme.io/ | | Rachio API auth | https://rachio.readme.io/v1.0/reference/authentication | | Rachio data objects | https://rachio.readme.io/reference/data-objects | | Rachio Postman collection | https://www.postman.com/rachio/rachio-public-workspace/ | | Rachio GitHub (QA testing) | https://github.com/Rachio/api-qa-testing | | Hydrawise REST API v1.5 (PDF) | https://www.hunterirrigation.com/sites/default/files/2024-03/Hydrawise%20REST%20API.pdf | | Hydrawise API info page | https://www.hunterirrigation.com/en-metric/support/hydrawise-api-information | | Hydrawise API terms | https://www.hunterirrigation.com/support/hydrawise-api-terms-use | | Hydrawise GraphQL explorer | https://app.hydrawise.com/api/v2/graph/explore | | pydrawise (Python GraphQL) | https://github.com/dknowles2/pydrawise | | pyrainbird (Rain Bird Python) | https://github.com/allenporter/pyrainbird | | Rain Bird SIP commands | https://github.com/allenporter/pyrainbird/blob/main/pyrainbird/resources/sipcommands.yaml | | Rain Bird IQ4 | https://www.rainbird.com/usa/iq4-main | | Rain Bird IQ4 API brochure | https://www.rainbird.com/sites/default/files/media/documents/2023-10/iq4_api_brochure.pdf | | bhyve-api (Node.js) | https://github.com/billchurch/bhyve-api | | pybhyve (Python) | https://github.com/sebr/pybhyve | | OpenSprinkler API docs | https://opensprinkler.github.io/OpenSprinkler-Firmware/2.2.1/221_4_api/ | | OpenSprinkler firmware | https://github.com/OpenSprinkler/OpenSprinkler-Firmware | | OpenSprinkler Weather | https://github.com/OpenSprinkler/OpenSprinkler-Weather | | HAsmartirrigation | https://github.com/jeroenterheerdt/HAsmartirrigation | | IFTTT Rachio | https://ifttt.com/rachio_iro | | HA Rachio integration | https://www.home-assistant.io/integrations/rachio/ | | HA Hydrawise integration | https://www.home-assistant.io/integrations/hydrawise/ | | HA Rain Bird integration | https://www.home-assistant.io/integrations/rainbird/ |

---

8. Risks and Mitigations

| Risk | Severity | Mitigation | |------|----------|------------| | Rachio removes or restricts public API | Medium | Establish partnership relationship; build OpenSprinkler as backup | | Rate limit (1,700/day) insufficient for multi-user platform | High | Use webhooks to minimize polling; discuss enterprise rate limits with Rachio | | No OAuth flow makes onboarding friction-heavy | High | Build clear step-by-step onboarding wizard; lobby Rachio for OAuth support | | Reverse-engineered APIs break (Rain Bird, B-hyve) | High | Do not build production features on reverse-engineered APIs | | Hunter denies commercial API access | Medium | Continue with Rachio + OpenSprinkler; revisit as SimplyScapes scales | | Users expect per-plant zone control but controllers only support per-zone | Medium | Clearly communicate zone-level granularity; recommend zone design that groups similar plants | | Schedule creation not available via Rachio API | Medium | Use seasonal adjustment + run-once as workaround; guide users to create base schedules in Rachio app |

---

9. Conclusions

1. Per-plant schedule pushing to smart controllers is feasible today -- with the right controller. Rachio and OpenSprinkler provide sufficient API access for SimplyScapes to calculate irrigation schedules based on plant data and push them to hardware.

2. The integration value proposition is strong. No existing product bridges landscape design data (what plants are where, their water requirements, soil type) with irrigation controller scheduling. SimplyScapes is uniquely positioned to fill this gap.

3. Start with Rachio (largest market) and OpenSprinkler (deepest control). These two cover the consumer market (Rachio) and the tech-forward/professional market (OpenSprinkler) without requiring any business development effort.

4. Pursue Hydrawise commercial access as a business development priority. Hunter's professional landscaper base is SimplyScapes' core audience. A partnership here would be strategically significant.

5. Do not build on reverse-engineered APIs. Rain Bird (pyrainbird) and B-hyve (bhyve-api) are technically interesting but commercially unviable for a production product.

6. The Rachio API's zone data model is remarkably well-suited. The customCrop, customSoil, customNozzle, and customShade properties map directly to SimplyScapes' plant and irrigation data. This is not a coincidence -- Rachio designed their zones around the same irrigation science (ET, MAD, root depth) that SimplyScapes uses.

7. Authentication UX is the biggest near-term challenge. Without an OAuth flow, users must manually copy API keys. This creates onboarding friction that may limit adoption. Solving this through clear UX and potentially lobbying Rachio for OAuth support should be a priority.

Establishment & Growth Lifecycle Science

ID: SS-RB-2026-002 | Date: 2026-03-01 | Status: draft Domain: Irrigation Management / Establishment & Growth Science Related: plant-specific-drip-irrigation-intelligence v1 report (historical reference, superseded by v2)

TL;DR

Building a system that generates evolving multi-year watering schedules requires deep knowledge of plant establishment science. This research compiles published establishment tapering schedules from 10+ university extension services across every major US climate region, ornamental plant growth rate databases, planting method effects on establishment, and phase transition triggers. Key findings: (1) establishment timelines are well-modeled by the formula "X months per inch of trunk caliper," with X varying by hardiness zone (3 months in zones 10-11, up to 12 months in zones 2-6); (2) the USDA Forest Service Urban Tree Database provides allometric equations for 171 species across 16 US climate zones that predict crown diameter from age; (3) all major extension services converge on a 3-phase tapering pattern (daily -> every few days -> weekly) with duration scaled by plant size; (4) planting method (container vs B&B vs bare root) and season significantly affect establishment duration; and (5) establishment completion is best determined by resumption of pre-transplant twig growth rates, not by a fixed calendar date.

---

1. Published Establishment Tapering Schedules

1.1 UF/IFAS (Edward Gilman) — The Most Comprehensive Source

Gilman's research at UF/IFAS provides the most granular, research-backed establishment data in the literature. His work covers both trees and shrubs with separate schedules.

Tree Establishment Timeline by Hardiness Zone:

| Hardiness Zone | Months Per Inch of Trunk Caliper | |----------------|----------------------------------| | Zones 10-11 (South FL, Hawaii) | 3 months | | Zones 8-9 (Gulf Coast, Southeast) | 4 months | | Zones 6-8 (Mid-Atlantic, Upper South) | 8 months | | Zones 2-6 (Northern US) | 12 months |

Tree Irrigation Schedule by Nursery Stock Size (Vigor Schedule):

| Caliper at Planting | Phase 1: Daily | Phase 2: Every Other Day | Phase 3: Weekly Until Established | |---------------------|----------------|--------------------------|-----------------------------------| | < 2 inch | 2 weeks | 2 months | Until established | | 2-4 inch | 1 month | 3 months | Until established | | > 4 inch | 6 weeks | 5 months | Until established |

Survival-Only Schedule (Minimum Irrigation):

| Caliper | Minimum Frequency | Duration | |---------|-------------------|----------| | < 2 inch | Twice weekly | 2-3 months | | 2-4 inch | Twice weekly | 3-4 months | | > 4 inch | Twice weekly | 4-5 months |

Water Volume Per Irrigation Event:

• Cool climates: 1-2 gallons per inch of trunk caliper
• Warm climates: 2-3 gallons per inch of trunk caliper
• Applied directly over the root ball only

Desert Climate Post-Establishment Schedule:

• Years 1-5: Twice monthly (warm season), once monthly (winter)
• Years 5-7: Every three weeks (warm season), every six weeks (winter)
• After year 7: Drought-tolerant trees should survive on natural rainfall

Key Gilman Principle: "You cannot make up for lack of frequency by applying large volumes of water infrequently."

Source: UF/IFAS Landscape Plants — Irrigation Management After Planting; UF/IFAS Irrigation Research

Shrub Establishment (UF/IFAS Gardening Solutions — 6-year research project):

| Region | Container Size | Frequency | Volume | Establishment Period | |--------|---------------|-----------|--------|---------------------| | North of Orlando | 3-gallon | Every 8 days | 1 gallon | 20-28 weeks | | South of Orlando | 3-gallon | Every 4 days | 1 gallon | 20-28 weeks |

Key findings from the shrub research:

• Applying more than 1 gallon per irrigation event does NOT increase survival or growth
• More frequent watering (every 4 days vs. every 8 days) produces more vigorous growth but does not improve survival rates
• Establishment defined as when roots can sustain plant without supplemental irrigation (20-28 weeks)

Source: UF/IFAS Gardening Solutions — Watering to Establish Shrubs

---

1.2 Colorado State University Extension (GardenNotes #635)

CSU provides one of the clearest size-differentiated schedules, with explicit caliper-to-establishment-time correlations:

Caliper, Water Volume, and Establishment Duration:

| Trunk Caliper | Water Per Irrigation | Establishment Time | |---------------|---------------------|-------------------| | 1 inch | 1-1.5 gallons | 12-18 months | | 2 inches | 2-3 gallons | 2-3 years | | 3 inches | 3-4.5 gallons | 3-4.5 years | | 4 inches | 4-6 gallons | 4-6 years | | 5 inches | 5-7.5 gallons | 5-7.5 years | | 6 inches | 6-9 gallons | 6-9 years |

Frequency by Size:

| Caliper | Phase 1: Daily | Phase 2: Every 2-3 Days | Phase 3: Weekly | |---------|----------------|-------------------------|-----------------| | < 2 inch | 2 weeks | 2 months | Until established | | 2-4 inch | 4 weeks | 3 months | Until established | | > 4 inch | 6 weeks | 5 months | Until established |

Winter Watering (Colorado-specific): Water newly planted trees monthly on sunny days when temperature is above 40 degrees F and the ground is not frozen.

Source: CSU Extension — Care of Recently Planted Trees; GardenNotes #635 PDF

---

1.3 University of Minnesota Extension

UMN provides nearly identical data to CSU (same caliper table), which suggests these represent a shared body of research or consensus:

Frequency Schedule (same 3-phase pattern):

• Weeks 1-2: Water daily
• Weeks 3-12: Water every 2-3 days
• After 12 weeks: Water weekly until established

Establishment duration: Same caliper-based table as CSU (1.5 years per inch of caliper)

Shrub-specific guidance:

• Volume: 1/4 to 1/3 of the nursery container volume per watering event
• Establishment: When root spread equals canopy spread (typically 2+ growing seasons in Minnesota)

Source: UMN Extension — Watering Newly Planted Trees and Shrubs

---

1.4 AMWUA (Arizona Municipal Water Users Association) — Desert Southwest

AMWUA provides the most detailed week-by-week tapering schedule with seasonal adjustment:

New Plant Establishment Schedule:

| Week | Summer Frequency | Fall/Winter/Spring Frequency | |------|-----------------|------------------------------| | 1-2 | Every 1-2 days | Every 3-4 days | | 3-4 | Every 3-4 days | Every 6-7 days | | 5-6 | Every 4-6 days | Every 7-10 days | | 7-8 | Every 7 days | Every 10-14 days | | After week 8 | Gradually extend intervals | Gradually extend intervals |

Post-Establishment Timelines:

• Shrubs: ~1 year to establish
• Trees: ~3 years to establish
• After establishment: Allow slight drought between waterings to build drought tolerance

Each irrigation should wet the root ball and 1-2 inches of surrounding soil.

After the eighth week, drip emitters should be repositioned closer to the outer edge of the root ball as roots expand outward.

Source: AMWUA Watering Schedules

---

1.5 Southern Nevada Water Authority (SNWA)

SNWA uses an identical 8-week tapering schedule to AMWUA (reflecting the shared desert climate context):

• Same week-by-week frequencies as AMWUA table above
• Special exemption: New landscapes may be watered daily for up to 14 days (once per calendar year)
• After week 8: Check plants for proper drainage and signs of stress, water based on need

Source: SNWA — How and When to Water

---

1.6 University of Arizona Cooperative Extension

Provides depth-based guidance for established plants by plant type:

| Plant Type | Watering Depth | Root Zone | |------------|---------------|-----------| | Annuals/Perennials | 12 inches | 6-12 inches | | Shrubs | 24 inches | 12-24 inches | | Trees | 36 inches | 18-36 inches |

Seasonal multiplier: Plants use 3-5x more water during hot, dry seasons vs. winter.

Soil probe method: Water when soil probe will not penetrate more than 3-4 inches. Mulch (3-4 inch layer) significantly reduces watering frequency.

Establishment timelines match AMWUA: 1 year for shrubs, 3 years for trees.

Source: UA Cooperative Extension — Watering Trees and Shrubs

---

1.7 Portland, Oregon (City of Portland)

Represents the Pacific Northwest perspective:

First 2-3 years: 15-30 gallons per tree weekly during dry season (May-October) Years 3-5: Once monthly watering After 5 years: Full establishment — trees survive on natural rainfall (in PNW climate)

Key note: Portland defines establishment as a 5-year process, longer than most other sources. This reflects the PNW's wet winters and dry summers, where trees must develop deep enough roots to survive the summer dry season.

November-April: No watering needed during rainy season.

Source: Portland.gov — Tree Establishment Care

---

1.8 Saving Water Partnership (Seattle/Pacific NW)

Year 1: Daily for first 2 weeks, then 2-3 times per week through first fall rains Years 2-3: Water deeply 1-2 times per week After Year 3: Drought-tolerant plants may need no supplemental water; others 1-2 times per month

Source: Saving Water Partnership — How to Water New Plants

---

1.9 NYC Department of Transportation

NYC specifies formal establishment periods in municipal contracts:

| Plant Type | Establishment Period | Watering Requirement | |------------|---------------------|---------------------| | Trees | 24 months | 15-20 gallons weekly, May-October | | Understory (shrubs, perennials, groundcovers) | 18 months | Per standard specs |

Caliper-based rule: 10 gallons per caliper inch per week (e.g., 2.5-3 inch tree = 25-30 gallons/week).

Planting windows: March 1-May 15, October 1-December 15 (no summer planting, no frozen ground).

Source: NYC Street Design Manual — Plant Installation & Establishment

---

1.10 Purdue Extension (Midwest)

5-plus-5 rule: Apply 5 gallons of water plus 5 gallons per inch of trunk diameter. Example: a 4-inch tree needs ~25 gallons per watering event.

Source: Purdue Extension FNR-433-W — Tree Installation: Process and Practices

---

1.11 Perennial and Groundcover Establishment

Perennials and groundcovers have shorter establishment timelines but less formally documented schedules:

General consensus across sources:

• Daily watering for first 2 weeks
• Every other day for weeks 3-4
• 2-3 times per week for first 2-3 months
• Weekly through remainder of first year
• After 1 year: Established (most perennials)
• After 4-6 weeks: Can transition to automated irrigation (depending on species and season)

Duration to establishment by plant type:

| Plant Type | Typical Establishment Period | |------------|----------------------------| | Annual | 4-6 weeks | | Perennial (1-gallon) | 6-12 months | | Groundcover | 6-12 months | | Shrub (3-gallon) | 20-28 weeks (FL research) to 1-2 years | | Small tree (< 2" cal) | 12-18 months | | Medium tree (2-4" cal) | 2-4 years | | Large tree (> 4" cal) | 4-9+ years |

---

1.12 Consolidated Tapering Model

Across all sources, the establishment irrigation pattern converges on a 3-phase model:

Phase 1 — Frequent (Root Ball Hydration):

• Duration: 2-6 weeks (scaled by caliper/plant size)
• Frequency: Daily to every other day
• Volume: Applied directly to root ball
• Purpose: Keep root ball moist while initial root regeneration occurs

Phase 2 — Moderate (Root Expansion):

• Duration: 2-5 months (scaled by caliper/plant size)
• Frequency: Every 2-3 days
• Volume: Root ball plus 1-2 inches of surrounding soil
• Purpose: Encourage roots to grow into native soil

Phase 3 — Infrequent (Root Establishment):

• Duration: Until established (months to years depending on size and climate)
• Frequency: Weekly (summer), monthly (winter in cold climates)
• Volume: Deep watering to full root zone depth
• Purpose: Drive deep root development; begin drought-tolerance training

Phase 4 — Mature (Post-Establishment):

• Frequency: As needed based on ET and rainfall
• Volume: Full root zone watering (2-3x dripline)
• Purpose: Maintain health; adjust for seasonal demand

---

2. Ornamental Plant Growth Rate Databases

2.1 USDA Forest Service Urban Tree Database (GTR-253)

The most comprehensive growth database for urban landscape trees.

Overview:

• 14 years of data collection (1998-2012)
• 17 cities across 13 states
• 14,000+ trees measured
• 171 distinct species
• 16 US climate zones
• 365 sets of allometric equations (8 equations per species per climate zone)
• Nearly 2,600 regionally specific equations total

Equation Chain:

1. Tree age -> predicted DBH (diameter at breast height)
2. DBH -> predicted tree height
3. DBH -> predicted crown diameter
4. DBH -> predicted crown height
5. DBH -> predicted leaf area
6. (Reverse: crown diameter -> predicted DBH for remote sensing)

Climate Zones Covered: Aggregated from 45 Sunset climate zones into 16 zones, each with a reference city where data were collected. States represented: Arizona, California, Colorado, Florida, Hawaii, Idaho, Indiana, Minnesota, New Mexico, New York, North Carolina, Oregon, South Carolina.

Key Finding — Growth Varies Dramatically by Region: Green ash in Fort Collins, CO grows to 7m taller after 30 years than the same species 75km away in Cheyenne, WY. Fort Collins trees produce ecosystem services worth $201,000 over 40 years vs. $66,000 for Cheyenne trees. This underscores why regional specificity matters for growth prediction.

Data Access: Raw data, growth equations, coefficients, and application guides available at the USDA Forest Service Research Data Archive (RDS-2016-0005). Published as PSW-GTR-253 by McPherson, van Doorn, and Peper (2016).

Source: USDA Forest Service — Urban Tree Database; Ag Data Commons

2.2 i-Tree Tools

i-Tree Eco and i-Tree Streets use the reference city growth equations from GTR-253 as their foundation. These tools calculate ecosystem services (carbon sequestration, air quality, stormwater interception) from tree size predictions.

Relevance to SimplyScapes: The same allometric equations that predict ecosystem services can predict canopy size over time, which is directly needed for:

• Adjusting emitter placement (move toward expanding dripline)
• Calculating shading effects (microclimate factor Kmc)
• Predicting when to add more emitters
• Estimating root zone expansion

Source: ISA — Urban Tree Growth Modeling

2.3 ANSI Z60.1 — Nursery Stock Size Standards

ANSI Z60.1 (updated to Z60.2 in April 2025) defines standardized plant sizes for commercial transactions:

Shade Tree Caliper Size Classes with Root Ball Minimums:

| Trunk Caliper | Field-Grown Root Ball Dia. | Fabric Container Dia. | Container Size | |---------------|---------------------------|----------------------|----------------| | 1 inch | 16 inches | 12 inches | 5 gallon | | 2 inches | 24 inches | 18 inches | 20 gallon | | 3 inches | 32 inches | 20 inches | 45 gallon | | 4 inches | 42 inches | 30 inches | 95 gallon | | 5 inches | 54 inches | 36 inches | 95 gallon |

Measurement Standards:

• Caliper measured 6 inches from ground (< 4 inch caliper)
• Caliper measured 12 inches from ground (>= 4 inch caliper)
• Standard defines height-to-caliper ratios, minimum branch counts, and container class relationships

Relevance to SimplyScapes: ANSI Z60.1 defines the "starting state" of a newly planted tree. When a user specifies a 2-inch caliper tree, the system knows the root ball is ~24 inches diameter, which determines initial emitter placement distance and initial watering volume.

Source: UF/IFAS — Root Ball Size Standards; AmericanHort — ANSI Z60.1

2.4 Growth Rate Classifications

Industry standard growth rate categories:

| Category | Height Growth Per Year | Examples | |----------|----------------------|----------| | Slow | < 12 inches | Most oaks, Japanese maple, dogwood | | Medium/Moderate | 13-24 inches | Red maple, zelkova, crape myrtle | | Fast | 25+ inches | Hybrid poplar (5-8 ft/yr), willow (3-8 ft/yr) |

These categories are widely used in plant databases and nursery catalogs but are imprecise for irrigation scheduling. The USDA Urban Tree Database allometric equations provide much more specific, regionally-adjusted predictions.

2.5 WUCOLS — Species-Level Water Use (Recap)

WUCOLS V contains 4,100+ taxa across 6 California climate zones. While primarily used for established plant water needs (Section 4.2 of v1 report), WUCOLS provides the species factor (Ks) that drives the landscape coefficient calculation at every lifecycle stage.

Source: UC Davis — WUCOLS

---

3. Establishment Variation by Planting Method and Season

3.1 Container vs. Balled-and-Burlapped vs. Bare Root

| Factor | Container | Balled & Burlapped (B&B) | Bare Root | |--------|-----------|--------------------------|-----------| | Root system at planting | 100% retained | ~5% retained (95%+ lost) | Variable (roots exposed) | | Fine root density | High (more fine roots than B&B) | Moderate | Low initially | | Drought sensitivity after planting | HIGH — roots are very sensitive to drying | Moderate — field-hardened roots | Low (planted during dormancy) | | Watering frequency needed | Most frequent early on | Moderate | Least frequent (dormant at planting) | | Establishment speed | Slower than expected (root defects, circling) | Standard | Often fastest (roots grow outward immediately in spring) | | Stability at 3 years | Lower (less well-anchored) | Higher | Variable | | Root defect risk | HIGH — circling, girdling roots common | Low | Low | | Optimal root treatment | Root shaving (remove outer 3-6cm) | Remove burlap/wire | Hydrogel dip |

Key Finding (Gilman): Container-grown trees take longer to establish than field-grown trees, despite retaining 100% of their root system. This is because container roots are often defective (circling, kinked) and the growing media dries out faster than native soil. Container trees are "more sensitive to lack of water after planting than hardened-off field-grown or bare-root trees."

Key Finding (ISA): Multiple studies found "no difference between survival and growth of bare root vs. balled and burlapped trees." Bare-root trees performed best when roots were dipped in absorbent gel prior to planting.

Key Finding (Watson): Container trees were less stable (less well-anchored) three years after planting than field-nursery transplants.

Sources: UF/IFAS — Selecting Trees: More Comparisons; ISA — Growth of B&B vs. Bare-Root Trees in Oklahoma

3.2 Seasonal Planting Effects

| Planting Season | Root Growth Advantage | Establishment Effect | Irrigation Requirement | |----------------|----------------------|---------------------|------------------------| | Fall (temperate zones) | Roots grow slowly even in cool soils (above 42-45 deg F) | Extra months of root growth before first summer stress | Irrigate until leaf drop; resume in spring | | Spring | Immediate root growth with warming soil | Standard establishment timeline | Full schedule from day one | | Summer | Roots active but heat-stressed | Longest establishment; highest mortality risk | Most intensive watering needed | | Winter (mild climates) | Roots grow in mild winter soils | Good for zones 8-11; excellent for B&B | Reduced frequency (cool, often rainy) |

Fall Planting Advantage (for temperate zones): Trees planted in fall develop roots at a slow rate even at low temperatures (42-45 deg F). By spring, they have several months of root growth head start before summer heat stress. However, in zones 2-5, the ground freezes too early for meaningful fall root growth, making spring planting preferable.

Gilman's Guidance on Seasonal Irrigation Adjustments:

• Spring/summer plantings in cooler zones: Discontinue irrigation once fall color begins
• Fall plantings: Continue irrigating until deciduous foliage drops from trees in the region
• Winter plantings (mild climates): Irrigate as needed through establishment

Sources: CSU Extension; WVU Extension — Fall vs Spring Planting

3.3 Root Ball Size Effects on Watering Needs

Industry standard root ball ratio: 10-12 inches of ball diameter per 1 inch of caliper.

Root loss at harvest:

• Field-harvested trees lose 95-98% of their root system regardless of tree size
• Roots of both small and large trees regenerate at approximately the same rate: ~18 inches of lateral growth per year (Watson, 1985)
• Therefore, larger trees take proportionally longer to reestablish because more root volume must be replaced

Watson's Root Regeneration Model:

| Caliper | Root Ball Dia. | Years to Replace Root System | |---------|---------------|------------------------------| | 1 inch | ~12 inches | < 2 years | | 2 inches | ~24 inches | ~3 years | | 3 inches | ~32 inches | ~4.5 years | | 4 inches | ~42 inches | ~6 years |

Critical implication for SimplyScapes: A 2-inch caliper tree planted from a 24-inch root ball starts with roots confined to a 24-inch diameter zone. At 18 inches of lateral root growth per year, roots reach ~5 feet from trunk after 2 years, approximately matching the canopy spread of a healthy young tree. This root-spread-equals-canopy-spread milestone is the standard definition of establishment (UMN Extension).

Sources: Watson — Tree Size Affects Root Regeneration; Watson & Himelick — Influence of Tree Size on Transplant Establishment

---

4. Phase Transition Triggers

4.1 How to Determine When a Plant is Established

The scientific literature identifies several measurable indicators of establishment completion:

Primary Indicators:

| Indicator | Measurement | Threshold | |-----------|-------------|-----------| | Twig extension growth | Measure annual terminal shoot growth | Returns to pre-transplant rate | | Root spread ratio | Dig/probe to assess root extent | Root spread equals canopy spread | | Shoot-to-root ratio | Calculated from growth measurements | Restored to pre-transplant ratio | | Trunk diameter growth | Annual caliper increase | Consistent year-over-year increase |

Twig Extension Growth (Most Practical Indicator):

Struve (2009) found that twig growth was significantly reduced during the first 3 years after transplanting for all species tested. Annual twig growth equaled or exceeded pre-transplant rates by the fifth season for most species (Norway maple recovered faster). This makes twig extension the most accessible visual indicator of establishment: when annual twig growth recovers, the tree is established.

Root Spread = Canopy Spread (Standard Definition):

UMN Extension defines establishment as the point when root spread equals the spread of the above-ground canopy. This typically occurs at approximately 1.5 years per inch of caliper (in northern climates) or faster in warmer climates.

Other Scientific Measures (Less Practical for Consumer Use):

• Xylem water potentials returning to pre-transplant levels
• Photosynthetic rates matching pre-transplant rates
• Leaf area matching predicted values for species/size

Sources: Struve 2009 — Tree Establishment: A Review; UMN Extension

4.2 How Extension Services Recommend Determining When to Reduce Watering

Extension services provide practical (non-scientific) guidance for homeowners:

Time-Based Triggers (Most Common Approach):

• CSU, UMN: Follow the caliper-based table (1-1.5 years per inch of caliper)
• AMWUA, SNWA: Follow 8-week tapering schedule, then monitor
• Portland: 2-3 years intensive, then 2 more years of monthly watering
• NYC: 24 months for trees, 18 months for understory

Visual Triggers:

• Consistent new leaf growth and normal leaf color
• Trunk flare visible (proper planting depth)
• Annual twig growth increasing year over year
• No wilting during normal warm weather (without supplemental watering)
• Leaves correct color for season (green spring/summer, color change in fall)

Soil-Based Triggers:

• Soil probe method: Water when probe won't penetrate past 3-4 inches (UA Extension)
• Feel method: Squeeze soil from root zone — should hold together without dripping
• Soil dry to 6-9 inches depth = time to water (UMN for established plants)

Growth-Based Triggers:

• Trunk expanding in thickness each year (measurable with tape)
• Canopy spreading outward (new branches extending)
• Root suckers or surface roots visible at dripline distance

4.3 Practical Phase Transition Model for Software

Based on the research, a software system could implement phase transitions using the following logic:

Phase 1 -> Phase 2 Transition:

• Trigger: Calendar-based (2-6 weeks after planting, scaled by caliper)
• Confidence: High — nearly universal agreement across sources

Phase 2 -> Phase 3 Transition:

• Trigger: Calendar-based (2-5 months after planting, scaled by caliper)
• Confidence: High — well-documented across sources

Phase 3 -> Phase 4 (Established) Transition:

• Primary trigger: Calendar-based (months-per-inch-of-caliper formula, adjusted for hardiness zone)
• Secondary triggers (if user provides feedback): visual confirmation of new growth, no wilting without supplemental water
• Confidence: Moderate — the formula is well-supported but actual establishment varies by species, site conditions, and care quality

Recommended Formula:

establishment_months = caliper_inches * months_per_inch_factor

where months_per_inch_factor =
  3   for hardiness zones 10-11
  4   for hardiness zones 8-9
  8   for hardiness zones 6-8
  12  for hardiness zones 2-6

Planting Method Adjustment:

• Container-grown: multiply by 1.2 (slower establishment due to root defects)
• B&B: multiply by 1.0 (baseline)
• Bare root: multiply by 0.9 (faster establishment when planted during dormancy)

Season Adjustment:

• Spring planting: multiply by 1.0 (baseline)
• Fall planting (zones 6+): multiply by 0.85 (head start on root growth)
• Summer planting: multiply by 1.3 (stress delays establishment)
• Winter planting (zones 8+): multiply by 0.9 (mild conditions favor root growth)

---

5. Key Data Gaps and Research Needs

5.1 Species-Specific Establishment Data

Gilman's most detailed research was conducted on live oak (Quercus virginiana). He explicitly acknowledges the absence of data on irrigation requirements for most other species. The caliper-based formulas are general guidelines, not species-specific prescriptions.

Gap for SimplyScapes: The system should use the general caliper formula as default but flag high-confidence species-specific adjustments where data exists (e.g., known drought-tolerant species establish faster; known moisture-sensitive species need longer Phase 1).

5.2 Shrub and Perennial Growth Prediction

The USDA Urban Tree Database covers only trees. There is no equivalent database for shrub or perennial growth rates in landscape settings. Nursery catalogs provide mature size ranges but not year-by-year growth curves.

Gap for SimplyScapes: Shrub irrigation scheduling must rely on:

• Growth rate category (slow/medium/fast) as a proxy
• Container size at planting as starting point
• General establishment period (20-28 weeks for 3-gallon shrubs in warm climates, 1-2 years in cold climates)

5.3 Soil Type Interaction with Establishment

While extension sources mention that sandy soils drain faster and require more frequent watering, no source provides a complete soil-type adjustment matrix for the establishment schedule. The soil adjustment must be layered on top of the species/climate schedule.

5.4 Native vs. Non-Native Species

Gilman notes the absence of research on native vs. non-native species differences in transplant water requirements. Conventional wisdom holds that regionally native species establish faster, but this has not been rigorously quantified.

---

6. Implications for SimplyScapes

6.1 Multi-Year Schedule Generation

The research supports a software system that generates watering schedules using:

1. Inputs: Species, caliper/container size, planting date, hardiness zone, soil type, planting method, WUCOLS factor
2. Establishment phase calculation: Months-per-inch formula with zone, method, and season adjustments
3. Phase-specific frequency: 3-phase tapering (daily -> every few days -> weekly)
4. Volume calculation: Gallons-per-caliper-inch per event, adjusted by climate
5. Post-establishment: ET-based scheduling using WUCOLS species factor

6.2 Growth-Adjusted Emitter Management

Using the USDA Urban Tree Database allometric equations:

• Predict canopy diameter at year 1, 3, 5, 10
• Calculate when emitters should be repositioned toward expanding dripline
• Predict when additional emitters are needed (more emitters as canopy grows)
• Estimate when to transition from point-source drip to bubblers (large mature trees)

6.3 Feedback Loop Opportunity

The system could improve predictions over time by:

• Asking users to confirm establishment completion (visual triggers)
• Tracking actual watering frequency vs. recommended
• Collecting plant survival/mortality data
• Building species-specific establishment curves from aggregated user data

6.4 Data Architecture Needed

| Data Source | Coverage | Format | Use In System | |-------------|----------|--------|---------------| | WUCOLS V | 4,100+ taxa, 6 CA zones | Downloadable Excel | Species factor (Ks) | | USDA Urban Tree DB (GTR-253) | 171 tree species, 16 zones | Research data archive | Growth prediction (age -> crown diameter) | | ANSI Z60.1/Z60.2 | All nursery stock | Industry standard | Starting state (caliper -> root ball) | | Gilman establishment tables | Trees and shrubs | Published tables | Tapering schedule parameters | | AMWUA/SNWA schedules | Desert plants | Published guides | Desert-adapted tapering | | CSU/UMN caliper tables | Trees | Published tables | Establishment duration formula | | Local ETo data | National (CIMIS, OpenET) | API/data feeds | Runtime calculations |

---

7. Source Bibliography

1. Gilman, E.F. UF/IFAS. "Irrigation Management After Planting." https://hort.ifas.ufl.edu/woody/irrigation2.shtml
2. Gilman, E.F. UF/IFAS. "Irrigation Research." https://hort.ifas.ufl.edu/woody/irrigation-research.shtml
3. UF/IFAS Gardening Solutions. "Watering to Establish Shrubs." https://gardeningsolutions.ifas.ufl.edu/care/irrigation/watering-to-establish-shrubs/
4. Colorado State University Extension. "Care of Recently Planted Trees." GardenNotes #635. https://extension.colostate.edu/resource/care-of-recently-planted-trees/
5. University of Minnesota Extension. "Watering Newly Planted Trees and Shrubs." https://extension.umn.edu/planting-and-growing-guides/watering-newly-planted-trees-and-shrubs
6. AMWUA. "Watering Schedules." https://www.amwua.org/landscaping-with-style/maintain/watering-schedules
7. Southern Nevada Water Authority. "Watering & Maintaining Your Landscape." https://www.snwa.com/landscapes/how-and-when-to-water/index.html
8. University of Arizona Cooperative Extension. "Watering Trees and Shrubs." https://extension.arizona.edu/publication/watering-trees-and-shrubs
9. City of Portland. "Establishment Care." https://www.portland.gov/trees/establishmentcare
10. Saving Water Partnership. "How to Water New Plants." https://www.savingwater.org/lawn-garden/watering-irrigation/how-to-water-new-plants/
11. NYC Street Design Manual. "Plant Installation, Period of Establishment & Maintenance." https://www.nycstreetdesign.info/landscape/plant-installation-period-establishment-maintenance
12. Purdue Extension. "Tree Installation: Process and Practices." FNR-433-W. https://www.extension.purdue.edu/extmedia/fnr/fnr-433-w.pdf
13. McPherson, E.G., van Doorn, N.S., Peper, P.J. (2016). "Urban Tree Database and Allometric Equations." PSW-GTR-253. USDA Forest Service. https://research.fs.usda.gov/treesearch/52933
14. USDA Ag Data Commons. "Urban Tree Database." https://data.nal.usda.gov/dataset/urban-tree-database
15. ISA. "Urban Tree Growth Modeling." Arboriculture & Urban Forestry 38(5):172. https://auf.isa-arbor.com/content/38/5/172
16. AmericanHort. "ANSI Z60.1 — American Standard for Nursery Stock." https://americanhort.org/education/american-nursery-stock-standards/
17. UF/IFAS. "Root Ball Size Standards." https://hort.ifas.ufl.edu/woody/root-ball-dimension-chart.shtml
18. Watson, G.W. (1985). "Tree Size Affects Root Regeneration and Top Growth After Transplanting." J. Arboriculture 11(2):37-40. https://auf.isa-arbor.com/content/11/2/37
19. Watson, G.W. & Himelick, E.B. (2005). "Influence of Tree Size on Transplant Establishment and Growth." HortTechnology 15(1):118-122. https://ctufc.org/wp-content/uploads/2018/03/Establishment-and-Tree-Size.pdf
20. Struve, D.K. (2009). "Tree Establishment: A Review of Some of the Factors Affecting Transplant Survival and Establishment." Arboriculture & Urban Forestry 35(1):10-13. https://auf.isa-arbor.com/content/35/1/10
21. Gilman, E.F. UF/IFAS. "Selecting Trees: More Comparisons." https://hort.ifas.ufl.edu/woody/more-comparisons.shtml
22. Clemson HGIC. "Watering Shrubs and Trees." https://hgic.clemson.edu/factsheet/watering-shrubs-and-trees/
23. Utah State Extension. "Efficient Irrigation of Trees and Shrubs." https://extension.usu.edu/cwel/research/efficient-irrigation-of-trees-and-shrubs
24. UC Davis. "WUCOLS V." https://wucols.ucdavis.edu/
25. Waterwise Garden Planner. "Irrigation for Plant Establishment." https://waterwisegardenplanner.org/blog/irrigation-for-plant-establishment/