Y2K Update

With less than 160 days remaining until January 1, 2000, it is imperative that everyone continue their hard work ensuring that all critical systems are Y2K compliant. It is important that all billing and business systems, as well as infrastructure and other date-sensitive systems, be ready for the transition to Y2K. To further ensure a smooth transition, you should consult with those companies whose systems interface with yours to determine their compliance status.

Regardless of how thoroughly you plan for Y2K compliance, last-minute surprises are inevitable. After you have finished the necessary steps of awareness, inventory, assessment, remediation, testing, and implementation, potential risks must be identified and managed. It may be impossible to correct 100 percent of the issues in time; therefore, problems with mission critical processes should be solved first. As you are aware, because of your interaction with a multitude of other entities, there are Y2K issues beyond your control that may affect you. One important way to be sufficiently prepared is through the development and application of a well-defined and executable contingency plan.

The RUS Y2K Home Page (www.usda.gov/rus/y2k/index.htm) has information on contingency planning and links to other sites with a wealth of information on the topic. Links are also included to sites that discuss all aspects of the Y2K problem including descriptions of the steps in correcting it.

We would like to thank all of the electric and telecommunications borrowers who responded to our Y2K Compliance survey. A copy of the latest summary of responses can also be found on the RUS Y2K Home Page. We appreciate your continued interest and cooperation in this crucial matter.

If you have questions about general Y2K issues, please contact our Y2K Compliance Coordinator, John Schell, at (202) 720-0671, or by E-mail at jschell@rus.usda.gov. Your RUS General Field Representative is also available to provide assistance in helping you ensure Y2K compliance.

 

[Abbreviations] [Return to Table of Contents]