DEF STAN 00-60 (PART 2)/3

ANNEX A (CONTINUED)

to be documented in the same LSAR as the equipment rather than using a different LSAR specifically for the support/training equipment. It should be appreciated that using this approach may cause difficulties when transferring the LSAR from the introductory phase to in-Service use. For example, the Equipment Support Manager (ESM) for the support equipment may be different to that of the equipment that it will be used on. Therefore, the ESM for generic type support equipment will have difficulty in managing the equipment since the data will be contained in many different LSARs for the various equipment that it is used on, rather than in a specific support equipment LSAR. The supplier and customer should agree the most suitable LSAR for documenting the support/training equipment prior to LCN assignment.

A.7.5 Cross-Mapping - Detail Process

The purpose of cross-mapping is to link the physical items to their related functions. This process establishes the relationship between the functional breakdown and how the equipment will exist physically. The cross-mapping of the physical LCN to the functional LCN should, therefore, be carried out as late as is practicably possible whilst still meeting the needs of the customer in terms of data manipulation. A plan for the cross-mapping process should be developed which will identify all possible permutations for cross-mapping physical items to their respective functions. If possible, the cross-mapping process should be carried out on a copy of the LSAR to allow a trial of the cross-mapping process and to prove that the links are correct, before committing the process to the 'live' LSAR.

To demonstrate the Functional-to-Physical cross-mapping process a reproduction of the data table XG, complete with all data keys, for the missile system outlined in Figures 16 and 17 is shown in Table 10. This example does not show all the cross-mapping links that would be required for the missile system but does provide a representative sample of the cross-mapping process.

Table 10 Example of Cross-Mapping Records Held in Data Table XG

A-15

DEF STAN 00-60 (PART 2)/3

ANNEX A (CONTINUED)

It can be seen from Figure 16, Figure 17 and Table 10 that the cross-mapping process, for a given link, can occur across any indenture level of the LCN breakdown. For example, the sensor unit and sensor amp are cross-mapped between the third indenture level physically and the fifth indenture level functionally. There are three possible scenarios for establishing a cross-mapping link. They are as follows:

A.7.5.1 Direct One-to-One Linking. A one-to-one relationship is one where a single link exists between one physical and one functional item. An example of a direct one-to-one link within the missile system can be found with the sensor unit (LCN 1A01 in Figure 17) which has been identified as completely fulfilling the functional requirement for the detect function (LCN AB01A01 in Figure 16).

A.7.5.2 Representing Multiple Links. It may occasionally be necessary to create links between one function and the many physical items that fulfil that functional requirement; this is termed a one-to-many relationship. Conversely, a single physical item can sometimes fulfil several functional requirements; this is the many-to-one relationship. Both types of relationship are difficult to establish and should be approached with caution. One method is to introduce an additional 'dummy' cross-mapping indenture level purely for cross-mapping purposes, as explained below.

A.7.5.2.1 Linking Many Physical Items to a Single Function. Figure 16 shows the power function (LCN AB01C), with two 'dummy cross-mapping' functions (LCNs AB01C01 and AB01C02), indentured below it. The reason for these additional functional LCNs is to allow the forward battery (LCN 1B02C) and the rear battery (LCN 1D01C) on Figure 17, which make up the power system, to be cross-mapped to the power function in Figure 16. The inclusion of these 'dummy' LCNs allows a many physical to single function relationship to be cross-mapped as a one-to-one relationship (refer to Table 10). To use this method, all the physical candidates required to fulfil a function must be identified before the allocation of the dummy functional LCNs is made, as the number of physical items will dictate the number of LCN that will be required.

A.7.5.2.2 Linking Many Functions to a Single Physical Item. To satisfy the cross-mapping requirements of this type of relationship physical 'dummy cross-mapping' LCN will need to be allocated, on the physical LCN breakdown, at one indenture level below the item being crossmapped. This approach will allow a single physical item to be cross-mapped to the many functions that it can perform.

A.7.6 Additional Considerations Functional and Physical Cross-Mapping

When both a physical and functional LCN exist for the same item, the physical LCN structure takes precedence for data storage in an automated data processing system. By creating the physical to functional cross-mapping, any data documented under a functional LCN will be linked to a physical key. It is important to recognize that the two structures are completely independent, and that a ‘mixing’ of structures (part physical/part functional) for an equipment is not permitted within the physical structure.

A-16

DEF STAN 00-60 (PART 2)/3

ANNEX A (CONTINUED)

There should be no cross-mapping of a parent LCN above the point at which a related child LCN has already been cross-mapped as this would override the lower level cross-mapping links. For example LCN AB01A01 and AB01A02 (depicted in Figure 16), are cross-mapped to physical entities sensor unit and sensor amp respectively (depicted in Figure 17). Hence, sensor function (LCN AB01A), guidance electronics function (LCN AB01) and guidance function (LCN AB) should not be cross-mapped. Great care must be taken when crossmapping, as incorrectly cross-mapped LCN breakdowns will result in corrupt data.

A.8 Use of ALC and UOC

A.8.1 ALC

An LCN group uniquely identifies each part or assembly within the system or end item. If, however, there are alternative parts, alternative support concepts or alternative designs which have to be considered, there is a need to document these within the LSAR against the LCN for which they are an alternative. To differentiate between data for these alternatives the key data element ALC is used. This data element, recorded in data table XB, is used both in the documentation of alternatives within the LSAR database and as a selection criteria for the generation of reports. It consists of two numeric characters and is allowed values from 00 to 99.

A.8.2 Use of ALC to Record Alternatives

Within a single configuration equipment (ie where all items have the same UOC) the ALC alone is used to distinguish between alternatives. It will be used extensively during the design phase of an equipment to document design or support alternatives for trade-off analysis. At design freeze, redundant design alternatives are removed from the LSAR database, to reflect a basic equipment configuration, and the ALC 00 allocated to all aspects of the chosen design, including all items, functions and support concepts. ALC 00 is the default value and if, in report generation, no ALC is specified this default value will be assumed by the database. During the in-Service phase, ALC may be used within each system to document design changes (including modifications) and changes in support concepts.

A.8.3 ALC Allocation in a Single-Configuration System

Figure 18 shows the allocation of ALC within a single equipment configuration. The alternative design for the rocket motor (LCN 1D01B) is documented against an ALC of 01.

The fuel tank (LCN 1D01B1) also has ALC 01 allocated to it, although there is no 00 alternative, as it can only be used with the alternative rocket motor. This identifies it as part of the alternative rocket motor design and follows the convention that those parts of an alternative design, which are not part of the original design, should be allocated the same ALC. This applies even if the items in the alternative are not physically connected to each other. This is shown in Figure 18 by the allocation of ALC 02 to both the sensor amp (LCN 1A02)

A-17

Figure 18 ALC Assignment for single configuration equipment

DEF STAN 00-60 (PART 2)/3

ANNEX A (CONTINUED)

and the electronics unit (LCN 1B02A). Even though these items are not connected and are at different indenture levels, the same ALC 02 is allocated to both items as they must be used together. Although the alternative sensor amp and electronics unit are the first alternatives to those items, the ALC allocated to them is different to that allocated to the alternative rocket motor because the two changes are not connected. This preserves the convention that within an end item, system or subsystem, ALCs assigned to alternative items shall always be different for each alternate item unless those alternate items shall be used together. In that case, the ALC for those items shall be the same.

A.8.4 Use of UOC to Record Configurations

ALC and LCN combined can be used to document alternatives in simple equipment but to generate reports on more complex equipment there is a requirement to indicate within the database which configuration each item belongs to. This is achieved by using a combination of ALC and UOC. The UOC (DED 501) is a three character alpha-numeric code allocated, in data table XC, to each configuration model being considered. The keys to table XC are EIAC, LCN and ALC, so to differentiate between configuration models, which will have the same EIAC and LCN, a unique ALC must be allocated to each configuration in data table XB. Also in table XB, to allow an entry to be made in table XC, the item being assigned a UOC must be shown as a system or end item. To complete the establishment of a configuration model within the database, the components or systems/sub systems used within that configuration are then re-assembled within data table XF. This is done by plotting each component, system or subsystem in table XF to the LCN/ALC combination which have been allocated a UOC in table XC. This, in effect, relates that UOC to the items plotted in table XF. During report generation, which selects by a single UOC or multiple UOC, the combination of tables XB,XC and XF allows the database to assemble the data for each configuration.

A.8.5 ALC and UOC Allocation in a Multi-Configuration System

Figure 19 shows an example of the use of ALC and UOC in a multi-configuration equipment. The equipment shown has three configuration variants, Live Missile, Practice Missile, and Training Missile, all of which have ALC and UOC allocations as shown on Figure 19 and in the associated examples of data shown in tables 11, 12, 13 and 14. The physical LCN breakdown used in these examples follows the classical assignment method.

The baseline variant of the missile depicted in Figure 19, illustrates the breakdown of the live missile. The practice and training missile variants, also shown on Figure 19, detail the differences between these variants and the baseline variant as illustrated by the use of solid boxes. The dotted boxes shown on Figure 19 for the practice and training missile variants have only been included for clarity.

The baseline variant live missile (LCN 1) is given the default ALC value of 00. The baseline variant is allocated a UOC of AAA in table XC (as depicted in table 12). The component parts of the baseline variant are then assigned to their next higher assembly in table XF (as depicted in 13) until the complete hierarchical structure is established. This process is repeated for the remaining variants. None of the lower indentured components of the variants

A-19

DEF STAN 00-60 (PART 2)/3

ANNEX A (CONTINUED)

has been allocated a UOC in table XC but each of them has an implied UOC, linked through table XF. For example, in table 14 it can be seen that the forward battery pack (LCN 1B02C), which is used on all three configurations, has implied UOCs of AAA, BBB and CCC. During report generation the reports are selected against the allocated UOC in table XC. The database management system will then collect data from the components listed against that LCN/ALC combination in table XF. Allocation in this way can be repeated at any indenture level with ALCs assigned in table XB and subsequent UOC allocation in table XC.

To avoid having to re-enter data for common items table XF is used. For example, consider the missile body inert, (LCN 1C) which is part of the practice missile. The missile body inert is also used on the training missile. This comprises two components, the body casing (LCN 1C01), which is a common item to the base variant, and the ballast weight (LCN 1C03), which is unique to the missile body inert. Entries in table XF assign the missile body inert to both the practice missile (ALC 01) and the training missile (ALC 02) giving implied UOCs of BBB and CCC.

ALC in the complex system is not allocated at an end item level but is allocated within the breakdown at levels below the allocation of UOC. Defining systems at a lower level of indenture in this way allows an ALC range of 00 to 99 to be used at each system or subsystem level. Consider the electronics unit (LCN 1B02A). In the training variant (ALC 02) this assembly has two components shown with the same LCN 1B02A05. The second of these is a modification and requires an ALC allocation other than 00. As the next higher assembly is shown as a system, as identified by System End Item Identifier (DED 423), in table XB, and has a UOC allocated in table XC, this modification is counted as the first change within that system and can be allocated the ALC 01. A much greater range of changes can thus be documented within the database, which should allow the tracking of changes throughout the life of the equipment.

A-20