Worked examples — Reliability — MTTF, MTBF, exponential failure model
3.6.31 · D3· Physics › Spacecraft Structures & Systems Engineering › Reliability — MTTF, MTBF, exponential failure model
Yeh page ek firing range hai. Hum yahan har tarah ke questions line up karte hain jo exponential reliability model aapse pooch sakta hai — har sign, har extreme value, degenerate cases, ek word problem, aur ek exam twist — aur har ek ko ek complete worked solution se solve karte hain. Agar aap neeche diye gaye saalon ko kar sako, toh is topic ka koi bhi reliability question aapko surprise nahi kar sakta.
Shuru karne se pehle, parent note se ek reminder: haari poori duniya yahan ek picture par tiki hai — ek curve jo height se shuru hoti hai (launch par definitely alive) aur ki taraf slide karti hai (eventually definitely dead). Number (lambda) failure rate hai: har surviving unit per unit time mein kitni failures hoti hain. Neeche sab kuch bas uss ek curve ko alag-alag points par padhna hai.

Recall Woh chaar formulas jinpar hum lean karenge
Exponential survival curve ::: Mean time to failure ::: Exactly MTTF par reliability ::: Parallel mein do units (kaam karta hai agar koi ek bhi kaam kare) :::
Scenario matrix
Har reliability problem inhi case classes mein se ek hoti hai. Right-hand column us worked example ka naam batata hai jo us cell ko cover karta hai.
| # | Case class | Kya khaas hai | Covered by |
|---|---|---|---|
| A | Forward: diya → nikalo | seedha plug in karo | Ex 1 |
| B | Inverse: diya → (ya ) nikalo | ko "undo" karne ke liye use karna padega | Ex 2 |
| C | Degenerate | curve apni starting height par | Ex 3 |
| D | Limit | curve ki floor value | Ex 3 |
| E | Degenerate | ek component jo kabhi fail nahi karta | Ex 4 |
| F | landmark | "" wala surprise | Ex 5 |
| G | Parallel redundancy | do curves combine hoti hain | Ex 6 |
| H | Series stacking | rates add hoti hain | Ex 7 |
| I | Word problem (real mission) | English → math mein translate karo | Ex 8 |
| J | Exam twist (unit trap / partial mission) | hidden conversion ya piecewise time | Ex 9, Ex 10 |
Hum inhe order mein cover karte hain.
Worked examples
Forecast: Andaza lagao — kya ke kareeb hoga ya ke? Exponent thoda chhota sa hai, toh kuch se upar expect karo.
-
Exponent compute karo. Yeh step kyun? Poori curve sirf ek dimensionless number (failures/hour × hours = failures, ek pure number) par depend karti hai. ko touch karne se pehle hume ise build karna hoga.
-
Ise mein daalo. Yeh step kyun? Yeh literally par curve ki height padhna hai — figure s01 dekho, exponent axis par wala dot.
Answer: , yaani survive karne ka lagbhag 54.9% chance hai.
Verify: ✓ hamaara exponent recover karta hai. Units: exponent dimensionless hai ✓. Aur kisi bhi probability ki tarah aur ke beech hai ✓.
Forecast: Lambe time mein high reliability → hum ek bahut chhota expect karte hain.
-
Unknown ke saath equation likho. Yeh step kyun? Ab ek exponent ke andar band hai. Ise free karne ke liye hume ek aisa tool chahiye jo ko undo kare.
-
Natural logarithm apply karo. Natural log exactly yeh poochhta hai "kis power par raise karna hoga?" — yeh exponential ka inverse hai. Isliye hum choose karte hain, koi aur function nahi.
-
ke liye solve karo.
Answer: failures/hour (equivalently MTTF hours).
Verify: Wापस plug karo: ✓. Chhota jaise forecast kiya tha ✓.
Forecast: Launch par cheez kaam karti hai; hamesha ke liye wait karo toh definitely dead. Toh aur expect karo.
-
par: . Yeh step kyun? "start of mission" ka degenerate input hai. Curve zaroor height se guzarni chahiye — koi system on hone se pehle fail nahi ho sakta.
-
Jab : kyunki hai, exponent , toh . Yeh step kyun? Yeh curve ka floor hai. Yeh batata hai ki exponential components kabhi immortal nahi hote — itna time do, failure certain hai.
Answer: aur . (Figure s01 dekho: curve top-left corner ko touch karti hai aur right side mein bottom axis ke saath hugs karti hai.)
Verify: ✓; decreasing aur neeche se bounded ✓.
Forecast: Bilkul failure rate nahi → ise kabhi fail nahi hona chahiye.
-
substitute karo: Yeh step kyun? Decay ke driver ko zero karna curve ko flat kar deta hai — height par ek horizontal line.
-
MTTF check karo: . Yeh step kyun? Infinite expected life honest answer hai: ek component jo kabhi fail nahi hota uska koi finite average failure time nahi hota. Yeh model ki boundary hai — physically kisi cheez ka nahi hota, lekin yeh ideal limit hai.
Answer: , . Idealized never-failing part.
Verify: Jab , kisi bhi fixed ke liye ✓, aur ✓.
Forecast: Bahut log guess karte hain ("yeh average hai, toh 50/50"). Savdhan raho.
-
Yaad karo ka matlab hai. Toh exponent hai Yeh step kyun? MTTF par exponent hamesha exactly ke barabar hota hai, chahe kuch bhi ho. Isliye yeh point ek universal landmark hai.
-
Evaluate karo:
Answer: Sirf 36.8% apne MTTF tak survive karte hain — 50% nahi. Kyunki curve bent (convex) hai, zyaadatar failures jaldi ho jaati hain. Yeh "MTTF = safe lifetime" wali intuition ko khatam kar deta hai.
Verify: ✓. Parent note ke Mistake 1 ko confirm karta hai.

Forecast: Survive karne ke do chances → system ek single unit se better hona chahiye.
-
Pehle single-unit reliability nikalo. Yeh step kyun? Redundancy math individual survival probabilities se build hoti hai, isliye pehle ek unit ka chance compute karte hain.
-
System tab hi fail hota hai jab DON'T fail karti hain. Har unit probability se fail hoti hai. Kyunki units independent hain, dono ke fail hone ka chance product hai: Yeh step kyun? Independence hume multiply karne deti hai — yahi multiplication poori wajah hai ki redundancy help karta hai (figure s02 dekho: woh chhota purple overlap jahan dono curves dead hain).
-
System survive karta hai agar not-both-fail ho.
Answer: (69.6%), single unit ke 44.9% se kaafi zyada. Series vs. Parallel System Reliability aur Redundancy Design se compare karo.
Verify: ✓, aur (redundancy hamesha help karta hai) ✓.
Forecast: Series mein zyaada parts → kisi bhi single part se worse → kisi bhi best unit se chhota MTTF.
-
Series ke liye survival curves multiply karo: Yeh step kyun? Sab parts survive karne chahiye, isliye multiply karo — aur exponentials ko multiply karne se unke exponents add hote hain. Isliye precisely series mein failure rates add hoti hain.
-
Rates add karo:
-
Series MTTF:
Answer: hours — best single part se chhota ( h), exactly jaise forecast kiya tha.
Verify: ✓; aur ✓. Ex 6 ke parallel case se contrast karo (yeh Series vs. Parallel System Reliability split hai).
Forecast: 60,000 hours mein 12 failures ek modest rate hai; 1-year ka kaam chhota hai. Shayad pass kar le.
-
Test data se estimate karo. Failure rate hai failures per hour: Yeh step kyun? Real data hume empirically deta hai — failures count karo, total operating time se divide karo. Yeh rare events count karne ke Poisson Process view se jodta hai.
-
1 year ko hours mein convert karo. Yeh step kyun? Rate per hour hai, isliye time bhi hours mein hona chahiye — exponentiate karne se pehle units match mandatory hai.
-
Reliability compute karo.
Answer: (17.3%) — 90% requirement fail ho gayi, buri tarah. Aapko redundancy (Ex 6) ya bahut better part chahiye hoga. Yeh directly Mission Design Constraints mein feed hota hai.
Verify: ✓; ✓; toh requirement meet nahi hui ✓.
Forecast: 6 months 15 years ka sirf ek chhota sa slice hai → ko ke kareeb expect karo.
-
MTTF se convert karo, EK unit system rakhte hue. Years mein kaam karo: Yeh step kyun? Trap months aur years ko mix karna hai. Sab kuch years mein convert karo aur mismatch gayab ho jaata hai.
-
Mission time usi unit mein express karo. Chhe months year.
-
Reliability:
Answer: (96.7%). Unit conversion hi poora exam tha.
Verify: ✓, aur forecast ke anusaar ke kareeb ✓. (Cross-check: — same exponent chahe aap years use karo ya hours mein convert karo, kyunki ratio unit-free hai ✓.)
Forecast: Exponential "memoryless" hone ke liye famous hai. Guess: pichle 4000 hours matter nahi karte.
-
Conditional-survival ratio likho. h tak survive karne ka chance given ki h tak pahuncha: Yeh step kyun? Conditional probability = (poora survive karo)/(ab tak survive kiya). Hum dono curve heights divide karte hain.
-
Simplify karo — exponents subtract hote hain. Yeh step kyun? Exponentials ko divide karne se exponents subtract hote hain, sirf extra 6000 hours bachte hain. Starting 4000 cancel ho jaata hai — yahi ek line mein memoryless property hai.
-
Evaluate karo:
Answer: — exactly wahi jo ek brand-new unit ka 6000 hours mein chance hoga. Exponential model ki koi memory nahi hoti age ki (yeh limitation sirf Weibull Distribution / Bathtub Curve wear-out phase se cure hoti hai).
Verify: ✓, aur yeh ek fresh ke barabar hai ✓.
Recall Self-test
par kya hai? ::: , nahi. Teen parts ki series — rates kaise combine hoti hain? ::: Add hoti hain: . Do parallel units har ek — system ? ::: . Parallel units ke liye add kyun nahi kar sakte? ::: Parallel ko dono ka fail hona chahiye (failure probs ka product), rate sum nahi.