The current Cost Model wizard offers 4 alternatives to users:

1. AWS cost model
2. GCP cost model
3. Azure cost model
4. Red Hat OpenShift cost model

The first 3 are actually shortcuts to what one can achieve by using the 4th: if an AWS, GCP or Azure cost model is selected in the first screen in the wizard, Cost Management will automagically:

• a) Show only Sources of the respective cloud
• b) Distribute raw costs
• c) Allow users to set a markup or discount
• d) Distribute costs based on CPU usage 

(a) and (b) are convenient, (c) is obvious because it's explicit and (d) is non-obvious. This causes that sometimes users ask questions such as "how many cost models do I need? One [AWS/Azure/GCP/OpenShift] or two [AWS/Azure/GCP + OpenShift]?

The Red Hat OpenShift wizard can actually include everything: cloud costs (AWS/Azure/GCP), markups/discounts, additional ("supplementary") costs which can be defined in a price list, and you can decide whether you want to do the cost distribution based on CPU or RAM usage.

Also, in the Red Hat OpenShift cost model, the "raw cost" term seems to confuse some users, since it's not obvious that we are distributing the costs coming from the cloud in addition to the costs defined in the price list.

In fact, if one wants to distribute raw costs based on memory (i. e. a pure AWS/Azure/GCP cloud cost distribution but based on RAM instead of CPU usage), the only way is to create a Red Hat OpenShift cost model with an empty price list (actually, one price list rate with zero value needs to be created, even though it will not add any additional cost).

Can we simplify our cost model wizard so that we get rid of the shortcuts and make it actually optional to create a price list? That way, we will get rid of the "how many cost models do I need?" question?

Also, we should explain better what the "raw costs" term is, or find a better-known or easier to understand term.