What the FY2027 request buys
Verbatim from the R-2A exhibit for project CF6 of PE 0605625A. 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.
This initiative delivers a comprehensive digital engineering ecosystem, encompassing a cloud-based Digital Engineering (DE) environment and a government-owned software development platform that integrates Artificial Intelligence (AI), Machine Learning (ML), and a Development/Security/Operations (DevSecOps) pipeline. It employs a Digital Twin technology development approach to enhance system design and analysis. The DE costs include software engineering (SE) licenses for Product Lifecycle Management (PLM) software, Model-Based Systems Engineering (MBSE) SysML modeling tools, data management and analysis tools, and modeling and simulation software. DevSecOps costs cover the infrastructure necessary to support the XM30 Software Pathway program, including two vendors developing software within a government-furnished cloud environment. These costs are based on the licenses and pipelines required to oversee and develop XM30 software using an agile DevSecOps methodology. Integration costs include the development of Application Programming Interfaces (APIs) to connect PLM software with various government-owned and commercial tools. This effort also supports future cloud security enhancements, data backups, and data archiving. Additionally, this initiative funds the Virtual Software-In-The-Loop (VSIL) environment hosted within the Digital Acquisition Environment (DAE). The VSIL environment virtualizes computing hardware and software, including graphics and memory systems associated with vehicle designs. Virtual Machines (VMs) within the DAE emulate the computing hardware specifications of the physical systems. Software from the DevSecOps environment integrates into these VMs to virtualize computing machines, develop test software to evaluate computing resource constraints, and assess interactions among virtual machines. These VMs are instantiated using scripts based on the hardware specifications defined in the vehicle's model-based definition. The VSIL environment enables early and frequent virtual testing of computing hardware, reducing uncertainty in hardware performance and improving overall system reliability and efficiency.
The decrease from FY 2026 to FY 2027 is due to transitioning Digital Engineering activities to a lower cost cloud environment and completing initial environment development activities in FY26.
FY2025–FY2026: what came before
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.
Provides the entire digital engineering ecosystem - which includes a cloud-based Digital Engineering (DE) environment and a government owned software development, Artificial Intelligence, and machine learning environment using a Development/Security/Operations (DevSecOps) software and Digital Twin technology development approach. DE costs include the software (SE) licenses for the requirement Product Lifecycle Management (PLM) software, Models Based Systems Engineering (MBSE) SysML modeling tools, data management and analysis, and modeling & simulation software. DevSecOps costs include the infrastructure required to implement the XM30 Software Pathway program, and multiple vendors developing software in a government furnished cloud environment - which are based on the licenses and pipelines required for the oversight and development of XM30 Software using an agile DevSecOps software approach. Integration costs include the creation of Automatic Program Interfaces (API) between the PLM software and various government owned and commercial tools. This also encompasses future cloud security enhancements, data backups and data archiving. This effort also funds the Virtual Systems Integration Lab (VSIL) environment hosted on the Digital Acquisition Environment (DAE) that seeks to virtualize computing hardware and software for computing, graphics, and memories associated with the vehicle designs. The use of Virtual Machines (VMs) within the DAE will emulate the computing hardware specifications of the hardware. Software will integrate from the DevSecOps environment and virtualize computing machines, develop the test software evaluating computing resource constraints, seeking to integrate and evaluate the interaction amongst the virtual machines. These VMs will be instantiated by scripts based on the hardware specifications in the vehicle's model-based definition. The VSIL environment will provide early and increased frequency of virtual testing of computing hardware facilitating reduced uncertainty of hardware performance.
Provides the entire digital engineering ecosystem - which includes a cloud-based Digital Engineering (DE) environment and a government owned software development, Artifical Intelligence, and machine learning environment using a Development/Security/Operations (DevSecOps) software and Digital Twin technology development approach. Cost includes further scaling up licenses, capacity, and support commensurate with the growth of MS&A, Architecture, and Test Evaluation teams. DE costs include the software (SE) licenses for the requirement Product Lifecycle Management (PLM) software, Models Based Systems Engineering (MBSE) SysML modeling tools, and logistics and modeling & simulation software. DevSecOps costs include 2 vendors developing software in a government furnished cloud environment - which are based on the licenses and pipelines required for the oversight and development of XM30 Software using an agile DevSecOps software approach. Integration costs include the creation of Automatic Program Interfaces (API) between the PLM software and various government owned and commercial.
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 | 28.3 |
| FY2026 | Enacted | 33.6 |
| FY2027 | Request | 21.7 |
This activity is 7.5% of project CF6's FY2027 request and 7.5% of PE 0605625A'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.
10 activities in project CF6
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.