Attachment_01_-_Performance_Work_Statement_Rev_02_0002.pdf

Performance Work Statement Southwestern Willow Flycatcher Monitoring

1. PURPOSE, OBJECTIVES AND AUTHORITY

1.1 PURPOSE

The purpose of this study is to monitor southwestern willow flycatcher in LCR MSCP conservation areas and suitable riparian habitats along the LCR. Historically, a substantial number of southwestern willow flycatchers may have existed in areas along the LCR (Unitt 1987). One of the major factors for the decline of southwestern willow flycatchers along the LCR has been habitat changes within riparian systems.

1.2 OBJECTIVES

1. The first objective of the study is to document the presence/absence, and breeding status of southwestern willow flycatcher at LCR MSCP conservation areas.

2. The second objective is to determine presence/absence and locate breeding territories at certain areas of the LCR near to, or that could provide a source population for, LCR MSCP conservation areas.

3. The third objective is to track the known breeding populations on the LCR to document areas that are used by southwestern willow flycatcher.

In obtaining data relative to the continued existence of the southwestern willow flycatcher, Reclamation is furthering its mission by protecting wildlife resources in an environmentally and economically sound manner in the interest of the American public.

1.3 Authority

This contract is entered into pursuant to the Endangered Species Act of 1973 as amended and supplemented; the Fish and Wildlife Coordination Act of 1934 as amended.

2. BACKGROUND

The southwestern willow flycatcher (Empidonax traillii extimus) is one of five subspecies of willow flycatcher recognized in North America. The breeding ranges of the five subspecies are not well known because of lack of breeding specimens, both in the East, where the species is apparently expanding its range, and in the West, where ranges had been assumed to be contracting (Browning, 1993). Subspecies designation is based on genetic analysis and subtle differences in color and morphology. The breeding range of southwestern willow flycatcher includes Arizona, southern California, New Mexico, southern Nevada, southern Utah, southwestern Colorado, western Texas and extreme northwestern Mexico.

Migration patterns are largely unknown though southwestern willow flycatcher are thought to winter in Mexico, Central America, and northern South America.

The factors contributing to the decline of southwestern willow flycatcher populations are loss and fragmentation of riparian habitat, invasion of exotic plant species, predation and parasitism, and loss of wintering habitat. The southwestern willow flycatcher is a riparian obligate bird restricted to dense riparian vegetation. The U.S. Fish and Wildlife Service (USFWS) listed southwestern willow flycatcher as an endangered species in March 1995 [Federal Register 60 (38): 10694]. The southwestern willow flycatcher is classified as state endangered with the Arizona Game and Fish Department and California Department of Fish and Wildlife.

The U.S. Bureau of Reclamation (Reclamation) has been conducting surveys for the presence of southwestern willow flycatcher along the lower Colorado River (LCR) since 1996, in compliance with requirements set forth by the USFWS regarding Reclamation’s routine operation and maintenance along the lower Colorado River. The Lower Colorado River Multi-Species Conservation Plan (LCR MSCP), signed in April 2005, was developed for long-term endangered species compliance in association with management of LCR water resources. The LCR MSCP’s conservation measures calls for continued southwestern willow flycatcher surveys and research to better identify and evaluate this species and its habitat.

3. REQUIREMENTS

Overview:

Biological monitoring services are required to survey for and collect demographic data on the endangered southwestern willow flycatcher. There are five tasks that are associated with this solicitation. Task 1, presence/absence surveys and territory monitoring at conservation areas, shall be performed each year of the contract. Other tasks may be performed periodically during the contract. In some cases the implementation of certain task for a contract year may be decided based on the results from the previous contract year. Reclamation shall direct the contractor which tasks are to be implemented prior to each contract year. The contractor shall provide for all the logistical needs for a crew size sufficient to conduct the work for all tasks that are implemented for each contract year. This will include any transportation and lodging that may be needed for the crew to perform their tasks. Due to the safety and logistical concerns of working in an extremely hot desert environment, the crew shall not camp as a means of principle lodging through the summer field season.

3.1 Task 1 - Presence/Absence Surveys and Territory Monitoring of LCR MSCP Conservation Areas

Southwestern willow flycatcher surveys shall be conducted each year of the contract using a protocol of 5 survey days per site with at least one survey between May 15 and June 1, two surveys between June 1 and June 24, and two surveys between June 24 and July 17. Surveys of each site shall be at least 5 days apart.

The surveys shall be conducted using as a minimum the United States Geological Survey (USGS) developed survey protocol (Sogge et al. 2010). Surveys shall be conducted from one hour before dawn to 10:00 am (weather permitting). Surveys shall be conducted playing recorded vocalizations to induce a response from any birds that may be present unless birds are already vocalizing when surveyors arrive at a site. Vocalization recordings shall be used that include more than one southwestern willow flycatcher vocalization. Surveys shall be conducted slowly within and throughout the habitat to increase probability of detection. Surveyors shall be thoroughly trained to recognize all calls of the southwestern willow flycatcher especially the fitz-bew and whit calls. Sightings shall be recorded and special notation shall be made of any birds sighted with bands. Please refer to the requirements for how data is to be collected in section 3.11.4 below.

At any survey site on a LCR MSCP Conservation Area where a southwestern willow flycatcher is detected, surveyors shall determine if the birds encountered are resident and territorial. This shall be done by confirming that a bird meets the criteria to be considered a resident bird, as outlined in the official protocol. If several resident birds are present, the contractor shall determine how many territories of pairs, or single individuals, are present at the site. Territory locations shall be derived from Global Positioning System (GPS) devices (see GPS hardware requirements) or estimated based on locations of territorial southwestern willow flycatchers. Territory locations may be estimated if it is not immediately apparent whether birds are migrants or resident pairs. If a nest is found during efforts to determine a territory this shall be noted, and the location documented. For Task 1 the contractor is not expected to conduct specific nest searches.

Deliverables: The contractor shall record all detections and territories on imagery of the site. Territories shall be plotted as polygons, or as points of territory center when data is insufficient to plot polygons, using Geographic Information System format (GIS). The contractor shall demonstrate how individual detections were used to determine and delineate territories or territory centers. All survey site boundaries, regardless of occupation, shall also be recorded as polygons using GPS devices and stored in GIS. All detections shall be recorded as point features in GIS. The data shall be collected electronically using the LCR MSCP Mobile Electronic Field Forms (MEFF) (see data management sections below).

Assumptions regarding level of effort: Table 1 represents the amount that will be surveyed each year and should be used to estimate the level of effort. The exact survey locations will be determined for each year in consultation with Reclamation’s Contracting Officer (CO) and Contracting Officer’s Representative (COR). Reclamation’s CO and COR will confirm site locations with the contractor by April 15 for each year of the study, approximately one month before surveys are to be conducted. Not all cottonwood-willow types I-IV will be surveyed at all conservation areas (please refer to LCR MSCP Final Habitat Conservation Plan for definitions of land cover typeshttps://www.lcrmscp.gov/publications/hcp_volii_2004.pdf). Beal Lake Conservation Area, Laguna Division Conservation Area, and Planet Ranch will be surveyed every contract year. A new conservation area, the Dennis Underwood Conservation Area, started planting in 2021 and will be surveyed over two years starting in 2024. Approximately half of the acreage will be surveyed each year. The rest of the conservation areas will be surveyed over the entire three-year period with approximately a third of the sites to be surveyed in each contract year. If the amount of sites that is needed to be surveyed is less than those listed in a contract year, Reclamation can direct the contractor to conduct other field activities, such as reconnaissance work for other potential areas of suitable southwestern willow flycatcher habitat, that represents an equal amount of time and effort and is within the scope of the contract. The amount of acreage to be surveyed has been estimated for sites that have been recently planted, or that will be planted during the life of the contract. Sites may be added or subtracted from the list through the 3 years of the contract based on annual direction given to the contractor from Reclamation’s CO and COR. Although sites may be added or subtracted, the total effort to survey will not change. New sites that are located separately from existing survey sites and that would require additional effort due to increased travel or logistics shall not be added.

https://www.lcrmscp.gov/publications/hcp_volii_2004.pdf

Table 1 Survey Sites for Task 1

LCR MSCP Area, LCR MSCP

Site

LCR MSCP

Section

Area (Acres)

Survey Frequency

Beal Lake Conservation Area Cphase 05 Cphase 05 32 Every year

Palo Verde Ecological Reserve

Phase 2 Phase 2 78 Once per 3 years

Phase 3 Phase 3 84 Once per 3 years

Phase 4 Phase 4 - Blocks 1,2,3 100

Once per 3 years

Phase 5 Phase 5 - Blocks 1,2,3 216

Once per 3 years

Phase 6 Phase 6 - Blocks 1,2 220

Once per 3 years

Phase 7 Phase 7 - Blocks 1,2 226

Once per 3 years

Cibola Valley Conservation Area

Phase 1 Phase 1 91 Once per 3 years

Phase 2 Phase 2 71 Once per 3 years

Phase 3 Phase 3 103 Once per 3 years

Phase 8 Phase 8 66 Once per 3 years

Phase 9 Phase 9 51 Once per 3 years

Cibola National Wildlife Refuge Unit #1

Nature Trail Nature Trail 34 Once per 3 years Upper Hippy Fire 70

Once per 3 years

Middle Hippy Fire 75

Once per 3 years

Lower Hippy Fire 60

Once per 3 years

Crane's Roost C2729 15 Once per 3 years

Dennis Underwood Conservation Area

Section 1 47 2024-20225

Section 2 88 2024-2025

Yuma East Wetlands J C4703 21 Once per 3 years

South AC C4711 2.25 Once per 3 years

I C4702 16 Once per 3 years

Laguna Conservation Area 250 Every year

Planet Ranch 80 Every year

3.2 Task 2 – Presence/Absence Surveys and Territory Monitoring of Alamo Lake, AZ

Alamo Lake, AZ is located below the confluence of the Big Sandy and Santa Maria Rivers and is the source of water flows into the Bill Williams River. A large population of breeding southwestern willow flycatcher has been monitored by Reclamation contractors since 2014 on the northeast end of the lake.

Presence/absence surveys and territory monitoring shall be conducted at approximately, but no more than, 23 sites. These surveys shall be conducted in the same manner as described in Task 1. A list of the sites to be surveyed can be found in Table 2 and a map of these sites can be found in Attachment 1. If nests are located while determining territory locations, this shall be noted, but no extra effort will be made to locate nests or determine nest contents or nest fate.

Areas on the map are just approximations as site conditions may change over time. Reclamation’s CO and COR will confirm site locations with the contractor by April 15 for each year Task 2 is implemented, approximately one month before surveys are to be conducted. Although the overall survey effort will not be increased, sites may be added or subtracted from the list through the 3 years of the contract. A list of the sites to be surveyed can be found in Table 4 and a map of the sites can be found in Appendix 1.

Background: In 2019, 86 pairs were detected and in 2021, 38 pairs were detected. Surveys could not be completed in 2020. The number of pairs seen in 2019 occurred under ideal flooded conditions and some of the trees in these areas that had supported breeding populations have since died and habitat quality has been reduced.

Assumptions regarding level of effort: For purposes of this contract, the contractor shall assume an effort that would require monitoring of no more than fifty pairs of birds. If more than fifty pairs of birds are encountered, the contractor will notify Reclamation’s CO and COR. The CO and COR will select the survey sites to be surveyed for the remainder of the survey period to avoid additional effort. For purposes of determining effort the contractor shall assume that the sites listed in Table 4 represent the total number of sites to be surveyed and the effort required. Sites will only be added if an equal amount of sites are removed. New sites that are located separately from existing survey sites and that would require additional effort due to increased travel or logistics shall not be added.

Table 2 Survey Sites for Task 2

LCR MSCP Area LCR MSCP Site LCR MSCP Section Area (Acres)

Alamo Lake

Lake Bullard Wash 4.7 South Camp 5.9 Over the Edge 5.2

Brown's Crossing

Sidebar 01 2.7 Edgewater 01 2.2 Camp 01 1.8 Camp 04 0.5 Camp 02 0.75 Camp 03 3.2 Middle Earth 01 5.4 Middle Earth 02 12.3 Prospect 01 2.7 Burro Wash 01 10.1 Burro Wash 02 19.5 Motherlode 02 10.6 Motherlode 03 20.5 Motherlode 04 1.25 Confluence 02 24.2 Santa Maria South 01 63.25 Santa Maria North 01 68.4

3.3 Task 3 – Presence/Absence Surveys and Territory Monitoring of Topock Marsh, AZ.

Presence/absence surveys and territory monitoring shall be conducted at sites located in Topock Marsh on the Havasu National Wildlife Refuge. These surveys shall be conducted in the same manner as described in Task 1. A list of the sites to be surveyed can be found in Table 3 and a map of these sites can be found in Attachment 1. As site conditions may change over time, areas on the map are just approximations.

Reclamation’s CO and COR will confirm site locations with the contractor by April 15 for each year Task 3 is implemented, approximately one month before surveys are to be conducted. Although the overall survey effort will not be substantially increased, sites may be added or subtracted from the list for each year through the 5 years of the contract based on direction from Reclamation’s CO and COR.

Background: In 2020, 6 pairs of southwestern willow flycatcher were confirmed in the Topock Marsh area. In 2021, 3 pairs of southwestern willow flycatcher were confirmed at Topock Marsh. In 2015, a large fire burned approximately half the southwestern willow flycatcher habitat found in the Topock Marsh area. Most of the burned areas will not be surveyed.

Assumptions regarding level of effort: For purposes of this contract, the contractor shall assume an effort that would require monitoring of no more than ten pairs of birds. If more than ten pairs of birds are encountered, this will be discussed with Reclamation’s CO and COR and work will be adjusted to avoid further effort (such as only collecting nest monitoring data on a subset of the total number of pairs or discontinuing surveys at sites which have not shown any previous signs of resident or breeding flycatchers). For purposes of determining effort, the contractor shall assume that the sites listed in Table 3 represent the total maximum acreage to be surveyed and the effort required. Sites will only be added if an equal amount of sites are removed. New sites that are located separately from existing survey sites and that would require additional effort due to increased travel or logistics shall not be added.

Table 3 Survey Sites for Task 3

LCR MSCP Area, LCR MSCP Site LCR MSCP Section Area (Acre)

Topock, Arizona Topock Marsh

Swine Paradise 2.2 Platform 4.7 Hell Bird 14.3 Glory Hole 15.8 Farm Ditch Road 10.9 The Wallows 1.7

PC 6-1 11.9

800M 11.6

Topock Bay Lost Lake 8.2

3.4 Task 4 – Presence/Absence Surveys and Territory Monitoring of the Bill Williams River National Wildlife Refuge, AZ.

Presence/absence surveys and territory monitoring shall be conducted at sites located on the Bill Williams River National Wildlife Refuge. These surveys shall be conducted in the same manner as described in Task 1. A list of the sites to be surveyed can be found in Table 4 and a map of these sites can be found in Attachment 1. As site conditions may change over time, areas on the map are just approximations.

Reclamation’s CO and COR will confirm site locations with the contractor by April 15 for each year Task 4 is implemented, approximately one month before surveys are to be conducted. Although the overall survey effort will not be substantially increased, sites may be added or subtracted from the list for each year through the 5 years of the contract based on direction from Reclamation’s CO and COR.

Background: In 2020, 1 pair of southwestern willow flycatchers was confirmed on the Bill Williams River. In 2021, 1 pair of southwestern willow flycatchers was confirmed on the Bill Williams River. In

2021 a fire burned large portions of the Bill Williams River. None of the areas that were burned will be surveyed for this contract.

Assumptions regarding level of effort: For purposes of this contract, the contractor shall assume an effort that would require monitoring of no more than five pairs of birds. If more than ten pairs of birds are encountered, this will be discussed with Reclamation’s CO and COR and work will be adjusted to avoid further effort (such as only collecting nest monitoring data on a subset of the total number of pairs or discontinuing surveys at sites which have not shown any previous signs of resident or breeding flycatchers). For purposes of determining effort, the contractor shall assume that the sites listed in Table 4 represent the total maximum acreage to be surveyed and the effort required. Sites will only be added if an equal amount of sites are removed. New sites that are located separately from existing survey sites and that would require additional effort due to increased travel or logistics shall not be added.

Table 4 Survey Sites for Task 4.

LCR MSCP Area LCR MSCP Site LCR MSCP Section Area (Acres)

Bill Williams River East

Esquerra Ranch Beaver Pond North 47 Beaver Pond 53.1

Honeycomb Bend Downstream Site 0 2.97 Site 08 29.9

Cave Wash Upstream From Site 08 3.7

3.5 Task 5 Capture and Place Nano-Tags on Southwestern Willow Flycatchers.

Reclamation will place MOTUS towers at LCR MSCP conservation areas. These towers will be able to detect both Lotek and CCT nano-tags. The contractor shall capture, leg band, and place nano-tags on known breeding southwestern willow flycatchers. The locations where attempts will be made to capture and tag birds, depending on available habitat each year, shall be Topock Marsh, Bill Williams River National Wildlife Refuge, and Alamo Lake State Park. Only birds that are known to be southwestern willow flycatchers, per the criteria from the official survey protocol, shall be captured or tagged. The contractor shall mark (band) territorial southwestern willow flycatchers with a USFWS leg band and a unique combination of color leg bands so individual birds can be positively identified. The contractor shall use aluminum bands and will not use plastic bands. General banding information shall be collected for each bird and recorded on a banding MEFF. This information shall include age, sex, how aged, how sexed, indications of breeding status, location of capture, the colors of the band combination, initials of the bander, wing chord measurement, weight, and any notes that are pertinent to the capture or banding of the bird. The contractor shall follow standard banding protocols in order to ensure bird safety and minimize disturbance to the birds (Ralph et al. 1993, Sogge et al. 2011).

The contractor shall conduct the operations of task 5 in conjunction with the efforts of Tasks 2,3 and 4 using the information gained from surveys conducted for Tasks 2, 3 and 4 to locate birds to be captured and tagged. For purposes of this contract the contractor shall assume an effort that requires capturing no more than 40 birds.

The contractor shall explain how they will ensure the safety of the birds while capturing, handling, and applying nano-tags. The contractor shall also describe how they will minimize the impact of the tag on the birds after they have been released. The contractor shall explain which method they will use to attach the nano-tags to the birds and why that method is the best for the safety of the birds and the tracking of their movements and locations.

3.6 Meetings

Four meetings will be held annually. Three meetings will be held in person, if federal policy and safety provisions permit to do so, and one will be held via conference call. If in person meetings cannot be held all meetings will be held virtually. Key personnel to the project, such as project coordinator and field supervisors, shall attend these meetings:

1. One meeting per year will be held at the annual CRTR meeting in January in Laughlin, NV where the findings from the year will be presented.

2. One meeting per year will be held in Boulder City before the field season starts to discuss survey locations and field logistics.

3. One meeting per year will be held via conference call after the data collection from the field season is complete to discuss the data analysis.

4. One meeting per year will be held at the contractor’s location after the data analysis is complete to discuss the annual report before delivery of the first draft

In addition, there will be a kickoff meeting that will be held shortly after the contract award takes place.

The meeting will be held at Reclamation’s office in Boulder City, NV. The meeting will be used to discuss the strategy for the initial implementation and timeline of the contract.

3.7 Data Ownership and Maps

Ownership: All data collected by the contractor shall be the property of Reclamation. If incidental data is documented on species other than the southwestern willow flycatcher while conducting southwestern willow flycatcher related work, this data will also be the property of Reclamation. All information collected on these other species shall be included as appendices to the final report. All publications and presentations related to this contract shall be submitted to Reclamation for review prior to publication. All forms used to record data shall be approved by Reclamation.

3.8 Permitting

The Contractor shall pay for (if applicable) and obtain all regulatory handling and research permits necessary to conduct presence/absence surveys, nest monitoring, and tagging and banding from the US Fish and Wildlife Service (USFWS) and each state’s wildlife management agency. The contractor shall also pay for (if applicable) and obtain all rights-of-way permits, special use permits, and/or land use authorizations for surveys on public, tribal and private lands. The contractor shall contact Reclamation’s CO and COR if permits and authorizations cannot be obtained in order to switch to sites where the permits can be obtained. All permits shall be acquired and approved for field work a month before field activities begin. The contractor needs to account for the permit processing time for each agency. If permits cannot be issued in time, the contractor shall contact Reclamation’s CO and COR and discuss what options are available and if adjustments in the schedule of field activities will be necessary. Permits shall be in place prior to surveys being conducted.

3.9 Reporting Requirements/Deliverables

3.10.1 Permits

1. All permits obtained from necessary landowners, USFWS, State wildlife agencies, Tribes, and others shall be delivered to Reclamation prior to any field work each year and shall be in place a minimum of 1 month before surveys are conducted.

2. The Contractor shall provide Reclamation with a copy of all documents provided to landowners, USFWS, State wildlife agencies, Tribes, and others that are required to comply with these permits and authorizations.

3.9.2 Monthly Reports

The contractor shall submit monthly reports of all field activities to Reclamation (April to September for each contract year). Monthly reports shall be submitted to the LCR MSCP SharePoint site. The reports shall include the following:

• Agency/Organization

• Contract Number

• Project Name

• Reporting Period

• Contact Name and Information

• Accomplishments during the reporting period, a brief description of field activities and a brief description of bird sightings. Explain how these accomplishments assisted the contractor in reaching the goal of the project. Indicators or benchmarks that were used to determine the contractor’s progress.

• Description of problems that were encountered and how the contractor dealt with the problems (e.g. fire in one of the sites, trespass issues, cows on site, disturbance, etc.).

• List of proposed activities that were not completed. Describe these activities, the reasons they were not completed and plans for carrying these activities out.

• Calculated percent of work completed.

• Foreseeable upcoming problems with future project activities. If there are any, explain how problems are to be overcome.

• Deliverables produced or milestones reached during the reporting period.

3.9.3 Raw Data Final Data and GPS/GIS Data

1. All initial raw data, including copies of all survey, banding, and nest monitoring forms, scanned copies of any physical data sheets (if applicable), and raw electronic data shall be delivered to Reclamation by September 15 of each year via LCR MSCP SharePoint site or ARC GIS Online unless other arrangements are agreed upon by Reclamation’s CO and COR.

2. All corrected (QA/QC) data by November 15 of each year.

3. All summarized electronic data, post processed electronic data, raw data that has been fully quality checked from the first delivery, statistical analysis data, GPS points and GIS files of survey areas and nest locations, and GIS maps and any other pertinent data shall be delivered to Reclamation’s CO and COR by January 31 of each year.

3.9.4 Data Management

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, 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 featured 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 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:

• 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., 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/content/build/create-accessible-documents). 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 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

Lower Colorado River Multi-Species Conservation Program

PO Box 61470

LC-8115

Boulder City, NV 89006

Physical Address (UPS/FedEx)

Lower Colorado River Multi-Species Conservation Program 500 Fir Street

LC-8115

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

The contractor shall provide to Reclamation a Data Management plan after contract award and no later than a month before field work begins in the first year of the contract. If changes or updates are made to this plan in subsequent years, these shall also be submitted to Reclamation no later than a week before field work begins.

3.9.5 Draft and Final Annual Reports

All reports shall be prepared using the LCR MSCP report template and LCR MSCP writer’s guidelines.

Reclamation will provide templates for these documents 30 days after award of the contract. The contractor shall submit in Microsoft Word format, a draft Annual Report for the year’s surveys to Reclamation by December 1st in 2023, 2024, and 2025. Reclamation shall provide comments on the initial draft to the contractor by January 2ndt in 2023, 2024, and 2025. After review by Reclamation and receiving comments addressing the need for corrections, revisions and/or additions, the contractor shall submit a revised draft to Reclamation that addresses Reclamation’s comments by January 31st of 2024, 2025, and 2026 (60 days from the first draft due date). Reclamation shall provide technical editing comments for the revised draft by Feb 28 in 2024, 2025, and 2026. If any of the due dates fall on a weekend or holiday, the due date shall be the next working day after the original due date.The contractor shall submit an electronic copy of the Final Annual Report, which incorporates all revisions, corrections, and/or additions agreed upon by Reclamation and the contractor by March 31st of 2023, 2024, and 2025.

All reports shall be prepared using the LCR MSCP report template and LCR MSCP writer’s guidelines.

Reclamation will provide templates for these documents 30 days after award of the contract. The report shall include a summary of the field season data, including presence/absence surveys, nesting data, and banding data along with any findings or significant outcomes. The report shall also include incidental sightings of other bird species. Specific sections that shall include, if applicable, but are not limited to:

1) A description of the study area;

2) Methods used in site selection, , southwestern willow flycatcher survey techniques and banding techniques;

3) Results of surveys, banding, and tracking for each specific site surveyed including a detailed description of the survey site;

4) Discussion of observations during the study,

5) Analysis of data for surveys, and banding including, but not restricted to, nanotag performance, habitat affinities, and dispersal

6) Tables and figures to represent the data along with summaries of surveys, banding, and tracking.

7) Maps in GIS format of sites surveyed.

The final annual report shall be submitted in Microsoft Word.

While the Contractor is not responsible for converting the Word version of reports into PDF 508 compliant documents, using the Report Template and Writer Guidelines created for these reports will incorporate all the styles to meet Reclamation’s Visual Identity standards and help ensure Reclamation’s technical editor can successfully convert the document. The MS Word documents submitted should allow for conversion to a PDF that passes the 508 accessibility test within the latest version of Acrobat Pro. For example, data presented in tables and figures shall also be described in the narrative. Table and figure headings shall have enough detail that their meaning and how they relate to the text is clear when read by a document reader to someone visually impaired. Elaborate formatting such as beveling, shadowing, or 3D effects should be avoided. Adobe Acrobat considers each shadow and beveling effect an image on its own. For instance, a small 1" by 1" square beveled and shadowed image can cause the program to believe there are close to a hundred images within that small item. This makes it very difficult to make the image 508 compliant.

Additional information on 508 compliance can be obtained at https://www.section508.gov/content/learn/standards/quick-reference-guide. Reclamation will ensure the report is fully 508 compliant prior to posting on the LCR MSCP website.

3.9.6 Quality Assurance/Quality Control Plan

The contractor shall provide to Reclamation a QA/QC Plan after contract award and no later than a month before field work begins in the first year of the contract. Any changes or updates to these procedures made in subsequent years shall be submitted to Reclamation in an updated QA/QC Plan no later than a week before field work begins.

Quality Assurance (QA) is defined in section 3.10.4 of this document.

3.9.7 Draft and Final Summary Reports

A draft summary report shall be completed (Year 3) only if each of the potential years of contract performance is granted (a total of 3 years). A final summary report is not required to be completed if the total years of contract performance are less than 3 years. The report shall include all the above requirements for all of the 3 years of the study, a final summary of all surveys, nesting, banding and tracking, occupancy modeling analysis and discussion of findings as appropriate. If a final summary report must be prepared:

1. The draft of this summary report shall be delivered for review by Reclamation by December 15, 2025 (Year 3)

2. Reclamation shall respond with comments to the draft report by January 15th, 2026.

3. The contractor shall deliver a revised draft by February 28th, 2026.

4. Reclamation shall provide technical editing comments on the revised draft by March 15th, 2026.

5. The final summary report shall be delivered to Reclamation incorporating any changes requested by Reclamation based on review of the draft by April 15th, 2026.

3.9.8 Safety Plan & Liability Insurance

The activities required in this statement of work may expose contractor employees to various outdoor environmental safety or health hazards such as: extremes of temperature; insects such as mosquitoes, stinging and biting insects or others; scorpions and other spiders; reptiles such as poisonous snakes;

falling trees; thick vegetation that could cause eye…