MIL-HDBK-1388UNITED STATES OF AMERICALOGISTIC SUPPORT ANALYSISNON-MEASUREMENT SENSITIVEDRAFTMILITARY HANDBOOKNOTE: This draft dated 1 Mar 94, prepared by the U.S. Army Materiel Command, LogisticsSupport Activity has not been approved is subject to modification.DO NOT USE PRIOR TO APPROVALDRAFTMIL-HDBK-1388iFOREWORD 1.This military handbook is approved for use by all departments andagencies of the Department of Defense (DOD).2.Beneficial comments (recommendations, additions, deletions) and anypertinent data which may be of use in improving this document should beaddressed to:Director, USAMC Logistic Support Activity, ATTN: AMXLS-ALD,Huntsville, AL 35898-7466 by using the self-addressed Standardization DocumentImprovement Proposal (DD Form 1426) appearing at the end of this document orby letter.3.This handbook is directed toward improving the understanding of theLogistic Support Analysis (LSA) process as it pertains to MIL-STD-1388-1,Logistic Support Analysis and MIL-STD-1388-2, DOD Requirements for a LogisticSupport Analysis Record and their associated interfacing standards anddocuments.This handbook is to be used in concurrent with MIL-STD-1388-1 andMIL-STD-1388-2.The tailoring of LSA data and LSA Record (LSAR) data shouldbe done in accordance with the tailoring guidance provided by each of therespective documents.CONTENTSMIL-HDBK-1388iiParagraphPage1.0Purpose..............................................................11.1Application of Handbook............................................11.1.1Content of Appendices............................................11.1.2Tailoring........................................................11.1.3LSA Process......................................................12.0Referenced Documents.................................................13.0Definitions..........................................................3CHAPTER 1LSA AND THE ACQUISITION PROCESS................................1-110.0 LSA and the Acquisition Process....................................1-110.1 Major Criteria...................................................1-110.1.1Manpower and Personnel Constraint.............................1-110.1.2System Readiness..............................................1-110.1.3Cost..........................................................1-110.2 Acquisition Process..............................................1-110.2.1Concept Exploration/Definition (CED) Phase....................1-110.2.2Demonstration and Validation (D&V) Phase......................1-110.2.3Engineering and Manufacturing (EMD) Phase.....................1-310.2.4Production and Deployment (P&D) Phase.........................1-310.2.5Operations and Support Phase..................................1-310.3 LSA Process......................................................1-310.3.1Analysis of Supportability....................................1-310.3.1.1System Level Analysis.....................................1-310.3.1.2System Level Tradeoffs....................................1-310.3.1.3Optimization..............................................1-310.3.2Assessment and Verification...................................1-410.4Interfaces........................................................1-410.4.1Comparative Analysis (Task 203)...............................1-410.4.2Functional Requirements Identification (Task 301).............1-410.4.3Tradeoff Analysis (Task 303)..................................1-410.4.4Task Analysis (Task 401)......................................1-410.4.5Inputs and Outputs for System Level LSA (Subtask 303.2.3).....1-710.4.6Refinement and Extension of System Level LSA..................1-710.4.7Task Analysis Interfaces......................................1-710.4.8Resource requirements Identification..........................1-710.5Strategy in Developing Analysis Requirements......................1-710.5.1General.......................................................1-710.5.2Task Selection and Focusing...................................1-710.5.2.1General...................................................1-710.5.2.2Focusing..................................................1-810.5.3Factors Impacting Strategy....................................1-810.5.3.1Type of Program/Change....................................1-810.5.3.2Amount of Design Freedom..................................1-910.5.3.3Time and Resources Available..............................1-910.5.3.4Work Already Done........................................1-1010.5.3.5Past Experience and Historical Data......................1-1010.5.3.6Procurement Consideration................................1-1010.6LSA Task Application.............................................1-2110.6.1LSA Definition...............................................1-2110.6.1.1LSA Process..............................................1-2110.6.2Hardware Levels to Which the LSA Process is Applied..........1-2210.6.3LSA Tasks....................................................1-22MIL-HDBK-1388iii10.6.3.1Task 101 - Development of an Early Logistic SupportAnalysis Strategy........................................1-2510.6.3.2Task 102 - Logistic Support Analysis Plan................1-2610.6.3.3Task 103 - Program and Design Reviews....................1-2610.6.3.4Task 201 - Use Study.....................................1-2710.6.3.5Task 202 - Mission Hardware, Software and SupportSystem Standardization...................................1-2810.6.3.6Task 203 - Comparative Analysis..........................1-2810.6.3.7Task 204 - Technological Opportunities...................1-2910.6.3.8Task 205 - Supportability and Supportability Related Design Factors...........................................1-2910.6.3.9Task 301 - Functional Requirements Identification........1-3010.6.3.10Task 302 - Support System Alternatives..................1-3110.6.3.11Task 303 - Evaluation of Alternatives and Tradeoff Analysis................................................1-3110.6.3.12Task 401 - Task Analysis................................1-3210.6.3.13Task 402 - Early Fielding Analysis......................1-3310.6.3.14Task 403 - Post Production Support Analysis.............1-3410.6.3.15Task 501 - Supportability Test, Evaluation, and Verification............................................1-3410.6.4 LSA Tailoring Process.......................................1-3510.6.5 LSA and the Managerial Functions............................1-3510.6.5.1Planning and Controlling.................................1-3510.6.5.2Coordination.............................................1-3510.7ILS, LSA, LSAR, and System Engineering...........................1-3610.8 LSA Documentation...............................................1-4010.8.1LSA Information..............................................1-4010.8.2Updates......................................................1-4010.8.3LSAR.........................................................1-4010.8.3.1LSAR Documentation Process...............................1-4010.9Logistic Support Analysis Record.................................1-4110.9.1Purpose......................................................1-4110.9.2LSAR Data Process............................................1-4110.9.3Manual Verse Automated LSAR..................................1-4110.9.4LSAR Data Tailoring Process..................................1-4110.10LSAR Data Tables and Reports....................................1-4710.10.1General.....................................................1-4710.10.2Cross Functional Requirement................................1-4710.10.3Operation and Maintenance (O&M) Requirements................1-4710.10.4Item Reliability, Availability, and Maintainability Requirements; Failure Mode Effects and Criticality Analysis; and, MaintainabilityAnalysis...............................1-4810.10.5Task Analysis, Personnel and Support Requirements...........1-4910.10.6Support Equipment and Training Material Requirements........1-5010.10.7Unit Under Test Requirements and Description................1-5110.10.8Facilities Consideration....................................1-5210.10.9Personnel Skill Considerations..............................1-53MIL-HDBK-1388iv10.10.10Packaging and Provisioning Requirement.....................1-5310.10.11Transportability Engineering Analysis......................1-54CHAPTER 2CONTRACTING....................................................2-120.0 Contracting for LSA................................................2-120.1 Application in Procurement.......................................2-120.1.1Pre-RFP and Bidders Briefings.................................2-120.1.2Preparing LSA RFP Requirements................................2-120.1.2.1Broad Versus Specifics....................................2-120.1.2.2Interfaces................................................2-120.1.2.3Interweave Supportability Requirements and Constraints....2-120.1.2.4Relative Importance of Requirements.......................2-220.1.2.5Support Related Design Drivers............................2-220.1.2.6Alternate Support Concepts................................2-220.1.2.7Evaluation Methods and Models.............................2-220.1.2.8Provisioning Procedures...................................2-220.1.2.9Spares Acquisition Integrated with Production (SAIP)......2-520.2Task Documentation................................................2-520.3 Contracting for LSAR............................................2-1520.3.1Objective....................................................2-1520.3.2Factors to Consider..........................................2-1520.3.2.1Type of Acquisition......................................2-1520.3.2.2Phase of Development.....................................2-1620.3.2.3LSAR Level of Effort.....................................2-1620.3.2.4Previous LSAR Effort.....................................2-1620.3.2.5Degree of Program Control................................2-1620.4 Determine Logistics Products....................................2-1720.4.1Logistic Products Figures....................................2-1720.4.2Reliability and Maintainability..............................2-1720.4.3Maintenance Planning.........................................2-1820.4.4Technical Data and Manuals...................................2-1920.4.5Support and Test Equipment...................................2-1920.4.6Supply Support...............................................2-2020.4.7Supply Support (continued)...................................2-2020.4.8Manpower, Personnel, and Training............................2-2120.4.9Facilities...................................................2-2220.4.10Packaging, Handling, Storage, and Transportability..........2-2220.5 LSAR Analysis Reports...........................................2-2320.5.1LSA-001, Annual Man-Hours by Skill Specialty Code andLevel of Maintenance.........................................2-2320.5.2LSA-003, Maintenance Summary.................................2-2320.5.3LSA-005, Support Item Utilization Summary....................2-2320.5.4LSA-006, Critical Maintenance Item Summary...................2-2320.5.5LSA-007, Support Equipment Requirements......................2-2320.5.6LSA-008,Support Items Validation Summary...................2-2320.5.7LSA-009, Support Items List..................................2-2420.5.8LSA-010, Parts Standardization Summary.......................2-2420.5.9LSA-011, Requirements for Special Training...................2-2420.5.10LSA-013, Support Equipment Grouping Number Utilization Summary.....................................................2-24MIL-HDBK-1388v20.5.11LSA-027, Failure/Maintenance Rate Summary...................2-2420.5.12LSA-037, Spares and Support Equipment Identification List...2-2420.5.13LSA-039, Critical and Strategic Item Summary................2-2420.5.14LSA-046, Nuclear Hardness Critical Item Summary.............2-2420.5.15LSA-078, Hazardous Materials Summary........................2-2420.5.16LSA-126, Hardware Generation Breakdown Tree.................2-2520.5.17LSA-152, PLISN Assignment/Reassignment......................2-2520.5.18LSA-154, Provisioning Parts Breakout Summary................2-2520.6 AD-HOC Queries..................................................2-2520.6.1Example AD-HOC Query.........................................2-2520.7 DD Form 1949-3, LSAR Data Requirements Form.....................2-2620.7.1Data Element Selection.......................................2-2620.7.2Selection of 1949-3 Data Elements............................2-2620.7.2.1DD Form 1949-3 Sections and Parts........................2-2620.7.2.2DD Form 1949-3, General Information......................2-2620.7.2.3Section 1 of DD Form 1949-3, Government Furnished Data...2-2620.7.2.4Peculiarities of 1949-3..................................2-2720.7.2.4.1Data Element Selection...............................2-2720.7.2.5Data Element Selection DD Form 1949-3 Example............2-2720.8 Delivery of LSAR Data...........................................2-3520.8.1Hard Copy LSAR Reports.......................................2-3520.8.2Master Table Delivery........................................2-3520.8.3On-Line Access...............................................2-3620.8.4Delivery Combination.........................................2-3620.9 Example Statement of Work.......................................2-3720.10Conversion From 1388-2A to 1388-2B..............................2-3920.10.1Additional Data.............................................2-40CHAPTER 3LSAR REPORT SPECIFICATIONS.....................................3-130.0 LSAR Reports.......................................................3-130.1 Common Selection Criteria........................................3-130.1.1EIAC..........................................................3-130.1.2LCN...........................................................3-130.1.3ALC...........................................................3-230.1.4UOC...........................................................3-230.1.5Service Designator............................................3-230.1.6O/M Levels....................................................3-230.1.7ICCs.........................................................3-230.2Subordinate LCN/ALC...............................................3-230.3 Task Referencing or Subtask Referencing..........................3-330.3.1 Report Usage of Referenced Tasks/Subtasks......................3-330.4LSA-001, Annual Man-Hours by Skill Specialty Code andLevel of Maintenance Report Specifications........................3-430.5LSA-003, Maintenance Summary Report Specifications .............3-730.6LSA-004, Maintenance Allocation Chart Report Specification.......3-1130.7LSA-005, Support Item Utilization Summary Report Specification...3-2030.8LSA-006, Critical Maintenance Item Summary Report Specification..3-2330.9LSA-007, Support Equipment Requirements by SSC and Maintenance Level Report Specification.......................................3-2630.10LSA-008, Support Items Validation Summary Report Specification..3-2830.11LSA-009, Support Items List Report Specification................3-31MIL-HDBK-1388vi30.12LSA-010, Parts Standardization Summary Report Specification.....3-3430.13LSA-011, Requirements for Special Training Report Specification.3-3630.14LSA-012, Facility Requirements Report Specification.............3-3830.15LSA-013, Support Equipment Grouping Number Utilization Summary Report Specification....................................3-4330.16LSA-014, Training Task List Report Specification................3-4530.17LSA-016, Preliminary Maintenance Allocation Chart Report Specification...................................................3-4830.18LSA-018, Task Inventory Summary Report Specification............3-5430.19LSA-019, Task Analysis Summary Report Specification.............3-5630.20LSA-023, Maintenance Plan Summary Report Specification..........3-6030.21LSA-024, Maintenance Plan Report Specification..................3-6930.22LSA-025, Packaging Requirements Data Report Specification.......3-7930.23LSA-026, Packaging Developmental Data Report Specification......3-8230.24LSA-027, Failure/Maintenance Rate Summary Report Specification..3-8430.25LSA-030, Indentured Parts List Report Specification.............3-9130.26LSA-032, Defense Logistics Service Center (DLSC) Submittals Provisioning Screening Report Specification....................3-10130.27LSA-033, Preventive Maintenance Checks and Services Report Specification..................................................3-10530.28LSA-036, Provisioning Requirements Report Specification........3-10830.29LSA-037, Spares and Support Equipment Identification List Report Specification..................................................3-11830.30LSA-039, Critical and Strategic Item Summary Report Specification .................................................3-12130.31LSA-040, Authorization List Items Summary Report Specification.3-12430.32LSA-046, Nuclear Hardness Critical Item Summary Report Specification .................................................3-12930.33LSA-050, Reliability Centered Maintenance Summary Report Specification..................................................3-13130.34LSA-056, Failure Modes, Effects, and Criticality Analysis (FMECA) Report Specification...................................3-13930.35LSA-058, Reliability and Maintainability Analysis Report Specification..................................................3-14830.36LSA-065, Manpower Requirements Criteria (MARC) Report Specification..................................................3-15130.37LSA-070, Support Equipment Recommendation Data (SERD) Report Specification..................................................3-15430.38LSA-071, Support Equipment Candidate List Report Specification.3-17330.39LSA-072, Test, Measurement and Diagnostic Equipment Requirements Summary Report Specification......................3-MIL-HDBK-1388vii17630.40LSA-074, Support Equipment Tool List Report Specification......3-18130.41LSA-075, Consolidated Manpower, Personnel and Training Report Specification..................................................3-18530.42LSA-076, Calibration and Measurement Requirement Summary Report Specification..................................................3-18930.43LSA-077, Depot Maintenance Interservice Data Summary Report Specification..................................................3-19330.44LSA-078, Hazardous Materials Summary Report Specification......3-19930.45LSA-080, Bill of Materials Report Specification................3-20130.46LSA-085, Transportability Summary Report Specification.........3-20530.47LSA-126, Hardware Generation Breakdown Tree Report Specification .................................................3-21130.48LSA-151, Provisioning Parts List Index Report Specification....3-21330.49LSA-152, PLISN Assignment/Reassignment Report Specification....3-21630.50LSA-154, Provisioning Parts Breakout Summary Report Specification..................................................3-22030.51LSA-155, Recommended Spare Parts List for Spare Acquisition Integrated with Production (SAIP) Report Specification.........3-223CHAPTER 4LSAR SOFTWARE VALIDATION.......................................4-140.0 Objective..........................................................4-140.1 General..........................................................4-140.2 Purpose..........................................................4-140.3 Differences in Validation Requirements with the Revised Standard.4-140.3.1Type 1........................................................4-140.3.2Type 2........................................................4-140.3.3Type 3........................................................4-140.4 Differences in LSAR Software System Design Criteria 2A versus 2B.4-140.4.1Master Table(s) Acceptance....................................4-240.4.2Master Table(s) Delivery......................................4-240.4.3LSAR Reports..................................................4-240.4.4Appendix A and E..............................................4-240.4.5Change Only Data..............................................4-340.4.6Comment Capabilities..........................................4-340.5 General Validation Procedures....................................4-340.5.1Step 1........................................................4-340.5.2Step 2........................................................4-340.5.3Step 3........................................................4-340.5.4Step 4........................................................4-340.5.5Step 5........................................................4-440.5.6Step 6........................................................4-440.6 Validation Completion............................................4-440.7 Validation Renewal Procedures....................................4-440.7.1Renewal Request...............................................4-4MIL-HDBK-1388viii40.7.2Renewal Issuance..............................................4-440.8 LSAR ADP System Revalidation.....................................4-440.9 Disapproval of Validation Request................................4-540.10Revocation of Validation.........................................4-540.11Considerations for Software Evaluation...........................4-540.12LSAR Independently Developed ADP Pamphlet........................4-5CHAPTER 5GUIDANCE FOR ASSIGNMENT OF LCN, ALC, LCN TYPE AND UOC..........5-150.0Purpose.............................................................5-150.1 Traditional LCN Assignment.......................................5-150.2 Functional and Physical LCN Assignments..........................5-150.2.1LCN Type......................................................5-350.3 LCN Assignment...................................................5-350.3.1Classical LCN Assignment......................................5-550.3.2Modified Classical Assignment Method..........................5-550.3.3Sequential Assignment Method..................................5-550.4 Alternate LCN Code (ALC).........................................5-550.4.1ALC Usage for a Single Configuration/Model....................5-950.4.2ALC Usage for LSAR Reports....................................5-950.4.3Lower-tiered LCN/ALC Selection...............................5-1150.5 Usable On Code..................................................5-1150.5.1ALC and UOC Relationship.....................................5-1150.5.2UOC and ALC Usage for LSAR Reports...........................5-1250.6 Summary.........................................................5-12CHAPTER 6ACTIVITY AND DATA MODELING.....................................6-160.0 Activity and Data Modeling.........................................6-160.1 Activity Modeling................................................6-160.2 Data Modeling....................................................6-160.3 LSAR Data Model..................................................6-160.3.1Normalization.................................................6-260.4 Implementation of the LSAR Data Model for MIL-STD-1388-2B.......6-13APPENDIX AACRONYM LISTING...............................................A-1APPENDIX BMIL-STD-1388-2B DATA TABLES AND REPORTS.......................B-11.0Data Tables and Report...............................................B-11.1Purpose............................................................B-11.2Report Comparison..................................................B-11.3New 1388-2b Reports................................................B-2 1.4LSAR Data Tables....................................................B-21.5Data Table to Report Usage.........................................B-7APPENDIX CPROVISIONING..................................................C-11.0Introduction.........................................................C-11.1Purpose............................................................C-11.2Product Reports and Their Interrelationship........................C-12.0Coding Requirements and Report Selection Logic Exception for Provisioning Reports.................................................C-32.1Assignment of the LCN..............................................C-32.2UOC Assignment.....................................................C-3MIL-HDBK-1388ix2.3Alternate LCN Assignment...........................................C-32.4FGC (WUC/TM FGC) Versus LCN Assignment.............................C-42.5TM Code............................................................C-72.6LCN-IC and IC.....................................................C-122.7Provisioning Contract Control Number (PCCN) Relationships.........C-132.8Suppression Indicator Code (SIC)..................................C-143.0Maintenance Allocation Chart (MAC)..................................C-163.1Purpose of the MAC................................................C-163.2MAC Man-Hour Computations.........................................C-173.3Relationship of the MAC and Tool and Test Equipment Requirements Sections..........................................................C-183.4MAC Source Data...................................................C-184.0Provisioning Requirements...........................................C-204.1Preparation of the PMF............................................C-204.2Utilization of the Automatic PLISN Assignment Routine.............C-214.3Defense Logistics Information System (DLIS) Submittals............C-234.4Provisioning Parts List Index.....................................C-254.5LSA-036 System....................................................C-264.5.1Report Sequence...............................................C-264.5.2Report Format.................................................C-264.5.3Report Options................................................C-264.5.4Control Data..................................................C-314.5.5Provisioning Baseline File (PBF)..............................C-314.5.6QPEI Calculation..............................................C-324.5.6.1Option 1 Quantity Per End Item............................C-324.5.6.2Option 2 Quantity Per End Item............................C-364.5.6.3Option 3 Quantity Per End Item............................C-364.5.7Same as PLISN.................................................C-384.5.8Update Transactions...........................................C-394.5.8.1Update Processing.........................................C-404.5.9The LSA-036 Report Header.....................................C-434.5.10The LSA-036 Part II Error Report.............................C-464.5.11LSA-036 Part III Options.....................................C-464.5.11.1Army LSA-036 System Edits................................C-464.5.11.2Air Force "L" Card Merge Routine.........................C-474.6Provisioning Utilities............................................C-474.6.1Sesame Extract Program........................................C-474.6.2Government/Contractor PBF Comparison..........................C-474.6.3LSA-036 to PMF Update Transactions............................C-474.6.4QPEI Calculation by PCCN and UOC..............................C-475.0Repair Parts and Special Tool List (RPSTL)..........................C-485.1RPSTL Content.....................................................C-485.2Report Selection..................................................C-485.3Documentation of KITS for RPSTL...................................C-485.4Data Content......................................................C-495.5Draft/Proof RPSTL Review..........................................C-50MIL-HDBK-1388xMIL-HDBK-13881.0Purpose.This handbook provides an easy to understand ready referencedocument for the entire LSA process as it is generally applied to a DODacquisition program.1.1Application of handbook.This handbook applies to all system/equipmentacquisition programs, major modification programs, and applicable research anddevelopment projects through all phases of the system/equipment life cycle.This handbook is for use by both contractor and government activities.Asused in this handbook, the requiring authority is generally a governmentactivity but may be a contractor when LSA documentation requirements arelevied on subcontractors.The performing activity may be either a contractoror government activity.The use of the term, contract, in this standardincludes any document of agreement between organizations to include between agovernment activity and another government activity, between a governmentactivity and a contractor, or between a contractor and another contractor.1.1.1Content of appendices.There are three appendices in this handbook.Appendix A contains a list of acronyms, appendix B is reference material onMIL-STD-1388-2B data tables and reports, and appendix c contains a proceduralsupplement to MIL-STD-1388-2B. This supplement will help in thedocumentation and report selection of provisioning related reports.MIL-HDBK-138821.1.2Tailoring.This handbook cannot be specified directly in a contract.MIL-STD-1388-1 and MIL-STD-1388-2 should be the standards specified in acontract.The requiring authority (RA) and the material developer (MD) willuse MIL-STD-1388-1 in the selection of tasks for inclusion in the contractstatement of work (SOW) and shall establish the LSA documentation requirementsbased upon the elements identified in those tasks.1.1.3LSA process.MIL-STD-1388-1 and MIL-STD-1388-2, implements the LSAguidelines and requirements established by DOD Instruction 5000.2, DefenseAcquisition Management Policies and Procedures, and DOD Directive 5000.1,Defense Acquisition.This handbook discusses the LSA and LSAR process;contracting for LSA and LSAR; LSAR report selection option and reportspecifications; LSAR software validation process; LSA Control Number (LCN),Alternate LCN Code (ALC), and Usable On Code (UOC) application in a functionalverse physical environment; and an explanation of the data modeling processwhich was used to develop the relational LSAR data base.2.REFERENCED DOCUMENTS.2.1General.Completion of the LSA process requires use of many relateddocuments from which the appropriate data can be obtained.The specific useof each document is identified in the appropriate chapter or appendix of thishandbook.Unless otherwise specified, the following standards and handbooksof the issue listed in that issue of the Department of Defense Index ofSpecifications and Standards (DODISS), specified in the solicitation form, apart of this standard to the extent specified, herein.Military Standards.MIL-STD-335 Manuals Technical Repair Parts and Special Tools ListMIL-STD-470 Maintainability Program for Systems and EquipmentMIL-STD-471 Maintainability Verification/Demonstration/EvaluationMIL-STD-680 Contractor Standardization Program RequirementsMIL-STD-756 Reliability Modeling and PredictionMIL-STD-785 Reliability Program for Systems and Equipment Development andProductionMIL-STD-881 Work Breakdown Structures for Defense Materiel ItemsMIL-STD-882 System Safety Program RequirementsMIL-STD-965 Parts Control ProgramMIL-STD-1366Transportability CriteriaMIL-HDBK-13883MIL-STD-1367Packaging, Handling, Storage, and Transportability Program Requirements for Systems and EquipmentMIL-STD-1379Military Training ProgramsMIL-STD-1388-1Logistic Support AnalysisMIL-STD-1388-2DOD Requirements for a Logistic Support Analysis RecordMIL-STD-1390Level of RepairMIL-STD-1478Human Performance AnalysisMIL-STD-1629Procedures for Performing a Failure Mode, Effect, andCriticality AnalysisMIL-STD-1839Calibration and Measurement RequirementsMIL-STD-1843Reliability Centered Maintenance for Aircraft Engines andEquipmentMIL-STD-2073-1DOD Materiel Procedures for Development and Application of Packaging RequirementsMIL-STD-2073-2Packaging Requirement CodesMIL-STD-2097Requirements for Acquisition of End Items of Support Equipment, Associated Integrated Logistics Support, andRelated Technical Data for Air SystemsMIL-STD-2173Reliability Centered Maintenance For Naval Aircraft Weapon Systems and Support EquipmentMilitary Handbooks.MIL-HDBK-217Reliability Prediction of Electronic EquipmentMIL-H-46855 Human Engineering Requirements for Military Systems, Equipments, and FacilitiesMilitary Specifications.MIL-T-31000 Technical Data Packages, General Specifications forMIL-M-38807 Manuals, Techincal:Illistrated Parts Breakdown, PreparationofMIL-M-49502 Manuals, Technical:Repair Parts and Special Tool ListMIL-M-63036 Manuals, Technical:Operators, Preparation of (Army)MIL-M-63038BManuals, Technical:Organizational or Aviation Unit DirectSupport, or Aviation Intermediate, and General Support MIL-HDBK-13884Maintenance (Army)Federal Manuals and Catalogs.H6-1Federal Item Name Directory for Supply CatalogingOther Documents.AMCP 750-2Guide to Reliability Centered MaintenanceDARCOM 750-16 DARCOM Guide to Logistic Support Analysis

DARS NO.6 Defense Acquisition Regulation Supplement NO. 6DOD 4100.38-M DOD Provisioning and Other Preprocurement Screening ManualDODD 5000.1 Defense AcquisitionDODI 5000.2 Defense Acquisition Management Policies and ProceduresMTMC PAM 70-1 Transportability for Better Strategic MobilityMRSAP 700-11Cost Estimating Methodology for Logistic Support Analysis(CELSA) Guide(Non-Government standards and other publications are normally available fromthe organizations that prepare or distribute the documents.These documentsalso may be available in or through libraries or other informationalservices.)3.DEFINITIONS. 3.1Assembly.A number of parts or subassemblies, or any combinationthereof, joined together to perform a specific function and capable ofdisassembly (e.g., power shovel-front, fan assembly, audio frequencyamplifier).NOTE:The distinction between an assembly and subassembly isdetermined by the individual application.An assembly, in one instance, maybe a subassembly in another where it forms a portion of an assembly.3.2Component.An assembly or any combination of parts, subassemblies, andassemblies mounted together normally capable of independent operation in avariety of situations.3.3Design Change.An approved engineering change incorporated into the enditem which modifies, adds to, deletes, or supersedes parts in the end item.3.4End Item.A final combination of end products, component parts/materialswhich is ready for its intended use, e.g., ship, tank, mobile machine shop,aircraft, receiver, rifle, or recorder.3.5LSA.The selective application of scientific and engineering effortsundertaken during the acquisition process, as part of the system engineeringand design process, to assist in complying with supportability and other ILSMIL-HDBK-13885objectives.3.6LSAR.That portion of LSA documentation consisting of detailed datapertaining to the identification of logistic support resources requirements ofa system/end item/equipment.3.7LSA Candidate.A component, subassembly, assembly, software, or enditem/article on which maintenance action is considered feasible as a result ofa preliminary or detailed tradeoff analysis.3.8LSA Documentation.All data resulting from performance of LSA tasks,conducted under MIL-STD-1388-1, to include LSAR, pertaining to an acquisitionprogram.3.9Manufacturers Part Number.See reference number.3.10Material Developer.The organization, government or industry, that isoverseeing the development of a piece of hardware/software.3.11Part.One, two or more pieces, joined together which are not normallysubject to disassembly without destruction or impairment of designed use.3.12Part Number.See reference number.3.13Performing Activity.The organization, government or industry, that isbuilding/designing a piece of hardware/software.3.14Reference Number.Any number, other than a government activity stocknumber, used to identify an item of production, or used by itself or inconjunction with other reference numbers to identify an item of supply.Reference numbers include:manufacturers part, drawing, model, type, orsource controlling numbers; manufacturers trade name; specification orstandard numbers; and, specification or standard part, drawing, or typenumbers. 3.15Repair Part.Material capable of separate supply and replacement whichis required for the maintenance, overhaul, or repair of a system, equipment orend item.This definition does not include Support Equipment, but doesinclude repair parts for support equipment.3.16Requiring Authority.The organization, government, that has arequirement for a piece of hardware/software.3.17Spares.Articles identical to or interchangeable with the end articleson contract which are procured over and above the quantity needed for initialinstallation for support of a system.3.18Subassembly.Two or more parts which form a portion of an assembly or acomponent replaceable as a whole, but having a part or parts which areindividually replaceable (e.g., gun mount stand, window recoil mechanism,floating piston, telephone dial, mounting board with mounted parts, powershovel dipper stick).MIL-HDBK-138863.19Support Equipment."Support Equipment" is that equipment required tomake an item, system, or facility operational in its intended environment.This includes all equipment required to maintain and operate the item, system,or facility including aerospace ground equipment and ground equipment.3.20Support Items.Items subordinate to or associated with an end item,i.e., spares, repair parts, and support equipment.Chapter 1MIL-HDBK-13881-110.LOGISTIC SUPPORT ANALYSIS AND THE ACQUISITION PROCESS.10.1Major Criteria.DOD Directives 5000.l and 5000.2 establish IntegratedLogistic Support (ILS) andacquisition policies.Prime factors governingsystem acquisition programs are cost, schedule, and performance withsupportability being a subset of performance.The LSA provides directsupportability and cost factor input for new systems and provides major inputto system decisions.Specific criteria and emphasis varies from system tosystem,but three prime LSA outputs emerge at the level affecting acquisitiondecisions.These are described below.10.1.lManpower and Personnel Constraints.Manpower and skill levelrequirements are treated as any major design function.Personnel parametersbegin with the initial concept.DODI 5000.2, Human System Integration in theDefense System Acquisition Process, sets system manpower estimatingrequirements.Manpower and personnel requirements are stated as numbers,skills, and skill levels during the design process and may use the manpowerand personnel policies of Services. 10.1.2System Readiness.Design parameters and logistic support resources relate to system readiness objectives and goals.Operational availability,sortie rates (surge/sustained), and percent coverage are wartime factors whichare often used for peacetime readiness measurements.System readiness, as anintegral part of system performance, must be managed beginning with theearliest conception of new/modified system/equipment.10.1.3Cost.Operation and support investment along with other acquisitioncosts must be considered for any acquisition.Comparison of life cycle cost(LCC) estimates to requirements for alternatives is vital to tradeoffdecisions.Cost factors should address resource requirements to achievespecified levels of readiness for given conditions.Uncertainty of resourcessuch as manpower and energy, must be addressed to minimize cost and meetsystem readiness objectives.The objective is to optimize an acquisitionrelated to system performance, cost, and schedule goals of the system.10.2Acquisition Process.Figure 1.1 is an overview of the acquisitionprocess, showing life cycle phases and LSA process decision points.The LSAprocess has five phases begining with a validated identified requirement. Program initiation documents are then prepared.The Acquisition phases are:10.2.1Concept Exploration/Definition (CED) Phase.Alternatives to satisfythe requirement are evaluated and compared in terms of performance, readiness,supportability, schedule, and cost.System level analysis which affect designand operational concepts, readiness, logistics and operational supportcharacteristics are defined.These support the use study and ILS/LSA conceptand strategy supportability constraints, of the proposed system.The ILS/LSAproducts include cost improvement and readiness targets, support conceptalternatives, supportability related design and support system objectives.10.2.2Demonstration and Validation (D&V) Phase. Concepts now become hardwaredesign.Removal of technical uncertainties in the design are verified andevaluated using advance development models.The ILS/LSA products now includeChapter 1MIL-HDBK-13881-2 f1.1Chapter 1MIL-HDBK-13881-3firm support concepts, supportability related design goals and thresholds,readiness, and supportability system parameter objectives.10.2.3Engineering and Manufacturing Development (EMD) Phase.Validateddesigns are developed as models or prototypes.Functional/environmentaltesting verifies design performance requirements.The ILS/LSA effort ismaximized to influence maintenance planning and identify detailed logisticsupport resource requirments and deficiency solutions which are validated byoperational testing.Detailed analyses identify preventive/correctivemaintenance, calibration, and servicing requirements.Firm logistic supportand maintenance plans are developed.Manufacturing procedures, and controltechniques are designed for economical mass production.10.2.4Production and Deployment (P&D) Phase.A model or prototype developedand optimized during EMD is produced and tested.An effective support base isestablished and new systems or equipment are readied for deployment andoperational use.10.2.5Operations and Support Phase.This phase begins after initialfielding and overlaps Prod/Deploy.The ILS/LSA activities include:postproduction support; correction of quality and safety problems; and newtraining programs and feedback mechanisms are devised for reduction ofreadiness and supportability problem areas.The LSAR is maintained andupdated during the life cycle of the system/equipment.l0.3 LSA Process. LSA is an iterative, multi-disciplined, process having many interfaces.It can be divided into two general parts: (a) analysis ofsupportability, and (b) assessment and verification of supportability. 10.3.1Analysis of Supportability.These analyses affecting design andoperational concepts begin at system level; identify gross logistic supportresource requirements of alternative concepts; and relate design, operational,and supportability characteristics to system readiness objectives and goals. 10.3.1.1System Level Analyses.These efforts are characterized by usestudies, comparative analysis studies, support driver identification,technologicalopportunities, tradeoffs analysis, alternative support conceptssuch as organic versus contractor support, built-in versus external testcapability, and varying maintenance levels. 10.3.1.2System Level Tradeoffs.Analyses of lower indenture levels andsupport system optimization set by the system level analysis begin.Thesedefine logistic support resource requirements of the system using anintegrated analysis of all operator maintainer functions and tasks.These aredone to determine task frequencies, task times, personnel and skillrequirements, and other support requirements, to include all ILS elements. 10.3.1.3Optimization.This is achieved by allocating functions and tasks tospecific maintenance levels, doing repair versus discard and ReliabilityCentered Maintnenance (RCM) analyses, and formulating design recommendationsto optimize maintenance times and logistic support resource requirements. Data developed is used as direct input forproducts associated with each ILSChapter 1MIL-HDBK-13881-4element e. g., provisioning lists, personnel and training requirements, andtechnical manuals.This assures compatibility between ILS element documentsand permits common use of data which apply to more than one logistic element.10.3.2Assessment and Verification.The process begins with early planningto verify support concepts and is used during the entire life cycle to demonstrate and adjust analysis results and products as required.10.4Interfaces.Some major LSA activities and their interfaces which playkey roles are listed below:10.4.1Comparative Analysis (Task 203).Interfacing activities:humanfactor, reliability, maintainability, safety, and design engineers and ILSelement managers.This task is used to:define a sound, analyticalfoundation for projecting new system design and supportability features; toidentify those which need improvements; identify those cost drivers whichsupport thereadiness of the new system; and document risks involved in usingthe comparative data in subsequent analyses.10.4.2Functional Requirements Identification (Task 301).Interfacingactivities:design, reliability, maintainability, and human factorengineering, safety and ILS element managers.10.4.3Tradeoff Analysis (Task 303).Interfacing activities:design,reliability, maintainability, safety, and human factor engineering, costestimating, and ILS element managers.10.4.4Task Analysis (Task 40l).Interfacing activities:reliability,maintainability, human factor, and safety engineering.Performed to analyzerequired operations, maintenance, and support tasks to identify resourcesneeded for each task; highlight are new or critical tasks, including hazardousmaterialsand their environmental impact; define transportabilityrequirements; identify support requirements which exceed desired goals,thresholds, or constraints; provide data supporting recommended designs whichenhance readiness and supportability; and provide source data to developrequired documents, i.e., Maintenance Allocation Charts (MAC), TechnicalManuals (TM), Provisioning documentation, etc.Figure 1.2 shows the interfaces and information flow from supporting militarystandards.Arrows indicate that information developed using one militarystandard is referenced as input from another standard.A military standardmust specifically require information developed using another standard for arelationship to be shown.For example:Failure Modes, Effects and Criticality Analysis (FMECA) data isdeveloped using MIL-STD-1629, but is also used for analysis purposes in MIL-STD-1388-1A and is documented in MIL-STD-1388-2B; therefore, an arrow leadsfrom MIL-STD-1629 to MIL-STD-1388-1A/2B.MIL-STD-1629 does not require datadeveloped by MIL-STD-1388-1A/2B; therefore, no arrow leads from MIL-STD-1388-1A/2B to MIL-STD-1629.Review of LSA interfaces should be described in the LSA Plan (LSAP) (Task l02)Chapter 1MIL-HDBK-13881-5f1.2Chapter 1MIL-HDBK-13881-6f1.3Chapter 1MIL-HDBK-13881-7to assure input-output relationships, responsibilities, and timing ofactivities are properly addressed to prevent over-lap and duplication. Guidance found in subsequent paragraphs will reduce interface problems.l0.4.5Inputs and Outputs for System Level LSA (Subtask 303.2.3).Systemlevel LSA may involve system analysis/engineering at thehardware-operating-support level.It is a collection, synthesis, and "system"analysis of various specialized input. It impacts interface activities bydefining boundary conditions or goals of specialized engineering programs andILS element concepts and plans.Figure 1.3 shows task 303.2.3 relationships.l0.4.6Refinement and Extension of System Level LSA.As the process isiterated, limits, constraints, and objectives are refined and expanded basedon engineering and ILS input.A support system is established with limits andobjectives set.Follow-on tradeoffs between engineering specialties and ILSelements are made within established boundaries which include Built In Test(BIT)/Built In Test Equipment (BITE) verse external dignostics (Subtask303.2.8) and training tradeoffs (Subtask 303.2.6).10.4.7Task Analysis Interfaces.LSA includes all task analyses, however,specific areas (e.g., critical maintenance tasks) may be analyzed as part ofthe human engineering program.Detailed task analyses input such as taskfrequencies, repair times, safety hazards, and failure effects, are normallydeveloped by reliability, maintainability, and safety specialists.l0.4.8Resource Requirements Identification.LSA identifies all logisticsupport resource requirements.This is an iterative process with informationbeing passed between logistics, design and specialized engineering areas.These requirements are summarized in the LSA data base.These requirementsare used by ILS managers for development of plans and products.10.5Strategy in Developing Analysis Requirements.10.5.1General.Cost effective analysis efforts channel available resourcesto areas offering the greatest benefit to the program.Strategies rely onestablishing programs to achieve supportability and support system objectives. They must influence hardware design, support, and logistic support resourcerequirements.The requirements are translated into specific objectives earlyin the program when maximum flexibility exists.Objectives are iterated andrefined until they are firm program goals/requirements.Developing analysisstrategies is difficult due to the number of variables.Possible impact ofvariables must be addressed during the process when analysis tasks/subtasksare tailored and scheduled to meet milestones.Guidance provided will assistin the tailoring process, however, it must be adapted to specific programs.10.5.2 Task Selection and Focusing.10.5.2.lGeneral.Analysis requirements selection, begining at subtasklevel, includes a wide range of considerations.Figure 1.4 depicts a generaltailoring logic tree useful when selecting tasks.Table 1 lists task/subtaskuse by development phase and engineering activity.Guidance must beadjustedfor each program since program aspects may occur different acquisition phasesChapter 1MIL-HDBK-13881-8for different programs.Initial task/subtask selection is adjusted for: (a)design freedom; (b) time phasing adjustments if program is "fast track"; (c)work already done; (d) data availability/relevancy; (e) time and resourceavailability; (f) Policy directive (DODI 5000.2) requirements; (g) desiredtasks not in the standard; and (h) procurement considerations. Most of thesefactors tend to reduce or restrict the amount of analysis activity. Additional guidance is provided later in this section. 10.5.2.2 Focusing.After initial subtask selection is completed, furtherfocus is needed to concentrate effort in high leverage areas and to specifyother requirements.Focusing considerations should include:(a) Modificationor restriction of the subtask to significant areas; (b) Specification ofsubtasks to allow assignment to the appropriate activity; (c) Specification ofmodels and associated data to be used; and (d) Specification of areas oractivity requiring requester approval.RA must be specific when defininganalysis needs for tasks and subtasks under the task input specified.Oftenl0 to 20 percent of systems subsystems control 80 to 90 percent of the totalsupport demands.Some Task 303 evaluations and tradeoffs are very general andbenefit from greater detail to focus on key areas.Models and definitions,particularly for LCC, desired for a particular analysis should be specified,if possible, especially if there is competition. Model considerations arediscussed in greater depth under procurement considerations.The remainder ofthis section deals with specific factors considered during development of theLSA strategy.10.5.3Factors Impacting Strategy.10.5.3.lType of Program/Change.Program categories are:new programs;planed product improvement (PPI); or "off-the-shelf" programs.Manymodifications require redoing or a new approach to some of the analysis workalready done.The program type impacts objectives, subtask selection andfocusing.For PPIs, analysis objectives may focus on support risks on thealtered part, or opportunities to improve the equipment by improvingsupportability characteristics.New or high technology efforts may increaserisk to attain supportability goals.Those risks must be reduced.Usingproven technology has less risk and may offer more opportunity to reducelogistic support burdens than a more advanced technology. These factors greatly impact on initial objective determination.Systemversus equipment proposals impact subtask selection and focusing.Forexample, a limited, focused readiness analysis may be appropriate for anequipment contract, while alternative support concepts may be more appropriatefor equipment level contracts due to a fixed system support concept. System readiness objectives may be to "hold the line" or they may be moreambitious.Readiness goals must be a primary management focus beginning withprogram initiation. If such goals are ambitious, one focus of the earlyanalyses should be toward readiness related system design and supportobjectives, such as reliability and turn around time. Systems and equipments having large support personnel demands or highOperations and Support (O&S) costs obviously present greater investmentChapter 1MIL-HDBK-13881-9opportunities for improvement than those with low demands or costs and shouldreceive greater consideration in selecting preliminary analysis objectives.10.5.3.2Amount of Design Freedom.The amount of design freedom is relatedto program considerations such as phasing and is a key factor in subtaskelection.The objective of most front end analysis subtasks is to influenceselection of design characteristics to achieve improvements in readiness,supportability, and cost.For fixed designs, little benefit be derived fromdoing these tasks.Some of the factors listed in paragraph 10.5.3.l provideclues in this regard. Product improvements may limit design freedom to specific subsystems unlessareas of no, or minor change are open to redesign opportunity to reducelogistic support burdens.Fast track programs tend to move up or back various possible analysissubtasks, but fast track programs also tend to use existing technology andplan on preplanned product improvement rather than employ new technology.Thepoint of design freedom thus shifts.Design freedom may exist for the supportsystem but not the mission system.LSA effort and objectives should befocused accordingly. The LSA objective of causing supportability requirements to be an integralpart of system/equipment requirements and design can best be achieved ifdesigners are oriented toward supportability objectives commencing with thedesign effort.Technical information documented during the design process, must be providedto designers and logisticians to help identify interface problems betweendesign concepts and operators, maintainers, and support equipment.Technicaldesign information, e.g. electro-mechanical diagnostic features, interfaces,reliability estimates, item functions, and adjustment requirements, whichdetermine supportability are an integral part of design documentation.Ifthere is design freedom, the LSA plan should describe the generation, control,and approval of this type information.10.5.3.3Time and Resources Available.LSA requires time and resources toinfluence design.Do not specify tasks if results will not be available toaffect design, or unless improvements can be scheduled as part of a PPI. Fast track programs reduce time available for design influence analysis tasks. Therefore, some analysis task results should be saved as assets for lateruse.Design influence LSA requires resources in the form of people and money.DOD policy is to fund readiness and support considerations upfront, however,resources are constrained in practice.If program funds are short, it may bepossible to perform some tasks, such as comparative analysis and driveridentification, by using in-house capabilities.If the in house capability islimited but funds are available, some subtasks may be done by "study"contractors having special expertise.Chapter 1MIL-HDBK-13881-10Another approach is to exploit inter-relationships between some tasks andsubtasks, e.g., comparative analysis feeds driver identification, which inturn feeds selection of targets for improvement.If only one of these tasksis affordable, targets for improvement would be the logical choice. Thatapproach loses precision since judgments are substituted for hard data on thedeleted tasks.It should be used only as a last resort.10.5.3.4 Work Already Done.Comparative analysis, driver identification andimprovement initiatives completed in preparation of other program initiationor other requirements documents should be reviewed.If adequate, it may beupdated rather than doing a complete revision.Also, program initiation orother requirements documents may prescribe objectives or constraints whichtend to limit the scope of the analysis effort.However, it is essential totest such constraints or objectives and the analysis which supported theirspecification prior to accepting them as hard data.10.5.3.5 Past Experience and Historical Data.The availability, accuracy,and relevancy of experience and historical data bases of similar systems iscrucial to accomplish some tasks and subtasks.Available data bases must beexamined to determine if extensive work is needed to provide focus orrelevancy. If not available, a special sample data effort may be considered,particularly if the required data is in an area of possible high leverage.10.5.3.6 Procurement Considerations. The RA must determine and specify the LSA tasks that will be performed by the government or independent agency,those shared by the government and the developer, and those required of thedeveloper.Once completed, the LSA portion of the contract plan can bedeveloped and work requirements writen into the statement of work (SOW).Prospective performing activities (PA) must be allowed to recommend adding ordeleting LSA tasks and to provide a more detailed subtask definition andschedule.Also, PAshould be encouraged to use cost effective datageneration procedures.Prospective PAs tailoring process and cost reductionefforts should become a factor in the assessment of their capability toperform the LSA.Acquisition program objectives must be considered in preparing procurementdocuments.For example, in a technology demonstration procurement, one mayspecifically exclude certain LSA task requirements. Supportability objectivesin this case would best be served through design influence and generation ofan LSA data base for subsequent detailed analysis effort when the technologyis utilized.If the acquisition program is oriented to develop and procure asystem/equipment, then other LSA tasks become equally important.The nature of the procurement may force the PA to do some analysis activity inorder to make a rational bid.The procurement process offers an excellentopportunity to refine the LSA strategy by involvement of potential performingactivities when competition is present.See chapter 2 for further discussionof contracting for LSA.Chapter 1MIL-HDBK-13881-11F1.4Chapter 1MIL-HDBK-13881-12T1 1Chapter 1MIL-HDBK-13881-13t1 2Chapter 1MIL-HDBK-13881-14t1 3Chapter 1MIL-HDBK-13881-15t1 4Chapter 1MIL-HDBK-13881-16t1 5Chapter 1MIL-HDBK-13881-17t1 6Chapter 1MIL-HDBK-13881-18t1 7Chapter 1MIL-HDBK-13881-19t1 8Chapter 1MIL-HDBK-13881-20t1 9Chapter 1MIL-HDBK-13881-2110.6LSA TASK APPLICATION.10.6.1LSA DEFINITION. LSA is any analysis that results in a decision onthescope and level of logistic support.10.6.1.1LSA Process.The LSA Process consists of: LOGISTICS - Pertaining to developing, acquiring, testing and providingthe elements of support; SUPPORT - That which sustains, maintains, or preserves intact; ANALYSIS- A method of examining something to determine its essentialfeatures and their relationships; PROCESS - A planned series of actions directed to some end.The overall term can then be defined as follows:The LSA PROCESS is a PLANNED TASK SERIES performed to EXAMINE all elements of a proposed SYSTEM to DETERMINE the LOGISTIC SUPPORT required to KEEP that system USEABLE for its intended purpose throughout its intended lifecycle; and to INFLUENCE theDESIGN so that BOTH the SYSTEM andSUPPORT can be PROVIDED at an AFFORDABLECOST.LSA tasks can be grouped into three generic sets:those which ANALYZE ANDSYNTHESIZE, support requirements, those which VERIFY the adequacy of logisticsupport identified and those required to MANAGE the other tasks.The numberof tasks associated with each generic set varies widely and are generallyperformed in sequence.The MANAGEMENT tasks must begin before the program isformally initiated during the Mission Need Statement (MNS) phase. Developing/planning a strategy for the LSA is the first task performed. Coordination and control tasks continue during the life of the LSA program.Most ANALYTICAL tasks begin during the CED phase and are iterated during alllater phases.The amount of information examined and level of detailidentified increase with each task iteration. The ANALYZE AND SYNTHESIZE setof tasks can be further divided into three subsets;the system definition(hardware, software and support), the evaluation and tradeoff alternatives,and the identification of required resources.Initially system level analyze and synthesize tasks are performed to:influence design and operational concepts; estimate gross logisticrequirements of alternative concepts; and relate design, operation, andsupport characteristics to system readiness objectives.Once the system level tradeoffs are made, emphasis shifts toward optimizingthe support system within established system boundaries.As additional datais specified and refined, the analyze and synthesize tasks are iterated forprogressively lower indenture levels.Sensitivities to changes in key factorsare analyzed and tradeoffs between elements of support are made.Chapter 1MIL-HDBK-13881-22A more detailed identification of the required support resources can then bemade.Support resources are optimized by:identifying repair and discardtasks; applying RCM; allocating tasks to specific maintenance levels; andformulating design recommendations to achieve improvements.Verifying the accuracy and adequacy of the logistic support identified beginsearly in the process.Testing, evaluating and correcting deficiencies in boththe design and the support system continue throughout the life cycle. Thevalidity of the analysis results and attendant data products must besuccessfully demonstrated within stated confidence levels.Results of formaltest and evaluation programs and post deployment assessments are analyzed andcorrective actions implemented as necessary.10.6.2HARDWARE LEVELS TO WHICH THE LSA PROCESS IS APPLIED.The LSA process is applied to the System/Subsystem and Subassembly/Componenthardware levels.These levels correspond to the amount of informationavailable for examination and the level of detail required to clearlydetermine and define the desired result. Two of the objectives of the LSAprocess are to influence the design of a proposed system and identify itslogistic support resource requirements.There are two relationships that aresignificant in meeting these objectives:logistics influence on design isgenerally initiated at the system/subsystem level and projected downward; andlogistic support resource requirements are identifies at thesubassembly/component level and summed upward.Figure 1.5 shows when the opportunity to influence the design logistically isgreatest.It also illustrates a point beyond which the opportunity toinfluence the design is lost.In addition, this figure shows when the actionsto identify and update the detailed ILS resource requirements should be taken.10.6.3 LSA TASKS.MIL-STD-1388-1A divides the LSA tasks into five general sections:TASK SECTION 100 - PROGRAM PLANNING AND CONTROLTASK SECTION 200 - MISSION AND SUPPORT SYSTEMS DEFINITIONTASK SECTION 300 - PREPARATION AND EVALUATION OF ALTERNATIVESTASK SECTION 400 - DETERMINATION OF LOGISTIC SUPPORT RESOURCE REQUIREMENTSTASK SECTION 500 - SUPPORTABILITY ASSESSMENTFigure 1.6 shows how the three broad generic sets of tasks constituting theLSA process relate to the five general task sections and 15 LSA tasksdescribed in MIL-STD-1388-1A.It also shows the relationship of these LSAtasks to LSAR data tables.Chapter 1MIL-HDBK-13881-23F 1.5Chapter 1MIL-HDBK-13881-24F 1.6Chapter 1MIL-HDBK-13881-25This section includes a summary of each LSA task as identified inMIL-STD-1388-1A.Each task summary addresses the following topics:Purpose;Required for; When required; Responsibility; Applicable Military Standards;LSA Documentation, for reference information see appendix b ;LSAR Reports, forreference information see appendix b; Products; and Input and Source.The RA for each of the serivices is:Army is Training and Docturine Command(TRADOC); Air Force is Concept Action Group (user and Product Personnel); Navyis Operations Naval (OPNAV) (Aircraft, Sea, Sub, and Missles); and MarineCorps is Marine Corps Combat Development Command (MCCDC).Each of these RAshave responsibilities for LSA task accomplishment for their respectiveservices.The MD for each of the services is:Army is Army Material Command(AMC); Air Force is Air Force Material Command (AFMC); Navy is Naval AviationCommand (NAVAIR), Naval Sea Command (NAVSEA), Naval Submarine Command(NAVSUB), and Space and Warfare Command (SPAWAR); and Marine Corps is MarineCorp Systems Command (MCSC).PA is the activity actually performing the LSA. It may be either a government organization or industry.It is emphasizedthat LSA task accomplishment is a cooperative effort between the RA, MD, andPA.10.6.3.1TASK 101 - DEVELOPMENT OF AN EARLY LOGISTIC SUPPORT ANALYSISSTRATEGYPURPOSE:This task is the earliest planning activity for an LSA program.Itspurpose is to:develop a proposed LSA program strategy for use early in theacquisition program; and identify the LSA tasks and subtasks which willprovide the best return on investment and document the risks of accomplishingthese objectives.REQUIRED FOR:The LSA strategy interrelates with the acquisition strategy and is included in the ILS Plan.It should generally be available prior topreparation of any solicitation document containing LSA task requirements, andshould be used as a guide in developing such documents.WHEN REQUIRED:Initial LSA strategy development is begun in the CED phaseconcurrent with development of the acquisition strategy.The LSA strategy isgenerally updated through the (P&D) phase.Required updates should becompleted prior to initiation of the next program phase, so that the updatedLSA strategy is available concurrent with phase initiation.RESPONSIBILITY:The RA is responsible for performing Task 101 to provideearly management of the LSA program prior to initiation of D & V.The MDassumes responsibility for this task prior to D&V and retains it through P&D.APPLICABLE STANDARDS:MRSAP 700-11.LSA DOCUMENTATION:None.LSAR REPORTS: NonePRODUCTS:Solicitation document and Statements of Work (SOW)Chapter 1MIL-HDBK-13881-26INPUTS AND SOURCE:MNS, Operational requiremetns Document (ORD), IntegratedProgram Summary (IPS), and Cost and Operational Effectiveness Analysis (COEA)of DODI 5000.210.6.3.2TASK 102 - LOGISTIC SUPPORT ANALYSIS PLANPURPOSE:To develop a LSAP which will effectively implement the LSA program. It also documents the LSA management structure and authority; what LSA tasksare to be accomplished; when each task will be accomplished; whatorganizational units will be responsible for accomplishing each task; how alltasks are integrated and how results of each task will be used.REQUIRED FOR:The LSAP is a basic tool for establishing and executing aneffective LSA program to meet the system and logistic requirements.When it is submitted as part of the response to a solicitation document, it is used inthe source selection process.WHEN REQUIRED:The LSAP is generally prepared in CED and is updated in allsubsequent phases.RESPONSIBILITY:During CED, the RA is responsible for initial preparation of the LSAP.The MD assumes responsibility for updating the LSAP prior to D&Vand retains LSAP responsibility during subsequent phases.The MD assess andverifies for completeness of all subtasks accomplished by the PA.APPLICABLE STANDARDS:MIL-STD-881.LSA DOCUMENTATION:None.LSAR REPORTS: NonePRODUCTS:Management structure; what LSA tasks/subtasks are done, when, bywhom, and how integrated; LSA schedules an their relationship to otherschedules; system engineering interfaces; Data exchange; Work BreakdownStructure (WBS) for LSA Candidate list; LCN numbering system; GovernmentFurnished Equipment/Government Furnished Information (GFE/GFI); and ReviewProcedures.INPUTS AND SOURCE:10.6.3.3TASK 103 - PROGRAM AND DESIGN REVIEWSPURPOSE:To provide for timely LSA program participation in the officialreview and control of design information; the scheduling of detailed LSAprogram reviews; and logistic risk assessments at program reviews.It alsoensures that all pertinent aspects of the LSA program are addressed as anintegral part of all formal program and design reviews.REQUIRED FOR:These procedures for the review of design information from asupport standpoint within the performing activity provide logistic supportspecialists a mechanism for accomplishing design influence and tradeoffs.LSAChapter 1MIL-HDBK-13881-27program reviews include but are not limited to ILS management team meetings,reliability program reviews, maintainability program reviews, technical datareviews, test integration reviews, and provisioning reviews.They aid inmonitoring the overall progress, quality, and consistency of the LSA effort.WHEN REQUIRED:Program and design reviews are generally initiated during CEDand are scheduled periodically throughout subsequent phases.RESPONSIBILITY:The RA is responsible for Task 103 during CED.The MDassumes responsibility during D&V and subsequent phases.The PA hasresponsiblity for setting up and conducting the reviews.APPLICABLE STANDARDS:None.LSA DOCUMENTATION:None.LSAR REPORTS: NonePRODUCTS:Program Reviews, LSA Reviews, Design Review, and ProvisioningReviews.INPUTS AND SOURCE:10.6.3.4TASK 201 - USE STUDYPURPOSE:To identify support factors related to the systems intended use.Also, to document quantitativedata results (e.g. target audiencedescription) which must be considered when developing support alternatives.REQUIRED FOR:Quantitative support factors (operating requirements, transportation modes/times, allowable maintenance periods, and environmentalrequirements which include hazardous materials, hazardous waste, and otherpollutants) identified by the use study are incorporated in the IPS/ORD.WHEN REQUIRED:The Use Study is a PREREQUISITE to all other analysis tasks;therefore, it should be initiated in the CED phase.Updates of the use studyare generally applicable through EMD.Once planned operational and supportenvironments of the new system are identified, visits to existing units anddepots which simulate those environments can provide significant input intouse study updates.RESPONSIBILITY:Task 201 is the responsibility of the RA through D&V.The MDhas update responsibility during EMD.APPLICABLE STANDARDS:None.LSA DOCUMENTATION:LSAR Data Tables AA, AB, AC, AD, AE, AF, AG, AH, JA, JB,and JE.LSAR REPORTS: LSA-003, 023, 075, and 085PRODUCTS:ORD, Support Alternatives Chapter 1MIL-HDBK-13881-28INPUTS AND SOURCE:None.10.6.3.5TASK 202 MISSION HARDWARE, SOFTWARE AND SUPPORT SYSTEMSTANDARDIZATIONPURPOSE:To define support and support related design constraints based uponsupport standardization considerations.It also provides support relatedinput to mission hardware and software standardization efforts.REQUIRED FOR:Initial task results support the IPS.Results of furtheriterations of this task are used in the ORD and development specification.WHEN REQUIRED:Task 202 is initiated in the CED phase to establish supportsystem standardization requirements for the system/end item level prior tobeginning the design effort.This task is iterated at progressively lowerhardware levels through EMD.During the P&D phase, Task 202 is generallyapplicable to design changes only.RESPONSIBILITY:The RA is responsible for task 202 during MNS and CED. During D&V and subsequent phases, the MD is reponsible for this task.Datarequired for the latter part of Task 202 is normally provided by thestandardization program and the parts control program.Coording theseprograms is required to avoid duplication of effort.APPLICABLE STANDARDS:MIL-STD-680 and MIL-STD-965.LSA DOCUMENTATION:None.LSAR REPORTS: NonePRODUCTS:Determine benefits/risks if used, Define resultant designconstraints, Provide support related input to standardized efforts, Recommendstandardization approached, and Participate in standardization efforts.INPUTS AND SOURCE:None.10.6.3.6TASK 203 - COMPARATIVE ANALYSISPURPOSE:This task will:define an analysis base needed to project newsystem design and supportability features and identify those needingimprovement; identify features driving cost, support, and readiness of the newsystem; and document risks impacting comparative data in subsequent analyses.REQUIRED FOR:Initial results are used to develop supportability factorsneeded for the Organizational and Operational (O&O) Plan and ORD. Results oflater analyses are included in the ORD and development specification.Taskresults are also used to develop LSA input required for logistic supportmodeling techniques.WHEN REQUIRED:Supportability factors for the IPS are identified during theCED phase and analysis reports are updated through the EMD phase.Chapter 1MIL-HDBK-13881-29RESPONSIBILITY:The RA is responsible for Task 203 during the MNS and CEDphases.The MD is responsible for Task 203 during D&V and EMD. APPLICABLE STANDARDS:None.LSA DOCUMENTATION:Place comparative Reliability, Avalability, andMaintainability (RAM) data in LSAR data tables BD and BE.Existing facilitydata is placed in data tables FA, FB, and FC.LSAR REPORTS:LSA-012 and 023.PRODUCTS:None.INPUTS AND SOURCE:10.6.3.7TASK 204 - TECHNOLOGICAL OPPORTUNITIESPURPOSE:To identify state-of-the-art technology advancements and designapproaches having opportunities to achieve system support improvements. Available technology is used to improve projected safety, cost, support, andreadiness values, which reduce a new systems environmental impact, andresolve qualitative support problems or constraints identified. REQUIRED FOR:Recommended design objectives and risks identified by task 204are included in the IPS.Updated design objectives are incorporated in theORD and development specification. WHEN REQUIRED:Task 204 is generally initiated during CED and updated duringD&V.The task is selectively applicable during EMD.RESPONSIBILITY:The RA is responsible for Task 204 during CED, with the MDassuming task responsibility during D&V and during EMD when applicable.APPLICABLE STANDARDS:None.LSA DOCUMENTATION:None.LSAR REPORTS:None.PRODUCTS:None.INPUTS AND SOURCE:None.10.6.3.8TASK 205 - SUPPORTABILITY AND SUPPORTABILITY RELATED DESIGN FACTORSPURPOSE:To quantify operations and support characteristics of alternativedesign and operational concepts; and support related design objectives, goalsand thresholds and constraints; and environmental impactfactors to supportrequirement/decision/program documents and specifications.REQUIRED FOR:Input to the IPS, ORD, and development specification.TheChapter 1MIL-HDBK-13881-30translation of these support related design objectives, goals and thresholdsinto support requirements for inclusion in specifications is a criticalelement of this task. WHEN REQUIRED:Task 205 normally begins during CED and is updated during D&V.Subtask 205.2.5 (Specification Requirements) normally applies through EMD. Subtask 205.2.7 (Supportability Goals and Thresholds) is only applicableduring D&V.RESPONSIBILITY:The RA is responsible for Task 205 during CED.The MDassumes task responsibility during D&V and subsequent phases.REFERENCES:None. LSA DOCUMENTATION:Documentation is recorded in LSAR Data Tables AA, AB, AC,AD, AE, AF, AG, AH, AI, AJ, GA.LSAR REPORTS:LSA-003, 023, 075, 076, 077.PRODUCTS:ORD and Specifications.INPUTS AND SOURCE:None.10.6.3.9TASK 301 - FUNCTIONAL REQUIREMENTS IDENTIFICATIONPURPOSE:To identify missions (e. g., shoot, move, communicate) maintenance,and support (transport, maintain, dispose) functions that must be performedfor each system/equipment alternative in the intended environment.It alsoidentifies requirements for operations, maintenance and support, environmentalconsiderations and documenting task performance requirements in a taskinventory.REQUIRED FOR:Identification of functional requirements and risks involved inmeeting them are included in the ORD.Detailed operations and maintenancetask identification and the formulation of design alternatives are normallyincluded in IPS of the ORD.WHEN REQUIRED:Task 301 usually begins in CED Phase.Subtasks 301.2.4(Operations and Maintenance (O&M) Tasks) and 301.2.5 (Design Alternatives) maybe deferred to the D&V phase.Applicable subtasks are updated during EMD. During Production and Deployment (P&D), Task 301 is generally only applicableto design changes.RESPONSIBILITY:The RA is responsible for Subtask 301.2.1 (Functional Requirements) during CED.The MD assumes responsibility for all othersubtasks applicable during CED and subsequent acquisition phases.Allsubtasks require major RA and MD input. The MD assess and verifies forcompleteness of all subtasks accomplished by the PA.APPLICABLE STANDARDS:MIL-STD-1390/-1629/-1478.Chapter 1MIL-HDBK-13881-31LSA DOCUMENTATION:LSAR Data Tables AA, AB, AC, AD, AE, AG, BA, BB, BC, BD,BE, BF, BG, BH, BI, BJ, BK, BL, CA, CB, CC, CD, CE, CF, CG, CH, CI, GA, andXI.LSAR REPORTS:LSA-001, 003, 004, 005, 006, 007, 008, 011, 012, 013, 014, 016,018, 019, 023, 024, 027, 033, 037, 050, 056, 058, 065, 070, 071, 072, 074,075, 076, 077, and 078.PRODUCTS:FMECA report, RCM report, RAM reportINPUTS AND SOURCE:None.10.6.3.10TASK 302 SUPPORT SYSTEM ALTERNATIVESPURPOSE:To establish support system alternatives for evaluation, tradeoffanalysis, and determination of the best system to be developed.REQUIRED FOR:These alternative support system concepts/plans and associatedrisks are addressed in the ORD and IPS.As tradeoffs are made, support system alternatives are refined, updated and included in the ORD and IPS.WHEN REQUIRED:Those subtasks which establish support system alternatives andrisks are required during CED.Subtasks which provide for alternative supportplans and updates are generally applicable in EMD.RESPONSIBILITY:The MD, with major support from the RA, is responsible forall applicable Task 302 subtasks, during CED and subsequent life cycle phases. The MD assess and verifies for completeness of all subtasks accomplished bythe PA.APPLICABLE STANDARDS:LSA DOCUMENTATION:A, B, C, and F LSAR data tables, as applicable.LSAR REPORTS:None.PRODUCTS:None.INPUTS AND SOURCE:None.10.6.3.11TASK 303 - EVALUATION OF ALTERNATIVES AND TRADEOFF ANALYSISPURPOSE:To determine the preferred support system alternative(s) and theirassociated risks for each proposed system; and to determine, through tradeoffanalysis, the best approach to satisfying the need (the one that provides thebest balance between risk, cost, environmental impact, schedule, performance,readiness and support).Chapter 1MIL-HDBK-13881-32REQUIRED FOR:Logistic influence on design is achieved by including earlytradeoff analysis results in requirements documents (IPS and ORD), programdocuments (ILSP), and subsequently into the decision documents (IPS).Resultsof later tradeoff analyses are incorporated in the ORD and developmentspecification.WHEN REQUIRED:Task 303 is generally initiated during CED, with the exceptionof Subtask 303.2.7 (Level of Repair Analysis (LORA)) which is generallyapplicable during D&V.Both system and support system tradeoffs continue tobe iterated through EMD; other key tradeoffs are only selectively appliedduring EMD.RESPONSIBILITY:The RA is responsible for all applicable subtasks during CED; however, major MD support is required.The MD then assumes responsibilityfor all subtasks during D&V and, as applicable, during subsequent phases.TheMD assess and verifies for completeness of all subtasks accomplished by thePA.APPLICABLE STANDARDS:MIL-STD-1478.LSA DOCUMENTATION:LSAR Data Tables AI, AJ, AK, HG, and XALSAR REPORTS:None.PRODUCTS:LORA reportINPUTS AND SOURCE:None.10.6.3.12TASK 401 - TASK ANALYSISPURPOSE:To analyze operations, maintenance, and support tasks; identifyresources required for each task; highlight new or critical resourcerequirements, including hazardous materials and environmental impact; definetransportability requirements; identify support requirements meetingestablished goals/thresholds/constraints; provide supporting data forrecommended design alternatives which enhance supportability or readiness; and provide data to develop required documents, i.e., MACs, TMs, Provisioningdocumentation, etc. REQUIRED FOR:Task analysis, when properly interfaced with system engineeringdisciplines and other ILS functional element inputs, effectivelyintegrates/translates these inputs into ILS documentation output products.

WHEN REQUIRED:The overall program schedule, level of design and operationdefinition govern the timing and scope of the task analysis.The time periodduring which performance of this task can be cost effective is limited.Itbegins with availability of required input from design activities, and extendsonly to that point which allows time for analysis results to be used todevelop ILS documents and acquire the identified support resources.Selectiveuse of this task during D&V should be limited to identification/documentationof new/critical resources.Task 401 is generally applicable during EMD.Chapter 1MIL-HDBK-13881-33RESPONSIBILITY:The MD is responsible for detailed task analysis during EMD. The MD assess and verifies for completeness of all subtasks accomplished bythe PA.APPLICABLE STANDARDS:MIL-STD-335(TM), MIL-STD-470, MIL-STD-785,MIL-STD-882, MIL-STD-1367, MIL-STD-1478, MIL-STD-2073-1A, MIL-STD-2073-2A,MIL-H-46855, MIL-M-49502, MIL-M-63036(TM), and MIL-M-63038(TM).LSA DOCUMENTATION:All LSAR data tables as applicable, except the A LSAR datatables.LSAR REPORTS:All reports are applicable.Draft options should be used forthose reports that have draft options until the end of EMD phase.At thattime data development should be near completion and proof reports should bedeveloped.PRODUCTS:MAC, Repair Parts and Special Tool List (RPSTL), Indentured PartsBreakout (IPB), Stockage lists type III and IV, Preventive Maintenance Checksand Service (PMCS), AF and Navy Maintenance plans, Components of End ItemsList (COEIL), Basic Issue Items List (BIIL), Additional Authorization List(AAL), Expendable/Durable Supplies and Materials List (ESML), SupportEquipment recommendations Data (SERD), Support Equipment (SE) Candidate List,Calibration and Measurement Requirements Summary (CMRS) report, DefenseLogistics Services Center (DLSC) screening, Provisioning TechnicalDocumentation (PTD), Bill of Materials, Provisioning Parts List, SparesAcquisition Integrated with Production (SAIP), Task Analysis, Task InventoryList, Manpower Requiremnents Criteria (MARC) Report, Manprint Report, JointMaintenance interservice data, Packaging data requirements.INPUTS AND SOURCE:None.10.6.3.13TASK 402 - EARLY FIELDING ANALYSISPURPOSE:To assess new system impact on current systems by identifying risklevels surrounding system performance/supportability;sources ofmanpower/personnel skills to meet new system requirements; the impact of notobtaining necessary logistic support resources; and determine combat essentiallogistic support resource requirements.REQUIRED TO:Assure the new system is fielded with all required resources.WHEN REQUIRED:This task analysis is conducted during the EMD phase.RESPONSIBILITY:The MD is responsible for early fielding analysis during EMD. This analysis should be coordinated with and confirmed by the RA. The MDassess and verifies for completeness of all subtasks accomplished by the PA.APPLICABLE STANDARDS:None.

LSA DOCUMENTATION:None.LSAR REPORTS:None.Chapter 1MIL-HDBK-13881-34PRODUCTS:Early Fielding Report.INPUTS AND SOURCE:None.10.6.3.14TASK 403 - POST PRODUCTION SUPPORT ANALYSISPURPOSE:To correct potential post production support problems prior toclosing production lines and to develop a plan to ensure effective support ofthe system during its life cycle.Post production support plan shouldidentify single/dual source items and those for which the government has nodata rights.Plans should include available organic support assets,production line buy-out, or contractor logistic support agreements.REQUIRED FOR:Plans should document identified problems (e.g., inadequatesources of supply/repair); analyze alternative solutions, their associatedcosts and risks; and outline estimated funding and actions required toimplement the preferred solution(s).WHEN REQUIRED:Task 403 is only applicable during the P&D phase.RESPONSIBILITY:The post production support analysis is the responsibility ofthe MD during production.The MD assess and verifies for completeness of allsubtasks accomplished by the PA.APPLICABLE STANDARDS:Defense Acquisition Regulation Supplement (DARS) No. 6.LSA DOCUMENTATION:None.LSAR REPORTS:None.PRODUCTS:None.INPUTS AND SOURCE:None.10.6.3.15TASK 501 - SUPPORTABILITY TEST, EVALUATION, AND VERIFICATIONPURPOSE:To assess achievement of support parameters specified; identifyreasons for deviations from projections; and recommend changes to correctdeficiencies and improve system readiness.REQUIRED FOR:The formal Test and Evaluation (T&E) program.This task isused to develop a strategy for testing the support parameters of a systemwhich are input to the system T&E Master Plan (TEMP).Criteria areestablished to identify test resources, procedures and schedules required tomeet TEMP input objectives; and to analyze T&E results, develop correctiveaction, and update the support plan and LSAR.Post-deployment supportabilityassessment is obtained by analyzing the operational system maintenance andsupply data. WHEN REQUIRED:Subtask 501.2.1 (T&E Strategy) usually begins during CED. Chapter 1MIL-HDBK-13881-35Development of the System Support Package (SSP) component list (Subtask501.2.2), establishment of T&E program objectives and criteria (Subtask501.2.3), and updates/corrective actions (Subtask 501.2.4) are generallyapplicable during D&V and EMD.Subtasks 501.2.5 and 501.2.6, which involvepost deployment supportability assessment, only apply during EMD and P/D.

RESPONSIBILITY:The MD has primary responsibility for Task 501 in all applicable life cycle phases.However, supportability testing issues aredeveloped in coordination with the RA.The MD is responsible for technicaltest (TT) and for coordinating preparation of the TEMP.Test and EvaluationCommands for each of the services are responsible for user test (UT) andpreparation of that portion of the TEMP.The MD assess and verifies forcompleteness of all subtasks accomplished by the PA.APPLICABLE STANDARDS:MIL-STD-471.LSA DOCUMENTATION:All LSAR data tables as applicable.LSAR REPORTS:All reports as applicable.PRODUCTS:All products as applicable.INPUTS AND SOURCE:None.10.6.4LSA TAILORING PROCESS.The LSA effort must be tailored to meet theobjectives of the specific acquisition program in a cost effective manner. Tailoring is accomplished through the selective application of analysisrequirements at the subtask level. Some of the considerations which must beaddressed in the tailoring process include:type of program, amount of designfreedom, time and resource available, work already done, pastexperience/historical data, and acquisition strategy.Additional guidance onthese factors is provided in Appendix A of MIL-STD-1388-1A.10.6.5LSA AND THE MANAGERIAL FUNCTIONS.Actions required to MANAGE the LSAprocess include, to some degree, all of the functions of the manager, i.e.: PLANNING which identifies LSA objectives and schedules the actions required toachieve them. Planning is also decision making as it involves selectingamong alternatives.ORGANIZING which involves establishing an LSAorganization structure; identifying LSA tasks/subtasks; assigning tasks tospecific organizational units; delegating authority; and providing forcoordination of authority relationships both within the LSA program structureand with related program structures. STAFFING which involves manning andkeeping manned the technical and management positions identified in theorganization structure.DIRECTING which provides motivation, communication,and leadership.CONTROLLING which measures performance, corrects negativedeviations, and assures accomplishment of plans.10.6.5.1PLANNING AND CONTROLLING.Planning and controlling the LSA programis significantly aided by a time-event network analysis such as Program andEvaluation Review Technique (PERT).Management oriented summaries generatedby the LSAR Automatic Data Processing (ADP) system are useful in assessing theachievement of established objectives and identifying problem areas.Chapter 1MIL-HDBK-13881-3610.6.5.2COORDINATION.Good coordination solves problems as they occur;excellent coordination anticipates and prevents problems.Effectivecoordination of the LSA program with related program elements will identifymutual interests, maximize the benefits of mutually supporting tasks, andprevent duplication of effort.10.7ILS, LSA, LSAR, AND SYSTEM ENGINEERING.LSA is a design analysis toolwhich is employed as part of the ILS program.The LSA strategy whichsummarizes accomplished LSA tasks outputs and projects LSA task requirementsfor succeeding program phases is documented in the ILS Plan.LSA programmanagement and technical resources requirements, plan, procedures, schedules,and controls identified in the LSA Plan are incorporated in the overa