Forterra and May Mobility selected for military-base autonomous shuttle prototyping
Forterra and May Mobility were selected with four other vendors to advance to Phase III of the Department of War Innovation Unit’s Robotic Operations for Autonomous Delivery and Sustainment (ROADS) challenge. The up-to-$30 million program is testing commercial self-driving vehicles for base shuttles and logistics trucks, with goals that include using government vehicles more effectively and reducing the time personnel spend driving routine trips.
May Mobility will supply its autonomous driving system and passenger vehicles; if adopted, riders could request trips through a rideshare app. Forterra will operate the prototype through OneLink, which gives installation leaders a live vehicle map and dashboard with installation-specific parameters. May Mobility describes its onboard model as predicting up to 10 seconds ahead and evaluating multiple driving strategies.
Vendor mapping is planned for November, followed by phased demonstrations through 2026, including a month-long pilot at Fort Benning. The design includes onboard safety operators, remote assistance and conservative safe-stop behavior. Selection advances the teams to prototyping; broader adoption remains contingent on evaluation of technical performance, operating suitability, user needs, safety and data management.
Bases can have government vehicles sitting idle while personnel are diverted from training to shuttle people and equipment. This prototype tests whether pooled, on-demand autonomous service can make those assets more useful without shifting transport demand onto additional staffed trips.
Installation transport managers can use the OneLink map and trip demand to assign vehicles to recurring clinic, range and facility movements, while setting local operating limits and routing exceptions. The planned pilot should retain safety operators and remote assistance while the installation measures service reliability and intervention rates.
Before funding a broader rollout, require the Fort Benning pilot to report vehicle use, passenger wait time, personnel hours returned to training, completed trips, safety interventions and data-handling controls against a current-service baseline.
Campus, base and large-site transport teams can first map recurring short trips and current vehicle idle periods, then test a request-based shuttle on a bounded service area. Keep dispatch ownership, rider escalation and safe-stop response with named staff until operational evidence supports reducing those controls.