SAFETY MANUAL - Tuv-fs.com
SAFETY MANUAL - Tuv-fs.com SAFETY MANUAL - Tuv-fs.com
SAFETY MANUAL 4. CHECKLISTS This section provides a number of example checklists, these are provided as an aid for competent engineers. In general each checklist item should result in “yes”, where this is not the case a justification should be produced. 4.1 PRE-ENGINEERING CHECKLISTS The checklists provided within this section are applicable to the requirements. It should be recognised that the requirements will undergo refinement, particularly, in the early stages of a project. The information provided initially may be ‘outline’; in this case these checklists should be used to help identify where omission has occurred or where further refinement is necessary. 4.1.1 Scope Definition Checklist Description Reference Has a summary description of the intended application been provided Is the intended installation environment defined If so: • does this include both normal and possible abnormal conditions • does this include geographical distribution requirements Has a list of all the third-party equipment interfaces been provided and are definitions of both the protocol and the data to be interchanged established Are all of the plant interfaces defined, including the signal qualities and characteristics Have any special or abnormal conditions that exceed the normal equipment capabilities been highlighted to enable special measure to be implemented Is the presented information adequate to support the necessary level of understanding of the plant/EUC and its environment 2.2.1.1 2.2.1.1 and 3.13 2.2.1.1 2.2.1.1 2.2.1.1 2.2.1.1 Doc No P8094 Page 72 of 67 Issue 14 September 2003
SAFETY MANUAL 4.1.2 Functional Requirements Checklist Description Reference Is the definition of each of the required functions complete Are the interfaces, signals, and data associated with each function clearly identified Where a ‘tag referencing’ scheme is used for these signals, has a summary description of the naming convention been provided to facilitate an understanding of the role of the signal Have the performance requirements for each function, or collective functions, been defined Have the operating modes of the EUC, process or plant been clearly defined Have the functions required to operate in each plant operating-mode been identified Have the transitions between each plant operating-mode been defined Have the functions necessary to effect these transitions been established 2.2.1.2 2.2.1.2 2.2.1.2 2.2.1.2 2.2.1.2 2.2.1.2 2.2.1.2 4.1.3 Safety Requirements Checklist Description Reference Have all of the functional requirements been allocated a required safety requirements class Has the safety-related timing for each safety-related function, including process safety time (PST) and fault tolerance period, been established Have the safety requirements been approved Are there clear definitions of the external interfaces involved in each of the 2.2.1.3 2.2.1.3 2.2.1.3 2.2.1.3 Doc Number P8094 Issue 14 September 2003 Page 73 of 67
- Page 24 and 25: SAFETY MANUAL 1.3.1 Safety and Func
- Page 26 and 27: SAFETY MANUAL The additional elemen
- Page 28 and 29: SAFETY MANUAL The TMR architecture
- Page 30 and 31: SAFETY MANUAL 2.2.1 Safety Lifecycl
- Page 32 and 33: SAFETY MANUAL Tools used within the
- Page 34 and 35: SAFETY MANUAL 2.2.1.9 Safety System
- Page 36 and 37: SAFETY MANUAL • Method of detecti
- Page 38 and 39: SAFETY MANUAL 2.3.1 Competency The
- Page 40 and 41: SAFETY MANUAL 3.2.1 Safety-Related
- Page 42 and 43: SAFETY MANUAL Pulse Generator 8444,
- Page 44 and 45: SAFETY MANUAL 3.2.2 High-Density I/
- Page 46 and 47: SAFETY MANUAL 3.2.3 Analog Input Sa
- Page 48 and 49: SAFETY MANUAL 3.2.7 NFPA 86 Require
- Page 50 and 51: SAFETY MANUAL shall be provided for
- Page 52 and 53: SAFETY MANUAL 3.4 ACTUATOR CONFIGUR
- Page 54 and 55: SAFETY MANUAL 3.6.1.2 Composite Sca
- Page 56 and 57: SAFETY MANUAL Power Fail Timeout (P
- Page 58 and 59: SAFETY MANUAL • Access to the wor
- Page 60 and 61: SAFETY MANUAL 3.11.1 IEC1131 Workbe
- Page 62 and 63: SAFETY MANUAL 3.11.3 Testing of New
- Page 64 and 65: SAFETY MANUAL 3.11.4 Application De
- Page 66 and 67: SAFETY MANUAL Where the interaction
- Page 68 and 69: SAFETY MANUAL In addition to Normal
- Page 70 and 71: SAFETY MANUAL 1ºF/min Table 8 - Cl
- Page 72 and 73: SAFETY MANUAL 2. Alternatively, the
- Page 76 and 77: SAFETY MANUAL Description Reference
- Page 78 and 79: SAFETY MANUAL Description Reference
- Page 80 and 81: SAFETY MANUAL 4.2.4 High Density Mo
- Page 82 and 83: SAFETY MANUAL 5. PREVIOUSLY ASSESSE
<strong>SAFETY</strong> <strong>MANUAL</strong><br />
4.1.2 Functional Requirements Checklist<br />
Description<br />
Reference<br />
Is the definition of each of the required<br />
functions <strong>com</strong>plete<br />
Are the interfaces, signals, and data<br />
associated with each function clearly<br />
identified<br />
Where a ‘tag referencing’ scheme is used<br />
for these signals, has a summary<br />
description of the naming convention been<br />
provided to facilitate an understanding of<br />
the role of the signal<br />
Have the performance requirements for<br />
each function, or collective functions, been<br />
defined<br />
Have the operating modes of the EUC,<br />
process or plant been clearly defined<br />
Have the functions required to operate in<br />
each plant operating-mode been identified<br />
Have the transitions between each plant<br />
operating-mode been defined Have the<br />
functions necessary to effect these<br />
transitions been established<br />
2.2.1.2<br />
2.2.1.2<br />
2.2.1.2<br />
2.2.1.2<br />
2.2.1.2<br />
2.2.1.2<br />
2.2.1.2<br />
4.1.3 Safety Requirements Checklist<br />
Description<br />
Reference<br />
Have all of the functional requirements<br />
been allocated a required safety<br />
requirements class<br />
Has the safety-related timing for each<br />
safety-related function, including process<br />
safety time (PST) and fault tolerance period,<br />
been established<br />
Have the safety requirements been<br />
approved<br />
Are there clear definitions of the external<br />
interfaces involved in each of the<br />
2.2.1.3<br />
2.2.1.3<br />
2.2.1.3<br />
2.2.1.3<br />
Doc Number P8094<br />
Issue 14 September 2003 Page 73 of 67