2020-08-20 ODA Solution Design Blueprint Meeting notesand is based on Product to Service decomposition in ODA Core Commerce.Syvlie has some further informaton on the catalog aspects of thsi which we were unable to cover but we plan to cover them on next week's call.The issue of where the Product Order is decomposed into Service orders has come up previously MTOSI work and it was partially documented in the SAI interface Service Activation - DDP BA - Part 2: Service Activation Interface (SAI) TMF518_SA_2 Version 1.1 But I am not sure the assumptions there are corect for ODA current practices so best to revisit this topic.There was a SID Golden Nugget on this topic too. copied below as I don't belive thisis on the current web.
Here are two different viewpoints on Product and Service...there may be others and neither should be taken as the final word in how to view entities in these two related domains. Thanks to Martin Gutzki of T-Systems for summarizing these two views based on a quite lengthy email thread among SID team members that occurred in the later months of 2008.
* another way would be e.g. to call a hotline to get services performed by humans
I feel that the different viewpoints are best understood with two different mindsets:Viewpoint 1 figures out the construction of a product starting from the things that a customer / user actually sees, including the end-user device. This leads to the interpretation that a CFS is functionality that can be perceived at the end-user device. Viewpoint 2 looks on what needs to be provided in the service provider's infrastructure during fulfillment, thus using the CFS as a requirement for functionality of the provider infrastructure that needs to be provided through RFS. It seems to me that the different viewpoints and interpretations come from different system boundaries.Examples of Product/Service/Resource and their relationships can be found at