Year 2000 (Y2K) Testing and Compliance in the National Weather Service - Lessons Learned

The Year2000 (Y2K) software problem affects any organization that utilizes data processing software and hardware. The National Weather Service (NWS) has a vast array of automated systems producing great amounts of computer generated data and is thus not immune to the Y2K problem. Therefore, the NWS has been working since 1996 to ensure that all NWS systems are Y2K-compliant in order that no operations are disrupted when the millennium date change from December 31, 1999, to January 1, 2000, as well as the leap-day crossover from February 28, 2000, to February 29, 2000, both occur.

All NWS computer-based systems (i.e., applications software, system software, hardware, communications, non-information processing systems) were assessed in accordance with the U.S. Government Year 2000 (Y2K) compliance standards and requirements. These systems were all certified as being Y2K compliant. A series of integrated end-to-end tests were performed in order to validate this compliance. The end-to-end testing process involved a a diverse group of NWS partners and customers (e.g., Federal, private, and international) working together to ensure that the Y2K problem would not cause any negative impacts to the weather community. The end-to-end testing allowed the NWS to certify its full Y2K compliance as of March 31, 1999. Results of the testing along with other Y2K information can be found at the following web site address: http://www.oso1.x3.nws.noaa.gov/y2k

This paper is an update to information provided at the 15th annual IIPS Conference held in January 1999.