火龙果软件管理信息系统eTOM介绍中文资料.ppt

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 8 * * * * * * Need to mention that system entities will be added in phase 2 * * 9 * * * * * The fourth element of SMART TMN is Catalyst Projects. This is really a pragmatic way to get past the ‘chicken and egg’ problem that has caused problems for so long. The idea is that instead of writing a long and detailed specification, and then hoping vendors will implement it, we do our work more incrementatlly. Service providers and vendors discuss what is needed and what can be accomplished fairly quickly -- often by linking existing products with some minimal development work. Once they take the first steps, and see what the result looks like, they can choose to take additional steps. The venue for these catalyst projects is TM Forum’s TeleManagement World, which is held every six months. Having a very near-term target helps keep work moving quickly, and we have been amazed at just how much progress has been made in such a short time. After announcing SMART TMN in October 1997 at the first TeleManagement World in Montreal, we saw four demonstrations at the Paris TeleManagement World in April 1998 (just six months later) and will see five in Dallas in October of this year. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * The familiar TMN architecture for a generic OSS requires a multitude of interactions between and within layers to support an overall business process, e.g. provision service. At the NML and EML levels, applications often have rigorous real-time performance requirements and may need to handle large and frequent data flows. For this reason, such applications may be custom coded in specialized languages and architectures (e.g. manager-agent). Conversely, BML and SML applications are often COTS products and have widely differing requirements to the lower levels, for example transactional integrity, web-based access, etc. Imagine the steps needed to provision service, for e