1. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal 1

2. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal 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. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 13 3 Customer Perspectives: Oracle Data Integrator Julien Testut Product Manager

4. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal 4 Meet Our Panel  Paul Stracke, Paychex – Manager, Software Engineering, Enterprise Information Solutions  Soeren Ahrens, Ross Stores – Senior Manager, Enterprise Architecture  Gurcan Orhan, Turkcell – Software Architect & Expert Developer – Enterprise Architect of the Year 2011 – Oracle ACE Director

5. WHO AM I? +18 years of IT experience. +9 years of DWH experience. +5 years of Oracle Data Integrator experience, +4 years 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 : Oracle Magazine’s Editors’ Choice of Awards : Architect of the Year) Oracle ACE Director (Business Intelligence Expertise) http://gurcanorhan.wordpress.comhttp://www.twitter.com/gurcan_orhanhttp://tr.linkedin.com/in/gurcanorhan

6. TURKCELL GROUP – REGIONAL LEADER 9 countries 65.8 million subscribers Leadership in the region Turkcell Group: Subscribers in Q212 (million) Listed on the NYSE and the ISE since July 2000 (*) Revenues from Fintur (operations in Kazakhstan, Azerbaijan, Georgia, Moldova) is not included under subsidiaries. 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 18 years of experience combined with an ongoing commitment to innovation. More than 10 years of experience in Turkcell ICT TTECH Center put into service Team of 400+ people with 17 customers in 17 countries TTECH company formed with 44 engineers First out of group customers 20092008 201220071994 - 2006

8. WHAT WE ARE DEALING WITH (2011) 34,4 million Turkcell Customers Talked 87 billion minutes Sent 85 billion text messages (SMS) 121 million MMS (Multimedia Messaging) 26,5 million GB Internet usage 34,4 million Turkcell Customers Talked 87 billion minutes Sent 85 billion text messages (SMS) 121 million MMS (Multimedia Messaging) 26,5 million GB Internet usage 31 December 2011 – 01 January 2012 Talked 473 million minutes Sent 485 million text messages (SMS) 1,6 million MMS (Multimedia Messaging) 0,21 million GB Internet usage 31 December 2011 – 01 January 2012 Talked 473 million minutes Sent 485 million text messages (SMS) 1,6 million MMS (Multimedia Messaging) 0,21 million GB Internet usage

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

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

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

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

13. NODI ARCHITECTURE

14. NODI OFFLINE ARCHITECTURE DATA WAREHOUSE (Oracle 11G R2) replicationdaily extr (-1) daily extr-IKM MAXIMOTeMIPOPTIMAMERLIN OPERATIONAL DATA STORE (Oracle 11G R2) STAGING AREA (Oracle 11G R2) DATA MARTS (Oracle 11G R2) STAGING AREA (Oracle 11G R2) OLAP System Reporting System full extraction NEMSERP GEO DB full extraction

15. NODI ONLINE ARCHITECTURE MSSQL Oracle Application Integration Offline Reporting EasyFormsMerlin NOTSOSS Offline Reporting Sigos daily load for Offline Reporting SysLog NG MYSQLOracle MSSQLSybase ASEMYSQLfile ToledoPapirus Reportmaster Oracle Application Integration Sigos MYSQL Optima Oracle Reportmaster MSSQL Application Integration Merlin Oracle Netflow

16. Results Obtained with NODI Introduction to 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 Customer Complaints Swift responses to customer complaints Network Optimization Gathering information about complete Network Infrastructure

18. Results Obtained with NODI Introduction to 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 authentication Failure 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 VALUECOLUMN_NAME ZCTREERTCOLUMN1 tcell_nsCOLUMN1 anaCOLUMN1 rcoss5COLUMN1 rcssCOLUMN1 ONRM_RtttMoCOLUMN1 SNWCOLUMN1 TSPCOLUMN1 TSPCOLUMN1 SXCXN03COLUMN1 AuthenticationCOLUMN2 FailureCOLUMN2 AnCOLUMN2 authenticationCOLUMN2 FailureCOLUMN2 trapCOLUMN2 signifiesCOLUMN2 thatCOLUMN2 theCOLUMN2 sendingCOLUMN2 protocolCOLUMN2 entityCOLUMN2 isCOLUMN2 theCOLUMN2 addresseeCOLUMN2 ofCOLUMN2 a protocolCOLUMN2 messageCOLUMN2 thatCOLUMN2 isCOLUMN2 notCOLUMN2 properlyCOLUMN2 authenticatedCOLUMN2 ProbableCauseCOLUMN2 ZSSCOLUMN2 AuthenticationCOLUMN2 FailureCOLUMN2 EventTypeCOLUMN2 ZSSCOLUMN2 SecurityCOLUMN2 serviceCOLUMN2 violationCOLUMN2 start_nss_tagsCOLUMN2 @AlarmIdCOLUMN2 10156479912789300COLUMN2 @ManagedObjectCOLUMN2 SubNetworkCOLUMN2 ONRM_RootMoCOLUMN2 SubNetworkCOLUMN2 TCPCOLUMN2 ManagedElementCOLUMN2 SXCXN04COLUMN2 @SpecificProblemCOLUMN2 AuthenticationCOLUMN2 FailureCOLUMN2 @ProposedRepairActionCOLUMN2 NONECOLUMN2 @ClassCOLUMN2 ZCTREERTSXCOLUMN2 end_nss_tagsCOLUMN2 SourceCOLUMN2 ZSSRC_FMCOLUMN2 VALUECOLUMN_NAME ZCTREERTCOLUMN1 rcoss5COLUMN1 rcssCOLUMN1 SNWCOLUMN1 TSPCOLUMN1 TSPCOLUMN1 SXCXN03COLUMN1 ofCOLUMN2 ZSSCOLUMN2 ZSSCOLUMN2 TCPCOLUMN2 SXCXN04COLUMN2 ZCTREERTSXCOLUMN2 ZSSRC_FMCOLUMN2 VALUECOLUMN_NAME ZCTREERTCOLUMN1 SXCXN03COLUMN1 SXCXN04COLUMN2 ZCTREERTSXCOLUMN2 ZSSRC_FMCOLUMN2 Location Found ZCTREERTSX * Average of 80 ~ 200 records produces per alarm * Average of 10 ~ 30 records produces per alarm * Average of 3 ~ 10 records produces per alarm

21. DEVELOPMENT FACTS # of Variables55 # of Interfaces1127 # of ODI Procedures50 # of Packages124 # of Scenarios1300 # of Daily Steps>80.000 # of Tables678 # of Columns>41.000 # of Folders83 # of Model Folders39

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 per year  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 applications and 3 rd party systems  Knowledge Modules save development effort, highly configurable

23. http://gurcanorhan.wordpress.comhttp://www.twitter.com/gurcan_orhanhttp://tr.linkedin.com/in/gurcanorhan

24. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal 24

25. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal 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.

26. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal 26