<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="P0b002ee18039f3d3">
<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">1998-01-16</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>32 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:AIMD-98-35</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-98-35</identifier>
<identifier type="local">P0b002ee18039f3d3</identifier>
<identifier type="former package identifier">f:ai98035</identifier>
<recordInfo>
 <recordContentSource authority="marcorg">DGPO</recordContentSource>
 <recordCreationDate encoding="w3cdtf">2010-08-12</recordCreationDate>
 <recordChangeDate encoding="w3cdtf">2011-03-28</recordChangeDate>
 <recordIdentifier source="DGPO">GAOREPORTS-AIMD-98-35</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-98-35</accessId>
 <reportNumber>AIMD-98-35</reportNumber>
 <subject>Systems conversions</subject>
 <subject>Computer software verification and validation</subject>
 <subject>Strategic information systems planning</subject>
 <subject>Embedded computer systems</subject>
 <subject>Cost analysis</subject>
 <subject>Information resources management</subject>
 <subject>Systems compatibility</subject>
 <identifier>DOD Year 2000 Management Plan</identifier>
 <identifier>Air Force Year 2000 Program</identifier>
 <type>Letter Report</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
 <USCode title="31">
                      <section number="720"></section>
                </USCode>
</extension>
<titleInfo>
 <title>Defense Computers: Air Force Needs to Strengthen Year 2000 Oversight</title>
</titleInfo>
<abstract>Pursuant to a congressional request, GAO reviewed the Air Force&apos;s
program for solving its year 2000 computer systems problem, focusing on
the: (1) status of the Air Force&apos;s efforts to oversee its Year 2000
program; and (2) appropriateness of the Air Force&apos;s strategy and actions
for ensuring that the problem will be successfully addressed.&lt;p/&gt;GAO noted that: (1) as with other military services, the Air Force is
taking a decentralized approach to year 2000 correction--that is, it is
relying heavily on its components to identify and correct year 2000
problems affecting their own systems; (2) however, in providing
oversight for this effort, the Air Force must ensure that all of its
systems have been accounted for and that component actions are
successful; (3) it must also be well-positioned to make the resource
tradeoff decisions that are inevitable in any year 2000 effort and to
address conflicts between component approaches toward identifying and
correcting interfaces; (4) further, it must be able to provide
additional resources, such as testing facilities, that may be necessary
to correct and validate systems; (5) the Air Force has taken a number of
positive actions toward fulfilling its year 2000 oversight
responsibilities; (6) for example, it is taking inventory of its systems
and prioritizing them for conversion or replacement, and it has issued
extensive guidance on dealing with the year 2000 problem; (7) it has
also established a year 2000 working group comprised of focal points
from the components which aims to eliminate duplicative efforts, share
resources, and track component progress; (8) at the same time, the Air
Force has not yet adequately addressed several critical issues that
would ensure that it is well-positioned to deal with the later, and more
difficult, phases of year 2000 correction; (9) GAO&apos;s review revealed
that some components are failing to plan for the testing phase of their
year 2000 effort and develop contingency plans; (10) GAO also found that
some components are taking conflicting approaches toward determining the
actual impact or the program status of their system interfaces; (11) if
components and the Air Force do not promptly address and take consistent
action on these issues, they may well negate any success they may have
in making systems within their control year 2000 compliant; and (12)
while the Air Force has enlisted the services of the Air Force Audit
Agency to help address some of these concerns, this work needs to be
backed by comprehensive and continued Air Force oversight in order to
ensure that it can address unforeseen problems and delays in the next,
more difficult phases.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-98-35/html/GAOREPORTS-AIMD-98-35.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-98-35/pdf/GAOREPORTS-AIMD-98-35.pdf</url>
</location>
<identifier type="preferred citation">GAO/AIMD-98-35</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-98-35</url>
</location>
<note>Letter Report</note>
<extension>
 <searchTitle>GAO/AIMD-98-35; Defense Computers: Air Force Needs to Strengthen Year 2000 Oversight;
            </searchTitle>
</extension>
<subject>
 <topic>Systems conversions</topic>
 <topic>Computer software verification and validation</topic>
 <topic>Strategic information systems planning</topic>
 <topic>Embedded computer systems</topic>
 <topic>Cost analysis</topic>
 <topic>Information resources management</topic>
 <topic>Systems compatibility</topic>
 <topic>DOD Year 2000 Management Plan</topic>
 <topic>Air Force Year 2000 Program</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>