Forward Counter Unmanned Aircraft Systems Command and Control (FCUAS C2) System

PROBLEM STATEMENT

The growing threat of adversarial unmanned aircraft systems (UAS) poses a significant global risk to critical infrastructure and force concentrations. Current command and control (C2) systems are not optimized to address the speed at which kill chain decisions (detect, track, identify/ assess, defeat) must occur to counter unmanned systems. As the UAS threat increases, a single operator conducting air defense operations may be overwhelmed. The threat challenges the observation, orient, decision, and act (OODA) process for human decision-makers defending against aerial threats. The rapid evolution of the threat means new sensors, capabilities and effectors are being developed, faster than they can be integrated into C2 systems.

PROPOSED SOLUTION



To counter this ever-increasing and adaptive threat, the DoD seeks a tactical edge based C2 system that enables a single operator to manage multiple targets and is capable of fire control providing the ability to rapidly adapt to counter swarms of unmanned systems along with other potential manned or unmanned system threats. The solution should reduce operator cognitive load and accelerate the decision process to conduct multiple simultaneous kinetic and/or non-kinetic engagements, be easy to operate and can quickly integrate additional data sources, capabilities, sensors, and effectors and be able to operate autonomously if needed.

Minimal viable solution for initial demonstration and test will integrate the Ku-band Radio Frequency Systems (KuRFs) radar, Coyote Effector, and LIDS (low, slow small unmanned aircraft integrated defeat system) and potentially other Product Manager C-sUAS systems.

Primary Attributes:

System

• Operate solely on a laptop, tablet or other portable system as a single piece of hardware, with no external communication for additional processing power or services to support mobile and tactical operations
• Utilize or ingest sensor data for detection, tracking, and identification/ characterization and be capable of automated creation of engagement plans and providing fire control for various systems to include effectors such as kinetic, directed energy (DE), and electronic warfare, and attack UAS (interceptors).
• Support automated identification and classification of targets, weapons pairing, prosecution of target, and assisting the user with pairing the best sensor with the best effector option for threat(s).
• Software shall be able to support a minimum of 2,000 tracks at 4Hz while maintaining minimal processing and communication latency (limited impact on hardware resources).
• Support ability to conduct fratricide avoidance and airspace deconfliction.
• Mitigates interference of electronic warfare systems.
• Support track cueing and track forwarding. 

Interoperability and Connectivity

• Support rapid integration of new sensors and effectors by 3rd parties, to support bringing new or emerging capabilities with little change to the software architecture. 
• Operate on both classified and unclassified networks.
• Communicate with other subsystems (i.e. sensors, effectors) using IP-formatted mesh-network radios in a modular open systems approach.
• Interoperate with Forward Area Air Defense (FAAD) legacy or emerging fielded C2 systems that may be co-located or local to the protected area for the purpose of maintaining a shared air picture.
• The C2/ Fire control solution must be capable of determining and displaying available missile systems (i.e. Coyote Block 2 or 3), kinetic systems (e.g. Land-based Phalanx Weapon System), electronic warfare systems, and directed energy systems, providing the operator with optimal weapon to target pairing.
• Supports a single integrated air picture (SIAP) in which all sensors (local and external) feed a C2 air picture utilizing correlated tracks (MIL-STD-6016C correlation criteria).
• Communicates with FAAD to maintain a shared air picture with other Program of Record systems (i.e., Maneuver - Short Range Air Defense (M-SHORAD) and Land Based Phalanx Weapon System (LPWS)).
• Supports a master-client construct consisting of multiple operators, but one master.

Additional Information:

• This prototype will require several field exercises and will include integrating with existing sensor and effector systems and executing a full kill chain in a live fire CUAS test event projected for the summer of 2025. 
• Companies are expected to demonstrate their solution in an unclassified environment as part of the Commercial Solutions Opening. Companies are expected to be able to interface with a Government provided simulation tool, Correlated Defense System of Systems Simulation (CDS3) to demonstrate their solution in an unclassified environment as part of the Commercial Solutions Opening process.
• The program currently uses a MILDEF RB14 laptop, there is a desire for the future solution to be able to operate on these computers.
• Offerors must be eligible for a COMSEC account and demonstrate the ability to maintain National Information Security Program standards. Security requirements for any resultant contract will be a facility cleared to the Secret level with authorization to store COMSEC items and individuals with clearance eligibility to the Secret level. A sufficient number of individuals will require access to COMSEC. Potential solutions sought shall have full National Security Agency (NSA) approved Type-1 and Advanced Encryption Standard (AES) level encryption capability.
• Companies are welcome to apply individually, however partnerships are recommended.
• Preference will be given to submissions that present a comprehensive and compelling solution to the entire AOI. Submissions should identify whether the submitter will employ subcontractors and, if so, which companies for which capabilities. 
• However, companies that have an innovative approach to specific aspects of the AOI are encouraged to submit. Such companies, if selected, may be asked to arrange a prime / subcontractor relationship with other submitters to ensure the delivery of an integrated solution. 

Teaming/Partnerships

The Government encourages teaming for responses to this Area of Interest. The government may seek to team companies with AI/ML solutions with companies that are integrators in the counter uncrewed systems technology space. Traditional defense contractors are reminded that under 10 USC 4022, that if you do not qualify as a non-traditional company that the government will seek either a one-third cost share in the prototyping effort or that significant work is being performed with a non-traditional partner.

Responsible AI (RAI)

All projects will be expected to comply with DIU's Responsible AI Guidelines and other DoD AI frameworks. Companies are encouraged to read the guidelines and develop a plan for implementation, which may be presented as part of the submission. Particularly relevant issues for this project include:

• Transparency and explainability of AI-generated content and recommendations
• Mitigation of potential biases in training data or model outputs
• Approaches for human oversight and ability to override AI systems
• Security and privacy protections for sensitive planning information
• Ethical considerations around AI's role in consequential military decision-making

The Statement of Work will require that the guidelines are followed in order to be eligible for a letter of completion and transition.