Open APIs

 View Only
Expand all | Collapse all

TMF 620 Product Modelling for Additional Chargable Items

  • 1.  TMF 620 Product Modelling for Additional Chargable Items

    Posted May 01, 2024 22:41

    Hi,

    I have this below scenario and need suggestions on what would be the best modelling approach from you experts.

    Say, our company is selling Broadband Internet. I configure this as below.

    Broadband Internet (Simple Product Offering)

          |_____ B/w (Characteristic) -> 100Mbps, 200Mbps ... (Characteristic Values)

          |_____ IPs (Characteristic) -> 8 (default), 16, 24 ... (characteristic Values)

          |_____ Broadband Monthly Fee (RC), Broadband Install Fee (OTC)

    Now, once customer is purchasing the above offering, if they choose 16 IPs instead of default 8 IPs, i want to show additional charge in the bill like Additional IPs charge - $100. So, in order to achieve this, are below approaches correct ? if not, can suggest the best approach.

    Approach 1: Create Additional IPs as another product offering and show it as recommendation during configuration. With this, customer can choose this upsell item and configure the required ips and to this product offering, OTC and RC pricing will be attached. This will be treated as a order item. But i want this product offering to be just a billable offering, the actual provisioning should happen on the parent Broadband Internet offering, which means, during ordering, what ever is the additional IPs chosen will be overwritten on the Broadband Internet parent order item, and this child order item will be automatically completed as soon as the parent order item is completed. The child shouldn't be sent to OSS systems for provisioning activities. Is this a valid approach ?

    Approach 2: Instead of creating a separate product offering like in approach 1, just create an additional charge item which will be additionally added when customer chooses any IPs other than the default 8. This way there is no need to maintain any separate offerings and COM to SOM is much more convenient. But the downside is, if on day 2 customer want to terminate this additional ips and go back to default 8 ips, i don't know how straight forward is the approach.

    Thank you for taking your time to reading it.



    ------------------------------
    Mahesh Kothamasu
    SP Telecommunications Pte Ltd
    ------------------------------


  • 2.  RE: TMF 620 Product Modelling for Additional Chargable Items

    Posted May 06, 2024 23:22

    Experts, Any advice on this please ?



    ------------------------------
    Mahesh Kothamasu
    SP Telecommunications Pte Ltd
    ------------------------------



  • 3.  RE: TMF 620 Product Modelling for Additional Chargable Items

    TM Forum Member
    Posted May 13, 2024 01:02

    Hi Mahesh

    It seems to me that your challenge is primarily one of bill presentment, rather than the underlying charge calculation. I don't think it's scalable to add offerings and prices for each possible combination of characteristic values.

    So I would isolate this logic in your bill presentment solution, and keep the charge calculation model as simple as possible.

    Please note that I am working on an enhancement to the Product Catalog API TMF620 signatures, to allow easier modeling for parameter-driven pricing. It's early days yet so I cannot tell you when this enhancement will be released.



    ------------------------------
    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.
    ------------------------------



  • 4.  RE: TMF 620 Product Modelling for Additional Chargable Items

    TM Forum Member
    Posted May 14, 2024 06:59
    Edited by Matthieu Hattab May 14, 2024 07:18

    I don't think it's scalable to add offerings and prices for each possible combination of characteristic values.

    This is not necessarily true.

    Our handset supplier generates a very long list of handset product offerings with SKUs representing each combination of colour and memory for a single static recommended price. It's a very long list!

    They deliver to us via a SaaS PIM. that supplier itself works with manufacturer to collect the data and content.

    PS: I didn't realise Mahesh was asking to combine characteristic values (bandwidth charvalues and IP charvalues ), just a way to price extra charges if user select a higher number of IP addresses.



    ------------------------------
    Kind regards,

    Matthieu Hattab
    Lyse Platform
    ------------------------------