Draft PWS_24Sep26_Updated labels.pdf

PERFORMANCE WORK STATEMENT

(PWS)

Integrated Small Unmanned Aircraft Systems (sUAS) Detection and

Bird/Wildlife Aircraft Strike Hazard (BASH) Radar System

AT

KEESLER AFB, MS

24 Sep 2026

1.1. GENERAL: This is a non-personal services contract to provide an integrated small unmanned aircraft systems (sUAS) and bird/wildlife aircraft strike hazard (BASH) radar system to Keesler Air Force

Base (KAFB), Mississippi (MS). The Contractor shall establish a system operating on a closed-loop, air-gapped, dedicated dark-fiber virtual local area network (VLAN) architecture to deliver a unified Common

Operating Picture (COP).

1.2. SCOPE OF WORK: Contractor shall provide all personnel, equipment, tools, materials, software, firmware, mounting hardware, transportation, supervision, integration, installation, testing, documentation, training, warranty support, and non-personal services (except those identified as Government provided) necessary to deliver a complete, operational, and standalone airspace awareness system.

1.3. HOURS OF OPERATION: The Contractor shall be responsible for conducting business between the hours of 8:00 a.m. and 4:30 p.m., Monday through Friday, except Federal recognized holidays

Contractor shall maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS.

1.3.1. Contractor shall staff a business office to respond to all complaints and requests for repairs during the stated business hours (7:00 a.m. and 7:00 p.m. Central Standard Time (CST), Monday through Friday except recognized Federal holidays). After Normal Duty Hours, the contractor shall be available to receive complaints and requests for repairs, with an expected response the following business day. A 24-Hour contact number shall be provided to the 81 Training Wing (TRW) Plans and Programs Office and

Contracting Officer (CO).

1.4. PHYSICAL SECURITY: Contractor shall be responsible for safeguarding all Government property provided for contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured.

1.5. PERSONNEL INFORMATION ROSTER: Contractor shall provide a primary and alternate personnel to manage and oversee PWS. Names of primary and alternate (who shall act for primary personnel in his/her absence) shall be designated in writing to the Contracting Officer. Contractor shall provide telephone numbers for primary and alternate personnel where these persons may be contacted before, during, or after normal work hours. The Contractor shall provide the personnel information roster

(CDRL A001) no later than five (5) business days after contract award. If there are any changes to the personnel, the contractor shall submit the updated information no later than 24 hours after the change.

Contract personnel shall be able to read, write, speak, and understand English fluently. Contract personnel shall have full authority to act for the Contractor on the installation and possess full contractual signatory authority. Contractor shall meet with the 81 TRW Plans and Programs Office and CO when requested.

Contractor may request a meeting with 81 TRW Plans and Programs Office and CO as necessary.

1.6. CONTRACTOR EMPLOYEES: Contractor personnel shall present a clean, neat, and professional appearance and be easily recognized as contractor personnel. This may be accomplished by wearing distinctive clothing showing the name of the company or by wearing appropriate badges that contain the company name and employee name. No item of military clothing shall be worn by a contractor as an outer garment.

1.7. QUALITY ASSURANCE: The Contractor shall provide a Quality Control Plan (QCP) (CDRL

A002) covering the services outlined herein to allow for the inspection and acceptance of services rendered no later than ten (10) days after contract award.

1.8. SAFETY PROGRAM: Contractor shall be responsible for ensuring their employees and managers have a comprehensive understanding of safety as well as full compliance with Occupational Safety and

Health Administration (OSHA) requirements. Detailed information on safety is available on the OSHA website at https://www.osha.gov/.

https://www.osha.gov/

1.8.1. Contractor shall submit a Safety and Health Plan (CDRL A003) and corresponding site safety checklist to the CO and 81 TRW Plans and Programs Office not later than ten (10) calendar days after contract award. Contractor’s safety and health plan shall include appropriate measures to ensure the contractor reacts promptly to investigate, correct, and track alleged safety and health violations and/or uncontrolled hazards in contractor work areas. The plan shall:

1.8.1.1. Identify the roles and responsibilities of the following individuals with respect to safety:

Management, Supervisors, Employees, and Safety Coordinator;

1.8.1.2. Identify applicable safety rules and regulations;

1.8.1.3. Include a worksite hazard analysis to include base-line hazard identification and required control measures;

1.8.1.4. Include a job site analysis to include hazards of tasks required to control measures;

1.8.1.5. Identify employee safety and health training requirements and the documentation process;

1.8.1.6. Include a workplace inspection frequency, to include identifying the individual conducting the inspections;

1.8.1.7. Include employee hazard reporting procedures;

1.8.1.8. Identify individual(s) responsible for corrective action of hazards;

1.8.1.9. Identify first aid/injury procedures;

1.8.1.10. Identify procedures for accident investigation and reporting;

1.8.1.11. Identify emergency response procedures; and

1.8.1.12. Identify the process for tracking controlled hazards in contractor work areas.

1.8.2. Contractor’s QCP shall identify the processes and procedures the contractor will use to track compliance with the Safety and Health Plan, and the process and procedures that will be used to correct violations.

1.8.3. Contractor shall establish these safety requirements for all subcontractors who qualify as applicable contractors under the resulting contract.

1.9. SECURITY REQUIREMENTS: All Contractor Personnel employed by the Contractor in the performance of this contract, or any representative of the Contractor entering the Government installation, shall abide by all security regulations of the installation (i.e. DAFMAN 31-101V1, Base Defense Planning, 16 October 2024).

1.9.1. Base Access. The 81 Plans and Programs Office will arrange access to the Government Installation with the contractor.

1.10. RECORDS:

1.10.1. Freedom of Information Act (FOIA) Program. The Contractor shall comply with the requirements of DoDM 5400.07_AFMAN 33-302, Freedom of Information Act Program, 27 April 2018. If the

Contractor receives a FOIA request, the Contractor shall ensure it is delivered immediately to the base

FOIA manager (81 CS/SCOK) for processing. The FOIA manager will task a Government official who, as the authorized official, will make the decision on releasing Government records.

1.10.2. Privacy Act Program. The Contractor shall create, maintain, and destroy Privacy Act data IAW

AFI 33-332, The Air Force Privacy and Civil Liberties Program, 9 March 2020, and Privacy Act systems of records notice(s) (http://dpcld.defense.gov/Privacy/SORNs.aspx). The Contractor shall not create or maintain a Privacy Act system of records prior to public notice. If the Contractor receives a Privacy Act request, the Contractor shall be responsible for searching for the records and providing those records to a

Government official who, as the authorized official, will make the decision on releasing the Government records.

1.10.3. For Controlled Unclassified Information (CUI). When creating paper documents containing sensitive information, add “Controlled Unclassified Information” at the top of the document and the following statement at the bottom: The information herein is Controlled Unclassified Information (CUI) which must be protected under the Freedom of Information Act of 1966 and Privacy Act of 1974, as amended. Unauthorized disclosure or misuse of the PERSONAL INFORMATION may result in criminal and/or civil penalties. Shred documents containing sensitive information when the disposition has been met.

1.11. OPERATIONAL SECURITY (OPSEC):

1.11.1. Critical Information. The Contractor shall safeguard critical information identified by the 81 TRW

Plans and Programs Office and assist in identifying any specific data, systems, and processes that, if compromised, could significantly harm the organization. This includes but not limited to:

1.11.1.1. User Data.

1.11.1.1.1. Usernames and Passwords. Access credentials are highly sensitive and should be protected at all costs.

1.11.1.1.2. Traffic Data. Information about user activity, files accessed, and communication content, can reveal sensitive operations or personal information.

1.11.1.1.3. Location Data. If applicable, data about user locations derived from wireless connections could be used for tracking or targeting.

1.11.1.2. Physical Security.

1.11.1.2.1. Facility Locations. Specific addresses or detailed descriptions of buildings housing critical infrastructure can make them targets.

1.11.1.2.2. Security Procedures. Information about access control measures, guard schedules, or surveillance systems can be used to bypass security.

1.11.1.3. Operational Information.

1.11.1.3.1. Maintenance Schedules. Knowledge of when systems are offline for maintenance could be exploited to cause disruptions or gain unauthorized access.

1.11.1.3.2. Incident Response Plans. Details about how the organization responds to security incidents could be used to hinder mitigation efforts.

1.11.1.3.3. Contract Details. Sensitive information within the PWS itself, such as specific technologies used, costs, or timelines, could be valuable to competitors or adversaries.

1.11.1.4. Personal Information.

1.11.1.4.1. Employee Rosters. Lists of names, contact information, or roles within the organization could be used for social engineering attacks or to target individuals with specific knowledge.

1.11.1.4.2. Security Clearances. Information about the security clearances held by personnel could be used to assess the sensitivity of the information they have access to.

1.11.2. Threat Analysis: 81 TRW Plans and Programs Office shall provide a brief analysis of potential adversaries and their capabilities.

1.11.3. OPSEC Measures: 81 TRW Plans and Programs Office will detail specific countermeasures the contractor must implement beyond basic training, such as:

1.11.3.1. Information Handling Procedures. Secure storage, transmission, and disposal of sensitive information

1.11.3.2. Incident Reporting. Clear processes for reporting suspected or actual OPSEC breaches.

1.11.3.3. Social Engineering Awareness. Training to recognize and resist social engineering attempts.

1.11.4. OPSEC Training.

1.11.4.1. Contractor personnel shall complete unit specific OPSEC in-processing training provided by the

81 Plans and Programs Office OPSEC Coordinator within 30 calendar days of providing services. Training must be documented on the DD Form 254 - Contract Security Classification Specification for classified contracts.

1.11.4.2. All Contractor personnel shall complete annual refresher OPSEC awareness training provided by the 81 TRW Plans and Programs Office OPSEC Coordinator.

1.11.5. Disclosure of Information.

1.11.5.1. The Contractor shall not release to anyone outside the Contractor’s organization any unclassified information, regardless of medium (e.g., film, tape, document, etc.), pertaining to or execution of any part of this contract or any program related to this contract, unless:

1.11.5.1.1. The 81 TRW Plans and Programs Office, CO, 81 MSG/CC, or OPSEC Coordinator has given prior written approval; or

1.11.5.1.2. The information is otherwise in the public domain before the date of release.

1.11.5.2. Requests for approval shall identify the specific information to be released, the medium to be used, and the purpose for the release. The Contractor shall submit the request to the CO, 81 MSG/CC, or

81 TRW Plans and Programs Office OPSEC Coordinator at least 45 days before the proposed date for release.

1.11.5.3. Subcontractor OPSEC Requirements. The Contractor shall ensure that all OPSEC requirements specified in this PWS, including but not limited to those outlined in prior sections are flowed down to all subcontracts at every tier. This includes the requirement for subcontractors to submit requests for authorization to release information through the prime Contractor to the 81 TRW Plans and Programs

Office, CO, the 81 MSG/CC, or OPSEC Coordinator.

1.12. SMOKING IN AETC FACILITIES: Contractors are advised that the Commander has placed restrictions on the smoking of tobacco products in AETC facilities. AFI 48-104, Tobacco Free Living, 10

Jul 2019, outlines the procedures used by the commander to control smoking in our facilities. Contractors and visitors are subject to the same restrictions as Government personnel. Smoking is permitted only in designated smoking areas.

1.13. HAZARDOUS MATERIALS: If hazardous materials will be used in the execution of this contract, the Contractor shall be required to obtain authorization from the Installation Hazardous Materials

Management Program before ordering or purchasing the hazardous product, IAW AFMAN 32-7002, Environmental Compliance and Pollution Prevention, 3 Feb 20. This authorization process may take up to two weeks, which should be considered in the performance period of this contract.

1.14. SAFETY:

1.14.1. Obligations. Contractors shall comply with the Occupational Safety and Health Act (OSHA, Public Law 91-596) and the resulting standards, OSHA Standards 29 CFR 1910 and 1926. The detailed provisions of the act for accident prevention are directly applicable to all Contractor operations.

Contractors shall comply with applicable DAFMAN 91-203, Air Force Occupational Safety, Fire, and

Health Standards, 24 March 2022. Prime Contractors are also responsible for ensuring any sub-contractors also adhere to OSHA Guidance. OSHA compliance officers visit Contractor worksites on the installation.

1.14.2. Responsibilities. Following is a list of responsibilities for Contracting, Contractor, and Wing Safety personnel.

a. Contractor Responsibilities.

(1) Contractors are responsible for ensuring OSHA and Air Force safety requirements are followed.

(2) Contractors must report all accidents involving Air Force people, property, or equipment damage, and any Contractor personnel injured in the performance of the

Air Force contract to the CO and 81 TRW Plans and Programs Office.

(3) Take immediate corrective action to comply with safety regulations if informed of a violation by the CO or 81 TRW Plans and Programs Office.

b. Contracting Officer (CO) Responsibilities.

(1) Inform Contractor of non-compliance with safety regulations, which may cause injury to Air Force personnel or property.

(2) Notify Wing Safety of any injuries or damage to AF property reported by the

Contractor, in performance of an Air Force contract.

c. Wing Safety Responsibilities.

(1) 81st Training Wing Safety Personnel will periodically monitor Contractor operations to ensure safety regulation compliance as it applies to Air Force personnel and equipment.

(2) Wing Safety personnel are available to the 81 TRW Plans and Programs Office for technical assistance on matters pertaining to accident prevention.

(3) Notify the 81 TRW Plans and Programs Office if a safety procedure or condition exists which requires correction by the Contractor.

1.14.3. Safety Rules. Contractors shall pay particular attention to the following safety rules and ensure strict compliance while on the installation.

a. General Safety Rules While on the Installation.

(1) Traffic Rules While on the Installation. All drivers, mobile equipment, and vehicles must comply with applicable federal, state, and local laws.

(a) Seat belts are mandatory for all passengers as well as drivers.

(b) An approved bicycle helmet is required to be properly worn while riding bicycles on the installation.

(c) Drive the speed limit:

i. Base proper speed limit is 25 mph or as otherwise posted.

ii. Housing area speed limit is 15 mph.

iii. Parking lot speed limit is 5 mph.

(d) Distracted driving. Vehicle operators on Keesler Air Force Base and operators of government-owned vehicles whether on or off the installation will not use cell phones or other portable electronic devices or any device function unless the vehicle is safely parked or unless the driver uses a hands-free device that does not require touching the cell phone or other portable electronic device. Note that using the speakerphone function of a cell phone while holding the device is not considered "hands-free".

(2) Park in designated areas and IAW Keesler AFB Instruction (KAFBI) 31-218, Installation Traffic Code.

(3) Upon encountering troop formations on the installation:

(a) Vehicles must stop when approaching an active marching formation or closer than 50 feet.

(b) It is unlawful to pass a marching formation.

Integrated sUAS Detection and BASH Radar System Services:

2.1. DESCRIPTION OF SERVICES: The Government requires an integrated airspace monitoring capability to mitigate operational risks associated with low-altitude bird activity and unauthorized sUAS operations in and around the airfield. The Contractor shall provide a radar-based or multi-sensor airspace awareness system that operates on a closed-loop, air-gapped, dedicated dark-fiber VLAN architecture to deliver a COP that supports BASH monitoring and detection, tracking, classification, alerting, and monitoring of cooperative and non-cooperative sUAS. The system shall be capable of real-time situational awareness, rapid alerting, historical data playback, and operator decision support.

2.1.1. COVERAGE & DETECTION CAPABILITIES: The Contractor shall provide persistent, 360-degree low-altitude surveillance of the Government defined area of interest (unless sector-based coverage is specifically defined by the Government).

2.1.1.1. ALTITUDE COVERAGE: The Contractor shall provide a system capable of altitude coverage from the surface level to a minimum of 5,000 feet Above Ground Level (AGL).

2.1.1.2. TARGET CAPACITY: The Contractor shall provide a system capable of simultaneous tracking of at least 100 targets without performance degradation or operator lag.

2.1.1.3. sUAS DETECTION: The Contractor shall provide a system capable of detecting and tracking

Group 1 sUAS (multi-rotor) and Group 2 sUAS (fixed-wing) with a Radar Cross Section (RCS) down to

0.01square meters at a minimum range of 3.5 kilometers Line of Site (LOS).

2.1.1.4. BIRD/WILDLIFE DETECTION: The Contractor shall provide a system capable of detecting and tracking individual bird/wildlife targets with an RCS down to 0.003 square meters at a minimum range of 5 kilometers LOS.

2.1.1.5. MULTI-TARGET SEPARATION & SWARM/DENSE TARGET DETECTION: The system shall maintain distinct tracks for multiple airborne targets identified as operating in proximity within the surveillance volume to include dense bird/wildlife activity, multiple sUAS, mixed activity

(biological and non-biological targets), and swarm-like concurrent target conditions.

2.1.1.6. CLUTTER REJECTION: The Contractor shall provide a system that can detect and maintain tracks on qualifying targets despite the presence of ground, buildings/structures, vegetation/tree-line, vehicle or non-target movement, maritime/coastal, and weather clutter.

2.1.1.7. SYSTEM RELIABILITY: The Contractor shall provide a system capable of detecting and tracking at least 95% of qualifying sUAS and bird/wildlife targets present for greater than 5 seconds within the coverage volume.

2.1.2. TARGET CLASSIFICATION & DISCRIMINATION: The Contractor shall provide a system capable of distinguishing biological airborne targets from non-biological targets.

2.1.2.1. CLASSIFICATION CATEGORIES: The Contractor shall provide a system that automatically identifies and classifies targets as Bird, Group 1 sUAS, Group 2 sUAS, or Unknown and the discrimination method used to determine the classification (e.g. signature-based, kinematic, digital signal processing, statistical, or algorithmic).

2.1.2.2. ACCURACY STANDARDS: The Contractor shall provide a system capable of accurately classifying targets as follows:

a. Maintain a false negative rate of less than 1% for qualifying Group 1 and Group 2 sUAS targets.

b. Generate no more than 5 false positive sUAS classifications within any consecutive 8-hour operational period.

2.1.2.3. QUALIFYING TARGET INFORMATION: The system shall provide timestamped event information to include operator-visible range, bearing, altitude, and track history for qualifying targets.

2.1.3. COMMAND & CONTROL (C2) SOFTWARE AND USER INTERFACE: The Contractor shall provide browser-based or locally hosted C2 software that aggregates sensor data into a single, unified

COP.

2.1.3.1. C2 PRIORITIZATION: The Contractor shall provide a system capable of allowing authorized users to configure alert thresholds, surveillance zones, and priority rules. The system shall automatically assign operator-visible priorities and support user-configurable thresholds and surveillance zones.

2.1.3.2. DISPLAY FEATURES: The Contractor shall provide a system capable of real-time display of target altitude, speed, heading, track history, and map-based visualization of the surrounding airspace.

2.1.3.3. ALERTING & GEOFENCING: The Contractor shall provide a system that supports operator-defined 2D and 3D geofenced zones. The system shall be capable of triggering distinct visual and audible alarms when unauthorized targets breach defined zones.

2.1.3.4. RECORDING & PLAYBACK: The Contractor shall provide a system capable of recording, tracking, and alerting on all detections, operator-relevant events, and system status data necessary for historical review and reporting. The system shall be capable of offline historical playback and export capabilities (CSV, PDF, JPEG, KML).

a. The system shall provide historical playback; BASH heat map reporting by day, week, and season;

sUAS incursion logging with time, duration, altitude, and flight path; local storage of radar tracking and alerting data on offline drives.

2.1.4. NETWORK CONFIGURATION & RADIO FREQUENCY (RF) CONSTRAINTS: The

Contractor shall provide a system capable of running exclusively on the close-loop, air-gapped, dedicated dark-fiber VLAN, isolated from the public internet, AFNET, and NIPRNet.

a. Building 6653 (Gator Site, Lat/Lon N 30.4077757 W 88.9324137) is designated as the primary flight line network connection point. The Government will provision dedicated single-mode dark fiber paths connecting this flight line injection point to the central distribution hub and designated display endpoints.

2.1.4.1. ROUTING:

a. Primary Connection Point: Building 6653 (Gator Site, Lat/Lon N 30.4077757 W 88.9324137

b. Central Distribution Node: Building 4223 (Matero Hall)

c. Air Traffic Control (ATC) Endpoint: Building 4223 to Building 4209 (ATC Tower)

d. Security Forces Endpoint: Building 4223 to Building 4225 (BDOC/ECC)

e. Airfield Operations Endpoint: Building 4223 to Building 4217 (OSF)

f. 403d Wing Endpoint: Building 4223 to Building 233 (Base Ops) via transition routing at Building

2801.

2.1.4.2. INTEGRATION HARDWARE: The Contractor shall provide all fiber patch cables (LC/SC), transceivers (SFPs), media converters, and rack-mounting hardware to terminate connections at each facility patch panel. The Contractor shall make a recommendation on the optimal radar sensor location(s) to achieve the required airfield coverage specifications. The 81 TRW Plans and Programs Office has final determination authority for radar sensor locations and installation approval.

a. The Contractor shall provide a formal site survey report/final siting recommendation.

b. The Contractor shall install the radar sensor, mounting hardware, power interfaces, and C2 workstations at the four (4) designated Government facilities (ATC Tower, BDOC/ECC, OSF, Base Ops).

2.1.4.2.1. INTEGRATION & DISPLAY ENDPOINTS: The Contractor shall integrate the radar feed across the dedicated dark-fiber VLAN to provide dedicated, standalone display workstations to include processing units, monitors, peripherals, and C2 software, at the following buildings: 4209 (ATC Tower), 4225 (BDOC/ECC), 4217 (OSF), 233 (403d Wing). The Contractor shall provide the following:

a. System architecture drawings and network topology (CDRL A004);

b. Physical placement and cable run diagrams for the radar and each display location; and

c. An installation and integration plan.

2.1.4.2.2. AIRFIELD SAFETY & OBSTACLE CLEARANCE: The Contractor shall adhere to airfield planning and safety standards outlined in UFC 3-260-01, Airfield and Heliport Planning and Design and

AFMAN 13-204, Airfield Operations.

2.1.4.2.2.1. OBSTACLE CLEARANCE: No installed equipment, radome, mast, or temporary construction equipment (e.g., cranes, lifts, etc.) shall penetrate FAA/airfield imaginary surfaces, primary surfaces, approach/transitional surfaces, or obstacle-free zone (OFZ) without prior written authorization and airspace waiver approval from Airfield Management (81 OSS/OSA) and Wing Safety (81 TRW/SE).

2.1.4.2.2.2. NAVAID PROTECTION: Sensor siting, structural heights, and cable routing shall not infringe upon or degrade the electromagnetic critical zones or LOS operations of existing navigational aids

(including TACAN, instrument landing system/Glidescope, and air traffic control radars).

2.1.4.3. WIRELESS DATA LINKS (IF APPLICABLE): If the Contractor utilizes a wireless link from the sensor to Building 6653, it shall operate within the 868 MHz – 915 MHz band to prevent interference with local Gulf Coast RF congestion. The Contractor shall not utilize the 2.4 GHz and 5.0 GHz ISM bands;

those are prohibited.

2.1.4.4. SPECTRUM CERTIFICATION: The Contractor shall provide emission spectra, operating frequencies, and power levels to the 81 TRW Spectrum Manager and 81 Communication Squadron.

2.1.4.5. AIRFIELD RADAR EMISSIONS: The Contractor shall provide a system that operates within authorized Government/DoW radar bands (e.g., S-band, X-band, etc.) without causing electromagnetic interference (EMI) to airfield navigation aids (ILS, TACAN, Glide Slope) or local communications.

2.1.5. ENVIRONMENTAL & SURVIVABILITY: The Contractor shall ensure the outdoor hardware provided can operate continuously in Gulf Coast maritime/coastal conditions during daylight and night time, to include but not limited to precipitation, humidity, fog, and/or wind-driven clutter. The Contractor shall provide the operating and survivability thresholds for the following conditions: humidity, precipitation, corrosion/salt exposure, lighting/surge environment, and dust/debris exposure.

2.1.5.1. WIND LIMITATIONS: Continuous operation in sustained winds up to 75 miles per hour;

survivability up to 130 miles per hour.

2.1.5.2. ENVIRONMENTAL DEGRADATION: The Contractor shall define operational thresholds and performance impacts related to temperature, humidity, precipitation, corrosion, salt, lighting, and dust.

2.1.6. POWER SUPPLY: The Contractor shall provide and install a sensor-site Uninterruptible Power

Supply (UPS) featuring surge suppression, continuous power conditioning, a minimum of 30 minutes of full-load operational runtime, automatic restart/recovery, and remote status monitoring via the C2 workstation.

2.1.7. DATA MANAGEMENT & CONFIGURATION CONTROL

2.1.7.1. ACCESS, LOGGING, & DATA PROTECTION: The system must support Role-Based Access

Control (RBAC), unique user identification, and administrative audit logging. The Contractor shall provide written guidance for user roles, authentication protocols, and log export processes.

2.1.7.1.1. USER ACCESS AND LOGGING: The Contractor shall identify user roles, authentication approach, account creation and deletion procedures, log content, retention period and export capability.

2.1.7.2. MAINTENANCE, PATCHING, & CONFIGURATION MANAGEMENT: The Contractor shall provide all system software, firmware, and AI/ML target classification model updates on-site. The physical media used for updates shall be inspected by the Government prior to use.

2.1.7.2.1. DATA RETENTION & EXPORT: The Contractor shall identify data retention period for tracks, alerts, logs, and playback records, storage capacity, backup and restore procedures, and export methods and restrictions.

2.1.7.2.2. PATCHING & UPDATES: The Contractor shall provide written guidance for software and firmware updates to include update method, validation method, rollback procedures, and version control method. The Contractor shall include the operational impact resulting from any update.

2.1.7.2.3. CONFIGURATION CONTROL: The Contractor shall maintain configuration control for delivered hardware and software baselines. The Contractor shall provide in writing an inventory of hardware, the software and firmware version list, and the configuration baseline at Final System of

Acceptance (FSA). The Contractor shall notification provide change notification procedures for updates.

2.1.8. COMPATABILITY: The Contractor shall deliver a system that is compatible with Drone Shield

Rf Patrol Mk2 and its software.

2.1.9. TRAINING: The Contractor shall deliver digital training materials and conduct on-site instruction to ten (10) operators. The training shall educate on how to operate the system, interpret alerts, review tracks, manage geofence, generate reports, manage accounts, perform routine maintenance, conduct basic troubleshooting, handle security/system updates, identify system limitations, and inform on user interface functions.

2.2. INTERRUPTION OF SERVICE: The Contractor shall at all times maintain the system in good condition and repair to provide uninterrupted service in conformance with all standards and requirements.

Contractor shall limit to the shortest time possible any interruption of service for the purpose of maintaining, repairing, or upgrading the system. Preplanned interruptions shall be preceded by written notice to the 81 Plans and Programs Office.

2.2.1. TELEPHONE SUPPORT: The Contractor shall be available 24 hours a day/7 days a week/365 days a year and respond within two (2) hours of notification.

2.2.2. CRITICAL OUTAGES: The Contractor shall provide a response within four (4) hours of notification and have a technician on-site within 48 hours for resolution, correction, and return to service.

a. The Contractor shall ship critical replacement components via priority overnight delivery.

2.2.3. ROUTINE/DEGRADED MAINTENANCE: The Contractor shall provide a response within eight

(8) hours of notification and have a technician on-site and/or replacement part arrival within five (5) business days for resolution, correction, and return to service.

2.3. COMPLAINTS: Contractor shall respond to user complaints within five (5) working days. The

Contractor shall maintain written records of all complaints received during the performance of the contract.

Written records shall include the date of complaint, identity of the user, the nature of the complaint, and the contractor’s response.

2.4. WARRANTY: The Contractor shall provide a standard 12-month warranty from FSA covering parts, labor, travel, software, firmware, and repairs.

2.5. PREVENTATIVE MAINTENANCE (PM): The Contractor shall perform semi-annual on-site PM, including radome inspections, mountings, antenna alignment validation, seal integrity checks, UPS load testing, and sensor calibration.

2.6. SERVICE SUMMARY: Contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success. The performance objectives will be measured based on customer feedback, Government surveillance, and Corrective Actions Reports (CAR).

SS Performance Objective

PWS

Section Performance Threshold

Method of

Assessment

1. System Availability

& Airspace Coverage.

Provide continuous, 360-degree radar airspace surveillance for both sUAS and bird/wildlife detection within required altitude and target capacities.

§ 2.1.1.1 through § 2.1.1.7

• Altitude Coverage:

Surface to ≥ 5,000 ft

AGL.

• Target Capacity: ≥

100 targets simultaneously tracked without degradation.

• Reliability: Detects and tracks ≥ 95% of qualifying targets present for > 5 seconds.

• Government Surveillance

(periodic testing)

• Review of system log exports and playback records

2. Target Classification

& Accuracy.

Accurately distinguish and classify biological vs.

non-biological targets.

§ 2.1.2.1 through § 2.1.2.3

• False Negatives: <

1% for qualifying

Group 1 and Group

2 sUAS.

• False Positives: ≤

5 false positive sUAS classifications in any 8-hour operational period.

• System Audit Log

Review

• Random Sampling /

Performance Audits

3. Operational Outage

Resolution. Provide rapid response and resolution for system outages to maintain uninterrupted coverage.

§ 2.2.1 through § 2.2.3

• Telephone

Support: Respond within 2 hours of notification

(24/7/365).

• Critical Outages:

Response within 4 hours; technician on-site within 48 hours for resolution.

• Routine/Degraded:

Response within 8 hours;

resolution/technician on-site within 5 business days.

• Contractor Maintenance

Logs

• User/Customer Feedback

(ATC, BDOC, OSF)

• Corrective Action

Reports (CAR)

4. CDRL Deliverable

Submissions. Submit critical programmatic, safety, network, and installation deliverables on-time.

§ 1.5, § 1.7, § 1.8.1, § 2.1.4.2.1, § 5.0 (CDRLs)

• A001 (Roster):

Within 5 business days of award

(updates within 24 hours).

• A002 (QCP) &

A003 (Safety):

Within 10 business days of award.

• A004 (Topology):

Within 45 calendar days.

• A005 (Site

Survey): Within 30 calendar days.

• All other CDRLs submitted per § 5.0 schedule with 100% timeliness.

• 100% Inspection / COR

Tracking Log

5. OPSEC and Security

Compliance. Maintain absolute network air-gap and protect critical operational information.

Complete mandated training.

§ 1.9, § 1.10, § 1.11

• Zero (0) unauthorized releases of unclassified information.

• Zero (0) connections to

NIPRNet, AFNet, or public internet.

• 100% of personnel complete OPSEC in-processing training within 30 days.

• Security Audits

• Training Records

Verification (DD Form

254 tracking)

• Network Scans

GOVERNMENT PROVIDED PROPERTY:

3.1. GOVERNMENT PROVIDED PROPERTY: None.

3.2. FACILITIES: Any facilities the Contractor shall request for use during the performance of this

PWS shall be requested through the 81 TRW Plans and Programs Office. This PWS makes no provision for facilities located on installation.

DEFINITIONS & ACRONYMS:

4.1. DEFINITIONS:

4.1.1. AFNet. Air Force Network.

4.1.2. AGL. Above Ground Level.

4.1.3. AI/ML. Artificial Intelligence/Machine Learning.

4.1.4. ATC. Air Traffic Control.

4.1.5. BASH. Bird/Wildlife Aircraft Strike Hazard.

4.1.6. BDOC/ECC. Base Defense Operations Center/Emergency Communications Center.

4.1.7. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

4.1.8. C2. Command and Control.

4.1.9. CONTRACTING OFFICER (CO). A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the Government. Note: The only individual who can legally bind the Government.

4.1.10. COP. Common Operating Picture.

4.1.11. DEDICATED DARK-FIBER VIRTUAL LOCAL AREA NETWORK (VLAN). A

Government-coordinated, logically and physically isolated network path used exclusively to support the delivered system and segregated from NIPRNet, AFNet, and the public commercial internet.

4.1.12. EMI. Electromagnetic Interference.

4.1.13. FAA. Federal Aviation Administration.

4.1.14. FALSE NEGATIVE. A failure to detect or correctly classify a qualifying sUAS target under required conditions.

4.1.15. FALSE POSITIVE. A system classification or alert indicating a likely sUAS when the target is not a sUAS.

4.1.16. FSA. Final System Acceptance

4.1.17. ILS. Instrument Landing System.

4.1.18. KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

4.1.19. LC/SC. Lucent Connector/Subscriber Connector.

4.1.20. LOS. Line of Site.

4.1.21. NIPRNet. Non-classified Internet Protocol Router Network.

4.1.22. OFZ. Obstacle Free Zone.

4.1.23. OSF. Operations Support Flight.

4.1.24. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

4.1.25. QUALIFYING TARGET. A bid or sUAS target that meets Government-defined test profile for size, altitude, duration, and flight path.

4.1.26. QUALITY ASSURANCE. The Government procedures to verify that services being performed by the contractor are performed according to acceptable standards.

4.1.27. QUALITY CONTROL PLAN (QCP). All necessary measures taken by the contractor to assure that the quality of an end product or service shall meet contract requirements.

4.1.28. RBAC. Role-Based Access Control.

4.1.29. RCS. Radar Cross Section.

4.1.30. RF. Radio Frequency.

4.1.31. SFP. Small Form-factor Pluggable.

4.1.32. sUAS. Small Unmanned Aircraft System.

4.1.33. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

4.1.34. TACAN. Tactical Air Navigation.

4.1.35. UPS. Uninterruptible Power Supply.

4.1.36. WORK-DAY. The number of hours per day the contractor provides services in accordance with the contract.

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

CONTRACT DATA REQUIREMENTS LIST (CDRL) DELIVERABLES:

5.1. PERSONNEL INFORMATION ROSTER (CDRL A001): Contractor shall provide a primary and alternate personnel to manage and oversee PWS. Names of primary and alternate (who shall act for primary personnel in his/her absence) and telephone numbers where these persons may be contacted before, during, or after normal work hours. The Contractor shall provide the personnel information roster in accordance with paragraph 1.5 no later than five (5) business days after contract award.

5.2. QUALITY CONTROL PLAN (CDRL A002): Contractor shall submit a QCP to the 81

Communications Squadron and CO in accordance with paragraph 1.7. Contractor shall provide the QCP no later than ten (10) business days after contract award.

5.3. SAFETY & HEALTH PLAN (CDRL A003): Contractor shall submit a Safety and Health Plan to the 81 Communications Squadron and CO in accordance with paragraph 1.8.1. Contractor shall provide the

Safety and Health Plan no later than ten (10) business days after contract award.

5.4. SYSTEM ARCHITECTURE DRAWINGS & NETWORK TOPOLOGY (CDRL A004):

Contractor shall provide plans for network configuration and hardware integration of the system to include architecture drawings and network topology in accordance with paragraph 2.1.4.2.1 no later than forty-five (45) calendar days after the contract award date.

5.5. SITE SURVEY REPORT (CDRL A005): Contractor shall make a recommendation on the optimal radar sensor location(s) to achieve the required airfield coverage specifications in accordance with paragraph 2.1.4.2 no later than thirty (30) calendar days after the contract award date.

5.6. INSTALLATION & INTEGRATION PLAN (CDRL A006): Contractor shall provide an installation and integration plan in accordance with paragraph 2.1.4.2.1 no later than fifteen (15) calendar days after the Government approves the site survey report.

5.7. DIGITAL/WRITTEN GUIDANCE (TRAINING) (CDRL A007): Contractor shall provide written guidance for data management and configuration controls in accordance with paragraphs 2.1.7.1 and 2.1.7.2.2 in addition to digital training materials in accordance with paragraph 2.1.8 no later than fifteen (15) calendar days prior to scheduled training.

5.8. SOFTWARE & FIRMWARE BASELINE LIST (CDRL A008): Contractor shall provide in writing, a draft version at installation and a final version upon FSA, the software and firmware version list, and the configuration baseline in accordance with paragraph 2.1.7.2.3.

5.9. HARDWARE INVENTORY (CDRL A009): Contractor shall provide in writing, a draft version at installation and a final version upon FSA, an inventory of hardware in accordance with paragraph

2.1.7.2.3.

CDRL Description Frequency

A001 Personnel Information Roster Initial, as needed

A002 Quality Control Plan Once

A003 Safety & Health Plan Once

A004 System Architecture Drawings and Network Topology Initial, 45

Calendar Days

After Contract

Award

A005 Site Survey Report Initial, 30

Calendar Days

After Contract

Award

A006 Installation & Integration Plan Initial, 15

Calendar Days

After Site

Approval

A007 Digital/Written Guidance (Training) Initial, 15

Calendar Days

Before Training

A008 Software and Firmware Baseline List Initial Draft at

Hardware

Installation;

Final list at FSA

A009 Hardware Inventory Initial upon delivery; Final list at FSA