A Planned Maintenance System Is Not a Superyacht Operating System

A planned maintenance system is one of the best pieces of software many yachts already own. That does not make it an operating system, even when the vendor starts using the phrase.

What a PMS is actually for

A PMS exists because a yacht is a plant. Equipment has manufacturer intervals, running hours, job cards, spares and a history that a class or flag surveyor is entitled to see. Logging a service against a named asset, with the parts used and the person who signed it, is a real job. Spreadsheets and paper job cards can do it. A mature PMS does it better.

That category is not the problem. Many dedicated PMS products are specialised, stable and honest about the one job they do. The problem starts when the same product, or a thin layer on top of it, is sold as the system for the whole yacht.

Seven departments, not one

A superyacht is not an engine room with a hotel attached. It is seven kinds of record that already exist on board, whether or not any of them are digital: navigation and passage planning; maintenance and work orders; crew and certification, including STCW, medicals and MLC rest hours; provisioning and inventory; charter and guest services; compliance, including MARPOL logs, ISM documentation, flag and class papers; and owner financial oversight.

A superyacht operating system is the layer those records share. Admissions, pharmacy and billing are separate hospital jobs, but they read the same patient file. A yacht that enters a guest allergy in the interior notebook, a certificate expiry in a crew spreadsheet and a spare part in the PMS has three files. The test is whether they are one.

A vessel does not have to use every category on day one. Many operations start with maintenance and crew, because those already have software equivalents and a survey calendar. What has to hold, if the label is going to mean anything, is that the second category shares the record with the first. Two products under one login are still two products.

How to tell if a vendor is wrapping a PMS

Ask questions that force the data model into the open. Feature lists will not do it. Every vendor can show a work-order screen.

Does a certificate expiry logged against a crew member appear in the compliance view without being typed again? If a surveyor asks who was qualified and on watch for a job, can you answer from the same record as the job card?

Does a part ordered against a work order show up in inventory, next to galley stock, or is there a second spares list the steward cannot see and the engineer does not trust?

If the passage plan adds a port call, does provisioning see lead times for that harbour, or does the chef find out from a WhatsApp forward? If a guest's dietary restriction is logged, does it reach the provision list, or is it a PDF on the chief steward's laptop? When a work order carries a cost, does it appear in the owner view as that work order, or only as a monthly total after someone re-keys invoices?

If any of those answers is "we export a spreadsheet" or "that is in the other module, you re-enter it", the categories are not unified. The product may still be a good PMS. It is not an operating system.

Watch also for interface theatre. A new dashboard and a mobile app on top of the same asset tree do not change what the software can see. If the only deep objects are equipment, intervals and spare parts, you are looking at a maintenance tool. Crew, guests and spend will be fields bolted on: incomplete, optional, first to go stale.

Ask to log in as the captain, then as the chief stew, then as the owner's representative. If every role lands in running hours and job cards, the product is a PMS with extra users.

Surveys, handovers and the cost of the seam

The PMS is at its best the day before a class survey, if the hours were kept current. It is at its weakest the day a chief engineer signs off.

The incoming engineer inherits whatever is in the system and whatever was in the outgoing engineer's head. Intervals and job history, if they were logged, survive. The reason a pump was left on a shortened interval, or the supplier who actually has the impeller, often lives in notes. A wrapped PMS does not fix that unless the surrounding context is in the same record.

Crew change elsewhere on the yacht exposes the same seam. STCW and rest hours are not maintenance data, but they decide who can do the job the PMS just raised. A work order assigned to someone whose rest window is closed, or whose certificate lapsed last month, is a compliance problem created by two systems that do not speak.

Provisioning is the other regular failure. A spare for a work order and a case of wine for a charter guest are both inventory. On most yachts they are two lists, two people, two budgets. The owner's representative then sees two unexplained lines and has to call the captain. That call is not a reporting feature. It is the seam.

What AI does not fix

Putting a chat box on a PMS does not turn it into an operating system. It turns it into a PMS you can query in English. That can still be useful. An engineer who can ask what is due before Barcelona is faster than one paging through job cards in a seaway. It does not create a guest record, a crew record or an owner spend record, and it does not survive a department the software cannot see.

AI is only as good as the record it is allowed to read. YachtOS uses voice and chat against a shared core covering those seven categories. The captain still approves anything that matters. The model does not get to invent a certificate date or a fuel figure. Humans stay in command.

What this means on board

Keep the PMS you trust for machinery if it is doing the job. Do not accept the word "operating system" unless departments share a record. Test that with one fact, a certificate, a part, a dietary restriction, and follow it across screens. If you have to type it twice, you are buying a bundle, not a platform.

The longer definition of the category is on What is a superyacht operating system? YachtOS is built for that shape of work, with role-based apps rather than one screen for everyone. The apps are live demos. Humans stay in command. The software does not sign the survey. Try the live apps, or request a demo around the systems you already have.