Robot Buying Guide

Lift and Door Integration for Delivery Robots: Questions to Ask Before You Buy

Facts last checked: 2026-10-20 · Not legal advice

Scope. For hotels, hospitals, offices and residential buildings in the Gulf considering a delivery or cleaning robot that has to use lifts, automatic doors or access-controlled gates. This page is a list of questions built from public manufacturer and lift-maker information. It does not describe how any specific installation works; where we could not find a public answer we say confirm with the manufacturer. We give no prices. Anything we could not confirm says not verified .

1. What “lift integration” means

A robot cannot press lift buttons the way a person does in the systems described below; it exchanges messages with the lift’s control system. Public descriptions from four lift makers describe the same basic functions: the robot (or its server) places a lift call or a destination call, receives the lift’s position and door status, and the lift holds its doors while the robot enters and exits.

  • KONE’s Service Robot API lets robots make calls “from floor X to floor Y”, with real-time elevator position, direction and door status.[source, retrieved 2026-10-20] [source, retrieved 2026-10-20]
  • Otis Integrated Dispatch is described as “a cloud-based or on-premise API solution” for connecting service robots to Otis elevators, with door open and close times adjustable to the robot’s speed.[source, retrieved 2026-10-20]
  • Schindler’s BuilT-In Robot Service Connection (Jardine Schindler page) has the robot send a destination call and ask for the lift’s position and door status, connecting via Wi-Fi, 4G or 5G.[source, retrieved 2026-10-20]
  • Mitsubishi Electric’s robot-movement support service registers calls and destinations on the robot’s request, keeps the doors open while the robot boards and exits, and can also pass a robot ID to an access-control system to request unlocking.[source, retrieved 2026-10-20] [source, retrieved 2026-10-20]

Otis contrasts its API approach with “traditional hard-wired integrations”, and the Mitsubishi leaflet shows an interface device installed at the lift control panel. So there is more than one way to connect, and which one applies to your lifts is a question for both the robot side and the lift company.

2. What the robot makers state publicly

ModelWhat the manufacturer’s page saysSource
KEENON W3“The IoT Elevator Rider”: the W3 “can now take the elevator for item delivery”KEENON W3 page[source, retrieved 2026-10-20]
KEENON C40“IoT elevator & door auto-passing”KEENON C40 page[source, retrieved 2026-10-20]
KEENON C55IoT elevator and gate interconnection (feature list)KEENON C55 page[source, retrieved 2026-10-20]
AGIBOT C5“Access Control and Elevator Linkage”AGIBOT C5 page[source, retrieved 2026-10-20]

Each line is a single manufacturer statement. None of these pages says which lift brands or models are supported, what hardware is installed, or whether the integration is direct or through a lift maker’s API: confirm with the manufacturer. KEENON’s Docs Center has an “Elevator Equipment” section, but it showed “No Data” when we opened it on 2026-10-20.

KEENON’s map-deployment documentation (the same text appears in its hotel and cleaning-robot sections) does give some on-site rules for lift areas: scan the lift car by rotating slowly inside it; apply frosted film if the car walls are transparent, light-absorbing or reflective; and set the in-lift, waiting and queuing points 60–100 cm from the lift door.[source, retrieved 2026-10-20] [source, retrieved 2026-10-14] This is one KEENON document published twice, so treat it as a single source.

3. Questions for the robot manufacturer or dealer

  • Which lift brands and controller models has this robot model been connected to? Is there a list, and is it for the Gulf?
  • Does the robot connect through the lift maker’s API (for example KONE, Otis, Schindler, Mitsubishi Electric), through hardware you install at the lift panel, or both?
  • What do you supply (module, gateway, software licence), and what must the building or lift company supply?
  • Which network does the lift link use: building Wi-Fi, the robot’s 4G, a cloud server? Where is that server, and who operates it?
  • How many robots can share a lift group, and does the robot ride with passengers or wait for an empty car?
  • What happens on a lost connection, a full car, a fire alarm or a lift fault? (The robot should not be inside the lift’s emergency procedures unless the lift company agrees.)
  • Which doors and gates can the robot pass: automatic sliding doors, swing doors with operators, turnstiles, access-controlled doors? Through which interface?
  • Is the integration covered by the same warranty and support as the robot? Who answers when the robot and lift disagree?
  • Can you show a running installation with the same lift brand?

4. Questions for building management or the facility owner

  • Which lifts and doors would the robot use? List the lift maker, model and age of each, and the access-control system and its vendor.
  • Are any lifts under a maintenance contract that restricts third-party connections?
  • Does building policy allow a robot to ride with guests or patients, or only in service lifts or at set hours?
  • Which network can the robot and lift interface use, and does IT security need to approve it? Lift makers stress encryption (Otis states all robot–elevator communication is encrypted), so ask what your IT team requires.
  • Who pays for and owns any installed hardware, and who removes it at the end?
  • Fire and life safety: who signs off that robots and installed devices do not affect lift or door emergency functions? (For Dubai corridor and egress notes, see our site survey checklist.)

5. Questions for the lift company or access-control vendor

  • Do you offer a robot interface for our lifts (for example a robot API or a gateway), and which controller generations does it support? Otis’s own pages give its compatibility as “most Otis elevators manufactured since 2000” on the product page and “since the 1990s” in an innovation article,[source, retrieved 2026-10-20] [source, retrieved 2026-10-20] and Mitsubishi notes conditions on which lifts can be served,[source, retrieved 2026-10-20] so ask for your exact units.
  • Is that interface available in our country, and through which local entity? not verified for each brand in the GCC.
  • What hardware do you install, and does installation need an inspection or authority approval? Otis says its engineers “coordinate with local safety inspectors”. Local requirements in each GCC state are not verified .
  • Does the robot maker’s software already work with your interface? Otis and Schindler both describe test or simulation environments for robot developers.[source, retrieved 2026-10-20] [source, retrieved 2026-10-20]
  • Is the robot interface a subscription or a one-time service, and what does it cover? (Ask for terms; we publish no prices.)
  • For doors: can the access-control system accept a robot identity, and how is that logged? Mitsubishi describes passing a robot ID for authentication and unlocking;[source, retrieved 2026-10-20] whether your vendor offers anything similar is a question for them.

6. Is there a standard?

In Japan, a robot–elevator interface standard exists. The Robot Revolution & Industrial IoT Initiative (RRI) published “Robot/Elevator Cooperation Interface Definition” RRI B 0001:2021 (draft rev. 2.0) on 2021-06-04; its public part says it defines the interface between a robot server and an elevator server, that only one robot rides a car at a time, and that contact-type (hard-wired) systems without an elevator server are outside its scope.[source, retrieved 2026-10-20] Its successor, RFA B 0001:2025, was published by the Robot Friendly Asset Promotion Association in Japanese (2025-02-20) and English (2025-07-31); the full text is sold, and we have not read it.[source, retrieved 2026-10-20] Otis says its interface is compatible with the RRI definition.[source, retrieved 2026-10-20] Whether any GCC authority references this or any other robot–lift standard is not verified . Do not assume a robot or lift “complies” with it unless the supplier shows evidence.

7. Checklist

  • Lifts listed: maker, model, controller age, maintenance contractor.
  • Doors and gates listed: type, operator, access-control vendor.
  • Robot maker confirmed in writing which of those lifts and doors it has connected to, and how.
  • Lift company confirmed a robot interface is available for your units and in your country.
  • Division of supply agreed: robot side, lift side, building side, network.
  • IT security approved the network path.
  • Fire and life safety sign-off arranged.
  • Failure behaviour agreed: lost link, full car, alarm, lift fault.
  • Lift-area mapping rules met (car walls scannable, space for waiting and queuing points).
  • Trial in your building with your lifts before full rollout; see the site survey checklist.

8. What we could not confirm

  • Which lift brands and controllers KEENON and AGIBOT robots are integrated with, and what hardware they use.
  • Availability of KONE, Otis, Schindler or Mitsubishi robot interfaces in each GCC state.
  • Gulf authority requirements for robot–lift or robot–door connections.
  • The content of RFA B 0001:2025 beyond its public description.
  • How the robots behave in lift emergencies.

Sources used

Related robot models