A task schedule is the rule behind planned maintenance: it says what the job is, and how often it needs doing. Schedules live on the PMS tab of a component, and every maintenance schedule belongs to exactly one component.
The schedules table
The PMS tab lists the component's schedules with columns for Name, Recurrence (Recurring or One-time), Priority, Time Schedule, Hours Schedule and Actions, plus a Columns control for hiding columns.
The two schedule columns also show how close the job is: the time column counts down days left or reports days overdue, and the hours column counts down hrs left or reports hrs overdue against the component's current reading. On a component that does not track running hours the Hours Schedule column is left out — unless hours-based schedules were created before hours tracking was switched off, in which case it stays so those schedules remain visible.
Row actions are View, Edit, Generate Task and Delete. Edit and Generate Task need permission to edit maintenance tasks, and Delete needs permission to delete them (on an archived component, only View is available). Generate Task opens a Perform Scheduled Task dialog pre-filled from the schedule, so a task can be raised without waiting for the schedule to come due — useful when a job is being done early. It is offered only while the schedule is not yet fulfilled.
Creating a schedule
Add Schedule opens a form asking for:
- Name (required), a rich-text Description, Assigned Ranks, Department and a Priority of High, Medium or Low (Low by default).
- Scheduled One-Time — a switch. Left off, the schedule is recurring and keeps producing tasks. Turned on, it produces a task once and is then finished. Recurrence is fixed at creation; it cannot be switched afterwards.
- Enable running-hours schedule — with Hours Schedule (the interval in running hours) and Last Hours When Completed (the component's reading when the job was last done, pre-filled from the component's current hours when you tick the box). On a component that does not track hours the checkbox is disabled and says Component has no hours tracking enabled.
- Enable calendar-based schedule — with Time Schedule Value, a Time Schedule Frequency of Day(s), Week(s), Month(s) or Year(s), and Last Date When Completed.
When editing an existing schedule (or editing an AI-suggested schedule before approving it), the form also shows a Tags field.
At least one of the two schedule types must be enabled; a Schedule Configuration warning appears while neither is, and the save is rejected. As you fill it in, that same banner spells out in plain words what you have configured — for example that the task will be created every 250 hours, or every 6 months, or whichever of the two comes first.
The last-completed date and hours are what the next occurrence is measured from, so they matter on day one. Nauticare checks a schedule the moment it is saved, so a calendar schedule left without a last-completed date raises its first task immediately; setting it to when the job was genuinely last done avoids that.
How a schedule becomes a task
Nauticare checks schedules on active components and raises tasks automatically. There is no manual step.
- Calendar-based schedules are checked hourly. A schedule is due once the configured interval has elapsed since its last completion date.
- Running-hours schedules are checked the moment a component's hours are saved — including hours saved on a component that others are linked to, or received from a telemetry connector — so a reading that pushes a schedule past its interval raises the task straight away. A sweep every six hours acts as a safety net for anything the immediate check missed.
- Every schedule is also checked immediately when it is created or edited.
- A schedule with both triggers fires on whichever comes first.
Three rules keep the task lists sane:
- One open task per schedule. While a schedule already has an uncompleted task, no second one is created for it. The next occurrence only appears after the current one is closed out.
- A one-time schedule stops after its task is completed. It is then marked Fulfilled in the table and produces nothing further.
- Archived components are paused. While a component is archived, its schedules are skipped and raise no tasks.
The generated task inherits the schedule's name, description, priority, tags, assigned ranks and department, is linked back to the component, and starts with no people assigned and a status of To do. Editing a schedule later affects only the tasks it raises from then on; tasks already raised keep what they were created with. Its due date is the date the calendar schedule became due, or today if that is later or if the schedule is hours-based.
Deleting a schedule
Deleting a schedule needs permission to delete maintenance tasks and asks for confirmation. It stops future tasks being raised; tasks already created from it are unaffected and stay in the lists. A component cannot be deleted while any of its schedules still exist (though it can be archived).
Yachts running the on-board app
On a yacht running the on-board app, schedules are created, edited and deleted aboard — the cloud shows the PMS tab read-only, with no Add Schedule button and no row actions beyond View. The automatic checks described above also run aboard rather than in the cloud, so the tasks appear in the cloud lists once the yacht syncs.