Keel to Quay

Merchant ships are repaired under conditions that punish improvisation. A drydock berth is booked months in advance, often shared across several vessels in sequence, and a delay on one ship can cascade through a yard's entire schedule. A vessel out of service earns no freight, so every additional day in dock has a direct commercial cost that owners track closely. At the same time, the physical work involves cutting into pressure boundaries, lifting heavy machinery, working in confined tanks, and disturbing systems that were never designed to be reopened. The combination of tight time, high stakes, and inherently hazardous work is exactly the condition under which structured methods earn their keep, because intuition alone cannot hold all the relevant variables in view at once.

Consider what happens without structure. A yard planning team estimates docking duration from experience on a similar vessel, without a documented Critical Path Analysis. Hull thickness gauging begins on day three instead of day one, because ballast tank access was not scheduled early. The readings come back showing diminution beyond the Allowable Diminution on several frames, which means steel renewal that was never budgeted or scheduled. The vessel now needs ten additional days, the yard has no slack because another ship is waiting for the same berth, and the owner is negotiating late-delivery penalties. None of this was unforeseeable. It was unplanned, because no one had built a sequence that put hazard and condition discovery ahead of the decisions that depend on it.

Structured analysis works by forcing the sequence to run in the right order: identify what could go wrong, measure what has already gone wrong, decide which findings are acceptable and which are not, and only then commit to a schedule and a specification. This is not bureaucracy for its own sake. It is the only way to convert a repair project's many sources of uncertainty (corrosion rates, equipment condition, supply lead times, weather windows) into decisions that can be defended afterward, whether that defense is to a classification surveyor questioning a repair decision or to a court examining liability after an incident.

The cost of skipping structure shows up most clearly in two places: schedule overruns and safety incidents. Industry data on ship repair projects consistently points to late discovery of hull and machinery condition as the single largest driver of schedule slippage, a pattern echoed in classification society guidance that pushes early and thorough survey scoping specifically to reduce this risk^[1]. Safety incidents during repair, meanwhile, cluster around hot work, confined space entry, and lifting operations, precisely the activities that a HAZID Workshop is designed to surface before they begin. Structured analysis does not eliminate these risks. It converts them from surprises into managed, documented decisions.

There is also a professional reason to formalize these methods, distinct from the commercial and safety case. A superintendent or surveyor who can run a defensible HAZOP Study, build a Risk Matrix with clearly defined scales, and produce a Survey Report with full Documentation Traceability is more valuable to an owner, a class society, or a yard than one who relies on undocumented experience. Experience matters, but it does not transfer easily between people or survive a change of personnel partway through a long repair cycle. A documented method does both. It also protects the individual professional: when a repair decision is challenged later, whether in an insurance claim or a Port State Control detention, the record of how the decision was reached is often more important than the decision's technical merit alone.

For the graduate researcher, the stakes are different but related. Ship repair as a field has a substantial body of applied practice, codified in classification rules, IMO instruments, and yard procedures, but a comparatively thin body of peer-reviewed research that tests, compares, or improves these practices empirically. This gap is itself a professional observation worth taking seriously, because it means a well-framed Doctoral Research Question in this area can draw on rich field practice while still making a genuine Research Gap claim. Understanding why structure matters operationally, as covered in this subchapter, is also what equips a researcher to ask sharper questions. A study that proposes a new risk matrix design, for instance, is only interesting if it is built on an accurate picture of where current matrices fail in practice, not a generic critique borrowed from another industry.

One useful way to think about the stakes is to separate three kinds of cost that poor structure imposes: direct cost, schedule cost, and reputational cost. Direct cost is the extra steel, labor, and equipment needed when a problem is found late rather than planned for. Schedule cost is the knock-on effect of delay, both on the vessel in dock and on the yard's other commitments. Reputational cost is harder to quantify but often larger over time: a yard known for schedule overruns or an owner known for disputed specifications finds future negotiations harder and more expensive. Structured methods address all three simultaneously, because better hazard identification and condition assessment reduce direct cost, better scheduling reduces schedule cost, and better documentation reduces reputational cost by making outcomes traceable and defensible.

A short example illustrates how these costs compound. Suppose a vessel's intermediate shaft bearing, flagged as a vibration concern before docking, is not assessed through a formal FMEA before the drydock period begins. The yard opens the bearing housing only when vibration readings worsen mid-docking, discovers scoring on the shaft journal, and must now source a replacement sleeve on short notice. The direct cost is the expedited part and the extra labor. The schedule cost is the days lost waiting for that part, which may exceed the direct cost many times over if it pushes the vessel past its berth window. The reputational cost falls on whoever owned the decision not to open the bearing earlier, even if that decision seemed reasonable with the information available at the time. A pre-docking FMEA, by contrast, would have assigned this failure mode a Risk Priority Number high enough to justify opening the bearing proactively, during the scope-freeze window when parts could still be ordered with lead time.

None of this implies that structured analysis is a guarantee against surprise. Ships are old, complex, and often poorly documented by the time they reach a repair yard decades into service, and some condition findings cannot be anticipated no matter how thorough the pre-docking hazard and condition review. What structured methods change is the proportion of surprises that are genuinely unforeseeable versus the proportion that were foreseeable but unaddressed. Every method covered later in this book, from HAZID through doctoral research design, is aimed at shrinking that second category as far as practically possible, while building in enough schedule and decision-making flexibility to absorb what remains in the first.

It is also worth recognizing that structure and speed are not opposites, despite how they are often framed in yard culture. A HAZID Workshop that takes two days before docking begins is not lost time if it prevents a ten-day delay discovered mid-project. A well-built Planned Maintenance Schedule that flags a component for inspection based on Condition-Based Maintenance logic, rather than a fixed calendar interval, often reduces unnecessary work rather than adding to it. The perception that structured methods slow projects down usually comes from seeing them applied badly, as a paperwork exercise disconnected from the actual decisions being made, rather than from the methods themselves. Done well, they are what makes speed possible, because they remove the guesswork that causes delay in the first place.

The remainder of this book treats these methods as a connected toolkit rather than a checklist to complete once and file away. A Hazard Register built during a HAZID Workshop feeds directly into the Risk Matrix used to rank findings. A Risk Priority Number from an FMEA informs whether a task belongs in the Planned Maintenance Schedule. A Survey Report's As-Found Condition data determines the Repair Work Specification's scope, which in turn sets the Scope Freeze point for the Drydocking Campaign's Critical Path. Seeing these connections is more valuable than mastering any single method in isolation, because in practice a repair decision rarely touches only one of these tools at a time.

The practical skill this book aims to build, then, is not just competence in any one method but fluency in moving between them as a project unfolds. A superintendent who can run a HAZOP Study but cannot translate its findings into a Risk Matrix that a class surveyor will accept has only half the skill needed. A researcher who understands Reliability-Centered Maintenance theory but cannot connect it to the Documentation Traceability requirements that make maintenance data usable has only half the research foundation needed. The chapters ahead build each piece, but the goal throughout is the connected system, not the isolated technique.

Merchant fleet repair covers a wide range of vessel types and project scales, and it is useful to be precise about what sits inside the scope of this book and what sits outside it. The focus here is on repair and drydocking work carried out on operational merchant ships, meaning cargo-carrying vessels such as bulk carriers, tankers, container ships, and general cargo ships, rather than newbuilding construction or naval vessel maintenance. Repair work in this context ranges from routine Special Survey drydockings that occur on a roughly five-year cycle, through intermediate and annual surveys with smaller scopes, to emergency repairs following grounding, collision, or machinery failure. Each of these project types shares the same underlying methods but applies them at different intensities and under different time constraints.

A Special Survey drydocking is the anchor event around which most of this book's examples are framed, because it is the point in a vessel's Repair Cycle where the widest range of methods comes into play at once. During a Special Survey, class requirements call for close-up examination of structure, Hull Thickness Measurement across extensive areas, tailshaft and rudder surveys, and verification of safety and machinery systems, all within a single docking period. This concentration of requirements is exactly why Hazard Identification Methods, risk matrices, FMEA, and scheduling tools matter most here. Intermediate surveys and voyage repairs use the same toolkit but at smaller scale, often with a single system or a limited structural area as the focus rather than the whole vessel.

Emergency repair work deserves separate mention because it compresses every method into a shorter timeframe without removing the need for rigor. A grounding that damages bottom shell plating still requires a hazard assessment before hot work begins, a risk-based decision about whether temporary or permanent repair is appropriate, and a specification precise enough for an insurer or class society to accept. The difference from planned drydocking is tempo, not method. A professional who has internalized these tools from routine planned work is far better positioned to apply them correctly under the pressure of an emergency than one encountering them for the first time in a crisis.

Geographically, merchant ship repair happens across a global network of yards with very different regulatory environments, labor practices, and technical capabilities, from major repair hubs in Asia and the Middle East to smaller regional yards serving coastal and short-sea fleets. This book does not assume a single regulatory jurisdiction, because the methods covered, HAZID, HAZOP, FMEA, risk matrices, and the structure of survey documentation, are shaped primarily by classification society rules and IMO instruments that apply internationally, rather than by national law alone. Where flag state or Port State Control requirements matter specifically, they are addressed directly rather than assumed as background knowledge.

The systems covered span structural, mechanical, and safety-critical scope. On the structural side, this includes hull plating, framing, tanks, and coatings, with particular attention to corrosion and fatigue-driven degradation. On the mechanical side, it includes main engines, auxiliary machinery, propulsion shafting, and the engine room systems that depend on them, such as cooling, lubrication, and fuel systems. On the safety-critical side, it includes life-saving appliances, fire-fighting systems, and the structural and mechanical items tied directly to class and statutory survey requirements. The book treats these as a connected set rather than separate silos, because a single repair project typically touches all three, and the hazard, risk, and scheduling tools apply across the boundaries between them.

The stakeholders whose decisions this book addresses form a defined group, covered in depth in a later chapter on Stakeholder Mapping, but worth naming here. They include the vessel owner and the technical manager acting on the owner's behalf, the Classification Society surveyor responsible for verifying compliance, the repair yard's project and production management, the flag state administration, and Port State Control authorities at the ports the vessel calls. Each of these parties reads the same documents, the Survey Report, the Repair Work Specification, the Risk Matrix, for different purposes and with different concerns. Understanding this plurality of readers from the outset shapes how documentation should be written, a point developed fully in the chapter on survey reports and specifications.

In terms of the academic scope, the book is calibrated for readers pursuing graduate-level study, including doctoral candidates whose research sits inside or adjacent to ship repair practice. This shapes two things about how the material is presented. First, each method is explained with enough procedural depth that a reader could design a study around it, not merely apply it operationally. Second, the final chapter on research design treats ship repair practice as a field with identifiable Research Gaps, meaning gaps between what is codified in class rules and shipyard procedure versus what has been tested, measured, or compared in peer-reviewed literature. A master's or doctoral reader should come away able to locate their own research question somewhere in that gap.

It is useful to be explicit about what this book does not attempt to cover, so expectations are set correctly from the start. It does not provide shipyard cost estimation or commercial contract negotiation guidance, beyond noting where schedule and scope decisions carry commercial consequences. It does not cover naval architecture or structural design calculation in the way a stability or strength textbook would, though it draws on structural concepts where they bear directly on repair decisions. It does not serve as a substitute for a specific Classification Society's rules, which must always be consulted directly for a given vessel and class notation, since rule requirements vary by society and are revised periodically. The book instead provides the method and the reasoning that sits around those rules, the part that rules alone do not teach.

The table below summarizes how the book's scope maps across project type, time pressure, and the primary methods each one draws on most heavily, which is useful as a quick orientation before moving into the chapters themselves.

Reading across that table, a pattern emerges that recurs throughout the book: the amount of formal method applied should scale with consequence and complexity, not with how much time is available. An emergency repair under severe time pressure still needs a documented risk decision, even if that decision is reached in hours rather than weeks. What changes with time pressure is the format and speed of the method, not whether it is used at all. This principle, matching method to both the question being asked and the time available, runs through every chapter that follows and is worth keeping in mind as a filter when applying any single technique to a real project.

A final point on scope concerns the vessels themselves. Merchant fleets include ships with vastly different ages, from newly delivered tonnage still under warranty to vessels approaching thirty years of service with correspondingly different corrosion histories, equipment obsolescence, and documentation quality. Older vessels, in particular, often arrive at a repair yard with incomplete or inconsistent maintenance records, which complicates both Reliability-Centered Maintenance analysis and Hull Thickness Measurement trending. This book addresses that reality directly rather than assuming a clean data environment, because incomplete records are the normal condition in much of the world merchant fleet, not an exception. Methods are presented with this constraint in mind, including guidance on how to proceed with partial data rather than treating complete records as a prerequisite.

Taken together, this scope defines a book about the applied, cross-disciplinary work of keeping merchant ships safely and efficiently in service through their repair cycles, written for the people who do that work and the researchers who study it. The chapters ahead move from context and regulation, through hazard and risk methods, into failure analysis and maintenance logic, then into documentation, hull assessment, and scheduling, before closing with stakeholder dynamics and research design. Every method introduced is scoped to this repair-cycle context specifically, rather than imported generically from process safety or manufacturing reliability literature without adaptation, even where the underlying technique originated in those fields.

This book is structured so it can be read start to finish as a connected argument, or consulted chapter by chapter as a working reference, and both uses are intentional. A reader preparing for a first drydocking assignment will benefit from reading sequentially, since later chapters assume familiarity with terms and methods introduced earlier, such as the Risk Matrix vocabulary established before FMEA is introduced. A reader already experienced in repair work, by contrast, might go directly to the chapter on Drydocking Campaign scheduling or the chapter on Survey Report structure, using the earlier chapters as a reference when an unfamiliar term or method appears. Both paths are supported by the consistent terminology used throughout, so a term like Risk Acceptance Criteria means the same thing wherever it appears.

For the working professional, the most direct way to use this book is alongside an active or upcoming repair project. Before a HAZID Workshop, the relevant chapter provides a procedure and a set of prompts to structure the session. Before drafting a Risk Matrix for a specific project, the chapter on likelihood and consequence scales gives a framework for calibrating those scales to the vessel and yard in question rather than importing a generic matrix unexamined. Before writing a Repair Work Specification, the relevant chapter lays out the structure and the traceability requirements that make the document defensible later. Used this way, each chapter functions less like a textbook section and more like a prepared checklist that can be adapted to the project at hand.

The checklist below offers one way to use the book as a practical companion across a repair project's lifecycle, mapping project phases to the chapters most relevant at that stage.

For the graduate researcher, the book should be read with a different question in mind at each stage: not only "how is this done" but "what is assumed, what is contested, and where has this not yet been tested." Each chapter describing an operational method, from HAZOP procedure to Critical Path Analysis, implicitly carries assumptions about data availability, stakeholder cooperation, and organizational maturity that are rarely stated explicitly in industry guidance or classification society publications. A doctoral reader should treat these implicit assumptions as candidate Research Gaps worth probing, since testing whether a standard method holds under atypical conditions, such as incomplete maintenance records or a yard with limited risk assessment experience, is often a productive line of inquiry in its own right.

The final chapter on designing doctoral research is written to be used in dialogue with the rest of the book rather than read in isolation. A reader working on a dissertation proposal should expect to move back and forth: reading the chapter on FMEA, for instance, to understand current practice, then returning to the research design chapter to test whether a specific weakness noticed in that practice, such as inconsistent Risk Priority Number scoring across assessors, could be framed as a testable Doctoral Research Question. This iterative use, treating the earlier chapters as a literature-adjacent foundation and the final chapter as a method for converting observations into research questions, is the intended relationship between the two parts of the book.

Several structural features recur across chapters and are worth understanding before proceeding, since they are used consistently rather than being explained again in later chapters. Canonical terms, such as Hazard Register, Scope Freeze, or Condition-Based Maintenance, are introduced once with enough context to understand their meaning, then used consistently afterward without redefinition. Worked examples appear throughout, generally drawn from realistic but illustrative scenarios rather than named real vessels or incidents, since the purpose is to demonstrate method rather than to report on specific case histories. Where a concrete statistic or named study is cited, it reflects an attributable, verifiable source rather than an invented figure, and footnotes are used sparingly and only where a specific claim benefits from one.

Checklists, decision trees, and tables appear at points where a method benefits from a structured visual summary rather than prose alone, but they are not meant to replace the surrounding explanation. A checklist for a HAZID Workshop, for example, is useful as a quick reference during an actual session, but the reasoning behind each item, covered in the surrounding paragraphs, is what allows a reader to adapt the checklist when a project's circumstances do not match the typical case exactly. Treat these structured elements as compressed versions of the argument, not as a substitute for reading the argument itself.

A practical habit worth adopting while working through the book is to keep a running project file, whether real or illustrative, and apply each chapter's method to it as it is introduced. A reader working through the hazard identification chapter might open a Hazard Register for a vessel they are currently responsible for, even in draft form, and populate it as the chapter's procedure is explained. By the time the risk matrix chapter is reached, that same register provides material to practice matrix scoring on. This approach turns the book from a sequence of explained methods into an accumulating body of practical work, which is especially valuable preparation for a professional facing a live project or a researcher building the foundation for a methodology chapter.

For readers using this book in a classroom or structured training setting, the chapter divisions align reasonably well with multi-week modules, since each numbered chapter after this introduction covers a distinct method or document type with enough depth for a dedicated session. An instructor might pair the hazard identification chapter with a practice HAZID Workshop exercise, or pair the stakeholder mapping chapter with a role-play exercise assigning students to owner, yard, and class surveyor perspectives. The book does not prescribe a specific training curriculum, since training contexts vary too widely to standardize, but its chapter structure is deliberately modular enough to support this kind of use without modification.

One caution applies regardless of how the book is used: none of the methods described here substitute for direct consultation of the applicable Classification Society rules, flag state requirements, or the ISM Code provisions relevant to a specific vessel and voyage. Rules are revised periodically, vary by society, and sometimes vary by vessel type or trading area within the same society's framework. Where this book explains, for instance, the general structure of a Special Survey scope, it is describing a common pattern across class societies rather than reproducing any single society's current rule text. A reader applying these methods to a real vessel must verify current rule requirements directly with the relevant class society and flag administration before finalizing any specification or schedule.

The decision tree below offers a simple way to orient a first read of the book, helping a reader decide whether to proceed sequentially or jump to a specific chapter based on their immediate need.

Whichever path fits, the chapters ahead are written to be applied, not merely read. Each method, from the first HAZID session through the final research question, is meant to leave a trace in the form of a document, a register, a schedule, or a draft proposal that can be checked, challenged, and improved. That trace, more than familiarity with the terminology, is what separates a repair project or a research project built on structured method from one built on hope that experience alone will be enough when the unexpected finding surfaces three weeks into a forty-two day docking.