Scheduling Best Practices

Planned Maintenance Schedules are the backbone of YMS, they're what turns a static equipment list into a proactive maintenance program that generates the right task, for the right person, at the right time. Getting a schedule's setup right from the outset keeps your tasks list clean, organised and helps prevent missed maintenance.

Before setting up schedules, it's worth knowing which of the four Scheduling sub-modules fits the work:

• Equipment Scheduling — recurring maintenance tied to a specific piece of equipment, on a time interval, an hours interval, or both.

• Event Scheduling — recurring tasks that aren't tied to a piece of equipment, like weekly chart corrections or monthly cabin inspections.

• Drill Scheduling — drill frequency and requirements, aligned to flag, state, or company standards.

• Inspection Scheduling — routine safety and operational checks (e.g. bilge alarm tests, fire extinguisher checks), with the Checklist feature (see below) available to group repetitive checks under one task.

This article covers how to think about configuring schedules well. For the click-by-click steps, see the individual How to Guides linked throughout.

Matching the Schedule Pattern to the Work

Every schedule runs on an Hours-based pattern, a Date-based pattern, or both — see the Schedule Patterns guide for the full mechanics. Choosing the right one (and the right options within it) matters more than it looks:

• Use Hours-based patterns for wear-driven maintenance. If a task is really governed by how much the equipment has run — an oil change every 250 hours — an Hours-based pattern tracks the actual wear instead of an arbitrary calendar date. Only available on equipment that monitors running hours (see Monitoring Hours).

• Lock hours for manufacturer/warranty-mandated intervals, unlock them for everything else. A Locked interval always lands on the same multiple (250, 500, 750...) regardless of when you actually did the work — use this when a strict interval matters, such as warranty-required servicing. An Unlocked interval recalculates from the hours at completion, which is more forgiving if a task regularly runs a little early or late and you don't want the gap to compound.

• Use Advanced Date patterns for anything compliance-driven, Simple patterns for everything else. An Advanced pattern (e.g. "Day 1 of every 1 month(s)") always lands on the same calendar date no matter when the task was actually completed — this is what prevents "schedule creep" on things like monthly fire extinguisher checks. A Simple pattern resets from the completion date instead, which is the better choice for flexible, operationally-driven tasks (e.g. "deep clean the forepeak every 6 months") where rigid dates would just create friction against actual vessel operations.

• Combine Hours and Date patterns when either condition should trigger the work. Whichever limit is hit first pushes the task onto the task list; both portions of the schedule update together on completion. Useful for maintenance specified as "every 500 hours or 12 months, whichever comes first."

• Set a Remind Me buffer on anything that needs lead time to plan for — spares to source, a contractor to book, a window in the vessel's operational schedule. Remind Me pushes the task onto the task list ahead of the actual due point without changing when it's officially due.

• Use iteration limits for maintenance that's only ever supposed to happen a fixed number of times, like manufacturer-recommended break-in servicing. Once the count reaches zero, the schedule stops generating tasks on its own — nobody has to remember to go delete it.

Copying vs. Linking Across Sister Equipment

When you have multiple pieces of equipment that share a maintenance schedule — say, three identical generators — you rarely want to build the same schedule three times by hand. Copying and Linking both save you that work, but they solve different problems:

• Copy when the schedules should be able to drift apart over time. A copy is a fully independent schedule from the moment it's created — editing one has no effect on the others. Use this for equipment that's similar but not identical in how it's used or serviced (e.g. a primary generator that runs far more hours than the backup).

• Link when the schedules must always stay in sync. A linked schedule is the same schedule reflected across every piece of equipment it's linked to — editing one immediately updates all of them, and each carries a link icon so it's obvious at a glance. Use this for genuinely identical equipment you always want serviced under the same rule (e.g. all three generators should always be serviced every 500 hours, no exceptions).

• Unlink when one piece of equipment needs to become the exception. Unlinking breaks the connection while keeping the schedule's history and related data intact, so you can hand-tune it from there without disturbing the others it used to share a schedule with.

Getting Ahead of a Due Date: Trigger vs. Log & Reset

Both Trigger and Log & Reset let you act on a schedule before it's naturally due — the difference is whether the work still needs to happen, or already has:

• Trigger when the work still needs to be done, just earlier than scheduled — for example, getting ahead of maintenance before a long passage or a guest trip. Triggering pushes the task onto the task list now, and it's completed the normal way once the work is done.

• Log & Reset when the work has already been completed off the back of the normal schedule — you don't need a task on anyone's list, you just need YMS to record that it happened and reset the next-due point accordingly, without a detour through the Tasks module.

Managing the Schedule Lifecycle: Suspend & Activate

Not every schedule should be generating tasks all the time. Suspending and activating schedules — individually or in bulk — keeps the task list relevant to what's actually happening on board:

• New builds — enter every schedule during the build phase, but keep them suspended until handover, so the task list doesn't fill up with maintenance for a vessel that isn't operating yet.

• Dry dock — suspend whatever maintenance genuinely can't be performed while the vessel is out of the water, rather than letting those tasks pile up as overdue.

• Equipment breakdown — suspend planned maintenance for anything awaiting major repair, so it stops generating tasks for work that can't happen until the equipment is running again.

Structuring Inspection Checklists

Checklists group repetitive safety checks — fire extinguisher inspections, bilge alarm tests — under a single Inspection Schedule, rather than creating a separate schedule per item.

• Keep checklists for safety verification, not maintenance work. They're built for confirming something is in the expected state or passes a functionality test, not for logging repair or servicing work.

• Write the first check generically if you're going to copy it. When building a repetitive checklist (e.g. every fire extinguisher onboard), write the title and description in a way that applies accurately to all of them before copying it out — the copy carries that text verbatim to every piece of equipment you apply it to.

• Order each checklist to match the physical route a crew member will actually walk, not the order equipment happens to appear in a list. A checklist ordered by the shortest logical route around the vessel gets completed faster and more reliably than one ordered arbitrarily.

• Split a checklist by area when it grows unwieldy — for example, breaking one vessel-wide fire extinguisher checklist into one per deck, so checks can be staggered through the month instead of done all at once.

Final Notes

A well-configured schedule setup:

• Keeps the task list a reliable reflection of what actually needs doing, not noise to filter through

• Prevents both missed maintenance and duplicate/redundant tasks across sister equipment

• Makes compliance-driven work (drills, safety checks, warranty servicing) easy to demonstrate during an audit

• Scales cleanly as equipment is added, retired, or moved between departments

Time spent choosing the right pattern, pays for itself every time the schedule runs.