ITS 18-202 - Attachment F - Web viewA current state SQL server discovery assessment will provide the foundation for the SQL Server ... MS Excel and MS Word. ... During the project

Dell EMC

Prepared for:

Partner200 W. Washington StreetPhoenix, AZ 85003

Prepared by:

Dell EMC4250 N. Drinkwater BlvdSuite 200Scottsdale, AZ 85251

Effective Date: October 17, 2107 Quote Number: 6001570698

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

Statement of Work for

City of Phoenix IT TransformationSQL Server – COP Police and Fire

Dell EMC Statement of Work for City of City of Phoenix IT Transformation – SQL Server COP Police and Fire

TABLE OF CONTENTS

1. INTRODUCTION.............................................................................................................32. ENGAGEMENT OBJECTIVE.........................................................................................33. ENGAGEMENT SCOPE AND APPROACH...................................................................3

3.1. SERVICES...............................................................................................................33.2. ENGAGEMENT PHASES AND DELIVERABLES....................................................4

3.2.1. Phase 0: Project Management Phase..........................................................................43.2.2. Phase 3: SQL re-architecture Phase............................................................................53.2.3. Project Deliverables.....................................................................................................103.2.4. Microsoft SQL Re-architecture Assumptions...............................................................10

4. COMPLETION AND ACCEPTANCE............................................................................125. CHANGE MANAGEMENT............................................................................................126. CITY OF PHOENIX RESOURCE PLAN.......................................................................137. CITY OF PHOENIX RESPONSIBILITIES.....................................................................15

7.1. GENERAL CITY OF PHOENIX RESPONSIBILITIES............................................167.2. DISCOVERY AND ANALYSIS RESPONSIBILITIES.............................................167.3. INFRASTRUCTURE READINESS RESPONSIBILITIES.......................................167.4. MIGRATION PLANNING RESPONSIBILITIES......................................................167.5. MIGRATION EXECUTION RESPONSIBILITIES...................................................17

8. ADDITIONAL ENGAGEMENT SCOPE SPECIFICATIONS.........................................189. LOCATION................................................................................................................... 1910. ENGAGEMENT CONTACTS........................................................................................2011. FEES AND INVOICING................................................................................................20

11.1. ESTIMATE REVISIONS......................................................................................2111.2. EXPENSES AND OTHER CHARGES................................................................21

12. ACCEPTANCE OF STATEMENT OF WORK..............................................................22APPENDIX A MILESTONE ACCEPTANCE FORM...............................................................23APPENDIX B CHANGE REQUEST FORM............................................................................24APPENDIX C PROJECT ORGANIZATION CHART..............................................................27APPENDIX D TERMS AND DEFINITION..............................................................................28

© Copyright 2017 Dell EMC 2 of 29


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:

SQL Server consolidation and migration for the City of Phoenix Police and Fire

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. 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 SQL Server migration includes:Up to 7 migration events Police and Fire SQL: Up to 16 production and 23 non-production Microsoft SQL instances to be migrated

o 293 production databaseso 230 non-production databases

Transition Manager (TM) or other best-in-class migration information management tool and database will be deployed remotely by Software as a Service (SaaS).

The parties anticipate the start date for this engagement will be October 2, 2017 and estimate completion of this engagement by June 29 , 2018.

3.1.SERVICESDell EMC will perform the following Services for Partner on behalf of the City of Phoenix (“COP”) under this SOW:

SQL Re-architecture Phase – Create the target SQL infrastructure in the target location

a) Assessment and Planning

b) Design

c) Construction – Target Environment

d) Migration

The anticipated project schedule (to be refined and finalized during the first two weeks of the engagement) is shown below. At this time it is assumed that Public Safety will have the highest migration priority.


Robert F. Sonders, 10/17/17,

To update


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 Transition

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 3: SQL RE-ARCHITECTURE PHASEThe Migration for Microsoft SQL Server re-architecture and migration phase is designed to provide the City of Phoenix with the information they need about their environment, create a robust migration plan to mitigate the impact on City services, and test, validate, and execute the plan. The first part of this work stream—the assessment and planning phase—leverages our application-centric approach to provide the knowledge necessary to prepare for migration. The second part delivers the final design and execution of the plan generated in the earlier assessment and planning activities. The SQL re-architecture approach is highlighted below:

Discovery SQL Requirements and Constraints: Review the existing source and target environments to determine requirements for migration as well as constraints or dependencies that may need to be addressed prior to the migration execution.

Application teams database mappings: The client application owners will be required to participate in multiple discussions to align the proper application to database level mapping and understanding. Interview meetings and electronic files will be requirements for participation.

Infrastructure, Database, and Application Assessment: Using automated tools, we gather and analyze information on existing database servers and corresponding database instances. We identify issues, risks, and mitigation strategies. Finally, we create an inventory of applications dependencies on the data infrastructure and rate the applications for migration/upgrade criticality, complexity, business impact, licensing, and support impact. The inventory also includes application-to-database mapping and potential application configuration issues.

Future-State Database Information Architecture: Leveraging information from the current-state assessment and future-state requirements, we design the new architecture for SQL Infrastructure, including high-availability for the production environment. If required, the additional SQL Server ancillary services are also assessed: SQL Server Integration Services (SSIS), SQL Server Reporting Services (SSRS), and SQL Server Analysis Services (SSAS).

Develop Migration Solution: Design a migration solution for City of Phoenix physical and virtual SQL Servers. Test the migration solution in proof of concept lab in order to minimize risk to the source and target environments during the consolidation. In instances where the SQL Server version is no longer supported by Microsoft, analysis and signoff regarding a like for like migration will be documented.o To the best of the ability, a gold standard will be built and utilized for SQL Server. This version may or

may not be a possibility with all applications requiring a SQL database. Some environments may remain physical with regards to the application specific requirements.

o Where there are application restriction that will require a need to remain on SQL 2005, etc. Applications that will not work with the Gold Standard SQL image version will need a separate VM. High Availability will be provided by VMware technologies.

Develop Reliable Migration Procedures: Document, test, and execute a repeatable migration process in the production environment that will minimize risk to user productivity during the consolidation

Detailed Infrastructure Design, Final Migration & Consolidation Plan: A detailed design and sizing of the Microsoft SQL Server environment including integration and related infrastructure where applicable.

Comprehensive Test Plan and SQL Server Infrastructure Build-out: Deployment of a modern best practice SQL infrastructure including validation of processes, tools, and procedures. Build out up to 12 Production and 7 Non-Production SQL server environments. High Availability and Disaster Recovery SQL AlwaysON or SQL Clusters that target the AD domain based on the future state agreed upon solution. Restore SQL databases to newly built servers. Hand over the SQL build to City of Phoenix applications team for testing.



Migration of Microsoft SQL Databases: Once the SQL infrastructure build is fully tested and migration process is established, SQL components will be piloted and migrated. The existing scripts, SSIS and SSRS (SSAS is out of scope) components will be frozen from further development during the migration waves. The freeze will allow for any connection string remediation to be completed pre-migration, thus being ready and available for execution post migration. The migration will include a go-live event consisting of restoring of most recent SQL databases and testing of data access within single City of Phoenix target domains.

SQL Discovery

As part of the overall work stream, a dedicated team will focus on the database specific servers and they will conduct an initial discovery and assessment of all SQL Server infrastructure. Dell EMC will expect the City of Phoenix will provide SQL server database instances and versions, nodes and configuration, as well as HA and DR in use. A current state SQL server discovery assessment will provide the foundation for the SQL Server migration path roadmap.

The joint Dell EMC/City of Phoenix project team will identify the relevant business and technical requirements for an SQL Server migration and then perform an environment review. The review will consist of the Dell EMC team conducting meetings and using a tool based discovery to collect essential data about the City of Phoenix SQL environments to be migrated. Dell EMC believes it is important to verify the data to ensure it is accurate and that all critical components have been addressed. This discussions and review will aid in identifying hidden requirements, unknown risks and specific constraints that must be addressed during the architecture and design phase.

The core set of SQL Server meeting topics will include:

Define and analyze current SQL Server system inventory (Development, Test, Load, Stage, Production) Understand timeline and dependencies Conduct SQL Server migration requirements gathering Conduct SQL SME interviews Understand business processes and model surfaced from SME interviews Document business and technical requirements Inventory and document SQL nodes and instances needed to be migrated Inventory and document SQL Server pre-requisites Create Current State Database Assessment Define inventory of database servers and databases Document data and storage specific requirements Determine high-level candidate architecture for SQL infrastructure

In general, EMC will conduct twelve (12) SQL discovery sessions of which each session is limited to one and one-half hours in duration, with multiple sessions in a single day. Because so much of the focus is on discovery of the City of Phoenix environment it is critical that key technical and business staff for the legacy environment be dedicated to this effort and free from distractions. Based on the results of each meeting it is expected that a limited number of additional follow-up meetings may be required to introduce additional information or gain consensus, Dell EMC has planned for six (6) follow-up meetings.

Note: If any design or operational documents from the current environment exist then they should be provided to the Dell EMC team prior to these sessions. This maximizes the relevance of the sessions and the accuracy of the data exchanged.

The Dell EMC SQL SME will require access to the MSFT TAM for full COP SQL Server licensing disclosure.

COP will acquire and make available, from Microsoft or licensing vendor, the appropriate number of SQL Server licenses and versions to account for the new SQL Server target environment.

Dell EMC will work closely with the TAM to ensure all SQL Server required licenses by registered version, are correctly distributed and accounted for, within the target virtual environment.



The SQL SME will discover all SQL Server licenses existing in the physical environment. Potentially also working with the TAM for specifics. Armed with these SQL licensing details, the SQL SME will align the final target definition SQL architecture and confirm with the TAM upon completion. If any gaps exist, COP, the MSFT TAM and the SQL SME will work in concert to define any additional optimizations that are required for SQL licensing compliance.

Once these sessions are complete, Dell EMC staff will conduct further manual and tool-based discovery. This process requires authorization to access the client environment which can either be granted through a temporary username/password given to Dell EMC or through direct execution by City of Phoenix administrator.

After the discovery data collection is complete for both source and target environments, EMC will document and review issues and gaps identified with existing infrastructure found during discovery needing remediation to support the migration. All results from the sessions and the discovery processes will be compiled into the SQL Discovery Phase Deliverables. City of Phoenix will have 3 days to review these deliverables and provide feedback prior to review with Dell EMC.

Finally, Dell EMC will conduct the discovery phase deliverable review meeting in order review content, answer questions, document updates needed and secure City of Phoenix’s acceptance.

Definition

With a detailed understanding of the current system state, the project team will develop a complete technical migration solution to address business and functional requirements. Dell EMC will facilitate discussions for migration design to review options and the tradeoffs of with the City of Phoenix project team. This type of facilitation provides sound architecture concepts to guide engineers through the design process and will present a best-practice solution to the City of Phoenix team based on expert knowledge of the technical options available. The Dell EMC Consulting library of derivative works will be heavily leveraged to expedite the design process through reusable architecture templates.

The following content areas are addressed during this task:

SQL Server Infrastructure Design

Size and design infrastructure, Windows Server OS, and SQL Server instances to host future SQL Environment.

Determine any HA/DR requirements for targeted infrastructure inclusive of SQL availability.

SQL Server Migration Planning

Included within the design will be a review and documented analysis of the detailed findings provided from the SQL Server Best Practice Analyzer (BPA) and the SQL Server Upgrade Advisor. A combination of both manual and automatic installations will be tested for feasibility and ease of migration execution.

The EMC team will met with COP to gather info to develop migration approach to provide SQL infrastructure to Applications team and perform go-live events. Similar to the discovery, COP participation and input is critical. A series of meetings limited to one and one-half hours will be scheduled to discuss strategies, procedures and implications.

Topics will include:

Physical or Virtual Hardware configuration - System Inventory Define and analyze current environment (development, test, load, stage, production) Define Windows servers that will host instances of SQL Server in the datacenters (Development, Test,

Load, Stage, Production) Define migration path for SQL servers Installation requirements such as physical and virtual specs for CPU, memory and storage Network requirements such as DNS and IP and networks/network adapters HA and DR requirements such as cluster and Always On



Database backup and restore Testing and Go – live events

Based on the feedback from COP staff in these meetings, EMC will define the following:

A detailed Migration Approach for SQL server instances, nodes, and databases of which outlines the goals, dependencies, high level process and sequence for migration steps. For example, the document will describe a migration sequence of databases hosted on a server and how the go-live events will be coordinated. Additional details include

Define approach for migration of servers nodes Define approach for migration of cluster nodes Define approach for migration of databases Define approach for migration of HA/DR techniques Define approach for additional processes and jobs needing to be performed by COP dba Define communication plan required for end user and helpdesk notifications Identify representative servers/ users to serve as pilot migration users.

A Migration Test Plan, which will explicitly define the use cases and conditions for a satisfactory migration in POC and production Additional details and test unit instructions may be included as necessary.

Construction

During this phase, any necessary testing will need to be conducted in an isolated testing lab prior to moving to production. Once the architecture, migration processes, and specific technologies are tested and validated, the migration solution is built out in the production environment parallel to the current messaging environment. Initial build out of selected hardware and software components will be deployed in a “pre-production” configuration to allow for pre-production testing of the target environment. Once the production environment has been validated, the remaining production systems will be built and configured to allow full scale testing of the production environment prior to pilot testing. The production build out will include items such as testing and stabilization of the collaborative services prior to placing a production dependency upon the new systems. The results of the testing will be delivered to City of Phoenix through test plan checklists.

The primary tasks executed during the SQL Construction Phase include the following: Installation of prerequisites to support SQL server installation Installation of the base SQL server software Creation and configuration SQL instances Configuration of HA and DR per the requirements

SQL Database Migration Waves

Dell EMC will perform the database migrations using the processes developed in the Definition phase and tested in the Construct phase.

The following tasks will need to be addressed during this phase. Organizations responsible for each task are identified after each bullet:

Backup of source database (Dell EMC) Restore of target database (Dell EMC) Handover to COP applications team to perform testing and app installation (Dell EMC & City of Phoenix) Install and test associated applications needing access to SQL (City of Phoenix) Schedule cut-over events and communicate to users effected City of Phoenix Build remaining SQL server and backup/restore SQL database (Dell EMC) Perform Tier 3 next day support for SQL migration (Dell EMC) Deliver communication messages per the defined communications plan (City of Phoenix) Conduct knowledge transfer to COP personnel (Dell EMC) Receive end user trouble ticket calls and assign to appropriate group (City of Phoenix) Provide Tier 3 support for failed computer/email migration after all FAQ are followed (Dell EMC) Decommission legacy source environment post migration (City of Phoenix)



SQL Re-Architecture Key Activities Define and analyze current SQL Server system inventory (Development, Test, Load, Stage, Production) Understand timeline and dependencies Conduct SQL Server migration requirements gathering Conduct SQL SME interviews Understand business processes and model surfaced from SME interviews Document business and technical requirements Inventory and document SQL nodes and instances needed to be migrated Inventory and document SQL Server pre-requisites Create Current State Database Assessment Define inventory of database servers and databases Document data and storage specific requirements Determine high-level candidate architecture for SQL infrastructure Determine the appropriate SQL Server solution for High Availability and Disaster Recovery Complete SQL Implementation Planning Develop Test Plan Build out SQL solution in test environment Build out production SQL solution in primary data center Create Systems Build Document Test solution Backup of source database Restore of target database SQL Database Migration aligned with application migration waves Hand-off to City of Phoenix applications team for testing and application installation Knowledge Transfer

Below is a RACI diagram for the SQL re-architecture workstream:



RACI represents: R - Responsibility, A - Accountable, C - Consulted, and I - Informed

COP SME's Consultant Team Members

Proj

ect M

anag

er

SQL

DB

A

Secu

rity

Team

Bus

ines

s In

telli

genc

e

Lice

nsin

g C

ompl

ianc

e

App

licat

ion

owne

rs

Proj

ect M

anag

er

SQL

Team

App

licat

ion

Team

Le

ad

Proj

ect T

eam

M

embe

r

SQL Server Work Stream

Backup current SQL databases C/I R/A I I I C/I C/I C/I I I

Restore SQL databases into new environment C/I I I I I C/I R/A R/A/C I I

SQL install media and appropriate license keys C/I A/C A/C I R/A/C I R/A R/A I I

SQL BI components (SSIS, SSRS and SSAS) C/I A/C I R/A I R/A/C R/A R/A/C I I

SQL Server SA and local admin access against the target environment C/I R/A/C R/A/C I I I R/A R/A/C I I

Build target SQL Server environment C/I C/I C/I C/I C/I R/A/C R/A R/A/C I I

Application connection string migration (Production migration and Alpha/Beta testing) C/I A/C C/I R/A/C I R/A/C C/I C/I I I

Role

Project Deliverable (or Activity)

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

Deliverables Tasks Deliverable MediaSQL Requirements Document

Current state discovery and requirements for SQL Server MS Word

SQL Database and Application Assessment Mapping

Database and application assessment for the current environment

MS PowerPoint

SQL Detailed Design/Build Document

Design and build document for the target SQL Server environment

MS Word

SQL Test Plan Executed Test Plan for target environment (solution tested in lab and production)

MS Excel and MS Word

SQL Migration Procedures

Migration run book for SQL Server database migration (target environment), aligned to application migration waves

MS Excel and MS Word

3.2.4. MICROSOFT SQL RE-ARCHITECTURE ASSUMPTIONS SQL Server Object Counts for migration - Police and Fire 16 Production SQL Servers (Enterprise)

293 Production databases



7TB Total Storage Footprint Up to 4 Production SQL Servers configured for High Availability (SQL Clustering or SQL AlwaysON).

No more than 4 AlwaysON replica nodes each Up to 9 distinct Production High Availability nodes

1 DTS package – SQL 2000 (Upgraded or migrated like for like) 1 SSIS package – SQL 2005 (Upgraded or migrated like for like) 2 SSIS packages – SQL 2008R2 (Upgraded or migrated like for like) 85 SSIS packages – SQL 2012 (Migrated like for like) 265 SSRS reports – SQL 2008R2 (Upgraded or migrated like for like) 500 Crystal Reports – Crystal 2013 (Migrated like for like)

Each server instance, including all object dependencies (SQL Logins, Permissions, Server Configurations, Agent Jobs, Linked Servers, Drive Configurations, Database File Locations).

SQL Server OS Version upgrades are includedSQL Versions are determined after the Discovery and Analysis phase Consolidation of SQL Instances are determined after the Discovery and Analysis phaseConsolidation of SQL Databases are determined after the Discovery and Analysis phaseConfiguration changes will be made to the instance per best practice for the agreed upon SQL Server versionDowntime will be required for go-liveDell EMC will be provided full local operating system admin and SQL Server system admin access for the source

and target environments, for entire duration of the engagement.Backup software is able to restore on a database levelDatabase data will be migrated up to a maximum of two times, per database. Once for testing and once more at

final database cutover.Migrated database data will be limited to the quality and content available through the backup software provided.No coexistence of SQL Server Instances in source and target domains. Each SQL instance will be migrated to the

Target domain and the corresponding SQL instance in the source domain will no longer be operational at the time of cut over (migration) to the new Target domain

New SQL servers will be installed in the target domainCity of Phoenix will ensure Dell EMC team has appropriate access to SQL server installation media for SQL ServerCity of Phoenix will provision all appropriate Active Directory for SQL Server, supporting artifacts before the

construction phase begins.Dell EMC to configure Windows Failover clustering for each Windows Server supporting SQL Server Instances

configured for AlwaysOn Availability groupsCity of Phoenix will ensure all domain service accounts required for configuration are available for SQL Server

Database Engine, SQL Server Agent, SQL Server Reporting Services, SQL Server Integration Services and SQL Server Analysis Services prior to the beginning of construction phase

Migrated database data will be limited to the quality and content available through the backup software provided.Dell EMC will upgrade, where possible, all Production SSIS (SQL Server Integration Services) Packages and

SSRS (SQL Server Reporting Services) reports to the appropriate consolidated Production SQL Server version level as these Production SSIS and SSRS align with the Production SQL migration effort. SSIS and SSRS artifacts that are not part of the Production SQL Server migration effort are out of scope

All Crystal Reports objects and the Crystal Reports Central Management Server for Police and Fire will be migrated “like for like” with no report modifications, upgrades or server upgrades

All Crystal Reports database connection strings and associated <ODBC name>.dsn on individual servers or client workstations will be updated, as needed for migrations, by the City of Phoenix IT team

SSAS (SQL Server Analysis Services) is out of scope and does not exist in the environmentAny application connection string changes that are not related to SSIS or SSRS are the responsibility COP and the

application owners to update during each migration wave activity where the application relies on a SQL Server database connection.



Dell EMC will be given full access to the SQL backup and restore management consoles for the Source and Target environments.

City of Phoenix will ensure backup and restore software is the same between the Source and Target environments.Dell EMC assumes the Cut-over of applications is within six weeks of initial data migration on the completed server

build. The timelines will be determined and agreed upon by the City ITS and application owner departmentsDell EMC assumes the Cut-over of applications is within six weeks of initial data migration on the completed server

build.City of Phoenix is responsible for all application support and troubleshootingCity of Phoenix is responsible for Tier 1 (helpdesk) and Tier 2 (desktop) supportCity of Phoenix will provide all storage allocation including temporary storage for the backups in the target

environmentCity of Phoenix will provide timely access to an onsite Active Directory SMECity of Phoenix is responsible for application Migration Test Plans, Test Cases and Test ExecutionCity of Phoenix is responsible for Application migration, testing, support and any end user re-configuration

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



CITY OF PHOENIX STAFFING TABLE

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

SQL Server Platform Engineering SME

City of Phoenix SQL Server Platform team shall provide 8 hours per week of access for the duration of the project. This might include system interaction, meetings, and/or reviews.

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

Database SME 10-20hours /wk 8-10 hours /wk 8-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. COP is responsible for all infrastructure relocation services 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.

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 .

Dell EMC may use subcontractor resources to assist with this project. Such resources shall be bound by Dell EMC’s obligations under the terms and conditions of this SOW.

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 COP to provide current infrastructure and application test plans COP to provide system and application shutdown and restart procedures COP to provide and manage suitable SAN to SAN replication or copy for migration of virtualized servers 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 Transition Manager COP to execute infrastructure and application test procedures Sign off on server owner acceptance of completed Migration’s will be in Transition Manager upon completion of

migration tasks. COP will be responsible for providing ~60-70 qualified virtual machine workloads per week across all server locations

to meet the planned weekly conversion targets 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.

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 COP will have the target VMware virtual infrastructure available, ready, configured according to VMware best

practices, and the workload is suitable for migration Communicate with application vendors to determine VMware affinity Complete all data migrations for underlying VM’s

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 Transition Manager 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. SQL Discovery and Design Complete 20% $

3. SQL Construct, Build and Test Complete 20% $

4. Completed Development Database Migration event #1 5% $

5. Completed Migration Event #1 10% $







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 <Phase/Milestone/Deliverable> described below has been successfully completed because Dell EMC’s has met all of the applicable acceptance criteria for such <Phase/Milestone/Deliverable>. 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 <Phase/Milestone/Deliverable> 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 <Phase/Milestone/Deliverable> 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 Transition Manager and is the initial Bundle designator in Transition

Manager, 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 Transition Manager (TM) – End-to-end Integrated Database Software for Data Center Migrations, Consolidations,

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


Documents

ITS 18-202 - Attachment F - Web viewA current state SQL server discovery assessment will provide the foundation for the SQL Server ... MS Excel and MS Word. ... During the project