Vision and Scope
Datacenter & Cloud Consolidation and Migration
i
Table of Contents
1
Introduction ............................................................................................................................................ 3
2
Opportunity Statement....................................................................................................................... 4
2.1
3
Business Opportunity .................................................................................................................................. 5
Project Vision and Scope ................................................................................................................... 6
3.1
Vision Statement ........................................................................................................................................... 6
3.2
Benefit Analysis.............................................................................................................................................. 7
3.3
Scenario Value Proposition ....................................................................................................................... 7
3.4
Technologies .................................................................................................................................................. 8
3.5
Special Hardware Requirements ............................................................................................................. 8
3.6
Requirements ................................................................................................................................................. 8
3.6.1
Business Requirements ........................................................................................................... 9
3.6.2
Functional Requirements ....................................................................................................... 9
3.6.3
Operational Requirements ..................................................................................................... 9
3.6.4
Technical Requirements ......................................................................................................... 9
3.7
Scope of Project ......................................................................................................................................... 10
3.7.1
Areas within the Scope ........................................................................................................ 11
3.7.2
Service Areas Out of Scope ................................................................................................ 12
3.8
Constraints ................................................................................................................................................... 12
3.9
Acceptance Criteria ................................................................................................................................... 13
4
Project Structure ................................................................................................................................. 14
5
Project Risks and Mitigations ......................................................................................................... 17
ii
1
Introduction
Update [Customer] in Doc Properties has selected the Datacenter Consolidation and Migration
Offering for optimizing its data centers. The purpose of this engagement is to:

Discover and assess the existing VMware and Hyper-V environments to determine the
recommended scenario and approach for migration.

Provide a pilot migration of up to 20 virtual workloads to the Hyper-V or Microsoft Azure
Infrastructure-as-a-Service (IaaS), depending on the scenario.

Provide a full migration plan and (optionally) additional resources to perform the
migrations.
The purpose of this document is to provide a sufficient level of detail about each component of
the Solution. This document is an outcome of the Solution Alignment Workshop meeting where
all requirements (business, functional, technical, and operational) are shared and discussed.
3
2
Opportunity Statement
Guidelines for a problem statement:
•
Provide a background of the client and their reason for undertaking this project
•
Establish the motivation for the project (purpose)
•
Stay at a high level and use business language (guidelines)
The problem statement should include information on the high cost of maintaining VMware licenses or
why the customer wants to migrate to the Hyper-V platform. It should include information on the lack of
a comprehensive application and systems management Solution in the VMware stack. An example has
been provided below:
At a high level, Update [Customer] in Doc Properties has three goals for the project:

Reduce IT costs by using a hypervisor that does not have variable costs that charges
based on virtual machine usage


Migrate its server machines with zero impact to its current IT staff
Assess and consolidate the number of hosts used to run the server machines to reduce
operational costs
From the Solution Alignment Workshop, the following challenges have been identified with the
current environment at Update [Customer] in Doc Properties:

The rising cost of running VMware in their environment has forced Update [Customer] in
Doc Properties to move to a more cost effective platform.

The lack of a comprehensive systems management Solution to monitor, predict, and
automate the overall health of the IT environment is a gap in the current IT operations.

Less infrastructure to manage means more focus on the business and lower overall IT
costs.
4
2.1 Business Opportunity
<Describe the customer’s current situation that creates the need for the project. You may include a
statement of the customer’s opportunity and the impact of capitalizing on that opportunity (infrastructure
services innovation, maturity enhancement, cost avoidance, operational streamlining, and using
knowledge). You may also include a statement of the customer’s problem and the impact of solving the
problem (IT and business units partnership, cost reduction, and alignment of strategy and technology).
You should include a statement that connects the customer’s opportunity or problem to the relevant
business strategy and drivers. The opportunity statement is written concisely using business language.
Justification: The opportunity statement demonstrates that Microsoft understands the customer’s
situation, and it provides the project team and other readers with the strategic context for the remaining
sections.>Purpose: establish the motivation for the project. An example has been provided below:
The Datacenter Consolidation and Migration Offering provides a highly automated and low-risk
path to migrating server machines to Windows Server Hyper-V and/or Microsoft Azure.
5
3
Project Vision and Scope
3.1 Vision Statement
<Guidelines for a vision statement:
•
Purpose: establish the long-term vision and provide design-making content. Provide
unbounded sustaining motivation.
•
Guidelines: balance all of the interests to arrive at a single vision statement. Bring to light any
enterprise architecture implications early.
Clearly and concisely, describe the future, desired state of the customer’s environment when the project is
complete. This can be a restatement of the opportunity; however, it is written as if the future state has
already been achieved. This statement provides a context for decision-making. It should be motivational
to the project team and to the customer.>
The Datacenter Consolidation and Migration Offering is an engagement that utilizes
technologies such as Windows Server 2012 R2 Hyper-V, Microsoft Azure, and one or more
migration Solutions.
This project is divided in three engagement phases:
1. Discovery and Assessment: The first phase is Discovery and Assessment of the current
server machines to be migrated.
2. Migration Proof of Concept (POC): The second phase is a Migration Proof of Concept
(POC) to demonstrate the migration solution as well as to air in planning a full migration.
3. Full Migration: The third phase full migration of server machines to Windows Server
Hyper-V and/or Microsoft Azure IaaS.
During the Discovery and Assessment server machines are discovered and assessed for potential
suitability for the target platform in mind.
During the POC, the consultant provides a demonstration of the migration process, how it
works, and how it might fit into the customer’s environment. This provides the customer with an
evaluation of the process and a view of its risk. The objectives of the POC are to:

Set up and configure the migration toolkit to migrate server machines from
AWS/VMware to Windows Server Hyper-V and/or Microsoft Azure (if required).

Provide a showcase of the process and demonstrate both the automation and risk-free
nature of the process.
6
<Modify the Proof of Concept below according to the requirements of the engagement. Some optional
items have been included, but they can be removed or changed depending on the customer’s needs.>
The POC will be based on and demonstrate the following products and technologies:


Windows Server 2012 R2 with Hyper-V
Microsoft Azure IaaS (if required)
During the third phase, we will implement a full migration of server machines. The consultant
will collaborate with Global Delivery or other additional migration resources, if applicable, to
support them in performing the migrations for the customer at a lower cost. Global Delivery will
also perform the necessary pre- and post-migration validation tasks to ensure consistency and
validity of the process.
3.2 Benefit Analysis
<Describe how the customer will gain value from the proposed Solution. Connect the business goals and
objectives to the specific performance expectations to be realized from the project. These performance
expectations should be expressed numerically.
Justification: benefits analysis demonstrates that Microsoft sufficiently understands the customer’s
situation. It also defines the customer’s business needs that may provide vital information for making
Solution and technology recommendations.>
Customize or insert benefits as appropriate (example provided below):
By migrating its server machines to the Windows Server Hyper-V and/or Microsoft Azure
platform, Update [Customer] in Doc Properties will like to gain the following benefits:



Licensing and support cost savings of using the Hyper-V platform
Increased usage of the System Center platform for monitoring and management
<<add text>>
3.3 Scenario Value Proposition
The migration toolkit helps an organization to migrate server machines from the VMware
platform to the Hyper-V platform in a highly automated, low-risk way with the assistance of
<Partner> Services and its Global Delivery components. The key scenarios that the migration
toolkit supports are:

Discovery and assessment of the existing VMware environment and the proposed
Hyper-V or Microsoft Azure environment capacity—to support customers in making
decisions on virtual machine retirement.
7

Resource optimization—to support customers’ understanding of the resource
consumption of their server machines to allow for changes in resource consumption
policies.

Server conversion—to support customers in reducing the total number and cost of
server ownership by maximizing hardware utilization, consolidating workloads, and
reducing infrastructure management and facilities costs.

Vendor and platform reduction—to support customers in reducing the different types
and numbers of hypervisor providers.
3.4 Technologies
The following technologies are associated with the Migration Toolkit:





Windows Server 2012 R2
Microsoft Migration Accelerator (MA) (if used)
MAT4MVMC / MVMC (if used)
Double-Take Move (if used)
MAT4SHIFT (if used)
3.5 Special Hardware Requirements
The Hyper-V virtualization platform requires x64 hardware running either the Intel VT- or AMDV-enabled processors. Child partitions, hosting guest operating systems, can be either 32-bit or
64-bit, but the parent partition must run on 64-bit hardware.
3.6 Requirements
<Identify what the Solution must do. These requirements can be expressed in terms of functionality (for
example, a registration website Solution will allow the users to register for events, arrange for housing,
and so on), as well as the rules or parameters that apply to that functionality (for example, the user can
only register once and must stay in housing approved by the travel department). Requirements exist at
both the user level and the organizational level.
For the Business Requirements, insert the business goals that motivate the customer to deploy the
Solution as identified in the Solution Alignment Workshop and documentation review. Write each
requirement preferably using a business executive’s voice.>
The following sections define the business, functional, operational, and technical requirements
that must be met for the Datacenter Consolidation and Migration engagement to be successful.
8
3.6.1 Business Requirements
These are the business goals that motivated [Author] to design a Datacenter Consolidation and
Migration Solution include:
For example:

Reduce IT costs by using a hypervisor that does not have variable costs that charges
based on virtual machine usage.


Migrate its server machines with zero impact to its current IT staff
Assess and consolidate the number of hosts used to run the server machines to reduce
operational costs
3.6.2 Functional Requirements
For example:

Migrate a virtual machine to the Hyper-V platform with no impact to, or loss of, the
original virtual machine

Manage the migrated virtual machine with Virtual Machine Manager once on the HyperV host

Validate the migrated machine attaches to network with the correct configuration
(proper VLAN, and so on)
3.6.3 Operational Requirements
For Example:


Conform to the business availability and redundancy requirements
Provide integration with existing System Center 2012 R2 infrastructure to achieve
centralized management

Integrate with existing approval and rejection control gates for virtual machine migration
3.6.4 Technical Requirements
For Example:
Facilitate and support the virtual machine migration from following systems to Windows Server
Hyper-V and/or Microsoft Azure:


VMware ESX 4.x and 5.x
Amazon Web Services (AWS)
9
3.7 Scope of Project
The preceding vision statement provides a motivating goal for the team working on this project.
As such, we write it with broad brush strokes in order to provide a shared and inspiring ideal.
The statement provides context for decision-making at later stages of this project when team
leaders will be deciding among features, cost, and scheduled delivery. It is not provided to be a
legally binding contract for the Solution.
The revisions of this document going into the future provide the detailed scope of what will and
will not be accomplished to meet the vision. That said, the core features to be implemented by
the Solution could be characterized by the following specific goals and objectives, areas in and
out of scope:
10
3.7.1 Areas within the Scope
Modify the following sections based on the appropriate delivery path.
The scope of the project should include the discovery, assessment, and migration of all
supported server machines that the customer has approved for migration.
Phase
Discovery and
Assessment
Migration POC
Activity







Full Migration








Install and configure of the assessment scripts to collect and analyze
data in the virtualized environment
Execute assessment scripts to analyze the environment
Analysis data to provide cost estimates, cost savings, and return on
investment (ROI) analysis on the full migration
Review findings from Discovery and Assessment.
Install and configure the migration solution/s and its prerequisites
Migrate of up to 20 non-production server machines to Windows Server
Hyper-V and/or Microsoft Azure
Produce a baseline project plan for Full Migration
Install and configure of the toolkit environment, if not already completed
in the POC phase
Migrate of in-scope server machines to a properly sized Hyper-V or
Microsoft Azure environment
Test basic connectivity to server to make sure networking is working as
expected
Remediate virtual network connection in Hyper-V as needed
Provide Internet connectivity to Microsoft Azure as needed
Provide live migration of server machines to their final host or cluster
destination
Provide other pre- and post- migration validation activities to ensure
quality
Report success rates and migration velocity
11
3.7.2 Service Areas Out of Scope
You can delete some of the out of scope activities if their inclusion was agreed with the customer and the
necessary changes have been made to the duration and effort allocated for the engagement.
Any area that is not explicitly listed in as within scope is out of scope for this engagement. The
areas that are out of scope for this engagement include, but are not limited to, the following:


Any server machines that the customer explicitly does not want migrated.
Installation and configuration of the customer’s VMware environment including ESX
hosts and vCenter servers.

Installation and configuration of the customer’s Hyper-V environment including Hyper-V
hosts, SAN storage, networking or role services.

This may be a separate project, such as a Private Cloud Jumpstart project, but is out of
scope for the “migration” project.



Functional testing of applications on server machines after the migration.
Migration of server machines with desktop operating systems.
Remediation of servers that are incompatible with working on a Hyper-V or Microsoft
Azure platform.

Removal or deletion of server machines on the VMware platform after the completion of
the migration.

Any activity that is not listed in Section 3.7.1 as “In Scope” is out of scope for this
engagement.
3.8 Constraints
Based on the environmental assessment and Solution Alignment Workshop, the following
technical assumptions have been made:
Insert list of technical assumptions. For example:

Active Directory Domain Services (Active Directory (AD) DS) would be used for an
enterprise identity


Licenses for System Center 2012 R2 would have been procured
Hardware infrastructure to support Solution would be in place
Any changes to these assumptions and constraints may affect the project timeline and should
be identified as early on in the engagement as possible.
12
3.9 Acceptance Criteria
<Define the conditions and circumstances by which the customer’s operations teams judge the Solution
ready to deploy into the production environment. Once the Solution is deployed, the customer takes
ownership of the Solution. This section may specify the customer’s requirements for training operators
and administrators, using the different elements of the fabric management system provided to manage
the infrastructure services lifecycle. An example has been provided below.>

Validate and prove virtual machine is running properly on the Windows Server Hyper-V
and/or Microsoft Azure platform
13
4
Project Structure
Services recommends that the project team be organized according to the Microsoft Solutions
Framework (MSF) Team Model. The MSF Team Model identifies major roles and responsibilities
during the phases of planning, implementing, and deploying a business Solution.
Figure 1: Team Model of the Microsoft Solutions Framework
14
The roles identified in the preceding figure do not imply that all projects require all six people.
The roles must be assigned among individuals on a project team. Each role brings a particular
mindset that contributes to the overall quality of the effort. Only a subset of these roles is
required for this particular engagement.
Role
Focus
Skills
Responsibility
<Partner> Services
Customer satisfaction
Good communication
Responsible for
and knowledge of the
managing customer
business
expectations, and
Engagement Manager
On-time delivery,
architecture, problem
maintaining the business
solving, and
Facilitation, project
identifying and
management,
resolving critical
communication, writing,
issues
business model and IT
Responsible for
standards knowledge
specification
case, research,
promotion, and launch
management, tracking,
coordination, and signoff
<Partner> Services
A responsive, reliable,
Problem solving,
Responsible for discovery
Consultant
and compliant
development skills, and
and assessment of
product
deep technical
source environment
A usable, supportable
knowledge
Responsible for
product that
User empathy and
documentation design,
enhances user
technical writing
terms definition,
performance
Smooth rollout,
documentation, testing,
base lining, and training
migration, and
Responsible for
operation
performing migration
tasks from to Windows
Server Hyper-V and/or
Microsoft Azure
15
In order to cover the responsibilities of completing the project, the following roles have been
assigned to the following individuals from Microsoft and [Author][Type Author Here]. At later
phases of the project, these roles may be explicitly transitioned to other team members who join
the effort:
Resource
Company
Role
[Author]
Key Stakeholder
Microsoft
Project/Engagement
Manager
[Author]
Testing
Microsoft
Development, Deployment
and User Education
[Author]
Logistics
[Key Stakeholder Name] will also be the project lead, becoming the primary point of escalation
for any external issues and the project advocate inside [Author].
One understands, from these role assignments, that <Partner> Services will deliver a Solution
architecture and functional specification for the Datacenter Automation implementation.
[Author] will provide adequate quality assurance and testing in order to sign off on the
functional specification. <Partner> Services expects [Author] to provide quality management of
the Solution in terms of defining needs and requirements and managing expectations. [Author]
will also need to provide a resource to provided testing on test scenarios to be run in a
simulated environment.
16
5
Project Risks and Mitigations
Customize the table below with the risks identified at this stage. An example is provided below.
The project team takes a proactive approach in managing risks. The risks listed below represent
issues that may affect the success of the engagement (time, scope, or quality of the completion)
and will be proactively addressed during the implementation:
Risk Statement
Probability
Impact
Responsible
Risk Mitigation Plan
The necessary infrastructure
Medium
High
[Customer]
See that the list of all hardware
and facilities to create a lab
and software resources
environment may not be
required to create the lab
available on time for the
environment has been
project.
communicated to the
appropriate team member.
Assemble the lab during the
second week to help make
sure the environment is ready
to run the test plan during the
third week.
Lack of a lab environment
High
Medium
[Customer]
Customer will assemble a lab
that closely represents the
environment that mirrors
production environment and
production in order to
meets the requirements as
adequately test migration.
outlined in the vision and
scope document.
Insufficient expertise in
High
Low
[Customer]
Microsoft will provide a
critical technologies, such as
training class through
Hyper-V technology, failover
Microsoft Premier that will
cluster services, or System
address the appropriate
Center 2012 R2 Suite.
technologies with the
customer’s support staff.
This list will be continuously updated with newly found risks and reassessments of the
probability and impact of existing risks.
17