The budget split, with the denominators intact
The official OSW RDT&E justification, printed pages 991–992 identifies Mission Command Applications within PE 0604122D8Z, project 668. Its figures are in millions of dollars:
- FY2025: $103.241 million.
- FY2026: $240.485 million.
- FY2027 request: $2,030.963 million.
- Maven-related increase: $1,589 million to expand access and support the Joint Force AI-Enabled Headquarters initiative.
- VJOC increase: $60 million for the Virtual Joint Operations Center.
The out-year planning figures run from roughly $1.93 billion to $1.98 billion annually through FY2031. They are planning amounts, not a flat enacted commitment. The $1.589 billion Maven figure is an increase described within the justification; it should not be presented as the complete cost of Maven across all accounts.
The request also describes engineering support, data integration, third-party applications, development infrastructure and cloud costs. These are parts of delivering a service, not simply purchasing more licenses. Requested funding remains subject to congressional action and subsequent execution.
Enterprise adoption needs more than a common screen
The contracting history gives another measure of the expansion. The Department announced a $480 million Maven Smart System prototype award in May 2024 and a $795 million modification for software licenses in May 2025, under contract W911QX-24-D-0012. The announcements specify that individual orders determine work locations and funding. These contract amounts should not be treated as dollars already spent, or added to the FY2027 request as though they were separate annual appropriations.
The budget explicitly describes a transition from rapid deployment toward a program of record and enterprise tooling. That is a strong direction of travel. It does not mean every instance becomes one physical deployment, every service adopts identical workflows or every acquisition decision is concentrated in a single contract.
The underlying integration problem has been documented. GAO's 2025 review found that CJADC2 lacked a comprehensive framework to guide investments and track progress, while organizations pursued their own data-integration efforts. A common product can reduce some duplication. It cannot independently resolve classification restrictions, inconsistent data meanings or unclear responsibility for shared services.
Program-of-record status also does not guarantee future appropriations. Its practical value depends on ownership, planned development, sustainment and accountability being carried into actual budgets, contracts and operational arrangements. Suppliers should identify which organization buys their work, which integration path it uses and who accepts the result.
VJOC makes the connectivity question explicit
The budget describes VJOC as combining on-premises hardware and commercial software to provide browser-based access for low-connectivity users. That is an architectural complement to cloud-centered mission applications, rather than proof that all disconnected-operation problems have been solved.
A browser is a user interface, not a guarantee of connectivity or current information. The application behind it may depend on remote identity services, data feeds, licensing checks or compute. A credible low-connectivity design has to specify which functions remain available and what information they use when those dependencies cannot be reached.
Useful acceptance questions include:
- Which tasks remain possible under the network conditions defined for the deployment?
- How does the user distinguish current data from an older local copy?
- Which changes are retained locally, and how are conflicts handled when service resumes?
- What permissions remain valid, and how are expired or revoked access decisions treated?
- How much support, power and maintenance does the local capability require?
The $60 million line is much smaller than the Maven-related increase, but budget size does not establish engineering difficulty. Its value should be judged against a specified operational need and evidence that the funded capability meets it.
Common platforms concentrate some risks
Shared tooling can make an improvement available to many organizations. It can also distribute a flawed update or a misleading data product widely. Consolidation therefore changes the failure pattern rather than simply removing risk.
The assessment boundary should include the model, retrieved data, interfaces and user workflow. A good model can produce a poor recommendation from stale information. A correct data feed can be misinterpreted by an application using a different definition. A release that passes component testing can still create an operational problem when combined with another system.
This is why enterprise assurance should be an operating capability, with resources and ownership, rather than an assumed future procurement. The FY2027 OSW operations justification separately requests support for AI assessment, cybersecurity, training and program offices. These requests give program teams a basis for connecting delivery plans to funded support responsibilities.
Turn the request into a delivery plan
- Define the operational increments and the organizations responsible for each.
- Identify data products and interfaces needed for those increments, including permissions and ownership.
- Establish repeatable integration tests and evidence requirements for third-party applications.
- Test the promised low-connectivity behavior with representative users and dependencies.
- Fund monitoring, training, support and reassessment after changes.
- Report progress in terms of usable workflows and measured results, alongside spending and license counts.
The industrial opportunity extends beyond the anchor platform. Data engineering, integration, cybersecurity, evaluation and sustainment determine whether expanded access produces dependable capability. Each should have a defined place in the delivery plan, with evidence the government can inspect and reuse.
Sources and further reading
- Department contract announcement: Maven prototype, May 2024
- Department contract announcement: Maven software-license modification, May 2025
- FY2027 OSW RDT&E justification, project 668
- GAO: CJADC2 framework and progress
- FY2027 OSW operations and maintenance justification
Spartan X connects program execution with AI, cybersecurity and engineering so that enterprise adoption includes the less visible work: dependable data, tested interfaces and support for users beyond reliable reachback.
