WEBVTT

1
00:00:00.000 --> 00:00:02.276
Collect the supplier instructions

2
00:00:02.396 --> 00:00:07.637
and maintenance requirements applicable to
the installed model and revision.

3
00:00:07.757 --> 00:00:11.661
A large folder is not necessarily a usable
handover.

4
00:00:11.781 --> 00:00:15.437
Check that the team can identify the
correct document

5
00:00:15.557 --> 00:00:19.419
and that referenced drawings or schedules
are available.

6
00:00:19.539 --> 00:00:22.642
Superseded manuals should not silently
become

7
00:00:22.762 --> 00:00:26.486
the basis for maintaining the installed
configuration.

8
00:00:27.106 --> 00:00:29.175
For the vessel control system,

9
00:00:29.295 --> 00:00:32.606
identify the relevant hardware, software
version

10
00:00:32.726 --> 00:00:36.657
and configuration baseline through the
approved approach.

11
00:00:36.777 --> 00:00:40.087
A version screenshot can support
identification,

12
00:00:40.207 --> 00:00:44.138
but it does not establish that
permissions, audit trails,

13
00:00:44.258 --> 00:00:47.361
alarms or backup restoration work
adequately.

14
00:00:47.481 --> 00:00:51.757
Plan the applicable computerised-system
validation separately;

15
00:00:51.877 --> 00:00:55.050
this introductory installation module does
not

16
00:00:55.170 --> 00:00:57.859
claim complete Annex Eleven compliance.

17
00:00:58.479 --> 00:01:03.445
Link the supplier maintenance requirements
to responsible site functions

18
00:01:03.565 --> 00:01:07.565
and the resources needed for the next
authorized activity.

19
00:01:07.685 --> 00:01:10.444
For our case, a rear instrument requires

20
00:01:10.564 --> 00:01:13.667
a specific removal tool and accessible
space.

21
00:01:13.787 --> 00:01:17.097
Record missing resources and their
implications.

22
00:01:17.217 --> 00:01:20.252
Do not describe a task as established
merely

23
00:01:20.372 --> 00:01:22.993
because a supplier manual mentions it.

24
00:01:23.613 --> 00:01:27.130
A supplier test may be useful when its
method, data

25
00:01:27.250 --> 00:01:31.388
and configuration are applicable and its
reuse is justified.

26
00:01:31.508 --> 00:01:35.646
Consider what transport and installation
could have changed.

27
00:01:35.766 --> 00:01:38.938
A factory photograph cannot prove that a
field

28
00:01:39.058 --> 00:01:42.507
connection was installed correctly after
shipment.

29
00:01:42.627 --> 00:01:45.316
Retain the rationale for what is reused

30
00:01:45.436 --> 00:01:48.264
and the site verification still required.