Distributed LVC Integration and Cross-Facility Connectivity Architecture
Overview
Buyer
Place of Performance
NAICS
PSC
Set Aside
Original Source
Timeline
Qualification Details
Fit reasons
- NAICS alignment with historical contract wins in similar service areas.
- Scope strongly matches core technical capabilities and delivery model.
Risks
- Past performance thresholds may require one additional teaming partner.
- Potential clarification needed on staffing minimums before bid/no-bid.
Next steps
Validate eligibility requirements, assign capture owner, and schedule partner outreach to confirm teaming strategy before submission planning.
Quick Summary
The 96th Test Systems Squadron (96 TSSQ), under the Department of the Air Force, is conducting a Request for Information (RFI) for a Distributed LVC Integration and Cross-Facility Connectivity Architecture. This RFI seeks industry feedback and technical insight to develop a secure, synchronized, and scalable data exchange architecture for advanced weapons test activities across the Eglin Gulf Test and Training Range (EGTTR). Responses are due May 15, 2026.
Scope of Need
The Government aims to establish a unified, secure, and scalable architecture to overcome current limitations of isolated, facility-specific configurations. Key objectives include:
- Distributed Live–Virtual–Constructive (LVC) connectivity across multiple test nodes.
- Time-synchronized data distribution and event coordination.
- Multi-domain access control and controlled data release.
- Configuration management and version control.
- Monitoring, logging, and health management of distributed links.
- Interoperability with existing modeling, simulation, and test systems.
Information Requested
Respondents should provide input on:
- Technical Approach: Proposed architecture, timing/synchronization methods, data distribution, access control, configuration management, and integration strategies.
- Demonstrated Capability & Past Performance: Verifiable experience in distributed test or LVC environments, technical maturity (TRL 7 threshold, TRL 8 objective), objective performance metrics, and deployment history.
- Vendor Qualifications: Corporate experience, technical staff qualifications, cybersecurity maturity, and multi-domain/multi-node architecture experience.
- Risks, Dependencies, and Assumptions: Technical risks, dependencies, and cybersecurity considerations.
- Rough Order of Magnitude (ROM): Cost bands for prototype, integration, and sustainment, along with schedule assumptions.
Response Requirements
Responses must adhere to a 10-page maximum core response including an Executive Summary, Technical Approach, Requirements Traceability Matrix, Risks and Assumptions, and ROM Cost and Schedule. Optional attachments (10 pages/slides) and an optional slide deck (15 slides) are permitted. A mandatory System-of-Interest (SoI) Isolation Rule requires vendors to describe only components relevant to the distributed LVC integration architecture. Responses will be considered non-responsive if they fail to meet TRL 7, lack verifiable past performance, provide only conceptual capabilities, fail to isolate the SoI, or exceed page limits.
Contract & Timeline
- Type: Request for Information (RFI) / Sources Sought
- Set-Aside: None specified
- Response Due: May 15, 2026, 8:00 PM EDT
- Published: May 14, 2026
Additional Notes
This is for market research and planning purposes only and does not constitute a solicitation or commitment to award a contract. The Government will not reimburse respondents for costs incurred. Proprietary information should be clearly marked. All submissions become U.S. Government property.