LSA Data Creation Activities

Follow-on LSA Data Modification

LSA Data Management

LSA Data Uses During the Acquisition Process

LSA Data Uses During the Operational Phase

CALS Support Related Questions

LSA Data Creation Activities

The first level of activity during the acquisition phase of a programme is the creation of the data. The acquisition project manager is the primary focal point during the creation phase. Of utmost concern to the project manager from a CALS perspective, should be the assurance that the data is developed once and then used many times. The ability to review and/or access LSA data by all areas involved in the design process ensures early identification and quantification of support systems requirements as well as the best design for supportabilty. The project manager must ensure that the internal contractor product development team members, as well as NATO/NATO nations reviewing agencies, have access to current and relevant LSA data.

The ability to access and review digital data is driven by the availability of appropriate infrastructure. The project manager should ensure all functional areas are addressed in the NCoO and that the appropriate infrastructure is in place or will be phased-in as the acquisition progresses prior to contract placement.

Of equal importance, the project manager should ensure that support activities are aware of LSA data access, review and approval methodologies, and the roles and responsibilities each activity will play.

Follow-on LSA Data Modification

In addition to concerns associated with the creation of LSA data, the project manager should consider future requirements to modify the data. It is of particular importance to ensure that all Front End Analyses studies, as well as the LSAR database, are made available on digital media to the depot or support agency in a usable format. By doing this, the depot and/or support agency will be provided not only with the LSAR database that supports the design, but also with the analyses and studies used to arrive at the design.

LSA Data Management

The second level of activity is associated with the management of LSA data during both the acquisition and operational phases. It should be noted that "LSA data management" will be afforded the same management controls as any other technical data acquisition, but with the emphasis being on digital delivery or electronic access.

The project manager must consider the specific NATO/NATO nations infrastructure program that will manage and store the digital data during both phases. The data delivered must be compatible with the existing digital NATO/NATO nations systems in place or being developed. If changes to the digital NATO/NATO nations infrastructure systems are required, they must be fully justified and coordinated with the personnel responsible for the management and configuration control of LSA data.

During the operational phase, the LSA data is typically assigned to a support organisation such as a Depot or organic NATO/NATO nations Data Repository. Of primary importance here would be making data available to potential users and maintaining configuration control.

LSA Data Uses During the Acquisition Process

The final level of activity is associated with the use of LSA data. During the Acquisition Process, LSA data is typically used in three ways:

• First, the logistic support analysis (MIL-STD-1388-1A) Front End Analysis 200 and 300 series tasks are used to influence and provide a basis for the design of the system (both the hardware and the support elements required for deployment and use).
• Secondly, the LSAR database is used to capture the system's configuration and maintenance/ support requirements and procedures.
• Finally, the LSAR database is used as a cornerstone for the developing ILS element products that include technical data, training data, supply support data, etc.

Paramount to ILS product development is the timely access to current and accurate LSA data. The following are just a few of the considerations the project manager should make when contracting for LSA data:

• Technical Data: Since the technical data functional area has access not only to LSAR data, but also to technical drawings and associated supply support data, the project manager must ensure this data is closely managed for the development of data products such as Technical Manuals (TM). The LSAR tasks analysis (LSA-Task-401) is a basis for, and/or a direct input to the system's TM(s). The project manager should ensure that the development of the TM(s) and the detailed LSA task analysis are orchestrated in such a manner as to eliminate duplicate efforts.
• Training and Training Support (T&TS) Data: This functional area takes information from the LSAR and uses it as source data to develop the training plans and various other training products. An important CALS-related consideration would be to ensure the training-related LSA source data for the training development are in a usable digital format.
• Supply Support: Supply support and initial provisioning efforts take direct advantage of the data contained within the LSAR database.
• Support Equipment: Support Equipment Recommendation Data (SERD) information is typically generated during the LSA process and captured within the LSAR database.

LSA Data Uses During the Operational Phase

A major concern to the project manager is the accuracy of the LSA data during the operational phase of a programme. The project manager should ensure that both LSA Front End Analysis data and the LSAR database are made available and/or maintained by the support organisation for both configuration control and evaluation of potential Engineering Change Proposals (ECP) during the operational phase.

One additional area of major importance concerns the end users. The end users perform a vital feedback function with LSA Task 501. Knowledge of actual usage of the data when fed back into the LSA process is invaluable in correcting design and support system deficiencies. The project manager must not overlook this vital source of data and should consider the end users when acquiring digital data and feedback methodologies. In conclusion, the project manager must include in the decision making process the infrastructure that exists at all user sites being considered.

It is counterproductive to generate and make available to the end users digital data that they do not have the capability of using. The project manager cannot assume the infrastructure exists and will be used. The end user's specific environment must be determined.

CALS Support Related Questions

• What systems are available in the field and at support organisations?
• How is the data to be used by the field/support organisations?
• For specific users, what data media and formats are compatible with what equipment/systems they already have or are planning to acquire?
• How will they acquire the new equipment and software needed if existing systems are inadequate?
• How will these new systems be supported?

The answers to these and similar questions will provide a comprehensive plan for implementing and using the digital data that is acquired. The answers are dependent on the individual users in the specific acquisition programme.