Scribd
Upload
1K views

Data Center Risk Management Plan

The document outlines a risk management plan for relocating a data center. It identifies over 30 risks across various categories such as construction, networks, organizational issues, systems failure, third party involvement, resources, project management, security, and applications. For each risk, it describes the likelihood and potential impact, as well as mitigation strategies and contingencies to address each risk. The plan provides a framework to assess and manage risks that could impact the success of the data center relocation project.

Uploaded by

Jorge Mendoza
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
1K views

Data Center Risk Management Plan

The document outlines a risk management plan for relocating a data center. It identifies over 30 risks across various categories such as construction, networks, organizational issues, systems failure, third party involvement, resources, project management, security, and applications. For each risk, it describes the likelihood and potential impact, as well as mitigation strategies and contingencies to address each risk. The plan provides a framework to assess and manage risks that could impact the success of the data center relocation project.

Uploaded by

Jorge Mendoza
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

RISK MANAGEMENT PLAN

DATA CENTER RELOCATION

Risk Management Plan


1 P ROJECT I NFORMATION
Project Number (if applicable): TBA
Project Name: Data Center Relocation
Date:
Project Ownership: Information Technology Services
Prepared by: Name, Project Manager
Project Contacts:
Name

Position

Phone

Primary
Other
Other

2 V ERSION C ONTROL / R ISK C HANGE L OG


Add new rows to the table as versions are created. No changes should me made to this
document without approval of the Project Manager, Data Center Relocation project. The
first row should reflect the current version in distribution.
Version
Number

Date

Description, Reasons, Comments Approvals

V1.0

January 12, 2009

Initial Draft C.E. Pierce

V1.1
V1.2
After acceptance of this document by the project Advisory committee any new risks or
changes to risk table should be listed here for quick identification by stakeholders.
Risk No.

Date

Description, Reasons, Comments Approvals

/VAR/WWW /APPS/CONVERSION/TMP/SCRATCH_3/289094616.DOC
PAGE 1 OF 6

RISK MANAGEMENT PLAN DATA CENTER RELOCATION

3 R ISK A SSESSMENT
Risk
Id.

AND

Risk description

M ANAGEMENT T ABLE
Likelihood

Mitigation Strategy

Impact

Contingency

Who owns

1. Construction/Build
1.1

Does not meet requirements

WW through site

1.2

Requirements were wrong

Reviews, WW, early sign-off of


critical items

1.3

Cabling/power not completed on


time

WW inspection

Delay equipment installation

L-H

Rectify, Delay move, compromise


Contingency budget or Accept

2. Network
2.1

Insufficient funds for min.


hardware & network

Re-negotiate budget, redesign


network

Stage move over long period

2.2

H/W Delivery, DOA

Order early, regular enquiries,


vendor inspection

Maintenance contracts & Vendor


Certification

2.3

Incorrect design

External peer review

L-M

Use basic functionality. Seek


vendor help

2.4

IP addressing schema fails

Dont change

L-H

Regress

2.5

Performance issues with WAN


Links

Identify and implement


monitoring and management
processes

Identify who is the approval & signoff delegate.

3. Organizational
3.1

Insufficient budget or budget over


run

Do detailed costing
Have budget approved

Increase in budget approved


Project delayed
Scope of move reduced and
compromise reached.

/VAR/WWW /APPS/CONVERSION/TMP/SCRATCH_3/289094616.DOC
PAGE 2 OF 6

RISK MANAGEMENT PLAN DATA CENTER RELOCATION

Risk
Id.
3.2

Risk description

Likelihood

Timetable for move not approved


or not workable

Mitigation Strategy
Sponsor and BU sign-off of
timeline

Impact

Contingency

Delay relocation

Who owns

Publish timeline
3.3

Cabling/power not completed on


time

WW inspection

Delay relocation

Develop a plan for every


system. Test each system

Use backup system

Develop a plan for every


system. Rehearse migration.
Appropriate consideration for
connectivity requirements.

4. Systems failure during migration track


4.1

4.2

4.3

Systems fail on cutover day

Full and adequate understanding


of the complexities and
interdependencies of systems
and application.

System latency from MCNC is


unacceptable

System owners to rectify failures


Using regression plans
Invoke rollback plan and redo
/correct system documentation
Delay migration

5. 3rd Party Issues


5.1

Key 3rd party staff unavailable


including :
Pinnacle,

Define migration schedule


requirements and engage
suppliers/contractors via
contracts

M-H

Seek alternate support

Sun, Cisco
Relocation specialist

/VAR/WWW /APPS/CONVERSION/TMP/SCRATCH_3/289094616.DOC
PAGE 3 OF 6

RISK MANAGEMENT PLAN DATA CENTER RELOCATION

Risk
Id.

Risk description

Likelihood

Mitigation Strategy

Impact

Contingency

Who owns

6. Resources
6.1

New Technology The system


staff at UNCC is not familiar with
virtualization technologies
planned for the project.

Will require extensive training of


staff and could cause project
delays with respect to time, cost
and quality.

6.2

Business resources unavailable


for user acceptance testing

Publish dates and get buy in.

6.3

IT resource contention for


migration

Backup test resource

Sign-off system relocation plans

IT test on behalf

Document test and acceptance


plans and authorize IT staff to
undertake testing for business.

Test in business hours after move

Co-ordination and prioritization

Business accepts no test


M

Cross skilling

External resources called in


Extend relocation time

Use external resources


6.4

Relocation preparation affected


by day to day operations and
other projects

M-H

Use Change Control process to


stop unauthorized system
changes

M-H

Use external resources


Delay relocation

Backfill key project staff


Use external resources
7.Project Management Risks
7.1

Inadequate project definition

Ensure Advisory committee


approve and sign-off
acceptance of Project Plan

Go back to AC and seek mandate


for new project definition

7.2

Project plan deficient

Distribute Project Plan to AC


and project team to identify any
omissions early.

Rewrite project Plan to include all


in scope activities

/VAR/WWW /APPS/CONVERSION/TMP/SCRATCH_3/289094616.DOC
PAGE 4 OF 6

RISK MANAGEMENT PLAN DATA CENTER RELOCATION

Risk
Id.

Risk description

7.3

Lack of communication

Likelihood
M-H

Mitigation Strategy
Develop communication plan
and adhere to agreed
communication activities

Impact
H

Include regular formal reporting


in this plan.
7.4

Scope creep

Detail project scope in PMP and


get SC sign-off.

Contingency

Who owns

Seek agreement from project team


and stakeholders to follow
Communication activities.
Delay project

Seek additional time and


resources to deliver agreed
changes to scope of project.

Ensure all equipment in


inventoried, labelled and
accounted for.

Group related backups prior to


move. May result in data loss.

Only change scope if agreed to


by AC.
8.Security Risks
8.1

Logical threats unlabelled


equipment.

M-H

8.2

Data is corrupted during move.

Create system/data backups


prior to move

Ensure that infrastructure is in


place to restore systems.

8.3

Machines wont start after move.

Define working start order,


working configuration prior to
move.

Ensure machines can be restarted


prior to move. Maintain working
backup of machine in that state.

8.4

Infrastructure not working (UPS,


Network etc).

Test and configure


infrastructure prior to move.

Delay move if infrastructure is not


working or not in place.

8.5

Loss of passwords, system


documentation.

Make copies of passwords and


configuration guides. Keep in
secure location, accessible by
key persons if needed. Destroy
after move.

Ensure current cache of


passwords and configuration
guides is accessible during move.
Fail over to reserve cache if
needed.

9. Application Risks
/VAR/WWW /APPS/CONVERSION/TMP/SCRATCH_3/289094616.DOC
PAGE 5 OF 6

RISK MANAGEMENT PLAN DATA CENTER RELOCATION

Risk
Id.
9.1

Risk description

Likelihood

Mitigation Strategy

Impact

Contingency

Who owns

SAN based replication of Oracle


DBs (re:RW email March 3,
2009)

This is the last page in the document.

/VAR/WWW /APPS/CONVERSION/TMP/SCRATCH_3/289094616.DOC
PAGE 6 OF 6

You might also like