Shantanu Ayerkar
Floating wind is being built faster than we have learned to look after it. The chain holding a floating
turbine in place must survive 20-30 years of waves, corrosion and storms, yet between inspections
nobody really knows its condition. Load sensors on the line could tell us, but they rarely survive
the sea. Finding another way became my final EngD project at Tarucca.
Innovation.
MOOR-LIFE turns the question around. Instead of measuring load on the line, it starts
from platform motion, which every floating asset already records with onboard instruments. From
that motion it estimates line tension, accumulates fatigue damage with a capacity model that
weakens as the chain corrodes, and produces a remaining-life estimate with its uncertainty stated
rather than hidden. I built two independent fatigue methods to cross-check each other, and three
ways of estimating tension. The most useful lesson came from the one that failed: a simplified
physics model recovered the average load but almost none of the fluctuation, and fluctuation is
what breaks chain. Keeping the physical structure but learning its coefficients from data cut the
error from 48-112 kN to 8-12 kN. I then packaged the pipeline as a streaming application that
updates damage and remaining life every ten minutes, in under a tenth of a second per update.
Impact.
Three findings stand out. Fatigue is driven by how much a line moves, not its average
load: lines with near-identical mean loads had predicted lives up to ten times apart. Which line
fails first depends on rotor thrust as well as wave direction, so ignoring the turbine can send
inspectors to the wrong line. And the faster frequency domain method gave a longer life for the
first line to fail in every case tested, because its statistical treatment underweights sharp load
spikes. When Tarucca asked how close it was to certification, I reviewed all 106 modelling
assumptions against DNV-ST-0119 and DNV-OS-E301. The answer was honest: MOOR-LIFE is
a methodology demonstrator today, its reported lives are optimistic, and the route to a certifiable
tool is now documented. For Tarucca, that clarity matters as much as the open-source code itself.
Leadership and collaboration.
The requirements came from close work with Tarucca’s CTO,
my TU/e supervisors, and six practitioners across the floating wind value chain, from an asset
manager to a platform designer and a maritime research institute. I came to offshore engineering
from automotive and MBSE work, so learning the field meant asking many questions of people
who knew more. I tried to give that back by making the work easy to pick up: a traceable
requirements chain, a documented assumptions register, and a talk at the EngD graduation
symposium.
The project was awarded cum laude, but this award would recognize something bigger that the
EngD does well: placing an engineer in an unfamiliar industry and asking for a result that works,
is honest about its limits, and can built on.

