Track every subsea asset from warehouse to seabed.

Every vessel, container and shore-side warehouse is a location in one shared tree. A part sits in exactly one location at a time and moves between them are recorded, so a single search tells you which vessel or store holds the spare and how many are left there. Stock levels and reorder points are held per location, not just per fleet.

Yes, with the offshore parts that generic PMS tools leave out. Equipment sits in an asset register, jobs carry their own interval and their own overdue threshold, and every completed occurrence keeps its steps, readings, photos and sign-off. The next due date is calculated from the job actually completed rather than a fixed calendar, so a service that slipped through a crew change reschedules honestly instead of quietly going green.

Yes, and the fleet view is the point. Every vessel is a branch of one asset register: spares, maintenance history and certification stay with the vessel, while overdue jobs, open faults and availability roll up across all of them on one screen. A superintendent onshore sees which vessel is carrying the overdue work and which spare is sitting on the wrong boat; the crew aboard see only their own. One database, filtered to whatever you are responsible for, instead of a monthly exercise in merging vessel spreadsheets.

Each planned maintenance occurrence records who carried out the job, when each step was completed, the readings entered, any photos attached and the sign-off. Records are appended rather than overwritten, so when a client asks what happened on a given date you can show the trail instead of reconstructing it. The structure follows the record-keeping habits IMCA-aligned operations already work to.

Yes. The system tree holds assemblies to any depth, so a thruster sits under an ROV, its seal kit sits under the thruster, and the bill of materials rolls up from the parts actually fitted. Move a container or a sub-assembly and everything beneath it follows, so the hierarchy stays honest.

That is what it was built for. Subsea asset management is the awkward case for generic maintenance software: the equipment moves between vessels, gets rebuilt at sea out of a spares kit, and has to be evidenced afterwards. Roger That! models the assembly rather than a flat asset list, so ROV spares management and subsea equipment maintenance follow the kit as it moves instead of staying behind with the last vessel it sailed on.

Yes. Operational events, downtime, crew movements and safety observations are logged through the day and pulled into a single daily progress report (DPR). The client reviews it and signs it in the system, and you can see at a glance which reports are still unsigned. Once approved, the report is locked.

Yes. Downtime events are logged against the system that caused them and categorised, so unpaid hours are totalled separately and broken down by cause. The dashboard shows your system availability rate per project and across the fleet, alongside open faults and overdue planned maintenance, so you can see what is driving the number.

Yes. Certificates are held against the part they belong to, and the compliance view counts expired, expiring and missing certificates separately so nothing sits unnoticed until an audit. Hose registers are handled the same way, with specifications, assemblies, end fittings and inspection history kept as structured records.

Jobs carry their own recurrence rule and overdue threshold. Roger That! calculates the next due date from the last completed occurrence and raises the job to a warning state before the due date passes, so the crew sees it while there is still time to plan it into a window.

Wherever you want it. Roger That! runs on PostgreSQL and Linux — on a local server aboard the vessel, in the cloud in a region you choose with UK and EU hosting available, or both, with the vessel syncing to the cloud when the link is up. Backups are taken daily with point-in-time recovery and are restore-tested. The stack is self-contained, so your data is not spread across a chain of third-party services.

Yes. Roger That! can run entirely on a local server aboard the vessel, so the crew keeps working at full speed whether or not the satellite link is up. When connectivity returns, the vessel syncs with the cloud and shore-side staff see the same picture. You can also run it cloud-only if your vessels have reliable bandwidth, or mix the two across a fleet.

Narrower, faster, and aimed at a problem the big suites were never shaped around. An EAM rollout is a project in its own right; Roger That! is running on your own data in weeks and covers the offshore end of it — asset integrity, unplanned downtime, certification and the daily progress report the client signs. You give up enterprise-wide finance and procurement workflows. You get a system that already understands an ROV rebuilt at sea out of a spares kit, and a thruster that moves between vessels without losing its history. If you need a deep EAM integration on day one, say so early — that is not where we are yet.

Yes, for shore-side work that feeds a fleet. Warehouses, workshops and the people in them are first-class locations rather than an afterthought bolted onto a vessel system, so a thruster stripped in a workshop in Aberdeen, recertified and shipped back out to the boat carries one continuous history across the whole loop — which is exactly where spreadsheet handovers lose it. That is the preventive maintenance and MRO case we are built for. Plant or manufacturing MRO with no offshore leg is not our fight, and you would be better served elsewhere.

Usually, yes. Most fleets arrive with spreadsheets, an old database export or a mix of both. We map what you have onto the parts catalogue and location tree, load it, and show you the result before you commit to it.

A short assessment of how your fleet tracks parts and maintenance today, a working environment loaded with your own data, and direct access to the people building the software. In return we want honest feedback from crews and shore-side staff while the product is still shaped by it.