This section presents four business use cases with range tables to model tiered pricing in the pricing logic:
|
Example |
Description |
Boundary |
Computation Mode |
|
#1 |
Tiered pricing for telecommunications |
Last range is unbounded |
Range Size Cumulative |
|
#2 |
Tiered pricing for transports |
Last range is bounded |
Single |
|
#3 |
Tiered pricing for loyalty management |
|
|
|
#4 |
Spending status monitoring |
Last range is unbounded |
n/a |
You can configure the pricing logic by creating a range table or a set of range tables added to the pricing catalog of a service provider or by creating subscriber range tables assigned to a subscriber account and dedicated to some provider contracts belonging to this account.
Example
A company sells voice services that apply decreasing tariffs according to the duration of the phone calls.
The first 2 minutes are charged at 0.20 €/minute; The following 4 minutes are charged at 0.1 €/mn. The following 24 minutes are charged at 0.05 €/mn; The following minutes are charged at 0.01 €/mn.
The range table is defined by:
|
Range (in mn) |
Unit Price (defined per mn) |
|
[0, 2] |
0.2 |
|
]2, 6] |
0.1 |
|
]6, 30] |
0.05 |
|
]30, +∞[ |
0.01 |
The following configuration applies:
Choice of a range table class that defines range tables whose last ranges are unbounded. The class specifies an output column named Price for numerical values. The computation mode for the values of this column is "range size cumulative" to add up the prices of each selected range.
Pricing logic concept, in which the final price is the sum of the cumulative price and the unit tariff multiplied by the position in the range that includes the input value (call duration).
Linear Function component to set up the final price: Final price = cumulative price + unit price (input value - lower bound of the current range)
|
Note: Refer to the Logic Component Help for more information about the detailed configuration that corresponds to this example. |
In this example the final prices are computed by the SAP CC system:
|
Call duration |
1 mn |
2 mn |
3 mn |
4 mn |
5 mn |
10 mn |
20 mn |
40 mn |
|
Generated properties |
|
|
|
|
|
|
|
|
|
Unit price |
0.2 |
0.2 |
0.1 |
0.1 |
0.1 |
0.05 |
0.05 |
0.01 |
|
Price (cumulative) |
0 |
0 |
= 0.2 (2-0) = 0.4 |
= 0.4 |
= 0.4
|
= 0.2 (2-0) + 0.1 (6-2) = 0.4 + 0.4 = 0.8 |
= 0.7 |
= 0.7 + 1.2 = 1.9 |
|
Introduced properties |
|
|
|
|
|
|
|
|
|
Lower bound of the range |
0 |
0 |
2 |
2 |
2 |
6 |
6 |
30 |
|
Beyond lower bound |
= 1 - 0 = 1 |
= 2-0 = 2 |
= 3 -2 = 1 |
= 4-2 = 2 |
= 5-2 = 3 |
= 10 - 6 = 4 |
= 20 - 6 = 14 |
= 40 - 3 = 10 |
|
Final prices |
= sum of price (cumulative) and prorated unit price |
|
|
|
|
|
|
|
|
Computed by a component function added to the branch "Is in a range" |
= 0 + 0.2 (1-0) = 0 + 0.2 = 0.2 |
= 0.4 |
= 0.4 + 0.1 (3-2) = 0.4 + 0.1 = 0.5 |
= 0.6 |
= 0.4 + 0.1 (5-2) = 0.4 + 0.3 = 0.7 |
= 0.8 + 0.05 (10-6) = 0.8 + 0.2 = 1.0 |
= 1.4 |
= 1.9 +0.1 = 2.0 |
The previous range table replaces a long price list:
|
Call duration |
Total price |
|
1 mn |
0.20 |
|
2 mn |
0.40 |
|
3 mn |
0.50 |
|
4 mn |
0.60 |
|
5 mn |
0.70 |
|
6 mn |
0.80 |
|
7 mn |
0.85 |
|
8 mn |
0.90 |
|
9 mn |
0.95 |
|
10 mn |
1.00 |
|
... |
... |
Example
A company sells postal services whose parcel postal tariffs are priced according to the weight of the parcel (weight in kilogram) limited to 20 kg.
|
Range |
Gold Price |
|
[0 , 2.5] |
65 |
|
]2.5 , 8] |
102 |
|
]8 , 20] |
139 |
The following configuration applies:
Computation mode: Single
Pricing logic: Flat Function component to set up the final price
The final prices are:
|
Parcel Weight |
-1 |
0 |
2.5 |
3 |
8 |
10 |
50 |
|
Total price |
Denied |
65 |
65 |
102 |
102 |
139 |
Denied |
Example
A company provides customer services and want to manage a loyalty program based on the usage of services, for which cumulative bonus points are attributed to some customers according to the level of price computed for the consumption of services.
The following example provides a second option, for which special bonus attributed under certain conditions are granted to customers (the upper bound of a range is reached or the last range is exceeded).
|
Range |
Bonus Points |
|
[0, 2] |
1 |
|
]2, 4] |
10 |
|
]4, 6] |
20 |
The following configuration applies:
Computation mode: Cumulative
Pricing logic: Flat Function component to add up the single price and the cumulative price
The final prices are (in points):
|
Consumption Level |
1 |
2 |
3 |
4 |
5 |
6 |
10 |
|
Bonus points (cumulative) |
0 |
0 |
1 |
1 |
11 |
11 |
31 |
|
|
|
|
|
|
|
|
|
|
Total bonus (first modeling) |
1 |
1 |
11 |
11 |
31 |
31 |
31 |
|
|
|
|
|
|
|
|
|
|
Total bonus (Second modeling) (*)
(*) Extra Bonus +5 points if the upper bound is reached and Mega Bonus +50 points if the last range is exceeded |
1 |
6 |
11 |
16 |
31 |
36 |
81 |
Example
You implement policy control in your system landscape to ensure fair usage and to optimize the network bandwidth allocation with predefined policy rules.
You must configure a range table and its class to be able to customize the necessary monitoring plans and set up the generation of a spending status based on this range table.
You configure the "RT dedicated to data monitoring" range table that defines the spending thresholds to be associated to a status label defined in the 'Data fair usage' spending status description. The range table is based on the 'RTC dedicated to data monitoring' range tale class.
The range table is defined by:
|
Range (Spending Thresholds) |
LABEL (Spending Status Labels) |
|
[0 -- 2,000] |
QUOTA_OK |
|
]2,000 -- 2,500] |
QUOTA_WARNING |
|
]2,500 -- +∞[ |
QUOTA_REACHED |