Hi Paras
Firstly, I'd like to understand what you mean by "product technical feasibility". In general, the technical feasibility is determined at the service level. Of course this has a knock-on effect on products that are implemented using these services. But product feasibility includes also commercial considerations (such as credit-worthiness, risks, and more), and these are represented in the product offering qualification API. But perhaps you had in mind additional technical feasibility aspects that are not related to service?
Regarding the relationship between these two APIs, the connection is at the level of product specification and corresponding service specification. The assumption in TM Forum model and architecture (e.g. ODA) is that the Product layer (BSS, Core Commerce) is aware of the Service layer (OSS, Production). When an API consumer gets a result from service qualification, it should be able to use the information in product catalog to map the returned service/service spec into the product implications.
Hope this helps somewhat.
------------------------------
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: Feb 25, 2022 03:54
From: Paras Agrawal
Subject: Confusion on using Product offering qualification and service qualification apis
Hi,
I need to create an application layer on top of BSS application. The role of this layer is to receive requests from client systems, transform and invoke corresponding BSS/OSS APIs as per the requirement. Here, I need to expose a capability to client for Product technical feasibility check (e.g. Fiber Connectivity Product) . In the Open API definitions, I could only find Service Technical feasibility, but not Product Technical feasibility. Usually client systems will mainly have info on Product instead of underlying service.
I checked TMF links related to it i.e.
Use Case UC002: Browse B2C catalogue and check Fiber technical eligibility v1 - Published Deliverables - TM Forum Confluence
https://projects.tmforum.org/wiki/display/PUB/TMF070B+Advanced+Platform+Deployment+Blueprints+R17.5.1?_ga=2.107166212.723378726.1524824266-753906893.1507067474#TMF070BAdvancedPlatformDeploymentBlueprintsR17.5.1-ProductPre-Ordering
But not getting clarity why dont we have an API as Product technical feasibility. Also, in case we have to use service technical feasibility only, then can the service specification id be returned to client in getProductOffering call? Mainly how client systems should fetch Service specification?
Thanks!
Paras
#General
------------------------------
Paras Agrawal
Infosys
------------------------------