Hi Milind
In order to call TMF 645 (service qualification), the consumer of the API must "understand" the concept of product=>service decomposition.
But it is also necessary to "understand" the reverse transformation, so that feasible services can be translated back to products.
Either the consumer of TMF 679 (product offering qualification) will also call TMF 645, or the implementation of 679 will itself call 645, dealing with the above translations.
I don't have a feeling of which is "better", it seems to me that this will be an implementation decision dependent on the service provider business.
Sorry if this doesn't help much.
------------------------------
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: May 07, 2020 05:47
From: Milind Bhagwat
Subject: TMF 679 : Does it include calls to TMF 645
We have been trying to understand the scope of TMF 679. The description states that the API is used to check commercial eligibility. However when we read the example, it seems to suggest that the API also check for technical feasibility at a location.
Does this mean the API is a combination of Commercial Eligibility+Service Qualification or is the expectation to do commercial check first followed by a separate call to 645?
Regards,
Milind
------------------------------
Milind Bhagwat
BT Group plc
------------------------------