A practical framework for assessing automated storage, building constraints, safety, workforce capability and digital readiness.

Professional illustration of an automated storage shuttle system inside a Singapore warehouse, with callouts for building readiness, safety, inventory data and workforce training.

Warehouse automation is becoming a more practical consideration for Singapore businesses facing space constraints, rising operational complexity and growing expectations for inventory visibility. However, installing automated storage equipment is not just a matter of selecting a shuttle system or adding robotics to an existing facility.

Iron Mountain’s announcement on 28 September 2026 provides a timely Singapore case study. The company announced the introduction of automated shuttle technology at a Singapore storage facility and the upskilling of local staff to operate advanced robotics. The announcement does not, by itself, establish productivity gains, labour savings or a payback period. Its value for other operators is the deployment context: automation must be considered together with the building, storage profile, people, safety controls and digital operating model.

For facility managers, warehouse operators, building owners and SMEs, the following readiness questions can help structure an initial assessment.

1. Start with the storage profile, not the equipment

Automated storage works best when the system is matched to the physical and operational characteristics of the inventory. Before approaching suppliers, operators should document the items that will enter the system and how frequently they are accessed.

  • What are the dimensions, weights and packaging formats of the stored items?
  • Are pallets, cartons, archive containers or mixed unit loads involved?
  • How often are items received, retrieved, returned or relocated?
  • Are there special handling, environmental or security requirements?
  • Which items require rapid access, and which can remain in longer-term storage?

This information affects the required load carriers, rack configuration, shuttle design, retrieval logic and interface with manual work areas. A system designed around a narrow range of standardised loads may be unsuitable for irregular or frequently changing inventory.

Operators should also review inventory accuracy before automation. If item master data, locations, labels or transaction records are unreliable, automation can make errors faster and harder to diagnose. A data-cleansing exercise may therefore be an important early workstream.

2. Check whether the existing building can support the system

Singapore facilities are often retrofitted, multi-tenant or constrained by existing structural and services layouts. The available floor area is only one part of the assessment.

A technical feasibility review should consider floor loading, slab condition, levelness, clear height, rack anchoring, vibration, access routes and the movement of installation equipment. The team should also check whether columns, beams, fire compartments, doors, loading bays, lifts and escape routes create restrictions on the proposed layout.

Power distribution, lighting, ventilation, cooling, communications and maintenance access must be considered as part of the design. Automated storage equipment may require new electrical circuits, control panels, network points, sensors and safe access zones. These requirements should be coordinated with the building’s existing mechanical and electrical infrastructure.

Where the facility is leased or shared, the owner and occupier should agree responsibilities for structural surveys, service upgrades, penetrations, reinstatement, shutdowns and future maintenance. Early coordination can reduce the risk of designing a system that cannot be installed or maintained without disrupting neighbouring operations.

3. Treat fire and workplace safety as design inputs

Safety should be addressed before equipment selection and not left to the installation stage. Automated storage introduces moving machinery, restricted access areas, maintenance interfaces and potentially new work-at-height or contractor-management considerations.

The project team should identify emergency stops, guarding, interlocks, isolation procedures, access control, inspection arrangements and safe methods for recovering items or equipment faults. Fire protection, detection, compartmentation, escape routes and emergency access must be reviewed against the actual proposed layout and building conditions.

Recent workplace safety discussions in Singapore, including the Ministry of Manpower’s circular on new scaffold fire safety requirements, reinforce a broader principle: temporary works, contractors, inspections and site controls require clear ownership. The circular is not an automated-storage design standard, but it is a useful reminder that project safety arrangements must be planned and documented.

Any detailed fire, structural, electrical or machinery assessment should be carried out by the relevant qualified professionals and coordinated with applicable authorities, landlords and project stakeholders.

4. Design the workflow around people and exceptions

Automation should improve a defined operating process rather than create a separate technology island. Operators should map the full flow from receiving and identification to storage, picking, checking, dispatch, returns and exception handling.

Important questions include:

  • Where will goods be inspected, labelled and consolidated?
  • How will damaged, unidentified or quarantined items be handled?
  • What happens if a shuttle, conveyor, lift, scanner or network connection is unavailable?
  • Can operators access urgent inventory through a controlled fallback process?
  • How will cycle counts, audits and discrepancy investigations be performed?

These details are particularly important for storage operations where chain of custody, document control or customer access requirements matter. A system that performs well during normal operation may still create business risk if exceptions depend on improvised manual work.

5. Plan workforce upskilling as part of commissioning

Iron Mountain’s announcement specifically refers to upskilling local staff to operate advanced robotics. This is a practical lesson for other Singapore operators: workforce capability should be developed alongside the system, not after handover.

Training should cover normal operation, safe access, alarms, recovery procedures, isolation and restart, inventory exceptions, basic troubleshooting and escalation. Different roles may need different levels of competence, from warehouse users and supervisors to maintenance personnel, system administrators and managers.

Standard operating procedures should be tested during commissioning. Scenario-based exercises can include a failed scan, blocked location, power interruption, communication fault, damaged load or emergency stop. These exercises help reveal whether the operating model is genuinely ready or only technically installed.

6. Integrate automation with inventory and facility data

Automated storage depends on reliable communication between the equipment controls, warehouse management processes and business systems. The integration scope should be defined early, including item master data, location records, order release, confirmations, status messages, user permissions and audit trails.

Facility teams should also ask what operational data will be available after deployment. Useful information may include equipment status, alarms, transaction history, downtime events, fault categories, access records and maintenance indicators. The purpose is not to collect data for its own sake, but to support practical decisions about service response, inventory accuracy, capacity and operating performance.

Data ownership, cybersecurity, remote access, backup procedures and vendor support should be included in the project discussion. These issues become more important when the warehouse depends on connected equipment and software to maintain normal throughput.

7. Build a staged business case

A responsible business case should compare the proposed automated-storage model with realistic alternatives. These may include layout changes, selective mechanisation, improved slotting, better scanning discipline, warehouse management improvements or a phased pilot.

Cost planning should include more than the equipment purchase. Consider surveys, design, structural or services modifications, software integration, training, commissioning, temporary disruption, maintenance, spare parts, support contracts and future replacement requirements. The business case should also identify operational assumptions such as available shifts, inventory volumes, service levels and access patterns.

Do not rely on generic claims about labour reduction, productivity or return on investment. Results depend on the specific storage profile, operating rules, building limitations and implementation quality. A pilot or staged deployment may provide better evidence before committing the entire facility.

What Singapore operators can do next

Iron Mountain’s Singapore announcement demonstrates that automated storage and workforce development can be considered together in a local operating context. For other businesses, the immediate next step is not necessarily to purchase robotics. It is to establish whether the facility and operating model are ready.

  1. Document inventory characteristics and transaction patterns.
  2. Complete a building, structural and services feasibility review.
  3. Map safety controls, fire interfaces and emergency procedures.
  4. Define normal, exception and fallback workflows.
  5. Assess staff roles, training needs and maintenance capability.
  6. Confirm system integration, data visibility and support responsibilities.
  7. Compare a phased pilot with full-scale deployment.

ISS can help Singapore businesses discuss the engineering, facility management and AI automation considerations behind a warehouse modernisation project. Contact ISS through intelligencesolutionservice.com to discuss your facility requirements, automation objectives and implementation constraints.