DEF_STAN_00_60_Part_0_i5

Ministry of Defence Defence Standard 00-60 Part 0 Issue 5 Publication Date 24 May 2002

Integrated Logistic Support

Part 0: Application of Integrated

Logistic Support (ILS)

This Defence Standard supersedes Def Stan 00-60 (Part 0)/Issue 4

dated 18 August 2000

AMENDMENTS ISSUED SINCE PUBLICATION

REVISION NOTE This part of Def Stan 00-60 is raised to Issue 5 to update its content. The current issue status of each part of this Defence Standard can be found by contacting the Defence Standards Help Desk, see back cover for details. Details of the changes in all Parts can be obtained by contacting the ILS Help Desk by phone/fax +44(0)1225 467251, by e-mail to: [email protected] or via the AMS web site. HISTORICAL RECORD May 96 - Initial Issue. Mar 98 - Up-Issue. Jan 99 - Up-Issue. Aug 00 - Up-Issue. May 02 – Up-Issue. ARRANGEMENTS OF DEF STAN 00-60 The proposed arrangement of the complete series of Defence Standards comprising Def Stan 00-60 is shown below.

Part 0 - Application of Integrated Logistic Support (ILS)

- Defines Requirements for the implementation of ILS

Part 1 - Logistic Support Analysis (LSA) and Logistic Support Analysis Record (LSAR)

- Defines the MOD requirements for implementing Logistic Support Analysis (LSA) and the LSA Record (LSAR)

Part 2 - Guide to the Application of LSA and LSAR

- Provides supplementary guidance on the MOD application of Logistic Support Analysis (LSA) and the LSA Record (LSAR)

Part 3 - Guidance for Application of Software Support

- Defines the MOD LSA for Software requirements

Part 10 - Electronic Documentation - Defines the MOD Electronic Documentation requirements.

Part 20 - Application of Integrated Supply Support Procedures

- Defines the MOD requirements for implementing Supply Support within ILS.

Part 21 - Procedures for Initial Provisioning - Defines the MOD requirements for implementing Initial Provisioning

Part 22 - Procedures for Codification - Defines the MOD requirements for implementing Codification

Part 23 - Procedures for Procurement Planning

- Defines the MOD requirements for implementing Procurement Planning

Part 24 - Procedures for Order Administration - Defines the MOD requirements for implementing Order Administration

Part 25 - Procedures for Invoicing - Defines the MOD requirements for implementing Invoicing

Part 26 - Procedures for Repair Administration

- Defines the MOD requirements for implementing Repair Administration

DEF STAN 00-60 (PART 0)/5

1

INTEGRATED LOGISTIC SUPPORT

PART 0: MOD APPLICATION OF INTEGRATED LOGISTIC SUPPORT (ILS)

PREFACE a. This Part of the Defence Standard defines the Ministry of Defence (MOD) requirement for

the application of Integrated Logistic Support (ILS) principles in the through life management of defence equipment.

b. This Standard has been agreed by the authorities concerned with its use and is intended to be

used in all future designs, contracts, orders etc and by amendment to those already in existence. If any difficulty arises which prevents application of the Defence Standard, the Defence Standard 00-60 Help Desk shall be informed so that a remedy may be sought.

c. Any enquiries regarding this Standard in relation to an Invitation To Tender (ITT) or a

contract in which it is incorporated are to be addressed to the responsible technical or supervising authority named in the ITT or contract.

d. This Standard has been devised for use of the Crown and its contractors in the execution

of contracts for the Crown. The Crown hereby excludes all liability (other than liability for death or personal injury) whatsoever and howsoever arising (including, but without limitation, negligence on the part of the Crown, its servants or agents) for any loss or damage however caused where this Defence Standard is used for any other purpose.

This Defence Standard supersedes Def Stan 00-60 (Part 0)/Issue 4

dated 18 August 2000


2

CONTENTS Description PAGE Preface 1 SECTION ONE. GENERAL 0 Introduction 6 1 Scope 6 2 Related Documents 6 3 Definitions 8 4 Policy 8 SECTION TWO. THE PURPOSE AND SCOPE OF DEF STAN 00-60 5 Purpose 11 6 Scope of Def Stan 00-60 12 SECTION THREE. DEFENCE EQUIPMENT ACQUISITION AND MATERIEL SUPPORT (DEAMS) 7 Business Overview 13 8 Contracting Environment 20 9 Programme and Timing 23 10 Process Integration and Data Management 23 SECTION FOUR. ADDITIONAL ILS ELEMENTS AND THEIR INTERFACES WITH DEF STAN 00-60 11 Introduction 24 12 ILS Principal Elements 24 13 Additional ILS Elements 26 SECTION FIVE. DATA MANAGEMENT 14 Introduction 28 15 Data Dictionary 28 16 LSAR Relational Tables Business Rules and Reports 28 17 SGML 28 18 EDI 29 SECTION SIX. MANAGEMENT OF DEFENCE STANDARD 00-60 MAINTENANCE 19 Introduction 30 20 Change Procedure 30 21 Defence Standard 00-60 Help Desk 30


3

CONTENTS (Contd) PAGE Figure 1 Importance of ILS Within Defence Equipment Acquisition and Materiel Support 15 Figure 2 ILS Process Diagram 19 Figure 3 Defence Standard 00-60 Change Procedure 31 Figure 4 Not Yet Allocated Figure 5 Not Yet Allocated Figure 6 X Table Relationships C-14 Figure 7 A Table Relationships C-21 Figure 8 B Table Relationships C-28 Figure 9 C Table Relationships C-43 Figure 10 E Table Relationships C-58 Figure 11 U Table Relationships C-69 Figure 12 F Table Relationships C-78 Figure 13 G Table Relationships C-84 Figure 14 H Table Relationships C-89 Figure 15 J Table Relationships C-110 Figure 16 Z Table Relationships C-119 Figure 17 LSA Reports/Relational Data Table Cross- Reference Matrix C/B-3 Figure 18 LSA Report 001 Example Illustration C/C-3 Figure 19 LSA Report 003 Example Illustration C/C-4 Figure 20 LSA Report 004 Example Illustration C/C-5 Figure 21 LSA Report 005 Example Illustration C/C-9 Figure 22 LSA Report 006 Example Illustration C/C-10 Figure 23 LSA Report 007 Example Illustration C/C-11 Figure 24 LSA Report 008 Example Illustration C/C-12 Figure 25 LSA Report 009 Example Illustration C/C-13 Figure 26 LSA Report 010 Example Illustration C/C-14 Figure 27 LSA Report 011 Example Illustration C/C-15 Figure 28 LSA Report 012 Example Illustration C/C-16 Figure 29 LSA Report 013 Example Illustration C/C-18 Figure 30 LSA Report 014 Example Illustration C/C-19 Figure 31 LSA Report 016 Example Illustration C/C-20 Figure 32 LSA Report 018 Example Illustration C/C-23 Figure 33 LSA Report 019 Example Illustration C/C-24 Figure 34 LSA Report 023 Example Illustration C/C-25 Figure 35 LSA Report 024 Example Illustration C/C-30 Figure 36 LSA Report 025 not used Figure 37 LSA Report 026 Example Illustration C/C-33 Figure 38 LSA Report 027 Example Illustration C/C-34 Figure 39 LSA Report 030 Example Illustration C/C-35 Figure 40 LSA Report 033 Example Illustration C/C-47 Figure 41 LSA Report 036 Example Illustration C/C-48


4

CONTENTS (Contd) PAGE Figure 42 LSA Report 037 Example Illustration C/C-53 Figure 43 LSA Report 039 Example Illustration C/C-54 Figure 44 LSA Report 040 Example Illustration C/C-55 Figure 45 LSA Report 046 Example Illustration C/C-60 Figure 46 LSA Report 050 Example Illustration C/C-61 Figure 47 LSA Report 056 Example Illustration C/C-64 Figure 48 LSA Report 058 Example Illustration C/C-69 Figure 49 LSA Report 065 Example Illustration C/C-71 Figure 50 LSA Report 070 Example Illustration C/C-72 Figure 51 LSA Report 071 Example Illustration C/C-84 Figure 52 LSA Report 072 Example Illustration C/C-85 Figure 53 LSA Report 074 Example Illustration C/C-87 Figure 54 LSA Report 075 Example Illustration C/C-89 Figure 55 LSA Report 076 Example Illustration C/C-91 Figure 56 LSA Report 077 Example Illustration C/C-93 Figure 57 LSA Report 078 Example Illustration C/C-96 Figure 58 LSA Report 080 Example Illustration C/C-97 Figure 59 LSA Report 085 Example Illustration C/C-98 Figure 60 LSA Report 126 Example Illustration C/C-101 Figure 61 LSA Report 151 Example Illustration C/C-102 Figure 62 LSA Report 152 Example Illustration C/C-103 Figure 63 LSA Report 154 Example Illustration C/C-104 Figure 64 LSA Report 155 Example Illustration C/C-105 Figure 65 LSA Report 602 Example Illustration C/C-108 Figure 66 LSA Report 604 Example Illustration C/C-113 Figure 67 LSA Report 606 Example Illustration C/C-116 Figure 68 LSA Report 608 Example Illustration C/C-118 Figure 69 LSA Report 610 Example Illustration C/C-119 Figure 70 LSA Report 612 Example Illustration C/C-120 Figure 71 LSA Report 614 Example Illustration C/C-121 Figure 72 LSA Report 624 Example Illustration C/C-122 Figure 73 LSA Report 626 Example Illustration C/C-125 Figure 74 LSA Report 628 Example Illustration C/C-126 Figure 75 LSA Report 630 not used Figure 76 LSA Report 632 not used Figure 77 LSA Report 634 Example Illustration C/C-129 Figure 78 LSA Report 636 Example Illustration C/C-131 Figure 79 LSA Report 648 Example Illustration C/C-132 Figure 80 LSA Report 650 Example Illustration C/C-135 Figure 81 LSA Report 652 Example Illustration C/C-136 Figure 82 LSA Report 654 Example Illustration C/C-137 Figure 83 LSA Report 656 not used Figure 84 LSA Report 658 not used


5

CONTENTS (Contd) PAGE Figure 85 LSA Report 660 Example Illustration C/C-139 Figure 86 LSA Report 662 Example Illustration C/C-140 Figure 87 LSA Report 664 Example Illustration C/C-141 Figure 88 LSA Report 668 not used Figure 89 LSA Report 672 Example Illustration C/C-142 Figure 90 LSA Report 674 Example Illustration C/C-143 Figure 91 LSA Report 676 Example Illustration C/C-146 Annex A Glossary of Terms A-1 Annex B MOD Data Selection Sheet & CDRL B-1 Annex C Data Dictionary and Related Technical Information C-1 Introduction C-5 Logistic Support Analysis Record Relational Tables C-7 Appendix A - LSAR Reports Summary C/A-1 Appendix B - LSAR Reports/Relational Data Table Cross Reference Matrix C/B-1 Appendix C - Example LSAR Output Report Illustrations C/C-1 Appendix D - Index of Data Element Titles C/D-1 Appendix E - Listing of Data Element Codes C/E-1 Appendix F - Data Element Dictionary C/F-1 Appendix G - Alphabetical Listing of Data Element Titles C/G-1 Appendix H - Listing of Document References C/H-1 Annex D DID D-1 Annex E Defence Standard 00-60 Help Desk E-1


6

PART 0: APPLICATION OF INTEGRATED LOGISTIC SUPPORT (ILS) SECTION ONE. GENERAL 0 INTRODUCTION 0.1 The cost of in-Service support of defence equipment is generally equal to or more than the cost of its procurement. This cost is therefore a significant factor in procurement decisions and hence needs to be managed in a disciplined way. Integrated Logistic Support (ILS) is the accepted discipline for managing that cost, for causing support considerations to influence the design, including maintainability or selection of equipment and for delivering and monitoring a consistent support environment for the fielded equipment. The reliability and maintainability of equipment are two of the key drivers of its support costs. 0.2 There are many components of ILS and this Defence Standard will evolve to encompass them all in a structured and integrated way. The subject has several individual disciplines, or elements, which have developed over time, many of which are supported by standards and specifications which are already in general use. These standards need to be profiled to allow them to be interpreted consistently and to be usable in the Ministry of Defence (MOD) environment. 1 SCOPE 1.1 This Part of the Defence Standard describes the overall context of ILS in the MOD and states the way in which ILS shall be applied in MOD contracts in the procurement and in-Service support of defence equipment and materiel. It presents the background and the inter-relationships between the component Parts, putting the ‘business’ of ILS in context and describing the electronic environment in which this business shall be conducted. 1.2 This and other Parts of this Defence Standard provide a consistent profile for the application of specific existing standards used in the application of ILS. 2 RELATED DOCUMENTS 2.1 The following documents and publications are referred to in this Defence Standard: ISO 7372 UN Trade Data Elements Directory ISO 8879 Information Processing Text and Office systems SGML BS-EN-ISO 9001 Quality Systems - Model for Quality Assurance in Design,

Development, Production, Installation and Servicing 10007 Guidelines for Configuration Management ISO 9735 Electronic Data Interchange For Administration,

Commerce & Transportation (EDIFACT) Application Level Syntax Rules

ISO 10179 Document Style Semantics & Specification Language ISO 10744 Hytime AECMA International Specification for Technical Publications Utilising a


7

Specification 1000D Common Source Database AECMA Specification 2000M

International Specification for Materiel Management Integrated Data Processing for Military Equipment

Def Stan 00-40 Reliability and Maintainability Def Stan 00-41 MOD Practices and Procedures for Reliability and Maintainability Def Stan 05-57 Configuration Management Policy and Procedures for Defence

Materiel Def Stan 81-41 Packaging of Defence Materiel MIL-STD-974 Contractor Integrated Technical Information Service (CITIS) MIL-STD-1840 Automated Interchange of Technical Information MIL-Q-87270 Quality Assurance Program Interactive Electronic Technical Manuals

and Associated Technical Information Requirements MIL-M-87268 Manuals Interactive Electronic Technical General Content Style

Format and User Interaction Requirements MIL-D-82769 Data Base Revisable: Interactive Electronic Technical Manuals for the

Support Of MIL HBK 59B - DoD CALS Implementation Guide (Currently in Draft)

Prompt Payment Booklet

MOD Prompt Payment Booklet - A Guide for Contractors

99-M1 United Kingdom Manual for Codification of Materiel A COD P-1 NATO Manual on Codification A COD P-2 NATO Supply Classification Handbook A COD P-3 NATO Item Name Directory 2.2 Reference in this Part of this Defence Standard to any related document means that in any ITT or contract, the edition and all amendments shall be stated in the contract. 2.3 A list of sources to obtain copies of related documents is shown below: DOCUMENT SOURCE

British Standards (BS, BS EN and ISO)

BSI Customer Services BSI 389 Chiswick High Road LONDON W4 4AL

AECMA Standards AECMA European Association of Aerospace Ind Gulledelle 94 B-12OO - BRUSSELS BELGIUM

Defence Standards Directorate of Standardization Kentigern House 65 Brown Street GLASGOW G2 8EX


8

DOCUMENT SOURCE

US Military Standards BSI Customer Services BSI 389 Chiswick High Road LONDON W4 4AL

Prompt Payment Booklet DBA Mersey House Drury Lane Liverpool L2 7PX

ACODS UK NCB Kentigern House 65 Brown Street GLASGOW G2 8EX

2.4 This and other Parts of this Defence Standard specifically provide application profiles describing the way in which other documents are to be used. Where there is any conflict between statements made in these documents, then this Defence Standard shall take precedence. 3 DEFINITIONS 3.1 Glossary. A glossary of definitions appropriate to this Defence Standard is included at annex A. 3.2 Abbreviations. A glossary of abbreviations appropriate to this Defence Standard is included at annex A. 4 POLICY It is MOD policy to procure equipment that meets the required performance to time and cost and which is fully supportable at the optimum Life-Cycle Cost (LCC).


9

4.1 Application of ILS. It is MOD policy that the discipline of ILS will be applied to all future equipment procurement in accordance with this Defence Standard. This includes technology demonstrator programmes (TDP), major upgrades, software projects, collaborative projects, non-development and off-the-shelf procurement. ILS will be applied to ensure that equipment is designed to be supportable, that the necessary support infrastructure is put in place and that LCC is optimized. In those categories where design decisions cannot be affected, then ILS will still be required to influence the selection of equipment already developed, on the grounds of supportability and optimum LCC. 4.1.1 CADMID Acquisition Cycle The CADMID Acquisition Cycle is a development of the Downey procurement cycle. The objective of this acquisition cycle is to assist with the reduction of risk during the early programme phases so that, at Main Gate, there is a high level of confidence that project targets for time, whole-life cost and performance will be achieved. The basic content of each stage is described in the glossary of definitions at annex A. 4.1.2 Reliability and Maintainability (R&M). The R&M activities in a programme have a highly significant influence on the design of an equipment for supportability. While ILS and R&M are distinct disciplines, they must be closely co-ordinated. The overall Project Management Plan shall recognise the working relationship between ILS and R&M activities and ensure that the outputs from the R&M activities, required as inputs to ILS, are identified and scheduled to be available in time to allow the support considerations to influence the design and trade-off analysis. 4.1.3 In-Service. The LCC will continue to be monitored and compared with anticipated performance. In-Service decisions will also be made on a LCC basis and any modifications to equipment or its support will employ the discipline of ILS. 4.2 Sponsor. The MOD’s Chief of Defence Logistics (CDL) is the sponsor for MOD ILS policy and hence, via AD/ILS for this Defence Standard. 4.3 Standardization. It is MOD policy to standardize the application of ILS. This Defence Standard is a profile of existing, internationally recognized standards which are brought together for consistent use. This Defence Standard profiles standards and specifications for Logistic Support Analysis (LSA), Logistic Support Analysis Record (LSAR), Integrated Supply Support Procedure (ISSP) and Electronic Documentation creation and delivery. The baseline standards and specifications are:


10

a. MIL-STD-1388 1A (Notice 4) and MIL-STD-1388-2B (Notice 1). The

appropriate content of these standards has been reflected in this Defence Standard, as they are no longer maintained by the US DoD.

b. AECMA Specification 2000M (S2000M). c. AECMA Specification 1000D (S1000D).

These are supported by standards for electronic interchange of information to handle the large quantities of data involved. 4.3.1 International Standardization. Development of this Defence Standard commenced before NATO defined the required path for the development of an ISO standard for Acquisition Logistics. The above standards are proposed to be harmonized for international and non-military as well as military use. Moreover, it is MOD policy to support the internationalization of these standards. Consequently this Defence Standard will evolve to become a profile of the proposed International Standards. The development programme can be expected to take many years, however this does not prevent this Defence Standard from being issued now. There are direct benefits as well as being an influence in itself for wider standardization. It is only through use of this Defence Standard that it will develop. 4.3.2 Data Dictionary. The Def Stan 00-60 Data Dictionary is susceptible to change as a result of national and international development.


11

SECTION TWO. THE PURPOSE AND SCOPE OF DEF STAN 00-60 5 PURPOSE The Purpose of Def Stan 00-60 is to prescribe, for contractual use, the application of ILS to defence equipment. It provides the disciplines for ensuring that supportability and cost factors are identified and considered from concept and throughout the life of an equipment, with the aim of optimizing the LCC. Within these processes, the R&M design data will assist in influencing the cost of ownership through life. Thus the cost of ownership of defence equipment is driven down by: 5.1 Causing support considerations to influence equipment concept and design, in line with agreed R&M equipment performance characteristics. 5.2 Identifying the necessary support required to field the equipment. 5.3 Describing an efficient, integrated process for procuring and delivering supportable equipment, the support infrastructure and standardized support data. 5.4 Making the support data accessible for in-Service monitoring of equipment performance, allowing informed management decisions. 5.5 Forming a standard (business and data) interface between MOD and industry and between MOD departments, as well as facilitating a standard interface between industry partners, which aims to be both national and international in application. 5.6 Improving interoperability of defence equipment between Services and internationally between allies. This includes rationalizing differences in current practice, particularly between the Sea, Land and Air Systems. 5.7 Application and Tailoring. This Defence Standard shall not be used indiscriminately. It shall be tailored, as described in this Defence Standard, according to its particular application. 5.8 Contractual Context. This Defence Standard is intended to be called up in MOD contracts for new procurements, in-Service support management and post-design activity. It may also be used between industrial partners. To this end, this Defence Standard contains prescriptive requirements. It also contains ‘without prejudice’ advice and background to provide the best possible information for a clearly understood contract. The contracting environment is described in more detail in Section 3.


12

5.9 Integrated Processes and Data. ILS contains many inter-related elements within the business of defence equipment management. The elements include specific processes and have associated data to support those processes. This Defence Standard integrates the key processes and their data in a consistent way. 5.10 Continuous Acquisition and Life-Cycle Support (CALS). It follows that this Defence Standard is a fundamental element in the MOD approach to CALS. In the MOD, the implementation of CALS is being conducted within the wider initiative of Computer Integration of Requirements, Procurement, Logistics and Support (CIRPLS). 6 SCOPE OF DEF STAN 00-60 This Defence Standard is presented in Parts as described on the inside front cover. This Part describes the overall context of ILS and integrates the remaining Parts. Subsequent Parts of this Defence Standard describe the individual processes and their data and information management in detail covering the LSA, LSAR, ISSP and Electronic Documentation.


13

SECTION THREE. DEFENCE EQUIPMENT ACQUISITION AND MATERIEL SUPPORT (DEAMS) 7 BUSINESS OVERVIEW Clause 7.1 provides background to the business implications of MOD’s implementation of ILS. Subsequent paragraphs contain prescriptive requirements for the application of ILS. The business overview describes firstly the concept of DEAMS and then develops the importance and role of ILS throughout an equipment life cycle. The detailed components of ILS are then assembled and the specific coverage of this Defence Standard is described. 7.1 DEAMS. The conceptual DEAMS business process aims to provide and sustain equipment performance, and its availability, reliability and maintainability, at optimum LCC. Achievement of this, requires the equipment’s entire life-cycle to be managed. The ILS process within DEAMS is described in Figure 1 and is amplified below. 7.1.1 Once a military need has been identified and equipment concepts to satisfy that requirement are being determined, the activity of ILS, and in particular LSA, commences. This will ensure that informed decisions are made which take into account supportability and LCC factors when equipment options are being considered. 7.1.2 As the equipment concept is refined and moves through assessment and demonstration, LSA is applied in more detail. This both influences the equipment design and sustains an ongoing LCC model. As the design is refined, so are the support requirements and LCC estimates. 7.1.3 ILS shall be implemented concurrently with equipment concept and design activity. As shown in Figures 1 and 2, the LSA activity shall take its inputs from design information but shall also influence that design as it progresses to achieve supportable equipment along with the associated support data. This will ensure that informed decisions are made which take into account supportability and LCC factors when equipment and system options are being considered. 7.1.4 As the equipment design solution matures, the LSA sustains directly the activities to plan and provide the necessary logistic support. This prepares the ground for initial and in-service provisioning. The LSA will also define maintenance requirements, which will lead directly to the creation of Electronic Documentation. The need for support and training facilities will also be determined. 7.1.5 The LSA process generates data, which will be stored in the LSA Record (LSAR). This Defence Standard describes the LSAR in relational data base form. The LSAR provides the information required to define the support. Some or all of this LSAR information will be maintained throughout the life of the equipment. There may be circumstances (eg for small quantities of data) where the LSAR information can be presented in other forms; specific requirements will be included in the contract.


14

7.1.6 In-service support of the equipment will include maintenance, spares re-supply, documentation-update and continuous configuration management. In addition, data will be gathered on equipment performance and support consumption to compare with the original requirements. Support performance will be measured and the LSAR will be updated to reflect actual experience - this is referred to as maintaining a ‘hot’ LSAR. The LCC model will be updated in line with the hot LSAR. 7.1.7 Actual performance will be compared with that anticipated, on a continuous basis, not only to effect in-service management actions, but also to influence decisions about follow-on procurements, eg of the same equipment or, perhaps, a different modification state (or batch) of equipment. In-service management decisions, based on the resultant predictions, may include the need to change support facilities, spares holding, maintenance skill levels, or a modification to the equipment itself. Similarly, new projects will be influenced by the results of the disciplined monitoring of previous equipment performance and costs. 7.1.1 Disposal costs can be significant. ILS ensures that disposal requirements are determined and costs identified. These are considered during equipment concept and taken account of during subsequent phases. The comparison between actual and anticipated costs will be made to complete the historical record of the equipment. 7.2 Disciplines and Elements of ILS. Within a project, ILS has both an influence on and draws information from the following disciplines and related elements:

a. Maintenance Planning. b. Supply Support. c. Support And Test Equipment (S&TE). d. Reliability and Maintainability (R&M), Safety, Testability and other design

disciplines. e. Facilities. f. Manpower and Human Factors. g. Training and Training Equipment. h. Technical Documentation. i. Packaging, Handling, Storage and Transportation (PHS&T). j. Disposal (To be addressed in more detail in subsequent issues).

IDENTIFY A

MILITARY NEED

DEVELOPEQUIPMENTCONCEPTS

ASSESS FEASIBILITY,DESIGN

PRODUCE EQUIPMENT

SUPPORT( RESUPPLY, REPAIR,

MAINTAIN ) & MONITORIN - SERVICE USE

DEVELOP SUPPORT STRATEGY DETERMINE / DELIVER SUPPORT

LCC

OTHER ILS ELEMENTS

MAINTAIN SUPPORT

REVISELCC

REVISE OTHER ILS ELEMENTS

TERMINATE SUPPORT

FINALLCC

DISPOSE

PROPOSE

EQUIPMENT

DESIGN CHANGE

LCC

PROCUREMENT IN - SERVICE

KEY

ILS FUNCTION

DEF STAN 00-60FUNCTION

ACTIVITY LINK

LSAHIGH LEVEL LSA ISSP

COMPARELSAR SUPPORT

SUPPLY

DOCSTECH

REVISE

LSARFINAL

TECHDOCS

Figure 1 Importance of ILS Within Defence Equipment and Materiel Support

DE

F ST

AN

00-

60 (P

AR

T 0

)/5

15


16

7.3 ILS Functions Within Def Stan 00-60. This Defence Standard identifies specific, inter-related functions, defined by their own standards and specifications profiled herein for consistent use. This includes the fundamental function of LSA and the core ILS Elements of supply support and Electronic documentation identified above. The functions are shown in Figure 2 and described below: 7.3.1 LSA. LSA, which is fully detailed in Part 1 of this Defence Standard, is conducted iteratively as part of the design process. It shall influence the design by stimulating trade-off decisions to optimize LCC. As the design matures, the role of LSA moves towards identifying the support operations and resources required for the selected design. The results are documented within the LSAR. This LSAR shall then be used to inform the concurrent procurement of the support infrastructure to meet fielding requirements. The LSAR must remain alive to design changes as the design moves into production and thus reflect the as-built equipment. 7.3.2 The LSAR, which is fully detailed in Part 1 of this Defence Standard, records data which is used to determine the requirements for many of the ILS elements in Clause 7.2. The LSAR for the production-standard equipment shall be available for delivery as required by the contract. Finally, the LSAR will normally be kept active, comparing in-service with anticipated performance, in order to manage LCC by improving the design and/or supportability characteristics as appropriate. 7.3.3 The LSAR shall be implemented in a relational database as defined in this Defence Standard, unless (exceptionally) otherwise specified in the contract. 7.3.4 LSA for Software. Guidance on the application of LSA to software in equipment procurement is provided in Part 3 of this Defence Standard. 7.3.5 Supply Support. The procedures for Supply Support are detailed in Part 20 of this Defence Standard. Specialist Supply Support aspects are covered in Parts 21 to 26 of this Defence Standard as follows:

b. Part 21 Initial Provisioning. c. Part 22 Codification. d. Part 23 Procurement Planning. e. Part 24 Order Administration. f. Part 25 Invoicing. g. Part 26 Repair and Overhaul.

The ranging requirements for initial provisioning shall be decided during the LSA programme. S2000M provides for these functions and is applicable to land, sea and air supply support


17

procedures. Supply Support shall use this Defence Standard’s interpretation of that specification. 7.3.6 Electronic Documentation Creation and Delivery. 7.3.6.1 The procedures for Electronic Documentation are detailed in Part 10 of this Defence Standard. Information to support defence equipment comes from a variety of sources including the LSAR (for maintenance task descriptions and parts data) and also from the design activity itself (for technical drawings and other information). The range of Electronic documentation shall be prepared and delivered in accordance with the contract requirements. S1000D is a European specification for Technical Publications utilizing a common source database. Electronic documentation creation and use shall be in accordance with this Defence Standard’s profile of S1000D. 7.3.6.2 Where Technical Documentation creation and/or delivery is by means other than that prescribed within Part 10 of this Defence Standard, the requirement will be specified within the contract. 7.4 Business Interfaces Within ILS. The interfaces between the functions above are represented in Figure 2. The diagram presents the model for procuring equipment. However, in-service actions are also portrayed by recognizing that the in-service feedback influences new or revised activities in each of the ILS functions. 7.5 Interfaces Outside the Current Scope of Def Stan 00-60. The integrated support processes defined in this Defence Standard have interfaces with other ILS processes and standards which do not currently have a standard MOD prescription. These include, but are not limited to: LCC modelling; equipment configuration management; equipment materiel management; spares modelling and Human Factors. Where there are specific requirements for them, they will be stated in the Contract. 7.6 Quality Assurance (QA) 7.6.1 QA requirements will be defined for the overall project and be set down in the terms and conditions of the contract. 7.6.2 The QA requirements will apply to the ILS management, analysis and document control arrangements and be provided for in the Project Quality Plan. There will be no differentiation in the quality system employed for the design, development, engineering or logistics of the Project. 7.6.3 All ILS deliverables and their design management and control shall be subject to the QA arrangements. The Contractor shall provide full traceability of analysis, data and any trade-off studies undertaken to obtain the delivered equipment support package.


18

7.7 Configuration Management (CM) 7.7.1 There are two inter-related aspects of CM: the CM of the equipment and the CM of the ILS elements, together with the management of the associated data. The ILS activities shall be subject to the overall CM requirements of the project and as defined under the terms of the contract.

DE

F ST

AN

00-

60 (P

AR

T 0

)/5

19

DocumentationProduction

Generate DataModules

Verification

DocumentationDesign Planning

Verification

Delivery

Data Capture &Preparation

Maintenance TaskAnalysis

RCM

Preventive Tasks

Level of RepairAnalysis

Skills

FMECA

Support & TestEquipment

Training Packaging HandlingStorage & Transport

Facilities

Corrective Tasks

DESIGN

MaintenanceTask Data

IP Data /Range of Spares

Product / Operational Data

MILITARY NEED

USE STUDY

Operational Data

Operational Data

IPCData

IPC

Data

LSA

Tech Docs

ISSP

Key

Feedback

Figure 2 ILS Process Diagram

Codify

Scale

Invoice

Order

Plan ProcurementSparesConsumptionData

ScreenIncl Range

Verification

IPC

Data


20

7.7.2 The CM requirement shall be as defined in Def Stan 05-57 covering all technical and administrative functions of identifying, documenting, controlling and reporting the functional and physical characteristics of the logistic support requirements during the life cycle. 7.7.3 Strict Configuration Control of the data within the LSAR is essential. Changes to the LSAR resulting from changes to the design or support policies must be reflected in the Supply and Electronic Documentation information. Configuration Management procedures should address the mechanism for ensuring the logistics databases are mutually aligned. 7.8 Data Management 7.8.1 The management of information in an electronic environment requires formal data management. This involves the management and control of the data dictionary, comprising data elements, data names, data meanings (semantics) and data format (syntax). This data management is applied to the data dictionary described in this Defence Standard at Section 5. 7.8.2 The data management system invoked shall comply with the Configuration Management arrangements thus ensuring that all data changes and updates are controlled within the change control procedures. 8 CONTRACTING ENVIRONMENT 8.1 Introduction. ILS requirements will be included in the ITT and should be addressed at bidders’ conferences if held. The overall tender package may also include a questionnaire, which will incorporate ILS aspects, to which the Contractor shall respond. 8.1.1 ILS TENDER PACKAGE. To enable the Contractor to understand the MOD’s ILS requirements, suitable ILS documentation will be included with the ITT. This will generally comprise of the documents detailed below. 8.1.1.1 ILS Plan. The ILS Plan (ILSP) outlines the MOD management plan for the identification and provision of logistic support to introduce and sustain an equipment in-Service. The ILSP will be the action guide for ILS participants, describing equipment procurement events and processes requiring ILS action, interface and/or support. It defines the details of the MOD activities, including ILS Element Plans (See Section 4 for the definition of ILS Principal Elements). MOD sensitive information will be removed from the ILSP for tendering purposes. 8.1.1.2 LSA Strategy.


21

The LSA Strategy (LSA Task 101), which will form part of the ILSP, sets the foundation of the LSA activity and formalizes the interfaces with the related LSA subjects. Major considerations in determining the LSA Strategy are the type of procurement, equipment complexity, project phase, availability of historical data, timescales and the resources available. The LSA Strategy will be periodically reviewed and updated to reflect any significant changes to the project. 8.1.1.3 Use Study. The purpose of the Use Study (LSA Task 201) is to detail the new system description, its mission profile, operating requirements, quantitative supportability factors, a description of the equipment being replaced and the existing support available for the new equipment. The MOD will promulgate the Use Study in the first instance and may request the Contractor to develop the document prior to completion of the appropriate procurement phase. The Use Study is not intended to constrain innovation. 8.1.1.4 Statement of Work (SOW). The SOW describes the activities that the Contractor shall complete. It details all the related engineering tasks, reporting requirements, reviews and schedules. The SOW states when LSA tasks shall be performed and when they shall be accomplished. The SOW provides instructions concerning the governing documents and standards. The following documents support the SOW: 8.1.1.5 Contract Data Requirement List (CDRL). The CDRL is a contractual document that supports the SOW for each data deliverable. The MOD CDRL template is provided at annex B. 8.1.1.6 Data Item Description (DID). DID provide the supporting detail to the CDRL. Each DID details the information required to meet the deliverable, by specifying the format, content, preparation and delivery material. The level of detail varies depending upon the DID and the project. DID will be specified in the ITT. Examples of DID which may be specified are at annex D. 8.1.1.7 MOD Data Selection Sheet (DSS). The MILSM will select which LSAR data elements are required for each phase of the project. The data elements are entered on the MOD DSS, detailed in annex B. Recommendations for adding or deleting data elements shall be submitted by the Contractor for each Candidate Item. 8.1.2 ILS Contract Activity. Some important elements of ILS contracting activity are described below:


22

8.1.2.1 Tailoring. The key to productive and cost effective ILS is the accurate tailoring of the activity to meet the requirements of a specific project. The MILSM will conduct the initial tailoring, possibly in concert with the Contractor. 8.1.2.2 Meetings/Conferences. This Defence Standard interprets the requirements for Guidance Conferences as follows: a. The Tenderer shall ensure that he understands the MOD’s requirements clearly. Any matters requiring further information or resolution should be raised either at bidders’ conferences prior to the submission of tenders, or at clarification meetings or Guidance Conferences prior to the award of the contract. b. Guidance Conferences may be held after the award of the contract but will have the sole purpose of agreeing how the detailed requirements of the contract are to be implemented. The onus will be on the contractor to raise problem issues, propose solutions and seek agreement to outstanding issues to which the MOD will respond. These conferences may expose issues the resolution of which may require a change to the contract. However, the conference itself is an inappropriate forum to propose any amendments to the contract or to the contract price; such proposals can only be discussed at separate formal contractual negotiations. c. After contract award, ILS review/coordination meetings should be held, as part of the Project review process, appropriate to the phase, to monitor and to facilitate the Contractor’s progress with the ILS Programme. 8.1.2 INTEGRATED SUPPORT PLAN (ISP). The Tenderer shall prepare and submit an ISP in response to the ILS requirements in the ITT. This will become the Tenderer’s principal ILS management plan. It shall describe his planned approach to meet the ILS requirements of the contract. The format of the ISP will be specified in a DID. 8.2 Electronic Environment ILS can generate data which requires to be bought under Configuration Management. Many participants require access to the data meaning that automated access to the data is essential. Within a company or organization there are important management issues which need to be addressed relating to information management, access and control (security). 8.3 Interchange Agreement. Where information is exchanged, either on-line via Electronic Data Interchange (EDI) or via magnetic media, an Interchange Agreement shall be negotiated and become part of the


23

contract. EDI is explained in Clause 18. The contractor shall be required to demonstrate the capability to exchange data successfully with the MOD’s IT system(s). 8.4 Use of Customer’s Experience. In the concurrent engineering environment of equipment development, where performance and logistic support trade-offs are being made, there is an opportunity to draw directly on the customer’s experience. Similarly, during detailed support planning, the customer’s advice can be valuable. Any arrangements for this will be stated in the contract which calls up this Defence Standard. The following mechanisms may be considered. They are primarily relevant to MOD/contractor relationships, but may also be relevant to contractor/sub-contractor relationships. 8.4.1 Consultation with Customer. The contractor may be permitted to seek advice from the MILSM on the basis that it shall be received ‘without prejudice’. The responsibility for the final outcome remains with the contractor. 8.4.2 On-site Expertise. It may be agreed that the customer will put his own representatives forward to work alongside the contractor. Again, the contractor may seek advice on the basis that it shall be received `without prejudice’. The responsibility for the final outcome remains with the contractor. 9 PROGRAMME AND TIMING The contract to which this Defence Standard applies will define the key dates for the conduct and completion of the necessary tasks in the application of ILS through the life of a defence equipment. 10 PROCESS INTEGRATION AND DATA MANAGEMENT The data integration of the business processes are described in Section 4. The detail of the individual processes is described in the subsequent parts of this Defence Standard.


24

SECTION FOUR. ILS ELEMENTS AND THEIR INTERFACES WITH DEF STAN 00-60. 11 INTRODUCTION 11.1 Section 3 of this Part of this Defence Standard introduced all the ILS elements and described the detail of the core functions contained in this Defence Standard. This Section describes in more detail those elements not yet discussed. 11.2 The elements are those which lie outside the core of this Defence Standard because, unlike Integrated Supply Support and Electronic Documentation, they are not fully supported by integrated standards. However, the LSA process requires that all these elements are considered and are no less important in the development of supportable equipments. 11.3 The overall interfaces of ILS with the procurement process and with in-Service support are introduced first. 12 ILS PRINCIPAL ELEMENTS The meaning to the MOD of the ILS Elements is described below: 12.1 Maintenance Planning. Maintenance planning is the process conducted to evolve and establish maintenance concepts and requirements for a equipment. The result is a maintenance plan for the equipment, the data of which is recorded in the LSAR. The maintenance plan shall be consistent with the Use Study. The detailed requirements and applicable standards are described in Parts 1 and 2 of this Defence Standard. 12.2 Supply Support. Supply Support has already been discussed in Section 3. 12.3 Support and Test Equipment (S&TE). S&TE comprises all equipment (mobile or fixed) required to support the operation and maintenance of a equipment. This includes associated multi-use end items, maintenance equipment, tools, metrology and calibration equipment, test equipment and automatic test equipment. All the required S&TE shall be determined and reported in the LSAR. The S&TE shall be identified in accordance with the specific requirements of the ILS Plan (ILSP) and Use Study. The ILSP will state the requirements for: using equipment from an existing standard range; using equipment already held at a maintenance facility; and the use of built-in test equipment. The determination of the S&TE shall be closely linked with the requirements for standardization which ILS promotes. Special tools and test equipment shall normally be avoided unless there are over-riding LCC benefits.


25

12.4 Reliability and Maintainability (R&M). R&M are performance requirements of defence equipment and have a dominant impact upon both operational effectiveness and LCC. The requirements for R&M will have been stated in the technical specification for the equipment. ILS provides the mechanism to identify and optimise the cost of support options relative to the cost of achieving given R&M and performance requirements. The activities undertaken within the LSA will require outputs from the R&M activities, such as Failure Modes Effects Analysis (FMEA), Failure Modes Effects and Criticality Analysis (FMECA) and Reliability Centred Maintenance (RCM). The results of LSA in the determination of system support criteria for optimal whole life costs may need a subsequent trade-off between the ILS elements and disciplines. The ILSP shall detail the requirement for the outputs from the R&M programme. 12.5 Facilities. Facilities comprise all the physical infrastructure required to integrate, operate and maintain the equipment. There are links with S&TE and Training elements. The facilities required shall be determined through the LSA process and recorded in the LSAR. This shall include the justification of their need, their specification and cost. 12.6 Human Factors Integration (HFI). 12.6.1 HFI is a specific discipline containing a set of Manpower and Human Factor considerations, which was formerly known as MANpower and PeRsonnel INTegration (MANPRINT). This programme aims to examine the balance of manpower and personnel across both operational and support areas with the overall objective of ensuring that during equipment definition and procurement, full account is taken of the capabilities and limitations of the military and civilian personnel required to operate and maintain the equipment or facility in-service. The Manpower and Human Factors implications of the equipment support shall be determined and shall meet any over-riding requirements of the technical specification and ILSP. In particular, the number and skills of military and civilian personnel needed to operate and maintain the equipment or facility shall be determined. In a wider sense, the recognition of all human factors issues, in so far as they relate to supportability of the equipment, shall be considered during LSA. The safe and efficient operation and maintenance of equipment shall be a fundamental requirement of considering Human Factors. 12.6.2 ILS/HFI Interface. HFI covers areas outside the scope of ILS but the discipline is fed with much information arising from the LSA. The System ‘MANPRINT’ Management Plan and Target Audience Description will influence MOD’s ILSP and Use Study. This Defence Standard does not define the application of HFI but requires all relevant data from the LSAR to be made available in a consistent form to satisfy any HFI requirements. The application of HFI will naturally influence LSA and may drive the maintenance requirements in a particular direction. It is anticipated that the direct linkages with HFI will further develop over time.


26

12.7 Training and Training Equipment. Trained and qualified operators and maintainers will be required to support the equipment. The ILSP will define how the requirements for training are defined and the Use Study will outline the current skill levels and qualifications of Service support personnel. LSA will be used to determine the training needs of the support personnel. LSA will also provide data for Training Needs Analysis (TNA). 12.8 Electronic Documentation. Electronic Documentation is discussed in Section 3. 12.9 Packaging, Handling, Storage, and Transportation (PHS&T). The resources, procedures, design considerations and methods to ensure that all system equipment and support items are packaged, handled, stored and transported properly shall be determined during LSA and recorded in the LSAR. The requirements shall include environmental limitations, equipment preservation requirements for short and long term storage and transport requirements. PHS&T shall conform to appropriate legislation, particularly for hazardous materials. 13 Additional ILS Elements The previous clauses have reviewed the principle elements of ILS. In the MOD application, the following elements are also identified as significant to the integrated approach to the through life management of equipment. 13.1 LCC. The system life cycle refers to the entire spectrum of activity commencing with the identification of the need for the equipment and culminating in its disposal. The objectives of ILS are to ensure that all support requirements are identified and put in place in a manner which contributes to the optimization of overall LCC, by influencing design, identifying cost effective support solutions and programme planning. The Contract, which calls up this Defence Standard, will define the requirements for LCC and the modelling techniques to be employed. 13.2 In-Service Monitoring of Logistic Performance. MOD Policy requires data, which is subject to change, to be collected in-service. Actual R&M and support data realized in-service shall be recorded and compared with the equipment’s LSAR. The comparison of anticipated and actual performance and in-service costs, shall permit decisions to be made and may lead to changes in the support strategy. For example, the equipment may be redesigned, the spares holding may be changed, technical publications may be updated or the skill levels of maintainers changed (ie conduct an in-service Level of Repair Analysis (LORA)). In-Service monitoring may require automatic data


27

collection equipment, which shall be identified in the Facilities function described in Clause 12.5. The overall responsibilities and requirements for in-Service monitoring will be stated in the ILSP and SOW.


28

SECTION FIVE. DATA MANAGEMENT 14 INTRODUCTION It is essential that data be transferable between the ILS activities described in this Defence Standard. The flow and access to data will allow the processes to be performed more efficiently, concurrently or sequentially, as appropriate, and with strict configuration management. The tools, which facilitate this interaction, are the Data Dictionary of this Defence Standard and that of S2000M, LSAR Relational Tables, Business Rules and Reports, Standard Generalized Mark up Language (SGML) Tag Set and EDI, which are expanded in this Section. 15 DATA DICTIONARY 15.1 Defence Standard 00-60 Data Dictionary. The Defence Standard 00-60 Data Dictionary defines all Data Elements required to record results in the LSAR, from the business processes detailed in this Defence Standard. It includes data elements identified as necessary to allow transfer of information between the processes, but excludes those data elements peculiar to Parts 23 to 26 of this Defence Standard. The Data Dictionary of this Defence Standard ensures that terms (name, syntax and meaning) used to describe items of data are consistent throughout this Defence Standard; it is published at annex C along with related technical data. 15.2 S2000M Data Dictionary. The S2000M Data Dictionary defines data elements required for the ISSP business processes detailed in Parts 22 to 26 of this Defence Standard. However, data elements in the S2000M Data Dictionary used for the ISSP business processes detailed in Part 21 of this Defence Standard are subsumed in the Data Dictionary at annex C. 16 LSAR RELATIONAL TABLES BUSINESS RULES AND REPORTS To facilitate linking of the LSA, IP, Codification and Electronic Documentation processes, Relational Tables, Business Rules and Reports have been created, along with data elements and these are defined in annex C. There is no requirement to pass information between IP and Electronic Documentation other than via the LSAR.

17 SGML This Defence Standard profiles ISO 8879 (SGML) for exchanging Electronic documentation data. ISO 8879 describes a standard way of defining the structure of a document without reference to its format. Use of SGML requires the production of an SGML declaration and a Document Type Definition (DTD).


29

17.1 DTD. A DTD describes how document elements are structured. Once a document, report or data element is tagged in this way, it is not reliant on software or hardware configurations, hence it is neutral. 17.2 Application of SGML. Part 10 of this Defence Standard describes the detailed application of SGML, utilising AECMA S1000D. 18 EDI 18.1 EDI is the automated exchange of predefined and structured data, for some business purpose, between information systems of two or more parties. EDI transactions shall be covered by an EDI agreement (see DEF FORM 30 ‘MOD Electronic Data Interchange Agreement’) between the communicating parties. 18.2 On line EDI does not yet successfully handle the exchange of large data files, such as multiple drawing and graphics files. Until this is resolved, the data exchange standard shall be MIL STD 1840. This allows interchange using bulk storage media (magnetic and optical media).


30

SECTION 6. MANAGEMENT OF DEFENCE STANDARD 00-60 MAINTENANCE 19 INTRODUCTION As the sponsor of this Defence Standard, AD ILS is responsible for its maintenance and change control. MOD policy and changes to the enabling standards may affect the functionality of this Defence Standard. Only essential changes will be introduced to maintain functionality and promote convergence. 20 CHANGE PROCEDURE Users wishing to seek clarification or propose changes to this Defence Standard should do so in accordance with the flowchart detailed at Figure 3. 21 DEFENCE STANDARD 00-60 HELP DESK Details of the Defence Standard 00-60 Help Desk are at annex E. Any advice provided via the Help Desk is given without commitment and without prejudice.


31

PASSED TO D-STAN

USER QUERY

QUERY LOGGED

HELP DESK

QUERY ANSWERED

ANSWER LOGGED

REFER TO SPONSOR

REVIEW

CHANGE REQUIREMENT LOGGED

RESOLVED

DRAFT CHANGE

APPROVED

NO

YES

NO

YES

AMENDMENT TO ENABLING STANDARD

POLICY/ STRATEGY

ISSUE

NO

YES

Figure 3 DEFENCE STANDARD 00-60 CHANGE PROCEDURE

Date post:	24-Oct-2014
Category:	Documents
Upload:	mjpl
View:	86 times
Download:	0 times