For owners and operators working on voyage charter

The time you lose in port is money. Don't miss it.

MarineOS keeps the demurrage file from document to collection. It calculates time to your charter party, puts the last day to claim in front of you every day, and runs the negotiation with the charterer in the same place.

Laytime summary

Sample calculation

Laytime allowed
72 h 00 min
Laytime used
96 h 30 min
Time over
24 h 30 min
Demurrage rate
12,000 USD / day
Claimable
12,250 USD
Last day to claim18 days left

A sample prepared for illustration. It does not belong to a real voyage.

This money is lost in two places

In the calculation.

Events are read by hand from port documents. One hour counted wrongly lowers the claim, and the other side disputes every line.

In the calendar.

A claim has a last day (the time bar). Once that day passes the claim is lost in full, and most of the time nobody notices.

How the clock runs

The five days in port behind the sample calculation above

Now

Loading completed

Laytime used

96 h 30 min

Time over

24 h 30 min

Demurrage

12,250 USD

Vessel arrived, NOR tenderedRain startedLaytime expiredTime starts to countRain stoppedLoading completed
Time countsDoes not count (notice time, rain)Demurrage runs

The charter party decides which hours count. MarineOS places every event on this strip; you only look at the doubtful ones. Six hours came off because the rain did not count.

A sample voyage prepared for illustration. It does not belong to a real voyage.

The path of one voyage

Six steps from document to collection

  1. Reads the document.

    The charter party and SOF are uploaded. AI extracts the terms and the events in port. Everything it extracts is a suggestion first.

  2. Leaves the decision to you.

    An event you have not approved does not enter the calculation. Who changed what, and when, is recorded.

  3. Calculates hour by hour.

    Every event is marked "counts" or "does not count". Where it is doubtful the system does not decide; it says "check against the contract".

  4. Prepares the claim file.

    The calculation, the supporting documents and the relevant contract clauses in one file. The days left to the last day sit on the opening screen.

  5. Runs the negotiation.

    The charterer accepts or disputes line by line from a link, without opening an account. If they upload their own calculation, the difference shows in hours and in money.

  6. Follows it to collection.

    The amounts claimed, invoiced and received at the bank are kept apart. Money that could not be collected because the time ran out is not hidden either; it is written as "missed".

What's on board

Demurrage does not stand alone. Voyage, document, fleet and fuel records are in the same system. Each module sits in a part of the ship; touch a part.

86154327

1 · Bridge

Today and Alerts

The first screen of the morning. The summary of money and calendar sits on one line.

  • Claimable, awaiting collection and missed amounts, each on its own
  • Days left to the nearest last day to claim
  • Open alerts, the urgent one on top

Common to every module: who changed what and when is recorded, and permissions decide who sees amounts. Anything that comes from AI or an outside source is a suggestion first.

What we don't promise

It does not win in court.

MarineOS is a negotiation tool. It lets you sit at the table with an orderly file; it does not replace your lawyer.

It does not decide for you.

It reads, calculates and warns. You decide which event counts and when the claim goes out.

It does not hand you a ready-made savings figure.

How much it recovers, we measure together during the pilot, on your own voyages. Until that figure exists it is not written on this page.

Let's run one of your voyages together.

During the pilot we take a single real voyage from document to collection together. At the end you hold your own figure.