Open APIs

  • 1.  TMF620 Product Offering and Product Offering Term

    TM Forum Member
    Posted 13 days ago
    Hi,

    I am looking to understand how ProductOfferingTerm is defined in TMF620. In going through the API specifications, I see ProductOfferingTerm in both Product Offering and Product Offering Price. Are they the same?

    ProductOfferingTerm in Product Offering is at the same level as Product Offering Price
    ProductOfferingTerm in Product Offering Price is one level below Product Offering Price

    What is ProductOfferingTerm? When is the data populated into ProductOfferingTerm? Any examples would be appreciated.

    ------------------------------
    Nirmal Kumar Ravindran
    Salesforce
    ------------------------------


  • 2.  RE: TMF620 Product Offering and Product Offering Term

    TM Forum Member
    Posted 12 days ago
    Hi Nirmal

    In the current Open API model, the ProductOfferingTerm (POT) is very much a skeleton resource. It is embedded, as you stated, in both PO and in POP, implying that you can apply a term at the offering level or at an individual price level.
    Examples of commercial terms might be:
    • Commitment period - customer promises to keep the product for 2 years, and will be subject to early termination fee if product was ceased or downgraded before end of period
    • Rate stability - customer promises to use the product at a certain level, if usage dips below that level customer will be subject to a penalty fee
    But the current model does not allow such term semantics to be modeled. Seemingly, there should be a link between the POT and AgreementSpecification (and between corresponding ProductTerm and AgreementItem at inventory level).

    Hope it helps

    P.S. apologies for the delay and the fact that you had to re-post the question.

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



  • 3.  RE: TMF620 Product Offering and Product Offering Term

    TM Forum Member
    Posted 6 days ago
    Thanks Jonathan. This helps. So essentially in the TMF definition of Product Offering Term, there is no parameter to say what type this is - Commitment term, rate stability term etc. Is there a default assumption to be made when Product Offering Term data is available.

    ------------------------------
    Nirmal Kumar Ravindran
    Salesforce
    ------------------------------



  • 4.  RE: TMF620 Product Offering and Product Offering Term

    TM Forum Member
    Posted 12 days ago
    It is also worth looking at the SID ABE corresponding to the API. In the Product SID documentation you will find further information on the various "Terms".
    I often find that the SID has more information than the related API.


    ------------------------------
    Matthieu Hattab
    Altibox AS
    ------------------------------



  • 5.  RE: TMF620 Product Offering and Product Offering Term

    TM Forum Member
    Posted 6 days ago
    Thanks Matthieu. I went through the SID ABE. However, I am still not clear on how one would identify the type of Product Offering Term. Also, it is not clear on how to interpret this when POT is available under Product Specification and when POT is available under Product Offering.

    ------------------------------
    Nirmal Kumar Ravindran
    Salesforce
    ------------------------------



  • 6.  RE: TMF620 Product Offering and Product Offering Term

    TM Forum Member
    Posted 6 days ago
    Edited by Matthieu Hattab 4 days ago
    Hi Nirmal,

    From what I see in the SID, for ProductOfferingTerm, has no attribute at all.

    digging in the UML models, it says that ProductTerms is associated to agreementTermOrCondition and the association is called ProductTermAppearsAs.You also have CommitmentTermOrCondition. both BE have few attributes: description, number and ValidFor.
    I'd rather have a generic BE and use type to classify the various terms and their expressions (Text, rules, formula...)

    The SID definition forProductOfferingTerm does suggest additional BEs, see below, but they don't exist in the SID documentation
    A condition under which a ProductOffering is made available to Customers. ProductOfferingTerm include ProductOfferingFinancialTerm, which includes such things as acceptable methods of payment, ShipmentTerm, and ServiceTerm.


    As Jonathan pointed out for the related API, it's a skeleton. Your implementation can change the API resources to include (terms) transaction data for your API payloads.

    Lastly, matching API resource name with SID entity name is not always possible.  The author of the API can use different (but similar) name of simply create resource that don't exist at all in SID. Same with attributes.

    ------------------------------
    Matthieu Hattab
    Altibox AS
    ------------------------------