Data Center Consolidation Work Group (DCCWG) Meeting

Transcription

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

2 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 -2-

3 DCCWG Status Update What has happened since our last meeting? The 5/30 High-Level Infrastructure Consolidation Plan was completed, containing your inputs for Data Center Services Where We Left Off (June Mid July) A high-level timeline for was established using the 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 The ITD leadership team has been tasked with creating a detailed infrastructure plan by a September 30 th due date The Next Steps (Now Late September) Deloitte is working with ITD to refine processes and chargeback mechanisms in preparation for activities The DCCWG team input is required to create a plan for data center services, including a detailed mapping of applications to waves In order to complete the described activities, we will need to gather detailed infrastructure data. This data will drive both facilities and planning -3-

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

5 What is the Data Center Services Consolidation Playbook? Collected data will be used to form the detailed migration approach for each identified application Step 1: Assess current environment and existing requirements Step 2: infrastructure approaches Step 3: Define detailed infrastructure plan 1 Collected data allows ITD to understand each agency s application profiles 2 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 Agency Application Profile Supporting Servers and Storage Platform and Backend Server Consolidation Models Storage Consolidation Models BC/DR Model Virtual to Virtual Shared to Shared MITC Only Physical to Virtual Dedicated to Shared Springfield Only Physical to Physical Lift and Shift MITC <-> Springfield Operations and Support Profile Lift and Shift MITC <-> Agency 3 The migration approach for each application is supported by a standard set of ITD solutions Service Level / Service Delivery Model Configure Options Supporting ITD Solutions Security Requirements Network Requirements Facilities Requirements -5-

6 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: Supporting Infrastructure: Network Requirements (In coordination with Network Architecture project): Security Requirements: BC/DR/HA Requirements: Service and Ops Requirements: Owning agency, external web address, description, # of end users, platform/runtime environment, DB backend, priority driver (at risk? Needs DR/HA?) 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 Key external integration points, unique bandwidth and latency requirements Regulatory and compliance requirements, unique firewall requirements, unique encryption and authentication requirements RTO/RPO model, future-state high-avail ability requirements Hours of operations, lifecycle stage, SLOs/SLAs ITSM Process and Toolsets OS Software, Monitoring and Management Tools Overall Assessment (by Secretariat and Agency): Supporting Tools: For each key ITSM process: maturity level, process description Software name, vendor, version, license type, maintenance/support cost and expiration High-Level Data by Agency or Secretariat: Software name, vendor, version, license type, purpose, number of systems supported, maintenance/support cost and expiration -6-

7 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) -7-

8 How Will Collected Data be Used? The data collected will drive the development of the Detailed Infrastructure Consolidation Plan Secretariat Data to be Collected Application Inventory Supporting Infrastructure SLOs / Support Model Agency / Secretariat ITSM Practices Supporting Tools Maturity Levels Monitoring and Management Tools Consolidation Playbook Industry Validation What apps are candidates for? 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 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? How must the chargeback model be tweaked? Secretariat Infrastructure Consolidation Plans Detailed Infrastructure Consolidation Plan ITD Roadmap 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 s? 3. What is the exact financial impact to the Secretariat? 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? Step 1: Assess current environment and existing requirements Step 2: infrastructure approaches Step 3: Define detailed infrastructure plan September 30th Step 4: Build ITD base capabilities Step 5: detailed Secretariat plan -8-

9 How Will Collected Data be Used? The playbook will allow the ITC team to categorize applications into the waves identified in the first project phase: FY 10 FY 11 FY 12 FY 13 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 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 Consolidation Playbook What apps are candidates for? 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 wave does the application belong in, and how should migrations be sequenced? Secretariat Infrastructure Consolidation Plans -9-

10 What is the Data Collection Process and Timeline? The process to collect the required data is shown below with approximate dates 7/30/09 8/4/09 8/4/09-8/20/09 8/27/09-9/15/09 Pre-Populate Existing Data Hold Initial Training Receive and Analyze Data Detailed Consolidation Plan 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 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 We Are Here 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 waves Identify staffing dependencies Review plans with key Secretariat and ITD stakeholders -10-