Precautions during the journey of ERP implementation.

“The whole is greater than the sum of its parts.”   By Aristotle.

Implement ERP as complete system

Implement ERP as a complete system

This also applies to ERP implementation.  Especially, for developing enterprises, striving to bring in discipline in the company.   This may sound simple, but it has profound impact in all departments.   And if ERP users are not careful, it can get difficult and may delay ERP project.  ERP software is a great example of a ‘system’.  It has a lot of different components and parts, called modules.  They all link (rather tightly) together to solve the problem and make it flow properly.   If one part is taken out of the software, and you don’t decrease it by the amount of the subtraction, but by the ripple effect of all the other modules or procedures, that depend upon it.  We have learnt this by implementing ERP in developing enterprises (better term for SME), for over a decade.

DNS ERP is a great example of an Enterprise Software System.  Everything is linked to everything else.   How can you decide NOT to do one module (like accounts) and do other ERP modules?    Yes, ERP offers different sub-systems, but you have to pay the price, and more important the time, to implement the full thing.  We have observed some businessman are still clinging to legacy account centric software.  All other procedures are implemented in ERP, except accounts module.  Even so called learned Chartered Accountants are so comfortable with rudimentary accounting package that they do not like ERP.   This is not correct.  You need to keep in mind that you are responsible for the dependencies that get broken.  DNS ERP has given some thought to minimizing these dependencies.    If you want to integrate the different levels of your organization, you need the full ERP solution.  That’s the maximum value – and also the maximum complexity and dependency.  It seems overwhelming to try to figure out where to start and how to break it down to implement that is why you need to follow guidelines given by experienced ERP professionals.

It is amazing how much you can accomplish when it doesn’t matter who gets the credit.

Team work

Team work

ERP implementation is a team work.  Implementing ERP in an organization, which has not yet ‘fully developed’ (like corporate) is a challenge.   A good leader will remain in background and give credit to other team members of the ERP task-force. The deeper we go into ERP project, the more complexity and dependency we uncover.  The more valuable we want to make it for ERP users, the more requirements crops up, and we have to get spread across the entire DNS ERP application.  The more flexible and configurable we want to make it, the more team work is necessary.  The more we want to deeply solve meaningful business problems, the more roles and stakeholders we need to address.  Stakeholder means, not only department heads, but also sales-tax consultant, excise consultants, ISO consultants, customers, suppliers, and so forth.  This means ERP implementers have to handle all the interactions between the requirements, workflow and process management.

%d bloggers like this: