Project 668
$2,031.0MFY2027 request ▲ 745%Mission Command Applications
FY2025 actual$103.2M
FY2026 enacted$240.5M
FY2027 request$2,031.0M
FY2027 Request
$2,109.9M
▲ 619% vs FY2026
House approps mark
$1,001.1M
▼ $1,108.8M vs request
FY2026 Enacted
$293.6M
In law
Roll-up of 4 projects. Projects are the summable leaves — the PE total is their sum, never added to it.
For fiscal year 2027, Defense-Wide agencies are requesting $2.11B for JADC2 Development and Experimentation Activities under RDT&E program element 0604122D8Z, up 619% over FY2026. In the FY2027 defense authorization, House approps moved to cut it to $1.00B.
Funding trajectory
Funding profile, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure.
Actual Enacted Request Outyear (FYDP) House approps mark
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 271.6 |
| FY2026 | Enacted | 293.6 |
| FY2027 | Request | 2,109.9 |
| FY2028 | Outyear | 2,019.0 |
| FY2029 | Outyear | 2,078.8 |
| FY2030 | Outyear | 2,081.0 |
| FY2031 | Outyear | 2,094.0 |
Where it sits
Acquisition lifecycle
This program is funded in RDT&E Budget Activity 6 — RDT&E Management Support.
Complete
Research
BA 1–2
Complete
Advanced Technology
BA 3
Complete
Prototyping
BA 4
Current
Development & Fielding
BA 5–7
Inside the program element
4 projects roll up into PE 0604122D8Z
Projects are the summable leaves — the PE total is their sum, never added to it. Program elements and projects carry the full five-year plan; activities stop at the budget year. This PE moves 619% overall, which can hide much larger swings below.
Project 085
$52.8MFY2027 request ▲ 101%Data Integration Layer (DIL)
FY2025 actual$163.3M
FY2026 enacted$26.3M
FY2027 request$52.8M
Project 669
$26.1MFY2027 request ▼ 2%Global Experimentation (GIDE)
FY2025 actual—
FY2026 enacted$26.8M
FY2027 request$26.1M
Project 973
$0.0MFY2027 request JADC2
FY2025 actual$5.0M
FY2026 enacted$0.0M
FY2027 request$0.0M
Congressional action
The request is contested
Committee marks on the FY2027 request. Adds and cuts are reconciled in conference before they become law.
RequestPresident's Budget
$2,109.9M
House NDAA (HASC)HASC
$2,079.9M −$30.0M · −1.4%
Senate NDAA (SASC)SASC
$1,459.9M −$650.0M · −31%
House Approps (HAC-D)HAC_D
$1,001.1M −$1,108.8M · −53%
▲ $1,078.8M chamber gap — unresolved as of 2026-07-27. These are FY2027 authorization marks (NDAA); appropriations and the conference agreement may differ.
Program detail
Mission & acquisition strategy
The Chief Digital and Artificial Intelligence Officer (CDAO) mission is to accelerate DoW adoption of data, analytics, and artificial intelligence (AI) to enable decision advantage from the boardroom to the battlefield. This includes improving CJADC2 in support of the Joint Warfighting Concept through three lines of effort: -Data Integration Layer: These efforts mature management of DoW operational data and deploy a tactical edge data mesh (EDM) to enable data integration among new and legacy systems.
Project 668, 085, 669, 973 — Mission Command Applications
Ask Hitch
Ask this program element
Answers are generated from the figures on this page — the FY2027 justification exhibits and the marks tracked above — and nothing else is consulted. Confirm any figure against the cited exhibit before you use it externally.
H
Questions this page can answer
How does the FY2027 request compare with FY2026, and what does the five-year plan show?What did House approps do to this request, and what is still unresolved?Which project inside PE 0604122D8Z is growing fastest, and which is shrinking?In plain terms, what is this program element for and how is it being acquired?
This page carries the budget justification and the NDAA marks — nothing else. For what a contractor has actually been obligated, the ledger is at hitchintel.com/vendors; for live solicitations, hitchintel.com/opportunities. Both are member surfaces.
Provenance
Cite this page
Sources
FY2027 Office of the Secretary of Defense RDT&E Budget Justification · Exhibits R-2 / R-3 · PE 0604122D8Z (President's Budget PB2027) — and FY2027 NDAA committee marks, as tracked 2026-07-27.
Suggested citation
HitchAI, "JADC2 Development and Experimentation Activities (PE 0604122D8Z)," federal budget intelligence, PB2027 vintage. hitchintel.com/programs/0604122D8Z
Machine access
Markdown twin
/programs/0604122D8Z.md · MCP mcp.hitchintel.com → budget_get_program_element, budget_get_cong_marksFY2027 Request
$2,031.0M
▲ 745% vs FY2026
FY2026 Enacted
$240.5M
▲ 133% vs FY2025
FY2025 Actual
$103.2M
Prior year
Mission Command Applications — one RDT&E project inside PE 0604122D8Z. Congressional marks are recorded on the program element, not on a project.
Project 668 — Mission Command Applications — requests $2.03B in FY2027, 96% of the $2.11B requested for program element 0604122D8Z. Year over year it grows 745% against FY2026.
Funding trajectory
Project 668 funding, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.
Actual Enacted Request Outyear (FYDP)
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 103.2 |
| FY2026 | Enacted | 240.5 |
| FY2027 | Request | 2,031.0 |
| FY2028 | Outyear | 1,932.2 |
| FY2029 | Outyear | 1,983.7 |
| FY2030 | Outyear | 1,977.2 |
| FY2031 | Outyear | 1,981.4 |
Inside the project
1 accomplishment / planned program
The R-2A exhibit. Activities carry the prior, current and budget year only — no five-year plan — and they are descriptive: coverage is partial and they do not always add back to the project, so count them, never total them. Opening lines only here — the full year-by-year narrative is on the project page.
FY2025 actual$103.2M
FY2026 enacted$240.5M
FY2027 request$2,031.0M
Funding will expand enterprise access to Joint C2 capabilities to Services across echelon and provide deliberate, sustained development and enterprise-wide integration. Funding will streamline acquisition, establish rigorous testing and evaluation standards, and create clear lines of accountability for performance and management…
Read the FY2027 plan →Project detail
What project 668 buys
This effort integrates data, analytics, and AI in support of the seven Joint warfighting functions leveraging a common government owned/contractor operated data stack that adheres to open architecture principles. Requested funding purchases commercial Joint C2 software licenses for Services and the Joint Force foron multiple networks, engineering support to integrate new data sources and digitize workflows, maintenance of a DevSecOps pipeline to allow third party vendors to develop and field applications , funding for those third party vendors to close CJADC2 gaps, and cloud compute costs needed to run applications and workflows. Joint C2 capabilities draw from tactical data bridges to the strategic level in order to provide live battlespace awareness and decision advantage to commanders on a single pane of glass.
FY2027 Request
$52.8M
▲ 101% vs FY2026
FY2026 Enacted
$26.3M
▼ 84% vs FY2025
FY2025 Actual
$163.3M
Prior year
Data Integration Layer (DIL) — one RDT&E project inside PE 0604122D8Z. Congressional marks are recorded on the program element, not on a project.
Project 085 — Data Integration Layer (DIL) — requests $52.8M in FY2027, 2.5% of the $2.11B requested for program element 0604122D8Z. Year over year it grows 101% against FY2026.
Funding trajectory
Project 085 funding, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.
Actual Enacted Request Outyear (FYDP)
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 163.3 |
| FY2026 | Enacted | 26.3 |
| FY2027 | Request | 52.8 |
| FY2028 | Outyear | 60.2 |
| FY2029 | Outyear | 67.9 |
| FY2030 | Outyear | 76.0 |
| FY2031 | Outyear | 84.3 |
Inside the project
1 accomplishment / planned program
The R-2A exhibit. Activities carry the prior, current and budget year only — no five-year plan — and they are descriptive: coverage is partial and they do not always add back to the project, so count them, never total them. Opening lines only here — the full year-by-year narrative is on the project page.
FY2025 actual$163.3M
FY2026 enacted$26.3M
FY2027 request$52.8M
Continue to field additional tactical edge data mesh nodes to build out capability supporting Department priorities. Additionally, CDAO will continue working with Echelon 1 and Echelon 2 components to prioritize API level data integrations for the nodes. CDAO continues to improve blue data objects and enterprise cross-domain solution…
Read the FY2027 plan →Project detail
What project 085 buys
The DIL funding line contains efforts to mature management of DoW operational data and deploy a tactical edge data mesh (EDM) to enable data integration among new and legacy systems. EDM is a resilient, interoperable data integration service connecting sensors, weapons, and other battlefield assets for enhanced situational awareness and coordination into a cloud environment. EDM leverages commercial software, a government-owned software development kit (SDK), and open application programming interfaces (APIs) to integrate government and vendor systems, facilitate tactical data sharing, and incorporate artificial intelligence/machine learning (AI/ML) capabilities at the edge. EDM supports multi-domain operations across echelons, including enhanced C2 and fires in contested environments by optimizing data exchange among Denied, Disrupted, Intermittent, and Limited (DDIL) communication paths. The tactical edge data mesh provides real time understanding at tactical level C2 into the data layer for the department in Joint C2 system.
FY2027 Request
$26.1M
▼ 2.4% vs FY2026
FY2026 Enacted
$26.8M
In law
Global Experimentation (GIDE) — one RDT&E project inside PE 0604122D8Z. Congressional marks are recorded on the program element, not on a project.
Project 669 — Global Experimentation (GIDE) — requests $26.1M in FY2027, 1.2% of the $2.11B requested for program element 0604122D8Z. Year over year it falls 2.4% against FY2026.
Funding trajectory
Project 669 funding, FY2026–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.
Enacted Request Outyear (FYDP)
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2026 | Enacted | 26.8 |
| FY2027 | Request | 26.1 |
| FY2028 | Outyear | 26.7 |
| FY2029 | Outyear | 27.2 |
| FY2030 | Outyear | 27.8 |
| FY2031 | Outyear | 28.4 |
Inside the project
1 accomplishment / planned program
The R-2A exhibit. Activities carry the prior, current and budget year only — no five-year plan — and they are descriptive: coverage is partial and they do not always add back to the project, so count them, never total them. Opening lines only here — the full year-by-year narrative is on the project page.
FY2025 actual—
FY2026 enacted$26.8M
FY2027 request$26.1M
In FY 2027 experimentation within the GIDE project will continue to align with Service and CCMD exercises and incorporate novel third party and Joint C2 capability in experimentational settings.
Read the FY2027 plan →Project detail
What project 669 buys
The Global Information Dominance Experimentation (GIDE) line comprises iterative, metrics-based experimentation with Combined Joint All-Domain Command and Control (CJADC2) capabilities and concepts. Experimentation events leverage CCMD and Service exercises to test Joint C2 capabilities and third party vendors in the context of real mission use cases, on live networks, and with real data and users. Capabilities that prove successful in experimentation rapidly field to warfighters on the spot because they are software-based.
FY2027 Request
$0.0M
No FY2026 funding
FY2026 Enacted
$0.0M
▼ 100% vs FY2025
FY2025 Actual
$5.0M
Prior year
JADC2 — one RDT&E project inside PE 0604122D8Z. Congressional marks are recorded on the program element, not on a project.
Project 973 — JADC2 — requests $0.0M in FY2027, 0.0% of the $2.11B requested for program element 0604122D8Z.
Funding trajectory
Project 973 funding, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.
Actual Enacted Request Outyear (FYDP)
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 5.0 |
| FY2026 | Enacted | 0.0 |
| FY2027 | Request | 0.0 |
| FY2028 | Outyear | 0.0 |
| FY2029 | Outyear | 0.0 |
| FY2030 | Outyear | 0.0 |
| FY2031 | Outyear | 0.0 |
Inside the project
1 accomplishment / planned program
The R-2A exhibit. Activities carry the prior, current and budget year only — no five-year plan — and they are descriptive: coverage is partial and they do not always add back to the project, so count them, never total them.
JADC2
FY2025 actual$5.0M
FY2026 enacted—
FY2027 request—
Project detail
What project 973 buys
This effort integrates data, analytics, and AI in support of the seven Joint warfighting functions leveraging a common government owned/contractor operated data stack that adheres to open architecture principles. Requested funding purchases licenses for Joint access to Joint C2 capabilities on multiple networks, engineering support to integrate new data sources and digitize workflows, maintenance of a DevSecOps pipeline to allow third party vendors to develop and field applications on operational networks, funding for those third party vendors to close CJADC2 gaps, and cloud compute costs needed to run applications and workflows. This line also supports the efforts to mature management of DoW operational data and deploy a tactical edge data mesh to enable data integration among new and legacy systems' and Joint C2 experimentation.