DEF STAN 00-60 (PART 2)/3

8.5.1Specific LSA subtask/LSAR table relationships are detailed in Tables 3 to 9. These tables do not include the general LSAR X-table requirements, which are necessary for the initial establishment of an LSAR database. All data/tasks identified in Tables 3 to 9 may be tailored to meet specific programme requirements and are provided for guidance purposes only.

8.5.2The product of the LSA/LSAR tailoring is the LSA subtask requirements element of the SOW and the LSAR Data Selection Sheet. These will lead to the creation of the total LSA data requirements. Factors that need to be taken into consideration whilst tailoring include:

(a)Phase of the project (eg PD, Production, etc).

(b)Type of project (eg NDI, COTS, etc.).

(c)Amount of design freedom involved.

(d)Estimate of return on investment.

(e)Time and resources available.

(f)Work already done.

(g)Past experience and availability of historical data.

(h)Reports required from the LSAR.

(i)In-Service management information requirements.

8.6The cost of ineffective tailoring is potentially high. Failure to identify data requirements adequately can be just as costly as the over purchase of data. Each functional and engineering speciality area must participate in the tailoring of the LSAR.

8.7Government Furnished Equipment (GFE). Where MOD provides GFE to a project, an LSAR may exist for that equipment. This might not be relevant for the specific application and may require further analysis to adapt it to the new use criteria. In cases where an LSAR does not exist, it will be necessary to undertake appropriate analysis.

9 Data Transfer

9.1 Options for the transfer of LSAR data are described in annex C.

24

25

DEF STAN 00-60 (PART 2)/3

26

27

DEF STAN 00-60 (PART 2)/3

Collation Page

28

DEF STAN 00-60 (PART 2)/3

ANNEX A

Guidance for Assignment of LSA Logistic Control Number (LCN) Alternate LCN Code (ALC) LCN Type and Usable on Code (UOC)

A.1 Purpose

This annex outlines the requirements for and use of End Item Acronym Code (EIAC), LCN, LCN Type and ALC, (collectively termed the LCN Group). It also provides guidance for the assignment of the LCN Group elements and explains the importance of the relationship between the constituent parts of the LCN Group and the UOC. It should be noted that the illustrations used throughout this annex relate to a hypothetical missile system. Different areas have been expanded within each figure to illustrate specific points related to the accompanying text.

A.2 Introduction

The breakdown of an equipment can be approached in two different ways; firstly with regard to how it works functionally, and secondly how it exists physically. These two approaches are illustrated in Figure 10. The LSAR can describe and document both methods. The relative positions of functions or items within each type of breakdown must be identified. This is achieved within the LSAR by using the LCN Group which, collectively, is a unique hierarchical identifier for an item or function against which additional information can be stored or retrieved. The assignment of LCN Group elements, along with any associated UOCs, must be approached carefully and logically in order to ensure that the LSAR contains the desired logistics data in a structure that will be of use throughout the life of the equipment.

A.3 The LCN Group

The LCN Group consists of four key elements. The following are definitions of the LCN Group elements and will provide an overview of their functions within an LSAR:

(a)EIAC (DED 096). The EIAC is an alpha-numeric code, consisting of up to 10 characters, which uniquely identifies the system or end item.

(b)LCN (DED 199). The LCN is an alpha-numeric code consisting of up to 18 characters which, when assigned with an associated LCN Type and ALC, identifies an item or function within the physical or functional breakdown of the system or end item.

(c)LCN Type (DED 203). LCN Type is a one position alpha code (‘P’ or ‘F’) indicating whether the LCN is part of a physical or functional LCN breakdown.

(d)ALC (DED 019). The ALC is a two position numeric code which indicates that an alternative item occupies the same position in the LCN breakdown and, therefore, the same position within the system, equipment or item, but has different logistic considerations.

The use and assignment of individual elements of the LCN Group is covered in greater detail later in this annex.

A-1

DEF STAN 00-60 (PART 2)/3

ANNEX A (CONTINUED)

Functional Breakdown

MISSILE

MISSILE

Figure 10 Comparison of Functional and Physical Breakdowns

A-2

DEF STAN 00-60 (PART 2)/3

ANNEX A (CONTINUED)

A.4 Usable On Code (UOC)

The UOC, (DED 501), is a three position alpha-numeric code which is not a constituent part of the LCN Group but is used in association with the LCN Group to indicate the configuration of the equipment or item.

A.5 Purpose of UOC and ALC

No two equipment procurement projects will be the same and could range from a project with complete design freedom through to the COTS type project. The LCN Group needs to be flexible enough to work across a wide variety of project types and to retain a common approach to its assignment. The principles for assigning the individual elements of the LCN Group therefore remain the same across all project types. However, the size and complexity of each equipment affects the way in which the LCN Group and associated UOCs are assigned. For example, a simple equipment with only one configuration may only require a single UOC with limited use of ALC, whereas a complex equipment with variants will undoubtedly require many UOCs and the comprehensive use of ALC.

During equipment development, the ALC is needed when alternative design items are being considered. As the equipment design stabilizes, the redundant design alternatives are removed from the LSAR database, reflecting the basic equipment configuration. Once an equipment enters production and the subsequent in-Service phases, engineering changes, modifications and changes in operational requirements may dictate the need for new configuration/models. When this occurs, the ALC and UOC are used to assist in recording these changes. It is important to ensure that the assignment of the ALC and UOC to alternative design/support concepts or multiple-configuration/models is carried out in an orderly and structured manner, as correctly allocating the ALC and UOC will greatly enhance the usability of the LSAR and its data.

The guidance contained in this annex enables the creation of a properly structured LSAR which can be used throughout the life of an equipment. All the topic areas outlined above are further amplified, with the aid of diagrams, in the following clauses.

A.6 Introduction to LCN

A.6.1 LCN Structure

The LCN Structure (DED 202) identifies the number of characters assigned to each indenture level of the LCN breakdown. Development of the LCN structure and its subsequent assignment down to the sub-system level should be accomplished prior to population of the first LSAR data tables. Extreme care should be exercised in developing the structure, so that the least number of characters is used for each indenture level. This may be accomplished by identifying the maximum number of items which will be assigned a unique LCN at each indenture level. If the maximum number of items in any branch of the LCN breakdown, at a given indenture level, is less than or equal to 36, then one alpha-numeric character will suffice. If the maximum number of items is greater than 36 but less than or equal to 1296,

A-3

DEF STAN 00-60 (PART 2)/3

ANNEX A (CONTINUED)

then two alpha-numeric characters will suffice. Further guidance may be found in clause A.7 of this annex, which explains the assignment of LCNs. The process of LCN assignment is inextricably linked to that of developing the LCN structure. The LCN structure used in the examples throughout this annex have been developed to highlight the difference between the functional and physical LCN structures. The LCN structures used throughout this annex are as follows;

A.6.2 Physical and Functional LCN

There are two different types of LCN that can be used within an LSAR; the Functional LCN and the Physical LCN. The two types are completely independent of one another and form two completely different LCN breakdowns as illustrated in Figures 11 and 12. To differentiate between functional and physical LCN, an LCN Type code is assigned to every LCN. This code indicates, with an ‘F’ or ‘P’, whether the LCN is functional or physical.

The functional LCN breakdown allows the early identification and documentation of the functional design within an LSAR. It is not always a requirement for a project to use a functional LCN breakdown within the LSAR. For example, simple projects with a limited data set or projects where the physical and functional breakdowns are identical may only require a single LCN breakdown; Note: additional guidance on LCN allocations for software is given in Part 3 of this Defence Standard. For the majority of projects the long term benefits of using both functional and physical LCN breakdowns outweigh any short term gains created by having the simplified LCN breakdown which results from using only one method. If both types of LCN breakdown are used within an LSAR then the functional and physical LCNs may need to be 'linked together' to provide the 'complete picture'. This process of linking the 2 LCN breakdowns is known as 'Cross-Mapping' and is achieved in the LSAR by using the Functional/Physical LCN Mapping Data Table (XG).

A.6.3 Functional LCN

Figure 11 shows a functional LCN breakdown of a simple missile. The functional LCN breakdown should be developed to the indenture level where a discreet physical item or design exists that will satisfy that system functional requirement entirely. This is depicted in Figure 11 by the four dotted boxes indicating that physical items have been identified that will completely fulfil the requirements of the functions represented by the dotted boxes. This

A-4

DEF STAN 00-60 (PART 2)/3

ANNEX A (CONTINUED)

A MISSILE

NOTE: The LCN Structure used in the Functional LCN Breakdown is 1, 1, 2, 1, 2. Clause A.6.1 provides a more detailed explanation of LCN Structure.

Figure 11 Functional LCN breakdown

A-5

DEF STAN 00-60 (PART 2)/3

ANNEX A (CONTINUED)

1 MISSILE