Attachment 19 LSAR MIL-STD-1388-2B.PDF

NOT MEASUREMENT

SENSITIVE

MIL-STD-1388-2B

28 MARCH 1991

SUPERSEDING

MIL-STD-1388-2A

20 JULY 84

MILITARY STANDARD

DOD REQUIREMENTS FOR A

LOGISTIC SUPPORT ANALYSIS RECORD

AMSC NO. A6045 FSC ILSS

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

Downloaded from http://www.everyspec.com

MIL-STD-1388-2B

FOREWORD

1. This military standard is approved for use by all departments and agencies of the Department of Defense (DOD).

2. Beneficial comments (recommendations, additions, deletions) and any pertinent data which may be of use in improving this document should be addressed to:

a. Director, OASD(P&L) Weapon Support Improvement Group Room 2B322 Pentagon Washington D.C.

Telephone: (703) 756-8420

b. USAMC Materiel Readiness Support Activity

ATTN: AMXMD-EL

Lexington, KY 40511-5101

Telephone: (606) 293-3962

3. Each DOD service maintains a Logistic Support Analysis (LSA) support office . In order to ensure that a service-wide position is presented to the proponent office, comments originating with a particular DOD service should be forwarded through that service’s LSA support office as listed below:

a.

b.

c.

Air Force:

ALD/LSA

Wright Patterson AFB, OH 45433

Telephone: (513) 255-3754

Army:

Commander, USAMC Materiel Readiness Support Activity

ATTN: AMXMD-EL

Lexington, KY 40511-5101

Telephone: (606) 293-3964

Marine Corps:

Commanding General, Marine Corps Research, Development and Acquisition Command

ATTN: PSL-S

Washington, D.C. 20380-0001

Telephone: (703) 696-1180 ii

d. Navy:

Commander, Naval Air Systems Command

ATTN: NAVAIR 41112

Washington, D.C. 20361

Telephone: (703) 692-0028

4. Comments may be submitted using the self-addressed Standardization Document Improvement Proposals (DD Form 1426) appearing at the of this document, or by letter,

5. This standard is based on the joint efforts of the military services and the Federal Aviation Administration with assistance from private industry. The goal of this standard is to establish uniform requirements for development and delivery of LSA Record (LSAR) data. The LSA documentation, including LSAR data, is generated as a result of performing any or all of the analyses specified in MIL-STD-1388-1, Logistic Support Analysis (LSA). The requirements of this standard are applicable to major and less than major system/equipment acquisition programs, major modification programs, and applicable research and development projects.

6. The LSAR, as designed herein, is intentionally structured to accommodate the maximum range of data potentially required by all services and all Integrated Logistic Support (ILS) element functional areas, This approach permits standardization of field lengths and data element definitions (DED), and establishes “one face to industry” for government required LSAR data.

However, LSA documentation must be tailored to each acquisition program and life cycle phase. The tailoring of LSAR data should be consistent with the level and depth of LSA performed in accordance with (IAW) MIL-STD-1388-1 as required to readiness and affordability of the acquisition program in accordance with Department of DOD Directive (DODD) 5000.39. An application guidance appendix (appendix D) is included herein to provide guidance on tailoring of LSAR data requirements to meet individual program objectives in a cost-effective manner. The general requirements of this standard also require completion of LSAR data selection sheets (DD Form 1949-1) to identify specific data for each program in order to prevent indiscriminate blanket applications of the data requirements.

7. This standard is directed toward improving the cost effectiveness of the generation, maintenance, acquisition, and use of the technical data required to support an ILS program. This is accomplished through the following:

a. Standardization of LSAR DEDs, field lengths, and formats between the services and industry.

b. Consolidation of logistics oriented technical information for the various engineering disciplines and ILS elements into one file to reduce redundancy, facilitate timely usage, and enhance consistency between elements and disciplines.

c. Maximum use of industry developed integrated data systems tied to engineering, manufacturing, and product support databases as sources of LSA documentation.

iii

d. Requiring delivery of LSAR data in a format which promotes/ accommodates current database technology.

8. The LSAR documents data across all ILS functional areas. This characteristic makes the LSAR an ideal vehicle for integration of systems’ engineering design, manufacturing, and product support databases for life cycle management of a system. The relational design of LSAR data is intended to facilitate such integration and to encourage independent development of useful ad hoc queries which promote use of the data in the design process. The use of industry developed, cost-effective automation tools which link “islands of automation” (e.g., computerized drawings and technical manual authoring systems) through the LSAR is encouraged.

9. This standard allows for delivery of LSAR data in manual or automated mode, and online access to LSAR data, as specified by the requiring authority. It does not prescribe Automated Data Processing (ADP) software that must be used to process LSAR data. The minimum ADP design requirements that must be adhered to for industry developed LSAR ADP systems are described under General Requirements , paragraph 4.2.2.1. These requirements are the basis for validation by government of industry developed LSAR ADP systems.

10. Conversion of existing programs to MIL-STD-1388-2B data table format is encouraged. In order to assist in this effort the Materiel Readiness Support Activity will provide, on request, software to convert MIL-STD-1388-2A master files to MIL-STD-1388-2B data table format.

iv

CONTENTS

Paragraph

MIL-STD-1388-2B

Page

1.

1.1 1.2 1.2.1 1.2.2 1.2.3

2.

2.1

3.

4.

4.1 4.2 4.2.1 4.2.1.1 4.2.2 4.2.2.1 4.2.2.2

5.

5.1 5.1.1 5.1.2 5.2 5.2.1

5.2.2

5.2.3

5.2.4 5.2.5 5.2.6 5.2.7 5.2.8 5.3 5.4

6.

6.1 6.2 6.3 6.4 6.5 6.6

SCOPE

Purpose Application of standard Content of appendices Tailoring LSA data documentation process

REFERENCED DOCUMENTS

General

DEFINITIONS

GENERAL REQUIREMENTS

LSAR data selection sheets LSAR data Manual LSAR data Manual LSAR report generation

Automated LSAR data Performing activity LSAR ADP system LSAR ADP system criteria

DETAILED INSTRUCTIONS FOR MANUAL/AUTOMATED

PREPARATION OF LSAR RELATIONAL TABLES

Requiring authority data tables Cross functional requirement Operations and maintenance requirements Performing activity data tables Reliability, availability, maintainability;

Failure modes, effects and criticality analysis; maintainability analysis Task analysis and personnel and support requirements Support equipment and training material requirements Unit under test requirements and justification . .

Facilities considerations Personnel skill considerations Packaging and provisioning requirement Transportability engineering analysis LCN assignment and structure LSA/LSAR guidance conference

NOTES

Intended use Issue of DODISS Consideration of data requirements Subject term (key word) listing Suppression data Changes from previous issue v

APPENDIX

10.

20.

30.

30.1

30.2 30.3 40.

50.

60.

70.

80.

90.

100.

APPENDIX

10.

20.

20.1 20.2 30.

30.1

30.2 30.3 30.4 30.5 30.6 30.7 30.8 30.9 30.10

30.11 30.12

30.13 30.14

30.15 30.16 30.17 30,18 30.19

APPENDICES

A. LSAR RELATIONAL TABLES

SCOPE

CONCEPT

RELATIONAL DATA TABLE FORMAT

Functional LSAR relational table listing and table relationships LSAR relational tables

LSAR Data Table Exchange/Delivery

CROSS FUNCTIONAL REQUIREMENT

OPERAONS AND MAINTENANCE REQUIREMENT

RELIABILITY, AVAILABILITY, AND MAINTAINABILITY;

FAILURE MODES, EFFECTS, AND CRITICALITY ANALYSIS;

AND MAINTAINABILITY ANALYSIS

TASK ANALYSIS AND PERSONNEL AND SUPPORT

REQUIREMENTS

SUPPORT EQUIPMENT AND TWINING MATERIEL

REQUIREMENTS

UNIT UNDER TEST REQUIREMENTS AND DESCRIPTION

FACILITIES CONSIDERATIONS

PERSONNEL SKILL CONSIDERATIONS

PACKAGING AND PROVISIONING REQUIREMENT

TRANSPORTABILITY ENGINEERING ANALYSIS

B. LSAR REPORTS

PURPOSE

CONCEPT

LSAR data table to report matrix General report selection criteria . . . , . . . . . , LSAR REPORTS

LSA-001, Man-Hours by Skill Specialty Code and Level of Maintenance LSA-003, Maintenance Summary LSA-004, Maintenance Allocation Chart LSA-005, Support Items Utilization Summary LSA-006, Critical Maintenance Task Summary LSA-007, Support Equipment Requirements . . . . . . . . . , LSA-008, Support Items Validation Summary LSA-009, Support Items List LSA-010, Parts Standardization Summary LSA-011, Special Training Equipment/Device Summary LSA-012, Facility Requirement LSA-013, Support Equipment Grouping Number Utilization Summary LSA-014, Training Task List LSA-016, Preliminary Maintenance Allocation Chart LSA-018, Task Inventory Summary LSA-019, Task Analysis Summary LSA-023, Maintenance Plan Summary LSA-024, Maintenance Plan LSA-025, Packaging Requirements Data vi

APPENDIX C.

10.

10.1 10.2

20.

20.1 20.2 20.3

LSA-026, Packaging Developmental Data LSA-027, Failure/Maintenance Rate Summary LSA-030, Illustrated Parts List LSA-032, Defense Logistics Services Center (DLSC) Submittals LSA-033, Preventive Maintenance Checks and Services LSA-036, Provisioning Requirements LSA-037, Spares and Support Equipment Identification List LSA-039, Critical and Strategic Item Summary LSA-040, Authorization List Items Summary LSA-046, Nuclear Hardness Critical Item Summary LSA-050, Reliability Centered Maintenance

(RCM)

LSA-056, Failure Modes, Effects and Criticality Analysis (FMECA) Report LSA-058, Reliability, Availability and Main-tainability Summary LSA-065, Manpower Requirements Criteria LSA-070, Support Equipment Recommendation Data (SERD) LSA-071, Support Equipment Candidate List LSA-072, Test Measurement and Diagnostic Equipment (TMDE) Requirements Summary LSA-074, Support Equipment Tool List LSA-075, Consolidated Manpower, Personnel and Training Report LSA-076, Calibration and Measurement Require-ments Summary LSA-077, Depot Maintenance Interservice Data Summary LSA-078, Hazardous Materials Summary LSA-080, Bill of Materials LSA-085, Transportability Summary LSA-126, Hardware Generation Breakdown Tree LSA-151, Provisioning Parts List Index LSA-152, PLISN Assignment/Reassignment LSA-154, Provisioning Parts Breakout Summary . . .

LSA-155, Recommended Spare Parts List for Spares Acquisition Integrated with Production

(SAIP)

GUIDANCE FOR ASSIGNMENT OF LOGISTIC SUPPORT

ANALYSIS CONTROL NUMBER (LCN), ALTERNATE LCN

CODE, LCN TYPE AND USABLE ON CODE (UOC)

PURPOSE

Traditional LCN assignments Functional and physical LCN assignments:

a new perspective

LCN ASSIGNMENT

Classical LCN assignment method Modified classical assignment method Sequential assignment method

- vii -

30.

30.1 30.2 30.3 40.

50.

50.1 50.2 60.

70.

APPENDIX D.

10.

10.1 10.2 20.

20,1 20.2 20.3 20.4 20.5 30.

30.1 30.2

40.

50.

APPENDIX E.

20.1 20.2 20.3

APPENDIX F.

10.

20.

Figure

ALTERNATE LCN CODE(ALC)

ALC usage for a single configuration/model ALC usage for LSAR reports Lower tiered LCN/ALC selections

LOGISTIC SUPPORT ANALYSIS CONTROL NUMBER

TYPE (LCN-TYPE)

USABLE EN CODE

ALC And UOC relationship UOC and ALC usage for LSAR reports

SERIAL NUMBER CONTROL AS AN ALTERNATIVE FOR

CONFIGURATION MANAGEMENT

SUMMARY

APPLICATION AND TAILORING GUIDANCE FOR THE

LOGISTIC SUPPORT ANALYSIS RECORD (LSAR)

GENERAL

Purpose How to use this appendix

LSAR APPLICATION AND USE BY LIFE CYCLE PHASE

LSA process Pre-concept and concept exploration (CE) phase . . .

Demonstration and validation phase Full scale development (FSD) phase Production and Deployment Phase

TAILORING LSAR REQUIREMENTS

LSA task selection Interfacing and coordination with other program elements

SCHEDULING OF LSAR DATA

ALTERNATIVES FOR DATA DELIVERY

DATA ELEMENT DICTIONARY

PURPOSE

SECTIONS

Section 1: Index of data element titles Section 2: Table of codes and titles Section 3: Data element definitions

LIST OF LOGISTIC SUPPORT ANALYSIS RECORD ACRONYMS

PURPOSE

ACRONYMS

FIGURES

LSA data documentation process LSAR data flow and system engineering interface . .

LSAR R&M parameter interface X table relationships A table relationships B table relationships C table relationships E table relationships U table relationships F table relationships

Page viii

15 thru 62

Table

I

II

III

G table relationships H table relationships J table relationships LSAR data tables to report matrix Standard LSAR reports Classical LCN assignment method Modified classical LCN assignment method Sequential LCN assignment method Alternate LCN code usage Functional versus physical LCN assignment Usable on code and alternate LCN code usage LSAR data table utilization by hardware breakdown Preconcert and concept exploration phase LSAR Example of DD Form 1949-1

TABLES

Page

LSA-036 report format LSAR data tables related to MIL-STD-1388-1 tasks Data item description relationships to the LSAR ix/x

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.2 Tailoring. 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.3 LSA 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 -

- 2 -

- 3 -

- 4 -

- 5 -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 of Specifications and Standards (DODISS), specified in the solicitation form, a Part Of this standard to the extent specified, herein.

Military Standards.

MIL-STD-12 Abbreviations for Use on Drawings, Specifications, Standards, and in Technical Type Publications

DOD-STD-100 Engineering Drawings Practices

MIL-STD-155 Joint Photographic Type Designation System

MIL-STD-196 Joint Electronics Type Designation System

MIL-M-49502 Manuals, Technical: Repair Parts and Special Tools List

MIL-STD-470 Maintainability Program for Systems and Equipment

MIL-STD-482 Configuration Status Accounting Data Elements and Related Features

MIL-STD-785 Reliability Program for Systems and Equipment Development and Production

MIL-STD-815 Designation System for Liquid, Solid and Liquid- Solid (Hybrid) Propellant Rocket Engines and Motors

MIL-STD-875 Type Designation System for Aeronautical and Support Equipment

- 6 -

MIL-STD-879

MIL-STD-882

MIL-STD-965

MIL-STD-1388-1

MIL-STD-1390

MIL-STD-1478

MIL-STD-1519

MIL-STD-1561

MIL-STD-1629

MIL-STD-1839

MIL-STD-1843

MIL-STD-2073-1

MIL-STD-2073-2

MIL-STD-2097

MIL-STD-2173

Designation of Aircraft Propulsion Gas Turbine Engines

System Safety Program Requirements

Parts Control Program

Logistic Support Analysis

Level of Repair

Human Performance Analysis

Test Requirements Documents, Preparation of

Provisioning Procedures, Uniform Department of Defense

Procedures for Performing a Failure Mode, Effects and Criticality Analysis

Calibration and Measurement Requirements

Reliability Centered Maintenance for Aircraft Engines and Equipment

DOD Materiel, Procedures for Development and Application of Packaging Requirements

Packaging Requirement Codes

Requirements for Acquisition of End Items of Support Equipment, Associated Integrated Logistics Support, and Related Technical Data for Air Systems

Reliability Centered Maintenance for Naval Aircraft Weapon Systems and Support Equipment

DOD-STD-2121(Navy) Determination of Electronic Test Equipment Parameters

Military Handbooks.

MIL-HDBK-59 Computer-Aided Acquisition and Logistic Support (CALS) Program Implementation Guide

MIL-HDBK-217 Reliability Prediction of Electronic Equipment

Military Specifications.

MIL-T-31OOO Technical Data Packages, General Specifications for

MIL-F-7024 Fluids, Calibrating, for Aircraft Fuel System Components

MIL-M-63036A Manuals, Technical: Operator’s, Preparation of (Army)

- 7 -

MIL-M-63038B

MIL-M-83495

Manuals, Technical: Organizational or Aviation Unit Direct Support, or Aviation Intermediate, and General Support Maintenance (Army)

Manuals, Organizational Maintenance Manual Set, General Requirements for Preparation of(for Aircraft Missles and Space Vehicles)

Federal Manuals and Catalogs.

H4/H8 Commercial and Government Entity Code

H6-1 Federal Item Name Directory for Supply Cataloging

(Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available from the Standardization Documents Order Desk, Building 4D, 700 Robbins Avenue, Philadelphia, PA, 19111-5094.)

Bulletins.

ANA Bulletin 306

ANA Bulletin 395

Other Documents.

DOD 41OO.38-M

DOD 5000.12-M

DODD 5000.39

AR 70-50

NAVMATINST 8800.4

AFR 82-5

AR 700-26

Engines, Aircraft Turbine and Jet, Designation of

Engines, Aircraft Reciprocating, Designation of

DOD Provisioning and Other Preprocurement Screening Manual

DOD Manual for Standard Data Elements

Acquisition Support for

Designating Rockets and

NAVAIRINST 131OO.3 Designating

AFR 66-11

AR 700-82

and Management of Integrated Logistic Systems and Equipment and Naming Defense Equipment Guided Missiles and Naming Military Aircraft

OPNAVINST 4410.2 Joint Regulation Governing the Use and Application AFR 66-45 of Uniform Source Maintenance and Recoverability Codes

MCO 4400.120

DSAR 4100.6

NAVFAC P-72 Category Codes for Real Property, Navy

NAVPERS 15839 Manual of Navy Officer Classifications

NAVPERS 18068 Manual of Navy Enlisted Manpower and Personnel Classifications and Occupational Standards

- 8 -

MCO P 1200.7

AR 415-28

AR 611-101

AR 611-112

AR 611-201

AFR 36-1

AFR 39-1

AFM 86-2

FPM Supplement 512-1

SB 700-20

JCS PUB 1

DA CPR 502

DA PAM 700-20

Military Occupational Specialties

Department of the Army Facility Classes and Construction Categories

Manual of Commissioned Officer Military Occupational Specialties

Manual of Warrant Officer Military Occupational Specialties

Enlisted Military Occupational Specialties

Officer Classification Manual

Airman Classification Manual

Standard Facility Requirements

Civil Service Commission, Job Grading Standard

Army Adopted/Other Items Selected for Authorization/ List of Reportable Items

Dictionary of United States Military Terms for Joint Usage

Department of Army - Civilian Personnel Regulations, Standardized Job Descriptions

Department of Army - Test, Measurement, and Diagnostic Equipment Register

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 -determined by the individual application. An assembly, in one instance, may be a subassembly in another where it forms a portion of an assembly.

3.2 Attaching part. An item used to attach assemblies or parts to the equipment or to each other.

3.3 Component. An assembly or any combination of parts, subassemblies, and assemblies mounted together normally capable of independent operation in a variety of situations.

3.4 Design Change. An approved engineering change incorporated into the end item which modifies, adds to, deletes, or supersedes parts in the end item.

3.5 End Article/Product. A component, assembly or subassembly being procured as the top item on the contract.

3.6 End Item. A final combination of end products, component parts/materials which is ready for its intended use, e.g. , ship, tank, mobile machine shop, aircraft, receiver, rifle, or recorder.

3.7 LSA Candidate. A component, subassembly, assembly, software, or end item/article on which maintenance action is considered feasible as a result of a preliminary or detailed tradeoff analysis.

3.8 LSA Documentation. All data resulting from performance of LSA tasks, conducted under MIL-STD-1388-1, to include LSAR, pertaining to an acquisition program.

3,9 Manufacturers Part Number. See reference number.

3.10 Part. One, two or more pieces, joined together which are not normally subject to disassembly without destruction or impairment of designed use.

3.11 Part Number. See reference number.

3.12 Reference Number. Any number, other than a government activity stock number, used to identify an item of production, or used by itself or in conjunction with other reference numbers to identify an item of supply.

Reference numbers include: manufacturer’s part, drawing, model, type, or source controlling numbers; manufacturer’s trade name; specification or standard numbers; and, specification or standard part, drawing, or type numbers. See appendix E, Data Element Definition 330.

3.13 Subassembly. Two or more parts which form a portion of an assembly or a component replaceable as a whole, but having a part or parts which are individually replaceable (e.g., gun mount stand, window recoil mechanism, floating piston, telephone dial, mounting board with mounted parts, power shovel dipper stick).

3.14 Topdown. A breakdown accomplished by sequencing all parts comprising the end item in a lateral and descending “family tree/generation breakdown”.

This breakdown shall consist of the end item, including all components, listing every assembly, subassembly, and parts which can be disassembled, reassembled/replaced. All parts are listed in their relation to the end item, component, assembly, or installation system in which they are contained and to their own further sub-subassemblies and parts. This relationship is shown by means of an indenture code.

4. GENERAL REQUIREMENTS. LSA documentation, including LSAR data, is generated as a result of the analysis tasks specified in MIL-STD-1388-1. As such, the LSAR data shall serve as the Integrated Logistic Support (ILS) technical database applicable to all materiel acquisition programs to satisfy the support acquisition. The DEDs, data field lengths, and data formats described in appendices A and E shall be adhered to by the performing activity in establishing the LSAR database. The specific data entry media, storage, and maintenance procedures are left to the performing activity. Validated LSAR ADP systems are available for automated storage of the LSAR data. A list of these LSAR ADP systems may be obtained from the USAMC Materiel Readiness Support Activity, ATTN: AMXMD-EL, Lexington, KY 40511-5101. The LSAR data forms a database to:

a. Determine the impact of design features on logistics support.

b. Determine the impact of the proposed logistics support system on the system/equipment availability and maintainability goals.

c. Provide data for tradeoff studies, life cycle costing, and logistic support modeling.

d. Exchange valid data among functional organizations.

e. Influence the system/equipment design.

f. Provide data for the preparation of logistics products specified by DIDs.

g. Provide the means to assess supportability of the fielded item.

h. Provide the means to evaluate the impact of engineering change, product improvement, major modification or alternative proposals.

4.1 LSAR data selection sheets. The LSAR data selection sheets (DD Form 1949-1, figure 71) provide a vehicle for identifying the required LSAR data elements to be completed and, when applicable, the media of delivery (e.g., floppy disk, magnetic tape, etc.). Preparation of the LSAR data selection sheets should be a result of the LSAR tailoring process discussed in appendix D. The data selection sheets are used to identify the specific data elements that are required and identified on the relational data tables. In addition, the sheets will be used to specify the data elements required for each Provisioning Technical Documentation (PTD) list or packaging categorization of items required. Generation of the PTD lists (format shown as table I, LSA-036 report) may be accomplished manually or via automation techniques. When more than one option of entry for a data element is possible, the options are spelled out as part of the data element dictionary.

In a similar manner, the LSAR data selection sheets list the options for data elements that have more than one option for entry. Only one option will be specified for a data element with multiple entry options. The LSAR data selection sheets will be attached to the contract SOW and attached to the

-11-

Contract Data Requirements List (CDRL), DD Form 1423, for the applicable DIDs.

Detailed instructions for completing DD Form 1423 are provide in appendix B, paragraph 20.1 and figure 14.

4.2 LSAR data. The preparation and maintenance of LSAR data is directly related to the hardware and software design of an end item. The requiring authority is responsible for specifying the equipment indenture level and the level(s) of maintenance for which LSAR data will be prepared and maintained.

The LSAR data may be prepared and maintained manually, using the LSAR data tables displayed in appendix A, or equivalent formats approved by the requiring authority. It may also be prepared and maintained automatically through use of current computer technology. The decision to automate the LSAR data versus a manual LSAR must take into account the following factors:

a. Costs and schedules of preparation.

b. Availability of an ADP system.

c. Hardware complexity.

d. Acquisition/life cycle phase,

e. Requiring authority’s schedule requirements.

f. Design stability,

g. Compatibility with other LSAR preparers, as well as the requiring authority’s ADP system.

h. Requiring authority involvement.

4.2.1 Manual LSAR data. While not preferred, the LSAR data may be prepared and maintained in hard copy format by using the LSAR data tables displayed in appendix A as guidelines for data groupings. When the LSAR data is prepared and maintained manually, the data displayed on the LSAR tables shall be grouped into LSAR data packages documenting individual reparable assemblies, embedded computer software, and support/test equipment. The LSAR data packages shall be sequenced by LCN, The data displayed on support equipment, facilities, and new or modified skill requirements shall be included in the applicable system/end item LSAR packages, or as directed by the requiring authority. LSAR data displayed on the support item identification and application data shall be sequenced by reference number and LCN within each reference number.

4.2.1.1 Manual LSAR report generation. When required, any or all of the LSAR reports contained in appendix B can be produced in a nonautomated environment.

When the LSAR reports are produced by nonautomated means, the reports shall be in accordance with (IAW) the content, format, sequence, and computational requirements contained in paragraph 30 of appendix B.

4.2.2 Automated LSAR data. The LSAR data may be automated and, as such, a validated LSAR ADP system shall be used as follows.

- 12 -

4.2.2.1 Performing activity LSAR ADP system. The performing activity shall use a validated LSAR ADP system. Validation will be accomplished by the USAMC Materiel Readiness Support Activity (MRSA). The systems shall be capable of fulfilling the basic criteria defined in paragraph 4.2.2.2 of this standard.

These systems shall be validated by exhibiting processing capability to input, edit, and build LSAR relational tables and output the relational tables and standard LSAR reports. Detailed validation procedures will be provide on request by MRSA.

4.2.2.2 LSAR ADP system criteria. The independently developed LSAR ADP system will be validated based on the following design criteria:

a. Shall be capable of automatically accepting relational table data in the formats displayed in appendix A, using the data elements, definitions) data element edits, data field lengths, and data relationships contained in appendices A and E.

b. Shall be capable of producing LSAR reports as displayed in appendix B.

c. Shall be capable, as a minimum, of satisfying all appendix E data elements.

d. Shall be capable of outputting LSAR ADP relational tables as displayed in appendix A.

e. Shall be capable of outputting change only data from last delivery of LSAR data.

f. Shall provide automated user comment capability.

These minimum design criteria are required to secure system validation.

Additional system automation is strongly encouraged.

5. DETAILED INSTRUCTIONS FOR AUTOMATED OR MANUAL PREPARATION OF LSAR

RELATIONAL TABLES. These instructions are applicable for either the automated or manual preparation of the LSAR data. Each data table contained in appendix A is identified by a three-position code, The first position of this code identifies the functional area most directly associated with the information contained within the data table. These codes are consistent with the data record letter identifications used in the previous version of this standard, e.g. , support item identification is identified by an “H” in the first position of the table code. The second position uniquely identifies the table within a functional area. The third position may be used to insert additional data tables at a later date.

5.1 Requiring authority data tables. Information in the “A” and portions of the “X” tables will be provided by the requiring authority and may be incorporated with the solicitation, or addressed at the LSA/LSAR guidance conference . This information will also be documented on the DD form 1949-1, Figure 69.

5.1,1 Cross functional requirements. These data tables have attributes which cross multiple functional areas or are used as a link to various functional data tables. The tables are used by the requiring authority to document

-13-supply, maintenance and personnel data in support of tradeoff analysis. The individual data elements may be used in conjunction with other LSA data in several LSA models with only minor adjustment, if any, for compatibility of units.

5.1.2 Operations and maintenance requirements. These tables are structured to consolidate the pertinent information related to the anticipated operation of the system, environment in which the system will be operated and maintained, and the system maintenance requirements which must be met. This information is prepared for the system, and for each subsystem for which maintenance requirements are to be imposed, and will also be prepared for government furnished equipment (GFE). When separate operational/maintenance requirements are established for wartime and peacetime scenarios, each set of requirements will be documented as separate table rows. The number of rows of information that will be prepared shall be based on the tasks contained in MIL-STD-1388-1, or as specified by the requiring authority. The performing activity shall incorporate this information into the LSAR and shall complete the appropriate key fields, unless the field has been completed by the requiring authority. Detailed instructions for completion of this information are contained in appendices A and E.

5.2 Performing activity data tables. The performing activity shall complete the required fields of data tables “B”, “C”, and “E”, “F”, “G”, “H”, “J”, “U” and portions of the “X” IAW the information contained in appendices A and E and to the extent specified by DD Form 1949-1. When DEDs state that specific information will be provided by the requiring authority, the information may be included in the solicitation or not later than the LSA/LSAR guidance conference.

5.2.1 Reliability, availability, maintainability, failure modes, effects, and criticality analysis; and maintainability analysis. The “B” data tables provide a description of the function of each item within the system; outline the maintenance concept to be utilized for design and support planning purposes; and, identify any design conditions such as fail-safe requirements/ environmental or nuclear hardness considerations imposed upon the system.

The tables summarize the reliability, maintainability, and related availability characteristics of the item resulting from the failure modes and effects, criticality, and maintainability analyses, and accommodates a narrative description of any analysis related to the potential redesign of an item. A separate row of information is prepared for the system, for each subsystem contained in the system, and for each level of breakdown for that subsystem until the lowest reparable item has been documented. The degree of breakdown shall be specified by the requiring authority. Additional “B” data tables are designed to accommodate the Failure Modes and Effects Analysis (FMEA), as described by task 101 of MIL-STD-1629. These tables will also accommodate the Damage Mode and Effects Analysis, to be utilized for survivability and vulnerability assessments, as described in task 104 of MIL-STD-1629, and accommodates the criticality and maintainability analyses, as described in tasks 102 and 103 of MIL-STD-1629. The purpose of the criticality analysis is to rank each identified failure according to the combined influence of severity classification and failure probability of occurrence. The relative ranking of the calculated item criticality numbers highlights system high risk items. The maintainability analysis serves as the starting point for maintenance task analysis. The FMEA documents the effects

-14-of an item failure upon system operations and is used to classify each potential failure according to the severity of those effects. The FMEA is initiated as an integral part of the early design process and is derived through a functional analysis. To provide concise information on the failure analysis, functional block diagrams should be provided. Subsequent to this effort, data is prepared to an indenture level, as specified by the requiring authority. The results are used as a guide in evaluating design features and as a basis for initial quantitative predictions. The analysis identifies high risk items, facilitates the evaluation of design features, and provides the basis for criticality and maintainability analyses. The failure effects data are the basis for developing fault location and troubleshooting routines.

These tables also document Reliability Centered Maintenance (RCM) logic results and accommodates a narrative description of any analysis related to the potential redesign of an item. These tables are completed to the same indenture level as the item R&M Characteristics tables.

5.2,2. Task inventory, task analysis, personnel and support requirements.

The Operation and Maintenance summary information is used to consolidate the operations and maintenance tasks identified for each reparable assembly and indicates necessary support requirements (e.g. , facilities, training equipment, tools, and support equipment). Included are the identification of the combination of all human performances required for operation and maintenance of a one-person position in a system (e.g., A job is that of a driver; one of the duties of a driver is emergency repair; a task within emergency repair is changing a flat tire). The task identification information on these tables is developed from the RCM analysis, maintainability analysis, and from the maintenance task analysis. This information is completed to the same indenture level as the R&M and FMECA Tables. This information is identified on “C” data tables. Additional “C” data tables provide a detailed step-by-step narrative description of how tasks identified on the Task Summary are to be performed, the specific skill specialty requirements, and applicable task man-hours per skill speciality.

These tables identify training, personnel, support equipment, and supply support requirements necessary for the accomplishment of the individual tasks.

Man-hours per skill specialty are also recorded on these tables. Data on these tables provide information necessary for the development of technical publications , training programs of instruction, supply support, and personnel requirements. This information will be initiated during the detailed system\equipment design effort. For all operational and maintenance level tasks, specific requirements for the completion of the task analysis, including the documentation of maintenance levels, specific hardware items, and indenture levels, will be as specified by the requiring authority.

Included in this documentation are the combination of all human performances required for operation and maintenance in a hierarchical breakdown, e.g., mission, scenario, function, job, duty, task, subtask and element, as described in MIL-STD-1388-1.

5.2.3 Support equipment and training material requirements. Data tables identified by “E” are structured to consolidate the pertinent information related to existing or new support/test equipment or training material, e.g., physical characteristics, calibration requirements, and test parameters. This information also serves as identification of hardware and software elements required to conduct off-line tests.

-15-

5.2.4 Unit under test requirements and justification. Data tables “U” are structured to identify the Unit Under Test (UUT), which will be removed from the system and those hardware and software elements required to test the UUT with off-line support/test equipment. The unique combination of these elements required for a specific UUT and support/test equipment configuration is a Test Program Set (TPS). In addition to defining the TPS elements, this information provides configuration identification of the UUT (i.e., UUT, and the support/test equipment to be used in the test). This information is established for each WT, which has a requirement to be tested by the support/test equipment documented.

5.2.5 Facility considerations. Data tables identified by “F” are used to describe and justify all proposed special or additional facility requirements, which are indicated as a result of the maintenance task analysis. Sketches or other information may be incorporated as part of the hard copy storage by entering the control fields (LCN and task code when applicable) on the supplemental data. These data are required to provide facility designers with the technical information necessary to prepare facility plans.

5.2.6 Personnel skill considerations. Data tables identified by “G” are used to describe and justify any new or modified personnel skills required to support the system/equipment. This information shall be completed for each new or modified skill required as a result of the maintenance task analysis and skill analysis.

5.2.7 Packaging and provisioning requirement. Data tables identified by “H” are used to document the static parts data (nonapplication dependent) related to provisioning screening results, packaging data, price analysis data, parts breakout coding results, and common maintenance data. This information is completed for each item that comprises a system (by reference number) to include, as specified by the requiring authority, reparable items, nonreparable items, bulk materials, common hardware, and common and peculiar support equipment. Additional “H” data tables are used to capture application data of items identified by the static data tables. This information will be prepared for each application of the item in a different next higher assembly and will document that data required for initial support requirements determination, repair parts manual, etc.

5.2.8 Transportability engineering analysis. Data tables identified by “J” are designed to capture the transportability engineering requirements for an end item. This information shall be prepared for the end item in its shipping configuration. In the event the end item is sectionalized for transport, the information shall be completed for each section of the end item. It may also be completed for critical subcomponents or as specified by the requiring authority. External items, which are removed and stored inside the package during transport, are not considered sectionalization for transport.

5.3 LCN assignment and structure. The development of the LCN structure and assignment of individual LCNs is the responsibility of the performing activity, and the resulting structure should be approved by the requiring authority. The LCN structure should represent a topdown generation or functional breakdown of hardware and software IAW the standard engineering drawing structure. LCN sequencing assignment shall adhere to the American Standard Code for Information Interchange (ASCII). Guidance for assignment of LCN, ALC, and UOC are contained in appendix C. This appendix is not

-16-contractual and does not establish requirements. However, the guidance in appendix C should be followed to ensure proper assignment of LCNs for a given system/equipment, as this is critical for successful configuration management and ILS product development.

5.4 LSA/LSAR guidance conference. The purpose of this conference is to ensure the performing activity and requiring authority have a firm understanding of the relationship of the LSA tasks to the LSA documentation, task milestones, and funding levels contractually required. When a guidance conference is not contractually specified and the performing activity desires a conference, the performing activity shall propose a date and place. The proposal shall be submitted within thirty (30) days after contract award. The specific date and place for the guidance conference will be determined by the requiring authority and performing activity. The guidance provided to the performing activity by the requiring authority may include, but shall not be limited to, the following:

a. Performing activity inquiries relative to contractual LSAR requirements.

b. Operational and maintenance concepts, i.e., program data.

c. Baseline logistics data, i.e., available skills, training programs, tools, test equipment, and facilities.

d. Requirement for joint service validation of the performing activity developed LSAR ADP system, when applicable.

e. Guidance relative to the use and application of LSAR data elements.

f. Review of the LSA candidate list.

6. NOTES. (This section contains information of a general or explanatory nature that is helpful, but is not mandatory.)

6.1 Intended use. This standard contains requirements which are applicable to the acquisition of military systems and equipment.

6.2 Issue of DODISS. When this standard is used in acquisition, the issue of the DODISS to be applicable to this solicitation must be cited in this solicitation (see 2.1).

6.3 Consideration of data requirements. The following should be considered when this standard is applied on a contract. The applicable DIDs should be reviewed in conjunction with the specific acquisition to ensure that only essential data are requested/provided and that the DIDs are tailored to reflect the requirements of the specific acquisition. To ensure correct contractual application of the data requirements, a CDRL (DD Form 1423) must be prepared to obtain the data, except where DOD FAR Supplement 27.475-1 exempts the requirement for a DD Form 1423. Refer to appendix D of this standard for suggested tailoring guidance.

-17-

Paragraph Number

5.2

Appendix B, 30.1

Appendix B, 30.2 Appendix B, 30.3

Appendix B, 30.4 Appendix B, 30.5 Appendix B, 30.6 Appendix B, 30.7 Appendix B, 30.8 Appendix B, 30.9 Appendix B, 30.10

Appendix B, 30.11 Appendix B, 30.12

Appendix B, 30.13 Appendix B, 30.14

Appendix B, 30.15 Appendix B, 30.16 Appendix B, 30.17 Appendix B, 30.18 Appendix B, 30.19 Appendix B, 30.20 Appendix B, 30.21 Appendix B, 30.22

Appendix B, 30.23

Appendix B, 30.24

Appendix B, 30.25

Appendix B, 30.26

Appendix B, 30.27

Appendix B, 30.28 DI-ILSS-81160 Appendix B, 30.29 DI-ILSS-81161

Summary

DID Number

DI-ILSS-81173

DI-ILSS-81138

DI-ILSS-81139

DI-ILSS-81140

MIL-STD-1388-2B

DI-ILSS-81141

DI-ILSS-81142

DI-ILSS-81143

DI-ILSS-81144

DI-ILSS-81145

DI-ILSS-81146

DI-ILSS-81147

DI-ILSS-81148

DI-ILSS-81149

DI-ILSS-81150

DI-ILSS-81151

DI-ILSS-81152

DI-ILSS-81153

DI-ILSS-81183

DI-ILSS-80119B

DI-PACK-80120

DI-ILSS-81154

DI-ILSS-81155

DI-ILSS-81156

DI-V-7016F

DI-ILSS-81157

DI-V-7002A

DI-V-7003A

DI-V-7004A

DI-V-7005A

DI-V-7006A

DI-V-7007A

DI-V-7008A

DI-V-7009A

DI-V-7011A

DI-V-7192A

DI-ILSS-81158

DI-ILSS-81159

DID Title

Logistic Support Analysis Record (LSAR) Data LSA-001, Annual Man-Hours by Skill Specialty Code and Level of Maintenance LSA-003, Maintenance Summary LSA-004, Maintenance Allocation Chart Summary LSA-005, Support Item Utilization Summary LSA-006, Critical Maintenance Item Summary LSA-007, Support Equipment Requirements LSA-008, Support Items Validation Summary LSA-009, Support Items List LSA-010, Parts Standarization Summary LSA-011, Requirements for Special Training Device LSA-012, Facility Requirements LSA-013, Support Equipment Grouping Number Utilization Summary LSA-014, Training Task List LSA-016, Preliminary Maintenance Allocation Chart LSA-018, Task Inventory Summary LSA-019, Task Analysis Summary LSA-023, Maintenance Plan Summary LSA-024, Maintenance Plan Preservation and Packing Data LSA-026, Packaging Developmental Data LSA-027, Failure/Maintenance Rate Summary LSA-030, Indentured Parts Lists

Provisioning and other Preprocurement Screening Data LSA-033, Preventive Maintenance Checks and Services (PMCS) Provisioning Parts List Short Form Provisioning Parts List Long Lead Time Items List Repairable Items List Interim Support Items List Tools and Test Equipment List Common and Bulk Items List Design Change Notices Post Conference List…