MIL-HDBK-502 - Barringer and Associates, Inc.

More documents

Recommendations

Info

MIL-HDBK-502: ACQUISITIONALOGISTICSinvestigation results. The strategy is developed in line with the acquisitiondecision and the associated systems engineering and other program activityrequirements associated with the type of acquisition decision. Theserequirements are further tailored based upon specific program needs andconstraints.Traditional DoD acquisition environments, based primarily uponproprietary products and isolated data processing systems have resulted ina costly, poorly integrated, and closed (rather than open) infrastructure inmost organizations. The open systems approach mandated by current DoDpolicy (reference DoD 5000.2-R, paragraph 4.3.4) encompasses theselection of specifications and standards adopted by industry standardsbodies or de facto standards for selected system interfaces, products,practices, and tools. Open systems standards define interfaces whichsupport portability, interoperability, and scaleability (i.e., expansion); andare available to the public. Potential benefits realized from the use of opensystems standards include reduced costs, increased competition, andincreased interoperability. Note, however, that an open system standard ISNOT SYNONYMOUS with the use of commercial and non-developmentalitems (C/NDI) . An open systems standard is primarily concerned withinterface compatibility to promote interoperability between multiplesuppliers’ equipmentIdeally, open systems represent a transparent environment in whichusers can intermix hardware, software, and networks of differentvintages from different sources to meet differing needs. In reality,systems are not purely open or closed. Because industry standardsdo not generally meet all military needs, trade-offs must be madebetween performance, cost, supportability, availability of standardsbasedproducts, and the ability to upgrade. The result is that for anygiven system, the degree of openness may have manyinterpretations.As with any integrated effort, supportability analysis activities must bealigned with the related systems engineering disciplines whose activitiesprovide essential support planning information relative to the hardware andsoftware designs.4.2.3 Design FlexibilityThe degree of flexibility in the total system hardware, software, andsupport system designs is a basic consideration in deciding whatsupportability analyses can and should be performed.The objective of most support system design activities is to identify supportconsiderations (e.g., constraints) which may influence selection of systemhardware and software design and support alternatives to improve4-7
MIL-HDBK-502: ACQUISITIONALOGISTICSreadiness, supportability, and cost. If the hardware design is fixed, as itwould largely be in a commercial or NDI acquisition, these early analysesmight seem to have little benefit. In the case of product improvementprograms, the scope of proposed improvements might limit designflexibility to specific subsystems and may or may not open non-affectedareas of the design to redesign opportunities that would address changes toreduce the anticipated support burdens.Flexibility may exist for the design of the support system but not in thehardware system. Commercial items for which maintenance support planshave not been developed are typical examples of this situation.Integrating supportability requirements into system and equipment designrequires that designers be oriented toward supportability objectives fromthe outset. Technical information generated during the design process mustbe disseminated among designers and members of the supportabilitydisciplines to surface interface problems. Technical design information—diagnostic features, electromechanical interfaces, reliability estimates, itemfunctions, adjustment requirements, and connector and pin assignments—that determines supportability should be an integral part of designdocumentation. When design flexibility exists, the performing activity's planshould describe the generation, control, and approval of this type of designdocumentation.4.2.4 Available ResourcesSupportability analyses require time and resources. It is pointless to imposesupportability requirements that depend upon an analysis whose resultsmay not be available in time to contribute to the design decisions whichthey are intended to affect. The exception to this rule would be a situationwhere the potential improvement can be included as part of future preplannedproduct improvements such as technology insertion programs.It is DoD policy to fund readiness and support considerations in the frontend of programs. Nevertheless, resources are constrained in practice. Ifprogram funds are short, it may be possible to perform some activities,such as the requirements definition activities, with in-house capabilities. Ifthe in-house capability is limited but funds are available, such analysesmight also be accomplished by "program support" contractors with therequired expertise.Another approach is to capitalize on the interrelationships between theanalyses. For example, an analysis of an existing system feeds theidentification of supportability drivers of a new system. These, in turn, feedthe selection of targets for supportability improvement in the new system.If, for some reason, only one of these activities could be afforded, then theidentification of targets for improvement would be the logical pick of thetwo. The process of target identification will obviously lose precision since4-8
Page 3: MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 9 and 10: MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 70 and 71:
MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
show all

MIL-HDBK-502 - Barringer and Associates, Inc.

Create successful ePaper yourself

Delete template?

Save as template?