rtifacts identified by NGOSS. Fundamentals of EMS, NMS and OSS/BSS Community or shared knowledge: Knowledge common to both NGOSS and corporation. This is represented as an intersection of existing corporate knowledge and NGOSS knowledge. 21.4 SANRR Methodology The NGOSS defines a road map that can be used by current systems to align with the reference models defined by NGOSS (see Figure 21.3). This roadmap is based on SANRR (scope, analyze, normalize, rationalize, and rectify) methodology. The methodology can be used for iteration at life cycle level or view level. The outcome of the iteration is to identify the activities and steps required to align with NGOSS components. Let us look into this methodology in detail: 1. Scope: In this phase the area that needs to get aligned with NGOSS is identified. There are multiple processes spread across customer, service, and network management. A modular approach is required to make changes to Scope Analyze Normalize Rationalize Rectify Figure 21.3 SANRR methodology flow diagram. NGOSS the process, architectures, and contracts. In scope, the organization identifies what module needs to be worked on. Although multiple modules would need to be worked on, each module is considered to define an element of scope. 2. Analyze: In this phase the scoped area is analyzed using cases and maps to identify the current system. This activity is intended to get the current model as it is in place, SO that the model based on NGOSS can be created. This would involve preparation of process maps, information models, and all artifacts that best describe the current system. A clear analysis needs to be performed by a dedicated team who needs to work on the technical and busi- ness aspects of the scoped area. 3. Normalize: The current description of the system in place based on available artifacts and those prepared as part of analysis will not be in a vocabulary as used by NGOSS. This makes it difficult to identify what is missing in the sys- tem or where an overhead is occurring. In the proces