Work With Us - Commercial Companies - Submit Solution
CUAS Close-In Kinetic Defeat Enhancement
We look forward to your solution —
To submit, scroll to the form at the bottom of this page.
Project Description
Area of Interest (AoI)
Endpoint Accuracy 2: CUAS Close-In Kinetic Defeat Enhancement
The Department of War (DoW) is seeking innovative technologies to enhance the lethality of integrated weapons and fire control systems, with a focus on improving effectiveness of Remote Weapons Systems (RWS) against Unmanned Aerial Systems (UAS) in support of the Counter-UAS (C-UAS) mission. Part One focuses on the integration of hardware and/or software that enables Aided Target Recognition (AiTR) (also known as Aided Target Detection and Recognition, AiTDR) to improve existing RWS capabilities. Part Two and Three will evaluate new RWS stations and next-generation enhancements to existing small arms systems. Part Four focuses on integrating and enhancing capabilities that enable weapon systems to fully connect and synchronize with sensors, fire control, targeting, and command-and-control systems, operating as part of a coordinated, networked kill chain rather than as standalone platforms.
Part 1
This initiative aims to integrate Aided Target Recognition (AiTR) functionality into current Remote Weapon Systems (RWS), specifically the Common Remotely Operated Weapon Station (CROWS). The primary objective is to accelerate the engagement timeline, initially focusing on Unmanned Aircraft Systems (UAS), with a secondary focus on other threats like vehicular and man-sized targets.
The desired AiTR system must offer passive detection, classification, ranging, and tracking of UAS targets, whether the RWS is stationary or on-the-move, during both daytime and, preferably, nighttime conditions. This capability will provide the operator with enhanced situational awareness and enable more effective engagement.
Passive detection and classification will be handled by the AiTR system. AiTR classification will assist the RWS operator with determining threats versus non-threats while minimizing false positives. The AiTR system needs to operate effectively even in cluttered background conditions, both natural and man-made. This system may incorporate additional sensors to enhance existing capabilities, provided their Size, Weight, and Power (SWaP) are compatible with the RWS station's base platform, use case, and constraints. Upon initial AiTR detection, target tracking may be performed using the RWS’s existing video output. The solution must achieve reliable target tracking while minimizing latency. While passive ranging is preferred, limited-duration active ranging may be acceptable. Overall the AiTR system must account for adverse conditions such as shake from weapon firing, muzzle flash, and high frequency jitter from the base vehicle platform.
Key characteristics for the integrated AiTR system include:
- Seamless integration with current RWS architectures.
- An open system design to ensure future scalability and interoperability.
- Improved target discrimination to minimize collateral damage.
- A reduction in operator workload and cognitive burden through automated target handling.
- The technology must demonstrably improve the RWS’s ability to optimally detect (~600m) accurately, track and engage at no less than ~100m both stationary and maneuvering (primarily incoming) UAS targets against dynamic Group 1 & 2 UAS moving at moderate speeds (<30 m/s) or faster.
- In the event of AiTR system malfunction or degradation, the RWS should revert to standard operational capabilities without any performance loss.
- Must have human-in-the-loop functionality.
Part 2
For Part Two, the Department of War (DoW) intends to either acquire a new system or substantially modify existing RWS and small arms systems. The goal is to enhance performance to achieve Counter-Unmanned Aerial Systems (C-UAS) capability on both moving and stationary platforms, including ground and maritime environments, while also maintaining and improving the system's effectiveness against traditional Remote Weapon System (RWS) targets. Future efforts may include scaling the system for different caliber weapons and integration with networked sensor and fire control systems.
Key characteristics for the C-UAS capability include:
- In addition to the criteria in Part One, the weapon system prototype must be able to be fired in land and maritime environments, rather than just a laboratory setting at time of pitch.
- Ability to engage and hit a Group 1 UAS moving laterally to the weapons system at 7m/s at a range of 50-200 meters.
- Ability to execute multi-target engagements.
- For RWS systems, full (360 degree) range of motion.
- For RWS systems, demonstrate -10 degree to 90 degree (direct overhead) range of elevation.
Part 3
For Part Three, the DoW intends to modify existing small arms systems to support dismounted C-UAS defeat. This may involve the scaled application of technologies from Part Two as well as the introduction of additional system enhancements to improve effectiveness against aerial threats. The goal is to enhance individual warfighter lethality by improving accuracy-to-decision through advanced fire control and projectile guidance. Desired solutions include systems capable of deflecting or self-aiming standard-issue rounds to increase hit probability against manually selected, transient targets, while integrating networked sensor and small arms fire control systems. Must be adaptable to dismounted legacy small arms, scalable across calibers and configurations, and maintain baseline weapon performance in the event of system degradation or failure. A semi-automatic, live-fire capable prototype is required.
The C-UAS solution must enable the ability to engage and hit a Group 1 UAS moving laterally to the weapons system at 7m/s at a range of 50-200 meters.
Part 4
Part Four aims to enhance battlefield lethality through the integration and improvement of sensor data, communications, and fire control systems. Key goals are: improved passive targeting, mutual sensor utilization, and communication between fire control and weapon systems. A commercial wireless edge network architecture that bridges to military systems and the reverse is essential across all stages of this effort to manage data transfer from sensors and weapon/fire control systems. This required network must:
- Be Capable: Integrate both RF and IP-based transport layers and support operations in both terrestrial and maritime domains.
- Be Secure: Employ post-quantum encryption protocols, enable packet-level data protection, and control access through tiered decryption keys.
- Prioritize Domestic Infrastructure: Data transit should utilize U.S./domestic company-controlled infrastructure wherever feasible.
- Ensure Compatibility and Efficiency: Deliver sensor data in formats compatible with existing DoD-supported visualization, geolocation, and analysis software. To conserve bandwidth, edge-based analysis of relevant data may be necessary before network transmission.
- Be Team Awareness Kit (TAK) compatible.
Eligibility Requirements
Solicitation Requirements and Important Considerations
The CSO phase two (pitches) requires vendors to deliver an in-person pitch. Vendors will be required to conduct a live-fire range demonstration of their product after the prototyping phase. Fully developed systems applying to Part Two and Three will be asked to conduct a demonstration on a live fire range of their system as part of the CSO downselect.
Demonstration and Validation
If selected, the effort will involve a series of demonstrations. These will culminate in a live-fire validation to effectively assess the solution's tracking performance under operational conditions.
Proposal Submission
Vendors must clearly specify which of the four parts their solution addresses. While these parts can be executed concurrently or in any sequence, proposals may be submitted for one, multiple, or all parts. Crucially, submissions must indicate the Part(s) being addressed on the first page. Only one submission per vendor is permitted. Fully AI generated submissions will be rejected.
Key Requirements
- Ethical AI Adherence: All AI-enabled solutions must strictly comply with the DoD AI Ethical Principles; non-compliance will result in immediate disqualification.
- Open System Architecture: Solutions must be built upon an open system architecture.
- Intellectual Property: Proposals must clearly demonstrate ownership or provide appropriate licensing and data rights for all proposed technologies.
- Excluded Submissions: Proposals from purely research organizations, resellers, and integrators will not be considered.
- Registration: Vendors who do not currently possess a Commercial and Government Entity (CAGE) code must register in the System for Award Management (SAM) to receive a prototype agreement
- Collaboration: The Government reserves the right to encourage collaboration among vendors with complementary capabilities to optimize overall results.
- Parts: All four parts may occur at the same time.
Demonstrations
- Commercial solution(s) in Part One should be ready for full-scale system testing, demonstration, and evaluation within three months from project start date.
- Part One vendors will provide on-site and remote support during the on-base system testing, demonstration, and evaluation period.
- Part Two should be ready for demonstration within three months of project start date.
- Demonstrations for Part Three will be determined during prototype development.
Awarding Process
DIU
Before You Submit
What we recommend you include when you submit a solution brief.
When you submit to a DIU solicitation, we'll ask you to include a solution brief. Here's some guidance about what that entails.
Potential Follow-On Production Contract for Prototype Other Transaction Agreements
Companies are advised that any Prototype Other Transaction (OT) agreement awarded in response to this solicitation may result in the direct award of a follow-on production contract or agreement without the use of further competitive procedures. Follow-on production activities will result from successful prototype completion.
The follow-on production contract or agreement will be available for use by one or more organizations within the Department of Defense. As a result, the magnitude of the follow-on production contract or agreement could be significantly larger than that of the Prototype OT agreement. All Prototype OT agreements will include the following statement relative to the potential for follow-on production: “In accordance with 10 U.S.C. § 4022(f), and upon a determination that the prototype project for this transaction has successfully been completed, this competitively awarded Prototype OT agreement may result in the award of a follow-on production contract or transaction without the use of competitive procedures.”
Common issues with submissions
If you are having problems uploading your AOI submission to DIU, it may be one of these common issues with submitting, click here for solutions to common submission issues.
Have a question about this solicitation?
Need clarification? Having technical issues?
Reach out to our team.
Submission Form
Please fill out the following form in its entirety.
*Required
We Work With You
If we think there’s a good match between your solution and our DoD partners, we’ll invite you to provide us with a full proposal — this is the beginning of negotiating all the terms and conditions of a proposed prototype contract.
After a successful prototype, the relationship can continue and even grow, as your company and any interested DoD entity can easily enter into follow-on contracts.
Our Process
We solicit commercial solutions that address current needs of our DoD partners. (View all open solicitations and challenges.
You send us a short brief about your solution.
We’ll get back to you within 30 days if we’re interested in learning more through a pitch. If we're not interested, we'll strive to let you know ASAP.