<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="P0b002ee18039bc48">
<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>
 <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">2003-08-13</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>46 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:GAO-03-1010R</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-GAO-03-1010R</identifier>
<identifier type="local">P0b002ee18039bc48</identifier>
<identifier type="former package identifier">f:d031010r</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-GAO-03-1010R</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-GAO-03-1010R</accessId>
 <reportNumber>GAO-03-1010R</reportNumber>
 <subject>Combat readiness</subject>
 <subject>Defense capabilities</subject>
 <subject>Strategic planning</subject>
 <subject>Program evaluation</subject>
 <subject>Strategic mobility forces</subject>
 <subject>Army Future Combat Systems</subject>
 <type>Correspondence</type>
 <accountNo>A08038</accountNo>
</extension>
<titleInfo>
 <title>Issues Facing the Army&apos;s Future Combat Systems Program</title>
</titleInfo>
<abstract>Under its transformation efforts, the Army plans to change the
way it organizes, trains, deploys, and equips its forces. It	 
expects the future force to be organized around brigade-size	 
units that perform virtually all Army combat functions. The Army 
wants to fully equip these units with the Future Combat Systems  
(FCS), a family of 18 networked, warfighting systems which are	 
intended to be more lethal, survivable, deployable, and 	 
sustainable than existing heavy combat systems. In order to	 
deploy faster, the FCS vehicles are expected to be a fraction of 
the weight of existing heavy armored fighting vehicles. The Army 
believes that nontraditional fighting tactics coupled with an	 
extensive information network will compensate for the loss of	 
size and armor mass by utilizing information superiority and	 
synchronized operations to see, engage, and destroy the enemy	 
before the enemy detects the future forces. The Army has	 
allocated about $22 billion for the FCS program during fiscal	 
years 2004 through 2009 and several billions more for non-FCS	 
programs that the FCS will need to become fully capable. In	 
addition, the Army recently implemented FCS schedule changes,	 
which added about 2 years to the system development and 	 
demonstration (SDD) phase.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-GAO-03-1010R/html/GAOREPORTS-GAO-03-1010R.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-GAO-03-1010R/pdf/GAOREPORTS-GAO-03-1010R.pdf</url>
</location>
<identifier type="preferred citation">GAO-03-1010R</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-GAO-03-1010R</url>
</location>
<note>Correspondence</note>
<extension>
 <searchTitle>GAO-03-1010R; Issues Facing the Army&apos;s Future Combat Systems Program;
            </searchTitle>
</extension>
<subject>
 <topic>Combat readiness</topic>
 <topic>Defense capabilities</topic>
 <topic>Strategic planning</topic>
 <topic>Program evaluation</topic>
 <topic>Strategic mobility forces</topic>
 <topic>Army Future Combat Systems</topic>
</subject>
</mods>