AMRs Across Floors: Make the Elevator Interface a Verifiable Mission State

AMRs Across Floors: Make the Elevator Interface a Verifiable Mission State

In a multi-floor factory, an AMR route does not end at a floor boundary. The point that most often disrupts flow is the short interface in front of the elevator: the robot arrives before the car, the car arrives while the door zone is occupied, or the door opens but the combined envelope of the robot and carrier is not ready to pass. Treating all of these cases as simply waiting for an elevator makes the mission ambiguous and leaves exceptions to be judged on the spot.

A more robust approach is to treat the elevator as a shared asset that must be requested, confirmed, occupied, and released. A cross-floor AMR mission should include more than an origin, destination, and floor number. It should model the landing zone, elevator car, carrier, and destination corridor as one verifiable transport state. The robot can then distinguish between conditions that are ready, conditions that are pending, and a safe place to hold the load when the sequence is interrupted.

Start with a transport unit that is elevator ready

Before an elevator call is made, the transport unit itself needs to be defined. Consider a latent-lifting AMR carrying a wheeled material rack. The rack base, lift interface, tote shelves, and overall height must form a known configuration before the mission begins. Once the AMR has moved beneath the rack and lifted it, the casters should be clear of the floor and each tote should remain continuously supported by its shelf. The combined length, width, and height must also fit the door opening and cabin clearance. Establishing these conditions at dispatch prevents a robot that can reach the elevator from discovering too late that the carrier cannot safely enter it.

Use three release gates for one elevator trip

The first release gate is outside the landing. Reaching a waiting rectangle is not permission to approach the door. The waiting position should preserve a clear boundary for door travel, shared traffic, and the main aisle. At this point, the mission should confirm that the elevator request has been accepted, the landing waiting zone is unoccupied, and the carrier remains in a valid lifted state. If any condition is missing, the AMR holds position instead of repeatedly inching toward the doorway.

Figure 1: Before elevator entry, the AMR waits outside the door zone with clear carrier and aisle boundaries

The second release gate begins after the door opens. An open-door signal alone is not enough. The car must be at the landing, the door must remain open, the cabin must be passable, the sill and cabin floor must be safe to traverse, and the destination landing should have a usable receiving corridor reserved for the task. For a latent-lifting AMR, entry should be centered, slow, and continuous. It should not pause on the sill, steer sideways, or change lift state in the doorway. Connecting these facts in the mission state makes the sequence easier to verify than adding an isolated speed limit or warning message at the door.

The third release gate occurs after the car reaches the destination floor. The AMR should leave only after the door is fully open, the destination landing is clear, and the outbound corridor is still available. A parked AMR in the car is not a completed delivery. The carrier remains supported by the AMR until it reaches the controlled receiving position at the destination station, where lowering or the next handoff can begin.

Figure 2: With the threshold aligned and the destination landing clear, the AMR carries the rack out in a centered path

Keep the mission whole inside the cabin

When the doors close, the mission is not complete. It has moved from corridor travel to controlled waiting inside the cabin. The AMR should not be treated as free capacity and reassigned, nor should a brief network interruption erase which rack it is carrying or which station it is serving. The mission record should preserve the robot identity, carrier identity, lift state, current floor, destination floor, and the next permitted action. During elevator travel, the AMR remains stably parked. A new environment confirmation is required before movement resumes at the destination.

Exception recovery should protect the load and the aisle first

The value of a state-based elevator interface is most visible when something goes wrong. If door opening times out, the car does not arrive as expected, or the destination landing becomes occupied, the task should not immediately reroute or force a retry. The first priorities are to preserve the supported carrier state, retain the occupancy context of the cabin or waiting zone, and avoid creating a blockage at the threshold or in the main aisle. The mission can then enter an explainable hold, retreat, or assisted-recovery branch. A person responding to the event should be able to tell whether the robot is waiting outside, parked inside the car, or at the destination without permission to exit.

Validate recovery paths, not only a successful ride

Commissioning should cover normal entry, delayed door opening, a temporarily occupied destination landing, arrival with the door not fully open, task cancellation, a short communications interruption, and assisted recovery. Each case should be evaluated against two questions: Does the carrier always have an explicit support and parking state? Do the door zone and aisle remain understandable and releasable? Shifting acceptance from one successful elevator ride to a set of recoverable mission states turns the elevator into a dependable intralogistics interface.

For facilities that connect warehousing, production, and inspection across floors, elevators do not have to remain manual handoff points. Chengdu Beaver latent-lifting AMRs can be deployed around the site-specific conditions of material racks, landing zones, and elevator interfaces. The objective is not merely to enter the door quickly. It is to ensure that every entry, stop, and exit has clear prerequisites and a traceable next action.