Can You Turn a Conventional Ship Autonomous in Nine Days?
🔔 Subscribe to ShipUniverse Weekly →
How Fast Can You Retrofit a Ship for Autonomy?
A 257-foot commercial offshore vessel received autonomous command and control in nine days, then crossed between Hawaiian islands under autonomous navigation. The more useful question is what those nine days actually changed, and what they did not.
In May 2026, Sea Machines spent nine days in Louisiana installing autonomous command and control aboard Hornbeck Offshore's HOS Resolution. Three months later, the 257-foot vessel was used in a U.S. Army demonstration between Oahu and Hawaii's Big Island.
That sounds like a nine-day autonomous-ship conversion. It was not quite that simple. The ship remained fully crewed, the open-sea navigation function was the focus of the demonstration, and engine-room automation was publicly described as a later phase.
The real breakthrough is narrower and more commercially useful: on the right vessel, the navigation brain can now be retrofitted much faster than the rest of the ship can be redesigned around it.
Nine days added the navigation brain, not an entirely new ship
The distinction matters for owners assessing retrofit potential. Autonomy can be installed function by function. Navigation may be ready long before machinery, deck equipment and statutory operating arrangements are.
Autonomous transit capability
The SM300 package integrated vessel navigation, perception and command functions sufficiently for an autonomous open-sea transit during the Army demonstration.
Fully uncrewed ship operation
HOS Resolution remained crewed. Engine-room automation and remote operation of the stern ramp were described as later phases rather than completed elements of the nine-day retrofit.
Autonomy is a stack of systems, not one black box
The hardware cabinet is only one layer. A retrofit has to perceive the environment, decide what to do, physically command the vessel, survive failures and give a human operator a safe way to intervene.
What the nine-day retrofit did and did not cover
| Function | Status | Publicly reported position |
|---|---|---|
| Autonomous navigation | Demonstrated | The vessel conducted autonomous navigation during the approximately 18-hour Hawaii transit. |
| Sensor + compute integration | Installed | Sea Machines described SM300 as a deployable autonomy package incorporating the supporting hardware required for rapid retrofit. |
| Human monitoring | Retained | Army mariners and technicians monitored the mission, and the vessel remained crewed during the demonstration. |
| Engine-room autonomy | Later phase | Public reporting identified machinery monitoring and control as a later development phase. |
| Stern-ramp automation | Later phase | Remote ramp operation was discussed as a potential later step rather than part of the original nine-day conversion. |
| Uncrewed commercial operation | Not proven | The demonstration did not establish routine crewless commercial operation or unrestricted autonomous service. |
The ship itself helps explain how nine days was possible
HOS Resolution was not purpose-built as an autonomous ship, but it was also not a mechanically simple legacy freighter. Its offshore-service specification already included sophisticated propulsion and vessel-control systems.
HOS Resolution
Age was not the main variable
The vessel was roughly 18 years old at the time of the demonstration, yet its published specification included DP2, controllable-pitch propellers, independent steering, multiple tunnel thrusters and substantial electrical generation.
Those features do not automatically make autonomy easy, and the exact control interfaces used by the retrofit have not been publicly detailed. They do indicate a more automation-ready platform than vessel age alone would suggest.
For owners, that shifts the first screening question from vessel age toward how much of steering, propulsion, navigation and machinery control is already electronically accessible.
The fastest retrofit candidates already have most of the nervous system
| Vessel profile | Control integration | Sensor readiness | Redundancy burden | Retrofit potential |
|---|---|---|---|---|
| Modern DP2 OSV Integrated bridge and electronic controls | Lower | High | Lower | Strong |
| Modern tug / PSV Electronic propulsion and current navigation suite | Moderate | High | Moderate | Good |
| Older digital workboat Mixed equipment generations | Moderate | Moderate | Moderate | Conditional |
| Legacy mechanical vessel Mechanical or fragmented controls | High | Low | High | Difficult |
| Full uncrewed conversion Navigation + machinery + deck systems | Very high | Very high | Very high | Not 9 days |
Installation speed is no longer the only clock running
Modern autonomous-vessel frameworks make the project an approval, safety-management and operating problem as well as a hardware installation. The physical retrofit may be the fastest part of the program.
Install
Mount compute, perception hardware and interfaces to propulsion and steering.
Commission
Calibrate sensors, validate control response and test failure behaviors.
Define limits
Establish operating boundaries covering weather, traffic, visibility, depth and communications.
Approve
Address class, flag, cyber, risk assessment, procedures and applicable autonomous-vessel requirements.
Operate
Train crews and remote operators, manage overrides and maintain the autonomous system lifecycle.
Could your vessel realistically approach a nine-day retrofit?
This screening model estimates onboard integration effort from six vessel-readiness variables. It is designed to show why some ships can accept an autonomy layer rapidly while others require substantial control-system work first.
Nine-Day Autonomy Retrofit Reality Check
Select the closest vessel configuration. The estimate covers onboard technical integration and commissioning only, not statutory approval or a complete commercial certification campaign.
A nine-day window is plausible for this scope.