<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="P0b002ee18039a2a4">
<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">1999-09-24</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>15 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:T-AIMD-99-297</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-99-297</identifier>
<identifier type="local">P0b002ee18039a2a4</identifier>
<identifier type="former package identifier">f:ai99297t</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-T-AIMD-99-297</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-T-AIMD-99-297</accessId>
 <reportNumber>T-AIMD-99-297</reportNumber>
 <subject>Internal controls</subject>
 <subject>Systems conversions</subject>
 <subject>Computer software verification and validation</subject>
 <subject>Information resources management</subject>
 <subject>Computer software</subject>
 <subject>Strategic information systems planning</subject>
 <subject>Data integrity</subject>
 <subject>Y2K</subject>
 <identifier>Y2K</identifier>
 <identifier>District of Columbia</identifier>
 <type>Testimony</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
</extension>
<titleInfo>
 <title>Year 2000 Computing Challenge: Status of the District of</title>
</titleInfo>
<abstract>Pursuant to a congressional request, GAO discussed the District of
Columbia&apos;s efforts to address the year 2000 challenge, focusing on the:
(1) District&apos;s progress in fixing its systems and the remaining risks it
faces; (2) actions it needs to take to mitigate these risks over the
next 3 months; and (3) recent experience it needs to capitalize on to
strengthen long-term information technology management.&lt;p/&gt;GAO noted that: (1) since February 1999, the District has taken actions
to strengthen its year 2000 project management and continuity and
contingency planning; (2) as of September 20, the District&apos;s Chief
Technology Officer reported the status of the District&apos;s year 2000
conversion effort for its mission-critical software applications; (3) of
a total of 223 mission-critical applications, 130 were tested and
determined to be ready for the year 2000; (4) of the remaining 93
mission-critical applications, 70 were reported as undergoing testing
and 23 were reported as still being remediated; (5) it should be noted,
however, that the status information being reported by the Chief
Technology Officer is not consistent with information being reported
separately by District agencies; (6) this raises the concern that
District managers are not getting accurate enough data on system status
on which to base their year 2000-related decisions; (7) District
officials told GAO that they are in the process of reconciling these
data differences; (8) at this point in time, the District can do little
to increase the rate of progress on system remediation and testing; (9)
however, the District can improve its chances for success by better
using the tools it has at hand; (10) by more aggressively monitoring the
status of key projects and ensuring that its status information is
accurate, District management can be better-equipped to focus attention
on projects running late and redirect resources, if necessary, to ensure
that most critical processes are remediated and tested on time; (11)
also, viable business continuity plans are important to all
organizations--even those who have already completed remediation and
testing; (12) they are especially critical to the District because of
the real possibility that remediation and testing may not be complete by
year&apos;s end; (13) the reason the District is so far behind in addressing
the year 2000 problem is that it did not have effective management over
its information technology assets and projects; (14) as a result, it
started very late and will finish late; and (15) by capitalizing on
recent year 2000-experience, the District can implement management
processes and controls needed to ensure that its technology assets are
effectively supporting city operations.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-99-297/html/GAOREPORTS-T-AIMD-99-297.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-99-297/pdf/GAOREPORTS-T-AIMD-99-297.pdf</url>
</location>
<identifier type="preferred citation">GAO/T-AIMD-99-297</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-99-297</url>
</location>
<note>Testimony</note>
<extension>
 <searchTitle>GAO/T-AIMD-99-297; Year 2000 Computing Challenge: Status of the District of;
            </searchTitle>
</extension>
<subject>
 <topic>Internal controls</topic>
 <topic>Systems conversions</topic>
 <topic>Computer software verification and validation</topic>
 <topic>Information resources management</topic>
 <topic>Computer software</topic>
 <topic>Strategic information systems planning</topic>
 <topic>Data integrity</topic>
 <topic>Y2K</topic>
 <topic>Y2K</topic>
 <topic>District of Columbia</topic>
</subject>
</mods>