Requires Free Membership to View
When you register, you'll begin receiving targeted emails from my team of award-winning editorial writers on the latest customer relationship management (CRM)and call center technology issues today. Our goal is to keep you informed on the hottest issues facing this fast-changing industry.
Hannah Smalltree, Editorial DirectorBeyond the fit with your configuration and quoting requirements, there are several additional factors to consider when you evaluate these solutions. First, you want to determine if the solution will integrate with your existing ERP system. Frequently, products and product configuration rules originate in the organization's ERP system. You will save yourself a lot of time and effort if the product configurator solution that you choose integrates directly into your ERP system in order to load existing products.
Second, examine the solution's administrative user interface and capabilities. Once you have loaded your products into your product configurator, you will need to define the relationships between various products and parts in your product catalog. The ease of defining and maintaining these product relationships will determine both your initial implementation and your ongoing maintenance costs. If the solution can identify relationships in your existing product data and point out inconsistencies, that is definitely a feature you would want to consider.
Finally, consider the how well the solution fits into Microsoft CRM's architecture. Solutions that leverage the Microsoft CRM Software Development Kit (SDK) to integrate with Microsoft CRM will be much easier to implement and maintain, and make for seamless upgrades when a new version of Microsoft CRM is released. A good litmus test for the architecture of any ISV solution, even if you have an on-premise deployment, is its ability to integrate with the Dynamics CRM Online.
This was first published in December 2008