Подія
Чемпіонат світу з даних Power BI
14 лют., 16 - 31 бер., 16
Маючи 4 шанси увійти, ви можете виграти пакет конференції і зробити його на live Grand Finale в Лас-Вегасі
ДокладноЦей браузер більше не підтримується.
Замініть його на Microsoft Edge, щоб користуватися перевагами найновіших функцій, оновлень безпеки та технічної підтримки.
To create a process-focused solution for your Dynamics 365 implementation, follow these recommendations. They help you improve the quality, optimization, and standardization of your business processes.
Start from Microsoft's business process catalog.
Download the latest version of the catalog from https://aka.ms/BusinessProcessCatalog. We update the catalog at least four times each year. Learn more at Business process contributions.
Update the business process catalog.
The business process catalog serves as a baseline for deriving more detailed business processes. Learn more at About the business process catalog for Dynamics 365 apps and services.
Consider importing the catalog into a tool, such as Azure DevOps, to help you manage the catalog and project.
Your requirements should map to your processes, and your processes should map to your business goals.
When you use the business process catalog, we recommend that you map all requirements to the lowest level possible. In other words, map your processes to a business process at level 3, work item type Feature, or a pattern at level 4, work item type User story.
Map the current processes (as-is) with the desired processes (to-be), if applicable.
Understand how your process works today and how you want it to work in the future to meet your business goals. If you're starting from scratch, focus on designing the desired process only.
Choose the appropriate level and type of business process.
Depending on the purpose, the hierarchy level, and the message of your process, you can use different forms of flows to illustrate it, such as the following list:
Build the end-to-end processes.
The end-to-end process shows the overall purpose of the business by connecting the core processes across different areas. Identify the business areas of your organization, and then create the end-to-end business process for each. For example:
Assign the right access and security to the users who carry out the tasks and activities.
This also helps you estimate the number of users and licenses you need for your project budget.
Determine what fits the standard and what the system gaps are.
Sometimes, the current processes might not be fully covered by the new system, which can be an opportunity to find better or more optimal ways to execute them. You might need to develop more features to meet your business needs.
Learn more about end-to-end business processes in Dynamics 365.
Подія
Чемпіонат світу з даних Power BI
14 лют., 16 - 31 бер., 16
Маючи 4 шанси увійти, ви можете виграти пакет конференції і зробити його на live Grand Finale в Лас-Вегасі
ДокладноНавчання
Модуль
Business process mapping for Dynamics 365 - Training
Discover how to implement business applications effectively, using techniques like shadowing and mapping processes into Dynamics 365.
Сертифікація
Microsoft Certified: Dynamics 365 Customer Service Functional Consultant Associate - Certifications
Удосконалюйте бізнес-процеси для функцій служби підтримки клієнтів, наприклад автоматичне створення інцидентів і керування чергами за допомогою Служби підтримки клієнтів Microsoft Dynamics 365.
Документація
Optimize your business processes with Dynamics 365 - Dynamics 365
Learn how to map, model, and standardize your current and future business processes as part of your Dynamics 365 implementation.
Case study in process-focused solutions - Dynamics 365
Read this case study to learn how a large, multinational organization changed its implementation approach and achieved better results with Dynamics 365.
Optimize your implementation with a fit-to-standard and fit-gap analysis - Dynamics 365
Learn how to review your current processes and identify what to change, keep, or add to make the most of your Dynamics 365 implementation.