23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Functional Safety 21-11<br />

TABLE 21.6<br />

FMEA of Network<br />

Network Failure Failure Mode Description Effect (Hazard)<br />

Data corruption Single bit destroyed EMC effect<br />

destroys bit<br />

Loss<br />

Incorrect sequence<br />

Repetition<br />

Delay<br />

Insertion<br />

Coupling between safety<br />

and non-safety-related<br />

messages<br />

Broken wire or<br />

gateway problem,<br />

wrong routing<br />

Buffering of messages<br />

in a gateway<br />

Wrong network<br />

configuration<br />

Aging of wire or<br />

hard software<br />

problem in<br />

gateway<br />

The gateway cannot<br />

process more than<br />

a single message<br />

at the same time<br />

A non-authorized<br />

message looks like<br />

a safety-related<br />

message<br />

Change of message can<br />

produce malfunction at<br />

receiver side<br />

A safety-related message<br />

is not or in the wrong<br />

sequence or more often<br />

transmitted to the<br />

receiver<br />

The delayed or inserted<br />

message includes an<br />

outdated value<br />

Receiver performs<br />

a non-intended<br />

safety-related action being<br />

triggered from a nonsafety-related<br />

sender<br />

According to [PHO97], the probability of a bit being destroyed on shielded twisted pair cables is p = 10 −5 .<br />

It is assumed that v = 10 safety-related messages are sent every second. The rate of single bit transmission<br />

error U is<br />

U<br />

1<br />

−4<br />

= p * v = 10 /s (21.1)<br />

In other words, every 10,000.s, a single transmission error occurs and the risk of a single bit being<br />

destroyed per second is 10 −4 . The probability that two bits are destroyed within 1.s is 10 −9 , assuming that<br />

probabilities are independent and therefore p 2 is inserted into the aforementioned formula instead of p.<br />

As a result, the safety integrity of a safety measure must be chosen so that the residual failure probability<br />

of a message is at least below 10 −7 h −1 to reach the target SIL3.<br />

Also, failures on node side must be investigated. That is, a hazard analysis and risk analysis has also<br />

to be performed to identify failures on the node itself (Table 21.7). In IEC61508, part 2, a detailed list<br />

is provided that gives information on the various failures in the components of a microcontroller that<br />

must be taken into consideration. Such a hazard analysis is also carried out by means of FMEA.<br />

TABLE 21.7<br />

FMEA of Node Hardware<br />

Hardware<br />

Component Failure Mode Description Effect (Hazard)<br />

Controller Malfunction Due to high temperature, the<br />

ALU of the CPU delivers<br />

wrong values<br />

Memory Wrong values stored Stuck at fault in the volatile<br />

memory results in wrong<br />

values stored<br />

Input device<br />

Output device to<br />

network interface<br />

Output device to<br />

actuator<br />

Wrong data read by<br />

controller<br />

Corrupted messages<br />

sent or received<br />

Failure of output switch<br />

Stuck at failure or shortcut<br />

failure between different<br />

channels<br />

Stochastic and systematic<br />

failures during data transfer<br />

Stuck at failure or shortcut<br />

failure in the output circuit<br />

Wrong operation<br />

of device<br />

Wrong operation<br />

of device<br />

Wrong operation<br />

of device<br />

Wrong operation<br />

of device<br />

Unable to switch off<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

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

Saved successfully!

Ooh no, something went wrong!