Home / Courses / Probabilistic Design and Reliability / Reliability of Mechanical Systems

Probabilistic Design and Reliability | Module 5 of 10

Reliability of Mechanical Systems

A machine fails as a system. Component reliability matters, but architecture, redundancy, dependence, and common-cause failure decide what system reliability means.

Readiness check

Tick only what you can do closed-notes before using this module for design decisions.

Multiply independent probabilities.
Explain a series load path in a mechanical system.
Explain redundancy in plain language.
Name a common-cause failure in a machine.
Read a simple block diagram.

0 or 1 weak itemsContinue with this module.

2 weak itemsReview system thinking in System Dynamics.

3 or more weak itemsReview probability in Mathematics, Module 15.

The core idea

Series reliability multiplies the reliabilities of components that all must work. Parallel reliability is one minus the probability that all redundant paths fail, but only when independence is justified.

series: R_sys = product(R_i)parallel two-unit: R_sys = 1 - (1 - R_1)(1 - R_2)fault tree OR: P(A or B) needs dependence awareness

Mechanical systems often combine series and parallel logic. A lifting mechanism may need motor, gearbox, brake, cable, hook, and control switch all working, so a single critical failure can stop the function. A cooling system may have two pumps in parallel, but if both share a clogged inlet filter, power supply, or hot environment, independence is false. Reliability block diagrams are function diagrams, not physical drawings. They show which component functions must succeed for the system function to succeed. Fault trees work from a top event, such as loss of braking, down to combinations of component failures and common causes. The central discipline is refusing to multiply probabilities until the dependence assumption has been inspected.

The skill works when: the failure event, units, assumptions, distributions, and checks are visible.

The skill breaks down when: a probability is reported without the mechanical model and evidence boundary.

The concept. Series reliability multiplies the reliabilities of components that all must work. Parallel reliability is one minus the probability that all redundant paths fail, but only when independence is justified.

The skills, taught in order

Define the system function

State the function whose reliability is being estimated, such as lift load, maintain pressure, cool electronics, or stop motion.

Map functional paths

Use a reliability block diagram to show which functions are series, parallel, or mixed.

Compute only justified independence

Independence is not automatic. Shared loads, environment, suppliers, controls, and maintenance can couple failures.

Use fault trees for top events

A fault tree is useful when failures combine through AND and OR logic toward a defined top event.

Interpret redundancy honestly

Redundancy improves reliability only when redundant paths are truly available and not defeated by common causes.

Engineering connection: use these skills to turn variability into a design decision, not just a plot.

Worked example 1: series reliability of an actuator chain

A small actuator chain requires motor R = 0.995, coupling R = 0.990, gearbox R = 0.985, and screw R = 0.992 to work for the mission. Estimate system reliability assuming independence.

ProblemA small actuator chain requires motor R = 0.995, coupling R = 0.990, gearbox R = 0.985, and screw R = 0.992 to work for the mission. Estimate system reliability assuming independence.
AssumptionsComponents fail independently for this first calculation. The mission and failure definitions are the same for all components.
ModelR_sys = R_motor R_coupling R_gearbox R_screw
SolveR_sys = 0.995 x 0.990 x 0.985 x 0.992 = 0.9625.
CheckThe system reliability is lower than every individual component reliability because every component must work.
ConclusionSeries system reliability is about 0.963 under the independence assumption.

Result. Series system reliability is about 0.963 under the independence assumption.

Worked example 2: parallel pump pair with a common inlet

Two parallel pumps each have reliability 0.94 for a short mission. Estimate ideal parallel reliability. Then explain why a shared inlet blockage changes the interpretation.

ProblemTwo parallel pumps each have reliability 0.94 for a short mission. Estimate ideal parallel reliability. Then explain why a shared inlet blockage changes the interpretation.
AssumptionsIdeal calculation assumes independent pump failures. Shared inlet blockage is a separate common-cause event.
ModelR_parallel = 1 - (1 - R)^2
SolveIdeal R = 1 - 0.06^2 = 0.9964. But this number excludes the event that the shared inlet is blocked, which can fail both paths at once.
CheckIf the inlet blockage probability is not negligible, the real system reliability is lower than 0.9964.
ConclusionRedundancy helps, but common-cause failures must be modeled or explicitly bounded.

Result. Redundancy helps, but common-cause failures must be modeled or explicitly bounded.

Python activity

Engineering question: Compute series, parallel, and mixed reliability for a pump cooling system.

Assumptions and units: Use the units shown in the code comments. Keep the random seed fixed while learning so the result is reproducible.

motor = 0.995
controller = 0.990
pump_a = 0.94
pump_b = 0.94
heat_exchanger = 0.985

parallel_pumps = 1.0 - (1.0 - pump_a) * (1.0 - pump_b)
system = motor * controller * parallel_pumps * heat_exchanger

print("parallel pump reliability", round(parallel_pumps, 5))
print("system reliability", round(system, 5))
print("common cause check: shared power, inlet blockage, coolant contamination")

Numerical checks: The mixed system must be less reliable than the ideal parallel pump subsystem because other series components also must work.

Limitations: The model assumes independence and equal mission definitions. Common-cause events require separate modeling.

Misconceptions and diagnostics

Mistake	Diagnostic question	Correction
Series-system reliability can be calculated without checking dependence.	Ask: what shared cause can fail multiple components?	Correct the assumption, then rerun the calculation or rewrite the report.
Redundancy always fixes reliability.	Ask: are redundant paths independent, monitored, and available when demanded?	Correct the assumption, then rerun the calculation or rewrite the report.
A reliability block diagram is a physical layout.	Ask: does the diagram show function success paths rather than geometry?	Correct the assumption, then rerun the calculation or rewrite the report.
High component reliability guarantees high system reliability.	Ask: how many components must all work?	Correct the assumption, then rerun the calculation or rewrite the report.

Practice ladder

Recognize

State whether a chain, cable, hook, and brake in a lift are mostly series or parallel for the lift function.

Solution guidance

Write the governing equation, state units and assumptions, then compare the answer with the relevant limit state or design decision.

Calculate

Compute series reliability for three independent components with R = 0.99, 0.98, and 0.97.

Solution guidance

Write the governing equation, state units and assumptions, then compare the answer with the relevant limit state or design decision.

Diagnose

A redundant pump calculation ignores the shared power supply. Explain the missing event.

Solution guidance

Write the governing equation, state units and assumptions, then compare the answer with the relevant limit state or design decision.

Design

Sketch a text reliability block diagram for a cooling system with two pumps and one heat exchanger.

Solution guidance

Write the governing equation, state units and assumptions, then compare the answer with the relevant limit state or design decision.

Working with AI, and proving it yourself

Useful AI support

Ask for alternative explanations of terminology, candidate code tests, or a checklist of assumptions to verify.

Ask it to challenge a derivation, then prove the result with units, limiting cases, and an independent calculation.

Do not let AI invent material distributions, fabricate failure data, claim standards compliance, or make final safety decisions.

Portfolio evidence

Create one short reliability note for this module. It must include the engineering question, assumptions, input definitions, equations, calculation, checks, interpretation, and limitations.

Verification required: dimensional analysis, a benchmark case, convergence or sample-size check, and a plain-language residual-risk statement.

Retrieval and spaced review

Closed notes. Answer out loud, then reveal.

What is a series system?

A system where every listed component function must succeed.

What is ideal two-component parallel reliability?

1 - (1 - R1)(1 - R2), if failures are independent.

What is common-cause failure?

One cause that can fail multiple components or paths together.

What does a fault tree start with?

A top event, then logical combinations of causes.

When is redundancy most valuable?

When redundant paths are independent enough and available when needed.

TodayFinish the review and first two practice levels.

+1 dayRebuild one worked example from a blank page.

+3 daysChange one assumption and predict the effect.

+7 daysConnect this module to the capstone bracket.

+30 daysReuse the method in a new mechanical component.

References and source discipline

This course synthesizes original MechCompass explanations from established reliability engineering sources. Confirm current editions and standards before using them for formal design approval.

Topic in this module	Reference direction
System reliability and block diagrams	Elsayed, Reliability Engineering, 3rd edition
Dependence and system reliability	Der Kiureghian, Structural and System Reliability
Mechanical design reliability	Le, Reliability-Based Mechanical Design, Volume 2