| | | | | | | | | | | | |
|---|
| A | 165 | Produce Environmental Compliance Documentation | Environmental Compliance Documentation | Provide copies of permit documents such as Section 10, 404-D, and cultural resources survey documents to lead EC Officer. | A | DELIV | Environmental Compliance Documentation | | 02/28/2009 | Concluded | | 05/14/2009 5:01 PM |
| B | 185 | Produce CBFish Status Report | Periodic Status Reports for BPA | The Contractor shall report on the status of milestones and deliverables in Pisces. Reports shall be completed either monthly or quarterly as determined by the BPA COTR. Additionally, when indicating a deliverable milestone as COMPLETE, the contractor shall provide metrics and the final location (latitude and longitude) prior to submitting the report to the BPA COTR. | A | SR | Dec-Mar 2009 (12/1/2008 - 3/31/2009) | 04/01/2009 | 04/15/2009 | Concluded | | 05/14/2009 5:01 PM |
| B | 185 | Produce CBFish Status Report | Periodic Status Reports for BPA | The Contractor shall report on the status of milestones and deliverables in Pisces. Reports shall be completed either monthly or quarterly as determined by the BPA COTR. Additionally, when indicating a deliverable milestone as COMPLETE, the contractor shall provide metrics and the final location (latitude and longitude) prior to submitting the report to the BPA COTR. | B | SR | Apr-Jun 2009 (4/1/2009 - 6/30/2009) | 07/01/2009 | 07/15/2009 | Concluded | | 05/14/2009 5:01 PM |
| B | 185 | Produce CBFish Status Report | Periodic Status Reports for BPA | The Contractor shall report on the status of milestones and deliverables in Pisces. Reports shall be completed either monthly or quarterly as determined by the BPA COTR. Additionally, when indicating a deliverable milestone as COMPLETE, the contractor shall provide metrics and the final location (latitude and longitude) prior to submitting the report to the BPA COTR. | C | SR | Jul-Sep 2009 (7/1/2009 - 9/30/2009) | 10/01/2009 | 10/15/2009 | Concluded | | 05/14/2009 5:01 PM |
| B | 185 | Produce CBFish Status Report | Periodic Status Reports for BPA | The Contractor shall report on the status of milestones and deliverables in Pisces. Reports shall be completed either monthly or quarterly as determined by the BPA COTR. Additionally, when indicating a deliverable milestone as COMPLETE, the contractor shall provide metrics and the final location (latitude and longitude) prior to submitting the report to the BPA COTR. | D | SR | Final Oct-Nov 2009 (10/1/2009 - 11/30/2009) | 11/16/2009 | 11/30/2009 | Concluded | | 05/14/2009 5:01 PM |
| C | 119 | Manage and Administer Projects | Project Management | Manage the project. Also covers administrative work in support of on-the-ground efforts and in support of BPA's programmatic requirements such as metric reporting, financial reporting (e.g., accruals), and development of an SOW package (includes draft SOW, budget, spending plan, and property inventory). | A | Suggested | Submit invoices to BPA consistent with BPA's contract management manual. | 12/01/2008 | 11/30/2009 | Concluded | | 05/14/2009 5:01 PM |
| C | 119 | Manage and Administer Projects | Project Management | Manage the project. Also covers administrative work in support of on-the-ground efforts and in support of BPA's programmatic requirements such as metric reporting, financial reporting (e.g., accruals), and development of an SOW package (includes draft SOW, budget, spending plan, and property inventory). | B | FPCIR | Funding Package - Conduct internal review (e.g., Supervisor or Interagency) | 08/01/2009 | 09/01/2009 | Concluded | | 05/14/2009 5:01 PM |
| C | 119 | Manage and Administer Projects | Project Management | Manage the project. Also covers administrative work in support of on-the-ground efforts and in support of BPA's programmatic requirements such as metric reporting, financial reporting (e.g., accruals), and development of an SOW package (includes draft SOW, budget, spending plan, and property inventory). | C | ASSEB | Accrual - Submit September estimate to BPA | 09/10/2009 | 09/10/2009 | Concluded | | 05/14/2009 5:01 PM |
| C | 119 | Manage and Administer Projects | Project Management | Manage the project. Also covers administrative work in support of on-the-ground efforts and in support of BPA's programmatic requirements such as metric reporting, financial reporting (e.g., accruals), and development of an SOW package (includes draft SOW, budget, spending plan, and property inventory). | D | Suggested | Contact BPA Environmental Compliance staff (KEC) to discuss next year's SOW. | 11/01/2009 | 11/23/2009 | Concluded | | 05/14/2009 5:01 PM |
| C | 119 | Manage and Administer Projects | Project Management | Manage the project. Also covers administrative work in support of on-the-ground efforts and in support of BPA's programmatic requirements such as metric reporting, financial reporting (e.g., accruals), and development of an SOW package (includes draft SOW, budget, spending plan, and property inventory). | E | DELIV | Funding Package - Submit draft to COTR | | 09/01/2009 | Concluded | | 05/14/2009 5:01 PM |
| D | 132 | Produce Progress (Annual) Report | Complete Draft Progress Report for the period (Dec 2008) to (Nov 2009) | The draft progress report summarizes the project goal, objectives, hypotheses, completed and uncompleted deliverables, problems encountered, lessons learned, and long-term planning. Examples of long-term planning include future improvements, new directions, or level of effort for contract implementation, including any ramping up or ramping down of contract components or of the project as a whole. Date range Dec. 1 2008 to November 30 2009 will be agreed upon by the COTR and the contractor. This may or may not coincide with the contract period. For an ongoing project, a progress report covering a contract period may be submitted under the subsequent contract, if approved by the COTR.
Progress reports must conform to BPA guidelines. See the ''formatting guidelines'' link at the Technical Reports and Publications page: https://www.cbfish.org/Help.mvc/GuidanceDocuments.
If producing a technical report for this contract, a discrete experiment, or a peer-reviewed publication, use work element 183: Produce Journal Article. | A | NonT1 | Review draft progress report format requirements | 12/01/2008 | 11/01/2009 | Concluded | | 05/14/2009 5:01 PM |
| D | 132 | Produce Progress (Annual) Report | Complete Draft Progress Report for the period (Dec 2008) to (Nov 2009) | The draft progress report summarizes the project goal, objectives, hypotheses, completed and uncompleted deliverables, problems encountered, lessons learned, and long-term planning. Examples of long-term planning include future improvements, new directions, or level of effort for contract implementation, including any ramping up or ramping down of contract components or of the project as a whole. Date range Dec. 1 2008 to November 30 2009 will be agreed upon by the COTR and the contractor. This may or may not coincide with the contract period. For an ongoing project, a progress report covering a contract period may be submitted under the subsequent contract, if approved by the COTR.
Progress reports must conform to BPA guidelines. See the ''formatting guidelines'' link at the Technical Reports and Publications page: https://www.cbfish.org/Help.mvc/GuidanceDocuments.
If producing a technical report for this contract, a discrete experiment, or a peer-reviewed publication, use work element 183: Produce Journal Article. | B | NonT3 | Submit progress report for internal contractor review | 11/01/2009 | 11/15/2009 | Concluded | | 05/14/2009 5:01 PM |
| D | 132 | Produce Progress (Annual) Report | Complete Draft Progress Report for the period (Dec 2008) to (Nov 2009) | The draft progress report summarizes the project goal, objectives, hypotheses, completed and uncompleted deliverables, problems encountered, lessons learned, and long-term planning. Examples of long-term planning include future improvements, new directions, or level of effort for contract implementation, including any ramping up or ramping down of contract components or of the project as a whole. Date range Dec. 1 2008 to November 30 2009 will be agreed upon by the COTR and the contractor. This may or may not coincide with the contract period. For an ongoing project, a progress report covering a contract period may be submitted under the subsequent contract, if approved by the COTR.
Progress reports must conform to BPA guidelines. See the ''formatting guidelines'' link at the Technical Reports and Publications page: https://www.cbfish.org/Help.mvc/GuidanceDocuments.
If producing a technical report for this contract, a discrete experiment, or a peer-reviewed publication, use work element 183: Produce Journal Article. | C | Suggested | Submit draft for technical/co-manager review (if necessary, and considering time/costs) | 11/16/2009 | 11/30/2009 | Concluded | | 05/14/2009 5:01 PM |
| D | 132 | Produce Progress (Annual) Report | Complete Draft Progress Report for the period (Dec 2008) to (Nov 2009) | The draft progress report summarizes the project goal, objectives, hypotheses, completed and uncompleted deliverables, problems encountered, lessons learned, and long-term planning. Examples of long-term planning include future improvements, new directions, or level of effort for contract implementation, including any ramping up or ramping down of contract components or of the project as a whole. Date range Dec. 1 2008 to November 30 2009 will be agreed upon by the COTR and the contractor. This may or may not coincide with the contract period. For an ongoing project, a progress report covering a contract period may be submitted under the subsequent contract, if approved by the COTR.
Progress reports must conform to BPA guidelines. See the ''formatting guidelines'' link at the Technical Reports and Publications page: https://www.cbfish.org/Help.mvc/GuidanceDocuments.
If producing a technical report for this contract, a discrete experiment, or a peer-reviewed publication, use work element 183: Produce Journal Article. | D | DELIV | Produce Draft Progress Report | | 11/30/2009 | Concluded | | 05/14/2009 5:01 PM |
| E | 157 | Collect/Generate/Validate Field and Lab Data | Task 1A: Conduct juvenile seining and PIT tagging activities in the South Fork Salmon River. | This task funds the Quantitative Consultants, Inc. (QCI) to conduct seining/collection activities for the capture of juvenile anadromous salmonids at sites in the South Fork Salmon River located in the Secesh River and East Fork South Fork Salmon River watersheds and associated lower mainstem South Fork Salmon River tributaries. In order to ensure equal sampling effort throughout the watershed, site locations will be selected from the Idaho Master Sample List, which was developed using a generalized random tessellation survey design. This also allows the sites to correspond with those selected for other regional sampling programs, such as Idaho Department of Fish and Game General Parr Monitoring Program, to maximize sub-basin collaboration and collection effort efficiencies.
At each selected site, a sample of the collected juvenile salmon and steelhead will be PIT tagged to enable life-stage specific survival estimates via recapture in subsequent seining/collection surveys, at rotary screw traps, extended length PIT tag arrays, and mainstem dam PIT tag interrogation facilities. Additionally, each PIT tagged individual will be weighed, measured for length, scales sampled, and life stage identified. Physical site description will include, at a minimum, site length, average width and depth from a minimum, average gradient, and proportion of major instream habitat types (pools, riffles, runs, rapids). Fish collection methods will not be limited to seining, but in order to ensure adequate sample sizes crews may employ angling, electrofishing, and snerding. | A | EC | Environmental compliance requirements complete | 12/12/2008 | 02/28/2009 | Concluded | | 05/14/2009 5:01 PM |
| E | 157 | Collect/Generate/Validate Field and Lab Data | Task 1A: Conduct juvenile seining and PIT tagging activities in the South Fork Salmon River. | This task funds the Quantitative Consultants, Inc. (QCI) to conduct seining/collection activities for the capture of juvenile anadromous salmonids at sites in the South Fork Salmon River located in the Secesh River and East Fork South Fork Salmon River watersheds and associated lower mainstem South Fork Salmon River tributaries. In order to ensure equal sampling effort throughout the watershed, site locations will be selected from the Idaho Master Sample List, which was developed using a generalized random tessellation survey design. This also allows the sites to correspond with those selected for other regional sampling programs, such as Idaho Department of Fish and Game General Parr Monitoring Program, to maximize sub-basin collaboration and collection effort efficiencies.
At each selected site, a sample of the collected juvenile salmon and steelhead will be PIT tagged to enable life-stage specific survival estimates via recapture in subsequent seining/collection surveys, at rotary screw traps, extended length PIT tag arrays, and mainstem dam PIT tag interrogation facilities. Additionally, each PIT tagged individual will be weighed, measured for length, scales sampled, and life stage identified. Physical site description will include, at a minimum, site length, average width and depth from a minimum, average gradient, and proportion of major instream habitat types (pools, riffles, runs, rapids). Fish collection methods will not be limited to seining, but in order to ensure adequate sample sizes crews may employ angling, electrofishing, and snerding. | B | | Task 1A1: Contact landowners to obtain permission to sample. | 03/01/2009 | 03/31/2009 | Concluded | | 05/14/2009 5:01 PM |
| E | 157 | Collect/Generate/Validate Field and Lab Data | Task 1A: Conduct juvenile seining and PIT tagging activities in the South Fork Salmon River. | This task funds the Quantitative Consultants, Inc. (QCI) to conduct seining/collection activities for the capture of juvenile anadromous salmonids at sites in the South Fork Salmon River located in the Secesh River and East Fork South Fork Salmon River watersheds and associated lower mainstem South Fork Salmon River tributaries. In order to ensure equal sampling effort throughout the watershed, site locations will be selected from the Idaho Master Sample List, which was developed using a generalized random tessellation survey design. This also allows the sites to correspond with those selected for other regional sampling programs, such as Idaho Department of Fish and Game General Parr Monitoring Program, to maximize sub-basin collaboration and collection effort efficiencies.
At each selected site, a sample of the collected juvenile salmon and steelhead will be PIT tagged to enable life-stage specific survival estimates via recapture in subsequent seining/collection surveys, at rotary screw traps, extended length PIT tag arrays, and mainstem dam PIT tag interrogation facilities. Additionally, each PIT tagged individual will be weighed, measured for length, scales sampled, and life stage identified. Physical site description will include, at a minimum, site length, average width and depth from a minimum, average gradient, and proportion of major instream habitat types (pools, riffles, runs, rapids). Fish collection methods will not be limited to seining, but in order to ensure adequate sample sizes crews may employ angling, electrofishing, and snerding. | C | | Task 1A2: Conduct seining surveys. | 04/01/2009 | 10/31/2009 | Concluded | | 05/14/2009 5:01 PM |
| | | | | | | | | | | | |
Help
Mitigation work
Reporting
Funding
Search
Log in
