C-sUAS RFI Final.pdf

Request for Information U.S. Air Force Counter-small Unmanned Aircraft

Systems

Table of Contents

1. Introduction/Purpose

2. Background and Objectives

2.1. Mission Overview

2.2. Capability Description

2.3. Key Technical Objectives

3. Support Needed

3.1. Software Related Work

3.2. Test and Evaluation

3.3. Sustainment

4. Contractor Capabilities and Experience 3 Submission of Information 4 Points of Contact 5 Disclaimer

1. Introduction/Purpose The United States Air Force (USAF) is issuing this Request for Information (RFI) to improve USAF understanding of market capabilities and identify qualified vendors capable of providing Counter Small Unmanned Aircraft Systems (C-sUAS) integration, development, training, and sustainment services. These activities will support C-sUAS systems that are capable of Detecting, Tracking, Identifying, and Defeating sUAS located globally. Responses to this RFI will help support the USAF strategy for this acquisition and identify businesses that are capable of successfully providing C-sUAS support to the USAF.

All interested and qualified businesses (i.e., Small Business, Other than Small) are encouraged to respond to this notice in accordance with the instructions addressed herein.

2. Background and Objectives

2.1. Mission Overview

The C-sUAS mission for the USAF is the defense of critical assets from threats which includes but is not limited to personnel, bases, flight lines, storage areas, and in transit equipment. Due to the widespread use of UAS technologies both for recreational and military use, the AF is tasked with protecting these critical assets from a diverse range of threats.

These threats are classified as groups 1-3 UAS that vary drastically in capability (range of characteristics can be found below).

Characteristics for Group 1-3:

- Size: <1,320 lbs

- Speed: <250 knots

- Operating altitude: < Flight Line 180 or < 3500 ft AGL

These threats range further in capability from commercial or hobbyist to military UAS. This poses a diverse and ever evolving threat. The operators of these UAS and their intent can also range quite drastically. They could be a commercial hobbyist who have interest in the DoD and their activities or a nefarious actor(s) who wish to cause harm to personnel, gather intelligence about, or destroy military assets.

Overall, the AF is tasked with protecting a diverse range of assets from a wide and ever evolving threat.

2.2. Capability Description

The USAF currently has a diverse set of systems fielded world-wide to combat the threats and is continuing to field to additional sites with updated sensors and effectors.

The fielded systems currently use a combination of COTS and GOTS electronic warfare systems, active Radars, and EO/IR sensors alongside a Government owned and maintained Command and Control (C2) system. The Government is rapidly integrating new capabilities to include newer versions of the above list in addition to Low Collateral Effects Interceptor (LCEI) systems and kinetic effects systems. Current systems are primarily fixed site; however, there is an On the Move EW system (which is used while driving) and there are plans for an expeditionary system and addition mobile or dismount systems in the future.

2.3. Key Technical Objectives

Due to the nature of the rapidly changing threat, the USAF is planning to continually evolving the system of systems. To facilitate this evaluation, the Government is focused on the following key technical objectives:

• Cloud Computing

• Maintaining the the Modular Open Systems Architecture (MOSA)

• Agile Software development (DevSecOps)

• Maintain Government DevSecOps Pipeline (DSOP)

• AI/ML for object detection, tracking, and ID, ROE suggestions, operator workload reduction, and automation of the kill chain

• Digital Engineering

• Continuous development with rapid incremental deliveries to meet mission needs (minimum of 2 per year)

• Persistent cyber patching and cyber security baked into the development process

• Continual integration of new sensors and effectors based on gaps and obsolescence

3. Support Needed

3.1. Software Related Work

The following is the basic outline of the C-sUAS development effort:

• Software development and/or integration to include the following:

o Correlation and fusion algorithms o Machine Learning Algorithms o Threat Prioritization Modules o User Interface o Camera slew-to-cue and tracking o Integration of COTS/GOTS products o Cyber hygiene o Resolving backlog items

• Developing and maintaining software documentation and software development kit

3.2. Test and Evaluation

• Writing test plans and procedures

• Tracking and resolving deficiencies

• Working with DoD (or other government equivalent) independent developmental and operational test organizations

• Requirements development and test method determination (e.g. formal test, analysis)

• Planning and conducting test events, specifically with live UAS flights.

• Test and Evaluation execution and support (assist government in test events and generation of test reports or supporting documentation)

3.3. Sustainment

Support and sustainment is required for all sensors, effectors, C2, and associated components (e.g.

mounts, comms, power, etc.) until components are deemed obsolete or “end of life” (EOL) by the USAF. Support and sustainment services required for this effort will include the following:

• 24/7 telephone Help Desk and troubleshooting

• Entering relevant data into the Government Lifecycle Management Information System

(LMIS)

• Fly-out support

• Full time on-site Field Service Engineers (FSEs) at some locations

• Tracking and storage spares

• Access to Original Equipment Manufacturers (OEM) vendors for coordinating support, repairs, and sparing

• Repairs of equipment on site, movement of equipment, and As-Built Drawing updates when needed

• Identifying and recommending resolution for deficiencies

• Identifying diminishing materiel support (DMS) situations and recommending resolutions

These requested services will be supplemented by an organic Government Depot Source of Repairs (DSOR). The extent to which is not fully known at this time. However, support will still be needed to generate, acquire from OEMs, or supplement documentation for the DSOR.

4. Contractor Capabilities and Experience The purpose of this RFI is for USAF to improve its understanding of market capabilities and identify vendors capable of providing C-sUAS integration, development, fielding, & sustainment services.

Interested vendors shall identify their capabilities to meet the requirements and questions detailed below. The total response to these questions shall not exceed 15 pages total.

1. General Information

1.1. Name and Address

1.2. Point of Contact for company (Name, Title, Email, and Phone Number)

1.3. List project names that were worked with government. Please provide POC(s).

1.4. Identify your business size/type – Other than small, small, small disadvantaged, 8(a)-certified small disadvantaged, HUBZone small, woman-owned small, very small, veteran-owned small, service-disabled veteran-owned small.

1.5. What percent will you perform as the prime and what percent will you subcontract for the requirements in this RFI?

1.6. Other contract vehicles the USAF may consider for this requirement for which you are an awardee (e.g., Government Wide Acquisition Contracts (GWACs), GSA Schedules, DHS Strategic Sourcing Contract).

1.7. Recommended North American Industry Classification Code (NAIC) best suited for the requirements within this RFI.

1.8. Provide a summary description of your company’s experience with C-sUAS as it relates to the information in this RFI. Limit response to 1 page.

1.9. Recommend an acquisition strategy to utilize for this effort (IDIQ: Single or multiple, TO/DO).

1.10. Recommend evaluation criteria to utilize in evaluations to include suggested subfactors.

2. Contractor Proficiencies (Limit below responses to 2 pages)

2.1. Please provide a brief overview of your company's understanding of USAF C-sUAS requirements as presented in this RFI.

2.2. Describe briefly the capability and experience in providing programmatic and technical management/support of a similar program including, but not limited to cost control strategies, and quality processes.

2.3. Describe resources and technical proficiency as it relates to the scope of effort to include the labor mix available and expertise.

2.4. Describe capability and experience of providing training program development services.

3. Technical

3.1. Have you worked with refining, integrating, and sustaining government owned software?

3.2. Have you developed a software-centric system which follows a Modular Open System

Architecture (MOSA)? Please list out software or program names.

3.3. Have you ever maintained a DevSecOPs pipeline?

3.4. Have you ever worked in a Government owned cloud (e.g., CloudOne)?

3.5. Have you ever continued developing a software from a third party?

3.6. What types of machine learning models have you worked with?

3.7. What were these models built for (e.g., Image Recognition, Natural Language AI, etc.)?

3.8. Have you implemented a Model Based Systems Engineering (MBSE) design? Attach example or provide POC.

3.9. Have you ever built a full Technical Data Package? What program or effort? What was provided if applicable.

3.10. Describe experience working with MBSE tools, creating/maintaining a DSOP, and experience being the main integrator for a Government C2 software. Limit response to 2 pages and provide any necessary diagrams, or drawings as an attachment.

3.11. How would your organization execute taking over the Government owned software pipeline and what resources and documentation would you envision being required?

3.12. How does your organization envision keeping up with the sUAS threat? In what mission space have you had previous experience or examples?

4. Cyber

4.1. Have you ever assessed security controls, conducted audits, continuous monitoring and proposed/implemented measures to address vulnerabilities or non-compliance issues?

4.2. Have you ever conducted vulnerability scanning of the information systems using approved

DoD industry tools?

4.3. Have you ever conducted compliance scans of the information systems per the NIST-800-

53 security technical implementation requirements using approved DoD industry tools?

4.4. Have you ever performed vulnerability scans on the static code deliverables?

4.5. Have you ever implemented the concept of least privilege to ensure that systems operate securely and efficiently without sacrificing capabilities?

4.6. Have you ever developed an Identity and Access Management system?

4.7. Have you worked with PKI authentication and implementation.

4.8. Have you ever worked with 802.1x implementation on layer 2 and layer 3 network devices?

4.9. Describe your experience and knowledge of verifying system compliance with cybersecurity requirements. This should include a high-level Cybersecurity plan to ensure supported systems are up to date and in compliance with Authority to Operate (ATO) requirements. Please limit response to 2 pages.

5. Logistics

5.1. Have you worked with managing Government approved ILS databases for inventory control?

5.2. Have you worked with Government Depot Source of Repair (DSOR)?

5.3. Have you worked with warehouses located both CONUS and OCONUS?

5.4. Have you worked with OEM Supply chain management?

5.5. Have you worked developing a tiered system of training, 3 levels or higher (Maintainer, Operator, Administrator? What program or effort? What type of personnel (commercial, civil, military)

5.6. Do you have experience with handling lost, damaged, or destroyed equipment?

5.7. Have you worked with maintaining Reliability, Availability and Maintainability Data?

5.8. Please describe experience working with a DSOR, supply chain management, PHS&T, and

RAM data. Limit response to 2 pages if applicable.

5.9. Have you shipped equipment to foreign countries for installation?

5.10. Have you ever made a Technical Order (TO)?

5.11. Have you ever made a TO based off a COTS/GOTS manual?

5.12. Have you performed a site survey to include spectrum interference, line of sight, and infrastructure assessment?

5.13. How would your organization envisioning working side by side with a government sustainment depot? Please provide any examples or previous history.

6. Contacts

6.1. List out other Government agencies you have worked with on a similar scope effort along with a Point of Contact for each.

6.2. This project requires working with other manufacturers and companies. Please list out other manufacturers and companies that you have worked with on a similar scope effort.

7. Other and General Statement(s).

7.1. Please use remaining pages to describe additional thoughts, approaches, or other information that you deem relevant to this RFI submission in addition to what risks an organization responding to this requirement foresees in partnering with the government.

3 Submission of Information The information requested in support of the Capabilities Statement must be submitted in writing. The submitted Capabilities Statement shall not exceed fifteen (15) pages, in addition to a one (1) page cover letter, for a total submission not to exceed twenty-one (21) pages.

Your submission should be organized in accordance with the instructions in this document to permit a thorough and accurate review and evaluation by the USAF. Responses to this RFI must be submitted to the USAF via electronic mail no later than July 31, 2025 at 10:00AM, EST to the following:

Mr. Robert Gill at Robert.Gill.12@us.af.mil

Ms. Kristen Rienzo at kristen.rienzo@us.af.mil

Ms. Ciabha Kelleher at ciabha.kelleher@us.af.mil mailto:Robert.Gill.12@us.af.mil mailto:kristen.rienzo@us.af.mil mailto:ciabha.kelleher@us.af.mil

4 Points of Contact All comments, inquiries and responses should be directed to the following individuals:

Ms. Kristen Rienzo Contract Specialist kristen.rienzo@us.af.mil

Ms. Ciabha Kelleher Contract Specialist ciabha.kelleher@us.af.mil

Mr. Robert Gill Procuring Contracting Officer robert.gill.12@us.af.mil

5 Disclaimer

THIS REQUEST FOR INFORMATION IS SOLELY FOR INFORMATIONAL AND

PLANNING PURPOSES AND DOES NOT CONSTITUTE A SOLICITATION. In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract, nor do they affect a potential offeror's ability to respond to any future synopsis/solicitation, which may or may not follow or restrict the Government's eventual acquisition approach. The Government will not provide reimbursement for any information that may be submitted in response to this notice, and no basis for a claim against the Government shall arise from a response to this notice or Government use of any information provided. Respondents are solely responsible for all expenses associated with responding to this RFI.

mailto:kristen.rienzo@us.af.mil mailto:ciabha.kelleher@us.af.mil mailto:robert.gill.12@us.af.mil