Telecom Enterprise Architecting Tuukka Valkeasuo, Accenture

advertisement
Telecom Enterprise Architecting
29.4.2011 Tuukka Valkeasuo, Accenture
Copyright © 2010 Accenture All Rights Reserved. Accenture, its logo, and High Performance Delivered are trademarks of Accenture.
1
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
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
Tuukka Valkeasuo
Tuukka Valkeasuo
Communications and High Tech
Manager
Areas of expertise
Functional
Industry
• Telecommunications
• Software industry
Accenture
Tampere, Finland
• Project management
• Telecom and ICT –processes and
strategies
• OSS/BSS and NE vendors
Mail: [email protected]
Tel: +358 772 5826
Selected telecoms experience
Professional background
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).
Copyright © 2010 Accenture All Rights Reserved.
• 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-12/2007: Enterprise
architecture design, main responsibility OSS (incl. fulfillment,
order management, service assurance, mediation)
• Nordic Telecom Operator, 12/2007-06/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.
4
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
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
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
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
Copyright © 2010 Accenture All Rights Reserved.
• Lean and horizontally layered
architectures
• Commercial packages
• Standards-based
• Best of suite
8
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.
9
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
Frameworks Guiding Telco Architecture Development
TMForum Business Process Framework eTOM
Strategy, Infrastructure & Product
Strategy &
Commit
Infrastructure
Lifecycle
Management
Operations
Operations
Operations
Support &
Readiness
Product
Lifecycle
Management
Marketing & Offer Management
Fulfillment
Assurance
Billing &
Revenue
Management
Customer Relationship Management
Service Development & Management
Service Management & Operations
Operations Support
& Readiness
Fulfillment
Customer Relationship
Management
CRM
Support &
Readiness
Marketing
Fulfillment
Response
Assurance
Billing & Revenue
Management
Customer Interface Management
Bill Payments & Receivables Mgt.
Selling
Order
Handling
Problem
Handling
Customer
QoS / SLA
Management
Bill Invoice
Management
Bill Inquiry
Handling
Manage
Billing Events
Charging
Retention & Loyalty
Resource Development & Management
(Application, Computing and Network)
Resource Management & Operations
(Application, Computing and Network)
Supply Chain Development & Management
Supplier/Partner Relationship Management
Service Management &
SM&O
Operations
Support &
Readiness
Resource Management &
Operations
RM&O
Support &
Readiness
Enterprise Management
Strategic & Enterprise
Planning
Enterprise Risk
Management
Financial & Asset
Management
Enterprise Effectiveness
Management
Stakeholder & External
Relations Management
Knowledge & Research
Management
Human Resources
Management
Copyright © 2010 Accenture All Rights Reserved.
Manage
Workforce
Supplier/Partner Relationship
Management
S/PRM
Support &
Readiness
Service
Configuration
& Activation
Service
Problem
Management
Service
Quality
Management
Service Guiding
& Mediation
Resource
Provisioning
Resource
Trouble
Management
Resource
Performance
Management
Resource Mediation
& Reporting
Resource Data Collection & Distribution
S/P
Requisition
Management
S/P Problem
Reporting &
Management
S/P
Performance
Management
S/P Settlements
& Payments
Management
Supplier/Partner Interface Management
11
Frameworks Guiding Telco Architecture Development
TMForum Telecom Applications Map TAM
Copyright © 2010 Accenture All Rights Reserved.
12
Frameworks Guiding Telco Architecture Development
TMForum Telecom Applications Map TAM
Copyright © 2010 Accenture All Rights Reserved.
13
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.
14
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
Management
Consulting
Technology
Outsourcing
Accenture Involvement
Opportunity
Phase
Time
Copyright © 2010 Accenture All Rights Reserved.
15
Architect in the Opportunity Phase
Engagements typically begin with an opportunity phase or a proposal
• Develops the Technology
Blueprint
• Develops Technology
Architecture sourcing
strategy
• Plans and leads execution
of technology and service
level-driven Proofs of
Concept (PoCs)
Opportunity Team
Opportunity
Lead
Opportunity
Manager
DCN SI Solution
Architect
Provides the DCN
components of the
solution plan
Human Performance
Architect
Provides expertise on
Human performance
requirements.
Solution
Architect
Owns the overall
solution plan, estimates,
cost & sourcing
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
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
QA Director
• Supporting development
by system integrator
teams
• Developing and
deploying productivity
enhancing tools and/or
techniques to system
integrator teams
PMO
Delivery QA
HR, CFM, Legal &
Commercial, etc.
Business / Appl.
Delivery
Analysis / Design / Build
for application
functionality
Technology
Architect
Testing
Lead
Realize the technology
Blueprint; provide
technical guidance to
the SI team
Define test plans, test
model; Manage test
execution and Break Fix
Conversion
Lead
Define conversion plans
covering data and
programs; Manage
execution of conversion
DCN
Provide support services across life cycle
• Identifying and
managing Technology
Risks
Copyright © 2010 Accenture All Rights Reserved.
17
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
Architect in the Delivery Phase
Technology Architect in the Analyze and Design Stages
ANALYZE
DESIGN
 Gathers client’s
requirements for
the Technology
Architecture
 Designs the Technology
Architecture for the
execution, development
and operational
environments
 Selects and
recommends
technologies,
leveraging
principles to
address
concerns
 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
Architect in the Delivery Phase
Technology Architect in the Build, Test and Deploy Stages
BUILD & TEST
DEPLOY
 Ensures the team is
following the approach
and plan
 Ensures the
deployed
components are
aligned with the
Technology
Architecture
blueprint
 Explains the details of
the Technology
Architecture to the
developers
 Validates that the
Technology Architecture
implementation is
aligned with the
Business Architecture
 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
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.
21
Case Study 1 - Architecture transformation for service
quality improvement
The Issues …
•Focus on Network Management instead
of end-to-end Service Management.
•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
Assessment
SA
master plan
The Journey …
The Vision ….
•Cost reduction through efficiency
improvement
•End-to-end Service Management 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
Execution
Planning
SA roadmap definition
and program launch
Copyright © 2010 Accenture All Rights Reserved.
• 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.
PoC and SW
selection
Implementation of
new Service Assurance platform
22
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.
23
Case Study 2 – EA Design and Transformation
The Issue
• 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.
•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
• Accenture worked with the client to
gather the needs and requirements,
and to design the architecture and
roadmaps for the implementation
Copyright © 2010 Accenture All Rights Reserved.
•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
24
Download
Related flashcards
Create Flashcards