Laserfiche WebLink
VOLUME XVIII, ISSUE 3 <br />ing, but curtailing any and all <br />pumping required to prevent a <br />negative impact on river. This <br />may be done on a farm by farm <br />basis or for the whole plan. The <br />accounting must be submitted to <br />Div 1 Accounting @state.co.us <br />within 30 days after the end of the <br />month for which the accounting is <br />being made. The accounting must <br />be submitted every month. <br />All depletions that exist when a <br />well drops out of the plan for <br />augmentation remain the obliga- <br />tion of the plan and must be <br />replaced by the plan. Any deple- <br />tions that have yet to impact the <br />river at the time a well joins the <br />plan must be replaced by the plan <br />unless those depletions are already <br />covered by another plan. Evi- <br />dence acceptable to the Division <br />Engineer that another plan is <br />obligated to make replacements <br />must be in the form of either a <br />decree or valid written contract. <br />Accounting <br />The monthly accounting must <br />consist of real data collected at <br />least monthly (daily for APOD <br />wells). The data may be in the <br />form of flow meter readings or <br />power meter readings with a <br />certified power coefficient and <br />dedicated utility meter. The data <br />must be submitted by WDID (the <br />number assigned by the Division <br />office during the Substitute Water <br />Supply Plan or water court proc- <br />ess). <br />The monthly summary must show: <br />• Diversions (Well Pumping) — <br />Current and historic <br />• Current depletions projected <br />through the end of the current <br />irrigation season or as much as <br />three years in advance, de- <br />pending upon the dynamics of <br />the plan area <br />• Replacement water from each <br />source (recharge, reservoir <br />delivery, etc.) <br />• Net impact on the river <br />The accounting must apply stan- <br />dard audit principles, meaning <br />numbers may not simply appear <br />out of thin air. Each input must <br />show the real source of the num- <br />ber. For instance, if four recharge <br />sites are receiving water from a <br />release of changed reservoir water, <br />the accounting must show the <br />reservoir balance sheet with the <br />volume of water being released on <br />that plan's behalf. It must then <br />show the portion of that water <br />being delivered to each of the four <br />recharge sites, corroborated by the <br />inlet flow recorder and accounting <br />for transit losses, etc. Accounting <br />that simply provides flow into a <br />recharge site "out of thin air" <br />would not be acceptable. <br />In addition to the above summary <br />information, the plan may be <br />required to submit: copies of raw <br />data collection forms, modeling <br />input /output, spreadsheets showing <br />formulas, etc. for verification and <br />other information as required. <br />Data Accessibility <br />All data is accessible for public <br />review. The division office is <br />currently working with the <br />SPMAP work team, exploring an <br />accounting module for the CSU <br />AWAS program that is internet <br />accessible and would be hosted by <br />CSU. Pending funding, the initial <br />tool (targeted for use during the <br />PAGE 5 <br />2005 irrigation season) will <br />create a geographic representa- <br />tion of the basin with a node for <br />each significant augmentation <br />plan in the approximate location <br />of the plan area. By "clicking" <br />on the node, one could drill down <br />for information regarding the <br />plan. The first level of informa- <br />tion would show the summary <br />accounting supplied to http:// <br />www.DivIAccounting@ state.co. <br />us for the current period of <br />operation. Eventually, additional <br />levels may be added to access or <br />even perform (using AWAS) <br />modeling, weather data, relevant <br />stream flow data, historic ac- <br />counting, etc. <br />DWR Focus <br />The primary focus of the DWR is <br />to gain compliance so that poten- <br />tial injuries to the river are <br />prevented, as opposed to enforce- <br />ment against parties that cause <br />injury. The goal is a level play- <br />ing field with a single set of rules <br />that is protective of all water <br />rights in accordance with the <br />doctrine of prior appropriation. <br />Noncompliant groups will be the <br />primary focus of enforcement. <br />Enforcement, because of limita- <br />tions in the process and staffing, <br />will be at least a year in arrears <br />for the next several years. <br />Another significant focus area is <br />automating the data collection <br />process. In the last several years <br />for instance, over 300 recharge <br />sites have been added along the <br />river system. SUTRON is cur- <br />rently working to develop a <br />digital flow measurement/ <br />recorder directly in response to <br />(Continued on page 6) <br />