As I wrote in my 2014 post, How To Get The Most Out Of Vessel Remote Support, yacht IT systems are getting more numerous and complicated.
Boats always had Chief Engineers. But very few Chief Engineers out there have the combination of Mechanical, Electrical, IT and Comms skills necessary to run today large mega yachts – they are a rare breed. Also, as vessel IT systems become more complex, specific skill sets outside those of a traditional 'Electrical/Mechanical Engineer’ are a required element.
For these reasons, many vessels have begun augmenting their team with ETOs. And to avoid yacht computer system down-time, many Captains also contract with vessel remote support providers to keep all on board Comms and IT systems running at an optimal level at all times.
There is a lot to love about these yacht IT support contracts—they can often get your crew out of a technical jam quickly with minimal down time. And having a technical team fixing things remotely while your crew continues to perform their daily tasks is a big plus.
But the contracts (and the IT teams behind them) can often attract a lot of hate. And unfortunately in some cases, that hate can be justified.