<mods xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" ID="P0b002ee18039528e">
<name type="corporate">
 <namePart>United States Government Publishing Office</namePart>
 <role>
  <roleTerm authority="marcrelator" type="text">publisher</roleTerm>
  <roleTerm authority="marcrelator" type="code">pbl</roleTerm>
</role>
 <role>
  <roleTerm authority="marcrelator" type="text">distributor</roleTerm>
  <roleTerm authority="marcrelator" type="code">dst</roleTerm>
</role>
</name>
<name type="corporate">
 <namePart>United States</namePart>
 <namePart>Government Accountability Office</namePart>
 <namePart>National Security and International Affairs Division</namePart>
 <role>
  <roleTerm authority="marcrelator" type="text">author</roleTerm>
  <roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
 <description>Government Organization</description>
</name>
<typeOfResource>text</typeOfResource>
<genre authority="marcgt">government publication</genre>
<language>
 <languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</language>
<extension>
 <collectionCode>GAOREPORTS</collectionCode>
 <category>Legislative Agency Publications</category>
 <waisDatabaseName>gao</waisDatabaseName>
 <branch>legislative</branch>
 <dateIngested>2010-08-12</dateIngested>
</extension>
<originInfo>
 <publisher>U.S. Government Printing Office</publisher>
 <dateIssued encoding="w3cdtf">1997-10-16</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>25 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:NSIAD-98-15</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-NSIAD-98-15</identifier>
<identifier type="local">P0b002ee18039528e</identifier>
<identifier type="former package identifier">f:ns98015</identifier>
<recordInfo>
 <recordContentSource authority="marcorg">DGPO</recordContentSource>
 <recordCreationDate encoding="w3cdtf">2010-08-12</recordCreationDate>
 <recordChangeDate encoding="w3cdtf">2011-03-23</recordChangeDate>
 <recordIdentifier source="DGPO">GAOREPORTS-NSIAD-98-15</recordIdentifier>
 <recordOrigin>machine generated</recordOrigin>
 <languageOfCataloging>
  <languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</languageOfCataloging>
</recordInfo>
<accessCondition type="GPO scope determination">fdlp</accessCondition>
<extension>
 <docClass>REPORT</docClass>
 <accessId>GAOREPORTS-NSIAD-98-15</accessId>
 <reportNumber>NSIAD-98-15</reportNumber>
 <subject>Army procurement</subject>
 <subject>Military training</subject>
 <subject>Computer software verification and validation</subject>
 <subject>Military systems analysis</subject>
 <subject>Management information systems</subject>
 <subject>Military communication</subject>
 <subject>Defense capabilities</subject>
 <subject>Computers</subject>
 <identifier>Army Maneuver Control System</identifier>
 <identifier>Army Command and Control System Common Hardware and</identifier>
 <identifier>Software Program</identifier>
 <identifier>Army Battlefield Command System</identifier>
 <identifier>Army Tactical Command and Control System</identifier>
 <identifier>ATCCS</identifier>
 <type>Letter Report</type>
 <seriesAbbrev>NSIAD</seriesAbbrev>
 <USCode title="10">
                      <section number="2399"></section>
                      <section number="2400"></section>
                </USCode>
 <USCode title="31">
                      <section number="720"></section>
                </USCode>
</extension>
<titleInfo>
 <title>Battlefield Automation: Software Problems Hinder Development of the Army&apos;s Maneuver Control System</title>
</titleInfo>
<abstract>GAO reviewed the Army&apos;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.&lt;p/&gt;GAO noted that: (1) since its 1993 reorganization, the MCS has continued
to experience development problems; (2) the initial operational test and
evaluation of version 12.01 software has slipped 28 months, from
November 1995 to March 1998, and interim tests have shown that
significant software problems continue; (3) despite these problems, the
Army awarded a contract in September 1996 for the concurrent development
of the next software versions--12.1, 12.2, and 12.3--which are being
developed by a new contractor and may involve substantially different
software; (4) if the Army&apos;s current development strategy for the MCS is
not strengthened, development problems may continue to occur; (5)
currently, the army&apos;s strategy allows: (a) less than full operational
testing of version 12.1; and (b) development of follow-on versions 12.2
and 12.3 to start about 18 months before the operational testing of each
version&apos;s predecessor; (6) despite the fact that the MCS has yet to
undergo an initial operational test and evaluation or be approved for
production, the Army plans to acquire 207 computers in fiscal years 1997
and 1998 to increase the number of computers available for system
training; (7) program officials stated that they need to acquire the
computers before operational testing to provide not only MCS specific
training but also training for the larger Army Battle Command System, of
which the Army Tactical Command and Control System and the MCS are major
components; and (8) the 207 computers, however, are not needed to
satisfy any of the three legislated reasons for low-rate initial
production before an initial operational test and evaluation.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-NSIAD-98-15/html/GAOREPORTS-NSIAD-98-15.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-NSIAD-98-15/pdf/GAOREPORTS-NSIAD-98-15.pdf</url>
</location>
<identifier type="preferred citation">GAO/NSIAD-98-15</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-NSIAD-98-15</url>
</location>
<note>Letter Report</note>
<extension>
 <searchTitle>GAO/NSIAD-98-15; Battlefield Automation: Software Problems Hinder Development of the Army&apos;s Maneuver Control System;
            </searchTitle>
</extension>
<subject>
 <topic>Army procurement</topic>
 <topic>Military training</topic>
 <topic>Computer software verification and validation</topic>
 <topic>Military systems analysis</topic>
 <topic>Management information systems</topic>
 <topic>Military communication</topic>
 <topic>Defense capabilities</topic>
 <topic>Computers</topic>
 <topic>Army Maneuver Control System</topic>
 <topic>Army Command and Control System Common Hardware and</topic>
 <topic>Software Program</topic>
 <topic>Army Battlefield Command System</topic>
 <topic>Army Tactical Command and Control System</topic>
 <topic>ATCCS</topic>
</subject>
<relatedItem type="isReferencedBy">
 <titleInfo>
  <title>United States Code</title>
  <partNumber>Title 10 Section 2399</partNumber>
  <partNumber>Title 10 Section 2400</partNumber>
</titleInfo>
 <identifier type="USC citation">10 U.S.C. 2399</identifier>
 <identifier type="USC citation">10 U.S.C. 2400</identifier>
</relatedItem>
<relatedItem type="isReferencedBy">
 <titleInfo>
  <title>United States Code</title>
  <partNumber>Title 31 Section 720</partNumber>
</titleInfo>
 <identifier type="USC citation">31 U.S.C. 720</identifier>
</relatedItem>
</mods>