R-2A Activity · President's Budget PB2027

Scaled Onboard Electronic Attack (SOEA) Government Engineering

FY2027 Request
$28.3M
▲ 110% vs FY2026
HitchAI read

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

FY2027 Request
$28.3M
▲ 110% vs FY2026
FY2026 Enacted
$13.5M
▲ 103% vs FY2025
FY2025 Actual
$6.6M
Prior year
Planned work

What the FY2027 request buys

Verbatim from the R-2A exhibit for project 3469 of PE 0604757N. 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

- Continue preliminary prototype builds and accept delivery to prove out and validate critical performance capability, system architecture functionality, and supportability requirements. - Continue testing to collect evidence for verification of SOEA requirements. - Continue platform integration studies. - Continue support of modularity specifications development. - Commence monitoring training curriculum development. - Continue Model & Simulation (M&S) to support further testing. - Coordinate Softkill Coordination System (SKCS) integration. - Commence support and monitoring of software and hardware fixes/upgrades. - Commence Land-Based Performance Testing & Environmental Testing to prove out integrated system capabilities and verify integrated system performance in a representative operational environment. - Conduct Phase 2 Rapid Fielding Designation Review.

FY2026 to FY2027 change

The increase in FY27 aligns with the initiation of Phase 2 Rapid Fielding, conduct of land-based performance and environmental testing, and support/monitoring of software/hardware upgrades based on testing results.

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

- Complete preliminary prototype builds and accept delivery to prove out and validate critical performance capability, system architecture functionality, and supportability requirements. - Continue testing to collect evidence for verification of SOEA requirements. - Conduct initial Operational Demonstration Assessment (ODA) - Continue platform integration studies. - Continue support of modularity specifications development. - Commence Model & Simulation (M&S) to support further testing. - Coordinate Softkill Coordination System (SKCS) integration. - Commence preparation for Phase 2 Rapid Fielding Designation Review

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.

2506.6FY25ACTUAL13.5FY26ENACTED28.3FY27REQUEST
Actual Enacted Request
Fiscal YearEstimate TypeAmount ($M)
FY2025Actual6.6
FY2026Enacted13.5
FY2027Request28.3

This activity is 44% of project 3469's FY2027 request and 14% of PE 0604757N'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

2 activities in project 3469

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 project page.

Scaled Onboard Electronic Attack (SOEA) Development$36.1M ▼ 18%
Scaled Onboard Electronic Attack (SOEA) Government Engineering — this activity$28.3M ▲ 110%
Source
FY2027 Department of the Navy RDT&E Budget Justification · Exhibit R-2A · PE 0604757N, project 3469 (President's Budget PB2027). Congressional marks are recorded on the program element, never on an activity.
Machine access
Markdown twin /programs/0604757N/3469/a0.md · MCP mcp.hitchintel.combudget_get_activity