Year 2000 Failures Likely

Federal agencies will probably not be able to prevent some of their computers from malfunctioning in the year 2000 because of a coding snafu, General Accounting Office officials told Congress yesterday.

Testifying before the House Government Reform and Oversight Subcommittee on Government Management, Information and Technology, GAO Director of Information Resources Management Joel Willemsen said there is a high probability that it is too late for agencies to fix all the coding in their computers that will cause the computers to think it is 1900 instead of 2000.

Because computer applications developed in the 1960s and 1970s use six digit date codes, when the date hits 01-01-00, the applications will read that as 1900. Some computer systems will simply freeze up or shut down when this happens. Others will continue to function, but the data they work with will be corrupted.

Willemsen said agencies should concentrate on fixing essential computer systems like air traffic control systems, Medicare databases, and national defense systems. GAO has categorized the Year 2000 problem as one of 25 high-risk areas for federal managers.

Earlier this month, the Office of Management and Budget estimated it would cost the federal government $2.3 billion to update all its computer programs to deal with the year 2000 problem. Last year, industry experts estimated the cost at closer to $30 billion.

Rep. Steve Horn, R-Calif., chairman of the subcommittee, questioned the OMB estimate, calling it "way too low."

GAO has released a guide for federal information technology managers to follow as they make Year 2000 fixes. It identifies five steps in the process:

  • Awareness. Define the year 2000 problem and gain executive level support. Establish a year 2000 program team. Ensure that everyone in the organization is aware of the problem.
  • Assessment. Assess the year 2000 impact on the enterprise. Identify core business areas, inventory and analyze systems supporting the core business areas, and prioritize their conversion or replacement. Develop contingency plans to handle data exchange issues, lack of data, and bad data. Identify and secure the necessary resources.
  • Renovation. Convert, replace, or eliminate selected platforms, applications, databases and utilities. Modify interfaces.
  • Validation. Test, verify, and validate converted or replaced platforms, applications, databases, and utilities. Test the performance, functionality, and integration of converted or replaced platforms, applications, databases, utilities and interfaces in an operational environment.
  • Implementation. Implement converted or replaced platforms, applications, databases, utilities and interfaces. Implement data exchange contingency plans, if necessary.
Stay up-to-date with federal news alerts and analysis — Sign up for GovExec's email newsletters.
Close [ x ] More from GovExec

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • Sponsored by Brocade

    Best of 2016 Federal Forum eBook

    Earlier this summer, Federal and tech industry leaders convened to talk security, machine learning, network modernization, DevOps, and much more at the 2016 Federal Forum. This eBook includes a useful summary highlighting the best content shared at the 2016 Federal Forum to help agencies modernize their network infrastructure.

  • Sponsored by CDW-G

    GBC Flash Poll Series: Merger & Acquisitions

    Download this GBC Flash Poll to learn more about federal perspectives on the impact of industry consolidation.

  • Sponsored by One Identity

    One Nation Under Guard: Securing User Identities Across State and Local Government

    In 2016, the government can expect even more sophisticated threats on the horizon, making it all the more imperative that agencies enforce proper identity and access management (IAM) practices. In order to better measure the current state of IAM at the state and local level, Government Business Council (GBC) conducted an in-depth research study of state and local employees.

  • Sponsored by Aquilent

    The Next Federal Evolution of Cloud

    This GBC report explains the evolution of cloud computing in federal government, and provides an outlook for the future of the cloud in government IT.

  • Sponsored by Aquilent

    A DevOps Roadmap for the Federal Government

    This GBC Report discusses how DevOps is steadily gaining traction among some of government's leading IT developers and agencies.

  • Sponsored by LTC Partners, administrators of the Federal Long Term Care Insurance Program

    Approaching the Brink of Federal Retirement

    Approximately 10,000 baby boomers are reaching retirement age per day, and a growing number of federal employees are preparing themselves for the next chapter of their lives. Learn how to tackle the challenges that today's workforce faces in laying the groundwork for a smooth and secure retirement.

  • Sponsored by Hewlett Packard Enterprise

    Cyber Defense 101: Arming the Next Generation of Government Employees

    Read this issue brief to learn about the sector's most potent challenges in the new cyber landscape and how government organizations are building a robust, threat-aware infrastructure

  • Sponsored by Aquilent

    GBC Issue Brief: Cultivating Digital Services in the Federal Landscape

    Read this GBC issue brief to learn more about the current state of digital services in the government, and how key players are pushing enhancements towards a user-centric approach.

  • Sponsored by CDW-G

    Joint Enterprise Licensing Agreements

    Read this eBook to learn how defense agencies can achieve savings and efficiencies with an Enterprise Software Agreement.

  • Sponsored by Cloudera

    Government Forum Content Library

    Get all the essential resources needed for effective technology strategies in the federal landscape.


When you download a report, your information may be shared with the underwriters of that document.