Why Vocabulary Is Key to Getting a Fast Start on Your Dynamics AX Implementation

It seems as if the first two months of most implementations are spent trying to effectively communicate high-level concepts of Microsoft Dynamics AX.  Until customers have that basic understanding of the system features, they have no real basis for attempting to leverage AX for their business model, except to demand that the system do what their current system does today.   

How to address this challenge, and thereby gain a faster start?  This article focuses on an effective approach I have developed for my clients in manufacturing and distribution. 

A key, in my experience, is a prescriptive approach, in which I seek to paint a vision for running the client's business that maximizes use of out-of-the-box functionality. This approach also provides the conceptual foundation for incremental customizations. 

Most important, the vision needs to be expressed in the users' vocabulary and mental model of how they do business (and want to do business) rather than the AX vocabulary.   The prescriptive approach shapes the model to "the new way of running your business", and leverages the embedded conceptual models within Dynamics AX.  

An embedded conceptual model refers to the forms and data (and applicable calculation tasks) that end-users employ to perform a business process with an ERP system such as AX.  As one example, the conceptual model for replenishing stocked material typically differs among traditional manufacturers (using MRP/DRP logic), lean manufacturers (using kanbans), and distributors (using order point logic), and each conceptual model may employ different forms, reorder policies and calculation tasks to support suggested replenishment.

An embedded conceptual model also defines the key intersection points between an end-user's system usage and the firm's business processes.  The end-user may employ a standard form at these intersection points, although other alternatives may ...