The End-to-End eTom Perspective and Solution(1).ppt

上传人:文库蛋蛋多 文档编号:2751865 上传时间:2023-02-24 格式:PPT 页数:117 大小:2.67MB
返回 下载 相关 举报
The End-to-End eTom Perspective and Solution(1).ppt_第1页
第1页 / 共117页
The End-to-End eTom Perspective and Solution(1).ppt_第2页
第2页 / 共117页
The End-to-End eTom Perspective and Solution(1).ppt_第3页
第3页 / 共117页
The End-to-End eTom Perspective and Solution(1).ppt_第4页
第4页 / 共117页
The End-to-End eTom Perspective and Solution(1).ppt_第5页
第5页 / 共117页
点击查看更多>>
资源描述

《The End-to-End eTom Perspective and Solution(1).ppt》由会员分享,可在线阅读,更多相关《The End-to-End eTom Perspective and Solution(1).ppt(117页珍藏版)》请在三一办公上搜索。

1、NGOSS,The End-to-End Perspective&BEA Solution,SE Team leader,Telco.BEA(China)Ltd.X,Leo cui,TMN Layers correspond with TOM horizontals,TOM processes are captured in“FAB”area of eTOM Operations,eTOM maps the NGOSS Business View,Agenda,Introduction to NGOSS,Explore the NGOSS Maps,Business&System Views,

2、Info&Implementation Views,Exec Summary View of NGOSS,“Framework for Rapid and Flexible Integration of OSSs&BSSs in Com/Telecom Industry”Framework Supports Multiple ViewpointsArchitecture Tech Neutral&Tech SpecificMethodology Business Process DrivenDevelopment Model-basedInteroperability Contract/Com

3、ponent-based using Shared Information ModelsCommunication Distributed NetworkingOperation Distributed Computing ServicesCompliance Standard able&Testable,Draws on a Broad Base of Ideas,NGOSS,NGOSS Key Elements,Definition of Business Processes and Information Models Definition of Systems Framework up

4、on which these business solutions will be builtPractical implementations and multi-vendor demonstrations via a series of collaborative Catalyst ProjectsCreation of a Knowledge Base of documentation,models and code to support developers,integrators and users,NGOSS Methodology,Methodology system of pr

5、inciples and procedures applied to a discipline,NGOSS*Knowledge Base(SID*)Overall repository of Information,Business View(eTOM*)Driver for development,Run-Time ViewOperational Solution to solve the business problem,Implementation ViewGuides the implementation of System Requirements,Systems View(SIM*

6、)Aids in defining System Requirements,*NGOSS-New Generation OSS eTOM-Enhanced Telecom Operations Map SIM-System Integration Map SID-Shared Information/Data Model,NGOSS Framework co-ordinates the elements involved in Integrated OSS solutions.,Explore the Maps,Methodology the QuadrantsBusiness Viewpoi

7、nt eTOMSystem Viewpoint SIMInformation Viewpoint SIDBehavior Viewpoint PM&BPMArchitecture TNAImplementation Viewpoint TSACompliance Viewpoint VV&T,Architecture,Business,System,Behavior,Information,Implementation,NGOSS The Landscape“View or vista of scenery”,Artifacts,Viewpoint focus on particular co

8、ncerns within a system(IEEE Std 1471-2000),Architecture,Business,System,Behavior,Information,Implementation,Artifacts,Viewpoint focus on particular concerns within a system(IEEE Std 1471-2000),NGOSS The Maps“Representation of a region”,BusinessMap-eTOM,eTOM-Business Map,Reference Map of Idealized Or

9、ganizationBusiness Process Model-based ViewpointExternal View of Functionality supported by Business ActivitiesMechanism for Identifying&CatalogingBusiness ProcessesActorsDomain BoundariesEntitiesCornerstone of Business View,eTOM e-Telecommunications Operations Map,NGOSS Business Map,Architecture,Bu

10、siness,System,Behavior,Information,Implementation,Artifacts,Viewpoint focus on particular concerns within a system(IEEE Std 1471-2000),NGOSS The Maps“Representation of a region”,SystemMap-SIM,SIM System Map,Reference Map of Idealized IT EnvironmentSystem Solution Model-based ViewpointInternal View o

11、f Functionality supported by Computing SystemsMechanism for Identifying&CatalogingSystem ProcessesActorsInterface Reference PointsContractsShared Information&Data ModelsCornerstone of System View,SIM Systems Integration Map,Level 1 SIM,Logical Business Components,Management Domains,Operations,Enterp

12、riseManagement,Customer,Supplier/Partner,SI&P LifecycleManagement,Invoice/Payment,Technology,Workforce,Equipment,Enterprise,EAI Approach,EAI Roadmap,Level 1 P2P,Level 2 Message Bus,Level 3 Process Integration,Level 4 WWW Integratration,BEA WebLogic Integration,BEA WebLogic Integration,BEA WebLogic S

13、erver,Database,Java Virtual Machine,Operating System-Kernel,Network-TCP,Enterprise Integration,Portal,Applications,*Overview can be found at http:/,Application Server,J2EE CAContainer,ConnectionManager,TransactionManager,SecurityManager,Enterprise InformationSystem(e.g.SAP),EIS-specific Interface,Re

14、sourceAdapter,J2EE Connector Architecture(J2EE CA),Adapter Client Interface(e.g Client Connection Interface-CCI),Application Component(e.g.JSP,EJB),J2EE is transforming the EAI market the same way it transformed application servers.,BEAs Standards-Based Adapters,应用视图(Application View),WLI业务流程管理,IF,I

15、FPlug-In,XML,XML,应用视图,业务级别的带XML数据的服务和事件接口,200+Adapters Ready,Application adapters SAP R/3,Siebel,PeopleSoft,Oracle Applications,JD Edwards and more;Adapters for industry-specific compliance HIPAA,FIX,SWIFT and others;Utility adapters RDBMS,SMTP,FTP,HTTP and more;Technology adapters for legacy enviro

16、nments including mainframes,message queuing systems,EDI and others.超过200个Adapters业已就绪,且在不断扩展 中,Service Adapter Architecture,BEA Value Add,UDDIRegistry,WSDL,WebService,SOAP,ServiceConsumer,Points to description,Points to service,DescribesService,FindsService,Communicates withXML Messages,Web Services

17、 Technologies,Web Services,Web Services 是松耦合型系统整合的基础,SOAP Server,WebLogic“Thin”Java client,SOAP Client,WebLogic Server,J2EEApps,Other clients,SOAP Client,SOAP Client,OtherWebLogicApps,SOAP Server,Othervendor apps,SOAP Server,WebLogic Server,J2EE Apps,HTTP,HTTP,RMI,Enterprise Class Web Services,To su

18、pport enterprise integration scenarios,Web services must be built to support:AsynchronousMost systems do not return an immediate responseSupport message buffering to smooth spikes in loadEssential for scalability-Loosely-coupledSeparate internal implementation from public contractEnsure changes do n

19、ot“break”existing integrationsCourse Grained messagingIntegration at business document level(ex:purchase order,shipping notice)vs.pieces of dataBusiness processes change less frequently More network friendly,PO,Invoice,WebLogic Platform,Siebel,SAP,AI,BPM(Workflow),WebServices,Portal,JCA,JCA,WebLogic

20、 Integration,Portlets,WebLogic Portal,WebLogic Workshop,WebLogic Platform Solution,BEA WebLogic Server,ArchitectureTeam,Artifacts,BusinessTeam,SystemTeam,InformationModel,Implementation,DataModel,TN Contract,NGOSS The Itinerary“Proposed route of a journey”,BusinessEntity,TS Contract,BusinessTrade,NG

21、OSS Steering,SystemProcess Plan,BusinessFlow,Execution Script,BehaviorDriven,InformationDriven,Process Management,Turning customer desire into delivered goodsMaking business processes visible and maintainableScope of visibility must be end-to-endSeparation of control of business process from system

22、componentsBusiness process implementationPolicy Rule EngineEAI-based Workflow EngineHard-CodedXML languages(BPML,XPDL),原始的多层企业级的C/S架构,控制散落在各个层面上复杂的C/S控制图,state-machine基于状态变量企业组件彼此调用每一个组件均有可能执行其它组件的调用每一个组件均有可能成为网状调用的组成节点,Business Process的架构,所有的控制由流程引擎完成流程的流转由引擎通过P2P的调用完成,企业级的流程驱动架构,工作流,工作流引擎工作流定义和模板工

23、作流元素和节点(elements and nodes)工作流触发任务(Tasks)动作(Actions)功能(Functions)表达式(Expressions),WebLogic Integration,ArchitectureTeam,Artifacts,BusinessTeam,SystemTeam,InformationModel,Implementation,DataModel,TN Contract,NGOSS The Itinerary“Proposed route of a journey”,BusinessEntity,TS Contract,BusinessTrade,NG

24、OSS Steering,SystemProcess Plan,BusinessFlow,Execution Script,BehaviorDriven,InformationDriven,Information Driven Activities,Shared Info&Data(SID)ModelingKey to InteroperabilityBusiness Process and Experience DrivenNGOSS Meta-Model for Shared Info&Data,Architecture,Business,System,Behavior,Informati

25、on,Implementation,NGOSS The Landscape“View or vista of scenery”,Artifacts,Viewpoint focus on particular concerns within a system(IEEE Std 1471-2000),NGOSS Key Architectural Principles,Built using commercial off the shelf software,Implemented contract Interface specification,Common communicationInfra

26、structure,Common(shared)info,Separation of process and info,Common registry service,Process flow control,Common Interface Definitions,Separation of Process and Data,Common data directory,Common Comm.Infrastructure,Component based software,J2EE Vs NOGSS,Positioning statement:http:/www2.tmforum.org/va

27、.asp?linkID=5074,Process/Policy Engine,Communication Infrastructure Services,Shared Data Services,NGOSS Architectural Concepts,Architecture style or method of design and construction,e.g.CRM Billing Service Assurance Provisioning,e.g.Presentation Services Adaptation&Mediation Component Registry Secu

28、rity,Agenda,Introduction to NGOSS,Explore the NGOSS Maps,Business&System Views,Info&Implementation Views,Explore the Maps,Methodology the QuadrantsBusiness Viewpoint eTOMSystem Viewpoint SIMInformation Viewpoint SIDBehavior Viewpoint PM&PBMArchitecture TNAImplementation Viewpoint TSACompliance Viewp

29、oint VV&T,The Methodology is,A way of analyzing the business through its supply chains.A way of automating selected processes through the use of a variant of the Unified Software Development MethodologyA way of implementing and integrating systems to automate the selected processes which is usable a

30、cross most standard“full featured”technologies such as J2EE,CORBA,Java core,XML/SOAP and Publish/Subscribe and many others!,Architecture,Business,System,Behavior,Information,Implementation,NGOSS The Maps,Artifacts,Identify Need,Model Solution,Validate Model,Business Viewpoint,Business OrganizationeT

31、OM L1 MapBusiness Process SpecificationeTOM L2+Process MapsBusiness Process FlowPlan and Trades(realized through activity)eTOM L2+Scenario MapsBusiness InformationeTOM entity with attributes,TMN Layers correspond with TOM horizontals,TOM processes are captured in“FAB”area of eTOM Operations,eTOM map

32、s the NGOSS Business View,eTOM Business Process Framework Conceptual Structure,The Operations area,Operations,“FAB”is still the core of the Operations area Operations Support&Readiness is separated from FAB“OPS”also supports functional process groupings shown as horizontal layers,The Strategy,Infras

33、tructure&Product area,“SIP”encompasses strategy and lifecycle management processes in support of operationsStrategy&CommitInfrastructure Lifecycle ManagementProduct Lifecycle Management“SIP”also has functional groupings,aligned with those in“OPS”,Strategy,Infrastructure&Product,The Enterprise Manage

34、ment area,Enterprise Management,eTOM“Level 0 view of Level 1”,Operations,Fulfillment,Assurance,Billing,Operations Support&Readiness,Customer Relationship Management,Service Management&Operations,Resource Management&Operations,Supplier/Partner Relationship Management,The Operations area,ServiceConfig

35、uration&Activation,ServiceProblemManagement,Service QualityAnalysis,Action&Reporting,Service&Specific Instance Rating,SM&O Support&Process Management,ServiceManagement&Operations Readiness,Supplier/Partner Interface Management,S/P Buying,S/P Purchase Order Management,S/P Problem Reporting&Management

36、,S/P PerformanceManagement,S/P Settlements&BillingManagement,S/PRM OperationsSupport&Process Management,S/P Relationship ManagementOperationsReadiness,Resource Provisioning&Allocation to Service Instance,ResourceProblemManagement,RM&O Support&ProcessManagement,ResourceManagement&Operations Readiness

37、,Retention&Loyalty,Customer Interface Management,Billing&CollectionsManagement,CustomerQoS/SLA Management,ProblemHandling,Selling,Order Handling,MarketingFulfillmentResponse,CRM Operations Support&Process Management,CRM Operations Readiness,Sales&Channel Management,Resource Data Collection,Analysis&

38、Control,Resource QualityAnalysis,Action&Reporting,The SIP area,The Enterprise Management Hierarchy,NGOSS Methodology,Methodology system of principles and procedures applied to a discipline,Business Process Driven approach,Process Decompositions,Level 2,Level 3,Level 4,Architecture,Business,System,Be

39、havior,Information,Implementation,NGOSS The Maps,BusinessEntity,BusinessTrade,BusinessFlow,Artifacts,Identify Need,Model Solution,Validate Model,eTOM Business Process Flows,企业级的流程驱动架构,Architecture,Business,System,Behavior,Information,Implementation,NGOSS The Maps,BusinessEntity,BusinessTrade,Busines

40、sFlow,Artifacts,Identify Need,Model Solution,Validate Model,Business to System:Application Associations,Business Process Model,System Model,DetermineFree Ports,GenerateWorkOrder,DetermineRoute,Resource Mgmt System,Application Association,Logical System Components capture application support for busi

41、ness processes,Architecture,Business,System,Behavior,Information,Implementation,NGOSS The Maps,BusinessTrade,BusinessFlow,Artifacts,Identify Need,Model Solution,Validate Model,BusinessEntity,Business to System:SIDM Interactions,Data Association,Business Process Model,Shared Information Data Model,SI

42、D Model captures business and system information,Summary,eTOM provides the NGOSS Business MapeTOM includes a Business Process Framework which showsprocess structure(hierarchy)process decompositions(levels)process flows(linkages)process dynamics(behavior)eTOM links with the NGOSS System Viewapplicati

43、on associations(system structure)data associations(business&system information)eTOM is being used in NGOSS projects,Explore the Maps,Methodology the QuadrantsBusiness Viewpoint eTOMSystem Viewpoint SIMInformation Viewpoint SIDBehavior Viewpoint PM&PBMArchitecture TNAImplementation Viewpoint TSACompl

44、iance Viewpoint VV&T,Architecture,Business,System,Behavior,Information,Implementation,NGOSS The Maps,Artifacts,Identify Need,Model Solution,Validate Model,B2B interactions,SP ACustomer Role,SP BSupplier/Partner Role,NGOSS System MapValue Chain view,Architecture,Business,System,Behavior,Information,I

45、mplementation,NGOSS The Maps,Artifacts,Identify Need,Model Solution,Validate Model,InformationModel,TN Contract,SystemProcess Plan,Process Plan Analysis,Architecture,Business,System,Behavior,Information,Implementation,NGOSS The Maps,Artifacts,Identify Need,Model Solution,Validate Model,InformationMo

46、del,SystemProcess Plan,TN Contract,Process Plan knitting together system activities,Tech Neutral Contracts defining system activities,Shared Information to bind together system activities,Exposes,Implements,Exposes,Implements,Customer,Product,The Contract/Information,The Contract/Information,The bus

47、iness service that one process/organization performs for another is done by contractThe systems service that one component performs for another or that a component performs for a person is done by contractA contract isHow the service is invokedWhat information is exchangedA strict definition of the“

48、rules of use”of the service,The Contract/Information,Shared information is the language of the contractIt identifies the concepts and relationships of the information that is being exchangedShared information is not a database or enterprise wide dataShared information must communicate the same conce

49、pts as the business requires,but not necessarily in the same formXML and Web Services will be the best choice.,NGOSS Contract,Architecture,Business,System,Behavior,Information,Implementation,NGOSS The Maps,Artifacts,Identify Need,Model Solution,Validate Model,TN Contract,SystemProcess Plan,Informati

50、onModel,SIM Logical Business Components,Explore the Maps,Methodology the QuadrantsBusiness Viewpoint eTOMSystem Viewpoint SIMInformation Viewpoint SIDBehavior Viewpoint PM&PBMArchitecture TNAImplementation Viewpoint TSACompliance Viewpoint VV&T,Architecture,Business,System,Behavior,Information,Imple

展开阅读全文
相关资源
猜你喜欢
相关搜索
资源标签

当前位置:首页 > 建筑/施工/环境 > 项目建议


备案号:宁ICP备20000045号-2

经营许可证:宁B2-20210002

宁公网安备 64010402000987号