Documente Academic
Documente Profesional
Documente Cultură
Goals
Compare the MTBCF & MTTCF parameters in view of complex systems engineering. Failure repair policy as the backbone for realistic MTBCF calculation. Motivation for modification of the technical specification requirements.
2
r =Number of Failures
t
=
i
t
=
i
MTBF = MTTF ??
An assumption:
DOWN
Critical Failures
Moving towards System Design A System Failure resulting in (temporary or permanent) Mission Termination.
COMPUTER SUBSYSTEM COMPUTER
X X
Critical Failures
A clue for Design Architecture
MTBCF
SAME?
UNIT A UNIT B
ANTENA ANTENA
UNIT C UNIT D
sw
ANTENA ANTENA
CPU
POWER SUPPLY POWER SUPPLY
2/4
Operational Demand: At least two receiver units and one antenna should work to operate the system.
7
ANT
2/4
Serial model : Rs = R1x R2 Parallel model : Rs = 1- (1-R1)x(1-R2) K out of N model : Rs = Binomial Solution
8
WARNING !!!
Is this realistic ?
After[ each S.Zacks, repair Springer-Verlag of a critical failure 1991,-Introduction The whole system To returns Reliability to status Analysis, As Good Par As 3.5] New.
9
Realistic interpretation:
MTBCF = MTTCF
Only failed Items which cause the failure are repaired to idle. All other components keep on aging.
10
Presentation I
Simple 3 aging components serial system model
A 2 2 3 3
C 1 2
1 3
3 2 TTCF
A B C
11
Presentation II
Simple 3 aging components serial system model
A 1 1 1 2
B 2 2
C 3
A B C
12
Presentation III
Simple 3 aging components serial system model
A
1 1 1 2
B
2 2
C
3
2 3
1 1 1
2
3
1 3 2 TTCF
A B C
13
Simulation Method
MONTE CARLO
14
1 N min i N i 1
1 N min i N i 1
electronic system was found to be ~40% Note: True in redundant systems even when all components have constant failure rates.
15
-40%
Example 1
Aging serial system each component is weibull distributed
17
18
19
20
21
Example 2
Two redundant subsystems in series each component is exponentially distributed
22
23
serial
24
(*)
Repair policies
1. Hot repair is allowed for redundant components. 2. All components are renewed on every failure event. 3. All failed components are renewed on every failure event. 4. Failed components are renewed only in blocks which caused the system failure. 5. Failed subsystems are only partially renewed.
26
Conclusions
System configuration and distribution of components determine the gap. Repair policy should be specified in advance to determine calculation method. Flexible software solutions are needed to simulate real MTBCF for a given RBD. Predict MTBCF not MTTCF
27