providers? In the context of Work Orders, electronic entry of Work Orders in the Clarity system can immediately inform reviewers and approvers (see Figure 6.15) of the existence of a Work Order. Errors in the selection of the relevant circuit (if any) are avoided by referring to the table of circuits. Costs can be automatically calcu- lated. Non-completion of the Work Order by the due date can at least be informed to the appropriate manager to ensure that the Work Order is raised to an urgent status. It is easy for any manager to check on all involved in the Work Order for the purpose of performance reviews or to understand what went wrong if something did go wrong in executing the Work Order. The phrase "any manager" in the previous OSS for Telecom Networks Table 6.2 Attributes of a product domain. Attribute Description Domain number A unique number for the product domain that is specified by the user Customer ID The identifier of the customer connected to the product domain Customer name This will be automatically populated based on the customer ID Account manager This is the account manager of the selected customer Request number These will be added as requests are made for this product domain. That is, there is a one-to-many relationship between product domains and product domain requests Requested delivery date This is the date that the initial product domain was raised Product type This comprises the various product types which makes up the product domain. There will be a many-to-many relationship between product domains and product types Market segment This is the business category into which the product domain fits Assigned workgroup This is the service group management workgroup to which the product domain is assigned Request status Each service order that is related to the product domain is given a status This is the date on which the order status was last changed Created by This is the user ID of the person who created the product domain and entered its details Date created This is the date that the pr