adequately with technical uncertainties
& Quality Management
Reliability Block Diagrams are useful
for visualizing and analyzing complex systems. The system is broken
down into functional blocks. The blocks are then connected with arrows
in such a way that they reflect the block interactions and therefore,
as a whole, the system behavior.
Complex systems can be distinguished by at least one of the following
The functional blocks, start and end point are connected with
"functional flow" arrows according to the system architecture. Reliability Block Diagram
- Parallel branches (redundancy)
- Fault tolerance
- Network structure (e.g. production line)
- Dedicated maintenance philosophy
As long as there is at least one
uninterrupted connection between start
and end (a so called path set, or success path), the system is
A good example may be a twin engine aircraft, which will be also used
in the Markov paragraph in order to demonstrate the differences between
Reliability Block Diagram and Markov.
Twin engine aircraft can safely fly with only one engine. However,
if one engine fails, the aircraft must fly directly to the nearest
eligible alternate airport.
The "1::2" below the node means that at
least one out of two incoming paths must be functional in order
to keep the system functional. In this example, each of the two paths
consists of one engine.
Depending on the capability of the Reliability Block Diagram software,
many system parameters can be calculated, for example:
The reason why we put the twin engine
example here is to show the limitations of Reliability Block Diagram in
comparison to Markov.
- Failure rate, MTBF
- Reliability R
- Availability A
- Repair cost, repair time
- Optimal maintenance interval (depending on criteria)
- Optimal number of spares (depending on criteria)
Here (RBD), the aircraft is considered to have failed as soon as both
engines fail. In practice however this is not necessarily the case,
because the aircraft can fly safely even with both engines failed ...
at least for 10 minutes. This would probably be enough time for the
crew to restart one of the engines in order to make it to the nearest
There is a further limitation: With one engine failed, the remaining
engine must work harder in order to keep the aircraft airborne. This in
turn would cause a higher failure rate for the remaining engine.
Reliability Block Diagram cannot address this behavior, but Markov can.