Хорошев / ИЛП_материал_маг_02.15 / Спецификация AECMA Specification 2000M / MIL-STD-1388-2B

MIL-STD-1388-2B

1.SCOPE.

1.1 Purpose. This standard prescribes the data element definitions (DED), data field lengths, and formats for Logistic Support Analysis (LSA) Record (LSAR) data. It identifies the LSAR reports that are generated from the LSAR data and identifies the LSAR relational tables and automated data processing (ADP) specifications for transmittal and delivery of automated LSAR data.

1.2 Application of standard. This standard applies to all system/equipment acquisition programs, major modification programs, and applicable research and development projects through all phases of the system/equipment life cycle. This standard is for use by both contractor and government activities. As used in this standard, the requiring authority is generally a government activity but may be a contractor when LSA documentation requirements are levied on subcontractors. The performing activity may be either a contractor or government activity. The use of the term, contract, in this standard includes any document of agreement between organizations to include between a government activity and another government activity, between a government activity and a contractor, or between a contractor and another contractor.

1.2.1 Content of appendices. There are six appendices in the standard. Appendix A contains the LSAR relational tables necessary for the development of a relational LSAR database. A description and the required format for each LSAR report is contained in appendix B. All reports contained in appendix B may be generated either manually or via automated techniques by using the LSAR data defined in this military standard. Appendices C, D, and F are guidance appendices covering assignment of the key data elements LSA Control Number (LCN), Alternate LCN Code (ALC), Usable On Codes (UOC); tailoring of the LSAR data; and, LSAR acronyms. Appendix E contains an LSAR Data Element Dictionary providing definitions for all data specified by appendix A. All appendices, except for C, D, and F, establish requirements and can be included/referenced in contractual documents.

1.2.2Tailoring. This standard shall not be specified in a contract without also specifying MIL-STD-1388-1, LSA. The requiring authority will use MIL-STD-1388-1 in the selection of tasks for inclusion in the contract statement of work (SOW) and shall establish the LSA documentation requirements based upon the elements identified in those tasks. Further tailoring of LSA documentation requirements shall be based on MIL-STD-1388-1 tasks performed in previous program phases, other system engineering program requirements, and logistics related data item descriptions (DID) included in the solicitation document. Detailed guidance on tailoring the LSAR data requirements is included in appendix D.

1.2.3LSA data documentation process. The LSA process is conducted on an iterative basis through all phases of the system/equipment life cycle to satisfy the support analysis objectives. Similarly, LSA data is generated in all phases of the system/equipment life cycle and is used as input to

follow-on analyses and as an aid in developing logistics products. Although automation of the LSAR data as depicted on figure 1 is not mandatory, it is strongly encouraged and should be a consideration in tailoring the LSA data effort. A more detailed display of the LSAR data flow and its interface, with the system engineering and the logistics functional organizations, is

- 1 -

MIL-STD-1388-2B

- 2 -

MIL-STD-1388-2B

- 3 -

MIL-STD-1388-2B

- 4 -

MIL-STD-1388-2B

:

- 5 -

MIL-STD-1388-2B

provided on figure 2. The figure represents general data table generation relationships and organizational elements normally responsible for generation of LSAR data. Figure 2 should not be misconstrued to mean that one type of data table must be completed in its entirety before the next data table can be completed. For example, certain reliability and maintainability (R&M) estimates included on the B tables must be completed prior to estimating logistics elements on other tables (R&M relationships are shown on figure 3). However, generation of LSAR data is also dependent on the design engineering process and release of drawings (preliminary, development, or final). Completion of B and C tables for a single assembly would provide the information necessary for initiation of data tables associated with support items (H tables), and also data related to support and test equipment (E & U tables), facilities (F tables), and skills evaluation and justification

(G tables) when peculiar requirements are identified. The LSAR data flow will be repeated for each repairable item comprising a system/end item until the total logistics data requirements are established.

2.REFERENCED DOCUMENTS.

2.1 General. Completion of the LSAR data requires use of many related documents from which the appropriate data/codes can be obtained. The specific use of each document is identified in the appropriate section or appendix of this standard. Unless otherwise specified, the following standards and handbooks of the issue listed in that issue of the Department of Defense Index

- 6 -

MIL-STD-1388-2B

- 7 -

(Unless otherwise indicated, copies of federal and military specifications,

- 8 -

Industry Documents.

ANSI Y32.16 Reference Designations for Electrical and Electronics Parts and Equipments

(Non-Government standards and other publications are normally available from the organizations that prepare or distribute the documents. These documents also may be available in or through libraries or other informational services.)

3. DEFINITIONS. The LSAR data elements are defined in the description of the LSAR reports contained in appendix B and in the LSAR data element dictionary comprising appendix E of this standard. In addition, for the purposes of this standard, the following definitions shall apply:

3.1 Assembly. A number of parts or subassemblies, or any combination thereof, joined together to perform a specific function and capable of disassembly (e.g., power shovel-front, fan assembly, audio frequency amplifier). NOTE: The distinction between an assembly and subassembly is

- 9 -