# Joint Planning and Execution Services (JPES)

**R-2A activity** of project CC01 — Joint Planning and Execution Services (JPES)  
**Program element:** 0303171K — Joint Planning and Execution Services (JPES)  
**Component:** Defense-Wide · **Budget Activity:** 7  
**Vintage:** President's Budget PB2027  
**Canonical URL:** https://hitchintel.com/programs/0303171K/CC01/a0  
**Parent:** https://hitchintel.com/programs/0303171K

## Summary

This activity requests $10.6M in FY2027, 100% of project CC01, up 70% on FY2026. The R-2A exhibit describes it across FY2025–FY2027, including what the FY2027 money is planned to buy.

## What the FY2027 request buys

**FY2027 planned work.** • 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.

**FY2026 to FY2027 change.** 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.

## Before the request year

**FY2026 plans — current year.** • 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.

**FY2025 accomplishments.** 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.

## Funding

| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 3.8 |
| FY2026 | Enacted | 6.2 |
| FY2027 | Request | 10.6 |

> Prior, current and budget year only — an R-2A activity carries no five-year plan. It sums exactly into its project in the request year and not necessarily in any other.

## Source & machine access

- **Source:** FY2027 Office of the Secretary of Defense RDT&E Budget Justification, Exhibit R-2A, PE 0303171K project CC01 (PB PB2027). Narrative is the government's own text.
- **No marks, no contractors at this grain** — congressional marks land on the program element and R-3 performers on the project.
- **MCP:** `mcp.hitchintel.com` — `budget_get_activity`.

*HitchAI is an independent intelligence service, not affiliated with the U.S. Department of Defense. Budget figures are requests/estimates, not obligations.*