Hello,
i work as a solution architect in the Addressing & Service Qualification Management Domain and with the introduction of ODA in my organisation,there is a real conflict kind of a situation which is happening ,Service Qualification was present in the legacy architecture as a component under OSS and was used to orchestrate against multiple network inventory systems to provide holistic SQ Results ,even for a particular domain like a Fixed Telephony Service or Fixed Internet Service , the orchestration used to happen against multiple different systems ,an network inventory system to determine availability of that service and a resource inventory system to determine availability of NTU's or availability of inplace copper path's ,after the introduction of ODA in my organisation and with the concept of new operational domain's like Fixed Internet Domain and Fixed Telephony Domain coming into picture,there is a widespread view that the individual domains would themself perform the SQ and there is no need for a Service Qualification Management to be an operational domain under NaaS as it creates a duplication ,i just want to get a view on whether this understanding is really correct and if ODA mandates SQ to be performed by Individual domains and does not require an Service Qualification Management operation domain by itself sitting under NaaS,your inputs would be really really helpful to me .
#OpenDigitalArchitecture