Post on 25-Feb-2016
description
Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal1
Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal2
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.
Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 133
Customer Perspectives: Oracle Data IntegratorJulien TestutProduct Manager
Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal4
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
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 IntelligenceSybase 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.comPublished 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
TURKCELL GROUP – REGIONAL LEADER
9 countries 65.8 million subscribersLeadership in the region
Turkcell TurkeyKazakhstan
Ukraine Azerbaijan
Georgia Belarus
Moldova Northern Cyprus
Turkcell Europe
34.711.7
10.14.3
2.01.71.1
0.40.3
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
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
WHAT WE ARE DEALING WITH (2011)
34,4 million Turkcell CustomersTalked 87 billion minutesSent 85 billion text messages (SMS)121 million MMS (Multimedia Messaging)26,5 million GB Internet usage
31 December 2011 – 01 January 2012Talked 473 million minutesSent 485 million text messages (SMS)1,6 million MMS (Multimedia Messaging)0,21 million GB Internet usage
Results Obtained with NODIIntroduction to NODI
Best Practices in NODI
WHAT IS NODI ?
N : Network
O : Operations
D : Data
I : Infrastructure
WHAT IS NODI ?
Online and offline value added reportingOffline and near-real-time data warehousing
A DWH Approach
Designed and Built for only Network Operations Division usage
Reporting Statistical MethodsFinding correlations and relations between different operational systems and making trend analysis
Heterogeneous Environment
Various VendorsCombining different subject areas in a historical way
WHY NODI?
Determining networking trends in a timely fashion period
Productive Network Planning
Reporting idle equipments in fieldLights 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 ReportingReporting different Network related operational systemsIntegrating different kinds of data, determining correlations and relations
NODI ARCHITECTURE
ADDRESS
PARTY
CONTRACTSUB-CONTRACT
LOCATION
EQUIPMENT
PARTY & PARTY
RELATION
NETWORK ALARMS
RESPONSIBILITYCUSTOMER COMPLAINTS
NETWORK PERFORMANCE
WORKORDERS
NETWORK PARAMETERSLOCATION HIERARCHY
SITE ACQUISITION
NODI OFFLINE ARCHITECTURE
DATA WAREHOUSE (Oracle 11G R2)
replication daily extr (-1) daily extr (-1) daily extr-IKM
MAXIMO TeMIP OPTIMA MERLIN
OPERATIONAL DATA STORE (Oracle 11G R2)
STAGING AREA (Oracle 11G R2)
DATA MARTS (Oracle 11G R2)
STAGING AREA (Oracle 11G R2)
OLAP SystemReporting System
full extraction full extraction
NEMS ERP GEO DB
full extraction
NODI ONLINE ARCHITECTURE
MSSQL MSSQL
Oracle OracleOracle
Application Integration
Application Integration
Offline Reporting Offline Reporting
EasyForms Merlin
NOTS OSS
Offline Reporting
Sigos
daily load forOffline Reporting
SysLog NG
MYSQL Oracle
MSSQL Sybase ASEMYSQLfile
Toledo Papirus
Reportmaster
Reportmaster
Reportmaster
Oracle
Application Integration
SigosMYSQL
Optima
OracleReportmaster
MSSQL
Application Integration
MerlinOracle
Netflow
Results Obtained with NODIIntroduction to NODI
Best Practices in NODI
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
Results Obtained with NODIIntroduction to NODI
Best Practices in NODI
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 FailureAn 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 violationstart_nss_tags@AlarmId=10156479912789340@ManagedObject=SubNetwork=ONRM_RootMo,SubNetwork=TCP,ManagedElement=SXCXN04@SpecificProblem=Authentication Failure@ProposedRepairAction=NONE@Class=ZCTREERTSXend_nss_tags Source:ZSSRC_FM
HOW ITS MADEVALUE COLUMN_NAME
ZCTREERT COLUMN1
tcell_ns COLUMN1
ana COLUMN1
rcoss5 COLUMN1
rcss COLUMN1
ONRM_RtttMo COLUMN1
SNW COLUMN1
TSP COLUMN1
TSP COLUMN1
SXCXN03 COLUMN1
Authentication COLUMN2
Failure COLUMN2
An COLUMN2
authentication COLUMN2
Failure COLUMN2
trap COLUMN2
signifies COLUMN2
that COLUMN2
the COLUMN2
sending COLUMN2
protocol COLUMN2
entity COLUMN2
is COLUMN2
the COLUMN2
addressee COLUMN2
of COLUMN2
a COLUMN2
protocol COLUMN2
message COLUMN2
that COLUMN2
is COLUMN2
not COLUMN2
properly COLUMN2
authenticated COLUMN2
ProbableCause COLUMN2
ZSS COLUMN2
Authentication COLUMN2
Failure COLUMN2
EventType COLUMN2
ZSS COLUMN2
Security COLUMN2
service COLUMN2
violation COLUMN2
start_nss_tags COLUMN2
@AlarmId COLUMN2
10156479912789300 COLUMN2
@ManagedObject COLUMN2
SubNetwork COLUMN2
ONRM_RootMo COLUMN2
SubNetwork COLUMN2
TCP COLUMN2
ManagedElement COLUMN2
SXCXN04 COLUMN2
@SpecificProblem COLUMN2
Authentication COLUMN2
Failure COLUMN2@ProposedRepairAction COLUMN2
NONE COLUMN2
@Class COLUMN2
ZCTREERTSX COLUMN2
end_nss_tags COLUMN2
Source COLUMN2
ZSSRC_FM COLUMN2
VALUE COLUMN_NAMEZCTREERT COLUMN1rcoss5 COLUMN1rcss COLUMN1SNW COLUMN1TSP COLUMN1TSP COLUMN1SXCXN03 COLUMN1of COLUMN2ZSS COLUMN2ZSS COLUMN2TCP COLUMN2SXCXN04 COLUMN2ZCTREERTSX COLUMN2ZSSRC_FM COLUMN2
VALUE COLUMN_NAMEZCTREERT COLUMN1SXCXN03 COLUMN1SXCXN04 COLUMN2ZCTREERTSX COLUMN2ZSSRC_FM COLUMN2
Location FoundZCTREERTSX
* Average of 80 ~ 200 records produces per alarm
* Average of 10 ~ 30 records produces per alarm
* Average of 3 ~ 10 records produces per alarm
DEVELOPMENT FACTS
# of Variables 55
# of Interfaces 1127
# of ODI Procedures 50
# of Packages 124
# of Scenarios 1300
# of Daily Steps >80.000
# of Tables 678
# of Columns >41.000
# of Folders 83
# of Model Folders 39
5
4
# of Integration KMs
# of Loading KMs
# of Projects 1
# of Daily Inserts > 1.000.000.000
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 3rd party systems Knowledge Modules save development effort, highly configurable
http://gurcanorhan.wordpress.comhttp://www.twitter.com/gurcan_orhanhttp://tr.linkedin.com/in/gurcanorhan
Q & A
THANK YOU
Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal24
Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal25
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.
Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal26