Microsoft Software Assurance
Cloud + Enterprise Deployment Planning Services
Work Order
Prepared for
Prepared by
Customer Name
Partner Name
Customer Name
Name
Customer Title
Title
{Date}
Cloud + Enterprise
Version
Deployment Planning Services Partner
Work Order
Table of Contents
Objectives ................................................................................................................................................................................................ 3
Scope ........................................................................................................................................................................................................ 3
Service Areas within Scope ........................................................................................................................................................ 3
Service Areas Out of Scope ....................................................................................................................................................... 5
Approach ................................................................................................................................................................................................. 5
Key Partner Name Activities ...................................................................................................................................................... 5
Key Customer Activities .............................................................................................................................................................. 6
Key Service Deliverables ............................................................................................................................................................. 6
Project Roles and Responsibilities ................................................................................................................................................. 6
Roles and Descriptions ................................................................................................................................................................ 6
General Customer Responsibilities and Project Assumptions ..................................................................................... 7
Project Assumptions..................................................................................................................................................................... 8
Cloud + Enterprise Planning Services Work Order
<Insert Partner Logo Here> 2
Work Order
Partner – Delete all pink text before you deliver this to the customer.
Use this template to define a Work Order format for your Cloud + Enterprise Deployment Planning Services
program.
Many partners will use their own Work Order templates, but for those who do not have one established, this will
provide a benchmark for Work Order creation. (Note that Partner Name and Customer Name are defined as
Advanced Properties of this document. To modify them, go to File -> Properties -> Advanced Properties)
Objectives
Partner Name will provide the Microsoft® Cloud + Enterprise Deployment Planning Services as described below.
Cloud + Enterprise Deployment Planning Services are a value and deployment planning benefit available to eligible Microsoft® Volume
Licensing customers with Software Assurance. Cloud + Enterprise consultants from Partner Name can help customers understand the
value and best practices of implementing a Microsoft solution extending their on premise environment into the cloud. The number of
DPS engagement days varies from 3 to 15 as determined by the engagement deliverable, the customer’s Software Assurance
coverage and available number of days.
Any timelines, dates, and delivery schedules provided here are estimates only, and are subject to change.
Scope
Service Areas within Scope
Partner Name will provide the following services:
Partner - Choose 1 of the offerings below ( 3, 5, 10 or 15 day engagement) and delete the rest. (There is a lot of
repetition in the content across the offering descriptions.)
Plan the Solution – Cloud + Enterprise 3 day engagement:
The engagement includes the following:

Envisioning Session – This session defines the customer objectives and introduces the new features of the Cloud +
Enterprise solution. There are two main components to the session- an overview of the business problem and the
definition of customer objectives. The purpose is to translate the business problem and solution statements into a
high-level solution and summarize how the solution could integrate with the customer’s environment

Architectural Design Session – These sessions introduce customers to the features and functionality of the solution
and demonstrate how those features could be deployed to help meet the customers’ requirements. Topics typically
include defining Vision and Scope, building an Infrastructure Overview and the creation of a Solution Concept. The
solution concept is the initial step towards a solution design and is the starting point for future detailed design
discussions. This solution concept IS NOT A FULL DESIGN and may not meet all Customer Name requirements.
The exact sessions should be worked out in advance between the customer and the delivery consultant.

Findings & Next Steps – Based on the problem statement, this session presents the overall findings, including:
business drivers, key deployment challenges, a proposed deployment strategy, high-level recommendations for
further investigation, and next steps.
The final deliverable is a customized document that consists of the problem statement, any identified requirements, identified
risks, a high level solution concept, proposed deployment strategy and next steps.
Cloud + Enterprise Planning Services Work Order
<Insert Partner Logo Here> 3
Work Order
Plan the Solution – Cloud + Enterprise 5, 10, 15 day engagement:
Partner - If you choose to extend the engagement with optional days to conduct one of the program’s
Proof of Concepts, modify the description immediately above and below to reflect the number of total
days.
Adding optional days is considered an extensive engagement aimed at larger organizations. It provides more time for deeper
dives into Cloud + Enterprise architecture, planning and deployment.
The engagement includes the following:

Envisioning Session – This session defines the customer objectives and introduces the new features of the Cloud +
Enterprise solution. There are two main components to the session- an overview of the business problem and the
definition of customer objectives. The purpose is to translate the business problem and solution statements into a
high-level solution and summarize how the solution could integrate with the customer’s environment

Architectural Design Session – These sessions introduce customers to the features and functionality of the solution
and demonstrate how those features could be deployed to help meet the customers’ requirements. Topics typically
include defining Vision and Scope, building an Infrastructure Overview and the creation of a Solution Concept. The
solution concept is the initial step towards a solution design and is the starting point for future detailed design
discussions. This solution concept IS NOT A FULL DESIGN and may not meet all Customer Name requirements.
The exact sessions should be worked out in advance between the customer and the delivery consultant.

Findings & Next Steps – Based on the problem statement, this session presents the overall findings, including:
business drivers, key deployment challenges, a proposed deployment strategy, high-level recommendations for
further investigation, and next steps. For extended engagements, next steps may include a proof of concept or limited
online pilot to demonstrate the proposed solution.

Proof of Concept (extended engagements only) – The POC is a tightly controlled, limited scope session using a
temporary tenant or deployment intended to show the customer particular features and capabilities in action. These
will include such things as on-demand capacity for services and resources and increased agility through the use of
virtualization, and standardized platforms and services. Additionally, it can demonstrate how improved levels of
service will be provided by the infrastructure team with reduced response times for infrastructure requests, metering
of resources by business units promoting optimal use of resources, and capacity reporting. This POC implementation
IS NOT A FULL INSTALLATION and will not meet all Customer Name production requirements. As a part of this
engagement, the partner will provide next steps for full production environment.

Limited Online Pilot (extended engagments only) - The Solution may be deployed on a limited scale in the
customer environment. The online pilot should help the customer to provide significantly reduced infrastructure and
operating costs through automation of key data center functions. These include on-demand capacity for services and
resources, increased agility and reduced datacenter hardware costs through the use of virtualization, and
standardized platforms and services. Additionally, the online pilot can demonstrate how the customer can realize,
improved level of service provided by the infrastructure team with reduced response times for infrastructure requests,
metering of resources by business units promoting optimal use of resources, and capacity reporting. This Limited
Online Pilot IS NOT A FULL INSTALLATION and will not meet all Customer Name production requirements. As a
part of this engagement, the partner will provide next steps for full production environment.
Partner - Fill in the custom objectives…
The final deliverable is a customized document that consists of the problem and solution statements, any identified
requirements, identified risks, an expanded high level solution concept, proposed deployment strategy and next steps.
Cloud + Enterprise Planning Services Work Order
<Insert Partner Logo Here> 4
Work Order
Service Areas Out of Scope
Partner - Using a bulleted list, identify specific areas that are out of scope for this engagement. Modify the
content below as required.
Any area that is not explicitly listed 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:

Microsoft Product Licenses

Modifying and stabilizing the current server environment

All network- or server-related issues that need troubleshooting

Installing any physical hardware

Review of operational processes

Industry regulatory compliance requirements

Establishment or production deployment of core central services at the customer environment.

Custom development for line of business applications

Racking and cabling hardware or servers

Customized virtual machine images

Customization of host deployment

Sourcing or procurement of hardware
Approach
In this section, please include a description of the overall project approach, including Microsoft partner
responsibilities, Customer responsibilities, and key deliverables.
Key Partner Name Activities
Partner - Customize the Partner Activities as appropriate

Lead the Envisioning Session

Lead the Architectural Design Session

Work with the customer to develop the solution concept

Lead a detailed walk through of particular features in the customer’s lab environment

Work with the customer to implement the proof of concept system (extended offering only)

Work with the customer to implement a limited online pilot (extended offering only)

Work with the customer to develop the final deliverable
Cloud + Enterprise Planning Services Work Order
<Insert Partner Logo Here> 5
Work Order
Key Customer Activities
Partner - Please list activities that the Customer must accomplish during each phase, in addition to any
prerequisites that must be accomplished prior to the beginning of the phase.

Fill out and return the Pre-Engagement Questionnaire

Work with the partner / delivery consultant on defining the program agenda

Provide information on key business, operational, and technical requirements

Provide input into the phases of the project covered by this Work Order and validating the results produced

Schedule sessions to include appropriate personnel

Attending sessions as appropriate

Work with the delivery consultant to develop the solution concept (if applicable)

Work with the delivery consultant to develop the final deliverable
Key Service Deliverables
Following is a list of key project mandatory service deliverables that will be delivered to the customer within this Work Order:

Engagement Findings and Recommendations document - The content of this customer deliverable is the result of the
Pre-Engagement Questionnaire and all activities during the engagement.

Delivery Evaluation Form
Partner - Please note that depending upon the length of the engagement the sections required for the
Engagement Findings and Recommendations document will vary.
Project Roles and Responsibilities
Partner - Revise as necessary
Roles and Descriptions
Role
Role Description
Project
Manager

Responsible for stakeholder management, single point of contact to the
customer for escalations, billing issues, contract extensions, project status,
and overall engagement, financials, and risk management.
Delivery
Consultant

Responsible for delivering the engagement

The Delivery Consultant provides technical oversight and leadership for all
aspects of the project
Cloud + Enterprise Planning Services Work Order
<Insert Partner Logo Here> 6
Work Order
Customer
Technical
Leads
Customer
Project
Sponsor
Customer
Project
Manager

Assist delivery organization during discussions and meetings

Provide input during discussions and meetings

Have the ultimate responsibility for the project

Ensure technical resources are available when needed

Make key project decisions

Assign key customer technical lead

Responsible for review of delivery organization deliverables

Sign off on scope for project

Ensure facilities are available as needed

Resolve critical-path issues in a timely manner

Sign off on delivery organization documents and change control requests

Accept and sign off in a timely manner on documents that pertain to the
delivery organization Work Order, and which are critical to the success of the
engagement

Sign off on Project deliverable-specific documents
General Customer Responsibilities and Project Assumptions
Partner - Please customize and add or delete sections as appropriate for your engagement.
The following are the responsibility of Customer Name

Project management and assigning project manager or managers (“owners”) as needed, to specific technical
initiatives.

Overall technical direction for customer IT infrastructure, and how it affects the Solution.

Ensuring availability of any required hardware and software.

Provision of workspace, including desk, phone with internal and external access, network connection, print services,
computer space, and an additional line (analog) for remote access to communicate with internal corporate network or
virtual private network (VPN) access through customer’s corporate Internet connection.

Provision of access to customer’s facilities and systems while maintaining appropriate levels of security.

Provision of timely access to people, documentation, and systems as required for successfully implementing and
completing this engagement.

Provision of clear goals and objectives mapped to customer’s business and IT strategies. Joint goals and objectives
need to be created and reviewed on a project-by-project basis.

Provision of access to customer’s management and planners. To be successful, Partner Name team will need
regular access to IT leadership to be able to provide input on customer’s strategic business and IT directions as they
relate to the use of Microsoft products and technologies.
Cloud + Enterprise Planning Services Work Order
<Insert Partner Logo Here> 7
Work Order
In addition to any customer activities identified elsewhere in this Work Order, Customer Name will perform or provide the following:
Partner - Please describe specific Customer responsibilities.
In performing our services under this work order and any applicable work order, we will rely upon any instructions, authorizations,
approvals, or other information provided to us by your Project Manager or personnel duly designated by your Project Manager.
Project Assumptions
The services, fees, and delivery schedule for this project are based upon the following assumptions:

The availability of your representatives to perform their roles on the project team.

The availability of all the information required for properly creating the project deliverables.

Product licenses. Product licenses (Microsoft or non-Microsoft) will not be provided under this work order. Customer
is responsible for acquiring all necessary product licenses required as a result of this work order.
Cloud + Enterprise Planning Services Work Order
<Insert Partner Logo Here> 8