When implementing an ERP solution, you may come to find that it doesn't do things exactly the way you thought it would. In order to fully utilize a specific function or process you may need to customize the software. Some companies also feel that there is a competitive advantage to be gained by customizing their ERP software so that it does more than their competitors’ solutions. Yet unlike configuration changes that are part of the normal set-up and implementation, customization involves changes to the source code of your ERP software; and when any of the code is modified there are risks involved.
Cost increases are likely
Writing and testing code is not an inexpensive process. Any time the code from the plain-vanilla implementation is altered, there is likely to be a ripple effect throughout the entire application. Chasing down the effects of your modifications also costs money through added quality assurance testing. Unless time for customization was built into your project plan from the beginning, the time you spend writing, testing and debugging code will throw you off schedule.
Maintenance and upgrades are more difficult
Every so often your ERP vendor will issue software patches to address different things in the current application and they will offer upgrades to increase the features and functionality of their software. If you have customized the code, upgrading the software becomes problematic. Installing upgrades and patches may overwrite your customized code or cause it to break. Likewise, your customized code again needs to be tested in the new environment and if there are any issues, they need to be tracked down and addressed.
You may open security holes
Enterprise software vendors frequently run tests against their software to seek out any known vulnerabilities so that they can fix them. With an ERP solution, this is extremely important as this application works with so much sensitive, confidential data. By modifying any code in the application, you render those security tests null and void making your organization responsible for testing the software on your own. Failing to scan customized software could expose your data to any number of exploits that would do serious harm to your company’s reputation.
Should you customization altogether?
Most experts will tell you that you should not customize your ERP code unless it is absolutely necessary as in the case of competitive advantage. If it comes down to process driven customization, re-evaluate those processes. It may be that your processes are broken and not the software. If functionality is driving the customization discussion, then may be you need to look for a solution that better fits your company or industry.
Despite the problems, a good number of companies still choose to customize their ERP solution during the implementation process. If this is something that your team is considering, make sure that there is an expert on hand to help determine if this is really necessary. If the decision to move forward with the customization is made, they can also help you make sure that you don’t leave anything out that could disrupt the rest of your implementation project.
The post Risks Associated with ERP Implementations: Customization appeared first on Merit Solutions.