A vessel is not a floating factory. It is an isolated industrial site exposed to salt, vibration and motion, operated by a team that rotates every two or three months, and monitored simultaneously by a Flag State, a classification society and, very often, a demanding charterer. When a bilge pump fails 300 miles offshore, nobody calls the supplier out within the hour. On board, maintenance is not a support function — it is a condition of operation.
This is exactly what a maritime CMMS (Computerised Maintenance Management System) is built for: software that structures the entire technical life cycle of the ship — equipment hierarchy, maintenance plans, work orders, spare parts, purchasing, statutory certificates, crew competencies — and that, unlike a shoreside industrial CMMS, must remain fully usable when the satellite link drops.
This guide covers the subject end to end: definition, differences from an industrial CMMS, functional architecture, gains by fleet type, the link with the ISM Code and class surveys, a five-step implementation method, common mistakes, a worked ROI calculation and selection criteria. Chief engineer, superintendent, DPA or owner: you will find enough here to frame your project properly.
What is a maritime CMMS?
A maritime CMMS is an information system dedicated to the maintenance and technical compliance of a vessel or a fleet. It holds, in a single database, the physical description of the ship, the maintenance tasks to be performed, their history, the parts consumed and the supporting evidence. Where a paper logbook or a folder of spreadsheets simply stores information, a CMMS makes it actionable: it triggers, reminds, records and reports.
The principle is straightforward. Every item of shipboard equipment is described once in a technical hierarchy. Maintenance plans are attached to it — every 500 running hours, every six months, every 2,000 starts. The system generates work orders at the right time, the crew completes and closes them with their observations, and the whole feeds a history that the shore office can consult in near real time.
CMMS, PMS and maritime ERP: sorting out the vocabulary
Three terms circulate and are frequently confused. The PMS (Planned Maintenance System) is the set of planned maintenance tasks required under the ISM Code and, in some cases, approved by the classification society. The CMMS is the software that carries that PMS and adds work order management, spares and history. A maritime ERP widens the scope further: purchasing, budgets, suppliers, crew, certificates, passengers, consumption. In practice, modern platforms merge all three levels, which avoids multiplying databases and double entry. If some technical terms are unfamiliar, the Smart Sailors maritime glossary covers the main ones.
Who is it for?
Contrary to a persistent belief, a maritime CMMS is not reserved for large commercial fleets. Three pilot boats, a 45-metre superyacht, a regional ferry, a deep-sea trawler or an offshore wind support base share the same fundamental need: knowing what must be done, by whom, with which part — and being able to prove it was done. Only the scale changes.
Industrial CMMS vs maritime CMMS: four constraints that change everything
You often hear that "a CMMS is a CMMS" and that a generic industrial tool will do the job on board. Field experience says otherwise: four structural constraints make the marine environment radically different from a shoreside workshop.
1. Intermittent connectivity
A factory CMMS assumes permanent network access. At sea, bandwidth is expensive, latency is high and dropouts are frequent. A maritime CMMS must therefore work fully offline: the crew records readings, closes work orders and consults procedures without a network, and data synchronises as soon as the link returns, transmitting only the differences to save bandwidth. An application that needs a connection to display a job card is unusable offshore.
2. Crew rotation
In a plant, the technician has known the machine for ten years. On board, the joining engineer may never have seen the vessel before. The CMMS becomes the technical memory of the ship, independent of individuals: intervention history, damage photographs, the predecessor's notes, safety instructions. That is what makes a clean handover possible. The Crew module completes the picture by tracking certificates of competency, medical certificates and individual expiry dates.
3. IMO regulation and the weight of evidence
A ship lives under permanent scrutiny: the ISM Code, SOLAS and MARPOL, MLC 2006, class surveys and Port State Control. Any intervention may have to be justified in front of an auditor. A maritime CMMS must therefore produce time-stamped, traceable evidence, not merely ticked boxes. We cover this in detail in our article on the ISM Code and maintenance compliance.
4. Logistical remoteness
Ashore, a missing part costs two hours. At sea, it costs a port call, a freight forwarder, sometimes downtime. Managing critical spares and anticipating supply against the trading programme are not optional extras but front-line functions, examined in depth in our guide to managing spare parts at sea.
| Criterion | Industrial CMMS | Maritime CMMS |
|---|---|---|
| Connectivity | Permanent network assumed | Offline operation mandatory, differential synchronisation |
| Users | Stable, specialised team | Rotating, multi-skilled, often multilingual crew |
| Compliance framework | Quality standards, machinery safety | ISM Code, SOLAS, MARPOL, MLC, class society, Flag State |
| Maintenance triggers | Calendar, running hours | Calendar, engine hours, starts, nautical miles, cycles, oil analysis |
| Parts logistics | Fast replenishment | Port call windows, forwarders, customs, high criticality |
| Functional scope | Maintenance and stock | Maintenance, stock, purchasing, certificates, crew, tanks, passengers |
| Reporting | Output, machine availability | Fleet, compliance, audit readiness, drydocking budget |
| Interface | Fixed workstation | Mobile and tablet, usable in the engine room |
The functional architecture of a maritime CMMS
A good maritime CMMS is built from functional blocks that feed each other. Here is the backbone found in mature solutions such as the 12 Smart Sailors modules.
The technical hierarchy: vessel, systems, equipment
Everything starts here. The vessel is broken down into systems (propulsion, power generation, steering, fire safety, water treatment, hull and structure), then into equipment, sub-assemblies and components. Each node carries its specifications, maker's documentation, photographs and associated spares — the role of the Equipment module. A sloppy coding scheme here produces an unusable CMMS within two years.
Maintenance plans: calendar-based and counter-based
Two logics coexist. Calendar tasks trigger on a fixed period: monthly extinguisher inspection, weekly emergency generator test, annual liferaft servicing. Counter-based tasks trigger on actual use: 250 engine hours, 1,000 starts, 5,000 nautical miles. A serious maritime CMMS handles both, per equipment item, with early warning thresholds. The Counters module collects shipboard readings and drives Maintenance due dates. To build a solid plan, see our 4-step method for an effective preventive maintenance plan.
Work orders
The work order is the daily unit of work. It carries the task, the job card, safety measures (isolation, permits to work, authorisations), the parts to be consumed and time spent. On closure, the crew records what was actually done, adds photographs and reports defects found. That discipline turns the CMMS into a single source of truth. On safety, see our article on lockout/tagout and work authorisations.
Stock and purchasing
Parts consumed on a work order automatically decrement shipboard stock, and a purchase request is proposed when a minimum level is reached. The Stock module handles locations, batches, equivalents and critical spares; the Purchasing module drives requisitions, quotation comparison, orders and receipts. This coupling is the main source of measurable savings, as explained in our article on MRO stock management and critical spare stockouts.
Certificates, tanks and forecasting
Class and statutory certificates, intermediate surveys, endorsements and crew documents all carry expiry dates, and overrunning one is expensive — sometimes up to detention. The Certificates module centralises documents, alerts at 90, 30 and 7 days, and produces a clean file for the inspector. Monitoring tanks (bunkers, lube oils, fresh and waste water) supports MARPOL compliance and cost control, while the Forecast module projects bunkering and maintenance workload against the coming trading programme.
Crew, passengers and fleet reporting
The Crew module tracks certificates, medicals, training and rest hours; for passenger vessels, the Passengers module handles headcount and the IMO FAL Form 6 required at each port call. Finally, the Dashboard aggregates what the owner cares about: preventive completion rate, overdue tasks per vessel, maintenance cost per vessel and per system, stock value tied up, statutory deadlines at risk. That is what moves maintenance from a technical topic to a management one, with ship-shore coordination handled in the Team module.
Where does your fleet stand? Four maturity levels
Before choosing a tool, it helps to position yourself honestly. The progression almost always follows the same path.
| Level | Medium | What works | What breaks | Audit preparation effort |
|---|---|---|---|---|
| 1 — Paper | Logbooks and engine room records | Simple, no training, robust on board | No fleet consolidation, lost documents, unreadable history | Several days |
| 2 — Spreadsheets | One file per vessel, exchanged by e-mail | Cheap, flexible, better than nothing | Diverging versions, no automatic alerts, no stock-maintenance link | 1 to 2 days per vessel |
| 3 — CMMS | Single database, structured plans and work orders | Automatic due dates, reliable history, time-stamped evidence, linked stock | Still depends on manual readings; can be abandoned if usage is not managed | A few hours |
| 4 — Connected CMMS | CMMS + offline mobile + automated data capture | Condition-based maintenance, early drift detection, continuous fleet oversight | Requires data discipline and clear governance | Immediate |
The decisive jump is between levels 2 and 3: that is where automated due dates and traceability are gained. Moving to level 4 is a finer strategy, described in our article on moving from corrective to condition-based maintenance.
Expected gains by fleet type
| Fleet type | What the CMMS changes first | Indicator to track |
|---|---|---|
| Yachting and superyachts | Impeccable traceability for resale value, clean handovers between seasonal crews, shipyard period preparation, justification of spending to the owner or management company | |
| Ferries and passenger vessels | Maintenance aligned with operating windows and statutory surveys secured: commercial availability comes first, since a missed sailing has an immediate cost | Commercial availability (missed sailings) |
| Port services (pilotage, towage, mooring) | Automated due dates on hard-worked, running-hour-driven engines, and spares pooled across sister craft | |
| Fishing | Spares anticipated before departure, on long trips with tight margins and critical dependence on auxiliaries (refrigeration, hydraulics, winches) | Downtime (the sector's most expensive) |
| Offshore (oil and gas, wind, research) | Evidence produced to meet charterers' documentation requirements, frequent client audits and contracts with penalties — evidence is worth as much as the maintenance itself | |
| Inland waterways and small commercial craft | Staying compliant without a dedicated technical department, in small organisations with little shore staff |
CMMS, the ISM Code and class surveys
This is often what settles the budget question. The ISM Code requires the Company to establish procedures ensuring that the ship and its equipment are maintained in conformity with applicable rules, to carry out inspections at appropriate intervals, to report and address non-conformities, and to keep the corresponding records. Particular attention is given to equipment whose sudden failure may result in a hazardous situation: such items require specific measures, regular testing or redundancy.
In practice, the auditor does not simply confirm that maintenance was carried out. They check that the system triggering it exists, that it is genuinely applied, that deviations are recorded and that corrective actions are documented. A well-kept maritime CMMS answers those four questions in minutes, where a paper system demands a laborious reconstruction. For more, read what the ISM Code is and how it applies.
The same logic applies to classification. The class society controls periodicities — annual, intermediate and renewal surveys, drydocking — and, under an approved planned maintenance scheme, may rely on CMMS records to credit certain machinery inspections. A structured history, with running hours and intervention reports, shortens the survey and reduces the risk of a condition of class. The digital engine room logbook plays a central role here.
Key takeaway: a maritime CMMS is not only about maintaining a ship, it is about proving that the ship is maintained. In an ISM audit or a class survey, the quality of the evidence weighs as much as the quality of the work.
Implementing a maritime CMMS: five steps
A failed rollout costs more than having no tool at all, because it burns budget and crew confidence. The method that works has five steps.
Step 1 — Audit what exists
List what is genuinely in use: engine room records, spreadsheets, ISM procedures, spares lists, certificates, maker's contracts. Identify pilot vessels, ship and shore champions, and define what you want to achieve. A project without a measurable objective always drifts.
Step 2 — Define your coding scheme before importing
The most neglected and most decisive step. Define one coding scheme for the whole fleet: hierarchy structure, equipment nomenclature, parts families, criticality levels. Sister vessels must share the same structure, otherwise fleet consolidation is impossible. Three criticality levels are almost always enough.
Step 3 — Migrate the data
Start with the essentials: critical equipment, statutory and maker's plans, critical spares, valid certificates. Do not attempt to recover ten years of history — take current counter readings and the last intervention per equipment item. Over-ambitious migration is the number one cause of delay.
Step 4 — Train and engage the crews
Train on board, not only by video call, and train reliefs as well as permanent crew. Short training focused on daily actions (closing a work order, entering a counter reading, requesting a part) beats an exhaustive day forgotten in two weeks. Appoint a champion on each vessel: the single biggest success factor.
Step 5 — Go live and manage adoption
The first three months decide adoption. Track simple weekly indicators: work orders closed on time, counter readings entered, purchase requests raised from the CMMS. Correct oversized plans quickly — an unrealistic plan generates permanent backlog and demotivates the crew. Our implementation checklist details each milestone.
Common mistakes to avoid
- Doing everything at once: ten vessels in parallel with full history guarantees a stall. Start with two pilot vessels.
- Copying the maker's plan without arbitration: adding up every recommendation produces an unmanageable task volume that is never met.
- Neglecting the coding scheme: renaming equipment afterwards costs ten times more than naming it correctly at the start.
- Choosing a tool without offline mode: usage collapses on the first passage without connectivity.
- Leaving stock out of scope: without a maintenance-stock link, emergency purchasing continues and the main saving disappears.
- Not managing adoption after go-live: an unmonitored CMMS reverts to a spreadsheet within six months.
We detail these in the five mistakes to avoid when implementing your CMMS.
Calculating the return on investment
The ROI of a maritime CMMS is built on four items: administrative time saved, reduced emergency purchasing, optimised stock value and avoided downtime. Here is a deliberately conservative example, to be adapted to your own figures.
Assumption: a port services operator running 6 craft, on a licence at EUR 100 per vessel per month (Premium plan), i.e. EUR 7,200 per year, plus around EUR 4,000 of setup in year one — EUR 11,200 for the first year.
| Source of gain | Assumption used | Annual gain |
|---|---|---|
| Administrative time | 3 hours per week per vessel saved on searching for documents, double entry and report preparation; over 46 weeks and 6 vessels, roughly 830 hours, of which only half is counted, at EUR 45 per loaded hour | approx. EUR 18,000 |
| Emergency purchasing | On an annual EUR 25,000 of unplanned buying (express freight, surcharges, forwarders), a one-third reduction through minimum levels and anticipation | approx. EUR 8,000 |
| Stock value | On EUR 120,000 held in store, a 10% reduction from removing duplicates and pooling across sister craft. One-off cash released, not a recurring annual gain — excluded from the total below | EUR 12,000 (one-off) |
| Downtime avoided | A single major breakdown prevented across the fleet, one day out of service at EUR 3,500 | approx. EUR 3,500 |
| Total | Recurring items only (administrative time, emergency purchasing, downtime avoided); excludes the one-off stock release | approx. EUR 29,500 per year |
On that basis the conservative recurring gain is around EUR 29,500 per year against EUR 11,200 in year one and EUR 7,200 thereafter: payback in four to five months. Even halving every assumption, the equation stays clearly positive — and the biggest item, reduced regulatory risk, has not been valued at all. Our tips to reduce vessel maintenance costs complement this calculation, and the pricing page lets you rerun it for your own fleet.
How to choose a maritime CMMS
| Criterion | The question to ask the vendor |
|---|---|
| 1. Genuine offline mode | Can you demonstrate the software with the network switched off, and can a work order be closed without connectivity? If not, rule the solution out. |
| 2. Mobile usability in real conditions | Does data entry remain possible in the engine room, on a phone? |
| 3. Native regulatory coverage | Do certificates, ISM, MARPOL and FAL Form 6 exist natively, rather than being improvised in free-text fields? |
| 4. Maintenance–stock–purchasing coupling | Are maintenance, stock and purchasing genuinely coupled, or is the maintenance module standalone? This is where most of the ROI sits, and a standalone module plateaus quickly. |
| 5. Fleet consolidation | Can sister vessels be compared on the same reference data? |
| 6. Data migration support | What support do you provide for data migration? This is often what separates a delivered project from an abandoned one. |
| 7. The vendor's sea experience | Have your teams sailed — do you know why readings are taken at the end of a watch? That is the Smart Sailors story. |
Our dedicated article sets out 10 criteria for choosing CMMS software, and we explain elsewhere why a maritime CMMS beats a generic tool.
FAQ
What is the difference between a CMMS and a PMS?
The PMS (Planned Maintenance System) is the set of planned maintenance tasks required under the ISM Code. The CMMS is the software that carries that PMS and adds work orders, stock, purchasing, certificates and history. In practice, a modern maritime CMMS includes the PMS.
Does a maritime CMMS work without an internet connection?
It must. The Smart Sailors mobile app lets crews consult job cards, enter counter readings, close work orders and photograph defects offline, then synchronise as soon as the link returns. This is a knock-out criterion when selecting a tool.
How long does implementation take?
For a first vessel with focused data migration, expect four to eight weeks between kick-off and stable daily use. Subsequent vessels roll out far faster once the fleet coding scheme is fixed.
Is a small fleet of two or three vessels worth equipping?
Yes, often more so than a large fleet, because small operators have no shore technical department to absorb oversights. Plans starting at EUR 10 per vessel per month make the investment marginal against a single breakdown avoided.
Does a CMMS replace the engine room logbook?
It complements it and, depending on the Flag State, can carry its digital version. Running hours, consumption and interventions recorded in the CMMS feed a coherent log that stands up in audit. See our complete guide to the ship's logbook.
Can we migrate from spreadsheets without losing everything?
Yes. Existing spreadsheets are the import base for equipment, plans and stock. The key is to clean and code the data before importing, rather than reproducing spreadsheet disorder inside the CMMS.
Conclusion
A maritime CMMS is not one more piece of software: it is the foundation linking real maintenance, cost control and regulatory compliance. Implemented well, it turns reactive maintenance into managed maintenance, secures ISM audits and class surveys, and gives the owner visibility no spreadsheet can provide. Implemented badly, it becomes a burden — the difference lies in the coding scheme, the training and how the first three months are managed.
Smart Sailors has been developed in Marseille since 2017 by seafarers and now equips more than 400 vessels. Request a demonstration tailored to your fleet, or start a 30-day free trial from the home page to test the software on a pilot vessel. Our team supports you through data migration and coding — the two steps that decide success. More resources are available on our blog.
.png){kind=small}
