Downloaded from https://www.everyspec.com MIL-HDBK-502: A MIL-HDBK-502: A CQUISITION CQUISITION L OGISTICS OGISTICS human judgments and estimates will be substituted for hard data. But this approach does result in the decision as to the program’s supportability targets of improvement. Performance specifications are streamlining the acquisition process by imposing fewer restrictions and giving more decision flexibility to the developer. Many of these programs include a “fast track” approach in scheduling as well. The schedules of these fast track programs may be making it impossible to accomplish all of the supportability analyses that should be accomplished given the type of acquisition.
In this situation select those activities that offer the greatest potential return on the investment. 4.2.5 Prior Work Results Work previously accomplished can seriously impact the analysis selection. Support drivers and improvement initiatives may already have been identified, developed as inputs in the preparation of program documents. The quality and currency of the available results must be assessed, but if deemed adequate, the work already done may eliminate the need for further iterations or limit the effort to one of updating the available results.
However, if the stated requirements or constraints are based upon previously conducted analyses it is essential to test their currency before adopting them as hard limitations. For example, if a supportability requirement such as repair turnaround time for a new system was based upon a preliminary demonstration of a new technology, such as a new composite repair procedure, obtain and evaluate updated repair procedure information before accepting the previously developed requirement. 4.2.6 Available Data and Experience The availability, accuracy, and relevancy of experience and historical data on similar existing systems is crucial for accomplishment of some supportability analyses.
Available data must be examined to determine how much work is needed to provide the necessary focus or relevancy to the new system design. If such data is not available, a special "sample data" effort should be considered to create an analysis baseline, particularly if the needed data is in an area of possible high risk or opportunity. The objectives and specific supportability analysis activities, including the depth to which they are conducted, also depend upon the acquisition phase of the program. As previously indicated, the acquisition phases are generally defined by the state of design development of a hardware/software element of the total system.
Program requirements and objectives should be aligned with the phase of the acquisition process that most closely represents the design activities to be accomplished. Too often acquisition programs attempt to make decisions before sufficient 4-9