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 process of normalization, the current view of the area that is scoped and analyzed is converted to NGOSS vocabulary. 4. Rationalize: The first step in rationalizing is to examine the normalized view of the current area for changes needed. In rationalization, activities like gap analysis, replication analysis, and conflict analysis is performed. The result of the rationalization is to identify what changes needs to be brought out for aligning with NGOSS. The first level of rationalization may not result in an alignment with NGOSS. The intent is to do a staged transformation to NGOSS. 5. Rectify: In rectification, modifications, deletions, and additions are performed on the scoped area based on changes identified during rationalization. The rectification will bring in changes to the business and technical aspects of the company for the scoped area. This is an iterative methodology in that once an activity from scoping to rec- tification is performed, the system is not immediately aligned with NGOSS. As already discussed, the intent is a staged migration where one round of rectification generated a new view of the current system. This is the new current view that is put back in the normalization phase and again normalized, rationalized, and recti- fied. In addition to NGOSS lifecycle, the other important elements in NGOSS are eTOM (enhanced telecom operations map), SID (shared information and data), TNA (technology 