Why this matters for maritime documentation

7.1 Maritime documents are already trees, they just do not know it yet

The maritime regulatory framework is one of the most deeply hierarchical documentation structures in any industry. At the top sit IMO conventions (SOLAS, MARPOL, STCW, the ISM Code). These are transposed into national law by 167 flag states, each potentially adding country-specific requirements. Classification societies like DNV, Lloyd's Register, and Bureau Veritas publish technical rules that interpret and extend these requirements. Shipping companies develop Safety Management Systems that implement the rules for their specific operations. And individual vessels carry vessel-specific procedures, checklists, and certificates adapted from company templates.

A single regulatory requirement flows through five levels of documentation before it reaches the bridge of a vessel. This is a tree. IMO conventions are the root. Flag state regulations are the first level of branches. Classification society rules branch further. Company procedures branch again. Vessel-specific documents are the leaves.

Yet almost no maritime organization manages this hierarchy as a navigable, queryable structure. Instead, it exists implicitly, in the heads of compliance managers, in cross-reference tables maintained in spreadsheets, in the institutional knowledge of experienced personnel.

7.2 The pain points are structural, not just administrative

The maritime industry's documentation challenges are not merely about efficiency. They create real operational and safety risks.

Version control failures are endemic. When a fleet of twenty vessels each carries its own copy of company procedures in PDF format, synchronizing updates across the fleet (especially with limited connectivity at sea) is genuinely difficult. Polaris Shipping, one of the world's largest bulk carrier operators, specifically sought software to achieve "100% version control of all forms and checklists across the entire fleet." The fact that a major operator identified this as a goal worth publicizing suggests how far the industry baseline falls short.

Copy-paste reuse creates invisible inconsistencies. When a procedure written for one vessel type is adapted for another by copying and editing a Word document, the two versions immediately begin diverging. A correction made to one is not reflected in the other. Over years and across fleets, these micro-divergences accumulate into a documentation landscape where no one is entirely certain which version of which procedure is current on which vessel. As one maritime technology analysis noted, "without a system of standardised documents in the industry, there can be incompatibilities between companies," let alone within them.

Manual cross-referencing is fragile and expensive. IMCA M 103 alone cross-references at least ten other IMCA documents plus IMO circulars and classification society rules. A DP FMEA must be cross-referenced against system drawings, operational manuals, and proving trial results. These references are typically static text ("Refer to IMCA M 166") with no mechanism to verify that the referenced document exists, is current, or has not been superseded. When the referenced document changes, nothing alerts the referencing document.

Tracking regulatory provenance is nearly impossible. Shipping companies must know which version of a regulation each procedure was written against. IMO conventions are frequently amended; SOLAS 1974 has been amended dozens of times. MARPOL's energy efficiency requirements evolve with each new round of greenhouse gas targets. When an auditor asks "Was this procedure written against the current version of SOLAS Chapter II-2?", the answer often requires manual detective work through revision histories and approval records.

7.3 Treating documents as data solves these problems structurally

When documents are stored as structured ASTs (trees of typed, validated, individually addressable nodes) the problems above become solvable at the architectural level rather than the procedural level.

An FMEA as structured data. A traditional FMEA worksheet is a complex table in a Word document or spreadsheet, containing equipment items, failure modes, severity ratings, detection ratings, risk priority numbers, and corrective actions. As structured data, each row becomes a node with typed attributes. The system can validate that every equipment item has all required fields, calculate risk priority numbers automatically, flag items above a threshold, and track which items have been verified through proving trials. DNV has called the FMEA "the most important technical document" for DP vessels, and also acknowledged it is "hard to produce, hard to understand, and hard to maintain." Structured data makes it maintainable.

A DP Operations Manual as an assembly. Rather than a single 150-page document that must be rewritten for each vessel, the manual becomes an assembly of reusable blocks (a system description block, an operational procedures block, an emergency procedures block) each maintained independently and composed into vessel-specific manuals through the assembly pattern. When operational procedures are updated, every vessel's manual reflects the change at the next publication cycle, with version pinning ensuring controlled rollout.

Regulatory cross-references as live links. When a procedure references IMCA M 166, that reference is not static text but a typed link to a specific version of a specific document in the system. If IMCA M 166 is superseded, every document referencing it can be automatically flagged for review. The cross-reference becomes a navigable, queryable relationship rather than an inert string of characters.