Skip to content
Back to search results

Reliability Block Diagram

Introduced by
Ebeling, C. E.
Year
2010
Type
Reliability analysis technique
Family
Reliability Engineering
Font size

What does it do?

A Reliability Block Diagram (RBD) is a visual representation of a system's architecture that models how component reliabilities combine to determine overall system reliability.

Each block represents a component or subsystem with a known reliability (probability of functioning without failure), and connections between blocks represent functional relationships (series, parallel, or mixed). RBD analysis is a fundamental tool in reliability engineering, used to identify critical components, optimize redundancy, and predict system-level failure rates.

The intuition behind the method

Imagine a communications system with three redundant data routers. If all three are connected in parallel (any one can handle traffic), the system fails only if all three fail simultaneously. The system reliability is much higher than any single router's reliability. Conversely, if routers are in series (all must function), the system reliability is lower than the weakest router. An RBD visually represents these configurations and calculates the combined reliability. For example, if each router has 99 percent reliability and two are in parallel: system reliability = 1 - (1 - 0.99)^2 = 0.9999 (99.99%). The RBD makes these calculations explicit and guides designers to invest in redundancy where it matters most.

History

Reliability Block Diagram analysis emerged in the 1950s–1960s from reliability engineering theory, particularly in aerospace (NASA, DoD) where system failures were catastrophic. The technique formalized how to combine component reliability data into system-level predictions. Modern RBD software (ReliaSoft, Isograph, MATLAB) automates calculations and enables complex analyses. RBD is now standard in industries with high reliability requirements and is taught in engineering curricula worldwide.

When to use it

RBD is essential for systems where reliability is critical (aerospace, medical devices, power systems, telecommunications) or where failures are costly (downtime, safety risk). Apply RBD when designing systems, assessing design trade-offs (cost vs. reliability), or optimizing maintenance strategies. It is less critical for non-critical systems or where redundancy is uneconomical. Most valuable in design phase; can also be used to diagnose reliability issues in operating systems.

Limitations and considerations

  • Requires accurate component reliability data; estimates or outdated data lead to unreliable predictions
  • Assumes component failures are independent; common-cause failures or wear-out correlations are not captured
  • Does not account for dynamic systems where component reliabilities change over time or under stress
  • RBD analysis focuses on reliability; other aspects (performance, cost, safety) require separate analyses

Source conditions do not replace independent scientific review or validation by an analysis engine.

Strengths

  • Provides clear visual representation of system architecture and how component failures propagate to system failure
  • Quantifies system-level reliability from component-level data, enabling design optimization
  • Identifies critical components (weak links) for targeted improvement and redundancy investment
  • Supports design trade-off analysis: cost of redundancy vs. improved reliability
  • Integrates with maintenance planning: higher-reliability components may allow longer maintenance intervals, reducing costs

Applications

  • An aerospace manufacturer uses RBD to design a redundant hydraulic system for an aircraft actuator, adding a standby pump that increases system reliability from 99.5 percent to 99.95 percent over a 10-hour mission
  • A telecommunications company applies RBD to optimize network topology, identifying that adding a second fiber-optic link between two cities increases system uptime from 99.7 percent to 99.99 percent with acceptable cost
  • A medical device maker uses RBD to evaluate battery redundancy in an implantable defibrillator, balancing the goal of 10-year reliability (>99.8 percent) with device size constraints
  • A power utility uses RBD to assess the reliability of a substation's transformer bank, determining whether adding a third transformer in parallel justifies the capital cost

How it works

How it works

1

Identify the system boundary, functional requirements, and failure definitions. Determine the mission time (how long the system must operate without failure).

2

Map the system architecture: which components are in series (all must work), parallel (at least one must work), or mixed configurations. Draw the RBD diagram.

3

Gather or estimate component reliability data from historical failure rates, supplier data, or testing. Express reliability as R(t) or mean time between failures (MTBF).

4

Compute system reliability by combining component reliabilities using series and parallel formulas. Perform sensitivity analysis to identify critical components.

5

Prioritize improvements: add redundancy to critical components, specify higher-reliability components, or extend maintenance intervals to reduce failure rates.

Common pitfalls

  • Over-simplifying system architecture in the RBD; missing failure modes or dependencies leads to optimistic reliability estimates
  • Adding redundancy indiscriminately without analyzing failure rates; redundant components may be underutilized or increase complexity
  • Neglecting maintenance in reliability planning; components fail faster if not properly maintained, violating RBD assumptions

Frequently asked questions

What is the difference between series and parallel reliability?

In series, all components must work; system reliability R_sys = R1 × R2 × ... × Rn. In parallel, at least one component must work; system reliability R_sys = 1 - [(1-R1) × (1-R2) × ... × (1-Rn)]. Parallel is more reliable but requires redundancy. Most real systems are mixed: some subsystems in series, others in parallel.

What is mean time between failures (MTBF), and how does it relate to reliability?

MTBF is the average time between failures, typically expressed in hours. For exponential failure distributions (common assumption), MTBF and reliability are related: R(t) = e^(-t/MTBF). Higher MTBF means higher reliability. MTBF is useful for field data and maintenance planning.

Can RBD handle time-dependent reliability (wear-out)?

Basic RBD assumes constant failure rates (exponential distribution). Time-dependent or wear-out failures require Weibull or other non-exponential distributions. Advanced RBD software can incorporate time-dependent component reliabilities, though the analysis becomes more complex.

How do we handle common-cause failures in RBD?

Standard RBD assumes component failures are independent. Common-cause failures (e.g., both pumps cavitate due to low pressure) violate this assumption. Model common-cause failures by grouping affected components or using specialized techniques (fault trees combined with RBD). Alternatively, specify higher maintenance standards to prevent common-cause scenarios.

Related methods

Sources

  1. Ebeling, C. E. (2010). An introduction to reliability and maintainability engineering (2nd ed.). Long Grove, IL: Waveland Press.

    Open publication reference
    Copied.
  2. Stamatis, D. H. (2003). Failure mode and effect analysis: FMEA from theory to execution (2nd ed.). Milwaukee: ASQ Quality Press.

    Open publication reference
    Copied.