Reliability block diagram

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

A reliability block diagram (RBD) is a diagrammatic method for showing how component reliability contributes to the success or failure of a complex system. RBD is also known as a dependence diagram (DD).

A reliability block diagram

An RBD or DD is drawn as a series of blocks connected in parallel or series configuration. Each block represents a component of the system with a failure rate. Parallel paths are redundant, meaning that all of the parallel paths must fail for the parallel network to fail. By contrast, any failure along a series path causes the entire series path to fail.[1][2]

An RBD may be drawn using switches in place of blocks, where a closed switch represents a working component and an open switch represents a failed component. If a path may be found through the network of switches from beginning to end, the system still works.

An RBD may be converted to a success tree by replacing series paths with AND gates and parallel paths with OR gates. A success tree may then be converted to a fault tree by applying de Morgan's theorem.

In order to evaluate RBD, closed form solution are available in the case of statistical independence among blocks or components. In the case the statistical independence assumption is not satisfied, specific formalisms and solution tools, such as dynamic RBD,[3] have to be considered.

See also[edit]


  1. ^ Modarres, Mohammad; Mark Kaminskiy; Vasiliy Krivtsov (1999). "4" (pdf). Reliability Engineering and Risk Analysis. Ney York, NY: Marcel Decker, Inc. p. 198. ISBN 978-0-8247-2000-1. Retrieved 2010-03-16.
  2. ^ "6.4 Reliability Modeling and Prediction". Electronic Reliability Design Handbook. B. U.S. Department of Defense. 1998. MIL–HDBK–338B. Archived from the original (pdf) on 2011-07-22. Retrieved 2010-03-16.
  3. ^ Salvatore Distefano, Antonio Puliafito: Dependability Evaluation with Dynamic Reliability Block Diagrams and Dynamic Fault Trees. IEEE Trans. Dependable Sec. Comput. 6(1): 4-17 (2009),

External links[edit]