Running Hours vs Calendar-Based Maintenance: Setting Up Your PMS Intervals

Every maintenance task in a PMS has a trigger — the condition that makes it come due. There are only two types: running hours and calendar intervals. That sounds simple, but the number of databases we see where these are set up incorrectly is remarkable.

Getting your intervals right is not a minor detail. It determines whether your maintenance programme actually prevents failures or just generates paperwork. An engine that gets serviced on a calendar schedule regardless of running hours is either being over-maintained or under-maintained. Safety equipment serviced on a running-hours basis makes no sense at all — a liferaft does not care how many hours the engines ran.

This article breaks down the two trigger types, when to use each, how to handle the tricky "whichever comes first" dual triggers, and the equipment-specific guidance that should inform your PMS setup.

Running hours: for equipment that wears with use

Running-hours-based maintenance applies to equipment where wear is directly proportional to operation time. The more hours it runs, the more it wears. The more it wears, the sooner it needs servicing.

This is the correct primary trigger for:

• -Main engines — oil changes, filter replacements, valve adjustments, injector servicing, turbocharger inspections. Every major engine manufacturer specifies intervals in running hours.
• -Generators — same principle as main engines. Generator sets have their own hour meters and their own maintenance schedules independent of the main engines.
• -Compressors — air compressors, refrigeration compressors, AC compressors. These have defined running hour intervals for oil changes, valve inspections, and filter replacements.
• -Hydraulic systems — hydraulic power packs, thrusters, stabiliser pumps. Oil quality degrades with use, and mechanical components wear proportionally to operation time.
• -Watermakers — the high-pressure pumps, energy recovery devices, and membrane flush systems all have running-hour-based intervals.

The key requirement for running-hours maintenance is an hour meter. Without one, you are guessing — and guessing is how engines get run thousands of hours past their service intervals.

How hour meters work in practice

Most marine engines and generators have built-in hour meters. These tick over whenever the engine is running, regardless of load. Some newer installations also track load hours separately, which is useful but not a replacement for total running hours.

For equipment without built-in meters, aftermarket hour counters can be fitted. A simple vibration-activated counter costs very little and attaches to any running machinery. There is no reason to have equipment on running-hours maintenance without a way to track those hours.

The hour reading needs to be recorded somewhere accessible — either automatically through a connected PMS system, or manually through daily logbook entries that get transferred to the PMS. The accuracy of your entire running-hours maintenance programme depends on this.

If the hour meters are not being read and recorded consistently, it does not matter how well the intervals are set up in the database. The PMS cannot trigger a task if it does not know the current reading.

Calendar intervals: for equipment that degrades with time

Calendar-based maintenance applies to equipment where degradation is driven by time, environment, or regulation — not by use.

This is the correct primary trigger for:

• -Safety equipment — liferafts, EPIRBs, fire extinguishers, pyrotechnics, breathing apparatus, immersion suits. These have strict regulatory servicing intervals (annual, biennial, or based on expiry dates) that are completely unrelated to vessel operation.
• -Coatings and anodes — hull coatings, antifoul, sacrificial anodes. These degrade with time in the water, not with engine hours.
• -Rubber goods and hoses — expansion joints, flexible hose connections, rubber bellows. Rubber degrades with age regardless of whether the system is running.
• -Batteries — bank testing, electrolyte checks, terminal servicing. Batteries degrade with time and charge cycles, not equipment running hours.
• -Seasonal systems — equipment that operates seasonally (heating systems on vessels that spend summers in the Med and winters in the Caribbean) needs pre-season commissioning and post-season layup on a calendar basis.
• -Certification-driven items — anything that has a certificate with an expiry date: lifting equipment, pressure vessels, gas systems, anchoring equipment load tests.

Calendar intervals do not need hour meters. They need a clear date reference — either the date of last service or the date of next service. The PMS tracks elapsed time and triggers the task when the interval expires.

Why calendar intervals exist for mechanical equipment too

Even equipment that is primarily maintained on running hours will have some calendar-based tasks. Oil does not last forever even if the engine is not running. Coolant inhibitors break down with age. Fuel sitting in tanks degrades. Seals dry out.

This is where the dual-trigger system comes in, and it is where most databases get it wrong.

Dual triggers: "whichever comes first"

Open almost any engine manufacturer's maintenance manual and you will see this format:

Replace engine oil: every 500 running hours or every 12 months, whichever comes first
Replace coolant: every 6,000 running hours or every 24 months, whichever comes first
Replace fuel filters: every 250 running hours or every 6 months, whichever comes first

The "whichever comes first" clause exists because equipment that sits idle still degrades. An engine that runs 200 hours in a year still needs its oil changed annually — the oil has been sitting in the sump oxidising, absorbing moisture, and losing its protective properties, even if the engine barely ran.

This is one of the most commonly botched setups in PMS databases. Here is what goes wrong and how to handle it.

The wrong approach: pick one and ignore the other

The most common mistake is entering only the calendar interval and ignoring the running hours, or vice versa. Someone decides "we will just do it every 6 months" and enters a 6-month calendar task. This means a vessel that runs its engines heavily during a busy charter season — accumulating 500 hours in three months — will not trigger a service until the 6-month mark. That engine is now 250 hours overdue.

The opposite mistake is just as bad. Enter only the running-hours interval, and a vessel that sits in port for extended periods will never trigger a service. The oil degrades, the coolant breaks down, seals dry out — and the PMS shows nothing due because the hours have not ticked over.

The correct approach: two triggers, one task

The ideal setup is a single maintenance task with both triggers active — the task comes due when either condition is met first. Some PMS platforms support this natively with dual-trigger fields. You enter the running-hours interval and the calendar interval, and the system monitors both.

If your PMS platform does not support dual triggers directly, the workaround is to create the primary trigger as the main task interval and set a separate calendar reminder as a backstop. For example, the fuel filter replacement gets set to 250 running hours as the primary interval, with a 6-month calendar check that prompts the engineer to verify whether the running-hours task has already been done.

This is not perfect, but it is better than ignoring one trigger entirely.

How to decide which trigger is primary

For most machinery, the running-hours trigger is primary — it will be reached first on a vessel with normal operational patterns. The calendar trigger is the backstop for idle periods.

The exception is vessels that operate infrequently. A yacht that sits in port for nine months and does a two-week Mediterranean trip each summer will hit calendar triggers long before running-hours triggers on most equipment. For these vessels, the calendar interval effectively becomes the primary driver.

Know your vessel's operational pattern. A busy charter yacht running 1,500 engine hours per year has a very different trigger profile from a private yacht running 200 hours per year. The same equipment, the same OEM manual, but the trigger that fires first will be different.

Equipment-specific guidance

Here is how the trigger types apply across the major equipment categories on a typical superyacht. This is not a substitute for reading your own OEM manuals — it is a framework for understanding the pattern.

Main engines

Primary trigger: running hours.

Main engine maintenance is driven almost entirely by running hours. Oil and filter changes, valve adjustments, injector servicing, turbocharger inspections, belt replacements — all specified in running hours by the manufacturer.

Calendar backstops apply for oil changes (typically 12 months maximum even if hours are not reached), coolant changes (24 months is common), and fuel system components.

Major overhauls (top-end, bottom-end) are specified at high running-hour thresholds — 8,000, 12,000, 20,000 hours depending on the engine. These are the tasks that separate a well-tracked engine from one with an uncertain maintenance history.

Generators

Primary trigger: running hours, but standby time matters.

Generator maintenance follows the same running-hours logic as main engines. However, generators often spend significant time on standby — not running, but ready to start at any moment. Standby time does not register on the hour meter, but it does affect certain components.

Start batteries, fuel priming systems, and control electronics are all affected by standby time rather than running time. These items need calendar-based maintenance in addition to the running-hours schedule for the generator engine itself.

Also consider that on many yachts, generators do not accumulate hours evenly. One generator may run as the primary unit and accumulate twice the hours of the standby unit. Your PMS needs to track each generator independently — not on a shared interval.

Watermakers

Primary trigger: running hours for mechanical components, calendar for membranes.

The high-pressure pumps, boost pumps, and energy recovery devices are maintained on running hours. Membrane replacement, however, is driven by a combination of running hours, age, and water quality — and the age factor means a calendar element is always present.

Membrane manufacturers typically specify a maximum age regardless of production hours. A membrane that has been installed for three years but only run for 500 hours may still need replacing based on age alone. This is a genuine dual-trigger scenario.

Preservation chemicals for membranes during storage are strictly calendar-based — typically every 30 days when the watermaker is laid up.

HVAC systems

Primary trigger: calendar, supplemented by seasonal use patterns.

HVAC maintenance is predominantly calendar-based because the systems run near-continuously during operational periods. Filter changes, coil cleaning, refrigerant checks, and condenser maintenance are all typically specified on calendar intervals — monthly, quarterly, or annually.

The complication is seasonal operation. A yacht that operates in the Caribbean in winter and the Mediterranean in summer uses its HVAC differently in each location. Cooling-dominant operation puts different demands on the system than heating or mild-weather operation.

Pre-season commissioning and post-season layup tasks are calendar-anchored to the vessel's operational pattern, not to fixed dates.

Safety equipment

Primary trigger: strict calendar intervals per regulation.

This is the one category where there is zero flexibility on trigger type. Safety equipment servicing intervals are set by regulation — class rules, flag state requirements, and SOLAS/LSA Code provisions. They are calendar-based, period.

Liferaft servicing: annual. EPIRB battery replacement: per manufacturer specification (typically every 5 years). Fire extinguisher servicing: annual inspection, pressure test at defined intervals. Pyrotechnic expiry: fixed date. Breathing apparatus: annual inspection and testing.

These dates are non-negotiable. The PMS must track them accurately, and the tasks must be completed on time regardless of vessel operational status. A yacht sitting in a yard for three months still needs its annual liferaft service done on schedule.

We have written separately about building [equipment hierarchies](/blog/how-to-structure-pms-equipment-hierarchy-superyacht) that keep safety equipment properly organised within the database — getting the hierarchy right makes it much harder for these time-critical items to slip through the cracks.

Deck machinery

Primary trigger: calendar, with low running hours.

Windlasses, capstans, cranes, and davits typically accumulate very low running hours relative to their calendar age. A windlass might run for a total of 20 hours in a year. Running-hours-based maintenance on deck machinery would result in services being years apart — far too long.

Calendar intervals make more sense here. Wire rope inspections, grease changes, brake pad checks, hydraulic oil sampling — all on 3-month, 6-month, or annual cycles.

Load testing of lifting equipment is strictly calendar-based per certification requirements — typically every 5 years, or as specified by the class society.

Common mistakes to watch for

Using only calendar intervals for everything

This is the "one size fits all" approach, and it is the most common mistake we see. Someone sets every task in the database to a calendar interval — monthly, quarterly, six-monthly, annual — because it is simpler to manage.

The problem is obvious: a vessel running 2,000 engine hours per year will blow past every running-hours-based service interval well before the calendar trigger fires. The engine needs an oil change at 500 hours, which it reaches in three months — but the calendar task is set to 6 months. The engine runs 500 hours overdue before the PMS says anything.

Not accounting for idle periods

The opposite mistake. A vessel sits in a Mediterranean port for four months over winter with minimal engine operation. The running-hours-based tasks never come due because the hours are not ticking. Meanwhile, oil is degrading, coolant inhibitors are depleting, seals are drying out, and fuel is oxidising.

Calendar backstops exist specifically for this scenario. If your PMS only tracks running hours, idle periods create invisible maintenance gaps.

Setting intervals from guesswork

We see this more often than you might expect — intervals set to round numbers because someone thought "every 500 hours sounds about right" without checking the manual. The OEM specifies 250 hours for that filter? Somebody decided 500 was fine. The manufacturer says check the belts every 1,000 hours? Rounded up to 2,000 because they "seemed fine."

Every interval should be traceable to a specific page in a specific manufacturer manual. This is not about being pedantic — it is about liability, warranty coverage, and actually preventing failures. Read more about this in our article on [what makes a good PMS database](/blog/what-makes-good-pms-database-superyacht).

Setting it up properly in your database

When we build a database, the interval setup follows a specific process:

1. Extract the manufacturer's stated interval — exactly as written in the OEM manual. Hours-based, calendar-based, or both. 2. Enter both triggers where "whichever comes first" applies — either as a dual-trigger task (if the platform supports it) or as parallel tasks with cross-references. 3. Note the source — every interval should reference the manual, section, and page it came from. When the next engineer questions why a task is set to 250 hours instead of 500, the answer is traceable. 4. Confirm the vessel's operational pattern — understand whether the vessel is high-utilisation (charter yacht) or low-utilisation (private, occasional use). This does not change the intervals, but it indicates which trigger type will typically fire first. 5. Set up hour-meter recording — ensure there is a process for regular hour-meter readings to be entered into the PMS. Without current readings, running-hours triggers are meaningless.

This is part of our standard [build process](/process). The interval setup happens after the equipment hierarchy is locked and before the database goes to the crew for review — because the crew are the best people to confirm whether the operational assumptions match reality.

The practical takeaway

Running hours and calendar intervals are not interchangeable. They measure different things, and using the wrong one for a given piece of equipment will result in either missed maintenance or unnecessary maintenance. Neither outcome is acceptable.

For machinery that runs: track hours, set intervals from the OEM manual, add calendar backstops.

For equipment that ages: use calendar intervals, driven by regulation or manufacturer guidance.

For the grey area in between: use both triggers, and make sure your PMS — or your process — catches whichever one fires first.

If you are looking at your current database and realising the intervals might not be set up correctly, it is worth a review. The fix is usually straightforward — but the consequences of getting it wrong compound with every missed or mistimed service. Take a look at our [services](/services) to understand how we approach database builds, or read about the [real cost of getting this wrong](/blog/pms-database-cost-superyacht) when it comes time for a survey.