Elements 1–3G
Governance & people
Leadership and the SMS, shore-based personnel, and the recruitment, management and wellbeing of vessel personnel.
TMSA 3 · Tanker management self-assessment
Move from yes/no answers to visible improvement.
Connect TMSA assessments with policies, risks, fleet context, evidence, findings, objectives and accountable actions—so continuous improvement remains visible between formal review cycles.
The supplied technical description lists TMSA among STORM’s currently supported frameworks. It does not identify the configured edition, complete KPI catalogue, stage logic or a direct SIRE integration; confirm these details for the intended deployment.
Tanker-management operating recordImprovement tracked
STORMgoverned record
Leadership & SMSPolicies, objectives and reviews
People & fleetResponsibilities and assets
OperationsRisk, change and incidents
ImprovementEvidence, findings and actions
Assess · evidence · improve · review
TMSA 3the third edition currently listed by OCIMF
13 elementsthe management areas described in the TMSA3 structure
4 stagesminimum expectation plus three increasing standards
12 monthsOCIMF’s recommended self-assessment repeat interval
What TMSA3 examines
Thirteen elements across the tanker-management system.
For readability, the official elements are summarised below in four editorial groups. These groups do not replace OCIMF’s element structure, KPIs or best-practice guidance.
Elements 4–6O
Vessel & operations
Reliability and critical equipment, navigational safety, plus cargo, ballast, tank cleaning, bunkering, mooring and anchoring.
Elements 7–11R
Risk & resilience
Change, incidents, safety, environmental and energy management, emergency preparedness and contingency planning.
Elements 12–13A
Assurance & security
Measurement, analysis and improvement together with maritime security, including the cyber-security dimension.
Product evidence boundary
Built-in TMSA support, with the implementation details made explicit.
The technical description names TMSA as a current framework and documents configurable assessments mapped to STORM’s control library. It does not specify the TMSA edition or an OCIMF/SIRE publishing connection.
Documented STORM support
- TMSA listed among current frameworks
- Configurable assessments and evidence records
- Gap, remediation and period comparison workflows
- Policies, risks, audits, incidents and KPIs
- Management reviews and exportable reports
Confirm for the intended deployment
- Configured TMSA edition and licensed content
- Coverage of all TMSA3 elements and KPIs
- Official four-stage dependency logic
- Direct SIRE creation, editing or publishing
- Planned maintenance and crew-training functions
Where STORM supports the programme
Connect assessment status to the work that changes it.
STORM’s documented modules create a connected governance layer around the configured TMSA assessment. OCIMF remains the authority for official content, programme access and publication.
TMSA assessments
Use the supported framework through online assessments, implementation-status tracking, evidence, gaps, reassessment schedules and reports.
Assessment · status · evidenceSMS documentation
Manage policies and procedures through version control, approvals, acknowledgements, scheduled reviews and an auditable history.
Policy Center · lifecycle · trailRisk & fleet context
Connect services, processes, locations, physical and ICT assets with risks, controls, treatment decisions and action ownership.
Cartography · risk · treatmentAudit & close-out
Plan internal audits, retain findings, assign remediation owners and monitor progress through a central audit repository.
Findings · owners · remediationIncidents & lessons
Record security incidents, affected assets, root causes, corrective and preventive actions, target dates and final resolution.
Incident record · root cause · actionKPIs & management review
Track defined objectives and KPIs, then consolidate risk, audit, incident, supplier and policy information for management review.
Trends · decisions · improvement
Assessment with context
Keep the configured TMSA assessment connected to the SMS.
The technical description links supported assessments to status, evidence, gaps and remediation. Policy workflows add version history, approval, acknowledgement and review records behind the management-system answer.
- Framework and category-level reporting
- Controlled policies and procedures
- Scheduled reassessments and comparison across periods
Follow-through you can see
Move gaps, risks and incidents into accountable action.
Risks can carry likelihood, impact, controls, treatment, owners, dates and attachments. Security incidents can retain affected assets, root causes and corrective actions. Marine operational incidents remain outside the documented scope unless separately configured.
- Owned mitigation and treatment plans
- Security-incident lifecycle and corrective actions
- Audit findings and remediation status
Management visibility
Relate measurable objectives to the assets and services involved.
Cartography provides the reusable business and ICT context behind security risks. The objectives and KPI module supports owners, targets, thresholds, monitoring periods and historical trends that can feed management reporting.
- Services, processes, assets and dependencies
- Objective ownership and performance thresholds
- Historical trends and management-review inputs
Official four-stage structure
01
02
03
04
Improvement is measured through increasing standards.
OCIMF describes Stage 1 as the minimum expected standard, followed by three stages of increasing standard or performance. Use the official KPIs and best-practice guidance for every conclusion.
Stage 1
The minimum standard expected by the programme and the base from which further improvement is measured.
Minimum expectationStage 2
The next set of official KPI expectations, representing a higher management standard than the programme baseline.
Increasing standardStage 3
A further progression in management performance, assessed only against the applicable official questions and guidance.
Further progressionStage 4
The highest of the four stages in the TMSA structure, supported by the corresponding OCIMF best-practice guidance.
Highest programme stageThe page does not reproduce OCIMF’s official KPI catalogue or assign an official TMSA stage.
Improvement workflow
01
02
03
04
From KPI response to controlled follow-through.
STORM can organise the supporting programme record. TMSA publication and authorised sharing continue through the applicable OCIMF process.
Confirm
Verify the applicable OCIMF edition, licensed content, operator access and the TMSA configuration deployed in STORM.
Edition · scope · accessAssess
Answer the official KPIs, retain comments and evidence, and identify the current status by element and stage.
KPI · evidence · statusImprove
Convert gaps into risks, findings, document changes, objectives and owned remediation with target dates.
Actions · owners · close-outReview
Monitor improvement, bring results into management review and use SIRE for official creation, editing or publication where applicable.
Review · repeat · publishPractical questions
Keep platform support and OCIMF programme authority distinct.
That distinction makes the implementation easier to assess and avoids unsupported assumptions about content or publishing.
What is TMSA?
The Tanker Management and Self-Assessment programme is OCIMF’s mechanism for companies to assess and improve their safety management systems against KPIs and recommended best practices.
Which TMSA edition is currently published?
OCIMF currently lists Tanker Management and Self Assessment 3, Third Edition (2017). OCIMF’s March 2026 newsletter also states that TMSA3 is entering an upcoming review and revision process, so the current official material should always be checked before configuring an assessment.
Does STORM currently support TMSA?
Yes. The supplied technical description explicitly lists TMSA among the platform’s current supported frameworks and documents configurable assessment surveys. It does not state which TMSA edition or exact KPI set is configured, so those details should be confirmed.
Can STORM publish a TMSA document to SIRE?
No direct SIRE integration is documented among STORM’s current integrations. OCIMF states that vessel operators use the SIRE programme’s MSA tool to create, edit and publish TMSA documents.
Does STORM replace planned-maintenance or crew-training systems?
No such replacement is documented. STORM can manage related governance records, policies, risks, evidence and actions. The technical description identifies LMS connectivity as a future integration, not a current capability.
Can STORM support the maritime-security element?
Documented capabilities include asset and dependency cartography, information-security risk assessment, policy workflows, technical vulnerability management, threat intelligence and security-incident management. These can support relevant evidence but do not independently establish an official TMSA stage.
Bring your TMSA context
Book a STORM demo
Test STORM against the improvement record your programme must actually maintain.
Walk through the configured edition, elements, KPIs, evidence, policies, risks, findings and actions—and verify how official SIRE publication will be handled.