September 10, 2009 DRAFT – FOR DISCUSSION PURPOSES ONLY

1. Commonwealth of Massachusetts Statewide Strategic IT Consolidation (ITC) InitiativeDetailed Infrastructure Consolidation PlanWorkshop September 10, 2009 DRAFT – FOR DISCUSSION PURPOSES ONLY

2. Table of Contents

3. Overview

4. Background • In February, Gov. Patrick issued Executive Order 510 calling for IT Consolidation and defined the three major requirements: • The appointment of Secretariat CIOs with authority over IT budgets and resources • Consolidation of four IT services at the Secretariat level:desktop, Helpdesks, web content, applications • Consolidation of four IT services at the Commonwealthlevel through ITD: networks, data centers, web hosting,enterprise applications (e-mail) • The Commonwealth’s new IT model aims at achieving three simple goals:To make our IT environment more: • Efficient – through standardization of IT resources • Effective – This requires and elevates strategic IT planning with SCIOs and enables Secretariats to align resources with their business priorities • Secure –To enable a coherent and streamlined architecture for information security

5. Framework and Scope for Infrastructure Consolidation • Based on Executive Order No. 510, the Commonwealth will consolidate four common services as identified in the diagram below. • Data Center Services — Enterprise computing resources, including: Raised Floor and/or Cooled Data Centers, Server Rooms, Server/Telecom Closets, SUDs (Servers Under Desks) • Network and Telecom Services — Centrally governed network architecture, associated processes and staff, that transport voice, data, and video traffic. • Website Hosting and Portal Services — Standardized Mass.Gov hosting platform, associated processes and people, that provides tools for web publishing and self-management of content • Enterprise Services (e-mail) — Electronic messaging system, with basic collaboration capabilities like calendaring and tasks. A centralized Active Directory service with appropriate security designations. Commonwealth-wide IT infrastructure services included for the consolidation effort.

6. The Mandate – Executive Order No. 510 • On February 20, 2009, Governor Deval Patrick issued Executive Order 510 mandating IT consolidation in Executive departments. The order outlined the provisions for the consolidation process, one of the seven initiatives outlined in the Commonwealth’s IT strategic plan. Specifically, the order outlined a planning timeline as described in the table below.

7. Business Risks • With a program as complex as IT Consolidation, many risks exist, risks have been and continue to need to be monitored and strategies developed to help mitigate the impact of these risks:

8. Approach

9. Approach to Infrastructure Consolidation – the “Playbook” • To achieve efficiencies in planning and execution, a “Playbook” approach incorporating the operational and technology consolidations is employed. This repeatable consolidation process is tailored to meet the needs of each of the technology threads for Network/telecomm, Data center services, and Shared enterprise services. Step 3: Define detailed infrastructure plan Step 1: Assess current environment and existing requirements Step 2: Develop infrastructure consolidation approaches Step 9: Refine capabilities Step 8: Transition to operations Step 4: Build ITD base capabilities Primary responsibility ITD Secretariat Step 7: Execute consolidations and stabilize environment Joint Step 5: Develop detailed Secretariat consolidation plan Step 6: Provision resources according to plan Prioritize Prioritize

10. Playbook – Planning Process – Roles and Responsibilities

11. Playbook – Repeatable Process – Roles and Responsibilities

12. Playbook – Transition to Operations – Roles and Responsibilities

13. Data Center Services Consolidation

14. Data Center Services Consolidation Overview, Scope, and Exclusions Applications and underlying infrastructure will be aligned to the migration waves defined in Phase I based on prescribed playbook approaches. Data center services consolidation does not include file and print services but can include consolidation of applications that have been initially placed on file servers but have become required for continued operation of Secretariat or Agency business processes.

15. Building the “Playbook” for Data Center Services In steps 1 to 3 of the consolidation process, detailed infrastructure consolidation plan will be created from the repeatable playbook-based approach Step 3: Define detailed infrastructure plan Step 1: Assess current environment and existing requirements Step 2: Develop infrastructure consolidation approaches 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 2 1 Agency Application Profile Server Consolidation Models Storage Consolidation Models Disaster Recovery Model Virtual to Virtual Shared to Shared Springfield <-> MITC Supporting Servers and Storage Physical to Virtual Dedicated to Shared MITC <-> Agency Platform and Backend Physical to Physical Dedicated to Dedicated Springfield Only Operations and Support Profile Lift and Shift Lift and Shift MITC Only Configure Options Supporting ITD Solutions The migration approach for each application is supported by a standard set of ITD solutions Service Level / Service Delivery Model Security Requirements Network Requirements Facilities Requirements 3

16. Application Categorization Based On Collected Data Application Inventory Data Mainframe Mainframe Category High Level Infrastructure Type Supporting Servers and Storage Virtual Server Category Platform and Backend Virtualized Server Operations and Support Profile Physical Server Physical Server Categories Gate 1: Hardware Type and System Config • Is the application running on a unique hardware or OS? • Is the hardware or OS not compatible with ITD’s standard service offerings? If Yes Legacy Physical Server Category Gate 2: Software Support • Is virtualization disallowed by the vendor/licensing terms? • Is the application minimally supported at the agency? If Yes Unsupported Physical Server Category Gate 3: Regulatory/Compliance Profile Restricted Physical Server • Does any regulation or statute require the application maintain physical or logical separation? If Yes Gate 4: Application Performance Profile Performance Constrained Physical Server • Does the application have high IO requirements? • Does the application require special component hardware configuration? If Yes Standard Physical Server Category

17. Application Categorization Based On Collected Data (cont.) Mainframe Virtual Server Legacy Physical Server Unsupported Physical Server Restricted Physical Server Performance Constrained Physical Server Standard Physical Server

18. Server Consolidation Approach Models Preference

19. Server Consolidation Approach Models (cont.) Preference

20. Storage Consolidation Approach Models Preference

21. Storage Consolidation Approach Models (cont.) Preference

22. Disaster Recovery Consolidation Approach Models Interim Preference

23. Disaster Recovery Consolidation Approach Models (cont.) Longer Term Preference

24. Service Level and Service Delivery Characteristics Relevant Data Collected from Agencies and Secretariats Supporting Service Level and Service Delivery Model

25. Security Characteristics Relevant Data Collected from Agencies and Secretariats Security Requirements

26. Network Architecture Characteristics Relevant Data Collected from Agencies and Secretariats Network Requirements

27. Facilities Characteristics Relevant Data Collected from Agencies and Secretariats Facility Requirements

28. Server Consolidation Approach to Application Category Mapping Mainframe Virtual Server Legacy Physical Server Unsupported Physical Server Restricted Physical Server Performance Constrained Physical Server Standard Physical Server

29. Storage Consolidation Approach to Application Category Mapping Mainframe Virtual Server Legacy Physical Server Unsupported Physical Server Restricted Physical Server Performance Constrained Physical Server Standard Physical Server

30. DR Consolidation Approach to Application Category Mapping DR solutions for different application profiles will evolve over time in order to reduce risk exposure “Warm” & “Hot” DR Models {Typically an instance of application has already been built in another location with replication of data. Application is not load balanced but can be recovered in less than 24 hours for “Hot” DR. “Cold” DR Models{Typically includes server acquisition/build and can take at least 72 hours to recover} Agency Primary | MITC DR MITC Primary | Agency DR MITC Only Virtual Server Virtual Server Mainframe* Restricted Physical Server Restricted Physical Server Virtual Server Performance Constrained Physical Server Performance Constrained Physical Server Legacy Physical Server Near Term Solutions Standard Physical Server Standard Physical Server Unsupported Physical Server Stage 1 DR Setup Stage 2 DR Setup Restricted Physical Server Standard Physical Server * May include use of Sungard for Mainframe Springfield Primary | MITC DR Springfield Only Virtual Server Virtual Server Restricted Physical Server Legacy Physical Server Long Term Solutions Performance Constrained Physical Server Unsupported Physical Server Standard Physical Server Restricted Physical Server Standard Physical Server Stage 3 DR Setup

31. V2V Server Consolidation Approach High Level Steps High level steps and notional timeline to be used for planning purposes to build detailed infrastructure consolidation plan. Primary responsibility ITD Outage Window Secretariat Joint *Assumes that any procurement of application licenses has already been completed by the Secretariat prior to start of the timeline.

32. P2V Server Consolidation Approach High Level Steps High level steps and notional timeline to be used for planning purposes to build detailed infrastructure consolidation plan. Primary responsibility ITD Secretariat Outage Window Joint *Assumes that any procurement of application licenses has already been completed by the Secretariat prior to start of the timeline.

33. P2P Server Consolidation Approach High Level Steps High level steps and notional timeline to be used for planning purposes to build detailed infrastructure consolidation plan. Outage Window Primary responsibility ITD Secretariat Joint *Assumes that any procurement of application licenses has already been completed by the Secretariat prior to start of the timeline.

34. L&S Server Consolidation Approach High Level Steps High level steps and notional timeline to be used for planning purposes to build detailed infrastructure consolidation plan. Outage Window Primary responsibility ITD Secretariat Joint *Assumes that any procurement of application licenses has already been completed by the Secretariat prior to start of the timeline.

35. Key Documents* ACS Application Consolidation Schedule SABP System Architecture Build Plan Process Activity V2V Server Consolidation Approach Process Flow The following outlines the rules of engagement for the consolidating an agency application that has already been virtualized. ITD Facility Engineering Secretariat/Agency ITD Service Account Mgmt Infrastructure Planning Group ITD Hosting Operations ITD Security & Network ITD Storage Operations Agency Team ITD SAM IPG Members HostingMembers Storage & Backup Members Network & Security FacilityMembers Review the Service Catalog choosing an existing ITD service offering utilizing standard policies Work with Secretariat / Agency to complete BAR with service targets. Service Catalog must be continually updated with new standard service offerings when economies of scale can be found. In an optimum position, the majority of offerings should meet the agency needs and unique agency configurations should be minimized. Legend Governance Activity Create a detailed migration schedule for the agency’s application Wiki Page Key Documents ACS Off-page Connector Create technical and process requirements for application instance Key Decision Point Validate sizing for server containers and storage Update capacity plans as appropriate Metrics and Estimates SABP SABP Iterative Process Allocate storage Configure network routes Configure server containers Identify firewall/security requirements Validate security zoning for application Build / transfer application Set network restrictions per security model Post Build

36. Key Documents* ACS Application Consolidation Schedule SABP System Architecture Build Plan Process Activity V2V Server Consolidation Approach Process Flow (cont.) The following outlines the rules of engagement for the consolidating an agency application that has already been virtualized. ITD Facility Engineering Secretariat/Agency ITD Service Account Mgmt Service Desk / NOC ITD Hosting Operations ITD Security & Network ITD Storage Operations Agency Team ITD SAM SD Members Hosting Members Storage & Backup Members Network & Security FacilityMembers Plan &Build Legend Integrate ITD and Secretariat operational processes Governance Activity Wiki Page Conduct load and User Acceptance Testing Schedule backups Key Documents Off-page Connector Key Decision Point Configure Disaster Recovery replication (As required) Metrics and Estimates Iterative Process Go Live Conduct Operational Readiness Testing Update Asset & Config Mgmt DB Stabilize and transfer to operations Decommission old instance

37. Key Documents* ACS Application Consolidation Schedule SABP System Architecture Build Plan Process Activity P2V Server Consolidation Approach Process Flow The following outlines the rules of engagement for the consolidating an agency application that is migrating from a physical to a virtualized environment. ITD Facility Engineering Secretariat/Agency ITD Service Account Mgmt Infrastructure Planning Group ITD Hosting Operations ITD Security & Network ITD Storage Operations Agency Team ITD SAM IPG Members HostingMembers Storage & Backup Members Network & Security FacilityMembers Review the Service Catalog choosing an existing ITD service offering utilizing standard policies Work with Secretariat / Agency to complete BAR with service targets. Service Catalog must be continually updated with new standard service offerings when economies of scale can be found. In an optimum position, the majority of offerings should meet the agency needs and unique agency configurations should be minimized. Legend Governance Activity Create a detailed migration schedule for the agency’s application Wiki Page Key Documents ACS Off-page Connector Create technical and process requirements for application instance Key Decision Point Load and execute performance discovery tool Metrics and Estimates SABP Iterative Process Validate sizing for server containers and storage Update capacity plans as appropriate SABP Allocate storage Configure network routes Configure server containers Identify firewall/security requirements Validate security zoning for application Build / transfer application Set network restrictions per security model Post Build

38. Key Documents* ACS Application Consolidation Schedule SABP System Architecture Build Plan Process Activity P2V Server Consolidation Approach Process Flow (cont.) The following outlines the rules of engagement for the consolidating an agency application that is migrating from a physical to a virtualized environment. ITD Facility Engineering Secretariat/Agency ITD Service Account Mgmt Service Desk / NOC ITD Hosting Operations ITD Security & Network ITD Storage Operations Agency Team ITD SAM SD Members Hosting Members Storage & Backup Members Network & Security FacilityMembers Plan &Build Legend Integrate ITD and Secretariat operational processes Governance Activity Wiki Page Conduct load and User Acceptance Testing Schedule backups Key Documents Off-page Connector Key Decision Point Configure Disaster Recovery replication (As required) Metrics and Estimates Iterative Process Go Live Conduct Operational Readiness Testing Update Asset & Config Mgmt DB Stabilize and transfer to operations Decommission old instance

39. Key Documents* ACS Application Consolidation Schedule SABP System Architecture Build Plan Process Activity P2P Server Consolidation Approach Process Flow The following outlines the rules of engagement for the consolidating an agency application that is migrating from a physical to a new physical environment. ITD Facility Engineering Secretariat/Agency ITD Service Account Mgmt Infrastructure Planning Group ITD Hosting Operations ITD Security & Network ITD Storage Operations Agency Team ITD SAM IPG Members HostingMembers Storage & Backup Members Network & Security FacilityMembers Review the Service Catalog choosing an existing ITD service offering utilizing standard policies Work with Secretariat / Agency to complete BAR with service targets. Service Catalog must be continually updated with new standard service offerings when economies of scale can be found. In an optimum position, the majority of offerings should meet the agency needs and unique agency configurations should be minimized. Legend Governance Activity Create a detailed migration schedule for the agency’s application Wiki Page Key Documents ACS Off-page Connector Create technical and process requirements for application instance Key Decision Point Validate capacity sizing for server s and storage Update capacity plans as appropriate Metrics and Estimates SABP SABP Iterative Process Allocate storage Configure network routes Configure server containers Identify firewall/security requirements Validate security zoning for application Build / transfer application Set network restrictions per security model Post Build

40. Key Documents* ACS Application Consolidation Schedule SABP System Architecture Build Plan Process Activity V2V Server Consolidation Approach Process Flow (cont.) The following outlines the rules of engagement for the consolidating an agency application that is migrating from a physical to a new physical environment. ITD Facility Engineering Secretariat/Agency ITD Service Account Mgmt Service Desk / NOC ITD Hosting Operations ITD Security & Network ITD Storage Operations Agency Team ITD SAM SD Members Hosting Members Storage & Backup Members Network & Security FacilityMembers Plan &Build Legend Integrate ITD and Secretariat operational processes Governance Activity Wiki Page Conduct load and User Acceptance Testing Schedule backups Key Documents Off-page Connector Key Decision Point Configure Disaster Recovery replication (As required) Metrics and Estimates Iterative Process Go Live Conduct Operational Readiness Testing Update Asset & Config Mgmt DB Stabilize and transfer to operations Decommission old instance

41. Key Documents* ACS Application Consolidation Schedule SABP System Architecture Build Plan Process Activity L&S Server Consolidation Approach Process Flow The following outlines the rules of engagement for the consolidating an agency application that the physical relocation of infrastructure from one physical location to another. ITD Facility Engineering Secretariat/Agency ITD Service Account Mgmt Service Desk / NOC ITD Hosting Operations ITD Security & Network ITD Storage Operations Agency Team ITD SAM SD Members HostingMembers Storage & Backup Members Network & Security FacilityMembers Review the Service Catalog choosing an existing ITD service offering utilizing standard policies Work with Secretariat / Agency to complete BAR with service targets. Service Catalog must be continually updated with new standard service offerings when economies of scale can be found. In an optimum position, the majority of offerings should meet the agency needs and unique agency configurations should be minimized. Legend Governance Activity Create a detailed migration schedule for the agency’s application Wiki Page Key Documents ACS Off-page Connector Create technical and process requirements for application instance Validate facility requirements; updating capacity plan as appropriate Key Decision Point Metrics and Estimates SABP SABP Iterative Process Identify firewall/security requirements Validate security zoning for application Prepare centralized facilities Integrate ITD and Secretariat operational processes Shutdown, disconnect, and pack Transport, rack, and stack Post Move

42. Key Documents* ACS Application Consolidation Schedule SABP System Architecture Build Plan Process Activity L&S Server Consolidation Approach Process Flow (cont.) The following outlines the rules of engagement for the consolidating an agency application that the physical relocation of infrastructure from one physical location to another. ITD Facility Engineering Secretariat/Agency ITD Service Account Mgmt Service Desk / NOC ITD Hosting Operations ITD Security & Network ITD Storage Operations Agency Team ITD SAM SD Members Hosting Members Storage & Backup Members Network & Security FacilityMembers Prepare &Move Legend Configure network routes Governance Activity Wiki Page Go Live Set network restrictions per security model Key Documents Off-page Connector Schedule backups as required Key Decision Point Metrics and Estimates Configure Disaster Recovery replication (As required) Iterative Process Harden the server and ancillary equipment as required Conduct Operational Readiness Testing Update Asset & Config Mgmt DB Stabilize and transfer to operations

43. Benefits of Data Center Services Consolidation • Improves security and reliability of agency applications through placement in properly maintained facilities and resilient infrastructure. • Positions the Commonwealth for the reduction of future recurring costs through achieving economies of scale in acquisition and elimination of duplication of maintenance and support services. • Positions the Commonwealth to provide enhanced talent management and resource utilization through pooling of technical resources. • Improves business continuity in Commonwealth services offered to the constituents in the longer term through geographic diversity of critical applications. • Improves flexibly to more rapidly respond to requirements of the Commonwealth’s Secretariats and agencies through use of common architecture. • Improves ability to support a more graceful evolution of the Commonwealth’s infrastructure.

44. Agency Cost Comparison In addition to the benefits gained from consolidation, some agencies will need to capture their current costs to make an equitable comparison to the ITD service rates.

45. For More Information • To learn more about IT Consolidation in the Commonwealth: • Visit the IT Consolidation Wiki: https://wiki.state.ma.us/confluence/display/itconsolidation/Home • Look also for the IT Consolidation Email Blast and Newsletter released regularly by Consolidation leadership • Have a Question or Feedback? • Search for answers at the Consolidation Frequently Ask Questions page,https://wiki.state.ma.us/confluence/display/itconsolidation/Frequently+Asked+Questions • Post your comments at www.mass.gov/itd/itconsolidationfeedback • Use the email address:ANF-DL-ITConsolidationCommunicationsSubcommittee@state.ma.usto provide your comments anonymously

46. Appendix A: Industry-Leading Product Solutions

47. IT Service Desk Magic Quadrant What You Need to Know Gartner's 2008 IT service desk Magic Quadrant focuses on enterprise-class vendors that met Gartner's criteria, as defined below, that includes the vendor's ability, demonstrated through customer references, to address the needs of customers seeking to provide functionality for incident, problem, change, knowledge, self-service and service-level agreement (SLA) management. Additional analysis for the 2008 Magic Quadrant has been placed on change management features, functionality and integration, because Gartner is finding that 60% to 80% of organizations are choosing change management and the service desk from the same vendor. IT organizations adopting a holistic approach to IT service and support tend to acquire the vendors' suites of IT service management (ITSM) modules. These suites can help clients aggregate data among modules, which leads to better decision making regarding end-user downtime, whether due to application failure or end-user-based issues, the cost and quality of IT service and support, and the business's overall satisfaction with IT. Tool selection is influenced by ease of deployment, integration with other ITSM modules, in particular change management and configuration management database (CDMB), pricing, as well as core functionality around incident and problem management, self-service, reporting, dashboards and workflow. The vendor's ability to deliver feature enhancements and additional ITSM modules has been evolutionary, not revolutionary.

48. IT Event Correlation and Analysis Magic Quadrant What You Need to Know Gartner's Magic Quadrant for IT Event Correlation and Analysis (ECA), 2009 evaluates vendors' ability to execute and their completeness of vision relative to a defined set of evaluation criteria regarding current and future market requirements. A Magic Quadrant should not be the only criterion for selecting a vendor, because the right solution for a given situation can be in any quadrant, depending on the specific needs of the enterprise. Enterprises considering the purchase of an ECA product should develop their own list of evaluation criteria and functional requirements in the categories of event collection/consolidation, processing/correlation and presentation. Large enterprises should consider a multitier event management hierarchy, pushing some event processing and correlation out to the managed IT element at the bottom of the hierarchy. These enterprises should use specialized event management tools in the middle, and should place a "manager of managers" or a business service management (BSM) product on top. When investing in event management, prospects should understand how the product will fit with their overall event-to-incident/problem resolution processes, including workflow, escalation and integration with service desk tools.

49. IT Asset Management Repository Market Scope • What You Need to Know • The enterprise-class IT asset management (ITAM) repository marketplace has undergone considerable consolidation by large players, reflecting the increased focus on financial management in a holistic IT management toolset. • ITAM repositories are moving toward financially supporting integrated IT service management and portfolio management visions. • The advent of the configuration management database (CMDB) has led to some confusion about the role and use of ITAM repositories in the marketplace

50. Enterprise Storage Market Scope • What You Need to Know • 2007 saw a reinvigoration of technology innovation in the high-end enterprise disk array storage market as storage vendors began delivering such technologies as thin provisioning, enhanced replication facilities, redundant array of independent disks (RAID) 6, and internal serial advanced technology attachment (SATA) disk support. While that innovation continued in 2008, albeit more slowly, economics and support capabilities continue to play a greater role in equipment and vendor selection. High-end enterprise disk array storage users are inherently risk-averse. They understand and embrace technology that is mature and stable, tending to wait for technologies to be proven before deploying them. However, the price also has to be right. In today's high-end enterprise disk array market, Gartner research shows that vendors that can compete on price and support are finding success in the market. • End users considering a high-end enterprise disk array purchase are therefore encouraged to include non-product criteria in the selection process, as well as array functionality. These non-product criteria include: • Presales support • Break/fix service and post-sales support • Total-cost-of-ownership evaluation • Technologies that have the net effect of reducing power and cooling consumption and space requirements • Independent software vendor support • Acquisition, upgrade, service and warranty pricing • The impact of changing storage vendors on procedures, automation and scripts, storage management tools, and training