A practical readiness guide for building owners planning autonomous inspection, cleaning, delivery or security robot deployments.

Professional illustration of an autonomous facility robot moving through a Singapore commercial building, connected to lifts, access doors, floor maps and an FM operations dashboard.

Autonomous robots are becoming a practical consideration for Singapore facility managers, warehouse operators, building owners and SMEs. Potential applications include floor cleaning, inspection, delivery, patrols and selected logistics tasks.

However, a robot deployment is not only a hardware purchase. The building must provide the access, connectivity, digital information and operating procedures that allow a robot to work safely and consistently.

This is especially important as facilities move towards more interoperable robotics. BCA has described a vendor-agnostic Robotic Middleware Framework trial intended to help robots from different manufacturers use shared building infrastructure, including lifts, and navigate buildings autonomously. The direction is significant for FM teams: future value may come from connecting several robots to a common operating environment rather than managing each robot as an isolated system.

What interoperability means for FM teams

Interoperability means that a robot can exchange information with relevant building systems and, where appropriate, operate through shared infrastructure. This could include lift controls, access points, maps, doors, charging areas, work-order systems and operational dashboards.

It does not mean that every robot will automatically work with every building. Compatibility still depends on technical interfaces, permissions, network conditions, physical layouts, cybersecurity controls, vendor support and the building owner’s operating policies.

Before selecting a robot, FM teams should therefore ask a broader question: Is the building ready to support autonomous work?

1. Audit the physical building environment

Start with a robot-readiness survey covering the routes, spaces and constraints that the robot will encounter. Document floor finishes, thresholds, ramps, narrow corridors, clutter zones, glass surfaces, loading areas, wet areas, lifts and areas with frequent human traffic.

For inspection robots, review whether plant rooms, risers, rooftops or service corridors can be accessed consistently. For cleaning robots, examine route availability, furniture changes, floor conditions and areas that require manual intervention. For delivery or security robots, consider loading bays, reception points, tenant access and after-hours movement.

Maintain accurate digital floor plans and identify changes that could affect navigation. A robot pilot should not rely on outdated drawings or assumptions about the building layout.

2. Review lifts, doors and access control

Vertical movement is one of the most important integration issues in multi-storey buildings. FM teams should determine how a robot could request and use lifts, identify its destination, enter and exit safely, and recover if a lift journey fails.

Review the available interfaces for lifts, turnstiles, gates, automatic doors and other access-controlled points. Confirm who owns each system, whether the vendor supports integration, what permissions are required and how access events will be logged.

Do not treat access integration as a last-minute technical detail. The robot’s operating routes, service hours and business case may depend on it. A building that supports only manual lift or door operation may restrict autonomous work to a single floor or require additional staff support.

3. Build a reliable connectivity and charging environment

Autonomous robots depend on dependable communications for navigation, task updates, alerts and fleet management. Map network coverage along intended routes, including lift lobbies, basements, loading areas and plant spaces. Identify dead zones, congested areas and locations where the robot may need to continue operating safely during a temporary connection loss.

Also plan charging and storage. A charging point needs a suitable location, power supply, physical protection and a clear process for cleaning, inspection and fault reporting. For multiple robots, consider whether charging areas could become a bottleneck or obstruct staff and emergency access.

These requirements should be reviewed with the building’s IT, engineering and operations teams before a pilot begins.

4. Connect robots to FM workflows and shared data

A robot creates limited value if its output remains inside a separate vendor application. Inspection findings, cleaning completion records, exceptions, images and alerts should be connected to the team’s existing operating workflow where appropriate.

Define which information is needed by which role. An operations supervisor may need task status and exceptions. An engineer may need an inspection image linked to an asset or location. A building manager may need service-level reporting and recurring issue trends.

Before integration, agree on common naming for buildings, floors, rooms, assets, routes and work orders. Establish data ownership, user permissions, retention expectations and escalation rules. A shared data layer or middleware approach can reduce duplicate interfaces, but it still requires clear governance and controlled access.

BCA’s Smart FM and AI guidance points towards data-driven operations, system integration and alignment across the FM value chain. The practical lesson is to design the workflow before choosing the technology.

5. Establish safety and operating controls

Robots operate around people, vehicles, equipment and changing site conditions. A deployment plan should define operating hours, speed or route restrictions, exclusion zones, manual override procedures, emergency stop arrangements, incident reporting and recovery after a fault.

Assess interactions with cleaners, security officers, contractors, tenants, visitors and delivery personnel. Consider wet floors, temporary obstructions, maintenance activities, fire doors, crowded events and construction works. The robot should have a clear handover process when an autonomous task cannot be completed.

MOM recognises robotics, sensors, video analytics and related technologies as applications that can support facilities management and logistics. Technology does not remove the need for risk assessment, competent supervision and suitable workplace procedures. Engage the relevant safety, engineering and operations stakeholders early.

6. Use procurement requirements that support interoperability

When evaluating suppliers, ask for more than a product demonstration. Request technical documentation covering application programming interfaces, supported building systems, map formats, authentication, data export, event logs, remote support and system availability.

Clarify who is responsible for lift and access integration, network configuration, site mapping, testing, software updates and fault recovery. Ask whether the robot can continue operating if one connected system is unavailable, and how it reports exceptions.

Contract terms should address data ownership, access to operational records, cybersecurity responsibilities, integration changes, maintenance windows, exit arrangements and the process for adding another robot or vendor later. A vendor-neutral architecture can help avoid unnecessary dependence on one platform, but technical and commercial compatibility must be tested rather than assumed.

7. Design a controlled pilot with measurable outcomes

A pilot should answer a defined operational question. For example, can an autonomous cleaning robot complete selected routes with less manual supervision? Can an inspection robot collect consistent observations from a defined area? Can the building support lift and door journeys without repeated intervention?

Choose a representative but controlled area. Record the baseline process before deployment, including staff time, task frequency, completion quality, exception handling and reporting effort. During the pilot, track measures such as successful task completion, human interventions, route availability, downtime, alert response and the quality of information delivered to the FM team.

Do not evaluate success only by robot operating time. The relevant outcome may be better visibility, more consistent inspection records, reduced repetitive work or faster escalation of issues. Review the results with the people who will operate and maintain the system every day.

8. Prepare the organisation, not just the site

Successful adoption requires role clarity. Decide who approves robot tasks, who responds to alerts, who maintains maps, who manages access permissions and who contacts the vendor. Train staff on normal operation, manual recovery and incident escalation.

Communicate with tenants and contractors where robots will operate in shared areas. Clear signage and simple instructions can reduce confusion during the pilot. Feedback from frontline teams is also valuable because they understand recurring obstacles that may not appear in drawings or vendor demonstrations.

A practical readiness checklist

  • Document robot routes, building constraints and areas requiring manual support.
  • Review lift, door, gate and access-control integration options.
  • Confirm network coverage, charging locations and physical storage arrangements.
  • Define common asset, location, task and event data requirements.
  • Set safety controls, operating procedures and fault-recovery responsibilities.
  • Request open integration and data requirements during procurement.
  • Run a measured pilot with baseline data and agreed success criteria.
  • Plan for multiple vendors, future integrations and system changes.

Prepare before you automate

Interoperable robotics can support more connected and flexible FM operations, but the foundation is building readiness. Infrastructure, access, data, safety, people and procurement must be considered together.

Singapore building owners and FM teams do not need to automate every task at once. A carefully scoped pilot can reveal where autonomous robots create genuine operational value and what must be improved before scaling.

ISS can support organisations reviewing engineering requirements, facility management workflows and AI automation opportunities. Contact ISS to discuss your engineering, facility management or AI automation requirements.

Further reading