Battlefield Automation: Software Problems Hinder Development of the Army's Maneuver Control System
NSIAD-98-15
Published: Oct 16, 1997. Publicly Released: Oct 16, 1997.
Skip to Highlights
Highlights
GAO reviewed the Army's developmental and acquisition plans for the Maneuver Control System (MCS), focusing on whether: (1) the current MCS software development strategy is appropriate to overcome prior development problems; and (2) 207 new computers for MCS-related training should be procured as planned.
Recommendations
Recommendations for Executive Action
| Agency Affected | Recommendation | Status |
|---|---|---|
| Department of Defense | The Secretary of Defense should direct the Secretary of the Army to set specific required capabilities for each software version beyond version 12.01, test those versions against specific pass/fail criteria for those capabilities, and award further development contracts once problems highlighted in that testing are resolved. |
In commenting on GAO's report, the Department of Defense (DOD) responded that the MCS development contract contains acceptance criteria (pass/fail criteria) for each of the three MCS versions to be developed under that five year contract. DOD stated that the Army would test each version against those criteria to ensure system maturity and determine continued operational effectiveness and suitability. DOD also stated that it would not support further contract awards until issues identified in those tests were resolved, but declined to specifically direct the Army as called for in the recommendation.
|
| Department of Defense | The Secretary of Defense should direct the Secretary of the Army to perform a full operational test and evaluation of MCS software version 12.1 to ensure that it provides the full capabilities of version 12.01. |
DOD stated that it will determine a risk level for MCS version 12.1 software following MCS version 12.01's completion of its initial operational test and evaluation. Based on the assigned risk level, DOD has stated that it will then determine the level of testing that is needed for MCS version 12.1 software. MCS version 12.01 underwent initial operational test and evaluation and failed. As a result, DOT&E is now requiring that MCS version 12.1 undergo a full initial operational test and evaluation.
|
| Department of Defense | The Secretary of Defense should direct the Secretary of the Army to procure additional MCS computers only after an initial operational test and evaluation and a full-rate production decision have been completed. | DOD stated that it had directed the Army to not procure or field more MCS hardware for operational units until MCS had completed required testing and a production decision had been made. This action was only partially responsive to the recommendation, as it would have allowed the Army to proceed with a planned procurement of MCS computers for training purposed. However, based on GAO's review and in line with this recommendation, GAO provided congressional staff and committees information on a potential reduction in the Army's fiscal year 1998 budget request and a potential rescission of fiscal year 1997 funds. As a result, Congress reduced the Army's fiscal year 1998 MCS funding by...
|
Full Report
Public Inquiries
Topics
Army procurementSoftware verification and validationComputersDefense capabilitiesManagement information systemsMilitary communicationMilitary systems analysisMilitary trainingU.S. ArmyOperational testing