ITS 18-202 - Attachment D Web viewMS Word. IaaS Configuration Workbook. ... SvMotion, Converter....

Dell EMC

Prepared for:

Partner200 W. Washington StreetPhoenix, AZ 85003

Prepared by:

Dell EMC4250 N. Drinkwater BlvdSuite 200Scottsdale, AZ 85251

Effective Date: November 1, 2017 Quote Number: 6001011599

For the most up-to-date listing of Dell EMC trademarks, see Dell EMC Trademarks on EMC.com and DellTechnologies.com. All trademark used herein are the property of their respective owners.

Statement of Work for

City of Phoenix IT Transformation (Base + Police)

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

TABLE OF CONTENTS

1. INTRODUCTION.............................................................................................................42. ENGAGEMENT OBJECTIVE.........................................................................................43. ENGAGEMENT SCOPE AND APPROACH...................................................................4

3.1. SERVICES...............................................................................................................53.2. ENGAGEMENT PHASES AND DELIVERABLES....................................................7

3.2.1. Phase 0: Project Management Phase..........................................................................73.2.2. Phase 1: Discovery Phase............................................................................................83.2.3. Phase 2: Infrastructure Readiness Phase....................................................................93.2.4. Phase 3: Migration Planning Phase............................................................................123.2.5. Phase 4: Migration Execution Phase..........................................................................133.2.6. Project Deliverables.....................................................................................................15

3.3. DATA CENTER MIGRATION ASSUMPTIONS......................................................173.3.1. Program / Project Management Assumptions.............................................................173.3.2. Discovery and Analysis Assumptions..........................................................................173.3.3. Migration Planning Assumptions..................................................................................173.3.4. Migration Execution Assumptions................................................................................18

3.4. DATA CENTER MIGRATION OUT OF SCOPE.....................................................184. COMPLETION AND ACCEPTANCE............................................................................205. CHANGE MANAGEMENT............................................................................................206. CITY OF PHOENIX RESOURCE PLAN.......................................................................217. CITY OF PHOENIX RESPONSIBILITIES.....................................................................23

7.1. GENERAL CITY OF PHOENIX RESPONSIBILITIES............................................237.2. DISCOVERY AND ANALYSIS RESPONSIBILITIES.............................................237.3. INFRASTRUCTURE READINESS RESPONSIBILITIES.......................................247.4. MIGRATION PLANNING RESPONSIBILITIES......................................................247.5. MIGRATION EXECUTION RESPONSIBILITIES...................................................24

8. ADDITIONAL ENGAGEMENT SCOPE SPECIFICATIONS.........................................269. LOCATION................................................................................................................... 2710. ENGAGEMENT CONTACTS........................................................................................2711. FEES AND INVOICING................................................................................................28

11.1. ESTIMATE REVISIONS......................................................................................2811.2. EXPENSES AND OTHER CHARGES................................................................29

12. ACCEPTANCE OF STATEMENT OF WORK..............................................................30

© Copyright 2017 Dell EMC 2 of 37


APPENDIX A MILESTONE ACCEPTANCE FORM...............................................................31APPENDIX B CHANGE REQUEST FORM............................................................................32APPENDIX C PROJECT ORGANIZATION CHART..............................................................35APPENDIX D TERMS AND DEFINITION..............................................................................36



1. IntroductionThis Statement of Work (this “SOW”) is between <Partner> (“Customer” or <Short Customer Name>”) and EMC Corporation (“Dell EMC” or “EMC”) and sets forth the business parameters and other matters regarding services that Customer has engaged Dell EMC 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.

2. Engagement ObjectiveThe City of Phoenix seeks 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)

o Service Catalogo Self Serviceo 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.

3. Engagement Scope and ApproachListed below is the overall scope for the project, Base (Enterprise and Fire) + Police. All deliverables referenced in this SOW are outlined in the milestone table. All deliverables are subject to the City of Phoenix acceptance criteria.

The scope of the Data Center Transformation includes: Transformation/consolidation within 2 existing City of Phoenix data centers:

o IO data centero ITOC data center

Migration out of 2 existing Public Safety data centers into IO and/or ITOCo 620 Police HQ (Police)o 150 S. 12th Street (Fire Operations) – (Only virtual environment for Fire)

Up to 240 physical servers (Discovery & Analysis)o Enterprise: 145o Police: 75o Fire: 20

Up to 198 business applicationso 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 remaining applications on their own)

o Police: 70o Fire: 78

Up to 65 P2V servers to be migrated o Enterprise: 15o Police: 50



Up to 163 V2V servers to be migratedo 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.)o Police: 51 (Police VM migrations are Hyper-V to VMware ESX)o Fire: 62

Migration of up to 145 TB of file data:o Enterprise: 110 TB (up to 500 shares)o Police: 35 TB (up to 275 shares)

Up to 7 migration events (COP will manage and execute subsequent migration events after the first 7 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:o 2 sites, 1 array per siteo 1 VMAX Family Witness arrayo Up to 10 device or consistency groups per arrayo Up to 10 dynamic R1/R2 RDF groupso Up to 100 device and/or Storage Group RDF pairso Up to 2 RA or Gigabit Ethernet directors per array

VMware Metro Storage Clustero 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 7 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 7-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.SERVICESDell EMC will perform the following Services for Partner on 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:

a. A self-service portal accessible by two User Groups (e.g. Cloud Administrator and Cloud Consumer) with access to the service catalog.

b. 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.

c. Request to City of Phoenix existing IPAM solution for full hostname and IP address during virtual machine provisioning.

d. A self-service backup and restore capability in the service catalog for virtual machines provisioned from pre-engineered blueprints in the service catalog.

e. 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

a. Establish T-Schedule

b) Migration Execution

a. P2V & V2V (executed by Dell EMC)

b. File Migrations (executed by Dell EMC)

c. 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 (~ 30 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 ~1 additional month to ensure a smooth transition. Additionally Dell EMC will maintain a consultant on the project for 6 months after the 7 events are concluded for the purpose of supporting the DTM tool while COP conducts subsequent migrations.



Mon 1 Mon 2 Mon 3 Mon 4 Mon 5 Mon 6 Mon 7 Mon 8 Mon 9

Dell EMC Program Management

IaaS

Mobilization

Planning & Execution (7 events)

SRDF/Metro

Dell EMC Move #1Dell EMC Move #2Dell EMC Move #3

Dell EMC Move #4

Discovery & Analysis

COP Enterprise MovesUntil COP completes6 month DTM support

Dell EMC Move #5Dell EMC Move #6

Dell EMC Move #7

3.2.ENGAGEMENT PHASES AND DELIVERABLESDell EMC will perform the project using a phased approach as detailed below

3.2.1. PHASE 0: PROJECT MANAGEMENT PHASETo 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 Manager are 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 PHASEDell 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 the City 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.)o 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 gapso Application interviews will be conducted to further close data gaps and to communicate migration strategies

with the application owners and technical/functional support groupso 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

DiscoverDell EMC will work with the COP’s teams to gather information about its current business system environment. This is done through workshops, interviews, collecting COP 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

o 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

ValidateResults 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 environment thru the change control process.

Analyze and BundleOnce 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 the COP 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 ScheduleWith 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 PHASEThis 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 ActivitiesInfrastructure as a Service Design Phase: Conduct IaaS Solution Overview Workshop

o 2 hour workshop introducing Infrastructure Automation Production Private Cloud solutiono Review a summary of the Infrastructure Automation Production Private Cloud prescriptive

architecture design, concepts, and terminologyo Review VMware vRealize Automation 3rd Party integration best practices for COP Avamar and

IPAM environments Conduct IaaS Service Catalog Definition Workshop



o 2 hour workshop introducing cloud services catalog concept and best practices guidelineo Review sample definitions for 2 IaaS single VM blueprints (e.g. RHEL or Windows)o 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

o 2 hour workshop introducing portal automation features, functionality, and best practice guidelines

o Review approval workflows via email notification for services requested, provisioned, changed and de-provisioned

Conduct Operations and Orchestration Workshopo 2 hour workshop introducing portal operations features, functionality, and best practice

guidelineso Review Operations Portal and Operations Dashboard features and functionalityo Document COP configuration details for the operations and management portal

Conduct Test and Acceptance Plan Workshopo 2 hour workshop introducing Test and Acceptance Plan best practice guidelineso Review test cases covering components and capabilities included in private cloud and expected

outcomes/results including portal operations and functionality, service catalog ordering, 3 rd party integration with Avamar, ServiceNow Standard CMDB and IPAM, default monitoring and security

Update documentationo Update Design Document Template with City of Phoenix specific design elementso 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

o Install and configure distributed VMware vRealize Suite Enterprise (load balanced)o Up to 2 vSphere Clusters, 1 default tenant plus 1 additional tenanto Up to 2 vRA appliances including vRealize Automation and Orchestratoro Up to 2 IaaS Web Windows Servers and up to 2 IaaS Manager Windows Serverso Up to 2 IaaS DEM Orchestrator / Worker Windows Servers and up to 2 IaaS Agent Windows

Serverso Up to 1 vCenter Server Instance for Cloud environment and up to 1 Update Manager Servero Up to 1 PSC/SSO Servers depending on the version of vSphere and up to 1 non-default tenant

and up to 2 Fabric Groupso Up to 3 Business Groups and up to 2 Approval Policieso Up to 1 vRealize Operations Manager Appliance and up to 1 vRealize LogInsight Applianceo Up to 2 single machine blueprints for IaaS services on 1 existing vCenter Server (RHEL or

Windows)o 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.

o Add 1 3PAR and 1 Compellent as endpoints to the primary site vRealize implementation.o Integrate COP’s existing IPAM environment with the vRealize Automation Applianceo Requests to customer's existing IPAM solution for full hostname and IP address during virtual

machine provisioning.o Integrate COP existing Avamar environment with the vRealize Automation Applianceo 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.

o Deploy and integrate vRealize Business Standard Edition with showback for catalog items.



Execute the IaaS Test and Acceptance Plano City of Phoenix and Dell EMC to execute Test and Acceptance Plano Dell EMC to remediate severity 1 and 2 defectso Dell EMC to update Test and Acceptance Plano City of Phoenix and Dell EMC to review final testing results and acceptance

Finalize documentationo Update Design Document and Configuration Workbook with changes made during acceptance

testing

Infrastructure as a Service Operational Hand-off Phase: Conduct Knowledge Transfer Workshop

o 1 day workshop to introduce stakeholders to operational best practice and usage guidelineso Review Design Document and Configuration Workbook including 3rd party integration with City of

Phoenix Avamar and IPAM environmentso Demonstrate and communicate Cloud Administrator roleo Demonstrate and communicate Cloud Consumer role

Conduct Scaling Options and Best Practices Roadmap Meetingo 2 hour meeting introducing limitations of deployed vRealize suite architectureo Discuss business needs for DR or continuous availabilityo Discuss options for scaling the deployed architecture

Conduct Recommended Training Meetingo 2 hour meeting introducing recommended technical trainingo Knowledge transfer sessions provide basic understanding and capabilities but not intended as

substitute for complete technology training Conduct Executive Briefing and Closeout Meeting

o 2 hour meeting to demonstrate Cloud Administrator and Cloud Consumer roles, provisioning IaaS workloads, and Operations Dashboards

o Discuss lessons learned and recommended next steps

SRDF/Metro and VMware Storage Clustero Validate VMAX configuration at both siteso Configure RA or Gigabit Ethernet director settingso Install SRDF licenseo Create dynamic RDF groupso Create and configure RDF pairso Perform initial monitoring of RDF device and/or Storage Group pair synchronizationo Create and deliver SRDF/Metro Test Plan and SRDF/Metro Configuration Guideo Configure vMSC clusters across 2 siteso Configure SRDF Metro R2 host access at secondary siteo Configure vMSC Cluster DRSo Configure vMSC Cluster HA & admission controlo Configure HA heartbeating – network & datastore for vMSCo Configure All Paths Down (APL) & Permanent Data Loss (PDL) for vMSCo Configure VM/Host Groups & VM/Host Rules for vMSCo Confirm HA capabilities between hosts within each vMSC cluster across sites



3.2.4. PHASE 3: MIGRATION PLANNING PHASEThis phase is directed at leveraging the data gathered during the Discovery Phase to develop migration plans and detailed procedures that will enable COP to successfully migrate in scope applications and servers within project expected timelines. Detailed Migration Planning contains four components:

Migration ProceduresThe results of Discovery and Analysis are leveraged during the Migration Procedures phase to develop migration plans and detailed procedures that will enable COP to successfully migrate within project expected timelines. COP and Dell EMC will incorporate the identified migration solutions into a final migration plan. This plan will serve as the mechanism for communicating schedules and detailed tasks to all participating and interested parties.

Test and Contingency PlansDell EMC will work with COP to collect the test and contingency plans (developed by COP SMEs) which Dell EMC will load in Dell Transformation Manager (DTM). Dell EMC will conduct workshop sessions to gather each server, database, and application group’s plan for testing their respective environment after the infrastructure has moved. All contingency/rollback plans will be identified during workshops and provided by COP to load into DTM.

From/To (infrastructure mapping)Dell EMC will work with the COP’s infrastructure teams to gather each device’s current physical and logical attributes. All attributes (physical location, attached hardware, storage, and networking) are accounted for, assigned, and provisioned for in the target Data Center. This information will be made available for infrastructure and application teams to allow them to prepare for changes that affect their respective systems.

Table Top ExercisesDell EMC will facilitate a minimum of two Table Top exercises per move event, one during the Detailed Migration Planning phase (at the end of first Table Top, DTM’s goal is to be 60%-65% complete) and one during the Migration Execution phase approximately 10 days prior to each move event (DTM should be greater than 90% complete). These exercises are “dry runs” of Migration Events from Pre-Migration through Post-Migration activities. Completion of the last Table Top exercise signifies that Migration Planning for the specific Migration Event is complete.

Migration Planning Key Activities



Conduct Workshops with the COP SMEs to collect and validate application/infrastructure mapping, detailed migration procedures to include Pre-Migration, Shutdown, Cutover, Startup, and Post-Migration activities into DTM

Collect and verify team resources scheduled for each migration event (application and infrastructure) Table Top 1 exercise – Review compiled data and mapping information to determine any gaps or

concerns that may need to be addressed and or corrected. Coordinate with COP to confirm target site readiness/certification Coordinate Infrastructure Readiness to confirm the target site infrastructure is ready per the master

migration scheduleMonitor server and storage swing/swap gear build-out if applicable

Dell EMC will work with COP to complete the Migration Planning:o Application and infrastructure dependencies for migrationo Rollback / remediation plans in case of failed migrationo All foreseeable significant action items and their owners and communicating the plan to the COP

stakeholder organizationso Identify final candidate server list(s) for migrationo Document the available outage windows by class of application (test/dev, QA, production)

Dell EMC will work with the COP support groups (server, application, network, DBA, storage, etc.) as COP develops test plans that will be executed after the equipment or logical data or equipment has landed on the target environment

Dell EMC will work with COP support groups to document contingency recovery approach to mitigate migration risks (COP, application and infrastructure teams own development of contingency plans). Dell EMC will track the delivery of contingency plans and escalate if the infrastructure and/or application team in accordance with the project schedule are not being delivered.

Work with COP infrastructure groups (server, network, database, storage, & facilities) to confirm all new equipment is provisioned for the Data Center

Monitor Target environment buildout Conduct 4-8 hour “dry run” of the DTM migration tasks to include collection and/or review of:

o Dell EMC / COP Resource Plano Infrastructure From/To reviewo Backup procedureso Application shutdown and startup procedureso Test Planso Back-out Plano Contingency Planso Hour-by-hour review (starting with pre-migration tasks)

3.2.5. PHASE 4: MIGRATION EXECUTION PHASEDuring this phase, Dell EMC will provide skilled V2V Migration Engineers who have technical expertise with VMware vSphere products to perform the actual virtual to virtual server migrations on behalf of COP.

The consultants will provide the following services to COP as identified in the detailed task list in the Migration Project Plan:

Conduct pre-migration, migration and post-migration tasks. Coordinate migration approvals and project management with COP project manager and project team Run the VMware tools to migrate virtual machines. Migrations shall be performed during the COP-defined

system maintenance windows Provide technical Level 1 (primary responsibility) and Level 2 (secondary responsibility) troubleshooting of

migration problems Integrate the virtual machines into COP vSphere environment



Migration Execution consists of three components:

Pre MigrationDell EMC will work with COP to confirm all migration preparation activities are accomplished and all possible migration risks are compiled and accounted for prior to the migration execution.

Migration ExecutionDell EMC will manage/coordinate the migration event, document all issues that arise including resolutions, and provide migration status. Additionally Dell EMC will execute the in-scope P2V and V2V migrations.

Post MigrationFinalize migration documentation and facilitating the Lessons Learned review

Lessons Learned to be completed within 4 business days of migration event completion.

Dell EMC will provide 6 months of Dell Transformation Manager Support after completion of the 7 in-scope migration events as COP continues Enterprise migrations on their own.

Migration Execution Key Activities Final Table Top exercise is a 4-8 hour “dry run” of all migration event tasks in DTM in preparation for

the migration event to Confirm migration readinesso Confirm with the COP the readiness of swing/swap equipment (if applicable) specific to each

migration evento Confirm COP resources/vendor(s) tasks and availabilityo Confirm pre-migration notifications are made per the Communication Plano Validate project resources availability

Confirm migration planning and lock-in scope of Application and Infrastructure freeze points Establish Go/No-Go Criteria Go/No-Go presentation to obtain sign-off on migration readiness T-2 days from migration date Staff and manage a migration command center Execute P2V and V2V migrations

o Plan and develop migration approacho Install and configure migration toolso Develop detailed back out / remediation planso Develop Test Plano Execute queued P2V and V2V migrationso Monitor City of Phoenix validation process for completiono Execute (with City of Phoenix) Test Plano Hand-off to City of Phoenix

Execute file data migrations to Isilono Install and configure DobiMinero Verify that the customer has source data backup, access privileges to source file storage,

network bandwidth requirements, and remediation required to source and target file environment.

o Develop migration design, including source to target mappings, migration limits, network, access privileges, migration schedule, pre-migration tasks, migration procedures, cutover activities, and post-migration tasks.

o Develop migration plan to execute test migration and documents the tasks for preparation, cutover, and post-migration.

o Develop the Test Plan.o Conduct implementation review meeting o Prepares the source and target for migration including verifying access privileges, source to

target mappings, network bandwidth, and recommended changes to migration environment.



o Conducts a test migration to verify connectivity and validity of the migration methodology.o Set groupings of data for migration cutover events and initiates the data migration.o Validates successful completion of data migration.o Verifies source system is no longer active once migration is complete.o Performs the data migration cleanup.

Track, coordinate, and report on Source and Target Data Center activities:o Dell EMC will manage migration documentation issues that arise during the migration

execution and provide escalation/notification per the Communication Plan Facilitate Lessons Learned review after each migration

o Description of migration activities and any issues encountered during the migrationo Corrective actions to resolve and/or escalate issues that may be applied to future migration

events

3.2.6. PROJECT DELIVERABLES Please note that all deliverables are takeaways except for DTM which remains a Dell EMC-owned tool.

Deliverables Tasks Deliverable MediaProject Charter Define:

Project Scope Project Objectives Project Governance Reporting Structure Stakeholders Roles and Responsibilities Resource Management Assumptions Critical Interdependencies Milestones and Deliverables Quality Management

MS Word

Communication Plan Define: Engagement Communication Guidelines Communication Vehicles Escalation Process Risk and Issues Management Action Items Project Status Reports Change Management

MS Word

Expectations Matrix Define: Scope Goals and Objectives Expectations

MS Excel

Project Work Plan Define plan to include: Tasks Dependencies Outputs Resources Timeframes

MS Project



Deliverable Matrix Define: Deliverable by phase Content of deliverable Acceptance Criteria and Date

MS Excel

Kick Off Deck Define: Resource Review Data Collection Plan Project Milestones

MS PowerPoint

Project Status Report Components: Action Item Register Risk and Issues Register Contact List

MS Excel/PowerPoint

Application and Infrastructure Validation

As defined in DTM DTM

Master Table Top Exercise Schedule

Create Table Top Overview summary Schedule Table Top review

DTM

Migration Bundle Review Components that must move together (based on Bundling Criteria) to define a “bundle.”

DTM

Vendor Contacts Prepare a presentation of vendor contacts for all vendors involved n move execution

MS PowerPoint

Resource Plan Receive Resource Plan for each application and infrastructure group.

DTM

Migration Execution Tasks DTM contains all procedures including the shutdown, cutover, startup and testing for the Migration Execution plan.

DTM

Migration Test Plans Include Test Plans in DTM for each move event to include: In-scope Application, Database, Server and Storage

environments

DTM

Contingency Plans Include Contingency Plans in DTM for each move event to include: In-scope Application, Database, Network, Server and

Storage environments

DTM

Back Out Procedures and Requirements

Include Back Out Procedures in event new Data Center cannot facilitate in-scope activities

DTM

Post Migration Migration Execution Tasks

Finalize Migration Event Tasks and Executive level Dashboard Report

DTM

IaaS Design Document Design document for future state IaaS infrastructure MS WordIaaS Configuration Workbook

Documented configuration of target IaaS infrastructure MS Excel

IaaS Test and Acceptance Plan

Executed test plan for IaaS environment MS Excel

SRDF/Metro Test Plan and Configuration Guide

Executed test plan for SRDF/Metro MS Excel and MS Word

vMSC Design Guide Design document for target VMware Metro Storage Cluster

MS Word

3.3. DATA CENTER MIGRATION ASSUMPTIONS3.3.1. PROGRAM / PROJECT MANAGEMENT ASSUMPTIONS Identified an executive sponsor will serve as a point of escalation and will be assigned prior to the Project

Kickoff SOW and Project Management artifacts are reviewed with COP within the first two weeks after Project Kickoff



Dell EMC provides Program Management services to facilitate the Data Center Migration process. COP is responsible to provide Project Management to coordinate and manage all other day-to-day activities related to the Data Center Migration including: all physical build-out of Network, Server and Infrastructure

Dell EMC will follow the current COP security procedures and access requirements in place at that time Any software, equipment, or consulting tools, which may be furnished or utilized by Dell EMC in the

performance of these services, shall remain the property of Dell EMC and shall be immediately returned to Dell EMC upon its request or upon completion of the services

Any system (i.e. output from vCenter native tools or CMDB) or verified data that COP has in hand will be provided at (or before) project kickoff. The Master Migration Schedule in Transition Strategy Report will be agreed to the beginning of the detailed migration-planning phase.

Dell EMC Project/Program Management resources are not guaranteed as dedicated resources to this engagement.

Dell EMC will provide a migration bridge line and breakout bridge lines with the capacity to handle all migration participants

The project is a continuous 24 week engagement with no pauses or breaks.

3.3.2. DISCOVERY AND ANALYSIS ASSUMPTIONSData normalization will occur with the assistance and inputs from application owners, DBAs, and server

administratorsCity of Phoenix will provide good and accurate inventory dataValidation application and infrastructure owners are in leadership positions for their respective areaData from COP will be provided in a csv formatCOP will provide complete list of application, infrastructure and associated owners (with contact information) to Dell

EMC on Day 1 or beforeAny on-boarding, work areas (i.e. building facilities, data center access) or other access / credentials necessary for

Dell EMC to perform the in scope work (VPN, network access, email ID, etc.) will be in place Day 1 or before project kick-off.

Physical site access (i.e. data center and office/workspace) will be available to Dell EMC team as needed to insure project success.

If Dell EMC resources will be required to access COP repositories (i.e. SharePoint etc.) a COP laptop or workstation will be made available for the duration of the project.

Missed workshop appointment by COP SME(s) or delegate has the potential to delay the project and impact timeline and resources

Any orphan servers/apps escalated by Dell EMC will be resolved within 1-2 business days of notificationCOP will provide access to COP app and infrastructure owner(s) SME(s) for the duration of discovery and analysis

to provide validation and any remaining data/server gapsIf COP primary contact/resource is not available a backup (or secondary) will be identified by COP and made

available as needed.From/To (infrastructure mapping) information will only be collected for infrastructure identified as “In Scope”Table-top for move event exercise is mandatory for all Dell EMC and COP migration teams

3.3.3. MIGRATION PLANNING ASSUMPTIONSMigrations will be considered “like for like”. This means no re-platforming of application or infrastructure will occur

during the migration events, if a re-platforming change moment is required, COP will be responsible to confirm it is completed prior to the 6 week migration lock down period in which no application and infrastructure configuration changes are allowed.

Dell EMC is integrated into COP Change Control process at both Data Centers throughout the migration.Hardware and software support contracts currently in place are sufficient to provide for timely resolution of any

hardware or software failures that may impact execution of migrations



Migration Schedule is considered locked as of the beginning of this phase. Any changes require mutual agreement of Dell EMC and COP.

Infrastructure will be provisioned in time to meet defined project schedulesResources necessary for the successful migration will be planned for, identified and communicated 4 weeks in

advance of each event. Infrastructure/Application remain “locked down” for a period of seven days after the associated migration is

complete.There is sufficient Network Capacity to support the proposed migration schedule.COP infrastructure and application staffing is available to support the migration schedule and COP will assign a

PM and Technical lead as SPOC for all server build management and will assign PM and Technical leads for Target Data Center build out.

Each migration event will take place over no more than three consecutive days (Friday 1800 hrs. – Sunday 2400 hrs.)

The Migration Team has physical access to both source and target Data Centers throughout the migration as required.

3.3.4. MIGRATION EXECUTION ASSUMPTIONSNo physical transportation costs are included in this SOW. Hardware and software support contracts currently in place are sufficient to provide for timely resolution of any

hardware or software failures that may impact implementation of migrationsUp to 7 move events are included. If a move event is cancelled by City of Phoenix less than 3 weeks prior to

scheduled move date the move will be considered complete and may necessitate a change request for an additional move event.

Migration of VMs is “like for like”, no O.S. upgrades or changes are includedAll in-scope Fire and Police applications are migrating to the same two destination data centers.Decommissioning and removal of decommissioned equipment and data center space is out of scopeThere is 1 GB bandwidth between Police DC and IO/ITOC. Network will be upgraded to 10 GB prior to migration

execution.

3.4. DATA CENTER MIGRATION OUT OF SCOPEDell EMC is responsible for performing the Services listed in the key activities and deliverable section above within this Statement of Work (SOW). All other services are considered outside the scope of this SOW. If the Customer wishes to modify the Services, the Customer agrees to use the Change Request procedures as described herein. The following are deemed to be expressly out of scope for this SOW:

Discovery and Analysis Out of Scope Determination of SLA’s or RTO/RPO requirements

Hosts and the associated Operating System and hardware that are not supported under the Dell EMC Support matrix for the destination array

Infrastructure Readiness Out of Scope Infrastructure performance, load testing, and installation of applications

Application services using VMware vRealize Application Services.

Post-provisioning services may be incorporated into a standard service catalog as part of an additional scope of work but are out of scope for this engagement.



Customization of the VMware vRealize Automation product beyond out-of-the-box features, including development and modification of default workflows.

Integration with additional endpoints that are not VMware vSphere, including VMware vCloud Director. Additional integration work or endpoints can be provided under a separate Statement of Work.

Integration with VMware NSX is out of scope in this SOW. NSX work is covered in separate VMware SOW.

Automated datastore provisioning.

Remediation work associated with any problems resulting from the content, completeness, accuracy, and consistency of any data, materials, or information supplied by COP.

Hardware procurement, installation, configuration, testing, validation, or management is out of scope in this SOW. Hardware procurement handled in separate quote by Dell EMC.

Purchasing, licensing, or configuring the Operating System (Windows, Linux, etc.) or Database Software (Oracle, Microsoft SQL, etc.). (Configuration of Microsoft SQL is covered under the related Microsoft SQL SOW)

Windows Imaging (WIM) or vRealize Automation Center guest agents.

Custom development, whether or not based on VMware APIs.

Implementing hardware-based security – compliance, logging, automated workflow, or backup and recovery solutions is out of scope for this SOW. Avamar backup work covered in separate services outside of this SOW.

Creating client operating system base images.

Virtualizing client application use cases.

Creating operation manuals for the IaaS services created in this SOW.

VMware product support is not covered within this SOW.

Migrating virtual machines or vApps from or to the vSphere environment, or to or from any other environment beyond the use cases included in the Infrastructure Automation Service.

Configuring, tuning, or troubleshooting the client server, storage, or network environment except when required to support the vRealize Automation Center environment.

Developing client IaaS offering descriptions.

IT Service Management (“ITSM”) - No integration with existing ITSM tools and systems (Change Management, Request, or Incident management) is included.

Enterprise Resource Planning (“ERP”) - No integration with existing ERP systems is included.

Ticketing - No integration with Ticketing/Change Management system(s) is included.

Network/Host Name: No integration with network naming or host naming brokers included.

External load balancers, or other software.

Detailed Migration Planning Out of Scope Application performance, load testing, and installation of applications

Application redesign and re-architecture, or transformation activities

Network analysis and latency assurance testing

Facilities design, redesign or build out

Services related to purchasing and/or procurement of hardware platforms and rack configurations to be installed in the new Data Center

Physical servers not being virtualized are out of scope for migration. COP is responsible for migrating any physical hosts not migrated along with their associated data.



4. Completion and AcceptanceUpon completion of a Milestone, Dell EMC will submit the associated tangible Deliverables, if any, to Customer accompanied by an Acceptance Form in the form set forth in Appendix A to this SOW. Upon such submission, Customer will review, evaluate and/or test, as the case may be, the applicable Deliverable(s) within five (5) business days (the “Acceptance Period”) to determine whether or not each Deliverable(s) satisfies the acceptance criteria for the particular Deliverable in all material respects. If the Deliverable satisfies its acceptance criteria in all material respects, Customer will furnish a written acceptance confirmation to Dell EMC via the Acceptance Form prior to the end of the Acceptance Period. For a Deliverable that is not accepted due to a non-conformity or defect, Customer will indicate the detailed reasons for such rejection on the Acceptance Form and return the Acceptance Form together with the associated tangible rejected Deliverables, if any, to Dell EMC (a “Rejection Notice”) within the Acceptance Period. Upon receipt of a Rejection Notice, Dell EMC will promptly correct any defects or non-conformities to the extent required so that each Deliverable satisfies the requirements of this SOW and its acceptance criteria in all material respects. Thereafter, Dell EMC will resubmit a modified Deliverable to Customer, accompanied by the Acceptance Form and the process set forth above will be repeated. However, Customer will limit its review, evaluation and/or test of each resubmitted Deliverable to determining whether or not Dell EMC has corrected the defects or non-conformities identified in the Rejection Notice and to the effects or impact which Dell EMC’s corrections or modifications have on other Deliverables or other portions of the same Deliverable. If Customer fails to provide Dell EMC with the above described Rejection Notice prior to the end of the applicable Acceptance Period, then the corresponding Deliverable(s) are deemed accepted.

5. Change ManagementTo ensure the success of this engagement, it is critical that Customer and Dell EMC have a clear understanding of engagement expectations. The parties will utilize the approach outlined below for managing the scope of the engagement.

Customer or Dell EMC may propose changes to the Services under this SOW, including Deliverables, scope or any other aspect of the engagement. Changes may be appropriate based upon actual experience or as Customer better understands or redefines its requirements. In addition, changes may be necessary if Customer does not comply with any of its responsibilities or other obligations under this SOW or in the event of any deviation from any assumption, constraint, dependency or engagement scope specification contained in this SOW. The change management process for this engagement consists of the following:

Change Initiation – All proposed changes will be forwarded to, or originated by, the Dell EMC project manager and documented. A copy of the proposed change request will be forwarded to the Customer project manager. Change requests will be documented using the Change Request form attached to this SOW as Appendix B.

Change Validation – Only when the change request is clearly understood can the engagement team evaluate the impact of the change and determine whether the change can be accommodated. Therefore, the proposed change will be examined and discussed with the Customer contact identified in this SOW.

Change Analysis and Impact Analysis – Dell EMC will prepare a change analysis and impact analysis using the Change Request form. The impact analysis includes a cost and schedule impact to the engagement, if applicable. This will be reviewed with Customer for approval. If Customer wishes to approve the change, it must provide its approval within five (5) business days of submission of the Change Request form.

Change Implementation – If approved, the change will be noted as “Approved” and will be incorporated into the schedule and managed for progress. If the change is not approved, the change will be noted as “Rejected” and Dell EMC will continue to perform without regard to the proposed change (to the extent practically possible).

Possible outcomes of a change request, as may be documented in the change analysis and/or impact analysis, include the following:

1. Can be accommodated within engagement resources and timelines;



2. Can be accommodated but will require an extension of the schedule;

3. Can be accommodated within the current schedule, but additional resources or budget will be required;

4. Can be accommodated but additional resources or budget and an extension of the schedule will be required;

5. Cannot be accommodated without a significant change to the engagement or it is not technically, economically or otherwise feasible.

Dell EMC has no obligation with respect to any change requested by Customer until an appropriate written change order or other amendment to this SOW is approved and signed by Customer and Dell EMC.

6. City of Phoenix Resource PlanThe following table lists the City of Phoenix individuals by functional title and the roles those individuals will perform in the Migration project.

CITY OF PHOENIX STAFFING TABLE

TITLE Role

Executive Sponsor Provide executive level sponsorship and oversight. Individual needs to be in a position to make decisions on escalated issues as needed. Needs to participate on Steering Committee. Provides input to analysis and strategy development.

Program Sponsor Provide program level sponsorship and oversight. Individual needs to be in a position to make decisions on escalated issues as required by the program manager. Provides input to discovery, analysis, and strategy development.

City of Phoenix Project Manager

Interfaces on a daily basis with the Dell EMC project team. Provides daily project management. Escalates issues as necessary.

Provides direction on scope discussions Provide issue resolution and escalation Coordinate and direct COP resources efforts Review and accepts deliverables Process milestones completion and project acceptance Participate in progress status meetings Confirms project requirements are completed satisfactorily Participate in daily and weekly meetings with Dell EMC PM Identify, manage, close, and escalate issues to Dell EMC PM Participate in impact assessments of change requests as needed Serves as Dell EMC point of contact for project change requests

City of Phoenix Subject Manager Expert(s)

Provide input to the discovery and analysis as required, migration planning, and execution planning of the COP application environment. Specific tasks include:

Provide applicable mapping and backup Information Validate applicable Data from Validation Reports Provide From/To Data Provides scripting changes if applicable Provide Start Up and Shutdown Procedures



CITY OF PHOENIX STAFFING TABLE

Provide Test Procedures Attend Table Top Exercises Attend Go/No-go Meeting Execute Migration Plan

Data Center Manager Assist with discovery and analysis, planning, and execution planning of applicable data center components involved in the Migration including any required remediation activities necessary to support the migrations. Specific tasks include:

Informs Dell EMC & the COP project manager status of target center Provide Data Center From/To Data (server rack, u-location) Attend Table Top Exercises Attend Go/No-go Meeting Execute Storage and Backup Migration Plan

Change Management Manger

Provide all application and infrastructure changes to the Migration Database Team Lead through the normal COP distribution cycle.

An estimate of time requirements to support the project for City of Phoenix roles is shown below:

ROLEDISCOVERY &

ANALYSISPLANNING EXECUTION

Sponsor 2 hours /wk 2 hours /wk 2 hours /wk

Project Manager 40 hours /wk 40 hours /wk 40 hours /wk

Business Owners 1 hours /wk 1 hours /wk 1 hours /wk

Application Owners 4-8 hours /wk 4-8 hours /wk 4-8 hours /wk

Infrastructure Owners 4-8 hours /wk 4-8 hours /wk 4-8 hours /wk

Change Management 4-8 hours /wk 4-8 hours /wk 4-8 hours /wk

Network SME 4 hours /wk 6 hours /wk 8 hours /wk

Windows/Unix SME 10-20 hours /wk 20-30 hours /wk 20-30 hours /wk

Storage SME 10-20 hours /wk 20-30 hours /wk 20-30 hours /wk

Application SME 10-20 hours /wk 10 hours /wk 10 hours /wk



Dell EMC will be able to confirm staff upon signing of this SOW. While every effort is made to staff projects immediately, Dell EMC may need up to four weeks to staff a project. This is to confirm the best combination of skills is aligned to the project based on the COP environment. In all cases, Dell EMC will begin the project mobilization process immediately to ensure a timely and quality kickoff.

Dell EMC reserves the right to supplement or substitute resources when, in Dell EMC’s business judgment, work assignments, tasks or engagement activities will benefit from such expertise or as necessary due to training, vacation, illness, termination of employment or other reason.

The planned maximum hours for the Services identified in this SOW is 40 hours/week. Dell EMC personnel will not work in excess of 40 hours in a workweek without joint agreement between Dell EMC and Customer. Days or hours outside of this schedule can be accommodated, but Customer must request this in writing at least ten (10) days prior to the actual need. Additional charges at Dell EMC’s overtime rate may be incurred if this work day(s) is not offset by a day off during the normal work week.

7. City of Phoenix ResponsibilitiesThe City of Phoenix’s timely provision to Dell EMC of office accommodations, facilities, equipment, assistance, cooperation, complete and accurate information and data from COP officers, agents, and employees, and suitably configured computer products (collectively, “cooperation”) is essential to the performance of any Services set forth in this SOW. Customer acknowledges that Dell EMC’s ability to perform the Services and any financial estimate or schedule or milestone commitments related thereto depends upon COP and Customer cooperation on a timely basis, the additional engagement scope specifications stated in the Additional Engagement Scope Specifications section below and Customer and/or COP fulfillment of any additional responsibilities described in this SOW.

7.1. GENERAL CITY OF PHOENIX RESPONSIBILITIES Providing onboarding support Provide a Single Point of Contact (SPOC) for all COP project activities (i.e. coordination and scheduling support) Provide weekly access to the COP project sponsor for the Dell EMC Management team For on-site events/meetings/collaborations, the COP will provide sufficient private meeting facilities or the

access/ability for Dell EMC to be able to schedule Provide a war room facility for migration events

7.2. DISCOVERY AND ANALYSIS RESPONSIBILITIES COP will provide current and accurate data supporting the Dell EMC deliverables in synchronization with the overall

project timeline COP will provide names and assign Application IT Business Owners to project one week prior to project kickoff COP will name and assign primary point(s) of contact to the project one week prior to project kickoff COP will review and approve Data Collection Plan in writing before data collection begins COP infrastructure owners and application SMEs will work with Dell EMC Lead to normalize data in synchronization

with the timeline and deliverables. COP will return Data collection workbooks in the agreed upon timeframe in the defined format COP will provide data extract from pre-define all automated discovery tools (ADDM) to be used in the Discovery &

Analysis process. The COP Application and Infrastructure owners will meet validation schedule

Analyze and Bundle Responsibilities

COP SME’s will review and approve results of the bundling criteria and migration event strategy options

7.3. INFRASTRUCTURE READINESS RESPONSIBILITIES COP will assign a lead technical resource to act as a single technical point-of-contact between COP and EMC as

necessary for the duration of the IaaS workstream.



COP will provide comments, revisions, and questions for all draft IaaS deliverables submitted to them within three (3) business days of receiving.

7.4. MIGRATION PLANNING RESPONSIBILITIES Dell EMC is responsible to facilitate the Discovery and Analysis, Detailed Migration Planning and Execution phases.

COP is accountable to validate application and infrastructure data, provide detailed Migration tasks processes, testing procedures, infrastructure mapping and to perform Migration tasks procedures.

The COP Project Manager will assist Dell EMC with aligning necessary resources to support Project Work and Resource Plan that will be validated by COP in accordance with the project schedule.

COP has a defined Change Control and Release Management process for their application/infrastructure environment.

COP is responsible to manage all third party vendors to meet defined COP project schedules.

Test and Contingency Plan Responsibilities

The COP Project Manager and SME’s are available per the Project Work and Resource Plan and are validated by the COP Project Manager in accordance with the project schedule.

COP will define, document and test the recovery approach for subordinate infrastructure systems COP will confirm test plans include stipulations for pre-testing test procedures are accurate one week prior to

migration COP is responsible for any DR certification activities and documentation that is required as a result of migration event

From/To Responsibilities

COP will assign available resources to support the Project Work and Resource Plan Dell EMC assumes that applications will not require changes to hardcoded IP addresses and will move like for like

7.5. MIGRATION EXECUTION RESPONSIBILITIESPre-Migration Execution Responsibilities

COP will assist Dell EMC to ensure all target are installed, configured and operational 4 weeks prior to the first migration event.

COP is responsible for Target Data Center infrastructure procurement, build, certification, and operational readiness is in place to support this SOW. Dell EMC is implementing infrastructure under separate, related quote.

COP Project Manager will assist Dell EMC to ensure resources availability to perform Infrastructure design; installation, configuration, and testing.

COP Project Manager will assist Dell EMC to ensure resources, including Database Administrators are available to perform any database design; installation, configuration and testing..

COP is responsible to provide sufficient resources to assist Dell EMC to ensure that data migration design, build, test will allow for the transfer of data from source to target Data Centers during migration

COP resources will assist to support Project Work and Resource Plan and all meeting schedules will be attended by the Application and Infrastructure SMEs.

COP and Dell EMC are responsible for pre-migration communications to users. Communications shall be provided on no less than a weekly basis during the term of the SOW.

COP is responsible for all customized scripting including updates required from changes to the client’s operating environments

Migration Execution Responsibilities

COP will determine and provide dedicated and adequate network bandwidth to handle migration and data replication workload

COP is responsible for all Domain Name Service (DNS) changes COP authorizes all outages through the Change Control process prior to the migration outage and communicated in

advance to the Dell EMC Project Management Office



Migration Rate: COP is responsible for providing the target number of fully-approved and scheduled workloads for migration on a daily basis that shall be equal to the prorated target weekly migration rate.

Completion of Migrations: Migration of each workload shall be considered complete based upon the agreed successful or unsuccessful migrations criteria.

Scheduling of Services: Core Migration Services may be provided during business or non-business hours based on a mutually agreed schedule of services. If non-business hours will be used COP and Dell EMC will agree upon in writing upon the execution of this SOW and will be subject to the terms and conditions thereof. Scheduling of services will be completed at least two (2) calendar weeks prior to the service delivery date(s).

Access for Remote Services: Services related to offsite migrations will be delivered remotely via network access to COP infrastructure. COP shall provide appropriate access and credentials so as to allow the remote migration teams to successfully gather data and complete migrations. COP may be billed for failed migrations due to access restrictions. Dell EMC employees will meet COP security standards for access to COP systems.

COP Point of Contact Authority: COP Project Manager will have the authority to make project decisions in all matters related to this SOW and provide a single consolidated response to any decision request.

COP Participation: COP personnel will actively participate in this engagement and if these participants are unable to attend a scheduled meeting, the COP Project Manager will become the final authority on all items of discussion.

Hardware and Software Delays: COP shall be responsible for procurement and availability of all required hardware and software in accordance with the project schedule. This SOW assumes no breaks in the project schedule due to delays.

Data Accuracy: COP will be responsible for, and assumes the risk of any problems resulting from the content of any data, materials and information supplied.

Evaluate and confirm consolidation criteria presented by COP and assign appropriate resources to investigate consolidation candidates identified by the COP.

COP will participate in working sessions to identify initial Migration source hosts and target servers COP will provide planned server, storage, network infrastructure details required for the migration. Dell EMC will

provide information for newly deployed Dell EMC equipment. COP to provide current infrastructure and application test plans COP to provide system and application shutdown and restart procedures A suitable SAN to SAN replication or copy for migration of virtualized servers is available. Dell EMC will execute V2V

migration of in-scope VMs. COP to review and approve fall-back and contingency plans for each host COP to provide infrastructure and application testing procedures for each host Identify and attempt to remediate any hard coded IP Addresses in applications on in-scope servers Implementation and/or modification of target infrastructure necessary to facilitate the target number of server

migrations Execute COP change control process for each bundle and freeze infrastructure and application changes for a specific

period (to be agreed upon during project start-up) before and after the migration date COP to assure primary and backup resources are assigned to each migration event COP to perform full backup of all hosts in each migration group, subject to COP exceptions and acceptance Securing go-decisions for weekly migration candidates based on the established schedule COP to execute assigned tasks in DTM COP to execute infrastructure and application test procedures Sign off on server owner acceptance of completed Migration’s will be in DTM upon completion of migration tasks. COP shall be responsible for obtaining the network and building access for Dell EMC Resources in a timely manner.

To accommodate scheduling and the ability to handle variations in workload scheduling, Dell EMC may present a primary and secondary list of resources who may be utilized at the discretion of the Technical Lead.

COP will be responsible for procuring all hardware and software required for this project including any conversion tools that may be required

Effort and costs associated with applications that require an initial migration to a test region to allow for extended validation (such as application, compatibility, scalability or performance testing) followed by a secondary final migration are not included.

Virtual Migration Tools Responsibilities



COP is responsible for properly licensing for such tools that require licensing, for use by Dell EMC. Dell EMC will use migration tools to perform V2V conversions on this project such as vMotion, SvMotion, Converter.

Facilitate installation of VMware products and tools to assure physical host is suitable for virtualization Identify the COP responsible parties for development of infrastructure and application test plans and assign them to

support the Virtualization Project The target VMware virtual infrastructure is available, ready, configured according to VMware best practices, and the

workload is suitable for migration (Target converged infrastructure implemented by Dell EMC under separate quote). Communicate with application vendors to determine VMware affinity

Post Migration Execution Responsibilities

COP will assign COP resources to support Project Work and Resource Plan and ensures attendance in post migration scheduled meetings

8. Additional Engagement Scope SpecificationsThe Services (including Deliverables) are subject to the following:

1. Costs for hardware and software are not included in Dell EMC’s fees. Our estimate is for labor only.

2. Access to COP personnel will be identified.

3. Responsibility for staffing the engagement is owned by Dell EMC.

4. Dell EMC will not be responsible for COP delays and the consequent costs incurred. Any delay caused by any third party vendor providing services or products to COP that impact the Services, will be considered COP’s responsibility and an excusable delay to the extent the Services are impeded or delayed.

5. COP is responsible for the performance of its employees and agents, including any contribution they make to the Services (including Deliverables), and for the accuracy and completeness of all data, information and materials provided to Dell EMC. Dell EMC is not providing any warranty regarding, and is not liable for, COP software, documentation, equipment, tools or other products or materials. Dell EMC’s performance is dependent upon timely decisions and approvals of COP in connection with the Services and Dell EMC is entitled to rely on all decisions and approvals of COP.

6. The Services and resulting Deliverables may include advice and recommendations, but COP agrees that all decisions in connection with the implementation of such advice and recommendations will be the responsibility of, and made by, COP. Dell EMC is not providing legal or regulatory advice.

7. Dell EMC is not providing any third party software, tools, equipment or other third party products or materials except for DTM which will be deactivated at the end of the project; including, without limitation, Dell EMC Select Products and Brokerage Products (“Third Party Products”) to COP. COP is solely responsible for the negotiation of an applicable agreement with the applicable third party from whom COP wishes to license or acquire Third Party Products, the terms of which, including without limitation, the license, warranty, indemnity, maintenance and support terms, shall govern such license or acquisition. Dell EMC is not providing any warranty regarding, and is not liable for, any Third Party Products. Third Party Products are not supported or maintained by Dell EMC and COP must contact the applicable third party manufacturer or supplier directly for support and maintenance services.

8. Dell EMC is not responsible for any alteration or other modification made to a Deliverable by COP or any third party (excluding any permitted subcontractors working for Dell EMC) or for any work performed by COP or its contractors in connection with this engagement.

9. COP will scan all Deliverables and the media on which they are delivered with a current version of an anti-virus application in an effort to detect and eliminate any virus or other software routine, code, device, mechanism or similar item that could disrupt, disable, harm or otherwise impede any program, hardware or data or otherwise interfere with



operations. COP will also maintain a current version of an anti-virus application continuously running on any system to which Dell EMC is given access.

10. Dell EMC may rely upon any standard operating procedures or practices of COP and any direction or regulatory or other guidance provided by COP.

11. COP is responsible for the identification and interpretation of, and ensuring compliance with, any laws, statutes, rules, regulations and standards applicable to its or its affiliates’ business or operations.

12. Any configuration or modification made by Dell EMC to any third party software or materials provided by COP or work product incorporating such items will be subject to the ownership and other rights agreed to by COP with the applicable third party.

13. The purchase and/or license of any Dell EMC product will be governed by the terms of a separate license or purchase agreement between the parties. Dell EMC products cannot be licensed or purchased under this SOW.

9. Location The Services shall be performed primarily at the City of Phoenix facility (work site) located at:

Phoenix, Arizona

However, Dell EMC shall have the option of performing appropriate portions such as planning and documentation at anDell EMC-selected location.

Customer acknowledges and agrees that identified portions of the Services may be performed by Dell EMC at an Dell EMC-selected off-shore location.

The billing address for the Customer is as follows:

Partner address

In the event that there is a discrepancy between the billing address set forth herein for the Customer and the address set forth on the applicable purchase order from the Customer, the address set forth on the Customer’s purchase order will govern for billing and payment purposes

10. Engagement Contacts

The primary contacts for each party are identified below and may be changed only by written notice to the other party.

DELL EMC CONTACT CUSTOMER CONTACT

NAME Balaji Ramani <Customer Contact Name>

TITLE Client Solutions Director <Customer Contact Title>

PHONE NUMBER (732) 996-1277 <Customer Phone Number>

E-MAIL ADDRESS [email protected] <Customer Email Address>



11. Fees and InvoicingThe total fees for the services in this engagement are $XX, inclusive of out-of-pocket expenses. Dell EMC will charge its fees for this engagement on a Fixed Price basis. Dell EMC will invoice Customer in accordance with the following schedule and Customer will pay such amounts pursuant to the Agreement or, if not specified in the Agreement, net thirty (30) days from invoice date

MILESTONE/EVENT PERCENTAGE FEES

1. Signature of Statement of Work 5% $

2. Approved Data Collection Plan 5% $

3. Approved Data Collection Plan 4% $

4. Completed Data Collection Workshops 5% $

5. Completed Data Collection 6% $

6. Completed Data Validation 6% $

7. Approved Data Bundling Criteria & Migration Options 7% $

8. IaaS Design Complete 8% $

9. IaaS Build and Test Complete 5% $

10. IaaS Operational Hand-off Complete 6% $

11. Approved Migration Options Report 4% $

12. Completed Migration Event #1 3% $







19. PMO Transition Month 1 2% $

20. Completion of Dell EMC-led Migrations 10% $

21. DTM Support Month 1 1% $






TOTAL 100% $

11.1. ESTIMATE REVISIONSShould Dell EMC’s fee estimate change because of a deviation in any assumption, engagement dependency or scope specification or other provision of this SOW for which a change order as described in the Change Management section of



this SOW does not already apply, Dell EMC will notify Customer and discuss any next steps. Agreed-upon changes may result in a change request pursuant to the Change Management section of this SOW.

11.2. EXPENSES AND OTHER CHARGESTravel and related expenses incurred by Dell EMC in its performance of the Services are included in the stated fees.



12. Acceptance of Statement of Work Dell EMC looks forward to the opportunity to work with Customer. Please review this SOW for accuracy. If the terms are acceptable, please sign and return via e-mail to the Dell EMC contact listed above. This SOW may be executed in any number of counterpart copies, each of which will be deemed an original, but which taken together will constitute a single instrument. The parties expressly authorize the use of facsimile counterparts or delivery by other electronic device as a valid method of execution; however, the parties agree to cooperate in good faith to provide each other with a fully executed original of this SOW within five (5) calendar days of any counterpart execution. This SOW together with the Agreement (i) is the complete and exclusive agreement between Dell EMC and Customer with regard to its subject matter, and supersedes all prior oral or written proposals, agreements, representations and other communications between the parties with respect to the Services described in this SOW; and (ii) will apply in lieu of any different, conflicting or additional terms and conditions which may appear on any order or other document submitted by either party.

IN WITNESS WHEREOF, the parties hereto have caused this SOW to be executed by their duly authorized representatives as of the Effective Date set forth on the first page of this SOW.

ACCEPTANCE OF STATEMENT OF WORK – CITY OF PHOENIX IT TRANSFORMATION

FOR EMC CORPORATION FOR CUSTOMER

Signature

Printed Name

Title

Date

Signature

Printed Name

Title

Date



APPENDIX A MILESTONE ACCEPTANCE FORM

<PHASE/MILESTONE/DELIVERABLE> ACCEPTANCE FORM

This Acceptance Form is official notice that Dell EMC believes that the Milestone described below has been successfully completed because Dell EMC’s has met all of the applicable acceptance criteria for such Milestone. By countersigning and returning this Form, Customer is confirming Dell EMC’s successful completion of the Milestone and fulfillment of the applicable acceptance criteria.

If Customer believes that the acceptance criteria for this Milestone have not been met, Customer shall indicate on this Form which acceptance criteria Customer believes have not been successfully met and return this Form as a Rejection Notice to Dell EMC prior to expiration of the Acceptance Period stated in the SOW. Thereafter, the parties shall follow the resolution process set forth in the SOW.

If Customer does not respond in writing within the Acceptance Period, the Services for this Milestone will be deemed accepted.

If the entire price for the Services was pre-paid in full, no invoice will be generated on the basis of this Form.

<PHASE/MILESTONE/DELIVERABLE>

CUSTOMER <Customer Name>

ENGAGEMENT NAME: <Engagement Name>

SOW NUMBER: <SOW Number>

DESCRIPTION: <Customer Name>

DATE OF COMPLETED: <Engagement Name>

DELIVERABLES/COMMENTS:

FOR EMC CORPORATION <CUSTOMER NAME>

Signature

Printed Name

Title

Date

Signature

Printed Name

Title

Date



APPENDIX B CHANGE REQUEST FORM

CHANGE REQUEST FORM

ENGAGEMENT: <name of SOW> ORIGINAL SOW DATE: <date>

TITLE: <descriptive title of change request>

REQUESTOR: <your name> DATE: <date>

REFERENCE SO # CR NUMBER#

DESCRIPTION OF PROPOSED CHANGE:<brief summary of change>

CATEGORY OF CHANGE:YES NO

SCOPE

COST

SCHEDULE

OTHER

CHANGE ANALYSISImpact if Change is NOT Approved:

<brief statement>

DETAILED DESCRIPTION OF REQUIRED CHANGE:<Statement of CR details>

PROPOSED WORK EFFORT: EFFORT (DAYS)

<list of associated work tasks with associated estimate>

TOTAL:



IMPACT ANALYSIS DELIVERABLESDESCRIPTION CHANGE REQUIRED

COST

RESOURCE# HOURS (ESTIMATED)

$ COST/HOUR EST. TOTAL

ESTIMATED TOTAL <T&M/FIXED FEE> COST (PAYABLE UPON INVOICE) $0.00

TIMETABLEENGAGEMENT PHASE EST. COMPLETION DATE



APPROVALS

For <Customer Name> Date

For EMC Corporation Date

PROJECT MANAGER USEYES NO

ENGAGEMENT SCHEDULE UPDATED:

ENGAGEMENT PLAN UPDATED:

ENGAGEMENT STATUS REPORT (INTERNAL & EXTERNAL) UPDATED

ENGAGEMENT SCHEDULE UPDATED:



APPENDIX C PROJECT ORGANIZATION CHARTDell EMC’s anticipated project organization. The Steering Committee is formed to provide executive support and oversight for the duration of the project and consists of the Customer and Dell EMC senior management.

During the project mobilization, the Dell EMC project manager will confirm Dell EMC and the Customer’s roles and responsibilities, add names to this chart, and confirm with all parties.



APPENDIX D TERMS AND DEFINITION Application - Any entity identified which may require a unique shut-down/start-up procedure, configuration change

procedure, migration tracking (either physical asset, data transfer, or both), test plan, and/or contingency plan as a result of migration. In addition, an application must be able to run stand-alone without other components required for its operation. Examples of ‘applications’ under this definition include:• Off-the-shelf or custom written code implemented to support a business function• Infrastructure service that provides functionality to support users and other applications (eg: Directory Services,

DNS, Proxy Services, Mail Services)• Stand-alone management device or specialized hardware (eg: Proxy, Firewall, Load Balancing Device)

BC – Business Continuity capability of the organization to continue delivery of products or services at acceptable predefined levels following a disruptive incident.

Bundle – Is the result of manually adjusting/combining dependency groups based on application and business requirements to finalize a bundle configuration

DBA – Data Base Administrator D&A – Discovery and Analysis DC – Data Center Dependency – The relationship between assets. Such as applications can be dependent on other application

interactions, or the server it runs on. Dependency Group – auto generated by DTM and is the initial Bundle designator in DTM, and is a defined group of

applications and servers that must move together or set of devices, Retired, Not Moving, etc. From/To – Document outlining the pre-migration state of the infrastructure/storage/network and the corresponding post-migration state (infrastructure mapping).

DNS – Domain Name Server HBH – Hour-by-hour migration implementation plan HBA - Host Bus Adapter - A circuit board and/or integrated circuit adapter that provides input/output (I/O) processing

and physical connectivity between a host system, or server, and a storage and/or network device. Infrastructure - All physical equipment to include servers, mainframes, attached devices, storage, and network

equipment Instance – Individual occurrence of an Operating System in the client’s environment PDM – Project Delivery Manager – resource responsible for an EMC geographical region to ensure successful

delivery of services engagements. PMO – Program Management Office RPO – Recovery Point Objective – The point in time prior to an outage to which systems and/or data must be restored

to. RTO - Recovery Time Objective – The time needed to recover from a disaster or, simply put, how long the application

can afford to be down. Migration Lead - EMC Consultant assigned the responsibility documenting the migration plans for a specific Move

Event. Migration Event– a single migration that includes bundle(s) and associated infrastructure which defines a migration

move event P2V – Physical to Virtual - Migrating a physical host or server to a virtual host or server. Operating System (OS) Instance – A single copy of a running program either physical or virtual within a Customer’s

environment SME- Subject Matter Expert - Person assigned the responsibility to represent their area of technical expertise. SOW – Statement of Work Software as a Service (SaaS) - s a software licensing and delivery model in which software is licensed on a

subscription basis and is centrally hosted



Table Top Review – Review the migration playbook Dell Transformation Manager (DTM) – End-to-end Integrated Database Software for Data Center Migrations,

Consolidations, Transformation WWN - World Wide Name - A unique identifier that is assigned to a manufacturer by the Institute of Electrical and

Electronic Engineers (IEEE) and hard-coded into a Fibre Channel (FC) device.


ITS 18-202 - Attachment D Web viewMS Word. IaaS Configuration Workbook. ... SvMotion, Converter....

Documents

Transcript of ITS 18-202 - Attachment D Web viewMS Word. IaaS Configuration Workbook. ... SvMotion, Converter....