Open APIs

Hi Team,

Need your suggestion on below use-case,

There is bundle product offering (id b1) contains two product offering

1. Postpaid mobily
2. Broadband

Bear in mind that the promotion API describes rules for applying promotions. The API does not manage the runtime instantiation of the benefits that accrue from application of the promotion rules. Those benefits will be instantiated products or product prices.

It's the responsibility of your implementation of (say) the Order API (TMF622) to run the promotion rules when anything significant "happens", and to apply or revoke the promotion benefit accordingly.

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.

Original Message:
Sent: Dec 18, 2023 04:43
From: subhanshu shukla
Subject: TMF 671 Promotion and product inventory

Hi Team,

Need your suggestion on below use-case,

There is bundle product offering (id b1) contains two product offering

1. Postpaid mobily
2. Broadband

------------------------------
subhanshu shukla
Lead Digital Architect
Bharti Airtel Ltd
------------------------------

Hi Team,

Need your suggestion on below use-case,

There is bundle product offering (id b1) contains two product offering

1. Postpaid mobily
2. Broadband

There are many ways to model this. For instance:

Let's assume these 2 product offerings already exist:

1. mobile postpaid, Id=PO1
2.  broadband, Id=PO2

Then you just have to setup your bundle:

1. create your bundle, Id=PO1
2. add components to the bundle:
   1.  mobile postpaid, Id=PO1
   2.  broadband, Id=PO2
3. add the discount POP to bundle PO1
4. optional: add a product term to the bundle (PO1) to charge a penalty when customer terminate the bundle before the end of commitment period.

so if customer terminates the bundle the associated discount will be terminated automatically.

My 2 cents

Hi Team,

Need your suggestion on below use-case,

There is bundle product offering (id b1) contains two product offering

1. Postpaid mobily
2. Broadband

Thanks Matthieu,

There are many ways to model this. For instance:

Let's assume these 2 product offerings already exist:

1. mobile postpaid, Id=PO1
2.  broadband, Id=PO2

Then you just have to setup your bundle:

1. create your bundle, Id=PO1
2. add components to the bundle:
   1.  mobile postpaid, Id=PO1
   2.  broadband, Id=PO2
3. add the discount POP to bundle PO1
4. optional: add a product term to the bundle (PO1) to charge a penalty when customer terminate the bundle before the end of commitment period.

so if customer terminates the bundle the associated discount will be terminated automatically.

My 2 cents

Hi Team,

Need your suggestion on below use-case,

There is bundle product offering (id b1) contains two product offering

1. Postpaid mobily
2. Broadband

The Open API initiative deals with APIs, i.e. exposed models and behaviors, not with internal implementation. It's entirely up to you (or your vendor) how to manage instantiated promotions.

As a representative from a vendor, I am not at liberty to explain exactly what we do in our software. But I don't think I'm giving away any trade secrets by saying that the product inventory is the most likely place to keep track of the granted benefits.

Having said that, the ODA spec for Product Inventory doesn't make a direct reference to promotion instances, so maybe they have a different view.

https://www.tmforum.org/resources/technical-specification/tmfc005-product-inventory-v1-0-1/

Thanks Matthieu,

There are many ways to model this. For instance:

Let's assume these 2 product offerings already exist:

1. mobile postpaid, Id=PO1
2.  broadband, Id=PO2

Then you just have to setup your bundle:

1. create your bundle, Id=PO1
2. add components to the bundle:
   1.  mobile postpaid, Id=PO1
   2.  broadband, Id=PO2
3. add the discount POP to bundle PO1
4. optional: add a product term to the bundle (PO1) to charge a penalty when customer terminate the bundle before the end of commitment period.

so if customer terminates the bundle the associated discount will be terminated automatically.

My 2 cents

Hi Team,

Need your suggestion on below use-case,

There is bundle product offering (id b1) contains two product offering

1. Postpaid mobily
2. Broadband

Thanks Matthieu,

There are many ways to model this. For instance:

Let's assume these 2 product offerings already exist:

1. mobile postpaid, Id=PO1
2.  broadband, Id=PO2

Then you just have to setup your bundle:

1. create your bundle, Id=PO1
2. add components to the bundle:
   1.  mobile postpaid, Id=PO1
   2.  broadband, Id=PO2
3. add the discount POP to bundle PO1
4. optional: add a product term to the bundle (PO1) to charge a penalty when customer terminate the bundle before the end of commitment period.

so if customer terminates the bundle the associated discount will be terminated automatically.

My 2 cents

Hi Team,

Need your suggestion on below use-case,

There is bundle product offering (id b1) contains two product offering

1. Postpaid mobily
2. Broadband

My general opinion is that this Promotion API is a bit isolated. All we have is an API, no ODA component, no SID, ETOM etc.
the API doc says "Normally, Promotion is not regarded as one type of product or product offering...

This is in contradiction with what the SID has written (from the SID entity catalogue):

"The Product Promotion ABE describes the publication of a ProductOffering to encourage Parties to buy, rent, or in some other way procure the offering."
... It is often applied when the customer buys the product offerings with the price or amount surpassing the certain limit."
=> that definition and the examples provided in the API guide describe more a loyalty scheme than a promotion. 
There is also example of promotions in the SID (GB922 Product) that explain how it works with product.

I've used promotion as defined in the Product domain. (This also depends largely on your BSS/CRM.)

In your scenario, I'd say you need the product inventory to have a relationship between the product offers, the promotion and the product terms.
Our process (simplifed in a nushelf):

1. customer terminates a product and provide a termination date
2. system checks if product is (or is connected to) a promotion
   1. YES: system checks product terms, let's make it simple: 12-month commitment, first 3 months for free. Pay prorated fee.
3. system check if customer is still in a binding period
   1. YES: system calculates the termination fee (based on terms, termination date etc)
4. customer is presented the fee amount and can accept (continue with check out) or abandon.
   1. YES: the termination fee (one-time charge) is added to the order and will be added on the customer's next invoice. (or pay everything online at checkout)

in essence, your product inventory is where you need to create that connection with the promotion and its terms

Thanks Matthieu,

There are many ways to model this. For instance:

Let's assume these 2 product offerings already exist:

1. mobile postpaid, Id=PO1
2.  broadband, Id=PO2

Then you just have to setup your bundle:

1. create your bundle, Id=PO1
2. add components to the bundle:
   1.  mobile postpaid, Id=PO1
   2.  broadband, Id=PO2
3. add the discount POP to bundle PO1
4. optional: add a product term to the bundle (PO1) to charge a penalty when customer terminate the bundle before the end of commitment period.

so if customer terminates the bundle the associated discount will be terminated automatically.

My 2 cents

Hi Team,

Need your suggestion on below use-case,

There is bundle product offering (id b1) contains two product offering

1. Postpaid mobily
2. Broadband

Any modification expected in Gen5 version of productInventory?

My general opinion is that this Promotion API is a bit isolated. All we have is an API, no ODA component, no SID, ETOM etc.
the API doc says "Normally, Promotion is not regarded as one type of product or product offering...

This is in contradiction with what the SID has written (from the SID entity catalogue):

"The Product Promotion ABE describes the publication of a ProductOffering to encourage Parties to buy, rent, or in some other way procure the offering."
... It is often applied when the customer buys the product offerings with the price or amount surpassing the certain limit."
=> that definition and the examples provided in the API guide describe more a loyalty scheme than a promotion. 
There is also example of promotions in the SID (GB922 Product) that explain how it works with product.

I've used promotion as defined in the Product domain. (This also depends largely on your BSS/CRM.)

In your scenario, I'd say you need the product inventory to have a relationship between the product offers, the promotion and the product terms.
Our process (simplifed in a nushelf):

1. customer terminates a product and provide a termination date
2. system checks if product is (or is connected to) a promotion
   1. YES: system checks product terms, let's make it simple: 12-month commitment, first 3 months for free. Pay prorated fee.
3. system check if customer is still in a binding period
   1. YES: system calculates the termination fee (based on terms, termination date etc)
4. customer is presented the fee amount and can accept (continue with check out) or abandon.
   1. YES: the termination fee (one-time charge) is added to the order and will be added on the customer's next invoice. (or pay everything online at checkout)

in essence, your product inventory is where you need to create that connection with the promotion and its terms

Thanks Matthieu,

There are many ways to model this. For instance:

Let's assume these 2 product offerings already exist:

1. mobile postpaid, Id=PO1
2.  broadband, Id=PO2

Then you just have to setup your bundle:

1. create your bundle, Id=PO1
2. add components to the bundle:
   1.  mobile postpaid, Id=PO1
   2.  broadband, Id=PO2
3. add the discount POP to bundle PO1
4. optional: add a product term to the bundle (PO1) to charge a penalty when customer terminate the bundle before the end of commitment period.

so if customer terminates the bundle the associated discount will be terminated automatically.

My 2 cents

Hi Team,

Need your suggestion on below use-case,

There is bundle product offering (id b1) contains two product offering

1. Postpaid mobily
2. Broadband