0300 M · Descent log · 2022–2026
Five chapters,
four years down
-
− 0600 M
Chapter 01 · 2022 · Greenfield
One ferry
There was a prototype and not much else. The team's tech lead knew me from our emetriq years and brought me in as the UX allrounder, the one who bridges design, development and business. The honest version of the brief: do whatever the product needs.
It needed one big thing first. The vessel's live data, brought ashore and onto a screen. Engines first, and soon far more than engines: vibration, oil quality, position, whatever the vessel reports, until the picture is the whole ship. See what your vessel is doing in that moment. Then turn around and study the same data historically. Live and history in one picture; that pairing is still the heart of the platform.
Within the first year it was running on a production vessel, a high-speed passenger ferry, and standing on a fair stand at SMM 2022. From nothing to production in year one.
-
− 1300 M
Chapter 02 · The product's face
The face of the fleet
For the crew, a cockpit and a bridge view: the vital signs of engines and systems, right where the vessel is run. For shore, a fleet overview and trend analysis: every vessel on one screen, weeks and months of behaviour instead of a phone call and a guess.
The piece I'm proud of is self-serve analytics. We built a chart and dashboard builder so that anyone, a superintendent, a service engineer, can answer their own question on their own data. Pick the signals, set the axes, save the view. No ticket. No developer. No waiting.
Around it, the features that speak the operator's language: trips you can compare, load profiles across an engine's life, emissions views. Not charts for their own sake; answers.
The self-serve idea: signals in, your own chart out. Rebuilt illustration, not the product. -
− 2000 M
Chapter 03 · The turn
From alarms to foresight
The platform started where every monitoring system starts: alarms. Something trips, somebody reacts.
Then the quieter work. Sensors fail more often than engines do, so we built data-quality guards: flag faulty sensors, show only plausible data, never let a broken probe impersonate a broken engine.
On clean data we could build anomaly detection, and weekly emails that tell operators what has started to drift before it becomes a problem. That shift took years, and it changed the product's job: from reacting to alarms to being told before it matters.
The arc in one line: react, then guard the data, then get told early. -
− 2700 M
Chapter 04 · Below the waterline
The unsexy hard problem: mapping
Data means nothing until every signal is mapped to the right name. Every engine generation names its sensors differently. Every vessel is wired a little differently again.
Get one column wrong and your history is quietly false: charts that look right and lie. So mapping is not a config chore here. It is a first-class product problem, and I keep pushing on it.
The current frontier is making it less manual: tooling that proposes mappings and makes every vessel's mapping state visible, instead of trusting a spreadsheet and one careful person. That work is in progress, not shipped. It is the part of the iceberg nobody shows at a fair.
Raw channels on the left, engine truth on the right. One wrong line poisons the history. -
− 3400 M
Chapter 05 · Convergence
The complete picture
A prediction is only useful next to reality: what was actually serviced, when, and at how many running hours. So the platform grew maintenance features: upload the records, see upcoming and completed tasks next to the live data. Running hours themselves had to be made trustworthy first, because every service schedule hangs off them.
The newest piece is service integration: platform data, maintenance history and the people who actually fix engines, meeting in one place.
Which is the point of this whole page. The prediction this site leads with works because someone integrated data collection across different spots and different teams: service with development with product with design, down to the workshop where repairs happen. That took four years. It was worth it.