1. Deloitte Consulting LLP Commonwealth of Massachusetts Statewide Strategic IT Consolidation (ITC) Initiative Data Center Consolidation Work Group (DCCWG) Meeting August 5th, 2009 DRAFT – FOR DISCUSSION PURPOSES ONLY

2. - 2 - DRAFT FOR DISCUSSION PURPOSES ONLY Agenda Status Update Consolidation Plan “Playbook” Approach for Data Collection o What Data Will Be Collected? o How Will Collected Data be Used? o What is the Data Collection Process and Timeline? Next Steps

3. - 3 - DRAFT FOR DISCUSSION PURPOSES ONLY The 5/30 High-Level Infrastructure Consolidation Plan was completed, containing your inputs for Data Center Services consolidation A high-level timeline for consolidation was established using the consolidation “waves” identified by the DCCWG The 2 nd Data Center team held a detailed working session with each Secretariat to gather high-level requirements for MITC/DC2 plans Your inputs were used as part of the high-level requirements and capacity model for MITC renovation and DC2 planning efforts Where We Left Off (June – Mid July) DCCWG Status Update What has happened since our last meeting? The ITD leadership team has been tasked with creating a detailed infrastructure consolidation plan by a September 30 th due date Deloitte is working with ITD to refine processes and chargeback mechanisms in preparation for consolidation activities The DCCWG team input is required to create a plan for data center services, including a detailed mapping of applications to consolidation waves In order to complete the described activities, we will need to gather detailed infrastructure data. This data will drive both facilities and consolidation planning The Next Steps (Now – Late September)

4. - 4 - DRAFT FOR DISCUSSION PURPOSES ONLY Infrastructure Consolidation Plan – “Playbook Step 1: Assess current environment and existing requirements Step 2: Develop infrastructure consolidation approaches The Playbook was reviewed during our sessions the last two weeks. It illustrates our framework for executing technology consolidations. It will be customized to outline a repeatable migration process that can be leveraged for data center services, network services, and email/directory services. Primary responsibility Secretariat ITD Joint Step 3: Define detailed infrastructure plan Prioritize Step 7: Execute, migrations and stabilize environment Step 9: Refine capabilities Step 8: Transition to operations Step 4: Build ITD base capabilities Step 5: Develop detailed Secretariat consolidation plan Step 6: Provision resources according to plan Phase 2 July 6 – Sept 30

5. - 5 - DRAFT FOR DISCUSSION PURPOSES ONLY What is the Data Center Services Consolidation Playbook? Agency Application Profile Supporting Servers and Storage Platform and Backend Operations and Support Profile Server Consolidation ModelsStorage Consolidation ModelsBC/DR Model Lift and Shift Physical to Physical Physical to Virtual Virtual to Virtual Dedicated to Shared Shared to Shared Lift and Shift MITC Only Springfield Only MITC Springfield Collected data will be used to form the detailed migration approach for each identified application MITC Agency Configure Options Supporting ITD Solutions Service Level / Service Delivery Model Security Requirements Network Requirements Facilities Requirements 2 Collected data allows ITD to understand each agency’s application profiles Applications are mapped to migration models for servers/storage/BC/DR based on their individual characteristics. ITD standard service offerings dictate the order of preference for each approach area 1 The migration approach for each application is supported by a standard set of ITD solutions 3 Step 1: Assess current environment and existing requirements Step 2: Develop infrastructure consolidation approaches Step 3: Define detailed infrastructure plan

6. - 6 - DRAFT FOR DISCUSSION PURPOSES ONLY What Data Will Be Collected? The following data elements will be required to close the inventory gap and complete the detailed plan Application Inventory High-Level Data: Owning agency, external web address, description, # of end users, platform/runtime environment, DB backend, priority consolidation driver (at risk? Needs DR/HA?) Supporting Infrastructure: Server make/model, quantities, locations, virtualization status and toolset, operating system and version, storage (direct attached and SAN), other specialty infrastructure (check printing, etc), maintenance/support cost and expiration, asset value/depreciation data Network Requirements (In coordination with Network Architecture project): Key external integration points, unique bandwidth and latency requirements Security Requirements: Regulatory and compliance requirements, unique firewall requirements, unique encryption and authentication requirements BC/DR/HA Requirements: RTO/RPO model, future-state high-avail ability requirements Service and Ops Requirements: Hours of operations, lifecycle stage, SLOs/SLAs ITSM Process and Toolsets Overall Assessment (by Secretariat and Agency): For each key ITSM process: maturity level, process description Supporting Tools:Software name, vendor, version, license type, maintenance/support cost and expiration OS Software, Monitoring and Management Tools High-Level Data by Agency or Secretariat: Software name, vendor, version, license type, purpose, number of systems supported, maintenance/support cost and expiration

7. - 7 - DRAFT FOR DISCUSSION PURPOSES ONLY Data Collection - Expectations It is important to set appropriate expectations on the data collection effort: This data collection effort WILL: Enable an understanding of application infrastructure/process/operational needs in consolidated future state Provide the basis for developing timelines and categorizing applications into migration waves and approach models Allow us to develop an understanding of servers and storage supporting each application Serve as input to ITD capacity models for facilities enhancement and build-out projects However, this effort is NOT intended to:  Result in a detailed, Commonwealth-wide application, infrastructure or asset inventory  Result in a detailed understanding of all applications and associated business processes  Be the application rationalization for each individual Secretariat (although it will be a valuable input)

8. - 8 - DRAFT FOR DISCUSSION PURPOSES ONLY How Will Collected Data be Used? Step 1: Assess current environment and existing requirements Step 2: Develop infrastructure consolidation approaches Step 3: Define detailed infrastructure plan Step 4: Build ITD base capabilities Step 5: Develop detailed Secretariat consolidation plan Application Inventory Agency / Secretariat ITSM Practices Supporting Infrastructure SLOs / Support Model Supporting Tools Maturity Levels Monitoring and Management Tools Consolidation Playbook Industry Validation What apps are candidates for consolidation? What is the best migration approach for each app (P2V, V2V, lift and shift, P2V, etc)? What will the future state infrastructure look like (approximate server counts and make/model based on ITD architectures)? What consolidation wave does the application belong in, and how should migrations be sequenced? What is the best staffing model in the consolidated environment? What is the plan to standardize tools and ITSM processes? What are the budgetary impacts of the consolidation? How must the chargeback model be tweaked? Secretariat Data to be Collected Secretariat Infrastructure Consolidation Plans ITD Roadmap Detailed Infrastructure Consolidation Plan September 30th 1.Based on estimates, how much capacity should be built out? 2.What standard set of processes should be rolled out? 3.What standard toolset should be rolled-out? 1.What is the exact physical and logical architecture for the app in the future-state? 2.What are the detailed WBS and for individual consolidations? 3.What is the exact financial impact to the Secretariat? The data collected will drive the development of the Detailed Infrastructure Consolidation Plan

9. - 9 - DRAFT FOR DISCUSSION PURPOSES ONLY How Will Collected Data be Used? Consolidation Playbook What apps are candidates for consolidation? What is the best migration approach for each app (P2V, V2V, lift and shift, P2V, etc)? What will the future state infrastructure look like (approximate server counts and make/model based on ITD architectures)? What consolidation wave does the application belong in, and how should migrations be sequenced? Secretariat Infrastructure Consolidation Plans The consolidation playbook will allow the ITC team to categorize applications into the waves identified in the first project phase: FY’10FY’11FY’12FY’13 Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4 Wave 1: HHS Pilot and Migration MITC Renovation Springfield Build-Out Wave 2: Migration of Systems At-Risk or Lacking Sufficient DR Capabilities Wave 3: Consolidation of Remaining Systems Across Secretariats

10. - 10 - DRAFT FOR DISCUSSION PURPOSES ONLY What is the Data Collection Process and Timeline? The process to collect the required data is shown below with approximate dates Pre-Populate Existing Data Build data collection tool based on required data elements Analyze Secretariat and Agency data collected as part of ITC Phase I and DCC projects Pre-populate data collection tool to give Secretariat and Agency resources a “head-start” Receive and Analyze Data Develop Detailed Consolidation Plan Hold Initial Training 7/30/09 8/4/098/4/09 - 8/20/09 8/27/09-9/15/09 Hold conference call / webinar session to explain data collection template in detail Review process for how data will be used Address any questions or concerns DCCWG representatives send completed inventory templates to Greg Guadagnolo (gguadagnolo@ deloitte.com) Review collected data and identify any key gaps Perform initial analysis Work with Secretariats to apply playbook approaches and draft infrastructure consolidation waves Identify staffing dependencies Review consolidation plans with key Secretariat and ITD stakeholders We Are Here