The All-Source Analysis System at DCX II - ASAS - TSM Notes - ASAS Remote Workstation - Brief Article

Military Intelligence Professional Bulletin, Jan-March, 2002 by Michel M. Strack

In October 2001, the U.S. Army Training and Doctrine Command (TRADOC) System Manager (TSM) ASAS participated in the successful Division Capstone Exercise Phase II (DCXII) held at Fort Hood, Texas. This was a good opportunity to observe the prototype ASAS Remote Workstation (RWS) Version 6.2.1 software in a command post exercise (CPX). While much work remains to be done, the results were encouraging. Presented below is a brief discussion of some problem areas and possible solutions.

Problem Areas and Operator Concerns

The most significant problem continues to be with the stability of the common tactical picture (CTP). DCX II produced 38 known trouble reports generated due to problems with the CTP; these reports described the system's inability to send, receive, or plot operational overlays from the CTP Explorer due to lock-up and booting problems. Throughout the CPX, the tactical operation centers (TOCs) observed that when the CTP was stable and operational, the analysts sometimes had to input graphics multiple times. Thus, aside from probing into the various stability issues, we are also looking at developing a way to convert ASAS overlays to operational overlays and vice versa.

Soldiers experienced with the RWS Version 4.3 systems were generally disappointed with the Version 6.2.1. The common complaint was that the intelligence functions in the Version 6 system did not meet the standard set by the earlier version and the overriding concern was that the Version 6 system is inflexible and unreliable. However, many of the soldiers' concerns were actually with the Army Battlefield Command System's (ABCS) foundation software rather than the Version 6 ASAS. Observations of the RWSs revealed unexplained lock-ups and screen freezes when multiple operations and processes were running in the background. When the operators updated their databases with new information, the systems would often lock during the data entry. As usual, the soldiers and contract technicians were able to find "work-arounds" like minimizing the other processes running at the same time; this increased system stability and restored reasonable processing speeds.

Solutions

TSM ASAS is committed to support the digitalized Army. To shift our focus from the "boxes" to the baffle, we are examining improved ways to transfer data between computers and systems. We will overcome the software complexities and improve the reliability and stability of our systems. In doing so, we focus on supporting the transformation effort at the U.S. Army Intelligence Center. One area that must continue to evolve is the training of competent digital operators--at both the initial entry and advanced levels--who are proficiently trained on ASAS with good understanding of the total ABCS Version 6 environment. Training should start with a familiarity of the ABCS products and later include the basic cross-system troubleshooting.

Mr. Michel Strack is the Acting TSM for ASAS. Readers can contact him via Email at mike. strack@hua.army.mil and telephonically at (520) 533-3504 or DSN 821-3504. The Deputy TSM is Lieutenant Colonel Vic Fink. Readers can reach him by E-mail at james.fink@hua.army.mil and by telephone at (520) 533-5145 or DSN 821-5145.

COPYRIGHT 2002 U.S. Army Intelligence Center and School
COPYRIGHT 2004 Gale Group
 

BNET TalkbackShare your ideas and expertise on this topic

Please add your comment:

  1. You are currently: a Guest |
  2.  

Basic HTML tags that work in comments are: bold (<b></b>), italic (<i></i>), underline (<u></u>), and hyperlink (<a href></a)

advertisement
advertisement
  • Click Here
  • Click Here
  • Click Here

Content provided in partnership with Thompson Gale