Ontolo
Under construction Book a call
{{ videoTitle }} Open on YouTube

Root cause analysis and close-out · for ship managers and operators

Inspection close-outs, made easier to get right.

Ontolo drafts the root cause, corrective action and preventive measure for every inspection finding, straight from your SMS, maintenance system and vessel records. Nothing goes out without a source. And no response is submitted without human approval.

Currently built forRightShip RISQIn preparationOCIMF SIREPort state controlClassFlag state

The product

{{ prodTitle }}

{{ prodLead }}

Watch the full walkthrough
Ontolo
Orvika Ship Management / MV Guillemot / Findings / 4.18
Day 5 of 15 · 10 days left
Vessel Supramax · 56,800 dwt · built 2014 · Manager Orvika Ship Management · 21 vessels · Inspection Gdansk · 2026-09-10
{{item.group}}
Fire extinguishers
HIGH Section 4 · ISM System · Question 4.18 RECURRING · PSC ROTTERDAM, JUN 2026

{{b.t}}

{{b.t}}

{{b.t}}

{{b.meta}}

Summary
{{c.t}}
{{b.label}}
Drafted by Ontolo

{{b.text}}

SOURCES{{c.t}}
{{b.label}}
{{b.by}}
#ActionOwnerDueStatus
{{r.n}} {{r.a}} {{r.o}} {{r.d}} {{r.s}}

{{b.tally}}

{{b.label}}
{{r.n}} {{r.a}} {{r.s}} {{r.ev}}
{{b.sid}}
{{b.title}}
{{b.body}}
VesselLast service reportUnits on reportUnits in registerStatus
{{r.v}}{{r.date}}{{r.rep}}{{r.reg}}{{r.status}}
{{b.head}}

{{b.text}}

{{r.who}}{{r.what}}{{r.when}}
Back to findings Edit response
{{statusLabel}}

Working prototype on synthetic data. Vessel, company and people are invented.

Watch the full walkthrough · 5 min

How it works

Four moves, and a loop.

Learn Close out 02 01 03 04 05
Learn what gets accepted, and why Close out this inspection, with sources 01A FINDING ARRIVES 02 · THE RECORD ANSWERS 03 · ONTOLO REASONS OVER THE RECORD 04A NAMED PERSON APPROVES THE INSPECTOR ACCEPTS OR REJECTS THE NEXT DRAFT STARTS FROM WHAT PASSED
01

A finding arrives

Drop the inspection report. PDF, Word or Excel. Ontolo splits it into findings, each with its deadline.

02

The record answers

Built from the documents and systems you already run, in whatever format they arrive.

03

Ontolo reasons over the record

Drafted root cause, actions, evidence and fleet scope with sources.

04

A named person approves

Every edit and approval is logged by name. Nothing leaves the system until a person signs it.

The verdict returns to the record

01

A finding arrives

Drop the inspection report. PDF, Word or Excel. Ontolo recognises the questionnaire and splits it into findings, each with its deadline.

02

The record answers

Built from the documents and systems you already run, in whatever format they arrive.

03

Ontolo reasons over the record

Drafted root cause, actions, evidence and fleet scope with sources. If a source is missing or too thin, the system says so.

04

A named person approves

Every edit and approval is logged by name. Nothing leaves the system until a person signs it.

Ontolo learns what gets accepted.

Every verdict goes back into the record: accepted, rejected, and why. The next draft for that kind of finding starts from what actually passed. The longer you use it, the closer the first draft lands to an accepted response, and the fewer rounds each close-out takes.

The record

Everything the answer is drawn from.

One record per ship, in five layers. Nothing is drafted that these layers cannot support.

The value

What changes, from one desk to the whole fleet.

A finding is raised on one desk. Its cause and its consequence sit higher up. Ontolo carries the answer through every level.

01 · THE FINDING 02 · THE RESPONSE 03 · THE FLEET

Your data

Our operating commitment.

Your data belongs to you. It is used to answer your findings, and for nothing else. These are commitments written into the agreement, not settings, and our AI providers are bound to the same terms.

{{r.lab}}

{{r.title}}

{{r.text}}

We are seeking design partners

If close-outs eat days you do not have, work with us.

Work through your next close-out with us, using your real findings alongside your team. Scope and data handling are agreed with you before we start.

Discuss a design partnership

Thirty-minute exploratory call with Sascha

What you get

{{r.num}} {{r.label}}{{r.text}}
Live todayRightShip RISQ
Expanding toOCIMF SIREPort state controlClassFlag state
Tell us which one hurts most.

Contact

Let's look at your close-out process together.

Thirty minutes: how you close out findings today, what the prototype does, and whether a test partnership makes sense for your fleet.

Sascha Struwe

Sascha Struwe, PhD

Founder · Copenhagen

Ex Business Architect and Change & Adoption Lead at WPP Enterprise Solutions MAP. PhD in B2B Service Innovation, Aalborg University.

Book a call

{{ status }}

Goes to Sascha so he can reply, and is used for nothing else. Kept 12 months, then deleted. Privacy notice