<strong>MIL</strong>-<strong>HDBK</strong>-<strong>502</strong>: ACQUISITIONALOGISTICSSection 7:Support Data7.1 SUPPORT DATA“Data requirements shall be consistent with the planned support concept<strong>and</strong> represent the minimum essential to effectively support the fieldedsystem. Government requirements for contractor developed support datashall be coordinated with the data requirements of other programfunctional specialties to minimize data redundancies <strong>and</strong>inconsistencies.” This direct quotation from paragraph 4.3.3.3 of DoD5000.2-R makes it clear that support data requirements must becoordinated with data requirements from other program elements. Notexplicitly stated, but clearly implied, is the need for the different functionalelements of support to coordinate their data requirements also.SOURCES FOR SUPPORT RELATED DATAConsider obtaining these types of data:Reliability Availability <strong>and</strong> Maintainability (RAM)Logistics Management Information (LMI)Technical PublicationsTransportabilityTrainingFrom these kinds of sources:Industry st<strong>and</strong>ardsOther commercial or military customersFigure 7-1. Support Data SourcesLMI specification summariesContractor’s in-house dataAs with the non-logistics functional specialties, the different functionalelements of support must coordinate with each other in order to eliminatebuying redundant support data. For example, it would be possible for alogistician to get reliability <strong>and</strong> maintainability data through one of thelogistics management information (LMI) summaries or, as Figure 7-1indicates, from commercial or government sources. However, if the sameinformation is being delivered to the reliability availability <strong>and</strong>7-1
<strong>MIL</strong>-<strong>HDBK</strong>-<strong>502</strong>: ACQUISITIONALOGISTICSmaintainability (RAM) community via industry st<strong>and</strong>ards, then thelogistician should utilize it <strong>and</strong> not buy redundant data. On the other h<strong>and</strong>,some of the reliability <strong>and</strong> maintainability data a logistician would like tosee may not be delivered to the RAM community. In this case, one of theLMI summaries, such as Maintenance Planning, could be utilized to get thenecessary data. If RAM data is requested on this summary, the data shouldbe in the same format <strong>and</strong> have the same definition that is specified inappropriate RAM st<strong>and</strong>ards. This restriction precludes levyinggovernment-unique requirements on the contractor.The remainder of this section will focus on using the LMI performancespecification as a source for support data. Remember, this specification isnot the only source of support data. In fact, its specific definitions inAppendix B are mainly for provisioning, packaging, cataloging, <strong>and</strong>support equipment, but the LMI specification summaries can be used toobtain information in other support areas.7.2 <strong>MIL</strong>-PRF-49506, LOGISTICS MANAGEMENTINFORMATIONAs a result of the Secretary of Defense’s policy on usage of specifications<strong>and</strong> st<strong>and</strong>ards, <strong>MIL</strong>-PRF-49506, LMI, has been developed to replace <strong>MIL</strong>-STD-1388-2B. It is not a revision of <strong>MIL</strong>-STD-1388-2B. Rather, itrepresents a fundamental change in the way data requirements are levied oncontracts. <strong>MIL</strong>-PRF-49506 does not contain any “how to’s.” The newspecification is designed to minimize oversight <strong>and</strong> government-uniquerequirements. The underlying philosophy of <strong>MIL</strong>-PRF-49506 is to allowcontractors maximum flexibility in designing systems <strong>and</strong> developing,maintaining, <strong>and</strong> providing support <strong>and</strong> support related engineering data. Inorder to achieve this objective, the new specification has the followingcharacteristics:1. The principal focus of <strong>MIL</strong>-PRF-49506, LMI, is on providingDoD with a contractual method for acquiring support <strong>and</strong>support related engineering data. The Department of Defenseuses this data in-house in existing DoD materiel managementautomated systems such as those for initial provisioning,maintenance planning, cataloging, support equipment data, <strong>and</strong>item management.2. Data products intended primarily for in-house use by contractorsduring their design process or those developed internally by theDepartment of Defense are beyond the scope of thisspecification.7-2