Many engineering organizations have a Logistics Support Analysis Records (LSAR) or Logistics Product Data (LPD) database solution, with analysis and documenting of equipment being the start point for the development of an asset or system. Within the LSA solution, engineers will develop the breakdown of the asset which will then become the definition of that item. Information that is often included in a more modern LPD database is:
- End Item Acronym Code
- Usable On Code
- System Level Usable On Code
- SNS (Standard Numbering System) for the asset
- Alternate Logistic Control or Alternate Indentured Product Code
These areas within the LPD solution will provide the method for building the Data Module Code (DMC) for the technical publication.
In addition to the ability to build the DMC, the LPD solution can also include core information or content for Descriptive, Procedural and Illustrated Parts Data. Common Information details, such as Warnings and Cautions, and illustrations are also included. By being able to retrieve this information from the LPD solution, the technical authors can reduce their documentation start-up time and costs by up to 30%.
R4i LTS provides the ability to have direct access to an OmegaPS database to retrieve this information. During the export process as well as creating the output types the linking between Procedural content and the information that has been populated within the Preliminary Requirements, such as tools, consumables and spares. The LPD database needs to have been built compliant to data structures such as:
- SAE GEIA-STD-0007
- ASD S3000L