ted with a prod- uct domain record. This association has the effect of creating a template, with the entry of implementation tasks and other service order characteristics. The work involved in satisfying a service order is given in the implementation task list. As the screen in Figure 6.13 shows, the first implementation task in completing a service order is the approval of the order, which was discussed above, and the final task is closure of the service order. A service order is closed when all implementa- tion tasks have been completed so that the service order has been implemented and the service is active. Each implementation task aside from approving and closing a service order gen- erally requires a Work Order since the raising of a Work Order is the means by which the workforce of a service provider is given instructions. Work Orders are the link between the raising of a service order resulting from a customer purchase and the work that the service provider must carry out in order to deliver to the customer what they have purchased. Product Domain Product Domain service group service order service order Figure 6.12 Association between product domain and other entities. 6 Service Provisioning and Activation 6.12.2 Work Orders Details about Work Orders do not fit within the scope of this book. The Work Order features of Clarity's Service Manager essentially implements Work Orders as they are generally understood. TO Service Implementation Tasks Implementation Tasks Allowed Time Timing Tesk Name Start Date Due Date Status Status Date Work Group Assigned Date (Minutes) Milestone APPROVE ORDER ASSIONED 22-NOV-2001 CLARITY 22-NOV-2001 CREATE CIRCUIT ASSIONED 22-NOV-2001 CLARITY 22-NOV-2001 DESIGN CIRCUIT ASSIONED 22-NOV-2001 CLARITY 22-NOV-2001 ISSUE WORK ORDER ASSIONED 22-NOV-2001 CLARITY 22-NOV-2001 COMMISSION CIRCUIT ASSIGNED 22-NOV-2001 CLARITY 22-NOV-2001 ACTIVATE CIRCUIT ASSIGNED 02-NOV-2001 CLARITY 22-NOV-2001 ASSION TEST ASSIONED 22-NOV-2001 CLARITY 22-NOV-2001 SERVICE DELIVERY ASSIGNED 22-NOV-2001 CLAR