How Navvex works

One chain, from a hand on a valve to a decision ashore.

Not a diagram of a process somebody hopes happens. The path one finding actually takes, in the order it takes it.

Why this is hard

A vessel is the most information-dense workplace most people will never see, and the worst-connected. Everything that matters happens in compartments with no signal, is written down by somebody with gloves on, and then has to reach an office three thousand miles away that needs to act on it this week.

The industry's answer for thirty years has been a person in the middle. The master emails a summary. Somebody ashore reads it, decides what it means, and retypes the parts that matter into three other systems. It works, in the sense that ships sail. It also means the shore picture is a reconstruction, the vessel picture is a memory, and the two are only ever accidentally the same.

Nothing below is a new idea about ships. It is one idea about plumbing: the record the crew makes and the record shore reads should be the same record.

The gap is not a metaphor. It is a satellite link that is expensive, slow and often absent — and everything NAVVEX does is shaped by the assumption that it is down right now.

The journey

Follow one finding, end to end.

Every screen below is the product's own interface. Scroll to follow the record from a deck, under the surface, ashore, and back to the crew who raised it.

  1. 01

    The crew inspect

    Aboard, offline, on a tablet. No signal required and none assumed.

  2. 02

    A question is answered

    Pass, fail, or an observation — with a photograph attached where it matters.

  3. 03

    A finding is raised

    The answer that was not a pass becomes a thing with an owner and a date.

  4. 04

    Work follows

    It reaches maintenance as a job, not as a note in somebody's book.

  5. 05

    The day is recorded

    Rounds, jobs, bunkers, the logbook — the ship's own record, kept aboard.

  6. 06

    It syncs

    When there is a link. Not before, and nothing is lost waiting for one.

  7. 07

    Shore sees it

    The fleet picture moves because the ship moved it, not because somebody retyped it.

  8. 08

    Shore answers

    An instruction goes back to the vessel and the crew acknowledge it.

The markup in those screens is the application's and the stylesheet is lifted verbatim from the one the vessel shell loads. If a screen here looks wrong, it looks wrong in NAVVEX — there is no version of this page that makes the product prettier than it is.

What has to be true for that chain to hold

Four constraints. They are not features, and none of them can be added afterwards — each one decides how everything above it is built.

Offline is the normal state

Not a degraded mode with a warning banner. Every screen a crew member touches works with no signal, stores locally, and behaves identically whether or not the vessel has a link. Nothing is ever lost waiting for one.

One record, not two copies

The finding aboard and the finding ashore are the same object. There is no vessel version and shore version to reconcile, because reconciliation is where data quietly diverges and nobody finds out for months.

Evidence travels with the claim

A photograph, a reading, a certificate reference — attached to the finding, not filed separately. An observation whose evidence lives in someone's phone is an observation that cannot be defended.

Sync that assumes failure

The link will drop in the middle of a transfer. The design takes that as given: transfers resume, repeats are harmless, and a half-finished sync leaves neither side holding something the other does not.

The five things it does

Not modules bought separately. One record moves through all of them, which is why the finding a crew member raises is the same object the work order is built from.

Inspections

Crew, tablet, question set, finding. Offline first, because a vessel is offline first.

Fleet readiness

Every hull, every element, every question — and which of them will not survive an inspector.

Maintenance

A finding becomes a job, a job becomes a record, and the record is the evidence.

Safety & incidents

Reported by the people it happened to, on the device already in their hand.

Reporting

The daily report writes itself out of work that was already done.