Features

Items in other modules can be deferred to a drydock period. They then surface as tasks in the drydock record on their own. These items are postponed PMS maintenance logs with the DryDock postponement type. They are also deferred Deficiency, Non-Conformity, Technical Finding and Enquiry records. Each creates a drydock task entry with the matching task type and a two-way reference to the originating record.

A change to a drydock's scheduled or estimated date triggers a cascade. It passes the new date to each linked postponed item across all 5 source modules. The cascade runs on the server as one coordinated update across all linked records in the same request. This keeps all originating modules consistent, with no coordination on the client side.

So the drydock work scope assembles itself from operational data. There is no manual re-entry of deferred items. There is no risk of date drift between the drydock plan and the originating module records.

Each drydock task carries 2 cost fields. Estimated cost is the budget figure captured at specification time. Actual cost is the real expenditure captured at completion. Both fields support currency codes for multi-currency tracking across international shipyard engagements.

A subcontractor name and reference field on each task records the responsible yard vendor for the work item.

Expenditure records created from drydock task invoicing receive a sequential PO number. A unique sequence counter makes sure no number repeats. The format uses the current year, the vessel identifier and a per-year-per-vessel counter that increments without gaps or collisions.

The 5-Widget Dashboard Suite includes a dedicated widget that surfaces completed tasks with no linked invoice. It works as a post-docking financial reconciliation checklist, so no work item escapes the cost record.

The drydock module includes a formatted PDF export. It generates a drydock specification document for yard handover. The export organizes tasks into 4 type-based groups: standard work items, maintenance-deferred items, issue-deferred items and enquiry-deferred items. This gives the yard a structured view of the complete work scope, organized by origin.

Each task in the export includes its title, category, description, status, cost estimates, and subcontractor assignment. The document header carries the drydock project identifier, vessel name, shipyard, scheduled dates, and assigned superintendent.

This print-ready format ends the need to compile docking specifications by hand from separate systems. It makes sure the yard receives a complete, authoritative work scope document.

The Predefined Task Library is a reusable template system for standard drydock specification items. Technical superintendents create predefined task templates with a title, description and category.

Templates are stored at the company level. They are available when adding tasks to any drydock project across the fleet.

When adding predefined tasks, the user selects from the library. Navatom then creates full drydock task records by copying the template data.

This ends the need to re-enter standard work items for each docking event. It applies the standard docking specification the same way across sister ships.

Each drydock task is classified into one of 14 categories. They represent the major work areas of a docking event. The categories are Drydocking, General Services, Surface Treatment & Painting, Steel Works, Pipe Works, Safety Equipment, Routine Drydock Items, Electronics & Electrical, Overhauls, Deck & Cargo, Engine, Bridge & Navigation Equipment, Accommodation, and Other. This classification drives the task organization within the drydock record. It also drives the 4-group PDF export that separates tasks by type for yard handover.

Categories are assigned at task creation and can be changed throughout the task lifecycle. The category is independent of the task type. A Maintenance task, a Deficiency task and a Predefined task can all carry the same category.

Each piece of work done during a docking event is recorded as a drydock task. There are 7 task types, covering every source. Maintenance is for deferred PMS items. Deficiency is for open deficiency records. Non-Conformity is for non-conformity records. Technical Finding is for technical findings from audits. Predefined is for reusable specification items from the predefined task library. Enquiry is for deferred enquiry items. Other is for manually specified ad-hoc work.

Each type has its own status lifecycle: Not Started, Started, Completed, and optionally Deleted for administrative removal.

Tasks created from cross-module postponements link back to the originating record on their own. The drydock task carries the source module's document ID and type. This creates a two-way traceability chain. Manually adding a task needs only a title and category. Navatom assigns a unique identifier, sets the initial status to Not Started, and emits a task creation event.

A whole set of standard tasks is added from the library in one step, all of it or none.

Each drydock starts with a scheduling action. It creates the project record and gives it a sequential identifier with vessel, year and sequence number. At the same time, it creates a calendar event with drydock-type, so the event appears on the fleet-wide shared calendar. There are 2 types: Scheduled (planned dockings with advance notice) and Unscheduled (emergency dockings that arise without advance planning).

The lifecycle follows a linear 4-status path: Scheduled, Started, Finished, Deprecated. Deprecated is used for cancelled events, without losing the record. A high-priority notification goes out when a drydock is completed, so stakeholders are informed at once.

Date fields distinguish between the scheduled date (planned), the estimated date (current working estimate) and the actual started date. Editing a scheduled drydock's date deletes and recreates the calendar event through the calendar integration. The calendar always reflects the current committed date, not the original plan.

Deleting a scheduled drydock removes both the calendar event and its metadata. No orphaned records are left in the calendar system. The inline-editable title, shipyard assignment and office assignee fields can all be changed after creation. There are 8 dedicated field update modes for this.

Each drydock task carries 2 independent rich-text fields with full formatting support. Details is the pre-work scope specification that describes what needs to be done. Report is the post-work completion narrative that describes what was actually done.

At the drydock project level, a third independent rich-text field gives a single narrative document. It is the Final Report, and it summarizes the entire docking event. The 3-level documentation structure (task details, task reports, project final report) gives superintendents a clean split. Planning documentation, execution records and the summary narrative that goes with project closure stay apart.

Scheduling a drydock puts it on the fleet calendar. Changing its dates moves the entry. Deleting the drydock removes it. Each drydock appears on the fleet-wide shared calendar alongside other module events such as audits and surveys.

The calendar event carries the drydock's drydock-type identifier. This enables filtered calendar views that show only docking events. Calendar integration is fully automatic. No manual calendar entry is needed, and date changes propagate instantly.

So fleet planners always have an accurate picture of when vessels will be out of service for docking. They do not need to cross-reference separate scheduling spreadsheets.

Each drydock record can be linked to a shipyard company managed through Navatom's CRM module. The shipyard field references a CRM company record. The yard's full contact details, location and engagement history show directly in the drydock project view. There is no separate vendor list to maintain.

So when a drydock is scheduled, the superintendent picks a shipyard from the company's existing CRM database. They do not type a free-text name.

Navatom Drydock has 5 dedicated dashboard widgets. They give fleet managers and technical superintendents real-time visibility into docking project status without opening individual drydock records. The first widget, My Active Drydocks, shows as a count of active drydocks assigned to the current user. It also shows as a detailed table with the underlying list, status, vessel and shipyard.

The second and third widgets are My Open Tasks and My Open Issues. They show the user's open task backlog and issue-type tasks respectively.

The fourth widget, My Maintenance Tasks, surfaces maintenance-type tasks. It gives technical superintendents a dedicated view of PMS-deferred work awaiting action in active dockings. The fifth widget, Completed Without Invoice, identifies completed tasks not yet linked to an expenditure record. It works as a post-docking financial reconciliation tool.

All 5 widgets can be placed on the dashboard alongside other module KPI widgets.

The drydock detail view has a 3-panel layout. It gives superintendents complete project visibility from a single screen. The west sidebar contains the definition fields. These are project ID, type (Scheduled/Unscheduled), status and 3 date fields (scheduled date, estimated date, started date, finished date). Authorized users can edit them all in place. The sidebar also has the Assignees panel, which lists the office team members assigned to the project.

The panel title can be edited in place, with no separate edit form.

The center panel has 6 tabs that cover the full project scope. Tasks shows all tasks with type indicators and status. Maintenance is filtered to Maintenance tasks only. Issues is filtered to Deficiency, Non-Conformity and Technical Finding types. Enquiries is filtered to Enquiry tasks. Report is the Final Report editor. Invoices is the expenditure table linked to all tasks. The side panel provides Comments (project-level conversation), Attachments (drydock-level file evidence) and Events (the drydock's full history of changes).

This 3-panel layout gives superintendents scope, cost, narrative and audit trail without leaving the project record.

The task detail view mirrors the drydock detail view's 3-panel structure, adapted for individual work items. The west sidebar contains 2 sections. Information has category, scheduled dates, task status and a type badge showing which source module the task came from. Expenditures has estimated cost, actual cost with currency codes, and subcontractor name and reference. The sidebar also has the Assignments panel, which shows ship-side and office-side assignees separately.

Start Task and Complete Task action buttons are prominently placed. The task status lifecycle enforces the Not Started → Started → Completed sequence.

The center panel has 3 tabs. Description is the Details editor for pre-work scope specification. Report is the completion Report editor for post-work narrative. Invoices shows the PO-linked expenditure records for this task. The side panel provides the same Comments, Attachments and Events tabs as the parent drydock view, scoped to the task.

The task's east dock is separate from the parent drydock's east dock. So task-specific comments and attachments stay apart from the project-wide collaborative record.

Each change to a drydock or one of its tasks is recorded with who and when. This covers status, dates, costs, assignees, reports, comments and files. The history is kept for class surveys, internal review and contract disputes.