What the FY2027 request buys
Verbatim from the R-2A exhibit for project CC01 of PE 0303171K. 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 and test the cloud hosting environment to modernize cyber resiliency and improve reliability and maintainability. • Execute JPES Phase II by modernizing business processes to integrate natural language queries, compare rapid course of actions, adapt dynamic plans, optimize resource allocations, and perform proactive risk assessment and mitigation. • Design and build a Joint Worldwide Intelligence Communications System (JWICS) instance of JPES. • Plan transition of Defense Innovation Unit’s prototype of Joint Sustainment Decision Tool (JSDT) to the Global Force Management (GFM) Program Office. The JSDT program aims to use artificial intelligence to anticipate logistics needs and proactively manage distribution. • Address DoW Chief Information Officer (CIO) priorities by incorporating Enterprise Identity, Credential, and Access Management, Zero Trust, Internet Protocol Version Six (IPv6), metadata tagging, and Joint Staff requirements including Newsgroups modernization and artificial intelligence to optimize planning and resourcing. • Build and deploy a Newsgroups replacement. Newsgroups are discussion groups on the Usenet, a global, decentralized network that predates the World Wide Web. Users can post messages to newsgroups, which are then distributed to servers worldwide, allowing other users to read and respond. Newsgroups are a popular JOPES communication tool.
The increase of +$4.373 million from FY 2026 to FY 2027 will support continuous enhancement of JPES. DISA will field a Newsgroups replacement and a JPES JWICS instance to address DoW CIO modernization priorities. DISA will continue enhancing JPES to meet the operational requirements of the Joint Staff, Services, and Combatant Commands.
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.
• Continue JPES Phase II planning. • Develop and analyze new JPES functional requirements beyond the replacement of JOPES. • Conduct Initial Operational Test & Evaluation testing and begin JOPES sunsetting activities. • Move remaining connected external systems, such as Maven Smart Systems, from JOPES to JPES. • Transition operational users and accounts from JOPES to JPES. • Design and prototype a Newsgroups replacement. • Move Joint Capabilities Requirements Manager (JCRM) to IL6 Cloud and Defense Logistics Agency Disposition Services lab assets.
Continue to work development of the JOPES modernization functionality. FY 2025 activities include: • Continuing the development of JPES functional requirements to continue Phase I. Completion of JPES Phase I is delayed and will stretch into FY 2025. • Analyzing new JPES functional requirement beyond the replacement of JOPES. • Conducting preliminary analysis for the modernization of JCRM. JCRM is a web-based application and database supported by web services. It enables the Global Force Management Allocation Process (GFMAP) for CCMDs to draft, staff, store, and submit force requirements for ongoing and emerging military operations, contingency plans, and military exercises worldwide. JCRM is vital to managing complex global force requirements and tracking the distribution of U.S. military forces among the CCMDs. • Conducting requirements analysis for JCRM replacement and beginning initial systems design.
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 | 3.8 |
| FY2026 | Enacted | 6.2 |
| FY2027 | Request | 10.6 |
This activity is 100% of project CC01's FY2027 request and 100% of PE 0303171K'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 CC01
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.