Installation (Optimization - Price Waterfall)

Owned by
Jana Volencová
Jan 24, 2024
3 min read

Price Waterfall Optimization Accelerator deploys a standard Price_Waterfall Model Class that optimizes the elements of a standard waterfall.

In this section, you will find all information to deploy and run a standard waterfall optimization. More details on data mapping, elasticity model creation, and optimization results evaluation are given on the sub-pages.

Prerequisites

Before you start the installation of the Accelerator, ensure you have a transactions Datamart. The Accelerator deployment requires fields mapping to define the price waterfall levels. You need a transactions Datamart with all required waterfall fields. For details see https://pricefx.atlassian.net/wiki/spaces/ACC/pages/4889215502.

To use the Accelerator, you will need:

  • Negotiation Guidance Model – To create and run an optimization model, you need to generate a Negotiation Guidance Model which will provide the price elasticities of the waterfall elements. To run a Negotiation Guidance Model, see https://pricefx.atlassian.net/wiki/spaces/ACC/pages/4889215229. To learn how to ensure compatibility between the Negotiation Guidance Model and the price waterfall optimization, see the next paragraph.

  • Optimization Engine (Image) – To run an optimization model, your partition needs to be allowed to use the Optimization Engine. The Optimization Engine image is automatically enabled on the partition when you deploy the accelerator using PlatformManager, with 2 CPUs and 4Gi memory. Please contact Pricefx Support if you want to increase these values.

  • Pricefx Hurricane 9.2.0 or later – The Accelerator can only be deployed on a partition with at least Hurricane 9.2.0 version of Pricefx.

Version Compatibility

There are some specific compatibility limits to be aware of. They depend on the accelerator version.

Optimization Price Waterfall Accelerator Version

Pricefx Platform

Associated Negotiation Guidance Model

Optimization Price Waterfall Accelerator Version

Pricefx Platform

Associated Negotiation Guidance Model

1.0.1 and before

Minimum 9.2.0 Hurricane

The model must meet these requirements:

  • It is based on a Model Type (Price Optimization Package Accelerator, any version).

  • It is of the kind Segmentation.

  • It has calculated elasticity.

  • If the user can choose the elasticity function, the choice must be Exponential (for the oldest versions, it is the only available elasticity function).

  • The first two levels of segmentation must be the customer group and the product group fields of the Optimization Price Waterfall model (in any order).

1.1

Minimum 10.0 Bee’s Knees

The model must meet these requirements:

  • It is based on a Model Class (Optimization – Negotiation Guidance Accelerator).

  • It has calculated elasticity.

  • The elasticity function must be of the type Sigmoidal.

  • The segmentation levels have to be of type string/text.

  • Negotiation Guidance accelerator version:

    • < 2.0: no restriction

    • from 2.0: the segmentation fields must have the exact same labels and names

Since 1.2

Minimum 10.4 Bee’s Knees

The model must meet these requirements:

  • It is based on a Model Class whose name contains Negotiation_Guidance Accelerator).

  • It has a calculated sigmoidal elasticity for all the product-customer pairs in the scope of optimization.

  • No restriction on the NG version

Deployment

  1. Get access to PlatformManager and target partition, as described in common installation prerequisites.

  2. Go to PlatformManager at https://platform.pricefx.com/ and log in.

  3. Go to Marketplace and find the Optimization - Price Waterfall accelerator.

  4. Click the accelerator tile, select the partition where you want to deploy the accelerator package and confirm the deployment dialog to start.
    For detailed description of all deployment options, see PlatformManager documentation.

  5. Set up Datamart mapping.

     

    • Some rules apply in the mapping:

      • Labels are not mandatory. If not filled, a related name field will be used.

      • Product Group and Customer Group fields must match the segmentation model used by the optimization.

      • Numerical Datamart fields must be configured as extended.

    • More details, particularly if your waterfall does not match the standard Accelerator one, are in https://pricefx.atlassian.net/wiki/spaces/ACC/pages/4889215502.

  6. Click Continue and wait until the deployment is complete.