MODERN OFFICE BUILDINGS UTILITIES ALTERNATIVES

Document Type: 
Collection: 
Document Number (FOIA) /ESDN (CREST): 
CIA-RDP89-00244R000200290006-8
Release Decision: 
RIPPUB
Original Classification: 
K
Document Page Count: 
27
Document Creation Date: 
December 22, 2016
Document Release Date: 
June 3, 2008
Sequence Number: 
6
Case Number: 
Publication Date: 
January 12, 1982
Content Type: 
REPORT
File: 
AttachmentSize
PDF icon CIA-RDP89-00244R000200290006-8.pdf775.02 KB
Body: 
Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 MODERN OFFICE BUILDINGS UTILITIES ALTERNATIVES PROJECT #9433 STATUS REVIEW STAT 12 JANUARY, 1982 TRW Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 as Z QLL Cv 00 LL00z J Z 0 J 2~~ I. v Q J W 0 J; C Q Z Q W W 0 W W W O Z Z a Z Q m a Q J W W Q I I 0 1 1 1 D i l l m a LL Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 PROJECT 9433 MODERN OFFICE BUILDING UTILITIES ALTERNATIVES ORGANIZE, PLAN. SCHEDULE ASSEMBLE TEAM TASK BREAKDOWN TASK ALLOCATION TASK SCHEDULES BUDGETS (MANPOWER. COMPUTING, REPRO, TRAVEL)/TRACKING ASSEMBLE REQUIREMENTS TOP LEVEL (SEE S.O.W.) DERIVED ? POWER ? ECS ASSUMPTIONS ? ARCHITECTURE IMPACT ? CONSTRUCTION IMPACT ? CLIMATIC STATISTICS GENERATE UTILITY SYSTEM CONCEPTS FMOOELSIill ARCHITECTURE IMPACTS SATISFY REQUIREMENTS AND REALITIES EVALUATE AVAILABILITY AND MISSION RELIABILITY FOR EACH CONCEPT BLOCK DIAGRAMS VALUES AT NODES AND FOR STRING POWER & ECS IN PARALLEL PREPARE DRAWINGS MODELS I St 11 1-"-0 EVALUATE COSTS INTERPRET. ANALYZE, DESCRIBE, PRESENT PATTERNS & RELATIONSHIPS TRENDS SENSITIVITIES UNCERTAINTIES ( OVERLAY CONCEPTS i ? POWER S, ECS ?~ - - - - -- - - - - - OF CONCEPTS ? ALLOCATION OVER AREA ITERATE OVER RANGE ? DISTRIBUTION TO AREAS COVER AVAILABILITY RANGE: A00 T ' ? ACQUISITION {-REPRODUCIBLES FROM ? OPERATION & I CUSTOMER FOOTPRINTS MAINTENANCE ,OBI DOLLARS) PREPARE FINAL REPORT DRAFT AND DELIVERY BRIEFING FINAL DOCUMENT O A0000 SEARCH Si PROJECT TECHNOLOGIES POWER CONVERSION TRENDS, EEFFICIENCIES, ECS ELECTRONICS E DEPENDENCE ON ENVIRONMENTS/RESOURCES Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 TRW Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 16 -a si ._ MW ail I H - - ^ ^ i t i 1 1 1 i t 11 1 . l i l 1 1 1 11 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 I I I 1 1 1 1 1 I I I ,, 1 1 1 1 1 1 1 t 1 1 1 1 1 I l i 11 1 1 1 1 1 1 1 1 1 ~~ ? I -s 1 1 i ar =- 1 1 1 1 1 1 1 1 1 1 , 1 1 1 1 1 1 1 1 1 1 1 1 1 1 I I I 1 1 1 1 1 1 1 1 1 1 1 1 I I I 1 1 1 III 1 1 1 III 1 1 1 1 1 1 u x ? J f 11 1 1 1 1 1 1 1 11 1 1 1 1 1 11 MM~~11 I 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 1 I I I 1 1 1 11 1 1 1 1 11 1 1 1 1 1 1 1 1~ 1 1 1 1 I I I r IYJI1 1 11 1 1 1 1 1 1 1 1 1 i l l 1 1 1 I l i I 1 1 1 1 1 1 1 11 1 11 1 i 1 1 131 I IC 1 tW1 1 i I I 111M0I 4 I I Wi ? i l, i i i I i i 1 1 1 IW i 131 1 Iv I I I I I IQ I I I I I I~1 I ICI 1 1 1 1 1401 I I4 t IWI 1 1, 1 t i t I 1401 1 1 1 i i i I i i 1 1 1 I i I I I I 1 4 W r1 I ill S I~1 1 I=1 Iig 1 1 1~ t 15 1 181 1 ICI t I~1 IQ 1 IQI I ~) ~ IJIN 11 1 IM t 1 1 I 1,y~~1, V' 1 1 IZI~1 1 1 1 1 1 , 1 I 1 Q I9 I Ifl~i IW 1 CI t 1~1 ICI I I 1 IG~1 IF Y 3 I 1 I 1 1 , 1 1 1 .1 1 1,y I~1 1 I I I i i i i 1 I I I Igfg4 I~~ 1~1 1 I'f~,s I I~1 I ICCi I ~ IM t I ItOi l i I 1 =i Ityl 1 i y l I t IJ i I~.I 1 13, , IWI I I `V ti yn - o p99~ ? j, g ~~ S yoo7d ~ ? # yoo~~ ~ ~ 2 roo> - - / yo o7! < 1714y: VN; I r Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 -~+ N ~- I- o ~~ ~d I ?g j tly IL , I I I _ i1 } i Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 0 a 0 Ow a W ~cq E- .oc Q a Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 ~_ m Q W W N ? 0 W I- a a Z J 0 OQ W a > } CO) io cC~!ic~~Q~~mccuQQ~~~?-ao~C!ao QOf OlCC))CO)OCOfaOlQfCW ) CQ~'1 Qf, 0f. ~ 001. CO CD C!, O 0 0 0 0 0 0 0 0 0 0 0 W ZJ Y m N CC Lu y Q A yE;. }ZOO JOCCC QO~NC Io o mcca< 0 ZZ O-OOOOOOMWcc m JWW ' ~ ZZZZZZ V)1-ma W J J y V! N V! V! V) N cn H Z Z Vpjj>>j~mC7C7 H I Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 ui .- coed C ONS as aAas ("X (x ( O AAA SRI '4 oo? aom a 44 Sao ~ ~ o00 000 Z (A u w all 1 0) J O O O O O O C.~m w - M ~~ V~ N M 2a, as p 2 o00 000 W C9 } coo GO Gm as c rc-I co 00 w G., w w 0! w C61 ca w~ . 000 000 W 0 w ~p w > Q ) ) Q) O O a ccaZ 000 000 N W J ~~~ 0))"'S) S L0 20 www 000 w 0 000 20. 0 C., 0 < a. J W z CC W ui y m z Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 N I- lb r-ft l- III W } 000 ?m0 Q1D LO to w 10 a IS ?b a OM 000 000 c NNN m! a! at A at ?00 000 W W C) cD CO tD 3 coo ;Q cc cc IM'a 83(1 aa8 a W C C O O O C J cc W ?C W o Dl 8 (on O! 8 3 2 d C d d O O C O v cc I F- W -i z 0. cr. } W (a W M W z cc I- Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 o ~ N N O a c~ N 0 a 8 O O LrC2 g 0 N OO O W Co CC Ir W $ z ca a 2 0 @LLO U. CL O mo CL O J > C) W O D v I I 0 25 g (lvWa3Hl) SllVMO1I)I 'avoi DNI1003 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 H } G Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Q W Q a J 04 19\14 j v\ N J I ~3 CC H W = 2 Mao ~ RZ 0 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 W I Z } I Le Q - Z W m IL W , V J < N Z W W 0 Z N Z 0 I- ~o F.. N 8 OZ =0 I-- W - C u1 y r W 0 W W 0 Vcc QmO Z W 0 Q V oO W Z CC W zQ38 ZHRN Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 ~C'l N 1 _1@ O W z L ?a o a. Q 4 1 W W F- ~Q H LLy 4N > z om~ OW W OW O~ O cgi k N 0 (1vWU3H1) SllVMO1DI - S"1300W O3NI9W03 "OVOl DNI1OO3 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Z, O z 49 > 0 1- N Co 00 J J C. d W C. ~a W 2 7~ 4 ,N N 0 Wglo 4gC04 Jy gas 00 C7 y 4 W 3 W ?~ J N v J W 3 4m mg 104-4 1] 2 W i 0 2 O No) s N k 2 g W W > J . ^ J V J ca Q W JaQ~~t7 Q m J ?~~ J J = D O 0 W c .o Of G N 191- (7 Q y W Wp ;;i 0. 0 o C7 I CC y ~ P, 3: C) V Z W W O O N--~ N J C ,~ W W 2 1_VOJ =>Co W LL, S W a I- p I 20 N W W Q N N W J 0LAA N Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 W 0 Co > U) CL Z ~W- Z N cc Q _j c> a ncc a Jp QaU Q U > Q Z Z 0 0 Q Q I CD 0 O Q Z Z O m O M W Q.O CL OZ Q W Q W W J J2C7 W W W ^ W'' O O Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 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) Performance - parameters and allowable limits c) Functional and physical boundaries d) 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-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 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-00244R000200290006-8 3 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 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-00244R000200290006-8 ? Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 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 fo 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-00244R000200290006-8 Approved For Release 2008/06/03: CIA-RDP89-00244R000200290006-8 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-00244R000200290006-8