What the FY2027 request buys
Verbatim from the R-2A exhibit for project 673509 of PE 0604840F. 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.
Continue development and support for DevSecOps infrastructure, platform, software development pipeline, and joint F-35 organizational connections. Continue to revise the transition plan based on emerging requirements to support stand-up of a team consisting of Industry and Government software development in support of software modernization and DevSecOps Cloud transition. Establish initial capabilities and expand existing software development efforts with the goal of transitioning dispersed and separated software development environments into model-based systems engineering and a fully collaborative requirements to development environment. Capabilities include software development environment for Maintenance Systems ODIN, ALIS to ODIN migration, Combat Data System's Mission Planning, Propulsion's Offboard Management System, and Air Vehicle Mission System domains. Additional goals of delivering flight-worthy rapid prototyping of capability, virtual test capability, and transitioning workloads to lower cost software sustainment efforts. New requirements from PMOs are expected. Prepare environment for on-boarding, as well as transitioning the PMOs from separate pillars to a centralized JPO-managed cloud environment. Includes software licensing for PMO tool sets and associated applications. Major cost drivers include requirements tool, and collaboration tools, authentication tools - supporting Single Sign On, Multi-Factor Authentication and development tools. For software tooling efforts, working towards an eventual consolidation of tools across the PMOs (i.e. application rationalization) with an end goal of a standardized compiler tool sets and Cybersecurity compliance. Accordingly, talent/consumption (hardware and software to run the environment) contracts must be renewed and expanded. Cybersecurity requirements must also be met, meaning additional resources for security processes, monitoring, scanning, vulnerability identification plus mitigation, and meeting all requirements for DoD compliance to obtain ongoing/continuous Authority to Operate (ATO) and continuous Authority to Operate (cATO). Provide support to F-35 partners and foreign military sales for cloud and DevSecOps capabilities and collaboration and incorporation of multicloud strategy to reduce risk to long term sustainment of the F-35 Lightning II.
No major changes from FY2026 to FY2027. Funding reflects FY2027 project needs in accordance with F-35 cost share rules.
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 development and support for DevSecOps infrastructure, platform, software development pipeline, and joint F-35 organizational connections. Establish initial capabilities and expand existing software development efforts with the goal of transitioning dispersed and separated software development environments into model based systems engineering and a fully collaborative requirements to development environment. Capabilities include software development environment for Maintenance Systems ODIN, ALIS to ODIN migration, Combat Data System's Mission Planning, Propulsion's Offboard Management System, and Air Vehicle Mission System domains. Additional goals of delivering flight-worthy rapid prototyping of capability, virtual test capability, and transitioning workloads to lower cost software sustainment efforts. New requirements from PMOs are expected. Prepare environment for on-boarding, as well as transitioning the PMOs from separate pillars to a centralized JPO-managed cloud environment. Includes software licensing for PMO tool sets and associated applications. Major cost drivers include requirements tool, and collaboration tools, authentication tools - supporting Single Sign On, Multi-Factor Authentication and development tools. For software tooling efforts, working towards an eventual consolidation of tools across the PMOs (i.e. application rationalization) with an end goal of a standardized compiler tool sets and Cybersecurity compliance. Accordingly, talent/consumption (hardware and software to run the environment) contracts must be renewed and expanded. Cybersecurity requirements must also be met, meaning additional resources for security processes, monitoring, scanning, vulnerability identification plus mitigation, and meeting all requirements for DoD compliance to obtain ongoing/continuous Authority to Operate (ATO) and continuous Authority to Operate (cATO).
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.0 |
| FY2026 | Enacted | 19.9 |
| FY2027 | Request | 19.7 |
This activity is 100% of project 673509's FY2027 request and 1.7% of PE 0604840F'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 673509
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.