Your Vessel
in a Virtual World

SeaTwin renders roll, pitch and yaw on the hull itself. Attitude is read at a glance, in the same view as everything else, rather than off a separate instrument — and because the model is three-dimensional, the relationship between heading, sea state and how the vessel is actually sitting is obvious rather than inferred.

Hull impacts are flagged in context — where on the vessel, and when. Alerting is tiered so a firm slam in a seaway is treated differently from a genuine structural event, with the thresholds set to suit the vessel:

The reason a spike is meaningful is how it is captured. Motion is sampled far faster than it is displayed, and what gets reported for each interval is the peak force in that window, not whatever the sensor happened to read at the moment of transmission. A hard slam between two readings is never averaged away.

Machinery vibration monitoring is available on the same sensing path, for tracking the condition of engines, gearboxes and pumps over time. See how the NCoDE Engine collects sensor data →

* Z-Wave requires the NCoDE Z-Wave add-on board and is available as a licensed option on both MX10 and MX100.

Because the collecting is done once, at the Engine, the same readings drive the twin, the alerts, the compliance records and the rest of the NCoDE suite — there is no second integration to build and no second version of the truth. See what the Engine connects to →  ·  What a maritime digital twin actually is →

The twin can be customised to show whichever data sets matter to you, laid out the way your crew actually works. If a value belongs on the hull, it goes on the hull. If a system deserves its own panel, it gets one. If something on the standard view is noise for your operation, it comes off.

Where a vessel carries equipment we do not read as standard — a proprietary control system, an unusual sensor package, a manufacturer’s own gateway, a bespoke piece of survey or research kit — we can add the feed at the NCoDE Engine on an MX10 or MX100. Once it is in the Engine’s data model it is available everywhere: on the twin, in alerts, in the historical record, and to the rest of the NCoDE suite. You integrate it once.

This is ordinary work for us rather than a special project, and it is the practical difference between a platform built for one type of fleet and one built for whatever is actually in your engine room. Tell us what you need to see →

Run the viewer onboard, on an NCoDE Engine MX10 or MX100, and the twin works on the vessel’s own network — the bridge, the engine room and the owner’s tablet all looking at the same model over the ship’s WiFi.

Run it in the cloud and the same twin is available to shore teams, technical managers and owners wherever they are, without a vessel visit and without anyone needing access to the ship’s network.

It is the same model and the same data either way. The only thing that changes is where the viewer runs, which means the decision is yours to make on connectivity, cost and who needs to see it — not one forced by the software. For fleets, NCoDE Fleet aggregates across vessels from shore.

Both run the same software on the same NCoDE Engine. Starting with SeaTwin on its own does not lock you out of anything later — adding the rest of NCoDE Command is a licence change rather than a reinstallation, and nothing already recorded is lost or migrated. See what NCoDE Command adds →