Last week I’ve written a post about Customization and IWMS. By explaining the customization paradigm I have put forward seven reasons why you shouldn’t customize your IWMS.

In this post I’ll discuss the other side of the Customization Paradigm; Configuration.

Configuration is adapting the IWMS towards your processes and requirements without modifications to the source code of the core product.

Configuration of an IWMS  has some big advantages:

1. Configuration is relatively cheap
   Since all processes and business logic are predefined you can only do modifications that are allowed within the IWMS. As programming is extremely time consuming configuration will save a lot of time. (= money)

   As tip I would advice you to have a look at the offering you’ve received from your IWMS vendor. Ideally, the ratio between software and consultancy would be approximately 50-50. The more consultancy is involved, the more expensive the entire solution will be. More consultancy services are an indication for functionality not being standard.

2. Configuration is fast
   Programming is time consuming. Even minor changes (such as work flow changes) can take weeks because all rules have to be programmed. Configuration on the contrary is because of its predefined boundaries faster. Limitations are a blessing as long as these are supporting your business requirements.
3. Configuration is flexible
   Although predefined boundaries seem to be limiting the support of your business processes they do not. In fact, IWMS vendors who provide an off-the-shelf product will provide better support of business processes because of those boundaries.

   Implementation of an off-the-shelf IWMS tends to be more organizationally focused than the technically focused implementation of IWMS’s that need to be customized (programmed) to your needs. Focusing on organizational processes will reduce the need for customization because as a side effect the business processes itself will be evaluated and non-performing, inefficient and irrelevant processes will be disposed.

4. Configuration ensures independency
   Since your organization is in full control of the IWMS you will be independent from the IWMS vendor. All changes both minor and major changes can be done by functional administrators of the IWMS.
5. Configuration facilitates upgrades
   Almost in every implementation of an IWMS that I have been involved in customization causes upgrade problems. When configuring a product and not modifying the source code of the core product you will have easier upgrade processes. My advice would be to request the IWMS vendor to provide the following data:
   • Customers that have been customer for at least 7 years
   • And that have migrated at least three times (only major releases, not including service packs)

   This will give you a very good indication about the IWMS’s upgrade possibilities.

6. Configuration does not require advanced technical skills
   Most professionals in FM and RE do not have a technical background but need to be able to do modifications to the IWMS themselves. When the IWMS provides easy to use configuration tools you ensure that your experts in the different functional areas of the IWMS can do functional changes.
7. Configuration changes the role of the IT Department
   Since your FM and RE professionals can do modifications to the systems themselves your organization will be less dependent on the IT Department. In fact, their role will change from both functional and technical administrators to only technical administrators.

Your Opinion

So what do you think about customization vs configuration? I’d love to hear to what extend you (dis)agree with me. Please use the comment option below the post to add your opinion.

Bookmark this article

Related Posts

1. 7 Reasons why you should not customize your IWMS
2. I18n of IWMS: Multi-language
3. 12 Reasons Why IWMS Thrills Every CIO
4. Taking the sting out of IWMS software selection
5. 6 Reasons Why No One Is Using Your IWMS