How Singapore building operators can prepare for service-robot integration with facilities workflows and connected building systems.

Professional illustration of a Singapore commercial building with a service robot connected to facility-management software, lifts, doors and access-control systems.

Singapore’s facility-management conversation is moving beyond the question of whether a service robot can perform a task. The more important question is how robots can operate safely and productively within the wider building environment.

On 12 October 2026, SJ Integrated Solutions and SoftBank Robotics Singapore announced a memorandum of understanding to develop an AI-powered facility-management solution, evaluate service-robot pilots at Singapore sites and explore connections between robotics management, facilities workflows and building systems.

The announcement is significant because it focuses on the integration layer. The proposed offering is expected to combine SJ Integrated Solutions’ 24K platform, a robotics-management platform and new facilities-management software modules. The announcement also refers to potential connections involving lifts, doors and access control.

However, this should be understood accurately. It is a development partnership and pilot-development effort, not evidence of a completed commercial rollout or verified operating results across Singapore buildings. For operators, the practical value lies in understanding what an integrated deployment would require.

From standalone robots to an operating stack

A service robot can move through a defined route, deliver items, conduct selected patrol activities or support repetitive service tasks. Its value increases when it can interact with the facility’s operating model.

That operating model may include:

  • Work-order and facilities-management platforms
  • Robot fleet management and task allocation
  • Lift call and floor-selection interfaces
  • Doors, gates and access-control systems
  • Incident escalation and human approval workflows
  • Environmental sensors, video analytics and building data
  • Electronic permit-to-work or other safety-control processes

In this model, the robot is one component in a wider stack. The stack must determine what task is issued, which system grants access, what happens when an exception occurs, who is accountable and how performance is measured.

Why lifts, doors and access control matter

Navigation inside a building is only part of the challenge. A robot may need to move between floors, pass through controlled areas, wait for people, interact with loading zones or access spaces that are unavailable during certain periods.

Connecting to lifts, doors and access control can reduce manual intervention, but it also introduces operational and cybersecurity considerations. Access should be based on defined permissions, operating times, zones and task requirements. The system should also record relevant events so operators can review what happened.

For example, a delivery task may require the robot to enter a service corridor, use a lift, access a receiving area and notify a human operator if a door is unavailable. A robust workflow would define the permitted route, the approval conditions, the fallback action and the escalation owner before the task begins.

These are not merely software questions. They involve building-system interfaces, operational rules, safety controls, network design, maintenance responsibilities and coordination with existing vendors.

What the partnership does—and does not—establish

The SJ Integrated Solutions–SoftBank Robotics Singapore announcement creates a basis for joint development and pilot evaluation. It indicates an intention to test how robotics management and facilities-management functions can work together in Singapore environments.

It does not, based on the announcement alone, establish a full commercial deployment, standard integration architecture, guaranteed productivity improvement or verified results for every building type. Conditions will differ between offices, hotels, hospitals, warehouses, mixed-use developments and industrial sites.

Facility managers should therefore treat pilot announcements as an opportunity to prepare and ask better engineering questions, rather than as a reason to assume that every building is immediately ready for autonomous operations.

Six preparation areas for building operators

1. Map the workflow before selecting the robot

Start with the task, not the device. Document the current process, including handovers, waiting time, access requirements, exceptions and safety constraints. Identify which activities are suitable for automation and which still require a trained person.

A useful workflow map should show the trigger, task owner, required systems, decision points, escalation path and completion record. This makes it easier to determine whether a robot is solving a real operational bottleneck or simply adding another interface.

2. Establish the integration boundary

List the systems that may need to exchange information: the facilities-management platform, robot-management platform, access control, lift controls, building management systems, CCTV or video analytics, environmental sensors and communication tools.

For each interface, clarify what data is exchanged, in which direction, how access is authenticated, what happens when the connection fails and who owns support. Integration requirements should be documented early, particularly where legacy systems or multiple vendors are involved.

3. Set an operational baseline

Before a pilot, record how the current process performs. Depending on the task, this may include response time, completion time, manual interventions, missed tasks, incident frequency, service coverage and staff workload.

The baseline should be specific enough to support a fair comparison. A pilot should not be judged only by whether the robot moves successfully. Operators should also assess reliability, exception handling, user acceptance, system availability and the amount of human supervision required.

4. Design human oversight and fallback procedures

Autonomous or semi-autonomous systems still need accountable human oversight. Define who can approve tasks, pause operations, respond to alerts, release a blocked route and investigate incidents.

Fallback procedures should cover loss of connectivity, lift or door failure, unexpected obstacles, unauthorised access, low battery, equipment faults and changes to the operating environment. The goal is not to remove people from the process without consideration; it is to allocate human attention to the decisions and exceptions that matter most.

5. Apply security and privacy controls from the start

Singapore’s smart-city and AI discussions increasingly emphasise security-by-design, continuous assurance, human oversight and organisational accountability. These principles are directly relevant to robotics integration.

Operators should consider network segmentation, least-privilege access, credential management, software updates, vendor remote access, logging, incident response and data-retention requirements. Where cameras, sensors or occupant information are involved, the project team should also clarify what data is collected, why it is needed and who can access it.

6. Track performance beyond labour reduction

Performance reporting should reflect the full operating objective. Suitable measures may include task completion rate, intervention rate, system uptime, time to resolve exceptions, access failures, route interruptions, safety observations and service-quality feedback.

For warehouse operators, measures could also include movement accuracy, delivery handover time and congestion at shared routes. For building owners, reliability, tenant experience, maintainability and integration support may be as important as task volume.

Relevance to Singapore SMEs and existing buildings

New developments may have more flexibility to plan connectivity and access interfaces. Existing buildings may need a phased approach because their lifts, doors, networks and facilities platforms were installed at different times.

SMEs do not necessarily need to begin with a large fleet or a complex transformation programme. A focused pilot around one repeatable workflow can help establish the business case and reveal integration constraints. The pilot should have a defined site, responsible owner, operating window, success criteria and exit plan.

It is also important to include maintenance and change management. Building layouts change, access permissions are updated, equipment is replaced and operating teams rotate. An integration that works during a demonstration may become unreliable without ownership, monitoring and periodic review.

What building operators should ask next

  • Which facility workflow is the best candidate for a controlled pilot?
  • What systems must the robot access, and what interfaces are available?
  • Which decisions require human approval?
  • How will incidents, access failures and downtime be handled?
  • What baseline data will be collected before deployment?
  • Who owns cybersecurity, integration support and ongoing maintenance?
  • How will the pilot results inform a scale-up decision?

The partnership between SJ Integrated Solutions and SoftBank Robotics Singapore is a useful signal that facility robotics is developing towards integrated operations rather than isolated device deployment. For Singapore operators, the immediate priority is readiness: clear workflows, dependable interfaces, measurable baselines and accountable oversight.

ISS supports organisations exploring engineering, facility-management and AI automation requirements. Contact ISS to discuss how a practical integration roadmap could fit your building, warehouse or business environment.