Software customization
Let us understand customization. Have you read the earlier write up "first time software purchase ?" Customization is just modifying the software to meet your business process and needs. Now why customization should be so complicating? Why is customization referred to as 'necessary evil?' Actually, not all 'customizations' fall into the 'evil' category. Some customizations are very simple and they come to you with the software. To name a few,
- Simple Data input screen customization- E.g.: In Financial statement add logo, add lines, change font etc.
- Simple Reports customization- E.g.: Change formats of invoice or receipt. Modify to use a preprinted material.
- Forms customization- E.g.: Rearranging fields, hiding or changing order etc.
- User definable fields: Add a new field to capture any special information
- Customization by user- E.g.: Different screens for different users
The above simple customizations are easy to use. But Customization is just not increasing the font size or insert columns there is much more to it…it can be complicating. To give a few examples:
- Database level customization.
- Integration customization. Data transfer to third party software.
- Report in two currencies.
Now let's assume you have selected software for your company. This software has all its purchase module, Sales module, finance module etc., in INR. You would like duel currency for your sales module as you intend to expand. Now is the need to customize. I must say it is very tempting to 'order' the vendor to customize, the minute you see this limitation in the software. "Hey, get me my sales figure in INR & USD. Customize it." What if tomorrow your Finance department also wants a duel currency reporting? Customize again? Please, let me warn you extensive software customizations can trap you.
I mentioned earlier you must select a software which meets at least 85% of your major requirements. Then tune the software to meet 90-95% of your needs. For the balance 5% modify your process to the software working. If you still think the missing 5% is most crucial, then get started with a new software search. Yes, this is better than getting into extensive customization. Like in the above example, if duel currency is a 'must be' then find a software. Customizing software packages are no fun for the vendor, either. Try asking them!
"How many companies spend millions of dollars 'tweaking' an ERP system rather than tweaking their business to match it" these were the words of Bill Gates from his book "Business at the Speed of Thought". It's true not only to ERP systems but also to any software product. I am trying to claim that 'customization is bad or evil', but you have to first justify what you are doing different *before* you justify making the customization.
OOK, if you have 'good reasons' and decide to customize then get the following question answered by the vendor:
How do I safe guard my customization? You got to remember, this vendor who has this software, is doing this modification or customization, only for you. When this vendor provides you with patches or updates, what happens to your private customization? Customization should not be lost when the software is upgraded or patches applied. This is possible if the user defined customization is saved as separate programming objects or in separate dictionaries. But the vendor has to promise this to you.
In some cases cost may be incurred if, from your side, you decide to upgrade. Eg: Move from SQL database application to a Oracle database application.
Happy customization!! Need some help from us? Have questions to shoot? Drop a line to info@ipott.com
|