After successful Decisions NAV 2009 and Decisions AX 2009 virtual conferences, MSDynamicsWorld.com has went for it once again, this time expanding the conference to cover full range of Microsoft Dynamics products, and merging it into a single event.
Long time no see, eh? I know I’ve promised to write about a lot of stuff here, and I see this queue of you hardly waiting to read my next topic on process manufacturing, but I am just far too lazy to think it out thoroughly. So, an easier one, but still about manufacturing.
I spent this week delivering two courses about manufacturing in Microsoft Dynamics NAV. Usually, these trainings are gatherings of partners who discuss geeky stuff over coffee breaks. This time, it was kind of different – there were two people from the customer front, and it was really amazing to listen to customer perspective when learning about standard NAV.
One of the points raised today, in the midst of closing of Manufacturing II course, was about parallel routings. Do we do them, or do we not. A tough one, indeed.
When implementing NAV in manufacturing companies, I’ve sometimes heard complaints that the type of manufacturing supported in NAV doesn’t fit the customer needs.
And sometimes that’s completely true. NAV supports discreet manufacturing, and it handles it pretty well. But the things do get bumpy when you venture into process manufacturing world.
Sometimes customers or even consultants don’t really understand why this happens. It’s simple: there is a big difference between process and discreet manufacturing, and to successfully implement NAV in these two fundamentally different environments you need to understand and appreciate these differences.
Panorama Consulting Group, the authors of the ERP report, have just made available two interesting tools: ERP Quick Diagnostic, and ERP Readiness Assessment. According to their website, if you are…
I’ve just got the news about Part III of Panorama’s ERP Report in my inbox. If you missed my analysis of the report, please read it first: part three builds on findings of the first two. I know that I am biased when writing about this, but how can I not be? Microsoft Dynamics is the best choice ERP and the report (as a whole) clearly shows why exactly.