QA-M-028 Quality Assurance Manual Computer Applications

Table of Contents

1. General
2. References

1. General

This section covers the quality-related requirements for the control of computer applications within Company.

The Information Systems Group shall administer in the Asset register all third party computer application programs together with issue number, date and relevant associated information like number of software licences, authorised users and location of original programs and manuals.

This is done to ensure that contracts with software suppliers are not violated and original material can be retrieved and returned to supplier in case upgrades of programs are acquired.

All computer application programs that perform a design and/or engineering function are further controlled as follows:

• the Engineering and the Process Department maintain each an index of all engineering/design programs including version number, the control status and if applicable the cross reference to the relevant codes, norms and standards that affect them.
• the form ref. 28.2.4 shall be completed for new software developments or major changes on existing software.
• program verification by the functional owner on the proper functioning of new programs and new versions of existing programs shall be evident.
• only those applications that are authorised by the responsible Discipline/ Department Manager are made available to users. In general through installation on the computer network and individual assignment of access authority.
• the Departmental/Discipline Manager shall ensure, if appropriate, that applications are regularly updated to include the latest issues of codes, standards, norms and laws that affect them (ref. 28.2.2).
• computer programs can always contain bugs irrespective of the level of checking the proper functioning. Therefore checks are carried out by the lead engineer by means of checking the input, reviewing the output and comparison with alternative calculations, as appropriate. The documentation of these checks will be held by the lead engineer, in the project file (see ref. 28.2.3).
• possible bugs/faults in the programs are immediately communicated to the responsible Departmental/Discipline Manager. He is responsible to take appropriate action. Programs, producing unreliable results, are removed from the network to prevent inadvertent use.
• Project specific requirements for the use of programs are described in the Project Procedure and Execution Manual (e.g. IT plan), as appropriate.

2. References