<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="P0b002ee1803719cf">
<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>Accounting and Information Management 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">1996-02-27</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>11 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:AIMD-96-28</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-96-28</identifier>
<identifier type="local">P0b002ee1803719cf</identifier>
<identifier type="former package identifier">f:ai96028</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-AIMD-96-28</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-AIMD-96-28</accessId>
 <reportNumber>AIMD-96-28</reportNumber>
 <subject>Embedded computer systems</subject>
 <subject>Systems conversions</subject>
 <subject>Bomber aircraft</subject>
 <subject>Advanced weapons systems</subject>
 <subject>Computer services contracts</subject>
 <subject>Defense capabilities</subject>
 <subject>Life cycle costs</subject>
 <subject>Air Force procurement</subject>
 <subject>Computer software</subject>
 <subject>Military cost control</subject>
 <identifier>B-1B Conventional Mission Upgrade Program</identifier>
 <identifier>Joint Standoff Weapon</identifier>
 <identifier>Wind Corrected Munitions Dispenser</identifier>
 <identifier>Air Force Operational Requirements Document</identifier>
 <identifier>Air Force System Requirements Document</identifier>
 <identifier>B-1B Aircraft</identifier>
 <type>Letter Report</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
 <USCode title="31">
                      <section number="720"></section>
                </USCode>
</extension>
<titleInfo>
 <title>Embedded Computers: B-1B Computers Must Be Upgraded to Support Conventional Requirements</title>
</titleInfo>
<abstract>The Air Force plans to upgrade the computer and software systems aboard
the B-1B bomber, which the Pentagon envisions as the &quot;backbone&quot; of its
new bomber fleet. The goal is to transform the B-1B from a nuclear
weapons carrier to a conventional weapons carrier. The 1970s vintage
computer systems found on the B-1B are operating at near capacity and,
without upgrades, cannot support additional weapons and capabilities,
such as cluster bombs, a global positioning system for better navigation
and guidance, and more-accurate and higher-range weapons. This report
discusses recent decisions by the Air Force to upgrade the B-1B&apos;s
embedded computer systems, particularly in view of concerns GAO raised
about the simple memory upgrade.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-96-28/html/GAOREPORTS-AIMD-96-28.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-96-28/pdf/GAOREPORTS-AIMD-96-28.pdf</url>
</location>
<identifier type="preferred citation">GAO/AIMD-96-28</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-96-28</url>
</location>
<note>Letter Report</note>
<extension>
 <searchTitle>GAO/AIMD-96-28; Embedded Computers: B-1B Computers Must Be Upgraded to Support Conventional Requirements;
            </searchTitle>
</extension>
<subject>
 <topic>Embedded computer systems</topic>
 <topic>Systems conversions</topic>
 <topic>Bomber aircraft</topic>
 <topic>Advanced weapons systems</topic>
 <topic>Computer services contracts</topic>
 <topic>Defense capabilities</topic>
 <topic>Life cycle costs</topic>
 <topic>Air Force procurement</topic>
 <topic>Computer software</topic>
 <topic>Military cost control</topic>
 <topic>B-1B Conventional Mission Upgrade Program</topic>
 <topic>Joint Standoff Weapon</topic>
 <topic>Wind Corrected Munitions Dispenser</topic>
 <topic>Air Force Operational Requirements Document</topic>
 <topic>Air Force System Requirements Document</topic>
 <topic>B-1B Aircraft</topic>
</subject>
<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>