What Is a Planned Maintenance System?
A planned maintenance system (PMS) is a structured programme that schedules, executes and documents the maintenance of all shipboard machinery, equipment and structures at defined intervals — by calendar, running hours or measured condition — so that the vessel remains safe, reliable, insurable and compliant.
In practice a modern PMS is software: a living database of every maintainable component on board, the jobs attached to each, the counters and dates that trigger them, the spares they consume, and the complete evidence trail of what was done, by whom, and what was found.
The PMS is also the vessel's institutional memory. Crews rotate every few months; a well-kept maintenance history is often the only continuous record of an engine room's real condition across years and crew changes.
Is a PMS Mandatory? What the ISM Code Requires
Yes. ISM Code paragraph 10.1 requires every company to establish procedures ensuring the ship is maintained in conformity with relevant rules and regulations and any additional company requirements. That breaks down into concrete obligations:
- Inspections held at appropriate intervals (10.2.1)
- Reporting of non-conformities with possible causes (10.2.2)
- Appropriate corrective action (10.2.3)
- Records of all these activities (10.2.4)
- Identification of critical equipment whose sudden failure may cause hazardous situations, with specific measures to promote reliability and regular testing of standby arrangements (10.3)
Beyond ISM, classification societies approve PMS schemes that unlock continuous machinery survey (CMS) arrangements — letting chief engineers credit surveys through documented PMS overhauls instead of opening machinery for a surveyor. Port State Control routinely checks overdue jobs during inspections, and a neglected PMS is a classic ISM major non-conformity that can take a ship out of service.
Maintenance Strategies Compared
| Strategy | Trigger | Best For | Trade-Off |
|---|---|---|---|
| Corrective (run-to-failure) | Breakdown | Redundant, low-consequence items only | Unacceptable for critical equipment; highest true cost |
| Preventive (calendar / running hours) | Fixed intervals per makers' recommendations | Regulatory minimum; the backbone of every PMS | Over-maintains healthy equipment; parts and labour spent on schedule, not need |
| Condition-Based (CBM) | Measured condition — vibration, temperatures, lube-oil analysis, performance | Rotating machinery, purifiers, pumps, aux engines | Requires sensors, routines and discipline in data capture |
| Predictive (PdM) | Trend analytics and AI forecasting on condition data | Main engine, critical systems on connected fleets | Needs quality historical data — which the PMS itself provides |
These are layers, not alternatives: preventive scheduling satisfies class and ISM, condition monitoring refines intervals, and predictive analytics catch the failures the calendar can't see. Industry studies consistently put the savings of condition-based and predictive layers at 25–30% of maintenance spend versus purely calendar-based programmes, with unplanned downtime reductions up to 70% on monitored equipment.
Core Components of a Modern Ship PMS
Equipment Hierarchy & Technical Library
A structured component tree — vessel → system → equipment → component — carrying makers' data, drawings, manuals and certificates. Everything else in the PMS hangs off this hierarchy, so its quality at implementation determines the system's value for a decade.
Job Scheduling & Work Orders
Calendar and counter-based jobs with clear instructions, safety precautions, required spares and tools. Running-hour counters updated from noon reports or automatic logging drive the due list the chief engineer actually works from.
Critical Equipment & Spares Linkage
ISM 10.3 critical items flagged and locked to stricter workflows, with minimum-stock spare parts linked directly to jobs — so completing an overhaul decrements stock and triggers procurement before the next one is due.
Class & Survey Integration
CMS items mapped to class survey codes, with windows, postponements and credits tracked so the superintendent sees survey exposure across the fleet at a glance.
Defect & Non-Conformity Management
Breakdown reporting with cause analysis feeding corrective actions — closing the ISM 10.2 loop and building the failure history that predictive layers learn from.
Dry-Dock & Major Overhaul Planning
Long-horizon planning that aggregates postponed jobs, survey items and owner's work into a specification, then tracks execution and cost against it.
Offline Ship–Shore Synchronisation
Non-negotiable at sea: the vessel database must work fully offline and reconcile automatically with the office when connectivity returns, without duplicating records or losing counter readings.
KPIs & Fleet Dashboards
Overdue percentage, critical overdue, MTBF on key machinery, spares consumption and maintenance cost per running hour — visible per vessel and across the fleet.
Why It Pays: Beyond Compliance
- Uptime and earnings — every avoided breakdown is avoided off-hire, deviation and claims exposure.
- PSC and vetting performance — inspectors read the PMS as a proxy for management quality; SIRE 2.0 and RightShip both probe maintenance evidence.
- Asset value — a complete, credible maintenance history materially supports resale and charter negotiations.
- Insurance — documented maintenance of critical equipment is the first thing H&M underwriters and P&I clubs examine after a casualty.
- CII and fuel efficiency — hull, propeller and engine condition are top CII levers; the PMS is where that work is scheduled and evidenced. See our CII rating guide.
- Crew workload — planned work in normal hours instead of emergency repairs at 0300 is a genuine work-and-rest-hours and safety issue.
Choosing PMS Software: A Practical Checklist
| Criterion | What to Verify |
|---|---|
| Offline capability | Full functionality with zero connectivity; automatic conflict-free sync; proven on low-bandwidth SATCOM |
| Class acceptance | Track record of PMS scheme approvals with your class societies for CMS arrangements |
| Integration | Native links to inventory, procurement, crewing, document management and voyage data — not CSV exports between silos |
| Usability on board | A due list a second engineer can work from after a 30-minute handover; mobile/tablet job completion in the engine room |
| Data migration | Structured import of your existing hierarchy, histories and counters — the vendor's methodology matters more than the demo |
| Analytics & AI readiness | Condition-monitoring inputs, trend dashboards, and a data model clean enough to support predictive maintenance later |
| Fleet scalability | Fleet-standard job libraries with vessel-level variations; one office view across all ships |
| Security & compliance | Encrypted sync, role-based access, audit trails, IMO cyber-risk (MSC.428(98)) alignment |
Implementation in Five Steps
- Baseline and clean your data. Audit the existing equipment registry, counters and histories; a PMS inherits the quality of what you load into it.
- Build the fleet-standard library. Define hierarchy, job descriptions and intervals once at fleet level, then apply vessel-specific deltas.
- Pilot on one or two vessels. Run a full maintenance cycle, tune intervals and workflows with the crews actually using it.
- Roll out with structured training. Train per rank and rotation, not once per vessel — the relief chief needs the same onboarding as the incumbent.
- Govern and improve. Review KPIs monthly, feed defect analysis back into intervals, and extend into condition-based and predictive layers as data accumulates.
See planned maintenance the way it should work — connected
Volaxin Maritime Suite unifies PMS with inventory, procurement, crewing, work-rest hours and CII reporting in one platform — with true offline ship-side operation and automatic cloud sync, trusted across 500+ vessels.
Request a DemoFrequently Asked Questions
What is a planned maintenance system on a ship?
A structured, documented programme — today almost always software — that schedules and records maintenance of shipboard equipment by calendar, running hours or condition, satisfying ISM Code paragraph 10 and class requirements.
Is PMS software mandatory?
The ISM Code mandates the maintenance regime and its records, not a specific tool — but at any realistic fleet size, paper systems fail audits in practice. Class-approved software is the industry norm and a prerequisite for CMS arrangements.
What is the difference between PMS and CMMS?
A CMMS is generic industrial maintenance software; a marine PMS is a CMMS built for ships — class survey integration, critical equipment per ISM 10.3, offline ship–shore sync and flag/PSC-ready reporting.
How often should shipboard equipment be maintained?
Start from makers' recommendations and class requirements, then refine with your own condition data and failure history. The interval that matters is the one your evidence supports at survey.