PROJECT PLAN

Project ID: Project Name: Plan Date: ITS-Q2-16 Secondary Data Center 10/13/07 Project Sponsor: Project Owner: Al Essa Jim Dierich

Project Manager: Kathleen Hertenstein

Project Description
During the process of defining its Business Continuity Plan, Minnesota State Colleges & Universities ITS department identified the need to establish a secondary data center whose primary function would be to support critical applications in the event of an unrecoverable failure at the West Bank Office Building (WBOB) data center. Minnesota State Colleges & Universities ITS department has identified the Centennial Office Building (COB) as the location for its secondary data center DR site. This project will create the infrastructure and process to failover D2L, ISRS, and RARE (Reporting & Research Environment).

Project Scope
Objectives Build a site that is capable of providing; Redundant infrastructure services, e.g., WWW, DNS, authentication, etc. Failover site for critical application services, e.g., D2L, ISRS, e-mail, Data Warehouse, etc. Protect MnSCUs enterprise data using controller based (middle ware) and software replication between the primary data center (WBOB) and the secondary-d/r data center (COB). Assumptions Constraints Out of Scope Phase 1: Physical Network, Security & D2L/ISRS Failover Device Installation: COB Failover Recovery "capable" Warm Site (no apps)" Phase 2A: Install Devices Pre-Application Minimums Phase 2B: D2L Build Database and Application Servers at COB Phase 2C: ISRS/RARE Build Environment at COB Phase 2D: Install Remaining Devices / Exit St. Cloud Phase 3: D2L Failover Process Creation Phase 4: ISRS/RARE Failover Process Creation Phase 5: Failover Determination for Other Applications OET data center is appropriate site Project is to provide failovers for individual applications, not a major disaster at WBOB MnSCU staff will be available to work on this project to reach milestones Lack of resources in MnSCU IT will significantly impact deliverable dates depending on how projects are prioritized. Some work tasks will be completed by staff from the Office of Enterprise Technology. Other MnSCU projects may take priority over Secondary Data Center which will pull resources from this project. An immediate need for failover of the identified applications could re-arrange or crash schedule. Communication plan in the event of a failure. Failover/Recovery plans for applications other than D2L, ISRS, RARE.

Work Breakdown

Office of the Chancellor

Confidential

Page 1 of 3

PROJECT PLAN
Project ID: Project Name: Plan Date: ITS-Q2-16 Secondary Data Center 10/13/07 Project Sponsor: Project Owner: Al Essa Jim Dierich

Project Manager: Kathleen Hertenstein

Roles and Responsibilities

Name Jim Dierich Role Project Owner % Time (est.) 50%
20hr/wk for 30/wks 600 hrs

Kathleen Hertenstein

Project Manager

50%
20hr/wk for 30/wks 600 hrs

Mike Janke

Senior Technical Architect Senior Windows Platform Architect / D2L Technical Expert Network Expert

50%
20hr/wk for 30/wks 600 hours

Denise Brandt

75%
30hr/wk for 30/wks 900 hrs

David Goetz

75%
30hr/wk for 30/wks 900 hours

Cory Erickson Kevin Meehan Bob Esson Ross Berndt

Senior UNIX Administrator UNIX Administrator Oracle Admin On-going Secondary Data Center Owner Windows platform architect SAN VMS

50%
20hr/wk for 20/wks 400 h ours

Responsibilities Serve as overall project lead, adjusting project scope/resources as needed. Approve all budget expenditures. Serve as liaison between MnSCU and OET, resolving conflicts as needed. Provide project management support to Project Owner and Project Team. Create project work plan, weekly status reports and 30 Day Status Reports. Provide other project updates as required by the PMO or Enterprise Investment Committee. Assist Project Owner with other tasks as assigned. Provide overall direction on network and infrastructure development at COB. Serve as technical expert on decisions regarding network and infrastructure. Serve as technical expert and primary installer for Windows platforms being installed, especially in relation to D2L. Serve as technical expert and primary installer on D2L failover environment and failover process. Install / test network at COB and ensure interface between WBOB and COB. Serve as technical expert on network issues. Serve as technical expert on UNIX infrastructure. Serve as lead on installation and testing of all UNIX devices. Install / test UNIX devices under the direction of Senior UNIX administrator. Provide expertise in process for Oracle failover/data protection Serving as overall manager of the Secondary Data Center, participate in the design and approval of the infrastructure and processes for failover. Support the Senior Windows Platform architect as needed to install and test devices. Install/support storage area network Serve as VMS support.

50%
20hr/wk for 20/wks 400 hrs

50%
20hr/wk for 4/wks 80 hrs

30%
15hr/wk for 30/wks 450 hrs

Rick Jones Bruce Carlson Charlie Anderson

25%
10hr/wk for 20/wks 200 hrs

30%
15hr/wk for 30/wks 450 hrs

25%
10hr/wk for 20/wks 200 hrs

Cost Benefit Analysis

Cost Employee Time Cost Consultant/Temp Time Cost Project Expenses Tangible Benefit Per Month Break Even Months
Office of the Chancellor

$$
$ 259,000 $ 90,000 $ 1,100,000

Explanation
5180 x $50/hr 600 hrs x $150/hr (starting 7/07) Dollars approved by EIC 8/07

Confidential

Page 2 of 3

PROJECT PLAN
Project ID: Project Name: Plan Date: ITS-Q2-16 Secondary Data Center 10/13/07 Project Sponsor: Project Owner: Al Essa Jim Dierich

Project Manager: Kathleen Hertenstein

Change Control Thresholds

Scope Any change to scope taking combined resource time of more than 16 hours must be approved by Project Owner. Cost Any spending which would go above approved budget must be approved by Project Owner. Time Delays to timeline which will result in any missed milestones must be explained to and approved by Project Owner. All other changes in timeline resulting in more than 5 days push must be approved by Project Owner.

Scenario Planning
Lever Risk Scope Description If this project is given priority, and resources can focus on tasks, the risk of not meeting deadlines decreases. Project can complete sooner if no additional planning needs to occur for other applications to be added to the failover process. (Phase 5) We might also be able to crash the timeline if resources working on Continuity of Operation can leverage/assist with failover process for the applications in scope. Time Savings No time would be lost and project would finish on schedule. 4-6 weeks.

Cost

Attached Plans and Documents (check all applicable)

X X X Project Requirements Project Deliverables (see Project Schedule) Project Schedule (see task plan in MS Project) Project Team Roster Project Risk Register

Approvals
Al Essa, Project Sponsor Date Jim Dierich, Project Manager Date

REVISION HISTORY Revision Description 1.0 Original creation 2.0 Re-worked change control thresholds

Date 10/15/07 11/19/07

Name Kathleen Hertenstein Kathleen Hertenstein

Office of the Chancellor

Confidential

Page 3 of 3