Translate Blue ButtonDoes your organization have a custom developed configurator or CPQ solution? 

It probably has worked well for years and may have "hit the wall" when it comes to being able to handle high volumes of quotes, orders and order lines. 

If your organization also is an SAP customer and uses the SAP Variant Configurator there are some unique ways to translate the legacy configurator to SAP VC.  

We recently worked with a well known company that has had a legacy configurator for believe it or not for 45 years.  It takes orders but the error rate is pretty high (>50%).  Now all those errors are not severe, but it takes a human to review the order and correct it delaying the order from being accepted by SAP.   There are over 600 configurator models and maintained by nearly 80 people at multiple plant locations.   One of this company's goals was to eventually create all the configurable products to the SAP VC so that the legacy configurator could be retired. 

This was planned to be done manually or to have a new CPQ soluion do the translation to a new CPQ solution.  Only problem with a new CPQ solution doing the translation was that the SAP VC was to be used for manufacturing, purchasing and engineering as the standard in SAP.  So, only part of the problem would be solved to have the CPQ solution do the translation.  The legacy configurator would not be translated to SAP VC.   This company also estimated that the manual conversion to SAP VC would take many new hires and many years.  Too many years.  So much for time to market.

eSpline analyzed the rule patterns in the legacy configurator in a Prood of Concept and over a period of about a month and using two part time resources converted about 80% of the rule patterns from the legacy configurator to SAP VC rule patterns.  So rule translation is very possible!  Unfortunately, this company experienced an economic downturn at the time and the translation project was not funded or completed.   The 600+ product models translation was incomplete but some of the models were 100% complete because the rule patterns used in that particular product model had been covered in the proof of concept. 

In order to finish the translation of all models would have taken a few more months based on the initial review and analysis of the legacy rule patterns.  Now the translation was the "easy" part because implementing the SAP VC in SAP and transitioning off their mainframe computer was going to be a sizable task to say the least.  By the way translation of the 600+ legacy product models processing took less than 10 minutes. 

Last Updated ( Wednesday, 09 August 2017 15:23 )  

Add comment

Please keep comments to the point.

Security code

You are here: Home eSpline Blog CPQ Translation