DEF STAN 00-60 (PART 2)/3

and development, the task analysis process will be conducted by the contractor to establish maintenance concepts and support resource requirements for that equipment. This process should include:

(a)Critical failure modes, identified by the FMECA, are analysed using RCM logic, to ensure equipment is designed to eliminate critical failure. Where this is not possible, preventive maintenance tasks are identified. The results of RCM are used, within both the Procurement and In-Service project phases, to optimize LCC whilst maintaining performance and availability requirements. The FMEA/FMECA and RCM lead to identification of corrective and preventive maintenance activities respectively, which enables the support resource requirements to be determined. The FMEA/FMECA/RCM standards to be used will be specified in the contract.

(b)The application of LORA to determine the level at which an item will be repaired or discarded. This will normally be based on economic factors unless there are overriding operational requirements.

8 Tailoring

8.1 Tailoring is an iterative process involving three concurrent activities:

(a)Identifying the project related ILS elements and the LSA tasks requirements to satisfy them for the current project phase.

(b)Selecting the data deliverable requirements.

(c)Selecting the LSA tasks which will provide the data requirements.

8.2 LSA Tailoring. Once the ILS elements have been established, the LSA effort must be tailored to meet the procurement and support objectives in a cost effective manner. This is accomplished through the selective application of analysis requirements at LSA subtask level. Factors which must be addressed in the tailoring process include those outlined in clause 8.5. The LSA tailoring logic is illustrated in the diagram shown at Figure 7, further guidance is provided at annex B and there are commercial software tools that are available that can also assist in tailoring. In addition, the degree of tailoring is influenced by the procurement type.

8.2.1Development Item (DI). This procurement type is relevant to equipment to be developed through a MOD development contract. It is defined as full development for a new item including all phases of the life cycle. There is the greatest amount of freedom for the LSA process to influence design.

8.2.2Non-Development Item (NDI). This procurement type requires LSA to be performed. Whilst there is little or no LSA influence on the design of the equipment there is scope to consider the logistic aspects of its installation. The equipment will have completed its research and design stages and will not be subject to a development cycle. NDI projects

18

DEF STAN 00-60 (PART 2)/3

require evaluation of existing data and support concepts to identify areas needing additional analysis and data generation.

8.2.3 Commercial Off The Shelf (COTS). The equipment may be procured as a commercial item, with minimal LSA influence on the design. The data to perform other aspects of LSA may not be available from commercial sources. If such information is required it may need to be calculated, predicted or measured on delivered equipments. This procurement strategy often applies to equipments that have established, commercial, support packages available, but they may need modifying to meet MOD requirements. Although the LSA and ILS process will probably not influence the design, the process may be used to:

(a)Evaluate existing data and support concepts to identify areas needing additional data analysis and generation.

(b)Select the contractor by comparison of the support costs within the through life cost activities.

8.2.4 Subtask Dependencies. Following LSA task tailoring, the dependencies and relationships between each subtask need to be considered, to ensure the correct creation and flow of data. The subtask dependencies are shown at Figures 8 and 9.

8.3This tailoring process will lead to the identification of the logistic information requirements, associated with each element of ILS, required to be held in the LSAR.

8.4LSAR Tailoring. The specific data element requirements may be determined by reference to the required LSA Reports. This enables determination of the analysis to be undertaken to obtain the data. The LSA tasks and the LSAR data requirements should be tailored concurrently as population of the LSAR is as a direct consequence of the LSA tasks performed. The LSA Reports/Relational Data Table Cross-Reference Matrix in Part 0 of this Defence Standard may be used to determine the data elements required to satisfy a LSA report. There may also be commercial software tools available to assist in the project tailoring. Further guidance is given in annex C.

8.5LSA/LSAR Tailoring Verification. The LSA/LSAR tailoring processes are repeated for each ILS element identified and need to ensure that LSA tasks have been requested that will provide the necessary data. Table 2 shows the LSA subtasks which provide data that may be used to populate the LSAR, for each phase of a project.

19

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

Table 2 LSA Subtasks Related to LSAR Data Production

0 = Data generated but not yet populated in the LSAR

ü= Data populated in the LSAR

-= Not directly applicable to LSAR population