Asug SAP HANA Presentation - Perceptive Technologies SAP
Linked In 1èRe Table Ronde 20110330
1. Le Réseau des professionnels de la
Business Intelligence en Suisse Romande
De l’utilité d’un ODS – Table ronde
Lausanne, le 30 Mars 2011
2. AGENDA
• 14h00 – 14h10 Le mot de bienvenue – Trivadis
• 14h10 – 14h15 Un mot sur le réseau sur LinkedIn – Dario Mangano
• 14h15 – 14h30 La BI chez Nespresso – Dario Mangano
• 14h30 – 14h45 La problématique ODS – Dario Mangano
• 14h45 – 15h15 Présentation de cas – Boris Horquin
• 15h15 – 15h30 Pause café
• 15h30 – 16h00 Présentation de cas – Michel Bridy
• 16h00 – 16h30 Discussion ouverte sur l’ODS
• 16h30 – 17h00 Présentation d’une solution ODS – Trivadis
• 17h00 – 17h15 Discussion sur les prochains sujets de table ronde
• 17h15 Conclusions et drink
6. La BI chez Nespresso
CIO
Knowledge
Management
Enterprise
Business
Content
Intelligence
Management
Unstructured Data Structured Data
From Data To Information To knowledge To Actions
7. La BI chez Nespresso
BI at HQ – Internal Organization
– 1st view: by activities
• Operational
• IT Projects
• Business Projects
– 2nd view: by BI layers / areas
• Back End
• Front End
• Infrastructure
– 3rd view: by interactions
• Businesses
• Markets
8. La BI chez Nespresso
The pre-existing Situation
Sources Integration Denormalization
SQL
CH
CEE ETL
FR BE
ProtoDWH
AU D-1 (Project)
DE Reporting DB
US
AS NesImports
ES
1156 reports, 2038 reports,
0 cubes 127 cubes, 0 reports, (1 cube)
1869 reports on cubes
Text
4 3
2 3
1
20
10
0
10 20 30 40 50
OLAP cubes Business Reports
9. La BI chez Nespresso
Roadmaps
DWH Foundation - IDH
Sources Integration Denormalization Presentation
ETL ETL
N1 CRM
Services
N2 Decoupling ETL
SCM
N3
IDH
ETL
Nn Quality FIN
.
. ETL
Nx HR
ETL
Web
Other
Tel
Other
Metadata
Real Time Operational reporting BI reports, Cubes
Operational reporting Control and QC reporting and Dashboards
10. La BI chez Nespresso
Roadmaps
DWH Foundation - IDH
IDH Reference Architecture – Components-Services View
Common Services Layer
Data Scheduler Process Exception Business Auditing Workflow Notification Data
Control Archiving Mgmt Rules Engine
Movement Movement
Data Import Layer Data Integration Layer Operational Integration Data Publication
Data Store Layer
MDH ETL Flat File
Staging MDH
Database
DB Load Datatype Extract
Flat File ETL 2
(files) Checks Integration Master Data such as Asset
Processes ETL/REPL DB Table(s)
and Account
Change Data 5
Data
DB Capture
DB Formatting
DB Table(s) ETL/ REPL Load ESB
Movement or
Formatting Identity Mgmt
Reference?
(DB)
4 Message
Cross Ref. (CDM)
Import Synchronization Mgmt Data
Staging Publication MOM
ESB Hierarchy
Message Message 3 D2
(CDM) Mgmt iTED Semantic
Capture Msg
RV (MOM) Match & Adapter from GIM
Form
Merge (optional )
D2 atting GIM
Transformation Transaction Data such as Data Access Layer
V1 Key Authorization Trade
Semantic Management
Archiving Authorization SQL 5
Adapter to GIM Target DB
Service Service
(optional) D1
Authentication Web
Service Service Subscriber
Archive iTED
Source DB Staging Application
Data Distribution
Publisher
Application KEY
Metadata Service
Data Quality Rules Configuration Rules Operational Metadata Process
Document 3
Created by FAAC Data Store
Created on May-5-2008 Metadata
Syntax File Syntax /
RI Semantic Structure Scheduler
RI Pub/Sub Enrichment Transform. LUW Data Lineage Operational DQ Profile Exception Store
Last Updated by CONMZC Rules Rules Rules Rules Entitlements Metadata Metadata Metrics Logs
Rules Config Rules Rules Rules
Last Updated on May-30-2008 Data Flow
Version 1.0
Location
Description / Objectives
The IDH reference architecture is
shown here from the perspective of Operations Console & Management Layer Metadata & Metrics Data Marts
its services are related to the Hub Operational
components of the IDH. Metadata Repair Archive Direct MD
Services Console Metatdata Update IDH DataMart IDH DataMart IDH DataMart
Console Console (e.g.
The diagram shows what services Configuration Reporting (e.g. (e.g.
each component is expected to 5 Performance) Data Quality) Data Lineage)
deliver. The components are what
will actually be built or bought must
deliver the services.
11. La problématique ODS
Sources
ETL - CDC
N1
Staging
N2
N3
ETL IDH
Nn
.
. ODS
Nx
Web
Tel
Other
Metadata
12. La problématique ODS
QUESTIONS :
• Pourquoi avons-nous besoins d’un ODS ?
• Historisation ?
• Scénario de reprise ?
• Alternatives ? (back-up des Stagings ?)
• Chargement par hub régional ?
• Etc.