eTOM framework as key component of process reengineering during implementation of Network Planning system
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

eTOM framework as key component of process reengineering during implementation of Network Planning system

  • 3,787 views
Uploaded on

E-plus and Comarch presentation during TM Forum Team Action Week in Paris in January 2011 titled: eTOM framework as key component of process reengineering during implementation of Network Planning......

E-plus and Comarch presentation during TM Forum Team Action Week in Paris in January 2011 titled: eTOM framework as key component of process reengineering during implementation of Network Planning system

More in: Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
3,787
On Slideshare
3,787
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
219
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. eTOM framework as key component of process reengineering during implementation of Network Planning system
    Heinz Wudtke Jakub Zaluski-Kapusta
    Team Manager P&S OSS Consulting
    & Product Management
    E-Plus Mobilfunk GmbH & Co. KG Comarch
  • 2. Next Generation OSS
    • Convergent solution
    • 3. Service-oriented
    • 4. Process-driven
    • 5. eTOM and FCAPS aware
    Sample Customers:
    T-Mobile Austria and Germany
    O2 Germany GmbH & Co. OHG, Germany
    Vodafone Group
    E-Plus Deutschland, Germany
    Polkomtel SA, Poland
    TPSA – Polish Telecom (FT Group), Poland
    Bouygues Telecom, France
    Auchan, France
    Vistream, Germany
    PTC / Era (T-Mobile Group), Poland
    Bite Latvia and Lithuania
    Vivacom (BTC Group), Bulgaria
    Crnogorski Telekom, Montenegro
    Tele Yemen, Yemen
  • 6. E-Plus survey – basic figures
    E-Plus Mobilfunk GmbH & Co KG was founded in 1993; market launch in 1994
    Since 2002 the Dutch telecoms group KPN has been the sole shareholder of E-Plus
    The telecommunications service provider is active in the Netherlands, Belgium, France, Germany and Spain
    The E-Plus Group ranks number 3 in the German mobile telecommunications market and is currently the fastest and most profitably growing network operator
    Annual revenues: 3.2 billion euros
    EBITDA: 1.3 billion euros, EBITDA Margin 41,9 %
    19 million customers
    Approximately 2,500 employees (FTE = Full Time Equivalent)
  • 7. E-Plus survey - Concentrating on what the customer wants
    • Multi-brand concept – responding to the individual needs of different target groups
    • 8. Low prices, simple tariffs and offers
    • 9. Focus on core services
    • 10. Products and services where an established demand exists
    • 11. Cooperation deals with strong partners
    A challenger breaking up established structures
    • New market segments
    • 12. New price points
    • 13. More choice for customers
    • 14. An end to handset subsidies
  • Agenda
    E-Plus Network & OSS strategy
    E-Plus OSS strategy
    “Next generation network planning” project
    Process transformation and documentation
    Process-oriented approach
    Example: SIP
  • 15. E-Plus survey – OSS Strategy
    Multi-brand concept
    Low prices, simple tariffs
    Focus on basic services
    business
    strategy
    Smart Follower strategy
    Multi vendor network strategy
    Outsourcing of network rollout and operation
    network
    strategy
    Getting OSS as a managed IT service -> Flexibility
    Use of COTS products -> market drives developments
    Use of “COTS” processes -> simplification, incr. efficiency
    OSS
    strategy
  • 16. “Next Generation Network Planning” - Motivation
    Scope:
    planning, building, configuration and optimization processes (e2e) for the radio, transport and core network
    Objectives:
    reduce time to market for new technologies (target 1 – 3 months)
    increase efficiency for network planning and configuration (+50% activities)
    plan
    build
    run
    Stream 1: Processes
    Stream 2: Systems
    Configuration &
    Optimisation
    Strategic Planning, Parameter Planning, Inventory, Work-Flow, GIS, …
    Fault-, Performance-, Maintenance-,
    Service-, Incident-Management …
    Planning Support Systems
    OSS
    Scope NGNP
  • 17. NGNP – System Transformation
    Legacy IT
    NGNP
    standardization
    simplification
  • 18. Process Transformation: Defining the scope
    • Start with simplified processes (only good path)
    • 19. Focus on completeness, scope
  • Process Transformation: Structuring processes
  • 20. Process Transformation: Standardization of scope
  • 21. Process Transformation: Detailing down to Workflow level
  • 22. Process Transformation: Standardization of workflow activities
  • 23. Split of responsibilities E-Plus – OSS supplier
    Build from eTOM level 3 processes
    Implementation and eTOM level 4 processes
    Field of standardization
    In our strategy the OSS supplier does more than just deliver IT solutions!
  • 24. Process oriented approach
    All network operator operations grouped in processes
    By technology (MV, LL, Transport, …)
    By operation (new NE, change, retirement, …)
    By business role – supporting processes
    Business level
    What is done when
    Technical level – Frameworx view
    Mapping with interfaces
    (which application is required when)
    Mapping with Business Objects
    (which data is modified when)
    Mapping with systems
    (which operation is done where)
  • 25. Technical processes identification
    Business processes covering business activities
    Technical realization of the processes based on OSS tools
    All inventory & planning data with tools available within process task forms
    SID & applications
  • 26. Example: New Simple Integration Process
    • SIP gathers several network activities
    • 27. Planner can choose the order of the actions
    • 28. Planner can see the dependencies
    • 29. Flexibility – plans realized within one day
    • 30. Flexibility – real time report on realized or skipped activities
    • 31. Integration process divided into
    • 32. Default configuration load
    • 33. Final/optimization load
    Legacy TOC process without flexibility for radio planner
    Complex dependency on other departments
    Unreliable network confirmation for accepted configuration
  • 34. Example: New Simple Integration Process
    Benefits
    Tightprocessintegration with Configuration Management and network integration
    Management and network integration
    Processes focus on best tool usage
    Limited mistakes in activities, due to full control of the network
  • 35. Q&A sessionhttp://ngnp.comarch.com
    Version 1.0