Track every subsea asset from warehouse to seabed.
Roger That! is an offshore CMMS built for ROV and subsea teams. Spares, planned maintenance, downtime and the daily progress report the client signs — one system, on the vessel and onshore.
Now in Beta with early offshore operators. Built by engineers with 16 years offshore.
- Daily progress reports & sign-off
- Downtime & availability tracking
- Planned maintenance & checklists
- Vessel & warehouse spares
- Certification & HSEQ records
- Works without a satellite link
Sound familiar?
Three ways a fleet loses money that have nothing to do with the equipment itself.
The spare wasn't on the vessel
The part was in stock. It was in the wrong warehouse, or on the wrong vessel, or on a spreadsheet last updated two mobilisations ago. The dive waits while somebody phones round.
The PM slipped, then the unit failed
Nobody skipped it on purpose. The job was due while the crew changed over, the paper log went in a drawer, and the first anyone knew was the fault on deck.
The client asked, and nobody could prove it
The work was done properly. Proving it means chasing photos on phones, notes in three formats and a technician who left the company in March.
Roger That! was built around these three problems, by people who had them.
Meet Roger That!
One system for what you own, where it is, and what has been done to it — from a seal kit in a shore-side store to the ROV on deck.
Every part, every assembly, every vessel
See what's fitted to what, and where it is. Build assemblies to any depth — a seal kit under a thruster, under an ROV, under a vessel — and the parts list follows the kit as it moves.
- Searchable system and location tree across the whole fleet.
- Service state on every item: in service, fault, or out of service.
- Move a container or an assembly and everything inside it moves with it.
Planned maintenance that doesn't slip
Every job carries its own interval and its own overdue threshold. Roger That! works out what's due next from the last job actually completed, and flags it before the date passes.
- Step-by-step checklists so the job is done the same way on every shift.
- Photos and instructions attached to the step, not buried in a manual.
- Digital sign-off, so you know who did it and when.
- Overdue PM counts per vessel and across the fleet, on one screen.
Know what you're short of before you sail
Roger That! compares what a system needs against what you actually hold, and tells you the shortfall — per vessel, per warehouse, per assembly.
- Stock levels and reorder points held per location, not just fleet-wide.
- Serial number tracking and certificates linked to the part.
- Purchase requests, cargo manifests and hired equipment tracked through to arrival.
The report the client signs
Where the day's work turns into the record you get paid on.
One DPR, built as the day happens
Operational events, downtime, crew on and off, safety observations — logged as they occur and pulled into a single daily progress report. The client reviews and signs it in the system.
- Event log, downtime, crew and HSEQ sections in one report.
- Crew embarked and disembarked, with role and organisation.
- Client review and signature — you can see what's still unsigned.
- No retyping the same figures into a spreadsheet at 2am.
Know what downtime is costing you
Downtime gets logged against the system that caused it, broken down by category, and totalled. You see your availability rate and your unpaid hours without building a spreadsheet to find them.
- System availability rate, per project and across the fleet.
- Unpaid downtime totalled and broken down by cause.
- Downtime tied back to the equipment and the fault that caused it.
- Open faults and overdue PMs alongside it, so the pattern is visible.
Ready for the audit, not scrambling for it
The three things a client or auditor asks for, kept current instead of reconstructed.
Certification that doesn't lapse
Certificates tracked against the part they belong to, with expired, expiring and missing counted separately — so you find the out-of-date LOLER cert before the client does, not after.
Hose registers, properly kept
A real hose register: specifications, assemblies, end fittings and inspection history, held as structured records rather than a spreadsheet somebody inherited.
Incidents and HSEQ in the same system
Incidents, injuries, asset damage and safety observations logged against the job and the vessel, and carried into the daily report — not kept in a separate folder nobody opens.
Built by people who have done the job
Roger That! comes from GRAM Systems and Concept Informatics, working in partnership: 25 years of database design behind it and 16 years offshore in front of it. We know what a handover looks like at 3am, why the spares list drifts, and what a client actually asks for in an audit.
That is why the data model is relational rather than a pile of spreadsheets, and why the screens are built for someone wearing gloves on a moving deck.
What it changes day to day
The practical difference for crews offshore and the people supporting them onshore.
Simple enough to actually get used
If the crew needs a week of training, the records rot. Roger That! is built to be picked up in an afternoon, so the data stays current.
Find a part in seconds
One search across every vessel and warehouse tells you what you have, where it is, and what it is fitted to.
Your data, where you want it
On a server aboard the vessel, in the cloud in a UK or EU region, or both. PostgreSQL on Linux, daily backups with point-in-time recovery, no third-party lock-in.
Fewer unplanned stops
Recurrence rules and overdue thresholds raise a job before the due date passes, while there is still a window to plan it into.
The same job done the same way
Step-by-step checklists mean the work matches the technical spec whichever crew is on shift.
An audit trail you can hand over
User records, timestamps, photo attachments and sign-offs, kept as history rather than overwritten.
Getting you onto Roger That!
Nobody starts from a clean sheet. Here is how a fleet gets from spreadsheets and a legacy database to running on Roger That!
Consultation
We sit down and follow the information: how parts get requested, how maintenance is logged, what the client asks for at audit. Where your process is sound, we fit around it.
Migration
Spreadsheets, exports from an old system, or both. We map what you already have onto the parts catalogue and location tree, load it, and show you the result before you commit.
Deployment
A self-contained stack — Go, PostgreSQL, Linux — installed on a vessel server, in the cloud region you choose, or both. Backups and recovery configured from day one.
Support
One-to-one training for the people who will use it, monitoring on our side, and a direct line to the engineers who built it. On-site in the UK and Cyprus.
Bespoke database work is how we get you onto the product — not a separate pitch.
Book a Demo & AssessmentQuestions offshore teams ask
Straight answers, including the things Roger That! cannot do yet.
How do I track spares across multiple vessels and shore-side warehouses?
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.
How does Roger That! keep planned maintenance records audit-ready?
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.
Can it map complex parent-child assemblies and BOMs?
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.
Can we produce a daily progress report the client can sign?
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.
Does Roger That! track chargeable and unpaid downtime?
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.
Can it track lifting and certification expiry across the fleet?
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.
How are overdue maintenance jobs flagged before something fails?
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.
Where is the data hosted and how is it backed up?
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.
Does it work offline or with poor vessel connectivity?
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.
Can we bring our existing spares data across?
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.
What does the Beta programme involve?
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.
Book a demo and fleet assessment
Tell us how you track parts and maintenance today. We will show you the same thing running in Roger That! — no obligation, and we will say so if it is not a fit yet.