• 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

The Maneuver Control System (MCS) is the central command and control system for the maneuver elements in battalion through corps echelons. MCS consists of a network of computer workstations that integrate information from subordinate maneuver units with that from other Army Tactical Command and Control System battlefield functional areas, to create a Force Level Information data base referred to as the Battlefield Common Tactical Picture. Tactical information products such as situation maps and reports allow the display and manipulation of this information. The MCS also provides a means to create, coordinate, and disseminate operational plans and orders. The MCS role in communicating battle plans, orders, and enemy and friendly situation reports make it a key component of the Army's ongoing effort to digitize the battlefield. As the primary command and control system from battalion to corps, MCS facilitates the accomplishment of dominant maneuver, precision engagement, focused logistics, and full-dimensional protection.

In 1980, the Army fielded the first MCS system with limited command, control, and communications capabilities to VII Corps in Europe. In 1982, the Army awarded a five-year contract to continue MCS development, and by 1986 MCS software had evolved to version 9, also fielded in Europe. In 1987, the Army performed post-deployment tests on version 9 in Germany. These tests led the Army Materiel System Analysis Activity to conclude that MCS did not exhibit adequate readiness for field use, and that further fielding should not occur until the problems were resolved. However, the Army awarded a second five-year contract that resulted in version 10, which was fielded in October 1988 and remains in the field today.

In 1988, the Army awarded a contract for the development of software version 11. By February 1993, the Army stopped development of software version 11 because of program slips, design flaws, and concerns with cost growth. The program was reorganized in April 1993, forming a team of contractors and government software experts to develop software version 12.01, using software segments salvaged from version 11.

In September 1996, the Army awarded a contract to initiate development of the next version of MCS. This effort, the Block IV MCS, is being developed by a new contractor and will involve substantially different software, including the required Defense Information Infrastructure Common Operating Environment. The Army postponed IOT&E of the Block III in November 1996, due to software deficiencies. In lieu of the IOT&E, a Limited User Test was conducted from October-November 1996 to establish a Block III baseline and identify software problems that required correction prior to IOT&E. These goals were achieved, and DoD approved the Army's LRIP acquisition decision to procure computers for a training base operational assessment. This operational assessment, completed in May 1997, supported the Army's procurement of MCS for fielding to the training base prior to successful completion of IOT&E.

Both the TEMP and System Evaluation Plan were finalized this year, and the IOT&E was conducted from June 8-12, 1998. The IOT&E was conducted during a Division Command Post Exercise at Ft. Hood, TX, and included Division, Brigade, and Battalion level Tactical Operations Center's (TOCs) from the 4^th Infantry Division. The IOT&E focused on the contribution of MCS to command post operations. The other four battlefield functional area systems that comprise the Army Tactical Command and Control System were present, and made it possible to address interoperability between these systems. IOT&E units employed MCS Block III software and Common Hardware and Software-2 computers.

There were several limitations known in advance of the test. As the "EXFOR," the 4^th Infantry Division has a number of experimental technologies integrated into its TOCs, which are maturing within the Division. As the Division evolves to become the Army's First Digital Division in CY00, it has become readily apparent that a number of technologies are inadequately integrated or hardened for field employment, particularly for the rigors of tactical displacement. As a result, Division-level TOC displacements were not conducted, and the associated issue of maintaining a common picture of the battlefield during a division-level displacement can not be evaluated. Additionally, test soldiers were allowed to use their resident experimental technologies in lieu of some of the capabilities embedded in MCS, which could limit full-scale assessment of these products. Based on these known limitations, the Army and DOT&E agreed prior to the IOT&E that fielding of MCS Block III software would not go beyond the First Digital Corps until successful completion of a follow-on event. Fielding to the First Digital Corps presumes a successful IOT&E outcome, and is motivated by the key role MCS plays in the Battlefield Digitization system of systems.

At the time of this writing, the IOT&E analyses are not final, but MCS Block III appears to have performed as it was designed, and has contributed to the planning, deployment, and reconstitution phases of unit operations. MCS contributions were greatest for monitoring the battlefield at higher echelons, but still provided improved situational awareness of adjacent units at the brigade and battalion levels. Update-rate requirements were generally met, but the more operationally relevant accuracy and consistency measures suffered when brigade and battalion units entered information manually into their MCS workstation, for which no automated updates are provided. Another cause for degraded accuracy and consistency is that MCS generates an update only when a unit-location change occurs. If a workstation misses an update, the inaccuracy will endure until another location change occurs and is successfully received.

A client-server architecture has been developed with the data base resident at the server instead of disseminating a data base to each MCS device. During the IOT&E, MCS demonstrated the ability to "client into" and host applications. However, the limitations on the number of clients and the size of individual monitors has motivated staffs to create a viewing area of the ATCCS systems by using multiple displays. A common setup at a division TOC includes dedicated monitors for MCS, ASAS, AFATDS, CSSCS, or a VTC link. This approach permits the commander to tailor his multiple displays and fuse data across them, rather than drawing information from a fused display. A serious drawback for this approach is the number of large screen displays required, screens which are currently "experimental" (commercial), lack ruggedization, and exceed the transportation assets of the TOC. Due to the amount of experimental technology, the division command post's moves were simulated by powering down the equipment. When the brigade TOC was displaced, their display bank was disconnected and stowed on a truck until their return.

Block III MCS provides basic/preliminary tools for planning activities such as terrain analysis and the creation of electronic overlays. These tools were not extensively employed during the IOT&E, because the test unit had access to various experimental technologies that they were more comfortable with in supporting their planning processes. It is anticipated that some of the experimental tools employed during the IOT&E will be incorporated into Block IV of MCS.

Many improvements, several of which are in areas the MCS program is not responsible for, will be necessary before a force equipped with MCS can be judged effective and suitable in an operational environment. Nonetheless, the limited capabilities present in the current MCS do provide enhanced military capability, and should be fielded to appropriate elements of the First Digital Corps that are necessary to continue progress in the areas of interoperability and development of digital tactics, techniques, and procedures. An IOT&E of TOC movement and Block IV capabilities will be required before fielding MCS to any other Army units.