Defense Computers: LSSC Needs to Confront Significant Year 2000 Issues
AIMD-97-149
Published: Sep 26, 1997. Publicly Released: Sep 26, 1997.
Skip to Highlights
Highlights
Pursuant to a congressional request, GAO reviewed: (1) the status of the Logistics Systems Support Command's (LSSC) efforts to correct Commodity Command Standard System (CCSS) Year 2000 systems problems; and (2) the appropriateness of LSSC's strategy and actions for ensuring that CCSS Year 2000 issues will be successfully addressed.
Recommendations
Recommendations for Executive Action
| Agency Affected | Recommendation | Status |
|---|---|---|
| Logistics Systems Support Center | The Director, LSSC, should act to improve LSSC's software development process that will provide the basis for achieving Compatibility Maturity Model (CMM) level 2 maturity. |
Closed – Not Implemented
LSSC's position is that it does not need to elevate to CMM level 2 to complete its year 2000 project. Moreover, LSSC stated that it has no intention of initiating action to elevate from a CMM level 1 designation to CMM level 2 until its year 2000 effort is completed on December 31, 1999.
|
| Logistics Systems Support Center | The Director, LSSC, should immediately assess the impact of competing workload and staffing demands on the CCSS Year 2000 project. Based on this assessment, the Director should consider: (1) cancelling or deferring less critical software projects until after the Year 2000 project is substantially completed; and (2) augmenting the Year 2000 project with staff having the necessity skills to ensure timely completion of the project. |
Closed – Implemented
LSSC identified system change packages which could be cancelled or postponed in June 1997 and action was taken by AMC to approve and reschedule LSSC's workload in late August 1997. In addition, LSSC initiated contract actions to acquire experienced personnel to assist with the renovation and testing phases of its Year 2000 project. This contract was approved in September 1997 and work commenced shortly after.
|
| Logistics Systems Support Center | The Director, LSSC, should ensure that LSSC has the capability to complete the testing of all CCSS subsystems and programs. Specifically, LSSC should: (1) determine test requirements; (2) identify the testing staff needed; (3) finalize Year 2000 plans describing how the testing staff will be acquired and scheduled for developing Year 2000 test compliant test scenarios and data; and (4) revise the Year 2000 test schedule to assure that enough time is available to meet Army-mandated deadlines for Year 2000 implementation. |
Closed – Implemented
LSSC has: (1) determined test requirements; (2) identified the testing staff needed; (3) finalized year 2000 plans describing how the testing staff will be acquired and scheduled for developing year 2000 test-compliant test scenarios and data; and (4) revised the year 2000 test schedule to ensure that enough time is available to meet Army-mandated deadlines for year 2000 implementation. LSSC completed Y2K testing of the CCSS system on March 3, 1999, and based largely on a review of test activities, CCSS was certified Y2K compliant by the Communications-Electronics Command and the Army Materiel Command on March 15, 1999. To provide additional assurance over the certification function, the DOD/IG reviewed LSSC's Y2K certification process on April 18, 1999 and concluded that it was properly performed.
|
| Logistics Systems Support Center | The Director, LSSC, should ensure that written interface agreements describe the method of data exchange between interfacing systems, name the entity responsible for performing the system interface modification, and state the completion date. |
Closed – Implemented
LSSC identified a total of 67 interfacing partners and has completed and approved memoranda of agreement for all 67 interfaces that describe the method of data exchange (i.e., data format), name the responsible entity for interface modification, and specify the date for ensuring the operability of the interface.
|
| Logistics Systems Support Center | The Director, LSSC, should develop a contingency plan that includes specific actions for ensuring that the Army's logistic functions continue to operate at appropriate levels if all or part of CCSS fails to work at the year 2000. |
Closed – Implemented
LSSC completed a system contingency plan for CCSS on February 5, 1999. In addition, each user command of CCSS has been directed to complete a functional contingency plan. According to LSSC, the DOD/IG reviewed the CCSS system contingency plan for adequacy and indicated the plan was sound, but should be tested. On August 23, 1999, LSSC tested the contingency plan.
|
Full Report
Office of Public Affairs
Topics
SoftwareSoftware verification and validationInventory control systemsLogisticsManagement information systemsMilitary inventoriesStaff utilizationStrategic information systems planningSystems conversionsY2K