1. Microsoft Dynamics Planning Services
11/7/2017
Microsoft Dynamics Planning Services
Implementing Microsoft Dynamics 365
PARTNER ENGAGEMENT OVERVIEW
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Engagement Customization & Exceptions
This document outlines the steps for a typical Microsoft Dynamics 365 implementation planning process. The tools and resources reflect tested Microsoft best practices.
We understand that no two customers are the same. The intent of the engagement is to assist Microsoft Dynamics 365 customers with their implementation planning, including taking advantage of new features. To best address the needs of your customers, please feel free to customize the engagement in the following ways:
Edit the Pre-Engagement Questionnaire to more accurately address your customer’s unique scenario
Skip any phases as long as you can justify doing so in your final deliverable.
Skip a phase if you or your customer has already conducted it
Skip the workshop if your customer is already familiar with the new features and functionalities or focus on deeper exploration and discussion of the newer CRM functionalities and scenarios listed later in the presentation
If the initial steps of the engagement are less relevant to your customer, you can extend the PoC implementing additional processes and new scenarios and capabilities
If your customer has a complicated environment and business requirments, extend the assessment phase to include in-depth functional assessment, transforming and adding processes, assessing existing and future integrations with additional tools and systems.
Customize the engagement documents or use your own documents if they are aligned with the engagement steps. Regardless of the documents you use, your deliverables to the customer must be attached to the Planning Service Completion Report and must cover findings and results similar to those listed in the provided templates.
Questions about permissible customizations and exceptions?

3. Contents Document Purpose Sections Engagement Overview
11/7/2017
Contents
Document Purpose
The goal of this document is to provide the engagement consultant with an overview of what is required to deliver during the Planning Services engagement Implementing Microsoft Dynamics 365. The engagement is offered in three, five, ten and fifteen day sponsored lengths, which build on each other. This document describes the steps, resources and requirements of each engagement.
The engagement lengths represent the minimum time needed to deliver the required deliverables for each engagement and the maximum paid days a Partner can expect against when delivering specific deliverables.
Sections
Engagement Overview
Engagement requirements, customization and exceptions
Execution detailed guidance
Tools & Resources
Planning Services Requirements
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

4. Implementing Microsoft Dynamics 365
11/7/2017
Implementing Microsoft Dynamics 365
About the Engagement
Implementing Microsoft Dynamics 365 helps customers who are just starting with Microsoft Dynamics 365 or looking to extend their current implementation to assess their business processes technical requirements, analyze the functional and technical gaps of their business processes and create a customized plan to implement Microsoft Dynamics The Planning Services engagement helps customers put their IT investment to work, drive productivity, improve business agility. Work with customers to identify the gaps between their current solutions implementation and business objectives and processes.
Envisioning Workshop & Demo
Business Process Assessment
Fit-Gap Analysis
Proof of Concept
Deliver a solution overview, discussing and collecting info on customer business needs, existing environment and processes and envisioning the suitable solution
Analyze “as-is” solution and existing system, process flow and functional requirements\integration. Document overall business requirements and selected business processes which will be used as an example for the rest of the engagement.
Conduct fit-gap analysis of business requirements and environment. Determine adequacy of the latest release of the Microsoft solution in details for the chosen processes and deliver estimated cost for an implementation plan.
Demonstrate the solution benefits, implementing 1 to few business process using Microsoft Dynamics 365 Online
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

5. Implementing Microsoft Dynamics 365
11/7/2017
Implementing Microsoft Dynamics 365
Engagement Overview, Requirements & Supporting Resources
3 days
5 days
10 days
15 days
Activity
Educate & Assess Top Requirements & Processes
Assess Business Requirements
Assess solution degree of fit to exemplary processes
Design & Showcase Integration with Customer Environment
Resources
Pre-engagement Assessment 
Pre-Engagement Requirements Questionnaire CRM
Envisioning Workshop + Demo
Dynamics 365 overview deck
Workshop assessment deck
Workshop finding templates (to be filled during the workshop)
Demo m/
Business Requirement Assessment (As-is analysis)
Requirements assessment guide
Requirements Review Final Report template
Fit gap and customization assessment (To- be analysis)
Fit Gap Analysis Worksheet/Guide
Scoping Assessment
Scoping Assessment Report
Dynamics Costing Worksheet
Proof of Concept (online or on- prem)
PoC/implementation guidance m/
Required Deliverable for Payment
Envisioning Finding Report & Next Steps
Requirements & Process Review Final Report
Fit gap and customization analysis report
PoC Closeout Presentation
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

6. Solution Overview and Envisioning
Required activities & deliverables for any voucher of 3 days or more
Required Activities
Pre-engagement Questionnaire
Ask the customer to complete the questionnaire in detail. Based on customer response, plan the envisioning workshop, conduct an initial high-level assessment of the current business process, business needs and ERP solutions in place and identify:
General need of the customer for a business solution and top business processes
Architectures and technologies used within the organization
Current system’s challenges, gaps and limitations that might be solved with Microsoft Dynamics 365 or Microsoft Dynamics 365 Online and considerations for different implementation options
Additional processes that can benefit from a Dynamics 365 implementation
Customer timeframe for deployment
Workshop
Once you have assessed the completed questionnaire and identified high level requirements plan a workshop that will help the customer envision their custom solution and will help you to collect more information about the customer.
The objective of the workshop is to educate the customer on Microsoft Dynamics 365 and provide guidance to facilitate decision-making. The activity should also be used for high-level solution envisioning, where business problems and their solutions are identified. Attendance of key stakeholders and decision- makers are required.
During the workshop discuss with the customer how implementing Microsoft Dynamics 365 can meet the functional requirements for their processes and how they can benefit most from such solution.
The completed pre-engagement questionnaire should have given you a good idea of the customer’s readiness for a CRM implementation. Next slide list In this subjects you should discuss during the workshop.

7. Discussion Points and Questions
Suggested Topics for Envisioning Workshop
Understanding of market and business landscape – what their industry and competitors are doing
How customer can benefit from a Dynamics 365 solution in the cloud or on-premises
How the customer can benefit from migrating their solution to Dynamics 365 either on- premise or in the cloud
Organization cloud “philosophy” and it incline to put applications and data in the cloud
Current cloud usage – what’s in the cloud already
Mobility needs and mobile employees
IT budgetary issues and other IT challenges such as – ROI, upgrade schedule and resources, nimbleness, hardware ownership
Crisis management and disaster recovery best practices
Industry-specific security and compliance requirements for the customer
BDMs and TDMs’ adversity to the cloud
Employee inclusion:
Need to include the buy-ins of more than just the front-line employees, also consult the wider user base such as customer service representatives and salespeople
Need to identify and tackle end-user problems from LOB/Office integration and other adoption challenges
Overview of the current version of Microsoft Dynamics 365 and highlighting newer capabilities recently added to the product or closely integrated with it as detailed on the next 2 slides. Discuss with your customers how these capabilities might replace custom code solutions they might have and solve business challenges they face.
Create a summary report outlining the findings of the workshop including: documented processes, customer goals, solution concept and functionalities and next steps.

8. Microsoft Dynamics 365 Before Now Evolution from current offerings
Dynamics CRM
Field Service
Project Service Automation
Parature
Dynamics 365 for Sales
Dynamics 365 for Customer Service
Dynamics 365 for Field Service
Dynamics 365 for Project Service Automation
Dynamics AX
Dynamics 365 for Operations
Project Madeira
Dynamics 365 for Financials
Dynamics GP
Dynamics NAV
Dynamics SL
Dynamics GP
Dynamics NAV
Dynamics SL
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9. Dynamics 365 Recommended Scenarios Discuss during envisioning workshop
Marketing
Sales
Field Service
Customer Srvice
Marketing resource management – streamlining marketing operations
Multichannel campaigns - designing your customer journey
Lead management and scoring - building sales pipeline and drive revenue
Social marketing – listen and engage customers on social
Marketing intelligence - demonstrate results and impact
Automating sales processes to boost productivity
Gaining key insights into sales data with Power BI, PowerApps and Flow
Streamlining sales cycles
Reducing costs, featuring a highly intuitive interface and Microsoft Office embedded capabilities
Mobile - staying connected to customers anytime, anywhere
Including: Field Service, Project Service and Employee Self-Service
Portal - make customer service effortless
Agent enablement – Empowering agents to wow customers
Onsite service - smart onsite care
Knowledge management – providing tools to get the right answers at the right time
Service intelligence - analyze and anticipate
Omni-channel - offer service anytime, anywhere
Social listening – helping expose customers sentiments
Intelligent social - understanding market insights
Social engagement – connecting better with customers
Social CRM - driving CRM with social

10. Discuss Dynamics 365 Business Process Support
Purpose-built business applications
Sales
Actionable Insights
Personal Engagement
Customer Management
Sales Performance
Intelligence
Customer Service
Omni-channel engagement
Self-Service and Communities
Unified Experience
Knowledge Base
Marketing *
Field Service
Optimized scheduling
Service agreements
Inventory
management
Mobile productivity
Connected devices
Customer Communications
Project Service Automation
Solution
selling
Project planning
Resource scheduling
Time + expenses
Customer billing
Operations
Retail
Procurement and sourcing
Supply chain management
Project accounting
Human capital management
Manufacturing
Financial management +
* Adobe and Microsoft announced plans for a strategic partnership. Microsoft will make Adobe Marketing Cloud its preferred marketing service for Dynamics 365 Enterprise edition.

11. Microsoft Social Engagement
11/7/2017
Additional Scenarios
Expand Dynamics 365 scenarios and capabilities with your customer to showcase additional benefit an ROI they can gain from their software investment + +
Microsoft Social Engagement
Portals
Turn-Key Solution Integrations + +
Azure
Cortana
TALK POINTS
Enhance first party solutions or custom solutions with turn-key integrations that offer extra capabilities for faster time to value experiences. + + +
Gamification
Surveys
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

12. Business processes assessment phase
Required activities & deliverables for any voucher of 5 days or more
Required Activities
The objective of the Requirements and Process Review is to identify and evaluate the high-level requirements and business processes to be addressed by the Microsoft Dynamics 365 implementation.
Your customer is responsible for providing you with a prioritized list of high-level functional, business processes, and integration requirements. The scope of this activity constitutes the following:
Explore customer business challenges and goals
Review existing processes and document requirements for business processes which are not included in the current environment:
Match each business process to a relevant module of Microsoft Dynamics 365.
For business processes that do not match against any module, new modules can be created to support them. Document these as non-critical issues.
Review high-level business processes, their requirements and their as-is implementation.
Review high level functional, business and integration requirements to ensure they can be met:
Analyze legacy systems, review existing business and IT requirements, and identify new requirements.
Validate the degree of fit of the Dynamics Solution to the overall customer’s requirements and goals.
Discuss possible limitations and customer’s concerns regarding the different implementation options
Identify risk areas where proposed solution does not map to the requirements. Work out acceptable compromises and devise a potential implementation strategy.
Identify one or few business processes which are suitable to for the engagement length you deliver, document these business processes
A written report highlighting all critical and non-critical issues, possible workarounds, as well as your recommendations and justifications. Your customer will need this information for product selection. Create an action plan and summarize next steps:
Prioritize business processes that can well exemplify the benefits of the solutions, but at a level of complexity that can be accommodated during the engagement you plan to deliver.
Document in details the identified business processes and ensure that they can be supported by Microsoft Dynamics 365
Prioritize a process which will highlight newly added Dynamics 365 scenarios and that will be a good example for a fit gap analysis

13. Discussion Points and Questions
Suggested Topics for Business Process Assessment
The Business Requirements gathering phase marks the official start of the engagement. The goal of this stage is to define and document the company’s business requirements related to Microsoft Dynamics 365 and any needed ISV solutions. These requirements include Business, System, Technical, Integration / Interfaces, Data, and Quality / Testing. Taking a "big picture" approach at the initial stage of the project allows us to consider all the requirements and possibilities related to if, how and when Microsoft Dynamics is deployed in the various locations and departments in the customer’s organization. At this time we also determine which Microsoft Dynamics functionality is required and document the Deployment Strategy that lays out in what phase of the implementation project the various modules and / or functionality will be implemented.
Gather enough background information about the current environment so that the engagement is focused in the right areas. This is not an in-depth analysis, which is beyond the scope of this exercise, but it should capture how the customer currently feels. Some examples of areas that should be covered include:
Customer’s general need for a business solution
Current system and the reason for changing it
Current architectures in use within the organization
Enterprise architecture standards, principles, and constraints
Code development standards
Current technologies in use within the operation
Integration and interface standards
Current master data and transaction volumes
Number and type of users
Current skill levels
Current change control management processes
Current ERP environment, and any other such tools that are in use
Current status of any initiatives in the organization relating to the current ERP environment

14. Fit gap and functional assessment phase
Required activities & deliverables for any voucher of 10 days or more
Required Activities
The objective of the this assessment is to determine the Microsoft Dynamics solution’s degree of fit to the business requirements and customer’s business processes. It should also help to determine the most suitable implementation path considering required configuration and customization for the process. This assessment should consider the functional gaps of the out-of–the-box features and functionalities of Microsoft Dynamics 365 for overall requirements and for the example processes identified. Required tasks:
To ensure the functional requirements will be met by the implementation, match each requirement to a relevant module of Microsoft Dynamics 365:
For functional requirements that do not match against any module, new modules can be created to satisfy them. Document these as non-critical issues.
A functional requirement with a matching module, but the area of functionality to which it maps cannot be modified to actually satisfy the requirement, presents a critical issue.
Identify risk areas where proposed solution does not map to the requirements. Work out acceptable compromises and devise a potential implementation strategy.
For the identified one to few customer business process deliver a detailed fit-gap assessment:
Ensure the functional requirements will be met by the implementation, by matching each requirement to a relevant module of Microsoft Dynamics 365:
Produce an assessment report summarizing the degree of functional fit of the suggested
A review of “as-is” and “to-be” process-flow fits and gaps, with an emphasis on the gaps. Including -
Validation of the “degree of fit” of Microsoft Dynamics 365 to certain business requirements and include a prioritized list of requirements
Review of critical gaps, and explore alternatives that solves them.
Estimate of Degree of Fit (i.e. identification of what is native functionality, configuration, or customization) for the overall environment and in particular identified and prioritized processes
High-level estimate of the services required for configuration and customization for each requirement
Development of a Solution Blueprint for the process which provides details, from a Business Perspective, of how Microsoft Dynamics 365 will be delivered and used

15. Scoping assessment phase
Required activities & deliverables for any voucher of 10 days or more
Required Activities
The objective of the Scoping Assessment is to provide your customer with a high-level view of the total cost and effort (internal and external) associated with the implementation of Microsoft Dynamics 365. Also help compare the implementation requirements against the customer’s risk/cost sensitivity profile and determine a high-level implementation plan that caters to your customer’s needs. The customer should receive an assessment report that describes the different implementation options and a high-level implementation plan for moving forward.
The following action items and deliverables are part of this Assessment:
Several  implementation options for consideration
A benefits analysis comparing and contrasting the two most appropriate implementation options
High-Level Implementation Plan for the overall solution and a detailed plan for the example processes including analysis of two or more implementation options. You should demonstrate the following:
Deeper insights into the implementation and resource plans allow risk anticipation and mitigation
Greater estimate accuracy on project costs lead to more consistent forecast on the return on investment (ROI)
Reduced risk and accurate ROI strengthen stakeholder alignment and executive sponsorship
The Assessment will vary in depth depending on the length of the engagement and the availability of information for the implementation plan.
We suggest that you provide the customer rough estimates of a few scenarios that entail the same number and complexity of processes as the one to be implemented. Since requirement gathering is ongoing, be sure the customer understands that the estimates may change drastically as more details about their requirements and more suitable solution architectures emerge.
Deliver a Scoping Assessment report including the following details and benefit:
Suggested high level implementation plan and cost associated with it as well as resources
Implementation Guiding Principles
Established Business Prioritization of cost vs. time vs. scope
Proposed Implementation Approach
High-Level Project Gantt Chart
Resource Plan and Proposed Project Organizational Chart
Project Effort and Cost Estimates
Critical Assumptions
Project Role Descriptions

16. Benefit Showcase (PoC) phase
Required activities & deliverables for a voucher of 15 days
Required Activities
The Vision for the Proof of Concept is to demonstrate select Microsoft Dynamics 365 functionalities implementing one to few business process to key Business and IT Users, so as to validate the solution, and drive solution acceptance. This will be achieved through the implementation of Microsoft Dynamics 365 Online trail environment.
You will create a PoC environment in Microsoft Dynamics 365 Online using customer data, records and users for the chosen process. This test environment must include at least one process, but we recommend including a few to cover different roles in all relevant organizations. Whichever processes you choose to include, however, you will need to explain your selections in the completion report. The customer may keep the PoC beyond the engagement for continued testing.
Required activities:
Establish PoC environment using Microsoft Dynamics 365 Online
Microsoft Dynamics 365 is configured to provide high-level support for the business processes defined and prioritized through discussion with the client;
Microsoft Dynamics 365 is configured for detailed support for selected critical business processes;
A characteristic subset of the Customer data is loaded;
The PoC is presented to the customer’s stakeholders to gain consensus in the proposed solution and gather additional requirements feedback;
All configuration, or developed interfaces, is left behind as transferable to the implementation project (all generated Intellectual Property (IP) is retained for use in the implementation project); and
A PoC report with the findings is delivered and reviewed with the customer.
The scenarios in the next slides are the recommended to showcase the highly beneficial solutions and functionalities of Microsoft Dynamics Customize the PoC according to the assessment results, customer requirements, and vision to best demonstrate the solution benefit. You may choose to demonstrate different scenarios based on your customers needs, but you must explain your choice in the PoC Findings Report.
The PoC Findings Report should summarize considerations, chosen scenarios and processes, implementation steps and customer usage, the benefits you showed case the customer, results and next steps.

17. 11/7/2017
Tools & Resources
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

18. Tools & Resources Microsoft Dynamics 365 Planning Services
11/7/2017
Tools & Resources
Microsoft Dynamics 365
Deploying and administering Microsoft Dynamics 365 Online and Microsoft Dynamics
Microsoft Dynamics 365 Spring 2016 Wave Release Preview Guide
Microsoft Dynamics Resource Guide 2016
What’s new (all features)
What’s new for end users
What’s new for admins and customizers
Field service -CRM field service guide
Project service -CRM project service automation guide
Dynamics 365 portals - Administrator’s Guide to portal capabilities for Microsoft Dynamics 365
Mobile offline - Configure the new mobile offline experience
Power BI - Embed Power BI tiles on a dashboard
Development for Microsoft Dynamics Marketing
Social Engagement Help & Training
What's new in Microsoft Social Engagement
Parature - Set up knowledge management in Microsoft Dynamics 365
Dynamics Online vs on-premises features FAQ
YouTube Videos
Planning Services
Partner Eligibility Requirements
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

19. Planning Services PROGRAM REQUIREMENTS
11/7/2017
Planning Services PROGRAM REQUIREMENTS
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

20. Program Requirements Partner organizations must:
11/7/2017
Program Requirements
Partner organizations must:
Gold competency in Customer Relationship Management (CRM); or
Silver or gold competency in Cloud Customer Relationship Management
Become an approved provider of Dynamics Deployment Planning Services (DYDPS)
See more detailed requirements here
Microsoft Dynamics 365 customers should:
Have Software Assurance points available to use for Planning Services
Interested in implementing Microsoft Dynamics 365 in the near future or extend existing implementation broader in the organization (engagement cannot include improvement of existing implementation or performance assessment)
Enable the partner to access relevant data for project success
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.