e server deals with the switch directly connected to it. Each satellite receives service provisioning verifica- tion information from the updated switches via the direct connections, and simi- larly with the central CallGate server and the updated switch connected to it. The verification information is forwarded from the satellites to the centralised server via a LAN/WAN. Verification information is summarised (for example, "updates in all switches are OK") in the centralised CallGate server and forwarded to the billing or CRM system, via a LAN/WAN. Besides executing service provisioning commands by sending instructions to network elements, CallGate can read results or status information from the switches and forward it to a customer care system. If there is more than one (satellite) customer care system, then the commands are split at the central server and distributed. Examples of typical Service Provisioning commands are: adding new subscribers to the switch (in series or individually) disconnecting and reconnecting subscribers (in series or individually) adding and removing value added services (in series or individually) bar all outgoing or incoming calls restrict calls within a close user group. 6.12 Service Provisioning OSS Solution We base a detailed description of a service provisioning OSS solution on the Clarity Service Manager OSS product. The aim of service management products is to streamline provisioning and activation of telecom services. A service management OSS product should allow convergent service provisioning for products such as leased line, fixed, mobile, freecall, broadband and IP-based services. Service man- ager provides a single platform for convergent service activation. Users specify design rules for: shortest path through the network smallest number of equipment nodes to utilise least cost routing protected paths traffic distribution. 6.12.1 Service Orders A service order is created to "order" work that is associated with providing a service to be done on a circuit. Such work may in