Upgrade Optimization Engine Model to V11 and V12 (DEPRECATED)
The Model Types represent the initial implementation of Optimization. Currently, all the functionalities is covered by Model Classes (https://pricefx.atlassian.net/wiki/x/ToA25g).
No more new implementations relying on “Model Type”, should be done; at some point in the future, it will be removed from the product.
The up-to-date documentation about the Optimization Engine is Optimization Engine and Job Trigger Calculations.
From the version 11.0, the Optimization module no longer has the menu item “Optimization Engine”.
Version 10.0 | Version 11.0 |
---|---|
The models in the Optimization Engine menu are based on Model Types, the same way as other Pricing Guidance models. So your models are not lost by the update: you can access them through the menu Optimization > Pricing Guidance > Models.
This interface is not specific to Optimization Engine based models and it has a strict format. All your model steps take place in the Calculation and the Results steps. Definition and Analysis are empty.
Update to V12 and Next
In the coming versions, the Model Type based models will not be available anymore. They are replaced with the Model Class based ones. This fact implies a lot of architectural changes.
If the models you use are based on optimization accelerators, such as Negotiation Guidance, Price Waterfall Optimization, you simply need to deploy a newer version of the accelerator – they are now based on Model Classes. Then, you will need to create new models in Optimization > Models, and parameterize them. There is no way to directly update models based on Model Types to models based on Model Classes.
If your models are based on you own Model Types, there is a configuration work to do to create the corresponding Model Class. A configuration engineer must be involved to do this (documentation in Optimization (Reference)).
Found an issue in documentation? Write to us.