MODERN OFFICE BUIDLINGS UTILITIES ALTERNATIVES

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP89-00244R000200290016-7
• Release Decision: RIPPUB
• Original Classification: K
• Document Page Count: 27
• Document Creation Date: December 22, 2016
• Document Release Date: June 3, 2008
• Sequence Number: 16
• Publication Date: January 12, 1982
• Content Type: REPORT

Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
1~1-
3
STAT
bl
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
W ~V yyNV!
0CC 3:3:
00 a0Z "'WOO
a. I-- Cc
ZN-0 0W
W
C <
cc
U.
I W z
10
4
W
W LL
hW Q
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
W
 `eI
r;
?4
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
1 1
1 I
u
1__LJ
IL I
11,01111
HV
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
3. co cc R
a V W W W ca
QZ
0 a y O( y o c. mQ
1 I I I I ;n I
0
3.
a.
W
rn ..:
ra O
uj
0 _
I- - a O C03 a
a l l l Z I I I I
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
z
0
rn
W
0
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
10 t0
z z z
0 00
N
0
z
I-
4 z
i II
87
0
a
W i
WI
NI
Z
Q
I
z
O
I
m
Q
t
OI-
CA l~ x
N
Jg
O
W
Z W >
N
I-
Y Oco
J I
>
z
y W
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
eo o~ n 0
W~WW D
V1 N H Y ~ Y~
k M N 9
Ilk ;I
i--- I
-'---------------J
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
N
~
r W k
~.
Q
X
ti
~
r-
C
~
~,
~
N
4 m
~C
l
l u
1.~
1.?'
~~JZ
pie9
y
r
t
~
u
K
~
o~
? v
v v
a~ v?
'"
vu
u~
vu
1-7
c I I~ I N I
060WAg.V? i9
I
'ot
'Its
LiJ
'VI
III
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
eo
aN
I
F I
it
o Q =
o po w
NI,3
I I
I
II
I. i
L`
`
t~ I I
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
X41
~y
mN
( V i
vY-'~ I 6 a-vo~s
ar-
r -L.
J8
O-N
I I
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
a,oe7d
'oo7!
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
2
Q
cc
0
Q
0
p
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
W
H
N
~i1~io~ caw~t. m
00000000000
W
ZJ
m N
c cc r. Lu
HP }z00
Q 3 V- N M V W W m Q Q Q
OmOOOOOO MwoC2
J~ZZZZzzw -wW
wwwwwwwwF-ZZ
QaaaaaaaQww
O>>> > w a u
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
W
Z
Q
cZ
W
Z3 cc
W
W3
2a
as 010 00
N
N N
W
O O 0
a CD
CD c
000
49
A a A
coo
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
J
S
OZ
0--
ii
qc ?1 1
N
Zw~ r.~
W 2J-(3 -j
1ii
Wgmi m hr
2
O
IL
Ccog
C I.
W
y
cc
W
Y
ii
cc
O
m
V
JQ?r
Z~O
F,.
Za
W
m
N - n
W
O
J
404
.J L
W=
u
Wr
J
0 0-
.
I-
L.J4 W
Q3
SmS
> O
W
CL
0
ZO
W J
3
ULZU H V G 0
I W W
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
ca > ca CL
Z H W
WO mya
J 2 a: _j Co - y w
U.
O Qa Q(j >>y
Q Z c Z Q
IDQ ~QO
CD Ch
a Z oZoC
O m O m W
aG CL aZ
O W O W W
-1 cc JQ0
W W
> .. > .
W W
G G
Z N J V
I-
W O C7
cc ci J U.
N ? ? z ?
WI U.
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
AVAILABILITY ANALYSIS METHODOLOGY
(Derived from MIL-STD-756A)
A feasibility prediction procedure is used in the conceptual phase of
development. This phase covers development of a design from its initial
design concept to and including its preliminary paper design.
During this phase the level of information available for environmental,
functional, and other requirements is usually restricted primarily to
overall aspects of design. Detailed ideas generally are limited to that
which may be derived from existing designs similar to that being developed.
The following steps are
applicable to all portions of the design:
a) Define the system
b) Establish the availability model
c) Establish the functional complexity
d) Compute the availability
DEFINE THE SYSTEM:
The system shall be defined in terms of the following:
a) Purpose, intended use, or mission
b)
c)
d)
Performance - parameters and allowable limits
Functional and physical boundaries
Conditions which constitute item failures
AVAILABILITY MODEL:
Construct an availability block diagram showing the functions, blocks, and
relationships that are necessary for successful system operation. Clearly
indicate alternate modes of operation. Derive a mathematic equation for the
availability of the system and for each functional block in the availability
block diagram. Assumptions and simplifications employed in the model are
clearly stated.
AVAILABILITY BLOCK DIAGRAM:
The availability block diagram represents a systematic arrangement of functions
that must be performed and the sequence in which they must be performed for
successful product function. In general, success of the individual components
is required for successful operation of the block.
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
General assumptions that apply to availability block diagrams are as follows:
a) The lines connecting blocks have no availability values.
The lines serve only to give order and direction to the
diagram.
b) Failure of any device denoted by a block in the diagram
will cause failure of the entire system, except that
alternate modes of operation may be present.
c) Each device denoted by a block in the diagram is independent,
with regard to probability of failure, fromall other blocks.
d) No interface problems occur between man and system, all human
elements are completely reliable.
FUNCTIONAL COMPLEXITY:
For each functional block, estimate the functional complexity by type of
function and number of parts. Estimate either the failure rate or the prob-
ability of success by using data obtained from experience with existing products
or from designs having similar requirements. The source and basis of data is
stated.
PART FAILURE RATE:
Electronic - Determine the failure rate for each electronic part using
MIL-HDBK-217. For electronic parts not covered by MIL-HDBK-216, use existing
data and specify the source.
All other parts- Determine the failure rate for each part using existing data
or data specified by the procuring activity. Specify the source of data.
SYSTEM AVAILABILITY
Compute the system availability using the mathematical equation derived from
the availability block diagram.
The availability of the facilities system is calculated by the computer simu-
lation program, AVAIL.
AVAIL - (Computer simulation program used in the availability prediction.)
AVAIL is a general purpose computer simulation model developed to evaluate
the effects of hardware failures and maintenance concept variations upon a
system. The model requires inputs of hardware success paths, which are formu-
lated in the availability block diagram, with their respective MTBFs, MTTRs,
and switching times.
The model simulates, by Monte Carlo methods, the hardware failures, records
the downtime, and checks to see of a spare is available.
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
If a hot standby spare is available, the model records the time required
to switch in the hot standby unit. If there is no hot standby unit, the
model checks for shelf spares. If a shelf spare is available, the model
records the downtime, and replaces the unit with the shelf spare. If a
shelf spare is not available, the model determines the time to repair the
failed item and to return it to service.
The program also has a feature which plots availability block diagrams.
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
The following definitions, from MIL-STD-721, are provided as reference
material:
AVAILABILITY - A measure of the degree to which an item is in the operable
committable state at the start of the mission, when the mission is called
for at an unknown (random) point of time.
DOWNTIME - That element of time during which the-item is not in condition
to perform its intended function.
FAILURE - The inability of an item to perform within previously specified
limits.
FAILURE RATE - The number of failures of an item per unit measure of life
(cycles, time, miles, events, etc., as applicable for the item).
INHERENT - Achievable under ideal conditions, generally derived by analysis,
and potentially present in the design.
MEAN-TIME-BETWEEN-FAILURES (MTBF) - For a particular interval, the total
functioning life of a population of an item divided by the total number of
failures within the population during the measurement interval. The defini-
tion holds for time, cycles, miles, events, or other measures of life units.
MEAN-TIME-TO-REPAIR (MTTR) - The total corrective maintenance time divided by
the total number of corrective maintenance actions during a given period of
time.
MISSION - The objective or task, together with the purpose, which clearly
indicates the action to be taken.
OPERABLE - The state of being able to perform the intended function.
OPERATIONAL - Of, or pertaining to, the state of actual usage.
PREDICTED - That which is expected at same future date, postualted on analysis
of past experience.
REDUNDANCY - The existence of more than are means for accomplishing a given
fundtion. Each means of accomplishing that function need not necessarily be
identical.
REDUNDANCY, ACTIVE - That redundancy wherein all redundant items are operating
simultaneously rather than being switched on when needed.
REDUNDANCY, STANDBY - That redundancy wherein the alternative means of perform-
ing the function is inoperative unti needed and is switched on upon failure of
the primary means of performing the function
RELIABILITY - The probability that an item will perform its intended function
for a specified interval under stated conditions.
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7
Other definitions which apply are:
INHERENT AVAILABILITY - The availability inherent in the design of a system
is the probability that the system, when used under stated conditions,
without consideration for any scheduled or preventive maintenance action,
in an ideal support environment (i.e., available tools, spares, manpower,
data, etc.), shall operate satisfactorily at any given point in time. It
excludes ready time, preventive maintenance downtime, logistics time, and
waiting or administrative downtime. Inherent availability is expressed by
the equation:
A = MTBF
MTBF + MTTR
Where MTBF = means time between failures
MTTR = means time to repair
SINGLE POINT FAILURE
Any piece part, assembly, component, or element of construction, such as
printed circuit board layout, the failure of which would result in irreversible
degradation of item performance below contractually specified levels, such as
failure of an item in operation which could be catastrophic to a mission
objective.
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290016-7