
45-13
TABLE 2. DATA
FOR
EXAMPLE
1
Part Generic Number
Generic
Failure
Quality
Count Part
Type"
of
Parts
Rate,
AG/106
hr"
Factor,
r0*
1
Film Resistor
32
0.042
0.1
(R)
2
Wire Resistor
5
0.110
0.1
(R)
3
Capacitor
15
0.044
0.1
(R)
RNR
55
182
RWR
35007
CKR
39014
*
Data
from
MIL-HDBK-217B
it is more convenient to think in terms of "availabil-
ity,"
A.
Product availability is defined as the probability that
the system will operate satisfactorily at any point in
time, where time includes not only operating life, but
also active repair time and administrative and logistic
time. An equation for availability is
A
=
MTBF/(MTBF
+
MTTR)
where,
A
=
availability,
MTBF
=
mean time before failure,
MTTR
=
mean time to repair.
The calculation of MTTR is related to repair hours,
while the calculation of MTBF
is
related to component
operating hours. Fig.
I1
is a graph of the above
equation.
It is evident from the figure that the effect of
maintainability
on
availability increases as the ratio of
MTBF to MTTR decreases, If an item has an inherently
low MTBF, the MTTR must be very low to sustain a
good level of availability.
In the design, of any complex system, an optimum
relationship should be established between reliability
and maintainability,
so
that reliability is not increased
beyond the point where very little availability gain is
obtained because of lack of consideration of the effect
of maximum maintainability.
To look at this another way, manufacturers of micro-
electronic devices claim that MTBF is very high and
repair time is nil or very low. Look again at Fig. 11 and
the ratio of MTBF/MTTR in the region to the right of
100. Little is to be gained by designing a module that
can be repaired extremely quickly, if to do the job
special tools and costs are involved.
In
other words, the
throwaway concept in this case is clearly justifiable.
NOTE: There
is
some ambiguity in the use of the terms
MTBF and MTTF. Some references use the same
definitions as accepted in this chapter. Others, such as
Reference 4, use MTTF as the inverse of failure rate,
with MTBF
to
be given by
MTBF
=
MTTF
+
MTTR
Hence, by this convention,
A
=
MTTF/MTBF
SOURCES
OF
RELIABILITY
DATA
There are two sources of failure-rate data:
Generic data banks
Experimental determination by life testing
Generic Data Sources
Generic data are usually used for initial design and
evaluation, whereas life testing
is
more appropriate to
the latter stages of system development, where questions
such as reliability growth and system substantiation are
important.
Data banks and other sources of failure-rate data have
grown considerably in recent years. A comprehensive
review of existing data sources is given in Reference 4.
Sources which are readily available are MIL-HDBK-
217B (Reference 7), the results of the IEEE Project
500
on failure rates for electronic components (Reference
8),
the Government/Industry Data Exchange Program
(GIDEP) (Reference 9), and the Failure Data Handbook
for Nuclear Facilities, available from NTIS (Reference
10). More detailed information can be obtained by
subscribing to one of several data banks, such as the
Nuclear Plant Reliability Data System (NPRDS) (Refer-
ence 11) or the System Reliability Service Data Bank
(SYREL) (Reference 12), operated by the United King-
dom Atomic Energy Authority.
Life Testing
If it is possible to perform adequately, life testing of
actual components is a more accurate method
of
determining failure rates, as long as testing conditions
are chosen to simulate actual service conditions as
realistically as possible.
Two basic methods are used in securing reliability
data. In the first method, assume that
20
units are
placed on test with the stipulation that each unit be
operated
SO00
hours, which requires over 200 days of
continuous operation. During this period of operation,
the time at which each of five failures occurs is
recorded. If they occur at 4200,4350,4400.4750, and
4900 hours, and if the test is stopped at the end of
SO00
hours, the total time of operation is
100
000
-
(800
+
650
+
600
+
250
+
100)
=
97
600
hours. If the