ESSC_APKWS_RFI V2.pdf

Counter-small Unmanned Aircraft Systems (C-sUAS) Advanced Precision

Kill Weapon System (APKWS) Request for Information (RFI)

C-sUAS Product Information

BACKGROUND:

The United States Air Force (USAF) Counter small-Unmanned Aircraft Systems (C-sUAS) branch (AFLCMC/ESSC) is requesting information regarding Advanced Precision Kill

Weapon System technologies related to combatting the sUAS in Groups 1, 2, and 3 as presented in Table 1 in order to evaluate industry offerings. ESSC is looking for all systems capable of taking track data/cues from sensors to laze targets and launch guided Hydra 70 APKWS rockets.

Native target detection/sensing and C2 capabilities are not required on system.

• The system must meet US government and TAA regulations on component origin.

• The system must have sufficient test and reliability data.

• Systems should be TRL 6 at minimum

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

3 55-1320 < FL 180 RQ-7B Shadow, RQ-

21 Blackjack

4 >1320 Any

Airspeed

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

5 >FL 180 MQ-9 Reaper, RQ-4

Global Hawk

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

Please note this Request for Information (RFI) is for planning purposes only. The information obtained from responses to this notice may be used to form a future acquisition strategy and solicitation, should one be issued.

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 31 December 2025 to Contracting

Officer, Robert Gill at Robert.gill.12@us.af.mil, Contract Specialist Ciabha Kelleher at ciabha.kelleher@us.af.mil and Program Manager, Capt. 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. However, 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 in 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 Point of Contact:

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

Program Manager, Capt. Thomas

Greene, thomas.greene.6@us.af.mil

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

6. Please fill out all sections below.

mailto:Robert.gill.12@us.af.mil mailto:thomas.greene.6@us.af.mil mailto:Robert.gill.12@us.af.mil mailto:thomas.greene.6@us.af.mil

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

8. If the documentation is too large to send via email, please drop-off via DoD Safe (up to 8

GB total) to above POCs. In the Short note to the Recipients section, type “2025 C-sUAS

APKWS RFI Response: (vendor’s name)”.

COMPANY INFORMATION:

Vendor/Company Name and POC contact information (name, email, phone)

Address

CAGE/UEID Number (if applicable)

Facility clearance level and Safeguarding clearance level

Product Name / Model Number

Business Size and Socioeconomic Status under NAICS

Website

System Questions

Hardware Configuration and Capabilities

Describe what components the system utilizes in stock configuration (i.e. radar, camera, ie/or)

Can system function effectively by integrating only minimum launcher and lazing/camera capability into existing Gov’t sensor and C2 system?

Describe system mobility options and capabilities (trailer mounted, vehicle mounted, stationery etc)

Describe the lazing/tracking methodology (ie.

Screen resolution, time to laze, must laze until target kill etc)

What are the system dimensions and weight?

Describe the networking/remote operating capabilities of the system, taking into account external C2 & sensor connection

What is the required number of operators? Is there a minimum or maximum number?

Describe the ability to operate at night or poor visibility (i.e. heavy fog)

Describe the system’s ability/options/limitations to engage 4+ (Swarms) sUAS in a short period of time (expected to be limited by existing

APKWS lazing requirement)

How many times can the system be fired before it’s required to be reloaded?

Describe/list the engagement success rate by target group type. Provide any live fire test data target speed. Provide any live fire test data target altitude. Provide any live fire test data

Describe/list the engagement success rate based on other factors (day/night, wind speed, number of targets, etc.). Provide any live fire test data

Provide an overview of required facilities, space, and power requirements for this system.

Number of personnel needed to install system?

Estimated Setup time?

Describe operator equipment required (tablet, workstation etc.)

Describe multi-mission capability (if applicable).

Describe the full system maturity. Provide

Technology Readiness Level (TRL) and your calculation file (reasoning) for the system.

Describe if there are any dependencies on external sensors for the system

Describe/List any systems or external hardware required for operation.

What data formats does the system generate, process, or export? What data formats does the system ingest?

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, thumbdrive or USB hard drive, etc.)

Does your system interface with any existing

C2 applications?

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

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?)

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])

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

Describe/list the systems resistance capabilities to shock, dirt, water, and temperature. Has the system gone through formal environmental testing?

Describe/list the operational weather limitations

(max wind speed, min/max temperature of operating environment, etc.) for the laser & launcher

Provide documentation if able.

Does the system require/has your system received an ATO?

(elaborate as needed)

What cyber hardening and testing have been done on the system?

Provide a description of any tracking functions

(video tracker, slew-to-cue functionality, etc.)

included in the system and any optimization for a particular detection role (marine, aircraft, vehicles, personnel).

Describe (if applicable) the imaging capabilities (black hot/white hot, color palettes, optimizations, etc.)

Has the system previously been integrated with the Air Force SUADS/MEDUSA system?

What would it take to do so? i.e (cost, time, efforts?)

Does the system have any autonomous engagement capabilities (e.g., automatic target tracking, autonomous lazing, autonomous launch)

Does the system and/or operator have the ability to prioritize targets based on threat level or other criteria?

Is there a method to confirm target identification prior to launch?

Is an operator required to confirm launch

Can the intercept be terminated after launch and what is the result (self-destruct, parachute, parabolic path etc.)

What protocols/standards does the system adhere to for communication with external sensors and C2 systems (e.g., STANAG, MIL-

STD)

What is the estimated lifespan of key components (e.g., laser, launcher)?

What are the recommended maintenance intervals for the system?

What level of training is required for personnel to perform basic maintenance tasks? - Is there a formal training curriculum for operators and maintenance personnel?

What are the safety considerations related to laser operation (e.g., eye safety, range safety)?

What are the specific requirements for site preparation and grounding… (power, terrain leveling, open space requirements trees, buildings..)

SOFTWARE

Please briefly describe software.

Does it rely on specific or unique hardware?

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

List any certificates the software has received.

List certifications the software is currently receiving.

Pricing, Support, & Sustainment

Where can the Government purchase your system?

Has your system been offered, sold, or leased to the General

Public?

Are there any existing

Government-wide Acquisition

Contract (GWAC), open solicitation, or other vehicle that this work could be performed under, or would a new source selection be more appropriate?

Provide available Government contracts and POCs if able to.

Provide price 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 if system is provided in stock/original configuration

Desired System State (DSS):

Provide cost per unit shipped if components are reduced only to what is needed for power, mobility, networking, lazing and launching (i.e. ready to be integrated with existing gov’t C2 and sensors)

Based on DSS above: Provide any reductions in price that may result from larger quantity buys.

Based on DSS above: What is the lead time to acquire one unit?

Based on DSS above: What is the lead time to acquire 30 units?

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

Provide any warranty/RMA information

Provide price for on and offsite

Field Service

Representative/Field Service

Engineer (FSR/FSE) support.

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 whether all components comply with TAA regulations

List any limited life items, or replaceable/serviceable items

(filters, batteries, etc) in the system.

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

What training/familiarization information is available?

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

Are any specialized training materials required or available for the system?

Is your system covered by a specific Security 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.)

Can this system operate

Unclassified, or does it require a

Classified environment/network?

(please explain)

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

Describe the storage/transportation/logistics of the system.

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

Documentation List

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

- Technical Data

- Generic layout of external interfaces

- Interface Control Document (ICDs), System Design Document (SDD), System Requirements Document (SRD), or any other applicable documents that describe the design and interfaces.

- System architecture diagram

- Pricing Models

- Test Data/Results

- Failure Analysis

- HERO, HERF, HERP

- Copy of DD2345

- JF-12, if applicable

- Include a brief (i.e. no more than but approximately 1 page total) description of your organization’s quality control, risk management, and safety practices as they would be applied to this effort.

- Any other additional documents