Telecom Enterprise Architecting Tuukka Valkeasuo, Accenture

Transcription

2 Agenda Introduction Enterprise Architectures in Telecoms Industry Standards and Frameworks in Telecom EA Architecture as a Profession Consultants Role Case Study 1 Architecture transformation for service quality improvement Case Study 2 EA Design and Transformation Copyright 2010 Accenture All Rights Reserved. 2

3 Agenda Introduction Enterprise Architectures in Telecoms Industry Standards and Frameworks in Telecom EA Architecture as a Profession Consultants Role Case Study 1 Architecture transformation for service quality improvement Case Study 2 EA Design and Transformation Copyright 2010 Accenture All Rights Reserved. 3

4 Tuukka Valkeasuo Tuukka Valkeasuo Communications and High Tech Manager Accenture Tampere, Finland Areas of expertise Functional Project management Telecom and ICT processes and strategies OSS/BSS and NE vendors Industry Telecommunications Software industry Professional background Mail: Tel: Tuukka is Manager at Accenture. In addition to the career at Accenture, he has worked as a freelancer consultant for German and Dutch system integrators and teleoperators. Tuukka has during the past +10 years been involved in consulting and delivery of OSS projects for over 20 teleoperators globally (mainly Europe, Middle East, South America). Selected telecoms experience Tuukka is specialized in teleoperator and OSS/BSS processes, architectures and strategies. Tuukka has been recognized as a subject matter expert of OSSsolutions in Accenture s global projects, and he is also responsible for OSS-domain of Accenture Finland Network Practice. Selected examples: Nordic Telecom Operator, 05/ /2007: Enterprise architecture design, main responsibility OSS (incl. fulfillment, order management, service assurance, mediation) Nordic Telecom Operator, 12/ /2008: Service delivery architecture analysis and design, blueprint, roadmap, target architecture, OSS/BSS interfaces. Full composition of RFP sent to vendors for the solution (multiple products). Middle-East, multi-phased: Definition of target OSS architecture, assessment and gap-analysis of as-is and to-be architectures, vendor analysis, preparation of RFP. Copyright 2010 Accenture All Rights Reserved. 4

5 Accenture in Brief Overview Accenture is a global management consulting, technology services and outsourcing company, with more than 215,000 people serving clients in more than 120 countries We have extensive relationships with the world's leading companies and governments and work with organizations of all sizes including 94 of the Fortune Global 100 and more than three quarters of the Fortune Global 500 In 2011, Accenture ranked No. 49 among Fortune's Top 50 World s Most Admired Companies and maintained its No. 2 position in the Information Technology Services category. Finland More than 1100 employees The best place to work in Finland in 2007, 2008, 2009, 2010 From Finland s 20 largest companies Accenture co-operates with 16 (Talouselämän 500 suurinta list). Copyright 2010 Accenture All Rights Reserved. 5

6 Accenture in Brief The Accenture market facing structure is organized into five operating groups tailored per industry As part of the Communications and High Tech group, the Network Practice serves the need of Telco Operators and Service Providers Copyright 2010 Accenture All Rights Reserved. 6

7 Agenda Introduction Enterprise Architectures in Telecoms Industry Standards in Telecom EA Architecture as a Profession Consultants Role Case Study 1 Architecture transformation for service quality improvement Case Study 2 EA Design and Transformation Copyright 2010 Accenture All Rights Reserved. 7

8 The Legacy of Teleoperators Architectures Telco operators can be divided in two in terms of their architecture legacy Complex Legacy Architectures Incumbents, telcos with long history Mergers and acquisitions Organizational impacts Unavailability of commercial applications Technology silos Custom development In-house architecture frameworks Best of breed Greenfield Architectures Recent startups xvnos (virtual operators) Non-merged subsidiaries Managed services Lean and horizontally layered architectures Commercial packages Standards-based Best of suite Copyright 2010 Accenture All Rights Reserved. 8

10 The Need of Industry Standards/Frameworks Fragmented and custom-oriented history of telecom architectures raised a need for: Common language Convergence and new technologies New services Capability for comparisons and gap analysis By using industry frameworks telco operators and service providers can achieve Analysis of as-is situation Jump-start for new design and development Completeness of the design Common understanding across organization Copyright 2010 Accenture All Rights Reserved. 10

11 Frameworks Guiding Telco Architecture Development TMForum Business Process Framework etom Strategy, Infrastructure & Product Strategy & Commit Infrastructure Lifecycle Marketing & Offer Service Development & Product Lifecycle Resource Development & (Application, Computing and Network) Supply Chain Development & Operations Operations Support & Readiness Fulfillment Assurance Billing & Revenue Customer Relationship Service & Operations Resource & Operations (Application, Computing and Network) Supplier/Partner Relationship Operations Operations Support & Readiness Customer Relationship CRM Support & Readiness Service & SM&O Operations Support & Readiness Fulfillment Assurance Billing & Revenue Marketing Fulfillment Response Selling Order Handling Service Configuration & Activation Customer Interface Problem Handling Retention & Loyalty Service Problem Customer QoS / SLA Service Quality Bill Payments & Receivables Mgt. Bill Invoice Manage Billing Events Bill Inquiry Handling Charging Service Guiding & Mediation Enterprise Strategic & Enterprise Planning Financial & Asset Enterprise Risk Stakeholder & External Relations Enterprise Effectiveness Human Resources Knowledge & Research Resource & RM&O Operations Support & Manage Readiness Workforce Supplier/Partner Relationship S/PRM Support & Readiness Resource Provisioning S/P Requisition Resource Trouble Resource Data Collection & Distribution S/P Problem Reporting & Resource Performance S/P Performance Supplier/Partner Interface Resource Mediation & Reporting S/P Settlements & Payments Copyright 2010 Accenture All Rights Reserved. 11

15 Accenture Involvement What is a Consultant? Type of consultancy varies during the client relationship lifecycle Client relationship can consist of one or more phases Consultants role and architecture work is different depending on the phase Client Relationship Opportunity Phase Consulting Technology Outsourcing Time Copyright 2010 Accenture All Rights Reserved. 15

16 Architect in the Opportunity Phase Engagements typically begin with an opportunity phase or a proposal Develops the Technology Blueprint Develops Technology Architecture sourcing strategy Opportunity Team DCN SI Solution Architect Provides the DCN components of the solution plan Opportunity Lead Solution Architect Owns the overall solution plan, estimates, cost & sourcing Opportunity Manager Plans and leads execution of technology and service level-driven Proofs of Concept (PoCs) Human Performance Architect Provides expertise on Human performance requirements. Business/Application Architect Provides expertise on industry, domain, client, application and functional requirements Technology Architect Creates the technology blueprint for the solution & technical guidance Delivery Lead Provides delivery Knowledge and takes ownership of plans through to delivery Identifies and manages technology risks and assumptions of the solution Copyright 2010 Accenture All Rights Reserved. 16

17 Architect in the Delivery Phase Projects are delivered to the client with varying setups of Accenture and client resources Creating the Technology Architecture Delivery Team Delivery Lead Supporting development by system integrator teams QA Director Delivery QA PMO HR, CFM, Legal & Commercial, etc. Developing and deploying productivity enhancing tools and/or techniques to system integrator teams Business / Appl. Delivery Analysis / Design / Build for application functionality Provide support services across life cycle Technology Architect Realize the technology Blueprint; provide technical guidance to the SI team DCN Testing Lead Define test plans, test model; Manage test execution and Break Fix Conversion Lead Define conversion plans covering data and programs; Manage execution of conversion Identifying and managing Technology Risks Copyright 2010 Accenture All Rights Reserved. 17

18 Architect in the Delivery Phase Technology Architect in Planning Phase PLAN Documents and solidifies the Architecture Guiding Principles Recognizes and prioritizes the nonfunctional requirements, balancing concerns Drives the conceptual definition of the Technology Architectures Analyzes technology trends and other best practices Sells the Technology Architecture to the Business Architect and the Client Copyright 2010 Accenture All Rights Reserved. 18

19 Architect in the Delivery Phase Technology Architect in the Analyze and Design Stages ANALYZE Gathers client s requirements for the Technology Architecture Selects and recommends technologies, leveraging principles to address concerns DESIGN Designs the Technology Architecture for the execution, development and operational environments Establishes the direction of the Technology Architecture team to the design of technology components, or realization of proofs-ofconcept or prototypes. Designs the most difficult or complex components Copyright 2010 Accenture All Rights Reserved. 19

20 Architect in the Delivery Phase Technology Architect in the Build, Test and Deploy Stages BUILD & TEST Ensures the team is following the approach and plan Explains the details of the Technology Architecture to the developers Validates that the Technology Architecture implementation is aligned with the Business Architecture DEPLOY Ensures the deployed components are aligned with the Technology Architecture blueprint Ensures that all the components work together to support the systems and business Ensures the functional and non-functional requirements are tested Copyright 2010 Accenture All Rights Reserved. 20

22 Case Study 1 - Architecture transformation for service quality improvement The Issues Focus on Network instead of end-to-end Service. Focus is on symptoms and not in the root cause. Inability to perform proactive SA Lack of IT infrastructure to support SLAs based on Network data (QoS). Architecture of network surveillance & fault management is based on Silo approach. 60 different systems support the processes. Various technologies, customer views across many layers The Vision. Cost reduction through efficiency improvement End-to-end Service for all networks including NGN. Root cause analysis. Improve Customer Satisfaction. Support SLA based on network data. The Methodology. Use COTS products Adopt Standards and best practices. Learn from similar projects The Journey Started 2 years ago Teamwork Technology IT NOCs Market research. Agree on a Master Plan. Define Architecture. Prioritization of program phases. Proof of Concept RfP for first set of Network and Services. Assessment Planning Execution SA master plan SA roadmap definition and program launch PoC and SW selection Implementation of new Service Assurance platform Copyright 2010 Accenture All Rights Reserved. 22

24 Case Study 2 EA Design and Transformation The client approached Accenture to analyze the possibility of implementing a SOA based IT strategy. Based on the analysis it became evident that the client was rather looking analyze the possibility of an enterprise architecture Transformation. Accenture worked with the client to gather the needs and requirements, and to design the architecture and roadmaps for the implementation The Issue Massively complex legacy architecture No capability to respond to business needs Long time-to-market High operating cost High churn The Vision Be bold re-design the enterprise architecture Use commercial best of suite applications Significantly lower costs Quick business and customer benefits The Journey Start by understanding business needs and requirements Keep people, processes, and technology linked Design the business capability roadmap Design architecture to fulfill the business capabilities Start the implementation according to the plan Copyright 2010 Accenture All Rights Reserved. 24