Maritime · Demurrage & Operations
MarineOS
Stop leaving demurrage on the table.
MarineOS is built for owners and operators trading on voyage charter. AI reads your charter party and statement of facts; your operator checks and approves. Laytime is calculated to your CP terms, invoices and collections are tracked, and you are warned before the time bar runs out — so you sit down with the charterer holding the calculation, the documents and the reasoning in one file.
2026 pilot period · Mersin
The problem
Where does demurrage get lost?
In most owners' offices the demurrage file lives in Excel, email and the memory of one experienced operator. The work usually gets done — but money slips away quietly, in four places:
- 01
The SOF is retyped by hand.
Dozens of lines per port are copied into Excel. Miss one line or count one stoppage wrongly and the result drifts by hours — and nobody notices.
- 02
CP clauses don't make it into the calculation.
The SHEX window, "unless used", when laytime starts after NOR… A generic template doesn't know your clauses, and a small difference in reading is worth thousands of dollars.
- 03
The time bar slips by.
Demurrage that is never invoiced is likely lost once the CP's claim period runs out. Without something watching that date, the claim simply disappears.
- 04
Arguing with the charterer's figures is hard.
When the charterer sends their own calculation, you need event-by-event backing to show where the difference comes from. And was that "rain" stoppage on the SOF really rain?
Each looks small on its own. Added up over a year, they are a serious number — one most companies have never measured.
Where the money goes
The first step of the pilot measures exactly this: a "what was left on the table last year" report built from your own CPs, SOFs and NORs for the past 12 months. We don't estimate the number; we take it from your documents.
The solution
From charter party to collection, in one file.
MarineOS doesn't make decisions for you. It takes over the manual part of the work and records every step. A voyage's demurrage file moves in four steps:
Reads.
Upload the CP or fixture recap: laytime, demurrage/despatch rates, SHEX, the NOR rule and the time bar fill the form. Upload the SOF: events arrive line by line as suggestions.
Lets you check.
Each suggestion sits next to the original SOF line, with warnings such as "vessel not ready" or "not sure — check". Nothing you haven't approved enters the calculation.
Calculates.
Laytime is calculated to your CP terms: demurrage or despatch, port by port. The Excel breakdown shows, hour by hour, what counted and why.
Follows up.
Invoice, collection, dispute… You are warned as the time bar approaches, and the gap between calculated and collected is reported together with its cause.
The result: your operator checks instead of typing, accounts know what to invoice, management sees what is left on the table — and behind every figure is a record of who decided what, when and why.
Modules
Built around the demurrage file — with the rest of the operation alongside.
The demurrage file is the core; vessels are tracked live on the map via AIS, and certificate, crew, fuel and cargo records live in the same system. Who sees what is set by role: the master sees the voyage, the money stays hidden.
CP reading
From a CP PDF or fixture recap: laytime, rates, SHEX window, "unless used", NOR rule, reversible and time bar. Comes with a confidence note; you check and save.
SOF reading
PDF or photo. Events arrive in local time as suggestions beside the original line; approve one by one or all at once. The document is filed under the voyage too.
Laytime engine
NOR + X hours, next working day, the Gencon 94 noon rule; SHEX windows such as Saturday noon to Monday morning; weather clauses; once on demurrage; reversible. Laytime can also be derived from a loading rate (mt/day).
Counts / doesn't count
On an approved event, one click sets "from here on, time doesn't count" — written to the audit log with reason, person and time. That is your backing at the table.
Claim tracking
Draft → invoiced → paid / disputed / waived. For despatch, the charterer's claim and the amount paid are kept apart, so overclaims and overpayments are visible.
Audit summary
For any period: calculated, collected, unrecoverable and still recoverable — with the reason for each loss. PDF (Turkish / English) and Excel.
Why it matters: claims are usually lost in the follow-up, not in the arithmetic — never invoiced, time-barred or short-paid.
★ A check for owners
Weather Defence
The SOF says "rain — work stopped". Did it actually rain?
- Weather stoppages are deducted from laytime — that works in the charterer's favour. The owner's question is whether the stoppage written down really happened.
- Voyages whose SOF contains weather stoppages are listed automatically; no AIS connection is needed.
- Each stoppage is compared with the port's archived precipitation, wind and wave data for those hours: supports, partly, does not support, or no data.
- For stoppages the archive doesn't support, the disputable amount is calculated — and can be added to the audit summary.
- If the vessel is tracked via AIS, an hourly weather trace along the voyage route is added too — exported as a Turkish and English report (PDF).
Example (demo data): the SOF records 8 hours of "heavy rain"; the archive shows 0 mm for the same hours. Those 8 hours are disputable — $10,667 at the demo voyage's rate.
How we start
Measure first, then decide.
The pilot begins with a demurrage audit of your own documents. We'd rather show you your number than tell you about ours.
- 01
Audit.
Send us the CPs, SOFs and NORs from the past 12 months (names can be redacted). We enter the voyages ourselves.
- 02
Report.
Every voyage is recalculated to its CP. Calculated, invoiced and collected are compared, and what was left on the table comes back to you with its causes, in PDF and Excel.
- 03
Live use.
If the number is worth it, you enter new voyages yourselves: upload the SOF, check it, and the calculation and follow-up run in the system. We help move your vessels, certificates and users across.
The pilot is free, needs no credit card and binds you to nothing. If the number turns out small, we both learn that without investing. In return we ask for your honest feedback.
Why MarineOS
Not a second workload.
You check — you don't type.
AI reads the SOF and the CP; your operator's job becomes approving lines, not writing them.
Nothing unapproved is counted.
Everything read is a suggestion first. Every decision is recorded with who, when and why — no black box.
The right scale.
Designed for small and mid-sized owners and operators trading on voyage charter. None of the weight or price of enterprise software; interface in Turkish, outputs in Turkish and English.
From inside the industry.
Developed in Mersin, alongside the people who run these files. The laytime engine is tested against published expert calculations.
Proof
This is not a mock-up.
The laytime engine was tested against a published expert calculation: the CP and SOF of a 2010 bulk grain loading were uploaded as PDFs, read by the system and checked by an operator. The tracking screens run on real vessel and weather data too.
- 01
SOF approved as it stood: about 100 hours used.
Hold-cleaning days would have counted as laytime; the result would have been plainly wrong.
- 02
With the "vessel not ready" warning and three reasoned decisions: 27 h 55 min.
The "All holds reproved" line came with a warning; three clicks brought the calculation in line with the CP.
- 03
Despatch: $13,520.58 — the same as the expert.
Time used and amount matched the expert's owner-side calculation to the cent.
- 04
A real vessel, real weather.
A real vessel followed hour by hour with live AIS position, speed and wind data; one click for its particulars and current weather.
Your own number we measure in the pilot, with your own documents.
FAQ
Frequently asked questions.
What if the AI misreads a line?
Every line it reads is a suggestion first. It is shown beside the original SOF line and doesn't enter the calculation until you approve it. Lines it is unsure of come with a "check this" warning.
Our CPs have different clauses. Will the calculation be right?
SHEX windows, unless / even if used, NOR + X hours, next working day, the Gencon 94 noon rule, weather clauses, reversible and once on demurrage are all configurable. Where a case doesn't fit, one click sets "from here on, counts / doesn't count". If a clause we don't support turns up, we'll see it together in the pilot.
Does MarineOS give legal advice?
No. The calculation comes from the CP terms you enter and the events you approve. The aim is negotiation, not court: going to the charterer with the calculation, documents and reasoning ready.
Do we have to give up Excel?
No. The laytime calculation and the audit summary download as Excel, so the file you send the charterer can still be Excel. What changes is that a recorded, checked calculation stands behind it.
Do AIS and weather data cost extra?
No. Live AIS tracking and weather / sea data are included; there is no separate charge.
Who sees what?
Start from role templates (admin, operations, technical, accounts, master, viewer), then adjust page by page. Demurrage rates and amounts are visible only to users with financial access.
Is the pilot binding?
No. It's free and needs no credit card. If you don't continue at the end, you have no obligation.
Let's look at what was left on the table last year.
Bring the CPs and SOFs from the past 12 months. We recalculate each voyage to its CP and compare it with what was invoiced and collected. If the number is large, we talk; if it's small, you've learned that for free.
Free pilot · no credit card · no commitment