PMS Database Services for Superyachts

We build your PMS database from OEM documentation — so your engineering team can focus on the vessel.

Complete Vessel Database

One complete deliverable covering every system on your vessel. We extract, structure, and verify all the data from your OEM documentation — work that would take your engineering team months of evenings and weekends.

Your crew stays involved through three review milestones, confirming the database reflects how the vessel is actually built and operated. But the extraction, structuring, and quality assurance? That's on us.

Equipment Hierarchy

Your complete equipment register, structured by system and location. Every component from main engines to bridge electronics, organised the way your vessel is actually built. Manufacturer, model, type designation, and technical specifications from OEM documentation — all in a logical hierarchy aligned to shipyard documentation.

Maintenance Library

All manufacturer-recommended maintenance tasks extracted directly from OEM operation and maintenance manuals. Hours-based and calendar-based scheduling, with 'whichever comes first' logic preserved exactly as the manufacturer specifies. Every task linked to the specific individual equipment it applies to — not to a system level.

Spare Parts Catalog

Complete spare parts data compiled from OEM parts manuals and documentation. Manufacturer part numbers and descriptions linked to the specific equipment each part serves. Your crew can see exactly which parts belong to which equipment — no guessing, no searching through separate lists.

Delivery & Ownership

Delivered as a comprehensive Excel workbook that belongs to the vessel permanently. This is your master reference file, independent of any PMS platform. You also receive a database guide explaining the structure, naming conventions, and how to maintain the database going forward. You own the data — no licensing fees, no restrictions.

Example equipment hierarchy

What you receive

Timeline

Operational vessels: typically 4–12 weeks depending on vessel size, complexity, and documentation availability. New builds: timeline follows the build schedule as documentation is released progressively.

What Makes the Difference

The details that separate a database that works from one that creates more problems than it solves.

Consistent Naming

Standardised naming conventions documented, agreed with your crew, and applied across every equipment item, task, and spare part. No more "ME1", "Main Engine #1", and "M/E Port" in the same database.

Shipyard-Aligned Structure

Equipment hierarchy aligned to your vessel's actual build and shipyard documentation. Not a generic template — a structure that reflects how your vessel was designed and built.

Full Traceability

Every entry sourced from and verifiable against OEM documentation. If you want to check where a task interval came from, you can trace it back to the exact manual and page.

Crew Review Milestones

Your team reviews and confirms the database at three key points during development. The final product reflects how your vessel is actually run, not just what the manuals say.

Equipment-Level Linking

Every task and every spare part linked to the specific individual equipment it applies to. No tasks assigned to "systems" — everything is precise and unambiguous.

Quality Assurance

Full QA process before delivery: naming consistency, completeness, traceability, duplicate and orphan checks. All verified against source documentation.

The difference, side by side

Additional Services

Available alongside or after the core database build. We'll discuss what's relevant for your vessel during our initial conversation and include it in your proposal.