<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="P0b002ee18037be6c">
<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">1997-09-26</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>31 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:AIMD-97-149</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-97-149</identifier>
<identifier type="local">P0b002ee18037be6c</identifier>
<identifier type="former package identifier">f:ai97149</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-97-149</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-97-149</accessId>
 <reportNumber>AIMD-97-149</reportNumber>
 <subject>Computer software verification and validation</subject>
 <subject>Strategic information systems planning</subject>
 <subject>Military inventories</subject>
 <subject>Management information systems</subject>
 <subject>Computer software</subject>
 <subject>Systems conversions</subject>
 <subject>Logistics</subject>
 <subject>Inventory control systems</subject>
 <subject>Human resources utilization</subject>
 <identifier>Army Commodity Command Standard System</identifier>
 <identifier>Army Continuing Balance System-Expanded</identifier>
 <identifier>Army Materiel Command Year 2000 Action Plan</identifier>
 <identifier>Software Capability Maturity Model</identifier>
 <identifier>DOD Year 2000 Management Plan</identifier>
 <type>Letter Report</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
</extension>
<titleInfo>
 <title>Defense Computers: LSSC Needs to Confront Significant Year 2000 Issues</title>
</titleInfo>
<abstract>Pursuant to a congressional request, GAO reviewed: (1) the status of the
Logistics Systems Support Command&apos;s (LSSC) efforts to correct Commodity
Command Standard System (CCSS) Year 2000 systems problems; and (2) the
appropriateness of LSSC&apos;s strategy and actions for ensuring that CCSS
Year 2000 issues will be successfully addressed.&lt;p/&gt;GAO noted that: (1) the Year 2000 problem is one of the most
comprehensive and complex information management projects ever faced by
LSSC; (2) if not successfully completed, the procurement of weapon
systems and their spare parts, accounting for the sales of Army
equipment and services to allies, and the financial management of $9
billion of inventory could be disrupted; (3) as a result, it could be
extremely difficult to efficiently and effectively equip and sustain the
Army&apos;s forces around the world; (4) LSSC has completed several actions
to address the CCSS Year 2000 problem; (5) a Year 2000 project manager
and management staff have been designated, a project manager charter and
schedule were developed, and supplementary contractor support was
acquired to assist with assessment tasks; (6) regularly scheduled
quarterly meetings are held by the Army Materiel Command (AMC)
headquarters to report LSSC Year 2000 status; (7) these steps are
compatible with the Department of Defense&apos;s (DOD) suggested approach and
consistent with those found in GAO&apos;s five-phased approach for planning,
managing, and evaluating Year 2000 projects; (8) although LSSC commenced
its Year 2000 project over a year ago, there are several issues facing
LSSC that, if not completely addressed, may result in the failure of
CCSS to successfully operate at the year 2000; (9) LSSC has yet to
completely address: (a) competing workload priorities and staffing
issues; (b) the appropriate mix and scheduling of needed testing data
and expertise as well as the development of test plans; (c) the scope
and substance of written interface agreements with system interface
partners to ensure that CCSS subsystems will be capable of exchanging
data at the year 2000; and (d) contingency plan development to help
assure that Army missions will be accomplished if CCSS is not fully
available to users by the year 2000; (10) LSSC&apos;s risk of failure is
increased because the agency has not attained the level of software
development and maintenance maturity that would provide the foundation
needed for successful management of large-scale projects such as the
Year 2000 initiative; and (11) because CCSS is used to support military
readiness, these critical elements must be resolved and aggressively
pursued to enable LSSC to achieve a Year 2000 compliant environment
prior to the year 2000.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-97-149/html/GAOREPORTS-AIMD-97-149.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-97-149/pdf/GAOREPORTS-AIMD-97-149.pdf</url>
</location>
<identifier type="preferred citation">GAO/AIMD-97-149</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-97-149</url>
</location>
<note>Letter Report</note>
<extension>
 <searchTitle>GAO/AIMD-97-149; Defense Computers: LSSC Needs to Confront Significant Year 2000 Issues;
            </searchTitle>
</extension>
<subject>
 <topic>Computer software verification and validation</topic>
 <topic>Strategic information systems planning</topic>
 <topic>Military inventories</topic>
 <topic>Management information systems</topic>
 <topic>Computer software</topic>
 <topic>Systems conversions</topic>
 <topic>Logistics</topic>
 <topic>Inventory control systems</topic>
 <topic>Human resources utilization</topic>
 <topic>Army Commodity Command Standard System</topic>
 <topic>Army Continuing Balance System-Expanded</topic>
 <topic>Army Materiel Command Year 2000 Action Plan</topic>
 <topic>Software Capability Maturity Model</topic>
 <topic>DOD Year 2000 Management Plan</topic>
</subject>
</mods>