What the FY2027 request buys
Verbatim from the R-2A exhibit for project 4033 of PE 0204229N. 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 M-Code planned activities include completion of EMD. EMD efforts include Proof of Manufacturing hardware and final software qualification, and achieve Security Approval of an M-Code capable Tactical Tomahawk (TACTOM) AGR5.
Decrease in funding due to completion of EMD efforts, transitioning to testing and production.
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.
M-Code planned activities include continuation of EMD efforts to include procurement of AGR5 Proof of Manufacturing units to be used for hardware and software qualification, integration, and testing of a M-Code AGR5.
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 | 20.4 |
| FY2026 | Enacted | 15.3 |
| FY2027 | Request | 13.3 |
This activity is 100% of project 4033's FY2027 request and 17% of PE 0204229N'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.
1 activity in project 4033
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.