PWS Drone Detection v 2.0.pdf

CUI FA701425Q0042 Page 1 of 10

CUI

Controlled by: AFDW/PK CUI Categories: PROCURE Distribution/Dissemination Controls:

FEDCON AFTER AWARD

POC: CO Shannon Weston

PERFORMANCE WORK STATEMENT

FOR

Drone Detection v 2.0

AT

JOINT BASE ANDREWS, MARYLAND

and

JOINT BASE ANACOSTIA-BOLLING

26 August 2025

CUI FA701425Q0042

Contents

SECTION I

1.0 Description Of Services

1.1 General

1.2 Background

SECTION II

2.0 Task Descriptions

2.1 Task 1 Deploy Cloud – Based Detection Capability

2.2 Task 2 Detection & Geolocation

2.3 Task 3 Integration & Alerting

2.4 Task 4 System Monitoring & Support

SECTION III

3.0 Service Summary

SECTION IV

4.0 Deliverables

SECTION V

5.0 Government Furnished Property, Equipment, Material, Information, Or Services

SECTION VI

6.0 General Information

6.1 Hours of Operation

6.2 Security Requirements

6.3 Period of Performance

6.4 Transition Plan

6.5 Quality Control

6.6 Kick Off Meeting

6.7 Emergency Operations\Mission Personnel

SECTION VII

7.0 System for Award Management (formerly CMRA)

SECTION VIII

8.0 Security Instructions

SECTION IX

9.0 Contractor Professionalism

SECTION X

10.0 Miscellaneous Paragraphs

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General. The Air Force District of Washington (AFDW) requires a commercially available, subscription-based Counter-Unmanned Aircraft System (C-UAS) detection and alerting service.

This contract supports persistent air domain awareness for Joint Base Andrews (JBA) and Joint Base Anacostia-Bolling (JBAB) through a Contractor-owned, Contractor-operated (COCO) solution. The system must detect, track, identify, and report unauthorized unmanned aerial systems (UAS) operating within and around installation airspace.

1.1.1 Scope. The scope of this requirement is to provide a commercially available, contractor-owned and operated, subscription-based Counter-Unmanned Aircraft System (C-UAS) detection and alerting solution to support Joint Base Andrews (JBA) and Joint Base Anacostia-Bolling (JBAB). The system shall provide persistent air domain awareness through remote sensing, telemetry decoding, and pilot geolocation, with real-time data accessible to government users via a secure web and mobile dashboard.

1.1.2 The Contractor shall deploy a turnkey solution that does not require government-owned infrastructure, personnel maintenance, or hardware installation.

1.1.3 The solution must:

• Detect and track Group 1–2 UAS within a range of 3–5 km in urban environments and 10–15 km in rural environments with ≥95% accuracy through Red Air testing annually.

• Provide real-time telemetry and pilot geolocation data.

• Integrate with government command-and-control (C2) systems, including ATAK.

• Support 24/7 monitoring access from computer, phone, or tablet.

1.2 Background. AFDW identified critical gaps in airspace monitoring after multiple unauthorized drone incursions. Existing detection solutions are hardware-dependent, costly, and difficult to maintain. This Subscription-as-a-Service (SaaS)-based approach leverages passive RF technologies, telemetry decoding, and secure cloud architecture to deliver an agile and scalable solution without requiring government infrastructure.

SECTION II

2.0 TASK DESCRIPTIONS

2.1 Task 1 – Deploy Cloud --- Based Detection Capability

- Provide a web-accessible, cloud-hosted system with no on-premises hardware.

- Accessible via secure login from computer, mobile phone, or tablet.

- System must be operational within 30 calendar days of contract award.

2.2 Task 2 – Detection & Geolocation

- Provide >95% detection rate for Class I/II UAS (up to 55 lbs) in urban (3–5 km) and rural (10– 15 km) environments.

- Support real-time and immediate telemetry decoding and pilot/operator geolocation.

2.3 Task 3 – Integration & Alerting

- Support ATAK plugin integration and compatibility with AFDW C2

(MEDUSA) platforms within 90 days.

- Enable geofencing, custom alerts, and full data export functionality.

2.4 Task 4 – System Monitoring & Support

- Provide 24/7 remote access and monitoring dashboards.

- Contractor shall provide onboarding, user training, and 24/7 online virtual help desk support.

- Detections (frequency, telemetry, Remote ID or Serial Numbers, etc.)

SECTION III

3.0 SERVICE SUMMARY

aluate under

The table below summarizes key performance objectives and how the Government will ev compliance. These standards ensure mission effectiveness while supporting accountability a subscription-based service model.

Performance Objective

PWS Reference Performance Threshold

Surveillance Method

System Deployment

2.1 Operational

within 90 days of award

COR validation

Detection Rate 2.2 Monthly performance report i

≥95% detection rate in urban/rural zones

Telemetry & Geolocation

2.2 ≥95% telemetry/pilot location data availability

Red Air Testing annually

ATAK/C2

Compatibility

2.3 100% integration with government platforms

Functional review

24/7 Monitoring Access

2.4 System accessible

from web/mobile 24/7

Government access testing

User Support 2.4 Response within 24 hours; >90% user

Monthly support log review

SECTION IV

4.0 DELIVERABLES

The Contractor shall provide deliverable(s) in a format mutually agreed upon by the Government and the Contractor.

The following enumerated deliverables are not expected to change. Due Date intervals are not expected to change but actual dates may need to be revised depending on actual contract start date.

DELIVERABLE PWS

PARA

DUE DATE DELIVERY

Monthly Detection Report

2.2 10th business day of each month

By email to the COR in Microsoft Word format

User Support Log 2.4 10th business day of each month

By email to the COR in Microsoft Word format

Incident Log 2.4 within 2 business days of request

By email to the COR in Microsoft Word format

Training and Onboarding Guide

2.4 prior to initial operating capability

By email to the COR in Microsoft Word format

Geofencing/Alert Configuration File

2.4 upon deployment and update

By email to the COR in Microsoft Word format

Kick-off Meeting Agenda

2.6 Submitted at Kickoff

Meeting

By email to the COR in Microsoft Word format

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL,

INFORMATION, OR SERVICES

5.1 No government-furnished equipment, property, information, or facilities will be provided.

The Contractor is responsible for all necessary infrastructure, including data collection nodes, cloud platforms, and end-user access interfaces.

SECTION VI

6.0 GENERAL INFORMATION

6.1 Hours of Operation. The system must be operational 24/7. Contractor support should be available Monday–Friday 0800–1700 EST, with emergency support after hours.

6.2 Security Requirements. The system must comply with FedRAMP High or DoD-authorized equivalent cloud security standards. All access must be role-based and encrypted.

6.3 Period of Performance. The PoP includes one (1) base year and four (4) one-year option periods.

6.4 Transition Plan. A Transition-In plan is required at kickoff. A Transition-Out plan is due 90 days before contract expiration.

6.5 Quality Control. The Contractor shall maintain a quality assurance plan to ensure consistent service delivery, address issues, and support government oversight.

6.5.1. Quality Assurance. The Government shall rely on the Contractors’ existing quality assurance system as the method to ensure that the requirements of the contract and performance thresholds are met; however, the Government reserves the right to monitor and evaluate the quality of services provided and compliance with the contract terms and conditions at any time.

6.5.2. Quality Control Plan (QCP). The Contractor shall develop and maintain an effective quality control program to ensure services are performed IAW this PWS, applicable laws and regulations, and best commercial practices. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services with special emphasis placed on those services listed in this PWS. The Contractor’s quality control program is how it assures itself that the work complies with the requirement of the contract.

6.6 Kickoff Meeting

6.6.1 The Kickoff Meeting location will be held at the Government's facility and the date and time will be mutually agreed upon by both parties.

6.6.2 The Contractor shall schedule and coordinate a Project kick-off Meeting no later than (NLT) five (5) calendar days after contract award at the location approved by the Government.

The meeting will provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The meeting will provide the opportunity to discuss technical, management, and logistic issues; travel authorization; communication process between Government and Contractor; and reporting procedures. At a minimum, the attendees shall include key Contractor personnel, OFFICE (SAF/# or AF/#), key Government representatives, and the COR. The Contractor shall provide a Kick-Off Meeting Agenda that will include, but not be limited to, the following.

• Introduction of personnel

• Overview of project tasks

• Review of organization (complexity)

• Schedule (shows major tasks, milestones, and deliverables; planned and actual start and completion dates for each)

• Communication Plan/lines of communication overview (between both Contractor and Government)

• Discussion of draft Program Management Plan (PMP) (If this is requested, please include in Section II and in your deliverables table)

• Travel notification and processes

• Government-furnished information (GFI) (Items that may not be included in Section V)

• Security requirements (Building access, badges, Common Access Cards (CAC))

• Analytical Support Status Accreditation (ASSA) Documentation

• Invoice procedures

• Monthly meeting dates

• Reporting Requirements, e.g. Monthly Status Report (MSR)

• POCs

• Roles and Responsibilities

• Overview of incoming Transition Plan to include process, timeframes, and status

• Prioritization of Contractor activities

• Any initial deliverables

• Other logistic issues

• Quality Control Plan (QCP)

• Sensitivity and protection of information

• Additional issues of concern (Leave/back-up support)

6.6.3 The Contractor shall provide a draft copy of the agenda NLT 3 days after contract award for review and approval by the COR prior to finalizing. The Government will provide the Contractor with the number of participants for the kick-off meeting and the Contractor shall provide sufficient copies of the presentation for all present.

6.7 Emergency Operations/Mission Essential Personnel.

6.7.1. Continuation of Essential Contractor Services During Crisis. All services in this PWS HAVE NOT been defined or designated as essential services for performance during crisis IAW DFARs 252.237-7023, “Continuation of Essential Contractor Services.”

SECTION VII

7.0 SYSTEM FOR AWARD MANAGEMENT (FORMERLY CMRA)

7.1. The Contractor shall report ALL labor hours (including subcontractor labor hours) required for performance of services provided under this contract via the System for Award Management (SAM) data collection site. The Contractor is required to completely fill in all required data fields at http://www.SAM.gov. Reporting inputs shall be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. The UIC for AFDW is FF16M0. While inputs may be reported anytime during the FY, all data shall be reported not later than 31 October of each calendar year. The Contractor may direct questions to the System for Award Management help desk.

7.2. Subcontractor Input in SAM. Prime Contractors are responsible to ensure all subcontractor data is reported. Subcontractors will not be able to enter any data into SAM, but will enter their information into a Bulk Loader spreadsheet available from the SAM helpdesk. Subcontractor shall fill in columns A-C then return it to the SAM helpdesk after it's completed and a technician team will enter the information into SAM.

http://www.sam.gov/

SECTION VIII

8.0 SECURITY INSTRUCTIONS

8.1 Physical Security. The Contractor shall safeguard all Government property, documents and controlled forms provided for Contractor use and adhere to the Government property requirements contained in this contract. At the end of each work day, all Government facilities, equipment, and materials shall be secured by a Government POC. Contractors are not allowed to secure Government facilities, equipment, and materials.

8.2 Access Control. The Contractor shall establish and implement methods of ensuring that no building access instruments issued by the Government are lost, misplaced or used by unauthorized persons. Access codes shall not be shared with any person(s) outside the organization. The Contractor shall control access to all Government provided lock combinations to preclude unauthorized entry. The Contractor is not authorized to record lock combinations without written approval by the Government COR. Records with written combinations to authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the approved containers.

8.3 Pass and Identification Items. The Contractor shall ensure the pass and identification items required for contract performance are obtained for employees and non-government owned vehicles.

8.4 Retrieving Identification Media. The Contractor shall retrieve all identification media, including vehicle passes, from employees who depart for any reason before the contract expires.

8.5 Traffic Laws. The Contractor and its employees shall comply with base traffic regulations.

8.6 Weapons, Firearms, and Ammunition. Contractor employees are prohibited from possessing weapons, firearms, or ammunition, on themselves or within their Contractor-owned vehicle or privately-owned vehicle while on Joint Base Anacostia-Bolling and/or Joint Base Andrews any other military facility.

8.7 Communications Security (COMSEC). Contractors may require access to COMSEC information on Air Force installations. The Contractor shall not require a COMSEC account.

Access shall be controlled by the sponsoring agency. Access to COMSEC material by personnel is restricted to US citizens holding final US Government clearances. Such information is not releasable to personnel holding only reciprocal clearances. If it is determined the Contractor is required to access COMSEC information, the necessary training information and courses shall be provided by the COR. The DD Form 254 shall give further instructions on safeguarding and managing COMSEC material.

8.8 Contractor Identification. All Contractor personnel shall wear the Air Force issued Common Access Card at all times when away from their immediate work area so as to distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, Contractor personnel shall identify themselves as a contractor to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, contractors occupying collocated space with their government program customer should identify their work space area with their name and company affiliation or as a minimum “Contractor” after name.

8.9 Drug, Tobacco, and Alcohol Use Policy. The consumption of alcoholic beverages or illegal drugs by contractor personnel, while on duty, is strictly forbidden. Contractor shall immediately remove any employee who is under the influence of alcohol or drugs.

SECTION IX

9.0 CONTRACTOR PROFESSIONALISM

The contractor shall:

• Present a professional appearance and maintain professional demeanor and conduct at all times.

• Conduct their work assignments IAW project schedules

• Function effectively and efficiently during extended periods of high pressure and stress.

• Function as an integral member of a team of highly trained professionals responsible for the safety and security of USAF personnel and resources.

SECTION X

10.0 MISCELLANEOUS PARAGRAPHS

10.1 Freedom of Information Act (FOIA). All official Government records affected by this contract are subject to the provisions of the FOIA (5 U.S.C. 552/DoD 5400.7-R/AF Supplement).

Any request received by the Contractor for access/release of information from these records to the public (including Government/Contractor employees acting as private citizens), whether oral or in writing, shall be immediately brought to the attention of the CO for forwarding to the AFDW FOIA Manager to ensure proper processing and compliance with the Act.

10.2 Controlled Unclassified Information (CUI). All DoD CUI must be controlled until authorized for public release in accordance with DoD Instructions (DoDIs) 5230.09, 5230.29, and 5400.04, or DoD Manual (DoDM) 5400.07. These regulations set policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding of CUI material.

10.3 Privacy Act. Working on this contract may require that personnel have access to information protected by the Privacy Act. Contractor personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations when handling such information.

10.4 Records. All records created and received by the Contractor in the performance of this contract shall be maintained and readily accessible. Records shall remain the property of the Government.

10.5 Safety Concerns. The Contractor is solely responsible for compliance with OSHA standards for the protection of their employees. The Government is not responsible for ensuring that Contractors comply with “personal” safety requirements that do not present the potential to damage Government resources.

10.6 Project Policy. The Contractor shall comply with all industry standards. All work shall be done in accordance with all federal, local, and state laws and regulations.

10.7 Inherently Governmental Functions. The Contractor shall not perform inherently Governmental functions as defined in the Federal Acquisition Regulation (FAR) Subpart 7.5 in relation to this PWS.

10.8 Ethics. The Contractor shall not employ any person who is an employee of the US Government if employing that person would create a conflict of interest. Additionally, the Contractor shall not employ any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives approval according to DoDD 5500-7, Joint Ethics Regulation.

10.9 Professional Appearance of Workspace. The Contractor shall keep workspace areas neat and orderly and avoid conditions leading to safety violations.

10.10 Non-Personal Services. The Government shall not supervise or task Contractor employees in any manner that generates actions of the nature of personal services, or that creates the perception of personal services. It is the responsibility of the Contractor to manage its employees directly and to guard against any actions that are of the nature of personal services or give the perception of personal services to the Government or to Government personnel. If the Contractor feels that any actions constitute, or are perceived to constitute personal services, it is the Contractor’s responsibility to notify the CO immediately. Non-personal Contractor services shall not be used to perform work of a policy/decision making or management nature.