oduct domain was entered into the system Created workgroup The workgroup of the user who created the product domain at the time they created the product domain sentence is important because when the application is distributed on a network, there is no need for administrative staff to chase up a piece of paper stored in some filing cabinet. So, although Work Orders are almost as old as work itself, implement- ing Work Order functionality in OSS software is a great value-add for a telecom service provider. Similar things can be said about other OSS functionality, such as service orders. Many other features of Clarity's Service Manager, which we are using for illustra- tive purposes, are examples of the "What if" scenarios of spreadsheets: they simply would not be possible without software. For example, to what extent were product domains or service groups used before OSS software came around? Circuit diagrams and graphical information system (GIS) functionality are functionalities which even more obviously have relatively lame parallels in the pen-and-paper world. 6.12.3 Product Domains The product domain is a high-level tying together of customer order, service group and service orders. They are related in the following way: A product domain contains one or more service groups and must be created before entering service group details. A service group may contain more than one service order and must be created before entering service order details. A service order can exist with or without a product domain and a product domain-service group. However, if a service order has a service group then it must also have a product domain. A product domain comprises the attributes given in Table 6.2. The main screen for product domains is shown in Figure 6.16. 6 Service Provisioning and Activation 6.12.4 Service Groups A service group is a service category label or a group of services. Over many years of implementing OSS software for telecom carriers, Clarity found that carriers wanted to 10 Product Domain Clarity Product Dem