What the FY2027 request buys
Verbatim from the R-2A exhibit for project 934 of PE 0606829D8Z. 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.
o Validate needed data elements and interfaces with industry to support DLMS transactions within the Defense Automated Addressing System to support MILDEP ICP functions within their enterprise business systems o Cross reference needed data elements with those established in FY2026 to support audit o Solicit proposals and award contracts in FY27 with the prime vendors to get data delivery and data interfaces with industry business systems to enable MILDEP ICP operations o Collaborate with DLA, Joint Program Office (JPO), and the MILDEPs to design prototype/Minimum Viable Product (MVP)for the data architecture and pipelines to facilitate ICP data and implement in 2027 to support testing and MILDEP ICP operations by end of 2027 o Coordinate any additional MILDEP or DLA business system changes in architecture to accommodate the Department architecture with their relative Program Element Offices o Continue testing and validation/verification of ICP processes - Per original issue paper and cost estimate, FY2027 neither increases or decreases at this time and is consistent with plan.
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.
- Validate needed data elements from the prime vendors to support DLMS transactions within the Defense Automated Addressing System to push audit data to Department business systems - Solicit proposals and award contracts early in FY26 with the prime vendors to get data delivery on the needed data elements - Collaborate with DLA, Joint Program Office (JPO), and the MILDEPs to design prototype/Minimum Viable Product (MVP) for the data architecture/pipelines to facilitate audit data and implement by mid-FY 2026 to support testing by mid-FY 2026 and implementation/Services reporting by 1 October 2026 - Coordinate any additional MILDEP business system changes to accommodate the architecture with their relative Program Element Offices - Design incremental data architecture after audit requirements to facilitate MILDEPs’ ICP transition - All $30 million was expected to be committed or obligated within FY 2026, pending award, some maybe allocated in FY27.
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) |
|---|---|---|
| FY2026 | Enacted | 30.0 |
| FY2027 | Request | 29.4 |
This activity is 100% of project 934's FY2027 request and 100% of PE 0606829D8Z'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 934
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.