Logistic Support Analysis (LSA ) or Supportability Analysis SA
ILS is the overall management and integration function with Logistic support analysis (LSA ) or Supportability Analysis SA (LSA/SA) being the analysis process which defines the support requirements and solution.
Design the Support and then Support the design
The objectives of LSA/SA
To influence design, through of the assessment of the proposed system design and the assessment of the impact of the operational environment, it is possible to identify the support resources required.
To identify total resources, through combining the identified resources into a complete set of resources.
To control analytical effort, this is a major element of the LSA/SA process. Many projects have over analysed and as a result spent too much time and money for little return. This is a reason the ILS and LSA has suffered a bad reputation with project managers who perceive an expensive function without significant benefits to their project.
This is also an issue where the benefits from performing LSA/SA are only gained by the end user not the producer or Purchaser as any savings later in the life cycle. This is specific to the Military as there is a procuring organisation which aims to buy systems as cheaply as possible and they do not have responsibility for the in service life cycle costs, as a result LSA/SA is seen to be a cost which no up front benefit.
The LSA/SA process must consider the Operation and support costs and identify what are the cost drivers and then what alternatives might be appropriate.
A major element of the development of a support solution is the analysis of the system Reliability & modes of Failure, this analysis provides the justification for maintenance tasks to either stop or prevent a failure or to fix the system once it has failed this leads to the preventative and corrective maintenance tasks. LSA/SA then moves on to Maintainability now there is a list of tasks how easy is it to carryout the maintenance and especially if a task is required more frequently then how easy to complete the task is even more important.
If you know what and how often a component will fail then it is possible to define what spares are required to enable the repairs to be completed. then the numbers of spares can be optimised to make sure that not too many spares are purchased.
And finally from a business logistic view point, knowing the way and how often the system will fail means it is possible to develop a view of what Warranty can be offered and what it might cost the company if it is offered.
Design to LCC
Repair vs. Discard decisions
Repair level (I/Base vs. depot /remote)
Contractor vs. own depot repair options
h/w configuration (options)
Safety and Human factors
Technology used in design vs. post production support
Testability/built in test options