|
Original Date: 05/08/1995
Revision Date: 01/18/2007
Best Practice : Logistics Support Analysis Record
McDonnell Douglas Aerospace (MDA)-St. Louis Logistics Support Analysis Records (LSARs) document data from across all ILS functional areas. These LSARs, captured in an electronic database, provide an excellent example of the Continuous Acquisition and Lifecycle Support (CALS) concept of “create/store once, use many times.” The relational design of the LSAR data was designed to facilitate integration and to encourage the use of ad-hoc queries for accessing different data files. The LSAR provides an integrated product development/CALS environment that supports real-time access to information with a single point, on-line access to the logistics database. This access is provided through the use of the CALS/Contractor Integrated Technical Information Service (CITIS) node using a point-to-point methodology (Figure 2-25).
Prior to 1993, major programs distributed information in various databases and individual islands of information. This did not allow internal or external customers easy access to data; there was no on-line capability; the only means to obtain information was through hard copy; and there was no single point of access for LSAR data.
The logistics database now serves as a single source of information for all LSARs. Any data file can be generated through ad hoc queries as well as any discrete LSAR requested by the customer. MDA-St. Louis Logistics Support Analysis (LSA) has been extended to allow for Provisioning Technical Documentation and to tightly integrate the LSA/LSAR process to both the present Technical Manuals and the development process and emerging Interactive Technical Manual process.
The logistics database contains the three elements of SLIC-2B applications, 1388-2B LSAR, and Extension tables, and shares common processes, data, and applications. Two major aircraft programs currently use this logistics database for data storage. The LSAR allows data exchange, requirements roll-down, and support for various data delivery options (dependent on customer contractual requirements). Customers and/or vendors can interact with the MDA-St. Louis logistics database in several ways such as FTP, electronic data interchange, and from floppy disks.
Figure 2-25. CALS/CITIS Current Direction
For more information see the
Point of Contact for this survey.
|
