Logistic Support Analysis Records (LSAR)
A support system is only as reliable as the data behind it. Every maintenance task, spare part, and repair decision generates data that must be captured in a consistent format if it is to be trusted for the decisions that follow.
Logistic Support Analysis Records (LSAR)
A support system is only as reliable as the data behind it. Every maintenance task, spare part, and repair decision generates data that must be captured in a consistent format if it is to be trusted for the decisions that follow. Without a structured record of this information, each phase of the life cycle rebuilds support knowledge from memory and assumption rather than carrying it forward as a single, auditable source of truth.
What is a Logistic Support Analysis Record?
A Logistic Support Analysis Record (LSAR) is the structured database that captures the outputs of Logistics Support Analysis (LSA): every maintenance task linked to the parts, tools, technician skill level, and facilities required to perform it. Its purpose is to provide a consistent information source from which Integrated Logistics Support (ILS) data products, such as technical publications, provisioning lists, and training materials, can be prepared without re-deriving the underlying analysis each time. LSAR was formally defined in MIL-STD-1388-2B, the US Department of Defense standard for a Logistic Support Analysis Record published in 1991.
How an LSAR is structured
An LSAR is organized as a set of relational tables rather than a single narrative document. Each table defines its data elements as columns and the individual records that populate them as rows, covering areas such as failure modes, maintenance task analysis, support and test equipment, training, and supply support. Every item and task across these tables is tied together by an LSA Control Number (LCN), the reference that allows the record to be queried, audited, and reported against consistently. National standards have since extended this structure with additional data elements and reporting requirements, such as DEF(AUST) 5692 in Australia.
From MIL-STD-1388-2B to GEIA-STD-0007
MIL-STD-1388-2B was cancelled and its role taken over by GEIA-STD-0007, Logistics Product Data. GEIA-STD-0007 keeps the same underlying data elements: logistics design requirements, reliability and maintainability, maintenance engineering, support and test equipment, training, manpower and skills, facilities, transportation, and supply support. What it changes is the emphasis, moving from rigid relational data storage to structured data transfer using modern schemas, so that logistics data can move between contractor and customer systems without being locked into one database format.
From static record to live analysis
Treated as an archive, an LSAR is only a record of past analysis. Its value is realized when that data is put back to work: feeding Level of Repair Analysis (LORA), spares optimization, and life cycle cost modeling as those analyses are refreshed through the life of the system. Programs that keep LSAR or Weapon System Database (WSDB) content isolated in standalone, legacy systems typically re-enter this data by hand into each downstream analysis tool, introducing delay and breaking traceability between the original support analysis and the decisions built on it.
Opus Suite+ closes that gap. Opus Suite Connect automates the transfer of GEIA-STD-0007 and S3000L-compliant data directly into Opus Suite+ models, eliminating manual re-entry and preserving traceability from LSA and LSAR data through to LORA decisions, spares optimization, and life cycle cost analysis, all within the same environment that combines the optimization capability of OPUS10, the simulation capability of SIMLOX, and the cost analysis capability of CATLOC.
Frequently Asked Questions
What is a Logistic Support Analysis Record (LSAR)?
An LSAR is the structured, relational database that stores the data generated by Logistics Support Analysis, linking each maintenance task to the parts, tools, skills, and facilities it requires, so the data can be reused to prepare ILS data products rather than re-derived from scratch.
What is the difference between LSA and LSAR?
Logistics Support Analysis (LSA) is the analytical process that determines what will fail, how often, and what it takes to fix. The LSAR is the record that stores the data this process produces, structured so it can be queried, audited, and carried forward into later analysis.
What standard governs the LSAR?
LSAR was formally defined in MIL-STD-1388-2B (1991). That standard was cancelled and its function taken over by GEIA-STD-0007, Logistics Product Data, which retains the same data elements but structures them for modern data transfer rather than fixed relational storage. Some nations, such as Australia with DEF(AUST) 5692, have developed their own extensions to the original structure.
How does Opus Suite+ use LSAR data?
Opus Suite Connect ingests GEIA-STD-0007 and S3000L-compliant logistics data directly into Opus Suite+, so LORA, spares optimization, and life cycle cost analysis all draw on the same consistent source, without manual re-entry..
Related Article
Explore Opus Suite+
The modern evolution of analysis-driven Life Cycle Management
Opus Suite provides the advanced analytical capabilities that organizations rely on to make informed, data-driven decisions across the entire system life cycle. From concept and development through to operations and sustainment, it enables powerful modelling, simulation, and optimization to manage cost, performance, and readiness.
Opus Suite+ brings these proven capabilities together in a unified, modern application, combining OPUS10, SIMLOX, and CATLOC into a single environment. With an intuitive interface, streamlined workflows, enhanced visualizations, and AI and cloud-enabled capabilities, it delivers an improved user experience and more efficient, consistent analysis across the system life cycle.
Designed to help organizations manage complexity and act with confidence, Opus Suite+ enables better decisions, faster.
