20250417 CsUAS_EW_RFI.pdf

Air Force Counter-small Unmanned Aircraft Systems (C-sUAS) Electronic Warfare Systems

REQUEST FOR INFORMATION (RFI)

C-sUAS Product Information Purpose

This Request for Information (RFI) is issued by the United States Air Force (USAF) Counter-small Unmanned Aircraft Systems (C-sUAS) branch to gather information about current and emerging technologies in electronic warfare (EW) to combat sUAS threats (groups 1-3). Examples targets are presented in Table 1.

UAS Group Maximum Weight (lb)(MGTOW)

Nominal Operating Altitude (ft)

Speed (kn) Representative UAS

1 0-20 < 1200 AGL 100 RQ-11 Raven, WASP, PUMA

2 21-55 < 3500 AGL < 250 ScanEagle, Flexrotor

55-1320

< 180 FL < 250

Ahield AI V-BAT, RQ- 7B Shadow, RQ-21 Blackjack

4 >1320 < 180 FL

Any

Airspeed MQ-8B Fire Scout, MQ- 1A/B Predator

5 >1320 >180 FL Any Airspeed

MQ-9 Reaper, RQ-4 Global Hawk

Table 1: US DoD UAS Groupings with Groups 1-2 highlighted in grey

INSTRUCTIONS:

1. The document below contains a form to be filled out concerning the description of the C- UAS technologies that a respondent desires to submit back for this RFI. The form allows Contractors to provide their product’s detailed specifications and can be used by the Government to determine which systems meet their needs.

2. THIS IS NOT A NOTICE OF REQUEST FOR PROPOSAL (RFP) ISSUANCE. This request is issued for the purpose of exchanging information and market research that will allow industry to best communicate to the Government their capabilities through this exchange of information. Responses to this request are voluntary and will not affect any contractor's ability to submit a proposal if, or when, an RFP is released. The requested information is for planning purposes only and does NOT constitute a commitment, implied or otherwise, that a procurement action will be issued.

No entitlement to payment by the Government of direct or indirect costs or charges will arise as a result of the submission of information in response to this request.

The Government shall not be liable for or suffer any consequential damages for any improperly identified proprietary information.

No award will be made as a result of this request. This request is for informational purposes only to promote exchanges of information with industry. The Government will not pay for any information and/or materials received in response to this request for information and is in no way obligated by the information received.

3. *** Responses to this request are due no later than Friday, 30 May 2025, at 3:00 P.M.

Eastern Standard Time (EST) to Contracting Officer, Robert Gill at Robert.gill.12@us.af.mil ,Contract Specialist Kristen Rienzo at kristen.rienzo@us.af.mil and Program Manager, Thomas Greene at Thomas.greene.6@us.af.mil. Responses to this notice may not be returned. Please request a confirmed receipt ***

4. Failure to provide documentation may result in the government being unable to adequately assess the product’s capabilities and its suitability to meet government requirements. The information provided on this form shall NOT exceed the CONTROLLED UNCLASSIFIED INFORMATION (CUI), formerly UNCLASSIFIED//FOUO. If existing substantiation is desired to be submitted in addition to this form (e.g., DD1494, additional slick sheets, photos, system architecture diagrams, etc.), please attach your response as separate files. Classified data should not be submitted in response to this RFI without prior coordination with the Points of Contact (POC) below. If classified data is desired to be included, first contact the POCs below to establish an appropriate means of transmittal for classified data.

Primary Point of Contact:

Contracting Officer, Robert Gill, Robert.gill.12@us.af.mil

Secondary Points of Contact:

Program Manager, Thomas Greene Thomas.greene.6@us.af.mil

Contract Specialist, Kristen Rienzo Kristen.rienzo@us.af.mil

1. Please specify/label all units, as appropriate, for numerical items.

2. Please fill out all sections below.

3. Please fill out one response per EW model for each section regarding the technical data.

These can be submitted as a single package with the company information only listed once.

mailto:Robert.gill.12@us.af.mil mailto:kristen.rienzo@us.af.mil mailto:Robert.gill.12@us.af.mil mailto:Thomas.greene.6@us.af.mil mailto:Kristen.rienzo@us.af.mil

4. Please provide all documents listed under “Document List” at the end of this RFI, if able.

If the documentation is too large to send via email, please drop-off via DoD Safe (up to 8 GB total) for Robert.gill.12@us.af.mil, kristen.rienzo@us.af.mil ,and Thomas.greene.6@us.af.mil. In the Short note to the Recipients section, type “2025 C-sUAS EW RFI Response: (vendor’s name)”.

COMPANY INFORMATION

Vendor Name and contact information

Address

CAGE/UEID Number (if applicable)

Recommended NAICS code for this effort

Business Size (small or large)

Section A: EW SYSTEM GENERAL INFORMATION

Product Name / Model Number mailto:Robert.gill.12@us.af.mil mailto:kristen.rienzo@us.af.mil

What data formats does the system generate, process, or export? What data formats does the system ingest? What type of I/O is used?

List formats and interfaces if able to.

Is wireless transmit/receive available, or intended to be used?

What is the estimated file size(s) and time to download and transfer approximately 8 hours’ worth of operational/test data?

What media would be used to transfer data to event coordinators/analysts? (i.e. CD/DVD, thumb drive or USB hard drive, etc.)

Does your system interface with any existing Command and Control (C2) applications?

List C2(s) if able to and which data format/language they use to communicate (i.e.

TCUT, ASTRIX, etc.).

What types of environments has the system been successfully operated in (i.e. test or operational)?

Is this data available upon request?

What is the reliability (Mean Time Between Failures and/or Mean time Between Critical Failures (mins/hours)) of the system?

How is your MTBF/MTBCF calculated?

(i.e. theoretical prediction, field data, or life testing?)

Number of personnel needed to install system? Estimated Setup time?

Does your system have troubleshooting functions? And can fault data be downloaded?

(i.e. Built-In-Test [BIT], Fault-isolation-test [FIT], log files, after action reports, elapsed time indicators [ETI])

Provide any warranty/RMA information

List the country the system is manufactured in, where it must go for intermediate or depot level repairs, and any export control considerations if they exist.

List any limited life items, or replaceable/serviceable items (filters, batteries, etc.) in the system.

Was Failure Mode & Effects Analysis (FMEA) or Failure Mode, Effects and Criticality Analysis (FMECA) performed on your system?

Provide Technology Readiness Level (TRL) and your calculation file (reasoning)

If the EW system has been manufactured and fielded with any organization, please describe the quantity produced/fielded (in total, and if able to, specify organization).

Provide a list of external support equipment your system requires for setup/operation/updates

Has your system received an ATO and/or what stage are you in the RMF process?

Please provide a graphical representation that illustrates the architecture of your EW System.

At a minimum show the major subsystems, key functions, software architecture, and physical/electrical interfaces.

Data interfaces should include but not limited to physical layer and transport protocols.

What type of I/O is used?

Is wireless transmit/receive available, or intended to be used?

What training/familiarization information is available?

(i.e. PowerPoint training for operation, system maintenance/troubleshooting, installation and setup procedures, technical documentation, etc.)

Is your system covered by a specific System Classification Guide (SCG)? If so please list it and provide it if able. Simply listing the SCG title and date is acceptable.

If any government sponsor has mandated the usage of a specific SCG for operation or testing of your component/subsystem, please list and/or provide, as able.

Please list IP assertions and rights of the system.

(e.g., Government owned, purpose rights, limited, etc.)

Describe any specific cybersecurity features or design principles that have been incorporated into the EW system's software and architecture to mitigate potential cyber threats and vulnerabilities.

What specific cybersecurity hardening measures and testing activities have been performed on the EW system to validate its security posture and resilience against cyberattacks?

Can this system operate Unclassified, or does it require a Classified environment/network?

(please explain)

Is there an existing digital model of the system? If yes, please elaborate on the type of model.

Has a HERO, HERP, HERF report been completed on the EW system? If yes, please attach. If in the works, please give estimated date of completion.

Does your system have an approved and current JF-12? If not, what percentage of the way through the process are you (please explain).

What specific EW techniques does the system employ? (e.g., jamming, deception, detection, direction-finding)

What is the primary intended use case for this EW system? (e.g., C-sUAS, communications intelligence, warning)

Does the system have any modularity or scalability features? (e.g., can components be swapped or added to adjust capabilities)

Additional comments not addressed above that you feel would help us understand your

SECTION A (Continued): EW SYSTEM HARDWARE

Please list all the hardware components required to operate the system.

(e.g., server, maintenance laptop, network switches, media converters, etc.)

What is the physical size of the system? List per subcomponent as necessary.

(e.g. LxWxH, server xU)

What is the total weight of the system (lbs.)?

List per subcomponent as necessary.

Describe the storage/transportation/logistics of the system.

(include sizes of transit cases, special equipment/handling, etc.)

What are the power requirements (Watts) to operate the system? List per subcomponent as necessary.

Are any specialized tools or training required to install, maintain, or repair the system?

Describe the overall construction grade and materials used to protect the system from damage from exposure to the sun, rain/ice, salt fog, corrosion, hail, lightning, and other environmental hazards.

Be specific regarding any United States Military Standard Compliance or equivalent.

What are the minimum and maximum operating temperatures?

List per subcomponent as necessary.

What weather conditions have the EW system been tested and operated in?

What are the weather tolerances or limitations?

(i.e. day/night, wind, precipitation, ice, etc. if applicable)

What minimum, recommended, and maximum processing power does the system require? List separate requirements for subcomponents as necessary.

(e.g. CPUs, Cores, Cuda Cores, threads, etc.,)

Is the hardware cleared to process, store, and cleanse classified data?

Cleansing refers to the process of destroying any classified data contained in a hard drive so that it cannot be recovered.

What is the system's operating frequency ranges?

What are the system's power output levels and duty cycle limitations?

Has the system been tested or operated in environments with high electromagnetic interference?

What are the system's self-protection capabilities against hostile EW countermeasures?

SECTION A (continued): EW UNCLASSIFIED CAPABILITES

What is the range of the system?

Please provide success rate of detection of Group 1 and 2 at different ranges, if possible.

What is the Detection/Array Type?

(scan type – mech/electronic, hemispherical panels, etc.)

Is it operator or installer configurable?

(i.e., who can change elevation range, azimuth range, detection range, nuisance-alarm parameters, etc.?)

What is the Pulse Repetition Rate?

What is the generic Spectrum Band?

(e.g., X-band, S-band)

What are the Spectrum Management Capabilities?

(spectrum range(s), bandwidth(s), waveform(s)) - (e.g., frequency hopping, spread spectrum, intelligent spectrum use)

What is the Target Search Sector Coverage (Min/Max Range, Elevation, Azimuth)?

What is the Target Track Sector Coverage (Min/Max Range, Elevation, Azimuth)?

What is the Transmit/Receive Antenna Beamwidth, azimuth and elevation?

What is the Transmit/Receive Antenna Gain?

Is it a 2D or 3D EW system?

What is the Target Location Accuracy?

(2D or 3D coordinates as appropriate, specify range accuracy) when detected and tracked using embedded or external software provided by offeror. Need to specify accuracy for what size (dBsm) target.

What kind of target identification capabilities does the EW system have?

Is it library based or other?

What is the False Alarm Rate (per hour)?

(Has your system operationally demonstrated a false alarm rate?)

detectable speeds of a UAS?

trackable speeds of a UAS?

Can the EW system support mobile active operation? Is the system capable of compensating for platform motion?

Can the EW system detect and track Group 3 targets?

Describe how the vendor tests and validates the EW system capabilities.

Are there any specific site survey requirements for optimal system deployment?

What specialized training or certifications are required for personnel installing, operating, or maintaining the system?

SECTION A (Continued): EW SOFTWARE

Please briefly describe the software.

Does it rely on specific or unique hardware?

List all licensing fees and licenses required to operate the software.

List how often the license needs to be renewed and cost of renewal.

List any certifications the software has received.

List certifications the software is currently receiving.

SECTION A (Continued): EW PRICE AND SUPPORT

Where can the Government purchase your product?

Has your product been offered, sold, or leased to the General Public?

Provide available Government contracts and POCs if able to.

Provide prices for follow on support for system. List different pricing models if applicable.

Provide price for reach back support. List different pricing models if applicable.

Provide cost per unit and any reductions in price that may result from larger quantity buys.

Provide price for on and offsite Field Service Representative/Field Service Engineer (FSR/FSE) support.

What is the lead time to acquire one EW system?

Describe vendor’s roadmap for the EW system? (planned updates, planned added capabilities, planned end of support)

Section B: Supply Chain Resiliency and Manufacturing Details

What are your current manufacturing locations?

What specific measures are in place to mitigate the risk of counterfeit electronic components entering the EW system's supply chain?

(e.g., supplier vetting processes, component testing procedures)

Are there plans for relocation or expansion in the near future (24 months)? If the plans are not yet confirmed, please note that.

What is the current production capacity for 6 months?

What is the current production capacity for 12 months?

How long can the manufacturing keep up with maximum capacity rates?

If 100 units were ordered tomorrow, what would the production schedule look like (i.e. time until first delivery, time until last delivery)?

Identify and describe any potential single point of failure within your supply chain that could disrupt the production or delivery of the EW system.

Does your supply chain include any specialized components or materials unique to EW systems (e.g., high-power amplifiers, RF filters)?

Please describe your sourcing strategies for these components.

Are all components and manufacturing processes for your EW system compliant with International Traffic in Arms Regulations

(ITAR)?

Can you provide a detailed description of your manufacturing process flow?

Can you describe your supply chain management process?

What are your defect rates in production?

How are the defects tracked and managed?

What quality control measures are implemented? What standards do you adhere to (e.g., ISO 9001)?

What acceptance testing do you perform on your system before shipping?

How do you ensure compliance with environmental and safety regulations during production?

How many systems are currently on back order?

If able, provide examples of past projects where you successfully ramped up production to meet increased demand.

Documentation List

Please provide the following list of documentation attached to the RFI (digitally), if able to.

- Technical Data

- Generic layout of external interfaces

- Interface Control Document (ICDs)

- System Design Document (SDD)

- System Requirements Document (SRD)

- Pricing Models

- EW Test Reports

- EW Safety Procedures

- Software Defined Radio (SDR) Architecture (if applicable)

- Failure Analysis

- Test Data/Results

- HERO, HERF, HERP (if applicable)

- Form DD-1494 and JF-12 (if applicable)

- EW System Description (optional): If not fully covered in other submitted materials, please provide a dedicated document that offers a comprehensive overview of the EW

- Any other additional documents

C-sUAS Product Information