Open APIs

Expand all | Collapse all

TMF620: Product Offering Price Modeling doubts

  • 1.  TMF620: Product Offering Price Modeling doubts

    TM Forum Member
    Posted Mar 22, 2021 09:59

    I'd like to understand in a better way the existing Product Offering Price (POP)
    modeling for TMF620 because in latest TMF620 version, it became a separated resource
    rather than a Product Offering sub-resource.

    Therefore, a POP can exist on its own and, we don't have a direct link points an
    association towards a PO or even a PS but, we still have these elements:
    - ProductOfferingTerm
    - ProductSpecificationCharacteristicValueUse

    So, questions are:
    1) How do we create a POP element and, fulfill these two particular sub-elements if,
    we don't have a field to indicate an association towards a particular PO or PS?
    In other words, if this is a unique resource, (that can be created without association
    towards PO or PS), how can we populate these two sub-elements?

    2) Why don't we have a Characteristic field dedicated to POP element?
    (i.e.: being a separated resource, can't we have new price related characteristics
    associated to it?)

    3) Suppose that we have two POs connected to the same POP and, suppose this POP is configured
    initially with recurring charge as U$ 10 per month. How can an user change the PO
    associated price details (e.g.: change the recurrency frequency or even the price)
    without affecting the other PO?

    Thanks and Regards,

    Marcos Donato da Silva
    Ericsson Inc.

  • 2.  RE: TMF620: Product Offering Price Modeling doubts

    TM Forum Member
    Posted Mar 24, 2021 10:08
    Hi Marcos

    Hopefully I can answer your questions
    1. It's a very good question. I would say that you can only use these if the POP is connected to a specific PO, without reuse.
    2. You could also ask - why don't we have characteristics on PO. In the SID, neither PO nor POP had native characteristics, but rather a restriction of characteristics from underlying product spec. So we have an open CR to add characteristics to PO for API, maybe we need another to add also to POP.
    3. One of the main motivations of having independent POP is to allow re-use. So yes, if you use the same POP in two different POs, the understanding is that you want the same price for these two offerings. To have a different price on one of the offerings you would need to detach the POP from that offering and attach a different POP.
    Hope it helps

    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.