Hello,
I work as a Solution Architect in the Addressing and Service Qualification Domain ,In my organisation the adoption of ODA has caused a real conflict ,
ODA defines Service Qualification Management as an operational domain under NaaS ,but there is a widespread view that an exclusive Service Qualification Management Operational Domain itself is not required and the responsibilities of the Service Qualification Management Domain can be fulfilled by Individual Operational Domains like Fixed Internet Connectivity,Fixed Voice Connectivity themself.is this the right understanding? ,In legacy architecture Service Qualification Management used to sit under OSS and would require orchestration against multiple systems like Network Inventory System for Network Coverage details and Device Inventory Systems for NTU,Copper path,Antenna availability to derive an holistic service qualification result with an outcome that the service has the required infrastructure available to be successfully provisioned,i believe with the introduction of ODA the underlying principles of orchestration to determine service availability and feasibility would remain the same but is it the view that Service Qualification Management in itself as an operational domain in not required under NaaS and its responsibilities can be fulfilled by Individual Operational Domains?
#OpenDigitalArchitecture