Internet Y2K Campaign

Best Practices
Example Assessment Plan

Contingency Plans

| Introduction | Inventory | Assessment | Remediation | Testing | Roll Out | Contingency Plans |
| Example Assessment Spreadsheet HTML or WordPerfect | Stickers |

Networks do contingency planning every day to prepare for normal day-to-day eventualities. For example, there is an impressive global web hosting service in Northern Virginia, USA. It is a complex facility offering premium services. In order to protect this investment and the customers, the Service Provider has a sophisticated fire control system, a security system, and a diesel generator with enough fuel to run for about five days. The Service Provider is simply preparing for normal life in Virginia which includes thunderstorms that knock out the power.

Now is the time for you to reexamine your own contingency plans. Whatever they are, they should be fully available for Y2K. What problems are foreseeable? What actions can you take now to prepare? Is it likely that you will have subscribers confronting problems? Perhaps you need to do additional training of your support staff so that you can respond to these problems and perhaps you may consider initiating a publicity campaign, giving notice to your subscribers that they should be using Y2K ready versions of applications. You may wish to plan full back ups of both your network and of your business (make sure all of your financial information is properly in order) and you may decide that now is the time to upgrade your backup power supply.

The sky is not falling. Contingency planning is a prudent part of any networks day-to-day experience. Y2K is simply an excellent opportunity to ensure that your plans are in order.

Check list of possible contingency items:

  • Backup power supply
  • Full system backups
  • Full business backups (make sure your records are in order, etc.)
  • Provide notice to users to update applications
  • Train support staff to respond to users with Y2K problems
  • Clarify command structure in event rapid response is required
  • Determine technical staff needs during critical date conversion periods
  • Emergency systems (fire suppression, security)
  • Consider turning off nonessential equipment prior to date conversion and then slowly turning equipment back on one at a time
  • Consider communication needs to remote POPs (for staff coordination purposes)

FCC Y2K Souvenirs
Support This Site

More Information

  • Contingency Planning.
  • CUNA Mutual Insurance Society Guidelines for Developing a YEAR 2000 Compliance Test.
  • Information Week's Year 2000 Contingency Planning.
  • Casper Jones, Software Productivity Research Contingency Planning: Damage Control for Euro and Year 2000 Software Problems
  • GSA's Y2K Contingency Planning Page.
  • FCC's NRIC Focus Group 1: Y2K Impact on Networks
  • Minnesota Year 2000 Project: Contingency Planning.
  • Mitre's Y2K Contingency Management Plan Outline.
  • Steve Davis' Managing Year 2000 Risks Part III Part Three - Contingency Planning.
  • Tech-Beamers Focus on Testing.
  • Texas Department of Information Resources Guidelines for Contingency Planning.
  • Texas Guidebook 2000 Commissioned by The Office of the Governor August 1998 Austin, Texas - Section Six: Contingency Planning

  • Year 2000 Computing Crisis: Business Continuity and Contingency Planning (GAO/AIMD-10.1.19, March 1998) (PDF).
    | Home | News |Bulletin Board | Best Practices | Mailing list | Contact us | Webmaster |