Hi Shino
I would say that it is a separation of concerns. You wouldn't necessarily want to expose the complexity of the network to the BSS layer. And in the BSS layer there is commerce-related stuff (pricing, promotions, bundles) that are completely extraneous to the network layer.
The relationship between product spec and service spec (even CFS) is not necessarily 1:1, and similarly for the mapping between product and service characteristics. For example a product characteristic value (Bandwidth) could be mapped into two different services (copper and fiber). Indeed it could be argued that the Open API model does not (currently) have sufficient information to make this mapping feasible (the SID does include such mapping), so there is room for improvement :) .
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: Jul 21, 2020 02:17
From: Shino Jacob
Subject: TMF 620 and TMF 633
Thanks Lester,
That was informative.
But that gives birth to another question, Why do we need Service Spec ,if we can express everything in PS. I know its designed the other way around, but why can't we design in such a way that PO contains all the details.
------------------------------
Shino Jacob
Infosys
Original Message:
Sent: Jul 20, 2020 08:49
From: Lester Thomas
Subject: TMF 620 and TMF 633
Hi Shino,
There is a good thread on this here: https://engage.tmforum.org/communities/community-home/digestviewer/viewthread?GroupId=31&MessageKey=e6c62bed-e884-412a-ae15-3ea39f7b8575&CommunityKey=d543b8ba-9d3a-4121-85ce-5b68e6c31ce5&tab=digestviewer&ReturnUrl=%2Fcommunities%2Fcommunity-home%2Fdigestviewer%3FListKey%3Db78bb58e-1261-46b1-b498-475445e46213
Basically a Digital Service Provider builds a catalog of technical services (that abstract from the technical implementation) - you expose these in a Service Catalog using the serviceSpecification in TMF633. To add the commercial considerations, you can then wrap these technical services into commercial products and expose to your customers as a Product catalog (using productSpecification in TMF620).
------------------------------
Lester Thomas
Vodafone Group
Original Message:
Sent: Jul 20, 2020 03:33
From: Shino Jacob
Subject: TMF 620 and TMF 633
I have a few questions
1. What is productSpecification in TMF620
2. how is it related to serviceSpecification in TMF633
Does service Specification exist to augment the productSpecification? Does it contain more attributes than service specification?
Once a Product Offering is decomposed, how does it help creating the CFS ?
------------------------------
Shino Jacob
Infosys
------------------------------