Real-Time Virtual Injection and Bidirectional Test Interaction Capability - Department of Defense

the Need The 96th Test Systems Squadron (96 TSSQ) is seeking industry input on technologies and architectures to support a real-time virtual injection capability enabling bidirectional interaction between simulated environments and real-world test assets across the Eglin Gulf Test and Training Range (EGTTR). This capability is intended to support advanced weapons test activities requiring deterministic, low-latency data exchange and closed-loop interaction. This announcement serves as a REQUEST FOR INFORMATION(RFI) only for the purpose of market research in accordance with Revolutionary Federal Acquisition Regulation (FAR) Overhaul part 10. This RFI is issued for planning purposes only and is not a Request for Proposal (RFP), an Invitation for Bid (IFB), or an obligation on the part of the U.S. Government to acquire any products or services. In accordance with (IAW) Revolutionary FAR Overhaul 15.101(c)(2), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract. The Government will not reimburse respondents for any costs associated with the prepa-ration or submission of the information requested. All costs associated with responding to this RFI will be solely at the responding party’s expense. Not responding to this RFI does not preclude participation in any future RFP, if issued. The Government reserves the right to reject or disregard, in whole or in part, any contractor’s input resulting from this RFI. This RFI does not constitute a solicitation for the proposals or the authority to enter into negotiations to award a contract. The information provided may be used by the Government in developing and acquisition strategy, a statement of work (SOW), statement of

objectives (SOO), or performance specifications. Any proprietary information or technology should be clearly marked. 1 2.

Background and Statement of the Need The Government is exploring approaches to enable real-time interaction between virtual and physical munitions and aircraft within test environments. This capability requires: • Bidirectional, low-latency data exchange • Deterministic timing and synchronization • Real-time fusion of simulated and real-world telemetry • High-assurance cross-domain data handling • Closed-loop interaction between virtual and physical systems Industry input is required to assess feasibility, identify technical risks, and refine architectural options. 3. Information Requested 3.1 Technical Approach • Proposed architecture for real-time virtual injection • Methods for achieving deterministic, low-latency bidirectional data flow • Approaches for real-time fusion of simulated and real-world telemetry • Cross-domain solutions for multi-caveat closed-loop interaction • Timing synchronization mechanisms • Integration with existing test and range infrastructure 3.2 Demonstrated Capability and Past Performance Respondents shall provide: • Verifiable past performance relevant to real-time or distributed test systems • Evidence of technical maturity (fielded systems, prototypes, accredited components) •

Objective performance metrics (latency, jitter, synchronization accuracy) • Deployment history and operational context • Points of contact who can validate claims 2 3.3 Minimum Technical Maturity (TRL Requirement) • Threshold: TRL 6 — System prototype demonstrated in a lab environment •

Objective: TRL 8 — Actual system completed and qualified 3.4 Vendor Qualifications Respondents shall describe: • Corporate experience with real-time or distributed test systems • Technical staff qualifications • Cybersecurity maturity and cross-domain experience • Experience supporting multi-domain or multi-node architectures 3.5 Risks, Dependencies, and Assumptions • Technical risks and mitigation strategies • Dependencies on distributed LVC integration services • Cybersecurity and cross-domain considerations 3.6 Rough Order of Magnitude (ROM) • Cost bands for prototype, integration, and sustainment • Schedule assumptions for phased capability delivery 4. Response Structure (Hybrid Model) 4.1 Required Core Response (10 pages maximum) 1. Executive Summary (1 page) 2. Technical Approach (5 pages) 3.

Requirements Traceability Matrix (2 pages) 4. Risks and Assumptions (1 page) 5. ROM Cost and Schedule (1 page) 3 4.2 Optional