What the FY2027 request buys
Verbatim from the R-2A exhibit for project 2901 of PE 0605013N. 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.
Following the full migration of users in FY26, ePS will shift its focus toward meeting FY28 audit requirements. The team will address and resolve any identified findings or defects, while also implementing improvements based on user feedback and evolving needs. These updates aim to enhance the overall ePS experience and ensure greater satisfaction for end users. Based on user priorities, FY27 Major Releases include: Q1: R2.0 ePS - CCM 2.0 - Backlog Prioritized Requirements ePS - PPP 3.0 - Backlog Prioritized Requirements ePS - SUP 3.0 - Backlog Prioritized Requirements ePS - OTA 2.0 - Backlog Prioritized Requirements FY28 Audit Requirements Q2: R2.1 ePS - CCM 2.1 - Backlog Prioritized Requirements ePS - ADM 2.0 - Backlog Prioritized Requirements ePS - AUT 2.0 - Backlog Prioritized Requirements FY28 Audit Requirements Q3: R2.2 ePS - CCM 2.2- Backlog Prioritized Requirements ePS - CLO 1.0 - Closeout ePS - EXP 2.0 - Backlog Prioritized Requirements ePS - IT 2.0 - Backlog Prioritized Requirements FY28 Audit Requirements Q4: R2.3 ePS - CCM 2.3 - Backlog Prioritized Requirements ePS - EVL 1.0 - Source Selection/Evaluation ePS - GAA 1.0 - Grants and Assistance Agreements ePS - VND 2.0 - Backlog Prioritized Requirements FY28 Audit Requirements Market research will continue to identify capability gaps throughout the development process. MSAs/OTAs will support capability gap identification and mitigation to produce future solution roadmaps.
FY26 to FY27 $25.333M decrease reflects the FY25/26 prioritization of ePS development to accelerate the timeline for deploying a fully functional and auditable Electronic Procurement System (ePS), enabling the Q4FY26 sunset of the Standard Procurement System (SPS).
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.
Building on the momentum achieved in FY25, ePS will continue releasing regular updates, capability releases, and development backlog priority items to users through continuous agile sprints to support extensive cut-over completion and user accession in FY26. In anticipation of the SPS sunset at the close of Q4 FY26, ePS engineers will complete preparations and user requirements to support the final cut-over for remaining user communities, apart from Grants and NAVSUP WSS. Reaching nearly all expected end-user counts of about 12,000 by the end of FY26, user communities completing cut-over to ePS in FY26 include USMC, I&L, WSS, NEST, NAVSEA, SeaPort, NAVSUP FLCs, USMC EXP, MSC, and NAVAIR. Based on user priorities, FY26 Major Releases include: Q1: R1.6.X ePS - CCM 1.6.X - Backlog Prioritized Requirements ePS - eFILE 2.0 - Backlog Prioritized Requirements ePS - SOL 1.0 - Solicitation ePS - ADM 1.0 - Contract Administration ePS - MWS 1.0 - Major Weapons Systems ePS - SUP 2.0 - Backlog Prioritized Requirements SPS User Acceleration Migration SeaPort User Acceleration Migration NEST Integration FY28 Audit Requirements Q2: R1.7 ePS - CCM 1.7 - Backlog Prioritized Requirements ePS - SHP 1.0 - Shipbuilding Repair/Availability ePS - AUT 1.0 - Contract Automation ePS - EXP 1.0 - Expeditionary Forward Support SPS User Acceleration Migration SeaPort User Acceleration Migration NEST Integration FY28 Audit Requirements Q3: R1.8 ePS - CCM 1.8 - Backlog Prioritized Requirements ePS - VND 1.0 - Vendor Portal and Engagement Capabilities ePS - IT 1.0 - IT Purchasing SPS User Acceleration Migration SPS Sunset Activities NEST Integration/ User Migrations FY28 Audit Requirements Q4: R1.8.X ePS - CCM 1.8.X - Backlog Prioritized Requirements Complete SPS User Acceleration Migration Complete SPS Sunset Activities NEST Integration/ User Migrations FY28 Audit Requirements Market research will continue to identify capability gaps throughout the development process. MSAs/OTAs will support capability gap identification and mitigation to produce future solution roadmaps.
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 | 45.4 |
| FY2026 | Enacted | 43.1 |
| FY2027 | Request | 17.7 |
This activity is 45% of project 2901's FY2027 request and 12% of PE 0605013N'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.
5 activities in project 2901
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.