owed by an analysis of the adoption strategies for working on the NGNM framework. 34.3 Legacy NMS The various modules in a typical legacy NMS are (see Figure 34.1): a. Platform components: These components include object persistence, logging framework, libraries, and SO on that are required by most of the management function implementation modules. b. Data collection components: Based on the NMS protocol supported on the network element, these components collect data from the network elements. In some management paradigms this component may not be part of the NMS and will be a separate solution called EMS. Fundamentals of EMS, NMS and OSS/BSS GUI components Management function components Data collection components Figure 34.1 Simplified legacy NMS. C. Management function components: These components use the data col- lected from the network elements to provide FCAPS (fault, configuration, accounting, performance, and security) and other specialized management functionality. d. Northbound interface components: These components provide management data to the northbound interfaces like another NMS or operations support systems (OSS). e. GUI components: These provide user interaction screens that enable a user to perform operations on the various modules in the NMS. 34.4 Issues with Legacy NMS From the perspective of the multivendor, heterogeneous network, and convergent service environment, the current legacy NMS has the following issues: 1. No clear demarcation between data collection and functional implementa- tion: For example, the data collection process itself implements fault and configuration management functionality for that network element (NE). The net result is when data needs to be collected from an NE that has the same network management protocol; most of the code needs to be rewritten or modified. If data collection is limited to protocol specific information acquir- ing, then this problem would not arise. 2. There is much network specific information hard coded in the functional implementation and dat