Safety Considerations Guide, Tricon v9.0 - Tuv-fs.com
Safety Considerations Guide, Tricon v9.0 - Tuv-fs.com Safety Considerations Guide, Tricon v9.0 - Tuv-fs.com
30 Guidelines for Tricon Controllers• Maintenance instructions outlined in the Tricon Planning & InstallationGuide should be followed.• If degradation to dual mode occurs, continued operation without repairshould be limited to 1500 hours (two months).• If degradation to single mode occurs, continued operation without repairshould be limited to one hour.• The GATENB function allows external hosts to write selected aliasedvariables even when the remote mode is false. A network using theGATENB function should be thoroughly validated to ensure that only theintended aliased variable range is used.Additional Fire and Gas GuidelinesProject Change and Control• Analog input cards with current loop terminations should be used to readdigital inputs. Opens and shorts in the wiring to the field devices should bedetectable. The Triconex library function, LINEMNTR, should be used tosimplify program development.• A controller should be powered by two independent sources.• If outputs are normally de-energized, a Supervised Digital Output Moduleshould be used to verify proper connection to the final control element andto check the load and the wiring for potential shorts.• If degradation to dual mode or single mode occurs, repairs should be timelyand limits for maximum time in degraded mode should not be imposed toensure maximum availability.A change to a project, however minor, should comply with the guidelines of yourorganization’s change control committee. The following steps are recommended:1 Generate a change request defining all changes and reasons for changes, thenobtain approval for the changes from the Safety Change Control Committee(SCCC).2 Develop a specification for changes, including a test specification, then obtainapproval for the specification from the SCCC.3 Make the appropriate changes to the project, including those related to design,operation, or maintenance documentation.Tricon Safety Considerations Guide
Guidelines for Tricon Controllers 314 To verify that the configuration in the controller matches the last downloadedconfiguration, use the Upload and Verify command on the Control Panel. Fordetails, see section “Upload and Verify” in the TriStation 1131 Developer'sGuide for Tricon Systems.5 Compare the configuration in your project with the configuration that was lastdownloaded to the controller by printing the Configuration Differences reportfrom the Configuration editor. For details, see section “Compare to LastDownload” in the TriStation 1131 Developer's Guide for Tricon Systems.6 Print all logic elements and verify that the changes to networks within eachelement do not affect other sections of the application.7 Test the changes according to the test specification by using the EmulatorControl Panel.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 on-line only if the changes are absolutelynecessary and are tested thoroughly.• To enable a Download Change command, select the EnableProgramming option in the Set Programming Mode dialog box on theControl Panel if it is not already selected.Note Changing the operating mode to PROGRAM should generate an alarm toremind the operator to return the operating mode to run as soon as possible afterthe Download Change. For more information, see section “Programming PermittedAlarm” on page 68.11 Save the downloaded project in TriStation and back up the project.12 Archive two copies of the project file and all associated documentation.Chapter 2Application Guidelines
- Page 1 and 2: TriconVersion 9Safety Consideration
- Page 3: AcknowledgementTriconex acknowledge
- Page 6 and 7: viRelated DocumentsRelated Document
- Page 8 and 9: viiiHow to Contact TriconexHow to C
- Page 10: xTrainingFor Turbomachinery Systems
- Page 13 and 14: xiCONTENTSAbout This Guide ........
- Page 15 and 16: xiiiAnalog Input Module Alarms ....
- Page 17 and 18: CHAPTER 1Safety ConceptsThis chapte
- Page 19 and 20: Safety Overview 3Protection LayersT
- Page 21 and 22: Hazard and Risk Analysis 5Hazard an
- Page 23 and 24: Hazard and Risk Analysis 7Completio
- Page 25 and 26: Hazard and Risk Analysis 9Equation
- Page 27 and 28: Hazard and Risk Analysis 11Flowchar
- Page 29 and 30: Hazard and Risk Analysis 13Some key
- Page 31 and 32: Safety Standards 15Safety Standards
- Page 33 and 34: Safety Standards 17Application-Spec
- Page 35 and 36: CHAPTER 2Application GuidelinesThis
- Page 37 and 38: General Guidelines 21• Under cert
- Page 39 and 40: Guidelines for Tricon Controllers 2
- Page 41 and 42: Guidelines for Tricon Controllers 2
- Page 43 and 44: Guidelines for Tricon Controllers 2
- Page 45: Guidelines for Tricon Controllers 2
- Page 49 and 50: Guidelines for Tricon Controllers 3
- Page 51 and 52: Guidelines for Tricon Controllers 3
- Page 53 and 54: CHAPTER 3Fault ManagementThis chapt
- Page 55 and 56: System Diagnostics 39System Diagnos
- Page 57 and 58: Operating Modes 41Operating ModesEa
- Page 59 and 60: Module Diagnostics 43Module Diagnos
- Page 61 and 62: Module Diagnostics 45Relay Output M
- Page 63 and 64: Module Diagnostics 47System Attribu
- Page 65 and 66: CHAPTER 4Application DevelopmentThi
- Page 67 and 68: Important TriStation Commands 51Imp
- Page 69 and 70: Setting Scan Time 53Setting Scan Ti
- Page 71 and 72: Sample Safety-Shutdown Programs 55S
- Page 73 and 74: Sample Safety-Shutdown Programs 57I
- Page 75 and 76: Sample Safety-Shutdown Programs 59A
- Page 77 and 78: Sample Safety-Shutdown Programs 61P
- Page 79 and 80: Sample Safety-Shutdown Programs 63O
- Page 81 and 82: Sample Safety-Shutdown Programs 65D
- Page 83 and 84: Sample Safety-Shutdown Programs 67P
- Page 85 and 86: APPENDIX APeer-to-Peer Communicatio
- Page 87 and 88: Data Transfer Time 71ParameterTS =S
- Page 89 and 90: Examples of Peer-to-Peer Applicatio
- Page 91 and 92: TR_CRITICAL_IO Function Block 75TR_
- Page 93 and 94: TR_CRITICAL_IO Function Block 77Par
- Page 95 and 96: TR_CRITICAL_IO Function Block 79Str
30 <strong>Guide</strong>lines for <strong>Tricon</strong> Controllers• Maintenance instructions outlined in the <strong>Tricon</strong> Planning & Installation<strong>Guide</strong> should be followed.• If degradation to dual mode occurs, continued operation without repairshould be limited to 1500 hours (two months).• If degradation to single mode occurs, continued operation without repairshould be limited to one hour.• The GATENB function allows external hosts to write selected aliasedvariables even when the remote mode is false. A network using theGATENB function should be thoroughly validated to ensure that only theintended aliased variable range is used.Additional Fire and Gas <strong>Guide</strong>linesProject Change and Control• Analog input cards with current loop terminations should be used to readdigital inputs. Opens and shorts in the wiring to the field devices should bedetectable. The <strong>Tricon</strong>ex library function, LINEMNTR, should be used tosimplify program development.• A controller should be powered by two independent sources.• If outputs are normally de-energized, a Supervised Digital Output Moduleshould be used to verify proper connection to the final control element andto check the load and the wiring for potential shorts.• If degradation to dual mode or single mode occurs, repairs should be timelyand limits for maximum time in degraded mode should not be imposed toensure maximum availability.A change to a project, however minor, should <strong>com</strong>ply with the guidelines of yourorganization’s change control <strong>com</strong>mittee. The following steps are re<strong>com</strong>mended:1 Generate a change request defining all changes and reasons for changes, thenobtain approval for the changes from the <strong>Safety</strong> Change Control Committee(SCCC).2 Develop a specification for changes, including a test specification, then obtainapproval for the specification from the SCCC.3 Make the appropriate changes to the project, including those related to design,operation, or maintenance documentation.<strong>Tricon</strong> <strong>Safety</strong> <strong>Considerations</strong> <strong>Guide</strong>