23.03.2017 Views

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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

21-8 Industrial Communication Systems<br />

C1<br />

Definition of<br />

{System}<br />

C2<br />

Definition of<br />

{Environment}<br />

G1<br />

{System} is safe in a<br />

given {Environment}<br />

S1<br />

Argument over<br />

hazard identification<br />

and mitigation<br />

C3<br />

Definition of<br />

“safe”<br />

J1<br />

If all hazards are found and<br />

their risk is acceptable, the<br />

system is safe by definition<br />

J<br />

G2<br />

All hazards are<br />

identified<br />

Sn1<br />

Hazard<br />

identification<br />

document<br />

G3<br />

All identified hazards<br />

are mitigated<br />

Sn2<br />

Hazard log<br />

Goal<br />

Context<br />

Strategy<br />

Justification<br />

J<br />

Evidence<br />

FIGURE 21.4<br />

Goal structuring notation example.<br />

are mitigated. This is shown by reference to the hazard-identification document (such as a HAZOP<br />

analysis) and to the hazard log (which contains a log of all hazards and why and how they are mitigated).<br />

The GSN notation is likely to be used in the safety validation phase. It shall enhance the readability<br />

of the safety case and shall ease the identification of weaknesses in the arguments. Ideally, the regulator<br />

or certifier of a system can read this notation and can then decide if a system may go into operation.<br />

21.5 Safety Approach for Industrial Communication System<br />

Safety-related <strong>industrial</strong> <strong>communication</strong> <strong>systems</strong> are accomplished by enhancing the standard <strong>communication</strong><br />

protocol and/or adapting the hardware of the standard nodes. Such <strong>systems</strong> have to be implemented<br />

in a way so that systematic failures (failures where the fault can be clearly identified [IEC61508])<br />

and stochastic failures (failures that occur randomly and where various faults can be the reason for a<br />

single failure [IEC61508]) are detected during the operation, leading to hazards and resulting from node<br />

or network faults.<br />

21.5.1 Overview of Safety-Related Systems<br />

What all safety-related <strong>industrial</strong> <strong>communication</strong> <strong>systems</strong> have in common is that the standard non-safe<br />

system is used and safety-related functions are integrated. Most of the <strong>communication</strong> <strong>systems</strong> adhere<br />

to the requirements of SIL3 specified in [IEC61508]. Predominantly, the <strong>communication</strong> <strong>systems</strong> use<br />

a two-channel architecture realized by a one-out-of-two (1oo2) architecture, meaning that such architecture<br />

consists of two independent channels that execute a given task, but have to agree on the result<br />

unanimously. Furthermore, safety-related <strong>industrial</strong> <strong>communication</strong> <strong>systems</strong> use a safety-related message<br />

format including a cyclic redundancy check (CRC), a timestamp, or sequence number. That message is<br />

embedded into the payload field of the non-safety-related protocol. Finally, the safety-related firmware<br />

is very often placed above layer 7 of the ISO/OSI reference model to guarantee compatibility between<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!