Logistic Support Analysis comprises six main areas.:
RAM – Reliability Availability, Maintainability
FMEA – Failure Modes Effects Analysis
FMECA – Failure Modes Effects Criticality Analysis
RCM – Reliability Centred Maintenance
LORA – Level Of Repair Analysis
LCCA – Life Cycle Cost Analysis
LSA software is available to help automate the LSA process:
Logistic Support Analysis Software: eLSA
Logistic Support Analysis Record Software: LSAR
Maintenance Engineering Analysis (MEA).
FMEA, RCM, and MTA are also referred to as Maintenance Engineering Analysis (MEA).
The six areas of LSA
Videos related to Logistic Support for the International Space Station (ISS)
Logistics Support Analysis Software: eLSA
Logistics Support Analysis Record Software: LSAR
The purpose of a Logistic Support Analysis Record (LSAR) is to provide a consistent information source to support the conduct of Logistics Support Analysis (LSA) and related analyses, and enable the development and preparation ILS data products.
An LSAR applied effectively support analysis and achieves the fourth goal of LSA for both project and In- service use, to: “Develop and prepare attendant data products from a consistent information source.”
The purpose of this standard is to define the requirements for the application of a Logistic Support Analysis Record for and by the Organisation.
Detail record Requirements
LSA documentation, including LSAR data, is generated as a result of the analysis specified for the LSA Program. As such, the LSAR shall serve as the main Integrated Logistic Support (ILS) technical database applicable to all materiel acquisition programs to satisfy the support acquisition.
Annex A of DEF(AUST)5692 establishes the Logistic Support Analysis Record (LSAR) relational table titles and data content and format to be produced by an LSAR relational Automated Data Processing (ADP) system:
DEF(AUST) 5692
Logistic Support Analysis (LSA) is a selected application of system engineering techniques, originally developed by the United States Department of Defence (US DOD) to provide effective and consistent analytical processes for identifying and implementing supportability requirements for the development and acquisition of major capital equipment. 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.
A key enabler to the success of the LSA Program, and the fourth goal of LSA, is to use a consistent data source for analysis to ensure an integrated solution between LSA, Integrated Logistic Support and related disciplines. The LSAR was developed to fulfil this requirement. Defence has added functionality to the LSAR developed by the US DoD and defined in MIL-STD- 1388-2B.
DEF(AUST)5692 provides the definition of data elements and structure of the LSAR to enable the collection, storage, retrieval and review of the LSAR data.
The DEF(AUST)5692 is structured as follows:
· Chapter 1: LSAR Program Requirements
· Chapter 2: LSAR General Requirements
· Chapter 3: Detailed requirements for the Preparation of an LSAR.
· Annex A. Contains the LSAR relational tables necessary for the development of a relational LSAR database.
· Annex B. Contains a description and the required format for each LSAR standard report.
· Annex C. Explains assignment of the key data elements: LSA Control Number (LCN), Alternate LCN Code (ALC), Usable On Code (UOC).
· Annex D. Contains guidance for tailoring of the LSAR Data.
· Annex E. Contains an LSAR Data Element Dictionary providing definitions for all data specified by Annex A.
Chapter 3, Annexes A,B and E establish requirements and can be included/referenced in contractual documents. Annexes C and D provide guidance for the implementation of LSAR data entry and program application of the LSAR. The main annexes for this course are Annex A and C.
LSA data is generated in all phases of the system/equipment life cycle and is used as input to follow-on analyses and as an aid in developing logistics products.
Logistic Support Analysis Record Software: LSAR
Logistics Support Analysis Software: eLSA
Background and History
US DOD realised a need to store results of Logistic Support Analysis (LSA) in a single database.
They developed standards to create LSARs that provided a standardised method for compiling and storing logistic and logistic related data for a program.
The Australian Defence Force (ADF) began looking at using LSARs in the early 1990s.
They actually had copies of a MIL‑STD‑1388‑2A product called DILSA.
Australian Dept of Defence began looking at using LSARs in the early ‘90s with the establishment of the CAPLOG (Capital Logistics) project.
The CAPLOG project got serious about using LSARs and associated software apps in an attempt to truly apply the principles of Integrated Logistic Support (ILS).
The centre of the CAPLOG ‘hub’ was a MIL‑STD‑1388‑2B based LSAR.
The project selected Omega2B as the corporate application.
As the project matured, it was recognised that MIL‑STD‑1388‑2B in its current form would not fulfil the intended needs of the ADF for two main reasons:
As a result, AAP 5102.003 was developed (AAP stands for Australian Air Publication)
The ADF called their databases Weapon System Databases (WSDBs) as opposed to LSARs to highlight the difference between MIL‑STD‑1388‑2B and AAP 5102.003
Over time certain deficiencies were identified with AAP 5102.003 and these were addressed with the development of DEF(AUST)5692 (including an overhaul of MIL‑STD‑1388‑1A to become DEF(AUST)5691).
S1000D
Weapon System Databases (WSDB)
Facility, Asset and Fleet Management are very similar in many ways to Integrated Logistic Support (ILS).
They have the same sub functions as ILS:
Consider a ship or sub marine, which is essentially a building on / in a hull, it constitutes many common systems that require the same analysis and support that any facility or equipment might need:
Electrical
Electronic systems
Water
Waste water
Power Plant / Engine
Transmission
Stowage
Structure
Ancillary equipment
Ancillary Support equipment
Safety systems
The majority of the above also apply to aircraft and to many vehicle systems and of course to land based buildings.
Thus the same integrated logistic support techniques can be applied to non military equipment and facilities with the same benefits in terms of minimising down time and through life costs while maximising availability and performance.
Australian Asset Management
RAM is the assessment of the inherent reliability of an item or system,
which are then used to determine redundancy requirements, equipment quantity and maintenance resources required.
Videos related to Software Maintainability
Failure Modes Effects Analysis
Failure Modes Effects Analysisis is the analysis of HOW the equipment can fail and what is the effect of failure.
It is designed to identify potential failure modes for an item or system, to assess the risks involved with those failures, to categorise and order in terms of importance, and to identify and either put in place mitigations or institute corrective actions to address those that can be addressed.
Failure Modes Effects Criticality Analysis
Failure Modes Effects Criticality Analysis (FMECA) is the analysis of HOW the equipment can fail, what is the effect of failure and how critical is the failure.
It is designed to identify potential failure modes for an item or system, to assess the risks involved with those failures, to categorise and order in terms of importance, identify the criticality of the failure, and to identify and either put in place mitigations or institute corrective actions to address those that can be addressed.
Level of Repair Analysis
What is Level Of Repair Analysis?
Level Of Repair Analysis combines two elements:
Cost Analysis determines Whether maintenance should be performed; which includes all costs incurred:
Repair Level Analysis (RLA) determines Where the maintenance should be performed; this in turn determines where the equipment can be repaired:
Level of Repair Analysis Software : eLORA
Maintenance Task Analysis – MTA
Maintenance Task Analysis (MTA) is the study of WHAT specific tasks need to be performed to maintain the equipment.
Reliability Centred Maintenance
Reliability Centred Maintenance is the analysis and execution of Maintenance tasks focused on preventive replacements in order to maximise the operational period.
The focus on preventive maintenance is easily understood when consideration is given to the typical reactive type maintenance, ie “fix it when it breaks”.
In the typical reactive maintenance situation, the planned preventive maintenance gets delayed while resources are sidetracked performing emergency repairs to keep the system running after something has failed.
The delayed or cancelled preventive maintenance tasks then cause the system to be put at further risk due to it now operating beyond the planned / calculated maintenance periods. These operations beyond expected maintenance periods may place extra stress on the system, resulting in failure, diversion of maintenance resources to fix the failure, and a constant downward spiral in reliability. eg
It is the desire to avoid this type of downward spiral that drives Reliability Centred Maintenance, particularly for system critical functions. (Sometimes a failure in a piece of equipment is not critical to the operation of the system, so repair on failure is acceptable. eg a light bulb failure when there is sufficient light from surrounding light bulbs to allow operations in the area to continue.)