Sector notes
Autonomous ships have a code now. Singapore's port was already built for it
The IMO adopted its first global code for autonomous ships in May 2026, voluntary from July that year and mandatory by 2032. PSA's Tuas mega-port, automating in phases toward 65 million TEU a year, has been running on the same planning horizon without waiting for the regulation to catch up.
Executive summary
1 Jul 2026
the IMO's non-mandatory MASS Code takes effect, voluntary for at least two years
65M TEU
PSA Tuas's target annual capacity at full build-out in the 2040s
Core conclusions
- The IMO adopted its first global code for autonomous ships in May 2026 — voluntary from July 2026, mandatory by 1 January 2032.
- PSA Tuas didn't wait for the global code to automate yard operations: 300+ AGVs already run across 11 berths, cutting emissions roughly 50% against diesel prime movers.
- Both run on the same shape of planning horizon — automate what's ready, on a published timeline, while the regulatory ceiling for the rest is still being tested.
Shipping now has a regulatory answer to a question it has been deferring for years: what is an autonomous vessel actually allowed to do, and under whose authority. The IMO's Maritime Safety Committee adopted the non-mandatory MASS Code by resolution MSC.595(111) in May 2026, taking effect on 1 July 2026 and remaining voluntary for at least two years while an Experience-Building Phase — convened from the committee's next session in December 2026 — gathers real operating data. A mandatory code is targeted for adoption by 1 July 2030 and entry into force on 1 January 2032.
That six-year runway from voluntary to mandatory is not a delay. It is a planning horizon, and it maps onto exactly the kind of phased capital programme a major port has to run regardless of when the regulation lands.
The four degrees the Code sits on top of
The regulatory groundwork goes back to the IMO's 2021 Regulatory Scoping Exercise, which defined four degrees of autonomy: a ship with automated processes but seafarers on board and in control (Degree 1); a remotely controlled ship with seafarers still aboard (Degree 2); a remotely controlled ship with no seafarers aboard (Degree 3); and a fully autonomous ship making its own decisions (Degree 4). The MASS Code that followed is the operating framework for moving vessels up that ladder, not a switch that turns autonomy on.
PSA Tuas: automation on the same kind of horizon
| Detail | Figure |
|---|---|
| Target capacity at full build-out | 65 million TEU a year, in the 2040s |
| Automation status reported in 2026 | Phase Two of automation complete — AI systems and AGVs running across multiple berths |
| Automated guided vehicles in operation | 300+ AGVs across 11 operational berths |
| Emissions impact | AGVs cut carbon emissions roughly 50% against diesel prime movers on the same duty |
The lesson for anyone planning around either
Tuas did not wait for a global MASS Code to start automating yard operations, because a port terminal's automation decisions — cranes, AGVs, yard planning — sit mostly inside its own perimeter and its own regulatory relationship with the Maritime and Port Authority of Singapore, not inside IMO vessel rules. But the shape of its programme, phased over roughly two decades toward a stated capacity target, is the same shape the MASS Code's own six-year voluntary-to-mandatory runway assumes for vessels: automate the parts that are ready, on a published timeline, while the regulatory ceiling for the rest is still being tested rather than fixed.
For an operator adjacent to either — a logistics partner, a vessel operator, a port-services vendor — the useful move is not to wait for 2032. It is to treat 2026 to 2032 as the window in which the operating data that will shape the mandatory Code gets generated, and to make sure whatever is being automated now is generating evidence, not just throughput.