t aligned with NGOSS to integrate these applications. Adoption of eTOM as a standard by ITU-T shows the wide spread use of NGOSS concepts. Legacy System owners can start by pre- paring a business map, information map, application map, and architec- ture map of their telecom system. The next step involves use of NGOSS methodology of SANRR (scope-analyze-normalize-rationalize-rectify). The end result of multiple iterations with SANRR is a set of level 4 eTOM business models, well-defined interfaces, and contracts with SID busi- nesses and system models, technology neutral architecture wherever pos- sible in implementation, and a detailed application map. Architecting based on SOA (service-oriented architecture) is another area of focus for architects. Benefits of using SOA in NMS, have driven NMS developers to come up with new SOA-based NMS suites. NGOSS does provide guidelines for developing SOA, but what is required is an archi- tecture that can convert the functionality rich legacy NMS solutions to SOA, addressing the capabilities of NGNM. Architects need to look at SID as the ideal abstract common model that provides an excellent foundation for OSS/BSS integration. In addition to Next Generation Network Management (NGNM) using SID business and system views to provide well-defined contracts of the existing system, SID can also be used for mapping application inter- faces and attributes for reuse. Applications that can enable content-based transformation logic to be captured on the SID without writing low-level code and capture validation rules on the SID are already available in the market. Enterprise common information model (CIM) and telecom shared information and data (SID) mapping is an area TMF and DMTF are jointly working on based on the convergence in management of tele- com and enterprise space. COTS integration is one of the major drivers in developing meta-models by NGOSS and architects needs to play a key role in promoting the use of meta-models. In a multivendor heterogeneous network environ- ment, i