Houston Neal of Software Advice is running a survey about the ERP implementation strategies, with the goal of identifying the best one. The survey is very short, it will take only a couple of minutes and is aimed at helping future customers choosing the best strategy.
Even though I don’t think that anyone should follow the results of any survey when choosing their implementation strategy, the introductory article of this survey does a nice job explaining the three common approaches of implementing ERP. If you are an existing ERP customer, or a consultant, please take a half a minute and answer the questions there, and if you are a potential ERP customer, check the article to learn more about possible approaches your organization can adopt. If you missed the link at the beginning of the post, just click here.
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.
According to their website, if you are “in the early stages of selecting a new ERP software or if you’ve already completed your project, our ERP Quick Diagnostic will help you benchmark with other ERP projects across the globe”.
On the other hand, if you are thinking about starting an ERP project, you can take advantage of the ERP Readiness Assessment which can “determine how ready you really are for ERP”.
All in all, two simple online tools which can help you understand how well your ERP project is going or completed, or what can you expect if you decide to venture into one. Click here to check this out.
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.
“Software projects are no different from other projects”.
This statement is being repeated over and over at project management courses and seminars, even endorsed in books.
It’s true that software (and ERP implementation, as a subset of software) projects have many traits in common with projects in other disciplines. But ignoring their specifics is almost as wrong as saying that software projects are completely different than other projects.