- •Preface
- •Section One. General
- •0 Introduction
- •1 Scope
- •2 Related Documents
- •3 Definitions
- •4 Abbreviations
- •5 LSA and LSAR
- •Section Two. Management
- •6 LSA and LSAR Management
- •Section Three. Application of LSA and LSAR to Projects
- •7 LSA Process
- •8 Tailoring
- •9 Data Transfer
- •Table 1 LSA Task Responsibilities
- •Table 2 LSA Subtasks Related to LSAR Data Production
- •Table 3 LSA Tasks/LSAR Table relationships - Feasibility (DI/NDI Only)
- •Table 4 LSA Tasks/LSAR Table relationships - Feasibility (COTS Only)
- •Table 5 LSA Tasks/LSAR Table relationships - Feasibility (GFE Only)
- •Table 6 LSA Tasks/LSAR Table relationships - Project Definition
- •Table 7 LSA Tasks/LSAR Table relationships - Full Scale Development
- •Table 8 LSA Tasks/LSAR Table relationships - Production (DI/NDI Only)
- •Table 9 LSA Tasks/LSAR Table relationships - Production (COTS Only)
- •Table 10 Example of Cross-Mapping Records Held in Data Table XG
- •Table 11 Examples of LCN Group Elements Allocated in Data Table XB
- •Table 12 Examples of UOC/ALC Allocation in Data Table XC
- •Table 13 Examples of LCN to System End Item UOC in Data Table XF
- •Table 14 Examples of Implied UOC
- •Figure 1 The complete feedback loop of Logistic Support Analysis
- •Figure 2 LSA Process during equipment design
- •Figure 3 Task breakdown for full development project
- •Figure 4 Task breakdown for first-of-class warship project
- •Figure 5 Task breakdown for commercial off-the-shelf project
- •Figure 6 Task breakdown for non-developmental project
- •Figure 7 Tailoring logic diagram
- •Figure 8 LSA programme planning, control and verification sub-task dependencies
- •Figure 9 LSA assessment and technical sub-task dependencies
- •Figure 10 Comparison of Functional and Physical Breakdowns
- •Figure 11 Functional LCN breakdown
- •Figure 12 Physical LCN breakdown
- •Figure 13 Functional LCN assignment - classical
- •Figure 14 Physical LCN assignment - classical
- •Figure 15 Physical LCN assignment - modified classical
- •Figure 16 Functional LCN - cross-mapping
- •Figure 17 Physical LCN - cross-mapping
- •Figure 18 ALC Assignment for single configuration equipment
- •Figure 19 ALC & UOC Allocation
- •Figure 20 System level Logistic Support Analysis interfaces
- •Figure 21 LSAR Data Table utilization by equipment breakdown
- •Figure 22 Feasibility study phase LSAR
DEF STAN 00-60 (PART 2)/3
Section Two. Management
6 LSA and LSAR Management
6.1 LSA Management. The management of LSA can be divided into three main areas:
(a)Determining and providing resources to enable the LSA process to take place.
(b)Integrating and conducting the LSA process.
(c)Implementing the results of the LSA process.
6.1.1 The LSA process, as defined by this Defence Standard, should form the basis for preparation, analysis and dissemination of all support and support related information for all products supplied, designed or produced by the contractor. For a specific equipment an Integrated Support Plan (ISP), as defined in Part 0 of this Defence Standard, and a Logistic Support Analysis Plan (LSA Task 102) are likely to be required. In these documents the contractor will be required to outline his organization, management and control arrangements for the project. This will include staff levels with assigned authority and responsibilities for the integration of the LSA activity with the equipment design and other support related activity covering the ILS elements specified in the tender requirements or the contract. It might be appropriate, depending on the phase and size of the project, for a contractor to:
(a)Appoint a manager to exercise control of the ILS functions and be accountable for the LSA programme, including deliverables specified in the contract.
(b)Assign a manager(s) to oversee each aspect of the LSA programme.
(c)Identify responsibilities for management and control of the use and dissemination of data and other analysis results using the LSA process.
(d)Integrate the LSA process with that of the design and associated manufacturing processes.
6.2The LSA tasks and subtasks are described in annex A to Part 1 of this Defence Standard.
6.3LSAR Management. The business rules, data tables and data elements (including data field lengths and data formats), described in Part 0 of this Defence Standard, must be adhered to when establishing and managing the LSAR database. However, as stated in Part 0 of this Defence Standard, the LSAR data may be delivered in other formats as specified in the contract.
6.4It is desirable that engineering disciplines and ILS functional elements are integrated to maximize the applicability of data developed by each and held in the LSAR. An example is the integration of LSA and Reliability and Maintainability (R&M) engineering processes.
These processes might be performed by separate (customer and contractor) organizations supported by separate automated systems. Benefits of integration include:
8
DEF STAN 00-60 (PART 2)/3
(a)Reduced duplication of effort.
(b)Improved consistency and quality of the data.
(c)Improved quality of the item or equipment under development.
(d)Improved influence on design for equipment supportability.
6.5The LSAR provides an organized, yet flexible database which consolidates the engineering and logistics data necessary to identify the detailed logistic support requirements of an equipment.
6.6The data contained in the LSAR is used to:
(a)Develop the maintenance requirements.
(b)Determine the impact of specific design features on logistic supportability.
(c)Determine how the proposed support system affects equipment R&M characteristics.
(d)Influence the design.
(e)Provide initial information for trade-off analyses, LCC studies, and logistic support modelling.
(f)Provide source data for the preparation of logistic products.
6.7A single LSAR may be created for each project; however, on large projects, sections of the LSAR may be developed separately for major sub-assemblies. If this is done, care must be taken to ensure that the LSA Control Number (LCN) structure is coherent across the entire project. See clause 7.7.2.1.
6.8The management and control of the relationship between the computing resources used to host the LSAR and other Information Technology (IT) systems must be considered. The need to import and export data to the LSAR or automated on-line access to the LSAR, must be planned using the Interchange Agreements described in Part 0 of this Defence Standard.
9