FASCOM and AutoWarCom: The Army's Bet on Centralized Autonomous Acquisition

BLUF — Bottom Line Up Front

Acting Secretary of the Army Adam R. Telle directed the creation of the Futures and Autonomous Systems Command (FASCOM) in a memo signed October 1, 2026. General Christopher LaNeve, Vice Chief of Staff of the Army and Acting Chief of Staff, selected Futures and Concepts Command for redesignation as FASCOM on October 13. The memo also designates a Portfolio Acquisition Executive directed to prioritize fielding of six priority autonomous capabilities by FY2028. The structure is intended to fix a recognized weakness of Army Futures Command—concept and research work without direct acquisition authority. For program offices and vendors, the practical question is whether FASCOM can convert that mandate into funded programs before two larger dependencies resolve: a final FY2027 NDAA provision for the planned joint Autonomous Warfare Command, and supplemental funding from a reconciliation bill that must pass in a narrow lame-duck window before Democrats take control in January.

Why Army Futures Command Wasn't Enough

Army Futures Command stood up in 2018 to fix the Army's broken requirements process. It produced modernization concepts and helped develop next-generation capabilities across Army modernization priorities. The recognized structural problem was acquisition authority: requirements flowed one direction, buying decisions remained at the Pentagon in program executive offices that AFC didn't control, and the two rarely synchronized at the pace combat experience demands. AFC was folded into a 2025 consolidation with the Army's Training and Doctrine Command.

Retired two-star general John G. Ferrari, a senior fellow at the American Enterprise Institute, described the new command to Defense One as: "So maybe this is kind of Futures Command 2.0, right?" Defense One's reporting frames the contrast as FASCOM having acquisition authority where AFC did not. Ferrari's own read was more cautious: "If it's just led by an acquisition executive, then you're going to have the same problem that the Army always has… not a warfighter." Army.mil describes FASCOM as led by a three-star general officer, not an acquisition executive alone.

What the October 1 Memo Actually Directed

Acting Secretary Telle signed the "Army Autonomous Initiatives" memo on October 1, 2026, directing three things: establish FASCOM, designate a Portfolio Acquisition Executive (PAE) for Autonomy, and define priority autonomous capabilities for fielding no later than FY2028. LaNeve's October 13 redesignation announcement followed that directive.

"This goes beyond drones," LaNeve said. "FASCOM will pioneer operational concepts that harness autonomous capabilities across all warfighting functions."

FASCOM will consolidate five organizations: the Combat Capabilities Development Command, Medical Research and Development Command, 75th Innovation Command, Joint Modernization Command, and the Transformation Decision Analysis Center. The Vice Chief's guidance describes these as the expertise base the new PAE will depend on to meet Telle's directive. Each absorbed command has distinct culture, existing industry relationships, and research agreements. Integrating them under a common acquisition framework is a management challenge that the redesignation announcement doesn't resolve automatically.

The Portfolio Acquisition Executive's Mandate

Autonomous programs had previously sat under Capability Portfolio Executive Mission Autonomy, within PAE Layered Protection and Integration (Breaking Defense). The new PAE designation gives autonomous systems programs a dedicated executive rather than a sub-portfolio inside a larger office. The memo directs that executive to prioritize acquisition and fielding of six capability areas by FY2028:

Autonomous fires
Autonomous combat vehicles
Watercraft resupply autonomy
Breaching systems
Reconnaissance, surveillance, and target acquisition
Crewed-uncrewed platform teaming

FASCOM will also create capability-based formations around autonomous long-range fires, protection, tanks, logistics, and obstacle breaching—aligned to the Army's four-element operational warfighting framework: convergence, strike, close battle, and endurance.

The mandate is meaningful only if it comes with the funding to execute. Ferrari told Defense One that the key to bringing it all together would be the funding, which would need to come from a reconciliation bill; otherwise the Army must wait until the FY2028 budget cycle. As documented in the DAWG budget analysis, $53.6 billion is the mandatory share of a department-wide autonomous systems line in the FY2027 budget request, with that share dependent on reconciliation legislation. Republicans lost both chambers in the November midterms; Democrats take control in January, leaving a narrow lame-duck window for a reconciliation push. On November 5, Secretary Hegseth called on Congress to pass a reconciliation bill of at least $350 billion—the reconciliation half of the FY2027 request, which carries the $53.6 billion mandatory autonomous systems share. FASCOM's FY2028 timeline depends on whether that push succeeds before the new Congress is seated.

AutoWarCom: The Planned Joint Destination

Telle described the Army-to-DoD relationship at the AUSA annual meeting: "We're pushing autonomy down into our units, but when it comes to having and making sure that the left hand in the Army knows what the right hand of the Army is doing, this happens at Fascom; then Fascom feeds up into Autowarcom." Defense One reported that FASCOM could nest under the planned joint command as a service component.

Secretary of War Pete Hegseth announced the Autonomous Warfare Command (AutoWarCom) on September 30, 2026, at Marine Corps Base Quantico. He framed it around a specific operational lesson from Ukraine: "Ukraine's lesson is not that one type of drone wins wars, but rather the need for a purpose-built system that maximizes the ability to adapt." AutoWarCom is intended to "fuse procurement with operations at scale, and then allow warfighters and engineers and entrepreneurs to learn, adapt, and rapidly iterate on their domain and their mission."

AutoWarCom carries a target establishment date of October 1, 2027, and requires congressional legislation. The House's FY2027 NDAA (H.R. 8800), passed July 22, includes no comparable provision. The Senate's S. 4784 includes Section 917, which would permit a Robotic and Autonomous Systems Command; the bill has cleared committee and is awaiting Senate floor action. No conference is currently under way. The interim Project Agincourt, led by Owen West, CEO of the War Department's Direct Reporting Portfolio Manager for Unmanned Systems, and Senior Chief Max Strasiser, is charged with laying the groundwork over the next year. At AUSA, Hegseth described it as the culmination of an intent present "since Day 1."

For vendors competing in multi-domain autonomous systems, AutoWarCom represents a potential future single point of authority for joint procurement, intended to function with service-like authorities. That future depends on a final NDAA provision.

Three Risks That Could Stall the Restructuring

Congressional authorization. The final FY2027 NDAA will determine whether AutoWarCom can be established with its intended authorities. If a provision permitting—but not requiring—the command is enacted, actual establishment may still depend on further authorization and appropriations. Without the joint layer, the services coordinate autonomous investment without a unified procurement authority. Acting Secretary of the Navy Hung Cao confirmed at AUSA that the Navy is increasing autonomous systems investment; structured joint purchasing across services depends on AutoWarCom's authorization to exist.

Funding availability. The autonomous systems funding FASCOM's new programs need is tied to reconciliation legislation. With Democrats taking both chambers in January and the lame-duck session's remaining window limited, the push is now a race against the calendar. If reconciliation doesn't pass, FASCOM must fund its priority programs through the FY2028 budget cycle or find reprogramming authority within existing appropriations. Programs that need new starts, not just additional procurement, face a real constraint on the FY2028 fielding mandate.

Organizational integration. Absorbing five organizations requires more than a redesignation. Each predecessor command has existing contract vehicles, program oversight relationships, and institutional knowledge built around its previous mission. FASCOM's PAE will need to rationalize potentially overlapping programs, determine which contract vehicles carry forward, and retain the people who know them. That's an execution challenge with no structural solution.

What Acquisition Officials and Industry Should Do Now

For program offices currently aligned to the five absorbed commands: identify which PAE office will own your program once FASCOM's internal organization is formalized. The pace of internal reorganization in a redesignated command varies; proactive engagement with the new PAE staff is more reliable than waiting for formal notifications. If your program supports any of the six FY2028 priority areas, treat it as a candidate for early execution under existing vehicles, independent of reconciliation.

For industry competing in autonomous systems: the six priority areas now converge toward a single acquisition executive. Expect consolidated procurement rather than fragmented service-level buys across former predecessor offices. That shifts competitive positioning toward portfolio-level interoperability and cross-domain integration—not just platform-specific performance. Vendors who can demonstrate how their system fits the crewed-uncrewed teaming architecture, or how their fires or ISR capability integrates with the convergence framework, have a structurally different pitch than point solutions.

For joint planners and other services: Acting Secretary Cao confirmed the Navy is increasing autonomous systems investment. FASCOM's cross-service coordination role—sharing purchasing power and best practices—is part of its mandate, but those coordination mechanisms are yet to be established. Identify your service's program overlap with FASCOM's six priority areas before those structures are finalized.

The Central Bet

The Army is betting that centralizing autonomous acquisition under a dedicated executive, nested within a future joint command, produces better outcomes than distributing that work across multiple program executive offices and research commands. The recognized weakness of AFC—no acquisition authority—informs that bet. FASCOM's PAE mandate is the structural change. Ferrari's caution is worth taking seriously too: separating acquisition from warfighting expertise created problems in the past. The analysis suggests FASCOM's three-star command structure, combining warfighting leadership with direct acquisition authority in the same organization, is designed to hold both together—but only if the command is staffed and resourced to exercise both simultaneously.

Whether the bet pays off depends on things outside FASCOM's direct control: a final NDAA provision for AutoWarCom, funding from reconciliation or the FY2028 budget cycle, and the ability to integrate five inherited organizations without losing the institutional knowledge that makes each of them useful. All three are live uncertainties. Program offices that plan against only the favorable scenario should expect at least one revision.

One dimension of that integration challenge is specific to AI-enabled platforms. As FASCOM builds its acquisition framework, the question of how AI assurance requirements get embedded in source selection criteria and contracts from the start—not evaluated after prototype delivery—is not settled. Spartan X is working toward that problem through the Arbiter platform in development—applying multi-model verification to structure corroboration and performance bounds for AI components before they reach decision-critical integration points.