DON26BZ01-NV013 TITLE: AI-Assisted Modernization and Optimization of Theater Mission Planning Center (TMPC) Software
COMPONENT TECHNOLOGY PRIORITY AREA(S): Advanced Computing and Software
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: Develop an AI-driven toolset to automate the modernization of Theater Mission Planning Center (TMPC) software, focusing on refactoring legacy code, optimizing performance, integrating advanced cybersecurity, and ensuring compatibility with modern and next-generation mission systems.
DESCRIPTION: TMPC software is built on legacy code that presents challenges in maintainability, performance optimization, cybersecurity, and integration with evolving mission systems. Current modernization efforts rely on manual refactoring, which is time-consuming, error-prone, and costly. There is a critical need for an AI-driven capability to automate code refactoring, optimize computational efficiency, and integrate cybersecurity features without disrupting TMPC’s core functions. This effort will enable seamless software upgrades while maintaining backward compatibility with existing operational platforms.
The proposed solution will leverage machine learning (ML) and natural language processing (NLP) to analyze, refactor, and optimize TMPC’s codebase while preserving mission-critical functionalities. Additionally, AI-assisted software validation and security enhancements will ensure that modernized TMPC software meets the evolving requirements of Navy mission planning environments.
Work produced in Phase II may become classified. Note: The prospective contractor(s) must be U.S. owned and operated with no foreign influence as defined by 32 U.S.C. § 2004.20 et seq., National Industrial Security Program Executive Agent and Operating Manual, unless acceptable mitigating procedures can and have been implemented and approved by the Defense Counterintelligence and Security Agency (DCSA) formerly Defense Security Service (DSS). The selected contractor must be able to acquire and maintain a secret level facility and Personnel Security Clearances. This will allow contractor personnel to perform on advanced phases of this project as set forth by DCSA and NAVAIR in order to gain access to classified information pertaining to the national defense of the United States and its allies; this will be an inherent requirement. The selected company will be required to safeguard classified material during the advanced phases of this contract IAW the National Industrial Security Program Operating Manual (NISPOM), which can be found at Title 32, Part 2004.20 of the Code of Federal Regulations.
PHASE I: Conduct an analysis of TMPC’s existing software architecture to identify modernization needs. Develop conceptual AI-based models for legacy code analysis, refactoring, and cybersecurity integration. Demonstrate proof-of-concept AI-driven refactoring on a representative TMPC software component.
The Phase I effort will include prototype plans to be developed under Phase II.
PHASE II: Develop a prototype AI toolset for TMPC code modernization. Integrate cybersecurity enhancements and automated validation/testing. Conduct functional and performance testing and validation. Ensure compatibility with existing and next-generation TMPC hardware/software.
Work in Phase II may become classified. Please see note in the Description.
PHASE III DUAL USE APPLICATIONS: Bring the AI tool from prototype to full-scale, improving the speed, security, and cost-effectiveness of software upgrades.
The same technology that helps the Navy can also potentially help the private sector fix and secure older software more easily.
REFERENCES:
KEYWORDS: AI-assisted; Legacy Code; Machine Learning; Natural Language Processing; Tomahawk; Mission Planning
| 5/14/26 | Q. | What is the expected transition pathway for a successful solution, including the target program office or system owner? |
| A. | Pathway is TMPC within PMA-281 | |
| 5/14/26 | Q. | What are the specific success criteria for Phase I that would enable transition to Phase II? |
| A. | As the title suggest, a AI induced solution to a TMPC process that provides efficiency | |
| 5/14/26 | Q. | Are there representative datasets, simulation environments, or test harnesses available to evaluate modernization approaches without impacting operational systems? |
| A. | We can provide a VM of a TMPC build | |
| 5/14/26 | Q. | What are the most critical external systems or interfaces that TMPC must integrate with, and where are the highest integration risks? |
| A. | CANES, the ship backbone is one of the external interfaces. Comms are problematic at times as well. I am not sure how this question relates to the task at hand. | |
| 5/14/26 | Q. | What cybersecurity and accreditation requirements (e.g., RMF, STIGs) must be incorporated into the modernization approach? |
| A. | Solution will be subject to ECP process and ATO cybersecurity accreditation so yest to RMF and STIGs. | |
| 5/14/26 | Q. | What constitutes acceptable validation of AI-refactored code in Phase I, particularly regarding functional equivalence, performance, and security? |
| A. | Testing and performance | |
| 5/14/26 | Q. | What requirements exist for traceability and validation of AI-generated code changes to ensure mission assurance and accreditation? |
| A. | Regression, and Stig testing, and cybersecurity testing | |
| 5/14/26 | Q. | What level of human oversight is expected for AI-assisted code refactoring and validation (e.g., human-in-the-loop vs semi-autonomous workflows)? |
| A. | Until the product is verified, a lot of human involvement. Then once approved, ECP to baseline and less human involvement | |
| 5/14/26 | Q. | What AI/ML tools or platforms are currently approved for use within NAVAIR environments, and are contractors permitted to propose alternative models or approaches? |
| A. | This area is new, so approvals are to be | |
| 5/14/26 | Q. | What constraints exist for maintaining backward compatibility with existing operational systems during modernization? |
| A. | Yes, but the project will be geared that way | |
| 5/14/26 | Q. | How does the government prioritize outcomes across code refactoring, performance optimization, and cybersecurity enhancement? |
| A. | How fast, a process takes, or how did AI help in efficiency | |
| 5/14/26 | Q. | Which specific components or subsystems of TMPC are the highest priority for modernization under this effort? |
| A. | MDS | |
| 5/14/26 | Q. | Are there existing CI/CD or DevSecOps pipelines supporting TMPC, or is the current process largely manual? |
| A. | We are currently building a software factory with DEVSECOPS and Pipelines soo they should be in fresh when task gets awarded | |
| 5/14/26 | Q. | What build systems, dependency management approaches, and configuration management practices are currently used? |
| A. | We follow agile build processes and System Software and Engineering practices | |
| 5/14/26 | Q. | Are there specific legacy frameworks, proprietary libraries, or tightly coupled components that present the greatest challenges to modernization? |
| A. | MDS is the most notable. | |
| 5/14/26 | Q. | What operating systems, databases, and middleware platforms underpin TMPC today? |
| A. | We us linux and Microsoft OS, java, | |
| 5/14/26 | Q. | What primary programming languages and runtime environments are used within the TMPC codebase, particularly for mission-critical components? |
| A. | Since MDS is the largest, I will focus on that. Here is what I roughly know. MDS is 1.3M LOC ~103 projects, mostly C#, there is some Seq, and Javascript, the TED database 678K LOC C# 104 projects, other database cover 27K LOC C#, 48K SQL LOC. TMT(Tomahawk Management Tool) is 198K LOC C# & 332K LOC Javascript, & 48 LOC VB6, comprising 51 projects. There are 7 MS Visual studio solutions. And some other stuff | |
| 5/14/26 | Q. | What level of access will contractors have to the TMPC codebase, documentation, and representative test environments during Phase I? |
| A. | This will be discussed with awardees | |
| 5/14/26 | Q. | In what environments is TMPC currently developed, tested, and executed (e.g., NIPRNet, SIPRNet, JIWCS, standalone, others), and what development environments will be accessible during Phase I? |
| A. | This will be discussed with awardees | |
| 5/14/26 | Q. | Can the government provide high-level architecture artifacts for TMPC, including system structure, major components, and key interfaces, to inform where AI-assisted modernization can be applied with minimal operational disruption? |
| A. | We can discuss if awarded to you, but I am thinking a build VM and Some DRs or CRs | |
| 5/08/26 | Q. | What is the page limit for the Phase I Technical Volume (Volume 2) for topic DON26BZ01-NV013? |
| A. | The page limit for the Phase I Technical Volume (Volume 2) is not to exceed 10 pages. This requirement is specific to responding to DON SBIR/STTR Conventional Topics. As indicated in the DON instruction a template to use when responding can be found on our website, https://www.navysbir.com/links_forms.htm | |
| 4/27/26 | Q. | Is there an existing program of record or acquisition pathway that a successful Phase II/III solution would transition into, or is this being explored as a new capability? |
| A. | The SBIR here is intended to incorporate into the existing TMPC POR. However, any modernization effort here must be transferable to any new development | |
| 4/27/26 | Q. | The topic references maintaining compatibility with existing operational platforms. Are there specific interface standards, APIs, or data formats that must be preserved during the modernization process, or will those details be provided during Phase I execution? |
| A. | Platforms can take on many different meanings. The solution set here as part of the vender solution will be incorporated in the existing TMPC code most likely in the MDS code. The hardware utilized by the fleet may or may not be affected by this change. It really depends on the proposal and what SW build it ultimately gets into and utilized | |
| 4/27/26 | Q. | Are there specific cybersecurity frameworks or standards (e.g., NIST 800-53, STIGs, RMF) that the AI toolset should prioritize for integration, or is the offeror expected to propose the most appropriate framework as part of their solution? |
| A. | That an entity of its own. We would do require secure software utilizing RMF and seeking ATOs for each build that is fielded | |
| 4/27/26 | Q. | The topic mentions demonstrating AI-driven refactoring on a "representative TMPC software component." Will the Government provide a representative code sample or test dataset for Phase I, or should offerors plan to demonstrate their approach on a surrogate codebase that mirrors the expected complexity? |
| A. | I anticipate giving the vender a current MDS VM build and maybe some other candidate capability or deficiency requests which could benefit from an AI induced solution. | |
| 4/27/26 | Q. | Can you share any general information about the languages, frameworks, or architectural patterns currently used in the TMPC codebase? Understanding whether this is primarily C/C++, Java, Ada, or another technology stack would help us tailor our AI-assisted refactoring approach. |
| A. | That's a large question, Since MDS is the largest, I will focus on that. Here is what I roughly know. MDS is 1.3M LOC ~103 projects, mostly C#, there is some Seq, and Javascript, the TED database 678K LOC C# 104 projects, other database cover 27K LOC C#, 48K SQL LOC. TMT(Tomahawk Management Tool) is 198K LOC C# & 332K LOC Javascript, & 48 LOC VB6, comprising 51 projects. There is 7 MS Visual studio solutions. And some other stuff | |
| 4/24/26 | Q. | The solicitation document states CMMC Level 2 (Self) is an anticipated requirement. Is this a requirement for proposal submission or a contract requirement when awarded? |
| A. | Thank you for your question. This will be required at time of contract award. |
** TOPIC NOTICE ** |
The Navy Topic above is an "unofficial" copy from the Navy Topics in the DoW FY-26 Release 1 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 1 SBIR Topics pre-release on April 13, 2026 which opens to receive proposals on May 6, 2026, and closes June 3, 2026 (12:00pm ET). Direct Contact with Topic Authors: During the pre-release period (April 13, through May 5, 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 May 6, 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 May 20, 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.
|