ST Logistics’ Smart Warehouse Upgrade: Why Automation Readiness Also Requires Workforce Reskilling and Equipment Support

A practical Singapore guide to preparing people, processes and equipment for automated storage and retrieval systems.

Warehouse automation is often discussed in terms of speed, capacity and return on investment. Those outcomes matter, but a successful deployment also depends on the people and engineering processes supporting the system every day.

ST Logistics’ upgraded Clementi warehouse provides a timely Singapore case study. According to The Straits Times, the system uses 14 autonomous shuttles operating across 23 storeys of racks. It brings goods to packing staff, increases storage capacity by more than 20 percent within the existing 2,000-square-metre storage area and supports throughput of more than 70 pallets per hour.

The report also highlights an equally important point: around 40 employees have been trained for new roles, including software operation, diagnosing sensor-related stoppages and escalating mechanical faults.

These reported details should not be treated as a universal benchmark for every warehouse. However, they illustrate a broader operational lesson for Singapore facility managers, warehouse operators, building owners and SMEs: automation readiness requires a coordinated plan for workflow, workforce, equipment and ongoing support.

1. Start with workflow mapping, not equipment selection

Before evaluating autonomous shuttles or an automated storage and retrieval system, operators should document how work currently moves through the facility.

A useful workflow review should examine receiving, put-away, storage, picking, replenishment, packing, dispatch, returns and exception handling. It should also identify where staff currently make decisions manually, where information is re-entered into software and where delays occur because goods, data or approvals are not available at the right time.

This mapping helps determine whether automation is solving the right problem. For example, a system may improve storage density but still create delays if stock records are inaccurate, packing stations are poorly balanced or outbound scheduling is not connected to warehouse activity.

For Singapore sites operating within a constrained footprint, the review should also consider ceiling height, floor loading, access routes, fire and life-safety interfaces, maintenance access, power requirements and the effect of construction or installation work on live operations. These matters require coordination between warehouse, facility and engineering teams.

2. Reskill workers for software-based operations

Automation changes job content rather than simply removing manual tasks. Workers may spend less time travelling to retrieve goods and more time monitoring software, managing exceptions, checking inventory status and coordinating with technical support.

Training should therefore be designed around actual operating scenarios. Relevant topics may include:

• Starting, stopping and safely isolating the automated system;
• Using warehouse management or equipment-control interfaces;
• Recognising alarms, error codes and abnormal system behaviour;
• Checking whether a stoppage is caused by a sensor, obstruction, software condition or mechanical issue;
• Applying approved first-response procedures without bypassing safeguards; and
• Recording incidents clearly for supervisors, engineers and equipment vendors.

Not every warehouse employee needs to become a controls engineer. However, frontline staff should understand what they are authorised to do, what they must not do and when to escalate. Supervisors should also be able to distinguish a routine operational exception from a condition that requires technical intervention.

3. Define fault escalation before the system goes live

A common weakness in automation projects is leaving fault response informal. When a shuttle, sensor or conveyor stops, uncertainty about who should respond can extend downtime and create unsafe workarounds.

Operators should establish a written escalation matrix covering at least three levels:

1. Operator response: safe observations, system acknowledgement, basic checks and controlled restart steps that are specifically authorised.
2. Supervisor or control-room response: verification of inventory impact, isolation of affected work areas, communication with packing or dispatch teams and decision-making on temporary workarounds.
3. Technical response: inspection of sensors, drives, mechanical components, controls, network connections or other equipment by suitably qualified personnel or the appointed support provider.

The matrix should include contact routes, response priorities, information to capture and rules for returning the equipment to service. A useful incident record may include the time of failure, alarm message, affected location, recent operating conditions, actions taken and whether stock or customer commitments were affected.

Where equipment interfaces with building systems or shared services, the escalation plan should also identify the relevant facility management and engineering contacts. This reduces the risk of a warehouse issue being treated as an isolated software problem when the underlying cause involves power, environmental conditions or physical access.

4. Plan preventive maintenance and safe access

Automated storage systems still contain mechanical, electrical and control components that require inspection and maintenance. Automation does not remove the need for technicians; it changes the type of support required.

A maintenance plan should clarify routine inspections, sensor cleaning or alignment checks where applicable, condition monitoring, lubrication requirements where applicable, spare-parts arrangements, software and controls support, and response procedures for recurring faults. Responsibilities should be agreed between the warehouse operator, equipment supplier, building owner and facility management team.

Safe access is equally important. Maintenance routes, isolation points, work-at-height needs, restricted zones and recovery procedures should be considered during design and reviewed after installation. Staff should not enter automated equipment areas or attempt to retrieve stock from restricted locations unless the approved isolation and access process has been followed.

For existing buildings, owners should confirm that the proposed system can be maintained without creating unacceptable disruption to other tenants, critical building services or emergency access arrangements. This is one reason early coordination between automation specialists and facility engineering teams is valuable.

5. Connect automation data to operational decisions

An automated system generates useful information, but data has value only when teams know how to use it. Operators should decide which information needs to reach the warehouse management team, facility manager, maintenance provider and business leadership.

Examples may include equipment availability, recurring alarm types, blocked locations, order exceptions, response time, recovery time and maintenance history. The purpose is not to collect every possible data point. It is to identify the information needed to improve reliability, plan maintenance and understand whether the system is supporting the intended workflow.

Data integration should also be tested through realistic scenarios. Teams can simulate a sensor stoppage, unavailable storage location, network interruption or mechanical fault and confirm how the event appears in operating systems, who receives the alert and how inventory status is protected.

6. Use a phased readiness plan

For SMEs and smaller warehouse operators, a phased approach may be more practical than attempting a full transformation at once. Start by identifying a suitable process, defining the business and safety requirements, and establishing baseline operating information. Then test training, fault escalation and maintenance procedures before expanding the automated scope.

A practical readiness checklist can include:

• Current-state workflow and space assessment completed;
• Target processes and exception cases documented;
• Roles, training needs and authorisations defined;
• Sensor, software and mechanical fault escalation procedures approved;
• Maintenance access, isolation and spare-parts responsibilities clarified;
• Warehouse management and equipment data flows tested;
• Emergency and business-continuity arrangements reviewed; and
• Post-installation performance reviews scheduled.

What Singapore operators can learn from the Clementi example

The reported ST Logistics deployment demonstrates the potential of automated storage to increase capacity within an existing footprint and change how workers interact with warehouse operations. Its worker-retraining component is particularly relevant: the system requires operational knowledge, software confidence and the ability to recognise when technical support is needed.

For other Singapore warehouses, the most useful takeaway is not to copy a particular shuttle count, rack arrangement or throughput figure. It is to develop an operating model in which automation, people, building services and equipment support are planned together.

ISS supports businesses in discussing engineering, facility management and AI automation requirements, including the practical coordination needed to make technology workable in real operating environments. Contact ISS to discuss your warehouse automation, engineering or facility management needs.