MA — Vessel Intelligence Platform

The problem

Once a vessel leaves the dock, the shore goes blind.

Blind

Nobody ashore sees engine load, temperature or throttle habit. When fuel burn climbs, no one can say why: the weather, the driver, or a fouled hull.

Expensive

Raw telemetry over cellular or satellite is costly, so most vessels send little or nothing ashore. Wave slamming and thermal creep go unnoticed until the emergency overhaul.

Manual

Voyage run-hours, idle time, and fuel by leg are reconciled by hand from logbooks, weeks after the fact.

What MA is

What a vessel needs, and what shore gets.

Know what your vessels are doing, what they cost to run, and what is about to break.

Aboard. An engine network MA can read, one gateway box in the engine room, and a cellular or satellite link; navigation and motion data come with the engine data. When coverage drops, the gateway buffers at sea and catches up later.

Ashore. A map and console for masters and the shore team: vessel health judged against the vessel's own engineering model, and a voyage record built from the data rather than the logbook.

One signal's journey. One team behind every layer.

MA is not software alone. MASS-MARAM engineers every layer, so the quality of the evidence is controlled from the sensor up.

Sensor

Where the vessel speaks: temperatures, pressures, motion, power.

Edge

The MA gateway aboard, collecting, securing and buffering every signal.

Link

Secure vessel-to-cloud connectivity, built for patchy coverage at sea and on the river.

Intelligence

MA, judging every signal against the vessel's own engineering model.

People

Dashboards for the humans who act on what she finds.

The live picture, as the ops room sees it.

REPLAY · SIMULATED WORKING DAY 2 VESSELS

Selected vessel

Vessel 10

Outbound · Boarding station Bravo

Speed over ground

12.4 kn

Heading

214°

Engine RPM

1,850

Fuel

68%

Active alert

Crossing harbour limits at reduced visibility

MA's explanation

Speed dropped 3.1 kn over 4 min while RPM held steady — consistent with a strong ebb set near the bank. No engine anomaly indicated.

Product demonstration — a replay of a simulated working day in a fictional district. Operational trial data remains private to the operator.

Past

Where every vessel begins

Every vessel carries design intent — the assumptions and calculations it was built from — and a history of how it has actually run. MA begins with both, so everything she observes is judged against what this vessel, specifically, should do.

Present

The live picture

Live operational data — machinery condition, performance, motion and operating context — flows securely from vessel to cloud, to crews, engineers and shore teams. That includes motion awareness: what the vessel's motion and the conditions it meets mean for the hull, the machinery and the people aboard.

Future

Earned, one level of trust at a time

When operational behaviour departs from the vessel's engineering model, that deviation can be the earliest sign of a developing problem, and MA is designed to show the evidence behind it. From there, the path leads to advice engineers can verify and, in time, increasingly autonomous operation.

Intelligence you can question.

The engineering model

MA begins with an engineering model of the vessel — its physics, its documentation, its operating history — tuned against live operation by AI and machine learning, so an engineer can inspect any deviation and the assumptions behind it.

Evidence classes

Every finding carries an evidence class: a plain label saying what kind of evidence stands behind it and how much weight an engineer should give it, travelling with the finding so it can be questioned later as well as when it appears.

The evolution ladder

Each level is earned when the one below it can be trusted.

Monitor

Live

Predict

In trial

Advise

In development

Assure

Future direction

Every solution on this site says where it sits on this ladder. The solutions →

Where MA applies

MA is designed around vessel-specific engineering context rather than a single vessel type, so the same architecture applies across vessel classes and ways of operating — from today's working fleets to increasingly autonomous vessels.

Pilot vessels, tugs, crew transfer vessels, coastal workboats, and ocean-going vessels.

Before the vessel exists: how MA works at the design stage →

In operation

MA is in live trial aboard two working vessels: Atlantic Owl, a pilot vessel in Nova Scotia, Atlantic Canada, and Flying Owl, a partner-funded predictive-maintenance deployment in Paraguay.

See the deployments →

Introducing MA.