 trouble ticket. These tickets are then assigned to the resolution team. Based on how critical the trouble condition, different levels of supports will be offered and there is usually a dedicated team to handle each level of support. Support level can map to the services offered like level zero support might involve calling up the person who raised the ticket within an hour and providing support or it could mean that the trouble needs to be closed within a day. These items are explicitly slated in the SLA. When a trouble ticket is raised and needs to be assigned to a support person, the work force management module provides necessary inputs on the best person to solve the trouble condition. The work force management module has details on the skill sets and location of the technicians. It also maps technicians to specific trouble tickets, like whether the technician is free or working on a ticket, was there a change in the ticket status, or was the ticket reallocated to some other technician, and SO on. Consider the trouble ticket deals with a faulty switch in Dallas, Texas. So the trouble ticket man- ager assigns the ticket to a technician in Dallas based on input from the work force module. After fixing the switch, the technician can change the status of a ticket, for reconfiguration of switch by an operations team in London. Now again the trouble ticket manager can use the work force management module to assign the ticket to a professional from an operations team in London. This way the trouble ticket manager can track the ticket from creation to closure. Inventory management: Cost saving in telecom space can only be achieved when the available inventory is properly utilized. The inventory needs to be properly allocated and deallocated for offering the service. Inventory data if not managed is really complex. For example, inventory will include a wide variety of network elements like switches, hubs, servers, trunks, cards, racks, shelves with different capacity, address range, access points, and SO on. The inve