<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="P0b002ee180397a66">
<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-10-02</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>13 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:T-AIMD-99-4</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-99-4</identifier>
<identifier type="local">P0b002ee180397a66</identifier>
<identifier type="former package identifier">f:ai99004t</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-4</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-4</accessId>
 <reportNumber>T-AIMD-99-4</reportNumber>
 <subject>Municipal governments</subject>
 <subject>Embedded computer systems</subject>
 <subject>Systems conversions</subject>
 <subject>Strategic information systems planning</subject>
 <subject>Systems compatibility</subject>
 <subject>Data integrity</subject>
 <subject>Information resources management</subject>
 <subject>Information systems</subject>
 <subject>Computer software verification and validation</subject>
 <identifier>Y2K</identifier>
 <identifier>District of Columbia</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 Faces Tremendous Challenges in Ensuring Vital Services Are Not Disrupted</title>
</titleInfo>
<abstract>Pursuant to a congressional request, GAO discussed the year 2000 risks
facing the District of Columbia, focusing on: (1) its progress to date
in fixing its systems; and (2) the District&apos;s remediation strategy.&lt;p/&gt;GAO noted that: (1) until June 1998, the District had made very little
progress in addressing the year 2000 problem; (2) to compensate for its
late start, the District has hired a new chief technology officer,
appointed a full-time year 2000 program manager, established a year 2000
program office, and continued to use its chief technology officer
council to help coordinate and prioritize efforts; (3) the District also
contracted with an information technology firm to assist in completing
the remediation effort; (4) to accomplish this in the short time
remaining, the District and the contractor plan to concurrently: (a)
remediate and test system applications; (b) assess and fix the
information technology (IT) infrastructure, including the data centers,
hardware, operating systems, and telecommunications equipment; (c)
assess and correct noninformation technology assets; and (d) develop
contingency plans; (5) the District has done the following: (a)
developed an inventory of information technology applications; (b)
initiated pilot remediation and test efforts with the pension and
payroll system; (c) adopted a contingency planning methodology which it
is now piloting on the 911 system, the water and sewer system, and the
lottery board system; and (d) developed a strategy for remediating
non-IT assets which is now being tested on the water and sewer system;
(6) the District&apos;s recent actions reflect a commitment on the part of
the city to address the year 2000 problem and to make up for the lack of
progress; (7) however, the District is still significantly behind in
addressing the problem; (8) the District has not: (a) identified all of
its essential business functions that must continue to operate; (b)
finished assessing its IT infrastructure and its non-information
technology assets; (c) provided guidance to its agencies on testing; and
(d) identified resources that will be needed to complete remediation and
testing; (9) until the District completes the assessment phase, it will
not have reliable estimates on how long it will take to renovate and
test mission-critical systems and processes and to develop business
continuity and contingency plans; (10) District officials acknowledge
that the city is not able to provide assurance that all critical systems
will be remediated on time; and (11) therefore, to minimize disruptions
to vital city services, it will be essential for the District to
effectively manage risks over the next 15 months.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-99-4/html/GAOREPORTS-T-AIMD-99-4.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-99-4/pdf/GAOREPORTS-T-AIMD-99-4.pdf</url>
</location>
<identifier type="preferred citation">GAO/T-AIMD-99-4</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-99-4</url>
</location>
<note>Testimony</note>
<extension>
 <searchTitle>GAO/T-AIMD-99-4; Year 2000 Computing Crisis: The District of Columbia Faces Tremendous Challenges in Ensuring Vital Services Are Not Disrupted;
            </searchTitle>
</extension>
<subject>
 <topic>Municipal governments</topic>
 <topic>Embedded computer systems</topic>
 <topic>Systems conversions</topic>
 <topic>Strategic information systems planning</topic>
 <topic>Systems compatibility</topic>
 <topic>Data integrity</topic>
 <topic>Information resources management</topic>
 <topic>Information systems</topic>
 <topic>Computer software verification and validation</topic>
 <topic>Y2K</topic>
 <topic>District of Columbia</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>