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

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

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. 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 Sample Customers: Next Generation OSS Convergent solution Service-oriented Process-driven eTOM and FCAPS aware

3. 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) E-Plus survey – basic figures

4. Multi-brand concept – responding to the individual needs of different target groups Low prices, simple tariffs and offers Focus on core services Products and services where an established demand exists Cooperation deals with strong partners A challenger breaking up established structures More choice for customers An end to handset subsidies New market segments New price points E-Plus survey - Concentrating on what the customer wants

5. Agenda E-Plus Network & OSS strategy E-Plus OSS strategy “Next generation network planning” project Process transformation and documentation Process-oriented approach Example: SIP

6. Multi-brand concept Low prices, simple tariffs Focus on basic services Smart Follower strategy Multi vendor network strategy Outsourcing of network rollout and operation business strategy network strategy OSS strategy E-Plus survey – OSS Strategy Getting OSS as a managed IT service -> Flexibility Use of COTS products -> market drives developments Use of “COTS” processes -> simplification, incr. efficiency

7. plan build run Planning Support Systems OSS Stream 1: Processes Stream 2: Systems 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 month s ) increase efficiency for network planning and configuration (+50% activities) Configuration & Optimisation Strategic Planning, Parameter Planning, Inventory, Work-Flow, GIS, … Fault-, Performance-, Maintenance-, Service-, Incident-Management … Scope NGNP “Next Generation Network Planning” - Motivation

8. NGNP – System Transformation Legacy IT NGNP standardi z ation simplification

9. Process Transformation: Defining the scope Start with simplified processes (only good path) Focus on completeness, scope

10. Process Transformation: Structuring processes

11. Process Transformation: Standardization of scope

12. Process Transformation: Detailing down to Workflow level

13. Process Transformation: Standardization of workflow activities

14. Split of responsibilities E-Plus – OSS supplier In our strategy the OSS supplier does more than just deliver IT solutions! Build from eTOM level 3 processes Implementation and eTOM level 4 processes Field of standardization

15. 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)

16. 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

17. Example: New Simple Integration Process Legacy TOC process without flexibility for radio planner Complex dependency on other departments Unreliable network confirmation for accepted configuration SIP gathers several network activities Planner can choose the order of the actions Planner can see the dependencies Flexibility – plans realized within one day Flexibility – real time report on realized or skipped activities Integration process divided into Default configuration load Final/optimization load

18. Example: New Simple Integration Process Benefits Tight process integration 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

19. Q&A session http://ngnp.comarch.com Version 1.0