Most Safety Management Systems Were Not Designed, They Were Assembled
Over time, procedures are added, updated, or copied.
Different systems evolve separately. What remains, is often:
-
A structure that no longer reflects how operations actually run
-
Procedures that overlap, contradict, or leave gaps
-
Systems that exist individually but don’t function together
-
Increasing difficulty maintaining consistency across vessels
-
Growing reliance on experience instead of system clarity
-
A sense that “it works on paper, but not as a system”
These issues don’t always show in audits.
But they show in day-to-day operations. And in incidents.
Safety Management System as Integrated Operational Architecture
We design Safety Management Systems as integrated operational architectures. Not as collections of documents.
Whether building a new SMS or restructuring an existing one, our focus is:
-
Clear system structure and logical hierarchy
-
Defined ownership and decision points
-
Integration between key systems (RA, PTW, drills, reporting, verification)
-
Practical usability for crews and shore teams
-
Proportionality: not over-engineered, not superficial
This results in a system that is:
-
Understandable
-
Usable
-
Verifiable
-
And aligned with real work onboard
Most SMS Projects Fail Because They Focus on Documents, Not on the Structure
We approach SMS design differently.
With a marine engineering background and operational experience, we build systems from the perspective of how work is actually done, not how it is described.
We use a structured SMS framework developed across ten core systems, including:
-
Risk Management
-
Operational Control
-
Emergency Preparedness
-
Reporting, Investigation & Learning
-
Assurance & Verification
-
And supporting systems that connect them
This allows us to design SMS that are not only compliant, but also coherent.
How We Can Help You to Build or Restructure Your SMS

1.
Structural Mapping & Gap Identification
We review your current SMS (or starting point) against a structured system framework.
We identify:
-
Structural gaps and overlaps
-
Missing integrations between systems
-
Areas where control logic breaks down

2.
System Design & Architecture
We design or restructure the SMS into a clear, modular system.
This includes:
-
System structure and hierarchy
-
Definition of core subsystems
-
Interfaces between key controls (RA, PTW, drills, reporting)
-
Ownership and governance logic

3.
Controlled Implementation & Integration
We support the implementation in a controlled and practical way.
We assist you with:
-
Prioritized rollout (not everything at once)
-
Alignment with existing operations
-
Integration with current tools and workflows
-
Support to ensure the system is understood, not just issued
In many organizations, individual elements exist: procedures, forms, drills, reporting tools. But without a clear structure, these elements remain disconnected.
Restructuring an SMS is not about rewriting everything. It is about creating a coherent architecture where:
-
Risk assessments drive controls
-
Permits reflect real decision-making
-
Drills test credible scenarios
-
Reporting feeds learning
-
Verification confirms that controls are actually working
This is what turns a “compliant system” into an operational one.
Ilmarine's Approach to Restructuring and Building SMS Architecture
Depending on your starting point, building or restructuring your SMS may involve:
-
Full SMS architecture redesign
-
Restructuring fragmented legacy systems
-
Building missing core systems (e.g. Emergency Preparedness or Reporting, Investigation & Learning)
-
Aligning high-risk work controls across the fleet
-
Integrating verification and assurance mechanisms
-
Simplifying overly complex or unusable procedures
We do not replace your SMS with a generic template.
We work with your existing system, and build it into something that functions as a whole.