Hi Darren
The field is intended for any product that is serializable, i.e. the CSP is interested in tracking the specific instance. So for accessories and consumables it's probably not useful.
Its prime use is certainly for high-value tangible products. But you could imagine (perhaps) digital goods that are not duplicated (think vouchers, but strictly speaking vouchers have their own API and are not really products). Perhaps a non-reusable entitlement for a movie, for example.
There is also an implication that the field could be used for retrieval of the product via a GET with query parameters productSerialNumber=theunique4523576734523
You can of course create characteristics to hold any data you like, but these would be less likely to have explicit search/retrieve semantics.
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: Dec 08, 2021 07:10
From: Darren Wylie
Subject: TMF637 - Product.productSerialnumber
Folks
In the TMF637 API spec the product resource has a field as described below. Was the intention for this that it would be restricted to tangible objects - we are exploring the use of it for a service asset's service id - eg. CV12345632. Or, is there a better field for this value
productSerialNumber A string. Is the serial number for the product. This is typically applicable to tangible
products e.g. Broadband Router
Thanks, Darren
------------------------------
Darren Wylie
BT Group plc
------------------------------