<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="P0b002ee18038d24f">
<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-10-29</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>70 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:AIMD-00-24</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-00-24</identifier>
<identifier type="local">P0b002ee18038d24f</identifier>
<identifier type="former package identifier">f:ai00024</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-00-24</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-00-24</accessId>
 <reportNumber>AIMD-00-24</reportNumber>
 <subject>Y2K</subject>
 <subject>Computer software verification and validation</subject>
 <subject>Systems conversions</subject>
 <subject>Strategic information systems planning</subject>
 <subject>Information resources management</subject>
 <subject>Systems compatibility</subject>
 <subject>Federal agency accounting systems</subject>
 <subject>Financial management systems</subject>
 <identifier>FMS Year 2000 Program</identifier>
 <identifier>Supplemental Security Income Program</identifier>
 <identifier>FMS Electronic Federal Tax Payment System</identifier>
 <identifier>Government On-Line Accounting Link System</identifier>
 <identifier>Y2K</identifier>
 <identifier>SSI</identifier>
 <type>Letter Report</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
</extension>
<titleInfo>
 <title>Year 2000 Computing Challenge: Financial Management</title>
</titleInfo>
<abstract>Pursuant to a congressional request, GAO reviewed the Financial
Management Service&apos;s (FMS) Year 2000 program, focusing on whether FMS
is: (1) effectively managing its year 2000 testing; and (2) taking
adequate steps to mitigate the year 2000 risks associated with four
mission-critical systems that were not implemented by the Office of
Management and Budget&apos;s (OMB) March 1999 deadline.&lt;p/&gt;GAO noted that: (1) FMS has established effective year 2000 test
management controls for its six most mission-critical systems; (2) for
instance, FMS developed test guidance, defined compliance criteria, and
defined test roles and responsibilities; (3) together, these and other
controls, provided the infrastructure needed for planning, executing and
reporting year 2000 test activities, including system acceptance and
end-to-end testing; (4) in line with GAO&apos;s year 2000 test guide, which
is widely accepted and used in government and private industry, FMS also
engaged an independent verification and validation (IV&amp;V) contractor to
ensure that testing was complete and thorough; (5) GAO reviewed this
contractor&apos;s work and found that: (a) its scope was consistent with
GAO&apos;s year 2000 test guide; and (b) the contractor identified no
material problems with system acceptance testing of five of FMS&apos; six
most critical systems; (6) GAO also found that although the IV&amp;V
contractor did not review the sixth system, FMS took steps to gain
reasonable assurance that year 2000 testing for this system was
effectively managed; (7) further, FMS has established effective
management controls in performing its portion of selected year 2000
end-to-end tests; (8) specifically, FMS satisfied the end-to-end testing
key processes defined in GAO&apos;s guidance for three critical test events;
(9) these events focused on three of FMS&apos; most important core business
functions--social security payments, Supplemental Security Income
payments, and Internal Revenue Service (IRS) tax refund payments; (10)
the tests included FMS processing payment files from Social Security
Administration and IRS, printing checks, and transmitting electronic
payment files to Federal Reserve Banks; (11) as of October 1, 1999, FMS
reported that it had implemented two of the four systems that did not
meet the March 31, 1999, OMB-imposed deadline for implementation; (12)
for the remaining two, FMS reported that it has: (a) renovated and
tested both; (b) implemented both at two of five sites; and (c) plans to
complete their implementation by the end of October 1999; and (13) in
addition, FMS has prepared and plans to test system contingency plans
for these late systems as well as its other mission-critical systems.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-00-24/html/GAOREPORTS-AIMD-00-24.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-00-24/pdf/GAOREPORTS-AIMD-00-24.pdf</url>
</location>
<identifier type="preferred citation">GAO/AIMD-00-24</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-00-24</url>
</location>
<note>Letter Report</note>
<extension>
 <searchTitle>GAO/AIMD-00-24; Year 2000 Computing Challenge: Financial Management;
            </searchTitle>
</extension>
<subject>
 <topic>Y2K</topic>
 <topic>Computer software verification and validation</topic>
 <topic>Systems conversions</topic>
 <topic>Strategic information systems planning</topic>
 <topic>Information resources management</topic>
 <topic>Systems compatibility</topic>
 <topic>Federal agency accounting systems</topic>
 <topic>Financial management systems</topic>
 <topic>FMS Year 2000 Program</topic>
 <topic>Supplemental Security Income Program</topic>
 <topic>FMS Electronic Federal Tax Payment System</topic>
 <topic>Government On-Line Accounting Link System</topic>
 <topic>Y2K</topic>
 <topic>SSI</topic>
</subject>
</mods>