DON27TZ02-NV004 TITLE: Validated Modular Autonomy for Undersea Multi-Vehicle Coordination
COMPONENT TECHNOLOGY PRIORITY AREA(S): Integrated Network Systems-of-Systems;Trusted AI and Autonomy
PROJECTED CMMC LEVEL REQUIREMENT: Level 2 (Self)
OBJECTIVE: Develop software modules for existing autonomous undersea vehicles that support and extend existing system autonomy with multi-vehicle coordination behaviors.
DESCRIPTION: Autonomous undersea vehicles performing expeditionary missions require state-of-the-art cooperative sensing and engagement capabilities. The Navy seeks to enhance those capabilities with modular software designed for reliability and operational effectiveness. The advancement sought is development of a modular coordination layer extending existing single vehicle with decentralized multi-vehicle behaviors to enable autonomous decision making under degraded communications, sensing, and PNT conditions.
The software prototype needs to take in mission requirements provided by existing Navy command and control (C2) systems and sensor data provided by multiple platforms and use those inputs to coordinate mission performance with other vehicles. It should be compatible with modular unmanned autonomy architectures already in use by the Navy, such as the Open Autonomous Underwater Vehicle (OpenAUV) architecture and the Robot Operating System 2 (ROS 2). Within those architectures, the prototype must interface with existing autonomy designed for single-vehicle operations with minimal changes to already established systems. When the prototype is disabled or unnecessary, vehicle performance and behavior must conform to what would be expected of an unmodified single vehicle.
The multi-mission management functions of the software prototype need to use a decentralized C2 scheme that is robust in low-information environments and that degrades gracefully if communications or sensing are limited. The C2 scheme must demonstrate sufficient scalability to effectively manage many vehicles: tens to hundreds. Real-time C2 is a must.
The prototype should assume the primary sensing mode of each vehicle is acoustic. Realistic sensors include forward-look and side-scan sonar, possibly with a synthetic aperture. Cameras may be available, but if so, their field of view should not be assumed to allow for keeping other vehicles in sight. Realistic communications include acoustic modems with transmission rates of 5000 bps or less, possibly much less. Communications methods with higher transmission rates are unlikely to be available and may only be possible at extremely close range.
The prototype should assume that access to radar and satellite systems is extremely limited or non-existent. In particular, the prototype should not depend on regular access to global positioning system (GPS) data, and it should take into account the possibility that each vehicle is subject to position, navigation, and timing errors that increase in magnitude as each mission progresses.
The software prototype must include as an essential component a method of continuous validation that establishes and quantifies risk and trust for all autonomous decision-making, with an emphasis on repeatability. Deliverables must include the documentation and software necessary to implement this continuous validation method, as well as a report quantifying the efficacy of the method.
The ideal prototype will be mission agnostic, instead focusing on a generalized set of multi-vehicle behaviors and objectives.
The software prototype should minimize potential negative impacts on mission effectiveness, vehicle endurance, vehicle survivability, and operator workload. The prototype can include enabling hardware, provided that such hardware can be installed on existing autonomous undersea vehicles. The complexity of any vehicle modifications should be minimized. The prototype software and any accompanying hardware should also minimize their overall power consumption. Deliverable reports should include analysis identifying and quantifying any such impacts.
PHASE I: Develop a concept for an architecture for a prototype multi-vehicle mission module. Ensure that this architecture should provide an approach for decomposing missions into generalized multi-vehicle behaviors and objectives. Identify and design a method of continuous validation that establishes and quantifies risk and trust for autonomous decision-making. Provide required deliverables that include prototype module architecture designs; documentation for the method of continuous validation; and analysis of how those approaches attain the topic’s goals, including both academic research and validated modeling and simulation.
PHASE II: Develop a method of continuous validation and determine the extent to which that method can quantify risk for autonomous decision-making, including repeatability analysis. Validate the method itself against a series of reference vehicles running a set of standard missions.
Using the proposed method of continuous validation, develop the prototype software module. Analyze its performance on one or more reference vehicles running standard autonomy. Base the analysis on modeling and simulation, component-level testing, laboratory tank tests, and at least one in-water test outside of a laboratory environment.
Demonstrate reliability and operational effectiveness in subsea environments with low-bandwidth communications.
Prepare a Phase III commercialization/transition plan.
PHASE III DUAL USE APPLICATIONS: Assess the performance of the prototype method of continuous validation as it would be used by Fleet stakeholders for their autonomous vehicles. Modify the method as necessary in response to Fleet feedback and any discrepancies between expected and actual performance. Complete the prototype software module, any associated hardware, and the documentation necessary for integration into modular unmanned autonomy architectures already in use by the Navy.
REFERENCES:
KEYWORDS: Autonomous; Autonomy; Continuous Validation; OpenAUV; Robot Operating System; ROS; ROS2; Validation
TPOC 1: Joseph Walsh
joseph.d.walsh25.civ@us.navy.milTPOC 2: Tory Cobb
james.t.cobb8.civ@us.navy.mil
** TOPIC NOTICE ** |
The Navy Topic above is an "unofficial" copy from the Navy Topics in the DoW FY-27 Release 2 STTR 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-27 Release 2 SBIR Topics pre-release on November 4, 2026 which opens to receive proposals on December 2, 2026, and closes January 6, 2027 (12:00pm ET). Direct Contact with Topic Authors: During the pre-release period (November 4, through December 1 , 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 December 2, 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 December 16, 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.
|