Your plans should contain the detailed approaches for alternatives to achieve mission goals in the event of outages as envisioned in replacement and renovation delay scenarios. After you become familiar with the minimal activities that need to be addressed to develop a contingency plan (as described below), you should:

• Read through our Contingency Plan Guidelines for more detailed guidance in developing a contingency plan
• Take a look at Sample Content of a Contingency Plan which details the types of information to be included in each section of your plan, and other related contingency plan information (including several sample plans)
• See the Year 2000 Contingency Plans briefing for background information
• See Guidelines for a Consequence Management Plan for help with establishing a plan to minimize and manage risks, as well as providing time to preposition resources in a way that gives you a better chance of quickly recovering from any problems you might encounter.

While the specific details of your individual Year 2000 contingency management plans must be worked out by your users and IT personnel and all computer center and networking support teams, all contingency plans should address the following areas, at a minimum:

1. Objective of the plan (e.g., continue normal operations, continue in a degraded mode, abort the function as quickly as safely possible, etc.)
   
2. Criteria for invoking the plan (e.g., missing a renovation milestone, reaching the projected Y2K-related failure date, experiencing serious system failures, etc.)
   
3. Expected life of the plan (How long can operations continue in contingency operating mode?)
   
4. Roles, responsibilities and authority
   
5. Plan(s) creation and checkout of resource constraints to plan for each contingency and objective
   
6. Training on and testing of plans
   
7. Procedures for invoking contingency mode
   
8. Procedures for operating in contingency mode
   
9. Resource plan for operating in contingency mode (e.g., staffing, scheduling, materials, supplies, facilities, temporary hardware and software, communications, etc.)



10. Criteria for returning to normal operating mode
    
11. Procedures for returning to normal operating mode
    
12. Procedures for recovering lost or damaged data

Serving as Architects of Information Advantage.™
Copyright © 1997-2008, The MITRE Corporation. All rights reserved.
MITRE is a registered trademark of The MITRE Corporation.
Material on this site may be copied and distributed with permission only.

Privacy Policy | Contact Us