Features

Every drydock starts with a scheduling action that creates the project record, assigns it a sequential identifier incorporating vessel, year, and sequence number, and simultaneously creates a calendar event with drydock-type so the event appears on the fleet-wide shared calendar. Two types are available: Scheduled (planned dockings with advance notice) and Unscheduled (emergency dockings that arise without advance planning). The lifecycle follows a linear four-status path — Scheduled, Started, Finished, Deprecated — with Deprecated used for cancelled events without losing the record. A single inbox notification with VeryHigh priority fires when a drydock is completed, ensuring stakeholders are immediately informed.

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 via 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, leaving no orphaned records in the calendar system. The inline-editable title, shipyard assignment, and office assignee fields are all patchable after creation through eight dedicated field update modes in the update modes.

Every piece of work performed during a docking event is recorded as a drydock task. Seven task types cover every source: Maintenance (deferred PMS items), Deficiency (open deficiency records), Non-Conformity (non-conformity records), Technical Finding (technical findings from audits), Predefined (reusable specification items from the predefined task library), Enquiry (deferred enquiry items), and Other (manually specified ad-hoc work). Each type carries its own status lifecycle: Not Started, Started, Completed, and optionally Deleted for administrative removal.

Tasks created from cross-module postponements automatically link back to the originating record — the drydock task carries the source module's document ID and type, creating a bidirectional traceability chain. Manually adding a task requires only a title and category; the system assigns a unique identifier, sets the initial status to Not Started, and emits a task creation event. Bulk task insertion from predefined templates uses batch write operations for guaranteed consistency — all-or-nothing insertion of an entire specification set.

Every drydock task is classified into one of 14 categories that represent the major work areas of a docking event: Drydocking, Hull, Tank, Deck, Cargo, Engine, Auxiliary Machinery, Electrical, Piping, Safety Equipment, Navigation, Communication, Accommodation, and Other. This classification drives both the task organization within the drydock record and the four-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 classification is independent of the task type — a Maintenance task, a Deficiency task, and a Predefined task can all carry the same category. Fleet-wide analytics can aggregate drydock work by category across multiple docking events to reveal patterns in where the most effort, cost, and delays concentrate.

The Predefined Task Library provides a reusable template system for standard drydock specification items. Technical superintendents create predefined task templates with a title, description, and category. These templates are stored at the company level and are available for selection when adding tasks to any drydock project across the fleet.

When adding predefined tasks, the user selects from the library and the system creates full drydock task records by copying the template data. The bulk insertion operation uses a batch write to insert all selected tasks and their corresponding event records in a single database round trip. This eliminates the need to manually re-enter standard work items for each docking event, and ensures that the standard docking specification is applied consistently across sister ships.

Every drydock task carries two independent rich-text fields with full formatting support: Details (the pre-work scope specification describing what needs to be done) and Report (the post-work completion narrative describing what was actually done). Both fields are stored as separate cloud storage objects with a field-level discriminator in the cloud storage key — neither field can overwrite the other. Content-based deduplication prevents redundant cloud writes when predefined task content is copied across multiple tasks.

At the drydock project level, a third independent rich-text field — the Final Report — provides a single narrative document summarizing the entire docking event. The three-tier documentation structure (task details, task reports, project final report) gives superintendents a clean separation between planning documentation, execution records, and the summary narrative that accompanies the project closure.

Every drydock task carries two cost fields: estimated cost (the budget figure captured at specification time) and actual cost (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 via a guaranteed unique sequence counter. 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 — serving as a post-docking financial reconciliation checklist to ensure no work item escapes the cost record.

When items in other modules are deferred to a drydock period, they automatically surface as tasks in the drydock record. Postponed PMS maintenance logs with DryDock postponement type, deferred Deficiency records, deferred Non-Conformity records, deferred Technical Finding records, and deferred Enquiry records all create corresponding drydock task entries with the appropriate task type and a bidirectional reference to the originating record.

Date change operations on a drydock's scheduled or estimated date trigger a cascade that propagates the new date to every linked postponed item across all five source modules. The cascade is executed server-side as a coordinated update across all linked records within the same request, ensuring consistency across all originating modules without client-side coordination. This means the drydock work scope assembles itself from operational data — no manual re-entry of deferred items, and no risk of date drift between the drydock plan and the originating module records.

Every drydock record can be linked to a shipyard company managed through Navatom's CRM module. The shipyard field references a CRM company record, providing the yard's full contact details, location, and historical engagement record directly from the drydock project view without maintaining a separate vendor list.

This integration means that when a drydock is scheduled, the superintendent assigns a shipyard from the company's existing CRM database rather than typing a free-text name. Fleet-wide analytics can aggregate drydock history by shipyard, revealing which yards handle the most projects, which yard relationships deliver the best cost outcomes, and which yards have the deepest experience with specific vessel types.

The calendar integration engine manages a three-operation lifecycle: CREATE (on drydock scheduling — inserts a calendar event with metadata), REBUILD (on date edit — deletes existing event and creates a fresh record with updated dates), and DELETE (on drydock deletion — removes both the calendar event and its metadata). Every 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, enabling filtered calendar views that show only docking events. Calendar integration is fully automatic — no manual calendar entry is needed, and date changes propagate instantly. This ensures that fleet planners always have an accurate picture of when vessels will be out of service for docking, without cross-referencing separate scheduling spreadsheets.

The drydock detail view provides a three-panel layout that gives superintendents complete project visibility from a single screen. The west sidebar contains the definition fields — project ID, type (Scheduled/Unscheduled), status, three date fields (scheduled date, estimated date, started date, finished date), all inline-editable for authorized users, plus the Assignees panel listing office team members assigned to the project. The panel title is directly editable inline without navigating to a separate edit form.

The center panel provides six tabs covering the full project scope: Tasks (all tasks with type indicators and status), Maintenance (filtered to Maintenance tasks only), Issues (filtered to Deficiency/Non-Conformity/Technical Finding types), Enquiries (filtered to Enquiry tasks), Report (the Final Report editor), and Invoices (the expenditure table linked to all tasks). The east dock panel provides Comments (threaded project-level conversation), Attachments (drydock-level file evidence), and Events (the real-time 22-event drydock-level audit log). This three-panel architecture gives superintendents everything — scope, cost, narrative, and audit trail — without navigating away from the project record.

The task detail view mirrors the drydock detail view's three-panel structure adapted for individual work items. The west sidebar contains two sections: Information (category, scheduled dates, task status, type badge showing which source module the task originated from) and Expenditures (estimated cost, actual cost with currency codes, subcontractor name and reference), plus the Assignments panel showing ship-side and office-side assignees separately. Start Task and Complete Task action buttons are prominently placed, with the task status lifecycle enforcing the Not Started → Started → Completed transition sequence.

The center panel provides three tabs: Description (the Details editor for pre-work scope specification), Report (the completion Report editor for post-work narrative), and Invoices (the PO-linked expenditure records for this task). The east dock panel provides the same Comments, Attachments, and Events tabs as the parent drydock view, but scoped to the task level and drawing from the 25-event task-level event type set. This separation between the task's east dock and the parent drydock's east dock ensures that task-specific comments and attachments are organized independently from the project-wide collaborative record.

Every action on a drydock project or its tasks is recorded as an immutable event in a tamper-proof log. The system defines 22 drydock-level event types covering: creation, type change, status transitions (schedule, start, complete, delete/deprecate), and individual field updates for title, start date, scheduled date, estimated date, shipyard, final report content, type, and office assignees. Additionally, comment operations (create, edit, delete) and attachment operations (add, edit, remove) are each their own distinct event type at the drydock level, producing a second-by-second narrative of every modification to the project record.

The task-level event log adds 25 more event types covering task creation, status transitions (start, complete), category change, date changes, estimated cost, actual cost, subcontractor updates, ship and office assignee changes, description content changes, report content changes, and the same comment and attachment operation events scoped to the task. This 47-event total across both levels means that the complete drydock event history — from scheduling the project through closing the final task invoice — is preserved as a tamper-evident, immutable record available for class society inspection, internal compliance review, and contract dispute resolution.

Navatom Drydock provides five dedicated dashboard widgets that give fleet managers and technical superintendents real-time visibility into docking project status without navigating into individual drydock records. The first widget — My Active Drydocks — renders as both a count (active drydocks assigned to the current user) and a detailed table (the underlying list with status, vessel, and shipyard). The second and third widgets — My Open Tasks and My Open Issues — show the user's open task backlog and issue-type tasks respectively.

The fourth widget — My Maintenance Tasks — surfaces maintenance-type tasks specifically, giving technical superintendents a dedicated view of PMS-deferred work awaiting action in active dockings. The fifth widget — Completed Without Invoice — identifies completed tasks that have not yet been linked to an expenditure record, serving as a post-docking financial reconciliation tool. All five widgets are configurable for dashboard placement alongside other module KPI widgets.

The drydock module includes a formatted PDF export that generates a formatted drydock specification document for yard handover. The export organizes tasks into four type-based groups — standard work items, maintenance-deferred items, issue-deferred items, and enquiry-deferred items — giving 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 eliminates the need to manually compile docking specifications from separate systems and ensures the yard receives a complete, authoritative work scope document.