early 1980s most of the equipment required by local exchange carriers (LECs) were supplied by one or two suppliers in most parts of the world. One of the major changes to this approach was the breakup of the Bell System toward the mid-1980s after with LECs were encouraged to procure equipment from any vendor of choice. As a result the network for offering basic service now had components from mul- tiple vendors. While there were standard protocols for interaction between network elements from different vendors, there were no popular and adopted standards for telecom data and interface management in a multivendor environment. This led to an increase in CAPEX for having new support systems, increase in OPEX with usage of more OSS solutions from different vendors, reduced interoperability between OSS solutions, and lack of flexibility in bringing in new OSS function- ality. The first popular attempt to define the management stack that was widely accepted was the TMN (telecommunications management network) model. The TMN model divided the management stack into five layers. The layers are: business management layer (BML), service management layer (SML), network management layer (NML), element management layer (EML), and the network element (NE) layer. There are management agents running on the network ele- ments in the network element layer that collect management data. This informa- tion from agents is collected by the element managers in EML. In a network with multiple network elements, there will be multiple element managers. To provide management data at a network level by aggregating information of multiple net- work elements in the network, a network manager is used that sits in NML. Over the network infrastructure, there can be multiple services that will be hosted. The management of the service happens in the SML. Finally the upper most layer of TMN, the BML is to handle business data in service provider space. The BML takes feed from the SML and it is the service reports that are used as input in the generati