Planned Maintenance at Sea: Running-Hours Jobs and Class-Survey Readiness

On a ship, maintenance is not a backlog to clear when there is time - it is a programme that has to run whether or not anything has broken. Machinery has to be serviced on schedule, spares have to be aboard before they are needed, and when a class surveyor arrives, the chief engineer has to show a defensible history of what was done and when. That is the job of a marine planned maintenance system (PMS, in the engineering sense of the term).

It is a different discipline from "raise a ticket when something fails." Done well, it keeps the vessel ahead of the work rather than behind it.

It starts with the equipment register

You cannot maintain what you have not catalogued. A planned maintenance system is built on a vessel equipment register - every piece of machinery in a hierarchy of systems, sub-systems and components. Each item carries a criticality rating (1 to 4, per IACS UR Z16) and class-society references (DNV, LR, RINA, BV, ABS). That register is the spine everything else hangs from: jobs, spares and survey readiness all reference it.

Criticality matters because it drives priority. When you cannot do everything at once - and at sea you often cannot - you do the critical equipment first, and the system makes that obvious.

Jobs that raise themselves

The heart of the system is planned maintenance jobs that generate automatically. You define a template once - this service, this interval - and the system raises the job when the trigger is met:

• a running-hours threshold (the pump has done its 2,000 hours), or
• a calendar interval (six months since the last service).

The chief engineer is not maintaining a wall planner and hoping nothing slips. The work appears when it is due, and a controlled, auditable history accumulates as it is completed. Good systems also guarantee they never raise the same job twice, however the data syncs between ship and shore - so the programme stays clean even on an offline-first vessel.

Class surveys become a download, not a scramble

Class surveys are where a maintenance record proves its worth. A surveyor wants evidence that critical equipment has been maintained to schedule. If your record is a defensible, equipment-linked history - every job, every completion, tied to the item and its class references - then survey readiness is a matter of producing it, not reconstructing it. The difference between a calm survey and a stressful one is almost entirely the quality of the record you walk in with.

Where it connects

A planned maintenance system is most valuable when it does not stand alone. Tie it to spares and procurement and you can see whether the parts a job needs are actually aboard. Tie it to the service-ticket workflow and unplanned defects sit alongside planned work in one view. The chief engineer gets a single picture of everything the engine department owes the ship.

What to ask

• Are jobs generated from running-hours and calendar thresholds, or entered by hand?
• Is the equipment register rated for criticality and linked to class references?
• Can you produce a class-survey-ready maintenance history on demand?
• Does it run offline and reconcile without creating duplicate jobs?

The bottom line

A marine planned maintenance system turns maintenance from a reactive scramble into a controlled programme: an equipment register that knows what is critical, jobs that raise themselves on running hours and calendar, and a history that makes class surveys defensible. For the chief engineer, that is the difference between chasing the work and staying ahead of it.