Army Digitization Master Plan '96
5. ARMY BATTLE COMMAND SYSTEM (ABCS)
ABCS is the integration of command and control systems found at all echelons: from the ground force component commander at the theater or joint task force level to the individual soldier or weapons platform; in an Army force deployed for land combat or conducting peace operations, humanitarian assistance, or operations in aid of civil authorities. ABCS is the integration of battlespace automation systems and communications which functionally link strategic and tactical headquarters. It can also employ a mix of fixed and semi-fixed installations and mobile networks. It is interoperable with joint and multinational command and control systems at upper echelons across the full range of command and control functionality, and is vertically and horizontally integrated at the tactical and operational levels.
ABCS has three major components:
Figure 5-1 Army Battle Command System
5.1 Army Global Command and Control System (AGCCS)
AGCCS is the Army component of the joint GCCS. It is being built from application programs developed by the Army WWMCCS Information System (AWIS), the Strategic Theater Command and Control System (STCCS), and the Echelons Above Corps (EAC) portion of the Combat Service Support Control System (CSSCS). The primary scope of this effort is to evolve these stand alone systems into a suite of modular applications (e.g., logistics, medical, personnel, Theater Army Special Operations Support, mobilization, deployment, Army Status of Readiness and Training, and Transportation Asset Management) that operate within the DII COE. AGCCS modules will interface with common applications and other shared components of the ABCS and with the joint C2 mission applications provided by GCCS.
5.1.1 Army WWMCCS Information System (AWIS)
When the Army is currently called upon to rapidly deploy its forces, AWIS provides the support for the entire operation: from mobilization and deployment through employment and sustainment. AWIS fulfills the Army's strategic C2 requirements for software, hardware, and databases for the implementation of the Joint Operations Planning and Execution System (JOPES) and other Joint Service systems that support the Unified Commands and the Joint Staff. In addition, AWIS modernizes the Army's C2 system, supporting conventional military planning and execution.
AWIS-developed software systems provide the capability for Army commands to
WWMCCS is a primary national system for both operational and administrative command and control of U.S. Military Forces. It supports the National Command Authority, the Joint Staff, the Unified Commands, and other DoD agencies and activities. WWMCCS is a SECRET system-high network with interfaces to joint, Army Theater, National Guard, and Reserve systems.
WWMCCS and the current AWIS are being replaced by GCCS and AGCCS in early FY1996. Since GCCS will operate at the SECRET system-high level, the TOP SECRET Support System (TS3) will be implemented until an upgraded GCCS (GCCS-T) is fielded to operate at the TOP SECRET level.
5.1.2 Strategic Theater Command and Control System (STCCS)
Timely, accurate information concerning hostile and friendly forces is essential in reducing decision-cycle time and effectively monitoring execution of operational orders. EAC command and control must not only pass information horizontally to theater staff and subordinate commands, but also interoperate with GCCS, other Service systems, multinational systems, ATCCS Battlefield Functional Area Control Systems (BFACS)/ABCS, and other C2 systems.
STCCS is the Army's means to accomplish EAC C2. It is a peacetime and go-to-war set of software modules that will reside on AGCCS and are designed to assist theater commanders in the execution of crisis and wartime EAC sustainment and operational maneuver functions. STCCS is a user-friendly, highly-adaptable, reliable, and maintainable system. STCCS features ease of modification to meet changing threats and functional requirements, and to enable expeditious insertion of new technology into the system. This is accomplished through adherence to a layered, open system architecture philosophy, employing common hardware and operating system software tied to modular, functional applications through a common ATCCS software system layer. An aggressive software re–use philosophy is also employed.
User experience with fielded software will identify needed capability improvements, user interface changes, and other problems requiring fixes. These will be readily incorporated into STCCS within the constraints of the annual development release cycle.
5.1.3 CSSCS at Echelons Above Corps (CSSCS/EAC)
CSSCS/EAC will consolidate and collate the data required to integrate situational awareness of the CSS mission areas. It will provide strategic and tactical commanders with timely, critical information on ammunition and fuel supplies, medical and personnel status, transportation, maintenance services, general supply, and other field services.
Rapidly changing tactical situations and the intensity of modern warfare demand faster evaluation of force status than is achievable by current manual systems. CSSCS/EAC will give commanders easy access to the resource management, supply, and administrative information required to determine each unit's capability to carry out its mission. The system will also allow commanders to conduct trade-off analyses and evaluate potential courses of action based on different logistical scenarios.
CSSCS/EAC is being designed to improve the planning and execution of CSS C2 operations. A near real-time automated system, CSSCS/EAC will collect, process, analyze, and summarize designated critical information from Standard Army Management Information Systems (STAMIS), including supply, maintenance, ammunition, transportation, personnel, financial, and medical. CSSCS/EAC will consolidate the data and transform it into decision support information for both CSS and force-level commanders.
5.1.4 DII COE Migration Strategy
The Army is committed to migrating its critical C2 mission application systems to the ATA. This will be achieved by developing or migrating mission application (MA) software to use the integrated, shared support services defined by the DII COE. The goal of this migration process is for MAs to eventually consist of only the software necessary to implement mission functionality. All common support functions and infrastructure services required by a MA will be provided by COE services (e.g., mapping and communications).
In order to implement this migration to the COE in compliance with the ATA, system developers will re-engineer and/or retrofit their applications by removing existing program-unique support functionality and replacing that functionality with calls for the common services of the DII COE. MA software calls for common services will use published DII COE APIs. These APIs will be provided as part of a configuration-controlled On-line Access Library.
The AAE has mandated that all systems must submit implementation plans for complying with the ATA and migration to the COE. The ADO, with ASEO support, is responsible for the review of these plans.
5.2 Army Tactical Command and Control System (ATCCS)
Initially, ATCCS will be linked directly to AGCCS, providing the framework for seamless connectivity from battalion to theater. Objectively, its five tactical C2 systems will merge into a single, coherent, interoperable system binding the combined arms Battlefield Operating Systems together within a unifying COE.
5.2.1 Maneuver Control System (MCS)
The Army is developing and fielding a system for use by commanders and staffs of tactical maneuver units, using a blocked approach. Block II—using Version 10 software running on NDI hardware—is currently fielded to all heavy corps and divisions except the 3rd Mechanized Division. The software for Block III is titled MCS/PHOENIX (MCS/P), since functionality from an experimental program named PHOENIX is being merged into the MCS Version 12.01, the software version currently under development. Block III software will be tested and fielded on Common Hardware and Software (CHS)-2 in FY1996-97. Block IV software will be developed and delivered under a 5-year contract scheduled for award in FY1996. A change to the system name is currently under consideration to reflect recent evolutionary changes in battle command philosophy.
MCS/P will distribute tactical information on the battlefield, allowing a commander to readily access and display current situation reports, intelligence, and contact reports that assess enemy strength and movement, as well as the status of friendly forces.
Through MCS/P, the commander can transmit critical battlefield information such as mission information; courses of action; schemes of maneuver; warning and operations orders; changes in priorities; and intelligence, fire support, supply status, and air operations requests. MCS/P assists the commander in applying combat power at the appropriate time and place in response to changing battlefield dynamics. In addition, it allows the commander sufficient flexibility to act preemptively to developing situations.
MCS/P databases maintain and display critical situation awareness information on friendly and enemy forces in both text and graphic formats, using data obtained from MCS/P and other BFACS. Using MCS/P decision support graphics—which include map overlays and battle resources by unit—possible courses of action are analyzed, the appropriate course of action is determined, and MCS/P is used to prepare and send warning orders, operations orders, and related annexes.
Exchange of information using MCS/P gives all command posts from battalion through corps the same common picture of the battlespace. Commanders can make decisions that mesh with the decisions and capabilities of other commanders in the network. With the ability to query both local and remote databases, MCS/P also assists in synchronizing the battle.
The MCS/P effort involves the transition of PHOENIX application software modules from the PHOENIX ACT II project into the MCS/P system in preparation for the TF XXI AWE. The procedure for transitioning PHOENIX application software modules is a three-phase process:
Non-compliant but essential PHOENIX application software modules will be incorporated as evolutionary insertions as they become COE-compliant. Application modules having common functionality within MCS Version 12 and PHOENIX will be consolidated into the MCS/P system. The unified MCS/P functionality will be exercised at Prairie Warrior 96, in a follow-on IOTE, and during the Force XXI AWEs.
IPT Working Groups (i.e., requirements, acquisition strategy/contracts, cost/funding, and testing) are overseeing this transition process. Oversight and review is being performed by an integrated OSD and Services body chaired by ASD(C3I).
5.2.2 Advanced Field Artillery Tactical Data System (AFATDS)
AFATDS is a totally integrated fire support C2 system designed to replace TACFIRE. It processes fire mission and other related information to coordinate and optimize the use of all fire support assets, including mortars, field artillery, cannon, missile, attack helicopters, air support, and naval gunfire. AFATDS will provide processing capabilities from the corps to the platoon Fire Direction Center.
Through the use of distributed processing capabilities, fire missions will flow through the fire support chain during which target attack criteria will be matched to the most effective weapon systems available at the lowest echelon. The automation provided by AFATDS will enhance the maneuver commander's ability to dominate the battle by providing the right mix of firing platforms and munitions to defeat enemy targets based on the commander's guidance and priorities. AFATDS also expands the fire support commander's ability to control assets and allocate resources.
AFATDS will automate and facilitate fire support planning and current operations. During battle, AFATDS will provide up-to-date battlefield information, target analysis, and unit status, while coordinating target damage assessment and sensor operations.
Integrating all fire support systems via a distributed processing system will create a greater degree of tactical mobility for fire support units and allow missions to be planned and completed in less time. AFATDS will also meet field artillery needs by managing critical resources; supporting personnel assignments; collecting and forwarding intelligence information; and controlling supply, maintenance, and other logistical functions.
AFATDS will interoperate with all fire support systems and ATCCS BFACS, as well as the fire support C2 systems for Germany (i.e., ADLER), United Kingdom (i.e., BATES), and France (i.e., ATLAS).
AFATDS will use modular applications software under development, in conjunction with ATCCS CHS. Major hardware components will be the Fire Support Control Terminal (FSCT) and the Fire Support Terminal (FST).
5.2.3 All Source Analysis System (ASAS)
ASAS is a ground-based, mobile, automated intelligence processing and dissemination system designed to provide timely and accurate intelligence and targeting support to battle commanders. ASAS will provide communications and intelligence processing capabilities to allow sensor and other intelligence data to automatically enter into the all-source database and be simultaneously available at multiple analyst workstations.
Elements of ASAS will provide seamless support to warfighters from theater to battalion levels.
ASAS functions as the IEW subsystem of ATCCS. It provides all-source intelligence fusion which allows commanders and their staffs to gain a timely and comprehensive understanding of enemy deployments, capabilities, and potential courses of action.
ASAS produces ground battle situation displays, disseminates intelligence information, provides target nominations, helps manage organic IEW assets, assists in providing operations security support, and aids in deception and counterintelligence operations.
The Block II development effort will provide an all-source intelligence fusion capability to gain a timely and comprehensive understanding of enemy deployments, capabilities, and potential courses of action. With this knowledge, commanders will have a significantly enhanced view of the battlespace and will be able to more effectively and efficiently conduct the land battle.
Hardware components of the Common Hardware and Software 2 (CHS-2) program will be used in Block II. This new hardware maximizes ruggedness, minimizes weight and cost, while increasing portability and mobility. Interoperability and flexibility will be enhanced through the use of ATA protocols, adoption of the DII COE, and an open systems architecture. Functionality will be enhanced in the areas of all-source and single-source processing; graphics and image manipulation; collection management; auto-sanitation; and the use of digital terrain and automated weather products.
5.2.4 Forward Area Air Defense Command Control and Intelligence System
FAADC2I is an integrated system of weapons, sensors, and command and control that provides C2 and targeting information to air defense weapons systems at the division-and-below levels. It protects maneuver forces, critical command posts, and CS/CSS elements from low–altitude air attack. The system uses CHS processors and operating systems, with data communications provided by the Army Data Distribution System (ADDS), SINCGARS, or dedicated digital radio links.
Integrating sensor inputs from various sources, FAADC2I provides early warning, targeting, and control information to FAAD and supported units. An area of interest air picture is developed and air tracks are identified using automated and manual means. Threat tracks cause alerts, with fire units automatically cued to the targets. FAADC2I integrates battlespace control measures in relationship to the air picture, which is displayed to fire units to enhance acquisition of hostile tracks by the weapons systems.
The initial development effort of FAADC2I is concentrating on engagement operations, which are real-time actions supporting aircraft engagement. The system will begin encompassing more force operations functionality (e.g., all unit plans, support, and day-to-day operations) as the program matures.
At the corps level, FAADC2I will be integrated with PATRIOT, HAWK, and future Corps SAM and their associated C2 systems into the comprehensive Air and Missile Defense (AMD) system. Within AMD, essential C3I operational functions will be distributed among Air Defense Tactical Operations Centers (ADTOCs), sensor nodes, and fire units throughout the depth of the battlefield, providing the capability to acquire, process and distribute information necessary for the planning and coordination of AMD operations. The ADTOC will serve as the AMD link to ABCS and joint/allied C3I systems. It will process and distribute the information required to direct AMD forces and synchronize the their actions with the maneuver commander’s concept of operations.
The objective AMD system will be achieved through an evolutionary process.
- Block I: the current FAADC2I and the prototype Air Defense Brigade TOC.
- Block II: improvements to the PATRIOT Battalion TOC and the battalion-level Improved C3I (IC3I) capability of FAAD. It will also provide a battalion/battery- level IC3I capability for the Theater High Altitude Air Defense System (THAAD).
- Block III: the objective system and reflects the fielding of the ADTOC capability and the required vertical and horizontal interfaces to ABCS.
- Block IV: reflects P3I.
5.2.5 Combat Service Support Control System (CSSCS)
CSSCS will consolidate and collate the vast quantities of data required to integrate situational awareness within the CSS mission areas. CSSCS will provide tactical commanders with timely, critical information on ammunition and fuel supplies, medical and personnel status, transportation, maintenance services, general supply, and other field services. CSSCS, as a component of ATCCS, has essentially the functionality as described in Section 5.1.3 (CSSCS/EAC), with the exception that data output will be tailored for brigade, division, or corps commanders, as appropriate.
5.2.6 ATCCS DII COE Migration Strategy
With the advent of the DII, the Army has acted vigorously to integrate CHS products into the COE. As a result, current CHS procurements include COTS modules which are COE-compliant and which are being migrated into the ATCCS systems as they are individually upgraded. In addition, many COE elements will be incorporated into the CHS program and will be provided to the ATCCS PMs as a coherent software package for incorporation into the ATCCS systems. The Army recognizes that this must be an evolutionary process, given the resource constraints which characterize the current and forecast defense budgets. To realize the full potential which the COE offers, MA software which cannot function within the COE must also be modified or rewritten to use the integrated, shared support services provided by the COE.
Army migration strategy involves the removal of existing support functions and their replacement with the appropriate/matching common function. When a mission application is undergoing significant modification and/or enhancement, developers must utilize COE components whenever generalized support functions are required and appropriate COE components are available. In instances where the appropriate functionality is not yet available in the released version of the COE, surrogate software modules that will perform the required support function may be used. This surrogate software will be provided to DISA as candidates for incorporation into the COE. Surrogate support software must still be replaced with the appropriate baseline COE modules as they become available.
Surrogate software must also comply with the ATA. If the COE contains published APIs for a specific support function, but the underlying modules do not yet contain the complete required functionality, the application developer should acquire the surrogate code using the public API as an interface specification for the surrogate support functionality. This supports a simplified migration from the surrogate code to the baseline COE module when it becomes available. These surrogate support modules may also be proposed for integration into the COE baseline. PM CHS will maintain configuration management control over surrogate code developments to ensure that multiple similar surrogates are not developed, and that those which are developed are compliant with the DII COE architecture.
The Army is currently working with DISA to expedite migration to the DII COE. For Army systems/platforms at or approaching COE compliance, the transition will be accomplished by using common build tapes. In other cases, the technical challenges associated with the transition will be addressed by an integrated DISA/PEO C3S team. The team will specifically address issues such as documentation, scaling the COE for limited-capability Army platforms, heterogeneous environments, and Army-required COE modules. The result will be an extension of the COE and a wider applicability of its products.
Under the AAE mandate that systems must submit implementation plans for compliance with the ATA and migration to the COE, the PMs for the ATCCS systems have submitted their initial draft plans for migrating to the COE and the other applicable standards of the ATA. The ASEO, in coordination with the ADO, will monitor the plans to ensure that the process remains coherent across the spectrum of Force XXI activities.
5.3 Force XXI Battle Command, Brigade-and-Below (FBCB2)
FBCB2—more fully described in Section 6.1—will provide situational awareness and command and control to the lowest tactical echelons. It will facilitate a seamless flow of battle command information across the battlespace, and will interoperate with external command and control and sensor systems, such as ATCCS. The end result will be a vertical and horizontal integration of the digital battlespace and the brigade-and-below tactical unit levels.
The FBCB2 system is comprised of:
Functionally, the FBCB2 system will support lower–echelon battle command tactical mission requirements including:
|
NEWSLETTER
|
| Join the GlobalSecurity.org mailing list |
|
|
|
