RFP 70RDA226R00000001 FINAL.pdf

RFP No. 70RDA226R00000001

FEDERAL ACQUISITION REGULATION (FAR) Subpart 12.6

COMBINED SYNOPSIS/SOLICITATION NOTICE

In accordance with (IAW) Federal Acquisition Regulation (FAR) subpart 12.603, Streamlined Solicitation for Commercial Items, Combined Synopsis/Solicitation Procedures, shall be utilized in support of the subject solicitation. As such the following synopsis information as required by FAR subpart 5.207 Preparation and transmittal of synopses is hereby provided to include detail required by aforementioned FAR subpart 12.603.

(1) Action Code: Not Applicable

(2) Date: November 21

(3) Year: 2025

(4) Contracting Office ZIP Code: 20528-0115

(5) North American Industry Classification Track 1 - Hardware/Software and Ancillary Services: 541519 footnote18, IT Value Added Reseller

Track 2 - Comprehensive Services 541512 Computer Systems Design Services

(6) Product or Service Code: Track 1: 7D20, Track 2: DJ10

(7) Contracting Office Address: U.S. Dept. of Homeland Security Office of Procurement Operations 245 Murray Lane, SW, Mailstop 0115 Washington DC 20528-0115

(8) Subject: Department of Homeland Security (DHS), Counter-Unmanned Aircraft Systems (C-UAS)

(9) Proposed Solicitation Number: 70RDA226R00000001

(10) Closing Response Date: December 8, 2025

(11) Contact Point or Contracting Officer: Leslie Kenser Email: Leslie.Kenser@hq.dhs.gov

Charnelle Brown Email: Charnelle.Brown@hq.dhs.gov

(12) Contract Award and Solicitation Number: Solicitation Number: 70RDA226R00000001 Award Number: TBD

(13) Contract Award Dollar Amount: $1,500,000,000.00

(14) Line Item Number: See Pricing Schedules, Attachment J-1 and J-2

(15) Contract Award Date: See Section F.2 IDIQ Ordering Periods

(16) Contractor: TBD – Multiple Awards Shall Be Made

(17) Description: This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in FAR subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation is hereby issued as a part of this notice.

Solicitation 70RDA226R00000001 is issued as a Request for Proposal (RFP) where FAR clauses and provisions 52.212-1, 52.212-3, 52.212-4 and 52.212-5 apply. FAR 52.212-2 does not apply to this acquisition. This RFP and incorporated provisions and clauses are those in effect through Federal Acquisition

Circular 2025-05.

(18) Place of Contract Performance: The place of performance is represented within solicitation document reference Section F.4.

(19) Set-aside Status: Solicitation 70RDA226R00000001 is being released as full and open.

(End of Synopsis/Solicitation Cover)

U.S. Department of Homeland Security

Counter-Unmanned Aircraft Systems (C-UAS)

Request for Proposal

70RDA226R00000001

November 21, 2025 Department of Homeland Security Office of Procurement Operations

Part I – The Schedule

SECTION A – STANDARD FORM (SF) 1449

The Official SF-1449 Form is attached in this document as a PDF Attachment.

The SF-1449 must be completed as described in Section L.4.1.

(End of Section A)

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 General Description

The solicitation, evaluation and award procedures for the requirements contained herein will be conducted using the procedures and policies in Federal Acquisition Regulation (FAR) Part 12 Acquisition of Commercial Products and Commercial Services. Where necessary, the procedures in FAR Part 15 Contracting by Negotiation apply. However, if the policies in FAR Part 15 are inconsistent with Part 12, the language in FAR Part 12 takes precedence.

This Multiple-Award Indefinite-Delivery, Indefinite-Quantity (IDIQ) contract is established to provide the Department of Homeland Security (DHS) and its Components with Counter- Unmanned Aircraft Systems (C-UAS) capabilities to address evolving threats posed by unauthorized or malicious unmanned aircraft systems (UAS). All DHS Components are authorized ordering activities.

The Government will order any products/services to be furnished under this IDIQ contract by issuing Orders from the effective date of the IDIQ contract through the expiration date of the IDIQ contract. Orders will be within the scope, issued within the IDIQ ordering period, and be within the maximum value of the IDIQ contract. The Ordering Contracting Officer shall ensure that the products/services are in scope of the IDIQ contract and consult with the IDIQ Contracting Officer/Contracting Officer’s Representative, if needed.

B.2 Contract Minimum Guarantee and Maximum Ceiling

(a) Minimum. The minimum guaranteed award amount for this IDIQ contract is $250.00 per

Contractor during the base period of this contract. Orders beyond this minimum will be determined by Department-wide needs. The guaranteed minimum covers the entirety of the contract (including the base and any exercised options). The exercise of an option does not re-establish the contract minimum for the IDIQ contracts.

(b) Maximum. The total value of ALL orders awarded under ALL contracts issued under this solicitation, including orders issued in option periods and minimum contract amounts, shall not exceed $1,500,000,000.00.

(c) Total Estimated Ceiling Amount by Track:

Track 1 - Hardware/Software and Ancillary Services: $1,011,000,000.00 Track 2 - Comprehensive Services: $489,000,000.00

(d) The Government has no obligation to issue orders to the Contractor beyond the amount specified in paragraph (a) of this section. Once the conditions of paragraph (a) have been met, the Contractor will continue to have the opportunity to be issued orders. An unlimited number of orders may be awarded under the IDIQ contract throughout the ordering period, including options, if exercised.

B.3 Contract Type

(a) This is an IDIQ Contract which will permit Firm-Fixed-Price (FFP), Labor-Hour (LH), and Time-and-Materials (T&M) orders, or any combination thereof in accordance with Federal Acquisition Regulation (FAR) Part Subpart 16.5 “Indefinite-Delivery Contracts” and as set forth in Section G “Contract Administration Data” and Section I “Contract Clauses.”

(b) The Contractor exceeds the total obligated funding and order ceiling prices of LH and T&M Contract Line-Item Numbers (CLINs) at its own risk. The Contractor shall notify the Order Contracting Officer (OCO) and Order Contracting Officer’s Representative (COR) in writing upon reaching 75% of the obligated funding and order ceiling prices.

(c) To be considered for award of an order inclusive of LH or T&M CLINs, Offerors shall submit documentation to the IDIQ CO demonstrating that it has and maintains an adequate accounting system that will permit timely development of all necessary cost data in the form required by the proposed contract type. The Offeror shall submit sufficient information it determines relevant to substantiate it has an adequate accounting system, such as a copy of the written determination of an adequate accounting system from the cognizant federal agency official (CFAO) or Certified Public Accountant (CPA). Contractors not providing this proof may be found ineligible for LH or T&M order award. A contractor’s self-certification of an appropriate accounting system is not acceptable. If requested, the offeror will provide sufficient accounting system information to allow a pre-award accounting system review for adequacy.

B.4 Tracks

The two Tracks under this vehicle include (1) Hardware/Software and Ancillary Services and (2) Comprehensive Services as defined in Section C. Statement of Work.

When responding to an Order Request for Proposal (ORP) under task order solicitations, the Contractor shall identify both Prime and Subcontractor labor using the C-UAS IDIQ Labor Categories. Prices proposed in response to an ORP shall not exceed the ceiling rates, as incorporated into Section C of this contract, for any services performed CONUS. Rates for services performed OCONUS will be established as needed at the task order level. IDIQ ceiling rates for labor categories in the Attachment J-2 – Track 2 Pricing Schedule identified as covered by the Service Contract Act may be exceeded where the prevailing wage rate for those categories at the time of order exceeds the prevailing rates used to establish the ceiling rate. The official closure date of the RFP that established this contract shall be the date used to determine the prevailing wage used to create the ceiling rates. The OCO will have the discretion to determine the appropriate wage rate based on the scope of the Task Order.

B.5 Ancillary Services

Ancillary services are defined as services which directly support a product-based requirement under the scope of Track 1.

When the predominant proportion of the requirement, expressed in terms of estimated order value, is for Hardware/Software and Ancillary Services, the requirement shall be solicited under

Track 1. When the predominant proportion of the requirement, expressed in terms of estimated order value, is for C-UAS as a Service, System Integration, and/or Research and Development (R&D) and Test and Evaluation (T&E) Support, the requirement shall be solicited under Track 2.

The Contractor should propose and identify each ancillary support requirement separately and shall be identified by a separate CLIN on the order award.

B.6 Specialized Professional Services Labor

Specialized professional services labor is defined as bona fide executive, administrative, or professional skills for which the expertise required or duties performed are within the scope of C-UAS, but are so specialized that they are not explicitly defined in any labor category description in Attachment J-3 - C-UAS IDIQ Labor Categories.

The Contractor may propose specialized professional services labor when proposing ancillary support or Task Order Unique Labor Categories, as defined below, if determined appropriate by the OCO. Task Order Unique Labor Categories are those categories not incorporated into the Contractor’s IDIQ contract. Task Order Unique Labor Categories and rates shall be negotiated and approved in writing by the OCO prior to the award of the Order or Order modification.

Labor categories and rates approved under a single order, but not specified in the Contractor’s IDIQ contract, shall apply to that specific order only.

B.7 Labor Subject to the Service Contract Labor Standards

(a) The orders under this contract may require work subject to 41 USC 67, Service Contract Labor Standards (formerly known as the Service Contract Act), at any locality in the United States. The orders may also require work within the United States not subject to the Act, as well as work outside the United States.

(b) This contract incorporates a wage determination for San Francisco, California. The contract’s ceiling prices accommodate this wage determination.

(c) Any order under this contract requiring work subject to Service Contract Labor Standards will include a wage determination for the work locality. In the unlikely event that an order’s wage determination requires the contractor to pay wages or furnish fringe benefits in excess of those in the San Francisco wage determination, that order’s rates may exceed the contract’s ceiling prices, for the applicable labor category.

B.8 Post Award Equipment and Labor Pricing

At the Ordering Contracting Officer’s (OCO’s) discretion, alternate equipment and labor categories that are within the scope of the IDIQ SOW requirements may also be added at the order level, without any need for approval from the C-UAS Contracting Officer. Prices for equipment and/or labor rates included in orders, whether or not the equipment and/or labor categories are included in the Pricing Schedule shall be established through the orders competition process. Labor rates for any labor categories identical to those in Attachment J-2 - Track 2 Pricing Schedule, shall not exceed the established ceiling rates.

B.9 Time-and-Materials (T&M) and Labor-Hour (L-H) Orders

T&M and L-H orders are subject to the definitions prescribed in FAR Sections 16.601 and 16.602, respectively, and any component-specific supplements.

All labor categories identified in Attachment J-2 - Track 2 Pricing Schedule are considered bona fide executive, administrative, and professional labor that are exempt from the Fair Labor Standards Act.

To the extent that any ancillary labor for services are within the scope of this IDIQ contract and subject to the Fair Labor Standards Act, in accordance with FAR Subpart 22.10 and any component-specific supplements, the OCO shall identify such work in the order solicitation and make a determination as to whether wage determinations are to be applied or not. For all additional labor categories and labor rates not established at the IDIQ level, OCOs shall determine those proposed labor categories are within scope and the proposed labor rate(s) fair and reasonable prior to order award.

This IDIQ contract does not include any provisions or clauses applicable to any Fair Labor Standards Act work that is part of a total solution within the scope of the IDIQ contract. The OCO shall incorporate the appropriate provisions and clauses in each order solicitation and subsequent award when the Fair Labor Standards Act applies.

B.10 Materials

Materials may be included at the order level in accordance with FAR 52.212-4(e)(1)(iii) ALT I (NOV 2021). OCOs shall determine the price(s) to be fair and reasonable and cost(s) to be allowable, allocable, and reasonable prior to order award.

B.11 Other Direct Costs (ODCs)

Requirements at the order level may include Other Direct Costs (ODCs) that are not explicitly named and priced within Attachment J-2 - Track 2 Pricing Schedule, which shall become the awarded C-UAS IDIQ Contract’s Section B. CLIN schedule. All ODCs required by the Government will be reimbursed to the Contractor in accordance with FAR 52.212-4 – ALT I (i)(1)(ii)(D)(1), when (a) the order listed each element of ODCs, and (b) the Contractor obtained Order-level COR approval (e-mail is acceptable) for all ODCs in advance of purchases. The Contractor shall be responsible for ensuring (a) and (b) above.

All requests to purchase ODCs via the ODC CLIN must be coordinated with the OCO to ensure all ODC CLIN requirements are within scope of the IDIQ contract, within the not-to-exceed (NTE) CLIN ceiling value, for performance of only those solutions secured under orders awarded against the IDIQ contract, offered at a fair and reasonable price.

B.12 Travel

Travel costs may be included at the order level. All travel required by the Government outside the local commuting area(s) will be reimbursed to the Contractor in accordance with the Federal Travel Regulations (FTR). Travel costs may be firm-fixed price or reimbursed at actual cost in accordance with the limitations set forth in FAR 31.205-46 and any component-specific supplements. OCOs shall determine all travel costs fair, reasonable, and allowable prior to the Contractor incurring and expensing any travel costs to the Government.

Unless otherwise directed by the order’s terms and conditions, the Contractor may apply indirect costs to travel consistent with the Contractor’s standard accounting practices. The Contractor shall be responsible for obtaining Order-level COR approval (e-mail is acceptable) for all reimbursable travel in advance of each travel event. Specific travel requirements will be indicated at the Order level.

The Contractor shall use the federal lodging and per diem allowances in accordance with FAR 31.205-46 and the applicable FTR governing the travel performed directly referable to this contract. The Government will not reimburse transportation costs in excess of coach class commercially scheduled air or ground transportation by the most expeditious route.

B.13 Subcontracting

Subcontracting shall follow the procedures set forth in FAR Part 12, Acquisition of Commercial Products and Commercial Services, and other applicable component-specific regulatory supplements.

B.14 Schedule of Supplies/Services

B.14.1 Schedule of Supplies/Services

Track 1 Pricing: Attachment J-1 - Track 1 Pricing Schedule

Track 1 requirements at the Order level shall include Commercial Off the Shelf (COTS) Hardware/Software and/or Ancillary Services. All Track 1 Hardware/Software, and Ancillary Services requirements must be within scope of the IDIQ and offered at a fair and reasonable price. In providing fair and reasonable prices for COTS hardware/software and ancillary services, the Contractor shall utilize its represented published pricing list. The Contractor shall provide a detailed description of the fair and reasonable nature of the proposed catalog item and/or service and its unit price. This detailed description shall include for example, clear references to already determined fair and reasonable unit prices available on offerings such as the Federal Supply Schedule, or other published price list for the same COTS hardware/software and ancillary services. The discounts contained in Attachment J-1 Pricing Schedule will be applied to the documented published unit price to determine Task Order level price for that specific catalog CLIN. Contractors are encouraged to offer additional discounts beyond the discount matrix found in Attachment J-1, Pricing Schedule. OCOs shall determine the price(s) to be fair and reasonable and cost(s) to be allowable, allocable, and reasonable prior to order award.

Track 2 Pricing: Attachment J-2 - Track 2 Pricing Schedule

All CLIN prices described in the Pricing Schedule, Attachment J-2 – Track 2 Pricing Schedule reflect the fully-burdened rates for each CLIN. The fully-burdened prices include all direct, indirect, general and administrative costs and profit associated with providing the required performance at Government and Contractor sites.

Services shall be provided in accordance with the labor categories defined in Attachment J-3 - C- UAS IDIQ Labor Categories (except for ancillary labor as defined under Section B.5 and when using Task Order Unique Labor Categories as defined in Section B.6). All labor categories must meet or exceed the labor category descriptions and educational/experience requirements provided in the Attachment J-3 - C-UAS IDIQ Labor Categories.

The Contractor is not precluded from offering discounts from the prices found in the Pricing Schedule, Attachment J-2 – Track 2 Pricing Schedule when preparing its proposals in response to Task Order Requests for Proposal. Proposed rates for Task Orders shall not exceed the rates established in the IDIQ contract.

B.14.2 IDIQ Ceiling Prices/Rates

(Reserved for award)

(End of Section B)

SECTION C - STATEMENT OF WORK

Department of Homeland Security Counter-Unmanned Aircraft System (C-UAS)

Statement of Work (SOW)

Counter-Unmanned Aircraft System (C-UAS)

Statement of Work (SOW)

GENERAL

1.1 Background

The Department of Homeland Security (DHS) requires Counter-Unmanned Aircraft Systems (C- UAS) solutions to address the growing threats posed by unauthorized or malicious unmanned aircraft systems (UAS). These systems must support the detection, tracking, locating, classification, identification, and mitigation of UAS threats across diverse operational environments. This procurement will enable DHS components to acquire adaptable C-UAS capabilities tailored to their unique mission requirements, ensuring the protection of critical infrastructure, public safety, and national security.

As part of its mission, DHS is responsible for securing National Special Security Events (NSSE) and Special Event Assessment Rating (SEAR) events, which include high-profile gatherings such as presidential inaugurations, major sporting events, and other large-scale public events.

These events often require specialized airspace security measures to address UAS threats and ensure the safety of attendees, critical infrastructure, and surrounding communities. C-UAS solutions procured under this effort will play a vital role in supporting DHS’s ability to secure these events and respond to evolving threats.

1.2 Scope

This contract will provide DHS with access to a variety of C-UAS solutions in the form of hardware, software, or services that support a variety of operational use cases, system types, and capabilities. This contract will remain current with available market solutions and provide a full range of C-UAS solutions throughout its life. The following C-UAS use cases are expected:

Fixed Location Security: Continuous airspace awareness and response capabilities for permanent installations, such as airports, government facilities, and critical infrastructure.

o Aviation Environments: Systems capable of operating in aviation environments, such as airports, airfields, or areas with high-density air traffic, where airspace safety and compliance with aviation regulations are critical.

o Maritime Environments: Systems capable of operating in maritime environments, such as ports and coastal areas, where environmental factors (e.g., saltwater exposure, high humidity) and maritime operational needs are key considerations.

Mobile Response: Portable, rapidly deployable systems or services capable of operating in dynamic, geographically dispersed, or roaming environments. This can include handheld, backpack, trailer, vehicle, maritime or airborne mounted solutions.

o Aviation-Based Operations: Systems capable of being deployed on aircraft to support airborne operations, such as patrolling borders, monitoring large areas, or supporting disaster response from the air.

o Maritime Environments: Systems capable of operating in maritime environments, such as aboard vessels, where environmental factors (e.g., saltwater exposure, high humidity) and maritime operational needs are key considerations.

1.3 Technical Tracks

The Contractor shall furnish a range of hardware, software, or services aligned with technical tracks to meet requirements of this contract and individual orders. All hardware and services must meet DHS policies, standards, and procedures as identified in individual orders. Each proposed solution will correspond to a specific Track as defined below.

Track 1 – HARDWARE/ SOFTWARE & ANCILLARY SERVICES The Contractor shall provide material C-UAS solutions for end users to test, evaluate, or operate.

These solutions shall include up to all physical components, associated or standalone software that meet the defined requirements and capabilities. Standalone software shall be able to be integrated into existing C-UAS hardware. This track includes all related ancillary services such as training, maintenance, installation, planning, customer support, and customization for the selected use case, enabling end users to sustain and operate their C-UAS solutions effectively.

Track 2 – COMPREHENSIVE SERVICES The Contractor shall provide services that meet defined requirements and capabilities to support vendor-operated turnkey solutions, system integration, research and development (R&D), and test and evaluation (T&E) support, to ensure effective and sustained operation of C-UAS systems.

The Contractor shall provide, as applicable, the following services:

o C-UAS as a Service: Vendor-operated turnkey solutions, where contractors provide any of the system types (Detection, Tracking, and Identification (DTI) Systems; Mitigation Systems; and Integrated Systems) as a fully managed service.

o System Integration: Provide technical expertise and tools to integrate C-UAS solutions with existing systems, platforms, and emerging technologies. Ensure DHS-wide interoperability through non-proprietary data formats, APIs, secure communication protocols, and compatibility testing.

o Research and Development (R&D) and Test and Evaluation (T&E) Support: Provide equipment, tools, data, personnel, and/or expertise to facilitate R&D and T&E activities for C-UAS solutions. This includes C-UAS equipment, simulation tools, data collection and analysis tools, system reports, and lifecycle and upgradability assessments.

2 TECHNICAL REQUIREMENTS

2.1 Functional Definitions and Requirements

The contractor shall deliver solutions that perform the requirements outlined below. While not all requirements are applicable to every solution, any applicable capability provided by the system must comply with the corresponding requirement.

2.1.1 Scalability:

Shall demonstrate ability to ramp up production to meet increased demand or surge requirements, including scalability of manufacturing processes, supply chain resilience, and workforce capacity due to future operational needs, increased UAS threats or expanded geographic coverage. This includes having contingency plans for addressing supply chain disruptions, ensuring timely delivery of systems and components under varying operational conditions.

2.1.2 Detect:

System shall incorporate one or more of the following technologies to ensure robust and comprehensive operational capabilities: Radio Frequency Detection, Radio Detection and Ranging (RADAR), Optical sensors (cameras), Acoustic sensors, and Electro- Optical/Infrared (EO/IR) sensors and detail how they are utilized.

Shall be able to detect a UAS at a minimum range of 2 km.

2.1.3 Track:

Shall compile reports over time of where a Ground-based Control System (GCS) or Unmanned Aircraft System (UAS) is located.

Shall display tracking data as a line or sequence of dots in the system’s user interface.

Shall provide track history with an update rate of ≤ 20 seconds.

Shall simultaneously track a minimum of 3 UAS.

Shall provide static estimated reports or displays of where a GCS or UAS is located.

Shall achieve geolocation capabilities with the following thresholds:

o 60% probability of geolocating UAS in 3D (latitude/longitude/altitude).

o Overall geolocation error of less than 75 m for moving UAS and 50 m for hovering UAS.

o 80% probability of geolocating UAS Ground Control Stations (GCS) with an error of less than 50 m.

2.1.4 Identification:

Shall assign detected UAS to high-level categories, such as UAS type, group, manufacturer, and/or protocol.

Shall assign detected UAS to more specific categories, such as the physical/MAC address of the modem, IMEI number, serial number, or the exact make/model and protocol of the

UAS.

Shall provide end user whitelist/blacklist management for known UAS.

2.1.5 Mitigate/Neutralize:

Shall provide methods to remove or reduce the threat posed by a UAS.

Shall mitigate UAS threats at a minimum range of 500 meters.

Shall mitigate at least one simultaneous UAS threat without degradation in effectiveness.

2.1.6 Command and Control:

The system shall support integration with Team Awareness Kit (TAK) or other existing situational awareness systems.

The system shall comply with relevant standards, including the National Information Exchange Model (NIEM), NIST SP 800-53, and DHS Management Directive 047-01.

The system shall allow operators to access and extract detection, identification, classification, and tracking data to support post-mission analysis.

The system shall store and maintain all system data (e.g., detection logs and reports) for at least 180 days.

The system shall share graphical user interface (GUI) display information to external displays using HDMI, DisplayPort, or USB-C.

2.1.7 System Resiliency:

The system shall have been evaluated against the following military standards to ensure durability, reliability, and survivability:

o MIL-STD-810H: For environmental durability, including temperature, humidity, shock, vibration, and other environmental conditions.

o MIL-STD-461G: For electromagnetic interference (EMI) and electromagnetic compatibility (EMC), ensuring reliable operation in environments with high electromagnetic interference.

o MIL-STD-464C: For electromagnetic environmental effects (E3), ensuring survivability and reliable operation in environments with electromagnetic threats, including electromagnetic pulse (EMP).

The system shall comply with the NIST Cybersecurity Framework and include encrypted communications links.

The system shall achieve an operational availability of at least 90% over a 12-month period.

2.2 Aircraft-Based Operations Requirements

For systems intended for deployment on aircraft, the contractor shall ensure the following:

2.2.1 Airborne Integration:

o Systems shall be compatible with aircraft systems, including avionics, communication systems, and onboard sensors.

o Systems shall meet size, weight, and power constraints for airborne platforms.

2.2.2 Operational Functionality:

o Systems shall operate effectively at altitude and in varying atmospheric conditions.

o Systems shall integrate with onboard situational awareness tools and provide real-time data transmission to ground stations or other aircraft.

2.2.3 Safety and Certification:

o Systems shall comply with Federal Aviation Administration (FAA) regulations for onboard equipment.

o Systems shall be certified for electromagnetic compatibility to prevent interference with aircraft systems.

2.2.4 Deployment Scenarios:

o Systems shall support airborne operations, such as patrolling borders, monitoring large areas, or disaster response.

o Systems shall be capable of detecting, tracking, identifying, and mitigating UAS threats during flight.

2.3 Maritime Deployment Requirements

For systems intended for deployment in maritime environments, the contractor shall ensure the following:

2.3.1 Maritime Integration:

o Systems shall be compatible with maritime platforms, including vessels, coastal installations, and port infrastructure.

o Systems must meet size, weight, and power constraints for maritime operations.

2.3.2 Operational Functionality:

o Systems shall operate effectively in maritime conditions, including high humidity, saltwater exposure, and dynamic movement aboard vessels.

o Systems shall integrate with onboard situational awareness tools and provide real-time data transmission to coastal command centers or other vessels.

2.3.3 Environmental Resilience:

o Systems shall be ruggedized to withstand maritime environmental factors, including corrosion resistance, waterproofing, and shock absorption.

o Systems shall have been evaluated against MIL-STD-810H standards for environmental durability, particularly for saltwater exposure and vibration.

2.3.4 Deployment Scenarios:

o Systems shall support maritime operations, such as securing ports, patrolling coastal areas, or responding to threats aboard vessels.

o Systems shall be capable of detecting, tracking, identifying, and mitigating UAS threats in maritime environments.

2.4 Technology Refresh Requirements

The contractor shall ensure that their product/service catalog remains current and reflects the latest advancements in technology. DHS reserves the right to audit the contractor's catalog and technology refresh process to ensure compliance with this requirement.

2.5 Testing Requirements

The contractor shall support testing activities, defined at the task order level, to ensure compliance with operational and technical requirements.

At a minimum, the contractor shall provide detailed testing reports as required to validate system functionality and performance. This shall include:

Operational Test Reports: Submission of any existing operational test reports for the system, including results from prior deployments or evaluations.

Pre-Deployment Testing: Testing in controlled environments to validate system functionality and performance. Pre-Deployment Testing shall include:

o Capturing results against MIL-STD-810H for environmental durability.

o Capturing results against MIL-STD-461G for electromagnetic interference (EMI) and electromagnetic compatibility (EMC).

o Capturing results against MIL-STD-464C for electromagnetic environmental effects (E3), including survivability in environments with electromagnetic pulse

(EMP).

o Testing of system capabilities, including detection, tracking, identification, and mitigation, under simulated operational conditions.

Operational Testing: Testing scenarios that mimic real-world conditions, including:

o Urban environments with high RF interference.

o Remote areas with limited infrastructure.

o High-density events with multiple UAS threats.

o Aviation environments, including airports or airfields.

o Aircraft-based operations, including testing at altitude and integration with onboard systems.

o Maritime environments, including ports, coastal areas, or vessels.

Acceptance Testing: Clear acceptance criteria, such as successful detection and mitigation of 95% of simulated UAS threats and seamless integration with DHS systems during testing.

2.6 Training Requirements

The contractor shall provide training tailored to the operational needs of DHS Components, including system setup, operation, and maintenance, as defined at the task order level.

Training shall be conducted in person unless otherwise requested by DHS. At a minimum, the training shall cover the entire solution, including:

System setup and calibration.

Detection, tracking, classification, identification, and mitigation workflows.

Troubleshooting and maintenance procedures.

Training shall be delivered at a train-the-trainer level to ensure DHS personnel can train others effectively.

2.7 Update and Maintenance Management

The contractor shall provide the process for implementing system/software updates, threat library updates, and hardware updates with every task order. This shall include:

Notification timelines for updates.

Testing and validation procedures prior to deployment.

Documentation of update impacts on system performance.

The contractor shall also provide their Maintenance Management Plan with every task order, including:

Scheduled maintenance activities.

Procedures for addressing unscheduled maintenance needs.

Availability of spare parts and consumables.

2.8 Interoperability Declaration

The contractor shall declare the file formats used by their system and provide documentation of existing interoperability with other systems, with every task order, including:

DHS situational awareness platforms (e.g., TAK, DHS COP).

Threat intelligence databases.

Command and control (C2) systems.

2.9 Spectrum Analysis

The contractor shall provide an analysis of their system’s impact on the RF spectrum, with every task order, including:

Frequency bands utilized.

Potential interference with other systems.

Any associated approvals for spectrum utilization.

2.10 System Documentation

The contractor shall provide detailed documentation of their system’s functionality, limitations, and maintenance procedures, with every task order, including, but not limited to:

Size.

Weight.

Power requirements Deployment time.

System setup and calibration.

Concept of Operation.

Assembly, Storage, and Transportation capabilities.

Detection, tracking, classification, identification, and mitigation workflows.

Troubleshooting and maintenance procedures Corrective actions to be taken if the system fails to meet defined parameters.

Environmental constraints and performance degradation under specific conditions.

2.11 Compliance Documentation

The contractor shall provide documentation demonstrating compliance with all applicable laws, regulations, and standards, with every task order, including, but not limited to:

FAA and FCC regulations governing UAS operations.

DHS cybersecurity standards (e.g., NIST SP 800-53, FedRAMP).

"Buy America" provisions for hardware components.

DHS Management Directives and policies.

3 Deliverables

3.1 General Report Requirements

All document deliverables shall be provided in Microsoft Office electronic format, unless indicated otherwise. Additional requirements may be specified at the task order level.

SOW

Section

Deliverable Description Due Delivered To

3.2 Order Status

Report

Monthly report of the status of orders received during the previous month, orders received at the start of the month

Monthly by the 10th of the following month

IDIQ COR

IDIQ CO

IDIQ PM

3.3 Monthly

Financial Report

Report of contract revenue during the previous month and contract revenue to date.

Monthly by the 10th of the following month

IDIQ COR

IDIQ CO

IDIQ PM

3.4 Transactional

Data Reports

Quarterly Report of the specific order, pricing, and savings information during the previous government quarter.

Quarterly, no later than 15 days after the end of each Government Fiscal quarter.

Dedicated Government Email Box (TBD)

3.5 Post-Award

Conference

Meeting to aid both the Contractor and the Government in achieving a clear and mutual understanding of all contract requirements and identify and resolve potential problems.

Approximately ten (10) business days after contract award.

IDIQ COR

IDIQ CO

IDIQ PM

3.2 Order Status report

The Contractor shall deliver an Order Status Report to the COR and PM monthly, by the 10th of the month. Status changes may include changes to expected delivery dates or locations and changes to anticipated shipping dates.

3.3 Monthly Financial Report

The Contractor shall submit a Monthly Financial report by the 10th day of the month following the previous reporting period. The Monthly Financial report shall provide the overall Contract financial status, including revenue from delivery orders during the reporting month as well as total Contract revenue to date.

3.4 Transactional Data Reporting Requirements

The Contractor is required to provide comprehensive transactional data reports for all orders placed under the C-UAS contract. These reports are critical for supporting federal government category management initiatives and ensuring transparency in procurement activities. The specific requirements are as follows:

1. Frequency and Format:

The Contractor shall provide a single group mailbox for all non-solicitation inquiries.

The Contractor shall provide the transactional data report on a quarterly basis, no later than 15 days after the end of each fiscal quarter.

The report must be submitted in electronic format, either .xls or .csv utilizing the DHS provided template, with the following column headers ordered from left to right: Award Vehicle, Contract Number (IDVPIID), Order Number (Award PIID), Modification Number (if applicable), Vendor Name, DUNS, Federal Department or Agency, Component or Office, Order Date/Date of Award, Delivery Date, Baseline Price Per Unit (Contract Ceiling Price), Baseline Price Per Unit (GSA or Commercial List Price), Award Price Per Unit, Quantity of Item Sold, Unit of Measure, Description of Deliverable, SKU/Part Number, and Manufacturer Name.

2. Data Elements:

Award Vehicle (C-UAS): Identify the contract vehicle under which the order was placed.

Contract Number (IDVPIID): Provide the contract number associated with the IDIQ vehicle.

Order Number (Award PIID): Provide the unique order number for each transaction.

Modification Number (if applicable): Include any modification numbers associated with the order.

Vendor Name: Identify the name of the vendor fulfilling the order.

UEI: Unique Entity ID Federal Department or Agency: Specify the federal department or agency placing the order.

Component or Office: Specify the component or office within the agency that issued/placed the order.

Order Date/Date of Award: Provide the date when the order was placed or awarded.

Delivery Date: Provide the date when this item was delivered.

Baseline Price Per Unit (Contract Ceiling Price): Include the contract ceiling price per unit.

Baseline Price Per Unit (GSA or Commercial List Price): Include the GSA or commercial list price per unit.

Award Price Per Unit: Provide the awarded price per unit.

Quantity of Item Sold: Include the quantity of each item sold.

Unit of Measure: Specify the unit of measure for each item.

Description of Deliverable: Provide a brief description of each deliverable.

SKU/Part Number: Include the SKU or part number for each item.

Manufacturer Name: Provide the name of the manufacturer for each item.

3. Submission Process:

The Contractor shall submit the transactional data report to the designated DHS email address (TBD). This email address is a dedicated, non-personal address for data reporting purposes.

The Contractor is responsible for ensuring the accuracy and completeness of the data provided in each report.

If there are zero transactions to report for the quarter, the Contractor shall submit a response indicating this information in lieu of a report.

4. Non-Compliance and Remedies:

Failure to submit the required transactional data reports on time or providing incomplete or inaccurate data may result in contractual remedies.

The Contractor must address any discrepancies or omissions identified by the Government within 3 days of notification.

5. Review and Verification:

The Government reserves the right to review and verify the transactional data reports for accuracy and completeness.

The Contractor shall cooperate with any Government audits or reviews related to the transactional data reporting requirements.

3.5 Post-Award Conference

The Contractor shall participate in a post-award conference that will be held approximately ten

(10) business days after contract award. The purpose of the post-award conference is to aid both the Contractor and the Government in achieving a clear and mutual understanding of all contract requirements and identify and resolve potential problems (See FAR Subpart 42.5).

The C-UAS IDIQ COR is responsible for establishing the time and place of the conference and will notify the appropriate Government representatives and the Contractor. The C-UAS IDIQ

COR will designate or act as the chairperson at the conference. The chairperson of the conference shall conduct the meeting.

The conference may be conducted virtual or at a location within the Washington DC Metropolitan area at the Government’s discretion.

The post-award conferences will establish work level points of contact, determine the administration strategy, roles and responsibilities, and other information pertinent to the successful administration of and participation in the C-UAS award.

4 APPLICABLE DOCUMENTS

4.1 Compliance Documents

The following documents provide specifications, standards, or guidelines that must be complied with in order to meet the requirements of this contract.

FAA and FCC regulations governing UAS operations.

DHS cybersecurity standards (e.g., NIST SP 800-53, FedRAMP).

"Buy America" provisions for hardware components.

DHS Management Directives and policies.

MIL-STD-810H

MIL-STD-461G

MIL-STD-464C

5 GOVERNMENT FURNISHED ITEMS

The Government will furnish no working space, equipment, or supplies in support of this Contract.

6 TRAVEL

Contractor travel may be required to customer sites (e.g. equipment installation or repair).

7 HOURS OF OPERATION

Hours of Operation will be determined at the order level.

8 COMPLIANCE WITH DHS SECURITY POLICY

All unclassified hardware, software, and services provided under this contract shall be compliant with DHS Sensitive System Policy Directive 4300A.

All classified collateral hardware, software, and services provided under this contract shall be compliant with DHS National Security Systems Policy Directive.

The Contractor shall comply with federal regulations, such as NIST SP 800-171, to safeguard Controlled Unclassified Information (CUI) through access controls, encryption, and incident response measures. The Contractor shall also address Foreign Ownership, Control, or Influence (FOCI) risks, implement physical and cybersecurity protections, comply with export control laws, and ensure secure data handling within approved locations. The Contractor shall report all security incidents and flow-down all clauses for subcontractors.

8.1 Sensitive But Unclassified Systems Requirements

The Contractor will have access to unclassified and Sensitive But Unclassified (SBU) Information under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination.

OCIO has determined that performance of this contract requires the Contractor access to SBU information. SBU is unclassified information for official use only. Contractor employees that do not have a security clearance and require access to SBU information will be given a suitability determination.

Data Security - SBU systems shall be protected from unauthorized access, modification, and denial of service. The Contractor shall ensure that all aspects of data security requirements (i.e., confidentiality, integrity, and availability) are included in the functional requirements and system design and ensure that they meet the minimum requirements as set forth in the DHS IT and cybersecurity policies and procedures. These requirements include:

o Integrity - The computer systems used for processing SBU data shall have data integrity controls to ensure that data is not modified (intentionally or unintentionally) or repudiated by either the sender or the receiver of the information. A risk analysis and vulnerability assessment shall be performed to determine what type of data integrity controls (e.g., cyclical redundancy checks, message authentication codes, security hash functions, and digital signatures, etc.) shall be used.

o Confidentiality - Controls shall be included to ensure that SBU information collected, stored, and transmitted by the system is protected against compromise. A risk analysis and vulnerability assessment shall be performed to determine if threats to the SBU information or data exist. If it exists, data encryption shall be used to mitigate such threats.

o Availability - Controls shall be included to ensure that the system is continuously working and that all services are fully available within a timeframe commensurate with the availability needs of the user community and the criticality of the information processed.

Data Labeling - The Contractor shall ensure that documents and media are labeled consistent with the DHS Sensitive Systems Policy for systems and services delivered and operated by the Contractor.

Controlled Unclassified Information (CUI) – Execution of orders under this IDIQ will incorporate the requirements of HSAR 3052.204-72, Safeguarding of Controlled

Unclassified Information commensurate to the categories of CUI used by the quoter for that given task order.

8.2 Encryption Compliance

If encryption is required, the following methods are acceptable for encrypting sensitive information:

1. FIPS 197 (Advanced Encryption Standard (AES)) 256 algorithm and cryptographic modules that have been validated under FIPS 140-2.

2. National Security Agency (NSA) Type 2 or Type 1 encryption.

3. Public Key Infrastructure (PKI) (Section 5 of DHS Sensitive Systems

Policy Directive 4300A).

4. National Security Systems requiring encryption shall comply with the following standards:

a. Products using FIPS 197 AES algorithms with at least 256-bit encryption that have been validated under FIPS 140-2 (Note: The use of Triple Data Encryption Standard (3DES) and FIPS 140-1 is no longer permitted. If AES cannot currently be used, the Program Manager will obtain the necessary waiver or exception.)

b. NSA Type 2 or Type 1 encryption

8.3 Security Review

The Government may elect to conduct periodic reviews to ensure that the security requirements contained in this contract are being implemented and enforced. The Contractor shall afford DHS, including the organizations of the DHS Office of the Chief Information Officer, the Office of the Inspector General, authorized COR, and other Government oversight organizations, access to the Contractor’s facilities, installations, operations, documentation, databases, and personnel used in the performance of this contract.

The Contractor shall contact the DHS Chief Information Security Officer to coordinate and participate in the review and inspection activity of Government oversight organizations external to DHS. Access shall be provided to the extent necessary for the Government to carry out a program of inspection, investigation, and audit to safeguard against threats and risks to the confidentiality, integrity, and availability of DHS data or the function of information systems operated on behalf of DHS, and to preserve evidence of a computer crime.

8.4 Interconnection Security Agreement

An Interconnection Security Agreement (ISA) between DHS and non-DHS information systems shall be established only through controlled interfaces and via approved service providers. The controlled interfaces shall be accredited at the highest security level of information on the network. Connections with other Federal agencies shall be documented based on interagency agreements, memoranda of understanding, service level agreements or interconnect service agreements.

8.5 OCIO CISO CYBER-SUPPLY CHAIN RISK MANAGEMENT (C-SCRM)

a. Definitions

i. Component: a unit defined by the supplier that connects to and functions as part of the product.

For software products, a component is a unit of software defined by a supplier at the time the component is built, packaged, or delivered. For hardware, a component is one hardware unit designed to connect to and function as part of a larger product.

ii. End-of-Life (EOL): means that an ICT product has reached the final stage of the product life cycle in which that version of the ICT product will no longer be supported nor manufactured (e.g., no patches will be developed, no security improvements will be made, and, sometimes, no troubleshooting technical assistance will be offered).

iii. End-of-Support (EOS): means that an ICT product will no longer be supported (e.g., no patches will be developed, no security improvements will be made, and, sometimes, no troubleshooting technical assistance will be offered).

iv. Information and Communications Technology (ICT): encompasses the capture, storage, retrieval, processing, display, representation, presentation, organization, management, security, transfer, and interchange of data and information; includes all categories of ubiquitous technology used for the gathering, storing, transmitting, retrieving, or processing of information (e.g., microelectronics, printed circuit boards, computing systems, software, signal processors, mobile telephony, satellite communications, and networks).

v. Product: part of the equipment (hardware, software and materials) for which usability is to be specified or evaluated.

b. Original Equipment Manufacturer (OEM) End-use…