Safety Considerations Guide for Triconex General ... - ICEWeb

Safety Considerations Guide for Triconex General ... - ICEWeb Safety Considerations Guide for Triconex General ... - ICEWeb

iceweb.com.au
from iceweb.com.au More from this publisher
02.02.2015 Views

2 Chapter 1 Safety Concepts Overview Modern industrial processes tend to be technically complex, involve substantial energies, and have the potential to inflict serious harm to persons or property during a mishap. The IEC 61508 standard defines safety as “freedom from unacceptable risk.” In other words, absolute safety can never be achieved; risk can only be reduced to an acceptable level. Safety methods to mitigate harm and reduce risk include: • Changing the process or mechanical design, including plant or equipment layout • Increasing the mechanical integrity of equipment • Improving the basic process control system (BPCS) • Developing additional or more detailed training procedures for operations and maintenance • Increasing the testing frequency of critical components • Using a safety-instrumented system (SIS) • Installing mitigating equipment to reduce harmful consequences; for example, explosion walls, foams, impoundments, and pressure relief systems Safety Considerations Guide for Triconex General Purpose v2 Systems

Overview 3 Protection Layers Methods that provide layers of protection should be: • Independent • Verifiable • Dependable • Designed for the specific safety risk This figure shows how layers of protection can be used to reduce unacceptable risk to an acceptable level. The amount of risk reduction for each layer is dependent on the specific nature of the safety risk and the impact of the layer on the risk. Economic analysis should be used to determine the appropriate combination of layers for mitigating safety risks. Acceptable Risk Level Mechanical Integrity Inherent Process Risk 0 SV Lower Risk SIS Process BPCS* Higher Risk * BPCS–Basic process control system SIS–Safety-instrumented system SV–Safety (relief) valve Figure 1 Effect of Protection Layers on Process Risk When an SIS is required, one of the following should be determined: • Level of risk reduction assigned to the SIS • Safety integrity level (SIL) of the SIS Typically, a determination is made according to the requirements of the ANSI/ISA S84.01 or IEC 61508 standards during a process hazard analysis (PHA). Safety Considerations Guide for Triconex General Purpose v2 Systems

Overview 3<br />

Protection Layers<br />

Methods that provide layers of protection should be:<br />

• Independent<br />

• Verifiable<br />

• Dependable<br />

• Designed <strong>for</strong> the specific safety risk<br />

This figure shows how layers of protection can be used to reduce unacceptable risk to an<br />

acceptable level. The amount of risk reduction <strong>for</strong> each layer is dependent on the specific nature<br />

of the safety risk and the impact of the layer on the risk. Economic analysis should be used to<br />

determine the appropriate combination of layers <strong>for</strong> mitigating safety risks.<br />

Acceptable Risk Level<br />

Mechanical Integrity<br />

Inherent Process Risk<br />

0<br />

SV<br />

Lower Risk<br />

SIS<br />

Process<br />

BPCS*<br />

Higher Risk<br />

* BPCS–Basic process control system<br />

SIS–<strong>Safety</strong>-instrumented system<br />

SV–<strong>Safety</strong> (relief) valve<br />

Figure 1<br />

Effect of Protection Layers on Process Risk<br />

When an SIS is required, one of the following should be determined:<br />

• Level of risk reduction assigned to the SIS<br />

• <strong>Safety</strong> integrity level (SIL) of the SIS<br />

Typically, a determination is made according to the requirements of the ANSI/ISA S84.01 or<br />

IEC 61508 standards during a process hazard analysis (PHA).<br />

<strong>Safety</strong> <strong>Considerations</strong> <strong>Guide</strong> <strong>for</strong> <strong>Triconex</strong> <strong>General</strong> Purpose v2 Systems

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

Saved successfully!

Ooh no, something went wrong!