I have a question regarding some conflicting attributes in the Product Offering Price for the Product Catalog.
With regards to TMF620 for the Product Offering - the 'POPCharge' object contains the following attributes:
If I had a monthly charge then I would set recurringChargePeriod=1 & recurringChargePeriodLength=month.
The 'POPCharge' object also contains the 'unitOfMeasure' object (pointing to the schema location 'Quantity') that contains the following attributes:
In the example, in the TMF620 the example identifies the 'amount=1' & 'unit= Month'.
Would I be correct in assuming that although the recurringChargePeriod/recurringChargePeriodLength and unitOfMeasure:amount/unit are doing the same thing (in my given example), the intention was intended to be slightly different?
For example, although the charge is monthly; the unitOfMeasure, is attempting to measure something other than the recurring duration (monthly), such as the number of inclusive data Mbps I have included as part of this product offering. Is this a correct assumption?
Many thanks in advance
I'm also currently working on this topic. My interpretation is that the unitofMeasure describes the unit for which a charge is valid. This way, you can describe prices for different units of a product. For example, one piece can cost 10 EUR and a package can cost 50 EUR. Piece and package are the units. The "recurring" parameters are identical.
Hi Pete, I think the unit of measure is important in combination with the period parameters. If you want to order a product and it`s available in different packages ( piece, package(s), pallet -->or better in your example: KBit/s, MBit/s, GBit/s...).
see https://engage.tmforum.org/discussion/tmf-637-how-to-present-value-of-allowance-priceso yes, the POP can also price a given allowance, like €7.99 for 40 GB of mobile data, or €1 for extra 5GB on top of the 40GB in case customer has exceeded their allowance/bucket.you also have several example of how to use price with allowance in GB922 - Product.