What the FY2027 request buys
Verbatim from the R-2A exhibit for project 640410 of PE 0207522F. 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.
- Will continue to update Medusa Command and Control (C2) software to further interoperability and incorporation within the Advanced Battle Management System (ABMS) architecture (e.g., Unified Data Library). - Will continue electronic warfare upgrades, to include but not limited to new sensor and effector components, and new Ninja skills which leverage full Ninja capability within Medusa C2 and other C2 systems. - Will continue efforts in alignment with the DoW's JIATF. - Will continue to evaluate new capabilities. - Will continue to develop and test C2 capabilities, via planned incremental software sprints, bi-annual software upgrades. - Will continue to ensure cyber security requirements are developed and incorporated in all new system changes. - Will continue to support oversight, management, and execution of JIATF funded development efforts. - Will continue to conduct studies, analysis, and evaluations of threats and capability gaps to refine and update requirements enabling upgraded and improved capabilities. - Will initiate and continue contractor testing of developed updates. - Will integrate initial kinetic effectors for evaluation for broader DAF employment to include low collateral effects intercept (LCEI) capabilities and other kinetic solutions such as APKWS. - Will continue to integrate capabilities on expeditionary systems. - Will continue to develop NCR COP technical solutions in coordination with the Air Force Rapid Capabilities Office to include joint interoperability of Counter-small Unmanned Aircraft Systems (C-sUAS) sensors, development of correlation and fusion process, and developing cyber-secure cloud infrastructure for data dissemination and processing for C-sUAS protection of Presidential aviation assets.
FY26 to FY27 increased due to NCR software and hardware development requirements.
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.
- Update Medusa Command and Control (C2) software furthering interoperability and incorporation within the Advanced Battle Management System (ABMS) architecture (e.g., Unified Data Library). - Upgrade electronic warfare, including but not limited to new sensor and effector components, and new Ninja skills leveraging full Ninja capability within Medusa C2 and other C2 systems. - Continue efforts in alignment with the DoW's Joint Interagency Task Force (JIATF) 401. - Evaluate new capabilities. - Develop and test C2 capabilities, via planned incremental software sprints, annual software upgrades. - Ensure cyber security requirements are developed and incorporated in all new system changes. - Support oversight, management, and execution of JIATF funded development efforts. - Conduct studies, analysis, and evaluations of threats and capability gaps to refine and update requirements enabling upgraded and improved capabilities. - Initiate and continue contractor testing of developed updates. - Integrate initial kinetic effectors for evaluation for broader DAF employment to include low collateral effects intercept (LCEI) capabilities and other kinetic solutions such as Advanced Precision Kill Weapon System (APKWS). - Integrate capabilities on expeditionary systems. - Develop NCR COP technical solutions to include joint interoperability of Counter-small Unmanned Aircraft Systems (C-sUAS) sensors, development of correlation and fusion process, and developing cyber-secure cloud infrastructure for data dissemination and processing for C-sUAS protection of Presidential aviation assets.
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 | 15.2 |
| FY2026 | Enacted | 9.9 |
| FY2027 | Request | 29.2 |
This activity is 34% of project 640410's FY2027 request and 34% of PE 0207522F'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.
2 activities in project 640410
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.