466-Management of Change / 748
Mana
g
e
m
ent of C
h
an
g
e
BOS-PRD-06.900701
Version 04. Original date: 24/05/2012. Version date: 31/12/2014. Valid version only on QMS site. Uncontrolled document when printed.
Procedure prepared by: BOS QHSES Manager. Approved by: BOS Managing Director. Validated by: BOS Quality Representative.
8 / 21
4.
2
MoC
d
o
c
um
entat
i
on
pr
o
c
e
ss
an
d
r
ev
i
e
w
All changes meeting the criteria of the present procedure
shall
be documented using the
BOS-FRM-06.0002
– Management Of Change
.
A MoC register recorded on BOS Intranet consolidates the details of all MoC raised by the Company. The
completed MoC forms and supporting documentation
shall
be archived for a period of 3 years from the date
of MoC closure.
MoC Coo
r
d
i
nato
r
shall
ensure that the MoC form, once filled out by
MoC
I
n
i
t
i
ato
r
, is given a MoC number
as follows :
MoC [ve
ss
el o
r
D
p
t a
br
ev
i
at
i
on] [YYYY]-[
i
n
c
r
e
m
ental n
umb
e
r
]
E.g: MoC AILET 2014-01
Vessels and Departments abbreviations are listed in
BOS-SPC-11.0002 – BOS Vessels and Department
Abbreviation
.
When change is supported by
MoC
I
n
i
t
i
at
i
o
r
and
L
i
ne Mana
g
e
r
(Step 1 passed), MoC forms and related
documents
shall
be :
- filed on BOS Intranet by the
MoC Coo
r
d
i
nato
r
,
- updated through the approval process,
- archived with all signatures when closed. Scanned, electronic files are accepted as records for MoC
purposes.
When
MoC
I
n
i
t
i
ato
r
’s work position is located onboard vessel, the M
oC
shall
also be filed on the vessel.
MoC forms that are indeed onboard a vessel
shall
be easily accessible on the Bridge and other applicable
locations.
Efficiency and proper application of MoC procedure will be checked during annual process review carried out
by
Qu
al
i
ty Re
pr
e
s
entat
i
ve
. Records of MoC and related documents
shall
be controlled at that time to
ensure that the changes have been implemented according to plans. Any improvement identified will be
recorded in the process review report.
4.
3
C
r
ee
pi
n
g
c
h
an
g
e
Incremental changes in a defined scope/system could over time pose a significant risk, and in the MoC
process is identified as a
c
r
ee
pi
n
g
c
h
an
g
e
. Creeping change is often hard to detect, due to changes
evolving over both time and by more than one initiator.
Examples could be:
- modifying several components within a system over time, such that if all changes were to be done
simultaneously a MoC would be required due to overall impact, whereas incremental steps does not require
a MoC.
- A significant number of
S
en
i
o
r
Off
i
c
e
rs
reaching the retirement age limit within a short range of time,
causing a recruitment challenge and a potential major loss of competence.
All
P
r
o
c
e
ss
O
w
ne
rs
have the responsibility to keep abreast of any changes in external
legislation/guidelines/practices over time, that could have a potential MoC impact, and incorporate such
changes in their process activities through MoC.
The principles of MoC
shall
be observed by all onshore and offshore personnel performing any changes to a
set scope/scenario/system in order to evaluate if the current change could be part of an incremental/creeping
change.
466