3.6.32 · D3 · HinglishSpacecraft Structures & Systems Engineering

Worked examplesRedundancy — cold standby, hot standby, active redundancy

2,728 words12 min read↑ Read in English

3.6.32 · D3 · Physics › Spacecraft Structures & Systems Engineering › Redundancy — cold standby, hot standby, active redundancy

Yeh page parent topic ke redundancy formulas ko drill karti hai jab tak har case muscle memory na ban jaye. Hum koi naya theory introduce nahi karenge — hum reliability tools ko stress-test karenge har tarah ke inputs par jo ek problem throw kar sakti hai: normal numbers, zero time, infinite time, degenerate switches, word problems, aur ek exam twist.

Shuru karne se pehle, ek reminder un symbols ka jo humne parent note mein already earn kiye hain (yahan kuch naya nahi hai):

Recall Woh symbols jo humne already build kiye
  • ::: failure rate — ek single unit average mein kitne failures per hour deta hai. Bada = jaldi fail hota hai.
  • ::: time par reliability — probability ki ek unit abhi bhi zinda hai time par. se start hoti hai (pakka zinda), ki taraf decay karti hai.
  • ::: ek unit ka survival curve — exponential kyun? Kyunki constant failure rate ka matlab hai ki agले ghante survive karne ka chance har ghante same hota hai, aur us constant survival ko kai ghanton par multiply karne se exponential milta hai. Yeh ek akela curve hai jisme "no memory" hoti hai.
  • ::: mean time to failure — survival curve ke neeche ka area. Zyada area = average mein zyada jeeta hai.

Scenario matrix

Har redundancy problem jo tumhe milegi, in case classes mein se kisi ek mein aati hai. Neeche ke worked examples mein us cell ka label lagaya gaya hai jise woh cover karte hain, aur milkar woh har cell ko hit karte hain.

Cell Case class Kyun tricky hai
A Normal cold vs hot MTTF numbers plug karo, vs compare karo
B Ek specific finite time par reliability evaluate karo, MTTF se confuse mat ho
C Zero-time input () degenerate: har system padhta hai
D Infinite-time limit () degenerate: har
E TMR (active, 2-of-3) crossover TMR bade ke liye single se worse hoti hai
F Imperfect switch (single point of failure) switch reliability multiply ho jaati hai
G Power-budget word problem reliability gain vs watts cost
H Exam twist — "TMR single ko kab beat karta hai?" ke liye inequality solve karo

Example A — Cold vs hot standby MTTF (normal numbers)

Forecast: Aage padhne se pehle ordering guess karo. Kaun sa redundancy scheme sabse lamba average life dega?

  1. Single unit. h. Yeh step kyun? Yeh hamara baseline hai — baaki sab kuch iske against measure hota hai.

  2. Hot standby. Parent se, h. Yeh step kyun? Dono units saath age karte hain, isliye backup apni aadhi life sirf warm baithke burn kar deta hai — hum sirf aadhi lifetime gain karte hain.

  3. Cold standby. h. Yeh step kyun? Cold backup ka clock sirf switchover par shuru hota hai, isliye hum ek poori second lifetime gain karte hain.

Verify: Ratio . Cold kaagaz par jeetta hai — parent ke key comparison se match karta hai. Units poore mein hours hain. ✓ (Yeh cell A hai.)


Example B — Ek finite mission time par reliability

Forecast: MTTF ne kaha tha cold best tha. Ek specific short time par, kya cold abhi bhi better lagega, aur kitna?

  1. Single unit. , isliye . Yeh step kyun? Hume pehle single-unit survival chahiye kyunki dono redundant formulas isi se bante hain.

  2. Hot standby. . Yeh step kyun? Hot standby tabhi fail hota hai jab dono fail ho jaayein; yeh formula hai.

  3. Cold standby. . Yeh step kyun? Cold pehle do Poisson terms use karta hai kyunki yeh doosri failure tak survive karta hai, aur backup wait karte waqt age nahi hua.

Verify: Is time par order hai — cold yahan bhi best hai, Example A se consistent. Sab mein probabilities hain. ✓

Neeche ki figure teeno survival curves plot karti hai. Notice karo ki sab left edge par se launch karte hain (Example C), grey single-unit curve sabse tez sagging karti hai, aur red dashed line h par teeno colored dots exactly unhi numbers par baithe hain jo humne abhi compute kiye — blue (cold) sabse upar, orange (hot) thoda neeche, grey (single) kaafi neeche.

Figure — Redundancy — cold standby, hot standby, active redundancy
(Cell B.)


Example C — Zero-time degenerate case

Forecast: Compute karne se pehle — jis pal turn on karo usi instant mein kuch bhi fail hone ki probability kya hai?

  1. Single: .
  2. Hot: .
  3. Cold: . Yeh steps kyun? par kisi cheez ko fail hone ka time nahi mila. Ek sahi reliability curve se start honi chahiye (certain survival). Koi bhi formula jo par kuch aur deta woh galat hota.

Verify: Teeno equal hain. Yeh sanity check hai jo har reliability formula ko pass karna chahiye — agar tumhara se start nahi hota, to tumne ise galat copy kiya hai. ✓ (Cell C.)


Example D — Infinite-time limit

Forecast: Infinite time dene par, kya koi bhi redundancy scheme hamesha ke liye survive karta hai?

  1. Single: . Yeh step kyun? Hum simplest curve se shuru karte hain kyunki baaki teeno sab se bane hain — agar yeh marta hai, to woh sab isse inherit karte hain.

  2. Hot: . Yeh step kyun? Dono terms mein decaying exponential hai, isliye har term independently zero par khich jaati hai — zeros ka sum zero hai.

  3. Cold: (exponential linear ko beat karta hai). Yeh step kyun? Yeh woh term hai jo tumhe fool kar sakti hai — factor barhta hai, lekin kisi bhi polynomial ke barhne se zyada tez shrink karta hai, isliye product phir bhi mar jaata hai. Humein sure hone ke liye sabse tez-barhne wala factor check karna hoga.

  4. TMR: jisme hai, deta hai. Yeh step kyun? TMR ki reliability mein ek polynomial hai jisme koi constant term nahi hai, isliye jab underlying unit reliability hoti hai to poora voter output bhi zero par gir jaata hai.

Verify: Har system ki taraf tend karta hai. Redundancy time kharidti hai, kabhi immortality nahi — yeh decay ko slow karti hai, ise rok nahi sakti. Slower-decaying curve ke neeche ka area exactly woh MTTF gain hai jo humne Example A mein compute kiya. ✓ (Cell D.)


Example E — TMR aur uska crossover point

Forecast: TMR hamesha single unit ko beat karta hai... ya karta hai? Guess karo jab har unit already unreliable ho () to kya hoga.

  1. High-quality units, . . Yeh step kyun? Jab units acchi hoti hain, "2-of-3" rare single failure ko mask kar deta hai — TMR () single () ko beat karta hai.

  2. Poor units, . . Yeh step kyun? Jab units kharab hoti hain, do ka simultaneously kaam karna ek ke kaam karne se mushkil hota hai — TMR () single () se worse hai!

Verify: Crossover exactly par hai (Example H dekho). Iske upar TMR help karta hai; neeche TMR hurt karta hai. Isliye help karta hai, hurt karta hai — match karta hai. ✓

Neeche ki figure grey diagonal (single unit, output = input) ko green TMR curve ke against draw karti hai. Jahan green curve diagonal ke upar hai (green shaded, ) TMR help karta hai; jahan yeh neeche dip karti hai (red shaded, ) TMR hurt karta hai. par blue dot green zone mein land karta hai, par orange dot red zone mein, aur dono curves exactly red dot par cross karti hain.

Figure — Redundancy — cold standby, hot standby, active redundancy
(Cell E.)


Example F — Imperfect switch (single point of failure)

Forecast: Parent ne warn kiya tha ki switch khud ek single point of failure hai. Guess karo: kya ek switch redundancy benefit ko wipe out kar deta hai?

  1. Ideal redundant pair. . Yeh step kyun? Yeh "do computers, perfect switch" fantasy hai — woh number jo log quote karte hain.

  2. Switch se multiply karo. Poori chain tabhi kaam karti hai jab switch bhi kaam kare, isliye multiply karo: . Yeh step kyun? Switch redundant block ke saath series mein hai — ek series weak link poore system ko cap kar deta hai (yeh ek reliability block diagram hai jisme ek series element hai).

  3. Single unit se sanity check. Single unit . Isliye real redundancy — abhi bhi ek gain hai, lekin fantasy se kaafi kam.

Verify: : redundancy abhi bhi help karta hai lekin switch zyaatar gain throw away kar deta hai. Isliye real spacecraft fault detection and isolation plus cross-strapping use karte hain taaki switch khud reliable ho. ✓ (Cell F.)


Example G — Power-budget word problem

Forecast: Reliability kehti hai cold ka waise bhi zyada MTTF hai. Kya power budget agree karta hai ya conflict karta hai?

  1. Hot-standby power draw check karo. Extra load W. Available margin W. Kyunki , hot standby power budget violate karta hai. Yeh step kyun? Jo design power budget bust karta hai woh reliability se regardless infeasible hai — power ek hard constraint hai.

  2. Cold-standby power draw check karo. Extra load W (backup OFF). : fit karta hai. Yeh step kyun? Cold ka zero standby power battery-tight spacecraft par uska headline advantage hai.

  3. Timing requirement check karo. Cold ka s switchover tolerable s gap: acceptable. Yeh step kyun? Cold ka ek hi downside (delay) yahan allowed limit ke andar hai.

Verify: Power ( ✓), timing ( ✓), aur cold ka pehle se Example A se zyada MTTF tha. Har constraint cold standby ki taraf point karta hai — yeh ek rare case hai jisme koi tradeoff nahi hai. ✓ (Cell G.)


Example H — Exam twist: TMR crossover ke liye solve karo

Forecast: Example E ne hint kiya tha crossover hai. Ise prove karo aur baaki roots nikalo.

  1. Equation set up karo. . Yeh step kyun? "TMR single ko beat karta hai" ⇔ ; boundary equality hai.

  2. Ek side par laao aur factor karo. . Yeh step kyun? Factoring ek cubic ko teen simple roots mein turn kar deta hai — koi formula nahi chahiye.

  3. Roots padho. , , . Yeh step kyun? Ek product zero hota hai tabhi jab uska koi ek factor zero ho, isliye hum teeno factors , , ko ek ek karke zero set karte hain — factoring ka poora point yahi hai, yeh seedha roots haath mein de deta hai.

  4. Winning region decide karo. test karo (Example E): TMR ✓. test karo: TMR ✓. Isliye TMR single ko exactly tab beat karta hai jab . Yeh step kyun? Roots sirf woh jagah mark karti hain jahan dono curves cross karti hain; kaun si side jeetti hai jaanne ke liye humein roots ke beech har interval mein ek point sample karna hoga — wahan difference ka sign poora interval settle kar deta hai.

Verify: Roots cubic satisfy karte hain; sign tests confirm karte hain ki TMR ke upar help karta hai aur neeche hurt karta hai. Example E se consistent. ✓ (Cell H.)

Recall Quick self-test

par, kya TMR single unit ko beat karta hai? ::: Nahi — woh exactly equal hain; crossover hai. Cold standby ka MTTF hot se zyada kyun hai? ::: Cold backup OFF rahte waqt age nahi karta, isliye tum ek poori second lifetime gain karte ho sirf aadhi ki jagah. Ek "redundant" system jisme fragile switch hai — switch reliability block diagram mein kahan baitha hai? ::: Redundant block ke saath series mein, isliye yeh total reliability ko cap kar deta hai.


Har idea kahan connect hota hai

cold

hot

active TMR

Redundancy scheme

longest MTTF slowest switch

instant switch more power

fault masking needs R above half

switch is series risk

Fault Detection and Isolation

voting rejects one bad unit

Yeh bhi dekho: Failure Modes and Effects Analysis (FMEA)kaun si failures ko cover karne ki zaroorat hai yeh jaanne ke liye, Single Event Upset (SEU) — radiation bit-flips ke liye jo switchovers trigger karte hain, aur Byzantine Fault Tolerance — jab koi faulty unit voter se jhooth bole.