Open APIs

If there is a bundled product offering consisting of a number of products, services and resources, then the bundled price could be at the Product Offering level.  But how do we get the breakup of all the prices of services and resources?  Further, a few services and resources could be optionally opted by the customer, so this breakup becomes essential.  There could be certain discounts applicable if customer opts for a specific combinations of services and resources.  How to handle these scenarios? Do we create ProductOffering for each service and resource separately also? 

Regards

Hi Sudhir,

The hierarchy is PO - > Product Spec-> Service Specs (CFS and RFS) and also PS - > Resource if a Physical and/or Logical resource is involved. 

As you pointed out the price is defined at the PO. It can also be defined at the PS so that the services and resources  under that PS are priced against that PS (Can also be based on the characteristic value selection at the PS). Multiple PS can be under one PO. So some of the PS can have the cardinality value 0..1 and  based on the selection or non-selection of that PS (meaning the services under the PS - which are actually hidden during the selling process), the pricing is rolled up to the PO level. The other approach is as you put it. Define child POs and bundle them into a bundle PO. Sometimes we use a combination of both the approaches. 

Regards,

If there is a bundled product offering consisting of a number of products, services and resources, then the bundled price could be at the Product Offering level.  But how do we get the breakup of all the prices of services and resources?  Further, a few services and resources could be optionally opted by the customer, so this breakup becomes essential.  There could be certain discounts applicable if customer opts for a specific combinations of services and resources.  How to handle these scenarios? Do we create ProductOffering for each service and resource separately also? 

Regards

Hi

My understanding from SID.

• is that a simpleProductOffering is made from a single ProductSpecification. A SimpleProductOffering can't be made from several ProductSpecifications but only 1. A BundledProductOffering is not directly made from several ProductSpecifications but at the end bundles several SimpleProductOffering.

• price is only at PO level, not at ProductSpecification level, not at CFS level, not at RFS level, not at Resource level

------------------------------
olivier arnaud
Orange

Original Message:
Sent: Feb 23, 2024 08:35
From: Sri-Jagadish (Jag) Baddukonda
Subject: Price Breakup for Bundled Product Offering

Hi Sudhir,

The hierarchy is PO - > Product Spec-> Service Specs (CFS and RFS) and also PS - > Resource if a Physical and/or Logical resource is involved. 

As you pointed out the price is defined at the PO. It can also be defined at the PS so that the services and resources  under that PS are priced against that PS (Can also be based on the characteristic value selection at the PS). Multiple PS can be under one PO. So some of the PS can have the cardinality value 0..1 and  based on the selection or non-selection of that PS (meaning the services under the PS - which are actually hidden during the selling process), the pricing is rolled up to the PO level. The other approach is as you put it. Define child POs and bundle them into a bundle PO. Sometimes we use a combination of both the approaches. 

Regards,

------------------------------
Sri-Jagadish (Jag) Baddukonda
Bell Canada

Original Message:
Sent: Feb 22, 2024 04:29
From: Dr. Sudhir Kumar Mittal
Subject: Price Breakup for Bundled Product Offering

If there is a bundled product offering consisting of a number of products, services and resources, then the bundled price could be at the Product Offering level.  But how do we get the breakup of all the prices of services and resources?  Further, a few services and resources could be optionally opted by the customer, so this breakup becomes essential.  There could be certain discounts applicable if customer opts for a specific combinations of services and resources.  How to handle these scenarios? Do we create ProductOffering for each service and resource separately also? 

Regards

------------------------------
Dr. Sudhir Kumar Mittal
Jio Platforms Limited
------------------------------

Hi Olivier,

Please use a composite PS underneath a PO and you can have more than one PS.

Regarding price, you need to extend the model. If you just use only POP, then the number of PO s is too many and that will have a  negative impact on other entities.

The end objective is to use the standards, make the implementation a success and improve the standard as a continuous process :-) 

Regards,

Hi

My understanding from SID.

• is that a simpleProductOffering is made from a single ProductSpecification. A SimpleProductOffering can't be made from several ProductSpecifications but only 1. A BundledProductOffering is not directly made from several ProductSpecifications but at the end bundles several SimpleProductOffering.

• price is only at PO level, not at ProductSpecification level, not at CFS level, not at RFS level, not at Resource level

Hi Sudhir,

The hierarchy is PO - > Product Spec-> Service Specs (CFS and RFS) and also PS - > Resource if a Physical and/or Logical resource is involved. 

As you pointed out the price is defined at the PO. It can also be defined at the PS so that the services and resources  under that PS are priced against that PS (Can also be based on the characteristic value selection at the PS). Multiple PS can be under one PO. So some of the PS can have the cardinality value 0..1 and  based on the selection or non-selection of that PS (meaning the services under the PS - which are actually hidden during the selling process), the pricing is rolled up to the PO level. The other approach is as you put it. Define child POs and bundle them into a bundle PO. Sometimes we use a combination of both the approaches. 

Regards,

If there is a bundled product offering consisting of a number of products, services and resources, then the bundled price could be at the Product Offering level.  But how do we get the breakup of all the prices of services and resources?  Further, a few services and resources could be optionally opted by the customer, so this breakup becomes essential.  There could be certain discounts applicable if customer opts for a specific combinations of services and resources.  How to handle these scenarios? Do we create ProductOffering for each service and resource separately also? 

Regards

I agree with you @olivier arnaud.  That is why I had initiated the post.  

@Jag Baddukonda, I think any product specification, by virtue of it being specification should not have price associated with it.  Offering is the one for the customer to go for, and there the price is making sense.  Regarding multiple product specifications under one product offering, it is not allowed directly, but you rightly pointed out that it could be a hierarchy.  

My question still remains, do we create a product offering for each chargeable resource or service with specific price? 

Regards,

Hi Olivier,

Please use a composite PS underneath a PO and you can have more than one PS.

Regarding price, you need to extend the model. If you just use only POP, then the number of PO s is too many and that will have a  negative impact on other entities.

The end objective is to use the standards, make the implementation a success and improve the standard as a continuous process :-) 

Regards,

Hi

My understanding from SID.

• is that a simpleProductOffering is made from a single ProductSpecification. A SimpleProductOffering can't be made from several ProductSpecifications but only 1. A BundledProductOffering is not directly made from several ProductSpecifications but at the end bundles several SimpleProductOffering.

• price is only at PO level, not at ProductSpecification level, not at CFS level, not at RFS level, not at Resource level

Hi Sudhir,

The hierarchy is PO - > Product Spec-> Service Specs (CFS and RFS) and also PS - > Resource if a Physical and/or Logical resource is involved. 

As you pointed out the price is defined at the PO. It can also be defined at the PS so that the services and resources  under that PS are priced against that PS (Can also be based on the characteristic value selection at the PS). Multiple PS can be under one PO. So some of the PS can have the cardinality value 0..1 and  based on the selection or non-selection of that PS (meaning the services under the PS - which are actually hidden during the selling process), the pricing is rolled up to the PO level. The other approach is as you put it. Define child POs and bundle them into a bundle PO. Sometimes we use a combination of both the approaches. 

Regards,

If there is a bundled product offering consisting of a number of products, services and resources, then the bundled price could be at the Product Offering level.  But how do we get the breakup of all the prices of services and resources?  Further, a few services and resources could be optionally opted by the customer, so this breakup becomes essential.  There could be certain discounts applicable if customer opts for a specific combinations of services and resources.  How to handle these scenarios? Do we create ProductOffering for each service and resource separately also? 

Regards

Hi Sudhir,

The hierarchy is PO - > Product Spec-> Service Specs (CFS and RFS) and also PS - > Resource if a Physical and/or Logical resource is involved. 

As you pointed out the price is defined at the PO. It can also be defined at the PS so that the services and resources  under that PS are priced against that PS (Can also be based on the characteristic value selection at the PS). Multiple PS can be under one PO. So some of the PS can have the cardinality value 0..1 and  based on the selection or non-selection of that PS (meaning the services under the PS - which are actually hidden during the selling process), the pricing is rolled up to the PO level. The other approach is as you put it. Define child POs and bundle them into a bundle PO. Sometimes we use a combination of both the approaches. 

Regards,

------------------------------
Sri-Jagadish (Jag) Baddukonda
Bell Canada

Original Message:
Sent: Feb 22, 2024 04:29
From: Dr. Sudhir Kumar Mittal
Subject: Price Breakup for Bundled Product Offering

If there is a bundled product offering consisting of a number of products, services and resources, then the bundled price could be at the Product Offering level.  But how do we get the breakup of all the prices of services and resources?  Further, a few services and resources could be optionally opted by the customer, so this breakup becomes essential.  There could be certain discounts applicable if customer opts for a specific combinations of services and resources.  How to handle these scenarios? Do we create ProductOffering for each service and resource separately also? 

Regards

------------------------------
Dr. Sudhir Kumar Mittal
Jio Platforms Limited
------------------------------

Multiple PS can be under one PO

it is true that some BSS do allow your scenario, this is not true with TM Forum SID:

• An simple PO has min 1 and max 1 PS
• An bundle PO has min 0 and max 0 PS

you can use composite PS but modeling POP with a composite PS is asking for trouble. I have yet to see an example that makes sense from a marketing view (which is what PO and POP are)

Hi Sudhir,

The hierarchy is PO - > Product Spec-> Service Specs (CFS and RFS) and also PS - > Resource if a Physical and/or Logical resource is involved. 

As you pointed out the price is defined at the PO. It can also be defined at the PS so that the services and resources  under that PS are priced against that PS (Can also be based on the characteristic value selection at the PS). Multiple PS can be under one PO. So some of the PS can have the cardinality value 0..1 and  based on the selection or non-selection of that PS (meaning the services under the PS - which are actually hidden during the selling process), the pricing is rolled up to the PO level. The other approach is as you put it. Define child POs and bundle them into a bundle PO. Sometimes we use a combination of both the approaches. 

Regards,

If there is a bundled product offering consisting of a number of products, services and resources, then the bundled price could be at the Product Offering level.  But how do we get the breakup of all the prices of services and resources?  Further, a few services and resources could be optionally opted by the customer, so this breakup becomes essential.  There could be certain discounts applicable if customer opts for a specific combinations of services and resources.  How to handle these scenarios? Do we create ProductOffering for each service and resource separately also? 

Regards

If there is a bundled product offering consisting of a number of products, services and resources, then the bundled price could be at the Product Offering level.  But how do we get the breakup of all the prices of services and resources?  Further, a few services and resources could be optionally opted by the customer, so this breakup becomes essential.  There could be certain discounts applicable if customer opts for a specific combinations of services and resources.  How to handle these scenarios? Do we create ProductOffering for each service and resource separately also? 

Regards