NOTE: Click here for questions and answers from the Y2K Information Session held on March 31, 1999.

Or, you can click here for the Word Document version. You will need either Microsoft Word or the Microsoft Word Reader.

Q: Do you anticipate problems with transfer of funds to outside institutions? Is it the responsibility of UC or the financial institution to ensure transfers, e.g. direct deposit, go through correctly?

A: No problems are anticipated. The banking industry is highly regulated and regulators have been working for several years to ensure that Y2K problems are addressed. UC Berkeley has worked with Wells Fargo to ensure that our payroll (Surepay/direct deposit) and accounts payable payments sent via that bank do not have any Y2K problems. Once Wells Fargo receives payment information, it is their responsibility to make sure that transfers to other financial institutions occur correctly; no Y2K problems with that are expected either.

Q. What is an embedded system, as opposed to an embedded chip?

A. An embedded system has a clock, and is therefore subject to Y2K problems. An embedded chip is a microprocessor, and unless it communicates with another system with a clock, it isn't subject to Y2K problems. (For more information on these and other terms, see the Glossary.)

Q. Has UCB done contingency planning for January 1, 2000?

A. Some individual departments have contingency plans. UCB has a standard emergency plan in place, but no overall campus contingency plan for the Y2K issue. We have concluded that the existing emergency plan, supplemented with phone lists of individuals available December 31-January 2, is adequate. UCB is fortunate that (1) we have, as of mid-November, finished virtually all Y2K work, and have sufficient resources to finish the rest by year-end; (2) January 1, 2000, occurs at a very quiet time, with students not due back to classes for more than two weeks; (3) as an educational institution, we aren't critically dependent on outside suppliers. Because of these factors, contingency planning can be decentralized and relatively informal.

Q. What about Y2K efforts at Lawrence Berkeley National Laboratory (LBNL)? [Formerly Lawrence Berkeley Laboratory (LBL)] A lot of research work is done there by UCB faculty and staff, and a lot of UCB students work there.

A. Although UC Berkeley has many close relationships with LBNL, UCB is not responsible for or involved in Y2K efforts at LBNL. LBNL is a separate entity, reporting to the University of California Office of the President, via the Laboratory Administrative Office. Some of LBNL's Y2K information can be found at their Computing Infrastructure Support Y2K Bug Reource Center, in their February 1998 articles, and their July 1998 articles. In addition, Y2K progress of LBNL and other federal laboratories funded by the U.S. Department of Energy are being tracked as part of DOE's Y2K status.

Q. How do I comment on something that is missing from the campus Y2K web site?

A. Comments and suggestions are definitely welcome. Send e-mail to salas@uclink4.berkeley.edu.