Contingency Planning Methodology
Appendix E. Contingency Planning Forms
- System Inventory Data Collection Form
- Interface Data Collection Form
- 3rd Party Data Collection Form
- Technical / Tactical Problem Scenario - Contingency Planning Worksheet
- Business Function Data Collection Form
- Functional Problem Scenario - Contingency Planning Worksheet
System Inventory Data Collection Form |
||||||
| System ID | System Name | System Type* | System Criticality | Owner & Contract | Failure Type | Failure Probability |
* IT System, End-User, Embedded or other as agreed upon by planning team.
Interface Data Collection Form |
||||||
| Interface ID | Interface Name | Interface Type* | Interface Owner & Contact | Interface Criticality | Failure Type | Failure Criticality |
* EDI, tape, disk, other (specify).
3rd Party Data Collection Form |
||||||
| 3rd Party ID | 3rd Party Name | 3rd Party Type* | 3rd Party Contact & Address | 3rd Party Criticality | Failure Type | Failure Probability |
Business partner, infrastructure supplier, parts supplier, service supplier, other (specify).
Technical / Tactical Problem Scenario
Contingency Planning Worksheet
This worksheet is used to document a single problem scenario that could impact a system, interface or supplier. Tactical project teams should use one form per failure scenario to document the impact and the contingency plan for that failure scenario. Note that multiple failure scenarios per item require the use of multiple copies of this form. Data collected using this form should ultimately be loaded into the contingency planning database.
The following data documents the system, interface or 3rd party at risk.
Business Unit: ____________
TYPE (check one): System:____ Interface:____ 3rd Party/Supplier:____
ID:____ Name:______________________________________________
Criticality: ___________(1-5 rating: 1=no impact & 5=mission critical)
Contact Name: ______________________________________________
Address: ______________________________________________
Phone/Email: ______________________________________________
The following data documents a failure scenario associated with this item.
Current Mitigating Action:__________________________________________
___________________________________________
Problem Scenario: ___________________________________________
___________________________________________
Trigger Date: ___________________________________________
Problem Probability: _____
(1-5: 1 = 0-20%, 2=20-40%, 3=40-60%,4=60-80%, 5=80-100%)
Criticality/Problem Probability Score: _______
Projected Loss/Damage: $__________/______________________________
(non-monetary damages)
(Comments on cost of corrective action)
Business Function Supported by this system, supplier or interface (could be more than one):
Function(s): __________________________________________________________
__________________________________________________________
__________________________________________________________
Business Function Data Collection Form Business Unit _______________ |
||||
| Function ID | Function Name | Function Contact | Function Contact Info | Functional Criticality |
Functional Problem Scenario
Contingency Planning Worksheet
This worksheet is used to document a single problem scenario that could impact a business function. One form per failure scenario should be used by functional contingency planning teams to document the impact and the contingency plan for that failure scenario. Note that multiple failure scenarios per business function require the use of multiple copies of this form. The data collected should ultimately be loaded into the contingency planning database.
The following data documents the business function at risk.
Business Unit: __________ (specify enterprise or infrastructure if applicable)
Impacted Function: __________________________________________________________
Function ID: __________
Functional Criticality: __________(1-5 rating: 1 = no impact & 5 = mission critical)
Contact Name: __________________________________________________________
Address: _______________________________________________________________
_______________________________________________________________
Phone/Email: ____________________________________________________________
The following data documents a failure scenario associated with this function.
Current Mitigating Action: _________________________________________________
Problem Scenario: ________________________________________________________
________________________________________________________
Trigger Date: ____________________
Problem Probability: _____ (1-5: 1 = 0-20%, 2=20-40%, 3=40-60%, 4=60-80%, 5=80-100%)
Criticality / Problem Probability Score: _____ (functional criticality * problem probability)
Projected Loss/Damage: $__________ / _____________________________________________
(Non-monetary damages)
Contingency Plan Resolution: _______________________________________________________
__________________________________________________________________________________
Contingency Cost: $__________ / ____________________________________________________
(Comments on cost of corrective action)
Problem Triggers: (list systems, suppliers or interfaces that directly trigger the failure scenario)
Systems: __________________________________________________________
__________________________________________________________
Suppliers: __________________________________________________________
__________________________________________________________
Interfaces: __________________________________________________________
Note: that problem triggers will be used to link business functions to source of problem in database.