DON26BZ05-NV076 TITLE: Open, Layered, Yielding Modular Platform for Unified Systems
COMPONENT TECHNOLOGY PRIORITY AREA(S): Sustainment
PROJECTED CMMC LEVEL REQUIREMENT: Level 2 (Self)
The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), 22 CFR Parts 120-130, which controls the export and import of defense-related material and services, including export of sensitive technical data, or the Export Administration Regulation (EAR), 15 CFR Parts 730-774, which controls dual use items. Offerors must disclose any proposed use of foreign nationals (FNs), their country(ies) of origin, the type of visa or work permit possessed, and the statement of work (SOW) tasks intended for accomplishment by the FN(s) in accordance with the Announcement. Offerors are advised foreign nationals proposed to perform on this topic may be restricted due to the technical data under US Export Control Laws.
OBJECTIVE: Transform maritime domain awareness and operational efficiency by developing a unified, modular, and open architecture platform that integrates shipboard systems and technologies.
DESCRIPTION: The current operational portfolio encompasses a large and diverse set of systems, many of which were developed piecemeal over time. This fragmented development history poses significant challenges to both sustainment and modernization efforts. The use of multiple, disparate systems performing similar or identical functions has resulted in a complex and costly "logistics tail", extensive technical documentation, and redundant training programs. This duplication increases costs, reduces efficiency, and heightens the risk of obsolescence. Additionally, the lack of commonality between systems hinders the integration of new capabilities and technologies, as each system requires unique modifications. This slows innovation and limits the ability to leverage advancements in automation, artificial intelligence (AI), and digital engineering. Ultimately, the lack of interoperability within portfolio creates a fragmented, inefficient, and costly development and sustainment environment, negatively impacting warfighter readiness and effectiveness.
To address these challenges, PMA-213 is developing a portfolio-wide architecture, referred to as Zeus, which functions as a system of systems (SoS). Zeus will provide a modular and open digital and hardware framework capable of delivering varying levels of service and functionality based on specific mission requirements. This architecture will enable data fusion, redundancy, and seamless integration of individual apertures and below-deck infrastructure, tailored to each ship’s mission set. By adopting an open and modular design, Zeus will support future cost savings, accelerated modernization, and enhanced interoperability across the fleet. OLYMPUS is a sub-project of Zeus focusing on the below deck ship infrastructure.
OLYMPUS will enhance situational awareness, streamline decision-making, and improve fleet-wide interoperability through advanced data fusion, real-time analytics, and secure communication networks. By leveraging cutting-edge technologies such as AI, machine learning (ML), and digital engineering, OLYMPUS will ensure naval operations are resilient, adaptive, and capable of addressing emerging threats in complex and context environments.
In addition to operational benefits, OLYMPUS aims to achieve significant long-term cost savings and cost avoidance across portfolio by increasing commonality in parts, enabling quantity buys, and simplifying maintenance requirements. For example, standardizing hardware procurement to allow the purchase of twenty-five (25) computers for use across five systems, rather than five different computers for five systems. These efficiencies will impact all air-capable fleet platforms, including CVNs, L-Class ships, and DDGs, optimizing readiness and sustainment across the fleet.
The transition of OLYMPUS technology and architecture will primarily occur through routine sustainment efforts and technology refreshes within. With government ownership of the majority of data rights for the affected portfolio, the technology developed through this SBIR effort can be gradually fielded over time via Engineering Change Proposals (ECPs). This approach ensures a smooth and cost-effective transition while enabling the Navy to modernize its systems and maintain maritime superiority.
PHASE I: Assess the technical, operational, and economic feasibility of the OLYMPUS system. Key activities include:
1. Preliminary Analysis and Scope Definition:
Conduct a detailed analysis to define the scope, objectives, and requirements of the feasibility study. Evaluate existing technologies and their compatibility with the proposed modular and open architecture system.
2. High-Level System Design and Architecture:
Develop a high-level design and architecture for the OLYMPUS system, outlining its modular framework, data fusion capabilities, and integration pathways for shipboard systems.
3. Proof-of-Concept (PoC) Demonstrations:
Perform PoC demonstrations for critical components to validate initial concepts and assess their functionality in representative operational scenarios.
4. Comprehensive Risk Assessment:
Identify potential technical, operational, and integration challenges. Develop mitigation strategies to address risks associated with system development and deployment.
5. Feasibility Report:
Compile findings into a detailed feasibility report, including technical recommendations, risk mitigation strategies, and a roadmap for Phase II development. The report will provide actionable insights to guide the next phase of the effort.
The Phase I effort will include prototype plans to be developed under Phase II.
PHASE II: Develop and test a prototype of the OLYMPUS system to validate its design and performance. This includes designing and building a prototype system based on the high-level architecture established in Phase I and integrating key components such as sensors, processing units, user interfaces, and communication networks. Laboratory and field testing will be conducted to evaluate system performance, interoperability, and resilience. Based on test results and stakeholder feedback, the system design will be refined. Detailed technical documentation and training materials will be developed to support system deployment and operation. A comprehensive test report will be prepared to summarize the findings and provide recommendations for full-scale deployment.
PHASE III DUAL USE APPLICATIONS: Transition the OLYMPUS system from prototype to operational deployment. Activities will focus on final system refinement, production readiness, and integration into operational environments. The system will be deployed in coordination with transition partners to support operational evaluation and adoption. Manufacturing, installation, and configuration processes will be established to support scalable deployment. Training and technical support will be provided to ensure effective system operation and sustainment. Feedback from operational use will be incorporated to support continuous improvement. Documentation developed during Phase II will be finalized to support long-term operation, maintenance, and sustainment, and deployment outcomes will inform broader implementation and commercialization efforts.
The OLYMPUS system has strong commercial potential in private sector applications that require integrated sensing, data processing, and reliable communication capabilities to support monitoring, decision-making, and operational efficiency. Potential dual-use applications include infrastructure monitoring, industrial operations, transportation systems, and emergency response environments where real-time data integration and system resilience are critical. The system’s modular architecture supports adaptation to commercial use cases with minimal modification, enabling scalability across multiple industries. Commercial deployment opportunities exist in environments that require improved situational awareness, system reliability, and coordinated operations. Lessons learned through DoW deployment and operational testing will support commercialization by reducing technical risk and demonstrating system effectiveness in demanding operational environments.
REFERENCES:
KEYWORDS: MOSA; Systems Engineering; Ship; Common; Computing; Interfaces; Architecture
TPOC 1 : Mark Worth
(240) 298-4833
mark.b.worth.civ@us.navy.milTPOC 2 : Stephen Alexander
(540) 688-8389
stephen.alexander33.civ@us.navy.mil
** TOPIC NOTICE ** |
The Navy Topic above is an "unofficial" copy from the Navy Topics in the DoW FY-26 Release 5 SBIR BAA. Please see the official DoW Topic website at www.dodsbirsttr.mil/submissions/solicitation-documents/active-solicitations for any updates. The DoW issued its Navy FY-26 Release 5 SBIR Topics pre-release on August 5, 2026 which opens to receive proposals on August 26, 2026, and closes September 23, 2026 (12:00pm ET). Direct Contact with Topic Authors: During the pre-release period (August 5, through August 25, 2026) proposing firms have an opportunity to directly contact the Technical Point of Contact (TPOC) to ask technical questions about the specific BAA topic. The TPOC contact information is listed in each topic description. Once DoW begins accepting proposals on August 26, 2026 no further direct contact between proposers and topic authors is allowed unless the Topic Author is responding to a question submitted during the Pre-release period. DoD On-line Q&A System: After the pre-release period, until September 9, 2026, at 12:00 PM ET, proposers may submit written questions through the DoW On-line Topic Q&A at https://www.dodsbirsttr.mil/submissions/login/ by logging in and following instructions. In the Topic Q&A system, the questioner and respondent remain anonymous but all questions and answers are posted for general viewing.
DoW Topics Search Tool: Visit the DoW Topic Search Tool at www.dodsbirsttr.mil/topics-app/ to find topics by keyword across all DoW Components participating in this BAA.
|