Preparing the published article.
Service Robot Constraints in Public Buildings: A Checklist
Check lifts, doors and peak-hour constraints before committing a service robot to a public building.
Check Lifts And Doors Before Anything Else
In public buildings, the constraint that ends a deployment is usually a doorway, a lift or a fire door, not the cleaning task itself. Survey these first, and survey them with a tape measure rather than a brochure. For every door the machine must pass, record the clear opening width with the door held in its normal operating position, the type of door, and whether it is normally open, held open, or self-closing. The type matters more than the width: a manual swing door, an automatic sliding door, a turnstile, a speed gate and a fire door each present a different problem, and a machine that crosses an automatic door in a demonstration may never cross a fire door at all. Record thresholds, floor-level changes and any tactile paving along the route as well, because these are common reasons a route fails after it has been approved on paper. For lifts, record the internal dimensions with the door open, the door dwell time, whether the lift can be held by a person pressing a button, and whether the building has a destination-control or group-control system. Then measure lift demand at peak hour. A service robot that needs exclusive use of a lift during a peak period is competing with people, and that competition is the real constraint, not the lift hardware.
Test Against The Peak Hour, Not The Quiet Hour
A demonstration held before opening hours proves very little about a public building. Run the same route at the busiest time the building actually experiences, and record what changes: where the machine has to yield, where people walk around it, where its route crosses a queue, a dining area, a buggy route or a wheelchair path. Log the stops and the yields per pass rather than describing the run as smooth or busy, and record the time the route took at peak against the time it took when the building was quiet. Then check the interfaces that turn a machine into a building system. Fire alarm interface is the one most often left until late: establish what the machine does when the alarm sounds, whether it parks or continues, where it parks, and whether that parking position blocks an escape route. Record the answer in writing, with the person who confirmed it named. Check audio too. A spoken warning or a chime has to be audible above the ambient noise of a lobby or an atrium, and a message that cannot be heard does not count as a warning.
Record Decisions Where The People Are
Public-facing deployments need measurement that ordinary back-of-house equipment does not, because complaints, incidents and near misses will surface through channels that have nothing to do with the cleaning team. Before you start, agree a small evidence set: who receives a complaint about the machine, how it is logged, what counts as an incident, and how a near miss is recorded. Keep the record simple enough that a security officer or a concierge can complete it on the spot, since that is where most observations will originate. Then check public information. Signage should say what the machine is doing and who to contact when it stops; if the machine carries instructional or safety text, someone in the building needs the authority to change it when routes change. Check that instructions exist in the languages actually spoken in the building. Set a review point with a date and a decision attached, for example whether to extend the route, hold it, or withdraw it. Base that decision on the records you collected rather than on how the machine looked on the first day.
Photo credits: the images in this article are licensed reference photographs of the relevant robot class, credited with author and licence in each caption; they are not photographs of the specific equipment discussed. Licence and author details are recorded with each image.