R E PLA CE ME N T O F S W C P L A NT-1 D RU M S C R E E N

S YST E M 72 00 0 43 00 0
( 7 NOS ) & LC P I N P LA NT- 2, JU B AI L
FAC TO RY A CC E P TA NC E T E ST P RO CE D U R E PA G E 7 O F 4 5

I NS -A B -DS - 219 RE V: 0

3. TEST METHODOLOGY

3.1. General Principles

This specification aims to ensure that the testing is performed consistently and accurately and
that all results are recorded.
Testing will continue, and faults corrected at the end of a test or series of tests as deemed
appropriate by ABB. Testing will only be interrupted for corrections to be carried out if further
testing is prevented until this has been completed.
Testing will be deemed to be completed once all the tests and any PQs raised as a result of
these tests have been signed off.
Refer to the typical Testing flow chart identified in section 3.2.
a) All hardware modules will be subject to formal configuration management control once
they have been incorporated into the system build.
b) The Query / Change Procedure will be used to manage queries raised from each stage of
testing.
c) A competent person independent of hardware and application program design,
development and production shall perform functional testing. Signatures will be
required at the appropriate sections of each test record.
d) Items that cannot be tested at any test stage(s) shall be recorded as a PQ.
e) Note that where target (client) hardware is not available for module & integrated or
factory acceptance testing, the test environment will be described and agreed with the
client. Additional site installation testing stages may be necessary to validate all
aspects of the integration of the target (client) hardware on site.
f) Full documentation of the test requirements and results are recorded and stored, so
that comprehensive records exist for the whole system, giving confidence that all
aspects of the system functionality has been satisfactorily tested.
g) Where testing has previously taken place, then reasonable credit for this may be taken
during subsequent test stages.
h) In all test stages, test coverage as identified within the respective tests will be the aim.
If it is not possible to achieve this test coverage, the reasons will be documented in the
test records.

i) Initial Quality Control Checks: The documents controlling the design of hardware and
application program modules (e.g. PQs) will be reviewed as part of the project quality
procedures. When these checks have been successfully completed, the Lead Engineer will
review and determine if the relevant hardware setup and application program is ready to
be released for test. Provided that it is appropriate, the Hardware and Software
Production Logs will be updated with the new module status recorded as “Authorised for
Test”.

j) Control of Hardware Setup And Application Program Released for Test: Hardware setup
and application program will always be tested against the current released and reviewed
reference documents. Where the changes require a significant re-test of the module, a PQ
will be raised and testing will be halted on that module until the updates have been

STATUS SECURITY LEVEL DOCUMENT ID. REV. LANG. PAGE

In Review Internal INS-AB-DS-219 0 en 7/45

© Copyright 2020 ABB. All rights reserved.
 REPL AC EM ENT O F SW C P L AN T-1 DR UM S CREEN
SYSTEM 72 00 043 00 0
( 7 N O S) & LC P IN PL A NT- 2, J U BAIL
FACTORY ACCEPTAN CE T EST PR OC ED URE PAG E 8 O F 45

I NS- AB -D S- 219 RE V: 0

completed. The testing of changes specified on PQs will be achieved by repeating, as

necessary, all or part of the test that generated the PQ.

3.2. Typical Testing Flowchart

Start

Pre-Test Meeting
Agree scope
Note exceptions

Test Stage
Test the application
software & hardware

Post-Test Meeting
Agree categorisation of
faults

Incorporate exceptions System passed back to

and re-submit for limited Test Status Fail correct and re-submit
Testing
Pass

Post-Test Meeting
Agree remedial work

Remedial Work
Implement remedial
actions

Remedial Fail
Retest

Pass

No Exceptions Yes Test Complete

Cleared

Figure 1 – Typical Testing Flowchart

STATUS SECURITY LEVEL DOCUMENT ID. REV. LANG. PAGE

In Review Internal INS-AB-DS-219 0 en 8/45

© Copyright 2020 ABB. All rights reserved.