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

More documents

Recommendations

Info

MIL-HDBK-502: ACQUISITIONALOGISTICSsignificant investment in the materiel asset, ensure that provisions for futuretechnology insertion are considered. In determining the most cost effectivemeans of support, the service life of a product will be a factor in thedecision to use contractor versus organic support. Further, the longer theanticipated service life, the greater the need for planned product upgradesto maintain currency of capability and to reduce support costs by usingcurrent technology. Maintaining a support capability for outdatedtechnology is expensive and limits opportunities to use contractor supportbecause the number of sources that can support the older technologyreduce dramatically as it is replaced with new technology.Standardization and interoperabilitySynthesisStandardization and interoperability are primary sources of designrequirements and constraints for a system. The difference betweenrequirements and constraints can be a pretty fine line. And while it does notreally matter as long as the need is correctly stated, generally, requirementsare used to define acceptable solutions and constraints to limit them.Interoperability with other systems and equipment may lead tostandardization opportunities in both functional or physical design efforts.A functional standardization requirement is one which establishes the needfor a particular capability such as transmitting a specified signal frequency.The hardware design, in that case, would not be restricted to a singlesolution. A physical standardization constraint, on the other hand, whichimposes the use of a specific transmitter, dictates that portion of the systemdesign.Standardization requirements are also derived from the software andsupport system design concepts. Mission software standardization needsmay dictate the use of compatible computer hardware, operating software,or program languages. Support standardization could includestandardization of the support concept with the support concepts of otheroperational systems, or the use of specific support resources. An organicsupport concept, for example, might lead to specific hardware testabilityrequirements ensuring diagnostic support by existing test equipment, or arequirement to perform field level maintenance with existing tools.The outcome of the FA/A segment should be supportability constraints thatare the basis for developing initial supportability requirements expressed asthresholds (minimum acceptable value) and objectives (desired value). Thespread between objective and threshold values will be individually set foreach program based on the characteristics of the program (e.g., maturity,risk, etc.). The range between the objective and the threshold is known as5-5
MIL-HDBK-502: ACQUISITIONALOGISTICSthe "trade space." Program objectives may be refined based on the resultsof the preceding program phase.These supportability constraints should be analyzed through acomprehensive systems analysis effort conducted during the Synthesissegment. This effort should include a systems effectiveness/cost analysisthat weighs supportability constraints against each other and against userrequirements, other system parameters, and life cycle costs. Tradeoffstudies within this effort should establish alternative performancerequirements (supportability included) to satisfy operational and missionneeds. Preliminary support concepts should also be examined at this time inlight of constraints imposed by the user’s operational and readinessrequirements. The support concept is a critical element in determining bothspecification and support resource requirements, and it needs to be updatedthroughout the systems acquisition process to reflect modifications to thesystem and changes in the operation and maintenance requirements. Thisupdating will enable supportability requirements to accurately reflect theevolution of the operational system.Supportability RiskRisk assessment of the supportability constraints and concepts should alsobe an integral part of the systems analysis effort. These assessments shouldidentify risk drivers, determine the sensitivity of interrelated risks, andquantify risk impacts. A major risk factor in defining the operating andsupport environment is the difficulty in describing the environment as it willbe, and not as it is. Depending upon the type of acquisition, the timeseparation between this initial description of a system’s operationalenvironment and the time of fielding can be many years. It is logical toexpect the operating and support environment to change during that timeas new products, new personnel skills, new support resources, and newoperational needs are introduced, and economic considerations change. Butthese changes must be identified and factored into the supportabilityanalyses to ensure that planning assumptions and decisions for the supportsystem can be adjusted.To get a good picture of the overall suitability of support systemrequirements, it is important to consider the best and worst case operatingscenarios. System supportability should be assessed under both peacetimeand wartime scenarios. Peacetime support planning is based uponequipment readiness and economic considerations. Repair decisions in thisscenario are made to reduce the cost of obtaining replacement products.A wartime scenario should include both surge and sustained rates ofoperation. Wartime support planning is driven by equipment readiness oroperational availability. Detailed component repair may be discarded infavor of major subsystem replacement to reduce system downtime5-6
Page 3: MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 9 and 10: MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 86 and 87:
MIL-HDBK-502: ACQUISITIONALOGISTICS
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.

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?