ician needs to be involved in setting up resources to offer a service, then the order management system sends data to the workflow manager SO that an appropriate technician can be allocated to fix the issue before auto-provisioning can be triggered. Fundamentals of EMS, NMS and OSS/BSS The same is the case when an auto-provisioning action fails and a technician needs to fix the issue, SO that auto-provisioning can be retriggered. Interactive user interface: Web-based ordering is most popular in customer space and most service providers offer their customers the capability to place and track their order on the Web. The sales, operations, order management, and customer support team in the service provider space would mostly have an application or Web-based 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 g