Safety Considerations Guide for Triconex General ... - ICEWeb

More documents

Recommendations

Info

24 Chapter 2 Application Guidelines 6 Print all logic elements and verify that the changes to networks within each element do not affect other sections of the application. 7 Test the changes according to the test specification using the Emulator Panel. For details, see the TriStation 1131 Developer’s Guide. 8 Write a test report. 9 Review and audit all changes and test results with the SCCC. 10 When approved by the SCCC, download the changes to the controller. • You may make minor changes online only if the changes are absolutely necessary and are tested thoroughly. • To enable a Download Change command, select the Enable Programming and Control option in the Set Programming Mode dialog box on the Controller Panel if it is not already selected. Note Changing the operating mode to PROGRAM generates an alarm to remind the operator to return the operating mode to RUN as soon as possible after the Download Change. For more information, see Programming Permitted Alarm on page 59. 11 Save the downloaded project in the TriStation 1131 software and back up the project. 12 Archive two copies of the project file and all associated documentation. Maintenance Overrides Three methods can be used to check safety-critical devices connected to controllers: • Special switches are connected to the inputs on a controller. These inputs deactivate the actuators and sensors undergoing maintenance. The maintenance condition is handled in the logic of the control application. • Sensors and actuators are electrically disconnected from a controller and manually checked using special measures. • Communication to a controller activates the maintenance override condition. This method is useful when space is limited; the maintenance console should be integrated with the operator display. TÜV recommends that the TriStation 1131 workstation used for programming is not also used for maintenance. Using Triconex Communication Capabilities For maintenance overrides, two options for connection are available: • DCS (distributed control system) connection using an approved protocol. • TriStation 1131 PC connection, which requires additional, industry-standard safety measures in a controller to prevent downloading a program change during maintenance intervals. For more information, see Alarm Usage on page 59. Safety Considerations Guide for Triconex General Purpose v2 Systems
Guidelines for Triconex Controllers 25 Table 3 describes the design requirements for handling maintenance overrides when using Triconex communication capabilities. Table 3 Design Requirements for Maintenance Override Handling Design Requirements Control program logic and the controller configuration determine whether the desired signal can be overridden. Control program logic and/or system configuration specify whether simultaneous overriding in independent parts of the application is acceptable. Controller activates the override. The operator should confirm the override condition. Direct overrides on inputs and outputs are not allowed, but should be checked and implemented in relation to the application. Multiple overrides in a controller are allowed as long as only one override applies to each safety-critical group. The controller alarm should not be overridden. DCS warns the operator about an override condition. The operator continues to receive warnings until the override is removed. A second way to remove the maintenance override condition should be available. If urgent, a maintenance engineer may remove the override using a hard-wired switch. During an override, proper operating measures should be implemented. The time span for overriding should be limited to one shift (typically no longer than eight hours). A maintenance override switch (MOS) light on the operator console should be provided (one per controller or process unit). Responsible Person TriStation 1131 DCS Software Project Engineer, Commissioner Project Engineer Operator, Maintenance Engineer Project Engineer Project Engineer, Commissioner Project Engineer Project Engineer, Commissioner, DCS, TriStation 1131 software Project Engineer, Commissioner Project Engineer, Type Approval Maintenance Engineer, Type Approval Project Engineer, Type Approval N/A Maintenance Engineer, Type Approval Safety Considerations Guide for Triconex General Purpose v2 Systems
Page 1 and 2: Triconex General Purpose v2 Systems
Page 3 and 4: Contents Preface vii Summary of Sec
Page 5 and 6: Contents v Partitioned Processes. .
Page 7 and 8: Preface This guide provides informa
Page 9 and 10: Preface ix • All other requests a
Page 11 and 12: 1 Safety Concepts Overview 2 Hazard
Page 13 and 14: Overview 3 Protection Layers Method
Page 15 and 16: Hazard and Risk Analysis 5 Hazard a
Page 17 and 18: Hazard and Risk Analysis 7 Sample S
Page 19 and 20: Hazard and Risk Analysis 9 Safety L
Page 21 and 22: Hazard and Risk Analysis 11 • Eac
Page 23 and 24: Safety Standards 13 CAN/CSA-C22.2 N
Page 25 and 26: 2 Application Guidelines Overview 1
Page 27 and 28: General Guidelines 17 General Guide
Page 29 and 30: Guidelines for Triconex Controllers
Page 33: Guidelines for Triconex Controllers
Page 41 and 42: 3 Fault Management Overview 32 Syst
Page 43 and 44: System Diagnostics 33 System Diagno
Page 45 and 46: Operating Modes 35 Operating Modes
Page 47 and 48: Module Diagnostics 37 Analog Output
Page 49 and 50: Module Diagnostics 39 Calculation f
Page 51 and 52: Module Diagnostics 41 External Comm
Page 53 and 54: 4 Application Development Developme
Page 55 and 56: Development Guidelines 45 Array Ind
Page 57 and 58: Setting Scan Time 47 application. T
Page 59 and 60: Sample Safety-Shutdown Programs 49
Page 69 and 70: Alarm Usage 59 Alarm Usage To imple
Page 71 and 72: A Triconex Peer-to-Peer Communicati
Page 73 and 74: Data Transfer Time 63 Data Transfer
Page 75 and 76: Data Transfer Time 65 A typical dat
Page 77 and 78: Examples of Peer-to-Peer Applicatio
Page 79 and 80: B HART Communication Overview 70 HA
Page 81 and 82: HART Position Paper from TÜV Rhein
Page 83 and 84: HART Position Paper from TÜV Rhein
Page 85 and 86:
HART Position Paper from TÜV Rhein
Page 87 and 88:
HART Position Paper from TÜV Rhein
Page 89 and 90:
C Safety-Critical Function Blocks O
Page 91 and 92:
SYS_CRITICAL_IO 81 SYS_CRITICAL_IO
Page 93 and 94:
SYS_CRITICAL_IO 83 Library Trident
Page 95 and 96:
SYS_CRITICAL_IO 85 END_IF ; PREVIOU
Page 97 and 98:
SYS_SHUTDOWN 87 Output Parameters (
Page 99 and 100:
SYS_SHUTDOWN 89 * the safety system
Page 101 and 102:
SYS_SHUTDOWN 91 ALARM_DISABLED_POIN
Page 103 and 104:
SYS_VOTE_MODE 93 Example For shutdo
Page 105 and 106:
Index A abbreviations, list of viii
Page 107 and 108:
Index 97 N NFPA 85 12 O operating m
Page 110:
Invensys Operations Management 5601
show all

Safety Considerations Guide for Triconex General ... - ICEWeb

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?