WEBVTT

1
00:00:00.000 --> 00:00:02.901
A supplier brochure, design calculation

2
00:00:03.021 --> 00:00:06.285
and executed test record are different
evidence types.

3
00:00:06.405 --> 00:00:08.935
Start with the question you need to
answer.

4
00:00:09.055 --> 00:00:12.169
A generic brochure may describe a product
family

5
00:00:12.289 --> 00:00:15.169
without identifying the purchased
configuration.

6
00:00:15.289 --> 00:00:18.383
A calculation may rely on conditions that
do

7
00:00:18.503 --> 00:00:20.503
not apply to our process.

8
00:00:20.623 --> 00:00:24.676
An executed record needs traceable results
and a clear method.

9
00:00:24.796 --> 00:00:28.871
More pages do not necessarily provide more
relevant evidence.

10
00:00:29.491 --> 00:00:32.456
Where third-party validation protocols are
used,

11
00:00:32.576 --> 00:00:35.223
site personnel should check their
suitability

12
00:00:35.343 --> 00:00:38.778
and alignment with internal procedures
before approval.

13
00:00:38.898 --> 00:00:41.693
In our example, the vendor protocol omits

14
00:00:41.813 --> 00:00:44.048
the required sensor-failure challenge.

15
00:00:44.168 --> 00:00:47.325
Record the gap and arrange a justified
supplement

16
00:00:47.445 --> 00:00:49.739
rather than accepting a complete stamp.

17
00:00:49.859 --> 00:00:53.209
DQ can identify this future verification
need

18
00:00:53.329 --> 00:00:56.635
while supplier documentation is still
being developed.

19
00:00:56.755 --> 00:00:59.465
Site responsibility does not disappear

20
00:00:59.585 --> 00:01:02.644
because a specialist supplier prepared the
template.

21
00:01:03.264 --> 00:01:06.912
Factory acceptance testing can provide
useful evidence,

22
00:01:07.032 --> 00:01:09.784
but it is not a replacement label for DQ.

23
00:01:09.904 --> 00:01:14.320
Any planned reuse of appropriate factory
tests needs a documented

24
00:01:14.440 --> 00:01:18.301
justification that considers the
applicable configuration

25
00:01:18.421 --> 00:01:22.068
and whether transport or installation can
affect the function.

26
00:01:22.188 --> 00:01:24.541
Some checks may still be needed on site.

27
00:01:24.661 --> 00:01:27.754
For example, a factory record cannot
demonstrate

28
00:01:27.874 --> 00:01:31.010
that the site’s final utility connection
is correct.

29
00:01:31.130 --> 00:01:34.542
Keep the evidence claim within what was
actually examined.

30
00:01:35.162 --> 00:01:38.469
The factory report refers to controller
version one,

31
00:01:38.589 --> 00:01:41.426
while the supplied design proposes version
two.

32
00:01:41.546 --> 00:01:45.407
Do not automatically accept everything or
discard everything.

33
00:01:45.527 --> 00:01:49.517
Identify what changed, assess effects on
relevant functions

34
00:01:49.637 --> 00:01:52.303
and decide which evidence remains
applicable.

35
00:01:52.423 --> 00:01:55.133
Document the rationale and additional
work.

36
00:01:55.253 --> 00:01:58.005
This focused review is more defensible
than

37
00:01:58.125 --> 00:02:00.429
deciding from the version number alone.

38
00:02:00.549 --> 00:02:03.855
The same reasoning applies to substituted
instruments,

39
00:02:03.975 --> 00:02:06.429
valves and software configurations.