
- •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
ANNEX A (CONTINUED)
Table 11 Examples of LCN Group Elements Allocated in Data Table XB
EIAC |
LCN |
ALC |
LCN TYPE |
SYSTEM EI IND |
MSL |
1 |
00 |
P |
E |
MSL |
1 |
01 |
P |
E |
MSL |
1 |
02 |
P |
E |
MSL |
1A |
00 |
P |
|
MSL |
1A |
02 |
P |
S |
MSL |
1A01 |
00 |
P |
|
MSL |
1A02 |
00 |
P |
|
MSL |
1B |
00 |
P |
|
MSL |
1B01 |
00 |
P |
|
MSL |
1B02 |
00 |
P |
|
MSL |
1B02 |
01 |
P |
S |
MSL |
1B02A |
00 |
P |
|
MSL |
1B02A |
02 |
P |
S |
MSL |
1B02C |
00 |
P |
|
MSL |
1B02D |
01 |
P |
|
MSL |
1B02A05 |
00 |
P |
|
MSL |
1B02A05 |
01 |
P |
|
MSL |
1C |
00 |
P |
|
MSL |
1C |
01 |
P |
S |
MSL |
1D |
00 |
P |
|
MSL |
1D |
02 |
P |
S |
MSL |
1D01 |
00 |
P |
|
MSL |
1D01A |
00 |
P |
|
MSL |
1D01B |
00 |
P |
|
MSL |
1D01C |
00 |
P |
|
MSL |
1D02 |
00 |
P |
|
Table 12 Examples of UOC/ALC Allocation in Data Table XC
EIAC |
LCN |
ALC |
LCN TYPE |
UOC |
PCCN |
MSL |
1 |
00 |
P |
AAA |
ZZZAAA |
MSL |
1 |
01 |
P |
BBB |
ZZZAAA |
MSL |
1 |
02 |
P |
CCC |
ZZZAAA |
MSL |
1A |
02 |
P |
CCA |
ZZZAAA |
MSL |
1B02 |
01 |
P |
BBC |
ZZZAAA |
MSL |
1B02A |
02 |
P |
CCE |
ZZZAAA |
MSL |
1C |
01 |
P |
BBA |
ZZZAAA |
MSL |
1D |
02 |
P |
CCD |
ZZZAAA |
A-22

DEF STAN 00-60 (PART 2)/3
ANNEX A (CONTINUED)
Table 13 Examples of LCN to System End Item UOC in Data Table XF
EIAC |
UOC ITEM |
UOC ITEM |
UOC ITEM |
UOC SYST |
UOC SYST |
UOC SYST |
|
LCN |
ALC |
LCN TYPE |
LCN |
ALC |
LCN TYPE |
MSL |
1A |
00 |
P |
1 |
00 |
P |
MSL |
1B |
00 |
P |
1 |
00 |
P |
MSL |
1C |
00 |
P |
1 |
00 |
P |
MSL |
1D |
00 |
P |
1 |
00 |
P |
|
|
Live Missile - Baseline Variant |
|
|
||
MSL |
1A |
00 |
P |
1 |
01 |
P |
MSL |
1B |
00 |
P |
1 |
01 |
P |
MSL |
1C |
01 |
P |
1 |
01 |
P |
MSL |
1D |
00 |
P |
1 |
01 |
P |
MSL |
1B02 |
01 |
P |
1 |
01 |
P |
MSL |
1B02A |
00 |
P |
1B02 |
01 |
P |
MSL |
1B02C |
00 |
P |
1B02 |
01 |
P |
MSL |
1B02D |
01 |
P |
1B02 |
01 |
P |
|
|
Practice Missile - First Variant |
|
|
||
MSL |
1A |
02 |
P |
1 |
02 |
P |
MSL |
1B |
00 |
P |
1 |
02 |
P |
MSL |
1C |
01 |
P |
1 |
02 |
P |
MSL |
1D |
02 |
P |
1 |
02 |
P |
MSL |
1B02A |
02 |
P |
1 |
02 |
P |
MSL |
1B02A05 |
00 |
P |
1B02A |
02 |
P |
MSL |
1B02A05 |
01 |
P |
1B02A |
02 |
P |
Training Missile - Second Variant
Table 14 Examples of Implied UOC
UOC ITEM |
UOC ITEM |
ITEM NAME |
IMPLIED |
LCN |
ALC |
|
UOC |
1A |
00 |
NOSE CONE |
AAA/BBB |
1A |
02 |
NOSE CONE DUMMY |
CCC |
1B |
00 |
GUIDANCE HOUSING |
AAA/BBB/CCC |
1B02 |
01 |
GUIDANCE ELECTRONICS (ALT) |
BBB |
1B02A |
00 |
ELECTRONICS UNIT |
AAA/BBB |
1B02A |
02 |
ELECTRONICS UNIT (ALT) |
CCC |
1B02C |
00 |
FORWARD BATTERY PACK |
AAA/BBB/CCC |
1B02D |
01 |
TELEMETRY UNIT |
BBB |
1B02A05 |
00 |
GROUND TEST MODULE |
CCC |
1B02A05 |
01 |
GROUND TEST MODULE (MOD) |
CCC |
1C |
00 |
MISSILE BODY |
AAA |
1C |
01 |
MISSILE BODY INERT |
BBB/CCC |
1D |
00 |
TAIL UNIT |
AAA/BBB |
1D |
02 |
TAIL UNIT PRACTICE |
CCC |
A-23
DEF STAN 00-60 (PART 2)/3
ANNEX A (CONCLUDED)
Collation Page
A-24
DEF STAN 00-60 (PART 2)/3
ANNEX B
Application Guidance for Implementation of LSA Programme Requirements
B.1 Introduction
B.1.1 General
This annex is heavily based on appendix A to MIL-STD-1388-1A. It has been included here to allow this Defence Standard to be a stand-alone document. However, it is intended to revise it for ease of use within the UK Logistics Business Context. The revised annex will be published as an amendment to this Defence Standard.
This annex provides rationale and guidance for the selection and tailoring of LSA tasks in Part 1 of this Defence Standard. This annex is to be used to tailor LSA requirements in the most cost effective manner to meet project objectives. However, it is not to be referenced or implemented in contractual documents. No requirements are contained in this annex. The users of this annex can include any customer who wishes to impose LSA tasks upon a supplier.
B.1.2 How to Use this Annex. This annex provides guidance on structuring LSA programmes (see clause B.2) and on applying the individual task and sub task requirements (see clause B.4). The user should first review the major considerations affecting the development of the LSA programme contained in clause B.2 and then refer to the appropriate parts of clause B.4 based on the tasks and sub tasks selected.
B.2 General Application Guidance for LSA Programmes
B.2.1 LSA Process. As described in Section 3 of this Part of this Defence Standard, LSA is an iterative and multi-disciplinary activity with many interfaces. The LSA process can be divided into two general parts:
(a)Analysis of supportability.
(b)Assessment and verification of supportability.
The iterative nature of this process and the input-output relationship of the interfaces change with the procurement phases as described below.
B.2.2 Analysis of Supportability. This portion of the LSA process commences at the equipment level to affect design and operational concepts; identify overall logistic support resource requirements of alternative concepts; and to relate design, operational, and supportability characteristics to equipment readiness objectives and goals. The equipment level analysis is characterized by use studies, comparative analysis and driver identification, identification of technological opportunities, and trade-offs between support, operational, and design concepts and between alternative support concepts such as in-house support versus contractor support, built-in versus external test capability, and varying numbers of maintenance levels. Once equipment level trade-offs are made, the analysis shifts to lower
B-1
DEF STAN 00-60 (PART 2)/3
ANNEX B (CONTINUED)
equipment indentures and toward support equipment optimization within the framework established by the equipment level analysis. This analysis defines the logistic support resource requirements of the equipment through an integrated analysis of all operator and maintenance functions and tasks to determine task frequencies, task times, personnel and skill requirements supply support requirements, etc, to include all elements of ILS. Optimization is achieved at this level through allocation of functions and tasks to specific maintenance levels, LORA, RCM analyses, and formulating design recommendations to optimize maintenance times and logistic support resource requirements. Data from this level of the LSA is used as direct input into the development of data products associated with each ILS element such as provisioning lists, personnel and training requirements, and electronic documentation. This ensures compatibility between ILS element documents and permits common use of data which apply to more than one logistic element.
B.2.3 Assessment and Verification. This part of the LSA process is conducted throughout the equipment's life cycle to demonstrate, within stated confidence levels, the validity of the analysis and products developed from the analysis, and to adjust the analysis results and products as required. This part of the process starts with early planning for verification of support concepts and continues through development, procurement, deployment, and operations to include assessment and verification of post deployment support.
B.2.4 Interfaces. Coordination of LSA interfaces is a major management challenge which requires final resolution at the working level in some cases. The LSA sub tasks in annex A to Part 1 of this Defence Standard are structured to facilitate assignment of applicable sub tasks to the community most directly involved without loss of overall task integrity. For a specific procurement programme, LSA interfaces will be described in the LSAP (Task 102) which should be reviewed to ensure that input-output relationships, responsibilities, and timing of activities are properly addressed to prevent overlap and duplication. The following general guidance may be useful in addressing the interface problem.
B.2.5 Inputs and Outputs for System Level LSA. Some of the system level LSA involves system analysis/engineering at the hardware-operating-support trade level (Subtask 303.2.3). Equipment system level LSA is an input to and subset of these trade-offs and is in turn a collection, synthesis, and system analysis of inputs from various specialized areas. Figure 20 shows some of these major relationships in input-output form. The outputs from the system level LSA impact the interfacing activities in that they constitute boundary conditions or goals for specialized engineering programmes and ILS element concepts and plans.
B.2.6 Refinement and Extension of the System Level LSA. As development progresses, the LSA is iterated and extended to lower indenture levels with the input-output concept described above still functioning. Boundary conditions, constraints, and objectives are refined and expanded based on inputs from specialized engineering and ILS element areas. Additionally, the support system is optimized within the boundaries and objectives established. Specific sub task trade-offs within engineering specialities and ILS elements are conducted to provide specific boundaries for follow-on analysis. These would include the Built-In-Test (BIT) versus external test trade-offs (Subtask 303.2.8) and training trade-offs (Subtask 303.2.6).
B-2