Y2K May 97


	YEAR 2000 ALERT


	May, 1997 • Number One


	A newsletter for the Columbia University community on year 2000 issues

It’s Monday, January 3, 2000. You’re returning to work after a great New Year’s celebration. You drive over an MTA bridge and all the EZ-Pass lanes are closed and you have to wait forever to pay cash. Or you’re traveling by subway and your Metro-Card doesn’t scan and you have to stand on a huge line to buy a token.

Either way, you’re an hour late for work. You get to the office and the elevators aren’t functioning. Finally you sit at your desk and turn on your computer. But it doesn’t work. Your secretary says his PC seems okay, but the scheduling software has lost all the appointments he’s been typing in for months.


	While the specifics of this scenario are fictional, such problems could occur. The year 2000 computer software bug is making headlines in The New York Times, The Wall Street Journal and other publications. If not corrected before the new century, the year 2000 bug will create havoc for any equipment using a microprocessor with date-dependent logic.


	The problem in a nutshell Many computers use the format mm/dd/yy to generate dates, writing January 1, 1999 as 01/01/99. When the year 2000 comes, the computer will write it as 01/01/00. Therefore, a child born in 2000 will be considered 100 years old on his birthday!


	To prevent these problems from seriously affecting the functioning of the University, all departments should begin to identify critical areas that could be affected when the year 2000 is upon us. The good news is that there is time to fix the problems—but we must actively and progressively work on solving them, if we are to be ready.


	AIS is responsible for the University’s central information systems (human resources, financial, alumni, etc.) and we have been planning and converting these systems to be year 2000 compliant. Although there is still much work to do, we feel that we are well on our way to dealing with the problem. What we are not so sure about are the many computerized systems in use throughout the University for which AIS does not have responsibility, as well as departmental desktop software and equipment, especially older versions and models. In raising these concerns, we do not want to create an atmosphere of alarm, but rather to urge you to consider if and how the new century will affect you and your working environment.

	Therefore, we have created this Year 2000 ALERT newsletter to ensure that everyone who needs to understand the severity and complexity of the problem is aware of it. The newsletter will be issued periodically as a way to share ideas, solutions, technical papers, and other relevant information. We hope that you find Year 2000 ALERT informative and useful. Robert Juckiewicz Deputy Vice President, AIS


	How can AIS help my department? AIS can share technical approaches, review project plans, and advise on potential consultants, who can examine software and hardware in your office computing environment. What we cannot do is provide programmers to prepare a plan for you or to make required code changes, as we simply do not have the necessary resources. This must be the responsibility of each University department. But we do encourage you to contact our Year 2000 Coordinator to discuss ways that we might be of help to you.

	In addition, if there is sufficient interest, AIS and Internal Audit will co-sponsor a seminar or working group to promote the exchange of information and sharing of resources needed to address year 2000 problems. AIS and Internal Audit will also be glad to attend appropriate meetings of your existing groups. Details will be announced later, but anyone interested should contact either Fred or Rebecca.


	OK. So what should I do now?

	Fall 1997: Determine resources required and time lines to complete conversions and changes.

	Fall 1998: Complete all software changes, and modify or replace equipment.

	All of 1999: Test, test, and test again!


	Year 2000 Tip If you renew any software licenses or purchase any hardware or software, make sure that the product is year 2000 compliant, or will be before the century ends. You must get this assurance in writing and included in your contract.