6
Representative records show how public water data, scenario rows, and incomplete records will be normalized before live imports.
SIM Water Ledger
Public water accounting for Arizona's next operating model.
Arizona water is usually discussed as volume. SIM Water Ledger treats it as an operating resource with source, location, reliability, storage status, delivery burden, energy cost, and field-level usability.
10
ADWR, CAP, Reclamation, and related public-data anchors are tracked with source notes and import status.
4
Every record is labeled as observed public data, calculated estimate, user scenario, or incomplete record.
Arizona Water Ledger
Search public water records by source, legal class, storage status, and delivery constraint.
These are prototype rows. They are structured to match the future public-data import model and keep facts, calculations, and scenario assumptions visibly separated.
| Source | Record | Location | Status | Volume | Confidence |
|---|---|---|---|---|---|
| SIM Public Water Accounting Lab | Scenario-Only Placeholder Stored or delivered water / Scenario assumption | Phoenix AMA Maricopa County | Buffered Low-flow field delivery modeled | 100.0 AF | User Scenario |
| ADWR Assured and Adequate Water Supply | Assured Water Supply / Municipal Demand Record Portfolio supply / Assured supply determination | Tucson AMA Pima County | Administrative record Municipal distribution system | 2,100.0 AF | Observed Public Data |
| ADWR Groundwater Site Inventory | Groundwater Right / Well / GWSI Record Groundwater / Well / groundwater inventory | Pinal AMA Pinal County | Not stored On-site pumping assumed | Not reported | Incomplete Record |
| Reclamation Lower Colorado River Water Accounting | Colorado River Diversion / Consumptive Use Record Colorado River mainstream / Diversion / consumptive use accounting | Lower Colorado River Yuma County | Reported use Diversion works and district delivery | 95,000.0 AF | Observed Public Data |
| CAP Subcontracting Status Report | CAP Allocation CAP / Colorado River / CAP Subcontract | Phoenix AMA Maricopa County | Allocated CAP delivery relationship required | 6,400.0 AF | Observed Public Data |
| ADWR Recharge Dashboard / LTSC | Long-Term Storage Credit / Recharge Record CAP / Colorado River / Long-Term Storage Credit | Phoenix AMA Maricopa County | Stored Requires recovery and distribution path | 12,500.0 AF | Observed Public Data |
6 records shown.
Nano Flow Opportunity Layer
Connect public water constraints to field-level hydraulic demand.
The opportunity engine identifies where water is legally constrained, physically constrained, hydraulically expensive, or operationally mismatched with conventional irrigation demand.
Research-Grounded Model
Use USDA, Reclamation, ADWR, UA, and USGS anchors to convert public records into hydraulic burden, field usability, and pilot-priority scores.
Open Research ModelPublic Water Stress to Pilot Site
Rank candidate regions using groundwater pumping burden, CAP exposure, agricultural demand, recharge proximity, district relevance, specialty crop fit, and public data confidence.
Open Opportunity MapLTSC-to-Farm Usability
Model how stored or recovered water changes when the receiving irrigation system can operate slowly, continuously, and with storage buffering.
Open LTSC ToolLower Colorado River Corridor
Frame Nano Flow pilot measurement where public accounting already tracks diversions, returns, consumptive use, ET, and acreage.
Open Validation PageWater scarcity is not only a supply problem. It is a usability problem.
Acre-feet become useful only when they can be stored, moved, recovered, pressurized, delivered, and applied at a rate the receiving system can actually use.
Public-data boundaries
- This platform does not create water rights, authorize transfers, or determine ownership.
- Public records are separated from calculated estimates and user scenario assumptions.
- Legal status, recovery feasibility, and delivery agreements require qualified review.