Attachment 1 Bird Drone Detection Radar Enterprise BOA SOW_06May22 CLEAN.pdf

PDF 397 KB Posted

Attached to
DRAFT RFQ Bird Detection Radar/Drone Detection Radar and Support Services for USAF Federal contract opportunity
Solicitation number
FA940122QZ001
Issued by
Department of the Air Force Materiel Command Nuclear Weapons Center

View the file

Other files for this federal contract opportunity

Other files attached to DRAFT RFQ Bird Detection Radar/Drone Detection Radar and Support Services for USAF, newest first.
File Type Posted
Attachment 4 Addendum to FAR 52.212-2 Evaluation—Commercial Items.pdf PDF
Attachment 5b Model Agreement Schedule with clauses DRAFT.pdf PDF
1 RFQ Cover Letter.pdf PDF
Attachment 2 BOA Provisions.pdf PDF
Attachment 6 Sample Order CLIN Structure.pdf PDF
Attachment 3 Addendum to FAR 52.212-1 Instructions to Offerors—Commercial Items.pdf PDF
Attachment 5a SF 1449.pdf PDF
Attachment 7 Question and Answer Spreadsheet.xlsx XLSX spreadsheet

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

DEPARTMENT OF THE AIR FORCE

BIRD/DRONE DETECTION RADAR

STATEMENT OF WORK (SOW)

06 May 2022

OVERVIEW

This Basic Ordering Agreement (BOA) is a written instrument of understanding, negotiated between the Government and Contractor to provide the Department of the Air Force (DAF) with a streamlined acquisition solution for Bird Detection Radar (BDR) or Bird/Drone

Detection Radar (B/DDR) units and support services to be competed among a pool of approved contractors. This agreement is not a contract. The purchasing organization (i.e., Ordering Activity [OA]) shall define individual requirements created in an independent scope tailored to the organization’s specific needs.

BACKGROUND

In 2005, independent contractors researched and developed a real-time bird monitoring radar using existing radar technologies to identify local bird hazards at airfields. Within the aviation industry, the developed technology is referred to as Bird Detection Radar. Since its inception, BDR technologies have advanced to accurately depict bird concentrations and movements at airfields.

Over the past 15 years, BDR units have been purchased and maintained at nine DAF locations, including: Beale Air Force Base, Dare County Bombing Range (Seymour-Johnson

Air Force Base), Dover Air Force Base, Joint Base Randolph-San Antonio, Offutt Air Force

Base, Royal Air Force Lakenheath, Wake Island (Pacific Regional Support Center), Melrose

Air Force Range, and Whiteman Air Force Base, with additional units continuously being added by DAF Major Commands (MAJCOMs) and Installation Wing Safety units for detection and avoidance of bird hazards to aircraft.

Over the past several years, advancements in commercially available Small Unmanned

Aircraft Systems (sUAS) have posed an operational security threat to DAF Installation assets and a hazard to safe aviation operations from midair collision events. To combat this threat, DAF security and counter-sUAS agencies have worked to advance sUAS intrusion detection technologies. However, commercially available BDRs have begun to market dual-detection capability for bird hazards and sUAS targets. These systems differentiate sUAS targets and bird hazards of varying sizes within detection ranges (i.e., B/DDR). Within the DAF, Wings and MAJCOMs have expressed interest and need for detection of wildlife and sUAS strike hazards to safe aviation operations. However, a department-wide solution currently does not exist.

DAF promotes use of BDRs through guidance in Air Force Instruction (AFI) 91-212, Bird/wildlife Aircraft Strike Hazard Management Program, encouraging integration of BDR output into site-specific bird hazard avoidance operations and procedures. However, no formal policies, Concept of Operations, or requirements for BDR use in DAF Bird/wildlife

Aircraft Strike Hazard (BASH) Programs exist. To formalize use of BDR technology into

DAF BASH directives, a streamlined acquisition strategy must be standardized, enabling

DAF Commanders with a tool for compliance and proactive BASH safety.

1.0 DESCRIPTION OF REQUIREMENT

1.1. Concept. The DAF experiences thousands of bird strikes each year during flight operations in low-altitude, airfield environments. As a result, the DAF incurs millions of dollars in aircraft damage due to wildlife strike events. The occurrence of hazardous bird abundances on/near airfields threatens the safety of aircrews and reduces the combat capability of military aircraft to fulfill the Department of Defense mission.

DAF Flight Safety (SEF) Offices employ integrated wildlife hazard management operations, consistent with requirements and guidance in AFI 91-212, Bird/wildlife Aircraft Strike

Hazard Program Management. Current DAF policy requires each installation to implement local bird hazard avoidance procedures, formally known as a Bird/wildlife Hazard Warning

System. This unit-defined system requires use of a tiered approach to restricting local flight conditions based on Bird Watch Conditions; an observed wildlife occurrence that could affect flight operations, resulting in a wildlife strike event. Under an increased Bird Watch

Condition, aircraft operations can be restricted or terminated based on the threat posed by wildlife, visually observed by ground personnel, Air Traffic Control, and/or aircrews.

Designation of Bird Watch Condition by observation is exclusively limited to the range of sight for air operations personnel or Air Traffic Control supervisors. Confident issuance of

Bird Watch Condition is restricted to diurnal air operations (e.g., confirming night bird activity is impossible without enhanced detection equipment). DAF installations with BDR units have reported instances where hazardous bird conditions were detected and avoided, but occurred outside the visual range of detection for operations personnel.

Information provided from B/DDR output can provide real-time hazard avoidance and enhance Mid Air Collision Avoidance (MACA) Programs while supporting requirements from Air Force Instruction 91-202, The US Air Force Mishap Prevention Program, paragraph 7.3.3. Currently, DAF policy for sUAS detection focuses on ensuring operational security from intrusion, with no specific radar requirement for MACA and SEF considerations.

The varying features of sUAS, including size, shape, coloration, and sophisticated movement capabilities, could negatively impact safe flight operations and pose an even greater detection challenge than wildlife. Airport wildlife biologists can anticipate movement of birds based on a familiarity with species behavior and known attractants on/surrounding the airfield.

Unlike birds, the movement of a sUAS aircraft is unpredictable, especially if the sUAS operator has malicious intent for operation within a DAF airfield environment. Siting sUAS with ground observers and maintaining visual confirmation over significant linear distances is inefficient and impractical for assuring midair avoidance by manned aircraft operations.

Integration of BDR and B/DDR technologies into DAF SEF programs enhances a unit’s ability to safeguard mission integrity and maintain combat capability through mishap prevention/avoidance. Detection of bird hazards and analysis of local bird movement provides BASH Managers with the data needed for immediate avoidance decisions and provides information to execute long-term management changes to the aerodrome landscape.

Detection of sUAS will aid air space management and avoidance procedures for manned

DAF aircraft operations (e.g., MACA program).

1.2. Scope. The objective of this SOW is to provide the DAF with a streamlined acquisition solution for BDR or B/DDR units and support services. The purchase of radar units and services under this SOW may occur as initial investments into detection radar technology; to recapitalize aging, inefficient BDRs currently maintained at DAF airfields; or to support sustainment of current radars on DAF installations. The availability of funds within each Squadron, Wing, and/or Major Command will dictate the number of radar units acquired under this SOW. The department-wide standup of BDR technologies involves over

59 DAF locations and within 140 Air National Guard units. The BOA may also be opened up to the wider Department of Defense community as needs are identified.

Acquisition under this BOA is accomplished through a Delivery or Task Order made by through Ordering Activities (OAs). Each Order could include:

Unit purchase of BDR or B/DDR with one-year equipment warranty and service support package, including radar site planning, delivery (Continental United States [CONUS] and/or Outside the Continental United States [OCONUS]), user training, and support service

Five-year full-service system support program (e.g., to include maintenance, data storage, data analysis, and training)

BDR upgrade to include sUAS detection capability

2.0. PROGRAM MANAGEMENT

2.1. General. The Government and contractor must communicate effectively to ensure the

SOW requirements meet the functional needs of DAF Safety programs while remaining consistent with DAF Safety and Security requirements. The relationship between the contractor, Air Force Safety Center (AFSEC), and DAF customers is critical to facilitate effective mission support, maintenance, sustainment, and technical support of radar technologies. The contractor shall manage all aspects of delivery, with consideration for enhancing proactive safety procedures to reduce the threat of bird and sUAS hazards to aircraft. The contractor shall provide a skilled, experienced workforce to ensure all deliveries meet all SOW requirements.

2.2. Work Hours. Contract services will be provided on normal business days, which are

Mondays through Fridays, during business hours from 8:00 AM to 5:00 PM, local to the contractor’s main office, or as specified by the OA, except for United States (U.S.) Federal holidays. The contractor shall be available by telephone within 30 minutes after notification to discuss contract matters with Government personnel. After scheduled duty hours, the contractor shall be available within two hours after notification. Any overtime for management functions shall be performed at no additional cost to the Government.

2.3. Reporting. The contractor will report to the 377 Mission Support Group (MSG)

Services Contracting Branch and AFSEC on all executed Orders. The contractor will report all Order actions, to include radar units purchased and upgrades/extended service warranties executed under this SOW. The reports support the 377 MSG and

AFSEC to serve an intra-agency liaison role to DAF customers and not as Contracting

Officer Representatives. Send reports electronically to the AFSEC BASH Team org email: BASH2@us.af.mil. Contractor reports will be submitted to the 377 MSG and

AFSEC quarterly, to include:

DAF organization purchasing unit and contact information.

Status of each Order (e.g., production, site selection, planning, and status to final functional capability).

Sustainment, updates, and warranty actions/repairs.

Communication with customers (DAF organizations).

Contractor-generated reports will also be sent to each respective Installation Primary Contact for each OA organization that executes an Order under this SOW.

mailto:BASH2@us.af.mil

2.4. Compliance. The contractor shall ensure that all options executed under this contract are accomplished in accordance with applicable Government regulations, directives, instructions, policies, and best business practices.

3.0. PERSONNEL

3.1. Qualifications. The contractor will ensure all staff supporting BDR and B/DDR units have a comprehensive understanding of DAF airfield environments, wildlife biology, radar detection, aviation safety, airspace security, DAF airfield operations, and sUAS systems.

The contractor must provide documentation, demonstrating technical competency and capability for development of BDR and B/DDR units. Each contractor will identify at least two primary Project Managers for the acquisition of commodities and delivery of services under this SOW:

3.1.1. Technical Project Manager. The contractor shall provide and identify a Technical

Project Manager that will serve as the primary contact for executing commodities-based disciplines under this SOW. The Technical Project Manager must demonstrate minimum key qualifications to serve this role for the contractor. Other personnel may support the execution of technical disciplines under this SOW, but only under the purview of the

Technical Project Manager. The minimum key qualifications for the Technical Project

Manager will include:

A minimum of a Bachelor of Science degree in Engineering, Wildlife Management, or an environmental compliance-based field of study.

Professional work experience in radar systems, engineering, or wildlife biology. A minimum of five consecutive years of experience is required. Experience must be demonstrated in a detailed resume documenting the type of professional experience acquired, duration, company, and a current reference.

Professional work experience within airfield safety or support for a U.S. military organization. A minimum of two years of non-consecutive experience is required and demonstrated in a detailed resume documenting the type of professional experience acquired, duration, company/unit, and a current reference.

3.1.2. Support Service Project Manager. The contractor shall provide a Support Services

Project Manager that will serve as the primary contact for executing services-based disciplines under this SOW. The Support Service Project Manager must demonstrate minimum key qualifications to serve this role for the contractor. Other personnel may support the execution of technical disciplines under this SOW, but only under the purview of the Support Service Project Manager. The minimum key qualifications for the Support

Service Project Manager will include:

A minimum of a Bachelor of Science degree in Engineering, Geographic Information

Systems management, data science/analytics, Wildlife Management, or an environmental compliance-based field of study.

Professional work experience in radar systems, engineering, data analysis, or

Geographic Information Systems. A minimum of five consecutive years of experience is required. Experience must be demonstrated in a detailed resume documenting the type of professional experience acquired, duration, company, and a current reference.

Professional work experience within airfield safety or support for a U.S. military organization in radar support applications. A minimum of two years of non-consecutive experience is required and demonstrated in a detailed resume documenting the type of professional experience acquired, duration, company/unit, and a current reference.

3.2. Setup and Sustainment Personnel. The contractor shall provide a sufficient number of qualified personnel to complete site selection, setup, and on-site sustainment at each DAF installation. The contractor shall ensure personnel fulfilling site selection, setup, and on-site sustainment meet qualifications for access to DAF installations. The contractor shall provide sufficient personnel to ensure the unit is fully operational at final setup. All personnel performing maintenance on electronic equipment shall meet the minimum qualification standards established by the U.S. Department of Labor’s Service Contract Act Directory of

Occupations.

4.0. Operational Security

4.1. Purpose. Contractor adherence to DAF and Department of Defense (DoD) Operations

Security (OPSEC) requirements is mandatory, to include stipulations under this SOW.

Adherence to OPSEC requirements includes real-time changes occurring throughout the life cycle of this agreement. Government contractors are provided this guidance to ensure compliance and protection of critical information that may be a threat to national security.

4.2. Definition. OPSEC is a methodical process to identify Critical Information (CI), identify threats to that CI and the related vulnerabilities and risks of exploitation to that CI, and identify, develop, and implement countermeasures to protect that CI. CI is specific facts about friendly intentions, capabilities, and activities vitally needed by adversaries for them to plan and act effectively so as to guarantee failure or unacceptable consequences for friendly mission accomplishment. CI includes those facts, which individually or in the aggregate, reveal sensitive details about U.S. Government (i.e. DAF installation or the contractor’s security or operations related to the support or performance of the SOW). These sensitivities require a level of protection from adversarial collection or exploitation not normally afforded to unclassified information. OPSEC supplements, but does not replace traditional security practices such as Physical Security and Information Security. OPSEC is essential to ensure the initial and continued success of our mission, operations, systems, and procedures.

4.3. OPSEC Applicability. OPSEC safeguards are an essential Task required for all Orders under this agreement. The contractor will adhere to the following minimum requirements in support of the DAF OPSEC Program:

Introduction of personnel electronic devices into government spaces, laptops, tablet PCs, cellular phones, cameras, recording devices, and data recording/storage devices is

STRICTLY controlled and forbidden in some areas of DAF installations. Photography and recording is not allowed except for official use and by permit only, unless otherwise stipulated in the Order.

Contractor personnel shall not discuss government operations in public or over unprotected or unencrypted communications. Official business, controlled unclassified information may only be transmitted as directed in the SOW.

The contractor shall not post to company websites, publications, newsletters or other media any images, data or information that reveal sensitive government operations, personnel, equipment, and/or classified or controlled unclassified information. When in doubt, company press releases related to this BOA and any Orders should be coordinated through the Ordering Activity’s Contracting Office.

Because observation of events, operations, physical changes, and other related actions may reveal National Security information, specific restrictions are needed to preclude unintentional release of this information to unauthorized parties. (Unauthorized disclosure and transfer of National Security Information is punishable under 18 USC §

793). Therefore, contractor personnel shall not disclose to unauthorized third parties, post to unofficial sites (including Social Networking sites) any images, data or information, or observed events that reveal sensitive government operations, personnel, or equipment.

Government-issued badges and identification shall be removed and/or concealed from plain sight when off installation and shall not be left unprotected. Badges and passes may not be duplicated or copied or loaned to others. Lost or stolen identification credentials will be immediately reported to the Installation Security Forces Law Enforcement Desk.

Practice OPSEC and implement countermeasures to protect CI and other sensitive unclassified information and execution of military operations performed or supported by the contractor in support of the mission.

The contractor shall mark and protect related internal production schedules, deliverables, inventories, shortages, and identified vulnerabilities related to production of government material. Internal company markings e.g., Business Sensitive, etc., are appropriate for identifying the aforementioned as sensitive information. Specific Government-provided information, drawings etc., will be protected in accordance with guidance in applicable

Sections of this SOW.

Destroy critical and/or sensitive unclassified information no longer needed to prevent the inadvertent disclosure and/or reconstruction of this material.

Critical information identified by Installation Safety Office will be marked and handled appropriately as Controlled Unclassified Information (CUI). Government CI includes but is not limited to: known or probable vulnerabilities to any U.S. system and their direct support systems, details of information about military operations, unit, vessel, aircraft movements/arrivals, missions and exercises, etc.

CUI initial and annual refresher training will be required for all contractors. The contractor shall not access, download or further disseminate any CUI outside the execution of the defined contract requirements without the guidance and written permission of the government Contracting Officer.

Questions regarding CI shall be directed to the Installation OPSEC Program Manager or

DAF OPSEC Support Team.

5.0. RADAR REQUIREMENTS AND SUPPORT SERVICES

Orders will include one of two unit options: a BDR (Section 5.1.) or B/DDR (Section 5.2.)

unit. A one-year equipment warranty, along with site planning, delivery, and installation/setup shall be included with purchase of unit. Multiple tasks exist under this

SOW, including site planning (Section 5.3.), CONUS delivery (Section 5.4.), OCONUS delivery (Section 5.5.), sUAS detection upgrade (Section 5.6.), and a five-year system service option (Section 5.7.), which shall be available as separate Order options under this agreement.

5.1. TASK – BDR Option Technical Capability. The contractor will provide a turnkey, sustainable BDR unit package, which includes all elements necessary, meeting full operating capability for detection/visualization of avian targets and support services.

5.1.1. Mobility. BDR units will be a corrosion-resistant mobile system. Mobility must be achieved using a full-size truck (transported within the truck bed or by pintle hook). Towed radar systems must be constructed to U.S. Department of Transportation road standards. The radar unit must be compatible with a flat, hard surface. Delivery of radar units must meet

DoD requirements for tie-down on board military airlift and sea freight and meet requirements for Air Transportability Test Loading Activity (ATTLA) certification.

5.1.2. Operational Capability. BDR radar system configuration must provide a continuous radar solution (24 hours per day, 7 days per week, 365 days per year) for real-time detection of bird hazards in support of safe aviation operations. BDR systems must include all operational components needed for full operational capability.

5.1.3. Durability. BDR antenna arrays and exterior coatings must be corrosion resistant and adequately safeguard internal components of the radar system from all possible extreme temperature ranges (-30ºF to 120ºF) and precipitation (rain/snow). The antenna utilized must meet the needs of each site, providing the greatest detection capability possible and consistent with identified performance standards.

5.1.4. Power and Connectivity. Provide adequate power and network connection capability for each BDR unit, consistent with standards in industry, DAF systems, and each geographic location. Power connections must adequately support functionality of the radar unit and allow the simplest level of connection to available sustainment sources (identified by each purchasing installation). Connections must also be compatible with systems available at

OCONUS locations. Network capabilities must be compatible with DAF hard-wired and wireless connections.

5.1.5. Backup Power. Provide and maintain a backup AC power source for each BDR unit in case of a failure or interruption of prime AC power. The backup power source shall be capable of maintaining full radar operational power for up to five hours. The backup power source shall be initially sized for full system load plus 50 percent future capacity. The backup power source shall be attached as part of the mobile solution.

5.1.6. Site-Specific Equipment. Provide ancillary support equipment necessary for BDR configuration at the sited location. Various support equipment may include: wheel chocks, lightning protection, tie-downs/ground anchors, basic tools and equipment storage box on site, reflective safety markings, frangible elements, fire extinguishers, and/or signage.

5.1.7. Risk Alert. Incorporate an automated bird strike risk alert system for bird detection within the approach/departure corridors and surrounding airfield environment. Calibration of the automated bird strike risk alert system must be flexible to each installation/site.

Detection alerts must include the capability to notify users across multiple communication techniques, to include but not limited to: email, text messaging, visual alert in the radar output, and Air Traffic Control tower information display systems (e.g., IDS5).

5.1.8. Coverage and capability. From the radar sensor, provide a three-dimensional solution for avian radar detection, capable of detecting 1 Standard Avian Target (SAT) up to an altitude of 1,000 feet above ground level (AGL) and within a range of 0.3 to 1 nautical mile or, detecting at least 2 SAT up to an altitude of 3,000 feet AGL and within a range of

0.3 to 3 nautical miles. An SAT is defined as an avian target with a Radar Cross Section of

-16 dBm²; and a mass of 1.1 pounds (e.g., an American crow). At a minimum, detection must include the runway(s) and approach/departure corridor uniquely defined at each airfield.

5.1.9. Detection Accuracy. The contractor must provide data processing techniques and tracking methods to detect bird movement across the airfield landscape. BDR detection response time must be within five seconds of Standard Object Detection. BDRs must have a range accuracy of at least 20 meters, and an azimuth/elevation accuracy of at least one degree, respectively, for bird detection. The radar will include a strategy for eliminating false target detections and errors. The radar design must include a strategy for reducing the impact of precipitation on target detection.

5.1.10. Network Security. Ensure real-time system display is available through either a closed, remote platform or over DAF networks. The contractor will provide all required services to accommodate a remote output solution (if requested by the OA, to include access over DAF computers, tablets, and cell phones, and other devices). The contractor will ensure all radar software and hardware is compatible with all DAF Operational Security, Information Technology, and Cooperative Vulnerability and Penetration Assessment

(CVPA) requirements. If an Authority to Operate (ATO) is required from the DAF to operate radars on DAF networks, the contractor is not responsible for obtaining and sustaining an approved ATO. The contractor will provide the DAF with specifications about the radar and information exchange as needed.

5.1.11. Detection Visualization. Display output must clearly depict bird detections and bird track movements for immediate visualization, complemented by a risk alert system (Section

5.1.7.). The radar system must include a technical solution to differentiate birds from other targets and false detections. The contractor will provide radar technologies and outputs that depict multiple bird targets simultaneously within all detection coverage of this requirement.

5.1.12. Detection Reports. Generate recurring reports for bird movement within the detection area. Reports must provide generalized interpretation of detection information for use by all levels of DAF personnel (i.e., BASH Managers, wildlife biologists, SEF personnel, and/or Senior Leadership). Reports should identify movement trends by hour, day, week, and month for analysis. Provide copies of these reports to AFSEC for reference, consistent with

Section 5.3.

5.1.13. Detection of sUAS Capability. Each BDR unit must be technically compatible for inclusion of future bird detection updates and sUAS intrusion detection system upgrades.

BDR sustainment services and sUAS detection radar upgrades are included in this SOW, while other sUAS detection support components are not. Acquisition of future sUAS detection support components is independent of this agreement and is based on requirements defined by the OA/owner. Support features include but are not limited to: sUAS detection hardware/software (outside the scope in Section 5.6.), video verification, electro-optical/infra-red cameras, acoustic sensors, Light Detection and Ranging (LiDAR) technology, and/or Radio Frequency detection.

5.1.14. Equipment Warranty. All unit hardware and software is covered under an all-inclusive warranty for one-year, beginning at the date of Government Acceptance of the

Order for each individual unit. The contractor will repair or replace radar system components deemed defective due to manufacture or workmanship. Equipment failure due to misuse, acts of God (e.g., lightning, flooding, or fire), and unit modification inconsistent with vendor guidance will void the one-year equipment warranty. All repairs and replacement parts will be new or refurbished parts – whichever provides the greatest benefit to the Government. The contractor will certify the repairs and workmanship performed by all employees; ensuring radar unit downtime does not exceed seven consecutive days. The one-year warranty does not include damage to the radar unit for actions outside the control of the contractor (i.e., damage or part failure due to an outside source).

5.1.15. Information Security. The contractor will maintain radar system hardware and software to ensure connectivity is sustained in accordance with DAF and DoD Information

Technology security requirements at the time of award for each Order.

5.2. TASK – B/DDR Option Technical Capability. The contractor shall ensure each

B/DDR unit meets all functional operation capabilities for detection of sUAS intrusion into the aerodrome. The B/DDR must meet all requirements and specifications of Section 5.1.

(Subsections 5.1.1. through 5.1.15.), as well as sUAS detection elements (Subsections 5.2.1.

through 5.2.4.)

5.2.1. sUAS Detection Standard. Provide continuous, real-time, three-dimensional detection of sUAS intrusion and tracking within the runway approach/departure corridor. All detections will be displayed real-time in spatial depiction along with an automated sUAS intrusion alert. At a minimum, detection coverage for sUAS will encompass 360 degree field of view around the airfield out to at least four nautical miles from the ground level to aircraft operational altitudes (3,000 feet AGL).

5.2.2. Target Detection Range and System Compatibility. B/DDRs must be capable of detecting small (approximately 245 x 290 x 55 mm) to medium (approximately 322 x 242 x

84 mm) sized, commercially available sUAS targets. Detection of sUAS targets must be compatible with detection of bird targets, simultaneously. B/DDR detection sensor(s) must support signature of multiple targets at one time.

5.2.3. Visualization and System Security. Ensure real-time system display is available through either a closed, remote platform or over the DAF networks. The contractor will provide all required services to accommodate a remote output solution (if requested by the

OA, to include access over DAF computers, tablets, and cell phones, and other devices).

Visualization of sUAS intrusion into the aerodrome must be depicted in a clear, easy to interpret output, complemented by intrusion alerts. The contractor will ensure all radar software and hardware is compatible with all DAF Operational Security, Information

Technology, and Cooperative Vulnerability and Penetration Assessment (CVPA) requirements. If an ATO is required from the DAF to operate radars on DAF networks, the contractor is not responsible for obtaining and sustaining an approved ATO. The contractor will provide the DAF with specifications about the radar and information exchange as needed.

5.2.4. Hardware and Software Requirements. Provide a software and hardware solution for sUAS detection to include a real-time intrusion alert system. Each B/DDR unit must be technically compatible for inclusion of future sUAS detection support components not included in this SOW. Each DAF customer will define these requirements outside of this agreement. At a minimum, B/DDR units must be compatible with solutions to enhance detection and counter-operations for sUAS intrusion, including but not limited to: video verification, electro-optical/infra-red cameras, acoustic sensors, Light Detection and Ranging

(LiDAR) technology, and/or Radio Frequency detection devices. Adoption of any system updates, outside the technical contractor solution, are not options under this agreement. The

B/DDR must include a solution to differentiate between avian and sUAS targets. The hardware and software solution must be capable of accepting data streams from the Air

Traffic Control system to include: Automatic Dependent Surveillance-Broadcast (ADS-B) and UAS Remote Identification Data (RID).

5.3. TASK – Site Planning – Shall be included with each unit purchase.

5.3.1. Unit Purchase. Site planning is a required service included with each BDR or B/DDR unit Order executed under this agreement. Any future site planning changes after the

Government Acceptance of the Order will remain outside this agreement, and will be negotiated between the OA and the contractor.

5.3.2. Site Access. Each OA will designate an Installation Primary Contact for each site. The contractor will coordinate with the Installation Primary Contact for executing the Order.

Coordination must include remote planning to fulfill each Order, consistent with all SOW requirements. Any planning required on-site at each installation is at the burden of the contractor. If on-site, all contractor personnel must comply with Installation Commander

Policy for base access, including local security requirements and procedures. The Installation

Primary Contact will support the contractor for installation access, coordinating with each respective Installation Security Office, if required.

5.3.3. Site Selection. The contractor must coordinate with each Installation Primary Contact to develop a radar Installation Site Plan. Development of the Installation Site Plan must include critical information needed for positioning the radar unit, including siting limitations.

The Installation Site Plan must identify the optimal placement of the radar unit, identifying limitations of siting in relation to base infrastructure (e.g., trees, buildings, and other obstructions affecting radar output), as well as other Unified Facilities Criteria requirements and airfield safety standards. The Installation Site Plan must identify at least three additional contingent siting locations if the optimal placement cannot be achieved. The Installation

Site Plan will include spatial depictions of radar capabilities relative to the preferred placement.

The Installation Site Plan will identify radar utility needs required for functionality, including power and network connections. Utility services (i.e., primary power source and DAF network requirements) are the responsibility of the Government. The Installation Primary

Contact will coordinate all utility needs outside this SOW. The OA is responsible for ensuring sufficient utilities are available at the proposed site prior to radar delivery (i.e., network/wireless connectivity, power, and local information security requirements). The contractor is responsible for fulfilling backup, auxiliary power requirements, as identified in

Section 5.1.5. The Installation Site Plan will be confirmed by the Installation Primary

Contact by signature.

5.4. TASK – CONUS Delivery, Installation, and Training – Shall be included with each unit purchase.

5.4.1. Unit Purchase. Delivery, unit installation, and training are all required services included with each CONUS BDR or B/DDR unit Order executed under this agreement. Any reinstallation for radar units or training requirements outside of the one-year service period, following the Government Acceptance of the Order will remain outside this agreement, and will be negotiated between the OA and the contractor.

5.4.2. Delivery Contact. The contractor will coordinate with the Installation Primary

Contact to facilitate all logistics for delivery of all order components. The Installation

Primary Contact is responsible for all administrative functions required for delivery of each radar unit onto the site. For planning, the contractor will provide delivery tracking updates to the Installation Primary Contact for movement of the cargo.

5.4.3. Delivery. The contractor is responsible for delivery of radar systems to a CONUS location designated by the Installation Primary Contact. For CONUS sites, Government

Acceptance of the Order will be designated once the radar is operational.

5.4.4. Setup. The contractor is responsible for final setup of the BDR or B/DDR unit at the designated site identified in the Installation Site Plan. Setup for CONUS radar unit purchases shall be executed within 90 to 150 days of an official Notice to Proceed issued by the

Installation Primary Contact, following award of each Order. Execution of the Site Planning

(Section 5.3.) for each Order is required concurrent with the purchase and delivery/installation Orders to avoid setup issues.

The Installation Primary Contact will ensure all utilities necessary to perform final setup are complete prior to issuance of the Notice to Proceed. The contractor will coordinate with the

Installation Primary Contact for setup access no later than 72 hours prior to entrance onto the

Installation.

5.4.5. Training Instruction. Upon Government Acceptance of the Order for each individual radar unit, the contractor will provide an in-person training for use of the BDR or B/DDR unit. At a minimum, the target audience for initial instruction must include: uniform and civilian representatives from SEF, Airfield Management, Air Traffic Control, Security

Forces, and Command Post. The contractor will coordinate remote trainings (i.e., interactive video conferencing) throughout the one-year period following Government Acceptance of the Order, upon request from the Installation Primary Contact.

5.4.6. Training Materials. The contractor shall maintain high quality, effective visual training materials for Installation personnel on BDR and B/DDR operations. Training materials must focus on operation of the unit, interpretation of detection output, and troubleshooting for BDR and B/DDR units. The method for recurrent, remote educational outreach will include, but is not limited to: interactive video conferencing (e.g., Microsoft

Teams), internet-based training, and proposed strategies for improved radar detection.

5.4.7. Services and Data Management. The contractor will provide data management, storage, and system services for the one-year warranty period. All of the five-year system support services included under Task 5.7 (Sections 5.7.1. through 5.7.7.) are required for the initial service year following Government Acceptance of each radar unit purchased under this

SOW.

5.4.8. sUAS System Calibration. For execution of B/DDR Orders (Section 5.2.), the contractor will provide one detection demonstration at the time of setup, ensuring sUAS detection capability. A demonstration will include the successful radar detection of a deliberate test flight for a target sUAS (consistent with the size of sUAS in Section 5.2.2.).

The contractor will provide any required site-specific calibrations of individual B/DDR units to execute sUAS target classification and verification, consistent with detection performance requirements of this SOW. The contractor must coordinate with the Installation Primary

Contact and is responsible for all administrative planning, travel, and execution of sUAS detection calibration or detection capability demonstration flights (e.g., all permissions and waivers for flying test sUAS on a DoD facility, consistent with current DAF policy).

5.5. TASK – OCONUS Delivery, Installation, and Training – Shall be included with each unit purchase.

5.5.1. Unit Purchase. Delivery, unit installation, and training are all required services included with each OCONUS BDR or B/DDR unit Order executed under this agreement.

Any reinstallations for radar units or training requirements outside of the one-year service period, following the Government Acceptance of the Order will remain outside this agreement, and will be negotiated between the OA and the contractor.

5.5.2. Delivery Contact. The contractor will coordinate with the Installation Primary

Contact to facilitate all logistics for delivery of all order components. The Installation

Primary Contact is responsible for all administrative functions required for delivery of each radar unit onto the site. For planning, the contractor will provide delivery tracking updates to the Installation Primary Contact for movement of the cargo.

5.5.3. Delivery. The contractor is responsible for delivery of radar systems to an OCONUS location designated by the Installation Primary Contact. The contractor is responsible for the integrity of the shipment to the OCONUS site (i.e., Government Acceptance of the Order is complete when the unit is operational OCONUS, consistent with Section 5.5.5.). OCONUS delivery is complete when the unit is operational, fulfilling Government Acceptance of the

Order.

5.5.4. Setup. The contractor is responsible for final setup of the BDR or B/DDR unit at the designated site identified in the Installation Site Plan. Setup for OCONUS radar unit purchases shall be executed within 90 to 150 days of an official Notice to Proceed issued by the Installation Primary Contact, following award of each Order. Execution of the Site

Planning (Section 5.3.) for each Order is required, concurrent with the purchase and delivery/installation Orders to avoid setup issues.

The Installation Primary Contact will ensure all utilities necessary to perform final setup are complete prior to issuance of the Notice to Proceed. The contractor will coordinate with the

Installation Primary Contact for setup access no later than 72 hours prior to entrance onto the

Installation.

5.5.5. Training Instruction. Upon Government Acceptance of the Order for each individual radar unit, the contractor will provide an in-person training for use of the BDR or B/DDR unit. At a minimum, the target audience for initial instruction must include, but not limited to: uniform and civilian representatives from SEF, Airfield Management, Air Traffic Control, Security Forces, and Command Post. The contractor will coordinate remote trainings (i.e., interactive video conferencing) throughout the one-year period following Government

Acceptance of the Order, upon request from the Installation Primary Contact.

5.5.6. Training Materials. The contractor shall maintain high quality, effective visual training materials for Installation personnel on BDR and B/DDR operations. Training materials must focus on operation of the unit, interpretation of detection output, and troubleshooting for BDR and B/DDR units. The method for recurrent, remote educational outreach will include, but is not limited to: interactive video conferencing (e.g., Microsoft

Teams), internet-based training, and proposed strategies for improved radar detection.

5.5.7. Services and Data Management. The contractor will provide data management, storage, and system services for the one-year warranty period. All of the five-year system support services included under Task 5.7 (Sections 5.7.1. through 5.7.7.) are required for the initial service year following Government Acceptance of each radar unit purchased under this

SOW.

5.5.8. sUAS System Calibration. For execution of B/DDR Orders (Section 5.2.), the contractor will provide one detection demonstration at the time of setup, ensuring sUAS detection capability. A demonstration will include the successful radar detection of a deliberate test flight for a target sUAS (consistent with the size of sUAS in Section 5.2.2.).

The contractor will provide any required site-specific calibrations of individual B/DDR units to execute sUAS target classification and verification, consistent with detection performance requirements of this SOW. The contractor must coordinate with the Installation Primary

Contact and is responsible for all administrative planning, travel, and execution of sUAS detection calibration or detection capability demonstration flights (e.g., all permissions and waivers for flying test sUAS on a DoD facility, consistent with current DAF policy).

5.6. TASK – Standalone sUAS Detection Upgrade.

5.6.1. Baseline Unit Requirement. To execute this order, the OA must already maintain a

BDR unit. This upgrade is applicable to any BDR unit, regardless of the original purchase method, to include an acquisition outside of this agreement.

5.6.2. sUAS Detection Upgrade. Provide a final deliverable that meets all performance requirements defined in Section 5.2. of this SOW, providing the OA with a B/DDR.

5.7. TASK – System Service and Data Management.

5.7.1. Technical Services. A five-year, full-service system support Order will facilitate technical service requirements for radar units beginning at the date of award, after any existing service contract periods have expired. Use of this task may be applied to radars purchased under this SOW or in other acquisition efforts. The Order must accomplish all repair and technical sustainment services for BDR or B/DDR systems. Technical services will include, but are not limited to: parts replacement, repair, software updates, hardware updates, or any other service required to return the radar unit back to the performance specifications of this SOW. All upgrades and repair services shall be coordinated with the

Installation Primary Contact prior to completion. As necessary, the contractor will conduct an on-site visit to each BDR and B/DDR location to inspect the unit and ensure operational integrity.

In the event of a system failure or defect, the Government will notify the contractor in a reasonable and timely manner. The contractor shall respond within three (3) business days to coordinate parts delivery and repair. The contractor will cover all costs to repair any damages to safety system components or any associated equipment in the event of any malfunction or non-operation of the equipment during the warranty period. Any costs associated with fulfillment of warranty repairs, including personnel travel or shipping, is the responsibility of the contractor. The contractor will coordinate with the Installation Primary Contact for service access no later than 72 hours prior to entrance onto the Installation.

5.7.2. Support Services. A five-year, full-service system support Order will facilitate support service requirements for radar units beginning at the date of award, after any existing service contract periods have expired. Use of this task may be applied to radars purchased under this SOW or in other acquisition efforts. The Order must accomplish all service support functions to ensure user access and function of the radar unit and generated data.

Support services will include, but are not limited to: training, suppression of non-targets, output calibration, interpretation reporting for OA inquiries, and support for OA data trend analysis. The contractor shall respond within three (3) business days to assist in support service requests, providing acknowledgement, course of action, and milestones for completion (e.g., informal, by email or telephone).

5.7.3. Data Storage Management. The contractor will provide all equipment and processes for the sustainment of bird data collected from BDR and B/DDR units. The contractor will maintain backup storage of all bird data collected from BDR and B/DDR for each annual service Task Order. Data storage must be compatible with DAF Information Security requirements, identified locally by each OA.

5.7.4. DAF Safety System Integration. The contractor must collect and store all bird radar detection data in a format this is compatible, transferrable, and readable for integration into the DAF Bird Avoidance Model (BAM)/Avian Hazard Advisory System (AHAS). Bird detection data must be continuously stored and provided to the OA’s Installation Primary

Contact and AFSEC Bird/wildlife Aircraft Strike Hazard Team by the 1st of each month through completion of contract. AFSEC delivery will be accomplished by an electronic data storage/exchange strategy compatible with DAF Information Technology and Security requirements using the email address (BASH2@us.af.mil) or by delivery using a Compact

Disc to the mailing address: Air Force Safety Center BASH Team, 9700 G Ave, SE, Kirtland

AFB, 87117. The data must be in a format that can be opened and utilized by the DAF and/or vendor supporting the AHAS system; this will be specified in the Order.

5.7.5. Data Rights. All data and data rights, including report documentation associated with this SOW, is property of the U.S. Government. The contractor shall provide the mailto:BASH2@us.af.mil

Government with unlimited data rights to all software and information developed under

Orders off of this agreement. The contractor will not use data for marketing, publication, or presentation without prior written consent from the AFSEC. Contact the

AFSEC Bird/wildlife Aircraft Strike Hazard Team to coordinate use and release of radar detection data.

5.7.6. Updates. Annually, at a minimum, contractor-released updates to operating software will be provided and installed either on-site (as necessary) or remotely. Updates must remain consistent with DAF and DoD Information Technology security requirements.

5.7.7. sUAS Recurrent Calibration. If the OA has a B/DDR, a minimum of one, annual sUAS detection demonstration is required for each year of the five-year system support/extended warranty. If sUAS detection performance is unmet during the demonstration the contractor will provide any required site-specific calibrations of individual

B/DDR units to execute sUAS target classification and verification, consistent with requirements in Section 5.2.1. through 5.2.4. of this SOW. The contractor must coordinate with the Installation Primary Contact and is responsible for all administrative planning, travel, and execution of sUAS detection calibration or detection capability demonstration flights (e.g., all permissions and waivers for flying test sUAS on a DoD facility, consistent with current DAF policy).

6.0. Acronym List

AFI – Air Force Instruction

AFSEC – Air Force Safety Center

AHAS – Avian Hazard Advisory System

BAM – Bird Avoidance Model

BDR – Bird Detection Radar

B/DDR – Bird/Drone Detection Radar

BOA – Basic Ordering Agreement

CONUS – Continental United States

CUI – Controlled Unclassified Information

DAF – Department of the Air Force

DoD – Department of Defense

MACA – Mid Air Collision Avoidance

MAJCOMS – Major Commands

OA – Ordering Activity

OCONUS – Outside the Continental United States

SEF – Flight Safety

SOW – Statement of Work sUAS – Small Unmanned Aircraft Systems

File details come from the government source that posted it. Updated .