Optimization - Negotiation Guidance 2.0.0

2.0.0

Nov 24, 2023

Price Gaps are now computed for all features and displayed in a new tab in Step 4 Segmentation, as a dashboard.

PFPCS-6793
PFPCS-6795

Percentile computation has been added to the OE computation library.

PFPCS-6946

There is now visualization of the distribution before/after optimization (at product/customer level) of discount/margin by segment.

PFPCS-6982

There is a new Alignment Type option: Reference based. It allows you to choose a reference value and define price gaps that the similar segments corresponding to another dimension value should reach in average.

PFPCS-7250

Next to discount rate, margin rate can now also be used as optimization target.

PFPCS-7259

At every calculation step, outdated tables are now dropped to avoid confusion about the state of the model.

PFPCS-7273

Improved feature recommendations: features are applicable as for hierarchy even if ignored due to low importance.

PFPCS-7320

Recommendations of alignment are now provided by the accelerator.

PFPCS-7335

The minimal working partition is now [10.4.14,11.0), [11.1.4,).

PFPCS-7393

Logics and Model Class have been renamed: logic name now starts with the prefix "NG2", Model Class name is "Negotiation Guidance 2".

PFPCS-7428

In step 5 Results in the Recommendations tab, there are now Achieved gaps shown, in relation to Current average gaps and Requested gaps.

PFPCS-7445

Values coming from aligned segments are now used to compute recommendations and impact.

PFPCS-7468

To make the process of setting Negotiation Guidance smoother and faster, tooltips have been added in the UI and wording has been improved.

PFPCS-7486

The latest version of Optimization Engine (v2) is now used in Negotiation Guidance, with resources set to 4 CPU and 8 Gi memory.

PFPCS-7493

Default preferences for layout are now part of the accelerator release.

PFPCS-7507

Calls of throw new RuntimeException() are replaced now with api.throwException() that is specifically designed for this purpose.

PFPCS-7512

In Results, there is a new table Segment Alignment Impact showing what impact the OE had per segment.

PFPCS-7585

In the Configuration step, colors of the hierarchy graph have been adjusted to create a subtle, yet clear palette.

PFPCS-7617

Selecting more than 20 segmentation levels leads to an error during creation of the parameters table (after the computation of the segmentation).

PFPCS-6937

In the Definition step, it is possible to select the same column twice and this causes an error only at the Segmentation step. 

PFPCS-7172

A dimension is not visible in the selection matrix even though it was returned with top importance.

PFPCS-7184

In the Analysis step, in order to handle large datasets, cardinality of fields are now fetch in batch and not anymore all at once.  

PFPCS-7318

Price driver listed as numerical were not always numerical. So there is a new category "Other feature" for such cases (meaning the feature was not defined as a dimension in the Datamart).

PFPCS-7319

"Meta" evaluation to check for elasticity does not work correctly as it causes Price Waterfall accelerator to time out.

PFPCS-7339

Optimization percent defaults are wrong: the default CEILING should be 90 : 10.

PFPCS-7367

In the Analysis step > Price Driver Candidate tab, target selected in the Definition step should not appear.

PFPCS-7384

When setting up a hierarchy link (in the hierarchy portlet) between pairs of features, some hierarchies were not displayed.

PFPCS-7417

If there are segments with CoV = 0, mostly coming from the same target for each transaction in the segment, you get an error "Unable to calculate metrics based on elasticity". To avoid such a case, the standard deviation should be capped.

PFPCS-7430

The field List Price in the Definition step does not get a value from the default data mapping.

PFPCS-7458

It is not possible to clear a non mandatory input Weight Measure in the Definition Step when it had a value set during deployment.

PFPCS-7459

When you set a column twice during mapping in Definition step and calculate using "Execute all next steps", the calculation fails only in the last step (instead of immediately).

PFPCS-7476

There is a timeout in the Alignment Review tab in the Result step with ~1m rows of data.

PFPCS-7547

Alignment option is not available if a Weight Measure is defined at the Definition step.

PFPCS-7590