140R3025R0002_-_Attachment_1_-_PWS.pdf

Attachment 1

Performance Work Statement

This page intentionally left blank

ATTACHMENT 1

PERFORMANCE WORK STATEMENT (PWS)

Monitoring Adult Population(s) of Razorback Suckers in Lake Mohave, AZ-NV

1.0 GENERAL: This is a non-personal services 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 solely 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 this PWS except for those items specified as government-furnished property and services.

The contractor shall perform to the standards in this contract.

1.2 Background: The razorback sucker (Xyrauchen texanus) is one of four large bodied river fish species native to the Colorado River Basin. Currently listed as endangered under the authority of the Endangered Species Act of 1973 (USFWS 1991), the razorback sucker was historically abundant throughout the Basin and was predominantly found in the main stem river and major tributaries of Arizona, California, Nevada, New Mexico, Utah, and Wyoming (USFWS 1998). The current distribution and abundance of razorback suckers are greatly reduced from historic levels, mainly due to main stem dam construction and the introduction of non-native game fish species (Minckley et al. 1991). Populations have however persisted following the creation of reservoirs in the lower Colorado River Basin, but this has only been possible due to recruitment events occurring soon after dam closures (Minckley 1983) and ongoing fish augmentation (Mueller 2006).

Current monitoring efforts focus on identifying annual spawning sites, locating and capturing adult razorback sucker, recording biological data of captured fish, collecting tissue samples from captured fish for genetic analyses, and using capture data and remote scanning of passive integrated transponder (PIT) tags to provide zone specific and lake-wide population estimates.

The adult population in Lake Mohave remains the most genetically diverse among razorback sucker populations and acts as the primary brood stock for this species. The LCR MSCP currently captures the offspring of this stock directly from Lake Mohave and rears them at Willow Beach National Fish Hatchery for future repatriation. Monitoring the Lake Mohave razorback sucker population through annual sampling and collection efforts will ensure the availability of suitable offspring for future LCR MSCP augmentation needs. This monitoring effort will also support ongoing razorback sucker conservation efforts by providing sound data on which management decisions can be made.

A-

2.0 SCOPE

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

Locating and capturing/contacting adult razorback suckers Locating and capturing larval razorback suckers Recording biological data (e.g. sex, total length, weight), documenting the

PIT tag number, and examining the general health and condition of captured adult razorback sucker

Collecting tissue samples from captured adult razorback sucker for genetic analysis (Samples may be provided to the designated Contracting Officer’s Representative [COR] or shipped directly to a lab of Reclamation’s choosing. The contractor is not responsible for reporting results of these analyses.)

Marking of captured adult razorback sucker with PIT tags for individual identification (only if fish have not been previously tagged)

Using mobile, remote PIT tag scanning units capable of deployment in both slack water and riverine sections of Lake Mohave

Participating in a maximum of two (2) annual, weeklong, multi-agency, survey events to take place in the spring (March) and fall (November or December) of each contract year (In the event these surveys do not take place, the contractor may conduct additional remote scanning during these periods.)

Providing estimates for current repatriate, and if possible, wild, razorback sucker populations

Assimilating Lake Mohave razorback sucker capture/contact data collected by other federal and non-federal entities into population estimates

Providing monthly progress reports summarizing all field, laboratory, or office work completed in the course of this effort

Providing copies of all data sets generated in the course of this work to the designated COR

Providing a draft interim report during each contract year for review by LCR MSCP staff

Providing a final interim report for each completed contract year Providing a draft project report during the final option year Providing a final project report for the complete contract Attending the annual CRAB meeting and presenting monitoring results

3.0 TASKS: The contractor shall perform the following tasks:

3.1 Monitoring

Monitoring efforts shall be initiated in Lake Mohave, AZ-NV with the goal of assessing the current razorback sucker population(s). A variety of sampling techniques may be used in this effort; however, trammel netting and remote scanning for 134.2 kHz passive integrated transponder (PIT) tags are required. The majority of monitoring will be conducted in areas of

Lake Mohave where razorback suckers are known to reside (River Miles (RM) 290-305, 312- 325, and 330-342). The contractor shall provide an initial estimate of the extant population(s) and determine the age of captured individuals and identify any recruitment pattern apparent from the population age structure. These activities shall support razorback sucker conservation efforts in Lake Mohave.

Remote Scanning – Monitoring via remote PIT scanning shall be conducted for one (1) week (5 Days) of every month during each contract year. The majority of remote scanning shall be focused from RM 312 – 325 and 330 – 342.

Trammel Netting – Monitoring via trammel netting shall be conducted for up to two (2) weeks ( Days in a week) of each contract year and shall be scheduled to coincide with annual, multi-agency monitoring events occurring in March and November or December of each year. The majority of trammel netting shall be focused from RM 290 – 305.

Larval Collections – Active search and capture of razorback sucker larvae shall be conducted for two (2) nights in January, February, and April of each contract year. The majority of larval collections shall be focused from RM 325-330. Capture locations and target quantities will be determined by Reclamation for each sampling event.

The tasks listed above shall be performed for each year of the contract.

3.2 Reporting

Reporting of this effort shall occur on both a monthly and annual basis during each contract year.

The contractor shall provide a brief progress report at the end of each month (invoicing period) summarizing all field, laboratory, and/or office work completed in the course of this effort. The report shall include a narrative of the work accomplished as well as a summary of any collected data. The contractor shall also provide a Draft annual report, in the form of a Microsoft® Word document, by the first working day of December of each contract year. The draft report shall contain multiple sections including, but not limited to, an executive summary, introduction, methods, results, and conclusions/discussion. The draft report shall also be consistent with LCR MSCP visual identity guidelines and requirements. Following LCR MSCP review of the draft annual report, the contractor shall submit a revised Microsoft® Word version and a fully accessible Adobe PDF version of the Final annual report prior to the official end date for each contracted year. Any time extensions for the delivery of the Final annual report must be approved by the Contracting Officer. The Final annual report must also be consistent with the visual identity requirements of the LCR MSCP in order to be accepted. Additional information regarding reporting and submission requirements can be found in the Deliverables section below, and in Table 2.

3.3 Annual Meeting Attendance and Presentations

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. The contractor shall also attend Lake Mohave Native Fish Work Group (NFWG) meetings which will coincide with the CRAB meeting during each contract year, as well as informal NFWG meetings that are scheduled to coincide with two annual, multi-agency monitoring events in March and November/December.

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 February 8, 2025 through February 7, 2026.

Option Year 1 shall be February 8, 2026 through February 7, 2027.

Option Year 2 shall be February 8, 2027 through February 7, 2028.

Option Year 3 shall be February 8, 2028 through February 7, 2029.

Option Year 4 shall be February 8, 2029 through February 7, 2030.

4.2 Place of Performance: Lake Mohave, AZ-NV

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. All payments will be made in accordance with the payment schedule which is based upon the below submittals schedule. Payment schedule is subject to approval by the COR.

6.0 PERMITS

Contractor shall possess within no later than 10 days after award, all necessary permits and permissions to conduct this work. Copies of the permits or letters from these include, but may not be limited to the following:

A) Scientific collecting permits for Lake Mead National Recreation Area B) USFWS Endangered Species Permit to cover take of ESA species in the study area C) Scientific Collection Permit from Arizona Game and Fish Department D) Scientific Collection Permit from Nevada Division of Wildlife

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 DELIVERABLES: The contractor shall submit the following reports in accordance with paragraph 9.0, “LIST OF CONTRACTOR SUBMITTALS”:

7.1 Monthly Progress Report

The contractor shall provide a brief letter report summarizing work completed each month. The report shall include a narrative of the work completed as well as a summary of collected data.

7.2 Draft Interim Report

The contractor shall electronically submit a draft interim report in the form of a Microsoft® Word document prior to the completion of each contract year. The draft report shall contain multiple sections including, but not limited to, an executive summary, introduction, methods, results, and conclusions/discussion. The draft report shall be consistent with the visual identity guidelines and requirements of the Lower Colorado River Multi-Species Conservation Program (LCR MSCP). Upon award, the Bureau of Reclamation (Reclamation) will provide the contractor with instructions for meeting all reporting requirements and with templates for all report pages requiring LCR MSCP visual identity elements. The draft report shall be submitted on or before the 1st of November of each contract year. The draft review process will include two reviews by the Contracting Officer’s Representative (COR). In the first review, the COR will provide comments and/or suggestions deemed necessary for incorporation into the Draft Interim Report and will return the draft report to the contractor within two weeks. The contractor will have two weeks to address and/or incorporate comments and suggestions and resubmit the Draft Interim Report for final review. The final review will also be accomplished within two weeks and will be completed by the COR and the LCR MSCP technical editor. The contractor will have the remainder of the performance period to address and/or incorporate any additional review comments.

7.3 Final Interim Report

The contractor shall address all 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 by the 7th of February for each contract year. Any time extensions must be approved by the Contracting Officer. The Final Interim Report must be consistent with the visual identity requirements of the LCR MSCP to be accepted.

7.4 Draft Project Report

The contractor shall electronically submit a Draft Project Report in the form of a Microsoft® Word document on or before the 1st of November of the last executed option year. The report shall be comprehensive and incorporate findings and results from all contract years. 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 will follow the same schedule and process as outlined for the Draft Interim Report.

7.5 Final Project Report

The contractor shall address all 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 the 31st of December for the last executed option year. Any time extensions must be approved by the Contracting Officer. The Final Project Report must be consistent with the visual identity requirements of the LCR MSCP to be accepted.

7.6 Data Sets

Reclamation is the owner of all data obtained in the execution of this effort. The contractor shall provide copies of all raw data sets on a quarterly schedule during each contract year. For statistical analyses, the contractor shall provide all input and output data from analyses run, the name and version of the statistical program(s) used, the party from whom the model was obtained, citation information about the program(s) used, and a description of statistical procedures. If code is used, the COR shall receive a copy of the input code. If a menu-based program is used, the COR shall receive information detailing the commands used. Data shall be made available at any time within the performance period upon the request of the COR. The contractor shall also meet any additional LCR MSCP data management requirements as outlined in Appendix 1.

8 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 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

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

Meetings Attend and present at both CRAB and NFWG meetings

Contractor will prepare and present findings at annual meetings.

95% attendance at meetings

9 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-

CO 1 0 Within thirty (30) days of notice of award.

002 Safety Program DIAR 1452.223-81 COR 0 1 Within thirty (30) days of notice of award.

003 Annual Meeting Attendance and Presentations

Section 3.0, Paragraph 3.3

COR 0 1 January, March, and November or December of each year.

004 Scientific permits for collecting native, non-native, and endangered fish species

Section 6.0 COR 1 1 Within ten (10) days of award date.

005 Monthly Data Collection Report

Section 7.0, paragraph 7.1

COR 0 1 Submit with monthly invoice.

006 Draft Interim Report Section 7.0, paragraph 7.2

COR 0 1 Due on or before December 7th of each year.

007 Final Interim Report Section 7.0, paragraph 7.3

COR 0 1 Due on or before February 7th of each year.

008 Draft Project Report Section 7.0, paragraph 7.4

COR 0 1 Due on or before December 7th of the last executed option year.

009 Final Project Report Section 7.0, paragraph 7.5

COR 0 1 Due on or before February 7th of the last executed option year.

010 Data Sets Section 7.0, paragraph 7.6;

Appendix 1

COR 0 1 April 7th, July 7th, October 7th, January 7th

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

10.0 REFERENCES

Holden, P.B. and C.B. Stalnaker. 1975. Distribution of fishes in the Dolores and Yampa River systems of the upper Colorado Basin. Southwestern Naturalist 19:403-412.

Joseph, T.W., J.A. Sinning, R.J. Behnke, and P.B. Holden. 1977. An evaluation of the status, life history, and habitat requirements of endangered and threatened fishers of the upper Colorado River system. U.S. Fish and Wildlife Service, Fort Collins, CO. FWS/OBS Rep. 24, part 2. 183 p.

Minckley, W.L. 1983. Status of the razorback sucker, Xyrauchen texanus (Abbott), in the Lower Colorado River Basin. Southwestern Naturalist 28: 165-187.

Minckley, W.L., P.C. Marsh, J.E. Brooks, J.E. Johnson, and B.L. Jensen. 1991. Management toward recovery of razorback sucker. In: W.L. Minckley and J.E. Deacon, editors. Battle against extinction: native fish management in the American West. Tucson: University of Arizona Press.

pp. 303-357.

Mueller, G.A. 2006. Ecology of Bonytail and Razorback Sucker and the Role of Off-Channel Habitats in Their Recover. U.S. Geological Survey Scientific Investigations Report 2006-5065, 64 p.

U.S. Fish and Wildlife Service (USFWS). 1991. Endangered and threatened wildlife and plants;

the razorback sucker (Xyrauchen texanus) determined to be an endangered species; Final rule.

Federal Register 56 (23 October 1991): 54957-54967.

U.S. Fish and Wildlife Service (USFWS). 1998. Razorback Sucker (Xyrauchen texanus) Recovery Plan. Denver, Colorado. 81 p.

Wick, E.J., C.W. McAda, and R.V. Bulkley. 1982. Life history and prospects for recovery of the razorback sucker. In: W.H. Miller, H.M. Tyus, and C.A. Carlson, editors. Fishes of the upper Colorado River System: present and future. American Fisheries Society, Western Division, Bethesda, MD. pp. 120-126.

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 quarterly 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), Work Task(s), website.) Abstract format, 1-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)

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: Main Work Task

Number(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)

Date Data Collection ended

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

Coverage Fiscal Year

(Fiscal Year covered by this document/data collection)

Coverage area

(What geographical area was the data collected in)

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)

(Work Task(s) associated with this data - Contact COR for number(s))

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)

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 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 Lower Colorado River Multi-Species Conservation Program PO Box 61470 Boulder City, NV 89006

LC-8326

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

LC-8326