Automated Parking Technology Comparison
Automated Parking Technology Comparison: Vehicle Interfaces and Vehicle Movement Architechitures
There is no single best automated parking technology. The clearest comparison separates two design decisions: how the vehicle is supported and how it is moved and stored. Pallet or palletless interfaces can be combined with different movement architectures, and each combination is appropriate under specific project conditions.
The choice is driven by six variables, in roughly this order of influence: peak throughput requirement, site geometry and depth, vehicle mix, tolerance for downtime, EV charging strategy, and the vendor’s ability to support the system for twenty plus years.
Successful projects depend on selecting the appropriate system configuration and choosing a vendor capable of delivering and supporting the installation throughout its lifecycle.
First, a distinction: semi-automated vs. fully automated
Two categories are frequently compared as though they were alternatives, but they solve different problems.
Semi-automated systems e.g., car stackers and puzzle systems, keep the driver in the loop. The driver maneuvers onto a platform, leaves the vehicle, then the machine shuffles platforms horizontally and vertically to reach the required space. They are the lowest-cost way to add parking density and they are well proven in small residential and mixed-use projects. Their limits are throughput and dependency: retrieval times lengthen as levels and occupancy increase, duty cycles are high, and in some configurations a single failure can immobilize several vehicles.
Fully automated systems remove the driver entirely. The driver stops in a transfer room, leaves the vehicle, and the system stores and retrieves it without human involvement. Density, throughput engineering, redundancy, controls and lifecycle support depend on the combination of vehicle interface and movement architecture selected for the project.
Two design decisions that define a fully automated system
Design decision 1: vehicle interface
A vehicle may remain on a pallet throughout storage or be handled directly by a palletless transfer device. This choice affects vehicle tolerance, clear height, moving mass, empty-pallet logistics and charging integration.
Design decision 2: movement and storage architecture
Shuttles and lifts, cranes or storage-and-retrieval machines, AGVs and tower arrangements describe how vehicles move through the garage. These architectures are not mutually exclusive with the pallet decision.
1. Vehicle interface: pallet-based systems
The vehicle is driven onto a pallet in the transfer area and remains on that pallet during storage and retrieval. Because the handling equipment engages a standardized carrier instead of the vehicle, the mechanical interface is consistent and repeatable across the system.
- Strengths: The handling equipment does not directly contact the vehicle; the interface can accommodate a broad vehicle population when designed for it; pallets can capture fluid drips; and charging equipment can be integrated into the pallet.
- Trade-offs: Pallets add capital cost, storage depth and moving mass. Empty pallets must be buffered, returned or repositioned after retrieval, so peak-hour performance depends on a clearly defined empty-pallet strategy.
2. Vehicle interface: palletless systems
No pallet remains beneath the vehicle in storage. Depending on the technology, interleaving combs or a wheel-lifting device transfers the vehicle. For example, Westfalia’s palletless Satellite® adjusts to the vehicle wheelbase, lifts at the wheels and allows the vehicle to be stored directly on a concrete or steel deck.
- Strengths: No pallet inventory or empty-pallet logistics; less moving mass; and direct storage on the deck with some systems. Subject to the structural and system design, eliminating pallet depth can increase usable vehicle clear height and allow taller vehicles within the same floor-to-floor envelope.
- Trade-offs: The handling device engages the wheels, so the system must be engineered for the expected wheelbases, tire and vehicle-weight range. Vehicle positioning must be more or less precise depending on the system, and unusual vehicles require explicit confirmation during design.
3. Movement architecture: fixed-rail lift-and-shuttle systems
Horizontal shuttles and vertical lifts move vehicles through a fixed rack or structure. The architecture may use either a pallet-based or a palletless vehicle interface, and capacity and throughput can scale through additional shuttles, lifts, aisles and transfer areas.
- Strengths: High density and throughput potential; defined travel paths; configurable redundancy; and efficient use of regular, multi-level geometry.
- Trade-offs: Rails, rack interfaces and transfer points require coordinated geometry. Performance depends on the number and location of shuttles and lifts, control strategy, storage depth and occupancy.
4. Movement architecture: AGV systems
Automated guided vehicles (AGVs) operate on an open floor plate rather than fixed rails. Many systems move a pallet or tray carrying the vehicle, while other carrier arrangements may also be used. Navigation can rely on markers, lasers, LiDAR or other positioning technology.
- Strengths: Irregular floor plates and some existing garages may be accommodated; capacity can scale by adding AGVs; and a single AGV outage may reduce performance rather than stop the entire system, depending on access routes and controls.
- Trade-offs: AGVs require travel clearances and suitable floor tolerances. Density and peak throughput depend on the layout, charging strategy, fleet size, traffic control, navigation reliability and software maturity.
5. Movement architecture: tower and silo systems
A single lift, usually with a turntable, serves spaces stacked around a central shaft in a narrow, tall footprint.
- Strengths: A very small footprint can suit constrained urban sites; the system can be built vertically with limited excavation; and the structure can become an architectural feature.
- Trade-offs: A single lift can limit throughput and create a concentrated failure consequence. Practical capacity, waiting time and limited redundancy due to the limited number of lifts and transfer points.
6. Movement architecture: crane-based rack systems (warehouse AS/RS lineage)
A storage-and-retrieval machine (SRM) works an aisle within a rigid rack or structure, moving in multiple axes simultaneously. This architecture has been used in high-density industrial warehousing for decades, adapted to vehicles. Storage can be single, double or multi-deep.
- Strengths: High density potential; simultaneous multi-axis motion; efficient use of deep-lane storage; and an established industrial-automation lineage.
- Trade-offs: A rigid rack and disciplined geometry are normally required. Redundancy and recovery must be designed around aisle access, crane quantity, transfer strategy and the ability to retrieve vehicles when a component is unavailable.
The pallet question, answered honestly
Pallet versus palletless is an important vehicle-interface decision, but neither approach is universally superior. The useful question is which operating, vehicle and lifecycle risks the project is best equipped to manage.
Choose pallets when the anticipated vehicle population is unusually varied or when the owner wants handling equipment to avoid direct wheel contact. Pallets may also simplify Level 1 or Level 2 charging integration because a charging interface can be incorporated into the pallet.
Choose palletless when usable clear height, density and cycle efficiency are priorities and the vehicle population can generally be defined. Direct-to-deck storage avoids empty-pallet logistics and, depending on the design, can accommodate taller vehicles within a fixed building envelope.
Ask any vendor a specific question: how does the system handle empty pallets during a peak retrieval period, and what does that do to throughput? A vendor who answers precisely, with a buffer strategy and a number, understands their own system.
Throughput: the number that decides most projects
Single-vehicle retrieval time, sustained vehicles per hour, queue length and percentile waiting time are different measures.
- How to size it: Establish the peak-hour requirement from the building use, not from the space count. A residential building empties over a broad morning window. A hotel discharges hard at checkout and again at valet-heavy events. An office generates two sharp peaks. A stadium-adjacent facility is an entirely different problem that may not be suitable.
- What to require: Ask for vehicles per hour at design occupancy, the assumptions behind it, and the queue length at peak.
- The trap: Throughput degrades as occupancy rises in most architectures, because free storage positions and clear travel paths become scarce. A system quoted at 90% occupancy behaves differently than one quoted empty. Insist that quoted figures state the occupancy assumed.
EV charging: how integration differs by architecture
EV-ready requirements in building codes have made this a design decision rather than an afterthought, and the architectures differ substantially in how they absorb it.
| Approach | How it works | Best fit | Consider |
|---|---|---|---|
| Per-space AC charging | A charger or outlet at every platform or space | Semi-automated systems; small counts | Per-space wiring and panel capacity scale linearly; slowest charge rates; capacity often under-used |
| Pallet-integrated charging | Charging interface built into the pallet | Pallet-based systems | Locks the project to a pallet architecture; charging hardware multiplies with pallets |
| Fixed charging bays | Vehicles are transported to dedicated charging positions | AGV and rack systems | Bay transfers consume system throughput; per-bay electrical infrastructure |
| Mobile overhead charging (gantry) | A mobile DC charger travels overhead to vehicles and serves multiple spaces sequentially from centralized electrical infrastructure | Covered configurations with adequate overhead clearance and compatible vehicle positioning | Requires overhead clearance, charge scheduling and project-specific integration; one gantry serves multiple vehicles sequentially |
The economic question to model is not cost per charger but installed cost per vehicle actually charged during the required dwell period, including panel capacity, utility service, demand management and operating schedule. Westfalia’s WePlug® system uses a mobile overhead 50kW DC fast charger to serve multiple vehicles sequentially from centralized electrical infrastructure. Compatibility depends on overhead clearance, system geometry, vehicle positioning, electrical capacity and project-specific integration.
Important! Evaluation criteria beyond the hardware
Hardware is the visible part of the decision. In practice, the risks that damage projects are commercial and operational. It is very important for project success that a rigorous evaluation occurs and should cover:
- Software ownership, support and escrow. Identify who owns and maintains the control and supervisory software, how it is licensed, whether source code or recovery materials should be held in escrow, and who responds to a software-related service call. Automated parking is a software-dependent electromechanical system, so controls support and modernization planning belong in the lifecycle strategy.
- Contractual performance. Define throughput, percentile retrieval time at design occupancy, availability, queue assumptions, recovery performance and service response times in the contract rather than relying on marketing descriptions.
- Vendor viability. Review audited financial standing, parts-availability commitments, service organization, controls ownership and the plan if the vendor is acquired or ceases operations. The objective is to protect a long-lived building asset from supplier and obsolescence risk.
- Operating references. Visit a system of comparable size, configuration and duty cycle that has operated for several years and speak with the developer or owner.
- Service model. Evaluate preventive maintenance, remote monitoring and diagnostics, local technician coverage, response commitments, spare-parts strategy, recovery procedures and the modernization plan for major components and controls.
- Codes, permitting and life safety. Confirm the applicable building, fire, electrical and accessibility requirements; the authority having jurisdiction; emergency access; fire-protection approach; and the approval path before design is fixed.
- Building integration. Evaluate structural loads, clear heights, vibration and noise, drainage, ventilation, maintenance access, transfer area layout and interfaces with architectural and MEP systems.
- Lifecycle value and adaptability. Compare total installed and operating cost, energy assumptions, expansion options, vehicle-envelope changes, EV growth and planned controls modernization: not only initial equipment price.
Frequently asked questions
In a pallet-based system, the handling equipment moves a standardized carrier beneath the vehicle. In a palletless system, a comb or a wheel-lifting device handles the vehicle directly. Pallets provide a broad, repeatable interface. Palletless direct-to-deck storage removes empty-pallet logistics and can improve clear-height utilization, depending on the design.
Neither is universally better. AGVs can suit irregular or retrofit floor plates. Fixed-rail shuttle, lift and crane arrangements can offer more density or higher peak throughput in regular geometries. The deciding factors are site geometry, equipment quantity, route redundancy, vehicle interface, occupancy and the required cars per hour.
No architecture is always fastest. Compare sustained vehicles per hour, percentile waiting time and queue length at design occupancy against the same demand profile. Results follow the number and speed of shuttles, lifts, AGVs and cranes, the number of transfer areas, storage strategy, vehicle interface, occupancy and degraded-mode assumptions.
Yes, when the system is specified for the expected vehicle range. Pallet-based systems provide a broad interface. Palletless systems accommodate a defined wheelbase, tire, weight and dimensional envelope. Direct-to-deck palletless storage can also increase usable vehicle height within a fixed building envelope, depending on the project design.
Retrofits are possible. Feasibility depends on the existing structure, clear heights, column grid, floor tolerances, access routes, fire and life-safety strategy, and required throughput. AGV, semi-automated and fixed-rail solutions each suit different retrofit conditions, and a feasibility review against the existing drawings will determine the best solution.
Four approaches are in use: per-space charging, pallet-integrated charging, dedicated charging bays, and a mobile overhead charger that serves multiple vehicles sequentially. The appropriate choice depends on EV share, dwell time, charging demand, system geometry and available electrical capacity.
Mechanical and structural elements are typically designed for decades of service, while controls and software require planned modernization on a shorter cycle. Lifecycle planning should assume at least one significant controls upgrade and continuous parts availability, which is why vendor longevity firmly belongs in the evaluation.
Next step
Architects and parking consultants: request technical coordination for design criteria, structural loads, clear heights, transfer area configuration and drawing resources.
Developers and owners: submit plans for a preliminary feasibility review so capacity, throughput and cost ranges can be modeled against the site.
Related reading: How Automated Parking Works · WePlug® Automated EV Charging · 500 Walnut and 4211 Chestnut case studies.
Author: Ian Todd, EVP of Automated Parking
