1. Copyright © TM Forum, 2008 All Rights Reserved. 1 Impact of SOA on TM Forum Specifications Tony Richardson (Senior Program Manager)

2. Copyright © TM Forum, 2008 All Rights Reserved. 2 Agenda  Brief Outline of TM Forum  Applying SOA – Service Delivery Framework (SDF)  SOA and NGOSS  Summary - Possible TM Forum / OASIS work areas

3. Copyright © TM Forum, 2008 All Rights Reserved. 3 About TM Forum World’s leading trade body focused on the management of telecom, cable, media & information services Improves the way that services are created, delivered, assured and charged through: Leadership & guidance Technology innovation & standards Practical solutions through an Ecosystem of members Improves the way that services are created, delivered, assured and charged through: Leadership & guidance Technology innovation & standards Practical solutions through an Ecosystem of members Members include service providers, network operators, software suppliers, equipment suppliers and systems integrators

4. Copyright © TM Forum, 2008 All Rights Reserved. 4 TM Forum Membership Around 700 members in over 70 countries: communications, cable, media, consumer electronics Geographical Spread Membership Distribution

5. Copyright © TM Forum, 2008 All Rights Reserved. 5 Collaboration Program

6. Copyright © TM Forum, 2008 All Rights Reserved. 6 Collaboration Program

7. Copyright © TM Forum, 2008 All Rights Reserved. 7 Convergence brings Opportunities and Challenges Web Media Cable TelecomAdvert ising Entertainment Technology kept many information markets separate Convergence allows entry into someone else's market Creates market explosion rather than coming together

8. Copyright © TM Forum, 2008 All Rights Reserved. 8 Service Delivery Framework (SDF) program

9. Copyright © TM Forum, 2008 All Rights Reserved. 99 Change of Communications Industry Landscape  Delivery of next generation services happens in a framework where the lines between Network and IT are blurred.  IT expands its footprint from supporting services to becoming part of the service to customer.  Customers / end Users have greater expectations for:  Blending existing and new services  Supply of services anywhere, anytime, and through any chosen access means.  Increasing pressure for efficient and effective Service Management.  Necessity for near-zero touch of business processes for delivering “next-gen services” by integrating existing systems (both for Telco / non-Telco SPs).  Need to create composite service marketplace across industry sectors that also need to be managed & monetized.  Service Providers need interoperability and agreed levels of compatibility across Service Delivery Platforms (SDPs).  New providers (e.g. Content) enter in the market and organizations operate using more complex business models.

10. Copyright © TM Forum, 2008 All Rights Reserved. 10 TM Forum’s Service Delivery Framework (SDF) programme  Address the industry challenge of producing an environment for the management of Next Generation Services.  S upports and integrates all aspects in the lifecycle of “next-gen services” delivered to a customer, across all the stakeholders, in an integrated Service Provider environment.  Unifies under a common logical view all the functions to support the service lifecycle: conceptualization, design, deployment, activation (execution), operation, retirement.  SDF operation is based upon a defined Reference Model, which itself is based upon SOA principles.  SDF impacts  Management specification for SDF will be realised through updates and additions to existing TM Forum artefacts (Business Process Framework, Information Framework etc.).  New specifications will be created by TM Forum (or liaised with other SDOs/Fora)  SDF will have impact on “new” B/OSS systems design and development.  Strong liaisons with other Industry Groups has been established in order to share the SDF vision / link into related work in these Groups. 10

11. Copyright © TM Forum, 2008 All Rights Reserved. 11 Attempt to position SDF and to illustrate relationship with OSS/BSS Device / Client Layer Transport Layer Access Layer IP / MPLS / PBT SONET / SDH / WDM Wireless: 2G, 3G WiFi, WIMAX Wireline: DSL, Cable, FTTx, PSTN Internet / 3 rd Parties / Enterprises OSS/BSS Platforms Service Layer Control Layer SS7SIP / IMS Application Servers SCE Application suites SDP SDF IMS

12. Copyright © TM Forum, 2008 All Rights Reserved. 12 Overall context for the “TM Forum SDF Reference Model” for SDF Services and their Management SDF ISS Consumer Infrastructure SDF Infrastructure Support Service Functional Interface SDF Service Functional Interface SDF Service Consumer Resource Consumer SDF Services SDF Infrastructure Support Services (SDF ISS) SDF Service Management Interface Consumer SDF Service Management Interface SDF Management Support Service Functional Interface Management Services SDF Management Support Services (SDF MSS) Infrastructure Consumer Resources In scope services Out of scope services In scope management/functional interfaces In scope consumer interfaces Out of scope management/functional interfaces Out of scope consumer interfaces Out of scope elements Items for further study Legend SDF ISS Consumer

13. Copyright © TM Forum, 2008 All Rights Reserved. 13 Industry Groups involvement  OMA  OSE / OSPE (open SDP for mobile service providers)  IPsphere  Pan-SP B2B agreements on supply of IP-based services  Parlay / Parlay X  Network Service interfaces  SDP Alliance  Practical best-of-breed SDP component integration  OASIS  IT capabilities for Service Component definition / combination  ETSI / TISPAN  NGN Sub-system components / Management Architecture  ITU-T / NGNMFG  NGN Management Roadmap  IEEE/NGSON  NGN Overlay Network  ATIS / TMOC  IPTV Management, NGS Accounting  CableLabs  Positioning of cable-based services / specifications

14. Copyright © TM Forum, 2008 All Rights Reserved. 14 TM Forum NGOSS Program

15. Copyright © TM Forum, 2008 All Rights Reserved. 15 NGOSS Frameworks Business Process Framework eTOM Information Framework SID Applications Framework TAM Architecture Framework TNA NGOSS (New Generation Operation Systems and Software) is based on four interrelated frameworks that form the core of the NGOSS program Business Process Framework – the eTOM Information framework – the SID Systems Architecture Framework – the TNA Applications Framework – the TAM NGOSS Frameworks

16. Copyright © TM Forum, 2008 All Rights Reserved. 16 1. Define the Business (Leadership Team, Business Process Engineers) 2. Architect the Business (Enterprise IT Architects) 3. Implement the Business (Development Org.) 4. Execute the Business (Operations) Business Contract 1 Implement Contract System Contract Deployment. Contract Business Contract 1 4 2 3 Corporate Knowledge Base NGOSS Knowledge Base Shared System Contract Business Contract 1 2 Implement Contract System Contract Business Contract 1 2 3 Contracts – Lifecycle Development

17. Copyright © TM Forum, 2008 All Rights Reserved. 17 Related OASIS Specifications SOA  OASIS SOA Reference Model TC Developing a core reference model to guide and foster the creation of specific, service- oriented architectures OASIS SOA Reference Model TC  OASIS Service Component Architecture / Bindings (SCA-Bindings) TC Standardizing bindings for SCA services and references to communication protocols, technologies and frameworks OASIS Service Component Architecture / Bindings (SCA-Bindings) TC  OASIS Service Component Architecture / BPEL (SCA-BPEL) TC Specifying how SCA component implementations for SOA can be written using BPEL OASIS Service Component Architecture / BPEL (SCA-BPEL) TC  OASIS Service Component Architecture / Policy (SCA-Policy) TC Defining an SCA policy framework to simplify SOA application development OASIS Service Component Architecture / Policy (SCA-Policy) TC Web Services  OASIS Framework for Web Services Implementation (FWSI) TC Defining methods and functional components for broad, multi-platform, vendor-neutral cross-industry implementation of Web services OASIS Framework for Web Services Implementation (FWSI) TC  OASIS UDDI Specification TC Defining a standard method for enterprises to dynamically discover and invoke Web services OASIS UDDI Specification TC  OASIS Web Services Quality Model TC Defining common criteria to evaluate quality levels for interoperability, security, and manageability of services OASIS Web Services Quality Model TC  OASIS Web Services Transaction (WS-TX) TC Defining protocols for coordinating the outcome of distributed application actions OASIS Web Services Transaction (WS-TX) TC  WSDM Management Using Web Services (WSDM-MUWS) v1.0 WSDM Management Using Web Services (WSDM-MUWS) v1.0

18. Copyright © TM Forum, 2008 All Rights Reserved. 18 Summary  Increasing - Telecom / IT Convergence  Business Processes - itSMF  eTOM /ITIL (IT Information Library - IT Service Management Forum)  Application of SOA – OASIS  SDF –  Development / Application of SDF Management Framework.  Linkage into OASIS specifications  NGOSS  Development / Application of NGOSS Contracts.  Extension of NGOSS specifications (eg eTOM, SID, TAM etc) into other SOA-based applications in other Industry Sectors

19. Copyright © TM Forum, 2008 All Rights Reserved. 19 Closing  Thanks for your Attention!  Questions?  Contact:  Tony Richardson  tonyr@tmforum.org tonyr@tmforum.org  +44 1394 386293

20. Copyright © TM Forum, 2008 All Rights Reserved. 20 Additional Information

21. Copyright © TM Forum, 2008 All Rights Reserved. 21 NGOSS  NGOSS  New Generation Operation Systems and Software

22. Copyright © TM Forum, 2008 All Rights Reserved. 22 Enterprise Management Strategy, Infrastructure & ProductOperations FulfillmentAssuranceBillingProduct Lifecycle Management Infrastructure Lifecycle Management Operations Support & Readiness Customer Relationship Management Service Management & Operations Resource Management & Operations Supplier/Partner Relationship Management Strategy & Commit Marketing & Offer Management Service Development & Management Resource Development & Management Supply Chain Development & Management (Application, Computing and Network) Customer Enterprise Effectiveness Management Knowledge & Research Management Enterprise Risk Management Strategic & Enterprise Planning Financial & Asset Management Stakeholder & External Relations Management Human Resources Management Business Process Framework (eTOM)

23. Copyright © TM Forum, 2008 All Rights Reserved. 23 Product Market / Sales Market Strategy & Plan Market Segment Marketing Campaign Competitor Contact/Lead/Prospect Sales StatisticSales Channel Product Product SpecificationProduct Offering Strategic Product Portfolio Plan Product Performance Product Usage Customer Customer Interaction Customer Order Customer Statistic Customer Problem Customer SLA Service Service Specification Service Applications Service Configuration Service Performance Service Usage Resource Supplier / Partner S/P Plan S/P Interaction S/P Product S/P Order S/P SLA Enterprise Common Business Party Location Business Interaction PolicyAgreement Applied Customer Billing Rate Customer Bill Customer Bill Collection Customer Bill Inquiry Service Strategy & Plan Service TroubleService Test Resource Resource Specification Resource Topology Resource Configuration Resource Performance Resource Usage Resource Strategy & Plan Resource TroubleResource Test S/P Problem S/P Statistic S/P Bill Inquiry S/P Payment S/P PerformanceS/P Bill (Under Construction) Revenue Assurance Usage Root Base Types Project Time Information Framework (SID)

24. Copyright © TM Forum, 2008 All Rights Reserved. 24 Resource Design / Assign Customer Mgt Service Mgt Resource Mgt Resource Inventory Mgt Resource Status Monitoring Resource Problem Management Resource Performance Monitoring/ Management Resource Performance Monitoring/ Management Workforce Mgt Resource Logistics Correlation & Root Cause Analysis Resource Activation Customer QOS/ SLA Mgt Customer Billing Management Customer Billing Management Customer Service / Account Problem Resolution Customer Service / Account Problem Resolution Service Design / Assign Service Design / Assign Product / Service Catalog Management Service Rating / Discounting Management Service Rating / Discounting Management Receivables Management Receivables Management Voucher Management Service Config Mgt Service Config Mgt Arbitrage Management Resource Testing Mgt Resource Data Mediation Billing Data Mediation Service Quality Monitoring & Impact Analysis Service Performance Mgt Service Performance Mgt Service Problem Mgt Service Problem Mgt Resource Planning/ Optimization Resource Planning/ Optimization Enterprise Management Customer Contact, Retention & Loyalty Product Management Market / Sales Management Supplier / PartnerManagement Partner Management Product Lifecycle Management Supply Chain Management Campaign Management Channel Sales Management Security Management Security Management HR Management HR Management Asset Management Asset Management Knowledge Management Knowledge Management Financial Management Financial Management Resource Provisioning / Configuration Customer Self Management Order Mgt Product Performance Management Product Strategy / Proposition Management The TAM R2.0 Corporate Sales Management Customer Information Management Bill Formatting Bill Formatting Invoicing Quotation Engine Quotation Engine Collections Management Collections Management Service Inventory Mgt Service Inventory Mgt Service Specification Mgt Service Specification Mgt Resource Specification Management Resource Domain Management (IT Computing, IT Applications, Network) Integration infrastructure: bus technology/ middleware / business process management SLA Mgt Real-time Billing Management Real-time Billing Management Oper Support & Readiness FulfillmentAssuranceBilling Fraud Management Fraud Management Revenue Assurance Management Revenue Assurance Management

25. Copyright © TM Forum, 2008 All Rights Reserved. 25 NGOSS Contracts and the Frameworks  NGOSS (eg eTOM, and SID etc) can be used to define business interactions across an intended interworking boundary, where the Contract is positioned  This boundary remains fixed as we move around the NGOSS Lifecycle, but our focus on the interactions will shift  In the Business View, we concentrate on process (eTOM) and the information (SID) on which the processes act  In the System View, process is a requirements influence, but a solution/system architecture now forms, and system interactions across the boundary are defined to support/realize the process needs  The TNA provides a structure for the system design  TAM can be used to guide positioning of Contracts against anticipated system “blocks” – TAM applications can be characterized by the Contracts they provide/use

26. Copyright © TM Forum, 2008 All Rights Reserved. 26 Populating the Contract Model  A range of elements should be addressed in defining a Contract  NGOSS helps us by providing source material that can be used for each specific Contract  eTOM for the System Process definitions  SID for the Entity definitions (SID also assists with Policy definitions)  TAM for the System Capability definitions (and System Operation definitions at a more detailed level)  TNA for the system environment supporting Contract operation  Each of these elements has a part to play in characterising the required behaviour of the Contract  In some cases, lower-level detail may be appropriate, using NGOSS extensions

27. Copyright © TM Forum, 2008 All Rights Reserved. 27 TM Forum SDF program: Phase II Deliverables Communication to TM Forum and Industry TM Forum SDF Program Phase 2 Other Industry Groups contributions TM Forum Board strategic indications Other TM Forum work areas Tool selection SDF Industry Groups Positioning Document SDF Business Agreement SDF Overview SDF Reference Model specification / enhancement SDF Management Requirements specification SDF positioning respect to related work in other Industry Groups TR 139 TMF 519 TR 141

28. Copyright © TM Forum, 2008 All Rights Reserved. 28 TMF 519: SDF Business Agreement - Requirements  Main characteristics  The SDF Business Agreement document contains the Requirements that define the Service Delivery Framework o List of Business Objectives (19) o List of Technical Objectives (12)  SDF requirements are divided in categories (in line with Reference Model): o Requirements on SDF Infrastructure (25) o Requirements on SDF Managed Entities (9) o Requirements on SDF Management (34) o Requirements on SDF Functional Capabilities (10) o Requirements on SDF support for Customer, Supplier and Partner relationships (6)  Some info on the “process” to define the BA  Specific use cases were developed to define scenarios for SDF and gather requirements  BA document obtained by active team commitment: more than 20 written contributions, ad-hoc meetings / calls, debate and synthesis  The SDF team usage of a tool (IBM RequisitePro) for Requirements capture / cross reference etc.

29. Copyright © TM Forum, 2008 All Rights Reserved. 29 Examples of SDF Requirements  Requirements on SDF Infrastructure  The SDF Infrastructure MUST enable flexible mash up, composition and reuse of pre- packaged elements. It must be based on standard IT technology as used in other industries to leverage economy of scale and maximize support.  The SDF Infrastructure MUST enable management of services as they are reused, reprogrammed or composed.  The SDF Infrastructure MUST provide SDF Services catalogues and other repositories (e.g. metadata), which contain all the elements (e.g. existing SDF Services, their dependencies, etc.) available to build new SDF services.  Requirements on SDF Managed Resources  Every SDF Service in the SDF MUST provide a “SDF Service Management Interface” to enable exposure of all appropriate operation and management functions (such as, but not limited to: configuration, performance management, retirement, fault handling, versioning, monitoring, usage, etc.) of the SDF Service.  For the SDF to be able to manage a resource that is outside the scope of SDF, that resource MUST be exposed as a SDF Service.  Requirements on SDF Management  The SDF MUST support functionality to enable the management of the lifecycle of SDF Services.  The SDF MUST enable the configuration of specific performance parameters for SDF Services by means of the SDF Service Management Interface (SDF Service MI) (e.g. driven by customer experience).  Requirements on SDF Functional Capabilities  The SDF MUST support an explicit state model which enables the management of the lifecycle of a SDF Service.

30. Copyright © TM Forum, 2008 All Rights Reserved. 30 Cooperation with Other Industry Groups

31. Copyright © TM Forum, 2008 All Rights Reserved. 31 Other Industry Group Liaisons DMTF (Distributed Management Task Force) 3GPP (3rd Generation Partnership Program) ETSI (European Telecommunications Standards Institute) ITU-T International Telecommunications Union ATIS (Alliance of Telecommunications Industry Solutions) TTC (The Telecommunication Technology Committee) OIF (Optical Internetworking Forum) MEF (Metro Ethernet Forum) MSF (Multi-service Forum) OMG (Object Management Group) RosettaNet (eBusiness) QuEST (Quality Excellence for Suppliers of Telecommunications) TOG (The Open Group) IPDR (IP Detailed Record organization) OMA (Open Mobile Alliance) IMSF (IMS Forum)