Customer Perspectives: Oracle Data Integrator

2. The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

3. Customer Perspectives: Oracle Data Integrator JulienTestutProduct Manager

4. Meet Our Panel • Paul Stracke, Paychex • Manager, Software Engineering, Enterprise Information Solutions • Soeren Ahrens, Ross Stores • Senior Manager, Enterprise Architecture • GurcanOrhan, Turkcell • Software Architect & Expert Developer • Enterprise Architect of theYear 2011 • Oracle ACE Director

5. WHO AM I? +18years of IT experience. +9years of DWH experience. +5years of Oracle Data Integrator experience, +4years of Oracle Warehouse Builder experience. Cognos, Microstrategy, Business Objects, Oracle Business Intelligence Sybase Power Designer, CA ERwin Data Modeler Joined Turkcell October 2008, Turkcell Technology March 2010. DWH & BI Chair : TROUG (Turkish Oracle User Group) Published Customer Snapshot for NODI @Oracle.com Published Video «ODI for NODI» @Oracle.com Oracle Excellence Awards, Technologist of the Year 2011 : Enterprise Architect (copied : OracleMagazine’sEditors’ Choice of Awards : Architect of theYear) Oracle ACE Director (Business IntelligenceExpertise) http://gurcanorhan.wordpress.com http://www.twitter.com/gurcan_orhan http://tr.linkedin.com/in/gurcanorhan

6. TURKCELL GROUP – REGIONAL LEADER 9 countries 65.8 million subscribers Leadership in the region TurkcellGroup: Subscribers in Q212 (million) Listedon the NYSE and the ISEsince July 2000 (*) Revenues from Fintur (operations in Kazakhstan, Azerbaijan, Georgia, Moldova) is not included undersubsidiaries. The contribution of Fintur is recorded under share of profit of associates below EBITDA line. (**) Voice revenues include outgoing, incoming, roaming and other (comprising almost 2% of Turkcell Turkey) revenues

7. TURKCELL TECHNOLOGY We are an energetic team having more than 18years of experience combined with an ongoingcommitment to innovation. Team of 400+ people with 17 customers in 17 countries More than 10 years of experience in Turkcell ICT TTECH Center put into service 1994 - 2006 2007 2008 2009 2012 First out of group customers TTECH company formed with 44 engineers

8. 34,4 millionTurkcellCustomers • Talked 87 billionminutes • Sent 85 billiontextmessages (SMS) • 121 million MMS (Multimedia Messaging) • 26,5 million GB Internet usage WHAT WE ARE DEALING WITH (2011) • 31 December 2011 – 01 January 2012 • Talked 473 millionminutes • Sent 485 milliontextmessages (SMS) • 1,6 million MMS (Multimedia Messaging) • 0,21 million GB Internet usage

9. Introduction to NODI Results Obtained with NODI Best Practices in NODI

10. WHAT IS NODI ? N : Network O : Operations D : Data I : Infrastructure

11. WHAT IS NODI ? Heterogeneous Environment A DWH Approach • Various Vendors • Combining different subject areasin a historical way • Designed and Built for only Network Operations Division usage Reporting Statistical Methods • Finding correlations and relations between different operational systems and making trend analysis • Online and offline value added reporting • Offline and near-real-time data warehousing

12. WHY NODI? Decision Support Productive Network Planning • Decision Support System in Network Operations eco-system • Reporting idle equipments in field • Lights a way from history to future to manage network better and increase performance Trend Based Analysis Statistical Methods All-in-one Reporting • Reporting different Network related operational systems • Integrating different kinds of data, determining correlations and relations • Determining networking trends in a timely fashion period

13. NODI ARCHITECTURE PARTY LOCATION NETWORK ALARMS CONTRACT ADDRESS EQUIPMENT SUB-CONTRACT CUSTOMER COMPLAINTS RESPONSIBILITY NETWORK PERFORMANCE WORKORDERS PARTY & PARTY RELATION LOCATION HIERARCHY NETWORK PARAMETERS SITE ACQUISITION

14. NODI OFFLINE ARCHITECTURE GEO DB MAXIMO TeMIP OPTIMA MERLIN NEMS ERP replication daily extr (-1) daily extr (-1) daily extr-IKM fullextraction fullextraction fullextraction OPERATIONAL DATA STORE (Oracle 11G R2) STAGING AREA (Oracle 11G R2) DATA WAREHOUSE (Oracle 11G R2) STAGING AREA (Oracle 11G R2) DATA MARTS (Oracle 11G R2) Reporting System OLAP System

15. NODI ONLINE ARCHITECTURE EasyForms Merlin Merlin Sigos MYSQL Oracle Oracle MYSQL Application Integration Application Integration Application Integration Application Integration MSSQL MSSQL MSSQL Oracle Toledo Papirus Netflow Optima SysLog NG Sigos NOTS OSS file MYSQL MSSQL Sybase ASE daily load for Offline Reporting Offline Reporting Offline Reporting Offline Reporting Oracle Oracle Oracle Oracle Reportmaster Reportmaster Reportmaster Reportmaster

16. Introduction to NODI Results Obtained with NODI Best Practices in NODI

17. WHAT WE HAVE GAINED WITH NODI • Reducing Network Operations costs • Decreasing alarms and network faults • Faster responses to alarms to improve customer satisfaction • Decreasing network deduction and forecasting network alarms • Supporting Purchase Orders for equipment choices • Answer to which equipment works better with which one • KPI Analysis with Network Alarms and CustomerComplaints • Swift responsestocustomercomplaints • Network Optimization • Gathering information about complete Network Infrastructure

18. Introduction to NODI Results Obtained with NODI Best Practices in NODI

19. ALARM LOCATION DETERMINING ALGORITHM Column 1 VARCHAR2(400) ZCTREERT tcell_ns:.ana.rcoss5.rcss.ONRM_RtttMo SNW TSP TSP SXCXN03 Column 2 (VARCHAR2 (4000) Authentication Failure An authenticationFailure trap signifies that the sending protocol entity is the addressee of a protocol message that is not properly authenticated. -ProbableCause(ZSS)=Authentication Failure -EventType(ZSS)=Security service violation start_nss_tags @AlarmId=10156479912789340 @ManagedObject=SubNetwork=ONRM_RootMo,SubNetwork=TCP,ManagedElement=SXCXN04 @SpecificProblem=Authentication Failure @ProposedRepairAction=NONE @Class=ZCTREERTSX end_nss_tags Source:ZSSRC_FM

20. HOW ITS MADE * Average of 3 ~ 10 records produces per alarm * Average of 10 ~ 30 records produces per alarm Location Found ZCTREERTSX * Average of 80 ~ 200 records produces per alarm

21. DEVELOPMENT FACTS # of Variables 55 # of Interfaces 1127 # of ODI Procedures 50 # of Packages 124 # of Scenarios 1300 # of Integration KMs 5 # of Daily Steps >80.000 # of LoadingKMs 4 # of Tables 678 # of Projects 1 # of Columns >41.000 # of Daily Inserts > 1.000.000.000 # of Folders 83 # of Model Folders 39

22. BENEFITS • Benefits: • Implemented Knowledge Modules for substantial development time and effort savings • Development effort savings by 50% • Developed more than 1000 interfaces using ODI, 1 ETL crash peryear • Reduced ETL job run time from 20,000 seconds to 170 seconds • Why did we choose Oracle Data Integrator: • High performance with lightweight E-L-T architecture • Heterogeneity - compatible with non-Oracle applicationsand 3rd party systems • Knowledge Modules save development effort, highly configurable

23. THANK YOU Q & A http://gurcanorhan.wordpress.com http://www.twitter.com/gurcan_orhan http://tr.linkedin.com/in/gurcanorhan

25. The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract.It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.