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

More documents

Recommendations

Info

MIL-HDBK-502: ACQUISITIONALOGISTICS7.4 EXPLANATION OF LMI DATA PRODUCTSThe LMI individual data products are organized alphabetically in AppendixB of the LMI specification. Appendix B contains definitions and formatcriteria for each of the data products. Specific data products needed fordelivery may be specified by the requiring authority on the data productworksheets (Worksheet 2, Figure 2, in Appendix B of the LMIspecification). The hollow data item descriptions (DID), DI-ALSS-81529(Data Products) and DI-ALSS-81530 (LMI Summaries) can be used tocontract for one or more data products. If multiple data productdeliverables are required at different times, this DID can be called outmultiple times. For example, a requiring authority may want a Long LeadTime Items List (LLTIL) and another provisioning list which is notrequired as early as the LLTIL.Data required from Appendix B of the LMI specification should ultimatelypopulate internal government data processing systems necessary for itemfielding and sustainment. Alternative methods for delivering this data to itsfinal destination are strongly encouraged and should be considered by therequiring authority.7.4.1 Life Cycle Application of LMI DataLogistic support resource needs associated with proposed systems, such asthose depicted by LMI data, must be identified and refined as the systemprogresses through its development. The extent of the identificationdepends upon the type of acquisition (e.g., NDI, commercial, new start,etc.), the maintenance concept (e.g., full organic, interim contractorsupport, lifetime contractor support), the complexity of the system, and thephase of the acquisition cycle. As development progresses and the basicdesign and operational characteristics are established, this identificationbecomes a process of analyzing specific design and operational data toidentify detailed logistics support needs more completely. This analysis canbe very costly and involve the development of a considerable amount ofdata. In determining the timing and scope of this analysis and thecorresponding data, consider the following points:1. Early identification of logistics support resources should be limited tonew or critical requirements.2. Logistics support resource requirements for different system alternativesshould only be identified to the level required for evaluation and tradeoffof the alternatives.3. Logistics support resources must be identified in a time frame whichconsiders the schedule of developing required documentation (e.g.,7-17
MIL-HDBK-502: ACQUISITIONALOGISTICSRPSTL, SERD) or completing a required action (e.g., initialprovisioning).4. Different levels of data documentation can be applied to theidentification of logistics support resource needs. For example, early in aprogram, supply support needs can be identified through documentationof only a few data products (e.g., Reference Number, CAGE, ItemName, PCCN, and Usable On Code); later the total range of dataproducts required to accomplish initial provisioning can be documented.5. Detailed input data for identification of logistics support resource needsis generated by other systems engineering functions; for example, RAMfailure rates drive the calculation of the provisioning MaintenanceReplacement Rates. Therefore, analysis, documentation requirements,and timing must be coordinated between the systems engineeringprograms to avoid duplication of effort and to assure availability ofrequired input data.7.5 LMI WORKSHEETS: HOW TO USE THEMThe LMI worksheets can be used to specify information for LMIsummaries identified in Appendix A of the specification and to select dataproducts identified in Appendix B. The worksheet for the LMI summariesis Worksheet 1, Figure 1, located in Appendix A of the specification. Theworksheet for the data products is Worksheet 2, Figure 2, in Appendix B.These worksheets do not have to be used. The requiring authority mayhave other means which may be simpler and more efficient. However, ifthese worksheets are used, the following paragraphs provide detailedinformation on how to fill them out.7.5.1 LMI SummariesEight functional summaries are identified in Appendix A of the LMIspecification. These summary write-ups are neither all inclusive orexclusive and are intentionally described in general terms to encouragemaximum flexibility. Project offices should tailor these summaries to fittheir information needs.Any timing issues, specific level-of-detail guidance, or other informationregarding a given summary should be documented in the SpecificInstructions section of Worksheet 1. The Specific Instructions area allowsthe requiring authority to add program-specific needs or give generalinformation regarding the summary.Data content for each summary must be identified either in Worksheet 1,Figure 1, Appendix A, or in some other way, and put in the contract.Remember that the content of a summary is not limited to informationidentified in the LMI specification, Appendix A narratives, or Appendix B7-18
Page 3:
MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 9 and 10:
Page 11:
Page 14:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37: MIL-HDBK-502: ACQUISITIONALOGISTICS
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?