What the FY2027 request buys
Verbatim from the R-2A exhibit for project 01 of PE 0605080S. 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.
In FY 2027, the DAI PMO will: • Will mature/ enhance system post OCI migration. • Maintain ATO for DAI Cloud hosting/ maintain ATO post cloud migration • Continue with cloud hosting stabilization efforts. • Develop Release 10 to deploy to customer organizations in October 2027. • Continue to develop, deploy, and support Departmental initiatives to include G-Invoicing and Identity Credential Access Management (ICAM). • Continue ongoing support to 30 Organizations as they undergo audit by helping them with answering auditor PBCs. • Support Defense Agencies and activities to consolidate Audit activities and include ADVANA wrapper. • Support the DLA Audit Readiness Office in developing their assertion package, supporting DLA’s SOC-1 report, and resolving any identified NFRs. • Undergo a DAI application standalone service provider independent audit (SSAE-18). • Maintain Application User Licenses to support additional users and increased data storage costs. • Conduct BEA compliance assessment against the current version and BPR for user organizations. • Continue to expand the use of RPA to replace manual processes and improve resource utilization. • Increase Tier 2 Help Desk support to meet Production Support Request (PSR) resolution targets. • Increase Development Support for System Change Proposal (SCP) requirements backlog resolution.
Funding increased due to new DAI initiatives with implementing/onboarding new agencies. • Funding increased due by $19.6M due to the planned integration of USTRANSCOM into the DAI ERP solution as well as increased application development resources to allow DAI to apply 10,000 hours per year to the DAI requirements backlog (accrued during the USMC DAI Implementation and Audit Focus). • TRANSCOM’s integration into the DAI ERP solution will allow TRANSCOM to utilize DAI’s centralized platform, enhancing financial accountability, audit, compliance, and operational efficiency aligned with DoW financial goals.
FY2025–FY2026: what came before
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.
In FY 2026,the DAI PMO plans to: • Transition the application from an on-premise DISA-hosted environment to a commercial cloud hosting environment with go-live in April 2026. • Continue with cloud hosting stabilization efforts. • Develop Release 9 deployed to customer organizations in October 2026. • Continue to develop, deploy, and support Departmental initiatives to include G-Invoicing and Identity Credential Access Management (ICAM). • Continue ongoing support to 30 Organizations as they undergo audit by helping them with answering auditor PBCs. • Support Defense Agencies and activities to consolidate Audit activities and include ADVANA wrapper. • Support the DLA Audit Readiness Office in developing their assertion package, supporting DLA’s SOC-1 report, and resolving any identified NFRs. • Undergo a DAI application standalone service provider independent audit (SSAE-18). • Maintain Application User Licenses to support additional users and increased data storage costs. • Conduct BEA compliance assessment against the current version and BPR for user organizations. • Support RMF processes to maintain DAI’s ATO packages for the DAI legacy on-premise application and the EPM SaaS application, and to maintain DAI’s IATT for DAI Cloud, and achieve an ATO in the DAI Cloud environment for FY 26. • Continue to expand the use of RPA to replace manual processes and improve resource utilization. • Increase Tier 2 Help Desk support to meet Production Support Request (PSR) resolution targets. • Increase Development Support for System Change Proposal (SCP) requirements backlog resolution.
In FY 2025, the DAI PMO will: • Migrate from DISA on-premises to Cloud Hosting throughout FY 2025. • Stabilize the USSGL update. • Conduct planning phase for onboarding USTRANSCOM, with Wave 1 implementation efforts beginning in FY 2026 • Deploy Release 7 to the existing customer organizations. • Develop Release 8 to deploy to customer organizations in October 2025. • Develop Release 9 to deploy to customer organizations in October 2026. • Support 30 organizations as they undergo audit by helping them with answering auditor RFIs and helping them locate required artifacts to maintain consistency of approach with all that use DAI. • Support the OSD Reform Initiatives including ICAM access control and G-Invoicing Support, includes monthly progress meetings and some coding. • Maintain Application User Licenses to support additional users and increased data storage costs based on application data growth. • Conduct a service provider, independent audit, SSAE-18, and support DLA Audit Readiness Office in developing an assertion package supporting DLA SOC 1 and resolve any identified NOFs. • Conduct BEA compliance assessment against the current version (v11.2 for compliance) document results in the Department’s assessment portal and conduct BPR for newly joining agencies. • Resolve critical software errors and critical statutory/regulatory enhancements that affect operations and incorporate changes identified during BPR, BEA compliance assessment and the Audit generated corrective action plans. • Support RMF process maintaining activity to support actions included in the AO’s required POA&M to maintain the ATO in both on-premise and Cloud environments. • Expand the use of RPA scripts to increase speed of data entry, ensuring data accuracy from data entry through the entire requisition life cycle.
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 | 30.8 |
| FY2026 | Enacted | 31.7 |
| FY2027 | Request | 51.3 |
This activity is 100% of project 01's FY2027 request and 100% of PE 0605080S'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 01
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.