ARTS-V3 Third-Party Software Initiative

1. Introduction and Purpose The United States Air Force is seeking information on industry capabilities for the Advanced Radar Threat System (ARTS) Variant 3 (V3) Variable Aperture Digital Radar (VADR) [ST1] Third-Party Software initiative. This RFI seeks input from industry to: Understand existing commercial and near-term planned capabilities relevant to the development of software for advanced threat emulation for systems like ARTS-V3. Attract both traditional and non-traditional defense contractors. Gauge industry interest in the proposed C5 structure. Refine the acquisition strategy for this software approach 2. Program Background: The ARTS-V3 program develops highly channelized digital Active Electronically Scanned Array (AESA) radar systems to emulate and replicate advanced adversary threat systems. As a ruggedized, closed-loop threat emulator, ARTS-V3 functions as a representative adversary fire control or multi-functional ground-based radar. It is designed with a high degree of hardware and software flexibility, allowing it to incorporate various adversary radar models to simulate how adversaries counter and adapt to contested environments. 3. Proposed OTA Consortium Structure The Government is executing this modernization effort utilizing the Consortium for Command, Control, and Communications in Cyberspace (C5) Other Transaction Authority (OTA) agreement, pursuant to 10 U.S.C. § 4022. Managed by the Consortium Management Group (CMG), this OTA framework significantly compresses acquisition timelines compared to traditional FAR-based contracts. The ARTS-V3 program will issue Requests for White Papers (RWPs) directly to the C5 member base, leveraging an established ecosystem of technology innovators. Eligibility: Interested parties must be members of the C5 consortium to receive awards. Registration: Information on joining can be found at the CMG C5 Overview Portal https://cmgnetworks.org/become-c5-member/ 4. Key Principles for Participation Prospective partners must adhere to the following principles: System Integration: Partner with the Lead System Integrator (LSI) to manage configurations, integrate legacy baselines, test code compliance, and perform post-deployment troubleshooting. Establish formal communication channels with the LSI. MBSE Compliance: Deliver and maintain technical baselines as dynamic, digital model elements using Cameo/SysML. The Government will provide necessary Government Furnished Information (GFI). DevSecOps & Cyber: Utilize the Government's cloud-based software factory and automated CI/CD pipelines. All developments must align with Zero-Trust Architecture (ZTA) and Department of War (DoW) cybersecurity requirements. Development Isolation: Do not reuse, copy, or integrate proprietary code from adjacent vendors. Maintain strict separation between ARTS-V3 ("Red") systems and friendly ("Blue") systems; no cross-system technology reuse is permitted. Cost-Sharing: Provide a one-third (33.3%) cost-share of the total project cost if operating as a traditional DoW vendor acting as the prime performer. 5. Scope of Work, Technical Requirements, & Desired Capabilities Successful partners must demonstrate deep expertise in developing, updating, and integrating advanced threat implementations into the ARTS-V3 system using rigorous, modern software engineering practices. 5.1 Scope of Work & Required Technical Capabilities Radar Integration & DSP: Integrate existing radar or transmit-only reactive models into the ARTS-V3 system. Partner must demonstrate an understanding of radar physics, Electronic Warfare (EW) principles, and the optimization of Digital Signal Processing (DSP) algorithms. Notional Example: Development of software to emulate an emerging X-band threat for an initial capability release. Software Updates & RTOS: Update and maintain existing radar software (e.g., streamlining calibration, improving tracking algorithms, and developing multi-target kinematic tracking filters). Development requires experience with Real-Time Operating Systems (RTOS) including VxWorks, real-time Linux, modern C++ (C++14/17/20), and hardware-accelerated computing (CUDA, OpenCL). C2 User Interface & Protocols: Update the Command and Control (C2) user interface software, specifically the VADR App (VAPP), with enhanced user interfaces or expanded range capabilities. Design open, non-proprietary APIs (REST, gRPC) aligned with Lead System Integrator (LSI) Interface Control Documents (ICDs) and ensure all messaging functions remain fully compatible with existing system protocols. AESA Resource Management: Develop and implement advanced beam-scheduling and power-management algorithms optimized for Active Electronically Scanned Arrays (AESA). Zero Trust Communications: Implement micro-segmentation and secure communications, enforcing mutual TLS (mTLS 1.3) using FIPS 140-3 validated cryptographic modules to exceed baseline DoW cybersecurity mandates. Modern Programming Practices: Utilize memory-safe programming languages (e.g., Rust, Go, Python, Java) where applicable. Deep working knowledge of C++ remains necessary to successfully utilize the Government Furnished Information (GFI) Software Development Kit (SDK). AI-Assisted Development & Safety: The use of AI coding tools is permitted, provided vendors prevent CUI/DoW data exfiltration. All AI-assisted logic must be clearly identified in an automatically generated Software Bill of Materials (SBOM), undergo strict Human-in-the-Loop (HITL) review, and pass Static (SAST) and Dynamic (DAST) Application Security Testing. AI-Optimized Algorithms: Ensure the development process for advanced tactical edge algorithms aligns directly with Cognitive Electronic Warfare (CogEW) methodologies. 5.2 Desired Capabilities The Government is highly interested in partners who can deliver next-generation enhancements, specifically: Advanced Digital Twin & Closed-Loop Emulation…