22.03.2014 Views

Biological Opinions - Bureau of Reclamation

Biological Opinions - Bureau of Reclamation

Biological Opinions - Bureau of Reclamation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Required hydrologic monitoring includes the following:<br />

3a. Klamath Basin Planning Model<br />

<strong>Reclamation</strong> shall use the WRIMS 2.0 s<strong>of</strong>tware platform, or the most recent version, for<br />

all future versions <strong>of</strong> the KBPM, including annual updates, instead <strong>of</strong> WRIMS 1.0.<br />

<strong>Reclamation</strong> shall update the s<strong>of</strong>tware to new versions as they are published and verified.<br />

Potential use <strong>of</strong> s<strong>of</strong>tware other than WRIMS will be evaluated in coordination with the<br />

Services.<br />

3b. Implementation<br />

As <strong>of</strong> mid-March 2013, <strong>Reclamation</strong> was developing one or more operations<br />

spreadsheets that will be used to implement the proposed action. The spreadsheet(s)<br />

translate the code in the KBPM and the detailed written description <strong>of</strong> the proposed<br />

action provided in Appendix 4A <strong>of</strong> <strong>Reclamation</strong>’s biological assessment (<strong>Reclamation</strong><br />

2012) into an operations spreadsheet(s). The operations spreadsheet(s) will bring<br />

together the input data (e.g. Williamson River flow, UKL elevations, NRCS forecasts),<br />

equations (e.g. the multiplier applied to UKL Supply to calculate EWA, fill rate ratio),<br />

and relationships (e.g. EWA is calculated before Project Supply, methods by which the<br />

Lower Klamath Lake Refuge may be delivered water) that <strong>Reclamation</strong> will use on a<br />

daily basis to implement the proposed action. <strong>Reclamation</strong> shall provide the Services<br />

with the proposed action implementation and operation spreadsheet(s) by June 1, 2013,<br />

and at least annually thereafter. Thereafter, <strong>Reclamation</strong> shall provide updates to the<br />

Services within 2 weeks <strong>of</strong> <strong>Reclamation</strong>’s acceptance and use <strong>of</strong> the updated<br />

spreadsheet(s). The Services expect a brief tutorial explaining how <strong>Reclamation</strong> uses the<br />

spreadsheet, which data may be updated, and which data should remain fixed and not be<br />

changed or updated. Thereafter, it will be the responsibility <strong>of</strong> the Services to use the<br />

spreadsheet(s). It is not <strong>Reclamation</strong>’s responsibility to continually provide updated<br />

spreadsheets or input data on a daily, weekly, or other planned schedule.<br />

3c. Implement Gage Quality Assurance/Quality Control Procedures<br />

<strong>Reclamation</strong>, in consultation with the Services, shall develop a draft QA/QC Procedures<br />

Plan for collecting, reviewing, and presenting Project reservoir elevation, flow, diversion,<br />

and pumping data. The draft plan shall be completed and formally submitted for the<br />

Services’ review and approval by October 1, 2013. A final QA/QC plan shall be<br />

completed and formally submitted to the Services by December 1, 2013, and<br />

implementation shall begin January 1, 2014. Quality assurance shall fully describe<br />

current measurement locations and equipment, gage (or other appropriate measurement<br />

device) maintenance and installation, pump-rating curves, and data collection procedures<br />

for measuring water use within the Project. Quality control shall describe procedures for<br />

review, correction (as needed), and finalizing datasets, including a schedule for<br />

completion <strong>of</strong> QA/QC and providing the data to stakeholders. An annual summary <strong>of</strong><br />

QA/QC compliance shall be included in the annual monitoring report due March 1 every<br />

year.<br />

400

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!