akes minimal manual intervention a key feature to be available in next generation network management. Traditionally there were different standardizing bodies working different technol- logies in telecom. With convergence in the telecom domain, these standardizing bodies need to work together in developing standards that can be used across tech- nologies. Convergence is also happening at the domain level. All telecom compa- nies have an enterprise aspect. That is in addition to the telecom infrastructure there is also an enterprise network that needs to be managed. Convergence of enter- prise and telecom domain leads to the need for standards that makes it possible for a single management solution that can manage both the telecom and enterprise network in a company. Let us next look into an outline of NGN management requirements and what is usually defined in this space, which is not currently limited to just a network. A general set of capability map for NGN management was captured as part of the OSS vision document of ETIS TISPAN. Many other standardizing bodies also contributed in this space and came up with an extensive set of NGNM require- ments. The major ones that came out with an initial set of NGNM requirements in Fundamentals of EMS, NMS and OSS/BSS addition to ETSI TISPAN are ATIS and ITU-T. TMF has compiled these require- ments in TR133 document. Given below are some of the main categories in which NGNM requirements are defined. 1. Customer centric requirements: Customer needs and end-user experience is a key capability that drives current industry. This has led to specific require- ments centered on the customer. In a competing telecom market the best vendor is the one that can satisfy customer demands. So choice of service provider is a default requirement of NGNM. Personalization and mobility is one key customer requirement in next generation network management. Personalization would involve each customer getting the experience he/she wants, this way the service capabilities are customized to suit t