This section details the Model Class and the logics that the List Price 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 Accelerator Customization and to documentation in Problem Modeling (Optimization Engine), Problem Description, and Problem Tables (Optimization Engine).

In this section:

List Price Optimization Model Class

The List Price Optimization Model Class organizes a list of logics to create the model architecture. It is transformed into an UI in the Pricefx platform that is organized in 4 steps:

Definition − Maps the sources of data and filters out invalid values.
Scope − Sets the scope of the optimization.
Configuration − Sets the parameters of the optimization.
Results − Reviews the outputs of the optimization.

There are two types of logics: calculation logics, which write tables in the model, and evaluation logics, whose purpose is only to display some results. The standard Model Class definition is documented in Model Class (MC).

All the logics of the List Price Optimization Accelerator follow a standard naming convention: first, the LP_ prefix, then the step order number and the first letters of the step name, followed by Calc or Eval, depending on the formula's nature, and finally the name of the tab. Additionally, there is a library logic named LP_Lib.

Library

The logic is LP_Lib.

This logic contains functions specifically needed for this Accelerator, including reading its configuration from the application settings, applying user filters to each part of the model, preprocessing data for the charts, and Optimization Engine configuration tools. The elements ParametersUtils, LabelsUtils, and TablesUtils contain the names of numerous elements and fields within the models.

This library is where you can change the names within the model to reflect the user's business vocabulary. You can also write functions here to be used in different parts of the model class.

It is also the place where the definition of the optimization problem can be changed.

Definition Step

There is no calculation logic run in this step. The tabs are Transactions and Costs.

Transactions Tab

The logics are LP_1_Def_Eval_Transactions and LP_1_Def_Eval_Transactions_Configurator.

These logics define the Data Source or Datamart, then the mapping of the entries for the transactions in the configurator. The main logic calls the configurator and the code for the dashboard portlets.

Two portlets show the data that will be materialized in the model (table Aggregated) and the filtered-out rows.

The mapping could be changed if a field is removed or added.

Costs Tab

The logics are LP_1_Def_Eval_Cost and LP_1_Def_Eval_Cost_Configurator.

Scope Step

The calculation logic is LP_2_Sco_Calc_Aggregating and there is one tab called Scope.

Calculation: Aggregating

The logic is LP_2_Sco_Calc_Aggregating.

Scope Tab

The logics are LP_2_Sco_Eval_Scope and LP_2_Sco_Eval_Scope_Configurator.

Configuration Step

The calculation logic is LP_3_Conf_Calc_FilterScope and there are three tabs: Strategy, Alignments, and Advanced Parameters.

Calculation: Filtering

The logic is LP_3_Conf_Calc_FilterScope.

Strategy

The logic is LP_3_Conf_Eval_Strategy_Configurator.

Business Alignments

The logic is LP_3_Conf_Eval_BusinessAlignments_Configurator.

Advanced Parameters

The logic is LP_3_Conf_Eval_AdvancedParameters_Configurator.

Results Step

Calculations: Run Optimization and Prepare Results

Calculation 1: Run Optimization

The logic is LP_4_Res_Calc_RunOptimization.

Calculation 2: Prepare Results

The logic is LP_Res_Calc_PrepareResults.

Impact Tab

The logics are LP_Res_Eval_Impact and LP_Res_Eval_Filter_Configurator. A configurator to set the filters to apply to the dashboard is embedded. This configurator is also used in the tab Details.

Details Tab

The logics are LP_Res_Eval_Details and LP_Res_Eval_Filter_Configurator. A configurator to set the filters to apply to the dashboard is embedded. This configurator is also used in the tab Details.

Glassbox and Drivers Tabs

The logics are LP_Res_Eval_Glassbox and LP_Res_Eval_Drivers.

Evaluation Tab

This tab mocks the model evaluation. More details in the next paragraph Technical User Reference (Optimization - List Price) | Query results.

Model Evaluations

More details about the model evaluations are available here: Model Class (MC) | Evaluation (evaluations). The List Price Optimization Model Class has two evaluations:

query_results, handled by the logic LP_4_Res_Eval_Evaluation;
eval_product_batch, handled by the logic LP_4_Res_Eval_Evaluation_Product_Batch.

Depending on your needs, you can add as many model evaluations as you want on top of those two.

Query results

The logic is LP_Res_Eval_Evaluation.

Product batch

The logic is LP_4_Res_Eval_Evaluation_Product_Batch.