We should revisit this in light of the introduction of
ResourceFunction . The purpose and function of a
PricingLogicAlgorithm (PLA) maps nicely to the concept of a
ResourceFunction (something which takes input to produce output). This has the benefit of making PLAs used in
ProductOfferingPrice first class resources with a suite of APIs to support them (TMF639, TMF634, TMF664).
In fact this is how we implemented PLAs in our open source
SigScale OCS a few years ago acting on the guidance of the late
@John Reilly. Also, with his further guidance, we used the
MatrixCharacteristic pattern to manage tariff tables as collections of
LogicalResources representing rows.
------------------------------
Vance Shipley
SigScale
------------------------------
Original Message:
Sent: Oct 11, 2020 09:56
From: Jonathan Goldberg
Subject: TMF620 Product Offering Price API - Usage Specification information
Hi
In the Open API world, Product Offering Price (catalog) and the instantiation (Product Price, Product Order Price) cover usage, recurring, and onetime.
For complex price schemes the catalog has an opaque reference to pricing logic algorithm (PLA), but the details of the PLA are not surfaced in the API model. A PLA could rate usage, recurring, or onetime.
Not sure if we have plans to enhance the Open API model in this area.
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.
Original Message:
Sent: Oct 05, 2020 10:21
From: Cristina Keserii
Subject: TMF620 Product Offering Price API - Usage Specification information
Hello,
I have noticed that the Product Usage Specification information linked to a Usage Product Offering Price Charge is not exposed in the Product Offering Price APIs.
------------------------------
Cristina Keserii
IBM Corporation
------------------------------