This solicitation closed on September 23, 2026
View current Department of Defense opportunities →Dynamic Open Systems Enclave
AI Overview
This RFP seeks an open-architecture software and hardware toolkit to rapidly modernize legacy aircraft by delivering processed sensor data to operators in real-time. The solution bypasses slow manual processes to improve pilot situational awareness and accelerate fielding of next-generation capabilities while maintaining airworthiness standards.
This summary is AI-generated from the official solicitation.
Key Details
Official Description
The U.S. faces a critical shortfall in its ability to rapidly deploy weapons and software to modernize legacy jets. The existing sensor-to-sensor process is excessively slow, manual and inefficient, hindered by flawed data links and difficult edge processing, failing to meet inflexibility, and critical FY26 modernization requirements that are preventing the U.S. from effectively countering rapidly evolving threats. As more systems gain connectivity, the amount of battlefield data becomes overwhe...
Change History
Informational change · Status
Dynamic Open Systems Enclave
Status changed from status: Open to status: Closed.
Dynamic Open Systems Enclave
Q&A Changes Summary
Updated Answer to Q1 (3 sub-questions): Clarified that OSE receives growing pub/sub traffic from aircraft buses for edge compute applications; confirmed target/threat display on both tablet and aircraft; stated software must meet 3U VPX form factor requirement; emphasized OSE prioritizes software by mission necessity before flight.
Updated Answer to Q2: Explicitly confirmed complementary solutions (e.g., MUM-T HMI) within OSE architecture are welcome, not just data fusion; encouraged new edge compute use cases.
No new questions added. Answers to Q3-Q7 remain unchanged.
Dynamic Open Systems Enclave
Q&A Changes Summary
New Question Added: Q1 clarifies own-ship PVT/orientation data sourcing, ethernet packet conversion requirements, Phase II display expectations (tablet/PVI demonstration vs. edge processing validation), and OSE hardware form factor preferences (3U VPX hosting options).
Renumbered Questions: Previous Q2-Q6 renumbered to Q2-Q7 due to new Q1 insertion.
Key Clarification: New Q1 addresses critical technical ambiguity regarding data conversion architecture (ethernet vs. 1553 bus integration) and hardware packaging constraints for production deployment.
Dynamic Open Systems Enclave
Changes to Q&A Section:
One new question added (Q1) clarifying solution scope: government will accept complementary OSE solutions that enable operator interaction with COP without requiring full data fusion capability. All other questions and answers remain unchanged; previous Q2-Q5 are now renumbered Q2-Q6.
Dynamic Open Systems Enclave
Q1 received a substantive answer addressing: (1) data conversion to ethernet/OMS/UCI messages for OSE consumption; (2) initial display integration limited to tablets, PVI, or general entity messages; (3) SDR hardware options including 3UVPX formfactor, TileMini, ARC-210, or MIDS radios; (4) OMS as primary open architecture standard with A-GRA alignment required.
Dynamic Open Systems Enclave
Q1 was significantly expanded from a simple waveform question into a comprehensive multi-part query covering: F-16 legacy bus architectures/protocols, cockpit display constraints and OFP limitations, SDR/radio specifications for BLOS mesh networks, and open architecture standards (OMS, FACE) for multi-platform scalability to F-15EX and F-35. No new answers were provided to address these detailed technical requirements.
Dynamic Open Systems Enclave
Status changed from Pre-Release to Open
Dynamic Open Systems Enclave
This Q&A clarifies that solutions must integrate with Starlink and Link 16 data sources, and leaves open whether proposals should work with existing aircraft communications hardware or provide standalone external systems—applicants should address this architectural approach in their proposals.
Dynamic Open Systems Enclave
Content updated for: qanda_content. Unable to compare - new version data not captured.
Dynamic Open Systems Enclave
This Q&A clarifies that Direct to Phase II applicants should adapt the standard Appendix A Technical Volume template for Phase II work while demonstrating equivalent Phase I progress, providing guidance on proposal structure that wasn't previously explicit.
Dynamic Open Systems Enclave
New opportunity: Dynamic Open Systems Enclave
Similar Opportunities
Get Alerts for Opportunities Like This
RallyProp monitors thousands of funding sources and sends instant alerts when opportunities match your technology and capabilities.
Start Free Trial