The All Source Analysis System (ASAS) is a network of computer workstations that processes and exchanges sensor data, fuses multi-source data into a single intelligence picture, and supports management of intelligence sensors. It is tactically deployable, supports intelligence and electronic warfare operations at battalion through echelons above corps, and provides interoperability with joint intelligence and sensor systems. Intelligence provided by ASAS allows commanders to identify key points for dominant maneuver and find high priority targets for precision targeting.

The original ASAS requirements were approved in 1986. Subsequently, the requirements were structured so that ASAS could be developed, acquired, and fielded in discrete increments or blocks. ASAS Block I successfully completed its Operational Test (OT) in 1993 and is fielded to selected theater, corps, and division units throughout the Army. The current Block II development is structured so that the interim capability is attained through a series of stand-alone products that can be tested and fielded when they are ready. The ASAS Remote Workstation (RWS) began fielding after completing its OT in March 1999. An upgrade to the Communications Control Set obtained a conditional material release in June 1999 following a series of developmental tests. The Analysis Control Team Enclave (ACT-E), a shelter for the team at brigade, successfully completed testing and started fielding in September 2000. The future ASAS Block III is the objective capability.

Planning continues for the remaining ASAS Block II products. The focus for CY02 is testing of the ASAS Remote Workstation implementing the Army Battle Command System (ABCS) Version 6 software. Planning also continues for the FY03 Analysis and Control Element operational test that will serve as an IOT&E for the ASAS Block II and support a full-rate production decision. The Army is exploring combining the Block II IOT&E and Distributed Common Ground Station testing.

The ASAS Light, a downsized, laptop version of the ASAS RWS at battalion, obtained a conditional material release and began fielding in FY01 supported by the Army's Limited User Test (LUT) assessment conducted in FY00.

The ASAS Light LUT conducted in FY00 showed that it provided the required functionality and contributed to intelligence preparation of the battlefield and planning in the battalion. However, contributions to the firefight were limited due to poor integration into the unit's operations, integration of digital technology into tactical command posts, and connectivity using existing combat net radio networks. Corrections to these shortcomings will be assessed again during the ASAS RWS operational test events planned for CY02.

There were no tests conducted in FY01 on the ASAS components. However, a significant issue for the upcoming assessment of the ASAS RWS in CY02 is the synchronization of ABCS Version 6 software testing and acquisition decisions. The ABCS Version 6 software is an integrated suite of applications comprised of independent acquisition programs (ASAS, Maneuver Control System, Advanced Field Artillery System, Forward Area Air Defense, Combat Service Support Command and Control, Force XXI Battle Command Brigade and Below). The ability to test, acquire, and field any component of the ABCS independent of the others is problematic; an appropriate strategy by the Army remains unclear.

Evaluation of the ABCS components as individual programs is becoming more difficult as the Army continues to integrate the software and foundation products that comprise these systems, as well as integrate the information into the Common Tactical Picture. An assessment of operational effectiveness and suitability is no longer limited to what the system provides within a single functional area (intelligence for ASAS), but now expands to what does the integration of that information with other functional areas provide to the commander's ability to prosecute the mission. Testing must be executed with all the ABCS components present to assess operational effectiveness and suitability. The Department should begin to look for Capstone acquisition, development, testing, and fielding strategies to more effectively and efficiently support, fund, and synchronize the ABCS programs.