everyspec.com n/a — MIL-HDBK-502: Department of Defense Acquisition Logistics Handbook PDF Download (EN)

Downloaded from https://www.everyspec.com MIL-HDBK-502: A MIL-HDBK-502: A CQUISITION CQUISITION L OGISTICS OGISTICS 7.4 EXPLANATION OF LMI DATA PRODUCTS The LMI individual data products are organized alphabetically in Appendix B of the LMI specification. Appendix B contains definitions and format criteria for each of the data products. Specific data products needed for delivery may be specified by the requiring authority on the data product worksheets (Worksheet 2, Figure 2, in Appendix B of the LMI specification). The hollow data item descriptions (DID), DI-ALSS-81529 (Data Products) and DI-ALSS-81530 (LMI Summaries) can be used to contract for one or more data products.

If multiple data product deliverables are required at different times, this DID can be called out multiple times. For example, a requiring authority may want a Long Lead Time Items List (LLTIL) and another provisioning list which is not required as early as the LLTIL. Data required from Appendix B of the LMI specification should ultimately populate internal government data processing systems necessary for item fielding and sustainment. Alternative methods for delivering this data to its final destination are strongly encouraged and should be considered by the requiring authority.

7.4.1 Life Cycle Application of LMI Data Logistic support resource needs associated with proposed systems, such as those depicted by LMI data, must be identified and refined as the system progresses through its development. The extent of the identification depends upon the type of acquisition (e.g., NDI, commercial, new start, etc.), the maintenance concept (e.g., full organic, interim contractor support, lifetime contractor support), the complexity of the system, and the phase of the acquisition cycle.

As development progresses and the basic design and operational characteristics are established, this identification becomes a process of analyzing specific design and operational data to identify detailed logistics support needs more completely. This analysis can be very costly and involve the development of a considerable amount of data. In determining the timing and scope of this analysis and the corresponding data, consider the following points: 1. Early identification of logistics support resources should be limited to new or critical requirements. 2.

Logistics support resource requirements for different system alternatives should only be identified to the level required for evaluation and tradeoff of the alternatives. 3. Logistics support resources must be identified in a time frame which considers the schedule of developing required documentation (e.g., 7-17