Multi level decisioning
Hi,
We have a business requirement where we need to to show a plan(lets say an internet plan) in real-time channels like Internet banking portal and mobile app. Once plan is displayed and customer selects the plan then we need to so the corresponding features for that plan to the customer.
We are using Pega 8.5 NBA designer and Plans & Features are created as different decision data under Plan and feature group (issue/group) respectively. Moreover, plan and feature have their own eligibility criteria.
Now my question is what is the best approach to implement this requirement
1. Make a single call from real-time channel(to CDH) to determine both plan and features at the same time in a single strategy execution and let Internet portal handle when to show feature corresponding to plan.
or
2.Make 2 calls from real-time channel(to CDH) and as a result 2 strategy execution. First one to determine Plans and then another calls to determine features.
Victor
Pegasystems Inc.
IN
Hi @victor
Is it not possible to have features be an attribute of a plan?
May be you have a valid use case, but I find it difficult to imagine when can one plan have different features. Do you mind explaining that in a bit more detail?
-Thanks!
Cognizant Technology solution
US
Hi @kamag
Here are some example
- Plan: XXTV
- Feature: Additional channel package, HD channel package,Optional movie package, premium movie package, TV equipment etc
and even though these features are linked with the plan but they also have their own eligibility rules based on customer data.
Hope that helps..
Victor
Pegasystems Inc.
GB
My reading of this is that features are optional, things a user can choose to add to a Plan. This would mean things like 10GB data would not be a feature, while things like “Apple music” or “Free international Roaming” would be features.
On this assumption, there are three ways we handle similar situations in NBA Advisor, maybe these could be considered for your situation:
My reading of this is that features are optional, things a user can choose to add to a Plan. This would mean things like 10GB data would not be a feature, while things like “Apple music” or “Free international Roaming” would be features.
On this assumption, there are three ways we handle similar situations in NBA Advisor, maybe these could be considered for your situation:
- Create Actions for the Plan and Actions for the features. Then run the Plan and the Features through the Strategy Framework, and then based on the Plan filter out the “Incompatible” Features and recommend the best Feature. If you want to let the user then pick features manually, which we call “Negotiation”, pass in the Plan as Context and return all the compatible features. This is the best solution if you want to leverage CDH modelling for the Features. This is the approach NBA Advisor takes to “Add-Ons”.
- Create Actions only for the Plan, and run only the Plan through the Strategy Framework, and recommend the Customer the best Plan. If the customer accepts this plan, have the Channel make a call to the Catalog with the Plan’s Product ID and let the Catalog return a list of Features, and then let the client choose the options. This is the best solution if there is no CDH modelling in the feature determination. This is the approach NBA Advisor takes to “Product configuration”.
- Create the feature as options on the Plan, by creating an Action for the Plan, and run the Plan through the Strategy, and use a Strategy extension to set the Features as options on the Plan Action. This is the most complex, but does give flexibility. This is the best approach where CDH modelling is not needed on features, but you still want CDH to determine the Features (maybe there isn’t scope to involve the Catalog). This is the approach NBA Advisor takes to “Configurable plans”.
I can elaborate on any of these points if required, just reach out.
John Hadwin.