sed user interface to create and edit orders placed by methods other than World Wide Web (www) like a telephone order, order by mail, or order placed at a sales center. Ease of integration: The order manager has to integrate with multiple support solutions. The solutions OMS has to integrate with may be from different vendors. So it is important that OMS has its APIs exposed for other mod- ules to integrate. Standard APIs and a scalable architecture is a usual trait of OMS, which make it easier for other modules to integrate with it. Some OMS solutions also support multiple platforms that makes it easier for inte- gration in a multivendor environment. Interaction with trouble ticket manager: The OMS also has to interwork with the trouble management module. The service terms and QoS parameters captured in the order needs to be communicated to the problem handling modules. In case of any trouble condition as part of completing an order or during the service execution linked to an order, the trouble ticket manager will raise a ticket and assign it to a technician for resolution. Each order placed by the customer is uniquely tracked and any trouble conditions are mapped to the order. Integration with customer relationship manager (CRM): The customer sup- port desk will get all types of queries with regard to an order like the date of completing the order, the quote, or the price the customer has to pay for the service in the order, the status of the order, changes to be made in the order, cancellations to the order, discounts or adjustments to the order based on promotions, confirmation on the order, troubles with regard to the order after service is activated, and SO on. In all cases where the customer interacts with the support desk, the specific order has to be identified to respond to the query. So the CRM module interacts with the OMS module to get informa- tion on the order. Reports: The OMS issues different types of reports that are useful for cus- tomers as well as internally by the service providers. The rep