Show new navigation
On
Columbia Basin Fish and Wildlife Program Columbia Basin Fish and Wildlife Program
View Work Elements Available in FY:

Summary

<<
<
>
>>
Work Element 157: Collect/Generate/Validate Field and Lab Data - Published
WE Name:
157. Collect/Generate/Validate Field and Lab Data (Collect Data)
Work Category:
RM & E and Data Management
WE Agreement Type:
Contracted
Status:
Active
Definition:
Collect, generate, or capture source or empirical data; enter data into a computer spreadsheet/database; use automated data capture programs/routines and related hardware/software (e.g., PDAs, data loggers, thermographs); prepare or compile metadata; implement quality assurance/quality control (QA/QC) processes.

Includes the collection and processing of field samples/specimens (e.g., tissue, macroinvertebrate, or water quality samples), remote sensing data, and the subsequent laboratory processing of field samples/specimens and generation of data summaries.

This work element may include the installation of a weir, trap, electronic portal, water measuring device, or other equipment or facility used to monitor fish passage, collect juvenile or adult fish, or collect other data. Installation of such equipment should be a milestone in the work element.

Do NOT use this work element for the following types of work:
• if you are marking or tagging animals, you must use 158. Mark/Tag Animals,
• data analysis or interpretation requires 162. Analyze/Interpret Data,
• validation of completion and intended performance of implemented actions, or verification of CBFish metrics should be captured under the appropriate implementation work element (e.g., fence or culvert installation, habitat improvement, construction),
• visual surveys, photo points, and inspection of physical parameters to assure habitat structures are functioning as intended should be captured under 186. Operate and Maintain Habitat/Passage/Structure.
WSE Description Template:
Effective Dates:
FY2005 to <no end date>
Work Phase:
monitoring/evaluation
Sort Sequence:
13.03
Focal Species Required:
Yes
RM&E Metadata Required:
Yes
Finite or Recurring:
Recurring
Is BPA Internal:
No
Is Contracted:
Yes
Is Cost Share:
No
Is Construction:
No

The core principal for this work is that each WE implements a discrete Study Design with a discrete data set for each location data is collected as a final product. “Study Designs” are detailed plans that explain how data are to be collected, managed, analyzed, and reported, and are a key component of quality assurance for natural resource monitoring programs (Oakley et al. 2006). A fully defined Study Design in monitoringmethods.org includes Purpose & Key Assumptions, Spatial Design, Temporal Design, Response Design, and Inference Design. This ensures that the correct information is being collected in the proper intensity, spatial and temporal scales, and is addressing the key F&W program information needs. This information is required to ensure the information attained is properly documented and repeatable by any entity choosing to use the Study Designs created. A separate Study Design should be used when there is variation in spatial or temporal designs, or variation in the data analysis or collection methods used in the specified design. A Metadata file must be posted as a public document in Pisces upon completion of contracted work and provided to any electronic data repository that stores the data collected under this scope of work. An export of BPA Pisces SOW, CBFish project location reports, and content from your Study Design at http://monitoringmethods.org may serve as core material for your metadata record. Additional documentation and guidance for creating metadata records may be found at http://www.pnamp.org/metadata. Data must be made available at completion of work by entering the Data Repository location in http://monitoringmethods.org. To support this, one may select the name of the Data Repository/database as documented at http://monitoringmethods.org or create a new entry. This includes URL/web address/FTP links or other relevant links to the data, as well as contact information for the person who administered the database that stores the data collected under this statement of work. In most cases a dataset may be joined with other data in a larger data repository or warehouse, or be a node in a data set for a specific year or location. In some cases, data set names are a discrete data file stored in a specific file folder on a personal computer. If your data is identified in Monitoring Resources as “No data repository, or not electronically available,” then a document must be attached that provides detailed information on how to attain the data analyzed under this WE. This must include contact information of the data manager in the form of: name of the person, position tile, phone number, email, and web address. NOTE: Proper documentation of this information informs researchers and policy staff where data and assessments are located, which is essential for primary or secondary assessments based on a project’s data collection efforts. When applicable, your deliverables should include recommendations to support the management questions or Biological Opinion RPA identified in the project’s proposal.


Deliverable Status:
Required
Default Deliverable Desc:
Data
Potential Deliverables:
  • Data and the Data Repository name
  • "Published" Study Design in MonitoringMethods.org
  • Metadata file posted to data files collected under this scope of work

  • Rule 1 (Environmental Compliance): Any associated ESA, cultural resources, NEPA, permitting, or other environmental compliance work should be split out under 165. Produce Environmental Compliance Documentation.

    Example:

    WE: 157. Collect/Generate/Validate Field and Lab Data
    WE Title: Collect water quality and habitat data in Fish Creek

    WE: 165. Produce Environmental Compliance Documentation
    WE Title: Environmental compliance for data collection activities
    WE Description: Work with BPA to obtain environmental compliance and cultural resource surveys associated with data collection activities under the contract.

  • Rule 2 (Location of Work): If you are collecting data at various locations, you may lump these under a single work element as long as the data collected at each site is the same (i.e., you're using the same protocol and methods at each site). However, you may break the work into separate work elements if it provides clarity or better supports project management.

    Examples:

    Option 1 (lumping):

    WE: 157. Collect/Generate/Validate Field and Lab Data
    WE Title: Collect water quality and habitat data in Walla Walla Subbasin
    WE Description: Collect water quality and habitat data in Lower Walla Walla River, Touchet River, Mill Creek, Little Walla Walla, and North and South forks using Monitoring Methods protocol PIBO.

    Option 2 (splitting):

    WE: 157. Collect/Generate/Validate Field and Lab Data
    WE Title: Collect water quality and habitat data in lower Walla Walla Subbasin
    WE Description: Collect water quality and habitat data in Lower Walla Walla River, Touchet River, and Mill Creek using Monitoring Methods protocol PIBO.

    WE: 157. Collect/Generate/Validate Field and Lab Data
    WE Title: Collect water quality and habitat data in upper Walla Walla Subbasin
    WE Description: Collect water quality and habitat data in Little Walla Walla, and North and South forks of Walla Walla River using Monitoring Methods protocol CHaMP.


Milestone Title
Type
Deliverable?
Description

Environmental compliance requirements complete -New
Required
No
On-the-ground work associated with this work element cannot proceed until this milestone is complete. Milestone is complete when final documentation is received from BPA environmental compliance staff.
Equipment Calibration
Recommended
No
Projects utilizing equipment that requires calibration (e.g. temperature sensors, water quality instruments, ect.) shall calibrate the equipment annually prior to use.
Review, revise, and finalize study plan sample design protocol and methods in MonitoringResouces.org
Required
No
The Study Plan's Sample Design, Protocol and Methods for this work element are stored at MonitoringResources.org and need to be completed (i.e., "Finalized" through MonitoringResources.org), preferably prior to data collection. Preparations for contract renewals must include reviewing any previously finalized Sample Designs, Protocols & Methods to ensure that they are consistent with how work will be done in any subsequent contract.
Install fish monitoring equipment
Suggested
No
May include the installation of a weir, trap, electronic portal, or other equipment or facility used to monitor fish passage or to collect juvenile or adult fish.
Provide EC Lead with the status of RM&E ESA Permit(s) (RM&E ESA)
Suggested
No
Provide EC Lead with the status of RM&E ESA permits:  type of permit(s) [e.g. Sec 4(d), 7 or 10] required by the Services (NMFS, USFWS), when applied, permit status, responses from the Services.  Once final permit(s) is received, forward a copy or copies to EC Lead for review and documentation of completion of ESA for WE.
Implement Study Plan
Recommended
No
Implement the study plan's protocols and sample design consistent with the WE description and methods in the SOW. The start date of this milestone is used to set the completion date for the EC milestone.
Process Field Samples/Specimens
Suggested
No
Process sample types, / samples by describing methods, and if the contractor or a subcontractor will be doing the work. e.g., tissue, macroinvertebrate, or water quality samples.
Secure data back-up
Recommended
No
Minimum requirements: Hard copies of field sheets and original dataloggers secured against fire and flood. At least daily data back-up of electronic data on a separate hard drive. Secure cloud-based or off-site location data back-up to preclude catastrophic data loss at least weekly. More frequent cloud/off-site back-up is greatly encouraged.
[TIMING GUIDANCE: FROM BEGINNING TO END OF CONTRACT. DELETE THESE BRACKETS AND ALL TEXT WITHIN THEM]
Yearly upload of error-checked datasets
Recommended
No
Upload datasets with associated metadata to a publicly accessible site each year as soon as they have been QA/QC checked. This generally happens within 6 months for direct field-to-database input, but may be longer if laboratory analysis is required (e.g., scale reading or genetic analyses). If data is not QA/QCed within 1 year, data must be made accessible with acknowledgement of QA/QC limitations. Periods for dataset collection should be no longer than a year, and coincide with the logical biology of the data collection, which may not be on a calendar year. Example of a dataset: redd counts for one species for one season for a particular brood year.

Dataset upload requirements apply to both original and derived data, which should be at a level of quality suitable for release to resource co-managers to make decisions – not the rigor required as if you were going to use the data for a peer-reviewed publication.
Produce accessible, error-checked datasets
Required
Yes
[DELETE THE GUIDANCE BELOW AND PROVIDE A DESCRIPTION OF DATABASE LOCATION. IF THIS MILESTONE IS RETAINED, DELETE THESE BRACKETS AND ALL TEXT WITHIN THEM.]
The deliverable for this work element is an error-checked dataset of the raw data uploaded to a publicly accessible site. That site is identified in the sample designs and the RM&E metadata section of the SOW. The dataset has a distinct set of variables (data fields) and may be captured in a flat or relational database.
Notes: 1. In your annual report (WE 132), you are required to provide a link to your data set with a file name in the report's first appendix. If not web accessible, provide instructions (e.g., file name, directory, or position title) for accessing data.
2. Any derived data will be produced under work element 162, Analyze Data.


4 Metrics Associated With Work Element 157: Collect/Generate/Validate Field and Lab Data

Metric Metric Association Status Last Comment Date Last Comment By Unit Type FY Start FY End Required / Optional Is Activated By Default Included in PI Supports PCSRF/PNSHP (Katz) PNSHP Metric Code PNSHP Metric
1464: Primary R, M, and E Focal Strategy [Population Status, Hydrosystem, Tributary Habitat, Estuary/Ocean, Harvest, Hatchery, Predation, Multiple Strategies] Active RMEFocalAreaList 2005 Required Yes No No
1472: Primary R, M, and E Type [Status and Trend Monitoring, Action Effectiveness Research, Uncertainties Research, Project Implementation/ Compliance Monitoring] Active RMETypeList 2005 Required Yes No No
1478: Secondary R, M, and E Type [Status and Trend Monitoring, Action Effectiveness Research, Uncertainties Research, Project Implementation/ Compliance Monitoring] Active RMETypeList 2005 Optional Yes No No
1495: Secondary R, M, and E Focal Strategy [Population Status, Hydrosystem, Tributary Habitat, Estuary/Ocean, Harvest, Hatchery, Predation, Multiple Strategies] Active RMEFocalAreaList 2009 Optional Yes No No

Location Requirement Type:
Location Sample Site in Monitoring Resources
Location Guidance:
Location data should now be entered into monitoringresources.org

Applicability and status of the following environmental compliance requirements can be found on the Environmental Compliance tab for that work element in your SOW for all 2007 contracts forward. BPA's Environmental staff will update and maintain this information in CBFish in real time, so that you can check the status of environmental compliance on your project at any time.

Note: Many of the fields are set to auto-load in CBFish, but the settings will be reviewed by BPA's Environmental staff prior to the contract being finalized, and may be revised depending on the specific circumstances.

  • National Environmental Policy Act (NEPA)
    NEPA coverage for this work element will be determined by BPA's Environmental staff and could include an Environmental Impact Statement (EIS), Environmental Assessment (EA), Record of Decision to an existing EIS, or Categorical Exclusion.

  • Endangered Species Act (ESA)
    ESA consultation is typically required for this work element.

  • National Historic Preservation Act (NHPA)
    NHPA Section 106 consultation is typically not required for this work element.

  • Public Involvement
    Public involvement is typically not required for this work element.


Reports that Use this Work Element

This work element and its metrics are used in measures in the following reports. These PDF reports are generated dynamically, always showing you the most up to date information. Most of them also have links to download the underlying data sets to structured text or Excel format.

Stats and Overview

Number of active contracts using Work Element #157 by FY

Top 5 BPA Project Managers using this Work Element:
(by number of current contracts)
Tracy Hauser 299
Deborah Docherty (Inactive) 292
Virgil Watts III 272
Jonathan McCloud 181
Jamie Cleveland (Inactive) 170
Average Work Element Budget: $62,084
Average Duration: 10 months