Columbia Basin Fish and Wildlife Program Columbia Basin Fish and Wildlife Program
RSS Feed for updates to Project 2010-075-00 - Upper Columbia Project-Scale Action Effectiveness Monitoring Follow this via RSS feed. Help setting up RSS feeds?

Project Summary

Project 2010-075-00 - Upper Columbia Project-Scale Action Effectiveness Monitoring
Project Number:
2010-075-00
Title:
Upper Columbia Project-Scale Action Effectiveness Monitoring
Summary:
This project supports the Upper Columbia Adaptive Management Framework, the 2008 FCRPS BiOp, the Yakama Nation Habitat Projects, the Colville Tribes Habitat Projects, and the Upper Columbia Habitat Programmatic Project by providing standardized implementation/compliance monitoring data for all salmon recovery projects implemented in the Upper Columbia, and by increasing the number of sites monitored as part of the Washington State Salmon Recovery Board's Reach-scale (Project) Effectiveness Monitoring Program.
Proponent Orgs:
Upper Columbia Salmon Recovery Board (Non-Profit)
Starting FY:
2011
Ending FY:
2017
BPA PM:
Stage:
Area:
Province Subbasin %
Columbia Cascade Entiat 25.00%
Methow 25.00%
Okanogan 25.00%
Wenatchee 25.00%
Purpose:
Habitat
Emphasis:
RM and E
Focal Species:
Chinook - Upper Columbia River Spring ESU
Steelhead - Upper Columbia River DPS
Species Benefit:
Anadromous: 100.0%   Resident: 0.0%   Wildlife: 0.0%
Special:
None

No photos have been uploaded yet for this Project.

Summary of Budgets

To view all expenditures for all fiscal years, click "Project Exp. by FY"

To see more detailed project budget information, please visit the "Project Budget" page

No Decided Budget Transfers

Pending Budget Decision?  No


Actual Project Cost Share

Current Fiscal Year — 2024
Cost Share Partner Total Proposed Contribution Total Confirmed Contribution
There are no project cost share contributions to show.
Previous Fiscal Years
Fiscal Year Total Contributions % of Budget
2017
2016
2015 $5,000 3%
2014 $5,000 3%
2013 $5,000 3%
2012 $5,000 3%
2011 $157,000 31%

Contracts

The table below contains contracts with the following statuses: Active, Closed, Complete, History, Issued.
* "Total Contracted Amount" column includes contracted amount from both capital and expense components of the contract.
Expense Contracts:
Number Contractor Name Title Status Total Contracted Amount Dates
53080 SOW Upper Columbia Salmon Recovery Board 201007500 EXP UPPER COLUMBIA IMPLEMENTATION/COMPLIANCE MONITORING Closed $330,625 5/1/2011 - 4/30/2012
53194 SOW Upper Columbia Salmon Recovery Board 2010-075-00 EXP UPPER COLUMBIA IMPLEMENTATION AND AE - FLOW Closed $0 5/15/2011 - 12/31/2011
57047 SOW Upper Columbia Salmon Recovery Board 2010-075-00 EXP UPPER COLUMBIA IMPLEMENT/COMPLIANCE MONITORING Closed $139,551 5/1/2012 - 4/30/2013
61474 SOW Upper Columbia Salmon Recovery Board 2010-075-00 EXP UPPER COLUMBIA PROJECT-SCALE ACTION EFFECTIVENESS Closed $152,812 5/1/2013 - 4/30/2014
64876 SOW Upper Columbia Salmon Recovery Board 2010-075-00 EXP UPPER COLUMBIA PROJECT-SCALE ACTION EFFECTIVENESS Closed $152,925 5/1/2014 - 4/30/2015
68904 SOW Upper Columbia Salmon Recovery Board 2010-075-00 EXP UPPER COLUMBIA PROJECT-SCALE ACTION EFFECTIVENESS Closed $146,799 5/1/2015 - 4/30/2016



Annual Progress Reports
Expected (since FY2004):6
Completed:5
On time:5
Status Reports
Completed:27
On time:16
Avg Days Late:1

                Count of Contract Deliverables
Earliest Contract Subsequent Contracts Title Contractor Earliest Start Latest End Latest Status Accepted Reports Complete Green Yellow Red Total % Green and Complete Canceled
53080 57047, 61474, 64876, 68904 2010-075-00 EXP UPPER COLUMBIA PROJECT-SCALE ACTION EFFECTIVENESS Upper Columbia Salmon Recovery Board 05/01/2011 04/30/2016 Closed 25 43 0 0 2 45 95.56% 0
53194 2010-075-00 EXP UPPER COLUMBIA IMPLEMENTATION AND AE - FLOW Upper Columbia Salmon Recovery Board 05/15/2011 12/31/2011 Closed 2 0 0 0 4 4 0.00% 0
Project Totals 27 43 0 0 6 49 87.76% 0


The table content is updated frequently and thus contains more recent information than what was in the original proposal reviewed by ISRP and Council.

Review: RME / AP Category Review

Council Recommendation

Assessment Number: 2010-075-00-NPCC-20110113
Project: 2010-075-00 - Upper Columbia Project-Scale Action Effectiveness Monitoring
Review: RME / AP Category Review
Proposal: RMECAT-2010-075-00
Proposal State: Pending BPA Response
Approved Date: 6/10/2011
Recommendation: Fund (Qualified)
Comments: See Programmatic Issue #2. Fast Track April 2011 Council decision.
Conditions:
Council Condition #1 Programmatic Issue: RMECAT #2 Habitat effectiveness monitoring and evaluation—.

Independent Scientific Review Panel Assessment

Assessment Number: 2010-075-00-ISRP-20101015
Project: 2010-075-00 - Upper Columbia Project-Scale Action Effectiveness Monitoring
Review: RME / AP Category Review
Proposal Number: RMECAT-2010-075-00
Completed Date: 12/17/2010
Final Round ISRP Date: 12/17/2010
Final Round ISRP Rating: Meets Scientific Review Criteria
Final Round ISRP Comment:
The proponents have a good track record of addressing science review concerns and the ISRP appreciates their responses to our questions. The explanation of the relationship between this project and others in the region is very helpful. Comments below are intended to help the proponents and their partners as the project goes forward.

The project proponents have provided a more detailed explanation of the link between the project and ongoing effectiveness monitoring programs such as ISEMP/CHaMP and OBMEP. The goals of this work in relation to the objectives of Upper Columbia River (UCR) salmon recovery plans have been made clearer. The project is intended to fill information gaps that have been identified by the UCR Technical Team as being critical to calculation of VSP parameters for focal species, and will help determine why at-risk salmon and steelhead populations are continuing to decline in spite of the extensive regional investment in restoration.

The proponents clearly identify the critical gaps addressed in the proposed work as monitoring of all projects in the Upper Columbia for 1) implementation/compliance monitoring, and 2) reach-scale effectiveness monitoring. They propose adding an additional 36 sites in the Upper Columbia to the effectiveness monitoring being conducted, but further information about sampling sites would have made the proposal a little clearer. The ISRP appreciates that additional detail was provided with respect to treatment-control reaches for evaluating restoration effectiveness. The methods for locating sites (randomly selected, but stratified for restoration category) seem appropriate. One ISRP concern has to do with reach length. Study reaches of 150-500 meters may not be sufficient to detect changes in target species densities or other response metrics (reach lengths of 30 times the average channel width have often been recommended in fisheries work), so project proponents may wish to revisit the size criteria for some locations.

A more complete rationale for the work was presented in the Project Significance and Problem Statement, and the Emerging Limiting Factors sections. Descriptions of the response metrics and their importance were improved over the original proposal. The categories of restoration projects, which form the basis for stratification of study pairs, are also better described, although it was not clear how the 6 site pairs in Panel 2 will address all 7 Salmon Recovery Funding Board project categories.

The response was a little weak in addressing the ISRP's request for information about the status and trends in habitats and fish populations in areas where restoration is taking place. We were hoping for a few examples to illustrate where restoration has had, or has failed to produce, a measurable effect on target species, including some insight into why the monitoring was or was not successful. The history of restoration activity in the Upper Columbia is long enough that there should be some useful case studies.

The response states that data sharing between CHaMP, OBMEP, and this project will occur to "coordinate and share resources related to data management and QA/QC." It was not clear from the revision how this coordination would occur and who would act as the central clearinghouse for shared data. We guess it would be ISEMP, but that may not be the case.

The preliminary list of implementation/compliance metrics given in Table 4 is quite extensive and will need to be winnowed down to the most cost-effective and applicable ones. An attempt to select the most potentially useful compliance metrics should take place prior to initiation of post-project sampling. Likewise, the QA/QC guidelines should be completed prior to initiation of field measurements.

The response correctly points out that time constraints may limit some BACI-design evaluations to a single year of pre-treatment data. While this is not necessarily the most desirable scenario, the ISRP stresses the importance of completing at least one full year of pre-treatment sampling for those treatment/control pairs where a BACI study design will be used.
First Round ISRP Date: 10/18/2010
First Round ISRP Rating: Response Requested
First Round ISRP Comment:

The ISRP feels that additional details are needed before it can complete a scientific assessment of this proposal, and for this reason we are asking for a response. The proposal should provide a clear description of relationships with other monitoring efforts in the Upper Columbia, including ISEMP/CHaMP and the large monitoring program planned for the Okanogan Subbasin (OBMEP). Monitoring is expensive and resources for conducting these projects are limited. Therefore, close coordination among related projects is critical to the efficient and effective use of monitoring funds. The description should go beyond box-and-arrow diagrams and explain how funding and manpower resources would be shared. The proposal needs to provide sufficient information about objectives, adaptive management, deliverables and work elements. More explanation could have been presented on the background and rationale for this project, as well as a summary of existing monitoring programs that have pointed to certain factors as being limiting to salmonid productivity. Most importantly, however, the proposal should provide more technical details about both the post-treatment implementation monitoring and the reach scale effectiveness monitoring. A brief list of metrics and citations is not enough; the ISRP needs to see a discussion of why certain metrics have been selected, information about sampling schedules, where monitoring sites will be located in relation to the restoration actions (at least in general terms), what types of sites will serve as controls, who will carry out the monitoring work, and how will the data be managed. Once this information is provided we will be able to assess the merits of the proposal. 1. Purpose, Significance to Regional Programs, Technical Background, and Objectives Valuable information could be produced by expanding current implementation and effectiveness monitoring efforts in the Upper Columbia to encompass all restoration projects (according to the presentation on September 13, 2010, many projects are not currently monitored). The proposal should include an expanded discussion of the threats to focal species in the Upper Columbia area and a summary of the major categories of habitat restoration that are taking place which the proposed monitoring would cover. It would also be helpful to summarize the existing implementation and effectiveness monitoring efforts currently in place, where they are located, what types of restoration projects they are monitoring, what the key findings to date have been especially with respect to limiting factors, and where significant knowledge or geographical gaps exist. More details should be given for the objectives. Most objectives are described in 1-2 sentences followed by an identical list of work elements (some of which are repeated multiple times) for each objective. This made it difficult to understand how the objectives were separated, other than by looking at the title. It was not clear in this section whether the proposal was primarily for post-implementation compliance monitoring or for reach scale effectiveness monitoring, although it became clear later in the proposal that the request was for both. 2. History: Accomplishments, Results, and Adaptive Management This project proposes to expand an existing set of monitoring sites. However, little information is provided on results that have been generated to date from the existing program. Some indication that the methodologies and design of the program have been effective would provide support for the plan to expand the number of sites monitored using this process. The project will expand the number of monitored sites to 30 control-impact pairs. A statement was made in the proposal that this number of sites was selected after conducting a power analysis, yet no information about this analysis is provided. As the ultimate value of the information generated by this project will be dependent on the statistical power of the experimental design, a reasonable description of this analysis should be included in the proposal. One must assume that this power analyses was based on monitoring results that have been generated from the existing study sites, further emphasizing the value of including project results in this proposal. Adaptive management is implied rather than directly addressed in the proposal. The statement is made that adaptive management in the Upper Columbia will be enhanced by the inclusion of more sites in the monitoring program, but no description of this adaptive management process is provided. There are several statements that monitoring data will be used by the Action Agencies’ expert panel process. Is this panel considered to be the core of the Upper Columbia adaptive management process? A more thorough explanation of how information generated by this project will be used to inform and change habitat restoration and fish management policies and practices in the Upper Columbia should be incorporated into the proposal. 3. Project Relationships, Emerging Limiting Factors, and Tailored Questions for Type of Work (Hatchery, RME, Tagging) A thorough explanation of the relationship between this proposed effort and other monitoring programs in the Upper Columbia should be incorporated into this proposal. The proposal does indicate several other monitoring programs, including ISEMP, but fails to indicate how this program will augment efforts already underway. The proposal also fails to mention a large monitoring effort planned for the area under the CHaMP program. The Colville Tribe has proposed a very large monitoring program for the Okanogan (OBMEP), with many of the same objectives as this proposal. The Colville monitoring program and the one proposed here should be carefully coordinated. Cooperation among these various monitoring efforts is essential to ensure that information is collected efficiently and in a compatible format. The proposal authors make the statement that this project will not interfere with other monitoring programs in the Upper Columbia. Avoiding interference should not be the objective. Rather all these monitoring efforts should be coordinated such that they provide complimentary information. A thorough discussion of the linkages among the various monitoring efforts in the area, one that clearly illustrates the coordination among these programs, should be added to the proposal. The statement is made that, “Various efforts are underway to resolve some of the confounding issues, including climate change-related projects in the Okanogan and Methow sub-basins to develop better streamflow forecasting tools.” This is useful to know because extreme low flows likely constitute a significant environmental limitation to salmonid productivity in many of the watersheds. However, more details are needed on how potentially confounding factors such as climate change will be addressed in this monitoring program. The proposal should be more explicit in this regard. 4. Deliverables, Work Elements, Metrics, and Methods Deliverables basically were often described in a single sentence. More description of what these deliverables will include should be added. The work elements were sometimes unclear and duplicative for different objectives. They were presented as a list of variables (e.g., length, width, bankfull height, etc.) with an associated reference, which provided the methods to be used in measuring this variable, but the same reference was often listed multiple times for a given parameter. The description of these elements in the proposal does not provide enough information to conduct a technical review. Under post-implementation compliance monitoring, the list of metrics should be given, even if it is still preliminary. For each provisional metric, sampling schedules (including years) and sample sizes (if possible) should be stated, as well as who would do the work and where the monitoring data would be housed. An explicit connection between each metric and one or more limiting factors should be given so that the relevance of the metric is clear. How, specifically, will QA/QC issues related to the metrics be addressed? Under SFRB reach scale effectiveness monitoring, will the 30 treatment-control pairs, plus the 6 pairs already requested, be stratified according to restoration type (e.g., fish passage improvement, increased in-stream flows, physical habitat restoration, nutrient management)? How long will the pre-treatment sampling period be? It would be very helpful to give more details on the SFRB effectiveness monitoring protocols and why post-treatment sampling will occur in years 0, 1,3, 5, and 10 (as opposed to a different schedule). Fish density is the only biological metric mentioned in the proposal, but some restoration actions could affect other parameters (e.g., fish growth or migration). Will other demographic properties of focal species be estimated?

Documentation Links:
  • Proponent Response (11/15/2010)

2008 FCRPS BiOp Workgroup Assessment

Assessment Number: 2010-075-00-BIOP-20101105
Project Number: 2010-075-00
Review: RME / AP Category Review
Proposal Number: RMECAT-2010-075-00
Completed Date: None
2008 FCRPS BiOp Workgroup Rating: Supports 2008 FCRPS BiOp
Comments: BiOp Workgroup Comments: No BiOp Workgroup Comments

The BiOp RM&E Workgroups made the following determinations regarding the proposal's ability or need to support BiOp Research, Monitoring and Evaluation (RME) RPAs. If you have questions regarding these RPA association conclusions, please contact your BPA COTR and they will help clarify, or they will arrange further discussion with the appropriate RM&E Workgroup Leads. BiOp RPA associations for the proposed work are: ( 56.1 73.1)
All Questionable RPA Associations ( ) and
All Deleted RPA Associations ()
Proponent Response:

Project Relationships: This project Merged To 2016-001-00 effective on 10/1/2016
Relationship Description: Sponsor is aware and asking for funds to be transferred to 2016-001-00 on a permanent basis. Work will commence under that project going forward. This action is part of the AEM Programmatic direction of the RM&E team. This project will be closed out for FY17


Name Role Organization
Joseph Connor Project Manager Bonneville Power Administration
James White (Inactive) Project Lead Upper Columbia Salmon Recovery Board
Derek Van Marter (Inactive) Supervisor Upper Columbia Salmon Recovery Board
Benjamin Zelinsky Interested Party Bonneville Power Administration
Debbie West Administrative Contact Upper Columbia Salmon Recovery Board
Jennifer Snyder (Inactive) Env. Compliance Lead Bonneville Power Administration
Peter Lofy Supervisor Bonneville Power Administration
Russell Scranton Project SME Bonneville Power Administration