Potential Sources of LSA Data
Managing/Maintaining LSA Data
Using LSA Data in the CALS Environment
CALS Effects on LSAR Report Requirements
Interaction of LSA Data with Concurrent
Engineering/Integrated Design
Specific CALS Considerations Affecting
Data Acquisition
Migration of LSA Data into ILS Element
Products
The four prime factors that govern system acquisition programs
are cost, schedule,
performance, and supportability. The LSA process provides direct
input into the supportability
and cost factors associated with a system/equipment and,
therefore, provides significant input
into system/equipment decisions. The CALS environment offers the
opportunity through digital
application of the LSA process for reductions in Life Cycle Cost
(LCC). The ability to create data
once (including LSA, engineering, and ILS data) and use it many
times impacts the cost of the
LSA process and the follow-on support costs. If the LSA data and
associated analyses are
created in a digital format, then digital data required for the
LSA can be linked and fed to the
LSAR database in an automated fashion. The initially created LSA
data is then available for use
in all technical data products.
The project manager must consider the digital format, media, HW/SW issues, required framework, architecture, and NATO military customers' infrastructure when developing the NCoC concurrently with selecting LSA tasks. Harmonized MIL-STD-1388-2B/AECMA 2000M/AECMA 1000D, when completed, should be required for all new procurements. Also, the instructions to offerors could indicate that the digital application and delivery of LSA data will be weighted strongly in the evaluation of the offerors' "Contractor's Approach to CALS (CAC)" response.
The digital application of data must start with the onset RFP/RFQ process. Project managers should begin by providing Customer Furnished Information (CFI), including the LSA strategy and ILS planning information, in digital form to the contractor. Digitizing these products will help reinforce the NATO/NATO nations commitment to CALS, as well as reduce costs and improve communications.
Populating the LSAR database can be aided by a well defined LSA Plan (LSAP). The project manager should require that this plan define not only who in the Contractor's organization is responsible for generating and receiving LSA source data, but also in what form the data should be developed, and how the Contractor plans to import this data into the LSAR database. Populating the LSAR database would be simplified if the LSA data existed in a digital format and data needed could be easily extracted for input. The amount of preparation and maintenance of the LSAR database is directly related to the complexity of the hardware and software end item design.
The project manager will decide whether the weapon system's data will be maintained under a Contractor Integrated Technical Information Service (CITIS) arrangement or other digital means of delivery to the NATO military customer. (See Section 5 of this Handbook for more information on CITIS.)
In either event, the decision process in determining the LSA data required will be the same. Considerations must be made that encompass all life-cycle phases from design to disposal. The project manager must be aware of the infrastructure systems available that will be affected and possibly use the LSA digital data created. The project manager must keep abreast of NATO/NATO nations programs that may create and/or use LSA data.
Using LSA Data in the CALS Environment
This subparagraph will focus on the current capabilities of CALS to employ and use the data that exists in the LSA database. Distinctions between MIL-STD-1388-2A and MIL-STD- 1388-2B will be discussed only where relevant to digital data interaction. Emphasis will be placed on creating the data once and using it many times. The unique effects of a shared digital environment on the current use of the LSAR database will be investigated and discussed.
CALS Effects on LSAR Report Requirements
In the past, the completeness and accuracy of the data has typically been verified by the contractor demonstrating the ability to produce various output reports from the LSAR database. The project manager is encouraged to shift emphasis from the delivery of the LSA reports to the delivery of, and/or preferably the access to, the LSAR database itself. In doing this, the verification of the database and its accuracy and completeness can be more easily and accurately assessed. However, prior to using this approach, the project manager must ensure that infrastructure is in place to accept, process, manage, and validate the LSA data.
Interaction of LSA Data with Concurrent
Engineering/Integrated Design
The LSA process is iterative in nature. The LSAR database provides a structured, uniform, yet flexible/tailorable approach to the documentation of the data that results from accomplishing various LSA tasks. As such, the LSA process is an effective tool to aid in the application of concurrent engineering initiatives.
To be effective, the systems engineering LSA process must be initiated early in the acquisition life cycle, and must be updated through LSA process iteration to reflect changes in the hardware design and support concept, and must be tailored to be commensurate with individual program requirements, constraints, and characteristics. This is consistent with concurrent engineering/integrated design as all life-cycle support considerations are being considered at each phase of the development process.
Specific CALS Considerations Affecting Data
Acquisition
During the analysis of the supportability portion of the LSA process, LSA data is used as a primary source for the development of data products associated with ILS elements such as provisioning lists, personnel and training requirements, and technical data products. This assures compatibility among ILS element products and permits common use of data that apply to more than one logistic element.
The CALS infrastructure available to the project manager when he is ready to issue an RFQ/RFP must be considered. Delivery of the LSA/LSAR data/database may be via digital media (magnetic or optical media) or can be made available under a CITIS requirement. The media selected will be driven by factors including infrastructure and data access needs.
Migration of LSA Data into ILS Element Products
For the proper migration of LSA data to be complete and in full support of all ILS element products, the concurrent engineering concept must also be implemented. The project manager must task the contractor to support the movement of LSA data into the design process and vice versa. The LSA tasks and LSA data captured is driven by the requirements as set forth in the acquisition contracts.
The LSA data and resulting LSAR database is then used as input data for decisions to develop various ILS element products including training programmes, support equipment, facilities, supply support, manpower and personnel lists, environmental impact, parts control, and so on. It is essential that coordination and interfacing of engineering disciplines and ILS functional elements be effected to maximize the usage of data developed by each program element, thereby realizing the economy of consistent and accurate information, and avoiding the generation of incompatible ILS products. Again, we want to create the data once and use it multiple times.