This section details the Model Class and the logics that the Price Waterfall Optimization Accelerator deploys. For each step, its aim, its outputs, and the main reasons to modify the logics are explained. If there is a need to modify the logics, refer to the process in Optimization Price Waterfall Accelerator Customization and to documentation in Problem Modeling (Optimization Engine), Problem Description, and Problem Tables (Optimization Engine).
...
| Expand | ||
|---|---|---|
| ||
This calculation is the main connection to the external data and most often requires to be modified to accommodate the specifics of the customer data, such as mandatory filters. If the waterfall structure is not the standard one, maybe some columns should be added to the Aggregated table. In this case, you may also change the user inputs to define this mapping, too (see https://pricefx.atlassian.net/wiki/spaces/ACCDEVACC/pages/3850928345#Mapping5933171198/Technical+User+Reference+Optimization+-+Price+Waterfall#Mapping-Tab). The Aggregated table is a result of an aggregation. In some cases, the aggregation can change; for example to replace an average with a median. |
...