Safety Procedures and Compliance - Marine Engineering Knowledge & Design Tools

🎯 Learning Objectives

✓ Explain the hierarchy of controls as applied to marine energy hazards
✓ Apply ISO 19901-6 requirements to assess a mooring system safety case
✓ Analyze incident reports to identify root causes violating SOLAS Chapter III or MARPOL Annex I
✓ Design a job safety analysis (JSA) for a turbine installation lift operation

📖 Why This Matters

In marine energy—whether deploying tidal turbines, floating wind platforms, or wave energy converters—a single safety lapse can trigger cascading failures: crane collapse over water, hydrocarbon release from support vessels, or uncontrolled subsea cable damage leading to ecological harm. In 2022, 68% of offshore renewable incidents reported to the UK’s HSE involved procedural non-compliance—not equipment failure. Mastering safety procedures and compliance isn’t about paperwork—it’s about building operational resilience where human judgment, regulatory boundaries, and engineering margins intersect.

📘 Core Principles

Safety in marine energy rests on three interlocking pillars: (1) Hazard identification and risk assessment (HIRA), which systematically uncovers threats like dynamic positioning failure, fatigue-induced structural cracking, or seabed scour under foundations; (2) Safety management systems (SMS), mandated under the International Safety Management (ISM) Code, requiring documented policies, competence verification, internal audits, and continuous improvement loops; and (3) Regulatory compliance layers—international (IMO conventions), regional (EU Offshore Safety Directive), national (US BSEE, UK HSE), and project-specific (contractor SMS, client HSE requirements). Crucially, compliance is not static: it evolves with technology—e.g., new guidance for hydrogen-fueled support vessels (ISO/CD 23917) or AI-assisted remote inspection (DNV-RP-0405).

📐 Risk Priority Number (RPN) Calculation

The Risk Priority Number quantifies hazard severity, likelihood, and detectability to prioritize mitigation efforts in marine energy SMS documentation. It is used during HIRA workshops and JSA development to allocate resources objectively.

Risk Priority Number (RPN)

RPN = S × O × D

Quantitative score used in hazard identification and risk assessment to prioritize corrective actions based on severity, occurrence probability, and detection capability.

Variables:

Symbol	Name	Unit	Description
S	Severity	dimensionless (1–10 scale)	Potential consequence magnitude of hazard (1 = negligible, 10 = catastrophic)
O	Occurrence	dimensionless (1–10 scale)	Likelihood of hazard realization (1 = extremely unlikely, 10 = inevitable)
D	Detection	dimensionless (1–10 scale)	Probability of detecting hazard before consequence occurs (1 = almost certain detection, 10 = undetectable)

Typical Ranges:

Offshore lifting operations: 1–100

Subsea intervention tasks: 5–85

💡 Worked Example

Problem: During pre-installation HIRA for a floating wind turbine lift, assess the hazard 'dynamic positioning (DP) failure during heavy lift'. Assigned scores: Severity = 8 (catastrophic—vessel capsize), Occurrence = 3 (unlikely, but possible due to GPS spoofing), Detection = 2 (difficult—DP alarms may lag by >15 sec). Calculate RPN.

1. Step 1: Confirm scoring scale: Severity (1–10), Occurrence (1–10), Detection (1–10), per ISO 12100 and DNV-RP-0405 Annex A.

2. Step 2: Multiply scores: RPN = Severity × Occurrence × Detection = 8 × 3 × 2.

3. Step 3: Compute result and interpret: RPN = 48. Compare to threshold—DNV recommends immediate action for RPN ≥ 40 in offshore lifting operations.

Answer: The result is 48, which exceeds the DNV-recommended action threshold of 40, requiring mandatory mitigation (e.g., dual independent DP reference systems + real-time redundancy monitoring).

🏗️ Real-World Application

In the 2021 Hywind Tampen project (Norway), a near-miss occurred when a supply vessel’s DP system lost GNSS signal during turbine component transfer. The operator’s SMS—certified to ISO 19901-6 and aligned with NORSOK Z-015—required immediate abort criteria, redundant sensor inputs, and crew competency logs. Post-event root cause analysis revealed outdated firmware in one inertial navigation unit. Corrective action included mandatory firmware updates across all vessels and revision of the SMS ‘technology obsolescence’ clause—demonstrating how compliance isn’t just about meeting baseline standards, but proactively managing evolving technical risk.