What the FY2027 request buys
Verbatim from the R-2A exhibit for project 666157 of PE 0606017F. 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.
- Maintain current and future force design and threat in scenarios that are used for analysis - Conduct analysis aligned to demand signal, capability-based gap identification, and the scope of DOTMLPF-P in candidate design development to support acquisition decision development - Continue efforts prioritized based on force design Examples include Autonomous Collaborative Platform Strategy, Weapons Portfolio Mix, and Counter C-C5ISRT - Collaborate across the joint force, Services and agencies in the analysis of candidate concepts and align candidate concepts into the larger force through mission integration and mission engineering - Identify and develop priority mission engineering threads for refinement and new builds for the next FY. Further develop and refine future concepts of employment and associated candidate concepts to address minimum attribute sets identified through time or driven by threat updates for concept evaluation - Continue market evaluation of flexible, digital instantiations for CONOP/CONEMP evaluation for new concepts - Continue building infrastructure necessary for mission engineering thread development and use: software tool implementation, validation and verification methods for models, thread information application for industry - Continue to partner with FFRDC, UARC, industry and non-traditional vendors to document state of the practice, state of the art, technically possible/feasible, promising emerging technologies for investment for various problem statements and solution sets. Examples include Electronic Warfare analyses. - Continue the formation of a competition strategy across technology development organizations internal and external to the Air Force.
- FY 2027 funding decreased compared to FY 2026 by $0.195 million due other higher Air Force priorities.
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.
- Continue to maintain current and future force design and threat in scenarios that are used for analysis - Develop new mission engineering threads for decomposition and analysis and expand upon existing threads to capture force design trends and trade space - Continue analysis aligned to demand signal, capability-based gap identification and the scope of DOTMLPF-P in candidate design development to support acquisition decision development - Derive capability gaps from operational mission definitions, CONOPS and CONEMPs, estimates inventory, then assess commercial and developmental technical solution sets in a multi-level security environment across domains - Continue collaboration across the joint force, Services and agencies in the analysis of candidate concepts - Continue collaboration with FFRDC, UARC, industry and non-traditional vendors to document state of the practice, state of the art, and the technically possible/feasible for various problem statements and solution sets. Examples include Electronic Warfare analyses - Continue efforts prioritized on force design. Examples include Autonomous Collaborative Platform Strategy, Weapons Portfolio Mix, and Counter C-C5ISRT - Continue to develop and refine future concepts of employment and associated candidate concepts to address minimum attribute sets identified through time or driven by threat updates for concept evaluation - Leverage market research and industry engagement aligned to demand signal and force design guidance - Continue to develop relationships with the joint force, Services and agencies to understand how candidate concepts fit into the larger force through mission integration and mission engineering
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 | 13.7 |
| FY2026 | Enacted | 11.0 |
| FY2027 | Request | 10.8 |
This activity is 100% of project 666157's FY2027 request and 50% of PE 0606017F'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.
1 activity in project 666157
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.