What is the role of the SMS in implementing the ISM Code, why does continuous improvement matter, and how has the Code evolved?

flowchart LR
  A["Plan: policy, procedures, responsibilities"] --> B["Do: operate the ship to the SMS"]
  B --> C["Check: internal audits, non-conformities, near-misses"]
  C --> D["Act: corrective action, management review (§12)"]
  D --> A

• Role: the ISM Code is goal-based; the SMS turns its objectives into the ship’s documented policies, procedures, responsibilities and records, so safety is systematic, not personal.
• Components (ISM §1.4): policy; instructions and procedures; levels of authority and communication, the DPA and the master’s overriding authority; reporting of accidents and non-conformities; emergency preparedness; internal audits and management reviews; resources, maintenance, document control.
• Continuous improvement (§12): plan, do, check, act: audits and near-miss analysis reveal weaknesses, corrective action follows, management review drives improvement; self-correcting and a real safety culture.
• Origin: born of management failures (the Herald of Free Enterprise, 1987); mandatory under SOLAS chapter IX from 1998 and 2002.
• Evolution: cyber risk brought into the SMS by MSC.428(98) from the first DOC verification after 1 January 2021; environmental sustainability (SEEMP, CII, ballast water) and new technology (alternative fuels, IGF Code, autonomous ships) handled by risk assessment and procedures, not a rewrite.
• As Chief Engineer: I run and continuously improve that system in the engine department.