Sericol CRM Application
iEnterprises Inc.
iEnterprises helped Sericol standardize on a single global CRM solution. Previously, Sericol's U.S. division had successfully deployed iEnterprises' iExtensions for Notes (http://www.ienterprises.com). While this was a factor in considering the product, Sericol believed a successful global implementation was dependent upon which languages it supported. Sericol had the added challenge of supporting specific dialects of Czech and other uncommon languages.
Sericol recognized that each language typically requires its own software installation, separate configuration, and independent administration. Ideally, the company wanted to limit the amount of duplicative effort required at each location. It had hoped, at a minimum, to have an application developed for all its target languages.
iEnterprises believed that with Lotus Domino 6, it could develop iExtensions for Notes so Sericol could have multilingual support for any language and a single consistent code-base. iEnterprises executed this solution by detecting the user's language preference using the @languagepreference formula. When iExtensions determines the user's language, it matches it with the appropriate stored translation of all the text and labels that appear throughout the solution on forms, documents, menus, and prompts. The translated text is cached on the user's system so forms and documents display quickly.
For Sericol, and other multinational organizations, this offers tremendous advantages. First, because the translation is calculated on-the-fly, only a single code-base is required. System administrators only have to install and configure the application on a single server. The configured databases then replicate to other servers. Upgrades can be handled similarly; and by relying on replication to deliver the solution updates, all users are using the same version enterprise-wide. This minimizes conflicts, alleviates incompatibility issues, and facilitates support.
Sericol found the total cost of ownership of the solution is reduced when customizations are required. For example, if a customization is wanted, it need not be developed or maintained independently for each language. Like configuration preferences, the single code base allows customizations to be executed once. As the system matures and is tailored to fit the organization's business processes, modifications are easily managed because there is only one place to make changes.
The introduction of these multilingual features means that every label in the entire solution is now configurable through the configuration database. This can result in greater user acceptance, because the solution can be configured to use the nomenclature employees are already accustomed to using. As such, any field label can be easily configured to use the vernacular that is specific to a particular company or industry. In many cases, this also provides an alternative to costly custom development.
Finalists