What the FY2027 request buys
Verbatim from the R-2A exhibit for project MPE of PE 0305601K. 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.
Develop data model with new and existing MPE solutions, correlate and map data fields between Maven Smart Systems and existing operational capabilities for an improved common operational picture, implement bi-directional interfaces, and implement container orchestration in Joint Operational Edge Coalition Environment nodes.
Change is due to the transfer responsibilities for Mission Partner Environment (MPE) operations, sustainment, and development activities from the United States Air Force to Department of War CIO and the Defense Information System Agency. In FY27, the Mission Partner Environment (MPE) portfolio will provide the foundational technology and support that enables the DoW to effectively collaborate and interoperate with mission partners across all phases of operations.
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 | 0.0 |
| FY2027 | Request | 15.5 |
This activity is 100% of project MPE's FY2027 request and 100% of PE 0305601K'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 MPE
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 program-element page.