Information Technology Reference
In-Depth Information
The access rights for the test system are not the same as those for the productive
system. Technical staff, trainers etc. will not obtain access to the productive
system. Vice versa the personnel from business units having access rights to the
test system are to be supplemented by additional users in the future.
7.3.4.7 Training
User training can possibly happen on the test system. This is an opportunity to let
participants of basic training take part in the test process. Or else training takes
place on a separate trainings system, being a complete mirror of the test system.
This normally means putting the training on hold until the test system has been
accepted to avoid undesired errors during training. As a consequence there would
be a delay between the acceptance of the test system (see below) and putting the
system into production due to intermediate training.
Training documents and work instructions for the application can be deduced
from the process documentation (see above). Training data come from the overall
data uploads.
7.3.4.8 Acceptance
Generally, when accepting a new test system the same rules apply as described in
principle already elsewhere. Since for such systems short cuts or variants are
possible the following options have to be checked in particular:
Which are the relevant acceptance criteria?
Does a declaration of operational readiness suffice?
Is a pilot operation required?
These and similar questions have to be clarified during a clearance meeting
where at the same time the test system should be approved for migration to the
productive system.
7.3.4.9 Migration
Building the test system and data upload strategy are organised in such a way that a
seamless transfer to the productive system should be possible. In this way any
customising does not have to be repeated for example.
The first action after acceptance thus is the backup of the latest version of the test
system: software, operating system, data base and all utilities. The whole package is
then uploaded on the initially empty productive system. Thereafter data quality
assurance takes place verifying the completeness and contents of the data upload
with a possible evaluation or initialisation of data clean-up measures. Only after this
the system can be cleared for productive usage.
