What project 2904 buys
Navy Maritime Maintenance Enterprise Solution (NMMES) is the Information Technology (IT) toolset currently utilized to execute ship and submarine maintenance in the Naval Shipyards (NSY), Regional Maintenance Centers (RMC), Ship Repair Facility (SRF) Japan, Intermediate Maintenance Facilities (IMF), Forward Deployed Regional Maintenance Center, Pearl Detachment - Guam, and commercial industrial sites worldwide. These maintenance activities support Fleet operations 24 hours per day, 7 days per week. The NMMES IT solution is used by over 40,000 civilians and military who conduct over $10.2B of ship, aircraft carrier, and submarine maintenance and modernization on an annual basis. The NMMES program includes sustainment as well as multiple modernization efforts to ensure the continued effectiveness of the Fleet maintenance IT toolset. These efforts consist of adding mandatory enhancements, such as Financial Improvement and Audit Readiness (FIAR) changes and aligning with the Standard Accounting Budget Reporting System (SABRS) and Navy Enterprise Resource Planning (ERP) system requirements as the general ledger. The NMMES program provides for software changes, retiring and/or replacing of costly legacy applications, transition planning, and systems engineering for integration with existing and future solutions. These efforts align with direction to ensure that proposed interim solutions support and facilitate the transition to the planned maintenance solution end state. This program will provide modernization, migration, testing, and consolidation of obsolete IT tools and code base to the next generation of centrally hosted tools supporting Fleet Maintenance systems for the Navy. Funding for NMMES addresses critical deficiencies and minimizes the inherent risks that a catastrophic failure would be to fleet readiness. The funds are required to support the modernization of products that are on outdated software, align maintenance applications and processes with evolving shipbuilding techniques, and enhance the existing applications to make them cloud capable. The implementation of Internet of Things (IoT) for modern industrial capabilities is also driving the requirement.
- Support
Project 2904 funding, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 20.3 |
| FY2026 | Enacted | 19.5 |
| FY2027 | Request | 20.8 |
| FY2028 | Outyear | 23.0 |
| FY2029 | Outyear | 23.3 |
| FY2030 | Outyear | 23.2 |
| FY2031 | Outyear | 23.7 |
12 accomplishments / planned programs
The R-2A exhibit — the only level of the budget that describes work that has not happened yet. Activities carry the prior, current and budget year only, no five-year plan. Coverage is partial across the corpus, so count activities, never total them.
FY2027 planned work Complete agile configuration and testing. Train end users and implement SMMS solution.
FY2026 to FY2027 change FY26 to FY27 decrease based on estimated completion of SMMS in Q1FY27.
FY2026 plans — current year Begin agile configuration and testing (System and UAT) of SMMS. Maintain MAT support until all material documents closed (to include contracts). Sustainment of current SMMS application. Complete Phase 2 requirements gathering. Begin Phase 2 analysis and design.
FY2027 planned work Continue consolidating required functionality of selected local naval shipyard applications that extend functionality beyond the aging shipyard IT systems. Continue to enhance the MSE suite of applications and implement local application functionality as older government made software is re-platformed or replaced with commercial off-the-shelf (COTS) software. Improve product support with consolidated functionality in fewer software applications.
FY2026 to FY2027 change FY26 to FY27 increase due to the additional backlog of local applications at the Naval Shipyards and increased capacity to rationalize into NMMES corporate frameworks.
FY2026 plans — current year Consolidate required functionality of selected local naval shipyard applications that extend functionality beyond the aging shipyard IT systems. Continue to enhance the MSE suite of applications and implement local application functionality as older government made software is re-platformed or replaced with commercial off-the-shelf (COTS) software. Improve product support with consolidated functionality in fewer software applications.
FY2027 planned work Begin transition from Solaris SPARC infrastructure to Amazon AWS RDS.
FY2026 to FY2027 change FY26 to FY27 increase to begin migration of the NMMES database from on-prem to AWS cloud, Maritime CHE.
FY2026 plans — current year Continuing / completing cloud architecture development and continue database optimization for applications within the cloud environment.
FY2027 planned work Continue the migration of applications to the cloud.
FY2026 to FY2027 change FY26 to FY27 increase to support NMMES application migration to cloud by end of FY27.
FY2026 plans — current year Continue the build out of updated Secure Cloud Computing Architecture (SCCA) and migration of NMMES applications from on-prem data centers to a virtualized environment.
FY2027 planned work Continue Digital Crew Board enhancements and integration with the shop floor information system toolset.
FY2026 to FY2027 change FY26 to FY27 increase by $900K to support integration and testing with additional NMMES toolsets.
FY2026 plans — current year Continue Digital Crew Board enhancements and begin integration with the shop floor information system toolset.
FY2027 planned work Continue expansion of the Business Intelligence Platform capability as a key component of the Logistics IT (LOG-IT) u-NNPI sub hub for Logistics Integrated Development Environment (L-IDE).
FY2026 to FY2027 change FY26 to FY27 increase due to expansion of data analytics capabilities supporting the intermediate and depot ship maintenance community.
FY2026 plans — current year Expand usage of the Business Intelligence Platform (BIP) data analytics toolset (Qlik) to further exploit self-service visualization and reporting. Expand capability as a key component of the Logistics IT (LOG-IT) u-NNPI sub hub for Logistics Integrated Development Environment (L-IDE).
FY2027 planned work Support the stabilization and sustainment of the NFS application by performing development required to address user request post-implementation.
FY2026 to FY2027 change FY26 to FY27 decrease due to implementation of NFS in FY26.
FY2026 plans — current year NFS implementation will occur in May 2026 in Maritime CHE. Development and operations support stabilization and sustainment of the current NFS software application. Additional analysis, development and project management support will be required as requirements for Navy ERP+ are identified that will require adjustments to NFS.
FY2027 planned work Continue the expansion of mobility solutions to enhance the capabilities and usability of NMMES applications on mobile platforms throughout the Naval Shipyards and Regional Maintenance Centers.
FY2026 to FY2027 change FY26 to FY27 increase to support application and user requirements for solutions.
FY2026 plans — current year Identify electronic controls required to secure information on mobile devices. Define technical attributes to support the expansion to include wearable devices, as well as expand to video and voice from inside ship hulls.
FY2027 planned work Finalize data integration and manipulation standards, policies, and practices to support COLUMBIA Class, FORD Class, and VIRGINIA Block V.
FY2026 to FY2027 change FY26 to FY27 increase due to discrete requirements from the acquisition and ship maintenance program offices.
FY2026 plans — current year Support configuration, integration, and testing activities of the 3-D product model pending program office requirements definition. Correct deficiencies identified during the testing processes. Initiate deployment in alignment with the rest of the NMMES modules as usable features become available. Expand deployment capability across the NAVSEA community from the initial localized deployment sites.
FY2027 planned work Continue development of solution that allows shipyard supervisors to more efficiently track time for employees.
FY2026 to FY2027 change FY26 to FY27 increase due to delayed start until FY27 due to supporting other priorities.
FY2026 to FY2027 change FY26 to FY27 decrease due to completion of requirements in FY26.
FY2026 plans — current year Continue work with OEM scheduling product vendor to configure product enhancements based on data analysis and continuous improvement process requirements. Complete the design and software modifications necessary to implement CCPM. Determine implementation roadmap and begin deploying to activities.
FY2026 to FY2027 change FY26 to FY27 decrease due to completion of project in FY26.
FY2026 plans — current year Continue development and testing of the final version of SPF. Begin transitioning the product to sustainment.