Dell EMC  Statement of Work for City of City of Phoenix IT Transformation

Dell EMC

Prepared for:
Partner
200 W. Washington Street
Phoenix, AZ 85003 / Prepared by:
Dell EMC
4250 N. Drinkwater Blvd
Suite 200
Scottsdale, AZ 85251
Effective Date: November 1, 2017 / Quote Number: 6001011599
For the most up-to-date listing of DellEMC trademarks, see DellEMC Trademarks on EMC.com and DellTechnologies.com.All trademark used herein are the property of their respective owners.

Table of Contents

1.Introduction

2.Engagement Objective

3.Engagement Scope and Approach

3.1.Services

3.2.Engagement Phases and Deliverables

3.2.1.Phase 0: Project Management Phase

3.2.2.Phase 1: Discovery Phase

3.2.3.Phase 2: Infrastructure Readiness Phase

3.2.4.Phase 3: Migration Planning Phase

3.2.5.Phase 4: Migration Execution Phase

3.2.6.Project Deliverables

3.3.Data Center Migration Assumptions

3.3.1.Program / Project Management Assumptions

3.3.2.Discovery and Analysis Assumptions

3.3.3.Migration Planning Assumptions

3.3.4.Migration Execution Assumptions

3.4.Data Center Migration Out of Scope

4.Completion and Acceptance

5.Change Management

6.City of Phoenix Resource Plan

7.City of Phoenix Responsibilities

7.1.General city of Phoenix Responsibilities

7.2.Discovery and Analysis Responsibilities

7.3.Infrastructure Readiness Responsibilities

7.4.Migration Planning Responsibilities

7.5.Migration Execution Responsibilities

8.Additional Engagement Scope Specifications

9.Location

10.Engagement Contacts

11.Fees and Invoicing

11.1.Estimate Revisions

11.2.Expenses and Other Charges

12.Acceptance of Statement of Work

Appendix A MIlestone Acceptance Form

Appendix B Change Request Form

Appendix C Project Organization Chart

Appendix D Terms and Definition

  1. Introduction

This Statement of Work (this “SOW”) is between Partner (“Customer” orShort Customer Name”) and EMC Corporation (“DellEMC” or “EMC”) and sets forth the business parameters and other matters regarding services that Customer has engaged DellEMC to provide hereunder (the “Services”). This SOW and performance of the parties hereunder is governed by and subject to the terms and conditions set forth in the <Master Agreement Name> between Customer and EMC dated as of <Master Agreement Date> (the “Agreement”), which by this reference is incorporated herein and made a part hereof. Capitalized terms used herein but not otherwise defined shall have the meanings ascribed to such terms in the Agreement.

  1. Engagement Objective

The City of Phoenixseeks a partnership with a recognized authority in large, mission critical data center architectures and transition management to assist and provide leadership in the planning, discovery, infrastructure readiness,design and re-architecture of the City’s critical business technologies.

This SOW includes critical components to help the City of Phoenix achieve its stated IT transformation objectives:

  • Consolidate equipment on the data center floors
  • Modernize infrastructure for next generation IT
  • Become an ITaaS provider (cloud-enabled)
  • Service Catalog
  • Self Service
  • Showback/Chargeback
  • Increase availability and agility to deliver services

The remainder of this document provides the detailed project phases, key activities, and work products that will be completed during the engagement.

  1. Engagement Scope and Approach

Listed below is the overall scope for the project, Base (Enterprise and Fire). All deliverables referenced in this SOW are outlined in the milestone table. All deliverables are subject to the City of Phoenixacceptance criteria.

The scope of the Data Center Transformation includes:

  • Transformation/consolidation within 2 existing City of Phoenix data centers:
  • IO data center
  • ITOC data center
  • Migration out of 1 existing Public Safety data centers into IO and/or ITOC
  • 150 S. 12th Street (Fire Operations) – (Only virtual environmentfor Fire)
  • Up to 165 physical servers (Discovery & Analysis)
  • Enterprise: 145
  • Fire: 20
  • Up to 128 business applications
  • Enterprise: 50(these are subset of overall City of Phoenix applications, estimated at 1195. Dell EMC will discover and migrate these applications, COP will learn the process and migrate the remainingapplications on their own)
  • Fire: 78
  • Up to 15 P2V servers to be migrated
  • Enterprise: 15
  • Up to 112 V2V servers to be migrated
  • Enterprise: 50 (50 is subset of Enterprise VMs, estimated to total 935 VMs. Dell EMC will migrate 50 Enterprise VMs, COP will learn the process and migrate the remaining VMs on their own.)
  • Fire: 62
  • Migration of up to 110 TB of file data:
  • Enterprise: 110 TB (up to 500 shares)
  • Up to 4 migration events(COP will manage and execute subsequent migration events after the first 4 included in this SOW).
  • Enterprise SQL Database Migration: Out of Scope in this SOW – covered in related SQL Server SOW. The SQL migrations should happen concurrently and coordinated with the data center migration, whether done by Dell EMC or COP.
  • Police and Fire SQL Database Migration: Out of Scope in this SOW – covered in related SOW. The SQL migrations should happen concurrently and coordinated with the data center migration, whether done by Dell EMC or COP
  • SRDF/Metro:
  • 2 sites, 1 array per site
  • 1 VMAX Family Witness array
  • Up to 10 device or consistency groups per array
  • Up to 10 dynamic R1/R2 RDF groups
  • Up to 100 device and/or Storage Group RDF pairs
  • Up to 2 RA or Gigabit Ethernet directors per array
  • VMware Metro Storage Cluster
  • Configure up to 2 vMSC clusters across 2 sites
  • Transition to COP-led migration of Enterprise applications and infrastructure. At COP request, Dell EMC is discovering and migrating a small subset of Enterprise applications over 4 migration events. After that COP will be responsible for all facets of the Enterprise application migrations, including P2V/V2V.

Dell Transformation Manager (DTM) or other best-in-class migration information management tool and database will be deployed remotely by Software as a Service (SaaS). Dell EMC will manage this as part of the 4-migration event project we are managing and then provide a resource to manage DTM on behalf of COP for 6-months as they continue the migrations.

The parties anticipate the start date for this engagement will be January 1, 2018.

3.1.Services

DellEMC will perform the following Services for Partneron behalf of the City of Phoenix (“COP”) under this SOW:

Program Management Phase - Program Management will establish proper executive sponsor communication and strategic coordination of the overall services effort.

Discovery and Analysis Phase – Establishes detailed discovery of IT applications and systems with an emphasis on their dependencies to ensure business and technical requirements are well understood and in alignment with migration and business continuity strategies. The four sub-phases are:

a) Discover

b) Validate

c) Analyze and Bundle

d) Planning and Scheduling

Infrastructure Readiness Phase – Create the target infrastructure components in the target data center environments from the Discovery and Analysis Phase

a)A functional private cloud with:

  1. A self-service portal accessible by two User Groups (e.g. Cloud Administrator and Cloud Consumer) with access to the service catalog.
  2. A service catalog with two (2) Infrastructure-as-a-Service (IaaS) single virtual machine blueprints (i.e. Red Hat Enterprise Linux or Windows Server) with City of Phoenix defined Operating System, CPU, Memory, and Storage resource allocations.
  3. Request to City of Phoenix existing IPAM solution for full hostname and IP address during virtual machine provisioning.
  4. A self-service backup and restore capability in the service catalog for virtual machines provisioned from pre-engineered blueprints in the service catalog.
  5. Add one secondary site (for provisioning) as an endpoint to the primary site vRealize implementation

b)SRDF/Metro and VMware Storage Cluster

Migration Planning Phase - Confirms the new facility is ready to accept the migrated infrastructure and that steps required to migrate the COP applications have been documented and assigned to appropriate resources. The four sub-phases are:

a) Migration Procedures

b) Test and Contingency Plans (provided by COP to be loaded into DTM)

c) From/To (infrastructure mapping)

d) Table Top Exercises

Migration Execution Phase - Migration Execution becomes a mechanical process with disciplined execution of the migrations as documented in the previous phase. The three sub-phases:

a)Pre-Migration

  1. Establish T-Schedule

b)Migration Execution

  1. P2V & V2V (executed by Dell EMC)
  2. File Migrations (executed by Dell EMC)
  3. Application cutovers (executed by COP)

c)Post-migration

The anticipated project schedule (to be refined and finalized during the first two weeks of the engagement) is shown below. After the seven (7) defined migration events are concluded (~ 24 weeks), the Dell EMC data center migration team will roll off and remaining migrations will be completed by COP. Dell EMC will maintain the overall program manager for ~2 additional months to ensure a smooth transition. Additionally Dell EMC will maintain a consultant on the project for 6 months after the 4 events are concluded for the purpose of supporting the DTM tool while COP conducts subsequent migrations.

3.2.Engagement Phases and Deliverables

Dell EMC will perform the project using a phased approach as detailed below

3.2.1.Phase 0: Project Management Phase

To complete the Dell EMC Data Center Consolidation and Migration services a comprehensive Project Management function is required from within the City of Phoenix’s organization for the relocation consolidation and migration. The City must:

  • Identify an actively engaged Executive Sponsor able to span the entire organization
  • Confirm ongoing Executive management support
  • Establish Project leadership early and follow the chain of command and communication
  • Communicate with and involve application and business stakeholders early
  • Implement a clear governance model with escalation points using best practices provided by Dell EMC
  • Track project risks and issues and escalate when appropriate to confirm proper accountability and a resolution path
  • Invest time in planning, so that all parties understand their roles and responsibilities

The City of Phoenix Project Manager is to confirm management strategy is in place for this engagement. These activities will minimize project risk, in regards to schedule and budget and will allow rapid issue identification, escalation and resolution. The following table describes the activities Dell EMC will perform and the associated work products.

Project Management Key Activities
  • Daily coordination with the City of Phoenix PMO
  • Project oversight for all Dell EMC and Vendor migration tasks
  • Develop, manage and maintain project artifacts
  • Create a detailed Project Work Plan
  • Deliver weekly status reports, including progress, accomplishments, risks and issues
  • Perform and manage change request per the agreed upon process
  • Review and reconcile COP documented changes and confirm data extracts provided by Dell Transformation Managerare correct as defined and agreed-upon in the Change Control Process
  • Prepare/present executive management updates as defined in the project work plan
  • First line of escalation for any engagement issues

3.2.2.Phase 1: Discovery Phase

Dell EMC will leverage data from the City of Phoenix’s asset lists, and/or CMDB’s to develop a data collection strategy.The data collection strategy will include a workshop approach that will update and expand upon theCity of Phoenix provided data as specified below. Dell EMC will conduct interviews with selected business/application and infrastructure SMEs to gather the required information to populate the DTM tool.Dell EMC will also collect documentation related to infrastructure, interfaces, and the data flows of each application. Below is an overview of the collection process:

  • Dell EMC will facilitate the documentation of the current production application and Infrastructure environments for the COP source Data Center with particular attention to the interdependencies among applications and servers and non-production components located in the Data Center (Dev, Test, DR, etc.)
  • COP will provide Dell EMC data from the systems of record and tools. Dell EMC will work with COP to normalize the data and determine data gaps
  • Application interviews will be conducted to further close data gaps and to communicate migration strategies with the application owners and technical/functional support groups
  • Individual mapping of non-production environments (…Development / test) are consider separate application instances
  • Server and application dependencies will be analyzed and confirmed
  • The dependencies and risk profiles of the applications will be used as input to build migration strategy application bundles

Discover

Dell EMC will work with the COP’s teams to gather information about its current business system environment. This is done through workshops, interviews, collectingCOP documents (as available), through the COP tools where available (CMDBs, Asset Lists, etc.) and stored in Dell Transformation Manager (DTM).

Success Criteria for completion of this phase is defined for each deliverable in the Key Deliverable Matrix.

Discover Key Activities
  • Develop Data Collection Plan
  • Agree on data elements to be captured and loaded into DTM
  • Collect and load application and infrastructure data into DTM tool
  • Conduct Managers Workshop to align to the Data Collection Plan
  • Timely receipt of client data from COP to normalize and ingest into DTM
  • Capacity planner assessment for current vSphere environment

Validate

Results of data collection are validated with application and infrastructure owners. Data validation must be complete before bundling and analysis can begin to confirm data integrity.

Validate Key Activities
  • Conduct Data Validation workshops receive sign off on data from identified data owner
  • Dell EMC is integrated into the COP Change Control process - Regularly update DTM to maintain accuracy with an evolving infrastructure/application environmentthru the change control process.

Analyze and Bundle

Once the system/application inventory is mapped and validated, migration bundles are developed based on a variety of criteria intended to minimize both the risk and cost of the moves. Risks will be identified and mitigation plans developed. Recommended Migration Events and Methods are reviewed and approved by theCOP prior to developing the migration strategy and master plan.

Analyze & Bundle (A&B) Key Activities
  • Develop Bundling Criteria
  • Perform Migration Options Analysis to determine the most appropriate migration strategy and tools required to migrate each application/server with minimal risk to the business
  • Develop bundles and assign to a migration method and event based on Bundling Criteria
  • Perform Risk Analysis
  • Perform Vendor Participation Analysis

Review and Schedule

With the bundles defined, move schedules and the detailed roadmap/master plan are developed. Review & Schedule should only be completed if other Discover & Analysis activities were completed by Dell EMC.

Review & Schedule (R&S) Key Activities
  • Complete Executive Summary
  • Define and present Migration Strategy
  • Develop Migration Roadmap

3.2.3.Phase 2: Infrastructure Readiness Phase

This phase will leverage the data gathered during the Discovery Phase to design, architect and implement the build out the target infrastructure at the COP data center to include the following key objectives:

  • Infrastructure as a Service (IaaS) Foundation based on VMware vRealize Automation technology
  • SRDF/Metro and VMware Metro Storage Cluster

The following are the Infrastructure Readiness key activities

Infrastructure Readiness Key Activities
Infrastructure as a Service Design Phase:
  • Conduct IaaS Solution Overview Workshop
  • 2 hour workshop introducing Infrastructure Automation Production Private Cloud solution
  • Review a summary of the Infrastructure Automation Production Private Cloud prescriptive architecture design, concepts, and terminology
  • Review VMware vRealize Automation 3rd Party integration best practices for COPAvamar and IPAM environments
  • Conduct IaaS Service Catalog Definition Workshop
  • 2 hour workshop introducing cloud services catalog concept and best practices guideline
  • Review sample definitions for 2 IaaS single VM blueprints (e.g. RHEL or Windows)
  • Review and document self-service backup and restore services for virtual machines provisioned from pre-engineered blueprints in the service catalog
  • Conduct Portal and Automation Workshops
  • 2 hour workshop introducing portal automation features, functionality, and best practice guidelines
  • Review approval workflows via email notification for services requested, provisioned, changed and de-provisioned
  • Conduct Operations and Orchestration Workshop
  • 2 hour workshop introducing portal operations features, functionality, and best practice guidelines
  • Review Operations Portal and Operations Dashboard features and functionality
  • Document COP configuration details for the operations and management portal
  • Conduct Test and Acceptance Plan Workshop
  • 2 hour workshop introducing Test and Acceptance Plan best practice guidelines
  • Review test cases covering components and capabilities included in private cloud and expected outcomes/results including portal operations and functionality, service catalog ordering, 3rd party integration with Avamar, ServiceNow Standard CMDB and IPAM, default monitoring and security
  • Update documentation
  • Update Design Document Template with City of Phoenix specific design elements
  • Update Test and Acceptance Plan with City of Phoenix specific testing and acceptance criteria
Infrastructure as a Service Build, Test and Acceptance Phase:
  • Build Infrastructure Automation Production Environment
  • Install and configure distributed VMware vRealize Suite Enterprise (load balanced)
  • Up to 2 vSphere Clusters, 1 default tenant plus 1 additional tenant
  • Up to 2 vRA appliances including vRealize Automation and Orchestrator
  • Up to 2 IaaS Web Windows Servers and up to 2 IaaS Manager Windows Servers
  • Up to 2 IaaS DEM Orchestrator / Worker Windows Servers and up to 2 IaaS Agent Windows Servers
  • Up to 1 vCenter Server Instance for Cloud environment and up to 1 Update Manager Server
  • Up to 1 PSC/SSO Servers depending on the version of vSphere and up to 1 non-default tenant and up to 2 Fabric Groups
  • Up to 3 Business Groups and up to 2 Approval Policies
  • Up to 1 vRealize Operations Manager Appliance and up to 1 vRealize LogInsight Appliance
  • Up to 2 single machine blueprints for IaaS services on 1 existing vCenter Server (RHEL or Windows)
  • Add one secondary site as an endpoint to the primary site vRealize implementation. This secondary site is for provisioning only. Cloud Management Portal will only reside in primary site and will not be configured in a DR (Disaster recovery). Tenant Workloads will not be configured in a DR configuration. Local Tenant workloads only.
  • Add 1 3PAR and 1 Compellent asendpointsto the primary site vRealize implementation.
  • Integrate COP’s existing IPAM environment with the vRealize Automation Appliance
  • Requests to customer's existing IPAM solution for full hostname and IP address during virtual machine provisioning.
  • Integrate COP existing Avamar environment with the vRealize Automation Appliance
  • IPAM integration assumes customer has an existing healthy IPAM environment (i.e. Infoblox, Men & Mice Suite, or Solarwinds with RESTful APIs) for EMC to integrate with the VMware vRealize Automation environment. Customer will be responsible for testing, troubleshooting, and remediating any issues with the IPAM environment and configuration.
  • Deploy and integrate vRealize Business Standard Edition with showback for catalog items.
  • Execute the IaaS Test and Acceptance Plan
  • City of Phoenix and Dell EMC to execute Test and Acceptance Plan
  • Dell EMC to remediate severity 1 and 2 defects
  • Dell EMC to update Test and Acceptance Plan
  • City of Phoenix and Dell EMC to review final testing results and acceptance
  • Finalize documentation
  • Update Design Document and Configuration Workbook with changes made during acceptance testing
Infrastructure as a Service Operational Hand-off Phase:
  • Conduct Knowledge Transfer Workshop
  • 1 day workshop to introduce stakeholders to operational best practice and usage guidelines
  • Review Design Document and Configuration Workbook including 3rd party integration with City of Phoenix Avamar and IPAM environments
  • Demonstrate and communicate Cloud Administrator role
  • Demonstrate and communicate Cloud Consumer role
  • Conduct Scaling Options and Best Practices Roadmap Meeting
  • 2 hour meeting introducing limitations of deployed vRealize suite architecture
  • Discuss business needs for DR or continuous availability
  • Discuss options for scaling the deployed architecture
  • Conduct Recommended Training Meeting
  • 2 hour meeting introducing recommended technical training
  • Knowledge transfer sessions provide basic understanding and capabilities but not intended as substitute for complete technology training
  • Conduct Executive Briefing and Closeout Meeting
  • 2 hour meeting to demonstrate Cloud Administrator and Cloud Consumer roles, provisioning IaaS workloads, and Operations Dashboards
  • Discuss lessons learned and recommended next steps
  • SRDF/Metro and VMware Storage Cluster
  • Validate VMAX configuration at both sites
  • Configure RA or Gigabit Ethernet director settings
  • Install SRDF license
  • Create dynamic RDF groups
  • Create and configure RDF pairs
  • Perform initial monitoring of RDF device and/or Storage Group pair synchronization
  • Create and deliver SRDF/Metro Test Plan and SRDF/Metro Configuration Guide
  • Configure vMSC clusters across 2 sites
  • Configure SRDF Metro R2 host access at secondary site
  • Configure vMSC Cluster DRS
  • Configure vMSC Cluster HA & admission control
  • Configure HA heartbeating – network & datastore for vMSC
  • Configure All Paths Down (APL) & Permanent Data Loss (PDL) for vMSC
  • Configure VM/Host Groups & VM/Host Rules for vMSC
  • Confirm HA capabilities between hosts within each vMSC cluster across sites

3.2.4.Phase 3: Migration Planning Phase