[Back]
[Index]
[Next] 		Warfighter Guide to Intelligence 2000

All Source Analysis System (ASAS)

Chapter 5 *
ASAS *
ASAS System *
ASAS Block I *
ASAS Block II *
ASAS CI/HUMINT SUBSYSTEM *
ASAS CI/HUMINT SUBSYSTEMS *
CI and INTG OPS WS. *
ACE ASAS CI/HUMINT Single Source (SS) Workstation (WS). *
  • ASAS
    •

    The All Source Analysis System (ASAS) is the Intelligence and Electronic Warfare (IEW) Battlefield Functional Area (BFA) component of the Army Battle Command System (ABCS). ASAS is an automated intelligence system that helps the commander rapidly gather, record, analyze, and disseminate the often-overwhelming volume of data available on the battlefield. ASAS will interface with the automated Command and Control (C2) and intelligence processing systems of the Joint Task Force (JTF) and components over tactical communications systems ranging from IEW special purpose, Area Command User System (ACUS), and Army Data Distribution Systems (ADDS) combat net radio. ACUS includes Mobile Subscriber Equipment (MSE), TRI-TAC communications, STU-III, and the Defense Messaging Service (DMS)/AUTODIN. This will permit military intelligence units and Army intelligence staffs to respond to the maneuver commander’s Critical Information Requirements (CCIR) and Priority Intelligence Requirements (PIRs).

    Commanders seek to achieve information dominance at the right place, the right time, and in the right circumstances to gain a relative advantage of position (maneuver) and/or massing of effects (firepower). Commanders achieve information dominance by gaining an information/knowledge advantage over an adversary. The collection, processing and dissemination of relevant information and intelligence (RII) is key to the process of achieving information dominance. The ASAS assists the warfighting commander in shortening his decision-making process in the areas of Battle Command and Information Operations (IO). It rapidly processes and correlates large volumes of combat information and sensor reports from all available sources to produce a composite, all source, near-real-time picture of the battlespace and provides timely and accurate targeting information and other RII to the Commander and his battle staff. This RII aids the commander to visualize the multidimensional battlespace, synchronize operations and achieve temporary information dominance in planning and conducting his decisive, shaping and sustainment operations.

    ASAS is the IEW component of the ABCS from battalion through Echelons Above Corps (EAC). It is a mobile, tactically deployable, computer-assisted IEW processing, analysis, fusion, dissemination and presentation system. It is employed during peacetime and wartime operational environments and is capable of continuous operation 24 hours a day, 7 days a week for extended periods of time. Its hardware and software modularity allows it to be tactically tailored to provide intelligence support to early entry forces as part of a Deployable Intelligence Support Element (DISE) or operate in a split-based mode of operations. It is also capable of maintaining operations at a degraded level during tactical redeployment for survivability.

    ASAS provides all-source intelligence operations in a collaborative environment. It can access and leverage national, EAC and Echelons Corps and Below (ECB) analysis databases and collection assets to enhance local and multi-echelon situational awareness, battlespace visualization, and promote synchronized operational planning and execution. It’s automation capabilities support intelligence and information management. This includes interface data handling, coupling IEW sensors and preprocessors. These capabilities permit ASAS, and the ABCS, the capabilities to meet the timeliness and accuracy requirements, to support IO planning and execution, and to secure the force.

    ASAS operates in the "system high" security mode of operation and processes both collateral and Sensitive Compartmented Information (SCI). It interfaces with standard Army communications systems as well as IEW special purpose communications systems e.g., Joint Worldwide Intelligence Communications System (JWICS), and TROJAN Special Purpose Integrated Remote Intelligence Terminal (SPIRIT). ASAS also provides the capability to process General Service (GENSER) and Defense Special Security Communications System (DSSCS)) record message traffic; and simultaneously maintain both SCI and collateral interfaces. The objective system (Block III) will be capable of operating in the "multi-security level" mode of operation and support direct computer-to-computer data exchanges across the Defense Information Systems Network (DISN), Army Common User System (ACUS) and Intelligence special user communications at both the collateral and SCI levels. The figure below depicts how ASAS is organized and provides a high level view of how information exchanges occur.

     

    1. ASAS System

      2. (a) ASAS Analysis and Control Element (ACE) Subsystem. The ASAS components of the ACE subsystem are under the operational control of the echelon G2/S2 and provide the Military Intelligence (MI) Analysis and Control (A&C) organization of the echelon the means to perform its doctrinal IEW mission and functions. The ACE subsystem provides the capability to automatically receive, process, analyze, store, and fuse combat information and intelligence into a variety of products and reports, allowing the commander to gain a superior situational understanding of the battlespace and develop windows of information superiority that support shaping decisive and sustainment operations. The ASAS ACE workstations are connected internally, by a local area network (LAN), to provide a distributed processing environment for accessing and managing intelligence data and information. In the Block II timeframe, these operator workstations will have the flexibility of being totally reconfigurable based on the commander’s mission needs.

      (b) ASAS Remote Workstation (RWS) Subsystem. The ASAS RWS subsystem operates within the existing IEW BFA and ABCS architectures to provide automation support to G2/S2 intelligence staff elements and other designated intelligence organizations from maneuver battalion (called ASAS Light) through EAC. It operates at the security level appropriate to its echelon, mission, and functions. It assists the G2/S2 in providing IEW support to the commander and other staff elements in planning, coordinating, and conducting current and future tactical operations. It interfaces with the SCI ASAS ACE subsystem to provide operational guidance and to exchange IEW information and products. It also operates as the technical control portion of the IEW C2 node of ABCS to provide current IEW and enemy situation information to the Joint Common Database (JCDB) for access and use by ABCS users. Two RWS are provided to the BDE Analysis and Control Team (ACT) of the DS MI Co, to process data input from DS collection systems, and filter intelligence data from broadcast systems, and pass tactically relevant enemy situation information or situation development data to the BDE S2 RWS.

      (c) RWS functionality. Dissemination and simplicity are the key to maximizing RWS functional capabilities. RWS functionality includes:

      Overlay Creation – Courses of action, decision support templates, current situation, intelligence preparation of the battlefield (which can be stored in a database).

      Database Management – Simple "point and click" – overlay, equipment, installation, etc.

      Data Communications – Overlay transfer (with some data) database transfer and quality control.

      Data Reporting – Preprocessors/sensors/simulation to ASAS, Unmanned Aerial Vehicle (UAV)/Common Ground Station (CGS), JSTARS, etc.

      Horizontal Feeds – Red situation awareness, and targeting.

      Internet (LAN/TOC level only) Web Server – Distribute to other servers to reduce communication over-load challenges.

      Collection Management – Key on asset management.

      (d) The Counter Intelligence (CI) and Human Intelligence (HUMINT) Subsystem. The CI/HUMINT subsystem operates in two distinct realms – intelligence reporting to the supported command and intelligence reporting to the Defense Counterintelligence Information System (DCIIS), in support of the Defense Intelligence Agency. These operations include intelligence reporting to the ARFOR/JTF commander, and/or intelligence reporting in support of theater/national command elements. CI/HUMINT assets will operate in GS, GSR and DS missions. In support of theater/national level intelligence requirements, the ASAS CI/HUMINT Subsystem provides the information flow from the supported command’s G2 Counter Intelligence (CI) officer via the DCIIS. Analysts located in the ACE, produce a fused intelligence product that supports all-source intelligence production, force protection and target development. Size, activity, location, unit, time, and enemy (SALUTE) report data from subordinate units are the most frequently generated HUMINT and will be the primary source of information used for this production mission. CI and SALUTE reports will be received and disseminated automatically. A more detailed description of the ASAS CI/HUMINT subsystem is presented in a later section of this guide.

      (1) EAC

      (a) Intelligence Support Element (ISE) RWS. The ISE RWS collocates with the supported command and assists in identifying IEW requirements, establishing priorities, and in providing access for the supported command to the EAC Intelligence Center (IC), its analysts, expertise, and products. The ISE RWS maintains continual contact with the collection management and all source production elements of the EACIC. The "need to know" and protection of classified information/data files dictates what information, data files, and products may be exchanged between the EACIC and the supported command. When feasible/appropriate, the ISE RWS also accesses data files and intelligence generated, by the supported command, for dissemination to the EACIC.

      (b) Battlefield Coordination Detachments (BCD) RWS. Also at EAC, the Battlefield Coordination Detachment (BCD) is the liaison interface for a joint force. The BCD is provided by the Army Component Commander (ACC) to the Air Operations Center (AOC) and/or to the component designated by the Joint Force Commander (JFC) to plan, coordinate, and deconflict air operations. The BCD processes Army requests for tactical air support, monitors and interprets the land battle situation for the Joint AOC (JAOC), and provides the necessary interface for exchange of current, operational, and targeting data. An ASAS RWS can provide the joint force BCD intelligence section with the necessary connectivity with the Army intelligence system supporting the ACC and other service intelligence organizations.

      (2) ECB

      (a) Corps and Division G2 RWS. The corps and division G2 RWS are consumers/users of preprocessed intelligence information and graphic IPB products received from the echelon ACE. They do not receive and process initial intelligence data (uncorrelated intelligence reports, etc.) for use by the staff elements. All initial unprocessed intelligence reports or information received by the G2 RWS will be passed to the echelon ACE to undergo all-source (AS) processing and integration with other intelligence disciplines before returning to the G2 RWS.

      (b) BDE S2 RWS. The Brigade S2 RWS is also a consumer/user of preprocessed intelligence information and graphic IPB products received from the brigade ACT RWS, division ACE, and G2 RWS. It does not receive and process initial intelligence data (uncorrelated intelligence reports, etc.) for use by the staff elements. All initial unprocessed intelligence reports or information received by the S2 RWS will be passed to the ACT or ACE (if an ACT is not available) to undergo all-source (AS) processing and integration with other intelligence disciplines before returning to the S2 RWS.

      (c) BDE ACT RWS. The ACT is an organic element of the MI DS Co and operates in a habitual relationship with a maneuver BDE TOC. It is the center of intelligence data and communications within the brigade and provides the brigade with intelligence connectivity, processing, analysis, and dissemination. The ACT RWS operates at the SECRET collateral security level in either an individual or in a multi-node configuration interfacing via a LAN. Unlike the G2/S2 RWS, the ACT RWS will receive and process direct sensor input and provides finished intelligence information to the BDE S2 RWS, the ACE, and to the subordinate battalions. The ACT RWS will co-locate and interface with the JSTARS Common Ground Station (CGS) and UAV Ground Control Station (GCS).

      (d) Bn S2 RWS (ASAS Light). The Bn S2 RWS consists of a lightweight computing device (e.g., notebook, laptop, etc.) and a select subset of the brigade RWS software capabilities and communications interfaces. It provides a limited automation support capability to the Bn S2 and is primarily a consumer/user of preprocessed intelligence information and graphic IPB products received from the BDE ACT, division ACE, and the BDE S2 RWS. It receives and processes initial intelligence reports and information received from the battalion organic assets to maintain situation awareness. It will also forward these reports to the BDE ACT to undergo all source processing and integration with other intelligence disciplines before returning to the Bn S2 as fully correlated intelligence information. Until the fielding of the Force XXI Battle Command Brigade and Below (FBCB2) System, the ASAS Light is the primary interface between the digital environment (ASAS and the rest of ABCS subsystems) and the analog environment. Until FBCB2 is fully fielded, the Battalion S2 sections must maintain the capability to operate in an analog, digital, and mixed environment.

       

    2. ASAS Block I

      3. (a) ASAS Block I, is comprised of the All Source (AS), Single Source (SS), the Remote Workstation (RWS) and the Block I Communications Control Set (CCS). The AS provides for a correlated all source intelligence database, to support developing the ground situation and targeting; the SS is a single source processor for Signal Intelligence (SIGINT) analysis. Both systems operate in an SCI environment. The RWS is the collateral workstation that receives a sanitized version of the ASAS database. The CCS provides communications interface between the SCI and collateral environment. ASAS Block I is currently fielded in the US Army’s divisions and corps elements, as well as the Intelligence School at Ft. Huachuca. Product improvements to ASAS Block I are currently being fielded.

      (b) The All Source Section (AS) consists of three to six computer workstations that manipulate the all source correlated database. The AS assists analysts with Intelligence Preparation of the Battlefield (IPB), maintenance of the enemy situation, and targeting. The AS may be task organized to provide additional workstations and analysts to support targeting, collection management database management, or situation development. The heart of the AS is the All-Source Correlated Database, or ASCDB. The ASCDB is where intelligence from multiple disciplines is fused together into an all source product. The AS database manager and analysts can perform many types of queries and display the results on a digital map to facilitate analysis and respond to consumer’s requests.

      (c) The Single Source Section (SS) consists of six computer workstations that process information from specific intelligence disciplines. The current ASAS Block I version of the SS handles SIGINT information primarily, but future versions will handle HUMINT and IMINT. After processing information, the SS workstations delivers near-real-time SIGINT updates to the ASCDB in the ASAS-All Source workstation. The SS also provides detailed technical support information back to tactical SIGINT sensors. The SS workstation may be task organized to provide additional workstations and analysts to Imagery Intelligence (IMINT), and SIGINT. ASAS Block II enhancements will include Counterintelligence and Human Intelligence (CI/HUMINT) capabilities.

      (d) Remote Workstation (RWS) receives and processes a sanitized version of the ASCDB. Until the full integration of the JCDB with ABCS 6.0 software upgrade, the RWS will continue to be the gateway for intelligence for dissemination, outside of compartmented channels. Since all unit designations, locations, and Date Time Groups (DTGs) are at collateral levels, the sitmap displayed on the RWS can be identical to the sitmap displayed within the AS. The RWS provides a collateral intelligence processing capability to the G2s of the Army divisions and corps. Doctrinally, each unit employs two workstations in the main Tactical Operations Center (TOC). It is the IEW component of the ABCS. The RWS is the interface between the Analysis and Control Element (ACE) and ATCCS. This subsystem is perhaps the most significant of all due to its ability to disseminate a collateral picture of the ASCDB, by providing tactical commanders with a common picture of the battlefield.

      (e) The Communications Control Set (CCS) is the primary communications processor for ASAS. There are four variants of CCS, two corps level and two division level sets. The corps sets are the AN/TYQ-40A (V) 3 (sheltered) and AN/TYQ-63A (V)1 (unsheltered). The division sets are the AN/TYQ-40A (V)2 (sheltered) and the AN/TYQ-63 (V)3 (unsheltered). The CCS has recently been upgraded to a single baseline. The CCS provides a communications front end, interfacing the ASAS enclaves (both AS and SS) with various communications systems – principally over MSE, LAN connect via TROJAN SPIRIT, or direct wire line connection to the AN/TYC-39 message switch and other interfacing systems. The CCS receives and relays information from adjacent, superior, and subordinate units to and from the intelligence processing enclaves. At division level it also connects multiple sensors directly to the ASAS. The division level sets are also equipped with one (unsheltered systems) or two (sheltered systems) SINCGARS RT-1523 VHF radio sets as well as a MST-ICOM (V)2 (unsheltered systems) or an AN/ARC-164 (sheltered systems, with KG-84A) UHF line of sight radio for sensor and ground-to-air communications. Each division level CCS has two low speed and two high speed serial communications canisters with associated cryptographic and mode/signaling equipment. The corps level sets have no radio capability but do have four (4) additional high-speed serial communications canisters. Upgrades to CCS will modernize the hardware platform, bring the configuration to a common baseline, and achieve compliance with current ABCS standards.

       

    3. ASAS Block II

    (a) ASAS Block II system builds upon fielded ASAS Block I and prototype systems, and provides additional software functionality required by the ABCS. Block II analytical components consist of three subsystems: The Analysis and Control Element (ACE) Workstations, the Remote Workstation (RWS), and the ASAS Light. Block II also features enhancements in communications interfaces and data handling. Block II hardware consists primarily of integrated government (GFE) items mounted in standard Army shelters or transit cases. The ACCS Common Hardware/Software II (CHS II) workstations used by ASAS may be operated in shelters, buildings, or tents. The communications control set provides the communications front end of the system. Block II software uses a compliant secure operating system and includes an extensive package of system services software with the Common ABCS Support Software architecture and the Joint/Army Common Operating Environment.

    (b) Analysis and Control Element (ACE) system level performance is improved through automatic sanitization and automatic collateral message release. Substantial improvements in communications include four additional channels, as well as Satellite Communications (SATCOM), improved High Frequency (HF) Radio, Joint Worldwide Intelligence Communications System (JWICS), Multiple Subscriber Equipment (MSE) Packet Switch, and Single-channel Ground and Airborne Radio System (SINCGARS) frequency hopping. These improvements will improve deployability, by making the system smaller and split-based/jump capable. Common applications will have enhanced alarm/alert services, better map operations, and digital weather/terrain products. Specific improvements to intelligence processing include secondary imagery dissemination with receipt, display, and storage capabilities, a Collection Management (CM) package with requirements, mission, and asset management capabilities, and enhanced SIGINT contributions to the correlated database.

    (c) The ASAS Light supports collateral intelligence processing at maneuver units below division level. Its functionality and security level is equivalent to that of an individual workstation on the subsystem, to which RWS is connected. The ASAS Light consists of a Pentium class notebook computer operating in a Windows NT environment. While focused to provide an automated intelligence capability between the Battalion (Bn) S2 and the other ABCS subsystems (to include the Bde RWS), it is conceivable that this device may migrate into the Army’s Light and Airborne forces at the Brigade level. ASAS Light will provide the Bn S2 the ability to operate in a fully digital environment (e.g. digital exchanges with FBCB2, the Maneuver Control System (MCS), and the Advanced Field Artillery Tactical Data System (AFATDS) at the Bn), or to the intelligence link between the digital and analog environments.

    (d) CCS Upgrades will bring system configuration to a common baseline, which will be in compliance with current ABCS standards. The heart of the upgraded CCS is the Tactical Communication Support Processor (TCSP), and supported by the Secure Messaging and Routing Terminal (SMART). The TCSP allows the CCS to function as an R/Y store and forward switch, while SMART provides a security guard to R-only external LANs. The CCS is a true Multi-Secure (MLS) system and is accredited by the Defense Intelligence Agency (DIA) to handle both SCI and collateral traffic. CCS software will be enhanced by implementation of ASAS unique protocols. The TCSP supports a system high LAN connection to ASAS SCI workstations and/or to other TCSPs/CSPs. The only allowable LAN interface from TCSP collateral LAN connectivity and provides the interface to the MSE Tactical Packet Network (TPN), TROJAN SPIRIT II (collateral Secret), ASAS RWS, ABCS, and/or the Secure Internet Packet Routing Network (SIPRNET). Upgrade features ensure that the AN/TYQ-40 CCS Year 2000 problem is solved as well as the elimination of the need for separate "R" and "Y" stacks in the AN/TYQ-63 variants and the need for dual-manual review of outgoing collateral messages. Also, all ASAS CCS variants will meet the identical interoperability standards and achieve commonality of functionality, training, maintenance and logistics and add Ethernet capability to the AN/TYQ-40 systems as well as achieving communication interfaces for LAN, TPN, JWICS, SIPRNET, AUTODIN, MSE, and NRP data exchange.

    (e) The Tactical Imagery Processing System (TIPS). TIPS is a Block II initiative to allow graphical products to move from the SCI level to the collateral environment. TIPS provides a function similar to the CCS, except the CCS is message text based and TIPS will allow the movement of overlays and other graphical products.

    (f) The Trusted Workstation (TWS). The TWS is a Block II initiative to provide multilevel security capabilities to the ASAS located in the ACE. The TWS will apply the appropriate downgrading actions to products leaving the ACE based on classification and handling caveats (data can be scrubbed and released based on up to 14 different classifications/handling caveats simultaneously).

    Note: For continuous updated information on TSM-ASAS systems review the TSM-ASAS website at www.tsmasas.

     

  • ASAS CI/HUMINT SUBSYSTEM

    • All Source Analysis System (ASAS) Counterintelligence (CI) and Human Intelligence (HUMINT) Subsystem.

    As a result of the Counter Intelligence and Human Intelligence (CI/HUMINT) Integrated Concept Team (ICT) process, hosted by the US Army Military Intelligence Center in 1996 and early 1997, CI/HUMINT operational requirements were identified, and the creation of a CI/HUMINT Subsystem within the ASAS program was established. The ASAS CI/HUMINT Subsystem will provide automation equipment, tailored software functionality, and a communications interface capability, for four distinct functional entities. These entities include – Single Source (SS), Counter Intelligence and Information (?)Operations Workstation (CI&IOPS WS), CI/HUMINT Automated Tool Set (CHATS) and Individual Tactical Reporting Tool (ITRT). The ASAS CI/HUMINT Subsystem will provide intelligence automation support to Army intelligence organizations and intelligence staff elements at separate brigade level/JTF echelons and above. These four entities will be supported by the following components of the CI/HUMINT Subsystem:

     

        1. ASAS CI/HUMINT SUBSYSTEMS

    The components of the ASAS CI/HUMINT Subsystem are described below.

    Mobile CI/HUMINT Team Automation Tools.

    Mobile CI/HUMINT/DOCEX teams will require two types of automation support to fulfill their missions.

    Individual Tactical Reporting Tool (ITRT)

    The first component is a portable, lightweight automation tool similar to a Palm Top computer to be used by the individual CI Agent or Interrogator (INTG) as the entry level device of the CI/HUMINT Subsystem. This device is the Individual Tactical Reporting Tool (ITRT). The primary function of this device is message preparation and dissemination. It will be capable of receiving a limited set of messages such as tasking messages from the team leader. The ITRT will be used to prepare and disseminate reports and digital imagery to the Team Leader CHATS. Individual CI/HUMINT agents and collectors will use the ITRT to interface with the CI/HUMINT team base element. Desired communications capabilities for the ITRT include interfacing directly with the team leader CHATS via docking, through use of Combat Net Radio (CNR), area communications or other available communications when the agent/collector operates away from the team base location. Current planning calls for fielding the initial ITRT (capability) in FY2000.

    CI/HUMINT Automated Tool Set (CHATS).

    The next component provides automation for CI, INTG, and DOCEX Team Leaders. This is the AN/PYQ-3 (V1) CI/HUMINT Automated Tool Set (CHATS). CHATS is the only component of the CI/HUMINT subsystem fielded to date. CHATS provides automation support to the CI Operational Management Team (OMT) Team Leader and/or CI Operational Control Element (OCE) Team Leader in those units employing OMT/OCE to manage two or more CI teams.

     

        1. CI and INTG OPS WS.

    There are two primary functions of the CI/INTG OPS WS:

    The OPS WS will provide automation for unit level operational and asset management of CI/HUMINT operations and activities; automation to access other CI/HUMINT database (DB); and communications with deployed CI and INTG elements.

     

        1. ACE ASAS CI/HUMINT Single Source (SS) Workstation (WS).

    The primary purposes of this WS are to (1) provide automation support to CI/HUMINT analysts at the ACE and (2) ensure intelligence produced by CI/HUMINT soldiers is parsed and fully integrated into the all source intelligence picture.

    ASAS CI/HUMINT Subsystem Architecture. At Figure 4- _ is a graphical representation of the ASAS CI/HUMINT subsystem, showing the components of the subsystem. At Figure 4_ is a message flow diagram showing the components of the subsystem and how information flows between the components.


    [Back]
    [Index]
    [Next]