| | | | | | | | | | | | |
|---|
| A | 162 | Analyze/Interpret Data | Provide RealTime Predictions | These activities apply analytical tools to render meaning from data for making better management decisions. They go beyond data summaries. Often involves tests of statistical significance and may include modeling, indices, and synthesis. Typically culminates in resource management recommendations presented in a report of research/evaluation findings. | A | DELIV | Deliverable complete | | 10/31/2005 | Concluded | Craig Scanlan | 01/27/2006 3:48 PM |
| A | 162 | Analyze/Interpret Data | Provide RealTime Predictions | These activities apply analytical tools to render meaning from data for making better management decisions. They go beyond data summaries. Often involves tests of statistical significance and may include modeling, indices, and synthesis. Typically culminates in resource management recommendations presented in a report of research/evaluation findings. | B | | Update website daily | 03/04/2005 | 10/31/2005 | Concluded | Craig Scanlan | 01/27/2006 3:16 PM |
| B | 162 | Analyze/Interpret Data | Integration of Performance Measure Results | These activities apply analytical tools to render meaning from data for making better management decisions. They go beyond data summaries. Often involves tests of statistical significance and may include modeling, indices, and synthesis. Typically culminates in resource management recommendations presented in a report of research/evaluation findings.
| A | DELIV | Deliverable complete | | 12/30/2005 | Concluded | Craig Scanlan | 01/27/2006 3:55 PM |
| B | 162 | Analyze/Interpret Data | Integration of Performance Measure Results | These activities apply analytical tools to render meaning from data for making better management decisions. They go beyond data summaries. Often involves tests of statistical significance and may include modeling, indices, and synthesis. Typically culminates in resource management recommendations presented in a report of research/evaluation findings.
| B | | Update website with summaries of performance measure results | 05/16/2005 | 12/30/2005 | Concluded | Craig Scanlan | 01/27/2006 3:16 PM |
| C | 162 | Analyze/Interpret Data | Analyze post-season outmigration success | These activities apply analytical tools to render meaning from data for making better management decisions. They go beyond data summaries. Often involves tests of statistical significance and may include modeling, indices, and synthesis. Typically culminates in resource management recommendations presented in a report of research/evaluation findings. | A | DELIV | Deliverable complete | | 12/31/2005 | Concluded | Craig Scanlan | 01/27/2006 3:48 PM |
| C | 162 | Analyze/Interpret Data | Analyze post-season outmigration success | These activities apply analytical tools to render meaning from data for making better management decisions. They go beyond data summaries. Often involves tests of statistical significance and may include modeling, indices, and synthesis. Typically culminates in resource management recommendations presented in a report of research/evaluation findings. | B | | update website with 2005 smolt PIT-tag analysis | 07/01/2005 | 12/31/2005 | Concluded | Craig Scanlan | 01/27/2006 2:06 PM |
| D | 162 | Analyze/Interpret Data | Analysis of Performance Measures | These activities apply analytical tools to render meaning from data for making better management decisions. They go beyond data summaries. Often involves tests of statistical significance and may include modeling, indices, and synthesis. Typically culminates in resource management recommendations presented in a report of research/evaluation findings. | A | DELIV | Deliverable complete | | 12/30/2005 | Concluded | Craig Scanlan | 01/27/2006 3:48 PM |
| D | 162 | Analyze/Interpret Data | Analysis of Performance Measures | These activities apply analytical tools to render meaning from data for making better management decisions. They go beyond data summaries. Often involves tests of statistical significance and may include modeling, indices, and synthesis. Typically culminates in resource management recommendations presented in a report of research/evaluation findings. | B | | Update analysis of biological and ambient performance measures for 2005 | 01/03/2005 | 12/30/2005 | Concluded | Craig Scanlan | 01/27/2006 2:06 PM |
| E | 156 | Develop RM&E Methods and Designs | Provide statistical review of, or stat. assistance for, community research proposals | Work that develops and tests conceptual, quantitative, and technological tools for application in research, monitoring, and/or evaluation projects. Includes statistical and sampling designs, conceptual models, tagging and other equipment, software development, and generally any other work that prepares for the implementation of actual data collection/generation. Does not apply to producing an RM&E plan itself (see WE# 174: Produce Plan), although it does include the analyses required to write the plan. Also does not apply to models that are developed primarily to analyze and interpret existing data. | A | DELIV | Deliverable complete | | 12/30/2005 | Concluded | Craig Scanlan | 01/27/2006 3:48 PM |
| E | 156 | Develop RM&E Methods and Designs | Provide statistical review of, or stat. assistance for, community research proposals | Work that develops and tests conceptual, quantitative, and technological tools for application in research, monitoring, and/or evaluation projects. Includes statistical and sampling designs, conceptual models, tagging and other equipment, software development, and generally any other work that prepares for the implementation of actual data collection/generation. Does not apply to producing an RM&E plan itself (see WE# 174: Produce Plan), although it does include the analyses required to write the plan. Also does not apply to models that are developed primarily to analyze and interpret existing data. | B | | As requested by BPA & F&W Managers provide statistical review of reports. | 01/03/2005 | 12/30/2005 | Concluded | Craig Scanlan | 01/27/2006 2:06 PM |
| F | 141 | Produce Other Reports | Submit quarterly report to BPA | This work element covers several types of reports. The most common type indicates the status of milestones in each contract or project. These milestone status reports would be completed either monthly or quarterly as negotiated with the contractor and COTR. The second type could be any report required or produced for a contract or project, except those specifically covered under other work elements (e.g., WE# 132: Produce Annual Report, or WE# 183: Produce/Submit Scientific Findings Report). If this work element is used for multiple reports in the same contract, then each report should be listed as a separate milestone. NOTE: Once the Pisces system is up and running, status reporting for milestones will be converted to a simple red, yellow, or green system and completed on line. | A | | Submit first status report to BPA 15 days after end of Federal Fiscal Year quarter | 04/11/2005 | 04/15/2005 | Concluded | Craig Scanlan | 10/26/2005 5:49 PM |
| F | 141 | Produce Other Reports | Submit quarterly report to BPA | This work element covers several types of reports. The most common type indicates the status of milestones in each contract or project. These milestone status reports would be completed either monthly or quarterly as negotiated with the contractor and COTR. The second type could be any report required or produced for a contract or project, except those specifically covered under other work elements (e.g., WE# 132: Produce Annual Report, or WE# 183: Produce/Submit Scientific Findings Report). If this work element is used for multiple reports in the same contract, then each report should be listed as a separate milestone. NOTE: Once the Pisces system is up and running, status reporting for milestones will be converted to a simple red, yellow, or green system and completed on line. | B | | Submit second status report to BPA 15 days after end of Federal Fiscal Year quarter | 07/11/2005 | 07/15/2005 | Concluded | Craig Scanlan | 10/26/2005 5:49 PM |
| F | 141 | Produce Other Reports | Submit quarterly report to BPA | This work element covers several types of reports. The most common type indicates the status of milestones in each contract or project. These milestone status reports would be completed either monthly or quarterly as negotiated with the contractor and COTR. The second type could be any report required or produced for a contract or project, except those specifically covered under other work elements (e.g., WE# 132: Produce Annual Report, or WE# 183: Produce/Submit Scientific Findings Report). If this work element is used for multiple reports in the same contract, then each report should be listed as a separate milestone. NOTE: Once the Pisces system is up and running, status reporting for milestones will be converted to a simple red, yellow, or green system and completed on line. | C | | Submit third status report to BPA 15 days after end of Federal Fiscal Year quarter | 10/11/2005 | 10/15/2005 | Concluded | Craig Scanlan | 01/27/2006 1:54 PM |
| F | 141 | Produce Other Reports | Submit quarterly report to BPA | This work element covers several types of reports. The most common type indicates the status of milestones in each contract or project. These milestone status reports would be completed either monthly or quarterly as negotiated with the contractor and COTR. The second type could be any report required or produced for a contract or project, except those specifically covered under other work elements (e.g., WE# 132: Produce Annual Report, or WE# 183: Produce/Submit Scientific Findings Report). If this work element is used for multiple reports in the same contract, then each report should be listed as a separate milestone. NOTE: Once the Pisces system is up and running, status reporting for milestones will be converted to a simple red, yellow, or green system and completed on line. | D | | Submit fourth status report to BPA 15 days after end of Federal Fiscal Year quarter | 12/11/2005 | 01/15/2006 | Concluded | Craig Scanlan | 01/27/2006 3:16 PM |
| F | 141 | Produce Other Reports | Submit quarterly report to BPA | This work element covers several types of reports. The most common type indicates the status of milestones in each contract or project. These milestone status reports would be completed either monthly or quarterly as negotiated with the contractor and COTR. The second type could be any report required or produced for a contract or project, except those specifically covered under other work elements (e.g., WE# 132: Produce Annual Report, or WE# 183: Produce/Submit Scientific Findings Report). If this work element is used for multiple reports in the same contract, then each report should be listed as a separate milestone. NOTE: Once the Pisces system is up and running, status reporting for milestones will be converted to a simple red, yellow, or green system and completed on line. | E | DELIV | Deliverable complete | | 01/15/2006 | Active | Craig Scanlan | 01/26/2006 4:46 PM |
| G | 132 | Produce Progress (Annual) Report | Summarize program RealTime performance | This work element covers two types of reports, which may be combined and submitted under a single cover. The first type is a progress report that includes details of accomplishments for each work element in the contract: Were the deliverables produced, and, if not, why not? For many contracts, this report is an essential product that - when published and posted on the BPA website - succinctly documents contract performance for the public record. The second type of report is technical and applies to projects that are gathering data, for example on a feasibility study. This report provides a summary and analysis of data gathered - such as smolt to adult return rates, etc. - typically in a technical report format. These reports usually include data summaries. Intensive research projects may only produce cursory technical reports in some years, if the COTR and contractor have negotiated for a full scientific findings report (see other work element) after a few (e.g., 2-4) years of dat | A | DELIV | Deliverable complete | | 12/31/2005 | Concluded | Craig Scanlan | 01/27/2006 3:48 PM |
| G | 132 | Produce Progress (Annual) Report | Summarize program RealTime performance | This work element covers two types of reports, which may be combined and submitted under a single cover. The first type is a progress report that includes details of accomplishments for each work element in the contract: Were the deliverables produced, and, if not, why not? For many contracts, this report is an essential product that - when published and posted on the BPA website - succinctly documents contract performance for the public record. The second type of report is technical and applies to projects that are gathering data, for example on a feasibility study. This report provides a summary and analysis of data gathered - such as smolt to adult return rates, etc. - typically in a technical report format. These reports usually include data summaries. Intensive research projects may only produce cursory technical reports in some years, if the COTR and contractor have negotiated for a full scientific findings report (see other work element) after a few (e.g., 2-4) years of dat | B | | Submit Technical Report summarizing performance of outmigration status prediction program RealTime | | | Concluded | Craig Scanlan | 01/27/2006 3:16 PM |
| | | | | | | | | | | | |
Help
Mitigation work
Reporting
Funding
Search
Log in
