Finding
Depots concentrate the hardest low-speed maneuvers an autonomous vehicle makes, and operators shape them through layout, charger management and dispatch rather than the driving software
Every shift starts and ends in the depot: tight turns, docking at chargers, reversing into bays, and people, forklifts and service vehicles in the same space. The vehicle's software belongs to the AV developer, but the lanes, markings, charger assignments, state-of-charge targets and dispatch windows belong to the operator. Fleet partners such as Moove, which runs Waymo depots in Phoenix and Miami, and Lyft's Flexdrive in Nashville, now do this work as a business.
The interfaces run through three systems the operator buys: the fleet management system (vehicle state, missions), the charger management system (usually OCPP 2.0.1, with ISO 15118-20 for plug-and-charge) and the yard management system (lanes, blocked bays, maintenance zones). Each needs open data feeds to the AV partner. Automated charging - inductive pads under SAE J2954, which Tesla has said Cybercab will use, or robotic connectors from makers such as Rocsys - removes the last routine human task in the charging lane.
Mixed fleets will share depots for years, so separation is the main safety lever: AV lanes, human-priority zones and defined areas for reversing. Driverless industrial vehicles inside the depot fall under ISO 3691-4, and mobile robots under ANSI/A3 R15.08. Standard layouts across sites let AV behavior transfer from one depot to the next. See Autonomous Fleet Depots for depot energy loads.
Touchpoints
Depot-to-autonomy touchpoints
| Touchpoint | Signals | System that carries it |
|---|---|---|
| Vehicle state | State of charge, health, autonomy readiness, next mission | Fleet management system |
| Depot state | Charger availability, lane status, blocked bays | Yard and charger management systems |
| Scheduling | Arrival windows, dwell targets, cleaning and service slots | Dispatch and fleet management |
| Policies | Speed limits, no-go zones, human-only areas, staging rules | Depot map shared with the AV partner |
| Data and OTA | Log upload, software and map updates | Depot edge network |
Design rules
Depot design rules for autonomous operation
| Area | Rule | Why |
|---|---|---|
| Lanes | Wide, marked lanes with simple geometry | Predictable paths for perception and planning |
| Separation | Split pedestrian, forklift and vehicle flows | Removes the densest interactions |
| Markings | Standard signs, stop bars and docking lines at every bay | Consistent visual patterns across sites |
| Clutter | No ad hoc storage in AV lanes | Unmapped obstacles stall vehicles |
| Charging | SOC target per mission type; chargers assigned by departure time | Avoids queues at dispatch |
| Dwell | Charge, clean, upload and update in the same stop | Shorter arrival-to-dispatch time |
Failure modes
Where integration breaks
| Failure | Cause | Fix |
|---|---|---|
| Vehicle blocked from charger | Conflicting flows, ad hoc parking | Reserved bays and enforced lanes |
| Long dwell | Charge, clean and service out of sequence | One schedule across all three |
| People in AV lanes | Shortcuts, improvised loading | Physical separation and training |
| Vehicle stalls | Ambiguous markings or signage | Standard markings; remote assistance |
Sources
Sources and scope
- Scope
- Fleet Autonomy Depot Integration
- Sources
- Waymo, Moove and Lyft (fleet partnerships); Open Charge Alliance (OCPP); ISO 15118; SAE J2954; ISO 3691-4; ANSI/A3 R15.08; Tesla (Cybercab, 2024)
- Updated
- October 2026