- •Preface
- •0 Introduction
- •1 Scope
- •2 Related Documents
- •3 Definitions
- •4 Policy
- •Section Two. The Purpose and Scope of Def Stan 00-60
- •5 Purpose
- •6 Scope of Def Stan 00-60
- •Section Three. Defence Equipment Acquisition and Materiel Support (DEAMS)
- •7 Business Overview
- •8 Contracting Environment
- •9 Programme and Timing
- •10 Process Integration and Data Management
- •11 Introduction
- •12 ILS Principal Elements
- •13 Additional ILS Elements
- •Section Five. Data Management
- •14 Introduction
- •15 Data Dictionary
- •16 LSAR Relational Tables Business Rules and Reports
- •17 SGML
- •Section 6. Management of Defence Standard 00-60 Maintenance
- •19 Introduction
- •20 Change Procedure
- •21 Defence Standard 00-60 Help Desk
- •Figure 3 Defence Standard 00-60 Change Procedure
- •Figure 6 X Table Relationships
- •Figure 7 A Table Relationships
- •Figure 8 B Table Relationships
- •Figure 9 C Table Relationships
- •Figure 10 E Table Relationships
- •Figure 11 U Table Relationships
- •Figure 12 F Table Relationships
- •Figure 13 G Table Relationships
- •Figure 14 H Table Relationships
- •Figure 15 J Table Relationships
- •Figure 16 Z Table Relationships
- •Figure 17 LSAR Data Tables to Report Matrix
- •Figure 18 LSA-001 summary
- •Figure 19 LSA-003 summary
- •Figure 20 LSA-004 summary
- •Figure 21 LSA-005 summary
- •Figure 22 LSA-006 summary
- •Figure 23 LSA-007 summary
- •Figure 24 LSA-008 summary
- •Figure 25 LSA-009 summary
- •Figure 26 LSA-010 summary
- •Figure 27 LSA-011 summary
- •Figure 28 LSA-012 summary
- •Figure 29 LSA-013 summary
- •Figure 30 LSA-014 summary
- •Figure 31 LSA-016 summary
- •Figure 32 LSA-018 summary
- •Figure 33 LSA-019 summary
- •Figure 34 LSA-023 summary
- •Figure 35 LSA-024 summary
- •Figure 37 LSA-026 summary
- •Figure 38 LSA-027 summary
- •Figure 39 LSA-030 (Option 1) summary
- •Figure 40 LSA-033 summary
- •Figure 41 LSA-036 summary
- •Figure 42 LSA-037 summary
- •Figure 43 LSA-039 summary
- •Figure 44 LSA-040 summary
- •Figure 45 LSA-046 summary
- •Figure 46 LSA-050 summary
- •Figure 47 LSA-056 summary
- •Figure 48 LSA-058 summary
- •Figure 49 LSA-065 summary
- •Figure 50 LSA-070 summary
- •Figure 51 LSA-071 summary
- •Figure 52 LSA-072 summary
- •Figure 53 LSA-074 summary
- •Figure 54 LSA-075 summary
- •Figure 55 LSA-076 summary
- •Figure 56 LSA-077 summary
- •Figure 57 LSA-078 summary
- •Figure 58 LSA-080 summary
- •Figure 59 LSA-085 summary
- •Figure 60 LSA-126 summary
- •Figure 61 LSA-151 summary
- •Figure 62 LSA-152 summary
- •Figure 63 LSA-154 summary
- •Figure 64 LSA-155 summary
- •Figure 65 LSA-602 summary
- •Figure 66 LSA-604 summary
- •Figure 67 LSA-606 summary
- •Figure 68 LSA-608 summary
- •Figure 69 LSA-610 summary
- •Figure 70 LSA-612 summary
- •Figure 71 LSA-614 summary
- •Figure 72 LSA-624 summary
- •Figure 73 LSA-626 summary
- •Figure 74 LSA-628 summary
- •Figure 77 LSA-634 summary
- •Figure 78 LSA-636 summary
- •Figure 79 LSA-648 summary
- •Figure 80 LSA-650 summary
- •Figure 81 LSA-652 summary
- •Figure 82 LSA-654 summary
- •Figure 85 LSA-660 summary
- •Figure 86 LSA-662 summary
- •Figure 87 LSA-664 summary
- •Figure 88 LSA-668 summary
- •Figure 89 LSA-672 summary
- •Figure 90 LSA-674 summary
- •Figure 91 LSA-676 summary
- •Introduction
- •Logistic Support Analysis Record Relational Tables
DEF STAN 00-60 (PART 0)/3
7.7.2The 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.3Strict 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.1The 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.2The 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.1ILS Plan. The ILS Plan (ILSP) outlines the MOD management plan for the identification and provision of logistic support to introduce and sustain an equipment inService. 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.2LSA Strategy. 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.
19
DEF STAN 00-60 (PART 0)/3
8.1.1.3Use 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.4Statement 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:
(a)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.
(b)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.
(c)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:
8.1.2.1Tailoring. 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.2Meetings/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
20
DEF STAN 00-60 (PART 0)/3
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.3 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.3Interchange 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 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.4Use 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.
8.4.1 The following mechanisms may be considered. They are primarily relevant to MOD/contractor relationships, but may also be relevant to contractor/sub-contractor relationships.
(a)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.
(b)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.
21
DEF STAN 00-60 (PART 0)/3
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.
22