mplementation provider needs to ensure that TAM is Fundamentals of EMS, NMS and OSS/BSS defined to the lowest level of granularity process to make it beneficial for adoption. The development of procurable NGOSS contacts based on TAM also needs to be driven by the implementation provider. The implementation of a contract library including strategy for developing contract registry and repository vests on the implementation provider. In addition to solutions based on standards done as part of Prosspero, work should also go into development of tools that will aid the lifecycle, methodologies, interfaces, models, and maps defined by TMF. Operations /deployment team dealing with the deployment block The operations center should be implementing component-based man- agement that uses the capabilities provided by NGOSS system manage- ment architecture and reference implementations. Another activity of the operations center is to do business and service performance tooling. The performance tooling will include QoS, busi- ness activity, and equipment performance measurements to meet the SLA agreed upon with the customer. 17.4 M.3060 According to this document, NGNM is not a new generation of management systems, but a management system that supports monitoring and control of the NGN resources and services. The resources of NGN has both a service component and transport component. The role of NGNM is to have seamless flow of data across interfaces from the network element layer to the business management layer. Having both network and services in the scope of management, the suggestions of ITU-T addresses both network operators and service providers. The NGNM architecture can be divided into four views as shown in the dia- gram (see Figure 17.2). They are: Business process view (architecture): This view spans across the three other views and is concerned with the business process framework in the service provider space. eTOM is suggested as the reference framework for process view. Management functional view (architecture): T