Expedition, NGO and research vessels

An oceanographic winch bearing that fails alongside means a purchase order, a technician and two days of waiting. The same bearing failing 2,000 miles from the nearest supplier, three days into a six-week Southern Ocean leg, means the end of sampling stations for the entire campaign — and a twelve-month wait before the weather window opens again. Research vessels, polar expedition yachts, NGO units on rescue or ocean protection missions: these fleets share a constraint that neither fishing nor commercial shipping knows to the same degree, complete autonomy for weeks or months at a time. That is exactly what a CMMS for expedition and research vessels has to organise: the maintenance, the spares and the data all sail with the ship, because nothing will come from shore for a long while.

On these vessels there is no express delivery, no technical port call to catch up in, no maker's technician waiting on the quay. The sea adds its own conditions: polar waters with no network coverage, crews that rotate every leg, embarked scientific equipment the ship's engineers did not choose and do not always know, and funders — research institutes, public agencies, private donors — who expect irreproachable traceability for every euro or dollar spent.

This guide sets out the full method: putting real figures on what a failure costs mid-mission, sizing spares and fluids before departure, running the planned maintenance system without a network, keeping continuity through crew rotations, and turning the maintenance history into the backbone of end-of-campaign reporting.

A failure on mission costs far more than a repair

On a merchant ship, a breakdown is measured in delay and penalties. On a research or expedition vessel, it is measured in mission lost — and a mission is almost never recovered.

• Science time: sea time on a research vessel runs to thousands, sometimes tens of thousands of euros or dollars a day, and instrument slots are shared between laboratories years in advance. A CTD winch or dynamic positioning failure during a station is science that will not be done again.
• The weather window: in polar waters or the Roaring Forties, access to a study area lasts a few weeks a year. An engine unavailable at the wrong moment postpones the campaign by a year, not by a week.
• The humanitarian mission: for a search-and-rescue NGO, a vessel alongside for repairs is a search area left empty, an entire mission interrupted, and donors who will expect an explanation.
• Rescue logistics: getting a part to Ushuaia, Nouméa or Réunion often costs more than the part itself — when it is possible at all within the length of the port call.

The economics are therefore quite different from a conventional owner's. Preventive maintenance stops being a cost line to optimise and becomes the mission's insurance policy, which is the ground on which its budget should be defended, before management and board of trustees alike.

How does a CMMS for expedition vessels differ from a conventional one?

A CMMS for expedition and research vessels stands apart on four points: it works entirely offline for weeks at a time, it sizes spares by failure scenario rather than by supplier lead time, it schedules maintenance on running hours and the campaign calendar rather than fixed dates, and it produces exportable traceability for funders. Ship maintenance software designed for coastal trades, where a weekly port call catches everything, cannot hold all four requirements at once.

In practice, this shows in the configuration:

• Planning horizon: the whole campaign, not the week. Every job that would fall due at sea is either brought forward before departure or documented as feasible on board.
• Mission-driven criticality: the scientific winch, the stern A-frame, the watermaker or the davit that launches an NGO's rescue boats rank alongside the main engine in the criticality analysis, because their loss stops the mission even if the ship can still sail.
• "Guest" equipment: laboratory containers, instruments belonging to embarked science parties, an NGO's medical equipment — the CMMS must accommodate temporary assets with their own job plans.
• Two readings of cost: by equipment for the technical team, by campaign or mission for management and funders.

The general method — inventory, criticality, plans, indicators — remains that of any maritime CMMS; our complete maritime CMMS guide walks through it step by step. What follows is its adaptation to long missions.

Prepare the stock, not the regrets

Preparing a long campaign is above all an inventory exercise: which critical spares to embark, in what quantity, for which failure scenarios. Ashore, you reason in resupply lead time; on mission, the lead time is infinite until the next port call. The question therefore becomes: which failures must we be able to repair ourselves, twice in a row?

The approach takes three steps:

• Start from criticality, not from the catalogue: for every item whose loss stops the mission or threatens safety, list the failure modes repairable on board and the parts they consume.
• Build on real history: a per-vessel inventory with alert thresholds, fed by consumption from previous campaigns, replaces the chief engineer's intuition with data. The impellers, belts, filter cartridges and anodes consumed last year are the best forecast for next year.
• Duplicate what cannot be replaced: for parts unobtainable in a remote port — winch electronics, the watermaker's specific pump — the only strategy is embarked redundancy, decided and budgeted before departure.

Two of our articles detail this mechanism: building the loadout list for a long voyage, and the method of thinking spares in port calls rather than days. The common principle: every part issued is logged on the work order at the moment of the job, otherwise the inventory is lying by week three — and the next campaign will be prepared on that lying inventory.

Fluids and endurance: confirm before departure, watch during

The same logic applies to fluids. Tank and consumption tracking per sea day answers two distinct questions.

Before departure: real endurance

The vessel's theoretical endurance is worth nothing; only the endurance measured on past campaigns, under comparable operating conditions, counts. Fuel for propulsion and generators, engine and hydraulic oils, fresh water if the watermaker fails: each fluid is projected over the length of the leg, with the safety margin the area demands — in polar waters, the diversion to the nearest port of refuge is measured in weeks, and that reserve is not negotiable.

During the campaign: drift as a symptom

A consumption drifting 8 to 10 % from the baseline, under comparable conditions, almost always announces something: hull fouling, a tired injector, a clogged heat exchanger. Reading soundings and meters every sea day turns the tank into a condition-monitoring instrument — our article on vessel fuel consumption monitoring covers methods and KPIs. Add oil samples shipped to the laboratory at every port call: on engines that run for months without an external visit, oil analysis is the only medical examination available, and its long detection interval is exactly what a fleet that cannot stop needs.

Working without a network, by design

South of the fiftieth parallel there is no mobile coverage, and the satellite link — where one exists — is reserved for operations and safety. A CMMS that assumes a permanent connection is disqualified from the start: this is not a "degraded mode" to be tolerated for a few hours, it is the normal operating mode for weeks on end.

Offline operation has to be native: the mobile application carries the vessel's entire dataset — maintenance plan, job plans, history, stock — and the ship logs jobs, meters, soundings and parts issues throughout the campaign. A synchronisation queue transmits everything at the first port, or over the satellite link when it opens. Three practical consequences:

• The ship works normally: the work order is closed on a phone, in the engine room, at the moment of the job — no evening re-typing, no intermediate notebook lost at crew change.
• The office keeps visibility: at every synchronisation, the operator sees the real state of the fleet, the backlog and the consumptions, and prepares the next resupply while the ship is still at sea.
• Nothing is lost: every entry is timestamped on board; the chronology of the history stays exact even if synchronisation waits six weeks.

A maintenance plan set to the campaign, not the calendar

A conventional plan alternates calendar-based and running-hours-based jobs. On a long mission a third constraint appears: the execution window. An oil change falling due mid-leg is no problem; a shaft line bearing replacement is.

The method is to project every counter over the length of the campaign before departure: running-hours tracking shows which jobs will fall due at sea. Each is then handled in one of three ways: brought forward (done in port before sailing, even at the cost of a few hours of remaining potential), confirmed as feasible on board (spares embarked, job plan available, tooling checked), or knowingly deferred with the chief engineer's agreement and, where relevant, the classification society's. The hours-based maintenance schedule of a marine diesel engine lends itself well to this projection, and the 4-step planned maintenance method provides the general framework.

Do not forget scientific and mission equipment: winches and their wire (with metres-deployed tracking), A-frames and gantries, dive compressors, an NGO's fast rescue boats, the sample cold chain. They belong in the same plan, with their own counters — winching hours, launch cycles — because it is their failure, far more than the mother ship's, that stops the mission.

Rotating crews and volunteers: the job plan carries the continuity

These fleets have a crewing particularity: on an NGO vessel, part of the crew is volunteer and changes every rotation; on a research vessel, the embarked teams change every leg. The chief engineer who knows "his" watermaker by heart signs off one day, and his knowledge goes down the gangway with him — unless that knowledge is written down.

That is the role of the maintenance job plan: every recurring job documented step by step, with safety notes, tooling, parts, photographs and setting values, attached to the equipment in the CMMS. The newcomer works to the standard from the first week, and the quality of the work stops depending on who happens to be on board. QR code asset tagging completes the arrangement: scanning the pump displays its history, its job plan and its spares — invaluable when a crew member is competent but new to the ship.

Accounting to those who fund the work

Research institutes, public agencies, foundations, private donors: the funders of these fleets expect irreproachable traceability in the use of their money. And an end-of-campaign audit is prepared during the campaign, not after it.

• Timestamped history: every job dated, signed and attached to an item of equipment, with parts and hours — the raw material of any activity report.
• Costs by equipment and by campaign: showing what the winch's maintenance cost over the campaign, or defending a renewal budget before a board of trustees, becomes an extraction rather than a reconstruction.
• Exportable reports: the file handed to the funder comes out of the CMMS at the end of the campaign, instead of consuming a week of spreadsheet archaeology.
• Proof of upkeep: for the insurer, as for the vessel's future buyer, a complete history is also a residual-value argument.

The same documentary base serves regulatory compliance. Units subject to the ISM Code find in it their evidence of planned maintenance (chapter 10); the others — expedition yachts, smaller NGO units — are well advised to adopt it voluntarily, because a Port State Control inspection or an insurance survey makes no distinction of status, and vessels operating in polar waters add the requirements of the IMO Polar Code according to their certification.

Campaign preparation as a checklist

Here is the framework we see among the best-prepared operators. The milestones scale with the length of the mission; the logic stays the same.

The return deserves the same discipline: a debrief of every failure, forecast versus actual consumption, stock thresholds and job plans updated. That closing of the loop is what makes each campaign prepare the next one better.

Key takeaways

For a research, expedition or NGO vessel, maintenance is not a cost line: it is the condition of the mission's existence. Two thousand miles from the nearest supplier, everything that was not anticipated — a part, a fluid, a skill, a job plan — will be missing at the precise moment it can no longer be obtained. The method comes down to a few disciplines: size the spares by failure scenario from real history, confirm fluid endurance before departure and watch for drift during the campaign, project every maintenance due date over the mission, write the job plans so they survive crew rotations, and keep a history that serves funders as well as auditors.

You still need a tool that holds these constraints, starting with weeks without a network. That is what a maritime CMMS like Smart Sailors is built for: a mobile application that works entirely offline and synchronises when the network returns, per-vessel stock with alert thresholds, tank and counter tracking, documented job plans and exportable reports for your funders. Designed in Marseille by seafarers, it is deployed on more than 700 vessels, from research units to service fleets — our page on service, research and expedition vessels summarises the approach. If your next campaign is already in preparation, the time to talk is now, not on return: a free 30-day trial, and our pricing is public.