For the last day I kept the NAV features. Convergence is abundant in sessions devoted to Nav 2015 functionalities (even if some of them are already seen from previous versions, but now have an ecosystem in which they integrate perfectly).
And I start with a topic I touched yesterday tangentially, namely data analysis through Power BI. First of all, I want to tell you that Power Bi is an extension of Office 365 functionality (better for Excel), where you also benefit from Power Q & A (that is, the possibility of searching and graphics in natural language) within a Sharepoint (better known as Office 365 Sites). This functionality is based on the fact that data in Microsoft Dynamics NAV can be exposed to be analyzed in Power BI through OData. Once this is a type of Web service, designed to query and extract tabular information. After we expose the data, and set up the application analysis display, here's what we can get:
After this beautiful and useful data analysis method, I want to talk about another interesting, more specialized session, namely Supply Chain Planning in Microsoft Dynamics Nav. During this session, we were able to find out how most companies are doing to generate a production plan based on MPS and then a MRP acquisition plan. A tip I learned from this session: Do not put Lot-for-Lot for all commodities or raw materials. Set NAV to the "Fixed Reorder Quantity" policy for the majority and put Lot-for-Lot only on those "sensitive" products, that is, those products that have a high value or that are critical to the structure of the finished product. Also, another advice received at this session was that when you have multi-level production, manually schedule production orders for the main products (level 0 and possibly level 1) because they are fewer and you will control them perfectly. Once you've made these orders and checked their schedule according to the required delivery terms, fix them so they can no longer be modified by the NAV Planner, and then just run the automatic planning that will do the job later. By the way, if you have bottlenecks, you can solve the problem of erroneous planning by setting the "limited capacity" parameter to the maximum possible. But enough about the Supply Chain, for more tips & tricks, you will have to join our blog on another occasion, or contact us directly!
Another interesting session from which I wanted to give you some details was "Tips and Tricks: Warehouse Management in Microsoft Dynamics NAV". It's interesting how this session started, because the first question they raised was: Are you sure you need WMS? But first make sure you answer the following questions: What benefit will I have? What will WMS let me do better? How am I working to get the desired result? And all this because WMS comes with a number of advantages and challenges:
|Exponentially increase inventory accuracy when deploying WMS.||More parameterizations are required both in the application area, locations, compartments, and (especially) at the products.|
|Better tracking capability where there are many stock moves.||Increases the number of transactions in the inventory database.|
|Easier FEFO or FIFO management for batch tracked products.|
Users will need more training (they will not work with paper and pen).
Integration with RF technology (barcode readers).
|Users must be convinced that "It's not that hard".|
|Integration with E-Ship / E-Receive to simplify WMS application submission.|
And the last advice that you received at this session: If you want WMS to work, you need to: work planned, do not create exceptions intentionally, be consistent.
And for the end of the correspondence from Convercence Europe, I want to talk to you about a case study presented: Lyoness Group. Coincidentally, a gentleman stepped onto the Convergence scene, Christian Vancea, who learned NAV in college (Microsoft Academic Alliance result). More about the case presented here you can find here!
His name leads us to the idea that he has Romanian roots, and indeed Christian Vancea lives in Graz, but he is the son of two Cluj ballet dancers who have chosen the way of exile for more than 30 years. From Mr. Vancea, I learned that Lyoness Group is basing its work on Microsoft Dynamics NAV ERP, not in anyway, but in the most serious way. It operates from 46 countries across the globe with 160 competing users. Here's the most interesting information: All of these users work on 3 SQL instances, defined on the same SQL server, running on a physical server. So yes, I can and would like to share this information with those who do not believe in the possibility of operating with a large number of users or with many transactions in the Nav.
But Convergence EMEA it’s over and I am looking forward to Convergence EMEA 2015.
Correspondent, with your will: Microsoft Convergence Europe 2014