State Data Center Re-scoped Projects

1. State Data CenterRe-scoped Projects With emphasis on reducing loadon cooling systems in OB2 April 4, 2012

2. Revised Scope & Strategies • Revised SDC Project Scope • Consolidation based on individual agencies’ business case (e.g. WSP); no specific schedule • Maintain OB2 data center long term, move what is necessary to relieve cooling issues • SDC data hall 1 used for OB2 and co-location; “just-in-time” build-out; high security • SDC data hall 2 out of scope • Cloud “utility” still in scope, strategy being developed with OCIO • Previous SDC Project Scope • Support state’s strategy to consolidate all Thurston County data centers to SDC; scheduled • Migrate OB2 to SDC and restore to office space; first step in consolidation plan • SDC data hall 1 for OB2 migration; high security • SDC data hall 2 for co-location, consolidation, new customers; lower security • Cloud “utility” to facilitate state’s strategy for IT Transformation

3. Defining the Problem in OB2 • OB2 data center will be retained long term • No funds to refurbish and expand cooling system • OB2 cooling system is over capacity • Current temps higher than recommended • OB2 cooling system has no reserve • Every A/C unit operating full time • No redundancy in case of failure • Failure of a critical cooling system component would put mission-critical applications in peril

4. Defining the Problem in OB2 • Cooling demand in OB2 must be reduced by 37% minimum, 50% desired

5. Preventive & Contingency Actions • Regular preventative maintenance • A/C units maintained weekly • Critical pumps serviced quarterly, monthly during summer months • Large hurricane fans deployed to increase air circulation – curtains to contain cool air • Shutdown non-critical equipment if it becomes necessary to protect mission-critical systems • Contingency procedures not an adequate long term solution

6. Relieving the Cooling Problem Phased Strategy • Reduce the heat generated in OB2 • Shutdown unnecessary equipment as soon as possible • Develop plan to shutdown least critical equipment in event of major cooling system failure • Prepare the SDC to receive equipment • Facilities, networks, storage, security, etc. (multiple projects) • Move 35% - 50% of the load out of OB2 to SDC • Refresh equipment into SDC, migrate servers, move mainframes, etc. (multiple projects) • CTS managed equipment only. A la carte remains in OB2 • Optimize OB2 data center • Reconfigure enclosures, consolidate equipment, removeunder floor cables, shutdown unused areas, etc.

7. SDC Program: Re-Scoped Projects Reduce Heat Generated in OB2 Move the Load to the SDC • Reduce Heat in OB2 OB2 Migration Phase 1 Virtual Tape Library OB2 Migration Phase 2 Prepare the SDC to Receive Equipment SDC Operational Readiness – Facilities SDC Operational Readiness – Network Secure the SDC Infrastructure Storage Optimization CTS Cloud “Utility”(for OB2 server migrations) Optimize Air Flow in OB2 Data Center OB2 Optimization Consolidation WSP Migration to SDC(Very high priority project for SDC Program but not associated with OB2 cooling issue)

8. Map of Move Impacts to OB2

9. April Activities • Restart SDC Projects • Re-scope projects • Update charters • Severity & risk assessments • Update investment plans for Network, Security, Storage • Focus on Facilities project (critical path) • Initiate “Reduce Heat” project

10. Project: Reduce the Heat in OB2 • CTS working with OB2 tenant agencies • Identify equipment already planned for shutdown in near future as result of ongoing virtualization • Document least critical equipment that can be shutdown in an emergency in order to protect mission-critical systems from heat damage • Agencies name person to coordinate efforts with CTS (request sent to CIOs 04/02/2012) • Agency coordinators return completed equipment template to CTS by 04/25

11. DRAFT