loyed on separate platforms, allowing Ulysses deployments to be tailored. Common components are reused in a variety of service implementations, enabling new applications to be built on well-tested and field-proven code and data structures. The database servers are deployed in a live/shadow combination so that sub- scriber data are maintained in two real-time locations. The live and shadow systems are synchronised with each other and with the disk database stored in the OMP. Ulysses supports centralised operations, administration and management (OAM) via the OMP component, which provides mediation with the subscriber administra- tion and network management systems. The OMP is responsible for: startup and shutdown of database platforms modifications to secure databases maintenance and event reporting. The main system administration terminal is Java-based and can be operated locally and remotely via a Java-enabled system. Therefore, the OMP can be integrated into a web-based network management schema. 14.5 Conclusion The development of web-based network management is consistent with the growth of the web and its convenience to the enterprise. This chapter has presented a case study and several technologies that are being used to enabled web-based network management. Although the web is suited for making information available more easily to people throughout an organisation, this is not automatically so. For example, there is a finite set of standards that allowed the Moldova project to succeed. Now that one set of interfaces has been developed and implemented, we can see that progress will be made difficult in the future to the same extent that it has been in the past with OSS. That is, new software must be able to talk to the CORBA inter- faces or be compatible with whatever standards have been used. Further, because these standards have been implemented in multiple systems across geographically wide areas, the integration projects of the future might dwarf the OSS system inte- gration projects of today. However, t