[Congressional Record Volume 144, Number 3 (Thursday, January 29, 1998)]
[Senate]
[Pages S238-S239]
From the Congressional Record Online through the Government Publishing Office [www.gpo.gov]




         Y2K, THE FAA, AND INFRASTRUCTURE IN THE UNITED STATES

 Mr. MOYNIHAN. Mr. President, today's New York Times has 
confirmed what many on the forefront of fixing the Year 2000 Computer 
Problem have already learned. Namely, that the problem is not just a 
programming glitch within software (programs run on the computer), but 
a larger crisis of identifying and renovating hardware (the computer 
itself).
  As the Times story relates: ``The problem was first thought to be a 
programming glitch. But as the F.A.A. is demonstrating, the line 
between hardware and software is not so clear, because of computer 
instructions, called micro-code, that are built in and are more basic 
than the programs the computer runs. In some instances, the answer may 
be the wholesale replacement of computers that might otherwise have run 
for years. Early indications are that many airlines will also throw out 
numerous computers.''
  Like many private sector businesses, the FAA is finding that it may 
have to replace the interrelated computer systems themselves--in this 
case, systems that provide for the safety of air flight in America. 
While some programmers at the FAA believe the systems can be debugged 
without replacing them, the company which built the hardware,

[[Page S239]]

IBM, has recommended replacing the machines.
  There is a lesson to be learned here. Consultants confronted with 
this problem have told me this all along. The problem is deeper than 
the programs. It deals with the micro-code beneath the programs. This 
micro-code is in everything from our telecommunications systems to the 
personal computer on your desk--essentially the infrastructure of the 
company or agency.
  Thus, we peel back another layer of the onion. The FAA is taking 
multiple approaches to its fix: a combination of debugging and 
replacement. On the one hand, debugging old systems risks that they 
won't be fully tested until after the year 2000. On the other hand, 
replacing them costs millions upon millions. When the maker of the 
machines--in this case IBM--recommends replacement, and a failed effort 
to debug the machines could mean lives lost in air accidents across the 
country, I would prefer we lean heavily on the replacement approach.
  With fewer than two years until January 1, 2000, this lesson must be 
learned quickly and throughout the Federal Government. A few Chief 
Information Officers who are ahead of the curve on this issue are 
similarly discovering they not only have to fix the application codes, 
but they also have to make their infrastructure--telecommunication 
systems, micro-computers, and electrical components--year 2000 
compliant.
  In the few months ahead, agencies must be ready and willing to admit 
the extent of their problems, and find solutions that will be balanced 
between debugging and replacement. At the same time, we in Congress 
must be ready and willing to assist agencies in what is beginning to 
look a lot like a matter of damage control.
  I ask that today's Times article, ``F.A.A. to Fix and Replace Aging 
Computers,'' be printed in the Record.
  The article follows:

                [From the New York Times, Jan. 29, 1998]

               F.A.A. to Fix and Replace Aging Computers

                          (By Matthew L. Wald)

       Washington, Jan. 28--The Federal Aviation Administration 
     said today that it would hunt down and remove the ``year 
     2000'' bugs from 40 crucial, aging air traffic control 
     computers, and then throw out the computers themselves.
       One team at the F.A.A. has promised to have the bugs fixed 
     within 90 days. The leader of a second team announced today 
     that the agency would replace the computers anyway, at a cost 
     of about $100 million, because of uncertainty over whether 
     the software changes can ever be tested adequately. But since 
     there is also uncertainty over whether all the computers can 
     be replaced within the next 23 months, the de-bugging will 
     continue.
       Around the world, the issue, known in data processing as 
     ``Y2K,'' is perplexing companies because computers that 
     record the date as a 2-digit number will conclude that the 
     year after 1999 is 1900.
       The problem was first thought to be a programming glitch. 
     But as the F.A.A. is demonstrating, the line between hardware 
     and software is not so clear, because of computer 
     instructions, called micro-code, that are built in and are 
     more basic than the programs the computer runs.
       In some instances, the answer may be the wholesale 
     replacement of computers that might otherwise have run for 
     years. Early indications are that many airlines will also 
     throw out numerous computers.
       George L. Donohue, associate administrator of the F.A.A. 
     for research and acquisitions, said, ``Some of the software 
     people now say that even if you think you've fixed all the 
     micro-code, there's no way to be sure.''
       But, speaking today at an air traffic control conference, 
     Dr. Donohue said that trying simultaneously to de-bug the 
     system and replace it was a good ``belt and suspenders 
     approach,'' because it was impossible to be sure the F.A.A. 
     could replace the aging computers in the next 23 months.
       Drucella Andersen, a spokeswoman for the agency, said, 
     ``We're trying to do both because it gives us the highest 
     assurance and insurance.''
       Just last week the F.A.A. invited reporters to tour a ``war 
     room'' where a team of software engineers is coordinating the 
     de-bugging of 297 interrelated computer systems that make up 
     the National Airspace System.
       The machines are at the heart of the 20 air traffic control 
     centers that handle high-altitude, long-distance flights, and 
     officials said they were confident that their replacement 
     would not be necessary. The software changes are projected to 
     cost $91 million, and involve 22 million lines of software.
       The International Business Machines Corporation, which made 
     the computers, warned the F.A.A. last fall that it no longer 
     had the engineers or software tools to find the bugs, and 
     recommended replacing the machines.
       Dr. Donohue said the computers were about 14 years old, 
     which he termed old by the standards of private industry but 
     young for the F.A.A.
       The agency's budget does not include the estimated $100 
     million to replace the computers, but officials said they 
     could delay other modernization projects.

                          ____________________