New Build PMS Database: When Should You Start?

The most common question from new build projects: "When should we start building the PMS database?"

The most common answer from yacht management: "After delivery."

This is the most expensive approach. Here is why, and what to do instead.

The post-delivery problem

When a new build is delivered, the engineering team inherits a vessel with hundreds of pieces of equipment, thousands of maintenance tasks, and a PMS that is either empty or populated with generic data that does not match what is actually installed.

The Chief Engineer is now simultaneously: - Learning the vessel's systems during commissioning - Managing the crew during sea trials and the maiden voyage - Trying to build a database from a pile of manuals in a filing cabinet - Running the vessel operationally, often with guests onboard within weeks

This is not a recipe for a well-built database. It is a recipe for a database that gets started, half-finished, and eventually abandoned because operational demands take priority.

The result: maintenance gets tracked on paper, in spreadsheets, or in the engineer's head. The PMS exists but nobody trusts it. Two years later, preparing for the first yard period, someone realises the database needs to be rebuilt from scratch.

Start during the build

The right time to start is during construction, not after delivery. Here is why:

Documentation is available as systems are installed

During the build, documentation arrives in phases as equipment is delivered and installed. O&M manuals, parts lists, commissioning reports — all produced as part of the construction process.

This is the best documentation you will ever have. It is current, complete, and directly relevant to the equipment actually installed. Two years post-delivery, manuals get lost, crews change, and nobody remembers which version of the watermaker was installed.

The hierarchy can be built from shipyard documentation

Shipyards produce detailed equipment schedules, system lists, and technical specifications as part of the build process. These are the ideal source for building the equipment hierarchy — the structure is aligned to how the vessel was designed and built.

There is time to do it properly

During a build, the database can be developed systematically over months, in step with the construction schedule. Each system gets built into the database as it is installed and its documentation becomes available.

After delivery, the same work has to be compressed into weeks while simultaneously running the vessel. Quality inevitably suffers.

How to align database development with the build

Phase 1: Establish the hierarchy early

As soon as the builder's equipment schedule and technical specification are available, the top-level hierarchy can be established. This gives you the skeleton — every system and sub-system in its correct position.

This hierarchy is locked early and serves as the master framework for everything that follows.

Phase 2: Build the documentation matrix

Track every piece of documentation as it arrives from the yard and equipment suppliers. A documentation matrix shows what has been received, what is outstanding, and the impact of any gaps.

This matrix is a living document throughout the build. It gets updated as new documentation arrives and new equipment is installed.

Phase 3: Develop system by system

As each system's documentation becomes available (O&M manuals, parts lists, commissioning data), that system gets built into the database. Equipment details, maintenance tasks, and spare parts — extracted from the documentation and linked to the hierarchy.

This work does not need to follow the build sequence. It can happen in any order as documentation arrives.

Phase 4: Crew review before handover

Before the vessel is handed over, the crew reviews the database against what is actually installed. This catches any discrepancies between the documentation and reality — equipment that was changed during the build, modifications made during commissioning, or systems that differ from the original specification.

The handover advantage

A vessel delivered with a complete, crew-reviewed PMS database has a fundamentally different operational start than one delivered with an empty PMS.

Day one, the engineering team has: - Every piece of equipment registered and classified - Every manufacturer-recommended maintenance task scheduled - Every spare part catalogued with correct part numbers - A clear picture of what maintenance is due and when

No scrambling, no guessing, no "we will sort it out later." The vessel is operationally ready from the start.

What about the cost?

Building the database during the build costs the same as building it after delivery. The scope of work is identical — the same equipment, the same manuals, the same data.

The difference is efficiency. During the build, work progresses steadily over months with documentation arriving in an orderly fashion. After delivery, the same work is compressed into a shorter window with competing operational demands.

If anything, starting during the build is cheaper because: - Documentation is more accessible and better organised - There is no need to source missing manuals years after delivery - The crew review happens before operational pressures begin - There is no cost of running a vessel with an incomplete database (missed maintenance, wrong parts ordered, survey findings)

The review period

For new build databases, the review period starts at vessel handover, not at database delivery. This is because systems cannot be fully verified until they are commissioned and operational.

This gives the crew 30 days from handover to check the database against the actual vessel. Any errors or omissions are corrected at no charge.

Summary

Start your PMS database during the build, not after delivery. The documentation is better, the timeline is more manageable, and the vessel is operationally ready from day one.

The hierarchy gets established early from shipyard documentation. Systems are built into the database as their documentation arrives. The crew reviews before handover. And when the vessel is delivered, the PMS is ready to use — not ready to start building.

The most expensive PMS database is the one you have to build twice.