13
USPAS January 2012 Controlling Risks: Safety Systems Controlling Risks Safety System Architectures

Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

  • Upload
    others

  • View
    1

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

USPAS January 2012 Controlling Risks: Safety Systems

Controlling Risks Safety System Architectures

Page 2: Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

Architectures

• High level implementation of system

• Takes in to account:

– Fault Tolerance

– Final control devices

– Physical Environment

– Constraints on physical design

– R-M-D (Redundancy Multiplicity Diversity)

USPAS January 2012 Controlling Risks: Safety Systems

Page 3: Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

RMD – Redundancy Multiplicity Diversity

• Three elements of the architecture are used to achieve the required safety integrity level

– Redundancy – is the use of identical safety instrumented functions to achieve a high safety reliability

– Multiplicity - is the use of multiple shutdown paths or protection devices

– Diversity – is the use if different types of devices to reduce the probability that multiple or redundant devices can be affected by common failure modes.

USPAS January 2012 Controlling Risks: Safety Systems

Page 4: Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

Architectures

Architecture Number of Units

Output Switches

Safety Fault Tolerance

Availability Fault Tolerance

Objectives

1oo1 1 1 0 0 Base Unit

1oo2 2 2 1 0 High Safety

2oo2 2 2 0 1 High Availability

1oo1D 1 2 0 – fail not detected 1 – fail detected

0 High Safety

2oo3 3 6 (4*) 1 1 Safety and Avilability

2oo2D 2 4 0 – fail not detected 1 – fail detected

1 Safety and Avilability Bias toward availability

1oo2D 2 4 1 0 – fail not detected 1 – fail detected

Safety and Avilability Bias toward safety

* Some implementations of 2oo3 use 4 output switches.

USPAS January 2012 Controlling Risks: Safety Systems

Page 5: Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

1oo1

A

λDU λDD

PFD ≈ λD * TI

λD

USPAS January 2012 Controlling Risks: Safety Systems

Page 6: Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

PFD for 1oo1

Systems failsDangerously

Unit failsDD

Unit failsDU

𝑃𝐹𝐷1𝑜𝑜1 = λ𝐷𝐷 ∗ 𝑅𝑇 ∗ λ𝐷𝑈 ∗ 𝑀𝑇

Where detected failures are repaired and undetected failures remain until end of life or revealed by test.

Integrating over mission time

𝑃𝐹𝐷𝑎𝑣𝑔 = λ𝐷𝐷 ∗ 𝑅𝑇 ∗ λ𝐷𝑈 ∗𝑀𝑇

2

USPAS January 2012 Controlling Risks: Safety Systems

Page 7: Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

1oo2 Block Diagram

Sensor B

Sensor A

Logic Solver A

Logic Solver B

OutputB

Output A

Shutoff A

Shutoff B

EnergySource

Hazard

DeviceSensed orMonitored

USPAS January 2012 Controlling Risks: Safety Systems

Page 8: Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

1oo2 Features

• Two circuits are wired to minimize the effect of dangerous unit failures – Input shorted – Output shorted – Logic error (hardwired)

• For de-energize to trip systems a series connection of two output circuits both need to fail dangerously for the system to fail dangerous

• A PLC implemented 1oo2 architecture may have one physical controller with redundancy implemented internally

USPAS January 2012 Controlling Risks: Safety Systems

Page 9: Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

PLC Implemented 1oo2

USPAS January 2012 Controlling Risks: Safety Systems

Page 10: Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

CIP=Common Industrial Protocol

USPAS January 2012 Controlling Risks: Safety Systems

Page 11: Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

Actuator Sensor Interface

AS-Interface

Slave IC

one connection

1 module

enclosure

D2 = actuator 1

D0 = sensor 1

D1 = sensor 2

D3 = actuator 2

WatchdogP0

Energy

up to 4 sensors

or/and

4 actuators

USPAS January 2012 Controlling Risks: Safety Systems

Courtesy of ASI International Foundation

Page 12: Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

Fault Tree 1oo2

Systems failsDangerously

A&B failsDDC

A&B failsDUC

A failsDN

B failsDN

A failsDDN

A failsDUN

B failsDDN

B failsDUN

• Detected faults – Repaired (RT)

• Undetected – Never repaired (MT)

USPAS January 2012 Controlling Risks: Safety Systems

Page 13: Controlling Risks Safety System Archetectures · 2015-03-05 · Architectures • High level implementation of system • Takes in to account: –Fault Tolerance –Final control

Story Time

• Subject

– Site Architectures

– Hardware Implementation

USPAS January 2012 Controlling Risks: Safety Systems