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

More documents

Recommendations

Info

MIL-HDBK-502: ACQUISITIONALOGISTICS3. MIL-PRF-49506, LMI, is not intended to specify, define, orimply a requirement for contractors to establish or maintain anylogistic database.4. Electronic data interchange, on-line access, and all otherautomation issues are outside the scope of the specification andmust be addressed separately using other appropriate documentssuch as MIL-STD-1840.5. Information summaries are only examples of support informationthat DoD managers may want to request from contractors.These sample summaries are not all inclusive or exclusive andare intentionally stated in general terms to encourage maximumcontractor flexibility. Project offices can tailor samples to fittheir information needs.6. Contractors are strongly encouraged to offer support andsupport related engineering data to the government in their owncommercial formats if the data is readily available and can costeffectivelymeet DoD’s needs.7. MIL-PRF-49506, LMI, contains verification criteria basedstrictly upon performance.8. The LMI specification may be tailored down or tailored up (seesummary worksheet example, Figure 7-11).7.2.1 Guidance from DoD 5000.2-RThe following paragraphs discuss provisions of DoD 5000.2-R that relateto the execution of MIL-PRF-49506, LMI. The first few paragraphs touchon not imposing government-unique requirements and on issues related todigital data.To paraphrase paragraph 3.3.4.2: The government shall avoid imposinggovernment-unique requirements that significantly increase industrycompliance costs. Examples of practices designed to accomplish thisdirection include the open systems approach (one that emphasizescommercially supported practices, products, specifications, and standards);and replacement of government-unique management and manufacturingsystems with common, facility-wide systems.Furthermore, paragraph 3.3.4.5 states, “Beginning in FY97, all newcontracts shall require on-line access to, or delivery of, theirprogrammatic and technical data in digital form, unless analysis showsthat life-cycle time or life-cycle costs would be increased by doing so.Preference shall be given to on-line access to contractor developed datathrough contractor information services rather than data delivery. No ongoingcontract, including negotiated or priced options, shall be re-7-3
MIL-HDBK-502: ACQUISITIONALOGISTICSnegotiated solely to require the use of digital data, unless analysis showsthat life-cycle costs would be reduced.“Acquisition strategies and plans shall describe the extent ofimplementation of these requirements in accordance with DFARS207.105. Solicitations shall require specific proposals for an integrateddata environment to support systems engineering and logistics activities.The PM shall ensure compatibility of data deliverables with existinginternal information systems, and augment such systems as required toprovide timely data access and distribution consistent with DFARS 227and 252.”Paragraph 4.3.3.1 (the next paragraph) talks specifically to supportabilityanalyses. This quotation relates directly to Appendix A of the LMIspecification, “Supportability Analysis Summaries”: “Supportabilityanalyses shall be conducted as an integral part of the systems engineeringprocess beginning at program initiation and continuing throughoutprogram development. Supportability analyses shall form the basis forrelated design requirements included in the system specification and forsubsequent decisions concerning how to most cost-effectively support thesystem over its entire life-cycle. Programs shall allow contractors themaximum flexibility in proposing the most appropriate supportabilityanalyses.”7.3 EXPLANATION OF LMI SUMMARIESLMI summaries contain information that the government needs in order toassess design status, conduct logistics planning and analysis, influenceprogram decisions, and verify that contractor performance meets systemsupportability requirements. Appendix A of the LMI specification identifieseight types of summaries in broad, general terms and contains associatedworksheets that can be used to identify the content of the summaries.Please note that these summary titles do not have to be used. For example,the requiring authority could identify on the worksheets a summary for aLong Lead Time Items List with the necessary content, instead ofspecifically calling out a Supply Support summary.The LMI summaries may include any information deemed necessary by therequiring authority. The summaries can include data products fromAppendix B of the LMI specification, or they may include information notin Appendix B. If a summary contains data or information not defined inAppendix B, the requiring authority must specify the definition and format(or reference the governing or appropriate standard or specification) forsuch information.The LMI summaries can be delivered as stand-alone reports or as anintegral part of other systems engineering documentation. Requirements forthese summaries should be coordinated with data requirements of other7-4
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: MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 23: MIL-HDBK-502: ACQUISITIONALOGISTICS
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?