Logistics support analysis

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.[1]

Part of a series on
War

History

Logistics Support Analysis was codified into a military standard in 1973 with the publication of Military Standard 1388-1. Logistic Support Analysis (LSA) guidelines and requirements were established by Department of Defense (DOD) Instruction 5000.2, Major System Acquisition Procedures, and DOD Directive 5000.39, Acquisition and Management of Integrated Logistic Support for Systems and Equipment, to create a single, uniform approach by the Military Services to improve supportability of military weapon systems through a disciplined approach to defining the required operational support other Integrated Logistic Support (ILS) objectives during the acquisition development phase. 1388-1A was updated in 1983 and 1991 before being downgraded from a standard to a best practice on 26 November 1996. 1388-2A was updated in 1991 and 1993, and was also cancelled as a standard in 1996.[2] The definitions for the database records of LSA were established by the Logistics Support Analysis Record, MIL-STD-1388-2A, on 20 JULY 84.[3]

In 1986, the US Army began to transform the paper-intensive LSAR into a desktop application known as “Computer Aided Logistics Support” (CALS). The Navy began a similar effort in 1987. In 1991, the programs were combined and expanded to all services under the name Joint CALS (JCALS). JCALS was approved for use in August 1998.[4][5][6]

In 1996, as part of the OSD Mandate For Change, MIL-STD-1388 was cancelled. It was briefly replaced by MIL-PRF-49506[7] while a "civilian" replacement was being sought.

Alternative military specifications from other countries appeared as a replacement for MIL-STD-1388, namely DEF STAN 00-60 by the Ministry of Defence (United Kingdom)in 1998 (later replaced by DEF STAN 00-600 in 2010) or DEF (AUST) 5692[8] by the Australian Department of Defence in 2003. These military specifications had only limited distribution (typically only in their own countries) and MIL-STD-1388 was still requested by many military procurement contracts in different countries even after its cancellation.

Due to the disappearance of MIL-STD-1388, two "civilian" initiatives appeared to replace the LSA process. One was developed within the framework of the Government Electronics and Information Technology Association (GEIA), which lead to the publication of GEIA-STD-0007,[9] and associated GEIA-HB-0007[10] by the SAE International in 2007. The second one was the S3000L, published by the Aerospace and Defence Industries Association of Europe in 2010.[11] While the GEIA specification is mainly used in the US and only for military programs, S3000L has been more widely adopted, mainly in Europe, but also outside it for both civilian and military projects.

MIL-STD-1388 Structure

As originally envisioned, the LSA data was structured as a LSA Record (LSAR), as defined by MIL-STD-1388-1A (records) and MIL-STD-1388-2A (outputs)

Tasks:

100Programming, planning and control
200Mission and support system definition
300Preparation and evaluation of alternatives
400Determine logistics support resource requirements
500Supportability assessment

LSAR output was structured as:

15 Data records
115 Date cards
547 Data elements
80 STD report formats
104 Relational tables
518 Data elements
48 STD report formats

A similar structure was used by DEF STAN 00-60 and DEF (AUST) 5692.

gollark: SQLite is able to make it work *fine* with entirely variably sized everything.
gollark: Performance is for people who care about performance.
gollark: I don't like fixing the maximum size of things like that, since what if the path is somehow LONGER than that? WHAT THEN‽
gollark: And copying p[EXPUNGED] constantly would be irritating.
gollark: I mean, I can *copy* them for quoting messages, but not *type* them.

See also
  • Level of Repair Analysis
  • Logistics management
  • Military acquisition
  • Military logistics
  • Product life cycle management
  • Blanchard, Benjamin S. Logistic Engineering and Management Publication Date: March 10, 1998 | ISBN 0139053166 | ISBN 978-0139053160 | Editor's review: An authoritative exploration of logistics management within the engineering design and development process, this book concentrates on the design, sustaining maintenance and support of "systems." Deals with " logistics" from a total "systems/life cycle" perspective" and includes those activities associated with the determination of requirements, the design, development, production, utilization, sustaining maintenance and support, and retirement of systems." Emphasizes the importance of addressing logistics in the early phases of the system life cycle, including: design engineering aspects and design of systems for supportability.

References
  1. "Archived copy". Archived from the original on 8 July 2012. Retrieved 31 December 2014.CS1 maint: archived copy as title (link)
  2. MIL-STD-1388
  4. http://www.dote.osd.mil/pub/reports/FY2000/army/00jcals.html
  5. http://oai.dtic.mil/oai/oai?verb=getRecord&metadataPrefix=html&identifier=ADA183948
  6. http://www.plm.automation.siemens.com/en_us/Images/lsar%20wp%20W%201_tcm1023-5601.pdf
  7. MIL-PRF-49506, Logistics Management information, 1996
  8. DEF (AUST) 5692, Logistic Support Analysis Record Requirements for the Australian Defence Organization, dated 1 March 2003
  9. GEIA-STD-0007, Logistics Product Data
  10. SAE GEIA-HB-0007, Logistics Product Data Handbook, 2007
  11. S3000L - International specification for Logistics Support Analysis - LSA
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.