Open APIs

 View Only

  • 1.  TMF651 Agreement-Management is missing a reference to TMF738-RevenueSharingModels

    Posted Apr 18, 2024 09:07
    Edited by Anton Tsapko Apr 18, 2024 12:05
    Hi all,
     
    I am trying to implement a revenue sharing model using TMF738/736 Revenue Sharing Model and TMF651 Agreement Management. 
     
    In my use-case / domain a company has an agreement with its parter P1 (one partner) to lease network infrastrucutre (components) according to a ProductCatalog of P1.
    Additionally to that the lease conditions the agreement contains or defines a revenue sharing model. The revenue that is created 
    with internet products that are "produced" using the leased network infrastructure.
     
    I studied the TMF651 Agreement Management API and I cannot see a possibility to reference a Revenue Sharing Model in it. (I can see the possiblity to reference a ProductOffering in the AgreementItem though). I think there should be a RSModelRef in the AgreementItem. So that the agreement entity could "hold" all the conditions for one partner.
     
    Is this an known issue? If yes, will there be a possiblity in future to reference a RSM from an Agreement Entity?

    Best Regards

    Anton



    ------------------------------
    Anton Tsapko
    conology
    ------------------------------



  • 2.  RE: TMF651 Agreement-Management is missing a reference to TMF738-RevenueSharingModels

    Posted Apr 21, 2024 03:07

    Hi Anton

    Bear in mind that Agreement is a base class, that can cover all types of agreement. I don't think it would be a good idea to add an explicit reference to a specific business scenario, such as rev-share. Probably would be better to define a dedicated subclass for rev-sharing agreement, and then refer to the sharing model from the subclass.



    ------------------------------
    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: TMF651 Agreement-Management is missing a reference to TMF738-RevenueSharingModels

    Posted May 17, 2024 08:33

    Hello Jonathan, 

    thanks for the response.

    I still do not quite understand how this would work with the current Agreement API. In my case I have a Front-End which the user uses to create an Agreement. Part of this agreement are pricing models AND reveneu-sharing pricing. 

    As I understand it from your answer, if I can take the current API definition and define a sub-class using @type attribute, I could be able to add a new attribute to the API that would hold a reference to the rev-sharing price models.  The problem is, if I add such a sub-class, which would of course be a custom one, we add it in the Front-End only. The backends and further systems would expect a official TMF base-class structure and thus dismiss the additional custom attribute.

    So to solve that problem, we would need to alter the code in the back-end and potentially in many other places. Which basically means, that everything would work with a custom definition, which completly bypasses the standardisation idea.

    Maybe I am missing something, or getting it completly wrong?

    How would that work?

    https://raw.githubusercontent.com/tmforum-apis/TMF651_AgreementManagement/master/TMF651-Agreement-v4.0.0.swagger.json

    Best Regards

    Anton



    ------------------------------
    Anton Tsapko
    conology
    ------------------------------

    Original Message


Related Content