Book Image

Becoming a Dynamics 365 Finance and Supply Chain Solution Architect

By : Brent Dawson
Book Image

Becoming a Dynamics 365 Finance and Supply Chain Solution Architect

By: Brent Dawson

Overview of this book

Implementing an ERP project is a daunting task, and it can often get derailed due to several reasons, including but not limited to inefficient planning, inadequate resource scoping, insufficient working knowledge of ERP systems, and more. Becoming a Dynamics 365 Finance and Supply Chain Solution Architect helps you understand the intricacies of ERP project implementation for seamless deployment. This comprehensive guide helps you gain a deep understanding of how to implement and optimize robust business applications that meet the evolving needs of organizations. You’ll discover various integration methodologies to integrate different software applications and plan successful data migration seamlessly. By leveraging the author’s expertise, you’ll explore different challenges that can lead to project failure or cost/time overruns, along with customized solutions to maneuver past those issues for a successful outcome. By the end of the book, you’ll be able to identify potential issues that can negatively impact the delivery of the project and make design decisions that will prevent any potential negative impact on the design and functionality of the system at go-live stage.
Table of Contents (18 chapters)
1
Part 1: Architectural Considerations and Best Practices for D365 Finance and SCM
8
Part 2: From Solution Design to Deployment – Practical Advice

Building a Blueprint Solution

Once you have been through all the client discovery and requirements-gathering sessions, it’s up to the solution architect (SA) to create a viable solution for their project. Knowing what the client needs and how it should be implemented is an important step to a successful project. A good blueprint will be easily explained and defended. That, in turn, makes the sign-off by the client on the design a simple formality.

In this chapter, we’ll look at the following key topics:

  • Knowing what goes into a solution blueprint
  • Expressing user requirements
  • Documents to include in the blueprint
  • How to maintain a living document