Self-Healing Ship Systems

Navy STTR 21.A - Topic N21A-T014
ONR - Office of Naval Research - Mr. Steve Sullivan -
Opens: January 14, 2021 - Closes: February 18, 2021 (12:00pm EDT)

N21A-T014 TITLE: Self-Healing Ship Systems

RT&L FOCUS AREA(S): Cybersecurity

TECHNOLOGY AREA(S): Ground / Sea Vehicles; Information Systems

OBJECTIVE: Design self-healing computing systems for use on Navy vessels to keep a ship's primary functions operational in combat should the original computing system be damaged during an attack.

DESCRIPTION: What if, during combat, a ship is attacked by an enemy missile? The ship's physical weapon and propulsion systems are still intact but the computers that control them have been damaged. Ships cannot have several redundant racks of computers providing full operational capabilities as it is impossible to predict physical damage locations. Proposals simply based on virtual machines will not be considered competitive. What if other remaining computing platforms and network capabilities could be leveraged and prioritized to provide important functionality during combat? A commercial analogy would be a primary application runs on a user's laptop, but the user also has a smartphone and smartwatch. The laptop gets destroyed. The two remaining computing platforms could be leveraged to provide the primary functions of the original laptop application. A research institution can provide approaches such as mobile code, code analysis, and distribution of computing functionality.

PHASE I: Develop an approach and conduct a feasibility study on self-healing computing systems. Conduct analysis such as modeling and/or simulation. Provide a proof-of-concept demonstration with associated metrics of performance. The Proof of Concept should be able to identify key/essential components from the original application and successfully demonstrate how those components would execute on a system of lesser capabilities (processor, storage, and RAM) and distributed processing if necessary. The concept should also identify how to locate and migrate code around surviving computing and networking components left on the vessel. Develop a Phase II plan.

PHASE II: Prototype the concept using real hardware, applications, and networks. Conduct benchmark evaluations of the implementation. Analyze performance of remaining application as a function of computing platform and remaining code. Examine resultant network traffic for distribution and execution. Provide demonstration of prototype using scenarios of increasing complexity. Document approach, limitations, and metrics in final report.

PHASE III DUAL USE APPLICATIONS: In current commercial disaster contingency planning modalities, backup data is kept far away at one or more offsite locations. Bandwidth during normal operations is largely sufficient. Backup operations cells or centers for operations also may exist remotely elsewhere for resiliency. However, during natural or manmade disasters these approaches may be insufficient. This technology could be relevant to many commercial scenarios to include enterprise networks and cyber-physical systems that will require resiliency and survivability in a crisis.


  1. Simoncini, L. "Resilient computing: An engineering discipline." 2009 IEEE International Symposium on Parallel & Distributed Processing, Rome, 2009, pp. 1-1. doi: 10.1109/IPDPS.2009.5160867.
  2. Stoicescu, Miruna, Fabre, Jean-Charles and Roy, Matthieu. (2017). "Architecting Resilient Computing Systems: A Component-Based Approach for Adaptive Fault Tolerance. Journal of Systems Architecture." Journal of Systems Architecture, Volume 73, February 2017, pp. 6-16. 10.1016/j.sysarc.2016.12.005
  3. Wikipedia, the Free Encyclopedia. "Resilience."

KEYWORDS: Mobile code; system analysis and optimization; application resiliency; resilient computing


The Navy Topic above is an "unofficial" copy from the overall DoD 21.A STTR BAA. Please see the official DoD Topic website at for any updates.

The DoD issued its 21.A STTR BAA pre-release on December 8, 2020, which opens to receive proposals on January 14, 2021, and closes February 18, 2021 at 12:00 p.m. ET.

Direct Contact with Topic Authors: During the pre-release period (Dec 8, 2020 to January 13, 2021) proposing firms have an opportunity to directly contact the Technical Point of Contact (TPOC) to ask technical questions about the specific BAA topic. Once DoD begins accepting proposals on January 14, 2021 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.

SITIS Q&A System: After the pre-release period, proposers may submit written questions through SITIS (SBIR/STTR Interactive Topic Information System) at, login and follow instructions. In SITIS, the questioner and respondent remain anonymous but all questions and answers are posted for general viewing. Topic Q&A will close to new questions on February 4, 2021 at 12:00 p.m. ET

Note: Questions should be limited to specific information related to improving the understanding of a particular topicís requirements. Proposing firms may not ask for advice or guidance on solution approach and you may not submit additional material to the topic author. If information provided during an exchange with the topic author is deemed necessary for proposal preparation, that information will be made available to all parties through SITIS. After the pre-release period, questions must be asked through the SITIS on-line system.

Topics Search Engine: Visit the DoD Topic Search Tool at to find topics by keyword across all DoD Components participating in this BAA.

Help: If you have general questions about DoD SBIR program, please contact the DoD SBIR Help Desk at 703-214-1333 or via email at

[ Return ]