Manuals are files attached to components. They can be reached two ways: the Manuals tab on a component, which shows just that component's manuals, and Maintenance → Manuals, which lists every manual on the yacht in one place.
The boat-wide Manuals page
Maintenance → Manuals shows each manual with its Name, Created at, and chips for the Linked Components it belongs to, plus a Columns control for hiding columns. A search box matches the manual name, and a Filter dropdown narrows the list to manuals linked to particular components — a manual matches if any of its linked components is selected.
Clicking a row opens the file. Files the browser can display offer View; anything else offers Download.
Adding and linking
Add Manual, on a component's Manuals tab, uploads one or more files against that component. Pick the files or drag them onto the dialog; each one then gets a Name, pre-filled from the file name, and can be swapped with Replace or dropped with Remove before you confirm. Edit lets you rename a manual or replace the file afterwards.
A single manual often covers several components. Link to components attaches an existing manual to more of them, so the same file does not have to be uploaded repeatedly. Where a manual is linked to more than one component, that component's row offers Unlink from this component instead of a delete — the file stays available to the others. Delete only appears when this is the manual's last link, or when you are working from the boat-wide list, and it removes the manual everywhere.
Adding, editing, linking, unlinking and deleting all require maintenance edit permission (and are unavailable on an archived component); viewing and downloading only require view permission. On a yacht running the on-board app these actions are done aboard and the buttons are absent in the cloud.
Generating tasks from a manual with AI
Nauticare can read a manual and propose maintenance schedules from it. The action lives on the component's Manuals tab as Generate tasks, and needs maintenance edit permission.
- Choosing Generate tasks opens a Generate tasks from manual dialog with one question: whether to Group tasks with the same schedule into a single task. Grouping produces fewer, broader tasks; leaving it off produces one task per activity the manual describes.
- The analysis runs in the background. The manual's row shows an Analysing indicator, and a toast tracks progress across the app, so you can carry on working elsewhere. If the run fails, the toast reads Generation failed and offers Retry, which runs it again with grouping on. The exception is when your company has reached its monthly AI limit: the toast then shows that limit message instead, with no Retry, because another attempt would fail the same way until the limit is raised.
- When it finishes, the manual's row offers View generated tasks, which opens the suggestions in the component's PMS tab.
Any file type can be uploaded as a manual, but only PDFs, images and plain text can be analysed; where a manual's format is not supported, the button is disabled and says so. Up to three analyses can run at once — beyond that the button asks you to wait for one to finish. Activities the manual describes as daily or more frequent are filtered out, since those are operational routines rather than planned maintenance.
Reviewing the suggestions
The review panel is headed AI-Suggested Tasks from Manual and shows one card per proposal, with its name, priority, description, the schedule it derived, and, under Also applies to, any other components the AI matched the task to.
For each card you can:
- Edit it before accepting — the proposals are drafts, not commitments.
- Reject it, which marks the card without removing it, so you can still approve it later.
- Approve it, which opens a dialog listing the components the manual is linked to. The component you are reviewing plus everything the AI matched are pre-selected; uncheck what does not apply, set Last Hours When Completed and Last Date When Completed where relevant (with Copy first to all when approving onto multiple components at once), and confirm. For an hours-based task, only components that track hours can be picked. One schedule is created per selected component.
Approve All walks through the remaining cards in turn, skipping any you rejected. Reject All closes the panel without creating anything. Regenerate asks the grouping question again and re-runs the analysis from scratch. Once every card is approved or rejected, only Close remains.
Two guards apply. A proposal with no schedule at all is marked Incomplete and cannot be approved until you edit a schedule into it. A proposal triggered by running hours is marked Needs component hours and blocked when none of the manual's linked components track hours — enable hours on a component, or edit the proposal to use a calendar schedule instead. While either kind of card is outstanding, Approve All stays disabled and explains why.
Cards that already exist as schedules on a component are labelled as such, so re-opening the panel after a partial approval does not create duplicates, and an approval that failed for some components can be retried for just those.
Creating schedules from the review panel requires permission to edit maintenance tasks.