RFI - Mobile CsUAS - 06 Aug 2026.docx

1. Notice This Sources Sought Synopsis (SSS)/Request for Information (RFI) is issued for informational purposes and market research only; it does not constitute a solicitation or a Request for Proposal (RFP). The Government will not reimburse any company or individual for any expenses associated with preparing or submitting information in response to this posting. The information provided may be used by the Government in developing its acquisition strategy, statement of work/statement of objectives, and/or performance specifications. Interested parties are responsible for adequately marking proprietary or competition-sensitive information contained within their response.

2. Background and Scope The U.S. Army Product Manager Soldier Defense Systems (PdM SDS) is conducting market research to identify possible sources capable of providing Counter Small Unmanned Aircraft Systems (C‑sUAS) solutions targeting Group 1 and Group 2 threats.

Interest is specifically focused on mobile, ruggedized technologies to provide full kill-chain capability to detect, track, identify, decide, and defeat enemy UAS. Solutions must be capable of integration with the Infantry Squad Vehicle (ISV) variants (ISV-U and ISV-9) to provide a mobile, layered protection approach at the platoon and squad echelons. The Government is prioritizing readily available commercial off-the-shelf (COTS) products, modified COTS, or developmental items capable of achieving full production within six (6) months of the closing of this RFI. Any developmental system must be supported by a concise and attainable development and commercialization plan without participation or funding from the Government.

3. Required Capabilities Respondents must address their system's ability to meet some or all of the following capability requirements:

3.1. C-sUAS Kill Chain Performance

Detect, Track, Identify, & Decide: Ability to detect, track, positively recognize and/or identify, and decide how to engage enemy Group 1 and Group 2 UAS threats in various environmental conditions while on the move or at the halt.

Defeat Mechanisms: Provide kinetic, non-kinetic, or a layered combination of defeat mechanisms to neutralize identified threats while minimizing collateral damage.

Command and Control (C2): Intuitive user interface with the ability to integrate with existing Army network architectures and tactical C2 systems (e.g., ATAK, Nett Warrior).

3.2. Platform Constraints & Integration (ISV-U and ISV-9)

Modularity: Capabilities must be adaptable for integration onto the ISV-U and/or the ISV-9 platforms. The ISV-U is envisioned as a modular payload carrier at the platoon echelon, while the ISV-9 is a troop mobility vehicle primarily utilized at the squad echelon.

Installation: Bolt-On/Bolt-Off (BoBo) installation requiring minimal platform modification are preferred. Considerations should include both BoBo solutions and “last line of defense” capabilities that remain employable even if primary BoBo systems fail or are dismounted.

Platform constraints: Solutions must adhere to the primary platform constraints of the ISV-U and ISV-9, managing payload capacity, dimensional limits, and center-of-gravity considerations.

The ISV-U has a flat 48.5-inches by 65-inches cargo bed (48.5-inches by 76.8 inches with the tailgate open) capable of accommodating equipment and has 16 equidistant through-holes, 4 recessed MIL-STD 5k lbs tie-downs, as well as adjustable bed rail lash points. Cargo capacity is 1,450 lbs.

The ISV-9 does not have a dedicated cargo bed. CsUAS equipment must be capable of attaching directly to the rollover cage.

3.3. Power & Electrical Architecture

External Power Source: Systems with external power sources are strongly preferred. External ruggedized power sources must factor, and not exceed, the Size, Weight, and Power (SWaP) constraints of the platform.

Integration Limits: Solutions seeking to integrate with the ISV’s internal power must strictly adhere to the 53-amp sustained output limit of the Vanner Equalizer. These solutions must be compatible with the ISV power flow architecture (alternator → equalizer → 12V/24V batteries) and must effectively utilize available onboard power sources, including a 2,000W inverter, standard 120V outlets, and a 100A 24V bus bar, without overloading the vehicle's baseline systems.

3.4. Survivability & Environmental Profile

Ruggedization: Must be capable of operating in austere tactical environments, matching the mobility and off-road profile of the ISV without sustaining damage.

SWaP: Optimized SWaP footprint to maintain the ISV's tactical mobility and transportability (e.g., sling load, internal transport). Bed payload cannot exceed 1450 lbs.

4. Instructions to Potential Respondents Interested parties who desire to participate in this SSS/RFI are encouraged to submit responses demonstrating they presently possess the technology, expertise, and qualifications to provide the capabilities described above.

Response Parameters:

· Maximum of five (5) pages in 12-point font size (Note: Video links may be provided and will not count against the page limit)

· PDF format

4.1. Corporate Overview (A)

General information regarding the firm, including Point of Contact (POC), location, CAGE code, business size, and special socioeconomic designations (e.g., 8(a), WOSB, HUBZone, SDVOSB, etc.). State whether the company is domestically or foreign-owned (if foreign, indicate the country of ownership).

4.2. Technical Capability (B)

Describe the capability of your product(s) and provide detailed product information and specifications. Explicitly describe how your product(s) meets the desired performance requirements and platform constraints listed in Section 3. If proposing development to integrate existing or new subsystems, clearly detail your engineering approach and timeline.

4.3. Supporting Evidence (C)

Responses may include, but are not limited to, the following supporting materials:

Pictures and conceptual drawings.

Architecture and system views.

Known associations or connectivity with other military end items/systems.

Summarized test results or historical data to support performance claims.

Please note that any supporting evidence included in your submission will count towards the required 5 page limit.

4.4. Rough Order of Magnitude (ROM) (D)

Provide a rough cost estimate based on optimum or varied pricing quantities and associated lead times. Provide confirmation of the ability to deliver two (2) prototype/evaluation units within three (3) months after receipt of an order. (Note: This is strictly for Government budget planning purposes and will not be considered a formal bid or binding in any manner).

4.5. Relevant Experience/Contracts (E)

Indicate whether the proposed technology:

1. Has been previously evaluated by a Government organization (Department of War (DoW), Homeland Security, etc). If so, provide a Government POC. If previously evaluated by the DoW, indicate whether a cyber-security Authority to Operate (ATO) or Interim Authority to Test (IATT) was granted, or if a Safety Release was issued, if known.

2. Can be obtained under an existing Government contract (e.g., GSA, OTA, IDIQ). If so, provide the respective contract number(s) and Government POC.

4.6. Commercial Availability (F)

Indicate whether the company currently provides this type of technology as a commercial solution. State whether this item has been sold, leased, or licensed to the general public. Additionally, indicate whether all materials used are in compliance with the Buy American Act and Berry Amendment (10 U.S.C. 2533a), as applicable.

5. Submissions Responses must be submitted via email or DoD SAFE link to the POC listed below by the listed closing date.

William Lloyd: william.a.lloyd6.ctr@army.mil Collin Bright: collin.j.bright.civ@army.mil Rusty Jarrett: normand.c.jarrett.civ@army.mil Alejandro Silva: alejandro.a.silva.ctr@army.mil

6. Notice

THIS IS NOT A NOTICE OF REQUEST FOR PROPOSAL (RFP) ISSUANCE.

This request is issued solely for the purpose of exchanging information and conducting market research to allow industry to best communicate their capabilities to the Government. Responses to this request are voluntary and will not affect any contractor's ability to submit a proposal if, or when, an RFP is officially 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. The Government will not pay for any information and/or materials received in response to thi RFI and is in no way obligated by the information received.