R-2A Activity · President's Budget PB2027

Deployable Systems

Activity a4·Project 640141 — Advanced Battle Management System (ABMS)·PE 0604003F·U.S. Air Force
FY2027 Request
$146.2M
▲ 144% vs FY2026
HitchAI read

This activity requests $146.2M in FY2027, 14% of project 640141, up 144% on FY2026. The R-2A exhibit describes it across FY2026–FY2027, including what the FY2027 money is planned to buy.

FY2027 Request
$146.2M
▲ 144% vs FY2026
FY2026 Enacted
$60.0M
▲ 38% vs FY2025
FY2025 Actual
$43.6M
Prior year
Planned work

What the FY2027 request buys

Verbatim from the R-2A exhibit for project 640141 of PE 0604003F. 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.

FY2027 planned work

-Will complete experimentation and testing with TOC-L MR 2 kits in multi-domain joint force exercises, with a focus on INDOPACOM Defense of Guam initiatives, joint fire integration, and long-range kill chain scenarios. -Will conclude formal combined Developmental Test and Evaluation and Operational Test and Evaluation and will inform full prototype production decision and follow-on fielding effort determination. -Will deliver up to 15 TOC-L MR 2 kits with complete product support. -Will continue to deliver up-to-date software features for the Battlespace Command, Control, and Communications (BC3) battle management software to TOC-L, Air Base Air Defense for Missile Defense and the Control and Reporting Center programs.

FY2026 to FY2027 change

Funding increasing due to MR2 contract activities ramping up prototype production quantities in FY 2027, increase in cost per DDI kit, and continuing to deliver up-to-date software features for BC3.

Before the request year

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.

FY2026 plans — current year

-Will conduct experimentation and testing with TOC-L MR 1 kits in multi-domain joint force exercises, with a focus on INDOPACOM Defense of Guam initiatives, joint fire integration, and long-range kill chain scenarios. -Will complete the system design, technical evaluation, production, integration and acceptance testing of the first article MR 2 prototypes. -Will conduct formal combined Developmental Test and Evaluation and Operational Test and Evaluation to inform full prototype production decision and follow-on fielding effort determination. -Will deliver 6 TOC-L MR 2 kits with complete product support. -Will deliver up-to-date software features for the Battlespace Command, Control, and Communications (BC3) battle management software to TOC-L, Air Base Air Defense for Missile Defense and the Control and Reporting Center programs.

Money

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.

255075100125043.6FY25ACTUAL60.0FY26ENACTED146.2FY27REQUEST
Actual Enacted Request
Fiscal YearEstimate TypeAmount ($M)
FY2025Actual43.6
FY2026Enacted60.0
FY2027Request146.2

This activity is 14% of project 640141's FY2027 request and 14% of PE 0604003F'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.

Where this sits

7 activities in project 640141

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.

Source
FY2027 Department of the Air Force RDT&E Budget Justification · Exhibit R-2A · PE 0604003F, project 640141 (President's Budget PB2027). Congressional marks are recorded on the program element, never on an activity.
Machine access
Markdown twin /programs/0604003F/640141/a4.md · MCP mcp.hitchintel.combudget_get_activity