Got ya. Thanks for the quick answer!
Original Message:
Sent: Jun 20, 2023 10:36
From: Jonathan Goldberg
Subject: Modeling TMF620 ProductOfferings with different billing cycles in same bundle
I believe that the SID has a representation of irregular time period, but I haven't had time to look up the details. For your needs you would have to extend the Open API model to meet specific period definition requirements, I don't see that this is a sufficiently wide business requirement to be reflected in the standard Open API model.
------------------------------
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.
Original Message:
Sent: Jun 20, 2023 10:27
From: Anton Tsapko
Subject: Modeling TMF620 ProductOfferings with different billing cycles in same bundle
Hi Jonathan,
I saw those attributes you point to in tht API specification but I am not quite sure if they suffice the requirement. They are just string and integers. Thus it only allows to build symmetric intervals like:
"recurringChargePeriodType": "month"
"recurringChargePeriodLength": "2"
which means "every two months".
In my case the business dep wishes to flexibly slice the year in non symetric periods like:
- Period 1: January to March (3)
- Period 2: March to October (6)
- Period 3: November to December (3)
or
- Period 1: January to March (3)
- Period 2: April to December (9)
Any ideas on that?
------------------------------
Anton Tsapko
conology
Original Message:
Sent: Jun 20, 2023 10:15
From: Jonathan Goldberg
Subject: Modeling TMF620 ProductOfferings with different billing cycles in same bundle
Hi Anton
I would expect the information about billing period to be exposed on ProductOfferingPrice. And indeed we have these properties, maybe this is what you need?
"recurringChargePeriodType": {
"type": "string",
"description": "The period to repeat the application of the price\nCould be month, week..."
},
"recurringChargePeriodLength": {
"type": "integer",
"description": "the period of the recurring charge: 1, 2, ... .It sets to zero if it is not applicable"
},
------------------------------
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.
Original Message:
Sent: Jun 20, 2023 05:22
From: Anton Tsapko
Subject: Modeling TMF620 ProductOfferings with different billing cycles in same bundle
Hi all,
my question is: Where would I store the information on billing periods for each ProductOffering in (TMF620)?
When building a system that stores Agreements with partners, ProductOfferings of partners and agreed lease PriceModels the business requirement is that abstract groups of ProductOfferings (subscriptions to use infrastructure) like "segments" and "end points" have different billing periods although logically bundled, see picture below. I cannot find the right entity in ProductOffering in (TMF620) to put/connect this information about periods to. The billing period structure can be different for different ProductOfferings in the same bundle. For instance "once a year" or "every quarter" or "4+6+2" (see example below).
I have viewed:
- TMF620_Product_Catalog_Management_API_User_Guide_v4.1.0.pdf
- GB922_Product_v22.5.pdf
- GB922_Common_v22.5.pdf
Example:
Best Regards
Anton
------------------------------
Anton Tsapko
conology
------------------------------