 option, the Web interface can proceed with the rest of the order for service. In an integrated environment, the online ordering interface would be integrated tightly to the ISP's order and workflow management OSSs. The order manager would receive the incoming DSL order and decompose it for the workflow engine. The workflow engine then kicks off a series of tasks to fulfill the order. For example, the workflow engine can trigger a simple script on an authentication server. With some data captured from the customer Web interface, this script automatically will configure the customer's Internet services, setting up security, building an e-mail box, enabling Web space permissions, assigning IP addresses and telling the billing system which billing plan to activate once service is delivered. Service delivery, in this example, depends on outside parties filling specific needs. In our assumed eOSS environment with an automated supply chain, the ISP's order and workflow manager would be integrated with those of its trading partners or wholesale suppliers. Most likely through an interconnect gateway, the ISP's workflow manager would assign external tasks for the gateway to manage. Communicating with the Wholesalers The ISP's workflow managers must handle multiple sets of tasks among the various players involved in fulfilling the DSL service. Figure 8 illustrates the interdependence of workflow managers and tasks in an integrated supply chain. It also highlights the key responsibilities of each player in delivering the customer's DSL service. Keep in mind that the Internet underlies the customer ordering capability, as well as order and trouble management functionality among the IICs, and loop pre-qualification database access between the ISP and the DSL wholesaler. It also could support the ordering interface to the ILEC for loop requests and the ordering process for the ISP to order capacity from the NSP. The ISP's workflow manager or gateway sends a request for service to the DSL wholesaler. Most DSL wholesalers mainta