• Military Menu                       

• Introduction
• Systems
• Facilities
• Agencies
• Industry
• Operations
• Countries
• Hot Documents
• News
• Reports
• Policy
• Budget
• Congress
• Links

• WMD
• Intelligence
• Homeland Security
• Space

	Director, Operational Test & Evaluation
	FY98 Annual Report

SYSTEM DESCRIPTION & CONTRIBUTION TO JOINT VISION 2010

Information superiority underpins the operational concepts outlined in Joint Vision 2010. Intelligence provided by the All Source Analysis System (ASAS) allows commanders to identify key points for dominant maneuver and find high priority targets for precision targeting. ASAS contributes to attaining information superiority through a network of computer workstations that process and exchange sensor data, fuse multi-source data into a single intelligence picture and supports management of intelligence sensors. ASAS is tactically deployable to support intelligence and electronic warfare operations at battalion through echelons above corps.

ASAS requirements were approved in 1986. Subsequently, the requirements were structured so that the ASAS capability could be developed, acquired and fielded in discrete increments or blocks. ASAS Block I successfully completed OT in 1993, and is fielded to priority divisions and corps throughout the Army. The current development focus is on Block II.

Lockheed Martin Astronautics is developing ASAS Block II as a series of phased capability packages-a Single Source (SS) workstation, a collateral Remote Workstation (RWS), and an Analysis Control Element (ACE). . The Single Source workstation completed a Limited User Test in June 1997. The Single Source capability package was found neither operationally effective nor suitable and was not fielded. The Army and DOT&E defined an appropriate test program to support fielding of the Block I software on the Block II hardware. The Army successfully ported the Block I Single Source software to the new Common Hardware. The porting solves logistics supportability issues with the older hardware. It also addressed the Y2K problem for the existing Block I Single Source. The Remote Workstation began its first phase of OT in December 1998, and will complete the second phase in March 1999. The Analysis Control Element OT is anticipated in FY00.

The past year has been spent defining the operational test program for the ASAS Block II program. The T&E strategy uses all opportunities to gather information but emphasizes an operational focus. The challenge is integrating the various events into a coherent test program.

ASAS BLOCK II TEMP was approved in March 1997. This TEMP is undergoing revision due to changes in the ASAS Block II acquisition strategy.

The ASAS T&E program is moving towards a greater operational mission focus. The proposed program includes operational tests that are more than the traditional standalone ASAS exercises. The increasing integration of staff activities and automation requires operational testing to include other staff units and their automated systems in order to evaluate the operational contribution of the ASAS. A test strategy that addresses relevant issues using multiple events increases both the quality and quantity of information to support the ASAS acquisition decisions for the remaining capability packages. Continued coordination and exchange of concepts among the various systems are required to successfully plan and execute the test program that is being defined for the remainder of the ASAS Block II effort.

The rapid pace of development through Advanced Warfighting Experiments and Advanced Concept Technology Demonstrations can surpass the requirement process. The development of the RWS is a good example where system development far outpaced approved Army requirements. For the OTA, identifying the actual system requirements, vice listing system capabilities, is a challenge. The lack of mission-level system requirements complicates efforts to develop an adequate T&E program.

To be realistic, information systems must test functionality and verify interoperability with all available operational interfaces using a sample of real world messages not only simulated messages. In the developmental testing of the SS, simulated message traffic was used with no major problems encountered. However, during the Limited User Test, the SS workstation only processed about 20 percent of real message traffic. This was the main factor in judging the workstation neither effective nor suitable.