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

 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

DRAFT FOR DISCUSSION PURPOSES ONLY -2-

 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 consolidation

• A high-level timeline for consolidation was established using the consolidation “waves”
identified by the DCCWG
Where We Left Off
(June – Mid July)
• The 2nd 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
consolidation plan by a September 30th due date

• Deloitte is working with ITD to refine processes and chargeback mechanisms in

preparation for consolidation activities
The Next Steps
(Now – Late September)
• 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

DRAFT FOR DISCUSSION PURPOSES ONLY -3-

 Infrastructure Consolidation Plan – “Playbook
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.

Phase 2
July 6 – Sept 30
Step 1: Step 2: Step 3:
Assess current Develop Define detailed Step 9:
infrastructure plan Refine Step 8:
environment and infrastructure
capabilities Transition to
existing consolidation
operations
requirements approaches
Step 4:
Build ITD
base
capabilities

Primary responsibility
ITD
Secretariat Step 7:
Execute,
Joint migrations
and stabilize
Step 5: environment
Develop
detailed
Secretariat
consolidation Step 6:
Prioritize
plan Provision
resources
according to
plan

DRAFT FOR DISCUSSION PURPOSES ONLY -4-

 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: Step 2: Step 3:

Assess current Develop Define detailed
environment and infrastructure infrastructure plan
existing consolidation
requirements approaches

Collected data allows ITD to • Applications are mapped to migration models for servers/storage/BC/DR based on their
1 understand each agency’s 2 individual characteristics.
application profiles • ITD standard service offerings dictate the order of preference for each approach area

Agency Application Server Consolidation Models Storage Consolidation Models BC/DR Model
Profile
Virtual to Virtual Shared to Shared MITC Only
Supporting Servers
and Storage
Physical to Virtual Dedicated to Shared Springfield Only
Platform and Backend
Physical to Physical Lift and Shift MITC <-> Springfield

Operations and
Support Profile Lift and Shift MITC <-> Agency

Configure Options Supporting ITD Solutions

The migration approach
for each application is Service Level /
3 supported by a standard Service Delivery
Security Network Facilities
Requirements Requirements Requirements
Model
set of ITD solutions

DRAFT FOR DISCUSSION PURPOSES ONLY -5-

 What Data Will Be Collected?
The following data elements will be required to close the inventory gap and complete the detailed plan
High-Level Data:
Supporting
Infrastructure:
Network Requirements
(In coordination with Network
Architecture project):
Security Requirements:
BC/DR/HA
Requirements:
Service and Ops
Requirements:
ITSM Process and Toolsets
Overall Assessment
(by Secretariat and
Agency):
Supporting Tools:
DRAFT FOR DISCUSSION PURPOSES ONLY
Application Inventory
Owning agency, external web address, description, # of end users, platform/runtime
environment, DB backend, priority consolidation 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
OS Software, Monitoring and Management Tools
For each key ITSM process: High-Level Data by Software name, vendor,
maturity level, process Agency or version, license type, purpose,
description Secretariat: number of systems supported,
maintenance/support cost and
Software name, vendor,
expiration
version, license type,
maintenance/support cost
and expiration
-6-
 Data Collection - Expectations
It is important to set appropriate expectations on the data collection effort:

This data collection effort WILL:

9 Enable an understanding of application infrastructure/process/operational needs in

consolidated future state

9 Provide the basis for developing timelines and categorizing applications into migration
waves and approach models

9 Allow us to develop an understanding of servers and storage supporting each application

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

DRAFT FOR DISCUSSION PURPOSES ONLY -7-

 How Will Collected Data be Used?
The data collected will drive the development of the Detailed Infrastructure Consolidation Plan

• What apps are candidates for

1. What is the exact physical

Consolidation Playbook
consolidation?
Application • What is the best migration and logical architecture for
Secretariat
Inventory approach for each app (P2V, V2V, the app in the future-state?
Infrastructure
lift and shift, P2V, etc)? 2. What are the detailed WBS
Supporting Consolidation
Infrastructure • What will the future state and for individual
Plans
Secretariat Data to be Collected

infrastructure look like

SLOs / Support
(approximate server counts and
consolidations?
Model 3. What is the exact financial
make/model based on ITD
architectures)? impact to the Secretariat?
• What consolidation wave does the
application belong in, and how Detailed Infrastructure
should migrations be sequenced? Consolidation Plan
Agency /
Secretariat ITSM
Practices 1. Based on estimates, how
• What is the best staffing model in
much capacity should be
Industry Validation

Supporting Tools the consolidated environment?

• What is the plan to standardize built out?
Maturity Levels tools and ITSM processes? ITD Roadmap 2. What standard set of
• What are the budgetary impacts of processes should be rolled
the consolidation?
• How must the chargeback model
out?
Monitoring and be tweaked? 3. What standard toolset
Management should be rolled-out?
Tools

Step 1: Step 2: Step 3: Step 4: Step 5:

Assess current Develop Define detailed Build ITD base Develop
environment infrastructure infrastructure capabilities detailed
and existing consolidation plan September 30th Secretariat
requirements approaches consolidation
plan

DRAFT FOR DISCUSSION PURPOSES ONLY -8-

 How Will Collected Data be Used?
The consolidation 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 consolidation?

• What is the best migration approach for each app (P2V, V2V, lift and shift, P2V, etc)? Secretariat
• What will the future state infrastructure look like (approximate server counts and Infrastructure
Consolidation
make/model based on ITD architectures)? Plans
• What consolidation wave does the application belong in, and how should migrations
be sequenced?

DRAFT FOR DISCUSSION PURPOSES ONLY -9-

 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

Develop
Pre-Populate Hold Initial Receive and Detailed
Existing Data Training Analyze Data Consolidation
Plan

• Build data • Hold conference • DCCWG • Work with

collection tool call / webinar representatives Secretariats to
based on session to send completed apply playbook
required data explain data inventory approaches and
elements collection templates to draft
template in Greg infrastructure
• Analyze detail Guadagnolo consolidation
Secretariat and (gguadagnolo@ waves
Agency data • Review process deloitte.com)
collected as part for how data will • Identify staffing
of ITC Phase I be used • Review collected dependencies
and DCC data and identify
projects • Address any any key gaps • Review
questions or consolidation
• Pre-populate concerns • Perform initial plans with key
data collection analysis Secretariat and
tool to give ITD stakeholders
Secretariat and
Agency We Are Here
resources a
“head-start”

DRAFT FOR DISCUSSION PURPOSES ONLY - 10 -