 sending template to client, initiating the provisioning activities after user input and sending the results back to the client. This includes bypassing some or all of the template-based provisioning functions on the server. 2. Extensions can implement special parameters in the template, which will be processed by the application extensions. 3. Extensions can implement special configuration or other tags, so that these tags are processed by the application extensions at any stage of processing. For exam- ple, all network configuration can be done in the application extension, bypassing regular configuration and processing the new tags defined in the XML templates. 6.10 High-level Product Case Study The TEMPo architecture follows TMN and supports FCAPS management functions. It has embedded device management functions for a single device and a high-level, 6 Service Provisioning and Activation network-wide provisioning EMS providing end-to-end and integrated network management functions. TEMPo, Tenor's Element Management Platform, is a distributed multiplatform client-server solution. A fully scalable and redundant architecture ensures system performance and resilience under heavy loads. Software updates and distribution to client applications are supported via push services that are provided by the server to minimise administration. TEMPo represents and provisions services by creating "service contracts" that contain the customer information, order numbers, service endpoints, scheduled bandwidths, QoS constraints and associated SLA metrics. For example, a user might create a service contract for customer X specifying a 100 Mbps private line-equiva- lent service for video applications 9am-5pm on weekdays which drops to a best- effort service at other times, and also specifying that SLA reports are automatically generated daily and weekly detailing the service performance actually achieved, showing availability, latencies (delay), loss and utilization. Services are created through a point and click, forms-based graph