What the FY2027 request buys
Verbatim from the R-2A exhibit for project 3323 of PE 0608231N. This is the budget justification's own description of work that has not happened yet — the one thing no other level of the budget carries.
FY 2027 funding will provide continued execution under the Software Acquisition Pathway (SWP) and will continue iterative development of MTC2 software based on the SWP Capability Needs Statement (CNS). MTC2 will continue to field Ashore/Afloat. MTC2 will continue to receive feedback from fleet users for development, integration, and testing of additional capabilities/enhancements into Battle Management Aids (BMAs). MTC2 will continue iterative development and delivery to targeted platforms necessary for the completion of the Navy special project. The iterative delivery will include extended Battle Management Aids that will support strategic/tactical command and control as well as Joint All Domain Command and Control (JADC2) interfaces. MTC2 iterative delivery will include additional integration with other existing BMAs with data and service interfaces. These additional capabilities in MTC2 are necessary to meet the timeline of targeted strike group deployments. MTC2 will digitally enable the horizontal across Joint Forces and vertical across the Fleet and Echelons alignment of capabilities, the acceleration of MTC2 requirements and enablement of operational Battle Management Aids to enhance operational effectiveness during a wartime posture to procurement of Commercial off the Shelf (COTS) software, tools, integration, and services. In FY 2027 to support the acceleration effort for Rapid Operational Planning (OneBrief), funding will be utilized for the procurement of Commercial off the Shelf (COTS) software, tools, integration, and services. In addition, in FY 2027, MTC2 will support INDOPACOM's operations across three Pacific Fleet Maritime Operations Centers (MOCs).
FY 2026 to FY 2027 increase in the amount of $9.102M for Rapid Operational Planning (OneBrief) and MTC2 Tactical Planning Tool (TPT). This initiative digitally enables the horizontal alignment across the Fleet and vertical alignment across Echelons capabilities, the acceleration of MTC2 requirements and enablement of operational Battle Management Aids to enhance operational effectiveness during a wartime posture. Funds will be utilized for the procurement of Commercial Off the Shelf (COTS) software, tools, integration, and services and MTC2 will support INDOPACOM's operations across three Pacific Fleet Maritime Operations Centers (MOCs).
FY2026: the year under way
Prior-year accomplishments and current-year plans from the same exhibit. Context for the FY2027 plan, not a series — an activity partitions its project exactly in the request year, but can under-cover it in earlier years.
MTC2 continues development and deploy a containerized WebSked replacement, Employment Readiness Scheduler (EMPRESS), Minimal Viable Product (MVP). MTC2 will leverage existing Development, Security, Operations (DevSecOps) Pipelines. EMPRESS enables the Navy to conduct Unit Employment and Service Scheduling functions that support force readiness generation for planning/unplanning to maintain the Global Naval Force Presence Policy Schedule and Fleet Response Plan. MTC2 continues executing under the Software Acquisition Pathway (SWP) and continues iterative development of MTC2 software based on the SWP Capability Needs Statement (CNS). MTC2 continues to field Ashore/Afloat. MTC2 continues to receive feedback from fleet users for development, integration, and testing of additional capabilities/enhancements into Battle Management Aids (BMAs). MTC2 continues to provide iterative development and delivery to targeted platforms necessary for the completion of the Navy special project. The iterative delivery includes extended Battle Management Aids that will support strategic/tactical command and control as well as Joint All Domain Command and Control (JADC2) interfaces. MTC2 iterative delivery includes additional integration with other existing BMAs with data and service interfaces. These additional capabilities in MTC2 are necessary to meet the timeline of targeted strike group deployments.
Three years, and no five-year plan
An R-2A activity publishes the prior year, the current year and the budget year. The FYDP outyears exist at project and program-element level and are deliberately absent here rather than inferred. Estimate types are colored and never summed into one figure.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 8.4 |
| FY2026 | Enacted | 10.8 |
| FY2027 | Request | 19.9 |
This activity is 79% of project 3323's FY2027 request and 79% of PE 0608231N's. In the request year the activities under a project sum to it exactly; in the current year they under-cover it in about 9% of cases, so an activity's delta can legitimately exceed its parent's and the two must not be compared row to row.
2 activities in project 3323
Every R-2A line of this project, largest FY2027 request first. Linked where the activity has enough of its own narrative to carry a page; the rest are shown in full on the project page.