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

More documents

Recommendations

Info

MIL-HDBK-502: ACQUISITIONALOGISTICShuman judgments and estimates will be substituted for hard data. But thisapproach does result in the decision as to the program’s supportabilitytargets of improvement.Performance specifications are streamlining the acquisition process byimposing fewer restrictions and giving more decision flexibility to thedeveloper. Many of these programs include a “fast track” approach inscheduling as well. The schedules of these fast track programs may bemaking it impossible to accomplish all of the supportability analyses thatshould be accomplished given the type of acquisition. In this situationselect those activities that offer the greatest potential return on theinvestment.4.2.5 Prior Work ResultsWork previously accomplished can seriously impact the analysis selection.Support drivers and improvement initiatives may already have beenidentified, developed as inputs in the preparation of program documents.The quality and currency of the available results must be assessed, but ifdeemed adequate, the work already done may eliminate the need for furtheriterations or limit the effort to one of updating the available results.However, if the stated requirements or constraints are based uponpreviously conducted analyses it is essential to test their currency beforeadopting them as hard limitations. For example, if a supportabilityrequirement such as repair turnaround time for a new system was basedupon a preliminary demonstration of a new technology, such as a newcomposite repair procedure, obtain and evaluate updated repair procedureinformation before accepting the previously developed requirement.4.2.6 Available Data and ExperienceThe availability, accuracy, and relevancy of experience and historical dataon similar existing systems is crucial for accomplishment of somesupportability analyses. Available data must be examined to determine howmuch work is needed to provide the necessary focus or relevancy to thenew system design. If such data is not available, a special "sample data"effort should be considered to create an analysis baseline, particularly if theneeded data is in an area of possible high risk or opportunity.The objectives and specific supportability analysis activities, including thedepth to which they are conducted, also depend upon the acquisition phaseof the program. As previously indicated, the acquisition phases aregenerally defined by the state of design development of ahardware/software element of the total system. Program requirements andobjectives should be aligned with the phase of the acquisition process thatmost closely represents the design activities to be accomplished. Too oftenacquisition programs attempt to make decisions before sufficient4-9
MIL-HDBK-502: ACQUISITIONALOGISTICSknowledge of the design element is known. The result is always an increasein risk.4.2.7 Phase ConsiderationsEach of the acquisition phases is generally characterized by issues andobjectives associated with a particular level or state of a design (e.g.,conceptual, functional, allocated, physical). These issues and objectivesmust be satisfied through the milestone review procedures in order for aprogram to proceed.When permitted by regulation, the phase definitions should be redefined tofit the particular requirements of the program. Phase activities can becombined between two phases or a phase may be eliminated altogether.A supportability analysis effort evaluating existing support structure inconjunction with force/fleet analysis, threat analysis, and doctrinedevelopment must be conducted prior to entry into any acquisition phase.This effort is critical in developing supportable system requirements. Focusof the effort should be on a macro level and should identify the impacts onsustainment any requirement may have. The results should provide a basisfor tradeoffs in system capabilities during the actual acquisition phases(which may or may not follow), as well as ensuring that developedrequirements are actually achievable at affordable cost.Concept exploration phaseThe concept exploration phase, Phase 0, is the first phase of a DoDsystem’s life cycle. If it occurs at all, it typically consists of competitive,parallel short-term concept studies performed to investigate alternativeoperations and design concepts. The purpose is to identify, define, andevaluate the advantages/disadvantages, risks, costs, etc. of promisingoperational concepts and system design alternatives. The studies projectcharacteristics and costs of total systems as reflected by their conceptualdesigns. The results are reviewed at the Milestone I decision point wherepromising candidates may be selected for further definition anddevelopment.The design characteristics of the selected alternatives generally provide afunctional baseline of the system. These baselines define designperformance characteristics required to meet operational needs. Thefunctional baseline serves as the basis for establishing initial designthresholds and objectives. The resulting design requirements supportpreparation of total system design cost estimates and schedule projectionsand identification of trade-off opportunities. The system objectives are alsothe foundation for the acquisition strategy and the test and evaluationstrategy.4-10
Page 3: MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 9 and 10: MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 72 and 73:
MIL-HDBK-502: ACQUISITIONALOGISTICS
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?