ATTACHEMENT_1_140R3021R0024_Performance_Work_Statment.pdf

Solicitation: 140R3021R0024

REACH 4/5 NATIVE FISH MONITORING

Attachment 1 Performance Work Statement

This page intentionally left blank

ATTACHMENT 1

PERFORMANCE WORK STATEMENT (PWS)

REACH 4/5 NATIVE FISH MONITORING

1.0 GENERAL

This is a non-personal service contract to provide monitoring and data management support. The Government shall not exercise any supervision or control over the contract service providers performing services herein. Such contract service providers shall be accountable soley to the Contractor who in turn is responsible to the Government.

1.1. Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials supervision, and other items and non-personal services necessary to perform monitoring and data management support as defined in the PWS except for thos items specified as government-furnished property and services. The contractor shall perform to the standards of this contract.

1.1 Background: The razorback sucker (Xyrauchen texanus) and bonytail (Gila elegans) are two of four endemic, large-river fish species of the Colorado River Basin presently considered endangered by the U.S. Fish and Wildlife Service. Both species are heavily reliant upon stocking programs in order to maintain a presence in the main stem of the Colorado River. The Multi Species Conservation Program (MSCP) has been stocking fish since 2004. The program has a base stocking requirement of 6,000 razorback and 4,000 bonytail per year into Reach 4/5, Parker Dam to Imperial Dam, for 45 years with all fish ≥ 305mm. In addition to the base stockings, the MSCP has an accelerated stocking requirement. The accelerated stockings provide an additional 6,000 razorback and 4,000 bonytail per year over a 10-year period. These fish are designated for intensive research and monitoring. Currently all fish are released with a full duplex 134.2 kHz Passive Integrated Transponder (PIT) tag. (Bureau of Reclamation 2015)

The fish community in Reach 4/5 is comprised primarily of introduced non-native fishes which support a popular recreational sport fishery. Native fish populations are comprised entirely of stocked fish, but only razorback sucker have been documented to survive multiple years.

Bonytail have only been detected within months of their release, with post-stocking contacts diminishing rapidly. The razorback sucker population is comprised of several hundred fish, with numerous year classes represented in the population. Their current distribution appears centered around the section of river near the A-10 and C-7 backwaters (Haas et al. 2020), and a known spawning aggregate was discovered in the main channel just upstream of the C-7 backwater.

This group of razorback suckers and the other spawning site in A-10 Upper are the only known spawning aggregations and are an invaluable source of data for current research and monitoring activities.

This project is in support of the MSCP (http://www.lcrmscp.gov). The purpose of this monitoring is to assess the current repatriate razorback sucker and bonytail populations in Reaches 4/5 of the MSCP, as well as their relative distribution throughout these Reaches. If enough data are available, population and survival estimates will be calculated. In addition, any http://www.lcrmscp.gov/ potential factors that may influence survival should be evaluated (i.e. size at release, location of release, and season of release). Detailed estimates of survival and distribution could allow for alterations in current stocking and survey protocols. All data summaries will be provided using proven and repeatable statistical analysis. These activities will support razorback sucker and bonytail conservation efforts throughout the LCR by providing information for the continued development and maintenance of repatriated razorback sucker and bonytail populations.

The MSCP will release razorback sucker and bonytail annually from September through May during each study year. Release locations have historically been focused on the A-7 to C-10 section of river, but fish may be directed to other areas within Reach 4/5. If fish and resources are available, the MSCP will stock these alternate areas a year prior to them being surveyed.

2.0 SCOPE

This monitoring effort shall be accomplished over a five year period of performance. The services will include larval surveys, remote PIT scanning surveys, and broad scale telemetry for razorback suckers. The study area will include the main channel and connected backwaters between Palo Verde Diversion Dam and Imperial Dam. The totality of surveys over the course of this project is intended to inform management on where future monitoring shall be directed.

2.1 Objectives: The objective of this contract is to acquire services for monitoring and data management support.

The contractor shall assess the current populations for both razorback sucker and bonytail in the river and connected habitats between Palo Verde Diversion Dam and Imperial Dam using larval surveys, remote PIT scanners, and sonic telemetry.

The contractor shall assimilate data collected by other federal and non-federal entities.

The contractor shall monitor the current known population of razorback sucker annually

(A7 – C7) and survey the entire study area by the end of the fourth year in search of other aggregations of native fish.

The contractor shall provide estimates of abundance, survival, and distribution of native fish annually for the surveyed areas and for the entire study area by the end of the fifth year. The fifth year of the project shall focus on the areas that best represent the total populations of native fish.

The contractor shall provide copies of all data sets to the designated Reclamation Contracting Officers’ Representative.

3.0 TASKS: The contractor shall perform the following tasks:

3.1 Monitoring

The contractor shall contact razorback and bonytail using mobile remote PIT tag sensing units capable of detecting full duplex 134.2 kHz tags and deployable in backwater, slack water and riverine sections of the Colorado River.

The contractor shall conduct eight monitoring trips across multiple sub-reaches and habitat types within Reaches 4 and 5 of the MSCP from November through April of each year. This will include a minimum of one trip/month plus two discretionary trips for supplemental data acquisition. Ensure scanners are distributed throughout entire designated sub-reaches each study year. All scanning data shall be uploaded to the Lower Colorado Native Fish Database.

For the purpose of the project, the contractor shall divide the study area into five sub-reaches. One of the newly defined sub-reaches shall encompass the known distribution and population centers for razorback suckers between the A-7 backwater and the C-7 backwater. By the end of the fourth year, the entire study area will have been surveyed at least once and the A-7 to C-7 area will have been surveyed for four years.

Years 1 through 4: In order to explore new areas and still monitor the current known populations of native fish, a total of 2 subsections will be monitored annually. This will include the A7-C7 section annually along with one other subsection of river. For instance, year 1 would be below Palo Verde down to I-10 Bridge, plus A7-C7; year 2 from Walters Camp down to Picacho State Park, plus A7-C7; Year 3 – Picacho State Park to Imperial Ponds, plus A7-C7; Year 4 – Imperial Ponds to Imperial Dam, plus A7- C7. Sections within Reach 5 may need to be smaller due to more diverse habitat and remoteness. These are hypothetical delineations for sub-reaches and the offeror may propose alternate delineations.

Year 5: Monitoring effort will remain the same, but locations will be determined based on results from all known data sources. Effort will be distributed to ensure data are adequate for Reach-wide population and survival estimates.

The contractor shall conduct broad scale multi-year telemetry monitoring primarily via passive receivers (i.e., the Submersible Ultrasonic Receiver sold by Sonotronics Inc., or something similar) on 10 sonic tagged resident adult razorbacks per year to determine relative dispersal, and seasonal movements. The telemetry should inform us if the fish are using the entire study area or specific sections. There are no physical barriers from preventing fish from moving throughout the study area. The telemetry is not expected to be intense, and the use of passive receivers should provide the necessary data to direct ongoing PIT scanning efforts. These tags should have a minimum battery life of 36 months. These fish may be sourced directly from the resident population during annual electro-fishing events. The offeror will provide the surgery equipment and qualified staff to perform the surgeries under the guidance and authority of the MSCP. All tag types should be appropriate for the size of fish being tagged.

The contractor shall sassimilate and summarize all Reach 4/5 razorback sucker and bonytail contact data collected by other federal and non-federal entities into mark-recapture population estimates for each species with 95% confidence intervals. The preferred MSCP population estimate is the modified Peterson formula using the definitions for M, C, and R as described in Hass et al. 2020.

If data are adequate, the contractor shall use mark-recapture modeling to provide estimates for adult survival (with 95% confidence intervals) and assess its dependence on a variety of factors (i.e. size at release, location of release, and season of release) for all razorback and bonytail released since 2005. If data are inadequate for a model-comparison assessment of all factors, use exploratory analysis to identify their potential relationship to scanning contact rates (e.g., with graphs and/or correlation analysis).

The contractor shall participate in MSCP led electro-fishing surveys: This will be up to 2 weeks per year and performed in conjunction with monitoring trips.

The contractor shall include broad scale spatial larval sampling for razorback suckers to identify or confirm current and or new spawning areas

3.2 Reporting

Any and all methods, techniques, and equipment used by the contractor in the course of this study to contact, mark, and track razorback and bonytail should be described in detail and given a purpose. Chosen methods must be technically sound and appropriate for achieving stated goals and objectives and will be reviewed prior to use by Reclamation. Timeframes (both time of year and duration) for all activities including but not limited to field work, lab work, and report writing must be clearly stated. Results must be achievable in the timeframe specified.

3.3 Meeting Attendence

In addition to the reporting requirements outlined herein, the contractor will also be required to attend the annual Colorado River Aquatic Biologist (CRAB) meeting and provide an oral presentation summarizing the results from the previous contract year. The meeting is scheduled for three days in early January in Laughlin, NV, and shall be attended by a maximum of two contractor personnel including the designated project lead. Presentations for all meetings shall be prepared in an electronic format that allows for in-room viewing and electronic sharing with remote participants.

4.0 GENERAL INFORMATION

4.1 Period of Performance: This contract shall be for one base and four option years as follows:

Base Year shall be October 1, 2021 through September 30, 2022.

Option Year 1 shall be October 1, 2022 through September 30, 2023.

Option Year 2 shall be October 1, 2023 through September 30, 2024.

Option Year 3 shall be October 1, 2024 through September 30, 2025.

Option Year 4 shall be October 1, 2025 through September 30, 2026.

4.2 Place of Performance: Colorado River near Blythe, CA. This work shall be accomplished along the lower Colorado River and its connected backwaters between Palo Verde Diversion Dam and Imperial Dam. This section of river has limited access and the project will require remote field work.

4.3 Quality Control: The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure nonrecurrence of defective services. The contractor’s quality control program is the means by which they assure themselves that their work complies with the requirement of the contract.

4.4 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Performance Requirements Summary (PRS) as identified in section 7.0 of this PWS.

5.0 INVOICES

Invoices shall be submitted concurrently with, or following the completion and transmission of, the stated deliverables (Monthly Summary). All payments will be made based upon proposed payment schedule. Proposed payment schedule is subject to approval by the COR.

6.0 PERMITS

Contractor shall possess within no later than 30 days after award, all necessary permits and permissions to conduct this work.

The Government reserves the right to identify and require additional permits or letters as determined necessary by local, state and federal laws and regulations. Adequate notification will be provided as determined by the Contracting Officer.

7.0 PERFORMANCE REQUIREMENTS SUMMARY (PRS)

The Performance Requirements Summary (PRS) chart identifies the required services / tasks, the performance standards, and the acceptable quality level. The Contractor’s performance is evaluated on the basis of a number of performance elements relating to quality and timely performance. The applicable performance elements are identified in the PRS and each element is weighted in terms of its relative importance to the contract requirement.

Quality assessments will be conducted by Reclamation personnel in the form of reviewing data sets submitted, monthly progress reports, draft reports and final reports.

Table 1

Task No.

Task Description

Performance Indicator

Performance

Standard

Minimum Acceptable Quality Level

3-1 Services conducted in accordance with Contractor’s schedule & technical approach

Perform services in accordance with technical approach

All required services performed on time and in accordance with Contractor’s schedule & technical approach

100 % of established timelines for services are met

3-2

Reporting & Data Submission

Submit monthly progress reports and annual draft & final reports. Provide copies of all generated data sets to COR

All deliverables submitted on time and in accordance with Table 2 of the Statement of Work.

All data submitted so that it can be clearly understood.

100% of established timeline for deliverables and collected data be provided to Reclamation

3-3

Meetings Attend and present at CRAB meetings

Contractor will prepare and present findings at annual meetings.

90% attendance at meetings

8.0 LIST OF CONTRACTOR SUBMITTALS

The contractor shall provide the following data and reports as follows:

Table 2

RSN Submittals Required Reference paragraph or clause

Responsible Code

Number of sets to mail to*:

Due date or delivery date

CO COR

001 Liability Insurance FAR 52.228-

5 & DIAR

1452.228-70

CO 1 0 Within five (5) days of Task Order issued.

002 Safety Program DIAR 1452.223-81

COR 1 1 Within five (5) days of Task Order issued.

003 Draft Study Plan COR 1 1 Within fifteen (21) days of Task Order issued.

004 Final Study Plan COR 1 1 Within forty-five (45) days of Task Order issued.

005 Monthly Summary COR 1 1 Submit with monthly invoice.

006 Annual Summary COR 1 1 Due on or before September 30 of each study year

007 Draft Interim Report COR 1 1 Due on or before September 30th for each study year except for the last executed study year.

008 Final Interim Report COR 1 1 Due within sixty (60) days of the end date for each study year except for the last executed study year.

009 Annual Presentation COR 1 1 At least once per year of the study

010 Draft Project Report COR 1 1 Due on or before August 1st of the last executed study year.

011 Final Project Report COR 1 1 Due on or before September 30th of the last executed study year.

012 Data COR 1 1 Submit with Draft Interim Reports, and Draft Project Report.

"CO" denotes the Contracting Officer; "COR" denotes the Contracting Officer’s Representative.

9.0 DELIVERABLES

The contractor shall submit the following reports in accordance with paragraph 8.0, “LIST OF

CONTRACTOR SUBMITTALS”.

9.1 Study Plans: The contractor shall electronically submit a draft study plan in the form of a Microsoft® Word or MS Word compatible document within 21 days of contract start date. The draft study plan will include a detailed plan for accomplishing the objectives and tasks of the project including analytical methods. The Contracting Officer’s Representative (COR) will review and make comments or suggestions deemed necessary. All comments and suggestions will be addressed and incorporated into the final study plan.

Final Study Plan: The contractor shall address all of the review comments from the draft study plan and make revisions, as necessary, to the draft study plan. The contractor shall submit a final study plan in the form of a Microsoft® Word document within 45 days of the start date. The final study plan will be implemented by the contractor and any changes will need to be approved by the COR.

9.2 Monthly Progress Report: The contractor shall electronically provide a brief letter report (approximately 1 page in length) summarizing all work completed each month. The report shall include a narrative of the work completed, a brief summary of all collected data, and a 2-month schedule for future field work.

9.3 Annual Summary: The contractor shall submit a written annual summary no more than one page in length by September 30th of the current study year. This summary shall include the previous year’s accomplishments and the current year’s planned activities. This summary will be used to complete the LCR MSCP’s annual “Final Implementation Report” for this work task.

9.4 Oral Presentation: The contractor shall give an oral presentation each year of the study at the annual CRAB meeting each January (http://www.lcrmscp.gov/crab/crab.html). The presentation shall be a summary of the findings for the past study year and the work being completed for the current study year.

9.5 Draft Interim Report: The contractor shall electronically submit a draft interim report in the form of a Microsoft® Word document prior to the end of Year 1 and each subsequent Option Year of the project except for the last executed option year. The report shall contain multiple sections including but not limited to, an executive summary, introduction, methods, results, conclusions/discussion, and recommendations. The draft report shall also be consistent with LCR MSCP visual identity guidelines and requirements. Upon award, Reclamation will provide the successful awardee with instructions for meeting all reporting requirements and with templates for all report pages needing LCR MSCP visual identity elements. The draft report shall be submitted on or before September 30th of each year. The draft review process will involve 2 reviews by the COR. In the first review the COR will review and make any comments or suggestions deemed necessary within 3 weeks of receiving the report. All comments shall be addressed and/or incorporated into the Draft Interim Report within 2 weeks and then resubmitted for final review. The final review will be accomplished within 2 weeks and this will include comments from the COR and the LCR-MSCP technical editor. All comments will once again be addressed and/or incorporated into the Draft Interim Report within 2 weeks prior to it being finalized by the contractor.

9.6 Final Interim Report: The contractor shall address all of the review comments and make revisions, as necessary, to the draft interim report. The contractor shall submit a Microsoft® Word version of the final interim report within 60 days following the end date for Year 1 and each Option Year of the project except for the last executed option year. Any time extensions must be approved by the Contracting Officer. The report must be consistent with the visual identity requirements of the LCR MSCP to be accepted.

9.7 Draft Project Report: The contractor shall electronically submit a draft project report in the form of a Microsoft® Word document on or before August 1st of Year 1 or the last executed Option Year. The report shall incorporate findings and results from each year of the project.

The report shall contain multiple sections including but not limited to, an executive summary, introduction, methods, results, conclusions/discussion, and recommendations. The report must be consistent with the visual identity requirements of the LCR MSCP to be accepted. The draft review process will involve 2 reviews by the COR. In the first review the COR will review and make any comments or suggestions deemed necessary within 3 weeks of receiving the report. All comments shall be addressed and/or incorporated into the Draft Interim Report within 2 weeks and then resubmitted for final review. The final review will be accomplished within 2 weeks and this will include comments from the COR and the LCR-MSCP technical editor. All comments will once again be addressed and/or incorporated into the Draft Project Report within 2 weeks prior to it being finalized by the contractor.

9.8 Final Project Report: The contractor shall address all of the review comments and make revisions, as necessary, to the Draft Project Report. The contractor shall submit a Microsoft® Word version of the Final Project Report by September 30th of the last executed option year.

Any time extensions must be approved by the Contracting Officer. The report must be consistent with the visual identity requirements of the LCR MSCP to be accepted.

9.9 Data Sets: Reclamation is the owner of all data obtained in the execution of this effort. The contractor shall meet the LCR MSCP data management requirements as outlined in appendix 1.

Appendix 1 LCR MSCP Data Management Requirements

Contractors shall submit to the LCR MSCP external SharePoint a data package that includes all raw data (unedited), QC/QA (edited) data, all data input and output processes, scans (.pdf format) of datasheets, photos, video, and spatial (GIS) data, including all other associated files on a biweekly basis. For data collected in methods outside of mobile electronic field forms (MEFFs), metadata will be provided with each data package. All files containing raw data shall include an accompanying metadata file that lists each variable, its definition, abbreviation and a description of how it is collected/measured. Reclamation’s requirements for data submission include a level of detail that allows repeatable analysis of the data in the future, i.e. the Contractor will be required to “show their work” in the analysis by providing input and output files/codes and process descriptions.

In compliance with the Department of Interior’s Data Management Policy, Reclamation’s policy states “Data shall be managed as a resource that supports the range of mission and functional areas across the Department. The Data Resource Management Program, in this regard, promotes the adoption of standards and practices that encourage the sharing and exchange of information to further enhance mission and business performance. The Department’s Data Resource Management Program provides guidance and governance for activities involved in the planning, definition, design, creation, formatting, storage, access, securing, archiving, maintenance, and sharing of data. These activities address data requirements from the conception of an information need through the logical design, physical implementation and on-going maintenance.” (DOI Series: Information Management, Part 378, Chapter 1, See: http://elips.doi.gov/elips/release/3713.htm )

Paper Documents - All paper documents used to collect data on behalf of Reclamation shall have a document number and be scanned to Adobe PDF using OCR text recognition; PDFs shall be organized within established folder architecture and catalogued in a MS Excel spreadsheet. Document numbering, folder architecture and formatting for all data sheets shall be established prior to any data collection in collaboration with the COR and the LCR MSCP Data Management Group. All fields on data sheets will be filled out. NO blank entries are allowed.

Metadata - All data and applications used by Reclamation in fulfilling its mission shall be properly documented with metadata. Non-spatial and spatial data shall be companied by Federal Geographic Data Committee (FGDC) (http://www.fgdc.gov/metadata/geospatial-metadata-standards) compliant metadata files (.html and/or .xml formats). All metadata shall have a title, reference date, topic category, abstract of data, point of contact, date stamp, description of processes and/or protocols used in collection, links to internal and external data types, identification (entities and attributes), creation, retrieval, management, and analysis of the data. All metadata shall also have a description of the major hardware/software components used for acquisition and post-processing of spatial data.

Spatial data shall include information on the horizontal and vertical accuracy of the data and how the accuracy was determined. Spatial data shall have GPS base station and control point information, projection/coordinate system and datum/units information, and any other information appropriate for future users of the data sets. Metadata format and entry shall be established prior to any data collection in collaboration with Reclamation. See the following table for examples of metadata standards for tabular data.

Example of LCR MSCP Metadata Standards for Tabular Data

Title (Title of tabular data workbook) Project Name Creator (Who created the data and their contact information), Jon Clear, Galapagos Bird Observatory, phone number and email address Subject data, MSCP, summary, riparian, LCR, species, etc.

Description (A textual description of content of the resource, including abstracts (what is this data, what is its purpose, how was it collected, QA/QC), contract number for BOR, year(s), Worktask(s), website) Abstract format, one-2 paragraphs

Publisher (Who at BOR is the main point of contact for this data, office phone number; also insert: This data is public property and is not being published in this form) XXXX (please use COR name here) at Bureau of Reclamation's Lower Colorado River Multi-Species Habitat Conservation Program (LCR MSCP), contact number: 702-XXX-XXXX. This data is public property and is not being published in this form.

Contributor (Who worked on the project; list all people who collected data, other contributors, etc)

Submitted (Date, when this data was submitted to BOR) November 1, 2013

Type (What type of data is this) tabular data Format (What format is the data in, list all) text and numbers Identifier (Unique number to this workbook use format:

MainWorktaskNumber(D7)Year(2013)-01, 02, 03, etc) D72013-01 (01 indicates a specific portion of the data such as presence/absence data)

Source (Data or product that this data or product is derived) This data is a summary of the raw XXXX (enter species name here) data collected in 2012.

Language (What language is this data in) English Relation (What other data is associated with this data or relevant, contract, etc?

List them) This data is 1 of 3 sets of data deliverables for contract number XXXXX. The other two are: D72012-02 (population data), D72011-03 (habitat data)

Date Data Collection began

(Date, when was the first day of data collection began) April 15, 2011

Date Data Collection ended

(Date, when was the last day of data collection ended) August 15, 2011

Coverage Fiscal Year

(Fiscal Year covered by this document/data collection) 2013-

Coverage area

(What geographical area was the data collected in) MSCP planning Area

Spatial Datum

(What is the datum, location units (if not applicable = N/A)) UTM Zone 11, NAD83 horizontal datum, NAVD88 vertical datum, in meters, and stored electronically in a spatial data file format (e.g., ESRI shapefile or geodatabase).

Work Task Number(s)

(What worktask are associated with this data- Contact COR for this number (s)) D7

Rights (A rights management statement, an identifier that links to a rights management statement, or an identifier that links to a service providing information about rights management for the resource) TBD

These standards above are a modification of the Dublin Core elements (http://dublincore.org/documents/usageguide/elements.shtml)

Naming Convention - The Contractor shall assist Reclamation in developing a cross-reference document that connects previous project site names with updated LCR MSCP standardized location names. These standardized location names will then be used for data entry, analysis, and reports during the contract period. A site and field data naming convention has been established by Reclamation for electronic document names, mobile electronic field forms names, excel columns, rows and table names, and database field names prior to any data collection in collaboration with Reclamation.

Tabular Data - Tabular data shall be stored in electronic format. All tabular data shall be accompanied with metadata or a description of the key fields and tabs (refer to section on Metadata). If there are multiple related tabular datasets, key fields and linkages of all relational tables in the data dictionary and metadata files must be provided. All fields in the tabular data will be filled out. NO blank entries are allowed.

Spatial Data - All GIS data and products shall be acquired or created in UTM Zone 11, NAD83 horizontal datum, NAVD88 vertical datum, in meters, and stored electronically in a spatial data file format (e,g. ESRI shapefile or geodatabase). When collecting project data, a project location shall be described either by including coordinates, representing the southwest and northeast corners of the project area or by a shape file of the project area. A http://dublincore.org/documents/usageguide/elements.shtml spatial file (shapefile, geodatabase, etc.) with a polygon shall be included that represents the project area and attributed relationships to all relevant data. GPS receivers and unit parameters shall be established by the Contractor and approved by Reclamation before collecting spatial data. Point and feature collection will fall into three categories. These categories are project dependent and shall be established by the Contractor with the Reclamation approval before collection of spatial data.

GPS - The GPS type, brand, and model must be included in the GPS data collection metadata. Contractor shall work with LCR MSCP Data Management Group for specification and recommendations of compatible/supported GPS devices prior to field collection.

Stewardship/Ownership - Because data is important to the Reclamation mission, anyone collecting data on behalf of Reclamation is responsible for data management and data stewardship. As the implementing agency for the LCR MSCP, Reclamation is the owner of all data obtained by those individuals or groups representing LCR MSCP, who obtain, create, maintain, and or have significant control over data. Data stewards are those individuals who ensure that adequate, agreed-upon quality data are maintained on a continuous basis during collection and analysis of the data. Before data is initially collected, strict protocols and procedures for data collection, quality assurance, storage, analysis, and transfer to Reclamation shall be established and in place by the Contractor before collecting data.

Before collecting data, a list of all applications used to collect and store data shall be provided to the COR and LCR MSCP Data Management Group. Reclamation shall review and approve all applications, protocols and procedures before any data is collected.

Although Reclamation shall develop the MEFFs with the Contractor, the Contractor is responsible for ensuring data security, maintenance, and backup while the MEFFs and data are in their possession. All re-entry of data must be documented. Any re-entry of data, etc.

due to Contractor error or failure is at Contractor’s expense

QA/QC - The Contractor, in coordination with Reclamation, shall develop QA/ QC measures for data collection, acquisition, evaluation and management.

Quality Assurance (QA) is defined as the regularly applied processes for preventing the introduction of erroneous information to a dataset. Common QA processes may include double entry, incorrect data entry, data field limiters or validation scripts, and many others.

Quality control (QC) is defined as post-entry review which includes: Correction(s) with date(s); Data Package Delivery completion (e.g. folder structure, file naming, all files included, file types, etc); and Evaluation of data to understand accuracy and precision and may include some degree of preliminary analysis. Together, QA/QC maximizes and documents data quality. QA/QC defines procedures to ensure documentation within archiving data and helps ensure the data may be properly applied and interpreted.

Review and Update - Data and Metadata shall be reviewed and updated on a regular schedule to maintain a high standard of quality. Each time the data, collection procedures, or analysis change, the metadata shall be updated at the same time. Scheduling of maintenance and the maintenance process shall be determined and scheduled by the Contractor with approval by the COR and LCR MSCP Data Management Group.

Statistical Analyses - The Contractor shall deliver to the COR via the LCR MSCP External SharePoint all data and outputs regarding any statistical analysis performed by the Contractor. This includes name and version of statistical program(s) used, the brand of computer and its operating system that the program requires, the party from whom the model is obtained, citation information about the program and description of statistical procedures used. The Contractor shall deliver to the COR via the LCR MSCP External SharePoint all input and output data from statistical analyses run. If code is used, the Contractor shall deliver to COR via the LCR MSCP External SharePoint a copy of the input code. If a menu based program is used, the Contractor shall deliver to the COR via the LCR MSCP External SharePoint a dictation of commands used. The Contractor shall deliver to the COR via the LCR MSCP External SharePoint all output data from statistical analyses run.

Backup - The Contractor shall provide a detailed description of their backup process to the COR and LCR MSCP Data Management Group. If the Contractor does not have backup procedures, one shall be created.

Accessing and Transferring Access - Access and security needs for the data shall be determined up-front in accordance with the project and established Reclamation policy.

Access and security needs shall be determined by Reclamation. The Contractor shall work with Reclamation in developing methods necessary to provide appropriate access and rights, in the format needed by the intended users.

Transfer - All data, reports, and maps (including electronic copies of completed original paper data sheets, original field notes, metadata, GIS and databases) produced during the project shall be submitted to Reclamation via LCR MSCP External SharePoint. All original completed paper datasheets and field notes shall be scanned into electronic copies using Adobe Acrobat using OCR recognition and cataloged in an Excel Spreadsheet prior to transfer. All raw spatial data files shall be cataloged in to an Excel Spreadsheet. The telemetry catalog shall reference the raw data files according to its specific project reporting.

A metadata file shall accompany all data and applications transferred to Reclamation via LCR MSCP External SharePoint (see Metadata above). If data is being accessed or transferred via web or proprietary application to Reclamation, a copy of the code and application shall be given to Reclamation via LCR MSCP External SharePoint. If the application was purchased from a third-party, the name of the application and the vendor name shall be given to Reclamation for acquisition.

Data shall be submitted electronically and in industry standard formats. For spatial data, ESRI shapefile and geodatabase formats shall be accepted, and each file must be accompanied by projection and metadata files. For raster datasets, ESRI GRID and ERDAS image formats shall be accepted, and each file shall be accompanied by projection and metadata files. AutoCAD dxf format shall also be accepted for spatial data if it is geographically referenced. For tabular databases, Microsoft Access or Excel, or delimited text file formats shall be accepted and each file shall be accompanied by a metadata file.

Metadata files in xml or txt, or html format shall accompany all spatial, data and database files.

Annual and final reports shall be submitted in Microsoft Word. In addition, the Contractor shall submit the final report in Portable Document Format (PDF). The PDF version of the report shall be fully accessible using the Accessibility/Full Check feature of Adobe Acrobat in order to meet Section 508 requirements under the U.S. Rehabilitation Act. Reclamation will provide information as needed to the Contractor’s Technical Editor in making final formatting changes to the document and meeting accessibility requirements.

Datasheets and field notes (if not recorded in MEFFs) shall be scanned and submitted in PDF format. When compiling a CD/DVD or portable hard drive with data written to multiple directories and/or subdirectories, a readme file defining contents of each directory shall be provided. When transferring data to LCR MSCP, a copy of all datasets will be created and delivered to the COR via LCR MSCP External SharePoint. Spatial data (GPS data and GIS files), and all aspatial data (scanned field data sheets, etc.) will be uploaded to via LCR MSCP External SharePoint.

Data Delivery - Spatial and aspatial data shall be delivered via LCR MSCP External SharePoint or if not available to US mail and or physically delivered (UPS/FedEx) to:

US Mail The Lower Colorado River Multi-Species Conservation Program PO Box 61470

LC-8315

Boulder City, NV 89006

Physical Address (UPS/FedEx) The Lower Colorado River Multi-Species Conservation Program 500 Fir Street Boulder City, NV 89005

Table 2