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: Novel, closed-loop threat simulations for Software-in-the-Loop (SIL) and Hardware-in-the-Loop (HIL) testing.
• AI/ML for Sensor Fusion & Cognitive EW: Embedded tactical-edge capabilities to enhance sensor fusion and threat reaction times.
• Predictive Maintenance: Advanced algorithms utilizing real-time system telemetry and diagnostic data to predict component failures.
• Development & Analysis Ecosystems: Specialized radar development environments, code-writing assistance tools, novel radar applications, and robust system analysis tools.

GOVERNMENT FURNISHED INFORMATION (GFI)

  The Government will provide:

• Applicable threat data from intelligence community members.
• A Modular Threat Design and Development Template and documentation.
• Access to the following equipment for testing:
  • Subscale Threat System
  • Anechoic Chamber
  • Cloud-based radar testing Environment
  • Cloud-based Software code verification and Integration Environment
• Access to the following tools for collaboration:
  • ARTS-V3 VADR and VAPP Software Development Kits (SDK)
  • Containerization tools (e.g., Pod Manager, Docker, Kubernetes)
  • Cameo Models
  • Git repository and container registry (e.g., GitLab)

7. SECURITY

Facility: Respondents should describe their classified handling and storage capabilities. An active security clearance is required to access the subscale threat system.

Networks: Once under contract, personnel may need access to unclassified and classified networks up to SIPRNet (primarily for Cloud Access).

Future Requirements: Respondents do not necessarily have to have a Top Secret clearances nor SAP and SCI access, but the government would like to understand each respondent’s current and future security posture up to TS/SAR and/or TS/SCI including willingness to obtain clearances and estimated timeline.

8. INDUSTRY RESPONSE AND SUBMISSION INSTRUCTIONS:

The Air Combat Command (ACC) and other DoW organizations are supported by this project. The ARTS-V3 Program Office anticipates releasing a request for white papers through the C5 consortium as early as November 2026, with an estimated project award around June 2027.

Please submit responses electronically to Kristina Lenderman (kristina.lenderman@us.af.mil) and Tyler Newey (tyler.newey@us.af.mil) no later than 3 Aug 2026.

9. Submission Format:

Submissions should be Unclassified. If including restricted data, mark the cover page and each relevant page clearly.

Responses are limited to one (1) cover page and five (5) content pages.

Use size 12 Times New Roman font with one-inch margins.

Please provide the following information:

1. Company Name and Commercial and Government Entity (CAGE) code.
2. Point of contact details (Name, phone, email).
3. Interest as a prime performer or as a partner.
4. Agreement with NAICS 541511 (if not, suggest an alternative)
5. Number of personnel with security clearances on your envisioned software team.
6. Willingness to operate within the proposed OTA structure.
7. For traditional DoW vendors: your thoughts on a cost-sharing model.
8. Suggestions for the acquisition strategy.
9. Details of any Anechoic Chamber capabilities you possess.
10. Your security posture as referenced in Section 7.

10. SOFTWARE DEVELOPMENT CAPABILITIES QUESTIONS:

Respondents are required to submit a comprehensive capability statement. Submissions must directly address each of the four domains outlined below, structured exactly as defined.

10.1 Technical Capabilities & Experience

Respondents must detail their technical proficiency and past performance in the following areas:

• Radar Innovation & Intelligence-Based Models:
  • Detail your organization's experience with intelligence-based threat radar models.
  • Describe any existing radar products or novel software-defined capabilities/telemetry tools that could directly support the ARTS-V3 mission.
• Enterprise C++ & RTOS:
  • Describe your company's depth of experience migrating legacy codebases, using C++ (necessary for utilizing the VADR SDK and understanding the base system), and optimizing software for High-Performance Computing (HPC) and RTOS environments.
  • Also, list all the various software languages your company has experienced with. Please rate your proficiency with each language (i.e. C++ = 50%).
• Memory-Safe Languages & Zero Trust:
  • Describe your company's experience with memory-safe programming languages (e.g., Rust, Go, Python, Java, Swift, etc).
  • Outline your secure coding practices and experience securing sensor-to-C2 interfaces via mutual TLS (mTLS).
• C2 Software Development:
  • Describe your experience developing remotely operated C2 software and web applications (necessary to understand or utilize the VAPP SDK).
• Model-Based Systems Engineering (MBSE):
  • Describe your practical experience using Cameo or other SysML tools to drive agile system development and maintain technical baselines.
• AI Validation, Supply Chain & DevSecOps:
  • AI Tools & CUI Protection: If utilizing AI-assisted coding tools, specify which tools are used and detail your protocols to prevent CUI/DoW data exfiltration.
  • Validation Pipeline: Describe your DevSecOps pipeline for testing, validating, and scanning AI-generated code (SAST/DAST).
  • SBOM Generation: Detail your capability to produce an automated Software Bill of Materials (SBOM) that explicitly distinguishes between human-authored and AI-generated code.
  • Environment Operations: Detail your experience operating software and CI/CD pipelines within heavily restricted cloud environments (IL5+) and utilizing Kubernetes orchestration.

10.2 Security & Infrastructure Posture

Personnel Clearances: Provide the total number of personnel holding active Secret and Top Secret security clearances.

Facility Safeguarding: Detail your facility safeguarding capabilities (including SCIF/SAPF) and network access to SIPRNet.

Special Access Roadmap: Provide a detailed roadmap demonstrating your capability to operate within Special Access Program (SAP) environments and handle Sensitive Compartmented Information (SCI) data.

​​​​​​​10.3. Strategic Alignment & Cost-Sharing Structure

Cost-Sharing (Traditional Contractors Only): Proposed models, co-investment strategies, or financial structures to meet the statutory one-third (1/3) cost-sharing requirement under the OTA.

Acquisition Strategy Feedback: Provide actionable feedback, identify key risks, or offer suggestions regarding the proposed OTA strategy, software lifecycle timeline, and Intellectual Property (IP) approach.[JH9] 

11. POINTS OF CONTACT:

Kristina Lenderman

Agreements Officer

801-775-4427

kristina.lenderman@us.af.mil

Tyler Newey

Agreements Specialist

801-586-5097

tyler.newey@us.af.mil

Rajathi Noel

Program Manager

801-777-0598

rajathi.noel@us.af.mil

Eric Fink

Technical POC

777-0829

eric.fink.2.ctr@us.af.mil

12. DISCLAIMERS AND NOTICES

This is a Request for Information (RFI) for market research and planning purposes only. It is not a solicitation for proposals, and responses cannot be accepted by the Government to form a binding contract. Participation is voluntary, and the Government will not reimburse respondents for any costs associated with this RFI. All information submitted will be used for market analysis and will not be returned. Not responding to this notice does not preclude participation in any future solicitation.

All responses are limited to one cover page and five (5) pages, size 12 Times New Roman font, one-inch margins on all sides. Responses longer than one cover page and five content pages will only be read through the first five content pages.

13. GLOSSARY:

C2: Command and Control

Threat: Desire to emulate behaviors and functionality of a particular adversary Surface-to-Air system.

Radar Function Software: RFS is the collection of programs, algorithms, and computational tools that control a radar system's hardware, process the raw data it collects, and translate that data into understandable information for analysis and decision-making.