Deep Signal: Oshkosh Showcases Plug-and-Play War Machines at AUSA 2026

Oshkosh L-MAV and Modular Cannon Signal: What the AUSA 2026 Unveiling Means for Autonomous Ground Combat

Product Portfolio — Elbit Systems Ltd.

Signal Activity — Elbit Systems Ltd.

Deal History — Elbit Systems Ltd.

Competitive Positioning — Elbit Systems Ltd.

What Happened

Oshkosh Defense used AUSA 2026 to unveil two distinct autonomous ground platforms: the Light Multi-Mission Autonomous Vehicle (L-MAV) and a modular 10×10 mobile cannon platform. Both systems emphasize rapid payload swapping and open-architecture integration — the core pitch being that operators can reconfigure mission roles in the field without depot-level maintenance cycles. The L-MAV targets the light autonomous logistics and reconnaissance segment; the 10×10 cannon addresses mobile fires at a weight class below traditional self-propelled artillery. Neither platform carried announced contract values or confirmed unit orders at the time of the showcase, placing both firmly at PROTOTYPE/LIMITED deployment status.

Why It Matters

The “plug-and-play” framing is the operative signal here, not the hardware itself. Oshkosh is explicitly positioning these platforms around modular payload integration — the same architectural bet that Elbit Systems made with its Dominion-X autonomous management OS (launched February 2025, currently LIMITED deployment status). The convergence of two major defense primes on open-architecture autonomy within a 12-month window is not coincidental. It reflects a procurement signal from the U.S. Army and allied customers: proprietary, single-mission autonomous vehicles are losing favor against reconfigurable platforms that can absorb new payloads as threat environments evolve.

The modular cannon platform is particularly significant. Mobile fires have historically required purpose-built platforms — the ATMOS howitzer (Elbit, FIELDED) and the AS-90 (BAE Systems) are fixed-configuration systems. A 10×10 chassis that accepts interchangeable weapon modules compresses the procurement cycle for fires capability and reduces the logistics tail. MODERATE CONFIDENCE that this architecture will attract Army interest under the Mobile Protected Firepower and Long-Range Precision Fires modernization priorities, both of which have combined budgets exceeding $4B through FY2028.

Who Is Affected

Company	Platform	Deployment Status	Direct Exposure
Elbit Systems	Dominion-X OS, ATMOS howitzer	LIMITED / FIELDED	Moderate — ATMOS competes in mobile fires; Dominion-X competes as autonomy layer
General Dynamics	Stryker, Ajax	FIELDED / SCALING	High — L-MAV targets the light vehicle segment GD dominates
Textron Systems	RIPSAW M5, Cottonmouth	LIMITED	High — direct UGV competitor in light autonomous segment
Anduril Industries	Ghost 4, Roadrunner	LIMITED	Moderate — autonomy software layer competition
Shield AI	Hivemind	LIMITED	Moderate — autonomous mission management overlap
BAE Systems	CV90, AS-90	FIELDED	Low-Moderate — cannon platform threatens legacy fires architecture

General Dynamics faces the most immediate pressure. The L-MAV’s light autonomous positioning directly challenges GD’s Stryker-family derivatives in the 8–15 tonne class, and GD has no announced open-architecture UGV program at comparable maturity. Textron’s RIPSAW M5, currently at LIMITED deployment after Army Robotic Combat Vehicle evaluations, is the closest direct competitor — Oshkosh’s AUSA timing appears calibrated to maintain visibility in the same procurement conversation.

For Elbit Systems, the signal cuts two ways. The ATMOS howitzer (FIELDED, export-focused) competes in the mobile fires segment the 10×10 cannon targets, though ATMOS operates in a heavier weight class (wheeled 155mm). More strategically, Oshkosh’s plug-and-play architecture creates a potential integration opportunity for Dominion-X — or a competitive threat if Oshkosh develops a proprietary autonomy OS. Elbit’s E-CiX open framework is explicitly designed for third-party platform integration, making it a candidate autonomy layer for the L-MAV if Oshkosh pursues a software-agnostic approach. LOW CONFIDENCE on any near-term Elbit-Oshkosh integration given the absence of announced partnerships.

Anduril and Shield AI face a structural question: as hardware primes build their own autonomy stacks, the addressable market for pure-play autonomy software narrows. Both companies have argued that mission software is the defensible layer; Oshkosh’s plug-and-play emphasis suggests hardware primes are not conceding that argument.

What to Watch

• Q3 2025 – Q2 2026: Whether Oshkosh announces a named Army program office engagement for L-MAV under the Robotic Combat Vehicle-Light (RCV-L) or similar designation. RCV-L has a projected acquisition value of $1.2B–$2.4B over a full program of record.
• AUSA Annual 2026 (October): Payload integration demonstrations — specifically whether third-party sensors or weapons are shown on the 10×10 cannon platform, validating the modularity claim beyond the prototype stage.
• Elbit Dominion-X procurement wins: Any named multi-service contract for Dominion-X on a non-Elbit platform would directly validate the open-architecture competition Oshkosh is entering. Watch Elbit’s Q2 and Q3 2026 earnings calls for backlog attribution.
• Textron RCV-L competitive response: Textron has until approximately mid-2026 to demonstrate RIPSAW M5 upgrades before Army source selection timelines tighten. A Textron-Oshkosh head-to-head evaluation is the most likely near-term competitive forcing function.

Database Context

The Oshkosh signal fits a pattern visible across the robotics.press database: defense hardware primes are converging on modular, software-receptive architectures after a decade of purpose-built autonomous platforms underdelivering on operational flexibility. Elbit’s $25.2B backlog (September 2025) and Dominion-X’s open E-CiX framework represent one response — software-led integration across existing fielded hardware. Oshkosh’s approach represents the hardware-prime response: build the reconfigurable chassis and let the autonomy layer competition play out above it. Both strategies are rational given Army procurement signals, and both will be tested against the same operational requirement: autonomous ground systems that function in GNSS-denied, EW-contested environments without mission-specific hardware swaps.