Attachment_1_-_PWS.pdf

PERFORMANCE WORK STATEMENT

MONITORING RAZORBACK SUCKERS IN LAKE MEAD,

ARIZONA–NEVADA (AZ–NV)

This Performance Work Statement (PWS) provides the Government’s overall requirements for this solicitation. Offerors shall use the PWS, together with other applicable portions of this Request for Proposal (RFP), as the basis for preparing their proposal. The offeror shall ensure all aspects of the PWS are addressed and propose the most appropriate methods for accomplishing the objectives and tasks required. Preparation of an effective proposal requires both an understanding of the tasks needed to satisfy the stated objectives and an ability to define what is required in specific, quantitative terms. The offeror's understanding of both the required results and the work effort required to accomplish them should be fully demonstrated in the offeror's proposal. The objectives and tasks listed below are the Government’s minimum requirements; however, the offeror may include value-added elements to these requirements as part of their proposal. The proposal should also specify in clear, understandable terms the work to be done in developing or producing the deliverables associated with each requirement.

1 SCOPE

1.1 OBJECTIVE

The objective of this contract is to acquire contract services to monitor the population of razorback suckers (Xyrauchen texanus) in Lake Mead, AZ–NV. Monitoring efforts shall be initiated with the goal of assessing the current razorback sucker population. The contractor shall provide an estimate of the extant population, document successful annual spawning through capture of razorback sucker larvae, determine the age of captured razorback sucker juvenile/subadult and adult individuals, and identify any recruitment pattern apparent from the population age structure. This monitoring effort will be accomplished through a contract with one (1) base year and up to four (4) additional option years. These activities will support razorback sucker conservation efforts in Lake Mead.

2 INTRODUCTION AND BACKGROUND

The razorback sucker 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).

In the late 1990’s, the Southern Nevada Water Authority and the Nevada Department of Wildlife initiated a study on Lake Mead to evaluate the stock of razorback suckers observed in localized areas of the lake. These observations were made in Las Vegas Bay and Echo Bay, and it was believed that the characteristics of these areas, increased turbidity and vegetative cover respectively, were the reason that these remnant groups of razorback suckers were able to persist. Since that time the Las Vegas Wash inflow and the Muddy River/Virgin River inflow have been confirmed as sites supporting recruiting populations of razorback suckers.

Lake Mead is the only reservoir in the lower Colorado River Basin that has been able to support a known, recruiting population of razorback suckers since the closure of various dams in the region.

The Lower Colorado River Multi-Species Conservation Program (LCR MSCP) is a partnership of Federal and non-Federal stakeholders created for the purpose of conserving native species and their habitats along the lower Colorado River. The Bureau of Reclamation (Reclamation) is the implementing agency of the LCR MSCP and is responsible for several monitoring projects within the program area. Included in these projects is the monitoring of razorback suckers in Lake Mead (LCR MSCP River Reach 1). Monitoring the Lake Mead razorback sucker population and characterizing the habitat types it uses will further the understanding of conditions that allow for successful recruitment. Identifying these conditions may make it possible to improve razorback sucker survival and conserve this species in other reservoirs where similar conditions persist.

3 TASKS

Reclamation is requiring that several specific tasks be accomplished as part of this LCR MSCP project. These tasks include, but are not limited to:

Intensive Monitoring

1) Locating and capturing larval, juvenile/subadult, and adult razorback suckers

2) Identifying annual spawning site locations within the study area

3) Marking of captured juvenile/subadult and adult razorback suckers for individual identification (to be accomplished only when no preexisting means of identification are present)

4) Monitoring movements and/or movement patterns of adult razorback suckers within the study area and identifying general habitat types where these fish are found

5) Recording biological data (e.g., sex, total length, weight, etc.), examining, and documenting the general health and condition of captured adult razorback suckers

6) Collecting tissue samples from captured juvenile/subadult and adult razorback suckers 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.)

Additional Monitoring

7) Monitoring movements and/or movement patterns of adult razorback suckers within the study area and identifying general habitat types where these fish are found Reporting

8) Providing monthly and annual reports detailing the results of the above tasks

9) Providing an estimate of the current Lake Mead razorback sucker population using data from all sources, e.g., the contractor, State agencies, Federal agencies, etc.

10) Providing mean daily and/or mean annual growth rates for recaptured razorback suckers

11) Characterizing the age structure of the Lake Mead razorback sucker population through appropriate aging techniques

12) Summarizing and incorporating remote monitoring data collected by Reclamation into annual reports

13) Providing copies of all data sets to the designated Reclamation Contracting Officer’s Technical Representative

Meeting Attendance and Oral Presentations

14) Attending the annual Colorado River Aquatic Biologist (CRAB) and Lake Mead

Work Group (LMWG) meetings and presenting project updates

All methods, techniques, and equipment used to capture, hold, mark, sample, record, or document razorback suckers shall be described in detail and given a purpose. Chosen methods must be technically sound and appropriate for completing project tasks and achieving stated objectives. 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.

Specifically, a description of when activities will begin, their expected duration, and how often they will occur shall be provided. If any flexibility is expected in the schedule, explain the basis for this flexibility. Results must be achievable in the timeframe specified.

3.1 INTENSIVE MONITORING (TASKS 1–6)

Intensive monitoring shall be conducted for eighteen (18) weeks during the preliminary and known spawning season (February–May) to take advantage of razorback sucker spawning aggregations. The onset, duration, and conclusion of the known spawning season are based on historical observations and previous monitoring efforts. Recent observations indicate a possible shift in the spawning season to earlier in the calendar year.

Efforts shall evaluate the validity of historical and/or recent observations, and findings will be used to suggest any changes to the required sampling schedule. All monitoring efforts shall be focused on, but not limited to, areas of the lake where razorback suckers are known to congregate (e.g., Las Vegas Bay, Echo Bay, Muddy River/Virgin River inflow, Bonelli Bay, Colorado River inflow, etc.).

3.2 ADDITIONAL MONITORING (TASK 7)

Additional monitoring shall include a total of five (5), one-week efforts which shall be conducted in the June–December time period during all contract years for the purpose of investigating adult razorback sucker movement patterns. The contractor shall use sonic telemetry to monitor sonic-tagged fish currently in the lake. The contractor shall identify the number of razorback suckers to sonic tag and release during the contract period that shall allow continued surveillance and documentation of movements and habitat use. Fish for sonic tagging shall be selected from captures during intensive monitoring efforts or obtained from other appropriate sources, as determined by the contractor. The contractor shall implant appropriate tags in individual fish and track these fish after release. The contractor shall utilize sonic telemetry to document the area(s) of the lake and the type(s) of habitat utilized by these fish outside of the known spawning season.

3.3 REPORTING (TASKS 8–12)

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 during 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 the eleventh (11th) month of each contract year. The draft report shall provide detailed results of each project task and 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 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.4 MEETING ATTENDANCE (TASK 13)

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 both spring and fall Lake Mead Work Group (LMWG) meetings and present project updates for the current contract year. These meetings are scheduled for one day each in late March and early October and will be held in Boulder City, NV. The LMWG meetings 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 PERFORMANCE

4.1 PLACE OF PERFORMANCE

Lake Mead, AZ–NV

4.2 PERIOD OF PERFORMANCE

Base Year shall be January 1, 2025, through December 31, 2025.

Option Year 1 shall be January 1, 2026, through December 31, 2026.

Option Year 2 shall be January 1, 2027, through December 31, 2027.

Option Year 3 shall be January 1, 2028, through December 31, 2028.

Option Year 4 shall be January 1, 2029, through December 31, 2029.

4.3 LOGISTICS

The contractor shall provide all personnel, vehicles, motorboats, equipment, supplies, materials, tools, facilities, supervision, and non-personal services necessary for completing project tasks and achieving stated objectives 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.

4.4 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.5 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 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 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 include the following:

A) Scientific collecting permits for Lake Mead National Recreation Area B) U.S. Fish and Wildlife Service Endangered Species Permit to cover take of

Endangered Species Act covered species in the study area C) Scientific Collection Permit from Arizona Game and Fish Department D) Scientific Collection Permit from Nevada Department 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 PERFORMANCE REQUIREMENTS SUMMARY (PRS)

The PRS table identifies the required services/tasks, the performance standards, and the acceptable quality level (table 1). 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.—Tasks, Standards, and Acceptable Quality Level

Task No. Task Description Performance

Indicator Performance

Standard Minimum Acceptable

Quality Level

3.1

Intensive Monitoring of the Lake Mead Razorback Sucker

Population

Perform services in accordance with

Contractor’s schedule & 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

Additional Monitoring of Adult Razorback Sucker Movement

Patterns

Perform services in accordance with

Contractor’s schedule & 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.3 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

PWS. 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 both CRAB and LMWG meetings

Contractor will prepare and present findings at annual meetings.

95% attendance at meetings

8 TABLE OF CONTRACTOR SUBMITTALS

Table 2.—Submittals

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 ten (10) days of notice of award.

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

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

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

Monthly Data

Collection Report Section 6.0, paragraph 6.1

COR 0 1

Submit with monthly invoice.

005 Draft Interim Report Section 6.0, paragraph 6.3

COR 0 1

Due on or before November 1st of each year.

006 Final Interim Report Section 6.0, paragraph 6.4

COR 0 1

Due on or before December 31st of each year.

007 Draft Project Report Section 6.0, paragraph 6.5

COR 0 1

Due on or before November 1st of the last executed option year.

008 Final Project Report Section 6.0, paragraph 6.5

COR 0 1

Due on or before December 31st of the last executed option year.

009 Data Sets Section 6.0, paragraph 6.7;

Appendix 1

COR 0 1

March 31st, June 30th, September 30th, December 31st

*CO = Contracting Officer; COR = Contract Officer’s Representative

9 DELIVERABLES

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

OF CONTRACTOR SUBMITTALS”:

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

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

9.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 31st of December 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.

9.4 DRAFT PORJECT 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.

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

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

10 REFERENCES

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.

Appendix 1

A-1

LCR MSCP Data Management Requirements

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: https://www.doi.gov/elips/browse, available upon request, not currently available online).

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 collection processes and data obtained by those individuals or groups representing LCR MSCP, who obtain, create, maintain, and/or have significant control over data. If the Contractor is interested in asserting copyright for data collected under this contract, this should be discussed with the Contracting Officer’s Representative (COR) prior to commencement of data collection. The prior, express written permission of the Contracting Officer is required to assert copyright for all data first produced in the performance of this contract (See FAR 52.227-14, https://www.acquisition.gov/far/52.227-14). A contractor’s employee shall be appointed as data steward(s) prior to project kickoff meeting by the contractor. The data steward shall coordinate closely with the COR and LCR MSCP Adaptive Management Group (AMG) on all data related issues. The 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, a list of all applications used to collect and store data shall be provided to the COR and the AMG. Reclamation shall review and approve all applications, protocols and procedures before any data is collected. Although Reclamation may develop the mobile electronic field forms (MEFF) 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 or data recovery costs due to Contractor error or failure is at Contractor’s expense. Prior approval by the AMG is required if the Contractor prefers to develop the MEFFs and the AMG will need to approve the MEFFs prior to data collection.

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” through providing all field instructions, field methods, protocols, all raw data collected, A-2 step-by-step QA/QC processes, data change logs, and analysis including input and output files/codes and process descriptions.

Field Data Collection - LCR MSCP requires that contractors collect data with mobile electronic field forms (MEFFs) whenever possible using ArcGIS Field Maps, Collector for ArcGIS, or Survey123 for ArcGIS (https://www.esri.com/en-us/arcgis/products/apps-for-everyone/overview). Since field data collection will be completed using Esri apps, the contractor will be required to have an ArcGIS Online subscription and provide ArcGIS Online (AGOL) organizational accounts to all employees involved in data collection and editing (field surveyors, field supervisors, GIS specialists, data stewards). Shared accounts shall not be used. Data collected using these apps shall be delivered to Reclamation by allowing Reclamation to consume the data through inter-organizational sharing (data will be collected in feature services hosted in the contractor’s organizational AGOL account and shared with a group that Reclamation personnel are members of).

For data collected in methods outside of 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.

Each data package will have a list of the files contained in the data package.

Metadata - All data and applications used by Reclamation in fulfilling its mission shall be properly documented with metadata. Tabular (non-spatial) and spatial data shall be accompanied by ISO 19115-1:2014 compliant metadata (https://www.fgdc.gov/metadata/geospatial-metadata-standards) using the North American Profile (NAP) of ISO 19115 in XML format adhering to the ISO 19139 standard schema.

Digital media (photographs, videos, PDF files) shall be accompanied by ISO 16684-1:2019 (XMP) compliant metadata (https://www.iso.org/standard/75163.html). LCR MSCP will provide metadata templates and guidance on metadata expectations for both ISO 19115- 1:2014 and ISO 16684-1:2012 metadata. LCR MSCP metadata templates may include additional elements not explicitly included in the standards. These additional elements will be extended in compliance with the ISO standard.

Spatial data created using Esri products shall be accompanied by metadata in the ArcGIS metadata format and must contain all required elements specified by either the ISO 19115- 1:2014 standard or LCR MSCP.

Naming Convention - A site and field data naming convention has been established by LCR MSCP for all data collection, including electronic document names, MEFF file names, Excel columns, shapefiles, geodatabases, row and table names, and database field names. This LCR MSCP naming convention will be used for all file naming, data entry, analysis, and reports during the contract period. If this project is a continuing project for LCR MSCP, the Contractor shall collaborate with Reclamation in developing a cross-reference document that connects previous project site names with LCR MSCP standardized location names prior to any data collection. The LCR MSCP shall provide the contractor with the standardized

A-3 naming convention to be used for all file naming, data entry, analysis and reports during the contract period.

Paper Documents - All paper documents used to collect data (e.g., data sheets, field notes) on behalf of Reclamation shall be scanned to Adobe PDF format using OCR text recognition.

Prior to scanning, each page shall be assigned a unique page number (to be written in document margin or header/footer) for each document group saved to an individual PDF file.

After scanning, PDFs shall be inspected for legibility before delivery to LCR MSCP. PDFs shall be organized within established folder architecture and cataloged 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 Adaptive Management Group. All fields on data sheets will be filled out. NO blank entries are allowed.

Tabular Data - Tabular data shall be stored in electronic format. All tabular data shall be accompanied with metadata including descriptions 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 (database schema) must also be provided. All fields in the tabular data will be filled out. NO blank entries are allowed; NULL values are allowed.

Spatial Data - All GIS data and products shall be acquired, created, and delivered in one of the two following spatial reference systems:

UTM Zone 11 North (Latitude Band S), NAD83 (Conus) horizontal datum, in meters, http://spatialreference.org/ref/epsg/nad83-utm-zone-11n/, (EPSG:26911), or

WGS84, in degrees, http://spatialreference.org/ref/epsg/4326/ (EPSG:4326).

Point data with x, y, and z coordinates shall be acquired, created, and delivered in one of the above spatial reference systems and the North American Vertical Datum of 1988 (http://spatialreference.org/ref/epsg/5703/, EPSG:5703) for the z coordinate.

All spatial data shall be stored electronically in a standard spatial data file format (e,g.

Esri file geodatabase). No shapefiles will be accepted. If data is proposed to be collected using different reference systems than those above, contractor shall coordinate with Reclamation on what coordinate system and datum shall be used prior to any collection.

All spatial data attributes shall be fully documented in accordance with the ISO 19115- 1:2014 metadata. All geoprocessing history shall be included in the metadata.

Raw data and post-processed spatial data products shall be delivered via inter-organizational sharing in AGOL as described in the Field Data Collection section above. All fields in the spatial data will be filled out. NO blank entries are allowed; NULL values are allowed.

GNSS receivers - The GNSS receiver type, brand, and model must be included in the metadata. Contractor shall work with LCR MSCP Adaptive Management Group for specification and recommendations of compatible/supported GNSS devices prior to field collection. Examples of recommended GNSS receivers are:

A-4

Trimble TDC100 Bad Elf GNSS Surveyor paired with data collection device Data collection devices equipped with integrated ublox NEO-M8 series of GNSS receiver (or similar)

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, data field limiters or validation scripts, and 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 at the end of each field season to maintain a high standard of quality and to document lessons learned. 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 AMG. If changes are made to these data, collection procedures, or analysis, the MEFFs and accompanying documentation shall be updated at a minimum on an annual basis.

Statistical Analyses - All data, outputs, and other items (as detailed below) regarding data summaries or statistical analyses performed by the Contractor shall be delivered to the LCR MSCP. This includes a complete citation for statistical program(s) (including version number and the required operating system) and a thorough description of statistical procedures in sufficient detail to reconstruct the analysis. This includes procedures used to modify raw data for analysis (e.g., transformation or standardization, creating derived variables, and categorizing continuous data). This includes all input and output from statistical analyses along with metadata that associates each input/output file to a statistical procedure and result in the project report. This should be an Excel spreadsheet that contains the inputs/outputs for each analysis and a table of contents if inputs/outputs are compiled into one or more workbooks. Input data will be in the format used for analysis. If code is used (e.g., R or SAS, etc.), a copy of the input code shall also be delivered. If a menu based program is used, documentation of commands used shall be delivered. If ecological modeling software is used (e.g., Program MARK or PRESENCE), provide all files that contain input data and model results that can be accessed from the software. This includes INP, DBF, and FPT files for Program MARK and PAO and PA2 files for Program PRESENCE.

Reports - Annual and final reports shall be submitted in Microsoft Word and will be prepared using the supplied LCR MSCP report template. Report content shall follow the supplied LCR MSCP ‘Writer’s Guidelines’. The Contractor shall ensure that all content (e.g., A-5 text, figures, and tables) in the Microsoft Word version of the report meets Section 508 requirements under the U.S. Rehabilitation Act (https://www.section508.gov/create/).

Reclamation will provide information as needed to the Technical Editor (or other responsible staff member) of the Contractor in making final formatting changes to the document and meeting accessibility requirements.

Publications, presentations, release of data - Contractors shall notify the COR of any planned presentations, publications, or release of data collected under this contract 30 days prior to dissemination. This shall be coordinated and approved by the LCR MSCP Adaptive Management Group. See FAR 52.227-14 (d) (2) (See https://www.acquisition.gov/far/52.227-14).

Backup - The Contractor shall provide a detailed description of their backup process to the COR and LCR MSCP Data Management Group. If no backup procedures are established, one shall be created that meets LCR MSCP standards.

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.

Delivery - 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 as data packages (compressed archive file in ZIP format) via LCR MSCP External SharePoint (or other approved delivery method such as AGOL for spatial data delivery). All files shall be cataloged in an Excel Spreadsheet. A metadata file shall accompany all data and applications transferred to Reclamation (see Metadata above).

For spatial data, Esri geodatabase formats shall be accepted, and each file must be accompanied by projection and metadata files. For raster datasets, Esri GRID, ERDAS IMAGINE, and TIFF formats shall be accepted, and each file shall be accompanied by projection and metadata files. Spatial data (raw and post-processed data products) should be delivered via ArcGIS Online.

For tabular data, Microsoft Access, Microsoft Excel, or delimited text file formats shall be accepted and each file shall be accompanied by a metadata file. Metadata files shall accompany all spatial data and database files and conform to the requirements described above.

If Reclamation authorizes delivery via CD/DVD or portable hard drive, a readme file defining contents of each directory/subdirectory shall be provided. If authorization has been given to deliver data packages via alternate delivery method, send to:

US Mail

A-6

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

LC-XXXX

Boulder City, NV 89006

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

Data Management Plan: How the contractor plans to implement and manage the above requirements shall be included in a data management plan prepared by the contractor. Prior to commencement of data collection, the Contractor shall deliver a data management plan to Reclamation which includes, but is not limited to, the following components:

1. Description of data management lifecycle for data collected under this contract

a. Raw field data collection procedures

b. Quality assurance/quality control procedures

c. Data post-processing procedures

d. Analytical procedures

e. Data delivery procedures

f. Review and update procedures

2. Backup and security procedures to be followed at all steps of the data management lifecycle

3. List of applications and devices to be used during the life of the contract

a. Data collection devices including GNSS receiver specifications

b. Software to be used for collection, storage, backup, processing, analysis, delivery