SAFETY MANUAL - Tuv-fs.com

SAFETY MANUAL - Tuv-fs.com SAFETY MANUAL - Tuv-fs.com

23.01.2015 Views

SAFETY MANUAL 4.2.4 High Density Module Configuration Checklist Description Reference For each of the I/O signal types, do the I/O module settings provide the correct characteristics and behaviour for the intended sensor or actuator Have the thresholds been verified with both increasing and decreasing field signal levels and with margins to allow for the accuracy and calibration to ensure that they do not result in overlapping bands Is consistent use made of front panel indicators 3.7.1 3.7.1 3.7.1 Ensure that “green” is not used for abnormal conditions. Have the update rates been set such that they are acceptable for fault annunciation requirements and that the rates result in the system’s response within the PST E. Have the settings been defined according to a field device type setting, and minimal use has been made of channel specific settings For any non-standard configuration settings, have tests been defined and executed to 100% test the required operation 3.7.1 3.7.1 3.7.1 4.2.5 Processor and Other Configuration Description Reference If Peer-to-Peer communications is used, are the timeouts set to ensure a response time less than that required by PST E 3.10 Has the diagnostic access password been set 3.6.2 Password: Has the security has been set up on the IEC1131 TOOLSET 3.11.1 Engineering supervisor password Engineer/ Application programmer password Maintenance engineer password General user password Doc No P8094 Page 78 of 67 Issue 14 September 2003

SAFETY MANUAL 4.2.6 Testing Description Reference Have all of the functions used been fully tested 3.11.2 and 3.11.3 Has the program been fully tested The code checker can be used to highlight which programs have changed during modification - see para. 3.9.12.2. 3.11.6 Record the application scan time (read from the Toolset display) Record the system throughput time (output SOE – input SOE) Record the system throughput time where Peer-to-Peer communications is required (output SOE – input SOE) Are the scan and response times in accordance with the PSTE requirements (< ½ PST E) Have the climatic conditions been verified to be suitable 3.13 Doc Number P8094 Issue 14 September 2003 Page 79 of 67

<strong>SAFETY</strong> <strong>MANUAL</strong><br />

4.2.6 Testing<br />

Description<br />

Reference<br />

Have all of the functions used been fully tested 3.11.2<br />

and<br />

3.11.3<br />

Has the program been fully tested The code<br />

checker can be used to highlight which<br />

programs have changed during modification -<br />

see para. 3.9.12.2.<br />

3.11.6<br />

Record the application scan time (read from the<br />

Toolset display)<br />

Record the system throughput time (output SOE<br />

– input SOE)<br />

Record the system throughput time where<br />

Peer-to-Peer <strong>com</strong>munications is required<br />

(output SOE – input SOE)<br />

Are the scan and response times in accordance<br />

with the PSTE requirements (< ½ PST E)<br />

Have the climatic conditions been verified to be<br />

suitable<br />

3.13<br />

Doc Number P8094<br />

Issue 14 September 2003 Page 79 of 67

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!