responsive site templates

E05
Release & Implementation
of System Changes


Version 01 - Issue Date: 01.10.2024

THIS IS A LIVING SYSTEM THAT WILL CHANGE REGULARLY

Everyone has a role to play in making sure this system is
fit for purpose. This section describes how changes
should be proposed, made and implemented.

MSMS belongs to everyone!

When it is working properly, those onboard will be the ones using this sytem more than anyone. Making sure it is fit for purpose is in everyones interest.

This means you can propose changes also!

If a section is wrong, makes no sense or could be improved, let the Company know or propose an amendment. This can be done in SafetyCulture.

MSMS is the Company Management System of MyriadSea GmbH. The Managing Director is responsible for the overall system, and ensuring it is in place and meets the requirements of the Company and its stakeholders.

However, the system belongs to everyone who uses it.

Anyone can propose changes to MSMS.

A form for proposing changes is provided in SafetyCulture for this.

All proposals for change will be reviewed by a member of the Shore Management Team and an initial decision will be made either to proceed, to request more information or to not proceed. In cases of disagreement the Managing Director has the final decision.

If initially approved, a draft amendment will be prepared and shared with the shore team, the ship and any other relevant parties for input.

Any further input will be reviewed, either implemented or not. The final proposal will be discussed by the Shore Management Team and approved or sent back for further work. 

Final approval for any change must come from the Managing Director.

When a change is finally approved for release it can either be released:

Urgently
In this case a Fleet Directive and a SafetyCulture Heads Up is issued implemeting the change with immediate effect until a new version of MSMS can be issued.

Routinely
In this case the change is implemented in the next routine update of the system.

A system amendment can impose new requirements or actions. If not stated otherwise, it is to be presumed that these apply immediately when the new requirement is implemented into the system.

However, in some cases this may not be practical. For example, a requirement for a new kind of internal audit may take time to be fully implemented.

In cases where an implementation period is to apply, then this must be clearly stated in the new section. It should be clearly stated the latest date when the new requirement is to be fully implemented.

Implementation periods should be as short as possible, and in no case should exceed 12 months.

Amendments

DATE DETAILS
01.10.2024Section newly issued.