<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="P0b002ee1803974ec">
<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-24</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>12 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:T-AIMD-99-85</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-99-85</identifier>
<identifier type="local">P0b002ee1803974ec</identifier>
<identifier type="former package identifier">f:ai99085t</identifier>
<recordInfo>
 <recordContentSource authority="marcorg">DGPO</recordContentSource>
 <recordCreationDate encoding="w3cdtf">2010-08-12</recordCreationDate>
 <recordChangeDate encoding="w3cdtf">2011-03-24</recordChangeDate>
 <recordIdentifier source="DGPO">GAOREPORTS-T-AIMD-99-85</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-85</accessId>
 <reportNumber>T-AIMD-99-85</reportNumber>
 <subject>Y2K</subject>
 <subject>Internal controls</subject>
 <subject>Information resources management</subject>
 <subject>Strategic information systems planning</subject>
 <subject>Data integrity</subject>
 <subject>Information systems</subject>
 <subject>Systems conversions</subject>
 <subject>Computer software verification and validation</subject>
 <identifier>Y2K</identifier>
 <identifier>Customs Service Automated Commercial System</identifier>
 <identifier>Treasury Enforcement Communications System</identifier>
 <identifier>Customs Service Seized Assets and Case Management Tracking</identifier>
 <identifier>System</identifier>
 <identifier>Customs Service Automated Export System</identifier>
 <type>Testimony</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
</extension>
<titleInfo>
 <title>Year 2000 Computing Crisis: Customs Is Effectively Managing Its Year 2000 Program</title>
</titleInfo>
<abstract>Pursuant to a congressional request, GAO discussed the Customs Service&apos;s
progress in addressing the year 2000 computing problem, focusing on
Customs&apos;: (1) progress to date; (2) program management; and (3) future
challenges.&lt;p/&gt;GAO noted that: (1) as of January 1999, Customs reported that it had met
milestones recommended by the Office of Management and Budget for
renovating and validating most of its mission-critical systems; (2) it
reported that it had completed renovation, validation and systems
acceptance testing of all five of its mission-critical systems; (3) it
plans to complete end-to-end testing for these systems and associated
telecommunications systems by March 1999; (4) Customs reported that 95
percent of the information technology products assessed is compliant, 4
percent requires renovation or replacement and one percent is to be
retired; (5) Customs&apos; program management structures and processes are
entirely consistent with GAO guidance, and Customs&apos; good progress to
date is largely attributable to this program management capability; (6)
Customs has done the following: (a) established a year 2000 Program
Office and designated a year 2000 Program Manager in May 1997 and
charged the office with authority over and responsibility for agencywide
year 2000 efforts, including such functional areas as year 2000
contracting, budgeting and planning, technical support to project teams,
quality assurance, auditing and reporting; (b) engaged its senior
executives in the year 2000 effort by charging the agency&apos;s Executive
Council with approving and overseeing the implementation of the year
2000 strategy and resolving such issues as institutional year 2000
priorities; (c) developed a year 2000 Strategic Plan and year 2000
Operational Program Management Plan in June 1998; and (d) issued
policies, guidelines, and procedures for managing and implementing the
year 2000 program, including guidance on quality assurance,
configuration management, and testing, as well as business continuity
and contingency planning; (7) Customs still needs to conduct end-to-end
testing of the systems that support important trade missions; (8)
additionally, Customs still needs to complete its contingency plans for
ensuring continuity of its core business areas in the event of year
2000-induced system failures; (9) Customs faces serious risks outside of
its control; (10) given the number of Customs ports of entry throughout
the United States, localized disruptions in infrastructure-related
services could seriously impact Customs business operations; and (11) as
Customs works to develop, test, and complete its contingency plans, it
must ensure that these localized event scenarios are adequately
addressed.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-99-85/html/GAOREPORTS-T-AIMD-99-85.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-99-85/pdf/GAOREPORTS-T-AIMD-99-85.pdf</url>
</location>
<identifier type="preferred citation">GAO/T-AIMD-99-85</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-99-85</url>
</location>
<note>Testimony</note>
<extension>
 <searchTitle>GAO/T-AIMD-99-85; Year 2000 Computing Crisis: Customs Is Effectively Managing Its Year 2000 Program;
            </searchTitle>
</extension>
<subject>
 <topic>Y2K</topic>
 <topic>Internal controls</topic>
 <topic>Information resources management</topic>
 <topic>Strategic information systems planning</topic>
 <topic>Data integrity</topic>
 <topic>Information systems</topic>
 <topic>Systems conversions</topic>
 <topic>Computer software verification and validation</topic>
 <topic>Y2K</topic>
 <topic>Customs Service Automated Commercial System</topic>
 <topic>Treasury Enforcement Communications System</topic>
 <topic>Customs Service Seized Assets and Case Management Tracking</topic>
 <topic>System</topic>
 <topic>Customs Service Automated Export System</topic>
</subject>
</mods>