Or, Why Engineers Should Have What Software Developers Already Take for Granted
The Problem With Regulations
Marine engineering runs on regulations. MARPOL Annex I, IV, VI. SOLAS II-1, II-2. IACS Unified Requirements. Class rules. Flag state interpretations. EU MRV. CII ratings. The list is long and the list changes. A ship designed under this year’s regulations may be non-compliant before it leaves the builder’s yard.
Engineers know this. The problem is that compliance is not a moment — it’s a state. It has to be maintained across every drawing revision, every equipment substitution, every retrofitted scrubber, every re-route of a vent line.
And yet, the tools engineers use to manage this are largely the same ones they used twenty years ago: PDFs, spreadsheets, checklists, and a lot of institutional memory held in the heads of senior reviewers.
