Request for Information (RFI): Fire Control Sensor Market Availability

2026.06.03 AMEND 0001 - REVISE TITLE TO: Request for Information (RFI): Fire Control Sensor Market Availability

1. Introduction

The United States (U.S.) Army Contracting Command-New Jersey (ACC-NJ), Picatinny Arsenal, NJ 07806-5000, on behalf of U.S. Army Combat Capabilities Development Command (DEVCOM) Armaments Center (AC), is conducting market research to identify potential sources for a sensor system capable of tracking both outbound projectiles (7.62mm, .50 cal) and inbound threats from small Uncrewed Aircraft Systems (UAS) (Group 1 and 2). This RFI is being issued to gather information on existing concepts and technologies that can meet this need. The ideal solution will be small, lightweight, and affordable.

The proposed sensor, which may include radar, Electro-Optical/Infra-Red (EO/IR), or other active/passive technologies, must be suitable for both stationary and on-the-move operations. It should be configurable for mounting on a variety of Army ground combat vehicles, including:

• High Mobility Multipurpose Wheeled Vehicle (HMMWV)
• Bradley Fighting Vehicle
• Stryker
• Abrams Tank
• Joint Light Tactical Vehicle (JLTV)
• Next-Generation Combat Vehicles

ITAR RESTRICTION NOTICE: The subject matter of this RFI may be considered a “critical technology” and is therefore subject to International Traffic in Arms Regulations (ITAR) restrictions.

DISCLAIMER: For Informational Purposes Only

This notice is for market research and is NOT a Request for Proposal (RFP). This RFI does not constitute a solicitation or a commitment by the U.S. Government. Responses are not offers, and the Government is under no obligation to award a contract or provide funding for any information submitted. All participation is strictly voluntary, and no funds are available to pay for the preparation of responses.

2. Technical Requirements

The following outlines the minimum (Threshold) and desired (Objective) capabilities for the sensor system.

1. Inbound Threat Tracking
   
   1. Threshold (Minimum) Requirement: The system must be able to search, detect, and track multiple inbound Group 1 & 2 UAS while the vehicle is on the move. This capability must be provided without any external cue. A self-cuing system with an alert/cue mode or sensor, coupled with a higher accuracy tracking mode or sensor, is an admissible solution. The optimal angular search region is 360° in Azimuth and 60° or more in Elevation; achieving this with multiple, limited-coverage sensors on the same platform can be a solution, depending on size and cost. For the purposes of this RFI, “on the move” is defined as the vehicle traveling with constant linear motion on a flat roadway at speeds up to 35 mph. The response should comment on the system's capability to accept external INS data and operate under conditions of both moving platform and remote weapon system kinematics.
   2. Objective (Desired) Requirement: The system should independently detect threats without an external cue and provide the required information to the system.
2. Simultaneous Tracking
   1. Threshold (Minimum) Requirement: The system must detect and track inbound threats (Group 1, 2 UAS) at a range of at least 1000m while also tracking outbound 7.62mm or .50 cal projectiles from a weapon system on the platform.
   2. Objective (Desired) Requirement: The system should detect and track multiple inbound threats (Group 1, 2 UAS) at a range greater than 1000m while also tracking outbound 7.62mm or .50 cal projectiles from multiple weapon systems, whether on or off the platform.
3. Track Accuracy & Data
   1. Threshold (Minimum) Requirement: The system must provide fire-control quality data sufficient for a hit-to-kill engagement of a single threat. This required data includes position, velocity, and time (PVT). The tracking data update rate must be greater than 5Hz, and the system must be able to interface with external command and control in real time.
   2. Objective (Desired) Requirement: The system should provide position, velocity, and time (PVT) data to a closed-loop Fire Control System (FCS) to enable the hit-to-kill of multiple simultaneous threats (up to at least 20). The data should be provided for multiple threats present simultaneously, which are to be engaged sequentially by the same gun. If the sensor supports multiple guns, simultaneous engagements are possible, which would require tracking outgoing projectiles from each weapon, though the data need not be referenced to each gun. Targets may be close together in angle and range, with typical spacing between drones being less than 10 meters.
4. Size, Weight Requirement (Minimum): The system must be at most 30 inches in any plane and have a maximum weight of 70 lbs.

3. White Paper Submission Guidelines

Interested parties are requested to submit a white paper with the following specifications:

Format                                White paper, limited to 15 pages.

Executive Summary           A 1-page summary must be included.

Technology Readiness      Submissions should focus on systems at Technology Readiness Level (TRL) 5 or 6. Justification for the TRL assessment must be provided. Concepts not yet at TRL 5/6 may be included if they have a detailed development path to achieve TRL 6.

Performance & Risk           Include sensor performance predictions (e.g., Blake charts for radar), size, weight, power, an assessment of all technical risks, and recommendations for technical mitigations for major hurdles.

Cost & Production             Provide projections for development and production costs (lot of 100), broken down to the major subsystem level. Include an estimated cost for a complete technical data package and identify opportunities for cost reduction.

Data & Credibility              Support performance and cost projections with credible information, such as past test results, modeling and simulation data, live-fire test results, or existing program cost data.

Prototypes                          Note any available prototype hardware/software systems that are ready for near-term live-fire testing.

Company Information        Provide the firm's name, address, CAGE Code, point of contact (with phone number and email), and business size (small/large) based on the relevant NAICS code.

4. Response Instructions

• Deadline: Responses must be submitted within thirty (30) calendar days from the date of this publication.
• Email for Electronic Submissions & Questions: kristina.l.catalano.civ@army.mil

Please Note: Phone inquiries will not be addressed. All technical questions must be submitted in writing via email. While all questions will be reviewed, the Government reserves the right to share any questions and answers that impact the RFI with all participating parties.