|
BUILDING A YEAR 2000 DISASTER PLAN Despite their best intentions, many U.S. companies will not be Year 2000 compliant in time for January 1, 2000. Assuming your company has a Y2K effort underway, now is the ideal time to build a Y2K contingency plan. Here are some items you can incorporate into a Y2K contingency plan: 1. Remember that Y2K affects all software-based systems. In addition to IT/IS applications, voice and data network devices and their management systems are at risk as well. It is just as important to assess the Y2K risks in your networks as it is in your business systems. 2. Prioritize your efforts to obtain Y2K compliance by focusing on your most critical hardware and software. Try to have as many mission-critical systems converted as possible. 3. Cut back or defer non-critical production as much as possible to provide additional Y2K compliance testing time. 4. Verify Y2K compliance for specialized systems, e.g., HVAC, lighting, alarms, and environmental control, to ensure they function properly. 5. Make sure that all critical systems and files are backed up as close to the Y2K deadline as possible. 6. Establish critical dates, e.g., when to complete final backups of files, when to cease production, and when to shift production to an alternate processing facility. 7. With that in mind, make arrangements with hot site firms to use their computing and network facilities on an interim basis. Be sure to verify they are Y2K compliant! 8. As an alternative, make arrangements to borrow computer time from other companies that have completed their Y2K compliance testing. 9. Establish interim processing arrangements with all your equipment vendors, network service providers, and other key suppliers. 10. Notify all key customers, suppliers, shareholders and other important organizations in advance about your plans to deal with Y2K compliance. 11. Continue activities to modify code on all date-sensitive systems to accommodate Y2K changes. 12. When faced with the task of upgrading a large number of network devices, if you know in advance it is unlikely you will complete all conversions in time, consider testing mission-critical non-compliant devices for Y2K problems to better understand the impacts of Y2K failures on your business. BY THE WAY… About the Author: |