<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="P0b002ee180376b74">
<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-02-19</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:T-AIMD-99-84</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-99-84</identifier>
<identifier type="local">P0b002ee180376b74</identifier>
<identifier type="former package identifier">f:ai99084t</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-T-AIMD-99-84</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-84</accessId>
 <reportNumber>T-AIMD-99-84</reportNumber>
 <subject>Y2K</subject>
 <subject>Computer software</subject>
 <subject>Systems conversions</subject>
 <subject>Schedule slippages</subject>
 <subject>Municipal governments</subject>
 <subject>Information resources management</subject>
 <subject>Strategic information systems planning</subject>
 <subject>Computer software verification and validation</subject>
 <subject>Data integrity</subject>
 <identifier>Y2K</identifier>
 <type>Testimony</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
 <law congress="104" isPrivate="false" number="8"></law>
</extension>
<titleInfo>
 <title>Year 2000 Computing Crisis: The District of Columbia Remains Behind Schedule</title>
</titleInfo>
<abstract>Pursuant to a congressional request, GAO discussed the challenges facing
the District of Columbia in addressing the year 2000 problem, focusing
on: (1) the District of Columbia&apos;s progress in fixing its information
systems; and (2) the risks it now faces.&lt;p/&gt;GAO noted that: (1) the District Year 2000 Program Office has
established an orderly process for addressing the year 2000 problem and
has been working hard to develop an understanding of its core business
processes and supporting information systems; (2) the Year 2000 Program
Manager holds weekly meetings to review deviations from schedule
baselines and to monitor the overall program status; (3) additionally,
the Program Office recently began preparing year 2000 report cards for
all systems included in the District year 2000 effort; (4) these report
cards, which are provided to each agency, summarize the progress being
made on each system; (5) the District&apos;s recent actions reflect a
commitment to protect its key business processes from year 2000 failure;
(6) however, its schedule for fulfilling this commitment is highly
compressed and moves through four phases of the year 2000 process in
less than one year-assessment by the end of February, renovation and
contingency planning by the end of September, and system validation by
the end of October; (7) the District remains over one year behind GAO&apos;s
recommended schedule and is just now transitioning from the assessment
to the renovation phase of the year 2000 conversion model; (8) according
to the District&apos;s Year 2000 Program Manager, at this time, the District
has only renovated about 5 percent of its mission-critical systems, with
less than 1 percent of its mission-critical systems completing
validation; (9) further, only one of the District&apos;s over 200
mission-critical systems, which is responsible for paying District
employees and pensioners, has been through the entire conversion process
and is now implemented; (10) only six business continuity plans--such as
the plan for documenting the manual registering of students for the
University of the District of Columbia&apos; student enrollment process--have
been finalized; (11) it will be difficult for the District to adequately
compensate for its late start in initiating effective action on the year
2000 challenge; and (12) given the District&apos;s compressed year 2000
schedule--which allows no margin for error--and to have a reasonable
chance of avoiding serious disruption to public services, it must be
well prepared for likely project delays and failures of mission-critical
systems.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-99-84/html/GAOREPORTS-T-AIMD-99-84.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-99-84/pdf/GAOREPORTS-T-AIMD-99-84.pdf</url>
</location>
<identifier type="preferred citation">GAO/T-AIMD-99-84</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-99-84</url>
</location>
<note>Testimony</note>
<extension>
 <searchTitle>GAO/T-AIMD-99-84; Year 2000 Computing Crisis: The District of Columbia Remains Behind Schedule;
            </searchTitle>
</extension>
<subject>
 <topic>Y2K</topic>
 <topic>Computer software</topic>
 <topic>Systems conversions</topic>
 <topic>Schedule slippages</topic>
 <topic>Municipal governments</topic>
 <topic>Information resources management</topic>
 <topic>Strategic information systems planning</topic>
 <topic>Computer software verification and validation</topic>
 <topic>Data integrity</topic>
 <topic>Y2K</topic>
</subject>
<relatedItem type="isReferencedBy">
 <titleInfo>
  <title>United States Public Law 8 (104th Congress)</title>
</titleInfo>
 <identifier type="public law citation">Public Law 104-8</identifier>
</relatedItem>
</mods>