Dated 01 March This page lists the ownership and areas responsible for providing technical approval for this Standard. It also lists applicable documents that should be read in conjuncti on with this Standard. Approving Authority:. Applicable Documents:. Historical Record.
|Published (Last):||26 December 2005|
|PDF File Size:||10.15 Mb|
|ePub File Size:||4.85 Mb|
|Price:||Free* [*Free Regsitration Required]|
Dated 01 March This page lists the ownership and areas responsible for providing technical approval for this Standard. It also lists applicable documents that should be read in conjuncti on with this Standard. Approving Authority:. Applicable Documents:. Historical Record. Blank Page. Logistic Support Analysis LSA is a selected applic ation of systems engineering techniques, originally. LSA, as applied in the Australi an Defence Organisation ADO , expands LSA as a Life Cycle Discipline to enable the benefits of consistent anal ytical techniques to be readily applied to major and minor projects, modifications, In-service analysis for logistic optimisation, and disposal.
The LSAR was developed to fulfill this requirement. A number of these activities provide and use LSAR data. Document Management Information.
Amendment list. List of Figures. LSAR Reports. Data Element Dictionary. The goal was to establish uniform requirements for development and delivery of LSA Record data. However, LSA documentation must be tailored to each acquisition program and for each phase of the materiel life cycle. Application guidance in Annex D is included to provide guidance for tailoring LSAR data requirements to meet individual program objectives in a cost-effective manner. The general requirements of this standard also require completion of LSAR Data Selection Sheets to identify the specific data requirements for each program in order to prevent indiscriminate blanket applications of the data requirements.
This is accomplished through. Consolidation of logistics orientated technical information for the various engineering disciplines and ILS elements into one file to reduce redundancy, facilitate timely usage, and enhance consistency between elements and disciplines. Maximum use of industry developed integrated data systems tied to engineering, manufacturing, and product support databases as sources of LSA documentation. This characteristic makes an LSAR an. The relational design of LSAR data is intended to facilitate such integration and to encourage independent development of useful ad hoc queries that promote use of data in the design process.
The use of industry developed, cost-effective automation tools which link "islands of automation" eg. It does not prescribe Automated Data Processing. Application of Standard. As used in this standard,.
The Performing Activity may be either a Contractor or government activity. The use of the term, contract, in this standard includes any document of agreement between organisations to include between a government activity and another government activity, between a government activity and a Contractor, or between a Contractor and another Contractor. Annex A. Annex B. Contains a description and the required format for each LSAR standard. Annex C. Annex D. Contains guidance for tailoring of the LSAR data.
Annex E. The requirements for an LSAR shall not be specified in a contract without also specifying the. Activity and Requiring Authority have a firm understanding of the relationship between the LSA Activities to the LSA documentation, program milestones, and contractual requirements. When a guidance conference is not contractually specified and the Performing Activity desires a conference, the Performing Activity shall propose a date and place.
The specific date and place for the guidance conference will be determined by the Requiring Authority and Performing Activity. The guidance provided to the Performing Activity by the Requiring Authority may include, but shall not be limited to, the following:. Figure Figure should not be misconstrued to mean that one type of data table must be completed in its entirety before the next data table can be completed.
However, generation of LSAR data is also dependent on the design engineering process and release of drawings preliminary, development, or final. RAM Parameter Relationships. RAM Parameter Relationships - continued. Input sources for establishing data are listed as A to F. The numbers 1 to 6 are used for cross-referencing between the two figures. These relationships lead to the identification of the respective availability measures at the top of Figure The rest of Figure is based on determining reliability parameters while Figure focuses on maintainability parameters repair times.
Abbreviations list at the end of this standard. Related Policies. Military Standards and Handbooks. Systems and Support Equipment cancelled.
Other Publications. LSA Program. The specific data entry, media, storage, and maintenance procedures may be left to the Performing Activity.
The LSAR data forms a database to:. Determine the impact of design features on logistics support. Provide data for trade-off studies, life cycle costing, and logistic support modelling. Exchange valid data among functional organisations.
Provide the means to assess Su pportability of the fielded item. Provide the means to evaluate the impact of engineering change, product improvement, major modification or alternative proposals. In addition, the form will be used to specify the data elements required for each Provisioning Technical Documentation PTD list or packaging categorisation of items required. Only one option will be specified for a data element with multiple entry options.
The Requiring Authority is responsible for specifying the equipment indenture level. It may also be prepared and maintained automatically through use of LSAR application software. Costs and schedules of preparation. Availability of an ADP system. Hardware complexity.
Requiring Authority's schedule requirements. Design stability. Requiring authority involvement. All manual preparation must comply with table structures, relationships and data element field formats or considerable manual rework of data will be required for conversion of data into Defence project and In- service LSAR systems.
There is also the option of preparing the ASCII text transfer file directly, this enables data import into a compliant LSAR although this is a detailed and time consuming. When the LSAR reports are produced by non-automated means, the reports shall be in accordance with IAW the content, format, sequence, and computational requirements contained in.
There are many disadvantages of manual report preparation, not least it is time consuming and the. Additionally, manual preparation requires repeated writing of the same data, and lacks the flexibility to keep and easily update the data through life. Manual preparation is only an option for small programs where data will not be retained. The systems shall be capable of fulfilling the basic criteria defined in the paragraph titled "Requirements for Compliant LSAR Software.
Packages" below. These systems sha ll be compliant by exhibiting proc essing capability to input, edit, and build LSAR relational tables and output the relational tables and standard LSAR reports. The independently developed LSAR. ADP system will be validated based on the following design criteria:. Shall be capable of automatically accepting relational table data in the formats displayed in Annex A, using the data elements, definitions, data element edits, data field lengths, and data relationships contained in Annexes A and E.
Shall be capable of outputting change only data from last delivery of LSAR data. Shall provide automated user comment capability. It may occur that large quantities of.
In order to reduce LSA Program costs, unnecessarily repeating of analysis should be avoided and conversion of the existing data to LSAR format should be pursued where cost-effective to do so. In this instance, access to the developing data should also be provided via access to the Performing Activity's data source.
Each data table contained in Annex A is identified by a three-position code. The first position of this code identifies the functional area most directly associated with the information contained within the data table. The second position uniquely identifies the table within a functional area. The third position may be used to insert additional data tables at a later date. Information for the "A" and portions of the "X" tables will be provided by the Requiring Authority and.
Cross Functional Requirements. The tables are used to record information from the Requiring Authority with respect to supply, maintenance and personnel data, which are.
Logistics support analysis
LSA, as applied in Defence expands LSA as a life Cycle Discipline to enable the benefits of consistent analytical techniques to be readily applied to major minor projects, modifications, In- service analysis for logistic optimisation, and disposal. The LSAR was developed to fulfil this requirement. Contains a description and the required format for each LSAR standard report. The main annexes for this course are Annex A and C. They developed standards to create LSARs that provided a standardised method for compiling and storing logistic and logistic related data for a program. The project selected Omega2B as the corporate application.
Logistics in a nutshell
Logistics Support Analysis LSA is a structured approach to increase efficiency of maintenance and reduces the cost of providing support by preplanning all aspects of Integrated Logistics Support. A successful LSA will define those support requirements that are ideal for the system design. Logistics Support Analysis was codified into a military standard in with the publication of Military Standard The Navy began a similar effort in These military specifications had only limited distribution typically only in their own countries and MIL-STD was still requested by many military procurement contracts in different countries even after its cancellation.
Def(Aust) 5692 LSAR