Bragg_2726_RCWMon_RFP_comb.pdf

Auburn University Request for Proposal

Red-cockaded woodpecker monitoring support, Fort Bragg, NC

TABLE OF CONTENTS

Page Section I: Request for Proposal 2

Statement of Purpose 2 Scope of Work 2

1. General 2

1.1. Description of Services/Introduction 2

1.2. Objectives 2

1.3. Period of Performance 3

1.4. Quality Control 3

1.5. Recognized Federal Holidays 3

1.6. Hours of Operation 3

1.7. Place of Performance 3

1.8. Security Requirements 4

1.9. Special Qualifications 4

1.10. Other Qualifications 4

1.11. Key Personnel 4

1.12. Service Provider Personnel 5

2. Definitions and Acronyms 5

2.1. Definitions 5

2.2. Acronyms 6

3. Government Furnished Items and Services 7

3.1. Materials 7

3.2. Equipment 7

4. Service Provider Furnished Items and Responsibilities 7

4.1. General 7

4.2. Materials 7

4.3. Equipment 7

5. Specific Tasks 7

5.1. Multi-purpose Training Range 7

5.2. Infantry Platoon Battle Course 9

5.3. Special Requirements 11

6. Applicable Publications 11

TECHNICAL EXHIBIT 1 13

TECHNICAL EXHIBIT 2 15

TECHNICAL EXHIBIT 3 17

TECHNICAL EXHIBIT 4 19

TECHNICAL EXHIBIT 5 20

TECHNICAL EXHIBIT 6 22

TECHNICAL EXHIBIT 7 23

TECHNICAL EXHIBIT 8 25

TECHNICAL EXHIBIT 9 27

TECHNICAL EXHIBIT 10 28

TECHNICAL EXHIBIT 11 29

Section II: Instructions to Proposers 31 Section III: Form of Proposal 32 Section IV: Evaluation Criteria 33 ATTACHMENT A –Pricing Sheet 35

Section I. Request for Proposal

Statement of Purpose

Auburn University (AU) is seeking to contract with a service provider capable of providing red-cockaded woodpecker monitoring support to the Directorate of Public Works, Environmental Division, Fort Bragg, North Carolina.

Scope of work

1. GENERAL: This is a non-personal service agreement to provide all professional and technical support staff necessary to plan and conduct Red-Cockaded Woodpecker (RCW) activities. Additionally, the service provider shall provide the support to collect, document, edit and input all required data to conduct monitoring activities. In addition, the service provider shall provide documentation of all required permits for RCW monitoring activities. The service provider shall cooperate with Fort Bragg and other officials appointed by Fort Bragg during performance period(s), and follow standard procedures and protocol required by service providers working on the Fort Bragg installation.

1.1. DESCRIPTION OF SERVICES/INTRODUCTION: The service provider shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform RCW monitoring as defined in this Scope of Work (SOW), except for those items specified as Government Furnished Property (GFP) and services.

1.2. OBJECTIVES: The basic service objective includes the following:

1.2.1. The service provider shall follow US Fish and Wildlife Service permitting guidelines to handle dead, injured, or sick red-cockaded woodpeckers found during or as a part of research activities. The service provider should notify the Endangered Species Branch (ESB) immediately and provide a written report describing the circumstances under which the individual was found within 2 working days.

1.2.2. The service provider shall document, and report endangered species violations to Fort Bragg Military police officials (911 emergency; (910) 907-4815 non-emergency dispatch) and the Endangered Species Branch (910) 396-2544 within the same working day. The service provider shall document activities using the Government furnished Endangered Species Incident Report template and forward electronically to the Endangered Species Branch.

1.2.3. The service provider shall have communications between field crews and the Government, specifically Range Control (910) 432-1161. The service provider shall be responsible for accomplishing all work in a timely and professional manner.

1.2.4. All RCW data shall be provided using Fort Bragg cluster numbers on Global Position System (UTM referenced) Map provided by Endangered Species Branch.

1.2.5. All deliverables shall be in most recent Microsoft software, including Word, Access, and Excel, unless otherwise directed by the Technical Representative (TR).

1.2.6. All monitoring activities shall occur on the 13 Multipurpose Training Range (MPTR) and 12 Infantry Platoon Battle Course (IPBC) clusters on Fort Bragg, located in the North Carolina Sandhills. All clusters where monitoring activities take place are in Hoke County, NC.

1.3. Period of Performance: 1 April 2026 to 31 March 2027.

1.4. Quality Control: Quality Control is the responsibility of Auburn and the service provider. Auburn and the service provider are responsible for the delivery of quality services/supplies to the Government.

1.4.1. Quality Control Program: The Government is committed to a highly interactive relationship between quality control by the service provider and quality assurance by the government recipient of services. This relationship shall be achieved through an effective Prevention Based Quality Control Program (QCP) dedicated to ensuring the best possible products and services to end users.

1.4.2. Quality Assurance: The Government will evaluate the service provider’s performance under this agreement.

1.4.3. Property Management System: The service provider shall establish a system to manage Government Furnished Equipment (GFE) in its possession to control, use, preserve, protect, repair and maintain.

1.5. Recognized Federal Holidays: The service provider shall not be required to perform services on recognized federal holidays. The recognized federal holidays include:

New Year’s Day Labor Day Martin Luterh King Jr’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Juneteenth Holiday Christmas Day Independence Day

1.6. Hours of Operation: The service provider shall be responsible for conducting business, between the hours of 0500-2200 Monday through Sunday, except federal holidays or when the government facility is closed due to local or national emergencies, administrative closings or similar government directed facility closings. The service provider shall at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this SOW when the government facility is not closed for the above reasons. When hiring personnel, the service provider should keep in mind that the stability and continuity of the workforce are essential.

1.7. Place of Performance: The work to be performed under this agreement will be completed at Fort Bragg Installation.

1.8. Security Requirements: Service provider personnel shall comply with all applicable security and safety regulations, guidance, and procedures, including local, referenced in this SOW and in effect at the work sites.

1.8.1. Physical Security: The service provider shall be responsible for safeguarding all government equipment, information and property provided for the service provider’s use if applicable.

1.8.2. Fraud, Waste, and Abuse: In accordance with AR 11-2, Internal Management Controls, the service provider, shall be responsible for maintaining proper conduct and good discipline within their occupied work areas. Service provider personnel shall be encouraged to be alert to and report to designated representatives suspected of situations of fraud, waste, and abuse or other intentionally dishonest conduct observed during or in the performance of task order.

1.8.3. Access and General Protection/Security Policy and Procedures: All service provider personnel performing work under this agreement shall comply with applicable installation, facility and area commander installation/facility access, local security policies and security procedures provided by the Security Manager Government representative. Service provider personnel shall provide all information required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of Emergency Services or Security Office. Service provider personnel must comply with all personal identity verification requirements as directed by DoW, HQDA or local policies. In addition to the changes otherwise authorized by this task order, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in service providers security matters or processes.

1.9. Special Qualifications

1.9.1. Personnel performing work under this agreement shall be able to read, write, speak, and understand the English language to effectively carry out all agreement requirements. They shall have a command of both the written and spoken English language to properly clearly and effectively communicate in person or via electronic devices (telephone or Email) with co- workers, customers, and the public.

1.9.2. Service provider personnel performing work under this agreement shall be U.S. citizens unless the provisions of Army Regulation 25-2, Information Assurance have been fully completed, and approval has been granted by the Government for the non-U.S. citizen to perform the required support.

1.10. Other Qualifications: The service provider shall possess and provide ESB with a copy of all required permits for RCW banding activities. Required permits shall include Federal Endangered Species Authorization, State Endangered Species Permit, and Federal Bird Banding Lab Permit as well as Auxiliary Marking Authorization for color banding specific for the North Carolina Sandhills Region. The service provider shall have direct access to long-term RCW demographic data initiated by North Carolina State University for the North Carolina Sandhills population throughout the duration of task order performance.

1.10.1. The lead service provider employee shall have a Master’s or Doctorate degree in Biology/Wildlife/Zoology with a minimum of 10 years’ work experience in RCW biology, research and conservation.

1.11. Key Personnel:

1.11.1. The following are considered key personnel by the Government: The service provider shall provide a Program Manager (PM) who shall be responsible for the performance of the work under this task order. The name of this person, and an Alternate PM (APM), who shall act for the service provider when the PM is absent, shall be designated in writing. The PM or APM shall have full authority to act for the service provider on all agreement matters relating to daily operation of this agreement. The PM or APM shall be available between the hours of 7:30 AM to 4:30 PM, Monday through Friday, except federal holidays or when the government facility is closed for administrative reasons.

1.11.2. Qualifications of Key Personnel:

1.11.2.1. Program Manager (PM): The PM shall meet or exceed the following minimum qualifications: shall have a minimum of 10 years work experience in RCW biology, research, and conservation in the North Carolina Sandhills.

1.11.2.2. Biological Technicians: Shall be adequately trained and qualified in RCW banding techniques, monitoring, and data management while working under the contractor’s permit.

1.12. Service Provider Personnel:

1.12.1. Service provider personnel attending meetings and working in other situations where their status is not obvious to third parties, are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are government officials. They must also ensure that all documents or reports produced by the service provider are suitably marked as service provider products or that their participation is appropriately disclosed.

1.12.2. Service provider personnel shall develop, maintain, and provide to the Endangered Species Branch Technical Representative (TR) an updated roster which shall include names and positions of all service provider personnel. The service provider shall submit initial roster to the TR within ten (10) calendar days after commencement of the notice to proceed.

1.12.3. Service provider personnel shall meet the highest standards of professionalism and personal integrity.

They shall ensure their personnel do not perform work under the influence of alcohol, illegal prescribed drugs, or any other incapacitating agents. Service provider personnel shall always present a professional appearance.

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

2.1.1. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the SOW.

2.1.2. DELIVERABLE. Anything that can be physically delivered, but may include non-physical things, such as meeting minutes or reports.

2.1.3. GOVERNMENT-FURNISHED PROPERTY (GFP) OR GOVERNMENT PROPERTY (GP). Property in the possession of or directly acquired by the Government and subsequently made available to Auburn.

2.1.4. PHYSICAL SECURITY. Actions that prevent the loss or damage of government property.

2.1.5. PROPERTY MANAGEMENT SYSTEM. System established by Auburn that is used to manage GFP/GFE in its possession to control, use, preserve, protect, repair, and maintain.

2.1.6. QUALITY ASSURANCE. A planned and systematic pattern of all actions necessary to provide confidence that adequate technical requirements are established; products and services conform to established technical requirements; and satisfactory performance is achieved. For the purposes of this document, quality assurance refers to actions by the Government.

2.1.7. WORKDAY. The length of time during the day on which the service provider provides services, in accordance with the contract.

2.1.8. WORK WEEK. Monday through Friday, unless otherwise specified.

2.1.9. CAVITY START TREE. A tree containing one or more active or inactive RCW cavities or cavity starts.

2.1.10. CLUSTER. The aggregate area encompassing cavity trees (plus a 200ft buffer zone) occupied or formerly occupied by an RCW group.

2.1.11. BUFFER TREE. A tree with a sign posted on it that says you are 200 feet from a cavity tree which represents the boundary of the cluster.

2.1.12. ENDANGERED SPECIES. The following endangered species are found on Fort Bragg and Camp Mackall: Red-cockaded woodpecker (Picoides borealis), Michaux's sumac (Rhus michauxii), Rough-leaved loosestrife (Lysimachia asperulifolia), and American chaffseed (Schwalbea Americana).

2.1.13. SITES. Synonymous with endangered species sites and refers to a static location on the ground such as a RCW cavity tree, cluster of cavity trees, a population of endangered plants, etc.

2.2. ACRONYMS:

AIE Automated Installation Entry AR Army Regulation CT Compensation Time DA Department of the Army DES Directorate of Emergency Services DoW Department of War ESB Endangered Species Branch HIPAA Health Insurance Portability and Accountability Act of 1996 IGSA Intergovernmental Support Agreement INRMP Integrated Natural Resources Management Plan NCIC National Crime Information Center ODC Other Direct Costs OT Overtime POC Point of Contact POV Privately Owned Vehicles PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QC Quality Control QCP Quality Control Plan RCW Red Cockaded Woodpecker TE Technical Exhibit TR Technical Representative TSI Timber Stand Improvements UTM Universal Transverse Mercator

3. GOVERNMENT FURNISHED ITEMS AND SERVICES

3.1. MATERIALS: The Government will provide an RCW Standard Operating Procedure (SOP), an Endangered Species Branch Incident Report template, Endangered Species Branch RCW computer program;

including data on RCW Observations, USFWS Banding, Nest Checks, and Breeding Summary (separate EXCEL spreadsheet), updated cluster maps, and new tree data sheets.

3.2. EQUIPMENT: The Government will provide one Panasonic Toughbook field computer with updated data collection software and associated pertinent database.

4. SERVICE PROVIDER-FURNISHED ITEMS AND RESPONSIBILITES

4.1. GENERAL: The service provider shall furnish all supplies, equipment, facilities and services, equipment repairs required to perform work under this contract that are not listed under Section 3 of this SOW.

4.2. MATERIALS: The service provider shall provide transportation and fuel required to perform the work necessary to meet the requirements under this SOW.

4.3. EQUIPMENT: The service provider shall provide equipment required to meet the requirements under this SOW.

5. SPECIFIC TASKS

5.1. MULTI-PURPOSE TRAINING RANGE (MPTR):

5.1.1. The service provider shall complete intensive monitoring and banding of (13) RCW groups in the vicinity of the Multipurpose Training Range (MPTR) at Fort Bragg Military Installation, North Carolina.

Clusters include seven recruitment clusters (2000-2006), five clusters (112, 113, 115, 603, 194) with incidental take, and cluster 251 which was “shifted” due to the removal of 11 cavity trees during the building of the MPTR. Clusters pioneered or budded within the MPTR will be identified, tracked and monitored as discovered. All activities within MPTR will require access approval from Range control.

5.1.2. RCW cavity tree suitability updates/associated data reporting.

5.1.3. Annual cavity tree updates shall be conducted at all marked trees within approximately 13 managed RCW clusters in the vicinity of the MPTR on Western Fort Bragg. The service provider shall assess RCW cluster Activity status based on annual tree updates at all managed clusters.

5.1.3.1. Spring cavity tree updates and cavity suitability checks at designated clusters shall be accomplished using (government provided) hard copy for all clusters unless new Toughbook application becomes available through ESB. Clusters shall be visually inspected and cavity trees updated for the tree condition and progression of starts to cavities, cavity suitability checks, changes in activity status, effects of fire and military training, cavity tree losses, habitat conditions, and conditions on paint of bands.

5.1.3.2. Spring RCW cavity tree updates shall be accomplished according to the following Standard Operating Procedures (SOPs): RCW Cavity Tree Suitability /Cluster Update; Tree/Cavity Characteristics;

Cavity/Habitat Code Sheet; and Habitat Characteristics/Codes.

5.1.4. Bud or pioneered clusters: In the event of a newly pioneered cluster within the MPTR area, the service provider shall determine group composition and band nestlings and unbanded adults where necessary. The service provider shall record data on ESB provided copy and submit to the Endangered Species Branch.

5.1.5. Documentation of new RCW cavity trees: New RCW trees shall be identified in UTM (easting /northing) coordinates and documented on the New Tree Data Sheet in accordance with RCW Cavity Tree/Cluster Update SOP submission to Endangered Species Branch for (13) monitored clusters.

5.1.6. RCW monitoring, banding, and associated data reporting.

5.1.6.1. Monitoring/banding activities shall occur at all active RCW clusters on Fort Bragg MPTR (appx 13), to include cyclic nest checks, band nestlings, conduct fledgling follows, determine group composition, collect specified data, and band adults.

5.1.6.1.1. Visit managed clusters beginning during the third week of April and continuing throughout the RCW breeding-season until approximately 15 July, unless otherwise directed by the Endangered Species Branch. The service provider shall locate nests on 7–11-day cycle (nest checks); document number of eggs and nestlings and age nestlings using Ligon’s Age Chart; band nestlings at appropriate age (5-10 days, as stated in permits); identify and determine sex of fledglings following “Fledging work SOP” (Appendix F) guidelines on time since fledging nest; identify all adult red-cockaded woodpeckers for group composition;

and capture and band unknown/un-banded adults.

5.1.5.1.2. Banding data entry and reporting: The service provider shall collect/record all intensive monitoring data in accordance with the Nest Check, Fledgling, Adult Banding, and Band Codes SOP’s. The service provider shall update the computer database with RCW observations and USFWS bands issued during the performance period(s) for submission to the Endangered Species Branch for 13 MPTR-monitored clusters (using code 0999 for CC sites and commenting out actual CC cluster number in comments columns). The database shall include all RCW observations including the natal cluster, cluster where observed, color-band combination and US Fish and Wildlife band numbers and sex at fledging.

5.1.5.1.3. RCW breeding summary data: The service provider shall provide a final breeding season summary including # adult RCW’s (listed by sex), nest-tree number, number of eggs, nestlings and related breeding data for 13 MPTR-monitored sites at the end of the breeding season. The service provider shall enter data into a breeding summary spreadsheet provided at the end of each breeding season by ESB (after budded, pioneered, and activated clusters have been determined).

5.1.5.1.4. RCW group-composition data: The service provider shall provide a list of final RCW group composition (in NCBS database provided by Endangered Species Branch) electronically and at the top of each respective cluster Nest Check Data Sheet. The database shall include identifications, natal cluster, and age of birds and their status within each group for MPTR monitored clusters at the time specified within the agreement.

5.1.6. Deliverables:

5.1.6.1. SOP for RCW cavity-suitability and tree data updates/activity status data reporting is shown in Technical Exhibit 1. Annual tree updates shall be reported for all marked cavity trees on trees within approximately 13 managed RCW clusters in the vicinity of the MPTR using paper copy (including newly found and prior listed trees) provided by Endangered Species Branch.

5.1.6.2. New RCW cavity-tree documentation: New trees (including substarts) shall be flagged, have GPS coordinates recorded (UTM easting/northing) and updated, and all trees EXCEPT substarts will be tagged (ESB will make a final decision on whether to mark substarts or watch them over time. New tree locations shall be plotted on RCW cluster map and forwarded to the Endangered Species Branch for Fort Bragg. The service provider shall forward locations of new trees (UTM easting/northing format) found during Spring/Summer work to the Endangered Species Branch by 15 August, and within 2 weeks of discovery throughout the performance period.

5.1.6.3. RCW monitoring, banding, and associated data reporting:

5.1.6.3.1. RCW nest tree data entry and reporting: The service provider shall report red-cockaded woodpecker nest trees to the Endangered Species Branch on a bi-weekly basis throughout the breeding season in an Excel spreadsheet provided by Endangered Species Branch, beginning May 1.

5.1.6.3.2. United States Geological band and associated RCW data: The service provider shall document Red-cockaded Woodpeckers banded with United States Geological Survey metal bands and sex determined during fledge checks and enter into the ESB RCW (Monitoring-Access) database. Submit by 1 October of the task order year.

5.1.6.3.3. RCW Nest check data for Fort Bragg: The service provider shall collect/enter nest check data into the ESB RCW monitoring database for Fort Bragg. Hard copy of Nest Check Data Sheets will list the Group Composition and all banded nestlings from the cluster on the top of the sheet. Adult group composition shall include color band combination, age, sex, group status (floater, intruder, or member.) Red-cockaded woodpeckers observed at clusters but NOT associated with the group are documented on top of the Nest Check sheet with notations (e.g. intruder, in conflict, floater see SOP). Floaters and intruders shall NOT be included in the adult members section of the breeding summary spreadsheet but SHALL be included in the comments section. Replacement breeding adults shall be noted in both the individual comments of the top of the nest check data sheet, and the comments section of the breeding summary spreadsheet.

5.1.6.3.4. RCW Observation data for Fort Bragg: The service provider shall gather and enter observation data into the ESB RCW (Monitoring-Access) database and provide to Endangered Species Branch for Fort Bragg, no later than 1 October of each task order year. The service provider shall provide hard copies of RCW Observation datasheets for any observations/banding activities from 1 October through the end of banding activities. for the 13 MPTR clusters no later than 31 December. The service provider is NOT responsible for entering these last months of observation data observations into the electronic database.

5.1.6.3.5. RCW Breeding summary data: The service provider shall provide breeding season data for 13 MPTR clusters on Fort Bragg no later than 1 September of each task order year.

5.2. INFANTRY PLATOON BATTLE COURSE (IPBC)

5.2.1. This Task order is for the monitoring of (12) of the 13 RCW groups within the future Infantry Platoon Battle Course (IPBC) project area at Fort Bragg Military Installation, North Carolina. Monitored clusters include 77-79,104,238-242, 424, 581, and 612 (clusters 240 and 242 received incidental take). Monitoring of IPBC clusters (Technical exhibit 11) will NOT include banding of nestlings or adults. All activities within IPBC will require access approval from Range Control.

5.2.2. RCW cavity tree updates and suitability checks/associated data reporting:

5.2.2.1. Annual cavity tree suitability updates shall be conducted at all marked trees within approximately 12 managed RCW clusters in the vicinity of the IPBC on Western Fort Bragg. The service provider shall assess RCW cluster Activity status and record on annual tree update data sheets at IPBC clusters.

5.2.2.2. Spring cavity tree updates and cavity suitability checks at designated clusters shall be accomplished using (government provided) hard copy for all clusters unless Toughbook application becomes available by ESB. Clusters shall be visually inspected and cavity trees updated, checked for cavity suitability, tree condition, and progression of starts to cavities, activity status, effects of fire and military training, cavity tree losses, habitat conditions, and condition of green tree bands. Documentation will be recorded for cavity trees damaged or destroyed by live fire training. To accomplish tree updates and cavity suitability checks, the service provider shall use SOPs: RCW Cavity Tree Suitability/Cluster Update; Tree/Cavity Characteristics;

Cavity/Habitat Code Sheet; and Habitat Characteristics/Codes.

5.2.2.3. Auburn shall provide documentation of new RCW cavity trees within the monitored IPBC clusters.

New RCW trees shall be identified in UTM (easting /northing) coordinates and documented on the New Tree Data Sheet in accordance with RCW Cavity Tree/Cluster Update SOP for submission to Endangered Species Branch for (12) monitored clusters.

5.2.3. RCW monitoring and associated data reporting at IPBC clusters: The service provider shall visit managed clusters ;77, 78, 79, 104, 238, 239, 240, 241, 242, 424, 581 and 612 (Cluster 48 is within the McPherson Impact Area and will not be monitored for safety reasons) beginning the third week of April and continuing throughout the RCW breeding-season until approximately 15 July, unless otherwise directed by the Endangered Species Branch. The service provider shall locate nests on 7–11-day cycle (nest checks);

document number of eggs and nestlings, age nestlings using Ligon’s Age Chart. Nestlings will NOT be banded. Nestlings shall be visited ON LIGON DAY 21 for a full nest count. If nestlings are present, the nest will be presumed to be successful (nestlings are likely to fledge). If no nestlings are present at day 21, the nest is presumed to have failed and is recorded as such. If no nest is found after a month of nest checks, biologists should conduct morning work at the active cavities. This entails arriving at the cluster prior to (sunrise) and determining activity of cluster—inactive, captured, solitary, or a non-breeding pair by conducting a 1-2 hour follow of the bird(s) exiting the cavity(ies).

5.2.3.1. Monitoring activities shall occur at all designated, RCW clusters on the Fort Bragg, NC IPBC (appx

12) (Technical exhibit 11) to include cyclic nest checks, determine if group is a potential breeding group (PBG), non-breeding group (NBG), solitary, or captured cluster, and collect data as specified below

5.2.3.2. Data entry and reporting: The service provider shall collect/record all intensive monitoring data in accordance with the SOP’s. The service provider shall update the computer database nest check data during the performance period(s) for submission to the Endangered Species Branch for 12 IPBC-monitored clusters.

5.2.3.3. RCW Breeding summary data: The service provider shall provide a final breeding season summary including # adult RCW’s, nest-tree number, number of eggs, nestlings and related breeding data for 12 IPBC-monitored sites at the end of the breeding season. The service provider shall enter data into a breeding summary spreadsheet provided at the end of each breeding season by ESB (after budded, pioneered, and activated clusters have been determined).

5.2.4. Deliverables:

5.2.4.1. Annual tree updates and cavity suitability shall be reported for all marked cavity trees on trees within approximately 12 managed RCW clusters in the vicinity of the IPBC using paper copy (including newly found and prior listed trees) provided by Endangered Species Branch. The SOP for the annual spring RCW cavity-tree suitability data updates/activity status data reporting is shown in Technical Exhibit 1.

5.2.4.2. New RCW cavity-tree documentation: New trees shall be flagged, have GPS coordinates recorded (UTM easting/northing) and updated, and all trees EXCEPT substarts will be tagged (ESB will make a final decision on whether to mark substarts or watch them over time. New tree locations shall be plotted on RCW cluster map and forwarded to the Endangered Species Branch. The service provider shall forward locations of new trees (UTM easting/northing format) found during Spring/Summer work to the Endangered Species Branch by 15 August, and within 2 weeks of discovery throughout the performance period.

RCW monitoring, and associated data reporting:

5.2.4.3.1. RCW nest tree data entry and reporting: The service provider shall report red-cockaded woodpecker nest trees to the Endangered Species Branch on a bi-weekly basis throughout the breeding season in an Excel spreadsheet provided by Endangered Species Branch, beginning May 1.

5.2.4.3.2. Electronic RCW data for Fort Bragg: The service provider shall document and enter red-cockaded woodpecker nest check data, into the ESB RCW Monitoring (Access database) nest visit table and submit by 1 October of the task order year.

5.2.4.3.3. RCW Breeding summary data: The service provider shall provide breeding season data for 12 IPBC clusters on Fort Bragg no later than 1 September of each task order year.

5.3. SPECIAL REQUIREMENTS:

5.3.1. A representative from Auburn or Fort Bragg Endangered Species Branch may be present during any task order activity conducted on the MPTR or IPBC clusters on Fort Bragg. The service provider shall provide names of all field personnel, vehicle descriptions, license plate numbers, and individual license numbers of individuals involved in activities prior to commencement of work.

5.3.2. Vehicle Registration: The service provider shall fully comply with the vehicle registration requirements regarding service provider-owned and service provider employees privately owned vehicles (POVs) as set forth in Fort Bragg Regulation 190-5. Please be advised that service provider vehicles and service provider employee POVs are subject to random search anytime.

5.3.3. Restrictions: Service provider field personnel shall restrict vehicular traffic to maintained firebreaks, trails and roads. Vehicles are prohibited from entering marked endangered plant sites. Parking within RCW clusters is only permitted while conducting field activities within the immediate cluster and should be avoided when possible. In areas where clearance shall be authorized by the Fort Bragg Directorate of Plans and Training (Range Operations), the service provider shall coordinate timely and appropriate access and assure radio or telephone communications with endangered species personnel and Range Operations personnel at

(910) 432-2900 (office phone) or (910) 432-1161 (radio room) as necessary. Entry into unauthorized areas or impact areas is prohibited. Service provider shall not conduct field activities if disruptive or conflicting with military training activities.

6. APPLICABLE PUBLICATIONS

6.1. Auburn must abide by all applicable regulations, publications, manuals, and local policies and procedures.

The following shall be referenced and utilized during the performance of this task order:

• AR 11-2 Managers’ Internal Control Program

• AR 25-2 Army Cybersecurity

• AR 200-1 Environmental Protection and enhancement

• AR 530-1 Operations Security (OPSEC)

• Endangered Species Act 16 U.S.C. §1531 et seq. (1973)

• Fort Bragg Endangered Species SOP’s

• Fort Bragg ESMC Endangered Species Management Component 2019

• Fort Bragg INRMP Integrated Natural Resources Management Plan (2019-2023)

• Migratory Bird Treaty Act (16 U.S.C. §§ 703–712)

• Red-cockaded Woodpecker (Picoides borealis) Recovery Plan Second revision 2003

• SIKES ACT (16 USC 670a-670o, 74 Stat. 1052)

TECHNICAL EXHIBIT 1

RCW CAVITY TREE SUITABILITY/CLUSTER UPDATE SOP

Update clusters for changes in tree or cavity conditions; collect midstory habitat data; determine damage from military training, including wildfires, etc. Document changes in tree conditions such as damage to bole, condition of painted bands, or death. Also make sure tree is properly tagged, plotted and GPS’d. See Code Sheets.

Visit managed clusters annually between mid-March and mid-July

Check each marked tree for cavity stage, shape, and activity. Determine whether each complete cavity is suitable or not suitable (See below): Record on cluster update datasheet

SUITABLE CAVITY: that does not need to be peeped

STATUS=ACTIVE,

STAGE=complete or recently complete SHAPE=Normal, Atypical, Burned normal, Slightly enlarged, Ent Enlarged, or Healing** but large enough for RCW to enter

If STATUS=INACTIVE, STAGE and SHAPE as above Then these trees can be peeped until 4 SUITABLE CAVITIES are identified within the cluster. Once 4 suitable cavities are identified, no more cavities need to be peeped and they will register as “possibly suitable in the data.

If there are not 4 suitable cavities in the cluster, additional cavities will be provisioned for the cluster later in the fall.

Only change a database field on the Toughbook if necessary; DO NOT CHANGE species, bole, deformity, flattop, dbh, height or direction! Simply note any discrepancies in comments

Record NEW starts/cavities, in existing cavity trees, on Toughbook/Paper copy.

If you find a RECENTLY dead cavity tree that still has evidence of fresh RCW activity, record a death cause, but still report the cavity/start as active. Report any recently dead cavity trees that show any sign of RCW activity or were previously active, to ESB within 48 hours.

Review .jpg cluster maps in the field and note any discrepancies. Report discrepancies in cluster maps with new GPS data in UTMs to ESB.

Re-tag any trees that are missing tags and NEVER remove a tree tag, unless directed by ESB.

NEW TREES - natural: when possible, paint, collect and enter data in Toughbook. When it is not possible to gather the data at the time, flag the tree and plot its location on the map-- fill out a New Tree data sheet and give to ESB for future data collection.

NEW TREES - provisioned: will be entered onto data sheets at time of provisioning.

Provide the following data to ESB bi-weekly:

Forward all known nest trees in Excel spreadsheet with GPS coordinates in UTMs

Cluster, inspection date, and activity status using criteria listed below.

ACTIVE– must have at least 1 active cavity BREEDING– change active to breeding IF there is a nest: a) Observe eggs, b) hear RCW nestlings / see adults feed nestlings, c) see adults feed fledglings.

FWS Active – has a possibly active cavity, active start only, or recent RCW chipping. Must follow-up to determine if activity increases or decreases, or morning follow to determine if bird is occupying site and make a final determination if cluster is active or inactive.

INACTIVE– NO RECENT RCW activity.

Provide completed computer (and/or paper copy as specified by ESB) tree update data and GPS maps (in UTM) at ESB office no later than 15 August of each year.

TECHNICAL EXHIBIT 2

TREE/CAVITY CHARACTERISTICS SOP

Use the following tree and cavity characteristics and codes while updating clusters - use Code Sheet supplied by ESB where appropriate.

TREE DATA

Tree number Cluster number Species - see Code Sheet Bole - see Code Sheet Disease and Deformity - see Code Sheet Flattop - yes or no DBH - use D-tape and enter measurement.

Bands - see Code Sheet Death - see Code Sheet; if tree has data recorded and is on the ground, do not need to visit Comments: issues re:tree eg: needs tag, paint, recently burned, etc.

CAVITY DATA (Do not change height and direction from previous year) Height - if new start/cavity, use clinometer to measure height Direction - use from 0 to 359 degrees

CAVITY STAGE (See Cavity/Habitat Code Sheet) Completed - back of cavity not visible; resin wells present; plate construction usually has begun.

Recently completed - no back visible; resin wells being developed (not numerous); plate - none or beginning.

Advanced start - at least 4" horizontal depth; resin wells few or lacking - serious resin well construction begins as cavity nears completion.

Start - circular excavation into sapwood no more than 4" deep (horizontally); few if any resin wells.

Substart - excavation small, just breaking into sapwood; do not confuse with resin wells which expose sapwood but do not enter it.

Open roost - used for crotch or crevice in the tree where birds regularly roost. Must have resin wells and sap accumulation. This classification is rarely used to mark trees anymore.

CAVITY SHAPE

Normal RCW - typical circular shape; approximately 2” diameter.

Enlarged RCW - enlarged by other species; 3” or greater and considered unsuitable.

Atypical - cavity shape irregular or possibly not of RCW origin; use for RCW cavities in scars, limb stubs, etc. Also use for open roost sites.

Burned RCW normal - cavity burned but not enlarged.

Burned RCW enlarged - cavity burned and enlarged - (may have been enlarged previous to being burned) -indicate in comments if you think fire-enlarged cavity.

Healed over - cavity/start aperture closed.

Slightly enlarged – entrance and tunnel are slightly enlarged; 2-3” diameter and considered suitable.

Entrance enlarged - entrance only is enlarged; tunnel is normal shaped and considered suitable.

Screened - used for provisioned trees.

Healing-RCW tree of any stage (start, adv. Start, complete) is beginning to heal over but not completely healed over.

ACTIVITY

Active - small amount of red chipping around cavity and in resin wells; for starts, inside of cavity bright yellow; wood particles in tunnel; fresh chipping around rim; fresh sap.

Possibly active - questionable RCW use; small amount of chipping; no fresh sap.

Inactive - usually no chipping, though rarely a very small amount may be present; little or no sap for starts, inside grayish yellow; no chipping; no fresh sap.

Relic - no fresh chipping; cavity often enlarged; plate and resin wells healing over. Relics can become active again, but usually revert to relic status (after becoming active and inactive) without passing through the inactive category.

OTHER OCCUPANTS - see Code Sheet

SUITABILTIY- suitable if cavity is in tact with no leaking or water, no rotting, and the entrance tunnel is intact. Wood outside the cavity plate must not be dead.*****************

COMMENTS – examples of pertinent comments: pileated woodpecker, debris in cavity, etc.

TECHNICAL EXHIBIT 3

CAVITY/HABITAT CODE SHEET SOP

STAGE NATURA ARTIFICIAL INSERT RESTRICTOR OTHER OCCUPANTS

COMPL 10 11 12 MECA = red bell wp REC COMPL 20 21 13 (Natural cav) GLVO = fly squirrel cav) ADV START 30 cavity) SISI = bluebird

31 14 (artificial

START 40 41 APME = honey bee SUB START 50 FASP = kestrel OPWN ROOST 80 MEER = redhead wp

SCCA = gray squirrel STVU = starling EULA = broad-h-skink

SHAPE ACTIVITY SICA = wh br nuthatch

1= NORMAL RCW 1 = ACTIVE COAU = flicker 2= ENLARGED RCW 2 = POSS ACTIVE SCNI = fox squirrel 3= ATYPICAL 3 = INACTIVE POSP = wasp 4= BURNED NORMAL 4 = RELIC OTAS = screech owl

5= BURNED ENLARGED 5 = NOT VISITED MYCR = gr cr flycatcher

6= HEALED OVER PIBO = RCW

7= SLIGHTLY ENLARGED

8= ENTRANCE ENLARGED

9= SCREENED

10=Healing

TREE DATA CODES

SPECIES

1=LL

2=LOB

BOLE

0=NONE

1=CAT/BOX

2=WOUND

BANDS DEF & DIS (up to 7 char) ` DEATH

0=NONE ``

1=WH/GOOD

2=WH/BAD

0=NONE ``1=FIRE

`1=DEAD/BRK/TOP 2=LIGHTN

3=PP

4=SL

5=SHRT

3=CAT/BOX

4=CROOK

5=GREEN/GOOD

6=GREEN/BAD

7=KNOT TRK

8=LTN OLD

9=LTN RECENT

2=FORK TOP

3=SWEEP

5=LEAN

6=DEAD

`````` ` ` 3=CUT

4=WINDTHR0

5=WINDSNAP

6=SILT

7=INSECT

8=OTHER

9=UNKN

HABITAT DATA CODES

HABITAT and TRAINING EVALUATIONS ARE WITHIN 50’ & ALSO 51-200’OF CAVITY TREES

SPECIE

S

0=NON

E

1=HARDWOOD

DENSITY

0=NONE

1=SPARSE

HEIGHT IN/NEXT TO

0=NON

E

1= 1-5 FT

DRAIN YES

or

NO

2=PINE (w/i 50ft) 2=MODERATE 2= 6-10 FT

3=SHRUBS 3=DENSE 3= 11-15 FT

4= 16+ FT

TRAINING IMPACTS: 0= NONE X=

1X=DAMAGE TO CAVITY OR START TREE 6=NEW IMPACTS

2X= SOIL DISTURBANCE 7=OLD

IMPACT

3X = HABITAT DISTURBANCE

4X = COMBINATION OF ABOVE (REQUIRES A COMMENT)

5X = OTHER

TECHNICAL EXHIBIT 4

HABITAT CHARACTERISTICS/CODES SOP

The following discussion of habitat codes should be followed while updating, and in conjunction with the Cavity/Habitat Code Sheet:

The habitat codes in general are used to measure any midstory encroachment to the cavity/start tree, in full circle around the cavity tree and at a distance of 50 and 200 feet from the cavity tree. When assessing the surrounding area, try to capture the condition that constitutes the greatest problem. For example, species code 2 is used when pines are the worst habitat problem, usually a pocket of pines within 50 feet of the cavity tree and blocking the entrance to cavity or start. Code 3 denotes “shrubs” and is used in instances when trees are in or next to drains and the presence of shrubs is more of a problem than surrounding hardwoods or pines. Code 1 is for hardwoods and a code of 0 means there is no trees or shrubs within 50 or 200 feet of the cavity tree (grasses, open areas).

When assessing midstory density, again measure midstory conditions surrounding the tree in the full circle around the cavity tree and at a distance of 50 and 200 feet from the cavity tree. Code 0 denotes an absence of midstory. Code 1 is defined as “sparse”; midstory trees have a spacing >20 feet. Code 2 is “moderate” and the spacing of midstory trees is 10-20 feet. Code 3, “dense”, is midstory trees with a spacing of less than 10 feet.

The height codes are self-explanatory and are used in conjunction with density specifically to assess any midstory encroachment problems. For example, a low density with low height midstory is not as serious a problem as would be moderate to dense density with heights over 10 feet. Height code 0 denotes none and should only be used with grasses or open areas. Code 1 is for encroachment of 1-5 feet; code 2 is for 6-10 feet; code 3 is for 11-15 feet; and code 4 is for encroachment greater than 16 feet.

There is also a comment to denote whether a cavity or start tree is in or next to a drain. No denotes that the tree is not in or next to a drain, yes indicates that it is.

Training impacts are indicated as new, since last updates (Code 6X) or old (Code 7X) impacts. All training impacts require a comment. Try to be as specific as possible, but if impact is unclear, comments are useful.

TECHNICAL EXHIBIT 5

NEST CHECK / NESTLING BANDING / BREEDING STUDY SOP

Study is to be conducted annually from the third week of April through early to mid-July on a 7-11 day cycle.

All data to be recorded in the Access database / Toughbook furnished by the Government.

Determine all potentially breeding clusters by checking the activity status of cavity trees at all clusters within the determined contract area. All cavities and advanced starts should be peeped during ‘suitability’ tree-cavity updates, and all active cavities shall be peeped thereafter on a 7-10 day cycle during the breeding season until a nest is found or it is mid-July.

At each cluster, check all active cavity trees and all active advanced starts for a nest by lightly scraping on the tree to see if an adult flushes. An approved “peeper” may be used for the nest check, (and cavity suitability checks) following strict adherence to recent permits and RCW Recovery Plan.

If a nest is not located, visit cluster again in 7-11 days and peep all active cavities and advanced starts.

If a nest is located, determine the number of eggs or nestlings present using a treetop peeper or climbing with a drop light and mirror. If eggs are present, record the number and revisit the nest in 7-9 days. At MPTR clusters, After eggs hatch, determine appropriate banding date (between day 5-10).

If nest fails (at any stage), record information and revisit for renesting activity on 7-11 day cycle.

If nestlings are present, estimate and record age - while birds are in cavity - using Ligon's Age Characteristic Chart.

Only when nestlings are old enough to band (at least 5 days old, preferably 6 – 9), proceed with banding. DO NOT pull or band nestlings less than 5 or greater than 10 days old (specific condition of federal endangered species permit).

If nestlings are not old enough to band, return to band when determined necessary.

Record the following nest check data in the current ESB computer program: cluster number; study area; date;

tree number (nest tree, or active trees checked); time (military); number eggs (if applicable) - note: only put 0 if tree was climbed or peeped and cavity was empty- otherwise leave blank for unknown; number nestlings (if applicable); Ligon's age (if applicable); number adults; add comments to the bottom of the Toughbook tab including pertinent observations to qualify above activities, including identification of adults, if adult flushed, number of GLVO or other occupants seen/removed etc.

When extracting nestlings to band, use only permit approved “pulling” techniques to extract nestlings.

Handle nestlings carefully and keep them warm or cool, as appropriate, and dry during entire activity. Do not pull/band nestlings during periods of inclement weather.

Determine appropriate group combination and individual colors using availability list in the cluster banding book. If colors are limited, and you need to reissue a color, reissue a color from a bird that was never seen during fledge checks. Check with ESB monitoring program coordinator BEFORE banding activity, if you think you will need a new combination.

Band nestlings (at MPTR-clusters) with color bands and USFWS band. Be sure that at least 1 individual conducting the banding is on the current permit.

Bands are read and recorded as follows: right leg top to right leg bottom; left leg top to left leg bottom. The top band is closest to the "knee" joint; the bottom band is closest to the foot. Fort Bragg birds are banded on one leg with a three-band combination identifying the group. A single-color band and aluminum band are placed on the other leg to identify the individual within the group. The “banding matrix” developed December 2003 will incorporate split color band combinations and tri-colored group combinations into the data-base.

See “Recording Band Codes for RCW Observations SOP”.

Check to make sure color bands are placed properly, that they do not pinch bird, and that all toes are outside bands.

Recording new banding data in the Updated ESB computer program will automatically generate a new observation for the individual, Record the following on field banding data sheets: cavity tree and cavity number; 1 or 2 for initial capture/band or recapture respectively; weight (in grams); age; cluster number; date;

military time; color combination and individual color issued; any pertinent comments, including any injury to nestlings. Sex of the nestling will be input into the banding data table after the bird has been fledged, otherwise it will be listed as “U” for unknown. All data recording must be approved by ESB.

Carefully return nestlings to the nest cavity, one at a time. If the nestlings vary in size, the smallest goes in

LAST.

Use drop-light and mirror to look inside cavity and check that all nestlings are secure (ie. no toes caught on cavity ledge).

If a nestling dies while conducting banding procedures, or is injured during banding activities, or is found dead prior to fledging, report immediately to ESB, who will notify the USFWS Endangered Species field offices and the Wildlife Resource Commission.

Leave immediate vicinity of nest tree as quickly as possible.

Try to identify any banded adults nearby during banding or nest check activities (note number of adults, if any/how many unbanded birds, conflict, etc). It is important to ID adults as often as possible.

If a site does NOT breed, early morning follows are necessary to determine what adults are present and group status and should be accomplished as early in the nesting season as possible.

TECHNICAL EXHIBIT 6

FLEDGING WORK (BREEDING STUDY) SOP

Estimate fledging date (approximately 26 days) at all breeding clusters within the MPTR banding study areas.

At IPBC clusters, where banding nestlings are not warranted, a pre-fledging check is allowed when nestlings are 21 days old. This activity must not disturb nestlings and should be limited in time. Once the nest has been peeped, and number (and sex, if possible) of nestlings determined and recorded, nest will be presumed “successful”

Visit (MPTR) clusters as soon as possible after estimated fledging date, preferably no later than 4 days.

Follow group until all fledglings have been identified and sex of each determined.

Determine sex of the fledglings by absence/presence…