• 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
FY97 Annual Report

MANEUVER CONTROL SYSTEM (MCS)

	Army ACAT ID Program 3156 systems Total program cost (TY$) 1030.4M Average unit cost (TY$) 0.188M Full-rate Production 4QFY98 Prime Contractor Block III: The Tightly Knit Confederation Block IV: Lockheed-Martin

SYSTEM DESCRIPTION & CONTRIBUTION TO JOINT VISION 2010

The Maneuver Control System (MCS) is the command and control system for the maneuver battlefield functional area of the Army Tactical Command and Control Systems (ATCCS). The MCS is a network of computer workstations that manages information relating to the planning, execution, and monitoring of military operations at corps and lower echelons. The MCS integrates information from subordinate maneuver units with that from the other ATCCS battlefield functional areas to create a Force Level Information database, often referred to as the common picture. Tactical information products such as situation maps and reports allow display and manipulation of this information. The MCS also provides a means to create, coordinate, and disseminate 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 efforts to digitize the battlefield. The basis for the new operational concepts in Joint Vision 2010 is improved command and control. The MCS is fundamental to improving command and control of Army maneuver forces and assuring information superiority. As primary command and control system and the integrator of information from battalion to corps, the MCS facilitates accomplishing 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 postdeployment 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 version 11. By February 1993 the Army stopped development of version 11 software because of program slips, design flaws, and concerns with cost growth. The program reorganized under a plan approved by the Office of the Secretary of Defense in April 1993. Under the reorganized program, a group of contractors and government software experts have been working to develop version 12.01 using software segments salvaged from version 11.

Since the 1993 reorganization, MCS has continued to experience development problems. The IOT&E of version 12.01 has moved from November 1995 to March 1998 and interim tests show that significant software problems continue. Despite these problems, 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 may involve substantially different software.

The Army postponed the IOT&E of the Block III (software version 12.01) in November 1996 because of software deficiencies. Consequently and Block IV (software versions 12.1 through 12.3) are in parallel development, which is a circumstance of the Army's decision to postpone the IOT&E for MCS Block III. The Tightly Knit Confederation continues to develop version 12.01 under a task order from the PEO C3S and Lockheed Martin is developing the Block IV MCS. In 1998, the Army plans to conduct an IOT&E and Milestone III decision using the Version 12.01 software.

During 1996, the MCS Customer Test was conducted from April 1-12, 1996 at Fort Monmouth, NJ. The Customer Test had two objectives. First, the results would support government representatives in the source selection process for the Block IV contract. Second, to assess the maturity of the Version 12.01 software as it approached IOT&E.

In August 1996, version 12.01 underwent a system confidence demonstration to determine readiness for the November 1996 IOT&E. Because the software was not ready, further work and two additional system confidence demonstrations followed in August and September 1996. Both demonstrations indicated that the system was not ready for operational test.

After postponement of the IOT&E, DoD approved the Army's acquisition of a low-rate initial production of 81 of the fiscal year 1997 computers for a Training Base Operational Assessment. The Training Base Operational Assessment, completed in May 1997, determined the merits of allowing the Army to procure sufficient numbers of MCS to field the training base prior to successful completion of an IOT&E. The Under Secretary of Defense for Acquisition and Technology considered that assessment in authorizing the Army in July 1997 to proceed with its acquisition plans.

The Army successfully completed the Training Base Operational Assessment in May 1997. The DOT&E considered the results of this assessment and agreed that the MCS Software Version 12.01 functionality is adequate for use in the training base. However, the MCS must complete an IOT&E prior to a Milestone III decision to procure and field to operational units.

The Army continues to plan for an IOT&E in June 1998. Technical tests completed in December 1997 indicate that the MCS will be ready to enter IOT&E. However, the March start date appears optimistic because the technical testing has moved from August to December 1997.

MCS has shown significant improvement in software stability and functionality. However, a major issue requiring resolution during the IOT&E is the ability of soldiers to employ the MCS and displace command posts consistent with the expected operational tempo. The ability to displace command posts touches on system concerns including system administration, network robustness, and suitability of the MCS for anticipated operational conditions.