Hi!Usually BSS Product Management Platform is creating CFS service orders and BSS knows the references with CFS and physical goods(resources)I am a little bit confused with following
TMF641 ServiceRestriction sub-resource has
A list of resource references (ResourceRef [*]). A list of supporting resources (SupportingResource [*]).Note: only Service of type RFS can be associated with Resources.
A list of service references (ServiceRef [*]). A list of supporting services (SupportingService [*]). A collection of services that support this service (bundling, link CFS to RFS).
Is it BSS responsibility to decompose both level CFS and RFS services(link CFS to RFS) and use Service Catalog and Service Inventory data for that?
Or it is still service order management systems responsibility to add this information (PATCH serviceOrder)
Inspecting TMF641(ServiceOrdering) and TMF645(ServiceQualification) their resource models look similar.
So our OSS architects figured out that BSS Order Management have to take service qualification resource information and add it as an input while creating service order. So service order management do not need Service Catalog for decomposition and OSS starts the work as BSS predefined.Could anyone explain how to understand this API spec?
HelloThank you Jonathan and Ludovic. It helps.
I got the answer that I have expected. We will use only CFS specs references we get from product catalog and create service orders on them.
We have discussed that service qualification done in pre-ordering phase usually does not change during ordering . So if it is not expired by some network event or other reason we can use it as backbone to design and book technical resources in SOM processes. Of course only those on which customer has selected offerings and characteristics.