SAFETY MANUAL - Tuv-fs.com
SAFETY MANUAL - Tuv-fs.com
SAFETY MANUAL - Tuv-fs.com
- No tags were found...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>SAFETY</strong> <strong>MANUAL</strong><br />
Description<br />
Reference<br />
If active and standby modules are to be<br />
installed simultaneous, has allowance been<br />
included for the effect on the accuracy<br />
Has the allocation of signals to I/O modules<br />
and channels considered each of the signals’<br />
function<br />
Ensure that potential module and power group<br />
failures result in either continued safety<br />
function or fail-safe operation.<br />
Do safety-related inputs and outputs use only<br />
those configurations identified as safetyrelated<br />
Are there any safety-related, normally deenergised<br />
outputs<br />
If so have redundant power sources, power<br />
failure warning and line monitoring been<br />
provided<br />
Have sensor fault conditions been taken into<br />
account<br />
Have actuator fault conditions been taken into<br />
account<br />
Have field power supplies conforming to<br />
EN6101-1 or EN 60950 been used<br />
3.3 and<br />
3.4<br />
3.2.1<br />
3.2.4<br />
3.3<br />
3.4<br />
3.14<br />
4.2.2 Language Selection Checklist<br />
Description<br />
Reference<br />
Has application programming for safety-related<br />
sections been limited to the FB programming<br />
language<br />
Are any functions not in the previously tested<br />
libraries required If so has provision been<br />
made to adequately test these functions<br />
Ensure that the programming languages<br />
classified as non-safety (‘C’ and SFC) are NOT<br />
used for safety-related projects<br />
3.11.2<br />
3.11.3<br />
3.11.2<br />
Doc No P8094 Page 76 of 67<br />
Issue 14 September 2003
Change language