1 / 25

February 2004 2004 年 2 月

Full Suite Integrated OSS Solution vs. Multiple Product Combination OSS 解决方案: “全系统集成”与“多产品组合”方式的比较. February 2004 2004 年 2 月. Agenda 议程. What does it mean “Full Suite Integrated OSS Solution”? “全系统集成的 OSS 解决方案”的含义

ganya
Download Presentation

February 2004 2004 年 2 月

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Full Suite Integrated OSS Solution vs. Multiple Product Combination OSS解决方案: “全系统集成”与“多产品组合”方式的比较 February 20042004年2月

  2. Agenda议程 • What does it mean “Full Suite Integrated OSS Solution”? • “全系统集成的OSS解决方案”的含义 • Benefits of Full Suite Integrated vs. Multiple Product Combination OSS Solution • OSS解决方案:“全系统集成”相对于“多产品组合”方式的优点 • Purchasing and Implementation • 采购和实施 • Ongoing Operation • 实际运行

  3. What does “Full Suite Integrated OSS” means“全系统集成的OSS解决方案”的含义 • Full Suite of “FCAPS” Applications • 覆盖“FCAPS” 全部应用的完整系统 • Products mostly developed by one SW house • 产品大部分由一家软件公司所开发 • Inclusion of “Third Party” products (as OEM) • 以OEM方式包含“第三方”产品 • Tightly Integrated but Loosely coupled • 紧密集成,并且松耦合 • Pre-Integrated and Tested • 经过预先集成和测试

  4. Other OSS Solution Approaches其他OSS解决方案的途径 • Multiple Product Combination • 多产品组合 • Collection of chosen products, from different vendors, in each OSS domain • 在每个OSS领域、从不同厂商选择的产品的集合 • Integration and implementation by SI • 由系统集成商进行集成和实施 • Alliance Combination • 联盟产品组合 • Alliance of several vendors to coordinate APIs and test integration of their products • 几家厂商联盟,协商其产品的API接口,并进行集成测试

  5. Netrac Integrated Suite of ProductsNetrac预先集成的产品

  6. Benefits of Full Suite Integratedvs. Multiple Product Combination“全系统集成”相对于“多产品组合”方式的优点Purchasing Phase采购阶段

  7. Purchase and Licenses costs采购和许可费用 • Accountability责任与义务  • Customer usually is not facing the point product vendors • 用户通常不直接面对每个产品的厂商 • One (or more) products does not interfaces properly with network • 单个(或者多个)产品不适于与网络接口 • API of a product does not comply with others in the Suite • 系统中某个产品的API与其他产品的API不一致 • 3rd Party Licenses Costs 第三方许可费用 • Multiple use of 3rd party SW products (DB) • 大量采用第三方软件产品(数据库) • Need for Multiple/Different license agreement • 需要多个、不同的许可协议 • Additional CAPEX 额外的投资成本 • Extended IP Infrastructure • 扩展IP基础设施 • EAI Bus – Additional licenses and HW • EAI总线——额外的许可和硬件投入

  8. Integration - Schedule and Cost集成-时间与成本 • Integration Complexity 集成的复杂性 • Inter-product APIs • 产品间的API接口 • Multiple interfaces to the Network • 多个与网络的接口 • Design and Implementation of extensive time period • 周期时间长的设计与实施 • Testing 测试 • Involvement of teams from point products vendors – coordination • 协调来自不同产品厂商的开发队伍 • Consecutive testing – Customer project team is occupied • 联合测试——需要客户的项目团队参与 • Solution Expansion 方案扩展 • Adding new functionality-engineering and testing with all point products • 增加新的功能——工程问题、与所有产品的测试问题 • Introduction of new NE or EM type – involving all products • 接入新网元或者网元管理系统类型——影响所有的产品 • Introduction of new technology in the service provider’s network • 引入新技术到服务提供商的网络中

  9. Benefits of Fully Integrated Solution“全系统集成”方案的优点 • No integration needed for Fully Integrated Suite • 对于“全系统集成”的系统,没有集成的必要 • ONE tool, faster implementation and customization • 一个工具,可以快速地实施和客制化 • One tool for many purposes >>>> Re-use: • 一个工具,多种用途>>>>复用: • Mediation Thresholds – same for Fault, Performance, Traffic etc. • 采集层门限设置方式——对于故障、性能、话务等都相同 • One Scheduler • 单一调度 • One Dispatcher • 单一分发 • One Web-Reporter.. • 一个基于Web的报表系统

  10. Benefits of Full Suite Integratedvs. Multiple Product Combination“全系统集成”相对于“多产品组合”方式的优点Ongoing Operation实际运行阶段

  11. Unified Mediation统一的采集层 • Unified mediation layer for all TOM/FCAPS functions • 统一的采集层,针对所有的TOM/FCAPS功能 • Reduced NE polling • 减少对网元的轮询 • See the big picture quickly (single client, multiple applications) • 快速看到全景图(单个客户端,多个应用) • Interface Modifications • 接口修正 • “Single Point” of interface • “单点”接口 • Less OSS solution administration workload • 降低OSS解决方案的管理工作负担 • Interface BUS Performance • 接口总线性能

  12. 0 0 0 0 0 0 0 0 0 0 0 0 0 0 01010 01010 01010 01010 01010 01010 01010 01100 01100 01100 01100 01100 01100 01100 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 Overall Quality of the System系统的总体品质 • Architecture is pre-defined to have best Performancee.g.: Impact Analysis • 系统架构预先定义,具有最优的性能  比如:影响性分析 EAI Bus EAI总线 Fault Management 故障管理 Inventory 资源

  13. 010101010 010101010 010101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 01010 01010 01010 01010 01010 01010 01010 1010 1010 1010 1010 1010 1010 1010 011010 011010 011010 011010 011010 011010 011010 01010 01010 01010 01010 01010 01010 01010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 011010 010101010 010101010 010101010 010101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 0101010 Overall Quality of the System系统的总体品质 • Architecture is pre-defined to have best Performancee.g.: Impact Analysis • 系统架构预先定义,具有最优性能  比如:影响性分析 EAI Bus EAI总线 Fault Management 故障管理 Inventory 资源 Inventory 资源

  14. Overall Quality of the System 系统的总体品质 • Architecture is pre-defined to have best performance e.g.: Impact Analysis • 系统架构预先定义,具有最优性能  比如:影响性分析 EAI Bus EAI总线 Fault Management 故障管理 Inventory 资源

  15. Data Management - Information re-use数据管理-信息重用 • Example: Inventory DB in a Fully Integrated Solution • 实例:“全系统集成”解决方案中的资源数据库 • no need to define entities (links) in inventory DB, performance DB, fault DB, mediation DB… • 无需为资源数据库、性能数据库、故障数据库、采集数据库……分别定义实体(或者连接) Inventory DB 资源数据库 Traffic 流量 Planning 规划 Performance 性能 Provisioning 业务开通 Fault 故障

  16. Information re-use信息重用 • Example: Inventory DB in a Multiple Product Combination solution • 实例:“多产品组合”解决方案中的资源数据库 • Constantly synchronize information in all DBs • 不断地同步所有数据库中的信息 • Extensive DBA workload • 增加数据库管理员的工作负担 • Expensive, more vulnerable to errors • 花费更多,易于出错 DB Vendor 数据库厂商 PM vendor 性能管理系统厂商 Netrac Netrac厂商 Auto Detect Vendor 自动检测系统厂商 FM Vendor 故障管理系统厂商

  17. DB Savings in Fully Integrated solution“全系统集成”解决方案在数据库方面的节约 • Reduced number of databases • 减少数据库的数量 • Reduced license costs • 降低许可费用 • Reduced maintenance costs • 降低维护费用 • Reduced system costs • 降低系统费用 • Faster data access by housing more informationin the same DB • 将更多信息保存在同一数据库中可以保证数据快速访问 • Less Data Re-conciliation • 减少对数据一致性的维护工作 • Big $$ saving on data integrity • 在数据完整性上节省大量的$$ • Big $$ saving on interfaces – initially and for ongoing maintenance • 在接口上节省大量的$$——初始实施和运行维护时

  18. Administration tool – in one system:管理工具-在单一系统中 • User definitions • 用户定义 • Security • 安全管理 • Logs (audit) • 日志(审计) • Single Sign-on • 单一标识 • Single method for partitioning the network • 划分网络的单一方法

  19. Upgrading the system系统升级 • Easier in one, integrated system • 在单一、集成系统中能尽早实现 • If APIs are affected – when upgrading one application – needs to re-integrate the whole solution • 如升级应用时影响到了API,需要重新集成整个方案 • In Multiple Product Combination, each point application vendor has its own upgrade schedules, hard to synchronize • 对于“多产品组合”方案,每个应用厂商均有自己的升级计划,难以保持同步 • Testing the system • 系统测试 • Adding a new network domain • 增加新的网络领域 • Full Integrated OSS Solution is usually multi-domain, its products automatically support new domains - Just need to model the new domain in Inventory, and add libraries • “全系统集成”OSS方案通常是跨领域的,其产品自动支持新的网络领域——仅需要在资源管理中对新领域进行建模,并增加新的运行库即可。 • In case of Multiple Product Combination solution Usually several applications must undergo changes to support the new domain • 在“多产品组合”方案中,通常有多个应用需要做大的改动,才能支持新的网络领域。

  20. On Going Benefits of Fully Integrated Solution全系统集成方案的运营优点 • Vendor understands full view of the network • 厂商理解网络的全局视图 • Single GUI • 单个GUI • Seamless end-to-end views • 无缝的端到端视图 • Complementary and combined fault, performance, configuration, provisioning, security and service views • 互补、组合的故障、性能、配置、开通、安全和业务视图 • Multi-dimensional drill through • 多维钻取 • Same view for all network domains, easy to add a new domain • 对于所有的网络领域,视图都相同。易于增加新的网络领域。 • Less training • 减少培训 • Worker mobility (from fault to performance, from IP to switching, …) • 工作人员岗位流动(从故障到性能,从IP到交换,……) • Customization and Development Roadmap • 客制化和开发路线图 • Service Provider ability to influence • 服务提供商具有影响的能力

  21. Summary小结 • Integrated solution saves at: • “全系统集成”方案可以节省成本和时间于: • Initial implementation of the system • 系统初始实施阶段 • Maintenance period (years!) • 维护阶段(许多年!) • One point of contact – reduce risks • 一个联系点——降低风险 • It provides an easy-to-use system • 提供一个易于使用的系统 • Data integrity is guaranteed • 可以保证数据完整性

  22. Fully Integrated OSS vs. Multiple Product Combination by Market Analysts市场分析家眼中的“全系统集成”OSS方案和“多产品组合”OSS方案 • “…costs associated with integrating multiple point products are anywhere from three to four times the costs of the original licenses…an integrated OSS platform is only about one and a half to two times the original license cost". • “…集成多个产品发生的费用大约是原始许可费用的3到4倍…而预先集成的OSS平台的费用仅仅是原始许可费用的1.5倍到2倍。” • Will Cappelli, V.P. - Giga Information Group • Will Cappelli, Giga信息集团副总裁 • “Operational issues are often an afterthought in acquisitions of OSS or new network investment. This investment is often fragmented…as a result…around 50% of all OSS/BSS spending is not productive. Around 12% of CapEx…are spent on OSS/BSS, but up to 50% is spent on integrating dissimilar systems.” • “运营问题通常是获得OSS或者新的网络投资之后才考虑的问题。这项投资通常被分解了…结果是…大约全部OSS/BSS开销的50%是非生产性的。大约投资的12%…用于OSS/BSS,但是高达50%的费用花在集成不同的系统之上。” • Mandarin Associates & Telemanagement Forum

  23. Fully Integrated OSS vs. Multiple Product Combination by Market Analysts市场分析家眼中的全集成OSS方案和多产品组合OSS方案 • Per RHK’s Analysis of OSS Integration, June 2003: • 根据RHK于2003年6月所做的OSS集成分析 • “Our research shows that integration of OSS systems can cost up to three times the cost of the underlying OSS application.” • “我们的研究表明,OSS系统集成费用高达底层OSS应用成本的三倍。 • “RHK calculates that between 20% and 75% of total OSS expenditure for any given project can be related to systems integration…often eating up the majority of the implementation budget.” • “RHK的统计表明,任何项目的OSS项目,其总体费用的20%到75%与系统集成相关…通常会消耗掉绝大部分实施预算。” • “The systems integration life-cycle cost of any particular OSS is increased further by revisions to the OSS as well as changes to the surrounding OSS systems, which may have a knock-on impact.” • “OSS版本的升级,使任何特定OSS的系统集成生命周期成本都在不断地增加。因为OSS系统外围环境发生了变化,这是决定性的影响。” • "Best of breed is dead, except for dog shows." • “最好的品种已经消亡,狗展上的除外。” • Larry Ellison, CEO of Oracle in an interview with Fortune Magazine, June 2003 • Larry Ellison,Oracle CEO,与《财富》杂志(2003年6月)的会见中

  24. What RHK says is…RHK的意思是…

  25. Thank You 谢谢

More Related