| | | | | | | | | |
|---|
| A | 87272 | 119 | Manage and Administer Projects | Project management | Routine project and contract management activities, including metrics reporting, invoicing, accrual estimates, and development of an SOW package (includes draft SOW, and budget). | $3,000 | 1.13% | 08/01/2009 | 09/30/2011 |
| B | 87273 | 174 | Produce Plan | Develop Implementation Plan | The project will develop a prototype of a web-based master sample management system. It will be necessary to explore with the web developer the various web-based systems and options to meet the desired capabilities. With the advice and input of PNAMP, a small workgroup will be established to define the details of the prototype and to ensure seamless integration with other PNAMP web-based applications. The work group will consist of a statistician, a web developer, and representatives from various federal agencies (e.g. PNAMP, USEPA, NOAA), state agencies (e.g., ODFW, WA ECY), tribal organizations (e.g., CRITFC), and other interested parties (e.g., LCREP, Pacific States Marine Fisheries Commission). The group will define operational attributes of the master sample management system. As the project develops, continual interaction between the work group and the web developer will be necessary to evaluate progress, explore the draft web-based capabilities, and ensure that the project is proceeding in a desired direction. | $24,000 | 9.01% | 07/01/2009 | 06/30/2010 |
| C | 87274 | 189 | Coordination-Columbia Basinwide | Coordination | The project will actively seek to establish partnerships to ensure compatibility of the system with existing state- or region-wide master sample management tools. For example, a Master Sample of streams already exists for Washington State, and the Washington State Department of Ecology (WA-ECY) has made it available on-line. However, the system, as currently configured, allows subset selection only by Water Resource Inventory Area, not by any other classification variable such as stream order. Moreover, there is no functionality that would allow a user to submit information about their designs and the status of the master sample sites that they drew from the web. This project intends to coordinate with agencies like ECY to insure that the web-based prototype is compatible with their systems. | $5,000 | 1.88% | 07/15/2009 | 09/30/2010 |
| D | 87275 | 160 | Create/Manage/Maintain Database | Prototype Web Based Master Sample Management System | Develop a prototype web-based master sample management system. Development of the web-based prototype will occur based on the specifications established in Task 2. We anticipate that this system will have at least the following capabilities:
• Store master samples and associated metadata (e.g., design documentation) on a readily accessible server;
• Allow users to download relevant parts of the master sample;
• Allow users to upload information about master sample sites that they have evaluated (to include design documentation, site evaluation, indicators measured, protocols used);
• Provide a tracking system that documents the history of sites selected from the master sample;
• Allow users to download histories of previously selected sites (to include design documentation, site evaluation, indicators measured, protocols used);
• Allow scaling up to a statewide, or multi-state system (this primarily means the capability to manage substantially larger master samples than that used for the prototype);
• Ensure protection of data (via a secure system);
• Provide a mapping tool to display master sample sites selected by previous users.
Once the prototype has completed the above tasks, some of the remaining funds should be used to start building the production system. As a first step to building a production level system, a project plan including high level requirements and a technology platform recommendation must be produced. The project plan is encompassed in tasks 1 through 6 below.
1. Walk---through Drupal code base, including interfaces to R functions, the mySQL databases (one for Drupal CMS stuff, one for the domain data). OUTPUT: Logical diagram of the prototype system today
2. A first draft of an "Overview & Basics" broadsheet similar to what was produced for MonitoringMethods.org project. This includes an understanding of project objectives, customers/stakeholders and user profiles, initial list of user tasks, and initial list of deliverables. Also includes drafting a list of people/organizations that we need to meet with to further explore requirements, but doesn't include actually meeting with them. OUTPUT: Broadsheet
3. A conceptual diagram of potential integrations with other systems. OUTPUT: Conceptual Diagram of APIs (added as a page to broadsheet)
4. Discuss and determine a technology platform, considering both project needs as well as contractors strategy. Includes considering OS, web server, database, coding framework, etc. This task includes internal discussion with larger team. OUTPUT: Recommendation report of technology platform.
5. Using the above deliverables, provide a cost estimate by deliverable, or by user task if possible, for the production---level Master Sample web application. OUTPUT: Cost estimate to build and deliver a production level system.
6. Provide OSU researches with assistance in developing user interfaces in order to test the panel/stratification tool; the evaluation & response analysis tools and the tutorials; and in developing query and site evaluation history storage and retrieval tools. OUTPUT: Functional web interfaces | $112,544 | 42.24% | 07/01/2009 | 09/30/2011 |
| E | 87276 | 159 | Transfer/Consolidate Regionally Standardized Data | Create Master Sample for the Lower Columbia | Several GRTS sample designs already exist in the Lower Columbia region. Methodology for merging an existing sample with additional sites has been developed by the StatNat Group at Oregon State University and applied to the Oregon Department of Fish and Wildlife’s coastal coho monitoring program. This methodology will be used to integrate these existing sites with newly selected random sites to produce a high-density, spatially-balanced GRTS sample. In addition, the USEPA selected a high-density area-based sample of the Lower Columbia estuary in 2007. This sample will be reviewed and if suitable, will be used for the area-based master sample of the estuarine portion of the Lower Columbia.
Data base will consist of geographic coordinates of the sample points together with ancillary information as determined by availability and advice of the workgroup. During the project, the data base and management system from WE D will reside on a server at OSU. At the conclusion of the project, the Master Sample data base and the Management System will be transferred to PNAMP or BPA and made publicly available, e.g., on StreamNet or PNAMP's web portal. | $24,000 | 9.01% | 07/01/2009 | 02/15/2011 |
| F | 87277 | 156 | Develop RM&E Methods and Designs | Identify Needs, Develop Web-Based Analysis Tools & Provide Interface to Master Sample Mgmt. System | Identify needs and develop web-based analysis tools. Another critical element is the development of tools that will link the design files with field data to provide easy access to analysis tools. It is important that these tools meet the analytical needs of ISTM major partners (e.g., OR and WA recovery plans, AREMP, etc), and that they are commensurate with standards developed by PNAMP and the Integrated Status and Effectiveness Monitoring Program (ISEMP). For example, the R package spsurvey developed by the USEPA already has tools for routine analysis of GRTS survey data, but there is a need to develop an interface to interact with these. Moreover, additional analysis tools are available that have not been implemented in spsurvey, and others, notably analysis of trend from rotating panel studies, will become available shortly. These tools will be made available as a part of the overall Master Sample implementation. | $30,000 | 11.26% | 07/01/2009 | 09/15/2011 |
| G | 87278 | 156 | Develop RM&E Methods and Designs | Provide Statistical assistance and support | The intent of the Master Sample web tool is to simplify application of rigorous statistical monitoring designs and analyses. Documentation will be provided that will facilitate most applications; however, the tool will have the capability to create designs to satisfy very complex requirements. For complex designs, users may need statistical support from a statistician familiar with the Master Sample management system to meet design requirements. | $15,000 | 5.63% | 07/01/2009 | 09/30/2011 |
| H | 87279 | 156 | Develop RM&E Methods and Designs | Develop/Implement Methodology | Historically, much monitoring data was collected without a formal probability design. Combining such non-probability data with data from a probability survey can be difficult because of the lack of unambiguous link between the data and population representation. Several methods (Brus & De Gruijter, 2003; Overton et al., 1993; Stein & Bernstein, 2007) have been proposed, and the applicability and feasibility of these will be evaluated and implemented accordingly. | $22,000 | 8.26% | 09/01/2009 | 09/30/2011 |
| I | 87280 | 122 | Provide Technical Review and Recommendation | Statistical Oversight | Provide statistical oversight as the web tool is developed. One of the benefits of a web-based Master Sample implementation is that it provides access to rigorous statistical sampling designs for any organization monitoring the Master Sample population. To maintain that statistical rigor, the web-based tool must be developed with close cooperation between the tool developers and statisticians familiar with the GRTS technique. The principles underlying the application of the Master Sample are well-understood, and Larsen, et al., (2008) present some examples of selecting focused samples from the Master Sample using ancillary information. However, implementation of a variety of design options, for example, stratification, rotating panels, and oversamples, will require statistical oversight. Furthermore, the web tool should be developed to facilitate eventual analysis of the sample selected. There must be a clear path for users to follow from design specification to sample selection to data collection, input, and analysis. One of the critical elements in that path is the automatic production of a design documentation file. This file documents the selection process so that appropriate inclusion probability or weight and other sample structure (e.g., stratification, panels) will be available for analyzing the data collected at the sample sites. The content and format of the file will be developed jointly by the web developer and the statisticians with input from the workgroup. Additionally, efforts under PNAMP to develop and capture metadata related to statistical and monitoring design, data collection and analysis will inform the format of design documentation developed under this task. | $9,900 | 3.72% | 07/01/2009 | 01/31/2010 |
| J | 87281 | 99 | Outreach and Education | Present Seminars and Workshops | The intent of the project is to make the management system user-friendly; nevertheless, we foresee the need to communicate and encourage its application by providing some introductory training via presentations, seminars, and/or workshops. This task will be coordinated through PNAMP. | $5,000 | 1.88% | 07/01/2009 | 09/30/2010 |
| K | 87282 | 141 | Produce Other Reports | Produce Users Guide & Training Materials | Develop training materials and user guides. This task will provide detailed documentation of the steps required to select a design, annotated examples of particular applications, guidance for selecting analysis procedures, and annotated examples of applying the analysis tools. | $10,000 | 3.75% | 01/01/2010 | 09/15/2011 |
| L | 87283 | 132 | Produce Progress (Annual) Report | Submit Progress Report for the period (MMM YYYY) to (MMM YYYY) | The 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 MMM YYYY to MMM YYYY (e.g. Apr 2001 to Mar 2002) 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. | $3,000 | 1.13% | 12/01/2009 | 09/30/2011 |
| M | 87284 | 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. | $3,000 | 1.13% | 10/01/2009 | 09/30/2011 |
Help
Mitigation work
Reporting
Funding
Search
Log in
SOW Report
