Figure 21 LSAR Data Table utilization by equipment breakdown

DEF STAN 00-60 (PART 2)/3

ANNEX C (CONTINUED)

C.1.4 Clause C.3 of this annex provides a step by step procedure for tailoring the LSAR. This is based upon LSA tasks and subtasks detailed in Part 1 of this Defence Standard, related engineering and Integrated Logistic Support (ILS) element analysis efforts which result in LSAR data and deliverable logistic products specified in the contract. The result of this tailoring process is a completed LSAR Data Selection Sheet (DSS), identifying the LSAR data table and data element requirements for the specific project phase. (see annex B to Part 0 of this Defence Standard). The DSS forms part of the Contract Data Requirements List (CDRL) as contract deliverables.

C.1.5 Guidance for determining LSAR completion schedules is contained in clause C.4 of this annex. The final step in tailoring the LSAR effort involves contractual delivery of the LSAR data itself. Clause C.5 of this annex discusses alternatives for delivery of the LSAR data.

C.2 LSAR Application and Use by Life Cycle Phase

C.2.1 The application of LSA and LSAR to projects is described in Section 3 of this Part of the Defence Standard.

C.2.2 Concept and Feasibility Study Phases. The results of the LSA that has been undertaken are embodied in the programme documents and supplemental technical reports and are used for procurement decision process prior to entry into the next project phase. The limited LSAR data is usually produced to define and document system level requirements. Figure 22 suggests a list of the data elements which might be generated in this phase to populate the LSAR. However, this list of data elements is not exhaustive. Moreover, it is unlikely that all of the elements will be required to support LSA objectives as each project will demand its own requirements for data.

C.2.3 Project Definition and/or Full Scale Development Phases. More detailed LSA may be specified in these phases and the data elements completed within each data table are dependent upon the analysis tasks specified. To make full use of the LSAR documentation previously developed, contracts should specify that repair and support requirements be documented for all maintenance levels down to major subsystems. This data can be used to verify data derived for lower assemblies/parts, and conversely, for the system and major subsystems.

C.2.3.1 As the project proceeds through Project Definition to full development, the LSAR data tables are completed to the hardware indenture level. The resulting data is used to develop logistics support requirements for testing, deployment, and operation.

C-4

Figure 22 Feasibility study phase LSAR

C-5

DEF STAN 00-60 (PART 2)/3

ANNEX C (CONTINUED)

C.2.4 Production and In Service Phases. The LSAR data established during the Development Phase is retained during these phases to:

(a)Support the logistics analyses that occur as a result of engineering design changes.

(b)Evaluate the system's performance after it is deployed to determine the impact of future equipment modifications or support requirements.

(c)Manage the support of the equipment in-Service.

(d)Establish design changes, goals, and requirements for succeeding generations of materiel procurement.

C.3 Tailoring LSAR Requirements. The extent of the LSAR inputs and outputs required to document and support the analyses of LSA tasks will vary by project. These variations are attributable to such factors as: life cycle phase; hardware and software complexity; and any other characteristics (e.g., new development, major modification, non-developmental). When tailoring the LSAR requirements, each functional and engineering specialist area should be involved. The guidance contained in the following clauses of this annex have been arranged in a logical, step by step sequence to assist in the optimum selection of LSAR requirements.

C.3.1 LSA Task Selection. The initial step in tailoring of the LSA data requirements involves selection of the LSA tasks described in Part 1 of this Defence Standard. Detailed guidance for LSA task and subtask selection, with respect to project characteristics, procurement phase, and information requirements associated with primary system developmental phases, is provided in annex A to this Part of the Defence Standard. Selection of some LSA tasks will result in data which is documented directly into the LSAR. Output from other tasks becomes the input to follow-on analyses, and as such, relates only indirectly to the LSAR documentation. Table 2 provides a list of the LSA tasks and subtasks which relate directly to the LSAR data tables. A review of each data table is required to ensure that only those data elements required to document the tasks are procured. Once established, the specific data elements required to document the tasks should be recorded on UK Data Selection Sheet (see annex B to Part 0 of this Defence Standard).

C.3.2 Interfacing and Coordination With Other Programme Elements. Data required to conduct an effective LSA programme may also be developed as a result of analyses conducted in support of in-Service equipment management requirements and also associated programme elements eg R&M; HFI; LCC, etc, etc. It is essential that engineering disciplines and ILS element interfaces are effectively managed and controlled. The emphasis should be to maximize the use of the data developed by each programme element to avoid duplication of data and the generation of incompatible ILS products.

C.3.3 Identification of the engineering and ILS functional element requirements which interface with the LSA process, and which use LSAR data, is an important consideration in the tailoring process. Results of analyses from other programme elements can be used as source data for LSA tasks and vice versa. For example, inputs from the design, reliability,

C-6

DEF STAN 00-60 (PART 2)/3

ANNEX C (CONTINUED)

maintainability, human factors integration, safety, and other programme elements may be required to satisfy the requirements of task 40l, Task Analysis, as described in annex A to Part 1 of this Defence Standard. There are clear benefits in using the features of the LSAR to record, store, and manipulate data in support of requirements imposed by other programme elements. As an example, the LSAR data tables can be used to produce the LSA-018, Task Inventory report. This report is used and reviewed by HFI specialists, as well as the LSA programme.

C.3.4 Once the related programme elements have been established, the next step in the tailoring process is the identification of the LSAR reports to determine the data table and specific data element requirements.

C.3.5 LSAR reports and the specific LSAR data elements are determined by using the LSAR relational tables to Report Matrix shown in Figure 17 in Part 0 to this Defence Standard. This matrix identifies all of the LSAR reports and the input data elements required to generate each (e.g. Maintenance Allocation Chart (MAC), can be satisfied by using the LSA-004 report).

Finding this report across the top of Figure 17 in Part 0 of this Defence Standard and then reading down the column will provide the user with the specific data elements and LSAR data tables required to produce the report. This process would be repeated for each report identified. The resulting information is included in the Data Selection Sheet and establishes the total LSAR data requirements from both an analysis and a logistics data product standpoint.

C.4 Scheduling of the LSAR Data. LSAR data is developed and provided so that it can be used in a timely manner as source data for the development and provision of the logistics products specified in the contract. This guidance is applicable to any type of development programme and any phase of the equipment life cycle. To establish timely completion requirements for the LSAR data, the completion dates for the data products that use the LSAR data should first be established. The required delivery dates for the logistic products should be established when preparing the ITT and/or contract, and should take into account the significant milestones of the project.

C.4.1 Once the scheduled completion dates for the logistic products have been established the required completion scheduled for the LSAR can be determined by using Figure 17, at annex C to Part 0 of this Defence Standard. This matrix table provides a cross-reference list of the LSAR data elements and the reports that use the data elements on a given data table for product development. Since the table is sequenced by data table, the completion date of each data table can be established by listing the delivery dates and then choosing the earliest date as the scheduled completion date for the LSAR data tables. This approach must be tempered by the range of data elements on a data table that are required as source data. For example, the scheduled delivery date for Long Lead Time Items List, may be l20 days after contract award, while the delivery date of Provisioning Parts List, is 24 months after contract award. This does not mean that all data tables related to support item identification and application are to be completed l20 days after contract award, but rather, specific data elements for parts with certain production lead times would be completed on data tables of support items to satisfy the Long Lead Time Items List.

C-7

DEF STAN 00-60 (PART 2)/3

ANNEX C (CONTINUED)

C.4.2 Completion dates for the LSAR reports can be established by using the required delivery dates of logistic products. Additionally, the scheduled completion date for the LSAR data tables, to include the specific data elements required to produce an LSAR report, can also be established by using Figure 17 in Part 0 of this Defence Standard. For example, if the Maintenance Allocation Chart (MAC) had a required delivery date of l8 months after award of contract, then the LSAR output report, LSA-004, must be available at that point for product development. It can also be established that specific data elements on the listed data tables must be completed for product development of MAC (and report LSA-004).

C.4.3 This approach to scheduling the completion of the LSAR data should take into account interim product delivery dates, final product delivery dates, and scheduled updates to final products. Each of these dates will impact the range of LSAR data required, depth of data required (i.e., the hardware, indenture levels and maintenance levels specified), and the number of updates to the LSAR data required. The LSAR completion schedule must then be coordinated with related programme schedules (eg drawing freeze and release) to ensure availability of data for LSAR development. Finally, by establishing a LSAR completion schedule which is timely for product development, the project now has the additional option of not requiring delivery of LSAR data as a separate data item. In effect, completion of a deliverable product is intimately tied to the LSAR data and quality.

C.5 Alternatives for Data Delivery. LSAR data can be delivered in manual form, LSAR reports, LSAR data table files, or through interactive access to a contractor LSA database. The use of a manual LSAR data file is generally applicable to simple hardware and COTS systems; limited report requirements; infrequent use of the data; and uncomplicated reports. Implementation of an automated LSAR is generally applicable to a complex hardware system; multiple and varied applications; ability to produce tailored reports; on demand use with short response time and the ability to manipulate the LSAR data for specialized reports.

C.5.1 An automated LSAR presents the additional decision option of who will be made responsible for Automated Data Processing (ADP) of the LSAR data. Normally, the contractor would be responsible for data processing using an appropriate LSAR software system. The alternative to this is to use the in-house ADP capabilities of the project, thus requiring only a data entry by the contractor. Once the decision is made who will be responsible for automated processing of LSAR data, the media for delivery can be established.

C.5.2 Delivery of the LSAR reports contained in annex C to this Part 0 of this Defence Standard is one option for delivery of data in an automated LSAR environment. The LSAR reports are intended to satisfy the delivery requirements of specific logistics products (e.g., MAC, Maintenance Plan, Support Equipment Recommendation Data, etc). As such, the LSAR reports are static presentations of LSAR data and cannot be updated or processed further after delivery. They offer the least flexibility for LSAR data use from an automated standpoint. Requiring LSAR reports as deliverables is appropriate for final product delivery, or when no further processing capability is available or necessary.

C.5.3 Delivery of the LSAR relational tables via magnetic tape/disc/drum is another option for delivery of data in an automated environment. This option also includes the delivery of

C-8

DEF STAN 00-60 (PART 2)/3

ANNEX C (CONTINUED)

LSAR data files that require processing from the LSAR relational tables (eg, input files for provisioning, codification screening, or packaging data, etc). An internal processing capability is required for each LSAR data file procured by the project. Delivery of the LSAR relational tables provides the capability to subsequently produce any of the LSAR reports, other data files, and to produce ad hoc reports via the query capability of the LSAR Relational ADP system. Separate delivery of the LSAR data files places the responsibility for their generation with the contractor rather than the project. Because of the flexibility provided by these processable data files, they can be used to satisfy both interim and final LSAR delivery requirements. Periodic delivery can reduce time spent for on-site data reviews by providing a vehicle for advanced review of the data. Final contract deliverables can be consolidated and reduced by internal processing of LSAR data files, in part or in total. In addition, LSAR systems are required to have the capability to produce and load standard outputs not only for all data tables, but also standard outputs for ‘change only’ data (changes to the data tables since the previous delivery of the LSAR data).

C.5.4 The third LSAR deliverables option is interactive access to a contractor’s LSA database by using a LSAR Relational software system. Interactive access includes the ability to selectively retrieve, review, print, and process contractor LSA source data. Interactive access for faster project review of LSAR information represents more of a contractor service capability than a specific deliverable requirement. This capability makes the most current authorized data available to the project and eliminates the time required for preparation and submission of deliverable products. It can also significantly reduce the time requirement for on-site reviews, while supporting internal analyzes and planning that requires up-to-date supportability information. Interactive access provides the greatest flexibility for using LSAR data, either by utilizing the contractor’s automated LSAR capabilities, or by electronically transferring the data for further internal processing. Since interactive access can support interim and final delivery of both LSAR reports and data files, it may entirely eliminate the need to bring the LSAR data in-house. (However, it is advisable to have the LSAR relational table files delivered at contract completion.) The interactive access service can be very effective for satisfying LSAR deliverable requirements during the early life cycle phases when the volume of LSAR data is low. In latter phases, interactive access may be more appropriate as a contract compliance, ‘change only’ data review, and internal analysis tool rather than for bulk transfers of complete LSAR master or data files.

C-9

DEF STAN 00-60 (PART 2)/3

ANNEX C (CONCLUDED)

Collation Page

C-10