TEMPo allows customers to utilise any other JDBC database, but has been optimised for Oracle environments.25 As TEMPO is written in Java, it can run on any hardware and software platform that supports a Java Virtual Machine. 6.10.3 Domain and Element Management Service networks require continuous uptime. This means that device and network monitoring and management are key. Achieving service flexibility and a high level 25 Pehaps because of Oracle's longer history with high-end RDBMS applications, Oracle has a greater presence in the OSS space than the competing Microsoft RDBMS technology. 6 Service Provisioning and Activation Provisioning XML/CORBA/RMI Distributed server(s) Administration Relational database Distribution Mediation agents Telnet Figure 6.9 TEMPo's distributed architecture permits flow-through service provisioning in a scalable environment. of network availability begins with a focus on element and domain management. With increasing bandwidth and port density and more sophisticated services comes the burden of device configuration. Networking elements commonly support many hundreds of interfaces, each with a specific service requirement. Of course, a com- mand line interface is totally inappropriate for this type of environment. Service provisioning solutions must offer GUI-based point-and-click functionality, and TEMPO does offer this. 6.10.4 Service Provisioning and Enhancement TEMPO was designed to enable service providers rapidly to define and provision enhanced service offerings. It is the first service provisioning product to allow a new class of service creation and provisioning through a graphical template which Tenor calls "ServiceExpress". The interface can be customised by service providers to rep- resent standard and custom service offerings. From the interface, services can oss for Telecom Networks quickly be defined and provisioned. From a ServiceExpress form, services are pro- visioned and then monitored to ensure that they are delivered. ServiceExpress increases provisioning quality